How to list only Reactor build order
Hi, I want to list only reactor build order. Is there ant mvn reactor option or anyother way to list only reactor build order? Thanks, Babji
Re: How to include the *-sources.jar in a binary distribution?
Then I think the other hint about classifier syntax is more to the point. Could I reproduce your problems by co'ing the jena trunk tree and fooling around? On Mon, Nov 21, 2011 at 7:03 PM, Paolo Castagna wrote: > Hi Benson, > the lib/ directory includes: > > - jena-arq-2.8.9-incubating-SNAPSHOT.jar > - jena-core-2.6.5-incubating-SNAPSHOT.jar > - jena-iri-0.9.0-incubating-SNAPSHOT.jar > - jena-larq-1.0.0-incubating-SNAPSHOT.jar > - jena-tdb-0.9.0-incubading-SNAPSHOT.jar > > Each of the modules (i.e. jena-arq, jena-core, etc.) produce a > jena-*-x.y.z-incubating-SNAPSHOT-sources.jar. > > What I am trying to add is a lib-src/ directory with these: > > - jena-arq-2.8.9-incubating-SNAPSHOT-sources.jar > - jena-core-2.6.5-incubating-SNAPSHOT-sources.jar > - jena-iri-0.9.0-incubating-SNAPSHOT-sources.jar > - jena-larq-1.0.0-incubating-SNAPSHOT-sources.jar > - jena-tdb-0.9.0-incubading-SNAPSHOT-sources.jar > > Paolo > > Benson Margulies wrote: >> Paolo, >> >> Are the -sources an artifact of the same project that is running the >> assembly plugin? >> >> Off hand I'd suggest making a separate module to build the combined >> sources jar, and then you should be able to pull that into the >> assembly. >> >> Or, just use a pointing at the right file in target/ instead of >> referencing a dependency? >> >> >> On Mon, Nov 21, 2011 at 3:05 PM, Paolo Castagna >> wrote: >>> Hi, >>> I'd like to include the *-sources.jar in a lib-src/ directory in my >>> binary distribution (done via assembly) [1]. >>> The reason why I'd like to include the *-sources.jar in the binary >>> distribution is because people using IDEs (and not Maven) can point at >>> them and browse the sources of our modules. >>> >>> I tried doing this in my assembly-binary.xml [2] but I don't >>> understand why is not working as I would expect: >>> >>> >>> lib >>> false >>> >>> >>> lib >>> >>> >>> lib-src >>> >>> *:sources >>> >>> >>> >>> >>> >>> Can you help me? >>> >>> Thanks, >>> Paolo >>> >>> [1] https://svn.apache.org/repos/asf/incubator/jena/Jena2/JenaDist/trunk/ >>> [2] >>> https://svn.apache.org/repos/asf/incubator/jena/Jena2/JenaDist/trunk/assembly-binary.xml >>> >>> - >>> 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 > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to include the *-sources.jar in a binary distribution?
Hi Benson, the lib/ directory includes: - jena-arq-2.8.9-incubating-SNAPSHOT.jar - jena-core-2.6.5-incubating-SNAPSHOT.jar - jena-iri-0.9.0-incubating-SNAPSHOT.jar - jena-larq-1.0.0-incubating-SNAPSHOT.jar - jena-tdb-0.9.0-incubading-SNAPSHOT.jar Each of the modules (i.e. jena-arq, jena-core, etc.) produce a jena-*-x.y.z-incubating-SNAPSHOT-sources.jar. What I am trying to add is a lib-src/ directory with these: - jena-arq-2.8.9-incubating-SNAPSHOT-sources.jar - jena-core-2.6.5-incubating-SNAPSHOT-sources.jar - jena-iri-0.9.0-incubating-SNAPSHOT-sources.jar - jena-larq-1.0.0-incubating-SNAPSHOT-sources.jar - jena-tdb-0.9.0-incubading-SNAPSHOT-sources.jar Paolo Benson Margulies wrote: > Paolo, > > Are the -sources an artifact of the same project that is running the > assembly plugin? > > Off hand I'd suggest making a separate module to build the combined > sources jar, and then you should be able to pull that into the > assembly. > > Or, just use a pointing at the right file in target/ instead of > referencing a dependency? > > > On Mon, Nov 21, 2011 at 3:05 PM, Paolo Castagna > wrote: >> Hi, >> I'd like to include the *-sources.jar in a lib-src/ directory in my >> binary distribution (done via assembly) [1]. >> The reason why I'd like to include the *-sources.jar in the binary >> distribution is because people using IDEs (and not Maven) can point at >> them and browse the sources of our modules. >> >> I tried doing this in my assembly-binary.xml [2] but I don't >> understand why is not working as I would expect: >> >> >>lib >>false >> >> >>lib >> >> >>lib-src >> >> *:sources >> >> >> >> >> >> Can you help me? >> >> Thanks, >> Paolo >> >> [1] https://svn.apache.org/repos/asf/incubator/jena/Jena2/JenaDist/trunk/ >> [2] >> https://svn.apache.org/repos/asf/incubator/jena/Jena2/JenaDist/trunk/assembly-binary.xml >> >> - >> 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: How to include the *-sources.jar in a binary distribution?
On Tue, Nov 22, 2011 at 6:35 AM, Paolo Castagna wrote: > Hi, > I'd like to include the *-sources.jar in a lib-src/ directory in my > binary distribution (done via assembly) [1]. > The reason why I'd like to include the *-sources.jar in the binary > distribution is because people using IDEs (and not Maven) can point at > them and browse the sources of our modules. > > I tried doing this in my assembly-binary.xml [2] but I don't > understand why is not working as I would expect: > > > lib > false > > > lib > > > lib-src > > *:sources > > > > > > Can you help me? have you verified that *:sources is correct? According to http://maven.apache.org/plugins/maven-assembly-plugin/component.html#class_binaries "(Many) When subelements are present, they define a set of dependency artifact coordinates to exclude. If none is present, then represents no exclusions. Artifact coordinatess may be given in simple groupId:artifactId form, or they may be fully qualified in the form groupId:artifactId:type:version[:classifier]. Additionally, wildcards can be used, as in *:maven-*" Classifiers are sometimes tricky, I find you need to explicitly list them as the default is that it is empty. Try mygroup:myartifact:*:sources And fiddle around. When you work it out, cosnider updating the documentation so your wisdom can benefit others. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to include the *-sources.jar in a binary distribution?
Paolo, Are the -sources an artifact of the same project that is running the assembly plugin? Off hand I'd suggest making a separate module to build the combined sources jar, and then you should be able to pull that into the assembly. Or, just use a pointing at the right file in target/ instead of referencing a dependency? On Mon, Nov 21, 2011 at 3:05 PM, Paolo Castagna wrote: > Hi, > I'd like to include the *-sources.jar in a lib-src/ directory in my > binary distribution (done via assembly) [1]. > The reason why I'd like to include the *-sources.jar in the binary > distribution is because people using IDEs (and not Maven) can point at > them and browse the sources of our modules. > > I tried doing this in my assembly-binary.xml [2] but I don't > understand why is not working as I would expect: > > > lib > false > > > lib > > > lib-src > > *:sources > > > > > > Can you help me? > > Thanks, > Paolo > > [1] https://svn.apache.org/repos/asf/incubator/jena/Jena2/JenaDist/trunk/ > [2] > https://svn.apache.org/repos/asf/incubator/jena/Jena2/JenaDist/trunk/assembly-binary.xml > > - > 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
Maven Surefire 2.11 release date
I noticed that Maven Surefire 2.10 was released this past september. In jira there are 8 issues associated with 2.11, all of which are closed. Is there any sense on when 2.11 will be sent for a vote on release? I'm particularly interested in the Junit Category support in the maven-surefire-plugin that is part of the 2.11 release. Thanks, Bob
Re: Maven surefire 2.11 release date
i cannot recall if kristian is aiming fir an 8 or 12 week average cycle... but it is likely to be close to one of those... we are volunteers you know ;-) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 21 Nov 2011 20:38, "Robert Jacoby" wrote: > I noticed that Maven Surefire 2.10 was released this past september. In > jira there are 8 issues associated with 2.11, all of which are closed. Is > there any sense on when 2.11 will be sent for a vote on release? I'm > particularly interested in the Junit Category support in the > maven-surefire-plugin that is part of the 2.11 release. > > Thanks, > Bob >
Maven surefire 2.11 release date
I noticed that Maven Surefire 2.10 was released this past september. In jira there are 8 issues associated with 2.11, all of which are closed. Is there any sense on when 2.11 will be sent for a vote on release? I'm particularly interested in the Junit Category support in the maven-surefire-plugin that is part of the 2.11 release. Thanks, Bob
How to include the *-sources.jar in a binary distribution?
Hi, I'd like to include the *-sources.jar in a lib-src/ directory in my binary distribution (done via assembly) [1]. The reason why I'd like to include the *-sources.jar in the binary distribution is because people using IDEs (and not Maven) can point at them and browse the sources of our modules. I tried doing this in my assembly-binary.xml [2] but I don't understand why is not working as I would expect: lib false lib lib-src *:sources Can you help me? Thanks, Paolo [1] https://svn.apache.org/repos/asf/incubator/jena/Jena2/JenaDist/trunk/ [2] https://svn.apache.org/repos/asf/incubator/jena/Jena2/JenaDist/trunk/assembly-binary.xml - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
plugin goal wont execute during process-test-resources phase
Hi
I am fairly new to configuring maven and i need to execute a goal of a
plugin but it wont execute when i do mvn process-test-resources. It seems
that the plugin goal is somehow unbound from the plugin phase.
I am attaching pom.xml here.
thanks for the help.
http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.xyz.sm.qatools
dashboard
war
2.5.0.0_RC4-SNAPSHOT
dashboard
3.0.0.RELEASE
1.6
1.3
localhost:11211
60
3.3.0.ga
3.2.6.ga
dashboard_db_test
com.mysql.jdbc.Driver
localhost
3306
${jdbc.test.username}
bugzilla_user
mysql-connector-java
mysql
5.1.6
com.sun.jersey
jersey-json
${jersey-version}
com.sun.jersey
jersey-server
${jersey-version}
com.sun.jersey
jersey-client
${jersey-version}
commons-beanutils
commons-beanutils
1.7.0
commons-collections
commons-collections
3.2
commons-lang
commons-lang
2.3
commons-logging
commons-logging
1.1
avalon-framework
avalon-framework
javax.servlet
servlet-api
logkit
logkit
commons-validator
commons-validator
1.3.1
commons-digester
commons-digester
net.sf.ezmorph
ezmorph
1.0.4
jfree
jcommon
1.0.12
jfree
jfreechart
1.0.8a
net.sf.json-lib
json-lib
2.3
jdk15
log4j
log4j
1.2.8
org.springframework
spring-webmvc
${spring.version}
org.springframework
spring-jdbc
${spring.version}
org.springframework
spring-context-support
${spring.version}
org.springframework
spring-test
${spring.version}
org.springframework
spring-tx
${spring.version}
org.springframework
spring-orm
${spring.version}
javax.servlet
servlet-api
2.3
provided
taglibs
standard
1.1.2
javax.servlet
jstl
1.1.2
org.apache.tomcat
dbcp
6.0.18
provided
org.hibernate
hibernate
${hibernate.version}
asm
asm
asm
asm-attrs
cglib
cglib
asm
asm
3.1
cglib
cglib-nodep
2.2
compile
javax.persistence
persistence-api
1.0
org.hibernate
hibernate-annotations
${hibernate.annotations.version}
org.apache.tika
tika-core
0.7
org.hibernate
hibernate-commons-annotations
${hibernate.annotations.version}
asm
asm
asm
asm-attrs
javax.transaction
jta
1.0.1B
org.hibernate
hibernate-validator
4.0.2.GA
org.slf4j
maven-war-plugin Dojo Build file being overwritten by the war plugin
The situation is that our web app has a /js directory containing our custom
JavaScript application files. In our release profile we are running a dojo
build that copies the src/js files into target/dojo-build and using maven exec
plugin to run the build. The built files are then copied into
${project.build.directory}\${project.build.finalName}\js so that they will
replace the unbuilt src files.
I added an exclusion for the src/js directory in the profile as well, but the
maven war plugin seems to ignore this. At package time the built files get
overwritten. Is there a better way to do this?
Thanks
Donald Smith
--- Confidentiality Notice:
This electronic mail transmission is confidential, may be privileged and should
be read or retained only by the intended recipient. If you have received this
transmission in error, please immediately notify the sender and delete it from
your system.
versions plugin does not show the maven-jar-plugin 2.3.2 as a new version
Hi! I'm using maven 3.0.3, which uses the maven-jar-plugin 2.3.1 as default (predefined in the super pom I think). If I run a mvn versions:display-plugin-updates then the maven-jar-plugin 2.3.2 does not shows in the list. Is it because I'm not explicitly declaring the use of the jar plugin in my pom.xml? That is, the versions plugin only works for the plugins I explicitly declare but not the ones in the super pom? Regards, Gabriel - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-dependency-plugin fails when using maven's multi-thread feature
FYI I recall correctly... ;-) On 21 November 2011 12:45, Stephen Connolly wrote: > The only way to avoid is to have the upstream modules as dependencies > of the downstream modules... IIRC I updated dependency:copy to > consider the reactor as a source of dependencies, in which case you > don't have to switch from dependency:copy to > dependency:copy-dependencies... but you will still have to add the > dependencies to your pom > > On 21 November 2011 12:19, tarand wrote: >> Sure, this works. But please note: we have many, many usages of this usage >> style of the dependency plugin. Thus it is hard work to change each and >> every location. We would like to avoid that. >> >> -- >> View this message in context: >> http://maven.40175.n5.nabble.com/maven-dependency-plugin-fails-when-using-maven-s-multi-thread-feature-tp5009857p5010376.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 >> >> > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-dependency-plugin fails when using maven's multi-thread feature
The only way to avoid is to have the upstream modules as dependencies of the downstream modules... IIRC I updated dependency:copy to consider the reactor as a source of dependencies, in which case you don't have to switch from dependency:copy to dependency:copy-dependencies... but you will still have to add the dependencies to your pom On 21 November 2011 12:19, tarand wrote: > Sure, this works. But please note: we have many, many usages of this usage > style of the dependency plugin. Thus it is hard work to change each and > every location. We would like to avoid that. > > -- > View this message in context: > http://maven.40175.n5.nabble.com/maven-dependency-plugin-fails-when-using-maven-s-multi-thread-feature-tp5009857p5010376.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 > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-dependency-plugin fails when using maven's multi-thread feature
Sure, this works. But please note: we have many, many usages of this usage style of the dependency plugin. Thus it is hard work to change each and every location. We would like to avoid that. -- View this message in context: http://maven.40175.n5.nabble.com/maven-dependency-plugin-fails-when-using-maven-s-multi-thread-feature-tp5009857p5010376.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: Workaround for manifestEntry bug
Hi Jan, honyk wrote: > Hello Everyone, > > I've refactored my ant-based library into maven based one, but I've > encounter the same issue reported as the blocker here: > http://jira.codehaus.org/browse/MSHARED-182 > > Seeing the date of creation of this ticket I suppose there is no prospect > of quick fix in the near future. > Is there another way to add custom items into the manifest.mf file via > Maven? We're configuring since years manifest as well as manifest entries for various plugins (jar, ear, ejb, rar, source, war and some own ones) and have no problem with it. However, we add typically always the default entries for implementation and specification (you can nevertheless overwrite these values individually in manifestEntries). Cheers, Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Migrating plugin to maven 3
no need to recompile... there is a need to re-test but not a major one! On 21 November 2011 11:05, Eyal Goren wrote: > Hi, > > So- we don't need to re-compile them again using maven 3? just try and run? > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Migrating-plugin-to-maven-3-tp501p5010205.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 > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Migrating plugin to maven 3
Hi, So- we don't need to re-compile them again using maven 3? just try and run? -- View this message in context: http://maven.40175.n5.nabble.com/Migrating-plugin-to-maven-3-tp501p5010205.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
Migration plugin from maven 2 to maven 3
Hi, I would like to start migrating our maven projects to maven 3, the issue is the plugins we are creating. What is the procedure to migrate plugins to maven 3? or we should just build them with Maven 3? Thanks -- View this message in context: http://maven.40175.n5.nabble.com/Migration-plugin-from-maven-2-to-maven-3-tp5010167p5010167.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: Migrating plugin to maven 3
They should just work. M3 is supposed to be 99.999% compat with m2 Note the 0.001 is to cover the hacks people have used that they shouldn't On 21 November 2011 09:42, Eyal Goren wrote: > Hi, > > I am using today maven 2, and would like to migrate to maven 3. > > I am having few plugins that I compile for my usage, in maven 2. > > My question is- what is the migration procedure to use them in Maven 3 as > well? > > Thanks > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Migrating-plugin-to-maven-3-tp501p501.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 > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Migrating plugin to maven 3
Hi, I am using today maven 2, and would like to migrate to maven 3. I am having few plugins that I compile for my usage, in maven 2. My question is- what is the migration procedure to use them in Maven 3 as well? Thanks -- View this message in context: http://maven.40175.n5.nabble.com/Migrating-plugin-to-maven-3-tp501p501.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-dependency-plugin fails when using maven's multi-thread feature
the copy goal works best for dependencies outside the reactor. if your copying dependencies from within the reactor you should use the copy-dependencies goal instead (side effect is you will have to add the artifacts as dependencies thus giving maven the required build ordering info) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 21 Nov 2011 08:54, "tarand" wrote: > I'm experieting with maven-3's multi-threading feature, as it looks > promising. Unfortunately I have basic problems with the dependency-plugin > (version 2.3): We are using the copy-goal, the configuration style with > . Whenever one of these artifacts have to be built within > the > same reactor, it happens that the dependent artifact has not been built > before, and we encounter an "artifact-not-found" error. > > Is that a know issue with the threading feature, or do we make a mistake? > > -- > View this message in context: > http://maven.40175.n5.nabble.com/maven-dependency-plugin-fails-when-using-maven-s-multi-thread-feature-tp5009857p5009857.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 > >
maven-dependency-plugin fails when using maven's multi-thread feature
I'm experieting with maven-3's multi-threading feature, as it looks promising. Unfortunately I have basic problems with the dependency-plugin (version 2.3): We are using the copy-goal, the configuration style with . Whenever one of these artifacts have to be built within the same reactor, it happens that the dependent artifact has not been built before, and we encounter an "artifact-not-found" error. Is that a know issue with the threading feature, or do we make a mistake? -- View this message in context: http://maven.40175.n5.nabble.com/maven-dependency-plugin-fails-when-using-maven-s-multi-thread-feature-tp5009857p5009857.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
