https://github.com/victornoel/smac-thirdparties-maven
  
  
    Third Party libraries not available on Maven Central 
    https://github.com/victornoel/smac-thirdparties-maven
  
        Last synced: 7 months ago 
        JSON representation
    
Third Party libraries not available on Maven Central
- Host: GitHub
 - URL: https://github.com/victornoel/smac-thirdparties-maven
 - Owner: victornoel
 - Created: 2015-07-25T16:14:34.000Z (over 10 years ago)
 - Default Branch: master
 - Last Pushed: 2015-07-25T16:15:25.000Z (over 10 years ago)
 - Last Synced: 2025-02-17T05:58:27.554Z (9 months ago)
 - Homepage:
 - Size: 172 KB
 - Stars: 0
 - Watchers: 1
 - Forks: 0
 - Open Issues: 0
 - 
            Metadata Files:
            
- Readme: README
 
 
Awesome Lists containing this project
README
          1) MASON and RLFORJ
We first need to get the source code corresponding to the version of the pom.
For Mason, from its parent directory:
$ svn co http://mason.googlecode.com/svn/trunk/mason mason 
If you want a specific revision, for version 18 (rev 1001) for example, go in the mason directory and do:
$ svn update -r 1001
For rlforj, from its parent directory (16 is the revision of the release 0.3):
$ svn co svn://svn.code.sf.net/p/rlforj/code/trunk rlforj
If you want a specific revision, for version 0.3 (rev 16) for example, go in the rlforj directory and do:
$ svn update -r 16
Then follow a normal release as explained here: https://wwwsecu.irit.fr/redmine/projects/may/wiki/MAY_Lib_Release_Process
2) IVY
A. Old way of deploying to our own repository:
$ mvn deploy:deploy-file -Dfile=external-libs/ivy-1.2.13.jar -DpomFile=external-libs/ivy.pom.xml -DrepositoryId=ftp-repository-irit-vnoel -Durl=ftp://ftpintra.irit.fr/../../usr/local/WWW/PERSONNEL/SMAC/noel/maven-repos/
B. To deploy to Central, it is needed to build a bundle and manually deploy it as explained here: https://github.com/sevntu-checkstyle/dsm-maven-plugin/wiki/Uploading-3rd-party-library-to-maven-central
We need these files:
project-1.0.pom
project-1.0.jar
project-1.0-sources.jar
project-1.0-javadoc.jar
If needed, create the sources and javadoc archive manually with a README in it explaining why there is nothing:
$ jar -cvf project-1.0-sources.jar README 
Then sign (see https://wwwsecu.irit.fr/redmine/projects/may/wiki/MAY_Lib_Release_Process for details):
$ gpg -ab filename
Then create bundle:
$ jar -cvf project-1.0-bundle.jar project-1.0.pom project-1.0.pom.asc project-1.0.jar project-1.0.jar.asc project-1.0-javadoc.jar project-1.0-javadoc.jar.asc project-1.0-sources.jar project-1.0-sources.jar.asc
And upload on maven central (click on Staging Upload the Nexus, see https://wwwsecu.irit.fr/redmine/projects/may/wiki/MAY_Lib_Release_Process for access).