Re: Transitive Dependency Question
Hi Jamal, Jamal B wrote: Interesting Taking your suggestion, it looks like it is coming in from another compile dependency, and was promoted to compile. [INFO] +- org.apache.maven.shared:maven-shared-jar:jar:1.1:compile [INFO] | +- org.codehaus.plexus:plexus-digest:jar:1.0:compile [INFO] | | \- org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:compile [INFO] | | +- junit:junit:jar:3.8.1:compile Is there a way to prevent this from happening without having to add exclude stanzas across projects where this is happening? You can control this with a dependencyManagement section of a shared parent. Just define there junit:junit:version and the scope. The annoying part is nevertheless that the situation is no longer obvious in M3. Try this in M2 and you'll see that the dependency makes much more sense. Since the same plugin produces different output, I blame the new Aether backend here which favors now the nearest occurrence without taking the inherited scope into account. While this behavior has no impact on the resulting class path, it hides dependency problems like the one, you have encountered here. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: source and javadoc jars from test-jar
I'm assuming it is a bug and opened
http://jira.codehaus.org/browse/MSOURCES-66
On 6/3/13 2:26 PM, Kurt T Stam wrote:
Hi guys,
I'm trying to add 'test-jar' resources to my assembly; i.e. the
following jars are created by one of our other modules:
main:
-rw-r--r-- 1 kstam admin 11603 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT.jar
-rw-r--r-- 1 kstam admin 27880 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-javadoc.jar
-rw-r--r-- 1 kstam admin 8873 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-sources.jar
test:
-rw-r--r-- 1 kstam admin106397 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-tests.jar
-rw-r--r-- 1 kstam admin149558 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-test-javadoc.jar
-rw-r--r-- 1 kstam admin 62545 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-test-sources.jar
I can successfully add the uddi-tck-3.2.0-SNAPSHOT-tests.jar to my
assembly using
...
dependencySet
outputDirectorybin/outputDirectory
includes
includeorg.apache.juddi:juddi-client:jar/include
includeorg.apache.juddi:uddi-tck:jar/include
includeorg.apache.juddi:uddi-tck:test-jar/include
...
However when I try to add the source jar:
...
!-- The source archives JARs --
dependencySet
outputDirectorysrc/outputDirectory
scopetest/scope
includes
includeorg.apache.juddi:juddi-client:jar:sources/include
includeorg.apache.juddi:uddi-tck:jar:sources/include
includeorg.apache.juddi:uddi-tck:test-jar:sources/include
...
Then the uddi-tck-3.2.0-SNAPSHOT-sources.jar is NOT picked up. I made
sure we reference the source
and javadoc artifacts in the pom.xml:
dependency
groupIdorg.apache.juddi/groupId
artifactIduddi-tck/artifactId
version${project.parent.version}/version
typetest-jar/type
classifiersources/classifier
/dependency
dependency
groupIdorg.apache.juddi/groupId
artifactIduddi-tck/artifactId
version${project.parent.version}/version
classifierjavadoc/classifier
typetest-jar/type
/dependency
Full pom and assembly.xml:
http://svn.apache.org/repos/asf/juddi/trunk/uddi-client-dist/pom.xml
http://svn.apache.org/repos/asf/juddi/trunk/uddi-client-dist/src/main/assembly/assembly.xml
When running with -X it says:
[DEBUG] Adding artifact:
org.apache.juddi:uddi-tck:test-jar:sources:3.2.0-SNAPSHOT with file:
/Users/kstam/.m2/repository/org/apache/juddi/uddi-tck/3.2.0-SNAPSHOT/uddi-tck-3.2.0-SNAPSHOT-sources.jar
to assembly location: src/uddi-tck-3.2.0-SNAPSHOT-sources.jar.
so it seem to be adding the source *jar*, rather then the *test-jar*.
eventhough it says it's going to add the *test-jar* version:
Adding artifact:
org.apache.juddi:uddi-tck:test-jar:sources:3.2.0-SNAPSHOT
Does anyone has an idea what I'm doing wrong? Is this a bug?
Any help you can provide would be great.
Thx,
--Kurt
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: source and javadoc jars from test-jar
the packaging is `jar` not `test-jar` there is only one artifact with
`test-jar` packaging, namely the `test-jar`
You want to use
includeorg.apache.juddi:**uddi-tck:jar:test-sources/**include
includeorg.apache.juddi:**uddi-tck:jar:test-javadoc/**include
Not a bug
On 4 June 2013 14:02, Kurt T Stam kurt.s...@gmail.com wrote:
I'm assuming it is a bug and opened http://jira.codehaus.org/**
browse/MSOURCES-66 http://jira.codehaus.org/browse/MSOURCES-66
On 6/3/13 2:26 PM, Kurt T Stam wrote:
Hi guys,
I'm trying to add 'test-jar' resources to my assembly; i.e. the following
jars are created by one of our other modules:
main:
-rw-r--r-- 1 kstam admin 11603 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT.jar
-rw-r--r-- 1 kstam admin 27880 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-**javadoc.jar
-rw-r--r-- 1 kstam admin 8873 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-**sources.jar
test:
-rw-r--r-- 1 kstam admin106397 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-tests.**jar
-rw-r--r-- 1 kstam admin149558 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-test-**javadoc.jar
-rw-r--r-- 1 kstam admin 62545 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-test-**sources.jar
I can successfully add the uddi-tck-3.2.0-SNAPSHOT-tests.**jar to my
assembly using
...
dependencySet
outputDirectorybin/**outputDirectory
includes
includeorg.apache.juddi:**juddi-client:jar/include
includeorg.apache.juddi:**uddi-tck:jar/include
includeorg.apache.juddi:**uddi-tck:test-jar/include
...
However when I try to add the source jar:
...
!-- The source archives JARs --
dependencySet
outputDirectorysrc/**outputDirectory
scopetest/scope
includes
includeorg.apache.juddi:**juddi-client:jar:sources/**include
includeorg.apache.juddi:**uddi-tck:jar:sources/include
includeorg.apache.juddi:**uddi-tck:test-jar:sources/**include
...
Then the uddi-tck-3.2.0-SNAPSHOT-**sources.jar is NOT picked up. I made
sure we reference the source
and javadoc artifacts in the pom.xml:
dependency
groupIdorg.apache.juddi/**groupId
artifactIduddi-tck/**artifactId
version${project.parent.**version}/version
typetest-jar/type
classifiersources/**classifier
/dependency
dependency
groupIdorg.apache.juddi/**groupId
artifactIduddi-tck/**artifactId
version${project.parent.**version}/version
classifierjavadoc/**classifier
typetest-jar/type
/dependency
Full pom and assembly.xml:
http://svn.apache.org/repos/**asf/juddi/trunk/uddi-client-**dist/pom.xmlhttp://svn.apache.org/repos/asf/juddi/trunk/uddi-client-dist/pom.xml
http://svn.apache.org/repos/**asf/juddi/trunk/uddi-client-**
dist/src/main/assembly/**assembly.xmlhttp://svn.apache.org/repos/asf/juddi/trunk/uddi-client-dist/src/main/assembly/assembly.xml
When running with -X it says:
[DEBUG] Adding artifact: org.apache.juddi:uddi-tck:**
test-jar:sources:3.2.0-**SNAPSHOT with file: /Users/kstam/.m2/repository/
**org/apache/juddi/uddi-tck/3.2.**0-SNAPSHOT/uddi-tck-3.2.0-**SNAPSHOT-sources.jar
to assembly location: src/uddi-tck-3.2.0-SNAPSHOT-**sources.jar.
so it seem to be adding the source *jar*, rather then the *test-jar*.
eventhough it says it's going to add the *test-jar* version:
Adding artifact: org.apache.juddi:uddi-tck:**test-jar:sources:3.2.0-**
SNAPSHOT
Does anyone has an idea what I'm doing wrong? Is this a bug?
Any help you can provide would be great.
Thx,
--Kurt
--**--**-
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Call a custom plugin from another project
Hi guys i'm try to implement my first plugin so i did just a plugin that print a log on the screen this is the code and this is the pom related to this plugin, from the pom generated from the plugin archetype i have just add the maven-plugin-plugin to add the prefix pojo to make same test finally i have configure my setting to register my group of plugin now my proble,: from the command line i can call with any problem my plugin mvn pojo:log but if i try to use it in another project it is not used! for example this is the pom of my test project and if i run on this project mvn process-sources i should aspect to see my output but the plugin is not used at all any advice of the reason that the plugin work directly from command line and not if configured in the pom of another project? thanks this is the log of the pom project this is instead the plugin.xml generated by maven -- View this message in context: http://maven.40175.n5.nabble.com/Call-a-custom-plugin-from-another-project-tp5758214.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: Call a custom plugin from another project
1. Please use a propper mail agent that does not strip the code from you email 2. Try `mvn it.spaghettisource.plugin:pojo:1.0:log` as Maven does not know where to look for your plugin On 4 June 2013 15:30, alesky alessandro.dotta...@gmail.com wrote: Hi guys i'm try to implement my first plugin so i did just a plugin that print a log on the screen this is the code and this is the pom related to this plugin, from the pom generated from the plugin archetype i have just add the maven-plugin-plugin to add the prefix pojo to make same test finally i have configure my setting to register my group of plugin now my proble,: from the command line i can call with any problem my plugin mvn pojo:log but if i try to use it in another project it is not used! for example this is the pom of my test project and if i run on this project mvn process-sources i should aspect to see my output but the plugin is not used at all any advice of the reason that the plugin work directly from command line and not if configured in the pom of another project? thanks this is the log of the pom project this is instead the plugin.xml generated by maven -- View this message in context: http://maven.40175.n5.nabble.com/Call-a-custom-plugin-from-another-project-tp5758214.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: Call a custom plugin from another project
1. Please use a propper mail agent that does not strip the code from you email ok i will do the next time sorry to all, i was supposing that in this way there was all the information to undestand my issue 2. Try `mvn it.spaghettisource.plugin:pojo:1.0:log` as Maven does not know where to look for your plugin as is wrote in my previous mail i can call correctly the plugin from command line: using mvn it.spaghettisource.plugin:pojo:1.0:log and i have registered the group in the setting so i can call it also by prefix mvn pojo:log my question is related to the fact that if i had the plugin configuration in another project inside the plugin section, it is not executed -- View this message in context: http://maven.40175.n5.nabble.com/Call-a-custom-plugin-from-another-project-tp5758214p5758217.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 Release plugin
Man i have your same issue i use this strategy to reduce the number manually file that i have to update when i change version in my main parent pom i added 1)in the dependencies management all the sub project 2)a property with the version of my project so at list i have reduced the manually upgrade of the version in the interrelationship between all the sub project obviously what remain to change in this case if update the version of the module is 1)main module pom version 2)a property with the version of my project 3)in any subjection the version in the parent tag -- View this message in context: http://maven.40175.n5.nabble.com/Maven-Release-plugin-tp5756929p5758219.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: Call a custom plugin from another project
plugins are not executed unless the packaging for the specified project injects an execution OR you specify an execution for the plugin yourself On 4 June 2013 16:01, alesky alessandro.dotta...@gmail.com wrote: 1. Please use a propper mail agent that does not strip the code from you email ok i will do the next time sorry to all, i was supposing that in this way there was all the information to undestand my issue 2. Try `mvn it.spaghettisource.plugin:pojo:1.0:log` as Maven does not know where to look for your plugin as is wrote in my previous mail i can call correctly the plugin from command line: using mvn it.spaghettisource.plugin:pojo:1.0:log and i have registered the group in the setting so i can call it also by prefix mvn pojo:log my question is related to the fact that if i had the plugin configuration in another project inside the plugin section, it is not executed -- View this message in context: http://maven.40175.n5.nabble.com/Call-a-custom-plugin-from-another-project-tp5758214p5758217.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: Call a custom plugin from another project
eg project ...build ...plugins ...plugin ...executions ...execution On 4 June 2013 16:46, Stephen Connolly stephen.alan.conno...@gmail.comwrote: plugins are not executed unless the packaging for the specified project injects an execution OR you specify an execution for the plugin yourself On 4 June 2013 16:01, alesky alessandro.dotta...@gmail.com wrote: 1. Please use a propper mail agent that does not strip the code from you email ok i will do the next time sorry to all, i was supposing that in this way there was all the information to undestand my issue 2. Try `mvn it.spaghettisource.plugin:pojo:1.0:log` as Maven does not know where to look for your plugin as is wrote in my previous mail i can call correctly the plugin from command line: using mvn it.spaghettisource.plugin:pojo:1.0:log and i have registered the group in the setting so i can call it also by prefix mvn pojo:log my question is related to the fact that if i had the plugin configuration in another project inside the plugin section, it is not executed -- View this message in context: http://maven.40175.n5.nabble.com/Call-a-custom-plugin-from-another-project-tp5758214p5758217.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: Site plugin woes
To summarize for any future thread readers...
Right now, the site plugin, and its related report plugins, are highly
unlikely to work reliably for any non-standard project layout (and I
personally haven't tried a layout that does work).
If you have just one extra layer between your parent/aggregator and
your children, then the project-info plugin breaks.
https://jira.codehaus.org/browse/MPIR-279
If you have an aggregator at the root and a child below, then the site
plugin breaks.
https://jira.codehaus.org/browse/MSITE-691
It also clobbers the target directory when using site:stage
(Was reported under http://jira.codehaus.org/browse/MSITE-690, but a
JIRA bug has created two issues with the same id MSITE-690)
The topSiteURL parameter mentioned below had no effect in fixing site:stage.
The Javadoc plugin runs the validate and generate-sources phases when
it shoudn't slowing down (and potentially generating incorrect) docs.
https://jira.codehaus.org/browse/MJAVADOC-369
The Javadoc plugin has performance/invocation problems meaning that it
takes longer and longer the more modules you have as it keeps on
repeating the same tasks.
http://jira.codehaus.org/browse/MJAVADOC-171 (or similar)
Figuring out a suitable set of configuration to generate aggregate
reports in the aggregate location and leaf reports in the leaf
location is hard, as the documentation is weak. While some plugins
just seem to work (checkstyle), others do not. Configuring the report
sets to avoid the undesired test-jxr and test-javadoc causes the
aggregates to stop working.
The reporting plugins generate incomplete HTML files that have to be
processed by the site plugin before they are readable (to handle ${}
interpolations and css). Yet, there is no way to run that site plugin
processing without running the rest of the broken site tasks. The site
plugin needs a new goal.
http://jira.codehaus.org/browse/MSITE-690
I ended up replacing the index.html and site.xml to avoid the broken
links from MPIR-279 and MSITE-691. I then generated only the aggregate
level docs, producing nothing at the child level, avoiding some of the
slow performance.
While some of my emails may appear negative, it is my opinion that
site and reporting in Maven is not currently suitable for general use.
thanks
Stephen
On 1 June 2013 12:05, Stephen Colebourne scolebou...@joda.org wrote:
On 1 June 2013 08:30, Hervé BOUTEMY herve.bout...@free.fr wrote:
yes, I worked recently on this exact issue: site *staging* on complex cases
like yours, which is not as usual as you expect
It took me a good number of hours with the issue reporter to understand what
he was doing, what he was expecting that wasn't trivial, and I found a
solution with this topSiteURL
Thanks for looking into it. Part of the problem with these things is
that it take 90 minutes to run the site plugin. Thats because of the
repeated invocation of the same goals, similar to
http://jira.codehaus.org/browse/MJAVADOC-286 and related issues. I
think there is still a more general problem with multi-modules sites.
Anyway, I will try to topSiteURL property next week.
4 issues raised in total now ;-)
Stephen
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: source and javadoc jars from test-jar
Thank you Stephen,
After also updating the dependencies in the pom to:
dependency
groupIdorg.apache.juddi/groupId
artifactIduddi-tck/artifactId
version${project.parent.version}/version
classifiertest-javadoc/classifier
typejar/type
/dependency
things started working.
Cheers,
--Kurt
On 6/4/13 9:25 AM, Stephen Connolly wrote:
the packaging is `jar` not `test-jar` there is only one artifact with
`test-jar` packaging, namely the `test-jar`
You want to use
includeorg.apache.juddi:**uddi-tck:jar:test-sources/**include
includeorg.apache.juddi:**uddi-tck:jar:test-javadoc/**include
Not a bug
On 4 June 2013 14:02, Kurt T Stam kurt.s...@gmail.com wrote:
I'm assuming it is a bug and opened http://jira.codehaus.org/**
browse/MSOURCES-66 http://jira.codehaus.org/browse/MSOURCES-66
On 6/3/13 2:26 PM, Kurt T Stam wrote:
Hi guys,
I'm trying to add 'test-jar' resources to my assembly; i.e. the following
jars are created by one of our other modules:
main:
-rw-r--r-- 1 kstam admin 11603 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT.jar
-rw-r--r-- 1 kstam admin 27880 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-**javadoc.jar
-rw-r--r-- 1 kstam admin 8873 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-**sources.jar
test:
-rw-r--r-- 1 kstam admin106397 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-tests.**jar
-rw-r--r-- 1 kstam admin149558 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-test-**javadoc.jar
-rw-r--r-- 1 kstam admin 62545 Jun 3 11:29
uddi-tck-3.2.0-SNAPSHOT-test-**sources.jar
I can successfully add the uddi-tck-3.2.0-SNAPSHOT-tests.**jar to my
assembly using
...
dependencySet
outputDirectorybin/**outputDirectory
includes
includeorg.apache.juddi:**juddi-client:jar/include
includeorg.apache.juddi:**uddi-tck:jar/include
includeorg.apache.juddi:**uddi-tck:test-jar/include
...
However when I try to add the source jar:
...
!-- The source archives JARs --
dependencySet
outputDirectorysrc/**outputDirectory
scopetest/scope
includes
includeorg.apache.juddi:**juddi-client:jar:sources/**include
includeorg.apache.juddi:**uddi-tck:jar:sources/include
includeorg.apache.juddi:**uddi-tck:test-jar:sources/**include
...
Then the uddi-tck-3.2.0-SNAPSHOT-**sources.jar is NOT picked up. I made
sure we reference the source
and javadoc artifacts in the pom.xml:
dependency
groupIdorg.apache.juddi/**groupId
artifactIduddi-tck/**artifactId
version${project.parent.**version}/version
typetest-jar/type
classifiersources/**classifier
/dependency
dependency
groupIdorg.apache.juddi/**groupId
artifactIduddi-tck/**artifactId
version${project.parent.**version}/version
classifierjavadoc/**classifier
typetest-jar/type
/dependency
Full pom and assembly.xml:
http://svn.apache.org/repos/**asf/juddi/trunk/uddi-client-**dist/pom.xmlhttp://svn.apache.org/repos/asf/juddi/trunk/uddi-client-dist/pom.xml
http://svn.apache.org/repos/**asf/juddi/trunk/uddi-client-**
dist/src/main/assembly/**assembly.xmlhttp://svn.apache.org/repos/asf/juddi/trunk/uddi-client-dist/src/main/assembly/assembly.xml
When running with -X it says:
[DEBUG] Adding artifact: org.apache.juddi:uddi-tck:**
test-jar:sources:3.2.0-**SNAPSHOT with file: /Users/kstam/.m2/repository/
**org/apache/juddi/uddi-tck/3.2.**0-SNAPSHOT/uddi-tck-3.2.0-**SNAPSHOT-sources.jar
to assembly location: src/uddi-tck-3.2.0-SNAPSHOT-**sources.jar.
so it seem to be adding the source *jar*, rather then the *test-jar*.
eventhough it says it's going to add the *test-jar* version:
Adding artifact: org.apache.juddi:uddi-tck:**test-jar:sources:3.2.0-**
SNAPSHOT
Does anyone has an idea what I'm doing wrong? Is this a bug?
Any help you can provide would be great.
Thx,
--Kurt
--**--**-
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.orgusers-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: Call a custom plugin from another project
ok Stephen thanks specifying an execution to the plugin it works but i would like to injects an execution in the packaging for the specified plugin project in the way that i can use the plugin in this way, and don't have to force the user to specific the execution but i didn't found any documentation on-line or in the reference guide regarding this point or at list I'm not able to find a correct on-line document to do it what i i found is that in the plugin annotation there is the @execute annotation, but from my understand this annotation is complete different from what i want to do @execute goal=goal This will execute the given goal before execution of this one. The goal name is specified using the prefix:goal notation. @execute phase=phase This will fork an alternate build lifecycle up to the specified phase before continuing to execute the current one. If no lifecycle is specified, Maven will use the lifecycle of the current build. @execute lifecycle=lifecycle phase=phase This will execute the given alternate lifecycle. A custom lifecycle can be defined in META-INF/maven/lifecycles.xml. -- View this message in context: http://maven.40175.n5.nabble.com/Call-a-custom-plugin-from-another-project-tp5758214p5758242.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: Call a custom plugin from another project
IIUC, you are trying to bind a plugin execution to a phase? Check this link http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Configuring_Build_Plugins Basically, you need an execution tag with the configuration for the plugin and a phase that the plugin is bound to so if you bind it to package for example, your plugin will be executed when you run mvn package Alejandro Endo | Software Designer/Concepteur de logiciels From: alesky alessandro.dotta...@gmail.com To: users@maven.apache.org, Date: 04/06/2013 01:17 PM Subject:Re: Call a custom plugin from another project ok Stephen thanks specifying an execution to the plugin it works but i would like to injects an execution in the packaging for the specified plugin project in the way that i can use the plugin in this way, and don't have to force the user to specific the execution but i didn't found any documentation on-line or in the reference guide regarding this point or at list I'm not able to find a correct on-line document to do it what i i found is that in the plugin annotation there is the @execute annotation, but from my understand this annotation is complete different from what i want to do @execute goal=goal This will execute the given goal before execution of this one. The goal name is specified using the prefix:goal notation. @execute phase=phase This will fork an alternate build lifecycle up to the specified phase before continuing to execute the current one. If no lifecycle is specified, Maven will use the lifecycle of the current build. @execute lifecycle=lifecycle phase=phase This will execute the given alternate lifecycle. A custom lifecycle can be defined in META-INF/maven/lifecycles.xml. -- View this message in context: http://maven.40175.n5.nabble.com/Call-a-custom-plugin-from-another-project-tp5758214p5758242.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 DISCLAIMER: Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.
Re: Call a custom plugin from another project
If I understand correctly, you want to be able to execute your plugin without having to declare it. If so then your are on the right path since the only way to do that is to create a custom lifecycle. Hope this helps. Cheers -- Baptiste Le 4 juin 2013 19:17, alesky alessandro.dotta...@gmail.com a écrit : ok Stephen thanks specifying an execution to the plugin it works but i would like to injects an execution in the packaging for the specified plugin project in the way that i can use the plugin in this way, and don't have to force the user to specific the execution but i didn't found any documentation on-line or in the reference guide regarding this point or at list I'm not able to find a correct on-line document to do it what i i found is that in the plugin annotation there is the @execute annotation, but from my understand this annotation is complete different from what i want to do @execute goal=goal This will execute the given goal before execution of this one. The goal name is specified using the prefix:goal notation. @execute phase=phase This will fork an alternate build lifecycle up to the specified phase before continuing to execute the current one. If no lifecycle is specified, Maven will use the lifecycle of the current build. @execute lifecycle=lifecycle phase=phase This will execute the given alternate lifecycle. A custom lifecycle can be defined in META-INF/maven/lifecycles.xml. -- View this message in context: http://maven.40175.n5.nabble.com/Call-a-custom-plugin-from-another-project-tp5758214p5758242.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: Javadoc: single configuration
Mon, 3 Jun 2013 07:04:58 -0700 (PDT), /Evan/: http://maven.apache.org/plugins/maven-javadoc-plugin/usage.html#Javadoc_Configuration That section warns me that the behaviour is different, but not *how* it differs. In the example at the bottom of that page the javadoc:javadoc uses elements from the configuration defined in the build *and* reporting sections: |mvn javadoc:javadoc |It will generate the Javadoc for private members (defined in build/) |using the stylesheet (defined in reporting/), and with no help page |(defined in build/). This is the documented behaviour that I can not reproduce. ( mvn javadoc:javadoc only looks at the configuration in the build section instead of both build and reporting sections) I see your point now. The documentation, including at the linked: http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_reporting_Tag_VS_build_Tag states it should behave as you expect. May be it is a bug in the javadoc plugin, but I can't say for sure. Do you use the latest (2.9) plugin version? Does it happen with Maven 2 or 3, or both? Ultimately I'm trying to define the javadoc configuration once and have it apply to all invocations of the javadoc plugin. You may try defining the common configuration in a build/pluginManagement section, but again I don't know if it's supposed to work that way (for the reporting configuration). -- Stanimir - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
create manifest with jars in multiple directories?
If I enable manifest class path creation, the jar or assembly or shade plugin will create a manifest class path that lists all of my dependencies in the same directory. But what if I need them in different directories? Our current requirements place certain jars in specific directories so that layered products can find them - something I doubt that I could get changed. How could I have Maven take that into consideration? - Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.gold-family.us/audio/misfile.html!
Re: create manifest with jars in multiple directories?
How do you decide which artifacts go into which folder? If this is done by hand, then there's your answer: specify the complete classpath yourself. Otherwise I'd suggest to write a custom ManifestResourceTransformer for the maven-shade-plugin. Robert Op Tue, 04 Jun 2013 20:11:21 +0200 schreef Russell Gold r...@gold-family.us: If I enable manifest class path creation, the jar or assembly or shade plugin will create a manifest class path that lists all of my dependencies in the same directory. But what if I need them in different directories? Our current requirements place certain jars in specific directories so that layered products can find them - something I doubt that I could get changed. How could I have Maven take that into consideration? - Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.gold-family.us/audio/misfile.html! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
