Re: URLs in artifact page
done : http://jira.codehaus.org/browse/MRM-731
I check the archiva code. The problem is in the class:
./archiva-base/archiva-repository-layer/src/main/java/org/apache/maven/archiva/repository/project/readers/ProjectModel300Reader.java
Why don't you use the MavenXpp3Reader class to parse the pom ?
Benoit
Brett Porter wrote:
Since that's something Maven does - Archiva should be doing it too. If
not, that can be considered a bug and filed in JIRA.
- Brett
On 06/03/2008, Benoit Decherf [EMAIL PROTECTED] wrote:
Hi,
I have a little problem with artifact page in archiva:
In my pom, the url of the project is :
urlhttp://mavenrepo.dev.kelkoo.net/docs/${project.groupId}/${project.artifactId}/${project.version}/url
So I expect that archiva replace the ${} variables of this URL, but it
doesn't :(.
Is there a way to correct this ? Or should I set the complete URL in all
my poms ?
Benoit
Any way to ignore LayoutExceptions?
I've deployed an artifact that does not have the same name as its parent module (long story) and I can't retrieve it, getting this exception: org.apache.maven.archiva.repository.layout.LayoutException: Invalid path to Artifact: filename format is invalid, should start with artifactId as stated in path. Is there any way I can prevent Archiva from enforcing this restriction? Thanks, Carlton - This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you.
Re: Any way to ignore LayoutExceptions?
This is a side effect of the ability to fetch content either as a maven 2 default layout or using a maven 1 legacy layout on the same repository base url. It's not so much as it's an enforcement than it is a failure to identify the layout type from the request url. Violate the layout rules and get exception. sorry. - Joakim Brown, Carlton wrote: I've deployed an artifact that does not have the same name as its parent module (long story) and I can't retrieve it, getting this exception: org.apache.maven.archiva.repository.layout.LayoutException: Invalid path to Artifact: filename format is invalid, should start with artifactId as stated in path. Is there any way I can prevent Archiva from enforcing this restriction? Thanks, Carlton - This message contains PRIVILEGED and CONFIDENTIAL information that is intended only for use by the named recipient. If you are not the named recipient, any disclosure, dissemination, or action based on the contents of this message is prohibited. In such case please notify us and destroy and delete all copies of this transmission. Thank you.
archiva corrupts the snapshot repository so that deploys don't increment build number
It appears that archiva consumers modify the repository and change timestamps to GMT. The next time I try to deploy an artifact it starts over at build number 1, even though the previous build number was 30. I am not sure what I can do to resolve this either in Archvia or maven??
RE: converting from maven1 to maven2, pom for third party jars?
I can't repeat it often enough: do not copy a local repository to be used as a remote repository. There is not the same information in your local repository as in your remote repository. Really, do use a Maven repository / mirror, like Archiva, Artifactory or Nexus/Proximity. Hth, Nick S. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thu 3/6/2008 07:04 To: Maven Users List Subject: Re: converting from maven1 to maven2, pom for third party jars? To be able to deploy something on your company's remote server, have a look at Distribution Management. What I do for those external jars is - on the console, when maven doesn't find a depdency, it always gives you the exact String you need to use to install it on your local server or to deploy it on your company's remote server. I always copy this String from the console, then edit it in a text editor, put the jar in the same folder as the pom, add the name of the pom to the end of the String, hit enter, the jar gets installed, its poms and checksums created, when done, I delete the jar I put in the project's folder. I've never tried the deploy option, as I am planning to copy my entire local repository to the remote one, as soon as I am finished migrating to Maven 2. The install version works perfectly (and I am sure when you set up distribution management, this works perfectly too). To set up Distribution Management, Add it to your pom, then set the login information in your setting.xml, though I wouldn't recommend you to leave away the password - a) for security reasons b) so that noone can accidently upload something to your repository... Hope that helps, Christine Original-Nachricht Datum: Wed, 05 Mar 2008 23:29:53 +0100 Von: david delbecq [EMAIL PROTECTED] An: Maven Users List users@maven.apache.org Betreff: Re: converting from maven1 to maven2, pom for third party jars? Did :) does not work, will investigate further. For now am doing scripted convertion server side, attackign directly the server direcgtory structure using install-file, works like a charm :D Nick Stolwijk a écrit : Take a look at the repositoryId [1] option of deploy-file and the server section in settings.xml [2]. They should take care of your authorisation. Hth, Nick Stolwijk [1] http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId [2] http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_server delbd wrote: the deploy target doesnt seem to accept the fact our local repository requires password authentification. it just fails. Our server ask client for credential for write operation (apache DAV mod) but maven doesn't try with password. i'll give a try using install:install-file thanks [EMAIL PROTECTED] a écrit : There is a solution for this problem. The deploy:deploy-file will automatically generate a pom file. So, remove the jars from your remote repository and deploy them again with mvn deploy:deploy-file . Perhaps if you make a list with the directories it should be possible to create a little script to do it. Hth, Nick S. -Original Message- From: David Delbecq [mailto:[EMAIL PROTECTED] Sent: Wed 3/5/2008 16:27 To: Maven Users List Subject: converting from maven1 to maven2, pom for third party jars? Hello, in the process of converting our app from maven1 to maven2, we changed our repository to have maven2 structure. For most library we use public repositories (maven, jboss, apache) to fetch files. But from some libraries we had to make them available to our local repository, moving the jar from his group/jars/artefact-version.jar to group/artifact/version/artifact-version.jar. However, for the jar there is no pom files coming along, just a jar. maven2 has no special trouble handling them, except it keeps trying to go to all our configured repositories and try to download those inexistant pom: Downloading: http://xxx/repository/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom Downloading: http://download.java.net/maven/2//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom Downloading: http://archiva.openqa.org/repository/releases//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom Downloading: http://repository.jboss.com/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom Downloading: http://repo1.maven.org/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom Downloading: http://xxx/repository/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom Downloading: http://download.java.net/maven/2//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom Downloading:
Re: dependency-copy
refactor your pom structure. If you originally had moduleA/ pom.xml (packaging jar) You refactor to something like moduleAsuper/ pom.xml (new pom with packaging pom) moduleA/ pom.xml (packaging jar - this is the old pom moved to a child) moduleB/ pom.xml (this is the dependency packaging pom) now when you do a mvn clean install from moduleAsuper it will do what you are looking for. Of course if you already have a directory-parent pom, I'd just add moduleB to that directory-parent (though it does mean that you have to do clean install from the directory-parent) Note: maven has two kinds of parent poms, the first kind is the one specified with the parent tag in the pom, the other kind is where the pom is in sub-directory. These do not have to be the same! (but for most people it helps if they are!) -Stephen On Thu, Mar 6, 2008 at 6:27 AM, sandeep28 [EMAIL PROTECTED] wrote: I want something like to run mvn clean install on my original POM and make an assembly which has all jars which I extracted using newly made POM. sandeep28 wrote: Hi Stephen, I did that, I made a seperate POM with all desired artifacts and used copy-dependencies to take all transitive dependency in a new folder, but now how to include this new POM in my original POM. If I create a module in my original POM, maven expects packaging type in aggregator POM as POM which is not possible as I have to create a jar. HOw should I go beyond this. Stephen Connolly-2 wrote: Sorry, my bad, I did not notice that dependency:copy does not have the option for transitive dependencies that copy-dependencies has Well I would refactor, have a module that has all the stuff you want as it's dependencies and use copy-dependencies to copy them, then archive them up into a zip or such. Then use unpack-dependencies on this zip in the module where you want them -Stephen On Wed, Mar 5, 2008 at 8:53 AM, Saxena, Sandeep [EMAIL PROTECTED] wrote: I did not get this. They are not in my projects POM. If I use Copy it just copies the artifacts in the list and not transitive Dependencies. -Original Message- From: Stephen Connolly [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2008 2:21 PM To: Maven Users List Subject: Re: dependency-copy On Wed, Mar 5, 2008 at 6:16 AM, Saxena, Sandeep [EMAIL PROTECTED] wrote: Thanks Upul. But it does not copy all transitive dependencies from a list. I want something like I give a list of 10 artifacts which may or may not be In the Project's POM and I want all transitive dependencies for these 10 I think you will need to separate your concerns. When they are in the project's POM you should use copy-dependencies, when not in the project's POM you should use copy. If you have both, you will need to use both. Artifacts to be copied in a folder of my assembly. Thanks, Sandeep. -Original Message- From: Upul Godage [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2008 11:37 AM To: Maven Users List Subject: Re: dependency-copy I think assembly plugin does this. Here all the dependencies are copied to a lib directory in the final release. http://maven.apache.org/plugins/maven-assembly-plugin/howto.html assembly idbin/id dependencySets dependencySet outputDirectorylib/outputDirectory /dependencySet /dependencySets /assembly Hope this helps. Upul On Wed, Mar 5, 2008 at 11:20 AM, Saxena, Sandeep [EMAIL PROTECTED] wrote: I want to copy all transitive dependencies for a list of artifacts in my assembly. If I use dependency: copy with a list of artifacts I just get all the jars defined In my list and not transitive dependencies. And if I use dependency: copy-dependencies, it takes all the artifacts from my project's POM Instead of taking a list of artifacts. To make it clear my project depends on three artifacts A, B and C but I want to copy all the Transitive dependencies of another artifact D in a folder of my assembly. Any clues? Regards, Sandeep. - 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] -- View this message in context: http://www.nabble.com/dependency-copy-tp15843742s177p15867316.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
Re: RE: converting from maven1 to maven2, pom for third party jars?
So what else do you recommend me to easily get all required dependencies on the remote server - at once if possible? What would / could happen if I simply copied the local repository to the remote one? Thanks in advance, Stefanie Original-Nachricht Datum: Thu, 6 Mar 2008 09:10:48 +0100 Von: [EMAIL PROTECTED] An: Maven Users List users@maven.apache.org Betreff: RE: converting from maven1 to maven2, pom for third party jars? I can't repeat it often enough: do not copy a local repository to be used as a remote repository. There is not the same information in your local repository as in your remote repository. Really, do use a Maven repository / mirror, like Archiva, Artifactory or Nexus/Proximity. Hth, Nick S. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thu 3/6/2008 07:04 To: Maven Users List Subject: Re: converting from maven1 to maven2, pom for third party jars? To be able to deploy something on your company's remote server, have a look at Distribution Management. What I do for those external jars is - on the console, when maven doesn't find a depdency, it always gives you the exact String you need to use to install it on your local server or to deploy it on your company's remote server. I always copy this String from the console, then edit it in a text editor, put the jar in the same folder as the pom, add the name of the pom to the end of the String, hit enter, the jar gets installed, its poms and checksums created, when done, I delete the jar I put in the project's folder. I've never tried the deploy option, as I am planning to copy my entire local repository to the remote one, as soon as I am finished migrating to Maven 2. The install version works perfectly (and I am sure when you set up distribution management, this works perfectly too). To set up Distribution Management, Add it to your pom, then set the login information in your setting.xml, though I wouldn't recommend you to leave away the password - a) for security reasons b) so that noone can accidently upload something to your repository... Hope that helps, Christine Original-Nachricht Datum: Wed, 05 Mar 2008 23:29:53 +0100 Von: david delbecq [EMAIL PROTECTED] An: Maven Users List users@maven.apache.org Betreff: Re: converting from maven1 to maven2, pom for third party jars? Did :) does not work, will investigate further. For now am doing scripted convertion server side, attackign directly the server direcgtory structure using install-file, works like a charm :D Nick Stolwijk a écrit : Take a look at the repositoryId [1] option of deploy-file and the server section in settings.xml [2]. They should take care of your authorisation. Hth, Nick Stolwijk [1] http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId [2] http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_server delbd wrote: the deploy target doesnt seem to accept the fact our local repository requires password authentification. it just fails. Our server ask client for credential for write operation (apache DAV mod) but maven doesn't try with password. i'll give a try using install:install-file thanks [EMAIL PROTECTED] a écrit : There is a solution for this problem. The deploy:deploy-file will automatically generate a pom file. So, remove the jars from your remote repository and deploy them again with mvn deploy:deploy-file . Perhaps if you make a list with the directories it should be possible to create a little script to do it. Hth, Nick S. -Original Message- From: David Delbecq [mailto:[EMAIL PROTECTED] Sent: Wed 3/5/2008 16:27 To: Maven Users List Subject: converting from maven1 to maven2, pom for third party jars? Hello, in the process of converting our app from maven1 to maven2, we changed our repository to have maven2 structure. For most library we use public repositories (maven, jboss, apache) to fetch files. But from some libraries we had to make them available to our local repository, moving the jar from his group/jars/artefact-version.jar to group/artifact/version/artifact-version.jar. However, for the jar there is no pom files coming along, just a jar. maven2 has no special trouble handling them, except it keeps trying to go to all our configured repositories and try to download those inexistant pom: Downloading: http://xxx/repository/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom Downloading: http://download.java.net/maven/2//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom Downloading: http://archiva.openqa.org/repository/releases//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Re: Coverage report of web application integration test with cobertura-maven-plugin
On Thu, Mar 6, 2008 at 4:23 AM, Joshua Spiewak [EMAIL PROTECTED] wrote: 1. Looks like an issue was just opened here: http://jira.codehaus.org/browse/MCOBERTURA-86 2. Not sure about Jeff, mine hasn't amounted to anything worth checking in, and my effort has fallen by the wayside for the past couple of months. I did not check in my code because I did not have the committer status. I still need to do more validation because I first developed it with an intent to use it with Cargo but this one has some problems with classifier. So I need to build a test POM for the validation. However, if you need it, I can send the code. Jeff joseph22 wrote: We have a very similar need. We have an integration-test module that has dependencies on other modules containing unit tests and would like to have the integration-test module use the instrumented classes from its dependencies to generate a cobertura report. A few questions: 1. Has this issue been logged as a jira bug or task against the plugin? If so, what is the jira number? 2. The work that you or jeff have been doing -- is it checked in anywhere? If so, how could someone check it out. tks Joseph Joshua Spiewak wrote: So in a simplistic attempt to get this to work, I looked at the Clover plugin to see what it did. I tried changing the execute phase of CoberturaCheckMojo and CoberturaReportMojo to verify, like the Clover mojos of the same function. This fails in the package phase: [INFO] Error configuring: org.apache.maven.plugins:maven-war-plugin. Reason: ERROR: Cannot override read-only parameter: classesDirectory in goal: war:war Looking at the Clover plugin a little more, it looks like it manages its separate lifecycle a little differently and only the instrument mojo kicks off the separate lifecycle. And in fact, the instrument mojo is a shell, and there is an internal instrument mojo that does the real work. Do you think that the Cobertura mojo can be incrementally moved to this model? What else were you intending? I would love to get this working, as having code coverage (with checking) is that last step in converting our main project from Ant to Maven. So let me know if you need help! -- Josh Jeff MAURY wrote: Richard, I have the same problem and I think this is not feasible with the current design of the Cobertura Maven2 plugin design as it is today. It does only address the test phase and not the integration-test phase. I plan to work on another Cobertura plugin (inspired from the philosophy of the Clover plugin) that address this issue. Jeff On Dec 13, 2007 3:29 PM, Brewster, Richard [EMAIL PROTECTED] wrote: I want to produce a coverage report for the integration test phase of a web application (war packaging). My integration tests are run by the Cargo maven plugin launching JBoss 4.0.5. I've been using the 2.0 version of the cobertura-maven-plugin (and will try the upgrade to 2.2). I have a modular project with core and web modules. I get the expected coverage reports for my core module, but zero coverage for the web module. The instrumented classes are not packaged into the war, for one. According to the Cobertura FAQ, this sort of coverage testing can be done. http://cobertura.sourceforge.net/faq.html Has anyone done this? Any advice would be appreciated! Also, it would be great if integration test coverage could be documented here, too: http://mojo.codehaus.org/cobertura-maven-plugin/usage.html Thanks, Richard Brewster Senior Associate Perrin Quarles Associates [EMAIL PROTECTED] (434) 817-2640 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com -- View this message in context: http://www.nabble.com/-ANN--cobertura-maven-plugin-2.2-tp14310731s177p15865771.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] -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe
RE: RE: converting from maven1 to maven2, pom for third party jars?
I would setup a maven repository, with mirrors for at least central and maybe some other repositories. Also create inhouse repositories for your own release, Snapshots and external dependencies. (3 different repositories) Then set up your local maven to use the mirrors, and rebuild with an empty local repository. For every dependency that is not found, use the same tactics as you did, but then with deploy:deploy-file deploy them to the external dependency repository and add the remote repository to the repository section in the pom file. The way local and remote repositories are different, for example: - Local snapshots are not saved with timestamp, remote snapshots are saved with timestamps. If you use a local repository as remote repository, maven can't tell if a SNAPSHOT has changed and won't download newer SNAPSHOTS. Hth, Nick S. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thu 3/6/2008 09:34 To: Maven Users List Subject: Re: RE: converting from maven1 to maven2, pom for third party jars? So what else do you recommend me to easily get all required dependencies on the remote server - at once if possible? What would / could happen if I simply copied the local repository to the remote one? Thanks in advance, Stefanie Original-Nachricht Datum: Thu, 6 Mar 2008 09:10:48 +0100 Von: [EMAIL PROTECTED] An: Maven Users List users@maven.apache.org Betreff: RE: converting from maven1 to maven2, pom for third party jars? I can't repeat it often enough: do not copy a local repository to be used as a remote repository. There is not the same information in your local repository as in your remote repository. Really, do use a Maven repository / mirror, like Archiva, Artifactory or Nexus/Proximity. Hth, Nick S. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thu 3/6/2008 07:04 To: Maven Users List Subject: Re: converting from maven1 to maven2, pom for third party jars? To be able to deploy something on your company's remote server, have a look at Distribution Management. What I do for those external jars is - on the console, when maven doesn't find a depdency, it always gives you the exact String you need to use to install it on your local server or to deploy it on your company's remote server. I always copy this String from the console, then edit it in a text editor, put the jar in the same folder as the pom, add the name of the pom to the end of the String, hit enter, the jar gets installed, its poms and checksums created, when done, I delete the jar I put in the project's folder. I've never tried the deploy option, as I am planning to copy my entire local repository to the remote one, as soon as I am finished migrating to Maven 2. The install version works perfectly (and I am sure when you set up distribution management, this works perfectly too). To set up Distribution Management, Add it to your pom, then set the login information in your setting.xml, though I wouldn't recommend you to leave away the password - a) for security reasons b) so that noone can accidently upload something to your repository... Hope that helps, Christine Original-Nachricht Datum: Wed, 05 Mar 2008 23:29:53 +0100 Von: david delbecq [EMAIL PROTECTED] An: Maven Users List users@maven.apache.org Betreff: Re: converting from maven1 to maven2, pom for third party jars? Did :) does not work, will investigate further. For now am doing scripted convertion server side, attackign directly the server direcgtory structure using install-file, works like a charm :D Nick Stolwijk a écrit : Take a look at the repositoryId [1] option of deploy-file and the server section in settings.xml [2]. They should take care of your authorisation. Hth, Nick Stolwijk [1] http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId [2] http://maven.apache.org/ref/2.0.7/maven-settings/settings.html#class_server delbd wrote: the deploy target doesnt seem to accept the fact our local repository requires password authentification. it just fails. Our server ask client for credential for write operation (apache DAV mod) but maven doesn't try with password. i'll give a try using install:install-file thanks [EMAIL PROTECTED] a écrit : There is a solution for this problem. The deploy:deploy-file will automatically generate a pom file. So, remove the jars from your remote repository and deploy them again with mvn deploy:deploy-file . Perhaps if you make a list with the directories it should be possible to create a little script to do it. Hth, Nick S. -Original Message- From: David Delbecq [mailto:[EMAIL PROTECTED] Sent: Wed 3/5/2008 16:27 To: Maven Users List Subject: converting from maven1
jaxws-maven-plugin with IBM SDK failed
Hi to all, I see the following error while trying to use the jaxws-maven-plugin with an IBM SDK (under XP). org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute wsgen at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to execute wsg en at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.j ava:96) at org.codehaus.mojo.jaxws.MainWsGenMojo.execute(MainWsGenMojo.java:14) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:539) ... 16 more Caused by: java.lang.NoClassDefFoundError: com.sun.tools.apt.Main at com.sun.tools.ws.wscompile.WsgenTool.buildModel(WsgenTool.java:194) at com.sun.tools.ws.wscompile.WsgenTool.run(WsgenTool.java:119) at com.sun.tools.ws.WsGen.doMain(WsGen.java:69) at org.codehaus.mojo.jaxws.AbstractWsGenMojo.execute(AbstractWsGenMojo.j ava:91) ... 19 more the com.sun.tools.apt.Main is available in the IBM SDK 1.5 tools.jar so I puzzled. Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Try to run install before eclipse:eclipse
Hi, for a multiple project it's necessary to run mvn install before mvn eclipse:eclipse because of dependencies. I want that install runs automatically if a developer runs eclipse:eclipse but i don't know how i can do that. I searched for hours in the internet but i didn't found a solution to integrate that into the pom-file. The way to do that with the preGoal-Tag is not possible in maven2. I'm very new with maven. I hope somebody can help me. Greetings Andi -- View this message in context: http://www.nabble.com/Try-to-run-install-before-eclipse%3Aeclipse-tp15869344s177p15869344.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: RE: RE: converting from maven1 to maven2, pom for third party jars?
The way local and remote repositories are different, for example: - Local snapshots are not saved with timestamp, remote snapshots are saved with timestamps. If you use a local repository as remote repository, maven can't tell if a SNAPSHOT has changed and won't download newer SNAPSHOTS. So - in other words - if I didn't use any snapshots so far, there won't be differences and I could simply upload my local repo?! Re-deploying every dependency MANUALLY would be VERY time consuming... :-( Thanks in advance, Stefanie -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: paging Japanese readers for a patch review....
I have reviewed and post comment with attachment on the jira. On 3/6/08, Brian E. Fox [EMAIL PROTECTED] wrote: Woo-hoo! Please comment on the jira -Original Message- From: Ryuzo Yamamoto [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 05, 2008 9:29 PM To: Maven Users List Subject: Re: paging Japanese readers for a patch review Hi Brian, Shall I review this patch? And shall I post comment on jira (MNG-428) ? Thanks, Yamamoto On 2/29/08, Brian E. Fox [EMAIL PROTECTED] wrote: Anyone able to verify this patch that can read Japanese? http://jira.codehaus.org/browse/MNG-428 - 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] -- -- Ryuzo Yamamoto http://d.hatena.ne.jp/dragon3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Try to run install before eclipse:eclipse
On 06/03/2008, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Making install run before eclipse:eclipse is a bad idea in some cases. In particular, when a project doesn't compile it is currently possible to still run eclipse:eclipse. Making install a pre-requisite would block that, which would be really anoying. I think what the original poster is saying is that eclipse:eclipse is correctly generating all of the eclipse projects, but that eclipse then displays build errors because the jars that the newly created eclipse projects point to don't yet exist. I don't see that as a big problem myself. The eclipse projects *do* exist. And anyway, some very basic user training is all that is needed, to ensure that people run mvn install eclipse:eclipse rather than mvn eclipse:eclipse If the users are so dumb that they cannot learn that, then the best solution would be to provide an eclipse-setup.bat file for them to click on (I assume that category of users run Windows :-) Perhaps binding eclipse:eclipse to the install phase is also a possibility. Then mvn install would be all that is needed. It would waste time on every build cycle by rewriting bits of the eclipse project def, but it's not a big overhead. you could always bind it inside a profile, then developers could use mvn install -Peclipse to get IDE files on install (perhaps they could enable by default in their settings.xml?) while build machines wouldn't have it enabled - something like... profiles profile ideclipse/id build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.4/version executions execution idide-support/id phaseinstall/phase goals goaleclipse/goal /goals /execution /executions /plugin /plugins /build /profile /profiles Note that i haven't tried this; there might be problems I haven't thought of.. Regards, Simon [EMAIL PROTECTED] schrieb: Hi, This is not possible to configure in your pom file. However, it should be possible to adjust the maven Eclipse Plugin to execute the install phase. (Just like surefire-reports execute the test phase) For this there should be a mojo added to the Maven Eclipse Plugin. This sounds like a nice feature request. What do others think of this? That you can execute eclipse:eclipse just like normal, but also a goal like eclipse:eclipse-install to execute an install before eclipse:eclipse is run? Hth, Nick Stolwijk -Original Message- From: 109s [mailto:[EMAIL PROTECTED] Sent: Thu 3/6/2008 10:21 To: users@maven.apache.org Subject: Try to run install before eclipse:eclipse Hi, for a multiple project it's necessary to run mvn install before mvn eclipse:eclipse because of dependencies. I want that install runs automatically if a developer runs eclipse:eclipse but i don't know how i can do that. I searched for hours in the internet but i didn't found a solution to integrate that into the pom-file. The way to do that with the preGoal-Tag is not possible in maven2. I'm very new with maven. I hope somebody can help me. Greetings Andi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Cheers, Stuart
RE: Try to run install before eclipse:eclipse
Hi, This is not possible to configure in your pom file. However, it should be possible to adjust the maven Eclipse Plugin to execute the install phase. (Just like surefire-reports execute the test phase) For this there should be a mojo added to the Maven Eclipse Plugin. This sounds like a nice feature request. What do others think of this? That you can execute eclipse:eclipse just like normal, but also a goal like eclipse:eclipse-install to execute an install before eclipse:eclipse is run? Hth, Nick Stolwijk -Original Message- From: 109s [mailto:[EMAIL PROTECTED] Sent: Thu 3/6/2008 10:21 To: users@maven.apache.org Subject: Try to run install before eclipse:eclipse Hi, for a multiple project it's necessary to run mvn install before mvn eclipse:eclipse because of dependencies. I want that install runs automatically if a developer runs eclipse:eclipse but i don't know how i can do that. I searched for hours in the internet but i didn't found a solution to integrate that into the pom-file. The way to do that with the preGoal-Tag is not possible in maven2. I'm very new with maven. I hope somebody can help me. Greetings Andi -- View this message in context: http://www.nabble.com/Try-to-run-install-before-eclipse%3Aeclipse-tp15869344s177p15869344.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: heap size for unit tests
Have a look at the configuration / block of the surefire plugin :
http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
to add the -Xmx option.
I think this is not a systemProperty / that you have to use. I seem to
remember there's an tag like argLine /.
I also found this: ${maven.surefire.debug} here
http://jira.codehaus.org/browse/MEVENIDE-435. Might work.
Cheers.
-Message d'origine-
De : Ritz, Martin [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 6 mars 2008 12:47
À : users@maven.apache.org
Objet : heap size for unit tests
Hello,
is it possible to increase the heap size for maven especially for the unit
tests?
---
regards
Martin Ritz
BTC AG - Unit Softwaredevelopment
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Try to run install before eclipse:eclipse
Poor thing. I don't want to describe every developer what they have to do after getting the sources from CVS. I thought eclipse:eclipse could be enough. Is there maybe a way for example to call ant and call back maven with install in this situation? Greets Andi Nick Stolwijk-4 wrote: Hi, This is not possible to configure in your pom file. However, it should be possible to adjust the maven Eclipse Plugin to execute the install phase. (Just like surefire-reports execute the test phase) For this there should be a mojo added to the Maven Eclipse Plugin. This sounds like a nice feature request. What do others think of this? That you can execute eclipse:eclipse just like normal, but also a goal like eclipse:eclipse-install to execute an install before eclipse:eclipse is run? Hth, Nick Stolwijk -Original Message- From: 109s [mailto:[EMAIL PROTECTED] Sent: Thu 3/6/2008 10:21 To: users@maven.apache.org Subject: Try to run install before eclipse:eclipse Hi, for a multiple project it's necessary to run mvn install before mvn eclipse:eclipse because of dependencies. I want that install runs automatically if a developer runs eclipse:eclipse but i don't know how i can do that. I searched for hours in the internet but i didn't found a solution to integrate that into the pom-file. The way to do that with the preGoal-Tag is not possible in maven2. I'm very new with maven. I hope somebody can help me. Greetings Andi -- View this message in context: http://www.nabble.com/Try-to-run-install-before-eclipse%3Aeclipse-tp15869344s177p15869344.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] -- View this message in context: http://www.nabble.com/Try-to-run-install-before-eclipse%3Aeclipse-tp15869344s177p15869991.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: Try to run install before eclipse:eclipse
You have a good point. Maybe it is better to let eclipse:eclipse do a resolve dependencies. So you're sure to have all the jar files in the repository? With regards, Nick S. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thu 3/6/2008 11:15 To: Maven Users List Subject: Re: Try to run install before eclipse:eclipse Making install run before eclipse:eclipse is a bad idea in some cases. In particular, when a project doesn't compile it is currently possible to still run eclipse:eclipse. Making install a pre-requisite would block that, which would be really anoying. I think what the original poster is saying is that eclipse:eclipse is correctly generating all of the eclipse projects, but that eclipse then displays build errors because the jars that the newly created eclipse projects point to don't yet exist. I don't see that as a big problem myself. The eclipse projects *do* exist. And anyway, some very basic user training is all that is needed, to ensure that people run mvn install eclipse:eclipse rather than mvn eclipse:eclipse If the users are so dumb that they cannot learn that, then the best solution would be to provide an eclipse-setup.bat file for them to click on (I assume that category of users run Windows :-) Perhaps binding eclipse:eclipse to the install phase is also a possibility. Then mvn install would be all that is needed. It would waste time on every build cycle by rewriting bits of the eclipse project def, but it's not a big overhead. Note that i haven't tried this; there might be problems I haven't thought of.. Regards, Simon [EMAIL PROTECTED] schrieb: Hi, This is not possible to configure in your pom file. However, it should be possible to adjust the maven Eclipse Plugin to execute the install phase. (Just like surefire-reports execute the test phase) For this there should be a mojo added to the Maven Eclipse Plugin. This sounds like a nice feature request. What do others think of this? That you can execute eclipse:eclipse just like normal, but also a goal like eclipse:eclipse-install to execute an install before eclipse:eclipse is run? Hth, Nick Stolwijk -Original Message- From: 109s [mailto:[EMAIL PROTECTED] Sent: Thu 3/6/2008 10:21 To: users@maven.apache.org Subject: Try to run install before eclipse:eclipse Hi, for a multiple project it's necessary to run mvn install before mvn eclipse:eclipse because of dependencies. I want that install runs automatically if a developer runs eclipse:eclipse but i don't know how i can do that. I searched for hours in the internet but i didn't found a solution to integrate that into the pom-file. The way to do that with the preGoal-Tag is not possible in maven2. I'm very new with maven. I hope somebody can help me. Greetings Andi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
MavenProject.getDependencyArtifacts() returns null
Hi. When running my plugin from a phase like 'package' (by using the execution tag) then project.getDependencyArtifacts() returns the dependencies artifacts. But when I run the plugin standalone, that is in the format 'mvn groupID:myplugin:version:goal' it returns null. How can I overcome this. Have I got to initialize something? Thanks for any answer ... , Daniel ' - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Try to run install before eclipse:eclipse
Making install run before eclipse:eclipse is a bad idea in some cases. In particular, when a project doesn't compile it is currently possible to still run eclipse:eclipse. Making install a pre-requisite would block that, which would be really anoying. I think what the original poster is saying is that eclipse:eclipse is correctly generating all of the eclipse projects, but that eclipse then displays build errors because the jars that the newly created eclipse projects point to don't yet exist. I don't see that as a big problem myself. The eclipse projects *do* exist. And anyway, some very basic user training is all that is needed, to ensure that people run mvn install eclipse:eclipse rather than mvn eclipse:eclipse If the users are so dumb that they cannot learn that, then the best solution would be to provide an eclipse-setup.bat file for them to click on (I assume that category of users run Windows :-) Perhaps binding eclipse:eclipse to the install phase is also a possibility. Then mvn install would be all that is needed. It would waste time on every build cycle by rewriting bits of the eclipse project def, but it's not a big overhead. Note that i haven't tried this; there might be problems I haven't thought of.. Regards, Simon [EMAIL PROTECTED] schrieb: Hi, This is not possible to configure in your pom file. However, it should be possible to adjust the maven Eclipse Plugin to execute the install phase. (Just like surefire-reports execute the test phase) For this there should be a mojo added to the Maven Eclipse Plugin. This sounds like a nice feature request. What do others think of this? That you can execute eclipse:eclipse just like normal, but also a goal like eclipse:eclipse-install to execute an install before eclipse:eclipse is run? Hth, Nick Stolwijk -Original Message- From: 109s [mailto:[EMAIL PROTECTED] Sent: Thu 3/6/2008 10:21 To: users@maven.apache.org Subject: Try to run install before eclipse:eclipse Hi, for a multiple project it's necessary to run mvn install before mvn eclipse:eclipse because of dependencies. I want that install runs automatically if a developer runs eclipse:eclipse but i don't know how i can do that. I searched for hours in the internet but i didn't found a solution to integrate that into the pom-file. The way to do that with the preGoal-Tag is not possible in maven2. I'm very new with maven. I hope somebody can help me. Greetings Andi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
override a goal within a phase
Hi, does anybody can tell me how can I replace the standard jar:jar, in the package phase, with my :jar goal implemented by my Mojo? or is there a way to disable the execution of the standard jar:jar goal? TIA, Paolo. -- GPG key: 1024D/9C5AE886 2004-10-21 Paolo Casarini [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Try to run install before eclipse:eclipse
On Thursday 06 March 2008 [EMAIL PROTECTED] wrote: Making install run before eclipse:eclipse is a bad idea in some cases. We would need it only in multi-module projects if some artifacts cannot be found in the repository. In particular, when a project doesn't compile it is currently possible to still run eclipse:eclipse. Making install a pre-requisite would block that, which would be really anoying. Good point! A new developer should not only be able to join the team if the project compiles right now. I think what the original poster is saying is that eclipse:eclipse is correctly generating all of the eclipse projects, but that eclipse then displays build errors because the jars that the newly created eclipse projects point to don't yet exist. No, mvn eclipse:eclipse fails in a multi-module project, if the artifacts are not in a (local or remote) repository, even if they could have been built. See also this thread for some more details: http://www.nabble.com/maven-eclipse-plugin-with-multi-module-projects-to15222495s177.html hth, - martin -- Martin Höller | [EMAIL PROTECTED] *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 signature.asc Description: This is a digitally signed message part.
RE: Try to run install before eclipse:eclipse
The problem is, that eclipse:eclipse is the invocation of a goal and instead of maven 1 preGoal and postGoal, maven 2 binds goals to phases and you can't chain goals. You could prescribe the dev'ers to execute mvn install eclipse:eclipse instead of mvn eclipse. Hth, Nick S. -Original Message- From: 109s [mailto:[EMAIL PROTECTED] Sent: Thu 3/6/2008 10:58 To: users@maven.apache.org Subject: RE: Try to run install before eclipse:eclipse Poor thing. I don't want to describe every developer what they have to do after getting the sources from CVS. I thought eclipse:eclipse could be enough. Is there maybe a way for example to call ant and call back maven with install in this situation? Greets Andi Nick Stolwijk-4 wrote: Hi, This is not possible to configure in your pom file. However, it should be possible to adjust the maven Eclipse Plugin to execute the install phase. (Just like surefire-reports execute the test phase) For this there should be a mojo added to the Maven Eclipse Plugin. This sounds like a nice feature request. What do others think of this? That you can execute eclipse:eclipse just like normal, but also a goal like eclipse:eclipse-install to execute an install before eclipse:eclipse is run? Hth, Nick Stolwijk -Original Message- From: 109s [mailto:[EMAIL PROTECTED] Sent: Thu 3/6/2008 10:21 To: users@maven.apache.org Subject: Try to run install before eclipse:eclipse Hi, for a multiple project it's necessary to run mvn install before mvn eclipse:eclipse because of dependencies. I want that install runs automatically if a developer runs eclipse:eclipse but i don't know how i can do that. I searched for hours in the internet but i didn't found a solution to integrate that into the pom-file. The way to do that with the preGoal-Tag is not possible in maven2. I'm very new with maven. I hope somebody can help me. Greetings Andi -- View this message in context: http://www.nabble.com/Try-to-run-install-before-eclipse%3Aeclipse-tp15869344s177p15869344.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] -- View this message in context: http://www.nabble.com/Try-to-run-install-before-eclipse%3Aeclipse-tp15869344s177p15869991.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]
heap size for unit tests
Hello, is it possible to increase the heap size for maven especially for the unit tests? --- regards Martin Ritz BTC AG - Unit Softwaredevelopment mailto:[EMAIL PROTECTED]
Re: heap size for unit tests
Check MAVEN_OPTS mentioned near the bottom of http://maven.apache.org/download On 3/6/08, Ritz, Martin [EMAIL PROTECTED] wrote: Hello, is it possible to increase the heap size for maven especially for the unit tests? --- regards Martin Ritz BTC AG - Unit Softwaredevelopment mailto:[EMAIL PROTECTED] -- ASCII ribbon campaign: () against HTML email /\ against Microsoft attachments Information: http://www.expita.com/nomime.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: override a goal within a phase
don't use packagingjar/packaging and that will disable the jar:jar On Thu, Mar 6, 2008 at 12:10 PM, Paolo Casarini [EMAIL PROTECTED] wrote: Hi, does anybody can tell me how can I replace the standard jar:jar, in the package phase, with my :jar goal implemented by my Mojo? or is there a way to disable the execution of the standard jar:jar goal? TIA, Paolo. -- GPG key: 1024D/9C5AE886 2004-10-21 Paolo Casarini [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mvn install ignore hibernate hbm.xml files
Hi! If I wanna install my project on my local repository the hibernate hbm.xml files always get ignored - No hbm.xml file is in the generated JAR! If I use mvn package the hbm.xml files are there - whats going wrong with mvn install pom file: http://www.nabble.com/file/p15873003/pom.xml pom.xml -- View this message in context: http://www.nabble.com/mvn-install-ignore-hibernate-hbm.xml-files-tp15873003s177p15873003.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: mvn install ignore hibernate hbm.xml files
MPF wrote: Hi! If I wanna install my project on my local repository the hibernate hbm.xml files always get ignored - No hbm.xml file is in the generated JAR! If I use mvn package the hbm.xml files are there - whats going wrong with mvn install I assume you have those along with your java source files. Only javadoc-related files are copied from there (i.e. src/main/java). You could copy the hbm mappings in your src/main/resources directory, keeping the same sub-dir structure if any. hth, Manos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: mvn install ignore hibernate hbm.xml files
Thank you very much, it works! Best regards Markus -Ursprüngliche Nachricht- Von: Manos Batsis [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 06. März 2008 14:19 An: Maven Users List Betreff: Re: mvn install ignore hibernate hbm.xml files MPF wrote: Hi! If I wanna install my project on my local repository the hibernate hbm.xml files always get ignored - No hbm.xml file is in the generated JAR! If I use mvn package the hbm.xml files are there - whats going wrong with mvn install I assume you have those along with your java source files. Only javadoc-related files are copied from there (i.e. src/main/java). You could copy the hbm mappings in your src/main/resources directory, keeping the same sub-dir structure if any. hth, Manos - 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: Extending maven to accomplish some tasks
Ah, the universal antrun solution. Guys, maven is better than ant, why
do you keep using ant?
For copying the built file use dependency plugin:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idcopy-installed/id
phaseinstall/phase
goals
goalcopy/goal
/goals
configuration
overWriteReleasestrue/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
stripVersiontrue/stripVersion
artifactItems
artifactItem
groupId${project.groupId}/groupId
artifactId${project.artifactId}/artifactId
version${project.version}/version
type${project.packaging}/type
/artifactItem
/artifactItems
outputDirectory/home/stefan/jboss/server/default/deploy/outputDirectory
/configuration
/execution
/executions
/plugin
/plugins
/build
To invoke things from other poms, use maven-invoker-plugin.
Regards,
Stefan
Ian Hummel wrote:
I use the antrun-maven-plugin to do things like this. I'm not sure if
that's the right way though!
In your specific case you could try
build
...
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
!-- bind to the install phase of the default lifecycle --
execution
phaseinstall/phase
goals
goalrun/goal
/goals
configuration
tasks
copy todir=${todir}
fileset dir=${fromdir} /
/copy
/tasks
/configuration
/execution
execution
!-- not sure in which phase you want to execute your sql
command --
phase???/phase
goals
goalrun/goal
/goals
configuration
tasks
!-- ant task to call subproject... --
/tasks
/configuration
/execution
/executions
/plugin
...
/build
here is some more info on lifecycles/phases:
http://docs.codehaus.org/display/MAVENUSER/introduction-to-the-lifecycle
On Mar 5, 2008, at 8:02 AM, Martin Monsorno wrote:
Hi *,
there's one point I do not understand with maven: how can I use it to
accomplish some tasks that doesn't seem to fit into the standard
phases. The question arised when implementing continuous
integration. For this I want to
- Copy a artefact to another directory. (more precisely: to deploy
the generated war-file to the app server) This is no job for
deploying something to a maven repository or generating a site, but
just a plain copy task.
- Call a special goal of a subproject. (more precisely: my db
subproject uses the hibernate-tools-plugin to execute some sql on the
database) The subproject includes a plugin for a specific task, but I
want to call this from the major build)
With maven 1.x, I wrote a maven.xml and defined goals for this. But
what is the maven 2 way? Must I write a plugin?
Thanks for your thoughts,
Martin.
--
Martin
-
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
Good Morning Anthony-
I am seeing the same errors when the local pom in my subfolder is ignored
and an aberrant base pom is being used for location dependencies
Is there any command we can use to request maven to use the location
parameters in my local pom.xml and IGNORE misleading parent parameters?
Many Thanks to your university for publishing working poms and jars for the
maven community to use
Please keep me apprised
Martin-
- Original Message -
From: [EMAIL PROTECTED]
To: users@maven.apache.org
Sent: Thursday, March 06, 2008 8:53 AM
Subject: MVN: release plugin
I've been working with the release plugin for the first time and
encountering build failures that I've gradually been able to resolve to
the point where I'm prompted for the desired release version, next
development version, etc. (in this initial test dry run I called it
2.5.0.a). My second to last failure involved a custom property
variable ${sakai.version} used in certain Sakai dependency declarations
that the release plugin was unable to update . I believe we have
resolved this version issue by updating ${sakai.version} to SNAPSHOT.
However, when I issue the following release command
mvn -e release:clean release:prepare -DdryRun=true
I encounter another build failure due to a non-existent
base-2.5.0.a.pom that Maven is attempting to locate. None of my poms
in the multi-project build reference 2.5.0.a nor is there a
release.properties file. The poms version are all SNAPSHOT.
How do I get the release plugin to stop trying to locate
base-2.5.0.a.pom and instead commence the release process anew?
Any suggestions would be appreciated,
Cheers,
Anthony Whyte
University of Michigan
arwhyte$ mvn -e release:clean release:prepare -DdryRun=true
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
Downloading:
http://repo1.maven.org/maven2/org/sakaiproject/base/2.5.0.a/base-2.5.0.a.p
om
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: org.sakaiproject
ArtifactId: base
Version: 2.5.0.a
Reason: Unable to download the artifact from any repository
org.sakaiproject:base:pom:2.5.0.a
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
org.sakaiproject:base for project:
org.sakaiproject:component-base:pom:null for project
org.sakaiproject:component-base:pom:null
. . . .
-
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]
MVN: release plugin
I've been working with the release plugin for the first time and
encountering build failures that I've gradually been able to resolve to
the point where I'm prompted for the desired release version, next
development version, etc. (in this initial test dry run I called it
2.5.0.a). My second to last failure involved a custom property
variable ${sakai.version} used in certain Sakai dependency declarations
that the release plugin was unable to update . I believe we have
resolved this version issue by updating ${sakai.version} to SNAPSHOT.
However, when I issue the following release command
mvn -e release:clean release:prepare -DdryRun=true
I encounter another build failure due to a non-existent
base-2.5.0.a.pom that Maven is attempting to locate. None of my poms
in the multi-project build reference 2.5.0.a nor is there a
release.properties file. The poms version are all SNAPSHOT.
How do I get the release plugin to stop trying to locate
base-2.5.0.a.pom and instead commence the release process anew?
Any suggestions would be appreciated,
Cheers,
Anthony Whyte
University of Michigan
arwhyte$ mvn -e release:clean release:prepare -DdryRun=true
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
Downloading:
http://repo1.maven.org/maven2/org/sakaiproject/base/2.5.0.a/base-2.5.0.a.pom
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: org.sakaiproject
ArtifactId: base
Version: 2.5.0.a
Reason: Unable to download the artifact from any repository
org.sakaiproject:base:pom:2.5.0.a
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
org.sakaiproject:base for project:
org.sakaiproject:component-base:pom:null for project
org.sakaiproject:component-base:pom:null
. . . .
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] compiling a generic method with maven fails
Now, I discovered that under Maven 2 with the following maven-compiler-plugin configuration: configuration source1.6/source target1.6/target /configuration Add forktrue/fork Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
how to use buildnumber-maven-plugin
when I use buildnumber-maven-plugin,
it generate the buildnumber as below:
buildNumber: 137261 at timestamp: 1204813937453
but I want to change the timestamp's format, configuration as below:
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
format{0,date,EEE MMM d HH:mm z }/format
items
itemtimestamp/item
/items
/configuration
/plugin
but result is :
buildNumber: Thu Mar 6 15:32 CET 2008 at timestamp: 1204813943453
not as my expect:
buildNumber: 137261 at timestamp: Thu Mar 6 15:32 CET 2008
Why?
Re: MVN: release plugin
Hi,
Try deleting the release.properties file.
Nicole
On 06/03/2008, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I've been working with the release plugin for the first time and
encountering build failures that I've gradually been able to resolve to
the point where I'm prompted for the desired release version, next
development version, etc. (in this initial test dry run I called it
2.5.0.a). My second to last failure involved a custom property
variable ${sakai.version} used in certain Sakai dependency declarations
that the release plugin was unable to update . I believe we have
resolved this version issue by updating ${sakai.version} to SNAPSHOT.
However, when I issue the following release command
mvn -e release:clean release:prepare -DdryRun=true
I encounter another build failure due to a non-existent
base-2.5.0.a.pom that Maven is attempting to locate. None of my poms
in the multi-project build reference 2.5.0.a nor is there a
release.properties file. The poms version are all SNAPSHOT.
How do I get the release plugin to stop trying to locate
base-2.5.0.a.pom and instead commence the release process anew?
Any suggestions would be appreciated,
Cheers,
Anthony Whyte
University of Michigan
arwhyte$ mvn -e release:clean release:prepare -DdryRun=true
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
Downloading:
http://repo1.maven.org/maven2/org/sakaiproject/base/2.5.0.a/base-2.5.0.a.pom
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: org.sakaiproject
ArtifactId: base
Version: 2.5.0.a
Reason: Unable to download the artifact from any repository
org.sakaiproject:base:pom:2.5.0.a
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
org.sakaiproject:base for project:
org.sakaiproject:component-base:pom:null for project
org.sakaiproject:component-base:pom:null
. . . .
-
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]
Wiping out a dependency from an internal repository
Hello, I would like to delete the whole folder that contains a certain dependency from my internal repository by running a Maven command from a dev machine. Is it possible to do that? Thanks, Papapara Tudu -- View this message in context: http://www.nabble.com/Wiping-out-a-dependency-from-an-internal-repository-tp15873175s177p15873175.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: Wiping out a dependency from an internal repository
Papapara Tudu schrieb: Hello, I would like to delete the whole folder that contains a certain dependency from my internal repository by running a Maven command from a dev machine. Is it possible to do that? Do you mean deleting stuff from the ~/.m2/repository directorty on the same computer you are running maven from? The best solution is probably maven-antrun-plugin. That's the fallback for doing weird things, and this really sounds like a weird thing to do. If you mean you want to delete stuff from some other computer, then that's trickier, but using maven-antrun-plugin is again probably the way to do it (via an scp or ssh command or something like that). There is certainly no standard way of doing that in maven, as nobody ever wants to. Maybe you should think carefully about whether you really need to do any of this though.. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: java.class.path and the surefire-plugin
This feature is often request and it would be nice to add it in the surefire plugin. Rémy
Re: Extending maven to accomplish some tasks
On 3/6/08, VUB Stefan Seidel [EMAIL PROTECTED] wrote: Ah, the universal antrun solution. Guys, maven is better than ant, why do you keep using ant? For copying the built file use dependency plugin: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution idcopy-installed/id phaseinstall/phase Is there a way to setup it so maven will 'copy' artifact in 'package' phase, without installing artifact to local repo? Thanks, Tomek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
looking up for a sample of plugin-registry.xml file content
Houdy, Can someone provide me a sample content of the plugin-registry.xml file ? -- View this message in context: http://www.nabble.com/looking-up-for-a-sample-of-plugin-registry.xml-file-content-tp15875026s177p15875026.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: Extending maven to accomplish some tasks
Fair enough...
I had never heard of the maven-invoker-plugin. How about for the
first part of his question? Which plug to use for copying a directory?
- ian.
On Mar 6, 2008, at 9:17 AM, VUB Stefan Seidel wrote:
Ah, the universal antrun solution. Guys, maven is better than ant, why
do you keep using ant?
For copying the built file use dependency plugin:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idcopy-installed/id
phaseinstall/phase
goals
goalcopy/goal
/goals
configuration
overWriteReleasestrue/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
stripVersiontrue/stripVersion
artifactItems
artifactItem
groupId${project.groupId}/groupId
artifactId${project.artifactId}/artifactId
version${project.version}/version
type${project.packaging}/type
/artifactItem
/artifactItems
outputDirectory/home/stefan/jboss/server/default/deploy/
outputDirectory
/configuration
/execution
/executions
/plugin
/plugins
/build
To invoke things from other poms, use maven-invoker-plugin.
Regards,
Stefan
Ian Hummel wrote:
I use the antrun-maven-plugin to do things like this. I'm not sure
if
that's the right way though!
In your specific case you could try
build
...
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
!-- bind to the install phase of the default lifecycle --
execution
phaseinstall/phase
goals
goalrun/goal
/goals
configuration
tasks
copy todir=${todir}
fileset dir=${fromdir} /
/copy
/tasks
/configuration
/execution
execution
!-- not sure in which phase you want to execute your sql
command --
phase???/phase
goals
goalrun/goal
/goals
configuration
tasks
!-- ant task to call subproject... --
/tasks
/configuration
/execution
/executions
/plugin
...
/build
here is some more info on lifecycles/phases:
http://docs.codehaus.org/display/MAVENUSER/introduction-to-the-lifecycle
On Mar 5, 2008, at 8:02 AM, Martin Monsorno wrote:
Hi *,
there's one point I do not understand with maven: how can I use it
to
accomplish some tasks that doesn't seem to fit into the standard
phases. The question arised when implementing continuous
integration. For this I want to
- Copy a artefact to another directory. (more precisely: to deploy
the generated war-file to the app server) This is no job for
deploying something to a maven repository or generating a site, but
just a plain copy task.
- Call a special goal of a subproject. (more precisely: my db
subproject uses the hibernate-tools-plugin to execute some sql on
the
database) The subproject includes a plugin for a specific task,
but I
want to call this from the major build)
With maven 1.x, I wrote a maven.xml and defined goals for this. But
what is the maven 2 way? Must I write a plugin?
Thanks for your thoughts,
Martin.
--
Martin
-
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: override a goal within a phase
Does that mean you will have to manually bind all the other goals to their respective phases? On Mar 6, 2008, at 7:37 AM, Stephen Connolly wrote: don't use packagingjar/packaging and that will disable the jar:jar On Thu, Mar 6, 2008 at 12:10 PM, Paolo Casarini [EMAIL PROTECTED] wrote: Hi, does anybody can tell me how can I replace the standard jar:jar, in the package phase, with my :jar goal implemented by my Mojo? or is there a way to disable the execution of the standard jar:jar goal? TIA, Paolo. -- GPG key: 1024D/9C5AE886 2004-10-21 Paolo Casarini [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: override a goal within a phase
I don't know... erasing packagingjar/packaging don't change any behaviour. The jar:jar goal is still invoked. Paolo. Il giorno 06/mar/08, alle ore 16:42, Ian Hummel ha scritto: Does that mean you will have to manually bind all the other goals to their respective phases? On Mar 6, 2008, at 7:37 AM, Stephen Connolly wrote: don't use packagingjar/packaging and that will disable the jar:jar On Thu, Mar 6, 2008 at 12:10 PM, Paolo Casarini [EMAIL PROTECTED] wrote: Hi, does anybody can tell me how can I replace the standard jar:jar, in the package phase, with my :jar goal implemented by my Mojo? or is there a way to disable the execution of the standard jar:jar goal? TIA, Paolo. -- GPG key: 1024D/9C5AE886 2004-10-21 Paolo Casarini [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] -- GPG key: 1024D/9C5AE886 2004-10-21 Paolo Casarini [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Extending maven to accomplish some tasks
Ian Hummel wrote: Fair enough... I had never heard of the maven-invoker-plugin. How about for the first part of his question? Which plug to use for copying a directory? http://maven.apache.org/plugins/maven-invoker-plugin/ As I understood the first question, it was about copying the artifact into a directory, which is what the dependency plugin does. A whole directory may also be copied with the resources plugin, although if it is really about external files copies to an external location, the ant task is not too wrong there. For copying external resources for inclusion into the artifact, there is another plugin. See http://maven.apache.org/plugins/ for a good start, and also http://mojo.codehaus.org/plugins.html. Stefan -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Extending maven to accomplish some tasks
Tomasz Pik wrote: On 3/6/08, VUB Stefan Seidel [EMAIL PROTECTED] wrote: phaseinstall/phase Is there a way to setup it so maven will 'copy' artifact in 'package' phase, without installing artifact to local repo? phasepackage/phase? Maybe even phaseverify/phase. Then run mvn package. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wiping out a dependency from an internal repository
I know I've seen someone mention a plugin here that can either wipe out your entire repo or selected parts of it. But I can't recall what its called right now, and a quick Google search didn't reveal anything (but I didn't dig much). So if someone else remembers, perhaps they'll post a follow-up. Wayne On 3/6/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Papapara Tudu schrieb: Hello, I would like to delete the whole folder that contains a certain dependency from my internal repository by running a Maven command from a dev machine. Is it possible to do that? Do you mean deleting stuff from the ~/.m2/repository directorty on the same computer you are running maven from? The best solution is probably maven-antrun-plugin. That's the fallback for doing weird things, and this really sounds like a weird thing to do. If you mean you want to delete stuff from some other computer, then that's trickier, but using maven-antrun-plugin is again probably the way to do it (via an scp or ssh command or something like that). There is certainly no standard way of doing that in maven, as nobody ever wants to. Maybe you should think carefully about whether you really need to do any of this though.. Regards, Simon - 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]
Archiva on MS SQL Server
Hi, was anyone able to get Archiva running with a Microsoft SQL Server backend? (I tested SQL 2000 and SQL 2005) I tried it several ways. The only way to succeed was, to reduce the field sizes within the model for the database. This seems to be because of field length limitations for varchar values in MS SQL. Is there an other possibility, I don't know? Or are some plans out there, perhaps to customize the field lengths in the model to support mor database backends? Thanks, Thomas
Re: override a goal within a phase
But then you also miss the other default goals: process-resources maven-resources-plugin resources resources compile maven-compiler-plugin compiler compile process-test-resources maven-resources-plugin resources testResources test-compilemaven-compiler-plugin compiler testCompile test maven-surefire-plugin surefire test package maven-jar-plugin jar jar See [1]. Hth, Nick S. [1] http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html#pom [EMAIL PROTECTED] wrote: jar is the default value, so simply deleting the element is insufficient. You must actually change the value to something else, like pom. Robert Egan Paolo Casarini [EMAIL PROTECTED] wrote on 03/06/2008 10:54:15 AM: I don't know... erasing packagingjar/packaging don't change any behaviour. The jar:jar goal is still invoked. Paolo. Il giorno 06/mar/08, alle ore 16:42, Ian Hummel ha scritto: Does that mean you will have to manually bind all the other goals to their respective phases? On Mar 6, 2008, at 7:37 AM, Stephen Connolly wrote: don't use packagingjar/packaging and that will disable the jar:jar On Thu, Mar 6, 2008 at 12:10 PM, Paolo Casarini [EMAIL PROTECTED] wrote: Hi, does anybody can tell me how can I replace the standard jar:jar, in the package phase, with my :jar goal implemented by my Mojo? or is there a way to disable the execution of the standard jar:jar goal? --- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: override a goal within a phase
Hi Stephen I had a similar situation present itself where I was building a mar (essentially same as jar with a module.xml configurator) so where the pom was specifying using packagingmar/packaging i simply changed the pom to use jar packaging e.g. packagingjar/packaging and this disables jar goals? This appears to be non-intuitive .. is there a readme which says to execute a goal specify the opposite on the packaging element? Any way to override packaging on command line? Is there any documentation on this? Thanks/ M- - Original Message - From: [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Thursday, March 06, 2008 11:05 AM Subject: Re: override a goal within a phase jar is the default value, so simply deleting the element is insufficient. You must actually change the value to something else, like pom. Robert Egan Paolo Casarini [EMAIL PROTECTED] wrote on 03/06/2008 10:54:15 AM: I don't know... erasing packagingjar/packaging don't change any behaviour. The jar:jar goal is still invoked. Paolo. Il giorno 06/mar/08, alle ore 16:42, Ian Hummel ha scritto: Does that mean you will have to manually bind all the other goals to their respective phases? On Mar 6, 2008, at 7:37 AM, Stephen Connolly wrote: don't use packagingjar/packaging and that will disable the jar:jar On Thu, Mar 6, 2008 at 12:10 PM, Paolo Casarini [EMAIL PROTECTED] wrote: Hi, does anybody can tell me how can I replace the standard jar:jar, in the package phase, with my :jar goal implemented by my Mojo? or is there a way to disable the execution of the standard jar:jar goal? --- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Installing multiple files in the local repository using mvn install?
Hi, Is there a way to install multiple jars in the local repository using the mvn install:install-file command? Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deploying build into snapshot repository is not working
Hi, it probably helps if you post the pom ste On Thu, Mar 6, 2008 at 7:38 AM, Arun Kathirvel Sarojam [EMAIL PROTECTED] wrote: Hi, I am using maven and continuum, when i get a successful build, the package or war is not getting copied to the snapshot repository. In pom.xml i have defined the snapshotrepository under distributionmanagement tag. but the snapshots are not getting copied into that folder. i hope the copying will happen when i call mvn deploy. when i do mvn deploy:deploy i am getting the following error. altDeploymentReopsitory =null Build Error The packaging for this project did not assign a file to build artifact please advice. Thanks ARN. DISCLAIMER: The information in this e-mail and any attachment is intended only for the person to whom it is addressed and may contain confidential and/or privileged material. If you have received this e-mail in error, kindly contact the sender and destroy all copies of the original communication. IBS makes no warranty, express or implied, nor guarantees the accuracy, adequacy or completeness of the information contained in this email or any attachment and is not liable for any errors, defects, omissions, viruses or for resultant loss or damage, if any, direct or indirect. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stefano Fornari - Funambol CTO === Home: http://www.funambol.org Documents: http://www.funambol.org/documentation/documents.html FAQ: http://www.funambol.org/support/faq.html WIKI: https://wiki.objectweb.org/sync4j/ Mailinglist archives: http://groups.yahoo.com/group/Sync4j (login required) http://sourceforge.net/mailarchive/forum.php?forum_id=215 (sync4j-users) http://sourceforge.net/mailarchive/forum.php?forum_id=48877 (funambol-dev) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: override a goal within a phase
jar is the default value, so simply deleting the element is insufficient. You must actually change the value to something else, like pom. Robert Egan Paolo Casarini [EMAIL PROTECTED] wrote on 03/06/2008 10:54:15 AM: I don't know... erasing packagingjar/packaging don't change any behaviour. The jar:jar goal is still invoked. Paolo. Il giorno 06/mar/08, alle ore 16:42, Ian Hummel ha scritto: Does that mean you will have to manually bind all the other goals to their respective phases? On Mar 6, 2008, at 7:37 AM, Stephen Connolly wrote: don't use packagingjar/packaging and that will disable the jar:jar On Thu, Mar 6, 2008 at 12:10 PM, Paolo Casarini [EMAIL PROTECTED] wrote: Hi, does anybody can tell me how can I replace the standard jar:jar, in the package phase, with my :jar goal implemented by my Mojo? or is there a way to disable the execution of the standard jar:jar goal? --- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally.
Re: override a goal within a phase
You probably want to implement your own packaging type and have that packaging type apply the bindings you are after On Thu, Mar 6, 2008 at 4:14 PM, Martin Gainty [EMAIL PROTECTED] wrote: Hi Stephen I had a similar situation present itself where I was building a mar (essentially same as jar with a module.xml configurator) so where the pom was specifying using packagingmar/packaging i simply changed the pom to use jar packaging e.g. packagingjar/packaging and this disables jar goals? This appears to be non-intuitive .. is there a readme which says to execute a goal specify the opposite on the packaging element? Any way to override packaging on command line? Is there any documentation on this? Thanks/ M- - Original Message - From: [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Thursday, March 06, 2008 11:05 AM Subject: Re: override a goal within a phase jar is the default value, so simply deleting the element is insufficient. You must actually change the value to something else, like pom. Robert Egan Paolo Casarini [EMAIL PROTECTED] wrote on 03/06/2008 10:54:15 AM: I don't know... erasing packagingjar/packaging don't change any behaviour. The jar:jar goal is still invoked. Paolo. Il giorno 06/mar/08, alle ore 16:42, Ian Hummel ha scritto: Does that mean you will have to manually bind all the other goals to their respective phases? On Mar 6, 2008, at 7:37 AM, Stephen Connolly wrote: don't use packagingjar/packaging and that will disable the jar:jar On Thu, Mar 6, 2008 at 12:10 PM, Paolo Casarini [EMAIL PROTECTED] wrote: Hi, does anybody can tell me how can I replace the standard jar:jar, in the package phase, with my :jar goal implemented by my Mojo? or is there a way to disable the execution of the standard jar:jar goal? --- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wiping out a dependency from an internal repository
On 3/6/08, Wendy Smoak [EMAIL PROTECTED] wrote: Maven Dependency Plugin - purge-local-repository maybe? http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html That's it! Thanks Wendy. ;-) Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: override a goal within a phase
this is a good solution in my case. Do you know where i can find some documentation to implement my own packaging type and how integrate it with standard maven stuff. Paolo. Il giorno 06/mar/08, alle ore 17:39, Stephen Connolly ha scritto: You probably want to implement your own packaging type and have that packaging type apply the bindings you are after On Thu, Mar 6, 2008 at 4:14 PM, Martin Gainty [EMAIL PROTECTED] wrote: Hi Stephen I had a similar situation present itself where I was building a mar (essentially same as jar with a module.xml configurator) so where the pom was specifying using packagingmar/packaging i simply changed the pom to use jar packaging e.g. packagingjar/packaging and this disables jar goals? This appears to be non-intuitive .. is there a readme which says to execute a goal specify the opposite on the packaging element? Any way to override packaging on command line? Is there any documentation on this? Thanks/ M- - Original Message - From: [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Thursday, March 06, 2008 11:05 AM Subject: Re: override a goal within a phase jar is the default value, so simply deleting the element is insufficient. You must actually change the value to something else, like pom. Robert Egan Paolo Casarini [EMAIL PROTECTED] wrote on 03/06/2008 10:54:15 AM: I don't know... erasing packagingjar/packaging don't change any behaviour. The jar:jar goal is still invoked. Paolo. Il giorno 06/mar/08, alle ore 16:42, Ian Hummel ha scritto: Does that mean you will have to manually bind all the other goals to their respective phases? On Mar 6, 2008, at 7:37 AM, Stephen Connolly wrote: don't use packagingjar/packaging and that will disable the jar:jar On Thu, Mar 6, 2008 at 12:10 PM, Paolo Casarini [EMAIL PROTECTED] wrote: Hi, does anybody can tell me how can I replace the standard jar:jar, in the package phase, with my :jar goal implemented by my Mojo? or is there a way to disable the execution of the standard jar:jar goal? --- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- GPG key: 1024D/9C5AE886 2004-10-21 Paolo Casarini [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: obtaining project dependencies in maven 1.1??
Very few people are using Maven1 lately, and your question is hard to understand, so I really doubt you'll get a response. Move to Maven2 or restate your question in such a way that someone will care enough to reply to it. Wayne On 3/5/08, san84 [EMAIL PROTECTED] wrote: suppose i hav two projects in maven 1.0 say MODULE-1 n MODULE-2 under a main project say MAIN-MODULE each of these subprojects(MODULE 1 MODULE 2) hav its own src directory structure . The MODULE-2 has to wait for MODULE-1 goals to be completed first. if i go and build MODULE-2 project without building MODULE-1 it has to complete MODULE-1 goals first. like the way we do for goals with prereqs element how to achieve this plz help me .. -- View this message in context: http://www.nabble.com/obtaining-project-dependencies-in-maven-1.1---tp15866756s177p15866756.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Extending maven to accomplish some tasks
On 3/6/08, VUB Stefan Seidel [EMAIL PROTECTED] wrote: Tomasz Pik wrote: On 3/6/08, VUB Stefan Seidel [EMAIL PROTECTED] wrote: phaseinstall/phase Is there a way to setup it so maven will 'copy' artifact in 'package' phase, without installing artifact to local repo? phasepackage/phase? Maybe even phaseverify/phase. Then run mvn package. nop :( If this is being bind to 'package', then maven: 1. builds and package project into 'target/...' 2. use dependency mechanism to locate artifact defined in configuration for plugin through repositories (both local and remote) and copy one from repository, not the new one. Should I report it as a feature request? Regards, Tomek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wiping out a dependency from an internal repository
On Thu, Mar 6, 2008 at 9:08 AM, Wayne Fay [EMAIL PROTECTED] wrote: I know I've seen someone mention a plugin here that can either wipe out your entire repo or selected parts of it. But I can't recall what its called right now, and a quick Google search didn't reveal anything (but I didn't dig much). So if someone else remembers, perhaps they'll post a follow-up. Maven Dependency Plugin - purge-local-repository maybe? http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Installing multiple files in the local repository using mvn install?
I've heard rumours about something called shell scripts or batch files. According to the speculation that I've seen about these things, they would provide the ability you are looking for Unfortunately they are not XML files, so you have to learn a whole new syntax. Some of them start with #!/bin/bash while others start with @echo off and then they have a sort of stream of conciousness list of commands On Thu, Mar 6, 2008 at 4:22 PM, Krishnamurthi, Venkat [EMAIL PROTECTED] wrote: Hi, Is there a way to install multiple jars in the local repository using the mvn install:install-file command? Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Adding additional information using MVN eclipse:eclipse
I need to add additional information into my project files that eclipse:eclipse generates. Is this possible to do using the eclipse plugin for maven? Thanks, Jeff -- View this message in context: http://www.nabble.com/Adding-additional-information-using-MVN-eclipse%3Aeclipse-tp15878724s177p15878724.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: override a goal within a phase
I found this information useful http://www.sonatype.com/book/lifecycle.html#plugins_and_the_lifecyle On Mar 6, 2008, at 11:47 AM, Paolo Casarini wrote: this is a good solution in my case. Do you know where i can find some documentation to implement my own packaging type and how integrate it with standard maven stuff. Paolo. Il giorno 06/mar/08, alle ore 17:39, Stephen Connolly ha scritto: You probably want to implement your own packaging type and have that packaging type apply the bindings you are after On Thu, Mar 6, 2008 at 4:14 PM, Martin Gainty [EMAIL PROTECTED] wrote: Hi Stephen I had a similar situation present itself where I was building a mar (essentially same as jar with a module.xml configurator) so where the pom was specifying using packagingmar/packaging i simply changed the pom to use jar packaging e.g. packagingjar/packaging and this disables jar goals? This appears to be non-intuitive .. is there a readme which says to execute a goal specify the opposite on the packaging element? Any way to override packaging on command line? Is there any documentation on this? Thanks/ M- - Original Message - From: [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Sent: Thursday, March 06, 2008 11:05 AM Subject: Re: override a goal within a phase jar is the default value, so simply deleting the element is insufficient. You must actually change the value to something else, like pom. Robert Egan Paolo Casarini [EMAIL PROTECTED] wrote on 03/06/2008 10:54:15 AM: I don't know... erasing packagingjar/packaging don't change any behaviour. The jar:jar goal is still invoked. Paolo. Il giorno 06/mar/08, alle ore 16:42, Ian Hummel ha scritto: Does that mean you will have to manually bind all the other goals to their respective phases? On Mar 6, 2008, at 7:37 AM, Stephen Connolly wrote: don't use packagingjar/packaging and that will disable the jar:jar On Thu, Mar 6, 2008 at 12:10 PM, Paolo Casarini [EMAIL PROTECTED] wrote: Hi, does anybody can tell me how can I replace the standard jar:jar, in the package phase, with my :jar goal implemented by my Mojo? or is there a way to disable the execution of the standard jar:jar goal? --- This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- GPG key: 1024D/9C5AE886 2004-10-21 Paolo Casarini [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: Installing multiple files in the local repository using mvn install?
The general principle behinh Maven is one project = one file produced. However, there are some rares cases that go beyond this point : in that case, you can use the Maven build helper plugin to attach new artifacts to the main artifact and both will be installed: see http://mojo.codehaus.org/build-helper-maven-plugin Jeff MAURY On Thu, Mar 6, 2008 at 5:41 PM, Stephen Connolly [EMAIL PROTECTED] wrote: I've heard rumours about something called shell scripts or batch files. According to the speculation that I've seen about these things, they would provide the ability you are looking for Unfortunately they are not XML files, so you have to learn a whole new syntax. Some of them start with #!/bin/bash while others start with @echo off and then they have a sort of stream of conciousness list of commands On Thu, Mar 6, 2008 at 4:22 PM, Krishnamurthi, Venkat [EMAIL PROTECTED] wrote: Hi, Is there a way to install multiple jars in the local repository using the mvn install:install-file command? Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com
Re: Extending maven to accomplish some tasks
Tomasz Pik wrote: On 3/6/08, VUB Stefan Seidel [EMAIL PROTECTED] wrote: Tomasz Pik wrote: On 3/6/08, VUB Stefan Seidel [EMAIL PROTECTED] wrote: phaseinstall/phase Is there a way to setup it so maven will 'copy' artifact in 'package' phase, without installing artifact to local repo? phasepackage/phase? Maybe even phaseverify/phase. Then run mvn package. nop :( If this is being bind to 'package', then maven: 1. builds and package project into 'target/...' 2. use dependency mechanism to locate artifact defined in configuration for plugin through repositories (both local and remote) and copy one from repository, not the new one. Should I report it as a feature request? Ah. Yes, this is correct behaviour, but not very helpful. Then you can use the outputDirectory option of the jar plugin (or war plugin) in a second execution of the plugin to build the file agaijn into the directory you need. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Adding additional information using MVN eclipse:eclipse
There is a pretty comprehensive list of additional configs that you can add
as documented on maven-eclipse-plugin page:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
I would suggest that you start by adding maven-eclipse-plugin config in the
root POM. It would be carried over to all of your sub maven projects. Then
if you want to overwrite certain maven-eclipse-plugin configs for particular
maven projects, i.e. WAR or EARs may need additional eclipse facet configs,
you could simply override maven-eclipse-config for that particular pom.
Here's a sample for the maven-eclipse-plugin for root POM. Note that it's
specifically targetted for Eclipse 3.2 based environment (will also work for
RAD 6.x/RAD 7). Use eclipse:rad mojo to generate RAD WTP resources ,and
eclipse:eclipse if you are working in Eclipse 3.2.x or higher environment.
Hope this helps.
!-- maven-eclipse-plugin config for generating WTP 1.5 settings for WAR
and EARs properly --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
configuration
manifest
${basedir}/src/main/resources/META-INF/MANIFEST.MF
/manifest
addVersionToProjectNametrue/addVersionToProjectName
useProjectReferencesfalse/useProjectReferences
wtpmanifesttrue/wtpmanifest
wtpapplicationxmltrue/wtpapplicationxml
wtpversion1.5/wtpversion
additionalBuildcommands
buildcommandcom.ibm.etools.common.migration.MigrationBuilder/buildcommand
buildcommandorg.eclipse.jdt.core.javabuilder/buildcommand
buildcommandorg.eclipse.wst.common.project.facet.core.builder/buildcommand
buildcommandorg.eclipse.wst.validation.validationbuilder/buildcommand
/additionalBuildcommands
additionalProjectnatures
projectnatureorg.eclipse.wst.common.project.facet.core.nature/projectnature
projectnatureorg.eclipse.jdt.core.javanature/projectnature
projectnatureorg.eclipse.wst.common.modulecore.ModuleCoreNature/projectnature
projectnatureorg.eclipse.jem.workbench.JavaEMFNature/projectnature
/additionalProjectnatures
classpathContainers
classpathContainerorg.eclipse.jst.j2ee.internal.module.container/classpathContainer
/classpathContainers
/configuration
/plugin
!-- maven-eclipse-plugin --
--
Salman Moghal
- Original Message -
From: jeffpuro [EMAIL PROTECTED]
To: users@maven.apache.org
Sent: Thursday, March 06, 2008 12:10 PM
Subject: Adding additional information using MVN eclipse:eclipse
I need to add additional information into my project files that
eclipse:eclipse generates. Is this possible to do using the eclipse
plugin for maven?
Thanks,
Jeff
--
View this message in context:
http://www.nabble.com/Adding-additional-information-using-MVN-eclipse%3Aeclipse-tp15878724s177p15878724.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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: MVN: release plugin
Nicole--I tried that but I still throw the build error.
Anthony
Quoting Nicole Lacoste [EMAIL PROTECTED]:
Hi,
Try deleting the release.properties file.
Nicole
On 06/03/2008, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I've been working with the release plugin for the first time and
encountering build failures that I've gradually been able to resolve to
the point where I'm prompted for the desired release version, next
development version, etc. (in this initial test dry run I called it
2.5.0.a). My second to last failure involved a custom property
variable ${sakai.version} used in certain Sakai dependency declarations
that the release plugin was unable to update . I believe we have
resolved this version issue by updating ${sakai.version} to SNAPSHOT.
However, when I issue the following release command
mvn -e release:clean release:prepare -DdryRun=true
I encounter another build failure due to a non-existent
base-2.5.0.a.pom that Maven is attempting to locate. None of my poms
in the multi-project build reference 2.5.0.a nor is there a
release.properties file. The poms version are all SNAPSHOT.
How do I get the release plugin to stop trying to locate
base-2.5.0.a.pom and instead commence the release process anew?
Any suggestions would be appreciated,
Cheers,
Anthony Whyte
University of Michigan
arwhyte$ mvn -e release:clean release:prepare -DdryRun=true
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
Downloading:
http://repo1.maven.org/maven2/org/sakaiproject/base/2.5.0.a/base-2.5.0.a.pom
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: org.sakaiproject
ArtifactId: base
Version: 2.5.0.a
Reason: Unable to download the artifact from any repository
org.sakaiproject:base:pom:2.5.0.a
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
org.sakaiproject:base for project:
org.sakaiproject:component-base:pom:null for project
org.sakaiproject:component-base:pom:null
. . . .
-
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: adding subversion revision to manifest
Hi -
Is this available as a Maven2 plugin?
Thanks,
Rk
x77309
-Original Message-
From: Torsten Curdt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 11, 2005 3:22 AM
To: Maven Users List
Subject: adding subversion revision to manifest
I've come up with a simple maven plugin that adds the subversion
revision to the manifest. So with
public static Map getJarRevisions() throws IOException {
final String[] jars = System.getProperty
(java.class.path).split(
System.getProperty(path.separator));
final Map revisions = new HashMap(jars.length);
for (int i = 0; i jars.length; i++) {
final JarFile jar = new JarFile(jars[i]);
final Manifest manifest = jar.getManifest();
final String revision = (String)
manifest.getMainAttributes().getValue(Revision);
revisions.put(jars[i], revision);
}
return revisions;
}
You know *exactly* what jars are in your path.
Only add it to your maven.xml like this:
postGoal name=jar:jar
attainGoal name=revision:add/
/postGoal
It is currently available at:
http://people.apache.org/~tcurdt/maven-revision-plugin.tgz
It's for maven1 but just wraps a simple class so a version for maven2
should be pretty straight forward.
If people think this is useful I am sure we can improve it and put it
somewhere properly.
cheers
--
Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Adding additional information using MVN eclipse:eclipse
Thanks for the quick response. Specifically, is there a way to add in
project references using additional configuration? I do not see a way to do
this.
Thanks,
Jeff
Salman Moghal wrote:
There is a pretty comprehensive list of additional configs that you can
add
as documented on maven-eclipse-plugin page:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
I would suggest that you start by adding maven-eclipse-plugin config in
the
root POM. It would be carried over to all of your sub maven projects.
Then
if you want to overwrite certain maven-eclipse-plugin configs for
particular
maven projects, i.e. WAR or EARs may need additional eclipse facet
configs,
you could simply override maven-eclipse-config for that particular pom.
Here's a sample for the maven-eclipse-plugin for root POM. Note that it's
specifically targetted for Eclipse 3.2 based environment (will also work
for
RAD 6.x/RAD 7). Use eclipse:rad mojo to generate RAD WTP resources ,and
eclipse:eclipse if you are working in Eclipse 3.2.x or higher
environment.
Hope this helps.
!-- maven-eclipse-plugin config for generating WTP 1.5 settings for
WAR
and EARs properly --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
configuration
manifest
${basedir}/src/main/resources/META-INF/MANIFEST.MF
/manifest
addVersionToProjectNametrue/addVersionToProjectName
useProjectReferencesfalse/useProjectReferences
wtpmanifesttrue/wtpmanifest
wtpapplicationxmltrue/wtpapplicationxml
wtpversion1.5/wtpversion
additionalBuildcommands
buildcommandcom.ibm.etools.common.migration.MigrationBuilder/buildcommand
buildcommandorg.eclipse.jdt.core.javabuilder/buildcommand
buildcommandorg.eclipse.wst.common.project.facet.core.builder/buildcommand
buildcommandorg.eclipse.wst.validation.validationbuilder/buildcommand
/additionalBuildcommands
additionalProjectnatures
projectnatureorg.eclipse.wst.common.project.facet.core.nature/projectnature
projectnatureorg.eclipse.jdt.core.javanature/projectnature
projectnatureorg.eclipse.wst.common.modulecore.ModuleCoreNature/projectnature
projectnatureorg.eclipse.jem.workbench.JavaEMFNature/projectnature
/additionalProjectnatures
classpathContainers
classpathContainerorg.eclipse.jst.j2ee.internal.module.container/classpathContainer
/classpathContainers
/configuration
/plugin
!-- maven-eclipse-plugin --
--
Salman Moghal
- Original Message -
From: jeffpuro [EMAIL PROTECTED]
To: users@maven.apache.org
Sent: Thursday, March 06, 2008 12:10 PM
Subject: Adding additional information using MVN eclipse:eclipse
I need to add additional information into my project files that
eclipse:eclipse generates. Is this possible to do using the eclipse
plugin for maven?
Thanks,
Jeff
--
View this message in context:
http://www.nabble.com/Adding-additional-information-using-MVN-eclipse%3Aeclipse-tp15878724s177p15878724.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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Adding-additional-information-using-MVN-eclipse%3Aeclipse-tp15878724s177p15880947.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]
Wessphere plugin
Hi All I know some time there was a plugin for Websphere5.1 did exist at maven, mojo,repository, but i couldn't find it now, any one knows where i can find it?
Re: Adding additional information using MVN eclipse:eclipse
If I'm not mistaken, in Eclipse, you are trying to build the Java Build
Path by referencing additional projects under the Projects tab for a
given Java Project? If that's what you are trying to do.. then yes, the
dependancy can be established by listing additional projects under the
projects/projects XML block of .project file.
Given MyProject1 and MyProject2, and MyProject1 depends on MyProject2,
.project file may look like below:
?xml version=1.0 encoding=UTF-8?
projectDescription
nameMyProject1/name
projectsMyProject2/projects
/projectDescription
Unfortunately, I don't know if there is a way to do add project references
using maven-eclipse-plugin.
However, the correct way, IMHO, would be to use a classpath entry to
establish inter-project dependancies. WTP resource .classpath defines these
daependencies, e.g. for MyProject1, .classpath will look something like
this:
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry combineaccessrules=false kind=src path=/MyProject2/
/classpath
If you have properly constructed the Maven project dependancies in pom.xml,
maven-eclipse-plugin will generate the correct depedancy in .classpath file
for you. So given MyProject1 and MyProject2 and corresponding POM files
below, .classpath for MyProject1 should contain a dependancy reference for
MyProject2:
MyProject1 pom.xml:
project
modelVersion4.0.0/modelVersion
groupIdorg.mytest/groupId
artifactIdMyProject1/artifactId
version1.0/version
packagingjar/packaging
build
plugins
plugin
!-- Configure Maven JAR plugin --
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifestEntries/manifestEntries
/archive
/configuration
/plugin
/plugins
/build
/project
MyProject2 pom.xml:
project
modelVersion4.0.0/modelVersion
groupIdorg.mytest/groupId
artifactIdMyProject2/artifactId
version1.0/version
packagingjar/packaging
dependencies
dependency
groupIdorg.mytest/groupId
artifactIdMyProject1/artifactId
version1.0version
/dependency
/dependencies
build
plugins
plugin
!-- Configure Maven JAR plugin --
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifestEntries/manifestEntries
/archive
/configuration
/plugin
/plugins
/build
/project
--
Salman Moghal
- Original Message -
From: jeffpuro [EMAIL PROTECTED]
To: users@maven.apache.org
Sent: Thursday, March 06, 2008 1:38 PM
Subject: Re: Adding additional information using MVN eclipse:eclipse
Thanks for the quick response. Specifically, is there a way to add in
project references using additional configuration? I do not see a way to
do
this.
Thanks,
Jeff
Salman Moghal wrote:
There is a pretty comprehensive list of additional configs that you can
add
as documented on maven-eclipse-plugin page:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
I would suggest that you start by adding maven-eclipse-plugin config in
the
root POM. It would be carried over to all of your sub maven projects.
Then
if you want to overwrite certain maven-eclipse-plugin configs for
particular
maven projects, i.e. WAR or EARs may need additional eclipse facet
configs,
you could simply override maven-eclipse-config for that particular pom.
Here's a sample for the maven-eclipse-plugin for root POM. Note that
it's
specifically targetted for Eclipse 3.2 based environment (will also work
for
RAD 6.x/RAD 7). Use eclipse:rad mojo to generate RAD WTP resources
,and
eclipse:eclipse if you are working in Eclipse 3.2.x or higher
environment.
Hope this helps.
!-- maven-eclipse-plugin config for generating WTP 1.5 settings for
WAR
and EARs properly --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
configuration
manifest
${basedir}/src/main/resources/META-INF/MANIFEST.MF
/manifest
addVersionToProjectNametrue/addVersionToProjectName
useProjectReferencesfalse/useProjectReferences
wtpmanifesttrue/wtpmanifest
wtpapplicationxmltrue/wtpapplicationxml
wtpversion1.5/wtpversion
additionalBuildcommands
buildcommandcom.ibm.etools.common.migration.MigrationBuilder/buildcommand
buildcommandorg.eclipse.jdt.core.javabuilder/buildcommand
buildcommandorg.eclipse.wst.common.project.facet.core.builder/buildcommand
buildcommandorg.eclipse.wst.validation.validationbuilder/buildcommand
/additionalBuildcommands
additionalProjectnatures
projectnatureorg.eclipse.wst.common.project.facet.core.nature/projectnature
projectnatureorg.eclipse.jdt.core.javanature/projectnature
projectnatureorg.eclipse.wst.common.modulecore.ModuleCoreNature/projectnature
projectnatureorg.eclipse.jem.workbench.JavaEMFNature/projectnature
/additionalProjectnatures
classpathContainers
RE: MavenProject.getDependencyArtifacts() returns null
You need to declare @requiresDependencyResolution scope in your mojo annotation. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2008 7:45 AM To: users@maven.apache.org Subject: MavenProject.getDependencyArtifacts() returns null Hi. When running my plugin from a phase like 'package' (by using the execution tag) then project.getDependencyArtifacts() returns the dependencies artifacts. But when I run the plugin standalone, that is in the format 'mvn groupID:myplugin:version:goal' it returns null. How can I overcome this. Have I got to initialize something? Thanks for any answer ... , Daniel ' - 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: Try to run install before eclipse:eclipse
This seems related to MNG-2277, which was fixed in 2.0.8. Are you seeing this on 2.0.8 or earlier? -Original Message- From: Martin Höller [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2008 5:41 AM To: Maven Users List Subject: Re: Try to run install before eclipse:eclipse On Thursday 06 March 2008 [EMAIL PROTECTED] wrote: Making install run before eclipse:eclipse is a bad idea in some cases. We would need it only in multi-module projects if some artifacts cannot be found in the repository. In particular, when a project doesn't compile it is currently possible to still run eclipse:eclipse. Making install a pre-requisite would block that, which would be really anoying. Good point! A new developer should not only be able to join the team if the project compiles right now. I think what the original poster is saying is that eclipse:eclipse is correctly generating all of the eclipse projects, but that eclipse then displays build errors because the jars that the newly created eclipse projects point to don't yet exist. No, mvn eclipse:eclipse fails in a multi-module project, if the artifacts are not in a (local or remote) repository, even if they could have been built. See also this thread for some more details: http://www.nabble.com/maven-eclipse-plugin-with-multi-module-projects-to15222495s177.html hth, - martin -- Martin Höller | [EMAIL PROTECTED] *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven2 emma Plugin Docs
Hi: Has anyone started using the recently added emma plugin for maven2? The plugin goals aren't well described yet. The Plugin Goals page is empty. The groupId and artifactId in an example on the How to Use page looks like it may be referring to maven1 plugin. [See http://mojo.codehaus.org/emma-maven-plugin/index.html.] I was hoping to avoid having to grok the mojo source. Thanks. Brad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Wessphere plugin
It's in the mojo sandbox (look for was) -Original Message- From: I am Who i am [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2008 1:58 PM To: Maven Users List Subject: Wessphere plugin Hi All I know some time there was a plugin for Websphere5.1 did exist at maven, mojo,repository, but i couldn't find it now, any one knows where i can find it? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Adding additional information using MVN eclipse:eclipse
Yes, the problem with using the classpath method is some tools (specifically
jrules) has its own plugin editor using eclipse and it uses the
project/project reference tags to define its own project dependencies.
i'm not sure if i remove these, and add in a classpath entry to a jar,
whether it will be able to locate the resources it needs...
Thanks,
-Jeff
Salman Moghal wrote:
If I'm not mistaken, in Eclipse, you are trying to build the Java Build
Path by referencing additional projects under the Projects tab for a
given Java Project? If that's what you are trying to do.. then yes, the
dependancy can be established by listing additional projects under the
projects/projects XML block of .project file.
Given MyProject1 and MyProject2, and MyProject1 depends on MyProject2,
.project file may look like below:
?xml version=1.0 encoding=UTF-8?
projectDescription
nameMyProject1/name
projectsMyProject2/projects
/projectDescription
Unfortunately, I don't know if there is a way to do add project
references
using maven-eclipse-plugin.
However, the correct way, IMHO, would be to use a classpath entry to
establish inter-project dependancies. WTP resource .classpath defines
these
daependencies, e.g. for MyProject1, .classpath will look something like
this:
?xml version=1.0 encoding=UTF-8?
classpath
classpathentry combineaccessrules=false kind=src
path=/MyProject2/
/classpath
If you have properly constructed the Maven project dependancies in
pom.xml,
maven-eclipse-plugin will generate the correct depedancy in .classpath
file
for you. So given MyProject1 and MyProject2 and corresponding POM files
below, .classpath for MyProject1 should contain a dependancy reference for
MyProject2:
MyProject1 pom.xml:
project
modelVersion4.0.0/modelVersion
groupIdorg.mytest/groupId
artifactIdMyProject1/artifactId
version1.0/version
packagingjar/packaging
build
plugins
plugin
!-- Configure Maven JAR plugin --
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifestEntries/manifestEntries
/archive
/configuration
/plugin
/plugins
/build
/project
MyProject2 pom.xml:
project
modelVersion4.0.0/modelVersion
groupIdorg.mytest/groupId
artifactIdMyProject2/artifactId
version1.0/version
packagingjar/packaging
dependencies
dependency
groupIdorg.mytest/groupId
artifactIdMyProject1/artifactId
version1.0version
/dependency
/dependencies
build
plugins
plugin
!-- Configure Maven JAR plugin --
artifactIdmaven-jar-plugin/artifactId
configuration
archive
manifestEntries/manifestEntries
/archive
/configuration
/plugin
/plugins
/build
/project
--
Salman Moghal
- Original Message -
From: jeffpuro [EMAIL PROTECTED]
To: users@maven.apache.org
Sent: Thursday, March 06, 2008 1:38 PM
Subject: Re: Adding additional information using MVN eclipse:eclipse
Thanks for the quick response. Specifically, is there a way to add in
project references using additional configuration? I do not see a way to
do
this.
Thanks,
Jeff
Salman Moghal wrote:
There is a pretty comprehensive list of additional configs that you can
add
as documented on maven-eclipse-plugin page:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
I would suggest that you start by adding maven-eclipse-plugin config in
the
root POM. It would be carried over to all of your sub maven projects.
Then
if you want to overwrite certain maven-eclipse-plugin configs for
particular
maven projects, i.e. WAR or EARs may need additional eclipse facet
configs,
you could simply override maven-eclipse-config for that particular pom.
Here's a sample for the maven-eclipse-plugin for root POM. Note that
it's
specifically targetted for Eclipse 3.2 based environment (will also work
for
RAD 6.x/RAD 7). Use eclipse:rad mojo to generate RAD WTP resources
,and
eclipse:eclipse if you are working in Eclipse 3.2.x or higher
environment.
Hope this helps.
!-- maven-eclipse-plugin config for generating WTP 1.5 settings for
WAR
and EARs properly --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
configuration
manifest
${basedir}/src/main/resources/META-INF/MANIFEST.MF
/manifest
addVersionToProjectNametrue/addVersionToProjectName
useProjectReferencesfalse/useProjectReferences
wtpmanifesttrue/wtpmanifest
wtpapplicationxmltrue/wtpapplicationxml
wtpversion1.5/wtpversion
additionalBuildcommands
buildcommandcom.ibm.etools.common.migration.MigrationBuilder/buildcommand
buildcommandorg.eclipse.jdt.core.javabuilder/buildcommand
Archetypes and plugins
I am working on an Archetype and would like to run a plugin to perform tasks during the create process. Initially this is the eclipse plugin to make an eclipse project but I also need to do some other processing using an as yet unwritten plugin. Is this possible? Any alternatives? Ian
How to generate an Eclipse jar file from Maven?
I'm using the following:
Maven version: 2.0.7
Java version: 1.6.0_02-ea
OS name: windows xp version: 5.1 arch: x86
Eclipse SDK
Version: 3.3.1.1
Build id: M20071023-1652
I'm building an Eclipse feature, using a pom.xml file where I use the
following code:
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdpde-maven-plugin/artifactId
extensionstrue/extensions
configuration
eclipseInstall${eclipse.home}/eclipseInstall
buildProperties
javacSource1.5/javacSource
javacTarget1.5/javacTarget
/buildProperties
/configuration
/plugin
/plugins
/build
The generated output of the above code is .zip file, but I need to build
a .jar file instead, so is there a way where I can use Maven to do that?
Also, is there is a way where Maven can build the needed Eclipse feature
jar file where the file name would indicate the version and build number
or date for example: org.eclipse.gef_3.3.1.v20070814
Does anyone know how or where I can find this information?
I'd like to use the following the code or something similar if possible:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
finalName${project.artifactId}-${project.version}-r${buildNumber}/fin
alName
My main goal is to be able to build an Eclipse feature jar file, copy
this jar to the update folder on a specified server, so users can update
their local systems with the newer version.
Thanks,
Sameh
This email and any files transmitted with it are confidential, proprietary
and intended solely for the individual or entity to whom they are addressed.
If you have received this email in error please delete it immediately.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Install an xml file
This may be an off the wall question, but I need to copy an xml file after an install. I tried the maven dependency plugin, but it appeared to want the file installed as a dependency. So I tried to install it using: mvn install:install-file -Dfile=c:/test/foo-bar.xml -DgroupId=catalina.context -DartifactId=foo-bar -Dgenerate-pom=true -DlocalRepositoryId=local But that throws and error: Missing group, artifact, version, or packaging information The documentation on install does not show an example of installing a non-jar type file. Can text files be installed into a repository? Is there a better way to accomplish this? If you are curious as to why I want to do this, I am using GWT and in non-server mode tomcat will whack the context file when maven does a clean on my project. So I want to copy this file back to tomcat after each build. -- View this message in context: http://www.nabble.com/Install-an-xml-file-tp15885404s177p15885404.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]
Validating version selections
Is there a standalone type plugin one can use to verify that multiple projects are using the same set of dependencies? I'd love to use something like dependency-analyze, but I want to compare two different deployable units (rather than having each deployable unit validate it's own set of dependencies).
Re: Install an xml file
The error message is accurate. You are missing required fields. Add -Dversion=1.0 and -Dpackaging=xml to the install line. Also, I'm pretty sure you want -DgeneratePom. Wayne On 3/6/08, buzzterrier [EMAIL PROTECTED] wrote: This may be an off the wall question, but I need to copy an xml file after an install. I tried the maven dependency plugin, but it appeared to want the file installed as a dependency. So I tried to install it using: mvn install:install-file -Dfile=c:/test/foo-bar.xml -DgroupId=catalina.context -DartifactId=foo-bar -Dgenerate-pom=true -DlocalRepositoryId=local But that throws and error: Missing group, artifact, version, or packaging information The documentation on install does not show an example of installing a non-jar type file. Can text files be installed into a repository? Is there a better way to accomplish this? If you are curious as to why I want to do this, I am using GWT and in non-server mode tomcat will whack the context file when maven does a clean on my project. So I want to copy this file back to tomcat after each build. -- View this message in context: http://www.nabble.com/Install-an-xml-file-tp15885404s177p15885404.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven Assembly for MultiModule project
Hi, I am a Maven newbie and I hope this is not a stupid question. I am trying to create two Maven assembly jars for modules Foo and Bar. My project -- | |--- Bar |--- Foo |Foo-A |--- Foo-B This is my project structure. In this project, FOO-A is dependent on Foo-B and Bar ,Foo are dependent upon FOO-A. I am trying to build assembly jars for both the for both Foo and Bar modules. Can you please help me? My project pom is as follows. modules moduleBar/module moduleFoo/module moduleFoo-A/module moduleFoo-B/module /modules dependencies dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.13/version scopecompile/scope /dependency .. /dependencies build plugins plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptors descriptorassembly.xml/descriptor /descriptors tarLongFileModegnu/tarLongFileMode /configuration /plugin /build pluginRepositories pluginRepository idapache.snapshots/id urlhttp://people.apache.org/repo/m2-snapshot-repository//url /pluginRepository /pluginRepositories My assembly.xml assembly idjar-with-dependencies/id formats formatjar/format /formats includeBaseDirectoryfalse/includeBaseDirectory fileSets fileSet directorytarget/classes/directory outputDirectory//outputDirectory /fileSet /fileSets dependencySets dependencySet outputDirectory//outputDirectory unpackfalse/unpack scoperuntime/scope /dependencySet /dependencySets /assembly -- View this message in context: http://www.nabble.com/Maven-Assembly-for-MultiModule-project-tp15885942s177p15885942.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: Maven Assembly for MultiModule project
This list really works better if you post what you've done and then tell us why its not working the way you wanted, or an error message you got, etc. Looking at what you sent, I have no idea if it is working how you expect or not. Sending your pom and assembly.xml file is probably not going to give you the results you are hoping for. So, send a reply and be more clear about what you've got vs what you want etc. Wayne On 3/6/08, krishnan.1000 [EMAIL PROTECTED] wrote: Hi, I am a Maven newbie and I hope this is not a stupid question. I am trying to create two Maven assembly jars for modules Foo and Bar. My project -- | |--- Bar |--- Foo |Foo-A |--- Foo-B This is my project structure. In this project, FOO-A is dependent on Foo-B and Bar ,Foo are dependent upon FOO-A. I am trying to build assembly jars for both the for both Foo and Bar modules. Can you please help me? My project pom is as follows. modules moduleBar/module moduleFoo/module moduleFoo-A/module moduleFoo-B/module /modules dependencies dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.13/version scopecompile/scope /dependency .. /dependencies build plugins plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptors descriptorassembly.xml/descriptor /descriptors tarLongFileModegnu/tarLongFileMode /configuration /plugin /build pluginRepositories pluginRepository idapache.snapshots/id urlhttp://people.apache.org/repo/m2-snapshot-repository//url /pluginRepository /pluginRepositories My assembly.xml assembly idjar-with-dependencies/id formats formatjar/format /formats includeBaseDirectoryfalse/includeBaseDirectory fileSets fileSet directorytarget/classes/directory outputDirectory//outputDirectory /fileSet /fileSets dependencySets dependencySet outputDirectory//outputDirectory unpackfalse/unpack scoperuntime/scope /dependencySet /dependencySets /assembly -- View this message in context: http://www.nabble.com/Maven-Assembly-for-MultiModule-project-tp15885942s177p15885942.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Validating version selections
Better question - is there a good example of how to iterate over dependencies? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2008 6:58 PM To: users@maven.apache.org Subject: Validating version selections Is there a standalone type plugin one can use to verify that multiple projects are using the same set of dependencies? I'd love to use something like dependency-analyze, but I want to compare two different deployable units (rather than having each deployable unit validate it's own set of dependencies). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Validating version selections
Perhaps a pom depending on those other projects? Then you could run the dependency plugin against it. On 3/6/08, EJ Ciramella [EMAIL PROTECTED] wrote: Is there a standalone type plugin one can use to verify that multiple projects are using the same set of dependencies? I'd love to use something like dependency-analyze, but I want to compare two different deployable units (rather than having each deployable unit validate it's own set of dependencies). -- ASCII ribbon campaign: () against HTML email /\ against Microsoft attachments Information: http://www.expita.com/nomime.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Validating version selections
That's what I tried initially, but it doesn't complaine about where exactly the mis-matched versions are (as well as being bound to the verify stage). Did I miss the boat a bit here? -Original Message- From: deckrider [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2008 9:57 PM To: Maven Users List Subject: Re: Validating version selections Perhaps a pom depending on those other projects? Then you could run the dependency plugin against it. On 3/6/08, EJ Ciramella [EMAIL PROTECTED] wrote: Is there a standalone type plugin one can use to verify that multiple projects are using the same set of dependencies? I'd love to use something like dependency-analyze, but I want to compare two different deployable units (rather than having each deployable unit validate it's own set of dependencies). -- ASCII ribbon campaign: () against HTML email /\ against Microsoft attachments Information: http://www.expita.com/nomime.html - 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: specifying version of Ant to use for maven-ant-run
On Tue, Feb 26, 2008 at 5:07 PM, Marshall Schor [EMAIL PROTECTED] wrote: Dennis Lundberg wrote: ... There is an issue for this in JIRA already: http://jira.codehaus.org/browse/MANTRUN-68http://jira.codehaus.org/browse/MANTRUN-68 I see that issue is more than a year old, and is still open. Until this is fixed, is there a recommended work-around? -Marshall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Would it be possible to add a relocation to the central repo like was done for ehcache (ehcache:ehcache:1.2 - net.sf.ehcache:ehcache:1.2)? It seemed to work transparently in that case. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Build Issues with Maven
Hi, I'm building SAKAI(2.4) using Maven 1.1 . When I try to build the SAKAI, I get the following error : Unable to download Dependencies for Tomcat 5.5.23 :zip from the site http://source.sakaiproject.org/maven Unable to download Dependencies for sakai2.2:plugin from the site http://source.sakaiproject.org/maven Can anyone please help me out : -- View this message in context: http://www.nabble.com/Build-Issues-with-Maven-tp15889556s177p15889556.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]
How can I create a maven project with multiple modules?
I can use this command to create a maven project: mvn archetype:create \ -DarchetypeGroupId=org.apache.maven.archetypes \ -DgroupId=com.mycompany.app \ -DartifactId=my-app But how can I create a project which includes many modules? -- View this message in context: http://www.nabble.com/How-can-I-create-a-maven-project-with-multiple-modules--tp15890230s177p15890230.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]
archiva corrupts the snapshot repository so that deploys don't increment build number
It appears that archiva consumers modify the repository and change timestamps to GMT. The next time I try to deploy an artifact it starts over at build number 1, even though the previous build number was 30. I am not sure what I can do to resolve this either in Archvia or maven??
Re: How can I create a maven project with multiple modules?
Hi, See the example 3 here. http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Aggregation Hope this is what you need. Upul On Fri, Mar 7, 2008 at 10:54 AM, youhaodeyi [EMAIL PROTECTED] wrote: I can use this command to create a maven project: mvn archetype:create \ -DarchetypeGroupId=org.apache.maven.archetypes \ -DgroupId=com.mycompany.app \ -DartifactId=my-app But how can I create a project which includes many modules? -- View this message in context: http://www.nabble.com/How-can-I-create-a-maven-project-with-multiple-modules--tp15890230s177p15890230.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]
Unable to send email notification despite setting gmail as smtp and also configuring proxy
I'm behind a corporate proxy and firewall (trendmicro). So I configured the firewall to allow ports 25, 465 587 for gmail. Then I configured the settings as documented, but still encountering the error below. For configuring the proxy, how do I specify the authentication? 101101 [SocketListener0-0] ERROR org.codehaus.plexus.redback.xwork.mail.Mailer:default - Unable to send message, subject [Welcome to Maven Archiva] org.codehaus.plexus.mailsender.MailSenderException: Error while sending the message... Caused by: javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 465; nested exception is: java.net.ConnectException: Connection timed out: connect at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1282) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java :370) at javax.mail.Service.connect(Service.java:275) at org.codehaus.plexus.mailsender.javamail.AbstractJavamailMailSender.send( AbstractJavamailMailSender.java:210) ... 71 more Caused by: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method)
Re: Maven Assembly for MultiModule project
Hi Wayne, I am sorry Wayne. I should have been more specific on the post. To answer your first comment, and I do not wish to sound rude, but if I knew what I was doing wrong, I would not have posted in the first place. 2. I am trying to assemble a jar of module Foo and Bar . I wish that I create an executable jar with a defined main class and a classpath added to MANIFEST.MF. So basically i want the to create foo.jar and bar.jar containing all the dependencies. 3. I find that if i make the changes in Foo-A or FooB java classes, and if i execute a mvn assembly:assembly, it does not build the FOO-A or FOO-B in the .m2 repository before building Foo and Bar successfully again I have to get around that by doing the following mvn install:install-file -Dfile=/home/krishnan/project/foo-a/target/foo-a-0.1.jar -DgroupId=project -DartifactId=foo-a -Dversion=0.1 -Dpackaging=jar -DgeneratePOM=true, the solution I found by doing a search on one of the posts. and again for foo-b. I would like to avoid that and just have mvn assembly:assembly do all this before creating foo.jar and bar.jar. Wayne Fay wrote: This list really works better if you post what you've done and then tell us why its not working the way you wanted, or an error message you got, etc. Looking at what you sent, I have no idea if it is working how you expect or not. Sending your pom and assembly.xml file is probably not going to give you the results you are hoping for. So, send a reply and be more clear about what you've got vs what you want etc. Wayne On 3/6/08, krishnan.1000 [EMAIL PROTECTED] wrote: Hi, I am a Maven newbie and I hope this is not a stupid question. I am trying to create two Maven assembly jars for modules Foo and Bar. My project -- | |--- Bar |--- Foo |Foo-A |--- Foo-B This is my project structure. In this project, FOO-A is dependent on Foo-B and Bar ,Foo are dependent upon FOO-A. I am trying to build assembly jars for both the for both Foo and Bar modules. Can you please help me? My project pom is as follows. modules moduleBar/module moduleFoo/module moduleFoo-A/module moduleFoo-B/module /modules dependencies dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.13/version scopecompile/scope /dependency .. /dependencies build plugins plugin artifactIdmaven-assembly-plugin/artifactId configuration descriptors descriptorassembly.xml/descriptor /descriptors tarLongFileModegnu/tarLongFileMode /configuration /plugin /build pluginRepositories pluginRepository idapache.snapshots/id urlhttp://people.apache.org/repo/m2-snapshot-repository//url /pluginRepository /pluginRepositories My assembly.xml assembly idjar-with-dependencies/id formats formatjar/format /formats includeBaseDirectoryfalse/includeBaseDirectory fileSets fileSet directorytarget/classes/directory outputDirectory//outputDirectory /fileSet /fileSets dependencySets dependencySet outputDirectory//outputDirectory unpackfalse/unpack scoperuntime/scope /dependencySet /dependencySets /assembly -- View this message in context: http://www.nabble.com/Maven-Assembly-for-MultiModule-project-tp15885942s177p15885942.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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Maven-Assembly-for-MultiModule-project-tp15885942s177p15890574.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: Maven Assembly for MultiModule project
build
plugins
plugin
artifactIdmaven-compiler-plugin/artifactId
version2.1-20080129.223043-7/version
configuration
source1.5/source
target1.5/target
/configuration
/plugin
!-- TestNg plugin --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.4/version
configuration
suiteXmlFiles
suiteXmlFiletestng.xml/suiteXmlFile
/suiteXmlFiles
/configuration
/plugin
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptorRefs
descriptorRefjar-with-dependencies/descriptorRef
/descriptorRefs
archive
manifest
addClasspathtrue/addClasspath
mainClasscom.jbe.core.Foo/mainClass
/manifest
/archive
/configuration
/plugin
/plugins
/build
parent
relativePath../pom.xml/relativePath
version0.1/version
artifactIdfoo-foo/artifactId
groupIdfoo/groupId
/parent
I also find that I have to include foo-b in my foo's pom.xml in order to
compile even though, foo-a is dependent on foo-b and therefore must compile
foo-b before foo-a.
dependencies
dependency
groupIdfoo/groupId
artifactIdfoo-a/artifactId
version${project.version}/version
scopecompile/scope
/dependency
dependency
groupIdfoo/groupId
artifactIdfoo-b/artifactId
version${project.version}/version
scopecompile/scope
/dependency
/dependencies
In addition, I have to add dependencies in all the pom.xml even if they have
been specified in the parent pom.xml.
Thanks,
Karthik Krishnan
krishnan.1000 wrote:
Hi Wayne,
I am sorry Wayne. I should have been more specific on the post. To answer
your first comment, and I do not wish to sound rude, but if I knew what I
was doing wrong, I would not have posted in the first place.
2. I am trying to assemble a jar of module Foo and Bar . I wish that I
create an executable jar with a defined main class and a classpath added
to MANIFEST.MF. So basically i want the to create foo.jar and bar.jar
containing all the dependencies.
3. I find that if i make the changes in Foo-A or FooB java classes, and
if i execute a mvn assembly:assembly, it does not build the FOO-A or FOO-B
in the .m2 repository before building Foo and Bar successfully again I
have to get around that by doing the following
mvn install:install-file
-Dfile=/home/krishnan/project/foo-a/target/foo-a-0.1.jar -DgroupId=project
-DartifactId=foo-a -Dversion=0.1 -Dpackaging=jar -DgeneratePOM=true, the
solution I found by doing a search on one of the posts.
and again for foo-b. I would like to avoid that and just have mvn
assembly:assembly do all this before creating foo.jar and bar.jar.
Wayne Fay wrote:
This list really works better if you post what you've done and then
tell us why its not working the way you wanted, or an error message
you got, etc. Looking at what you sent, I have no idea if it is
working how you expect or not.
Sending your pom and assembly.xml file is probably not going to give
you the results you are hoping for. So, send a reply and be more clear
about what you've got vs what you want etc.
Wayne
On 3/6/08, krishnan.1000 [EMAIL PROTECTED] wrote:
Hi,
I am a Maven newbie and I hope this is not a stupid question. I am
trying
to create two Maven assembly jars for modules Foo and Bar. My project --
|
|--- Bar
|--- Foo
|Foo-A
|--- Foo-B
This is my project structure. In this project, FOO-A is dependent on
Foo-B
and Bar ,Foo are dependent upon FOO-A. I am trying to build assembly
jars
for both the for both Foo and Bar modules. Can you please help me?
My project pom is as follows.
modules
moduleBar/module
moduleFoo/module
moduleFoo-A/module
moduleFoo-B/module
/modules
dependencies
dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
version1.2.13/version
scopecompile/scope
/dependency
..
/dependencies
build
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
descriptors
descriptorassembly.xml/descriptor
/descriptors
tarLongFileModegnu/tarLongFileMode
/configuration
/plugin
/build
pluginRepositories
pluginRepository
idapache.snapshots/id
urlhttp://people.apache.org/repo/m2-snapshot-repository//url
/pluginRepository
/pluginRepositories
My assembly.xml
assembly
idjar-with-dependencies/id
formats
formatjar/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
fileSets
fileSet
directorytarget/classes/directory
outputDirectory//outputDirectory
/fileSet
/fileSets
Re: Archetypes and plugins
Can you please raise a JIRA against the Archetype plugin to run defined goals just after the project generation. Regards, Raphaël 2008/3/6, Ian Godman [EMAIL PROTECTED]: I am working on an Archetype and would like to run a plugin to perform tasks during the create process. Initially this is the eclipse plugin to make an eclipse project but I also need to do some other processing using an as yet unwritten plugin. Is this possible? Any alternatives? Ian
How to set up a repository?
I use tomcat to set up a repository server in local network. And I install some jar files to this repository. When a client download their dependencies from the repository server, it will get a error: Downloading [203] - http://3.36.231.203:8080/maven/repository/dcm4che/dcm4che-net/2.0.13/dcm4che-net-2.0.13.jar ... [WARN] *** CHECKSUM FAILED - Error retrieving checksum file for dcm4che/dcm4che-net/2.0.13/dcm4che-net-2.0.13.jar - IGNORING The jar file can be downloaded successfully. But why the checksum failed? I install the file dcm4che-net-2.0.13.jar manually in the repository server: mvn install:install-file -DgroupId=dcm4che -DartifactId=dcm4che-net -Dversion=2.0.13 -Dpackaging=jar -Dfile=dcm4che-net-2.0.13.jar Did I make a mistake when installing the file? -- View this message in context: http://www.nabble.com/How-to-set-up-a-repository--tp15891048s177p15891048.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]
Web UI to upload into local archiva?
Assuming that I'm able to validate my newly created user (I can't send out email), is there a web UI for me to upload 3rd party JARs into the repository?
Re: How to set up a repository?
On 07/03/2008, youhaodeyi [EMAIL PROTECTED] wrote: I use tomcat to set up a repository server in local network. And I install some jar files to this repository. When a client download their dependencies from the repository server, it will get a error: Downloading [203] - http://3.36.231.203:8080/maven/repository/dcm4che/dcm4che-net/2.0.13/dcm4che-net-2.0.13.jar ... [WARN] *** CHECKSUM FAILED - Error retrieving checksum file for dcm4che/dcm4che-net/2.0.13/dcm4che-net-2.0.13.jar - IGNORING The jar file can be downloaded successfully. But why the checksum failed? I install the file dcm4che-net-2.0.13.jar manually in the repository server: mvn install:install-file -DgroupId=dcm4che -DartifactId=dcm4che-net -Dversion=2.0.13 -Dpackaging=jar -Dfile=dcm4che-net-2.0.13.jar Did I make a mistake when installing the file? install-file is for installing files into your local maven repository you should use deploy:deploy-file to deploy files into a remote shared repository (or use something like Archiva/Proximity) -- View this message in context: http://www.nabble.com/How-to-set-up-a-repository--tp15891048s177p15891048.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] -- Cheers, Stuart
