https://github.com/moosetechnology/moose-easy

Tools to facilitate access to Moose, e.g., generating MSE files from source code
https://github.com/moosetechnology/moose-easy

moose pharo smalltalk

Last synced: about 1 month ago
JSON representation

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

• Host: GitHub
• URL: https://github.com/moosetechnology/moose-easy
• Owner: moosetechnology
• License: mit
• Created: 2019-07-19T13:05:05.000Z (over 5 years ago)
• Default Branch: v3
• Last Pushed: 2024-01-08T13:36:30.000Z (12 months ago)
• Last Synced: 2024-01-08T15:29:54.897Z (12 months ago)
• Topics: moose, pharo, smalltalk
• Language: Java
• Homepage:
• Size: 9.42 MB
• Stars: 1
• Watchers: 3
• Forks: 0
• Open Issues: 4
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Moose-Easy

Master: [![Build Pass](https://travis-ci.org/moosetechnology/Moose-Easy.svg?branch=master)](https://travis-ci.org/moosetechnology/Moose-Easy)

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:

```Smalltalk

Metacello new

  baseline: 'MooseEasy';

  repository: 'github://moosetechnology/Moose-Easy';

  load.

```

# Famix Maker

Create MSE files easily, provided you have installed [VerveineJ](https://github.com/moosetechnology/VerveineJ).

```Smalltalk

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)

```Smalltalk

MooseEasyFamixMakerPresenter open

```

![image](https://user-images.githubusercontent.com/7606540/61800552-8767d100-ae2d-11e9-8450-b5080326995e.png)

## 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.