Difference between revisions of "Integration of Maven Components"
From Gcube Wiki
(Created page with '== Maven Reposiotries == * gCube Snapshots * gCube Releases * gCube Externals == Mavenizer == == Maven Proxy ==') |
|||
| Line 6: | Line 6: | ||
== Mavenizer == | == Mavenizer == | ||
| + | ''Mavenizer'' is a tool created with the intent of making gCube legacy components compatible with new maven components. It is able to generate a pom.xml on-the-fly from information available on component's profile.xml and ETICS configuration and upload artifacts on gCube repositories. | ||
| + | |||
| + | |||
| + | <pre> | ||
| + | [gabriele@gabriele-work maven-builder]$ bin/mavenize --help | ||
| + | USAGE: bin/mavenize [flags] | ||
| + | flags: | ||
| + | -g,--groupId: the groupId to use in the mvn commandline (default: 'org.gcube') | ||
| + | -k,--packaging: the type of the artifact. Default is 'jar'. (default: 'jar') | ||
| + | -n,--artifactId: the artifactId to use in the mvn commandline. If not specified, it will be the etics module's name (default: '') | ||
| + | -v,--version: the version to use in the mvn commandline. If not specified, it will be the etics module version (default: '') | ||
| + | -f,--file: artifact file to mavenize. If not specified, a search will be done in the etics module home trying to find a suitable artifact (default: '') | ||
| + | -d,--[no]forcedeploy: force deployment of artifact on remote repository (default: false) | ||
| + | -s,--[no]dryrun: no act. Perform just a simulation (default: false) | ||
| + | -l,--loglevel: log level. Accepted values are 0, 1, 2 (default: 1) | ||
| + | -h,--[no]help: show this help (default: false) | ||
| + | </pre> | ||
== Maven Proxy == | == Maven Proxy == | ||
Revision as of 12:35, 3 April 2012
Maven Reposiotries
- gCube Snapshots
- gCube Releases
- gCube Externals
Mavenizer
Mavenizer is a tool created with the intent of making gCube legacy components compatible with new maven components. It is able to generate a pom.xml on-the-fly from information available on component's profile.xml and ETICS configuration and upload artifacts on gCube repositories.
[gabriele@gabriele-work maven-builder]$ bin/mavenize --help USAGE: bin/mavenize [flags] flags: -g,--groupId: the groupId to use in the mvn commandline (default: 'org.gcube') -k,--packaging: the type of the artifact. Default is 'jar'. (default: 'jar') -n,--artifactId: the artifactId to use in the mvn commandline. If not specified, it will be the etics module's name (default: '') -v,--version: the version to use in the mvn commandline. If not specified, it will be the etics module version (default: '') -f,--file: artifact file to mavenize. If not specified, a search will be done in the etics module home trying to find a suitable artifact (default: '') -d,--[no]forcedeploy: force deployment of artifact on remote repository (default: false) -s,--[no]dryrun: no act. Perform just a simulation (default: false) -l,--loglevel: log level. Accepted values are 0, 1, 2 (default: 1) -h,--[no]help: show this help (default: false)
