Skip to content

Tools to facilitate access to Moose, e.g., generating MSE files from source code

License

Notifications You must be signed in to change notification settings

moosetechnology/Moose-Easy

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

36 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Moose-Easy

Master: Build Pass

Tools to facilitate access to Moose, e.g., generating MSE files from source code.

If Moose-Easy is not loaded in your image, you can do so with:

Metacello new
  baseline: 'MooseEasy';
  repository: 'github://moosetechnology/Moose-Easy';
  load.

Famix Maker

Create MSE files easily, provided you have installed VerveineJ.

wizard := MooseEasyFamixMaker new
    verveineJScriptPath: 'path/to/verveinej.sh' asFileReference;
    javaSourcePath: 'path/to/java/project/src' asFileReference;
    mseDestinationPath: 'path/to/mseFile.mse' asFileReference.
wizard generateMSE.

Handy user interface (Spec 2, Moose 8 only)

MooseEasyFamixMakerPresenter open

image

Version management

This project use semantic versioning to define the releases. This means that each stable release of the project will be assigned a version number of the form vX.Y.Z.

  • X defines the major version number
  • Y defines the minor version number
  • Z defines the patch version number

When a release contains only bug fixes, the patch number increases. When the release contains new features that are backward compatible, the minor version increases. When the release contains breaking changes, the major version increases.

Thus, it should be safe to depend on a fixed major version and moving minor version of this project.