Re: Maven Jar Plugin - Custom classpath with different style
Hi, there's only a per-artifact transformation possible right now with one layout pattern. You cannot apply a custom pattern on just a subset of artifacts, that would require several enhancements. thanks, Robert On Mon, 06 Feb 2017 15:15:18 +0100, Rolf Rosenbaum, sdbn Solutions GmbH wrote: Hi, i have a question concerning the Maven Jar Plugin. Is it possible to create a classpath entry in the Manifest, which contains version numbers for foreign depencies ans no version number for dependencies of my own modules of a multi module project? E.g.: Class-Path: module1.jar module2.jar libA-1.2.0.jar libB-2.0.0.jar I tried to work with a custom classpath layout, but i get only either all dependencies with or without versionnumber. Kind regards Rolf - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin
Hi, > I add this plugin to my project ,but it doesn't work ,the generated > jar package doesn't contain dependcy jars The maven-jar-plugin does not aggregate dependencies. To do that, check out these plugins: * http://maven.apache.org/plugins/maven-assembly-plugin/ * https://maven.apache.org/plugins/maven-shade-plugin/ * http://one-jar.sourceforge.net/ Regards, Curtis -- Curtis Rueden LOCI software architect - http://loci.wisc.edu/software ImageJ2 lead, Fiji maintainer - http://imagej.net/User:Rueden On Wed, Dec 21, 2016 at 5:52 AM, 亢龙不悔 <1016460...@qq.com> wrote: > I add this plugin to my project ,but it doesn't work ,the generated jar > package doesn't contain dependcy jars > who can help me? > > > > org.apache.maven. > plugins > maven-jar-plugin > 2.4 > > > > > cn.com.epicc.StartMain > > true > > lib/ > < > addDefaultImplementationEntries>true > > > > > >
Re: maven-jar-plugin out of heap space
Hey, It is good news! Thanks again. BR, Csaba
Re: maven-jar-plugin out of heap space
Hi, the VOTE for a fixed version maven-jar-plugin will be finished within a few days which includes this fix.. so only a few days to live with this remporary solution. Kind regards Karl Heinz Marbaise On 6/8/16 11:48 PM, Csaba Kozák wrote: Hey Karl, Updating plexus-archiver seems to do the trick. On 29 May 2016 at 15:21, Karl Heinz Marbaise wrote: Hi, I have checked a setup with -Xmx32m ...which will not work...but if you increase to -Xmx40m it will work... Kind regards Karl Heinz Marbaise On 5/29/16 3:11 PM, Karl Heinz Marbaise wrote: Hi, On 5/26/16 9:13 PM, WonderCsabo wrote: Hey, After i updated the maven-jar-plugin to version 3.0.0, i started to see these problems on my CI build: https://travis-ci.org/WonderCsabo/androidannotations/jobs/132201434#L2473 I can verify that this only happens with 3.0.0. Could you please try to configuration the maven-jar-plugin 3.0.0 like this in your build and check if this helps: org.apache.maven.plugins maven-jar-plugin 3.0.0 org.codehaus.plexus plexus-archiver 3.3 Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin out of heap space
Hey Karl, Updating plexus-archiver seems to do the trick. On 29 May 2016 at 15:21, Karl Heinz Marbaise wrote: > Hi, > > I have checked a setup with -Xmx32m ...which will not work...but if you > increase to -Xmx40m it will work... > > Kind regards > Karl Heinz Marbaise > On 5/29/16 3:11 PM, Karl Heinz Marbaise wrote: > >> Hi, >> >> On 5/26/16 9:13 PM, WonderCsabo wrote: >> >>> Hey, >>> >>> After i updated the maven-jar-plugin to version 3.0.0, i started to see >>> these problems on my CI build: >>> >>> https://travis-ci.org/WonderCsabo/androidannotations/jobs/132201434#L2473 >>> >>> I can verify that this only happens with 3.0.0. >>> >> >> Could you please try to configuration the maven-jar-plugin 3.0.0 like >> this in your build and check if this helps: >> >> >> >> >> org.apache.maven.plugins >> maven-jar-plugin >> 3.0.0 >> >> >> org.codehaus.plexus >> plexus-archiver >> 3.3 >> >> >> >> >> >> >> >> Kind regards >> Karl Heinz Marbaise >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: maven-jar-plugin out of heap space
Hi, I have checked a setup with -Xmx32m ...which will not work...but if you increase to -Xmx40m it will work... Kind regards Karl Heinz Marbaise On 5/29/16 3:11 PM, Karl Heinz Marbaise wrote: Hi, On 5/26/16 9:13 PM, WonderCsabo wrote: Hey, After i updated the maven-jar-plugin to version 3.0.0, i started to see these problems on my CI build: https://travis-ci.org/WonderCsabo/androidannotations/jobs/132201434#L2473 I can verify that this only happens with 3.0.0. Could you please try to configuration the maven-jar-plugin 3.0.0 like this in your build and check if this helps: org.apache.maven.plugins maven-jar-plugin 3.0.0 org.codehaus.plexus plexus-archiver 3.3 Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin out of heap space
Hi, On 5/26/16 9:13 PM, WonderCsabo wrote: Hey, After i updated the maven-jar-plugin to version 3.0.0, i started to see these problems on my CI build: https://travis-ci.org/WonderCsabo/androidannotations/jobs/132201434#L2473 I can verify that this only happens with 3.0.0. Could you please try to configuration the maven-jar-plugin 3.0.0 like this in your build and check if this helps: org.apache.maven.plugins maven-jar-plugin 3.0.0 org.codehaus.plexus plexus-archiver 3.3 Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin out of heap space
This issue has been fixed in plexus archiver, which has not been released yet. Kristian Hey, After i updated the maven-jar-plugin to version 3.0.0, i started to see these problems on my CI build: https://travis-ci.org/WonderCsabo/androidannotations/jobs/132201434#L2473 I can verify that this only happens with 3.0.0. Regard, Csaba -- View this message in context: http://maven.40175.n5.nabble.com/maven-jar-plugin-out-of-heap-space-tp5869355.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin out of heap space
Please file a ticket at https://issues.apache.org/jira/browse/MJAR Provide as much details (Maven version, JDK, OS, etc) as possible and preferably a project to reproduce. /Anders On Thu, May 26, 2016 at 9:13 PM, WonderCsabo wrote: > Hey, > > After i updated the maven-jar-plugin to version 3.0.0, i started to see > these problems on my CI build: > > https://travis-ci.org/WonderCsabo/androidannotations/jobs/132201434#L2473 > > I can verify that this only happens with 3.0.0. > > Regard, > Csaba > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/maven-jar-plugin-out-of-heap-space-tp5869355.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Thanks a lot! will wait for the updated version :) not sure how plugin in eclipse can be updated with snapshot version :( On Mon, May 23, 2016 at 11:44 AM, Karl Heinz Marbaise wrote: > Hi Maxim, > > I've already created an issue for m2e: > > https://github.com/tesla/m2eclipse-mavenarchiver/issues/8 > > Kind regards > Karl Heinz Marbaise > > On 5/23/16 5:54 AM, Maxim Solodovnik wrote: > >> Hello Karl, >> >> do I need to create JIRA issue? or maybe you can point me to the correct >> tracker I can file issue against m2e? >> >> On Sat, May 21, 2016 at 1:11 AM, Karl Heinz Marbaise >> wrote: >> >> Hi, >>> >>> >>> On 5/20/16 7:20 AM, Maxim Solodovnik wrote: >>> >>> I got following errors in eclipse: org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject, org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml /openmeetings-core line 1 Maven Configuration Problem command line build works as expected >>> This is a problem in M2E ... >>> >>> Kind regards >>> Karl Heinz Marbaise >>> >>> On Fri, May 20, 2016 at 11:16 AM, Dan Tran wrote: Hi > > My jar project can also create RPM via rpm-maven-plugin:attach-rpm now > throws this error > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar > (project-jar-for-docker) on project xxx: You have to use a classifier > to attach supplemental artifacts to the project instead of replacing > them. -> [Help 1] > > > This is a valid use case where I can have mutiple artifact extensions > without the need to use classifiers > > > The release notes of jar plugin 3.0.0 also not mentioned about this > > > I hope this is not intentional > > > My appology, i should have tested the during its voting period > > > Thanks > > > -Dan > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- WBR Maxim aka solomax
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Hi Maxim, I've already created an issue for m2e: https://github.com/tesla/m2eclipse-mavenarchiver/issues/8 Kind regards Karl Heinz Marbaise On 5/23/16 5:54 AM, Maxim Solodovnik wrote: Hello Karl, do I need to create JIRA issue? or maybe you can point me to the correct tracker I can file issue against m2e? On Sat, May 21, 2016 at 1:11 AM, Karl Heinz Marbaise wrote: Hi, On 5/20/16 7:20 AM, Maxim Solodovnik wrote: I got following errors in eclipse: org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject, org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml /openmeetings-core line 1 Maven Configuration Problem command line build works as expected This is a problem in M2E ... Kind regards Karl Heinz Marbaise On Fri, May 20, 2016 at 11:16 AM, Dan Tran wrote: Hi My jar project can also create RPM via rpm-maven-plugin:attach-rpm now throws this error [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (project-jar-for-docker) on project xxx: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1] This is a valid use case where I can have mutiple artifact extensions without the need to use classifiers The release notes of jar plugin 3.0.0 also not mentioned about this I hope this is not intentional My appology, i should have tested the during its voting period Thanks -Dan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Hello Karl, do I need to create JIRA issue? or maybe you can point me to the correct tracker I can file issue against m2e? On Sat, May 21, 2016 at 1:11 AM, Karl Heinz Marbaise wrote: > Hi, > > > On 5/20/16 7:20 AM, Maxim Solodovnik wrote: > >> I got following errors in eclipse: >> >> >> org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject, >> org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml >> /openmeetings-core line 1 Maven Configuration Problem >> >> command line build works as expected >> > > This is a problem in M2E ... > > Kind regards > Karl Heinz Marbaise > >> >> On Fri, May 20, 2016 at 11:16 AM, Dan Tran wrote: >> >> Hi >>> >>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now >>> throws this error >>> >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar >>> (project-jar-for-docker) on project xxx: You have to use a classifier >>> to attach supplemental artifacts to the project instead of replacing >>> them. -> [Help 1] >>> >>> >>> This is a valid use case where I can have mutiple artifact extensions >>> without the need to use classifiers >>> >>> >>> The release notes of jar plugin 3.0.0 also not mentioned about this >>> >>> >>> I hope this is not intentional >>> >>> >>> My appology, i should have tested the during its voting period >>> >>> >>> Thanks >>> >>> >>> -Dan >>> >>> > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- WBR Maxim aka solomax
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Awesome, case closed :) On Sun, 22 May 2016 00:05:49 +0200, Dan Tran wrote: I just checked appassembler source, this plugin does populate project artifact if it is found. This mean i just need to configure the appassembler to run at package phase. It works -D On Sat, May 21, 2016 at 12:40 PM, Dan Tran wrote: that would be awesome. appassembler-m-p should copy the primary jar to its lib directory. However, this also means it must run at package phase in order to see the jar-plugin output -D On Sat, May 21, 2016 at 1:39 AM, Robert Scholte wrote: Hi Dan, So if I've correct the appassemble-maven-plugin assumes all jars are already put in the /lib directory by another plugin. I think it is more correct to let the plugin pull its libraries to this folder instead. WDYT? Robert On Fri, 20 May 2016 22:26:45 +0200, Dan Tran wrote: I meant appassemble-maven-plugin. very likely the error is from the fix of https://issues.apache.org/jira/browse/MJAR-198 For now, I will need to use antrun to copy the local primary jar to the place I need. Maybe, appassemble should do this for me btw, if have RPM module but does invocation of 2 jar goals. Would that cause an issue? -D On Fri, May 20, 2016 at 1:11 PM, Karl Heinz Marbaise wrote: Hi Dan, On 5/20/16 10:04 PM, Dan Tran wrote: Hi Robert, According to the jar plugin source outputDirectory is not read only. that is why I can change the default value. here is my use case - Start out of jar module with a profile to create the RPM - In the profile, use assembler-maven-plugin to create staging distribution assembly-maven-plugin? Do you mean maven-assembly-plugin ? - since the primary jar file is not in my staging, I need to invoke jar plugin explicitly to create another jar. This makes jar plugin thinks it has 2 primary artifacts and bails out - Use RPM to package the staging As there has been already a call which sets the main artifact (primary artiact) of the project and maven-jar-plugin regrets to set the main artifact if it is already been set That sounds like you build needs to be cleaned up...to prevent setting the main artifact twice ? Can we see that build somewhere ? Or can you send me a log file of it? (privately?) This is a valid use case right? Hm..we will see Kind regards Karl Heinz Thanks -Dan On Fri, May 20, 2016 at 12:15 PM, Robert Scholte > wrote: Dan, outputDirectory has become a readonly parameter. The reason is that you can set it with . Does that work for you? thanks, Robert On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise < khmarba...@gmx.de> wrote: Hi Dan, On 5/20/16 7:16 AM, Dan Tran wrote: Hi My jar project can also create RPM via rpm-maven-plugin:attach-rpm now throws this error [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (project-jar-for-docker) on project xxx: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1] This is a valid use case where I can have mutiple artifact extensions without the need to use classifiers Can you create an example project for this? So i can create an JIRA for that or you can create the jira with that...sounds like an edge case which i didn't thought of ?... So you are replacing the main artifact but with different extensions ? Hm.. ? The release notes of jar plugin 3.0.0 also not mentioned about this https://issues.apache.org/jira/browse/MJAR-198 I hope this is not intentional Kind regards Karl Heinz Marbaise - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
I just checked appassembler source, this plugin does populate project artifact if it is found. This mean i just need to configure the appassembler to run at package phase. It works -D On Sat, May 21, 2016 at 12:40 PM, Dan Tran wrote: > that would be awesome. appassembler-m-p should copy the primary jar to its > lib directory. However, this also means it must run at package phase in > order to see the jar-plugin output > > -D > > On Sat, May 21, 2016 at 1:39 AM, Robert Scholte > wrote: > >> Hi Dan, >> >> So if I've correct the appassemble-maven-plugin assumes all jars are >> already put in the /lib directory by another plugin. I think it is more >> correct to let the plugin pull its libraries to this folder instead. >> >> WDYT? >> Robert >> >> >> >> On Fri, 20 May 2016 22:26:45 +0200, Dan Tran wrote: >> >> I meant appassemble-maven-plugin. >>> >>> very likely the error is from the fix of >>> https://issues.apache.org/jira/browse/MJAR-198 >>> >>> For now, I will need to use antrun to copy the local primary jar to the >>> place I need. Maybe, appassemble should do this for me >>> >>> >>> btw, if have RPM module but does invocation of 2 jar goals. Would that >>> cause an issue? >>> >>> -D >>> >>> On Fri, May 20, 2016 at 1:11 PM, Karl Heinz Marbaise >>> wrote: >>> >>> Hi Dan, On 5/20/16 10:04 PM, Dan Tran wrote: Hi Robert, > > According to the jar plugin source outputDirectory is not read only. > that > is why I can change the default value. > > here is my use case > > - Start out of jar module with a profile to create the RPM > - In the profile, use assembler-maven-plugin to create staging > distribution > > assembly-maven-plugin? Do you mean maven-assembly-plugin ? - since the primary jar file is not in my staging, I need to invoke jar > plugin explicitly to create another jar. This makes jar plugin thinks > it > has 2 primary artifacts and bails out > - Use RPM to package the staging > > As there has been already a call which sets the main artifact (primary artiact) of the project and maven-jar-plugin regrets to set the main artifact if it is already been set That sounds like you build needs to be cleaned up...to prevent setting the main artifact twice ? Can we see that build somewhere ? Or can you send me a log file of it? (privately?) This is a valid use case right? > > Hm..we will see Kind regards Karl Heinz > Thanks > > -Dan > > > > On Fri, May 20, 2016 at 12:15 PM, Robert Scholte > > wrote: > > Dan, > >> >> outputDirectory has become a readonly parameter. >> The reason is that you can set it with . >> Does >> that work for you? >> >> thanks, >> Robert >> >> >> On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise < >> khmarba...@gmx.de> >> wrote: >> >> Hi Dan, >> >> >>> On 5/20/16 7:16 AM, Dan Tran wrote: >>> >>> Hi >>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now throws this error [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (project-jar-for-docker) on project xxx: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1] This is a valid use case where I can have mutiple artifact extensions without the need to use classifiers Can you create an example project for this? So i can create an JIRA >>> for >>> that or you can create the jira with that...sounds like an edge case >>> which >>> i didn't thought of ?... >>> >>> So you are replacing the main artifact but with different extensions >>> ? >>> >>> Hm.. ? >>> >>> >>> >>> The release notes of jar plugin 3.0.0 also not mentioned about this https://issues.apache.org/jira/browse/MJAR-198 >>> >>> >>> >>> >>> I hope this is not intentional Kind regards >>> Karl Heinz Marbaise >>> >>> - >>> >>> >> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
that would be awesome. appassembler-m-p should copy the primary jar to its lib directory. However, this also means it must run at package phase in order to see the jar-plugin output -D On Sat, May 21, 2016 at 1:39 AM, Robert Scholte wrote: > Hi Dan, > > So if I've correct the appassemble-maven-plugin assumes all jars are > already put in the /lib directory by another plugin. I think it is more > correct to let the plugin pull its libraries to this folder instead. > > WDYT? > Robert > > > > On Fri, 20 May 2016 22:26:45 +0200, Dan Tran wrote: > > I meant appassemble-maven-plugin. >> >> very likely the error is from the fix of >> https://issues.apache.org/jira/browse/MJAR-198 >> >> For now, I will need to use antrun to copy the local primary jar to the >> place I need. Maybe, appassemble should do this for me >> >> >> btw, if have RPM module but does invocation of 2 jar goals. Would that >> cause an issue? >> >> -D >> >> On Fri, May 20, 2016 at 1:11 PM, Karl Heinz Marbaise >> wrote: >> >> Hi Dan, >>> On 5/20/16 10:04 PM, Dan Tran wrote: >>> >>> Hi Robert, According to the jar plugin source outputDirectory is not read only. that is why I can change the default value. here is my use case - Start out of jar module with a profile to create the RPM - In the profile, use assembler-maven-plugin to create staging distribution >>> assembly-maven-plugin? Do you mean maven-assembly-plugin ? >>> >>> >>> - since the primary jar file is not in my staging, I need to invoke jar >>> plugin explicitly to create another jar. This makes jar plugin thinks it has 2 primary artifacts and bails out - Use RPM to package the staging >>> As there has been already a call which sets the main artifact (primary >>> artiact) of the project and maven-jar-plugin regrets to set the main >>> artifact if it is already been set >>> >>> That sounds like you build needs to be cleaned up...to prevent setting >>> the >>> main artifact twice ? Can we see that build somewhere ? Or can you send >>> me >>> a log file of it? (privately?) >>> >>> >>> >>> This is a valid use case right? >>> Hm..we will see >>> >>> >>> Kind regards >>> Karl Heinz >>> >>> >>> >>> >>> Thanks -Dan On Fri, May 20, 2016 at 12:15 PM, Robert Scholte wrote: Dan, > > outputDirectory has become a readonly parameter. > The reason is that you can set it with . > Does > that work for you? > > thanks, > Robert > > > On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise < > khmarba...@gmx.de> > wrote: > > Hi Dan, > > >> On 5/20/16 7:16 AM, Dan Tran wrote: >> >> Hi >> >>> >>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm >>> now >>> throws this error >>> >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar >>> (project-jar-for-docker) on project xxx: You have to use a classifier >>> to attach supplemental artifacts to the project instead of replacing >>> them. -> [Help 1] >>> >>> >>> This is a valid use case where I can have mutiple artifact extensions >>> without the need to use classifiers >>> >>> >>> Can you create an example project for this? So i can create an JIRA >> for >> that or you can create the jira with that...sounds like an edge case >> which >> i didn't thought of ?... >> >> So you are replacing the main artifact but with different extensions ? >> >> Hm.. ? >> >> >> >> The release notes of jar plugin 3.0.0 also not mentioned about this >>> >>> >>> https://issues.apache.org/jira/browse/MJAR-198 >> >> >> >> >> I hope this is not intentional >>> >>> >>> Kind regards >> Karl Heinz Marbaise >> >> - >> >> > - >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Hi Dan, So if I've correct the appassemble-maven-plugin assumes all jars are already put in the /lib directory by another plugin. I think it is more correct to let the plugin pull its libraries to this folder instead. WDYT? Robert On Fri, 20 May 2016 22:26:45 +0200, Dan Tran wrote: I meant appassemble-maven-plugin. very likely the error is from the fix of https://issues.apache.org/jira/browse/MJAR-198 For now, I will need to use antrun to copy the local primary jar to the place I need. Maybe, appassemble should do this for me btw, if have RPM module but does invocation of 2 jar goals. Would that cause an issue? -D On Fri, May 20, 2016 at 1:11 PM, Karl Heinz Marbaise wrote: Hi Dan, On 5/20/16 10:04 PM, Dan Tran wrote: Hi Robert, According to the jar plugin source outputDirectory is not read only. that is why I can change the default value. here is my use case - Start out of jar module with a profile to create the RPM - In the profile, use assembler-maven-plugin to create staging distribution assembly-maven-plugin? Do you mean maven-assembly-plugin ? - since the primary jar file is not in my staging, I need to invoke jar plugin explicitly to create another jar. This makes jar plugin thinks it has 2 primary artifacts and bails out - Use RPM to package the staging As there has been already a call which sets the main artifact (primary artiact) of the project and maven-jar-plugin regrets to set the main artifact if it is already been set That sounds like you build needs to be cleaned up...to prevent setting the main artifact twice ? Can we see that build somewhere ? Or can you send me a log file of it? (privately?) This is a valid use case right? Hm..we will see Kind regards Karl Heinz Thanks -Dan On Fri, May 20, 2016 at 12:15 PM, Robert Scholte wrote: Dan, outputDirectory has become a readonly parameter. The reason is that you can set it with . Does that work for you? thanks, Robert On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise < khmarba...@gmx.de> wrote: Hi Dan, On 5/20/16 7:16 AM, Dan Tran wrote: Hi My jar project can also create RPM via rpm-maven-plugin:attach-rpm now throws this error [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (project-jar-for-docker) on project xxx: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1] This is a valid use case where I can have mutiple artifact extensions without the need to use classifiers Can you create an example project for this? So i can create an JIRA for that or you can create the jira with that...sounds like an edge case which i didn't thought of ?... So you are replacing the main artifact but with different extensions ? Hm.. ? The release notes of jar plugin 3.0.0 also not mentioned about this https://issues.apache.org/jira/browse/MJAR-198 I hope this is not intentional Kind regards Karl Heinz Marbaise - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Hi Dan, On 5/20/16 10:26 PM, Dan Tran wrote: I meant appassemble-maven-plugin. Ah sorry could have imagined that myself... very likely the error is from the fix of https://issues.apache.org/jira/browse/MJAR-198 For now, I will need to use antrun to copy the local primary jar to the place I need. Maybe, appassemble should do this for me btw, if have RPM module but does invocation of 2 jar goals. Would that cause an issue? If you run the jar goals without defining a classifier than yes...I assume you used the jar goal ? That's not a issue it prevents bad things which means simply replacing primary artifact without knowing it... -D On Fri, May 20, 2016 at 1:11 PM, Karl Heinz Marbaise mailto:khmarba...@gmx.de>> wrote: Hi Dan, On 5/20/16 10:04 PM, Dan Tran wrote: Hi Robert, According to the jar plugin source outputDirectory is not read only. that is why I can change the default value. here is my use case - Start out of jar module with a profile to create the RPM - In the profile, use assembler-maven-plugin to create staging distribution assembly-maven-plugin? Do you mean maven-assembly-plugin ? - since the primary jar file is not in my staging, I need to invoke jar plugin explicitly to create another jar. This makes jar plugin thinks it has 2 primary artifacts and bails out - Use RPM to package the staging As there has been already a call which sets the main artifact (primary artiact) of the project and maven-jar-plugin regrets to set the main artifact if it is already been set That sounds like you build needs to be cleaned up...to prevent setting the main artifact twice ? Can we see that build somewhere ? Or can you send me a log file of it? (privately?) This is a valid use case right? Hm..we will see Kind regards Karl Heinz Thanks -Dan On Fri, May 20, 2016 at 12:15 PM, Robert Scholte mailto:rfscho...@apache.org>> wrote: Dan, outputDirectory has become a readonly parameter. The reason is that you can set it with . Does that work for you? thanks, Robert On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise mailto:khmarba...@gmx.de>> wrote: Hi Dan, On 5/20/16 7:16 AM, Dan Tran wrote: Hi My jar project can also create RPM via rpm-maven-plugin:attach-rpm now throws this error [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (project-jar-for-docker) on project xxx: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1] This is a valid use case where I can have mutiple artifact extensions without the need to use classifiers Can you create an example project for this? So i can create an JIRA for that or you can create the jira with that...sounds like an edge case which i didn't thought of ?... So you are replacing the main artifact but with different extensions ? Hm.. ? > The release notes of jar plugin 3.0.0 also not mentioned about this https://issues.apache.org/jira/browse/MJAR-198 I hope this is not intentional - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
I meant appassemble-maven-plugin. very likely the error is from the fix of https://issues.apache.org/jira/browse/MJAR-198 For now, I will need to use antrun to copy the local primary jar to the place I need. Maybe, appassemble should do this for me btw, if have RPM module but does invocation of 2 jar goals. Would that cause an issue? -D On Fri, May 20, 2016 at 1:11 PM, Karl Heinz Marbaise wrote: > Hi Dan, > On 5/20/16 10:04 PM, Dan Tran wrote: > >> Hi Robert, >> >> According to the jar plugin source outputDirectory is not read only. >> that >> is why I can change the default value. >> >> here is my use case >> >> - Start out of jar module with a profile to create the RPM >> - In the profile, use assembler-maven-plugin to create staging >> distribution >> > > assembly-maven-plugin? Do you mean maven-assembly-plugin ? > > > - since the primary jar file is not in my staging, I need to invoke jar >> plugin explicitly to create another jar. This makes jar plugin thinks it >> has 2 primary artifacts and bails out >> - Use RPM to package the staging >> > > As there has been already a call which sets the main artifact (primary > artiact) of the project and maven-jar-plugin regrets to set the main > artifact if it is already been set > > That sounds like you build needs to be cleaned up...to prevent setting the > main artifact twice ? Can we see that build somewhere ? Or can you send me > a log file of it? (privately?) > > > >> This is a valid use case right? >> > > Hm..we will see > > > Kind regards > Karl Heinz > > > > >> >> Thanks >> >> -Dan >> >> >> >> On Fri, May 20, 2016 at 12:15 PM, Robert Scholte >> wrote: >> >> Dan, >>> >>> outputDirectory has become a readonly parameter. >>> The reason is that you can set it with . Does >>> that work for you? >>> >>> thanks, >>> Robert >>> >>> >>> On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise < >>> khmarba...@gmx.de> >>> wrote: >>> >>> Hi Dan, >>> On 5/20/16 7:16 AM, Dan Tran wrote: Hi > > My jar project can also create RPM via rpm-maven-plugin:attach-rpm now > throws this error > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar > (project-jar-for-docker) on project xxx: You have to use a classifier > to attach supplemental artifacts to the project instead of replacing > them. -> [Help 1] > > > This is a valid use case where I can have mutiple artifact extensions > without the need to use classifiers > > Can you create an example project for this? So i can create an JIRA for that or you can create the jira with that...sounds like an edge case which i didn't thought of ?... So you are replacing the main artifact but with different extensions ? Hm.. ? > The release notes of jar plugin 3.0.0 also not mentioned about this > > https://issues.apache.org/jira/browse/MJAR-198 > I hope this is not intentional > > Kind regards Karl Heinz Marbaise - >>> > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Hi Dan, On 5/20/16 10:04 PM, Dan Tran wrote: Hi Robert, According to the jar plugin source outputDirectory is not read only. that is why I can change the default value. here is my use case - Start out of jar module with a profile to create the RPM - In the profile, use assembler-maven-plugin to create staging distribution assembly-maven-plugin? Do you mean maven-assembly-plugin ? - since the primary jar file is not in my staging, I need to invoke jar plugin explicitly to create another jar. This makes jar plugin thinks it has 2 primary artifacts and bails out - Use RPM to package the staging As there has been already a call which sets the main artifact (primary artiact) of the project and maven-jar-plugin regrets to set the main artifact if it is already been set That sounds like you build needs to be cleaned up...to prevent setting the main artifact twice ? Can we see that build somewhere ? Or can you send me a log file of it? (privately?) This is a valid use case right? Hm..we will see Kind regards Karl Heinz Thanks -Dan On Fri, May 20, 2016 at 12:15 PM, Robert Scholte wrote: Dan, outputDirectory has become a readonly parameter. The reason is that you can set it with . Does that work for you? thanks, Robert On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise wrote: Hi Dan, On 5/20/16 7:16 AM, Dan Tran wrote: Hi My jar project can also create RPM via rpm-maven-plugin:attach-rpm now throws this error [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (project-jar-for-docker) on project xxx: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1] This is a valid use case where I can have mutiple artifact extensions without the need to use classifiers Can you create an example project for this? So i can create an JIRA for that or you can create the jira with that...sounds like an edge case which i didn't thought of ?... So you are replacing the main artifact but with different extensions ? Hm.. ? The release notes of jar plugin 3.0.0 also not mentioned about this https://issues.apache.org/jira/browse/MJAR-198 I hope this is not intentional Kind regards Karl Heinz Marbaise - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Hello, It might be a possible usecase to differentiate by extension, but if you want to follow the pure maven model just use an classifier which is used in the repo. Gruss Bernd -- http://bernd.eckenfels.net -Original Message- From: Dan Tran To: Maven Users List Sent: Fr., 20 Mai 2016 22:05 Subject: Re: maven-jar-plugin-3.0.0 compatiblity/regression? Hi Robert, According to the jar plugin source outputDirectory is not read only. that is why I can change the default value. here is my use case - Start out of jar module with a profile to create the RPM - In the profile, use assembler-maven-plugin to create staging distribution - since the primary jar file is not in my staging, I need to invoke jar plugin explicitly to create another jar. This makes jar plugin thinks it has 2 primary artifacts and bails out - Use RPM to package the staging This is a valid use case right? Thanks -Dan On Fri, May 20, 2016 at 12:15 PM, Robert Scholte wrote: > Dan, > > outputDirectory has become a readonly parameter. > The reason is that you can set it with . Does > that work for you? > > thanks, > Robert > > > On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise > wrote: > > Hi Dan, >> >> On 5/20/16 7:16 AM, Dan Tran wrote: >> >>> Hi >>> >>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now >>> throws this error >>> >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar >>> (project-jar-for-docker) on project xxx: You have to use a classifier >>> to attach supplemental artifacts to the project instead of replacing >>> them. -> [Help 1] >>> >>> >>> This is a valid use case where I can have mutiple artifact extensions >>> without the need to use classifiers >>> >> >> Can you create an example project for this? So i can create an JIRA for >> that or you can create the jira with that...sounds like an edge case which >> i didn't thought of ?... >> >> So you are replacing the main artifact but with different extensions ? >> >> Hm.. ? >> >> >>> >>> The release notes of jar plugin 3.0.0 also not mentioned about this >>> >> >> https://issues.apache.org/jira/browse/MJAR-198 >> >> >> >>> >>> I hope this is not intentional >>> >> >> Kind regards >> Karl Heinz Marbaise >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Hi Robert, According to the jar plugin source outputDirectory is not read only. that is why I can change the default value. here is my use case - Start out of jar module with a profile to create the RPM - In the profile, use assembler-maven-plugin to create staging distribution - since the primary jar file is not in my staging, I need to invoke jar plugin explicitly to create another jar. This makes jar plugin thinks it has 2 primary artifacts and bails out - Use RPM to package the staging This is a valid use case right? Thanks -Dan On Fri, May 20, 2016 at 12:15 PM, Robert Scholte wrote: > Dan, > > outputDirectory has become a readonly parameter. > The reason is that you can set it with . Does > that work for you? > > thanks, > Robert > > > On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise > wrote: > > Hi Dan, >> >> On 5/20/16 7:16 AM, Dan Tran wrote: >> >>> Hi >>> >>> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now >>> throws this error >>> >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar >>> (project-jar-for-docker) on project xxx: You have to use a classifier >>> to attach supplemental artifacts to the project instead of replacing >>> them. -> [Help 1] >>> >>> >>> This is a valid use case where I can have mutiple artifact extensions >>> without the need to use classifiers >>> >> >> Can you create an example project for this? So i can create an JIRA for >> that or you can create the jira with that...sounds like an edge case which >> i didn't thought of ?... >> >> So you are replacing the main artifact but with different extensions ? >> >> Hm.. ? >> >> >>> >>> The release notes of jar plugin 3.0.0 also not mentioned about this >>> >> >> https://issues.apache.org/jira/browse/MJAR-198 >> >> >> >>> >>> I hope this is not intentional >>> >> >> Kind regards >> Karl Heinz Marbaise >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Dan, outputDirectory has become a readonly parameter. The reason is that you can set it with . Does that work for you? thanks, Robert On Fri, 20 May 2016 21:09:55 +0200, Karl Heinz Marbaise wrote: Hi Dan, On 5/20/16 7:16 AM, Dan Tran wrote: Hi My jar project can also create RPM via rpm-maven-plugin:attach-rpm now throws this error [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (project-jar-for-docker) on project xxx: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1] This is a valid use case where I can have mutiple artifact extensions without the need to use classifiers Can you create an example project for this? So i can create an JIRA for that or you can create the jira with that...sounds like an edge case which i didn't thought of ?... So you are replacing the main artifact but with different extensions ? Hm.. ? The release notes of jar plugin 3.0.0 also not mentioned about this https://issues.apache.org/jira/browse/MJAR-198 I hope this is not intentional Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Hi, On 5/20/16 7:20 AM, Maxim Solodovnik wrote: I got following errors in eclipse: org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject, org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml /openmeetings-core line 1 Maven Configuration Problem command line build works as expected This is a problem in M2E ... Kind regards Karl Heinz Marbaise On Fri, May 20, 2016 at 11:16 AM, Dan Tran wrote: Hi My jar project can also create RPM via rpm-maven-plugin:attach-rpm now throws this error [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (project-jar-for-docker) on project xxx: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1] This is a valid use case where I can have mutiple artifact extensions without the need to use classifiers The release notes of jar plugin 3.0.0 also not mentioned about this I hope this is not intentional My appology, i should have tested the during its voting period Thanks -Dan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
Hi Dan, On 5/20/16 7:16 AM, Dan Tran wrote: Hi My jar project can also create RPM via rpm-maven-plugin:attach-rpm now throws this error [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (project-jar-for-docker) on project xxx: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. -> [Help 1] This is a valid use case where I can have mutiple artifact extensions without the need to use classifiers Can you create an example project for this? So i can create an JIRA for that or you can create the jira with that...sounds like an edge case which i didn't thought of ?... So you are replacing the main artifact but with different extensions ? Hm.. ? The release notes of jar plugin 3.0.0 also not mentioned about this https://issues.apache.org/jira/browse/MJAR-198 I hope this is not intentional Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
sorry about the noise, my pom also calls
org.apache.maven.plugins
maven-jar-plugin
project-jar-for-rpm
package
jar
${rpm.staging.directory}/lib
to push the main jar to another directory consumed by rpm-m-p, that
triggers this issue
Looks like I have to use antrun instead. Ouch!!
-Dan
On Thu, May 19, 2016 at 10:16 PM, Dan Tran wrote:
> Hi
>
> My jar project can also create RPM via rpm-maven-plugin:attach-rpm now
> throws this error
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (project-jar-for-docker)
> on project xxx: You have to use a classifier to attach supplemental artifacts
> to the project instead of replacing them. -> [Help 1]
>
>
> This is a valid use case where I can have mutiple artifact extensions without
> the need to use classifiers
>
>
> The release notes of jar plugin 3.0.0 also not mentioned about this
>
>
> I hope this is not intentional
>
>
> My appology, i should have tested the during its voting period
>
>
> Thanks
>
>
> -Dan
>
>
>
>
Re: maven-jar-plugin-3.0.0 compatiblity/regression?
I got following errors in eclipse: org.apache.maven.archiver.MavenArchiver.getManifest(org.apache.maven.project.MavenProject, org.apache.maven.archiver.MavenArchiveConfiguration) pom.xml /openmeetings-core line 1 Maven Configuration Problem command line build works as expected On Fri, May 20, 2016 at 11:16 AM, Dan Tran wrote: > Hi > > My jar project can also create RPM via rpm-maven-plugin:attach-rpm now > throws this error > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar > (project-jar-for-docker) on project xxx: You have to use a classifier > to attach supplemental artifacts to the project instead of replacing > them. -> [Help 1] > > > This is a valid use case where I can have mutiple artifact extensions > without the need to use classifiers > > > The release notes of jar plugin 3.0.0 also not mentioned about this > > > I hope this is not intentional > > > My appology, i should have tested the during its voting period > > > Thanks > > > -Dan > -- WBR Maxim aka solomax
Re: Maven Jar Plugin - Testjar: includes together with skipIfEmpty
Hi Nick, Nick Stolwijk wrote: > Hi Folks, > > I found a little curiosity in the maven jar plugin. > > if you specify includes and the skipIfEmpty property a jar is still > created and attached while it only has a pom file in it. I would have > expected that the creation of the jar was skipped if no files where > selected by my includes property. Well, since the default includes the pom, the jar is not empty. > My usecase: I only want to generate the tests jar when there are > builders in the module, so other modules can use those builders in > their tests. I don't want to package all tests, to prevent developers > to create dependencies on these tests. > > My configuration: > > > maven-jar-plugin > > > > test-jar > > > true > > **/*Builder.class > > > > > Configure the archiver to skip the Maven descriptor: == %< == false == %< == Cheers, Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Jar Plugin - Testjar: includes together with skipIfEmpty
Hi, I think I faced something similar, some time ago, but not absolutely sure, here is what I remember: works by testing if directory is present, so if src/test/java is present (no matter if empty or not) jar will be created. hope it helps tonio On Mon, Apr 28, 2014 at 6:12 AM, Nick Stolwijk wrote: > Hi Folks, > > I found a little curiosity in the maven jar plugin. > > if you specify includes and the skipIfEmpty property a jar is still > created and attached while it only has a pom file in it. I would have > expected that the creation of the jar was skipped if no files where > selected by my includes property. > > My usecase: I only want to generate the tests jar when there are > builders in the module, so other modules can use those builders in > their tests. I don't want to package all tests, to prevent developers > to create dependencies on these tests. > > My configuration: > > > maven-jar-plugin > > > > test-jar > > > true > > **/*Builder.class > > > > > > > With regards, > > Nick Stolwijk > > ~~~ Try to leave this world a little better than you found it and, > when your turn comes to die, you can die happy in feeling that at any > rate you have not wasted your time but have done your best ~~~ > > Lord Baden-Powell > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: maven-jar-plugin refuses to include META-INF/persistence.xml ! - Problem solved
If you use the bundle style in your pom, then its bnd that does the actual jar creation, and NOT the traditional jar plugin. We hit this same issue awhile ago when including compiled coffee-script into our jars, just putting them directly in target/classes doesn't "just work". Mark On 13/08/2012, at 2:29 AM, Tommy Svensson wrote: > I didn't know that the bundle-plugin affected jar:ing. I thought it just > packaged things correctly under target and then the maven-jar-plugin did the > rest. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven-jar-plugin refuses to include META-INF/persistence.xml ! - Problem solved
from now on we're going to rely on you... as our BND expert!
Glad to hear that worked
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Subject: Re: maven-jar-plugin refuses to include META-INF/persistence.xml ! -
> Problem solved
> From: to...@natusoft.se
> Date: Sun, 12 Aug 2012 16:29:18 +0200
> To: users@maven.apache.org
>
> I pulled those parts out and replaced them with "..." to make the example
> smaller. I didn't think those parts relevant, but apparently they are since
> the following suggested by Stuart McCulloch does work:
>
> {maven-resources},
> META-INF/persistence.xml=target/classes/META-INF/persistence.xml
>
> I didn't know that the bundle-plugin affected jar:ing. I thought it just
> packaged things correctly under target and then the maven-jar-plugin did the
> rest.
>
> I'm starting to realize that just assuming is probably a bad idea ...
>
> /Tommy
>
> 12 aug 2012 kl. 03:54 skrev Martin Gainty :
>
> >
> > http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
> >
> > I didnt see your
> > Export-Package
> > Private-Package
> > Bundle-Activator
> > At execution time you will need to config the maven-bundle-plugin with
> > configuration instructions such as what is here:
> >
> >
> >
> > org.apache.felix
> > maven-bundle-plugin
> > true
> >
> >
> > com.my.company.api
> > com.my.company.*
> > com.my.company.Activator
> >
> >
> >
> >
> > The Export-Package of com.my.company.api indicates
> > the plugin will copy the Log Service package into the resulting bundle JAR
> > file and export to other bundles
> > The Private-Package of com.my.company.* indicates
> > the available package(s) to copy into the bundle but NOT export to other
> > bundles
> >
> > But if you really want total control of your bundle you'll want to learn BND
> > The *best* example of BND configuration and an explanation of BND supported
> > attributes are located here
> > http://www.aqute.biz/Bnd/Bnd
> >
> > Martin Gainty
> > __
> > Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
> >
> > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
> > Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> > dient lediglich dem Austausch von Informationen und entfaltet keine
> > rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> > E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
> > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
> > destinataire prévu, nous te demandons avec bonté que pour satisfaire
> > informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
> > de ceci est interdite. Ce message sert à l'information seulement et n'aura
> > pas n'importe quel effet légalement obligatoire. Étant donné que les email
> > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
> > aucune responsabilité pour le contenu fourni.
> >
> >
> >> From: tommybsvens...@me.com
> >> Subject: Re: maven-jar-plugin refuses to include META-INF/persistence.xml
> >> ! - Problem solved
> >> Date: Sat, 11 Aug 2012 18:56:43 +
Re: maven-jar-plugin refuses to include META-INF/persistence.xml ! - Problem solved
I pulled those parts out and replaced them with "..." to make the example
smaller. I didn't think those parts relevant, but apparently they are since the
following suggested by Stuart McCulloch does work:
{maven-resources},
META-INF/persistence.xml=target/classes/META-INF/persistence.xml
I didn't know that the bundle-plugin affected jar:ing. I thought it just
packaged things correctly under target and then the maven-jar-plugin did the
rest.
I'm starting to realize that just assuming is probably a bad idea ...
/Tommy
12 aug 2012 kl. 03:54 skrev Martin Gainty :
>
> http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
>
> I didnt see your
> Export-Package
> Private-Package
> Bundle-Activator
> At execution time you will need to config the maven-bundle-plugin with
> configuration instructions such as what is here:
>
>
>
> org.apache.felix
> maven-bundle-plugin
> true
>
>
> com.my.company.api
> com.my.company.*
> com.my.company.Activator
>
>
>
>
> The Export-Package of com.my.company.api indicates
> the plugin will copy the Log Service package into the resulting bundle JAR
> file and export to other bundles
> The Private-Package of com.my.company.* indicates
> the available package(s) to copy into the bundle but NOT export to other
> bundles
>
> But if you really want total control of your bundle you'll want to learn BND
> The *best* example of BND configuration and an explanation of BND supported
> attributes are located here
> http://www.aqute.biz/Bnd/Bnd
>
> Martin Gainty
> __
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
> sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
> oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich
> dem Austausch von Informationen und entfaltet keine rechtliche
> Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen
> wir keine Haftung fuer den Inhalt uebernehmen.
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
> destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
> l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci
> est interdite. Ce message sert à l'information seulement et n'aura pas
> n'importe quel effet légalement obligatoire. Étant donné que les email
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
> aucune responsabilité pour le contenu fourni.
>
>
>> From: tommybsvens...@me.com
>> Subject: Re: maven-jar-plugin refuses to include META-INF/persistence.xml !
>> - Problem solved
>> Date: Sat, 11 Aug 2012 18:56:43 +0200
>> To: users@maven.apache.org
>>
>> I finally found the source of this problem! Or close to it at least. I have
>> managed to get my META-INF/persistence.xml included in the jar, but I'm
>> unsure what is to blame :-).
>>
>> I'm also using the Apache Felix bundle-plugin which allows for:
>>
>> bundle
>>
>> This due to the following configuration:
>>
>>
>> org.apache.felix
>> maven-bundle-plugin
>> 2.3.5
>> true
>> ...
>>
>>
>> jar
>> bundle
>>
>> ...
>>
>>
>>
>> That is, I can use either or of "bundle" or "jar" for packaging. However
>> when i use:
>>
>> bundle
>>
>> I don't get the META-INF/persistence.xml file in the jar.
>>
>> But when I change to:
>>
>> jar
>>
>> It is included! So my guess is that the maven-jar-plugin is affected by the
>> packaging. The Felix bundle-plugin still works OK with packaging "jar" so
>> I'll stick with that for now on.
>>
>> /Tommy
>>
>> 22 jul 2012 kl. 18:27 skrev Wayne Fay :
>>
>>>> I was hoping for a "Well, thats easy, just do ..." :-). But you are of
>>>> course right
>>>> Wayne, I need to isolate what is causing this. Thanks.
>>>
>>> If META-INF/persistence.xml was not even showing up in target, then we
>>> might be able to provide a simple "recipe" to solve it. But that is
>>> not the case here. Come back and let us know when you solve it.
>>>
>>> Wayne
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin refuses to include META-INF/persistence.xml ! - Problem solved
>> Most likely the "bundle" packaging does not include META-INF for some >> reason. I would talk to the Apache Felix people about this issue so >> they can resolve it in their code. > > This is working as designed, as covered in the FAQ: Thanks Stuart. This is a good thing to keep in mind for when future felix users land here complaining about similar problems. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin refuses to include META-INF/persistence.xml ! - Problem solved
On 12 Aug 2012, at 03:54, Wayne Fay wrote:
>> I'm also using the Apache Felix bundle-plugin which allows for:
>>
>>bundle
>
> This is not a packaging delivered by Apache Maven. Thus you can
> "blame" whoever is making this packaging available to you.
>
>> That is, I can use either or of "bundle" or "jar" for packaging. However
>> when i use:
>>
>>bundle
>>
>> I don't get the META-INF/persistence.xml file in the jar.
>
> Most likely the "bundle" packaging does not include META-INF for some
> reason. I would talk to the Apache Felix people about this issue so
> they can resolve it in their code.
This is working as designed, as covered in the FAQ:
http://felix.apache.org/site/apache-felix-bundle-plugin-faq.html#ApacheFelixBundlePluginFAQ-WhenIbuildabundle%252Csomeclassesarebuiltin%2522target%252Fclasses%2522butthey%2527renotincludedinthefinaljar.
Not everything in target/classes ends up in the bundle by default (unlike jar)
- the underlying bnd library will only pull what resources/packages you tell it
to into the bundle. While the plugin attempts to generate reasonable defaults
based on your source, it can't do this for generated resources such as this
persistence.xml file (see last FAQ item). Instead you need something like:
{maven-resources},
META-INF/persistence.xml=target/classes/META-INF/persistence.xml
Where {maven-resources} is a placeholder for the default detected resources, as
described in the Include-Resource section of
http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
The raw format of bnd's Include-Resource instruction can be found at
http://www.aqute.biz/Bnd/Format#include-resource
HTH
--
Cheers, Stuart
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin refuses to include META-INF/persistence.xml ! - Problem solved
> I'm also using the Apache Felix bundle-plugin which allows for: > > bundle This is not a packaging delivered by Apache Maven. Thus you can "blame" whoever is making this packaging available to you. > That is, I can use either or of "bundle" or "jar" for packaging. However when > i use: > > bundle > > I don't get the META-INF/persistence.xml file in the jar. Most likely the "bundle" packaging does not include META-INF for some reason. I would talk to the Apache Felix people about this issue so they can resolve it in their code. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven-jar-plugin refuses to include META-INF/persistence.xml ! - Problem solved
http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html I didnt see your Export-Package Private-Package Bundle-Activator At execution time you will need to config the maven-bundle-plugin with configuration instructions such as what is here: org.apache.felix maven-bundle-plugin true com.my.company.api com.my.company.* com.my.company.Activator The Export-Package of com.my.company.api indicates the plugin will copy the Log Service package into the resulting bundle JAR file and export to other bundles The Private-Package of com.my.company.* indicates the available package(s) to copy into the bundle but NOT export to other bundles But if you really want total control of your bundle you'll want to learn BND The *best* example of BND configuration and an explanation of BND supported attributes are located here http://www.aqute.biz/Bnd/Bnd Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > From: tommybsvens...@me.com > Subject: Re: maven-jar-plugin refuses to include META-INF/persistence.xml ! - > Problem solved > Date: Sat, 11 Aug 2012 18:56:43 +0200 > To: users@maven.apache.org > > I finally found the source of this problem! Or close to it at least. I have > managed to get my META-INF/persistence.xml included in the jar, but I'm > unsure what is to blame :-). > > I'm also using the Apache Felix bundle-plugin which allows for: > > bundle > > This due to the following configuration: > > > org.apache.felix > maven-bundle-plugin > 2.3.5 > true >... > > > jar > bundle > > ... > > > > That is, I can use either or of "bundle" or "jar" for packaging. However when > i use: > > bundle > > I don't get the META-INF/persistence.xml file in the jar. > > But when I change to: > > jar > > It is included! So my guess is that the maven-jar-plugin is affected by the > packaging. The Felix bundle-plugin still works OK with packaging "jar" so > I'll stick with that for now on. > > /Tommy > > 22 jul 2012 kl. 18:27 skrev Wayne Fay : > > >> I was hoping for a "Well, thats easy, just do ..." :-). But you are of > >> course right > >> Wayne, I need to isolate what is causing this. Thanks. > > > > If META-INF/persistence.xml was not even showing up in target, then we > > might be able to provide a simple "recipe" to solve it. But that is > > not the case here. Come back and let us know when you solve it. > > > > Wayne > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > >
Re: maven-jar-plugin refuses to include META-INF/persistence.xml ! - Problem solved
I finally found the source of this problem! Or close to it at least. I have managed to get my META-INF/persistence.xml included in the jar, but I'm unsure what is to blame :-). I'm also using the Apache Felix bundle-plugin which allows for: bundle This due to the following configuration: org.apache.felix maven-bundle-plugin 2.3.5 true ... jar bundle ... That is, I can use either or of "bundle" or "jar" for packaging. However when i use: bundle I don't get the META-INF/persistence.xml file in the jar. But when I change to: jar It is included! So my guess is that the maven-jar-plugin is affected by the packaging. The Felix bundle-plugin still works OK with packaging "jar" so I'll stick with that for now on. /Tommy 22 jul 2012 kl. 18:27 skrev Wayne Fay : >> I was hoping for a "Well, thats easy, just do ..." :-). But you are of >> course right >> Wayne, I need to isolate what is causing this. Thanks. > > If META-INF/persistence.xml was not even showing up in target, then we > might be able to provide a simple "recipe" to solve it. But that is > not the case here. Come back and let us know when you solve it. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
Re: maven-jar-plugin refuses to include META-INF/persistence.xml !
> I was hoping for a "Well, thats easy, just do ..." :-). But you are of course > right > Wayne, I need to isolate what is causing this. Thanks. If META-INF/persistence.xml was not even showing up in target, then we might be able to provide a simple "recipe" to solve it. But that is not the case here. Come back and let us know when you solve it. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin refuses to include META-INF/persistence.xml !
Which packaging do have? Can you post your POM?
Am 21.07.2012 22:51 schrieb "Tommy Svensson" :
> Hello maven fans,
>
> I've become slightly balder today. I've been tearing my hair over why JPA
> keeps insisting it cannot find my persistence unit. Everything in my
> persistence.xml file is correct I've checked it over an over.
>
> I've just discovered that the problem is not in the JPA provider (tried
> both EclipseLink and OpenJPA), but in Maven!!!
>
> Maven just refuses to include META-INF/persistence.xml in the jar no
> matter what I do! It resides in src/main/resources/META-INF. After building
> it is also in target/classes/META-INF along with MANIFEST.MF, but it is
> missing in the jar file.
>
> I googled and someone suggested this (yes, I'm not alone with this
> problem):
>
>
>
> false
> ${basedir}/src/main/resources
>
> META-INF/persistence.xml
>
>
>
>
> That however had no effect what so ever. Next I tried this:
>
>
> maven-jar-plugin
>
>
> META-INF/persistence.xml
>
>
>
> ${project.build.outputDirectory}/META-INF/MANIFEST.MF
>
>
>
>
> That didn't help either. Then I found at codehaus that this was a bug and
> that it was fixed in version 2.1 of the maven-jar-plugin. So I tried to add
> version to the plugin specification. Version 2.4 was the latest I found:
>
>
> maven-jar-plugin
> 2.4
>
>
> META-INF/persistence.xml
>
>
>
> ${project.build.outputDirectory}/META-INF/MANIFEST.MF
>
>
>
>
> That didn't work either. I'm out of ideas and my fingers hurt from all the
> googling. Do anyone have any idea how to solve this truly annoying problem ?
>
> I can add that I'm also using the Apache Felix maven-bundle-plugin. I
> don't know if it can affect this behavior.
>
> Anyhow, any suggestions are appreciated. Currently I have to manually jar
> my project.
>
> Regards,
> Tommy Svensson
>
>
Re: maven-jar-plugin refuses to include META-INF/persistence.xml !
I was hoping for a "Well, thats easy, just do ..." :-). But you are of course right Wayne, I need to isolate what is causing this. Thanks. /Tommy 22 jul 2012 kl. 05:30 skrev Wayne Fay: >> Maven just refuses to include META-INF/persistence.xml in the jar no matter >> what I do! It resides in src/main/resources/META-INF. After building it is >> also >> in target/classes/META-INF along with MANIFEST.MF, but it is missing in the >> jar file. > > Try a very simple test... > Run "mvn archetype:generate" (and pick maven-archetype-quickstart > which is 205 for me). Specify whatever values when prompted. > Then "mkdir src/main/resources/META-INF". > Copy your persistence.xml file there. > Run "mvn package" from the project directory. > Then "cd target" and "jar -tvf blah-1.0-SNAPSHOT.jar | grep > persistence" and see if it is in the jar. > > If so, there *must* be some additional configuration which you are > applying which is causing this to fail. > > "mvn help:effective-pom" might be helpful in tracking this down more. > I would remove as much configuration from your pom as possible while > keeping the basic functionality you require. > >> I can add that I'm also using the Apache Felix maven-bundle-plugin. I don't >> know >> if it can affect this behavior. > > No clue. If your test above works, I'd try to build things without > this plugin and see if the problem goes away. If that works, I'd ask > the Apache Felix team about it. Perhaps they are doing something funky > which causes this file to not be included in your artifacts. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin refuses to include META-INF/persistence.xml !
> Maven just refuses to include META-INF/persistence.xml in the jar no matter > what I do! It resides in src/main/resources/META-INF. After building it is > also > in target/classes/META-INF along with MANIFEST.MF, but it is missing in the > jar file. Try a very simple test... Run "mvn archetype:generate" (and pick maven-archetype-quickstart which is 205 for me). Specify whatever values when prompted. Then "mkdir src/main/resources/META-INF". Copy your persistence.xml file there. Run "mvn package" from the project directory. Then "cd target" and "jar -tvf blah-1.0-SNAPSHOT.jar | grep persistence" and see if it is in the jar. If so, there *must* be some additional configuration which you are applying which is causing this to fail. "mvn help:effective-pom" might be helpful in tracking this down more. I would remove as much configuration from your pom as possible while keeping the basic functionality you require. > I can add that I'm also using the Apache Felix maven-bundle-plugin. I don't > know > if it can affect this behavior. No clue. If your test above works, I'd try to build things without this plugin and see if the problem goes away. If that works, I'd ask the Apache Felix team about it. Perhaps they are doing something funky which causes this file to not be included in your artifacts. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-jar-plugin(put the configuration file to the WEB-INFO/classes rather than WEB-INFO/lib/xx.jar.
Remove config.properties from your server jar project!
Put it in src/main/resources of the war project (as you would for any Maven
project).
/Anders
On Fri, Mar 5, 2010 at 15:34, maven apache wrote:
> 2010/3/5 Anders Hammar
>
> > Generally, read files from the classpath.
> > So, remove the config.properties form your server project. For any unit
> > tests you can put a config.properties under src/test/resources (will be
> on
> > the test class path). The add the config.properties to you war project so
> > that it will be added to the webapp's class path. And there you go... Or,
> > you might even want to keep the config.properties outside the war if you
> > want to have different configuration for each environment.
>
> Yes, it is just why I did this.
> But where should I put the config.properties in the war module. The
> structures of my proect is :
>
> Server
> --src/main/java
>--ClassWhichUseTheConfigFile () //use the
> XX.class.getResource("config.properties")
>--config.poperties
> --src/mainresourcs
>
> Web
> --src/main/webapp
> ...
>
>
> So if I put the file to Web(war) module, I may have to modify the manner to
> get it.
>
>
> > Your app server
> > will likely have some folder where you can add config.properties so that
> it
> > ends up on the class path.
> >
> > /Anders
> >
> > On Fri, Mar 5, 2010 at 14:48, maven apache
> wrote:
> >
> > > HI:
> > > I have two module Server(type of jar) and Web(type of war).
> > > The Web module need Server, however in the Server module I need to read
> > > something from a config file(config.properties), this file is put under
> > the
> > > Server module, and I do not want to this file packaged to the
> server.jar
> > > file, I want to it under the Web/WEB-INFO/classes .
> > > So I use the maven-jar-plugin to exclude the config.properties, however
> > > after I run "mvn clean install" , I found that the server.jar do not
> > > contain
> > > the config.properties( this is just I expected), however the file do
> not
> > > exist under the Web/WEB-INFO/classes.
> > > So I want to know if there are any ways to implement my requirement?
> > >
> >
>
Re: maven-jar-plugin(put the configuration file to the WEB-INFO/classes rather than WEB-INFO/lib/xx.jar.
2010/3/5 Anders Hammar
> Generally, read files from the classpath.
> So, remove the config.properties form your server project. For any unit
> tests you can put a config.properties under src/test/resources (will be on
> the test class path). The add the config.properties to you war project so
> that it will be added to the webapp's class path. And there you go... Or,
> you might even want to keep the config.properties outside the war if you
> want to have different configuration for each environment.
Yes, it is just why I did this.
But where should I put the config.properties in the war module. The
structures of my proect is :
Server
--src/main/java
--ClassWhichUseTheConfigFile () //use the
XX.class.getResource("config.properties")
--config.poperties
--src/mainresourcs
Web
--src/main/webapp
...
So if I put the file to Web(war) module, I may have to modify the manner to
get it.
> Your app server
> will likely have some folder where you can add config.properties so that it
> ends up on the class path.
>
> /Anders
>
> On Fri, Mar 5, 2010 at 14:48, maven apache wrote:
>
> > HI:
> > I have two module Server(type of jar) and Web(type of war).
> > The Web module need Server, however in the Server module I need to read
> > something from a config file(config.properties), this file is put under
> the
> > Server module, and I do not want to this file packaged to the server.jar
> > file, I want to it under the Web/WEB-INFO/classes .
> > So I use the maven-jar-plugin to exclude the config.properties, however
> > after I run "mvn clean install" , I found that the server.jar do not
> > contain
> > the config.properties( this is just I expected), however the file do not
> > exist under the Web/WEB-INFO/classes.
> > So I want to know if there are any ways to implement my requirement?
> >
>
Re: maven-jar-plugin(put the configuration file to the WEB-INFO/classes rather than WEB-INFO/lib/xx.jar.
Generally, read files from the classpath. So, remove the config.properties form your server project. For any unit tests you can put a config.properties under src/test/resources (will be on the test class path). The add the config.properties to you war project so that it will be added to the webapp's class path. And there you go... Or, you might even want to keep the config.properties outside the war if you want to have different configuration for each environment. Your app server will likely have some folder where you can add config.properties so that it ends up on the class path. /Anders On Fri, Mar 5, 2010 at 14:48, maven apache wrote: > HI: > I have two module Server(type of jar) and Web(type of war). > The Web module need Server, however in the Server module I need to read > something from a config file(config.properties), this file is put under the > Server module, and I do not want to this file packaged to the server.jar > file, I want to it under the Web/WEB-INFO/classes . > So I use the maven-jar-plugin to exclude the config.properties, however > after I run "mvn clean install" , I found that the server.jar do not > contain > the config.properties( this is just I expected), however the file do not > exist under the Web/WEB-INFO/classes. > So I want to know if there are any ways to implement my requirement? >
Re: maven-jar-plugin version 2.3 MANIFEST.MF SNAPSHOT problem
Stephen Duncan Jr wrote:
> I see that http://jira.codehaus.org/browse/MJAR-28 was "fixed" in the 2.3
> release. From my perspective, this seems to have broken things, including a
> viable working system I had using 2.2.
>
> In 2.3 I have several SNAPSHOT dependencies, but when I build a jar with
> addClasspath, only one of those is getting a timestamp version, the rest
> still say -SNAPSHOT. In 2.2 all would say -SNAPSHOT. By adding:
>
>
>
> ${artifact.artifactId}-${artifact.baseVersion}.${artifact.extension}
>
>
> to my dependency-set config for the assembly plugin, the assembly plugin
> would also always use -SNAPSHOT.
>
> In 2.3 the versions in the MANIFEST still do not match up to the assembly
> (after removing the outputFileNameMapping), as in that case all the versions
> in the assembly are timestamped, but many are not in the manifest.
>
> Should I reopen MJAR-28?
>
Hi Stephen,
Please create a new issue if you are still having problems. We can add a
link to the old issue later, but I prefer not to reopen issues when the
version they were "fixed" in have been released. It messes up the
changes reports.
Also, please attach a sample project that we can use to reproduce the issue.
--
Dennis Lundberg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven Jar plugin 2.0 : ClassPath in manifest
Clicked on send before pasting the link:
http://jira.codehaus.org/browse/MJAR-61
Tomas Darbois
-Message d'origine-
De : Thomas Darbois
Envoyé : mercredi 23 avril 2008 11:00
À : 'Maven Users List'
Objet : RE: Maven Jar plugin 2.0 : ClassPath in manifest
Well i ve found the Jira that is linked to that problem :
Tomas Darbois
-Message d'origine-
De : Thomas Darbois [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 23 avril 2008 10:10
À : Maven Users List
Objet : RE: Maven Jar plugin 2.0 : ClassPath in manifest
Thanks for replying :)
I've tried to put to the pom for test, it didn't change anything. I
ve check the exported-pom and indeed the tag was already set to
${artifactId} even without adding your suggestion (it
inherits that part of the build from his parent pom). It seems that he doesn't
read finalName tag in the exported-pom(s) that are inside the jar of his
dependencies, but when you are generating the entire modules from the parent
module, it keeps in memory all their finalname.
I don't know what you mean with your alternative solution (I might understand
it but if it's the case it didn't work either).
I'll check the Jira if I see such a problem, but I've done several search and I
didn't see anything like that (one solution might be working with full name:
${artifactId}-${version} as finalname instead of just artifactId, but I would
prefer to avoid that).
And indeed I forget yesterday to put the maven version I'm using.
It's maven 2.0.8.
Tomas Darbois
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Lee Meador
Envoyé : mardi 22 avril 2008 19:34
À : Maven Users List
Objet : Re: Maven Jar plugin 2.0 : ClassPath in manifest
I'm not real familiar with that part of maven, but ...
Did you try adding a to the pom for "test" to give it the name
without the version number included?
Alternatively, there might be a problem inheriting the dependency plugin
configurations in the toto project. You could try copying them from the
parent.
You might also look in the Jira to see if one of the plugins or maven itself
has such a problem already reported. You didn't mention which maven version
you are using.
-- Lee
On Tue, Apr 22, 2008 at 3:30 AM, Thomas Darbois <[EMAIL PROTECTED]>
wrote:
> Hello
>
> I'm having trouble with a multi module project that I m working on.
>
>
> I need a class path inside the manifest of the built jar (plugin maven jar
> and configuration true in my parent pom defined
> in pluginManagement).
>
> The classpath is perfectly formatted when I'm running the project from the
> parent pom, but when I'm running maven from one of the module the class path
> is not well formatted: it add a version tag at the end of the name of the
> library the module depends on.
>
> Example:
>
>
>
> .
>
> |-- pom.xml
>
> |
>
> |-- test
>
> | `-- pom.xml
>
> `-- toto
>
> `-- pom.xml
>
>
> A module toto (packaging: jar, version: 0.1) dependending on an other
> module test (packaging: jar, version: 0.1) both are called by the pom parent
> (packaging: pom, version: 0.1) using and both are inheriting from
> him
> (parentcom.edifixio.sample0.1)=>
> fully project inheritance and aggregation.
>
> The parent pom.xml look likes:
>
>
> 4.0.0
> com.edifixio.sample
> parent
> 0.1
> pom
>
>toto
>test
>
>
>${artifactId}
>
>
> org.apache.maven.plugins
> maven-jar-plugin
> 2.0
>
>
>
>
> true
>
> ${mainClass}
>
>
>
>
>
> compile
>
> jar
>
>
>
>
>
> org.apache.maven.plugins
>
> maven-dependency-plugin
>
>
>
> copy
>
RE: Maven Jar plugin 2.0 : ClassPath in manifest
Well i ve found the Jira that is linked to that problem :
Tomas Darbois
Edifixio Grenoble - Projet ScorWare
04 76 29 89 27
[EMAIL PROTECTED]
-Message d'origine-
De : Thomas Darbois [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 23 avril 2008 10:10
À : Maven Users List
Objet : RE: Maven Jar plugin 2.0 : ClassPath in manifest
Thanks for replying :)
I've tried to put to the pom for test, it didn't change anything. I
ve check the exported-pom and indeed the tag was already set to
${artifactId} even without adding your suggestion (it
inherits that part of the build from his parent pom). It seems that he doesn't
read finalName tag in the exported-pom(s) that are inside the jar of his
dependencies, but when you are generating the entire modules from the parent
module, it keeps in memory all their finalname.
I don't know what you mean with your alternative solution (I might understand
it but if it's the case it didn't work either).
I'll check the Jira if I see such a problem, but I've done several search and I
didn't see anything like that (one solution might be working with full name:
${artifactId}-${version} as finalname instead of just artifactId, but I would
prefer to avoid that).
And indeed I forget yesterday to put the maven version I'm using.
It's maven 2.0.8.
Tomas Darbois
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Lee Meador
Envoyé : mardi 22 avril 2008 19:34
À : Maven Users List
Objet : Re: Maven Jar plugin 2.0 : ClassPath in manifest
I'm not real familiar with that part of maven, but ...
Did you try adding a to the pom for "test" to give it the name
without the version number included?
Alternatively, there might be a problem inheriting the dependency plugin
configurations in the toto project. You could try copying them from the
parent.
You might also look in the Jira to see if one of the plugins or maven itself
has such a problem already reported. You didn't mention which maven version
you are using.
-- Lee
On Tue, Apr 22, 2008 at 3:30 AM, Thomas Darbois <[EMAIL PROTECTED]>
wrote:
> Hello
>
> I'm having trouble with a multi module project that I m working on.
>
>
> I need a class path inside the manifest of the built jar (plugin maven jar
> and configuration true in my parent pom defined
> in pluginManagement).
>
> The classpath is perfectly formatted when I'm running the project from the
> parent pom, but when I'm running maven from one of the module the class path
> is not well formatted: it add a version tag at the end of the name of the
> library the module depends on.
>
> Example:
>
>
>
> .
>
> |-- pom.xml
>
> |
>
> |-- test
>
> | `-- pom.xml
>
> `-- toto
>
> `-- pom.xml
>
>
> A module toto (packaging: jar, version: 0.1) dependending on an other
> module test (packaging: jar, version: 0.1) both are called by the pom parent
> (packaging: pom, version: 0.1) using and both are inheriting from
> him
> (parentcom.edifixio.sample0.1)=>
> fully project inheritance and aggregation.
>
> The parent pom.xml look likes:
>
>
> 4.0.0
> com.edifixio.sample
> parent
> 0.1
> pom
>
>toto
>test
>
>
>${artifactId}
>
>
> org.apache.maven.plugins
> maven-jar-plugin
> 2.0
>
>
>
>
> true
>
> ${mainClass}
>
>
>
>
>
> compile
>
> jar
>
>
>
>
>
> org.apache.maven.plugins
>
> maven-dependency-plugin
>
>
>
> copy
> install
>
>copy
>
>
>
>
RE: Maven Jar plugin 2.0 : ClassPath in manifest
Thanks for replying :)
I've tried to put to the pom for test, it didn't change anything. I
ve check the exported-pom and indeed the tag was already set to
${artifactId} even without adding your suggestion (it
inherits that part of the build from his parent pom). It seems that he doesn't
read finalName tag in the exported-pom(s) that are inside the jar of his
dependencies, but when you are generating the entire modules from the parent
module, it keeps in memory all their finalname.
I don't know what you mean with your alternative solution (I might understand
it but if it's the case it didn't work either).
I'll check the Jira if I see such a problem, but I've done several search and I
didn't see anything like that (one solution might be working with full name:
${artifactId}-${version} as finalname instead of just artifactId, but I would
prefer to avoid that).
And indeed I forget yesterday to put the maven version I'm using.
It's maven 2.0.8.
Tomas Darbois
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Lee Meador
Envoyé : mardi 22 avril 2008 19:34
À : Maven Users List
Objet : Re: Maven Jar plugin 2.0 : ClassPath in manifest
I'm not real familiar with that part of maven, but ...
Did you try adding a to the pom for "test" to give it the name
without the version number included?
Alternatively, there might be a problem inheriting the dependency plugin
configurations in the toto project. You could try copying them from the
parent.
You might also look in the Jira to see if one of the plugins or maven itself
has such a problem already reported. You didn't mention which maven version
you are using.
-- Lee
On Tue, Apr 22, 2008 at 3:30 AM, Thomas Darbois <[EMAIL PROTECTED]>
wrote:
> Hello
>
> I'm having trouble with a multi module project that I m working on.
>
>
> I need a class path inside the manifest of the built jar (plugin maven jar
> and configuration true in my parent pom defined
> in pluginManagement).
>
> The classpath is perfectly formatted when I'm running the project from the
> parent pom, but when I'm running maven from one of the module the class path
> is not well formatted: it add a version tag at the end of the name of the
> library the module depends on.
>
> Example:
>
>
>
> .
>
> |-- pom.xml
>
> |
>
> |-- test
>
> | `-- pom.xml
>
> `-- toto
>
> `-- pom.xml
>
>
> A module toto (packaging: jar, version: 0.1) dependending on an other
> module test (packaging: jar, version: 0.1) both are called by the pom parent
> (packaging: pom, version: 0.1) using and both are inheriting from
> him
> (parentcom.edifixio.sample0.1)=>
> fully project inheritance and aggregation.
>
> The parent pom.xml look likes:
>
>
> 4.0.0
> com.edifixio.sample
> parent
> 0.1
> pom
>
>toto
>test
>
>
>${artifactId}
>
>
> org.apache.maven.plugins
> maven-jar-plugin
> 2.0
>
>
>
>
> true
>
> ${mainClass}
>
>
>
>
>
> compile
>
> jar
>
>
>
>
>
> org.apache.maven.plugins
>
> maven-dependency-plugin
>
>
>
> copy
> install
>
>copy
>
>
>
>
>
>
> ${project.groupId}
>
>
>
> ${project.artifactId}
>
&
Re: Maven Jar plugin 2.0 : ClassPath in manifest
I'm not real familiar with that part of maven, but ...
Did you try adding a to the pom for "test" to give it the name
without the version number included?
Alternatively, there might be a problem inheriting the dependency plugin
configurations in the toto project. You could try copying them from the
parent.
You might also look in the Jira to see if one of the plugins or maven itself
has such a problem already reported. You didn't mention which maven version
you are using.
-- Lee
On Tue, Apr 22, 2008 at 3:30 AM, Thomas Darbois <[EMAIL PROTECTED]>
wrote:
> Hello
>
> I'm having trouble with a multi module project that I m working on.
>
>
> I need a class path inside the manifest of the built jar (plugin maven jar
> and configuration true in my parent pom defined
> in pluginManagement).
>
> The classpath is perfectly formatted when I'm running the project from the
> parent pom, but when I'm running maven from one of the module the class path
> is not well formatted: it add a version tag at the end of the name of the
> library the module depends on.
>
> Example:
>
>
>
> .
>
> |-- pom.xml
>
> |
>
> |-- test
>
> | `-- pom.xml
>
> `-- toto
>
> `-- pom.xml
>
>
> A module toto (packaging: jar, version: 0.1) dependending on an other
> module test (packaging: jar, version: 0.1) both are called by the pom parent
> (packaging: pom, version: 0.1) using and both are inheriting from
> him
> (parentcom.edifixio.sample0.1)=>
> fully project inheritance and aggregation.
>
> The parent pom.xml look likes:
>
>
> 4.0.0
> com.edifixio.sample
> parent
> 0.1
> pom
>
>toto
>test
>
>
>${artifactId}
>
>
> org.apache.maven.plugins
> maven-jar-plugin
> 2.0
>
>
>
>
> true
>
> ${mainClass}
>
>
>
>
>
> compile
>
> jar
>
>
>
>
>
> org.apache.maven.plugins
>
> maven-dependency-plugin
>
>
>
> copy
> install
>
>copy
>
>
>
>
>
>
> ${project.groupId}
>
>
>
> ${project.artifactId}
>
>
>
> ${project.version}
>
>
> true
>
>
> ${project.packaging}
>
>
>
> ${artifactId}.${project.packaging}
>
>
>
>
> ${projectOutput}
>
>
>
>
> copy-dependencies
> install
>
>
> copy-dependencies
>
>
>
> true
>
>${projectOutput}
>
>
> provided
>
>
>
>
>
>
>
>
>
>
>
> The directory test contains a pom.xml :
>
>
>
>com.edifixio.sample
>parent
>0.1
>
> 4.0.0
>
>com.edifixio.sample
>
>
Re: maven-jar-plugin question
"Wendy Smoak" <[EMAIL PROTECTED]> wrote on 03/01/2008 09:54:25 PM: > On Sat, Mar 1, 2008 at 7:50 PM, <[EMAIL PROTECTED]> wrote: > > The following POM works as expected when run by itself (it uses > > org.apache.maven.plugins:maven-jar-plugin:2.1:jar) but when run as part of > > a multi-module build it uses > > org.apache.maven.plugins:maven-jar-plugin:2.2:jar. Does anyone have any > > suggestions as to why this happens and how I can resolve it? > > Try putting the maven-jar-plugin declaration in the parent pom, > probably in . > > I could be wrong, but I don't think you can use different versions of > the same plugin in the same build. > I suspect you're right, and it would make sense to cahce them. However, I can't use 2.1 exclusively either. So I'll probably bind something to add an empty file to the generate-resources phase, and another one to remove it in the verify phase. Thanks for the rapid response, especially on a Saturday night! Robert Egan -- 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: maven-jar-plugin question
On Sat, Mar 1, 2008 at 7:50 PM, <[EMAIL PROTECTED]> wrote: > The following POM works as expected when run by itself (it uses > org.apache.maven.plugins:maven-jar-plugin:2.1:jar) but when run as part of > a multi-module build it uses > org.apache.maven.plugins:maven-jar-plugin:2.2:jar. Does anyone have any > suggestions as to why this happens and how I can resolve it? Try putting the maven-jar-plugin declaration in the parent pom, probably in . I could be wrong, but I don't think you can use different versions of the same plugin in the same build. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven jar-plugin
Thanks Wendy. I was using the version 2.0 and the fix was available in the version 2.1. I also tried by not giving the version number so that maven can use the latest version but it was giving errors. Now, everything is fine. Regards, Shakun Wendy Smoak wrote: On Wed, Feb 27, 2008 at 5:08 AM, Shakun Gupta <[EMAIL PROTECTED]> wrote: I am using Maven 2, and i added the configuration of jar-plugin and war-plugin. I am able to assemble the war at a different place using outputDirectory property. But, this does not work with jar-plugin. I have read in the forums that this is an issue with the jar plugin and this will be updated in JIRA. May i know if my understanding is correct. And if yes, then which version of the jar-plugin contains this fix. You can search JIRA for the issue and find out the fix version (if any): http://jira.codehaus.org/browse/MJAR Then check to see what's been released: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-jar-plugin/ Is it this one? http://jira.codehaus.org/browse/MJAR-16
Re: Maven jar-plugin
On Wed, Feb 27, 2008 at 5:08 AM, Shakun Gupta <[EMAIL PROTECTED]> wrote: > I am using Maven 2, and i added the configuration of jar-plugin and > war-plugin. I am able to assemble the war at a different place using > outputDirectory property. But, this does not work with jar-plugin. I > have read in the forums that this is an issue with the jar plugin and > this will be updated in JIRA. May i know if my understanding is correct. > And if yes, then which version of the jar-plugin contains this fix. You can search JIRA for the issue and find out the fix version (if any): http://jira.codehaus.org/browse/MJAR Then check to see what's been released: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-jar-plugin/ Is it this one? http://jira.codehaus.org/browse/MJAR-16 -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven-jar-plugin
please ignore this thread - issue resolved Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven-jar-plugin customization
maybe you should use maven-assembly-plugin http://maven.apache.org/plugins/maven-assembly-plugin/ Rex On Feb 19, 2008 11:53 AM, Julien FOROT <[EMAIL PROTECTED]> wrote: > Hi ! > > I want to make 2different jars from the same source folder. So I made > this structure : > > - jar >-- pom.xml >-- src >-- heavyJar >--- pom.xml >-- lightJar > --- pom.xml > > I want that the heavy and light Jar used the folder src as sourceFolder. > The light Jar has to exclude some classes. I tried to put on the heavy's > pom something;ike that : > >org.apache.maven.plugins >maven-jar-plugin > >../src/ > > > But my jars are always empty (no .class on it) : [WARNING] JAR will be > empty - no content was marked for inclusion! > > How can I do that ? I hope I'm enough clear.. Thanks for your help ! > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: Maven-jar-plugin customization
Julien FOROT schrieb: > Hi ! > > I want to make 2different jars from the same source folder. So I made > this structure : > > - jar >-- pom.xml >-- src >-- heavyJar >--- pom.xml >-- lightJar > --- pom.xml > > I want that the heavy and light Jar used the folder src as > sourceFolder. The light Jar has to exclude some classes. I tried to > put on the heavy's pom something;ike that : > >org.apache.maven.plugins >maven-jar-plugin > >../src/ > > > But my jars are always empty (no .class on it) : [WARNING] JAR will be > empty - no content was marked for inclusion! > > How can I do that ? I hope I'm enough clear.. Thanks for your help ! I don't think you can reference a source directory outside of a module itself. Even if it is possible, it's not very elegant. I think the easiest solution would be to have a single project. One of your jars (eg the "heavy") is the primary artifact; set things up so that is generated, just like a normal project. Then add an extra execution of the maven-jar-plugin which simply has a few extra tags, and sets light. If you really do want two separate projects, then I suggest having the project with the source generate a normal jar, and have the other two projects use the maven-dependency-plugin to download the jar, unpack it, then repack it with just the desired classes. The project with source would be a "sibling" rather than a "parent" project. As always with Maven, it is best to think as if each mvn module was hosted by a different company; don't try to peek into the internals of other modules but instead just depend upon the artifacts that each produces. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: MAVEN-JAR-PLUGIN
Forget this last post. I was trying to include integration tests in the
same module and that was a bad idea.
-Original Message-
From: Matthew Shaw [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 13 February 2008 11:37 AM
To: Maven Users List
Subject: MAVEN-JAR-PLUGIN
Hi there,
I am trying to configure the maven-jar-plugin test-jar goal to use a
different source folder for the test classes. Here is my config in the
build section of my pom. It does not seem to be having any effect.
org.apache.maven.plugins
maven-jar-plugin
test-jar
${basedir}/src/test-integ
This email and associated attachments may contain confidential and
privileged CITEC information that is provided solely for the use of the
intended addressee. Views and opinions expressed in this email are those
of the individual sender and are not necessarily the views and opinions
of CITEC unless the sender expressly states that such views and opinions
are those of CITEC. The privilege and confidentiality associated with
this email and attachments will not be waived, lost or rescinded by
reason of mistaken delivery. Should you receive this email by mistake,
please notify the sender by return email then delete the email from your
computer system. You must not use, copy, modify, print, or distribute
the email or the information and attachments contained within same to
any third party. CITEC does not accept any liability in respect of
viruses or computer problems experienced by the recipient through access
gained to this email and its attachments.
This email has been scanned for viruses by the CITEC Email Anti-Virus
service powered by IronPort(r)
This email and associated attachments may contain confidential and privileged
CITEC information that is provided solely for the use of the intended
addressee. Views and opinions expressed in this email are those of the
individual sender and are not necessarily the views and opinions of CITEC
unless the sender expressly states that such views and opinions are those of
CITEC. The privilege and confidentiality associated with this email and
attachments will not be waived, lost or rescinded by reason of mistaken
delivery. Should you receive this email by mistake, please notify the sender by
return email then delete the email from your computer system. You must not use,
copy, modify, print, or distribute the email or the information and attachments
contained within same to any third party. CITEC does not accept any liability
in respect of viruses or computer problems experienced by the recipient through
access gained to this email and its attachments.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin location
All Maven plugins are hosted in the publicly accessible Central site -- http://repo1.maven.org. It seems like you have something weird going on in your network, most Maven users including myself have no such problems. Wayne On 1/28/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > better! But I cant get the next (maven-resources)-plugin? > > $AXIS_HOME/modules>mvn -U install > [INFO] Scanning for projects... > [INFO] - > --- > [INFO] Building Maven Default Project > [INFO]task-segment: [install] > [INFO] - > --- > [INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking > for up > dates from central > [WARNING] repository metadata for: 'artifact > org.apache.maven.plugins:maven-reso > urces-plugin' could not be retrieved from repository: central due to an > error: Error transferring file > > what I need is a publicly accessible folder for maven plugins.. > Any other suggestions? > > Thanks Wayne! > Martin-- > - Original Message - > Wrom: CONEUQZAAFXISHJEXXIMQZUIVOTQNQEM > To: "Maven Users List" > Sent: Monday, January 28, 2008 8:06 PM > Subject: Re: maven-jar-plugin location > > > > Try mvn -U to force Maven to check for plugin updates. > > > > Wayne > > > > On 1/28/08, Martin Gainty <[EMAIL PROTECTED]> wrote: > > > I see the following error while building with maven-2.0.8 > > > > > > [INFO] The plugin 'org.apache.maven.plugins:maven-jar-plugin' does not > exist or > > > no valid version could be found > > > > [INFO] - > --- > > > [INFO] Trace > > > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-jar-plugin' does not exist or no valid > version could be found > > > > > > Any ideas where maven determines locatations for plugins for build > environment? > > > > > > Thanks > > > 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: maven-jar-plugin location
better! But I cant get the next (maven-resources)-plugin? $AXIS_HOME/modules>mvn -U install [INFO] Scanning for projects... [INFO] - --- [INFO] Building Maven Default Project [INFO]task-segment: [install] [INFO] - --- [INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking for up dates from central [WARNING] repository metadata for: 'artifact org.apache.maven.plugins:maven-reso urces-plugin' could not be retrieved from repository: central due to an error: Error transferring file what I need is a publicly accessible folder for maven plugins.. Any other suggestions? Thanks Wayne! Martin-- - Original Message - Wrom: CONEUQZAAFXISHJEXXIMQZUIVOTQNQEM To: "Maven Users List" Sent: Monday, January 28, 2008 8:06 PM Subject: Re: maven-jar-plugin location > Try mvn -U to force Maven to check for plugin updates. > > Wayne > > On 1/28/08, Martin Gainty <[EMAIL PROTECTED]> wrote: > > I see the following error while building with maven-2.0.8 > > > > [INFO] The plugin 'org.apache.maven.plugins:maven-jar-plugin' does not exist or > > no valid version could be found > > [INFO] - --- > > [INFO] Trace > > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-jar-plugin' does not exist or no valid version could be found > > > > Any ideas where maven determines locatations for plugins for build environment? > > > > Thanks > > 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: maven-jar-plugin location
Try mvn -U to force Maven to check for plugin updates. Wayne On 1/28/08, Martin Gainty <[EMAIL PROTECTED]> wrote: > I see the following error while building with maven-2.0.8 > > [INFO] The plugin 'org.apache.maven.plugins:maven-jar-plugin' does not exist > or > no valid version could be found > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > 'org.apache.maven.plugins:maven-jar-plugin' does not exist or no valid > version could be found > > Any ideas where maven determines locatations for plugins for build > environment? > > Thanks > Martin- > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin and maven-ejb-plugin / generate manifest if not present
Maybe you could set the settings to
target/resources/META-INF/MANIFEST.MF (or whatever the right path is), and then
use maven filtering to transform the "template" in src/main/resources into the
form you want.
Regards,
Simon
Julien CARSIQUE <[EMAIL PROTECTED]> schrieb:
> Sorry, I didn't list all the tests I've done.
> I tried what you suggest, the result is a jar containing a new manifest
> with the wanted manifest entries from pom.xml but without all the
> content of the manifest present in src/main/...
>
> While doing this, I'm trying to manage with the buildnumber plugin in
> order to have manifest containing unique Bundle-Version; which is
> required by Eclipse when some of our artifacts are used as plugins.
>
> Being able to add entries from pom to an existing (or not) manifest
> would be very useful for this.
>
> Wayne Fay a écrit :
> > Try removing the entry and see what happens when
> > there's a file present in that location, and what happens when there's
> > not (check target to see what ends up in the JAR). By default, Maven
> > looks for the file in that location, and uses it if its there, or
> > generates one if there's not.
> >
> > I'm honestly not sure that adding a manifestEntry will work when the
> > file is present, but sounds like another thing to try while you're
> > doing the tests I suggested above.
> >
> > Wayne
> >
> > On 1/24/08, Julien CARSIQUE <[EMAIL PROTECTED]> wrote:
> >
> >> Hello,
> >>
> >> I would like the plugin to use the given manifest, if present, and add
> >> some properties; and to generate the manifest if it doesn't exist.
> >> Is it possible ?
> >>
> >> Here is my common configuration in the parent pom :
> >>
> >> org.apache.maven.plugins
> >> maven-jar-plugin
> >> 2.2
> >>
> >>
> >>
> >> src/main/resources/META-INF/MANIFEST.MF
> >>
> >> ${pom.version}
> >>
> >>
> >>
> >>
> >>
> >> For now, if there's no manifest in the specified place, I got this error :
> >> [ERROR] BUILD ERROR
> >> [INFO]
> >>
> >> [INFO] Error assembling JAR
> >>
> >> Embedded error: Manifest file:
> >> .../src/main/resources/META-INF/MANIFEST.MF does not exist.
> >>
> >> Of course, the aim is to have a generic configuration, in order not
> >> having to specify for each artifact if there's a manifest, or none.
> >>
> >>
> >> Thanks,
> >> Julien
> >>
> >> --
> >> Julien CARSIQUE, Nuxeo (Paris, France)
> >> Open Source Enterprise Content Management - http://www.nuxeo.org/
> >> Nuxeo EP 5: extensible, Java EE and standards based ECM Platform
> >> http://www.nuxeo.com/ - Tel: +33 1 40 33 79 87
> >>
> >>
> >> -
> >> 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]
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin and maven-ejb-plugin / generate manifest if not present
Sorry, I didn't list all the tests I've done.
I tried what you suggest, the result is a jar containing a new manifest
with the wanted manifest entries from pom.xml but without all the
content of the manifest present in src/main/...
While doing this, I'm trying to manage with the buildnumber plugin in
order to have manifest containing unique Bundle-Version; which is
required by Eclipse when some of our artifacts are used as plugins.
Being able to add entries from pom to an existing (or not) manifest
would be very useful for this.
Wayne Fay a écrit :
Try removing the entry and see what happens when
there's a file present in that location, and what happens when there's
not (check target to see what ends up in the JAR). By default, Maven
looks for the file in that location, and uses it if its there, or
generates one if there's not.
I'm honestly not sure that adding a manifestEntry will work when the
file is present, but sounds like another thing to try while you're
doing the tests I suggested above.
Wayne
On 1/24/08, Julien CARSIQUE <[EMAIL PROTECTED]> wrote:
Hello,
I would like the plugin to use the given manifest, if present, and add
some properties; and to generate the manifest if it doesn't exist.
Is it possible ?
Here is my common configuration in the parent pom :
org.apache.maven.plugins
maven-jar-plugin
2.2
src/main/resources/META-INF/MANIFEST.MF
${pom.version}
For now, if there's no manifest in the specified place, I got this error :
[ERROR] BUILD ERROR
[INFO]
[INFO] Error assembling JAR
Embedded error: Manifest file:
.../src/main/resources/META-INF/MANIFEST.MF does not exist.
Of course, the aim is to have a generic configuration, in order not
having to specify for each artifact if there's a manifest, or none.
Thanks,
Julien
--
Julien CARSIQUE, Nuxeo (Paris, France)
Open Source Enterprise Content Management - http://www.nuxeo.org/
Nuxeo EP 5: extensible, Java EE and standards based ECM Platform
http://www.nuxeo.com/ - Tel: +33 1 40 33 79 87
-
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: maven-jar-plugin and maven-ejb-plugin / generate manifest if not present
Try removing the entry and see what happens when
there's a file present in that location, and what happens when there's
not (check target to see what ends up in the JAR). By default, Maven
looks for the file in that location, and uses it if its there, or
generates one if there's not.
I'm honestly not sure that adding a manifestEntry will work when the
file is present, but sounds like another thing to try while you're
doing the tests I suggested above.
Wayne
On 1/24/08, Julien CARSIQUE <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I would like the plugin to use the given manifest, if present, and add
> some properties; and to generate the manifest if it doesn't exist.
> Is it possible ?
>
> Here is my common configuration in the parent pom :
>
> org.apache.maven.plugins
> maven-jar-plugin
> 2.2
>
>
>
> src/main/resources/META-INF/MANIFEST.MF
>
> ${pom.version}
>
>
>
>
>
> For now, if there's no manifest in the specified place, I got this error :
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error assembling JAR
>
> Embedded error: Manifest file:
> .../src/main/resources/META-INF/MANIFEST.MF does not exist.
>
> Of course, the aim is to have a generic configuration, in order not
> having to specify for each artifact if there's a manifest, or none.
>
>
> Thanks,
> Julien
>
> --
> Julien CARSIQUE, Nuxeo (Paris, France)
> Open Source Enterprise Content Management - http://www.nuxeo.org/
> Nuxeo EP 5: extensible, Java EE and standards based ECM Platform
> http://www.nuxeo.com/ - Tel: +33 1 40 33 79 87
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin not working
It's here:
http://jira.codehaus.org/browse/MJAR-30
pdelaney wrote:
Hello;
I am building an executable jar file and I am trying to remove my
database.properties file from the jar because I want to control the
properties outside of the jar file.
In my build I execute mvn package I have the maven-dependency-plugin part
of the lifecycle to get all of my .class files into the target/classes
directory. In that directory is my database.properties file.
Next the directory basically gets jared up via the maven-jar-plugin. I
cannot seem to get the jar plugin to remove or not put the
database.properties into the jar. Here is my jar plugin definition. Any
help would be appreciated.
org.apache.maven.plugins
maven-jar-plugin
true
com.putnam.fams.batch.BatchProcessMain
${project.build.directory}
junit
**/database.properties
The database.properties in the target/classes/database.properties directory
before jar happens.
In the excludes I've tried
**/database.properties
**/*database.properties
database.properties
Nothing seems to work. Is this a bug that anyone knows about ?
Thanks
Peter
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin - manifest customization
Thanks for you reply. 2007/9/25, Wayne Fay <[EMAIL PROTECTED]>: > > The other approach of course is to change your JAVA_HOME and use the > jdk4 compiler to run your Java process. Then everything will match up > and you won't need any extra configuration. > > Wayne > > On 9/25/07, Tim Kettler <[EMAIL PROTECTED]> wrote: > > Hi, > > > > this is because the compilation of the sources (compiler-plugin) and the > > packaging (jar-plugin) is done in two steps. Even if you fork the > > compiler, the jar-plugin execution isn't forked and thus runs under the > > java version you invoked maven with. > > > > You can override the maven generated entry like this: > > > > > > org.apache.maven.plugins > > maven-jar-plugin > > > > > > > >1.4.2 > > > > > > > > > > > > -Tim > > > > Guillaume Boucherie schrieb: > > > My problem is not on jdk version. > > > I just want to test maven. > > > And when you use the fork mode in compiler the jdk's manifest entry is > not > > > correct. > > > So I want to know how to get the correct value in manifest. > > > Thanks > > > > > > > > > - > > 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] > > -- CletteBou clettebou.miniville.fr
Re: maven-jar-plugin - manifest customization
The other approach of course is to change your JAVA_HOME and use the jdk4 compiler to run your Java process. Then everything will match up and you won't need any extra configuration. Wayne On 9/25/07, Tim Kettler <[EMAIL PROTECTED]> wrote: > Hi, > > this is because the compilation of the sources (compiler-plugin) and the > packaging (jar-plugin) is done in two steps. Even if you fork the > compiler, the jar-plugin execution isn't forked and thus runs under the > java version you invoked maven with. > > You can override the maven generated entry like this: > > > org.apache.maven.plugins > maven-jar-plugin > > > >1.4.2 > > > > > > -Tim > > Guillaume Boucherie schrieb: > > My problem is not on jdk version. > > I just want to test maven. > > And when you use the fork mode in compiler the jdk's manifest entry is not > > correct. > > So I want to know how to get the correct value in manifest. > > Thanks > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin - manifest customization
Hi, this is because the compilation of the sources (compiler-plugin) and the packaging (jar-plugin) is done in two steps. Even if you fork the compiler, the jar-plugin execution isn't forked and thus runs under the java version you invoked maven with. You can override the maven generated entry like this: org.apache.maven.plugins maven-jar-plugin 1.4.2 -Tim Guillaume Boucherie schrieb: My problem is not on jdk version. I just want to test maven. And when you use the fork mode in compiler the jdk's manifest entry is not correct. So I want to know how to get the correct value in manifest. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin - manifest customization
My problem is not on jdk version. I just want to test maven. And when you use the fork mode in compiler the jdk's manifest entry is not correct. So I want to know how to get the correct value in manifest. Thanks -- CletteBou clettebou.miniville.fr 2007/9/25, Jim Sellers <[EMAIL PROTECTED]>: > > Do you just need to compile to 1.4 or do you actually need to use a > different jdk (sun vs ibm)? > > If you just need 1.4, this might help: > > http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html > > Jim > > > On 9/25/07, Guillaume Boucherie <[EMAIL PROTECTED]> wrote: > > > > Hi, > > On my system I have two java installed : > > JAVA_HOME that point to a jdk1.5 > > JAVA_1_4_HOME that point to a jdk1.4 > > So when I run maven it use jdk1.5 and in my project I configure > > maven-compiler-plugin to use my jdk1.4. > > But when maven create the manifest for my project he use jdk1.5 for the > > Build-Jdk entry. > > How can I customize the manifest to have the correct jdk version in ? > > Thanks > > > > -- > > CletteBou > > clettebou.miniville.fr > > >
Re: maven-jar-plugin - manifest customization
Do you just need to compile to 1.4 or do you actually need to use a different jdk (sun vs ibm)? If you just need 1.4, this might help: http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html Jim On 9/25/07, Guillaume Boucherie <[EMAIL PROTECTED]> wrote: > > Hi, > On my system I have two java installed : > JAVA_HOME that point to a jdk1.5 > JAVA_1_4_HOME that point to a jdk1.4 > So when I run maven it use jdk1.5 and in my project I configure > maven-compiler-plugin to use my jdk1.4. > But when maven create the manifest for my project he use jdk1.5 for the > Build-Jdk entry. > How can I customize the manifest to have the correct jdk version in ? > Thanks > > -- > CletteBou > clettebou.miniville.fr >
Re: maven-jar-plugin: how to avoid conflicts in
Vote for http://jira.codehaus.org/browse/MJAR-82 :) With kind regards, Geoffrey De Smet Tim Kettler schreef: This is currently not possible with the jar-plugin , but it sounds like a useful feature. The assembly-plugin has an option for dependency-sets called 'outputFileNameMapping' [1] where you can specify the format of the filenames. Something similar would be useful for the format of the classpath-entries in the jar manifest, too. Going forward, I would post a feature request in jira [2]. You could even start looking into implementing this yourself and contributing it back to the community. After all, it seems all the pieces are there: The jar-plugin has the general infrastructure for writing the dependencies to the classplath-entry and the assembly-plugin has code for creating filenames using a given pattern. All that's needed is to incorporate the code from the assembly-plugin in the jar plugin. -Tim [1] http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet [2] http://jira.codehaus.org/browse/MJAR aldana schrieb: yes, for a workaround i did this too. but hoped there would be a tweak in maven-jar-plugin, so artifactId could standalone because information of a.b.c.d is already provided. this way i could avoid duplication. Michael McCallum-3 wrote: i name my projects a.b.c a.b.c.d that way all the aggregations never have clashes... I only wish library providers would to the same... it seems all the simple things are overlooked On Monday 27 August 2007 22:25, aldana wrote: hi, maven amongst others is using groupId to avoid name clashes between libraries (a:x.jar is different to b:x.jar). now the problem arises when adding Classpath to MANIFEST.MF with following: org.apache.maven.plugins maven-jar-plugin true lib with addClasspath in MANIFEST.MF it is unclear wheter to reference a:x.jar or b:x.jar because there is only one jar listed -> Class-Path: lib/x.jar how is it possible to tell the MANIFEST.MF to include the groupId too? Something like Class-Path: lib/a-x.jar lib/b-x.jar. thanks in advance -- Michael McCallum Enterprise Engineer mailto:[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: maven-jar-plugin: how to avoid conflicts in
alright, sounds like a good idea. just wanted to ensure that it is not a configuration error from my side. Tim Kettler wrote: > > This is currently not possible with the jar-plugin , but it sounds like > a useful feature. The assembly-plugin has an option for dependency-sets > called 'outputFileNameMapping' [1] where you can specify the format of > the filenames. Something similar would be useful for the format of the > classpath-entries in the jar manifest, too. > > Going forward, I would post a feature request in jira [2]. > > You could even start looking into implementing this yourself and > contributing it back to the community. After all, it seems all the > pieces are there: The jar-plugin has the general infrastructure for > writing the dependencies to the classplath-entry and the assembly-plugin > has code for creating filenames using a given pattern. All that's needed > is to incorporate the code from the assembly-plugin in the jar plugin. > > -Tim > > [1] > http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet > [2] http://jira.codehaus.org/browse/MJAR > > aldana schrieb: >> yes, for a workaround i did this too. but hoped there would be a tweak in >> maven-jar-plugin, so artifactId could standalone because information of >> a.b.c.d is already provided. this way i could avoid duplication. >> >> >> Michael McCallum-3 wrote: >>> i name my projects >>> >>> a.b.c >>> a.b.c.d >>> >>> that way all the aggregations never have clashes... I only wish library >>> providers would to the same... it seems all the simple things are >>> overlooked >>> >>> On Monday 27 August 2007 22:25, aldana wrote: hi, maven amongst others is using groupId to avoid name clashes between libraries (a:x.jar is different to b:x.jar). now the problem arises when adding Classpath to MANIFEST.MF with following: org.apache.maven.plugins maven-jar-plugin true lib with addClasspath in MANIFEST.MF it is unclear wheter to reference a:x.jar or b:x.jar because there is only one jar listed -> Class-Path: lib/x.jar how is it possible to tell the MANIFEST.MF to include the groupId too? Something like Class-Path: lib/a-x.jar lib/b-x.jar. thanks in advance >>> -- >>> Michael McCallum >>> Enterprise Engineer >>> mailto:[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] > > > -- View this message in context: http://www.nabble.com/maven-jar-plugin%3A-how-to-avoid-conflicts-in-%3CaddClasspath%3E-tf4334430s177.html#a12345658 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-jar-plugin: how to avoid conflicts in
This is currently not possible with the jar-plugin , but it sounds like a useful feature. The assembly-plugin has an option for dependency-sets called 'outputFileNameMapping' [1] where you can specify the format of the filenames. Something similar would be useful for the format of the classpath-entries in the jar manifest, too. Going forward, I would post a feature request in jira [2]. You could even start looking into implementing this yourself and contributing it back to the community. After all, it seems all the pieces are there: The jar-plugin has the general infrastructure for writing the dependencies to the classplath-entry and the assembly-plugin has code for creating filenames using a given pattern. All that's needed is to incorporate the code from the assembly-plugin in the jar plugin. -Tim [1] http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet [2] http://jira.codehaus.org/browse/MJAR aldana schrieb: yes, for a workaround i did this too. but hoped there would be a tweak in maven-jar-plugin, so artifactId could standalone because information of a.b.c.d is already provided. this way i could avoid duplication. Michael McCallum-3 wrote: i name my projects a.b.c a.b.c.d that way all the aggregations never have clashes... I only wish library providers would to the same... it seems all the simple things are overlooked On Monday 27 August 2007 22:25, aldana wrote: hi, maven amongst others is using groupId to avoid name clashes between libraries (a:x.jar is different to b:x.jar). now the problem arises when adding Classpath to MANIFEST.MF with following: org.apache.maven.plugins maven-jar-plugin true lib with addClasspath in MANIFEST.MF it is unclear wheter to reference a:x.jar or b:x.jar because there is only one jar listed -> Class-Path: lib/x.jar how is it possible to tell the MANIFEST.MF to include the groupId too? Something like Class-Path: lib/a-x.jar lib/b-x.jar. thanks in advance -- Michael McCallum Enterprise Engineer mailto:[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: maven-jar-plugin: how to avoid conflicts in
yes, for a workaround i did this too. but hoped there would be a tweak in maven-jar-plugin, so artifactId could standalone because information of a.b.c.d is already provided. this way i could avoid duplication. Michael McCallum-3 wrote: > > i name my projects > > a.b.c > a.b.c.d > > that way all the aggregations never have clashes... I only wish library > providers would to the same... it seems all the simple things are > overlooked > > On Monday 27 August 2007 22:25, aldana wrote: >> hi, >> >> maven amongst others is using groupId to avoid name clashes between >> libraries (a:x.jar is different to b:x.jar). >> >> now the problem arises when adding Classpath to MANIFEST.MF with >> following: >> >> >> org.apache.maven.plugins >> maven-jar-plugin >> >> >> >>true >>lib >> >> >> >> >> >> with addClasspath in MANIFEST.MF it is unclear wheter to reference >> a:x.jar >> or b:x.jar because there is only one jar listed -> Class-Path: lib/x.jar >> >> how is it possible to tell the MANIFEST.MF to include the groupId too? >> Something like Class-Path: lib/a-x.jar lib/b-x.jar. >> >> thanks in advance > > -- > Michael McCallum > Enterprise Engineer > mailto:[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-jar-plugin%3A-how-to-avoid-conflicts-in-%3CaddClasspath%3E-tf4334430s177.html#a12344732 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-jar-plugin: how to avoid conflicts in
i name my projects a.b.c a.b.c.d that way all the aggregations never have clashes... I only wish library providers would to the same... it seems all the simple things are overlooked On Monday 27 August 2007 22:25, aldana wrote: > hi, > > maven amongst others is using groupId to avoid name clashes between > libraries (a:x.jar is different to b:x.jar). > > now the problem arises when adding Classpath to MANIFEST.MF with following: > > > org.apache.maven.plugins > maven-jar-plugin > > > >true >lib > > > > > > with addClasspath in MANIFEST.MF it is unclear wheter to reference a:x.jar > or b:x.jar because there is only one jar listed -> Class-Path: lib/x.jar > > how is it possible to tell the MANIFEST.MF to include the groupId too? > Something like Class-Path: lib/a-x.jar lib/b-x.jar. > > thanks in advance -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin index=true ignoring files in META-INF/
On 8/12/07, Greg Morgan <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Zarick Lau wrote: > >> You're probably being bitten by http://jira.codehaus.org/browse/PLXCOMP-10. > > > > Thanks! I believe so !! > > > >> Someone needs to update the maven-jar-plugin/maven-archiver to use a > >> later version of plexus-archiver. > > > > Need to create an issue for this? > > I'd follow the see a problem, own a problem approach. If you leave the > problem in the mailing lists, then it may get missed. You have perfect > justification for a bug report that would speed resolution of the > problem. You're also a motivated user to boot. Issue created: http://jira.codehaus.org/browse/MJAR-79 Best regards, Zarick Lau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin index=true ignoring files in META-INF/
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zarick Lau wrote: >> You're probably being bitten by http://jira.codehaus.org/browse/PLXCOMP-10. > > Thanks! I believe so !! > >> Someone needs to update the maven-jar-plugin/maven-archiver to use a >> later version of plexus-archiver. > > Need to create an issue for this? I'd follow the see a problem, own a problem approach. If you leave the problem in the mailing lists, then it may get missed. You have perfect justification for a bug report that would speed resolution of the problem. You're also a motivated user to boot. Regards, Greg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGvernxyxe5L6mr7IRArdwAJ4qnhpCJdGmbO7AoC7J0goF0lkRTwCgjXXB WDqnavUBgEGrnxuQfoBN4G4= =WA84 -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin index=true ignoring files in META-INF/
On 8/10/07, Max Bowsher <[EMAIL PROTECTED]> wrote: > Zarick Lau wrote: > > Dear users and developers, > > > > I have a module with this files > > /src/main/resources/META-INF/persistence.xml > > /src/main/resources/log4j.xml > > > > In the pom, I have set true for the maven-jar-plugin > > After package as a jar, the log4j.xml is listed but > > META-INF/persistence.xml is not listed in the "META-INF/INDEX.LIST" > > file. > > > > So, my question is, whether put the persistence.xml in the > > /src/main/resources/META-INF/ is a correct and supported way? > > Or I should put these files in some other place? > > You're probably being bitten by http://jira.codehaus.org/browse/PLXCOMP-10. Thanks! I believe so !! > > Someone needs to update the maven-jar-plugin/maven-archiver to use a > later version of plexus-archiver. Need to create an issue for this? Best regards, Zarick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin index=true ignoring files in META-INF/
Zarick Lau wrote: > Dear users and developers, > > I have a module with this files > /src/main/resources/META-INF/persistence.xml > /src/main/resources/log4j.xml > > In the pom, I have set true for the maven-jar-plugin > After package as a jar, the log4j.xml is listed but > META-INF/persistence.xml is not listed in the "META-INF/INDEX.LIST" > file. > > So, my question is, whether put the persistence.xml in the > /src/main/resources/META-INF/ is a correct and supported way? > Or I should put these files in some other place? You're probably being bitten by http://jira.codehaus.org/browse/PLXCOMP-10. Someone needs to update the maven-jar-plugin/maven-archiver to use a later version of plexus-archiver. Max. signature.asc Description: OpenPGP digital signature
Re: maven-jar-plugin wraps manifest.mf line at wrong position
Hi Zhang, All MANIFEST.MF files that contain lines longer than 72 bytes are invalid, according to the Jar Manifest specification. That's why the plugin splits them, which is the only way to create a valid manifest. And no, AFAIK, you can not force the plugin to create invalid manifest files. Here is the specification extract: - Line length: No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE). You can find the spec here: http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Notes on Manifest and Signature Files Cheers Jo On 6/8/07, 張旭 <[EMAIL PROTECTED]> wrote: Dear friends, I have encountered a strange problem when specify custom manifest file when using the maven-jar-plugin. I've a very very long line in the manifest file that maybe have hundreds columns. It seems that the plug-in will automatically wrap the line every 70 cols. Is there a parameter in configuration that can override the default behavior? Thanks in advance.
Re: maven-jar-plugin wraps manifest.mf line at wrong position
On Fri, 2007-06-08 at 16:21 +0800, 張旭 wrote: > Dear friends, > I have encountered a strange problem when specify custom manifest file when > using the maven-jar-plugin. > I've a very very long line in the manifest file that maybe have hundreds > columns. > It seems that the plug-in will automatically wrap the line every 70 cols. > Is there a parameter in configuration that can override the default > behavior? The plugin does the right thing and you really don't want to override that. From the Jar specification: No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE). - Henry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin(?): customized classpath
I had to do this a while back so it might have changed in a more
recent build, but when I had something like this, I just had to
specify my own complete MANIFEST.MF file and tell Maven to use it
instead of generating one. You either took the Maven-generated
Manifest or built your own entirely (at the time).
This sounds like something that could be useful (merging your own
Manifest with the Maven-generated one) so I'd expect its already an
RFE in JIRA and possibly has been implemented in a Snapshot build.
Check JIRA and see what you can find.
Wayne
On 1/12/07, Ján Ďurovec <[EMAIL PROTECTED]> wrote:
Hi!
I would like to create a project with the following structure of the final build
+- conf/
| +-
+- lib/
| +- dep1.jar, dep2.jar
+- myAp.jar
I would like myApp to be able to access the configuration files, which can be manually
achieved by putting "Class-Path: conf/ lib/dep1.jar lib/dep2.jar" into
myApp.jar's manifest.
I have tried putting
maven-jar-plugin
true
lib
${mainclass}
into pom.xml but it only generates the "lib/dep1.jar lib/dep2.jar" part.
Adding
merge/MANITEST.MF
after the element, where the "merge/MANIFEST.MF" file contains only single
line "Class-Path: conf/" caused the whole classpath section to be replaced in the resulting
manifest (i.e. there were no dependencies).
Is there a way how to achieve the desired result using Maven so I do not need to manually
add the "conf/" to the jar's manifest after every build?
Jan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven-jar-plugin: include/exclude functionality?
Another option is to build your subset jars and attach them as artifacts with the build-helper plugin. See: http://www.nabble.com/-maven2--Generating-several-artifacts-per-project- --tf1689630.html#a4630045 Chris Hilton > -Original Message- > From: Denis Cabasson [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 25 July, 2006 02:37 > To: users@maven.apache.org > Subject: Re: maven-jar-plugin: include/exclude functionality? > > > > Simon Kitching-2 wrote: > > > > I need to build 3 jars from the classes created by a > module; a "full" > > jar and two jars that contain subsets of the available classes. > > > > If you need to build 3 different jars (not taking into > account javadoc and sources jar) from a single module, it's > probably that this module should be > 3 different modules :) > > If, for whatever reason, you don't want to split up your > module in 3 different modules, you have to use the assembly > plugin to create "customs" > jars out of your module. > > Denis. > > -- > View this message in context: > http://www.nabble.com/maven-jar-plugin%3A-include-exclude-func tionality--tf1995736.html#a5481135 > Sent from the Maven - Users forum 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: maven-jar-plugin: include/exclude functionality?
Simon Kitching-2 wrote: > > I need to build 3 jars from the classes created by a module; a "full" > jar and two jars that contain subsets of the available classes. > If you need to build 3 different jars (not taking into account javadoc and sources jar) from a single module, it's probably that this module should be 3 different modules :) If, for whatever reason, you don't want to split up your module in 3 different modules, you have to use the assembly plugin to create "customs" jars out of your module. Denis. -- View this message in context: http://www.nabble.com/maven-jar-plugin%3A-include-exclude-functionality--tf1995736.html#a5481135 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven jar plugin documentation
Not sure where on the web you can currently find it, but if you pull down the code from SVN to your local box and then run "mvn site", it should build the SNAPSHOT site on your local box for viewing etc... Wayne On 7/6/06, Sebastien Cesbron <[EMAIL PROTECTED]> wrote: Hi, Is there a place where it is possible to see snapshot documentation ? I search the maven jar plugin last snapshot documentation to see if it is more verbose on jar signing. Thanx Seb - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven jar plugin documentation
On 7/6/06, Sebastien Cesbron <[EMAIL PROTECTED]> wrote: Hi, Is there a place where it is possible to see snapshot documentation ? I search the maven jar plugin last snapshot documentation to see if it is more verbose on jar signing. best is to look at the code... http://svn.apache.org/viewvc/maven/plugins/trunk/maven-jar-plugin/src/main/java/org/apache/maven/plugin/jar/JarSignMojo.java?view=log - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin:2.1-SNAPSHOT
Hi Ben, You can checkout the jar plugin from svn and install it locally. Here's the url: http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jar-plugin Thanks, Odea ben short wrote: I get the following error while trying to build the maven repository manager. Any ideas where i can get the snapshot? [INFO] [INFO] snapshot org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT:checking for updates from apache.snapshots [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.plugins-DartifactId=maven-jar-plugin \ -Dversion=2.1-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin 2.1-SNAPSHOT
Oops wrong plugin http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-jar-plugin/ This is the correct location. On 5/20/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: Here http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-site-plugin/ Just checkout the code and run "mvn install". On 5/20/06, ben short <[EMAIL PROTECTED]> wrote: > Alexandre, > > Thanks for the reply, the emails i posted dint show in my inbox for some > reason, so i assumed that they didnt get sent properly. > > Do you know where i can get the snapshots from? > > Ben > > On 5/20/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > > > > By the way, don't post three mails about the same thing. It's a bit > > annoying > > > > On 5/20/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > > > I had the same error, there is definitly something wrong in Maven > > > 2.0.4 with remote snapshots repositories. Install it manually and > > > everything work fine. > > > > > > On 5/20/06, ben short <[EMAIL PROTECTED]> wrote: > > > > I get the following error while trying to build the maven repository > > > > manager. Any ideas where i can get the snapshot? > > > > > > > > [INFO] > > > > > > > > > > [INFO] snapshot > > > > org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT:checking for > > > > updates from > > > > apache.snapshots > > > > [INFO] > > > > > > > > > > [ERROR] BUILD FAILURE > > > > [INFO] > > > > > > > > > > [INFO] A required plugin was not found: Plugin could not be found - > > check > > > > that the goal name is correct: Unable to download the artifact from > > any > > > > repository > > > > > > > > Try downloading the file manually from the project website. > > > > > > > > Then, install it using the command: > > > >mvn install:install-file > > > > -DgroupId=org.apache.maven.plugins-DartifactId=maven-jar-plugin \ > > > >-Dversion=2.1-SNAPSHOT -Dpackaging=maven-plugin > > -Dfile=/path/to/file > > > > > > > > > > > > org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-SNAPSHOT > > > > > > > > from the specified remote repositories: > > > > central (http://repo1.maven.org/maven2) > > > > > > > > org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-SNAPSHOT > > > > > > > > from the specified remote repositories: > > > > central (http://repo1.maven.org/maven2) > > > > > > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin 2.1-SNAPSHOT
Here http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-site-plugin/ Just checkout the code and run "mvn install". On 5/20/06, ben short <[EMAIL PROTECTED]> wrote: Alexandre, Thanks for the reply, the emails i posted dint show in my inbox for some reason, so i assumed that they didnt get sent properly. Do you know where i can get the snapshots from? Ben On 5/20/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > > By the way, don't post three mails about the same thing. It's a bit > annoying > > On 5/20/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > > I had the same error, there is definitly something wrong in Maven > > 2.0.4 with remote snapshots repositories. Install it manually and > > everything work fine. > > > > On 5/20/06, ben short <[EMAIL PROTECTED]> wrote: > > > I get the following error while trying to build the maven repository > > > manager. Any ideas where i can get the snapshot? > > > > > > [INFO] > > > > > > > [INFO] snapshot > > > org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT:checking for > > > updates from > > > apache.snapshots > > > [INFO] > > > > > > > [ERROR] BUILD FAILURE > > > [INFO] > > > > > > > [INFO] A required plugin was not found: Plugin could not be found - > check > > > that the goal name is correct: Unable to download the artifact from > any > > > repository > > > > > > Try downloading the file manually from the project website. > > > > > > Then, install it using the command: > > >mvn install:install-file > > > -DgroupId=org.apache.maven.plugins-DartifactId=maven-jar-plugin \ > > >-Dversion=2.1-SNAPSHOT -Dpackaging=maven-plugin > -Dfile=/path/to/file > > > > > > > > > org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-SNAPSHOT > > > > > > from the specified remote repositories: > > > central (http://repo1.maven.org/maven2) > > > > > > org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-SNAPSHOT > > > > > > from the specified remote repositories: > > > central (http://repo1.maven.org/maven2) > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin 2.1-SNAPSHOT
Alexandre, Thanks for the reply, the emails i posted dint show in my inbox for some reason, so i assumed that they didnt get sent properly. Do you know where i can get the snapshots from? Ben On 5/20/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: By the way, don't post three mails about the same thing. It's a bit annoying On 5/20/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > I had the same error, there is definitly something wrong in Maven > 2.0.4 with remote snapshots repositories. Install it manually and > everything work fine. > > On 5/20/06, ben short <[EMAIL PROTECTED]> wrote: > > I get the following error while trying to build the maven repository > > manager. Any ideas where i can get the snapshot? > > > > [INFO] > > > > [INFO] snapshot > > org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT:checking for > > updates from > > apache.snapshots > > [INFO] > > > > [ERROR] BUILD FAILURE > > [INFO] > > > > [INFO] A required plugin was not found: Plugin could not be found - check > > that the goal name is correct: Unable to download the artifact from any > > repository > > > > Try downloading the file manually from the project website. > > > > Then, install it using the command: > >mvn install:install-file > > -DgroupId=org.apache.maven.plugins-DartifactId=maven-jar-plugin \ > >-Dversion=2.1-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file > > > > > > org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-SNAPSHOT > > > > from the specified remote repositories: > > central (http://repo1.maven.org/maven2) > > > > org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-SNAPSHOT > > > > from the specified remote repositories: > > central (http://repo1.maven.org/maven2) > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin 2.1-SNAPSHOT
By the way, don't post three mails about the same thing. It's a bit annoying On 5/20/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: I had the same error, there is definitly something wrong in Maven 2.0.4 with remote snapshots repositories. Install it manually and everything work fine. On 5/20/06, ben short <[EMAIL PROTECTED]> wrote: > I get the following error while trying to build the maven repository > manager. Any ideas where i can get the snapshot? > > [INFO] > > [INFO] snapshot > org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT:checking for > updates from > apache.snapshots > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] A required plugin was not found: Plugin could not be found - check > that the goal name is correct: Unable to download the artifact from any > repository > > Try downloading the file manually from the project website. > > Then, install it using the command: >mvn install:install-file > -DgroupId=org.apache.maven.plugins-DartifactId=maven-jar-plugin \ >-Dversion=2.1-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file > > > org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-SNAPSHOT > > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > > org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-SNAPSHOT > > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-jar-plugin 2.1-SNAPSHOT
I had the same error, there is definitly something wrong in Maven 2.0.4 with remote snapshots repositories. Install it manually and everything work fine. On 5/20/06, ben short <[EMAIL PROTECTED]> wrote: I get the following error while trying to build the maven repository manager. Any ideas where i can get the snapshot? [INFO] [INFO] snapshot org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT:checking for updates from apache.snapshots [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.plugins-DartifactId=maven-jar-plugin \ -Dversion=2.1-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven jar plugin: Manifest Entries?
It works. manifestFile is a var under MavenArchiveConfiguration so it needs to be declared under org.apache.maven.plugins maven-jar-plugin META-INF/MANIFEST.MF MavenArchiveConfiguration - sachin On Mar 17, 2006, at 8:31 AM, Sachin Patel wrote: I've opened MNG-2156 on this. - sachin On Mar 16, 2006, at 8:02 PM, Sachin Patel wrote: Yes, this is exactly what I have. I took a quick peak at the plugin code and I didn't see any reference to specifying a manifestFile either. ... org.apache.maven.plugins maven-jar-plugin META-INF/MANIFEST.MF - sachin On Mar 16, 2006, at 6:13 PM, Alexandre Poitras wrote: org.apache.maven.plugins maven-jar-plugin /path/to/MANIFEST.MF According to the documentation, this should work. Is it what you have in your pom.xml file? On 3/16/06, Sachin Patel <[EMAIL PROTECTED]> wrote: Adding the following manifestFile element failed to work for me as I get the following error.. [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT Cause: Cannot find setter nor field in org.apache.maven.archiver.ManifestConfiguration for 'manifestFile' Is this element no longer supported? If not, then how can I accomplish merging an existing manifest in my project with the maven generated one? I'm looking for a replacement for the m1 manifest override property. thx - sachin On Dec 30, 2005, at 10:32 PM, Alexandre Poitras wrote: And I think to add custom entries, you need to write them in a base manifest file wich you specify to be added to the generated manifest file. You just need to add this line to your plugin configuration : /path/to/MANIFEST.MF On 12/30/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote: From your example, I am guessing you are looking for a way to specify the classpath. If that the case, you work too hard. Maven is all about laziness and of course it can generate the class path for you : org.apache.maven.plugins maven-jar-plugin true Voilà, everything is always in sync with your dependencies. I like the magic of Maven :) I hope it help! On 12/30/05, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: Hi, how do I add manifest entries to the generated Jar file? I have tried various things in the style of maven-jar-plugin Name org/apache/xmlrpc/ none of which seem to be working? Regards, Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada -- Alexandre Poitras Québec, Canada -- --- 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] -- Alexandre Poitras Québec, Canada - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven jar plugin: Manifest Entries?
I've opened MNG-2156 on this. - sachin On Mar 16, 2006, at 8:02 PM, Sachin Patel wrote: Yes, this is exactly what I have. I took a quick peak at the plugin code and I didn't see any reference to specifying a manifestFile either. ... org.apache.maven.plugins maven-jar-plugin META-INF/MANIFEST.MF - sachin On Mar 16, 2006, at 6:13 PM, Alexandre Poitras wrote: org.apache.maven.plugins maven-jar-plugin /path/to/MANIFEST.MF According to the documentation, this should work. Is it what you have in your pom.xml file? On 3/16/06, Sachin Patel <[EMAIL PROTECTED]> wrote: Adding the following manifestFile element failed to work for me as I get the following error.. [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT Cause: Cannot find setter nor field in org.apache.maven.archiver.ManifestConfiguration for 'manifestFile' Is this element no longer supported? If not, then how can I accomplish merging an existing manifest in my project with the maven generated one? I'm looking for a replacement for the m1 manifest override property. thx - sachin On Dec 30, 2005, at 10:32 PM, Alexandre Poitras wrote: And I think to add custom entries, you need to write them in a base manifest file wich you specify to be added to the generated manifest file. You just need to add this line to your plugin configuration : /path/to/MANIFEST.MF On 12/30/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote: From your example, I am guessing you are looking for a way to specify the classpath. If that the case, you work too hard. Maven is all about laziness and of course it can generate the class path for you : org.apache.maven.plugins maven-jar-plugin true Voilà, everything is always in sync with your dependencies. I like the magic of Maven :) I hope it help! On 12/30/05, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: Hi, how do I add manifest entries to the generated Jar file? I have tried various things in the style of maven-jar-plugin Name org/apache/xmlrpc/ none of which seem to be working? Regards, Jochen - --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada -- Alexandre Poitras Québec, Canada --- -- 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] -- Alexandre Poitras Québec, Canada - 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: maven jar plugin: Manifest Entries?
Yes, this is exactly what I have. I took a quick peak at the plugin code and I didn't see any reference to specifying a manifestFile either. ... org.apache.maven.plugins maven-jar-plugin META-INF/MANIFEST.MF - sachin On Mar 16, 2006, at 6:13 PM, Alexandre Poitras wrote: org.apache.maven.plugins maven-jar-plugin /path/to/MANIFEST.MF According to the documentation, this should work. Is it what you have in your pom.xml file? On 3/16/06, Sachin Patel <[EMAIL PROTECTED]> wrote: Adding the following manifestFile element failed to work for me as I get the following error.. [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT Cause: Cannot find setter nor field in org.apache.maven.archiver.ManifestConfiguration for 'manifestFile' Is this element no longer supported? If not, then how can I accomplish merging an existing manifest in my project with the maven generated one? I'm looking for a replacement for the m1 manifest override property. thx - sachin On Dec 30, 2005, at 10:32 PM, Alexandre Poitras wrote: And I think to add custom entries, you need to write them in a base manifest file wich you specify to be added to the generated manifest file. You just need to add this line to your plugin configuration : /path/to/MANIFEST.MF On 12/30/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote: From your example, I am guessing you are looking for a way to specify the classpath. If that the case, you work too hard. Maven is all about laziness and of course it can generate the class path for you : org.apache.maven.plugins maven-jar-plugin true Voilà, everything is always in sync with your dependencies. I like the magic of Maven :) I hope it help! On 12/30/05, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: Hi, how do I add manifest entries to the generated Jar file? I have tried various things in the style of maven-jar-plugin Name org/apache/xmlrpc/ none of which seem to be working? Regards, Jochen -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada -- Alexandre Poitras Québec, Canada - 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] -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven jar plugin: Manifest Entries?
org.apache.maven.plugins maven-jar-plugin /path/to/MANIFEST.MF According to the documentation, this should work. Is it what you have in your pom.xml file? On 3/16/06, Sachin Patel <[EMAIL PROTECTED]> wrote: > Adding the following manifestFile element failed to work for me as I > get the following error.. > > [INFO] Failed to configure plugin parameters for: > org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT > Cause: Cannot find setter nor field in > org.apache.maven.archiver.ManifestConfiguration for 'manifestFile' > > Is this element no longer supported? If not, then how can I > accomplish merging an existing manifest in my project with the > maven generated one? I'm looking for a replacement for the m1 > manifest override property. > > thx > > - sachin > > > > On Dec 30, 2005, at 10:32 PM, Alexandre Poitras wrote: > > > And I think to add custom entries, you need to write them in a base > > manifest file wich you specify to be added to the generated manifest > > file. > > You just need to add this line to your plugin configuration : > > > > > > /path/to/MANIFEST.MF > > > > > > > > On 12/30/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > >> From your example, I am guessing you are looking for a way to specify > >> the classpath. > >> If that the case, you work too hard. Maven is all about laziness and > >> of course it can generate the class path for you : > >> > >> > >> > >> org.apache.maven.plugins > >> maven-jar-plugin > >> > >> > >> > >> true > >> > >> > >> > >> > >> > >> > >> Voilà, everything is always in sync with your dependencies. I like > >> the > >> magic of Maven :) > >> I hope it help! > >> > >> On 12/30/05, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: > >>> > >>> Hi, > >>> > >>> how do I add manifest entries to the generated Jar file? I have > >>> tried > >>> various things in the style of > >>> > >>> > >>> maven-jar-plugin > >>> > >>> > >>> > >>> > >>> > >>>Name > >>>org/apache/xmlrpc/ > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> none of which seem to be working? > >>> > >>> > >>> Regards, > >>> > >>> Jochen > >>> > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >> > >> > >> -- > >> Alexandre Poitras > >> Québec, Canada > >> > > > > > > -- > > Alexandre Poitras > > Québec, Canada > > > > - > > 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] > > -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven jar plugin: Manifest Entries?
Adding the following manifestFile element failed to work for me as I get the following error.. [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-jar-plugin:2.1-SNAPSHOT Cause: Cannot find setter nor field in org.apache.maven.archiver.ManifestConfiguration for 'manifestFile' Is this element no longer supported? If not, then how can I accomplish merging an existing manifest in my project with the maven generated one? I'm looking for a replacement for the m1 manifest override property. thx - sachin On Dec 30, 2005, at 10:32 PM, Alexandre Poitras wrote: And I think to add custom entries, you need to write them in a base manifest file wich you specify to be added to the generated manifest file. You just need to add this line to your plugin configuration : /path/to/MANIFEST.MF On 12/30/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote: From your example, I am guessing you are looking for a way to specify the classpath. If that the case, you work too hard. Maven is all about laziness and of course it can generate the class path for you : org.apache.maven.plugins maven-jar-plugin true Voilà, everything is always in sync with your dependencies. I like the magic of Maven :) I hope it help! On 12/30/05, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: Hi, how do I add manifest entries to the generated Jar file? I have tried various things in the style of maven-jar-plugin Name org/apache/xmlrpc/ none of which seem to be working? Regards, Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven jar plugin: Manifest Entries?
this is my pom, it works fine! org.apache.maven.plugins maven-jar-plugin com.mycompany.app.App Best Regards, Manchi Leung On Dec 31, 2005, at 5:34 AM, Jochen Wiedmann wrote: Hi, how do I add manifest entries to the generated Jar file? I have tried various things in the style of maven-jar-plugin Name org/apache/xmlrpc/ none of which seem to be working? Regards, Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven jar plugin: Manifest Entries?
And I think to add custom entries, you need to write them in a base manifest file wich you specify to be added to the generated manifest file. You just need to add this line to your plugin configuration : /path/to/MANIFEST.MF On 12/30/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > From your example, I am guessing you are looking for a way to specify > the classpath. > If that the case, you work too hard. Maven is all about laziness and > of course it can generate the class path for you : > > > > org.apache.maven.plugins > maven-jar-plugin > > > > true > > > > > > > Voilà, everything is always in sync with your dependencies. I like the > magic of Maven :) > I hope it help! > > On 12/30/05, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > how do I add manifest entries to the generated Jar file? I have tried > > various things in the style of > > > > > > maven-jar-plugin > > > > > > > > > > > >Name > >org/apache/xmlrpc/ > > > > > > > > > > > > > > > > none of which seem to be working? > > > > > > Regards, > > > > Jochen > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Alexandre Poitras > Québec, Canada > -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven jar plugin: Manifest Entries?
>From your example, I am guessing you are looking for a way to specify the classpath. If that the case, you work too hard. Maven is all about laziness and of course it can generate the class path for you : org.apache.maven.plugins maven-jar-plugin true Voilà, everything is always in sync with your dependencies. I like the magic of Maven :) I hope it help! On 12/30/05, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: > > Hi, > > how do I add manifest entries to the generated Jar file? I have tried > various things in the style of > > > maven-jar-plugin > > > > > >Name >org/apache/xmlrpc/ > > > > > > > > none of which seem to be working? > > > Regards, > > Jochen > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
