Eclipse: How to create a Simple Project type
Hi all. How can we get maven to create a simple eclipse project (not a Java one)? Ie, get it to generate a .project file: ?xml version=1.0 encoding=UTF-8? projectDescription nameBlah/name comment/comment projects/projects buildSpec/buildSpec natures/natures /projectDescription The type of the project from the pom.xml is pom, ie: packagingpom/packaging Can this be done? -Chris ** CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must: - Not use, copy, distribute or disclose it to anyone other than the addressee; - Notify the sender via return email; and - Delete the message (and any related attachments) from your computer immediately. Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent. Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checking for updates of versioned dependencies
It is indeed seriously strange. That URL should correspond to: groupIdeclipse.org.eclipse.core/groupId which is probably why the maven build isn't finding it. But that's a very weird groupId. And it doesn't match what is in the metadata files in the repository. Looks like the eclipse group have screwed up their 3.2.x uploads to me, replicating their data to the wrong directory within the maven repo. In addition, not finding a dependency during a build should be an error. So I don't understand why this build is succeeding at all. Regards, Simon Dennis Lundberg schrieb: Right. Now that's a seriously strange repo. Are they in the middle of a reorganisation? I'm out of clues now... manish wrote: Hi Dennis, The dependency is declared as dependency groupIdorg.eclipse.core/groupId artifactIdorg.eclipse.core.resources/artifactId version3.2.0/version /dependency So, unless I'm missing something, maven should look for it at http://repo1.maven.org/eclipse/org/eclipse/core/org.eclipse.core.resources/3.2.0/ where it does exist. Cheers, Manish Dennis Lundberg-2 wrote: [EMAIL PROTECTED] wrote: Hi, I was hoping someone could help explain this observed behaviour (maven 2.0.4). We have setup an internal repository (using Codehaus proxy repository). We have a large number of dependencies in our maven build. However, for a particular subset of these dependencies, maven performs an update check once per day on both our internal repository (te-uk) and the maven central repository. Here is the logging from maven - [INFO] artifact org.eclipse.ant:org.eclipse.ant.core: checking for updates from te-uk [INFO] artifact org.eclipse.ant:org.eclipse.ant.core: checking for updates from central Now, this only happens for this one particular set of jar dependencies. An exmple of one of the culprits is - dependency groupIdorg.eclipse.core/groupId artifactIdorg.eclipse.core.resources/artifactId version3.2.0/version /dependency There are 20 other dependencies that are all from the org.eclipse.core group. These are fetched from the repository at http://repo1.maven.org/eclipse. Every one of these gets the update check once per day. However, they are declared exactly the same way as any of our other versioned dependencies which never get an update check. I went looking in that repo for the dependency you specified above and it doesn't exist at http://repo1.maven.org/eclipse/org/eclipse/core/resources/ So what I think is happening is that Maven tries to download version 3.2.0 once a day because you said you wanted that version. But since it will never find it, it will retry every day. It is a problem because once per day our build takes 5 mins longer than necessary. I explicitly do not want an update check on any of our versioned dependencies (if I did, I would use snapshots). Hence, our repository is configured as follows - repositories repository idte-uk/id nameTE-UK Repository/name urlhttp://us99.pun.dom:/repository/url releases enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledfalse/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idte-uk/id nameTE-UK Repository/name urlhttp://us99.pun.dom:/repository/url releases enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledfalse/enabled /snapshots /pluginRepository /pluginRepositories I've tried playing around with the updatePolicy on the repository, but it has absolutely no effect whatsoever. Any help to explain this behaviour would be appreciated. Thanks, Manish -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checking for updates of versioned dependencies
Hi! Simon, I think you are wrong here. If I unstand correctly, the repository's base URL ist http://repo1.maven.org/eclipse, just like the base URL for central is http://repo1.maven.org/maven2. Thus, the URL http://repo1.maven.org/eclipse/org/eclipse/core/ should correspond to the groupId groupIdorg.eclipse.core/groupId which is correct, according to maven-metadata.xml. The question is, why does maven not find the Artifacts there? Is a repository declared for the URL http://repo1.maven.org/eclipse? regards, - martin On Tuesday 10 June 2008 [EMAIL PROTECTED] wrote: It is indeed seriously strange. That URL should correspond to: groupIdeclipse.org.eclipse.core/groupId which is probably why the maven build isn't finding it. But that's a very weird groupId. And it doesn't match what is in the metadata files in the repository. Looks like the eclipse group have screwed up their 3.2.x uploads to me, replicating their data to the wrong directory within the maven repo. In addition, not finding a dependency during a build should be an error. So I don't understand why this build is succeeding at all. Regards, Simon Dennis Lundberg schrieb: Right. Now that's a seriously strange repo. Are they in the middle of a reorganisation? I'm out of clues now... manish wrote: Hi Dennis, The dependency is declared as dependency groupIdorg.eclipse.core/groupId artifactIdorg.eclipse.core.resources/artifactId version3.2.0/version /dependency So, unless I'm missing something, maven should look for it at http://repo1.maven.org/eclipse/org/eclipse/core/org.eclipse.core.resou rces/3.2.0/ where it does exist. Cheers, Manish Dennis Lundberg-2 wrote: [EMAIL PROTECTED] wrote: Hi, I was hoping someone could help explain this observed behaviour (maven 2.0.4). We have setup an internal repository (using Codehaus proxy repository). We have a large number of dependencies in our maven build. However, for a particular subset of these dependencies, maven performs an update check once per day on both our internal repository (te-uk) and the maven central repository. Here is the logging from maven - [INFO] artifact org.eclipse.ant:org.eclipse.ant.core: checking for updates from te-uk [INFO] artifact org.eclipse.ant:org.eclipse.ant.core: checking for updates from central Now, this only happens for this one particular set of jar dependencies. An exmple of one of the culprits is - dependency groupIdorg.eclipse.core/groupId artifactIdorg.eclipse.core.resources/artifactId version3.2.0/version /dependency There are 20 other dependencies that are all from the org.eclipse.core group. These are fetched from the repository at http://repo1.maven.org/eclipse. Every one of these gets the update check once per day. However, they are declared exactly the same way as any of our other versioned dependencies which never get an update check. I went looking in that repo for the dependency you specified above and it doesn't exist at http://repo1.maven.org/eclipse/org/eclipse/core/resources/ So what I think is happening is that Maven tries to download version 3.2.0 once a day because you said you wanted that version. But since it will never find it, it will retry every day. It is a problem because once per day our build takes 5 mins longer than necessary. I explicitly do not want an update check on any of our versioned dependencies (if I did, I would use snapshots). Hence, our repository is configured as follows - repositories repository idte-uk/id nameTE-UK Repository/name urlhttp://us99.pun.dom:/repository/url releases enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledfalse/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idte-uk/id nameTE-UK Repository/name urlhttp://us99.pun.dom:/repository/url releases enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledfalse/enabled /snapshots /pluginRepository /pluginRepositories I've tried playing around with the updatePolicy on the repository, but it has absolutely no effect whatsoever. Any help to explain this behaviour would be appreciated. Thanks, Manish -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checking for updates of versioned dependencies
Ah, you're quite right Martin. It's too early in the morning :-) So it appears that eclipse has its own repository on the repo1.maven.org server, rather than using the standard maven2 repository on that server (aka central). I wonder why. Anyway, that repository is not the built in central repo. As seen here, only the maven2 repo is predefined: http://maven.apache.org/pom.html#The_Super_POM Therefore to access the artifacts in this special eclipse repository, that repo would need to be declared explicitly, either in pom.xml or settings.xml. Regards, Simon Martin Höller schrieb: Hi! Simon, I think you are wrong here. If I unstand correctly, the repository's base URL ist http://repo1.maven.org/eclipse, just like the base URL for central is http://repo1.maven.org/maven2. Thus, the URL http://repo1.maven.org/eclipse/org/eclipse/core/ should correspond to the groupId groupIdorg.eclipse.core/groupId which is correct, according to maven-metadata.xml. The question is, why does maven not find the Artifacts there? Is a repository declared for the URL http://repo1.maven.org/eclipse? regards, - martin On Tuesday 10 June 2008 [EMAIL PROTECTED] wrote: It is indeed seriously strange. That URL should correspond to: groupIdeclipse.org.eclipse.core/groupId which is probably why the maven build isn't finding it. But that's a very weird groupId. And it doesn't match what is in the metadata files in the repository. Looks like the eclipse group have screwed up their 3.2.x uploads to me, replicating their data to the wrong directory within the maven repo. In addition, not finding a dependency during a build should be an error. So I don't understand why this build is succeeding at all. Regards, Simon Dennis Lundberg schrieb: Right. Now that's a seriously strange repo. Are they in the middle of a reorganisation? I'm out of clues now... manish wrote: Hi Dennis, The dependency is declared as dependency groupIdorg.eclipse.core/groupId artifactIdorg.eclipse.core.resources/artifactId version3.2.0/version /dependency So, unless I'm missing something, maven should look for it at http://repo1.maven.org/eclipse/org/eclipse/core/org.eclipse.core.resou rces/3.2.0/ where it does exist. Cheers, Manish Dennis Lundberg-2 wrote: [EMAIL PROTECTED] wrote: Hi, I was hoping someone could help explain this observed behaviour (maven 2.0.4). We have setup an internal repository (using Codehaus proxy repository). We have a large number of dependencies in our maven build. However, for a particular subset of these dependencies, maven performs an update check once per day on both our internal repository (te-uk) and the maven central repository. Here is the logging from maven - [INFO] artifact org.eclipse.ant:org.eclipse.ant.core: checking for updates from te-uk [INFO] artifact org.eclipse.ant:org.eclipse.ant.core: checking for updates from central Now, this only happens for this one particular set of jar dependencies. An exmple of one of the culprits is - dependency groupIdorg.eclipse.core/groupId artifactIdorg.eclipse.core.resources/artifactId version3.2.0/version /dependency There are 20 other dependencies that are all from the org.eclipse.core group. These are fetched from the repository at http://repo1.maven.org/eclipse. Every one of these gets the update check once per day. However, they are declared exactly the same way as any of our other versioned dependencies which never get an update check. I went looking in that repo for the dependency you specified above and it doesn't exist at http://repo1.maven.org/eclipse/org/eclipse/core/resources/ So what I think is happening is that Maven tries to download version 3.2.0 once a day because you said you wanted that version. But since it will never find it, it will retry every day. It is a problem because once per day our build takes 5 mins longer than necessary. I explicitly do not want an update check on any of our versioned dependencies (if I did, I would use snapshots). Hence, our repository is configured as follows - repositories repository idte-uk/id nameTE-UK Repository/name urlhttp://us99.pun.dom:/repository/url releases enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledfalse/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idte-uk/id nameTE-UK Repository/name urlhttp://us99.pun.dom:/repository/url releases enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledfalse/enabled /snapshots /pluginRepository /pluginRepositories I've
Re: Checking for updates of versioned dependencies
Hi all, Thanks for your help with the detective work! We are using the Codehaus Maven Proxy (http://maven-proxy.codehaus.org/), which abstracts away links to several other repositories including central and the eclipse one. In addition, we link to the codehaus and atlassian repositories via our proxy. So, in our pom we just have one repository - our proxy one. If I remove one of the eclipse jars from my local repository and the proxy repository, then it is downloaded again from the eclipse repository. So, I assumme the connection is correct and the jar exists in the right place. Cheers, Manish Martin Höller schrieb: Hi! Simon, I think you are wrong here. If I unstand correctly, the repository's base URL ist http://repo1.maven.org/eclipse, just like the base URL for central is http://repo1.maven.org/maven2. Thus, the URL http://repo1.maven.org/eclipse/org/eclipse/core/ should correspond to the groupId groupIdorg.eclipse.core/groupId which is correct, according to maven-metadata.xml. The question is, why does maven not find the Artifacts there? Is a repository declared for the URL http://repo1.maven.org/eclipse? regards, - martin On Tuesday 10 June 2008 [EMAIL PROTECTED] wrote: It is indeed seriously strange. That URL should correspond to: groupIdeclipse.org.eclipse.core/groupId which is probably why the maven build isn't finding it. But that's a very weird groupId. And it doesn't match what is in the metadata files in the repository. Looks like the eclipse group have screwed up their 3.2.x uploads to me, replicating their data to the wrong directory within the maven repo. In addition, not finding a dependency during a build should be an error. So I don't understand why this build is succeeding at all. Regards, Simon Dennis Lundberg schrieb: Right. Now that's a seriously strange repo. Are they in the middle of a reorganisation? I'm out of clues now... manish wrote: Hi Dennis, The dependency is declared as dependency groupIdorg.eclipse.core/groupId artifactIdorg.eclipse.core.resources/artifactId version3.2.0/version /dependency So, unless I'm missing something, maven should look for it at http://repo1.maven.org/eclipse/org/eclipse/core/org.eclipse.core.resou rces/3.2.0/ where it does exist. Cheers, Manish Dennis Lundberg-2 wrote: [EMAIL PROTECTED] wrote: Hi, I was hoping someone could help explain this observed behaviour (maven 2.0.4). We have setup an internal repository (using Codehaus proxy repository). We have a large number of dependencies in our maven build. However, for a particular subset of these dependencies, maven performs an update check once per day on both our internal repository (te-uk) and the maven central repository. Here is the logging from maven - [INFO] artifact org.eclipse.ant:org.eclipse.ant.core: checking for updates from te-uk [INFO] artifact org.eclipse.ant:org.eclipse.ant.core: checking for updates from central Now, this only happens for this one particular set of jar dependencies. An exmple of one of the culprits is - dependency groupIdorg.eclipse.core/groupId artifactIdorg.eclipse.core.resources/artifactId version3.2.0/version /dependency There are 20 other dependencies that are all from the org.eclipse.core group. These are fetched from the repository at http://repo1.maven.org/eclipse. Every one of these gets the update check once per day. However, they are declared exactly the same way as any of our other versioned dependencies which never get an update check. I went looking in that repo for the dependency you specified above and it doesn't exist at http://repo1.maven.org/eclipse/org/eclipse/core/resources/ So what I think is happening is that Maven tries to download version 3.2.0 once a day because you said you wanted that version. But since it will never find it, it will retry every day. It is a problem because once per day our build takes 5 mins longer than necessary. I explicitly do not want an update check on any of our versioned dependencies (if I did, I would use snapshots). Hence, our repository is configured as follows - repositories repository idte-uk/id nameTE-UK Repository/name urlhttp://us99.pun.dom:/repository/url releases enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledfalse/enabled /snapshots /repository /repositories pluginRepositories pluginRepository idte-uk/id nameTE-UK Repository/name urlhttp://us99.pun.dom:/repository/url releases enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledfalse/enabled /snapshots
Re: Excluding packages and classes from jar
Hi Rémy, thanks for your reply. I also tried mvn package -Pmyflag, but this did't work out either - btw -p SPACE FLAG is what is said on the maven docu site: http://maven.apache.org/guides/introduction/introduction-to-profiles.html : mvn groupId:artifactId:goal -P profile-1,profile-2 However, the new Maven - The definitive Guide - Pdf book says -PMYFLAG. --- Next, as you suggested, I tried it directly without a profile, and it neither worked :-( I am not even sure if what I am trying is supposed to be working - I am trying to exclude certain classes or package - not simple exluding a certain src folder, like include src/java but exclude src/java2 or so - I am trying to do in on a package or class basis - plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration excludes exclude**/com/mycompany/mypackage/mysubpackage/MyClassA.java/exclude exclude**/com/mycompany/mypackage/mysubpackage/packageA/*/exclude exclude**/com/mycompany/mypackage/mysubpackage/packageB/*/exclude /excludes /configuration /execution /executions /plugin I suppose the exclude paths are wrong - but how should I define them? src/java/com...? Thanks in advance, Peter
problem deploying files in the snapshots repository
Hi,
We are in the process of setting up our maven repositories. We already
installed Archiva and we have now 2 repositories: internal and
internal.snapshots.
However, when we are deploying the application we get an error saying:
Uploading:
file:///usr/local/ecc/maven-repo/snapshots//com/ourcomp/ecc/assemblies/ecc-installer/1.0.0-SNAPSHOT/ecc-installer-1.0.0-20080610.072418-3.pom
11K uploaded
[INFO] Retrieving previous metadata from internal.snapshots
[INFO] Uploading repository metadata for: 'artifact
com.ourcomp.ecc.assemblies:ecc-installer'
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error installing artifact's metadata: Error while deploying metadata:
Specified source file does not exist:
/localdisk/users/continuum/.m2/repository/com/ourcomp/ecc/assemblies/ecc-installer/maven-metadata-internal.snapshots.xml
/usr/local/ecc/maven-repo/snapshots/com/ourcomp/ecc/assemblies/ecc-installer/maven-metadata.xml
(Permission denied)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 2 minutes 20 seconds
[INFO] Finished at: Tue Jun 10 00:26:34 PDT 2008
[INFO] Final Memory: 21M/48M
[INFO]
Here's the lt;distributionManagementgt; section from our main pom.xml:
nbsp;nbsp; lt;distributionManagementgt;
nbsp;nbsp;nbsp;nbsp;nbsp;
lt;downloadUrlgt;${project.url}/download.htmllt;/downloadUrlgt;
nbsp;nbsp;nbsp;nbsp;nbsp; lt;repositorygt;
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; lt;idgt;internallt;/idgt;
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; lt;namegt;Main Artifact
Repositorylt;/namegt;
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;
lt;urlgt;file:///usr/local/ecc/maven-repo/releases/lt;/urlgt;
nbsp;nbsp;nbsp;nbsp;nbsp; lt;/repositorygt;
nbsp;nbsp;nbsp;nbsp;nbsp; lt;snapshotRepositorygt;
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;
lt;idgt;internal.snapshotslt;/idgt;
nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;
lt;urlgt;file:///usr/local/ecc/maven-repo/snapshots/lt;/urlgt;
nbsp;nbsp;nbsp;nbsp;nbsp; lt;/snapshotRepositorygt;
nbsp;nbsp; lt;/distributionManagementgt;
The problem gets solved when I comment the snapshotsRepository above, but I
think this change will put all the snapshot artifacts in the internal
repository.
Can somebody help, please ?
RE: Excluding packages and classes from jar
Hi Peter, what is the complete configuration for the plugin? Have a look at mvn help:effective-pom. Remember, that the configuration is merged from the (inherited) pluginManagement section. Note, that in other plugin configuration with includes/excludes the exclude is ignored, if an include is defined (although this is not stated in the maven-jar-plugin's docs). This might also apply here. - Jörg Peter Horlock wrote: Hi Rémy, thanks for your reply. I also tried mvn package -Pmyflag, but this did't work out either - btw -p SPACE FLAG is what is said on the maven docu site: http://maven.apache.org/guides/introduction/introduction-to-pr ofiles.html : mvn groupId:artifactId:goal -P profile-1,profile-2 However, the new Maven - The definitive Guide - Pdf book says -PMYFLAG. --- Next, as you suggested, I tried it directly without a profile, and it neither worked :-( I am not even sure if what I am trying is supposed to be working - I am trying to exclude certain classes or package - not simple exluding a certain src folder, like include src/java but exclude src/java2 or so - I am trying to do in on a package or class basis - plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration excludes exclude**/com/mycompany/mypackage/mysubpackage/MyClassA.java /exclude exclude**/com/mycompany/mypackage/mysubpackage/packageA/*/exclude exclude**/com/mycompany/mypackage/mysubpackage/packageB/*/exclude /excludes /configuration /execution /executions /plugin I suppose the exclude paths are wrong - but how should I define them? src/java/com...? Thanks in advance, Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Excluding packages and classes from jar
Hi, Peter Horlock schrieb: Hi Rémy, thanks for your reply. I also tried mvn package -Pmyflag, but this did't work out either - btw -p SPACE FLAG is what is said on the maven docu site: http://maven.apache.org/guides/introduction/introduction-to-profiles.html : mvn groupId:artifactId:goal -P profile-1,profile-2 However, the new Maven - The definitive Guide - Pdf book says -PMYFLAG. --- Next, as you suggested, I tried it directly without a profile, and it neither worked :-( I am not even sure if what I am trying is supposed to be working - I am trying to exclude certain classes or package - not simple exluding a certain src folder, like include src/java but exclude src/java2 or so - I am trying to do in on a package or class basis - plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId executions execution phasepackage/phase goals goaljar/goal /goals configuration excludes exclude**/com/mycompany/mypackage/mysubpackage/MyClassA.java/exclude exclude**/com/mycompany/mypackage/mysubpackage/packageA/*/exclude exclude**/com/mycompany/mypackage/mysubpackage/packageB/*/exclude /excludes /configuration /execution /executions /plugin I suppose the exclude paths are wrong - but how should I define them? src/java/com...? The jar-plugin works on the compiled output in target/classes, so ecluding *.java files can't work. I just tried with a simple test project: . |-- pom.xml `-- src `-- main `-- java |-- pkg1 | |-- Class1.java | `-- Class2.java `-- pkg2 |-- Class1.java `-- Class2.java and this plugin configuration in the pom: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration excludes excludepkg1/Class1.class/exclude excludepkg2/**/exclude /excludes /configuration /plugin After 'mvn package' the resulting jar contained just pkg1/Class2.class, just as expected. Thanks in advance, Peter Hope this helps -Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Release:branch from a tag
I am trying to create a branch from a tag with the release plugin. I have a checkout from trunk and try the following command: mvn release:branch -Dtag=TestProject-1.4 -DbranchName=TestProject-1.4.x s -DupdateBranchVersions=true I was expecting that a branch (/branches/TestProject-1.4.x) was created from a tag (/tags/TestProject-1.4) but it is created from the current trunk (/trunk). It seems the -Dtag option doesn't do anything, because it is creating a branch from the current trunk. Is it really necessary to checkout a tag before branching it? I've looked at the ReleaseManager source and it seems the tag option isn't considered at all. With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl
activating profiles
Hello. i have question, how can i activate profile in pom.xml from profiles.xml file? For example i have profile Monday in pom.xml and profile Friday in profiles.xml If i start maven with command line: mvn install -PFriday i want to start both of the profiles. i don't want to write mvn install -PFriday,Monday because if i add more profiles in pom.xml the i should run them all manually. But if i can set some options in profiles.xml that give command to run profiles from pom.xml that can be very useful. Thanks and sorry for my bad english. -- View this message in context: http://www.nabble.com/activating-profiles-tp17751436p17751436.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse: How to create a Simple Project type
On Tuesday 10 June 2008 [EMAIL PROTECTED] wrote: How can we get maven to create a simple eclipse project (not a Java one)? [...] The type of the project from the pom.xml is pom, ie: packagingpom/packaging This is already in JIRA and has be discussed there. Don't know if there is a clean solution so far. For Details see [0] and search the MECLIPSE project in JIRA for packaging pom. hth, - martin [0] http://jira.codehaus.org/browse/MECLIPSE-94 signature.asc Description: This is a digitally signed message part.
Maven WebSphere 6.1
Hello folks, I'm following the instructions from http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integrating in order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I should have the following jars under was6home/lib : - wsanttasks.jar - webservices.jar - wsprofile.jar - ffdc.jar - wsdl4j.jar - commons-logging-api.jar - commons-discovery.jar - ras.jar - wsexception.jar - emf.jar - classloader.jar But they're missing. I have IBM WebSphere 6.1 AS Network Deployment - Am I using a wrong version of WAS? - Am I following an out-of-date how-to guide? Thanks in advance, Jo
don't execute submodules for specific goals
Hi there, i have a multi module project and run into following problmem. In the root pom i defined a plugin. build plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.0-alpha-4/version inheritedfalse/inherited /plugin ... i set inherited to false, because when i execute a goal of the plugin ($ mvn dependency:unpack) i want not that the plugin gets executed in every sub-module. But it get executed and the inherited flag only leads to an exception because i want to execute a plugin-goal on an project where the plugin is not defined. So is there a way to only execute the plugin-goal for the root project ? best regards Johannes ~~~ 101tec GmbH Halle (Saale), Saxony-Anhalt, Germany http://www.101tec.com
Archiva and -DdownloadSource
Hi, I have a problem with Archiva. It don't downloaded the sources for dependencies. I have execute : mvn eclipse:eclipse -Declipse.downloadSource=true. But this don't work and work only without Archiva. Alexandre Vaysberg Tetralog System AG - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Signing dependencies during a war build
Hi list, I'm developing a 3-tier system, and I want to distribute the desktop using the Java Webstart. Until now, I already did great progresses in my quest. In the server side I'm deploying a web application using Spring, and I publish some services using RMI. In the desktop, I'm using the Netbeans RCP, packaging all the code and libraries using the webstart-maven-plugin. To give the necessary permissions, I'm using the sign/sign configuration section, signing all the jars with a valid certificate, and everything works well. But now some problems: I'm using hibernate, and the hibernate use the cglib library to do some bytecode manipulations. The code in the client side is signed, and the SecurityManager doesn't allow this unknown, runtime-generated code to run in the desktop. Every time I query the database and try to use one database mapped object, everything blows up. To fix the mess, I did, manually, a war file with the domain libraries, hibernate.jar and cglib.jar signed. And everything worked! But know I want to do automatically. Does someone know how to create a war where each dependency jar file is signed? Something like what the webstart-maven-plugin do while generating the jnlp application. Thanks in advance, and I apologize my English mistakes. -- Fabio Braga de Oliveira Gerente de Projetos de Software Work: +55 19 3295-2111 Mobile: +55 19 9270-6574 E-mail: [EMAIL PROTECTED] Símula Sistemas de Planejamento e Comércio Ltda. Url: http://www.simula.com.br Address: Av. José Bonifácio, 2510 Zipcode 13093-240 Campinas - SP - Brazil begin:vcard fn:Fabio Oliveira n:Oliveira;Fabio org;quoted-printable:S=C3=ADmula Sistemas de Planejamento e Com=C3=A9rcio Ltda. adr;quoted-printable:;;Av. Jos=C3=A9 Bonif=C3=A1cio, 2510;Campinas;SP;13093-240;Brazil email;internet:[EMAIL PROTECTED] title:Gerente de Projetos de Software tel;work:+55 19 3295-2111 tel;cell:+55 19 9270-6574 x-mozilla-html:FALSE url:http://www.simula.com.br version:2.1 end:vcard smime.p7s Description: S/MIME Cryptographic Signature
Re: don't execute submodules for specific goals
The '-N' option avoids recursing into sub-projects: $ mvn -N plugin:goal See 'mvn -h' for other options ciao, PC Johannes Zillmann-3 wrote: Hi there, i have a multi module project and run into following problmem. In the root pom i defined a plugin. build plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.0-alpha-4/version inheritedfalse/inherited /plugin ... i set inherited to false, because when i execute a goal of the plugin ($ mvn dependency:unpack) i want not that the plugin gets executed in every sub-module. But it get executed and the inherited flag only leads to an exception because i want to execute a plugin-goal on an project where the plugin is not defined. So is there a way to only execute the plugin-goal for the root project ? best regards Johannes ~~~ 101tec GmbH Halle (Saale), Saxony-Anhalt, Germany http://www.101tec.com -- View this message in context: http://www.nabble.com/don%27t-execute-submodules-for-specific-goals-tp17752677p17754781.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: don't execute submodules for specific goals
Wow, so simple and i searched for hours... Thank you! Johannes On Jun 10, 2008, at 2:57 PM, Paolo Compieta wrote: The '-N' option avoids recursing into sub-projects: $ mvn -N plugin:goal See 'mvn -h' for other options ciao, PC Johannes Zillmann-3 wrote: Hi there, i have a multi module project and run into following problmem. In the root pom i defined a plugin. build plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.0-alpha-4/version inheritedfalse/inherited /plugin ... i set inherited to false, because when i execute a goal of the plugin ($ mvn dependency:unpack) i want not that the plugin gets executed in every sub-module. But it get executed and the inherited flag only leads to an exception because i want to execute a plugin-goal on an project where the plugin is not defined. So is there a way to only execute the plugin-goal for the root project ? best regards Johannes ~~~ 101tec GmbH Halle (Saale), Saxony-Anhalt, Germany http://www.101tec.com -- View this message in context: http://www.nabble.com/don%27t-execute-submodules-for-specific-goals-tp17752677p17754781.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ~~~ 101tec GmbH Halle (Saale), Saxony-Anhalt, Germany http://www.101tec.com
Release plugin questions
All, I am trying to evaluate the maven-release-plugin (version 2.0-beta-7) and I can't seem to get it to work flawlessly. Here is my scenario: I have a single library/artifact that has zero dependencies. The current version is set to 1.2-SNAPSHOT in the pom.xml file (see below for XML elements). However, when I go to run release:prepare I get the error pasted below. The Perforce path is valid and the user has the proper rights to edit the file (verified via Perforce UI and command-line). What am I doing wrong? [POM Elements] project ... modelVersion4.0.0/modelVersion artifactIdproj-utils/artifactId packagingjar/packaging version1.2-SNAPSHOT/version nameProject Utilities/name urlhttp://www.mydomain.com/url groupIdproj/groupId [Maven Error] [INFO] [release:prepare] [INFO] Resuming release from phase 'generate-release-poms' [INFO] Generating release POMs... [INFO] Generating release POM for 'Lty Utils'... [DEBUG] No SCM translator found - skipping rewrite [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot add release POM to SCM: Exception while executing SCM command. Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened for add [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot add release POM to SCM: Exception while executing SCM command.
Re: Archiva and -DdownloadSource
On Tue, Jun 10, 2008 at 5:14 AM, Alexander Vaysberg [EMAIL PROTECTED] wrote: I have a problem with Archiva. It don't downloaded the sources for dependencies. I have execute : mvn eclipse:eclipse -Declipse.downloadSource=true. But this don't work and work only without Archiva. Please ask on the Archiva user list. You can find subscription info here: http://archiva.apache.org/mail-lists.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Release plugin questions
Is your pom.xml having a scm section? Releasing also tags the version in your scm, so you have to tell maven the SCM repository it uses. LieGrü, strub --- Michael Delaney [EMAIL PROTECTED] schrieb am Di, 10.6.2008: Von: Michael Delaney [EMAIL PROTECTED] Betreff: Release plugin questions An: Maven Users List users@maven.apache.org Datum: Dienstag, 10. Juni 2008, 15:29 All, I am trying to evaluate the maven-release-plugin (version 2.0-beta-7) and I can't seem to get it to work flawlessly. Here is my scenario: I have a single library/artifact that has zero dependencies. The current version is set to 1.2-SNAPSHOT in the pom.xml file (see below for XML elements). However, when I go to run release:prepare I get the error pasted below. The Perforce path is valid and the user has the proper rights to edit the file (verified via Perforce UI and command-line). What am I doing wrong? [POM Elements] project ... modelVersion4.0.0/modelVersion artifactIdproj-utils/artifactId packagingjar/packaging version1.2-SNAPSHOT/version nameProject Utilities/name urlhttp://www.mydomain.com/url groupIdproj/groupId [Maven Error] [INFO] [release:prepare] [INFO] Resuming release from phase 'generate-release-poms' [INFO] Generating release POMs... [INFO] Generating release POM for 'Lty Utils'... [DEBUG] No SCM translator found - skipping rewrite [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot add release POM to SCM: Exception while executing SCM command. Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened for add [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot add release POM to SCM: Exception while executing SCM command. __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Release plugin questions
Yes, it does have the scm section, as defined by http://maven.apache.org/scm/perforce.html. project ... scm connection scm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils /connection /scm ... /project -Original Message- From: Mark Struberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 10:15 AM To: Maven Users List Subject: AW: Release plugin questions Is your pom.xml having a scm section? Releasing also tags the version in your scm, so you have to tell maven the SCM repository it uses. LieGrü, strub --- Michael Delaney [EMAIL PROTECTED] schrieb am Di, 10.6.2008: Von: Michael Delaney [EMAIL PROTECTED] Betreff: Release plugin questions An: Maven Users List users@maven.apache.org Datum: Dienstag, 10. Juni 2008, 15:29 All, I am trying to evaluate the maven-release-plugin (version 2.0-beta-7) and I can't seem to get it to work flawlessly. Here is my scenario: I have a single library/artifact that has zero dependencies. The current version is set to 1.2-SNAPSHOT in the pom.xml file (see below for XML elements). However, when I go to run release:prepare I get the error pasted below. The Perforce path is valid and the user has the proper rights to edit the file (verified via Perforce UI and command-line). What am I doing wrong? [POM Elements] project ... modelVersion4.0.0/modelVersion artifactIdproj-utils/artifactId packagingjar/packaging version1.2-SNAPSHOT/version nameProject Utilities/name urlhttp://www.mydomain.com/url groupIdproj/groupId [Maven Error] [INFO] [release:prepare] [INFO] Resuming release from phase 'generate-release-poms' [INFO] Generating release POMs... [INFO] Generating release POM for 'Lty Utils'... [DEBUG] No SCM translator found - skipping rewrite [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot add release POM to SCM: Exception while executing SCM command. Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened for add [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot add release POM to SCM: Exception while executing SCM command. __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Excluding packages and classes from jar
thanks a lot, this helped.
One more, however:
Now it creates the jar as it should, but I would like to have a different
name for it when installating it into the local / remote repo.
Under target, it creates:
myproject-mysubversion-1.1.jar
but when installing or deploying, it installs /deploys it as:
myproject-1.1.jar (just like the jar that contains all classes).
I tried:
plugin
artifactIdmaven-install-plugin/artifactId
configuration
artifactIdmyproject-mysubversion/artifactId
/configuration
/plugin
as well as:
plugin
artifactIdmaven-install-plugin/artifactId
configuration
fileyproject-mysubversion-${version}.${packaging}/file
/configuration
/plugin
but both just installed the file as myproject-1.1.jar into my repository.
This could lead to really bad confusions... :-(
Any ideas?
Thanks guys,
Peter Horlock
RE: Maven @ Silicon Valley Web Developer Java User Group
Wish I could..however I'm willing to chip in ten dollars to help cover the cost of putting it on video that we might have access after the fact. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2008 4:53 PM To: Maven Users List Subject: Maven @ Silicon Valley Web Developer Java User Group Hi, For any Maven users who are interested in Eclipse IDE integration and Maven repository managers I will be speaking at the Silicon Valley Web Developer Java User Group on June 17th at Google in Mountain View. I will be speaking extensively on Nexus and m2eclipse and doing demos of both. The details are here: http://sv-web-jug-6.eventbrite.com/ Hope to see you there! Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- A man enjoys his work when he understands the whole and when he is responsible for the quality of the whole -- Christopher Alexander, A Pattern Language - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Signing dependencies during a war build
2008/6/10 Fabio Braga de Oliveira [EMAIL PROTECTED]: Hi list, I'm developing a 3-tier system, and I want to distribute the desktop using the Java Webstart. Until now, I already did great progresses in my quest. In the server side I'm deploying a web application using Spring, and I publish some services using RMI. In the desktop, I'm using the Netbeans RCP, packaging all the code and libraries using the webstart-maven-plugin. To give the necessary permissions, I'm using the sign/sign configuration section, signing all the jars with a valid certificate, and everything works well. But now some problems: I'm using hibernate, and the hibernate use the cglib library to do some bytecode manipulations. The code in the client side is signed, and the SecurityManager doesn't allow this unknown, runtime-generated code to run in the desktop. Every time I query the database and try to use one database mapped object, everything blows up. To fix the mess, I did, manually, a war file with the domain libraries, hibernate.jar and cglib.jar signed. And everything worked! But know I want to do automatically. Does someone know how to create a war where each dependency jar file is signed? Something like what the webstart-maven-plugin do while generating the jnlp application. Thanks in advance, and I apologize my English mistakes. I wrote both the jar:sign and webstart mojos and I am not aware of an off the shelf war-with-signed-dependencies solution. If you find one, or end up creating yours, please let us know :) Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Release plugin questions
Try specifying the developerConnection, e.g., !-- P4 Location -- scm connectionscm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils/connection developerConnectionscm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils/developerConnection /scm -Original Message- From: Michael Delaney [mailto:[EMAIL PROTECTED] Sent: 10 June 2008 15:20 To: Maven Users List Subject: RE: Release plugin questions Yes, it does have the scm section, as defined by http://maven.apache.org/scm/perforce.html. project ... scm connection scm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils /connection /scm ... /project -Original Message- From: Mark Struberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 10:15 AM To: Maven Users List Subject: AW: Release plugin questions Is your pom.xml having a scm section? Releasing also tags the version in your scm, so you have to tell maven the SCM repository it uses. LieGrü, strub --- Michael Delaney [EMAIL PROTECTED] schrieb am Di, 10.6.2008: Von: Michael Delaney [EMAIL PROTECTED] Betreff: Release plugin questions An: Maven Users List users@maven.apache.org Datum: Dienstag, 10. Juni 2008, 15:29 All, I am trying to evaluate the maven-release-plugin (version 2.0-beta-7) and I can't seem to get it to work flawlessly. Here is my scenario: I have a single library/artifact that has zero dependencies. The current version is set to 1.2-SNAPSHOT in the pom.xml file (see below for XML elements). However, when I go to run release:prepare I get the error pasted below. The Perforce path is valid and the user has the proper rights to edit the file (verified via Perforce UI and command-line). What am I doing wrong? [POM Elements] project ... modelVersion4.0.0/modelVersion artifactIdproj-utils/artifactId packagingjar/packaging version1.2-SNAPSHOT/version nameProject Utilities/name urlhttp://www.mydomain.com/url groupIdproj/groupId [Maven Error] [INFO] [release:prepare] [INFO] Resuming release from phase 'generate-release-poms' [INFO] Generating release POMs... [INFO] Generating release POM for 'Lty Utils'... [DEBUG] No SCM translator found - skipping rewrite [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot add release POM to SCM: Exception while executing SCM command. Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened for add [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot add release POM to SCM: Exception while executing SCM command. __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Release plugin questions
Sorry, I am still getting the same error when I add that to the pom.xml file. -Original Message- From: Bracewell, Robert [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 11:28 AM To: Maven Users List Subject: RE: Release plugin questions Try specifying the developerConnection, e.g., !-- P4 Location -- scm connectionscm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils/connection developerConnectionscm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils/developerConnection /scm -Original Message- From: Michael Delaney [mailto:[EMAIL PROTECTED] Sent: 10 June 2008 15:20 To: Maven Users List Subject: RE: Release plugin questions Yes, it does have the scm section, as defined by http://maven.apache.org/scm/perforce.html. project ... scm connection scm:perforce:localhost:1666://depot/sandboxes/mdelaney/utils /connection /scm ... /project -Original Message- From: Mark Struberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 10:15 AM To: Maven Users List Subject: AW: Release plugin questions Is your pom.xml having a scm section? Releasing also tags the version in your scm, so you have to tell maven the SCM repository it uses. LieGrü, strub --- Michael Delaney [EMAIL PROTECTED] schrieb am Di, 10.6.2008: Von: Michael Delaney [EMAIL PROTECTED] Betreff: Release plugin questions An: Maven Users List users@maven.apache.org Datum: Dienstag, 10. Juni 2008, 15:29 All, I am trying to evaluate the maven-release-plugin (version 2.0-beta-7) and I can't seem to get it to work flawlessly. Here is my scenario: I have a single library/artifact that has zero dependencies. The current version is set to 1.2-SNAPSHOT in the pom.xml file (see below for XML elements). However, when I go to run release:prepare I get the error pasted below. The Perforce path is valid and the user has the proper rights to edit the file (verified via Perforce UI and command-line). What am I doing wrong? [POM Elements] project ... modelVersion4.0.0/modelVersion artifactIdproj-utils/artifactId packagingjar/packaging version1.2-SNAPSHOT/version nameProject Utilities/name urlhttp://www.mydomain.com/url groupIdproj/groupId [Maven Error] [INFO] [release:prepare] [INFO] Resuming release from phase 'generate-release-poms' [INFO] Generating release POMs... [INFO] Generating release POM for 'Lty Utils'... [DEBUG] No SCM translator found - skipping rewrite [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot add release POM to SCM: Exception while executing SCM command. Unknown input: //depot/sandboxes/mdelaney/utils/release-pom.xml#4 - opened for add [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot add release POM to SCM: Exception while executing SCM command. __ Gesendet von Yahoo! Mail. Dem pfiffigeren Posteingang. http://de.overview.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Signing dependencies during a war build
Hi Jerome, I wrote both the jar:sign and webstart mojos and I am not aware of an off the shelf war-with-signed-dependencies solution. If you find one, or end up creating yours, please let us know :) Jerome I want to thank you for your excellent work. Without your help my work will be very difficult, maybe impossible. I never did a maven plugin, maybe it's the time to start, can give me some advices on how to start? A good candidate solution (I think...) is to use the assembly plugin. I already did a .jar file where all the dependencies are unzipped in a single .jar and then this one was signed. Again, tips? Thanks! -- Fabio Braga de Oliveira Gerente de Projetos de Software Work: +55 19 3295-2111 Mobile: +55 19 9270-6574 E-mail: [EMAIL PROTECTED] Símula Sistemas de Planejamento e Comércio Ltda. Url: http://www.simula.com.br Address: Av. José Bonifácio, 2510 Zipcode 13093-240 Campinas - SP - Brazil begin:vcard fn:Fabio Oliveira n:Oliveira;Fabio org;quoted-printable:S=C3=ADmula Sistemas de Planejamento e Com=C3=A9rcio Ltda. adr;quoted-printable:;;Av. Jos=C3=A9 Bonif=C3=A1cio, 2510;Campinas;SP;13093-240;Brazil email;internet:[EMAIL PROTECTED] title:Gerente de Projetos de Software tel;work:+55 19 3295-2111 tel;cell:+55 19 9270-6574 x-mozilla-html:FALSE url:http://www.simula.com.br version:2.1 end:vcard smime.p7s Description: S/MIME Cryptographic Signature
Re: Maven @ Silicon Valley Web Developer Java User Group
Hi, would love to do that too as i m interested but im in UK.. please keep me posted on this issue rgds marco On Tue, Jun 10, 2008 at 3:49 PM, Sean Hennessy [EMAIL PROTECTED] wrote: Wish I could..however I'm willing to chip in ten dollars to help cover the cost of putting it on video that we might have access after the fact. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2008 4:53 PM To: Maven Users List Subject: Maven @ Silicon Valley Web Developer Java User Group Hi, For any Maven users who are interested in Eclipse IDE integration and Maven repository managers I will be speaking at the Silicon Valley Web Developer Java User Group on June 17th at Google in Mountain View. I will be speaking extensively on Nexus and m2eclipse and doing demos of both. The details are here: http://sv-web-jug-6.eventbrite.com/ Hope to see you there! Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- A man enjoys his work when he understands the whole and when he is responsible for the quality of the whole -- Christopher Alexander, A Pattern Language - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven WebSphere 6.1
Jo, my 2 cents here, it *could* be, but i think except for ws specific jars, you shouuld be able to fetch ther est from maven repo. hth marco On Tue, Jun 10, 2008 at 11:55 AM, Jo Support [EMAIL PROTECTED] wrote: Hello folks, I'm following the instructions from http://www.jroller.com/peter_pilgrim/entry/battling_with_maven_2_integratingin order to deploy EJBs for WebSphere 6.1. According to Pilgrim, I should have the following jars under was6home/lib : - wsanttasks.jar - webservices.jar - wsprofile.jar - ffdc.jar - wsdl4j.jar - commons-logging-api.jar - commons-discovery.jar - ras.jar - wsexception.jar - emf.jar - classloader.jar But they're missing. I have IBM WebSphere 6.1 AS Network Deployment - Am I using a wrong version of WAS? - Am I following an out-of-date how-to guide? Thanks in advance, Jo
Do you do .Net development on the Mac
This is pretty cool for Mac and Visual Studio funtionality. http://www.monodevelop.com/Main_Page Scott Ryan President/CTO Soaring Eagle L.L.C. 9742 S. Whitecliff Place Highlands Ranch, Co. 80129 (303) 263-3044 [EMAIL PROTECTED] www.soaringeagleco.com
Re: Do you do .Net development on the Mac
How does it compare to codewarrior? http://www.diskovery.com/codewarrior.html M- - Original Message - From: Scott Ryan [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Tuesday, June 10, 2008 2:42 PM Subject: Do you do .Net development on the Mac This is pretty cool for Mac and Visual Studio funtionality. http://www.monodevelop.com/Main_Page Scott Ryan President/CTO Soaring Eagle L.L.C. 9742 S. Whitecliff Place Highlands Ranch, Co. 80129 (303) 263-3044 [EMAIL PROTECTED] www.soaringeagleco.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven @ Silicon Valley Web Developer Java User Group
not to mention the cost of gas to travel to the other side of the planet.. Can the committee chair agree to a 'virtual meeting'? one option: https://www2.gotomeeting.com/t/gg/virtual_meeting/g2msem3?Portal=www.gotomeeting.comTarget=m/g2msem3.tmpl HTH Martin - Original Message - From: Marco Mistroni [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Tuesday, June 10, 2008 2:09 PM Subject: Re: Maven @ Silicon Valley Web Developer Java User Group Hi, would love to do that too as i m interested but im in UK.. please keep me posted on this issue rgds marco On Tue, Jun 10, 2008 at 3:49 PM, Sean Hennessy [EMAIL PROTECTED] wrote: Wish I could..however I'm willing to chip in ten dollars to help cover the cost of putting it on video that we might have access after the fact. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2008 4:53 PM To: Maven Users List Subject: Maven @ Silicon Valley Web Developer Java User Group Hi, For any Maven users who are interested in Eclipse IDE integration and Maven repository managers I will be speaking at the Silicon Valley Web Developer Java User Group on June 17th at Google in Mountain View. I will be speaking extensively on Nexus and m2eclipse and doing demos of both. The details are here: http://sv-web-jug-6.eventbrite.com/ Hope to see you there! Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- A man enjoys his work when he understands the whole and when he is responsible for the quality of the whole -- Christopher Alexander, A Pattern Language - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Excluding packages and classes from jar
Peter Horlock schrieb:
thanks a lot, this helped.
One more, however:
Now it creates the jar as it should, but I would like to have a different
name for it when installating it into the local / remote repo.
Under target, it creates:
myproject-mysubversion-1.1.jar
but when installing or deploying, it installs /deploys it as:
myproject-1.1.jar (just like the jar that contains all classes).
All artifacts in a repository have to follow a common naming schema so
that maven can locate them. The schema is:
artifactid-version[-classifier].packaging
This is fixed, you can't put arbitrary named jars in there.
I tried:
plugin
artifactIdmaven-install-plugin/artifactId
configuration
artifactIdmyproject-mysubversion/artifactId
/configuration
/plugin
as well as:
plugin
artifactIdmaven-install-plugin/artifactId
configuration
fileyproject-mysubversion-${version}.${packaging}/file
/configuration
/plugin
Where did you get that configuration parameters from? The
install-plugin's documentation [1] doesn't mention these.
but both just installed the file as myproject-1.1.jar into my repository.
This could lead to really bad confusions... :-(
That's expected, the install-plugin doesn't know these parameters and
just ignores them.
Any ideas?
I would configure it like this in my pom:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
executions
execution
idpackage-stripped-jar/id
phasepackage/phase
goals
goaljar/goal
/goals
configuration
classifierstripped/classifier
excludes
excludepkg1/Class1.class/exclude
excludepkg2/**/exclude
/excludes
/configuration
/execution
/executions
/plugin
This configures a second execution of the jar plugin in addition to the
default execution because of the jar-packaging. This second execution
creates the stripped down jar with the given classifier and attaches it
to the build.
The install (and deploy) plugin will automatically pick up the main
artifact (created by the default jar execution) and the second one with
the clsssifier and installs/deploys them to the repository.
when you need to reference the stripped plugin in another project the
dependency would look like this:
dependency
groupIdmygroup.id/groupId
artifactIdmy-artifact/artifactId
version3.14159/version
classifierstripped/classifier
/dependency
Thanks guys,
Peter Horlock
-Tim
[1] http://maven.apache.org/plugins/maven-install-plugin/install-mojo.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to make nexus work with thirdparty libraries??
On Tue, Jun 10, 2008 at 3:58 PM, Kent Närling [EMAIL PROTECTED] wrote: I have read the FAQ on how to upload thirdparty jars to a repository, but cannot seem to get it working? I have tried to upload the jacorb jar to our own local repository (nexus) with the command: mvn deploy:deploy-file -DgroupId=org.jacorb -DartifactId=jacorb -Dversion=2.3 -Dpackaging=jar -Dfile=jacorb.jar -Durl= http://nexus:8081/nexus/content/repositories/releases And then I have the following settings.xml: ?xml version=1.0? settings mirrors mirror idNexus/id nameNexus Public Mirror/name urlhttp://nexus:8081/nexus/content/groups/public/url mirrorOfcentral/mirrorOf /mirror /mirrors /settings But still I cannot use this artifact!! I tried searching for it using the index plugin in M2 eclipse but cannot find it (and cannot add it as a dependency either). But when I go into nexus I can easily find it when searching for artifacts in the web user interface... I also tried to upload it to repositories/thirdparty (in nexus) but no difference? Can anyone tell me what I am doing wrong? //Kent Is the releases repository defined as a member of the public group? When we've added additional repositories, we've had to make sure that we include them in the group definition if they're to be found at the group URL. Hope this helps, Ed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] any fundamental issues with profile inheritance ?
I have a reference project: Project A |--sub project 1 (parent is Project A) |--sub project 2 (parent is Project A) |--sub project 3 (parent is Project A) Then I have an implementation project: Project Ref A (parent is Project A) |-- sub ref 1 (parent is sub project 1) |-- sub ref 2 (parent is sub project 2) |-- sub ref 3 (parent is sub project 3) I am trying to create 3 standard pom projects, that a project can extend each different type of module. I want to make each downstream project simpler to read and understand. -- --- Thank You… Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com
Re: Do you do .Net development on the Mac
The IDE is pretty nice - good code completion and GUI builder but from what I saw last it lacks a debugger :S James On Tue, 2008-06-10 at 14:46 -0400, Martin wrote: How does it compare to codewarrior? http://www.diskovery.com/codewarrior.html M- - Original Message - From: Scott Ryan [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Tuesday, June 10, 2008 2:42 PM Subject: Do you do .Net development on the Mac This is pretty cool for Mac and Visual Studio funtionality. http://www.monodevelop.com/Main_Page Scott Ryan President/CTO Soaring Eagle L.L.C. 9742 S. Whitecliff Place Highlands Ranch, Co. 80129 (303) 263-3044 [EMAIL PROTECTED] www.soaringeagleco.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven WebSphere 6.1
Hi. I do not get maven to actually generate the EJB deployment code, WebSphere itself will do it at deployment time, so I do. If nothing else, this will give you a list of the jars that you need. Using RSA V7, it defines a classpath container that has all of the necessary jars in it needed to support complete websphere 6.1 development. What I have done is to define a runtime library/aggregrate pom for the websphere runtime. I have not needed to define one for the JRE. This is part of a batch file that I used to copy the necessary runtime files (as defined in the classpath container) to a temp holding dir, and then install/deploy them into your repo. md C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mqjms.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.ejbportable_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.emf_2.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.portletcontainer_2.0.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime.dist_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sib.server_2.0.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sip.container_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.wccm_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.webcontainer_2.0.0.jar C:\Temp\Maven\WAS61 That should have these files in the C:\Temp\maven\WAS61 dir: 50,767 bootstrap.jar 430,143 com.ibm.mq.jar 1,238,366 com.ibm.mqjms.jar 77,523 com.ibm.ws.ejbportable_6.1.0.jar 3,355,425 com.ibm.ws.emf_2.1.0.jar 622,223 com.ibm.ws.portletcontainer_2.0.0.jar 1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar 53,066,732 com.ibm.ws.runtime_6.1.0.jar 11,771,638 com.ibm.ws.sib.server_2.0.0.jar 1,179,014 com.ibm.ws.sip.container_6.1.0.jar 9,221,353 com.ibm.ws.wccm_6.1.0.jar 3,267,808 com.ibm.ws.webcontainer_2.0.0.jar 546,698 j2ee.jar 202,255 mail-impl.jar 72,730 marshall.jar I deployed them to the repo (in this case proximity) using: call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mq -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.mqjms.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=bootstrap.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=bootstrap -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=j2ee.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=j2ee -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=mail-impl.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=marshall.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=marshall -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.ejbportable_6.1.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.ejbportable_6.1.0 -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.emf_2.1.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.emf_2.1.0 -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.portletcontainer_2.0.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.portletcontainer_2.0.0 -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime.dist_6.1.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.runtime.dist_6.1.0 -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.ws.runtime_6.1.0.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.ws.runtime_6.1.0 -Dversion=6.1
AW: Maven WebSphere 6.1
Hello! I've got another approach. First, I've defined a WAS_HOME constant in my parent pom. Second, I've defined the websphere dependencies with system scope. Or in other words, I've defined the dependencies with a link to the local filesystem using the WAS_HOME constant. With this approach you don't need to copy the libraties into the repository. Furthermore, you can handle different Websphere versions. Though, it requires a local copy of WAS. And preferably with identical install path. In case the install path isn't identical, the constant WAS_HOME an be changed at runtime. At the beginning, I've copied the libraries to the repository too, however, I've stated that I need the WAS_HOME constant anyway when I started using was6 Plugin. Regards Kuno -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 11. Juni 2008 03:35 An: Maven Users List Betreff: Re: Maven WebSphere 6.1 Hi. I do not get maven to actually generate the EJB deployment code, WebSphere itself will do it at deployment time, so I do. If nothing else, this will give you a list of the jars that you need. Using RSA V7, it defines a classpath container that has all of the necessary jars in it needed to support complete websphere 6.1 development. What I have done is to define a runtime library/aggregrate pom for the websphere runtime. I have not needed to define one for the JRE. This is part of a batch file that I used to copy the necessary runtime files (as defined in the classpath container) to a temp holding dir, and then install/deploy them into your repo. md C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mq.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\WMQ\java\lib\com.ibm.mqjms.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\bootstrap.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\j2ee.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\mail-impl.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\lib\marshall.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.ejbportable_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.emf_2.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.portletcontainer_2.0.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime.dist_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.runtime_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sib.server_2.0.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.sip.container_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.wccm_6.1.0.jar C:\Temp\Maven\WAS61 copy C:\Program Files\IBM\SDP70\runtimes\base_v61\plugins\com.ibm.ws.webcontainer_2.0.0.jar C:\Temp\Maven\WAS61 That should have these files in the C:\Temp\maven\WAS61 dir: 50,767 bootstrap.jar 430,143 com.ibm.mq.jar 1,238,366 com.ibm.mqjms.jar 77,523 com.ibm.ws.ejbportable_6.1.0.jar 3,355,425 com.ibm.ws.emf_2.1.0.jar 622,223 com.ibm.ws.portletcontainer_2.0.0.jar 1,927,102 com.ibm.ws.runtime.dist_6.1.0.jar 53,066,732 com.ibm.ws.runtime_6.1.0.jar 11,771,638 com.ibm.ws.sib.server_2.0.0.jar 1,179,014 com.ibm.ws.sip.container_6.1.0.jar 9,221,353 com.ibm.ws.wccm_6.1.0.jar 3,267,808 com.ibm.ws.webcontainer_2.0.0.jar 546,698 j2ee.jar 202,255 mail-impl.jar 72,730 marshall.jar I deployed them to the repo (in this case proximity) using: call mvn deploy:deploy-file -Dfile=com.ibm.mq.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mq -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=com.ibm.mqjms.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=com.ibm.mqjms -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=bootstrap.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=bootstrap -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=j2ee.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=j2ee -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=mail-impl.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=mail-impl -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file -Dfile=marshall.jar -DgroupId=com.ibm.websphere.appserver -DartifactId=marshall -Dversion=6.1 -Dpackaging=jar -DgeneratePom=true call mvn deploy:deploy-file
