- 
                Notifications
    You must be signed in to change notification settings 
- Fork 45
Release Process
        Mária Jurčovičová edited this page Oct 17, 2015 
        ·
        28 revisions
      
    Steps needed to be done before releasing first time from new computer are described on Before First Release page.
- Run release tests. Less4j can not be released if they do not pass. Release tests are located in release tests repository. [they do not work right now due to less.js rhino bug - needs to be fixed]
- Update wiki and readme.md. The most important is maven dependency version number in readme.md.
- Add the next version to the released versions page.
- Close current milestone and create new one.
Create, tag and upload jar:
- mvn clean release:prepare -Dusername=<Github Username> -Dpassword=<Github Password>
- mvn release:perform -Darguments=-Dgpg.passphrase=<pgp passphrase>
Finish release in maven central:
- Log into Sonatype Nexus: https://oss.sonatype.org/index.html.
- Click "Staging Repositories".
- Close the artifact.
- Release the artifact.
Note: if anything goes wrong, refer to this for new tag fixing.
- Download wiki git clone https://github.com/SomMeri/less4j.wiki.git.
- Tag wiki git tag less4j-<version>.
- Push all tags git push --tags.
- Clone repository somewhere: git clone https://github.com/SomMeri/less4j.git.
- Enter repository.
- Checkout last tag: git checkout less4j-<version>.
- Run mvn package -P standalone.
- Take the target/less4j-<version>-shaded.jarfile and createless4j-<version>.jarandless4j.jarfiles.
- Copy them into Dropbox folder and check shared link.