Which versions of nexus-indexer and lucene-core are compatible with each other
Hi All, I am in need of upgrading my nexus indexer to nexus-indexer-3.0.1, I want to know which version of lucene-core would be compatible with. Is there any link/location where I can get the table of compatibility. Thanks, Amaresh
How to use Maven with a different (=non-default) project structure?
Assume I want (or have) to use a different project structure from the built-in default project structure of Maven (=the one which is generated by archetype:generate). Where do I have to adjust maven config files resp. in pom.xml to be able to use the new project structure? Ben -- View this message in context: http://maven.40175.n5.nabble.com/How-to-use-Maven-with-a-different-non-default-project-structure-tp3204372p3204372.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: How to use Maven with a different (=non-default) project structure?
2010/10/8 benxs bxsto...@yahoo.co.uk: Assume I want (or have) to use a different project structure from the built-in default project structure of Maven (=the one which is generated by archetype:generate). Where do I have to adjust maven config files resp. in pom.xml to be able to use the new project structure? http://maven.apache.org/general.html#dir-struct Anyway I strongly suggest to use Eclipse+m2eclipse POM Editor (with advanced tabs enabled) because it's really easier to use. Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven generated MANIFEST.MF: Commit or ignore?
They get packaged into the artifact itself. No need to commit Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time -Original Message- From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict Sent: Thursday, October 07, 2010 8:31 PM To: Maven Users List Subject: Maven generated MANIFEST.MF: Commit or ignore? Can anyone recommend whether to SCM commit the generated MANIFEST.MF files? Or should they just be ignored? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven 3.0 has landed!
The day has finally come, Maven 3.0 is here: http://www.sonatype.com/people/2010/10/maven-3-0-has-landed/ Big thanks to Benjamin Bentmann!! Come and get it! http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.zip http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.tar.gz Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham
RE: How to use Maven with a different (=non-default) project structure?
Look at the Maven SuperPOM ( http://maven.apache.org/guides/introduction/introduction-to-the-pom.html #Super_POM ) since that is where the *defaults* come from. In the start of the build section properties are set for where source and test code is plus some other items. I put all of those, as-is but commented out into the our Maven *template* we provide on the assumption that Maven is easy once you know what drives what. ;-) Curt Yanko | Continuous Integration Services Making IT Happen, one build at a time -Original Message- From: benxs [mailto:bxsto...@yahoo.co.uk] Sent: Friday, October 08, 2010 6:25 AM To: users@maven.apache.org Subject: How to use Maven with a different (=non-default) project structure? Assume I want (or have) to use a different project structure from the built-in default project structure of Maven (=the one which is generated by archetype:generate). Where do I have to adjust maven config files resp. in pom.xml to be able to use the new project structure? Ben -- View this message in context: http://maven.40175.n5.nabble.com/How-to-use-Maven-with-a-different-non-d efault-project-structure-tp3204372p3204372.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 This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 has landed!
Le Fri, 8 Oct 2010 08:06:42 -0400, Jason van Zyl ja...@sonatype.com a écrit : The day has finally come, Maven 3.0 is here: http://www.sonatype.com/people/2010/10/maven-3-0-has-landed/ Big thanks to Benjamin Bentmann!! Oura oura! Thanks for our time maven guys. Come and get it! For sure ;) http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.zip http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.tar.gz Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Archetype and post creation tasks
Hello everyone, trying to figure out the Maven way to do the following: I created an archetype that sets up a multi module project. After the creation of the new project, I want to run some other tasks, in my case there should be some classes generated from a database schema. I already created a Maven mojo as a wrapper for that generator, because one should also be able to call it independently. Regarding ease of use, the project creation and generation of files should be performed with one single command (so I don't want to do 'mvn archetype:generate[...]' and then 'cd newproject; mvn mygenerator:generate') and that's exactly my problem: how can I achieve that in a clean way? I already thought about creating another mojo that wraps the archetype and plugin calls, but that feels rather bumpy... What's the recommended way to do something like this? Thanks for any hints. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Archetype and post creation tasks
2010/10/8 Michael Sonntag frob...@googlemail.com: I created an archetype that sets up a multi module project. After the creation of the new project, I want to run some other tasks, in my case there should be some classes generated from a database schema. I already created a Maven mojo as a wrapper for that generator, because one should also be able to call it independently. Regarding ease of use, the project creation and generation of files should be performed with one single command (so I don't want to do 'mvn archetype:generate[...]' and then 'cd newproject; mvn mygenerator:generate') and that's exactly my problem: how can I achieve that in a clean way? I already thought about creating another mojo that wraps the archetype and plugin calls, but that feels rather bumpy... What's the recommended way to do something like this? Try goals parameter: http://maven.apache.org/archetype/maven-archetype-plugin/generate-mojo.html#goals However, since I've never tried it, I don't know if these goals are executed before or after the project generation. Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Archetype and post creation tasks
On Fri, Oct 8, 2010 at 7:23 AM, Michael Sonntag frob...@googlemail.com wrote: ... Regarding ease of use, the project creation and generation of files should be performed with one single command (so I don't want to do 'mvn archetype:generate[...]' and then 'cd newproject; mvn mygenerator:generate') ... take a look at http://docs.codehaus.org/display/MAVENUSER/Allow+goals+to+be+attached+to+post+Velocity+template+process+in+archetype+generation something like what is proposed there is probably what you want - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 has landed!
w00t! Great news! Thanks to everyone involved. Just one question: when will the maven site be updated to offer m3 in the downloads page? On Oct 8, 2010 8:07 AM, Jason van Zyl ja...@sonatype.com wrote: The day has finally come, Maven 3.0 is here: http://www.sonatype.com/people/2010/10/maven-3-0-has-landed/ Big thanks to Benjamin Bentmann!! Come and get it! http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.zip http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.tar.gz Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham
Re: Maven 3.0 has landed!
Ryan Connolly wrote: when will the maven site be updated to offer m3 in the downloads page? The updated site is already deployed and merely awaits its sync to the live server. Benjamin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 has landed!
Right on. Thanks Benjamin! On Oct 8, 2010 8:54 AM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Ryan Connolly wrote: when will the maven site be updated to offer m3 in the downloads page? The updated site is already deployed and merely awaits its sync to the live server. Benjamin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven generated MANIFEST.MF: Commit or ignore?
In some cases, if you're strongly relying on your IDE (this is the case for me with eclipse RSA websphere integration), it can be useful to commit this on your SCM. But generally, everything generated should be ignored :-) Frédéric On Fri, Oct 8, 2010 at 2:03 PM, Yanko, Curtis curt_ya...@uhc.com wrote: They get packaged into the artifact itself. No need to commit Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time -Original Message- From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com] On Behalf Of Paul Benedict Sent: Thursday, October 07, 2010 8:31 PM To: Maven Users List Subject: Maven generated MANIFEST.MF: Commit or ignore? Can anyone recommend whether to SCM commit the generated MANIFEST.MF files? Or should they just be ignored? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 has landed!
The ZIP appears to be working fine, but the tar.gz is only downloading a 12.3K file --- Nayan Hajratwala http://agileshrugged.com http://twitter.com/nhajratw 734.658.6032 On Oct 8, 2010, at 8:06 AM, Jason van Zyl wrote: The day has finally come, Maven 3.0 is here: http://www.sonatype.com/people/2010/10/maven-3-0-has-landed/ Big thanks to Benjamin Bentmann!! Come and get it! http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.zip http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.tar.gz Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven 3.0 Released
The Maven team is pleased to announce the release of Apache Maven 3.0. Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project. You can read more here: http://maven.apache.org/ Downloads of source and binary distributions are listed in our download section: http://maven.apache.org/download.html A major goal of Maven 3.0 is to be compatible, to the extent possible, with existing plugins and projects designed for Maven 2.x. Users interested in upgrading to this new major release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x: http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html If you encounter unexpected problems while using Maven 3.0, please feel free to contact us via the Maven developer list: http://maven.apache.org/mail-lists.html Last but not least, the Maven team would like to thank all the users that tested the various alphas/betas/RCs and provided valuable feedback that helped us to eventually release a solid Maven 3.0! Release Notes - Maven 2 3 - Version 3.0 (since 3.0-beta-3 only) ** Bug * [MNG-4592] - Snapshot artifacts that could not be downloaded due to communication problems are blacklisted for a day by default. * [MNG-4751] - Snapshot version not resolved for version range * [MNG-4785] - NPE in dependency resolution code for TC plugin * [MNG-4786] - [regression] Ant-based mojo using maven-script-ant:2.1.0+ cause NPE * [MNG-4788] - [regression] Appassembler Maven Plugin doesn't work like as it should * [MNG-4789] - [regression] Difference in compile scope dependency resolution * [MNG-4791] - [regression] POM artifacts passed into MavenProjectBuilder.buildFromRepository() are no longer resolved * [MNG-4793] - Unable to obtain archiver for extension 'zip' * [MNG-4794] - 'org.apache.maven.plugins:maven-install-plugin:2.3.1'. A required class is missing: org.codehaus.plexus.digest.Digester * [MNG-4795] - [regression] Dependencies in forked reactor projects are not resolved when aggregator bound to lifecycle forks * [MNG-4800] - Conflict resolution does not pick sub tree of nearest dependency if farther conflicting dependency has wider scope * [MNG-4810] - Maven cannot build if loaded in a classloader that is not backed by a real JAR file / classpath * [MNG-4811] - Custom Maven Plugin regression in Maven 3.x, custom ComponentConfigurator causes infinite loop * [MNG-4814] - Eary dependency resolution attempts for reactor projects prevent their later resolution from the reactor * [MNG-4818] - NPE in legacy.DefaultWagonManager.getArtifact * [MNG-4829] - [regression] Checksum failures aren't logged * [MNG-4832] - Maven 3 Regression: Missing constructor of org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter * [MNG-4834] - [regression] MavenProject.getParent() ignores configured repositories * [MNG-4836] - Incorrect recursive expression cycle errors (update plexus-interpolation) * [MNG-4837] - Interpolation error due to cyclic expression for one of the POM coordinates gets needlessly repeated * [MNG-4842] - [regression] Repositories discovered in dependency POMs override repositories configured for original resolution request of POM * [MNG-4845] - [regression] MavenProject.getDependencyArtifact() returns artifacts without version for dependency with version range ** Improvement * [MNG-4452] - Metadata for snapshots should include classifier * [MNG-4787] - Allow class realm manager delegates to alter public part of Maven core realm * [MNG-4815] - (3.0-RC1) Maven Java API does not give nice error messages when improperly configured * [MNG-4824] - multiple failures need additional whitespace * [MNG-4825] - Relative path errors could be more explicit ** New Feature * [MNG-4484] - Create a Maven API for component configuration ** Task * [MNG-4805] - Update default plugin versions used for built-in lifecycle mappings * [MNG-4807] - Extend core artifact filter to exclude relocated Guice-based Plexus shim ** Wish * [MNG-4796] - add a warning when profiles.xml is used (Maven 2) or detected (Maven 3) Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 has landed!
On 8 October 2010 14:09, Nayan Hajratwala na...@chikli.com wrote: The ZIP appears to be working fine, but the tar.gz is only downloading a 12.3K file the tar.gz looks fine on the main Apache distribution site, so I'd guess this is a mirror issue - perhaps it's not yet fully sync'd --- Nayan Hajratwala http://agileshrugged.com http://twitter.com/nhajratw 734.658.6032 On Oct 8, 2010, at 8:06 AM, Jason van Zyl wrote: The day has finally come, Maven 3.0 is here: http://www.sonatype.com/people/2010/10/maven-3-0-has-landed/ Big thanks to Benjamin Bentmann!! Come and get it! http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.zip http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.tar.gz Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Cheers, Stuart
Re: [ANN] Apache Maven 3.0 Released
Big up ! :) Thanks a lot for all the work and ... can't wait for the pom mixins ;) /Paul - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[Dependencies] Build fails from parent pom but works from module pom
Hi guys ! I work on a portlet project so some dependencies are provided by the portal (ie hibernate, spring etc...). My project has 2 modules : -parent |_services |_ui Hibernate is a dependency from the services module. The services module is a dependency from the ui module. I use classes from Hibernate in the ui module (DetachedCriteria), so I expect the hibernate dependency to be known by the ui module. Here is the weird thing : - ui module build is successfull when executed from his pom file. - ui module build fails with a package org.hibernate[...] does not exist error when executed from the parent pom file. Indeed as I watch the output of the mvn dependency:tree command for both locations (parent ui module), I don't get the same tree (hibernate dependency doesn't show in the ui tree generated from the parent pom). My workaround is to re-call the hibernate dependency in the ui pom file, but in my opinion Maven should resolve this alone... Any thoughts ? Romain WILBERT
Re: [Dependencies] Build fails from parent pom but works from module pom
2010/10/8 r.wilb...@akka.eu: My project has 2 modules : -parent |_services |_ui Hibernate is a dependency from the services module. With which scope? IIRC only if you have compile or runtime it becomes a transitive dependency. Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Apache Maven 3.0 Released
Thanks a lot for Maven 3.0! Thanks a lot for all the work and ... can't wait for the pom mixins ;) Speaking of which, it seems to me that POM mixins would offer a more flexible alternative to what is currently achieved by the packaging types' lifecycle bindings. Are there any plans to eventually supplant the current ad-hoc mechanism with a mixin-based approach? (After all, just because I want a JAR doesn't mean I want the Java compiler.) Best wishes, Andreas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [Dependencies] Build fails from parent pom but works from module pom
We are building a large portlet project (60+ maven projects) and have developed a pretty good methodology. I have described it a few times in the forum. It works well with Spring, Hibernate, MySQL, Jetspeed, CXF, and about 50 other common libraries from Apache and others. Ron On 08/10/2010 9:45 AM, r.wilb...@akka.eu wrote: Hi guys ! I work on a portlet project so some dependencies are provided by the portal (ie hibernate, spring etc...). My project has 2 modules : -parent |_services |_ui Hibernate is a dependency from the services module. The services module is a dependency from the ui module. I use classes from Hibernate in the ui module (DetachedCriteria), so I expect the hibernate dependency to be known by the ui module. Here is the weird thing : - ui module build is successfull when executed from his pom file. - ui module build fails with a package org.hibernate[...] does not exist error when executed from the parent pom file. Indeed as I watch the output of the mvn dependency:tree command for both locations (parent ui module), I don't get the same tree (hibernate dependency doesn't show in the ui tree generated from the parent pom). My workaround is to re-call the hibernate dependency in the ui pom file, but in my opinion Maven should resolve this alone... Any thoughts ? Romain WILBERT - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 has landed!
The day has finally come, Maven 3.0 is here: Awesome! Thanks to everyone involved for their persistance and hard work. This release ROCKS! Time to ditch Maven 2x for me today! Yeah.. manfred - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 has landed!
Are you using Safari? There's a long standing issue that it would download a HTML page instead for the .gz when you go via the mirror script. - Brett On 09/10/2010, at 12:09 AM, Nayan Hajratwala wrote: The ZIP appears to be working fine, but the tar.gz is only downloading a 12.3K file --- Nayan Hajratwala http://agileshrugged.com http://twitter.com/nhajratw 734.658.6032 On Oct 8, 2010, at 8:06 AM, Jason van Zyl wrote: The day has finally come, Maven 3.0 is here: http://www.sonatype.com/people/2010/10/maven-3-0-has-landed/ Big thanks to Benjamin Bentmann!! Come and get it! http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.zip http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-3.0-bin.tar.gz Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Phase between install and deploy?
On Thu, Oct 7, 2010 at 2:09 PM, Jesse Farinacci jie...@gmail.com wrote: Please describe why the verify phase is not appropriate? I want to disallow deployment if a certain property is not set to a certain value. I don't want to disallow compile or install. Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Phase between install and deploy?
On Thu, Oct 7, 2010 at 2:14 PM, Brian Topping topp...@codehaus.org wrote: You can create a custom lifecycle for that build, then bind where you want. http://www.sonatype.com/books/mvnref-book/reference/writing-plugins-sect-custom-lifecycle.html Thanks. I will see if this help us. Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Clean up unpacked dependencies...
On Thu, Oct 7, 2010 at 5:40 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
they will be being extracted into a sub-folder of ${basedir}/target if
you are following the Maven way... given some of your mail threads I
will not assume that you are following the Maven way ;-)
If you follow the Maven way then clean will tidy up as by default
clean removes the target folder and all its contents
Thanks! For some reason I hadn't even tried it without an
outputDirectory before, but knowing this pretty much convinces me to
use the default.
Although you have to admit deps is a lot shorter to type than
target\dependency :)
Phillip
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Clean up unpacked dependencies...
Phillip Hellewell wrote:
On Thu, Oct 7, 2010 at 5:40 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
they will be being extracted into a sub-folder of ${basedir}/target if
you are following the Maven way... given some of your mail threads I
will not assume that you are following the Maven way ;-)
If you follow the Maven way then clean will tidy up as by default
clean removes the target folder and all its contents
Thanks! For some reason I hadn't even tried it without an
outputDirectory before, but knowing this pretty much convinces me to
use the default.
Although you have to admit deps is a lot shorter to type than
target\dependency :)
As a rule of thumb: Put anything that is somehow generated, downloaded,
unpacked, ... into a subfolder of target.
- Jörg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Release Plugin 2.1 Released
The Maven team is pleased to announce the release of the Maven Release Plugin, version 2.1 This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. http://maven.apache.org/plugins/maven-release-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.1/version /plugin Release Notes - Maven Release Plugin - Version 2.1 ** Bug * [MRELEASE-128] - SCM properties being replaced during release:perform * [MRELEASE-317] - release:prepare should fail if any pom depends on SNAPSHOT parent * [MRELEASE-318] - Release plugin throws NullPointerException when using version range for dependency * [MRELEASE-350] - Option '0' for specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): is broken * [MRELEASE-370] - release:prepare is not updating inter-modules dependencies to the next version snapshot identifier correctly (-DdryRun=true). * [MRELEASE-458] - Branch Does Not Honor updateWorkingCopyVersions Setting * [MRELEASE-524] - command line versions don't seem to work on release:branch for specific format * [MRELEASE-536] - CommonBasedir Calculation fails on windows * [MRELEASE-546] - regression introduced in MRELEASE-261 * [MRELEASE-551] - Unable to release with maven 3 when having no $HOME/.m2/settings.xml * [MRELEASE-563] - help strings need help, they are not helpful out of context * [MRELEASE-586] - release:perform - The temporary file pom.xml.branch should be ignored as pom.xml.next and pom.xml.tag are ignored * [MRELEASE-589] - Resolved dependencies overwritten when multiple subprojects with SNAPSHOT dependencies are released ** Improvement * [MRELEASE-497] - Don't overwrite SVN auth cache * [MRELEASE-530] - Git provider does 'git push' during 'mvn release:prepare' which causes unwanted problems (scm 1.4 upgrade) * [MRELEASE-554] - Allow custom files to be modified before doing a prepare or branch... * [MRELEASE-583] - Better Snapshot Dependency Handling Enjoy, -The Maven team -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Copy an artifact
Hi, I have another dumb question here. Is there any way to use dependency:copy without a pom.xml file? Like by specifying the artifact name/ver/etc on the command-line? If not, is there another plugin that does this? Or do all plugins require a pom file to be present? Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Copy an artifact
On Fri, Oct 8, 2010 at 1:14 PM, Phillip Hellewell ssh...@gmail.com wrote: Is there any way to use dependency:copy without a pom.xml file? Like by specifying the artifact name/ver/etc on the command-line? It usually works better if you describe the problem you're trying to solve. :) Most likely someone has run into it before and can suggest a solution, which may or may not be what you've already come up with. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Clean up unpacked dependencies...
On Fri, Oct 8, 2010 at 10:58 AM, Jörg Schaible joerg.schai...@gmx.de wrote: As a rule of thumb: Put anything that is somehow generated, downloaded, unpacked, ... into a subfolder of target. Thanks. Sounds like a good practice to me. I just have one question. How does Maven know which files/folders inside of target/ to upload when doing an install/deploy? Earlier I was kinda under the impression that anything that got put into the target/ directory was what would get uploaded. Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Clean up unpacked dependencies...
The 'install' goal just puts the generated/attached artifacts into your repository. deploy I havent used (yet) so I cant say. On Fri, Oct 8, 2010 at 10:28 AM, Phillip Hellewell ssh...@gmail.com wrote: On Fri, Oct 8, 2010 at 10:58 AM, Jörg Schaible joerg.schai...@gmx.de wrote: As a rule of thumb: Put anything that is somehow generated, downloaded, unpacked, ... into a subfolder of target. Thanks. Sounds like a good practice to me. I just have one question. How does Maven know which files/folders inside of target/ to upload when doing an install/deploy? Earlier I was kinda under the impression that anything that got put into the target/ directory was what would get uploaded. Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Clean up unpacked dependencies...
On Fri, Oct 8, 2010 at 11:35 AM, Jon Paynter kittl...@gmail.com wrote: The 'install' goal just puts the generated/attached artifacts into your repository. This is just out of pure curiosity. How does it know which ones were generated/attached? Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Clean up unpacked dependencies...
On Fri, Oct 8, 2010 at 10:39 AM, Phillip Hellewell ssh...@gmail.com wrote: On Fri, Oct 8, 2010 at 11:35 AM, Jon Paynter kittl...@gmail.com wrote: The 'install' goal just puts the generated/attached artifacts into your repository. This is just out of pure curiosity. How does it know which ones were generated/attached? Well based on what ive seen -- binary artifacts ie, jar, war, ear and pom files are all generated, so they get installed. Then any assemblies that you have marked as attached will also get installed. there may be other criteria - but thats what ive gatherd from observation.
Re: Clean up unpacked dependencies...
On Fri, Oct 8, 2010 at 11:39 AM, Phillip Hellewell ssh...@gmail.com wrote: On Fri, Oct 8, 2010 at 11:35 AM, Jon Paynter kittl...@gmail.com wrote: The 'install' goal just puts the generated/attached artifacts into your repository. This is just out of pure curiosity. How does it know which ones were generated/attached? Does it somehow ask the goals bound to the package phase or something? Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Clean up unpacked dependencies...
On Fri, Oct 8, 2010 at 11:47 AM, Jon Paynter kittl...@gmail.com wrote: Well based on what ive seen -- binary artifacts ie, jar, war, ear and pom files are all generated, so they get installed. Then any assemblies that you have marked as attached will also get installed. Just for fun I did a test and created a bunch of files in my target dir named artifact-version.zip, artifact-version.jar, etc. But it only installed the one that was actually generated by the package step. So I don't know how it could possible know, unless it somehow asks the plugin whose goals are bound to the package phase what it generated. Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Copy an artifact
On Fri, Oct 8, 2010 at 11:21 AM, Wendy Smoak wsm...@gmail.com wrote: It usually works better if you describe the problem you're trying to solve. :) Most likely someone has run into it before and can suggest a solution, which may or may not be what you've already come up with. The problem I am trying to solve is that I just want to download an artifact to take a quick look at it without having to write a pom.xml file to get it. Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Copy an artifact
On Fri, Oct 8, 2010 at 12:04 PM, Phillip Hellewell ssh...@gmail.com wrote:
The problem I am trying to solve is that I just want to download an
artifact to take a quick look at it without having to write a pom.xml
file to get it.
I suppose I could just use wget with the repository, e.g., wget
${repo}/groupId/artifactId/ver/artifact-ver.zip, but that seems like a
bad practice since it requires intimate knowledge of how repositories
are laid out. Also, I'd need to change . to / in the groupId.
And there's probably something else I haven't thought of.
Phillip
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Copy an artifact
On Fri, Oct 8, 2010 at 2:09 PM, Phillip Hellewell ssh...@gmail.com wrote:
On Fri, Oct 8, 2010 at 12:04 PM, Phillip Hellewell ssh...@gmail.com wrote:
The problem I am trying to solve is that I just want to download an
artifact to take a quick look at it without having to write a pom.xml
file to get it.
I suppose I could just use wget with the repository, e.g., wget
${repo}/groupId/artifactId/ver/artifact-ver.zip, but that seems like a
bad practice since it requires intimate knowledge of how repositories
are laid out. Also, I'd need to change . to / in the groupId.
And there's probably something else I haven't thought of.
I would search or browse for it in Archiva (or your repository
manager) and download it from there -- no need to know the repository
format.
You've already worked out the formula if you want to use wget --
groupId with / instead of ., then artifactId then version.
--
Wendy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Antrun plugin 1.5 broken
Hi,
I've been using the antrun plugin (1.3) to do some post processing on
my generated JPA models using the replaceregexp task, e.g.:
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idmodify-hibernate-models/id
phasegenerate-sources/phase
goals
goalrun/goal
/goals
configuration
tasks
replaceregexp
file=${project.build.directory}/generated-sources/hibernate3/com/{redacted}persistence/model/BillingPolicy.java
match=(.*name=quot;periodquot;.*) replace=\1
@javax.persistence.Enumerated(javax.persistence.EnumType.STRING)
byline=true /
!-- snip --
/tasks
/configuration
/execution
/executions
/plugin
This has worked fine for me all along. However, after upgrading to 1.5
I start getting sax parse errors:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.5:run
(modify-hibernate-models) on project das-common-persistence: An Ant
BuildException has occured: Element type replaceregexp must be
followed by either attribute specifications, or /. - [Help 1]
It appears that the new strategy is to emit a temporary ant build.xml
file that is then run. The problem is that when this is done, the
quote entities in my regular expression above are expanded when this
file is written and the following is generated:
project name=maven-antrun- default=main
target name=main
replaceregexp replace=\1
@javax.persistence.Enumerated(javax.persistence.EnumType.STRING)
byline=true file={redacted}/BillingPolicy.java
match=(.*name=period.*)/
!-- snip --
/target
/project
This breaks the match attribute and fails my build.
Any ideas?
Thanks,
Charles
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Clean up unpacked dependencies...
plugins attach artifacts they generate to the reactor. you can also use build-helper-maven-plu...@mojo to attach artifacts if you are hacking about off the maven way (which you seem unnaturally prone to do) -Stephen On 8 October 2010 18:51, Phillip Hellewell ssh...@gmail.com wrote: On Fri, Oct 8, 2010 at 11:47 AM, Jon Paynter kittl...@gmail.com wrote: Well based on what ive seen -- binary artifacts ie, jar, war, ear and pom files are all generated, so they get installed. Then any assemblies that you have marked as attached will also get installed. Just for fun I did a test and created a bunch of files in my target dir named artifact-version.zip, artifact-version.jar, etc. But it only installed the one that was actually generated by the package step. So I don't know how it could possible know, unless it somehow asks the plugin whose goals are bound to the package phase what it generated. Phillip - 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
Update new release 2.1 plugin to Artifactory?
How can I manually deploy the new release plugin version 2.1 to Artifactory? -- C. Benson Manica cbman...@gmail.com
Re: Update new release 2.1 plugin to Artifactory?
On Fri, Oct 8, 2010 at 3:24 PM, C. Benson Manica cbman...@gmail.com wrote: How can I manually deploy the new release plugin version 2.1 to Artifactory? Maybe something to ask on an Artifactory users mailing list? In general, you can use mvn deploy:deploy-file ... from the command line, but you'll need to make sure it gets the metadata right, plugins are sensitive to that. And you may need to deploy other artifacts that the plugin depends on. I'm not sure if Artifactory has a web form where you can upload things. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Copy an artifact
On Fri, Oct 8, 2010 at 12:15 PM, Wendy Smoak wsm...@gmail.com wrote: I would search or browse for it in Archiva (or your repository manager) and download it from there -- no need to know the repository format. You've already worked out the formula if you want to use wget -- groupId with / instead of ., then artifactId then version. That or I guess I could just create a dumb little pom file. On a related note, is there an easy way to create a pom that cannot be installed/deployed? E.g., if I'm just using a pom as a means to download an artifact and I don't want someone to accidentally try to install or deploy it, because it's not a real artifact. Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Copy an artifact
On Fri, Oct 8, 2010 at 2:22 PM, Phillip Hellewell ssh...@gmail.com wrote: On a related note, is there an easy way to create a pom that cannot be installed/deployed? E.g., if I'm just using a pom as a means to download an artifact and I don't want someone to accidentally try to install or deploy it, because it's not a real artifact. One thing I can think of is using the enforcer plugin in the compile phase with a rule that always fails. But I wonder if there is an easier way, like leaving the artifactId empty. Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven 3.0
Does maven-enforcer-plugin with maven 3.0? The same rules are working correctly in 2.0. I have the following error: [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-versions) @ cbsp --- [WARNING] This rule is not compatible with the current version of Maven. The rule is not able to perform any checks. [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVersion failed with message: Java version: 1.6.0_20 is required [INFO] Thanks.
Re: Clean up unpacked dependencies...
On Fri, Oct 8, 2010 at 1:23 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: plugins attach artifacts they generate to the reactor. you can also use build-helper-maven-plu...@mojo to attach artifacts if you are hacking about off the maven way (which you seem unnaturally prone to do) Thanks. That wasn't really what I was getting at, but it is good to know in case I need it someday. Phillip - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Update new release 2.1 plugin to Artifactory?
You can build the plugin and deploy it as part of the build or you can use the Artifactory web UI to deploy it. No need to worry about plugins metadata etc. - Artifactory will recalculate it on the fly. On Fri, Oct 8, 2010 at 10:21 PM, Wendy Smoak wsm...@gmail.com wrote: On Fri, Oct 8, 2010 at 3:24 PM, C. Benson Manica cbman...@gmail.com wrote: How can I manually deploy the new release plugin version 2.1 to Artifactory? Maybe something to ask on an Artifactory users mailing list? In general, you can use mvn deploy:deploy-file ... from the command line, but you'll need to make sure it gets the metadata right, plugins are sensitive to that. And you may need to deploy other artifacts that the plugin depends on. I'm not sure if Artifactory has a web form where you can upload things. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Clean up unpacked dependencies...
The plugins are responsible for registering their artifacts into the model. The build-helper-maven plugin has a goal that will let you attach files from the pom On Oct 8, 2010, at 1:51 PM, Phillip Hellewell ssh...@gmail.com wrote: On Fri, Oct 8, 2010 at 11:47 AM, Jon Paynter kittl...@gmail.com wrote: Well based on what ive seen -- binary artifacts ie, jar, war, ear and pom files are all generated, so they get installed. Then any assemblies that you have marked as attached will also get installed. Just for fun I did a test and created a bunch of files in my target dir named artifact-version.zip, artifact-version.jar, etc. But it only installed the one that was actually generated by the package step. So I don't know how it could possible know, unless it somehow asks the plugin whose goals are bound to the package phase what it generated. Phillip - 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 3.0
It's telling you the rule doesn't work in 3.x, that's the current state. 3.x has similar functionality built in Sent from my iPad On Oct 8, 2010, at 4:33 PM, Jason Chaffee jchaf...@ebates.com wrote: Does maven-enforcer-plugin with maven 3.0? The same rules are working correctly in 2.0. I have the following error: [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-versions) @ cbsp --- [WARNING] This rule is not compatible with the current version of Maven. The rule is not able to perform any checks. [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVersion failed with message: Java version: 1.6.0_20 is required [INFO] Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven 3.0
So is there documentation on how I can configure that rule in 3.0? I looked around the site, couldn't find anything. Thanks. -Original Message- From: Brian Fox [mailto:bri...@infinity.nu] Sent: Friday, October 08, 2010 2:53 PM To: Maven Users List Subject: Re: maven 3.0 It's telling you the rule doesn't work in 3.x, that's the current state. 3.x has similar functionality built in Sent from my iPad On Oct 8, 2010, at 4:33 PM, Jason Chaffee jchaf...@ebates.com wrote: Does maven-enforcer-plugin with maven 3.0? The same rules are working correctly in 2.0. I have the following error: [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-versions) @ cbsp --- [WARNING] This rule is not compatible with the current version of Maven. The rule is not able to perform any checks. [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVersion failed with message: Java version: 1.6.0_20 is required [INFO] Thanks. - 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 3.0
I have this rule set up running under 3.0 and it works fine: rules requireJavaVersion version1.6/version /requireJavaVersion ... /rules What's the tag for the rule that is failing for you? --- Nayan Hajratwala http://agileshrugged.com http://twitter.com/nhajratw 734.658.6032 On Oct 8, 2010, at 6:00 PM, Jason Chaffee wrote: So is there documentation on how I can configure that rule in 3.0? I looked around the site, couldn't find anything. Thanks. -Original Message- From: Brian Fox [mailto:bri...@infinity.nu] Sent: Friday, October 08, 2010 2:53 PM To: Maven Users List Subject: Re: maven 3.0 It's telling you the rule doesn't work in 3.x, that's the current state. 3.x has similar functionality built in Sent from my iPad On Oct 8, 2010, at 4:33 PM, Jason Chaffee jchaf...@ebates.com wrote: Does maven-enforcer-plugin with maven 3.0? The same rules are working correctly in 2.0. I have the following error: [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-versions) @ cbsp --- [WARNING] This rule is not compatible with the current version of Maven. The rule is not able to perform any checks. [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVersion failed with message: Java version: 1.6.0_20 is required [INFO] Thanks. - 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 3.0
This is what I have:
properties
java.version1.6.0_20/java.version
/properties
rules
requireJavaVersion
version[${java.version},)/version
messageJava version: ${java.version} is required/message
/requireJavaVersion
/rules
-Original Message-
From: Nayan Hajratwala [mailto:na...@chikli.com]
Sent: Friday, October 08, 2010 3:29 PM
To: Maven Users List
Subject: Re: maven 3.0
I have this rule set up running under 3.0 and it works fine:
rules
requireJavaVersion
version1.6/version
/requireJavaVersion
...
/rules
What's the tag for the rule that is failing for you?
---
Nayan Hajratwala
http://agileshrugged.com
http://twitter.com/nhajratw
734.658.6032
On Oct 8, 2010, at 6:00 PM, Jason Chaffee wrote:
So is there documentation on how I can configure that rule in 3.0? I
looked around the site, couldn't find anything.
Thanks.
-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu]
Sent: Friday, October 08, 2010 2:53 PM
To: Maven Users List
Subject: Re: maven 3.0
It's telling you the rule doesn't work in 3.x, that's the current
state. 3.x has similar functionality built in
Sent from my iPad
On Oct 8, 2010, at 4:33 PM, Jason Chaffee jchaf...@ebates.com wrote:
Does maven-enforcer-plugin with maven 3.0? The same rules are
working
correctly in 2.0.
I have the following error:
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce
(enforce-versions)
@
cbsp ---
[WARNING] This rule is not compatible with the current version of
Maven.
The rule is not able to perform any checks.
[WARNING] Rule 1:
org.apache.maven.plugins.enforcer.RequireJavaVersion
failed with message:
Java version: 1.6.0_20 is required
[INFO]
Thanks.
-
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: Antrun plugin 1.5 broken
amp;quot;
would that work?
-Stephen
P.S. yep a hack I know
On 8 October 2010 20:09, Charles Hudak meadand...@gmail.com wrote:
Hi,
I've been using the antrun plugin (1.3) to do some post processing on
my generated JPA models using the replaceregexp task, e.g.:
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idmodify-hibernate-models/id
phasegenerate-sources/phase
goals
goalrun/goal
/goals
configuration
tasks
replaceregexp
file=${project.build.directory}/generated-sources/hibernate3/com/{redacted}persistence/model/BillingPolicy.java
match=(.*name=quot;periodquot;.*) replace=\1
@javax.persistence.Enumerated(javax.persistence.EnumType.STRING)
byline=true /
!-- snip --
/tasks
/configuration
/execution
/executions
/plugin
This has worked fine for me all along. However, after upgrading to 1.5
I start getting sax parse errors:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.5:run
(modify-hibernate-models) on project das-common-persistence: An Ant
BuildException has occured: Element type replaceregexp must be
followed by either attribute specifications, or /. - [Help 1]
It appears that the new strategy is to emit a temporary ant build.xml
file that is then run. The problem is that when this is done, the
quote entities in my regular expression above are expanded when this
file is written and the following is generated:
project name=maven-antrun- default=main
target name=main
replaceregexp replace=\1
@javax.persistence.Enumerated(javax.persistence.EnumType.STRING)
byline=true file={redacted}/BillingPolicy.java
match=(.*name=period.*)/
!-- snip --
/target
/project
This breaks the match attribute and fails my build.
Any ideas?
Thanks,
Charles
-
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 3.0
Perhaps you need to normalize your version string? Looks like it might not be
taking kindly to the _
http://maven.apache.org/enforcer/enforcer-rules/requireJavaVersion.html
On Oct 8, 2010, at 6:38 PM, Jason Chaffee wrote:
This is what I have:
properties
java.version1.6.0_20/java.version
/properties
rules
requireJavaVersion
version[${java.version},)/version
messageJava version: ${java.version} is required/message
/requireJavaVersion
/rules
-Original Message-
From: Nayan Hajratwala [mailto:na...@chikli.com]
Sent: Friday, October 08, 2010 3:29 PM
To: Maven Users List
Subject: Re: maven 3.0
I have this rule set up running under 3.0 and it works fine:
rules
requireJavaVersion
version1.6/version
/requireJavaVersion
...
/rules
What's the tag for the rule that is failing for you?
---
Nayan Hajratwala
http://agileshrugged.com
http://twitter.com/nhajratw
734.658.6032
On Oct 8, 2010, at 6:00 PM, Jason Chaffee wrote:
So is there documentation on how I can configure that rule in 3.0? I
looked around the site, couldn't find anything.
Thanks.
-Original Message-
From: Brian Fox [mailto:bri...@infinity.nu]
Sent: Friday, October 08, 2010 2:53 PM
To: Maven Users List
Subject: Re: maven 3.0
It's telling you the rule doesn't work in 3.x, that's the current
state. 3.x has similar functionality built in
Sent from my iPad
On Oct 8, 2010, at 4:33 PM, Jason Chaffee jchaf...@ebates.com wrote:
Does maven-enforcer-plugin with maven 3.0? The same rules are
working
correctly in 2.0.
I have the following error:
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce
(enforce-versions)
@
cbsp ---
[WARNING] This rule is not compatible with the current version of
Maven.
The rule is not able to perform any checks.
[WARNING] Rule 1:
org.apache.maven.plugins.enforcer.RequireJavaVersion
failed with message:
Java version: 1.6.0_20 is required
[INFO]
Thanks.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
