Re: update-child-modules of versions plugin on the whole hierarchy
That will be in 1.0-beta-1 2009/5/14 DanDude programmer_offs...@yahoo.com Actually, I am trying to use versions plugin to synchronize dependencies across all projects in a hierarchy, since I wish to release all projects with same version number. update-child-modules works, but the only problem is that I have to execute the goal on all parent poms. Since I have a 3-level hierarchy, is tedious and error prone. I wish I could execute update-child-modules on top parent and have it update all projects in the hierarchy. stephenconnolly wrote: just so you know what update-child-modules does... if the child references the *wrong version of the parent* then update-child-modules will fix your child poms for you. it is just for fixing a broken reactor. You are probably looking for update-properties as that is really the only way (currently) to specify what dependencies to update. -Stephen 2009/5/13 DanDude programmer_offs...@yahoo.com I have a project where my root project has child1, child2 etc... Each child has child11, child12, child21 etc.. I would like to execute update-child-modules so versions across all child projects are updated. Is this possible? -- View this message in context: http://n2.nabble.com/update-child-modules-of-versions-plugin-on-the-whole-hierarchy-tp2885629p2885629.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 -- View this message in context: http://n2.nabble.com/update-child-modules-of-versions-plugin-on-the-whole-hierarchy-tp2885629p2887823.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: Checkstyle plugin for 5.0?
That sounds like it could work. Thanx. Voted. Ramon Casha On Wed, 2009-05-13 at 13:09 +0200, Stevo Slavić wrote: Hello Ramon, Vote on this http://jira.codehaus.org/browse/MCHECKSTYLE-105 issue for official maven checkstyle release with 5.0 checkstyle included, or you can already use release in Atlassian public repo (see thishttp://jira.codehaus.org/browse/MCHECKSTYLE-105?focusedCommentId=176171page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_176171comment in same issue for instructions). Regards, Stevo. On Wed, May 13, 2009 at 9:56 AM, Ramon Casha ramon.ca...@megabyte.netwrote: Maven = 2.1.0 Apparently the changes have happened in checkstyle though - the plugin has some depenencies on a method loadModuleFactory which no longer exists - it doesn't build against the latest checkstyle. I tried looking for a replacement for that function but got lost. I'm currently working by nicking SuppressWithNearbyCommentFilter from checkstyle 5 and rebuilding it as a custom filter to 4.4, but I was hoping that the plugin might be updated to work against the latest checkstyle. Ramon Casha On Wed, 2009-05-13 at 07:25 +0100, Stephen Connolly wrote: 2009/5/13 Ramon Casha ramon.ca...@megabyte.net Ah. Ok, how about a Checkstyle 5 plugin for Maven in the meantime? :) Ah-ha a different question that is... it requires a different response... which version of Maven are you looking for a Checkstyle 5 plugin for Maven for? ;-) -Stephen P.S. I'm hoping you don't answer Maven 1.0 or Maven 1.1 :-p Ramon Casha On Wed, 2009-05-13 at 06:39 +0100, Stephen Connolly wrote: 2009/5/12 Ramon Casha ramon.ca...@megabyte.net Any chance of upgrading the Checkstyle plugin to work with Maven 5? I think people are probably more concerned with releasing Maven 3 first ;-) Ramon Casha DISCLAIMER -- The information contained in this electronic mail may be confidential or legally privileged. It is for the intended recipient(s) only. Should you receive this message in error, please notify the sender by replying to this mail. Unauthorised use of the contents is strictly prohibited. Whilst all care has been taken, the Megabyte Group is not responsible for the integrity of the contents of this electronic mail and any attachments included within. - 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: Wrap other plugin in my plugin
Because of how the maven plugin thingy is designed that is not possible... you have two choices: 1. copy and paste 2. (if the plugin developer was smart, the have the functionality of their mojos in a jar and their plugin is only a very thin wrapper) add their functionality jar as a dependency and copy and paste their thin wrapper 2009/5/14 Chirag Trivedi chiragincont...@yahoo.com Hi, I have created a maven plugin which uses another 2 plugins. I want to expose another plugin's goal as my plugin goal, so that a user can access all goals of the 2 plugins by just using my plugin. For e.g. pluginA - has goal generate pluginB - has goal execute I want to wrap pluginA and plginB in myPlugin. If anybody uses myPlugin, then he should be able to access generate and execute goals directly. Regards, Chirag Trivedi Now surf faster and smarter ! Check out the new Firefox 3 - Yahoo! Edition http://downloads.yahoo.com/in/firefox/?fr=om_email_firefox - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: directory separator not / but \\ in resource filtering
Hi,
It's probably due to http://jira.codehaus.org/browse/MSHARED-78.
It must be fixed with resources plugin 2.4-SNAPSHOT.
We only need to release maven-filtering and resources plugin. :-)
--
Olivier
2009/5/14 Rice Yeh rice...@gmail.com:
Hi,
I have a file put in resource like the following:
property name=hibernate.connection.url
value=jdbc:h2:tcp://localhost/${project.build.testOutputDirectory}/db/testdb
/
I use resource filtering to replaceing project.build.testOutputDirectory,
but the result becomes
property name=hibernate.connection.url
value=jdbc:h2:tcp://localhost/C\:\\projects\\xsf\\jdk15\\persistence\\as-automata-persistence\\target\\test-classes/db/testdb
/
, which is not accepted by H2 database. How do I make \\ to / ?
Regards,
Rice
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
AW: War Overlays and Conflicting Jars
Hi Brad, we had this issue too and used the following workaround (Works only if the overlay is never used as war itself): In the war plugin we exclude packaging of the jars. So we got a skinny jar. In the module building the actual war thatg is deployed to a container we depend the overlay with typewar/type and with typepom/type. By doing so maven uses the whole dependency management stuff to resolve conflicts. Best Regards, Sebastian -Ursprüngliche Nachricht- Von: Harper, Brad [mailto:brad.har...@fiserv.com] Gesendet: Montag, 11. Mai 2009 21:55 An: Maven Users List Betreff: War Overlays and Conflicting Jars Is there a way to detect when the dependencies of two war artifacts are inconsistent with respect to packaged jar versions? E.g. a war depends on artifact abc-1.0.0.jar. An overlay is performed where an inconsistent dependency on abc-1.0.1.jar is also defined. The resulting war will contain both jar files and, so far as I can tell, the subsequent behavior is indeterminate. Brad - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to add a script as part of build process of a WAR
Hello, As a part of building a WAR (web archive) file for my project from maven, I want to execute a script. If the script returns true, then the build should go further to create the .war file, otherwise the build process should not proceed further. How can I achieve this using maven? I am using maven version 1.2, for building .war file for my project. My use case is: I want to check for a certain patter in all the .jsp files that have been written in the project. Now, if anyone one of the jsp file does not contain that pattern, then the build should fail. I've written a script to do this. However, I want this script to be executed every time someone builds creates a war file using maven 1.2. Thanks, Komal Bhardwaj
Re: update-child-modules of versions plugin on the whole hierarchy
Hi Stephen, Did you fix it directly in the code? Looking in the bugs for the roadmap of the 1.0-beta1, I can't find the reference: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=11830fixfor=14766 Does a bug report exist for this bug? Cheers. 2009/5/14 Stephen Connolly stephen.alan.conno...@gmail.com That will be in 1.0-beta-1 2009/5/14 DanDude programmer_offs...@yahoo.com Actually, I am trying to use versions plugin to synchronize dependencies across all projects in a hierarchy, since I wish to release all projects with same version number. update-child-modules works, but the only problem is that I have to execute the goal on all parent poms. Since I have a 3-level hierarchy, is tedious and error prone. I wish I could execute update-child-modules on top parent and have it update all projects in the hierarchy. stephenconnolly wrote: just so you know what update-child-modules does... if the child references the *wrong version of the parent* then update-child-modules will fix your child poms for you. it is just for fixing a broken reactor. You are probably looking for update-properties as that is really the only way (currently) to specify what dependencies to update. -Stephen 2009/5/13 DanDude programmer_offs...@yahoo.com I have a project where my root project has child1, child2 etc... Each child has child11, child12, child21 etc.. I would like to execute update-child-modules so versions across all child projects are updated. Is this possible? -- View this message in context: http://n2.nabble.com/update-child-modules-of-versions-plugin-on-the-whole-hierarchy-tp2885629p2885629.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 -- View this message in context: http://n2.nabble.com/update-child-modules-of-versions-plugin-on-the-whole-hierarchy-tp2885629p2887823.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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: How can one handle release candidates in Maven?
Hi, I don't mean to hijack this thread, but my experience is that test people love traceability. Thus, I think they would expect a created tag/label to stay as they file bug reports on it. (I guess this is out of a larger non-agile organization's point of view.) Just my 2 cents, /Anders On Wed, May 13, 2009 at 16:41, sebb seb...@gmail.com wrote: On 13/05/2009, Jason van Zyl jvan...@sonatype.com wrote: On 13-May-09, at 10:11 AM, sebb wrote: On 13/05/2009, nicolas de loof nicolas.del...@gmail.com wrote: With this approach, all RC tags (and the final one) point to a source code that generate the finalName artifact. more complete sample Yes, but AFAICS the tag 1.0 points to different code at different times, so does not uniquely identify the code. Tags should not contain different code at different points in time. That's just a bad practice. It happens by accident occasionally but to change code on tags consciously is just a bad practice. I entirely agree. However AFAICT that is exactly what many Maven release procedures involve, because the tag is deleted and recreated. To go back to my original question - how does one use Maven with release tags? The restriction is that a tag, once created, is never changed (it may be copied or deleted, but never updated or *re*created). So if someone says that the archives generated from tag 1.0 are OK - or not OK - how do you know what code they are referring to? from trunk 1.0-SNAPSHOT release:prepare version = 1.0 release:stage -- tag = 1.0 -- artifact = foo-1.0.jar, deployed on staging repository test, test, test BUG ! release:roolback -- trunk is back to 1.0-SNAPSHOT // rename the tag, as this one was a buggy RC svn mv tags\1.0 tags\1.0-RC1 go back to step 1 No bug found ? well done, you've got your release 2009/5/13 sebb seb...@gmail.com On 13/05/2009, nicolas de loof nicolas.del...@gmail.com wrote: 1. release:stage with the target version 0.9 (renaming a released JAR may have some strange side-effects) test, test, test .. -- all fine ? you've got it -- some bugs : release:rollback , fix and back to step 1. You only have to rename (or remove) the tag created in SCM for the release (candidate) I don't follow this - how does this ensure that a given tag name (URL) only ever refers to a single code set? I may have misunderstood, but it seems to me that the tag is being reused, and therefore does not uniquely identify the source. 2009/5/13 Todd Thiessen thies...@nortel.com So what is the extact work flow? 1. Run release:stage with a version like myproject-0.9-RC1 2. When problems are found, rollback, fix the problem and run release:stage again, incrementing RC2, 3, etc 3. When no more problems are found with the RC, perform a rollback and then a release:perform using the actual release version. (in this case myproject-0.9) --- Todd Thiessen -Original Message- From: nicolas de loof [mailto:nicolas.del...@gmail.com] Sent: Wednesday, May 13, 2009 9:13 AM To: Maven Users List Subject: Re: How can one handle release candidates in Maven? Use the release:stage goal to create your release candidates. If you find a bug, you just have to release:rollback and rename the tag from finalName to finalName_RCx 2009/5/13 Fabien KRUBA fabien.kr...@gmail.com I suppose you can use release:prepare and perform multiple times if you give the RC version number when asked ? http://maven.apache.org/guides/mini/guide-releasing.html On Wed, May 13, 2009 at 8:55 AM, sebb seb...@gmail.com wrote: What I would like to be able to do with Maven is: Create an SVN tag, e.g. myproject-0.9-RC1 from current code in trunk (or perhaps a branch) Create and test the release candidate from the tag. Publish the release candidate somewhere temporarily so others can check if the release candidate is OK. If there are problems, fix the trunk (or branch) and create a new tag, e.g. myproject-0.9-RC2. Repeat as needed. Suppose RC3 is OK, then the artifacts need to be renamed (if necessary) to remove the -RC3 suffix, and published to the release repository. The tag is also
Set parameters of a mojo through Java
Hi, I am trying to execute a mojo from my mojo through java. I want to set parameters which are to be used by the mojo. From maven plugin, we can specify the parameters in pom.xml but through java how can I set the parameters? Regards, Chirag Trivedi Cricket on your mind? Visit the ultimate cricket website. Enter http://beta.cricket.yahoo.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Set parameters of a mojo through Java
I've seen two approaches:
1) if you are starting the Mojo using a MavenSession, you can set the
property defined in
@parameter expression=${propertyName} for that parameter.
2) If you are invoking the methods in the Mojo by yourself, then the
parameters are probably private fields, and you can set them using
reflexion: Field f = SomeMojo.class.getDeclaredField(parameter);
f.setAccessible(); f.set(instanceOfSomeMojo, value);
__
Diese E-Mail kann vertrauliche und geschuetzte Informationen enthalten. Wenn
diese E-Mail nicht für Sie bestimmt ist, bitten wir Sie, uns unverzueglich zu
informieren und sie zu loeschen.
This e-mail message may contain information, which is confidential and
protected. If you are not the intended recipient of this message, we ask you to
inform us immediately and delete the message afterwards.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Scope import and importing provided dependencies
I have a strange issue with importing provided dependencies. I have a-pom.xml, which has a few dependencies and b-pom.xml which imports a-pom.xml. After a mvn -f a-pom.xml install mvn -f b-pom.xml dependency:tree I see the following: [INFO] snapshot com.example:dependency-pom:0.1-SNAPSHOT: checking for updates from atlassian [INFO] [dependency:tree] [INFO] com.example:example-jar:jar:0.1-SNAPSHOT [INFO] \- com.example:dependency-pom:pom:0.1-SNAPSHOT:import [INFO]+- commons-validator:commons-validator:jar:1.3.1:runtime [INFO]| +- commons-beanutils:commons-beanutils:jar:1.7.0:runtime [INFO]| +- commons-digester:commons-digester:jar:1.6:runtime [INFO]| | +- commons-collections:commons-collections:jar:2.1:runtime [INFO]| | \- xml-apis:xml-apis:jar:1.0.b2:runtime [INFO]| \- commons-logging:commons-logging:jar:1.0.4:runtime [INFO]\- oro:oro:jar:2.0.8:runtime These are all the dependencies which are in a-pom.xml except for: dependency groupIdcom.google.collections/groupId artifactIdgoogle-collections/artifactId version0.8/version scopeprovided/scope /dependency Did I understand or do something wrong? With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl project xmlns=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; modelVersion4.0.0/modelVersion groupIdcom.example/groupId artifactIddependency-pom/artifactId packagingpom/packaging version0.1-SNAPSHOT/version nameExample Dependency POM/name dependencies dependency groupIdorg.mockito/groupId artifactIdmockito-all/artifactId version1.6/version scopetest/scope /dependency dependency groupIdcommons-validator/groupId artifactIdcommons-validator/artifactId version1.3.1/version /dependency dependency groupIdoro/groupId artifactIdoro/artifactId version2.0.8/version scoperuntime/scope /dependency dependency groupIdcom.google.collections/groupId artifactIdgoogle-collections/artifactId version0.8/version scopeprovided/scope /dependency /dependencies /project project xmlns=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; modelVersion4.0.0/modelVersion groupIdcom.example/groupId artifactIdexample-jar/artifactId packagingjar/packaging version0.1-SNAPSHOT/version nameExample Jar POM/name dependencies dependency groupIdcom.example/groupId artifactIddependency-pom/artifactId version0.1-SNAPSHOT/version typepom/type scopeimport/scope /dependency /dependencies /project - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Newbie-Problem: Wicket/Maven/Jetty: FileNotFoundException?
I am very new to the Java-World and want to make a web project using
Java/Maven2/Wicket.
I tried to install Wicket with these instructions:
http://cwiki.apache.org/WICKET/windows-guide-to-installing-wicket-on-eclipse-with-maven.html
Everything went fine up to the point of running a project. I tried
Wicket version 1.4 rc4 and 1.3.6.
Trying to reach localhost:8080 displays an 503-Error...
The console told me the following:
INFO - log- Logging to
org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via
org.mortbay.log.Slf4jLog
STARTING EMBEDDED JETTY SERVER, PRESS ANY KEY TO STOP
INFO - log- jetty-6.1.4
INFO - log- NO JSP Support for /, did not
find org.apache.jasper.servlet.JspServlet
WARN - log- Failed startup of context
org.mortbay.jetty.webapp.webappcont...@137c60d{/,src/main/webapp}
java.io.FileNotFoundException:
\\ROSSV01\ROSSV01\Users\mypersonalusername\.m2\repository\log4j\log4j\1.2.14\log4j-1.2.14.jar
(Access denied)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.init(ZipFile.java:114)
at java.util.jar.JarFile.init(JarFile.java:133)
[...]
ROSSV01 is the name of the networkserver where my userdata is stored.
I have no clue
why Maven(?) chose that directory... However the URL is false:
Right URL:
\\ROSSV01\Users\mypersonalusername\.m2\...
Wrong URL:
\\ROSSV01\ROSSV01\Users\mypersonalusername\.m2\...
So I'm pretty stuck here. Is it a Wicket error? Is it a Maven error?
Jetty error? Where could I change the URL using eclipse?
Right now I am pretty confused here...
Would be great if somebody can help me out...
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Scope import and importing provided dependencies
Later occured to me that all dependencies have scope runtime. If I replace in b-pom.xml the scope with scope provided, all dependencies show up as provided, except the one that is actually scoped provided. Can someone shed some more light on this? With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Thu, May 14, 2009 at 1:34 PM, Nick Stolwijk nick.stolw...@gmail.com wrote: I have a strange issue with importing provided dependencies. I have a-pom.xml, which has a few dependencies and b-pom.xml which imports a-pom.xml. After a mvn -f a-pom.xml install mvn -f b-pom.xml dependency:tree I see the following: [INFO] snapshot com.example:dependency-pom:0.1-SNAPSHOT: checking for updates from atlassian [INFO] [dependency:tree] [INFO] com.example:example-jar:jar:0.1-SNAPSHOT [INFO] \- com.example:dependency-pom:pom:0.1-SNAPSHOT:import [INFO] +- commons-validator:commons-validator:jar:1.3.1:runtime [INFO] | +- commons-beanutils:commons-beanutils:jar:1.7.0:runtime [INFO] | +- commons-digester:commons-digester:jar:1.6:runtime [INFO] | | +- commons-collections:commons-collections:jar:2.1:runtime [INFO] | | \- xml-apis:xml-apis:jar:1.0.b2:runtime [INFO] | \- commons-logging:commons-logging:jar:1.0.4:runtime [INFO] \- oro:oro:jar:2.0.8:runtime These are all the dependencies which are in a-pom.xml except for: dependency groupIdcom.google.collections/groupId artifactIdgoogle-collections/artifactId version0.8/version scopeprovided/scope /dependency Did I understand or do something wrong? With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven continuously initiates transfer of jars
Well, you should try to isolate the different possible causes of your problem. Open a CLI and run something like mvn compile from the root of your project. What does it say? Cheers. 2009/5/14 ezanih eza...@hotmail.com Hi there I am using Mavan 2.0.9 (although the problem occurs with older Maven versions). I have a Maven-enabled project which uses Spring, Hibernate and several Apache Commons libraries as well as Tomcat 5.5. I am using the Eclipse IDE. I have followed the Maven installation instructions and setup my M2_HOME and M2 environment variables and tested Mavenis ok with mvn --version. My problem is I have Maven dependency-enabled my project but my Eclipse IDE is showing red squares with a white cross over most of the files in my project with the error being : The import org.apache or org.hibernate or org.springframework cannot be resolved with red curvy lines below the import statements. I have reinstalled Maven, Eclipse and the project but to no avail. I have checked that my Maven .m2 repository has all the jar files in the allocated folder on my PC. However, my project seems to be unable to read the jar files and all my import statements at the top of my java class are turning red. Pls help. Many thks! -- View this message in context: http://www.nabble.com/Maven-continuously-initiates-transfer-of-jars-tp23534377p23534377.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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: update-child-modules of versions plugin on the whole hierarchy
Not yet... it's an issue I have in my head If you want to raise an issue and target it for 1.0-beta-1 it would help me remember -Stephen 2009/5/14 Baptiste MATHUS m...@batmat.net Hi Stephen, Did you fix it directly in the code? Looking in the bugs for the roadmap of the 1.0-beta1, I can't find the reference: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=11830fixfor=14766 Does a bug report exist for this bug? Cheers. 2009/5/14 Stephen Connolly stephen.alan.conno...@gmail.com That will be in 1.0-beta-1 2009/5/14 DanDude programmer_offs...@yahoo.com Actually, I am trying to use versions plugin to synchronize dependencies across all projects in a hierarchy, since I wish to release all projects with same version number. update-child-modules works, but the only problem is that I have to execute the goal on all parent poms. Since I have a 3-level hierarchy, is tedious and error prone. I wish I could execute update-child-modules on top parent and have it update all projects in the hierarchy. stephenconnolly wrote: just so you know what update-child-modules does... if the child references the *wrong version of the parent* then update-child-modules will fix your child poms for you. it is just for fixing a broken reactor. You are probably looking for update-properties as that is really the only way (currently) to specify what dependencies to update. -Stephen 2009/5/13 DanDude programmer_offs...@yahoo.com I have a project where my root project has child1, child2 etc... Each child has child11, child12, child21 etc.. I would like to execute update-child-modules so versions across all child projects are updated. Is this possible? -- View this message in context: http://n2.nabble.com/update-child-modules-of-versions-plugin-on-the-whole-hierarchy-tp2885629p2885629.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 -- View this message in context: http://n2.nabble.com/update-child-modules-of-versions-plugin-on-the-whole-hierarchy-tp2885629p2887823.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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
ear project
I have a maven project with subprojects for jar, war, ear , a dependency like spring i need I need in both the modules jar and war , so where should I specify the dependency? in parent project or each project war and jar ?
Re: How can one handle release candidates in Maven?
First, I'll acknowledge that it's not easy/possible to promote an artifact from one version to another - say 1.0-RC-10 to 1.0. Lets just accept that for now as it's a known issue that will be resolved down the road. Lets instead discuss a few ways to work within those bounds, since discussing what could be doesn't help the issue now (which i believe this thread derived from the discussion on commons-dev regarding a pending release). There are two approaches to this process, both are valid and I think you could pick one based on your requirements: The first is to append a build number to your version that is always incremented. So instead of 1.0 you have 1.0-1 or 1.0-b1. You increment this forever until you have a release that is good and that's the one that stays, it could be 1.0-b10 or 1.0-500. I've used this approach before and it's similar to what many commercial orgs do (if you look under the hood at MS versions for example, Vista SP1 is 6001.16659.070916-1443). In other words, the marketing for a release might be 1.0 but the actual version of the files might be 1.0-. This may be ok for things where the end result is a war or ear but probably not as desirable for projects like commons that release jars that are intended to be consumed. The approach we use in the Maven project is slightly different. We used to stage versions like 2.0.8 over and over until we got it right. The problems with this approach where: 1) you need to rollback the tag and versions every time and 2) someone may have an artifact called 2.0.8 that was actually not the final 2.0.8. This was a bigger problem when we wanted to start getting maven-users involved to test the release candidates. We instead use the RC versions (eg 2.0.9-RC10) until we get to a release that we decide is ready to do. The versions are all staged on Nexus and the binaries are ditched each time we rebuild, but the tags stay in place. Since each release is uniquely versioned, we no longer have to revert the versions and we don't have to worry about someone having an RC and thinking it's a final release. Since it's not possible currently to promote an actual RC to the final release (eg 2.0.9-RC10 to 2.0.9), we simply rebuild and restage one final time using the new release number (eg 2.0.9). The original RCs were never called for formal votes as we know it's unlikely to pass, think of them as tagged snapshots. Only the final release is voted upon and in this fashion, by the time we reach the final release it's highly unlikely we will find any showstoppers, since the release process was followed for each RC (a practice run 10+ times if you will). Yes there are issues where someone _could_ make a change in between the last RC and the final release, but when we are in this cycle it is expected that only the RM is making changes to that branch (once the RC process starts, it's moved to a separate branch) and it's watched very closely. In reality it's not an issue. Hope that helps. Brian On Thu, May 14, 2009 at 5:35 AM, Anders Hammar and...@hammar.net wrote: Hi, I don't mean to hijack this thread, but my experience is that test people love traceability. Thus, I think they would expect a created tag/label to stay as they file bug reports on it. (I guess this is out of a larger non-agile organization's point of view.) Just my 2 cents, /Anders On Wed, May 13, 2009 at 16:41, sebb seb...@gmail.com wrote: On 13/05/2009, Jason van Zyl jvan...@sonatype.com wrote: On 13-May-09, at 10:11 AM, sebb wrote: On 13/05/2009, nicolas de loof nicolas.del...@gmail.com wrote: With this approach, all RC tags (and the final one) point to a source code that generate the finalName artifact. more complete sample Yes, but AFAICS the tag 1.0 points to different code at different times, so does not uniquely identify the code. Tags should not contain different code at different points in time. That's just a bad practice. It happens by accident occasionally but to change code on tags consciously is just a bad practice. I entirely agree. However AFAICT that is exactly what many Maven release procedures involve, because the tag is deleted and recreated. To go back to my original question - how does one use Maven with release tags? The restriction is that a tag, once created, is never changed (it may be copied or deleted, but never updated or *re*created). So if someone says that the archives generated from tag 1.0 are OK - or not OK - how do you know what code they are referring to? from trunk 1.0-SNAPSHOT release:prepare version = 1.0 release:stage -- tag = 1.0 -- artifact = foo-1.0.jar, deployed on staging repository test, test, test BUG ! release:roolback -- trunk is back to 1.0-SNAPSHOT // rename the tag, as this one was a buggy RC svn mv tags\1.0 tags\1.0-RC1 go back to step 1 No bug found ?
Re: How would you approach this?
On Tue, May 12, 2009 at 1:58 PM, Doug Hughes dhug...@alagad.com wrote: Hi, I've been writing to the list off and on over the past few days. I'm a ColdFusion developer and I'm looking at Maven for a few different reasons. Mainly, I'm exploring the option of using Groovy+Spring+Hibernate to create the service layers and models for my applications. ColdFusion is simply a JEE app that can compile CFML code to Java bytecode and execute it. A typicaly ColdFuson developer would treat ColdFusion similar to how a PHP developer might. IE, they'd connect ColdFusion (running in its container) to a web server like Apache and have it compile and run CFML source code. However, because CF is Java we also have the ability to easily instantiate Java classes and work with them. CF is great for presentation work and many OO development tasks, but it's interpreted nature can sometimes cause issues. So there's a bit of a moment to look at Groovy to create a Java-based, compiled model and then using MVC frameworks in ColdFusion for presentation. This also makes a nice way to share an application's model between Flex and HTML UIs. Anyhow, ColdFusion itself can be deployed as a WAR or EAR file. If you do a WAR deployment there's actually both a cfusion.war and rds.war file. Both are needed to get the full range of features of the language and server. If I deployed the ear file both war files are included in it. If I were to deply war files to Jboss, for example, I'd put both war files (epanded) into the /server/default/deploy directory. When working with Maven, I'm not quite sure how to accomplish this. I've found that if I can expand the cfusion.war into the default webapp archetype's src/main/webapp directory and it will just work. However, I'm not sure where to put the rds.war, or if it's even possible to run more than on war file through maven. How would you do this? I'm not sure what you mean by run more than one through Maven My ultimate goal would be to have something like this: A parent project to build everything. A child project for my Groovy/Java code. This gets compiled into a jar and used by my next child project. Another child project which would be a webapp with the cfusion.war and rds.war deployed into it, along with any CFML code and the jar created in the first child project. This would be built into well, I'm not 100% sure. :) Probably a war file that would be deployed to a server but maybe it would really just be one war which as CF, my jar, and CFML code. The second rds.war would be used essentialy as-is. Are you talking about building something using the Coldfusion wars, or deploying it. I'm confused. Anyhow, I'd appreciate your feedback and suggestions. Thanks, Doug Hughes
Re: Building Maven with Maven failed when tried using HDK
Does it work with the Sun JDK? On Mon, May 11, 2009 at 12:11 PM, Mohanraj Loganathan mohanra...@gmail.comwrote: Hello I was trying to build Maven source (apache-maven-2.1.0-M1-src.zip) with Maven 1.0.10 Maven installed in the machine. With Harmony Development Kit, building is failed with the following error. Please let me know whether i can build Maven using Harmony Development Kit (HDK) *HDK Version: * Apache Harmony Launcher : (c) Copyright 1991, 2008 The Apache Software Foundation or its licensors, as applicable. java version 1.5.0 pre-alpha : not complete or compatible svn = r713673, (Nov 13 2008), Windows/ia32/msvc 1310, release build http://harmony.apache.org *Exception/Error:* Failed tests: testCompatibleRecommendedVersionWithChildren(org.apache.maven.artifact.resolver.DefaultArtifactCollectorTest) *Failure Exception:* testCompatibleRecommendedVersionWithChildren(org.apache.maven.artifact.resolver.DefaultArtifactCollectorTest) Time elapsed: 0.047 sec FAILURE! junit.framework.AssertionFailedError: Check artifact list expected:[test:a:jar:1.0:compile, test:b:jar:1.0:compile, test:e:jar:1.0:compile, test:c:jar:2.5:compile, test:d:jar:1.0:compile] but was:[test:a:jar:1.0:compile, test:b:jar:1.0:compile, test:c:jar:2.5:compile, test:d:jar:1.1:compile, test:e:jar:1.0:compile] at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:282) at junit.framework.Assert.assertEquals(Assert.java:64) at org.apache.maven.artifact.resolver.DefaultArtifactCollectorTest.testCompatibleRecommendedVersionWithChildren(DefaultArtifactCollectorTest.java:366) at org.apache.maven.artifact.resolver.DefaultArtifactCollectorTest.testCompatibleRecommendedVersionWithChildren(DefaultArtifactCollectorTest.java:366) at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java) at java.lang.reflect.Method.invoke(Method.java:317) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) *Maven used to build:* Maven version: 2.0.10 Java version: 1.5.0 OS name: windows xp version: 5.1 arch: x86 Family: windows Any suggestions? -- Mohan
Re: Solution for aggregating dependent source code
The aggregation is probably not a good idea as it can have other side effects. Instead I would use the dependency plugin to pull down the source jars you need, unpack them into a common location and then use the assembly plugin to zip them all back up. I've done this before to convert maven based builds with hundreds of modules into a flattened ant source structure for delivery to another partner (they made me do it at gun-point ;-) ) On Tue, May 12, 2009 at 3:00 AM, Rice Yeh rice...@gmail.com wrote: Hi, I have a need to aggregating a project's source code with its dependency's source code. That is, a project p1 has dependency on p2. I would like to create a source jar for p1 that also contains the source code of p2. How do I achieve this? Does the source:aggregate goal in maven-source-plugin can solve my problem? Regards, Rice
Run unit tests with multimple dependecies?
I have multiple versions of a jar file called child: child_1.0.jar, child_1.1, and child_1.2. In theory each version of child implements the same API and should be backwardly compatible. I have another jar file called parent_2.0.jar. I would like to run parent's unit tests three times, each time using a different version of child. Can this be done using Maven? Regards, Christopher ** This communication and all information (including, but not limited to, market prices/levels and data) contained therein (the Information) is for informational purposes only, is confidential, may be legally privileged and is the intellectual property of ICAP plc and its affiliates (ICAP) or third parties. No confidentiality or privilege is waived or lost by any mistransmission. The Information is not, and should not be construed as, an offer, bid or solicitation in relation to any financial instrument or as an official confirmation of any transaction. The Information is not warranted, including, but not limited, as to completeness, timeliness or accuracy and is subject to change without notice. ICAP assumes no liability for use or misuse of the Information. All representations and warranties are expressly disclaimed. The Information does not necessarily reflect the views of ICAP. Access to the Information by anyone else other than the recipient is unauthorized and any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. **
Re: Scope import and importing provided dependencies
I don't believe that provided dependencies are transitive. http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope Just a note: import is a scope used in the dependency management section, so I found your original question confusing. I have a-pom.xml, which has a few dependencies and b-pom.xml which imports a-pom.xml. I'd assuming that you mean a-pom depends on b-pom. You might want to take a look at the import feature too. http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies HTH Jim On Thu, May 14, 2009 at 8:12 AM, Nick Stolwijk nick.stolw...@gmail.comwrote: Later occured to me that all dependencies have scope runtime. If I replace in b-pom.xml the scope with scope provided, all dependencies show up as provided, except the one that is actually scoped provided. Can someone shed some more light on this? With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Thu, May 14, 2009 at 1:34 PM, Nick Stolwijk nick.stolw...@gmail.com wrote: I have a strange issue with importing provided dependencies. I have a-pom.xml, which has a few dependencies and b-pom.xml which imports a-pom.xml. After a mvn -f a-pom.xml install mvn -f b-pom.xml dependency:tree I see the following: [INFO] snapshot com.example:dependency-pom:0.1-SNAPSHOT: checking for updates from atlassian [INFO] [dependency:tree] [INFO] com.example:example-jar:jar:0.1-SNAPSHOT [INFO] \- com.example:dependency-pom:pom:0.1-SNAPSHOT:import [INFO]+- commons-validator:commons-validator:jar:1.3.1:runtime [INFO]| +- commons-beanutils:commons-beanutils:jar:1.7.0:runtime [INFO]| +- commons-digester:commons-digester:jar:1.6:runtime [INFO]| | +- commons-collections:commons-collections:jar:2.1:runtime [INFO]| | \- xml-apis:xml-apis:jar:1.0.b2:runtime [INFO]| \- commons-logging:commons-logging:jar:1.0.4:runtime [INFO]\- oro:oro:jar:2.0.8:runtime These are all the dependencies which are in a-pom.xml except for: dependency groupIdcom.google.collections/groupId artifactIdgoogle-collections/artifactId version0.8/version scopeprovided/scope /dependency Did I understand or do something wrong? With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Referencing plugin properties
Hi List,
It is possible to reference pom properties with ${project.version} for
example.
But how can I reference plugin properties?
I would like to reference the webapp directory. The property is called
webappDirectory, but I can't seem to get it's value.
Thanks.
Re: update-child-modules of versions plugin on the whole hierarchy
Done: http://jira.codehaus.org/browse/MVERSIONS-40 Cheers. 2009/5/14 Stephen Connolly stephen.alan.conno...@gmail.com Not yet... it's an issue I have in my head If you want to raise an issue and target it for 1.0-beta-1 it would help me remember -Stephen 2009/5/14 Baptiste MATHUS m...@batmat.net Hi Stephen, Did you fix it directly in the code? Looking in the bugs for the roadmap of the 1.0-beta1, I can't find the reference: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=11830fixfor=14766 Does a bug report exist for this bug? Cheers. 2009/5/14 Stephen Connolly stephen.alan.conno...@gmail.com That will be in 1.0-beta-1 2009/5/14 DanDude programmer_offs...@yahoo.com Actually, I am trying to use versions plugin to synchronize dependencies across all projects in a hierarchy, since I wish to release all projects with same version number. update-child-modules works, but the only problem is that I have to execute the goal on all parent poms. Since I have a 3-level hierarchy, is tedious and error prone. I wish I could execute update-child-modules on top parent and have it update all projects in the hierarchy. stephenconnolly wrote: just so you know what update-child-modules does... if the child references the *wrong version of the parent* then update-child-modules will fix your child poms for you. it is just for fixing a broken reactor. You are probably looking for update-properties as that is really the only way (currently) to specify what dependencies to update. -Stephen 2009/5/13 DanDude programmer_offs...@yahoo.com I have a project where my root project has child1, child2 etc... Each child has child11, child12, child21 etc.. I would like to execute update-child-modules so versions across all child projects are updated. Is this possible? -- View this message in context: http://n2.nabble.com/update-child-modules-of-versions-plugin-on-the-whole-hierarchy-tp2885629p2885629.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 -- View this message in context: http://n2.nabble.com/update-child-modules-of-versions-plugin-on-the-whole-hierarchy-tp2885629p2887823.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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: Scope import and importing provided dependencies
On Thu, May 14, 2009 at 5:00 PM, Jim Sellers jim.sell...@gmail.com wrote: Just a note: import is a scope used in the dependency management section, so I found your original question confusing. I had attached the a and b pom, but I did import the the pom in the dependencies section and it worked mostly. So, why is this only to be used in the dependency management section? What I want to achieve is a coupling of dependencies, so the project that depends on these coupling can depend on one dependency, instead of the group of dependencies. So, project A is the coupling project which has dependencies on X, Y and Z. Project B needs X, Y and Z, but instead of depending on the three of them, I want it as a package, thus A. I have inserted project A as a dependency with scope import in B and for most of the dependencies defined in A, project B now works, except for the provided dependency. Is this use case supported? With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Profile activation on project property
Hi List,
I have been struggling since a few days now with the following problem.
I want a profile to be enabled based on a project property, in my case
project.packaging.
I've tried doing this in the following way:
activation
property
nameproject.packaging/name
valuewar/value
/property
/activation
Unfortunately the profile is not being activated at all.
I also tried an example from the Maven Definitive Guide:
property
namemavenVersion/name
value2.1.0/value
/property
The property element tells Maven to activate this profile if the property
mavenVersion is set to the value 2.0.5.
mavenVersion is an implicit property that is available to all Maven
builds.
Unfortunately this isn't working either. (I changed the version to the Maven
build I am using).
I'm wondering whether it's actually possible to use project properties to
activate profiles.
According to the Maven Definitive Guide it is. This is a quote from the
books appendix:
property
The profile will activate if Maven detects a property (a value which can be
dereferenced within the POM by ${name})
of the corresponding name=value pair.
Thinking that this could be a Maven bug, I tried versions 2.0.8, 2.0.9,
2.0.10 and 2.1.0. All show the same behavior.
I'm stuck at this and would really appreciate any input.
Thanks in advance.
Re: ear project
I have a maven project with subprojects for jar, war, ear , a dependency like spring i need I need in both the modules jar and war , so where should I specify the dependency? in parent project or each project war and jar ? As a general rule, you should put the dependency in the module that needs it. If both Jar and War need it, then it is reasonable to put it there (specify in both of them). Alternatively since you are building an Ear, you may set the dependency to provided in the Jar and War, and then compile in the Ear so it is included when the Ear is packaged. There are various approaches -- fat wars vs thin wars etc to consider. It is entirely up to you. I would probably just include Spring's binary artifacts in my Ear if I were in your situation, and not bundle it in each War as well (aka thin war). Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Newbie-Problem: Wicket/Maven/Jetty: FileNotFoundException?
Right URL: \\ROSSV01\Users\mypersonalusername\.m2\... Wrong URL: \\ROSSV01\ROSSV01\Users\mypersonalusername\.m2\... Check the set command on Windows: HOMEDRIVE=C: HOMEPATH=\Documents and Settings\wfay ... USERNAME=WFay USERPROFILE=C:\Documents and Settings\wfay Unless specified otherwise, Maven uses current user's home directory to store the .m2 directory which has your local repo cache. If I were you, I'd probably just override that value with settings.xml and specify a true local path (c:/dev/maven/ or something) rather than involving this ROSSV01 server at all. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Referencing plugin properties
You can't reference it from another property. Why don't you just set it to
the new value?
On Thu, May 14, 2009 at 11:08 AM, Bocalinda bocali...@gmail.com wrote:
Hi List,
It is possible to reference pom properties with ${project.version} for
example.
But how can I reference plugin properties?
I would like to reference the webapp directory. The property is called
webappDirectory, but I can't seem to get it's value.
Thanks.
Filtering different test cases according to the profile
Hi all, In my project I want to run some Test cases only with Java 1.4 , in Java 5 I don't want to run these specific set of test cases , AFAIK I can create two Maven profile for java 1.4 and Java 5 along with maven-compiler-plugin , but I'm not sure how can filter different test cases according to each profile , generally it will run all the test cases available on project test directory . Can any one provide any clue .? Thanks , Sagara Gunathunga Blog - ssagara.blogspot.com Web - http://sagaras.awardspace.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to add a script as part of build process of a WAR
You can do this with the antrun plugin. Add the ant task to either do the scan or have ant run some program of your chosing to run the scan. Based on the result of the scan, you have ant fail and the build will fail. The thing I don't know is which lifecycle phase you tie that ant task to. You said the JSPs that had been written. If you mean the JSPs that the team wrote then the 'generate-source' phase would work just fine and it would fail right up front. If these JSPs are generated for you in some phase you will have to pick a phase after that one. -- Lee On Thu, May 14, 2009 at 3:59 AM, Komal Bhardwaj komalbhard...@gmail.comwrote: Hello, As a part of building a WAR (web archive) file for my project from maven, I want to execute a script. If the script returns true, then the build should go further to create the .war file, otherwise the build process should not proceed further. How can I achieve this using maven? I am using maven version 1.2, for building .war file for my project. My use case is: I want to check for a certain patter in all the .jsp files that have been written in the project. Now, if anyone one of the jsp file does not contain that pattern, then the build should fail. I've written a script to do this. However, I want this script to be executed every time someone builds creates a war file using maven 1.2. Thanks, Komal Bhardwaj -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com
Weird cycle problem. Solutions requested.
I have a strange cyclic problem that I have sort-of working but I'm not happy with it. I was wondering if any of you have a suggestion: The application is a J2EE application. Maven 2 builds the ear. The application is deployed on a cluster and I have a SOAP web service that an instance in the cluster can use to request status from the other guys in the cluster if he knows their IPs. There is a parent project and all the others are children of it. One child project (monitorIntegration) builds a jar that uses Axis 1.3 to build a web service client that can talk to the other servers in the cluster. There is also a proxy class that hides all the web service stuff from the rest of the application. Axis is run inside an ant build xml file in the generate-sources phase. It uses a wsdl that resides inside another project (monitorWS) that is described below to generate the web service client. But I do not tell Maven that this project depends on the monitorWS project as it just references the wsdl where it lies on the file system. I have a business jar project that depends on the monitorIntegration jar project. I have a service ejb project that depends on the business project. Inside this project is a session bean that handles the incoming monitor web service request (when its running on the other machine in the cluster) it has, if you care, two business methods. One provides the combinded status of all machines in the cluster and calls down into the monitorIntegration code described above for all cluster machines (including itself). The other business method provides the status for that one instance itself only. Finally, there is the monitorWS war project that has a POJO and an interface to define the web service endpoint. It depends on the service ejb project. That POJO uses JNDI to find the session bean and call its business methods. The process of building this project consistes of building the WSDL itself (details of which I will leave out), building the server code from the WSDL along with various XML files needed and then compiling the java code and whipping together the WAR file. To summarize the dependencies monitorWS depends on service service depends on business business depends on monitorIntegration monitorIntegration uses the WSDL that monitorWS generates. If you think about it you can see that the WSDL won't change to much and so WSDL version n-1 can be used to build monitorIintegration's web service client and it will mostly work. If any code is changed that causes the WSDL to change it will really take two builds before it all gets straightened out. Perhaps there is a deadlock condition in there somewhere but I don't really care enough to figure it out. One solution, I have thought of, is to quit generating the WSDL at build time. Instead the developer can generate (or edit) the WSDL during development time. That breaks the dependency cycle. If you don't see how immediately, consider that a WSDL that the developer edits (or generates) can be put into both the monitorWS and monitorIntegration projects and the cycle is totally gone. I wonder if there is some other solution. The cycle is actually present and valid because the code that seems to call itself in a recursive manner is really residing on another box which creates the end condition for the apparent recursion. Of course, if I told Maven2 that monitorIntegration depended on monitorWS it wouldn't let the build continue. (So ... I lied to it.) Thanks. -- Lee On Mon, May 11, 2009 at 2:39 PM, huser mpinj...@atxg.com wrote: Hi, I have Cobertura plugin configured in my pom.xml. Hudson renders the results from coverage.xml and reports the coverage results classified as Packages,Files, Classes,Methods,Lines,Conditionals Why am I not seeing BranchRate,LineRate,PackageLineRate etc ? I am not using Maven Genertate Site for any kind of Project Reports. My pom.xml looks like this: /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId configuration aggregatetrue/aggregate formats formatxml/format /formats check haltOnFailurefalse/haltOnFailure branchRate70/branchRate lineRate70/lineRate totalBranchRate70/totalBranchRate totalLineRate70/totalLineRate packageLineRate85/packageLineRate packageBranchRate85/packageBranchRate /check /configuration /plugin -- View this message in context: http://www.nabble.com/cobertura-results-tp23490065p23490065.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail:
Re: How can one handle release candidates in Maven?
Brian, Thanks for the excellent write up. In approach #2, when a build is done by just replacing RC versions by actual versions, since new binaries are going to be produced, don't they have to be tested again? I understand since no source code is changed(only version is changing in pom.xmls), the chances of side effects are very low, but an organisation with stricter quality control processes in place won't allow bits to be released without them being tested. Once you involve testing, we are back to square one, where we are not sure if the bits are final. Or, am I missing anything? Thanks, Sahoo Brian Fox wrote: First, I'll acknowledge that it's not easy/possible to promote an artifact from one version to another - say 1.0-RC-10 to 1.0. Lets just accept that for now as it's a known issue that will be resolved down the road. Lets instead discuss a few ways to work within those bounds, since discussing what could be doesn't help the issue now (which i believe this thread derived from the discussion on commons-dev regarding a pending release). There are two approaches to this process, both are valid and I think you could pick one based on your requirements: The first is to append a build number to your version that is always incremented. So instead of 1.0 you have 1.0-1 or 1.0-b1. You increment this forever until you have a release that is good and that's the one that stays, it could be 1.0-b10 or 1.0-500. I've used this approach before and it's similar to what many commercial orgs do (if you look under the hood at MS versions for example, Vista SP1 is 6001.16659.070916-1443). In other words, the marketing for a release might be 1.0 but the actual version of the files might be 1.0-. This may be ok for things where the end result is a war or ear but probably not as desirable for projects like commons that release jars that are intended to be consumed. The approach we use in the Maven project is slightly different. We used to stage versions like 2.0.8 over and over until we got it right. The problems with this approach where: 1) you need to rollback the tag and versions every time and 2) someone may have an artifact called 2.0.8 that was actually not the final 2.0.8. This was a bigger problem when we wanted to start getting maven-users involved to test the release candidates. We instead use the RC versions (eg 2.0.9-RC10) until we get to a release that we decide is ready to do. The versions are all staged on Nexus and the binaries are ditched each time we rebuild, but the tags stay in place. Since each release is uniquely versioned, we no longer have to revert the versions and we don't have to worry about someone having an RC and thinking it's a final release. Since it's not possible currently to promote an actual RC to the final release (eg 2.0.9-RC10 to 2.0.9), we simply rebuild and restage one final time using the new release number (eg 2.0.9). The original RCs were never called for formal votes as we know it's unlikely to pass, think of them as tagged snapshots. Only the final release is voted upon and in this fashion, by the time we reach the final release it's highly unlikely we will find any showstoppers, since the release process was followed for each RC (a practice run 10+ times if you will). Yes there are issues where someone _could_ make a change in between the last RC and the final release, but when we are in this cycle it is expected that only the RM is making changes to that branch (once the RC process starts, it's moved to a separate branch) and it's watched very closely. In reality it's not an issue. Hope that helps. Brian On Thu, May 14, 2009 at 5:35 AM, Anders Hammar and...@hammar.net wrote: Hi, I don't mean to hijack this thread, but my experience is that test people love traceability. Thus, I think they would expect a created tag/label to stay as they file bug reports on it. (I guess this is out of a larger non-agile organization's point of view.) Just my 2 cents, /Anders On Wed, May 13, 2009 at 16:41, sebb seb...@gmail.com wrote: On 13/05/2009, Jason van Zyl jvan...@sonatype.com wrote: On 13-May-09, at 10:11 AM, sebb wrote: On 13/05/2009, nicolas de loof nicolas.del...@gmail.com wrote: With this approach, all RC tags (and the final one) point to a source code that generate the finalName artifact. more complete sample Yes, but AFAICS the tag 1.0 points to different code at different times, so does not uniquely identify the code. Tags should not contain different code at different points in time. That's just a bad practice. It happens by accident occasionally but to change code on tags consciously is just a bad practice. I entirely agree. However AFAICT that is exactly what many Maven release procedures involve, because the tag is deleted and recreated. To go back to my original question - how does one use Maven with
Deploy an EAR into Websphere Application Server 6.1 using maven plugins
I'm trying to deploy on websphere 6.1 using the *maven-antrun-plugin* but I have a trouble executing the tasks displaying the following error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An Ant BuildException has occured: Unable to parse setupCmdLine:null\bin\setupCmdLine.bat (The system cannot find the path specified.) This error appears because somewhere on the maven lifecycle lost the wasHome, I couldn't continue... I also tried to deploy it using was6-maven-plugin but it gives me other error, I already asked about it but it haven't been answered yet... I have been looking for information or documentation but I didn't found anything... Someone know what is happening? Any idea? Thanks.
Re: How can one handle release candidates in Maven?
On Thu, May 14, 2009 at 3:19 PM, Sahoo sa...@sun.com wrote: Brian, Thanks for the excellent write up. In approach #2, when a build is done by just replacing RC versions by actual versions, since new binaries are going to be produced, don't they have to be tested again? Absolutely. However in the maven use case we don't need dozens of people testing every possible permutation like we try to do during the RCs. Assuming no code changed, we're really making sure that the binaries are not completely broken. Regardless, this is the build that we do the voting on so it does tend to have plenty of people using it before casting a vote. I understand since no source code is changed(only version is changing in pom.xmls), the chances of side effects are very low, but an organisation with stricter quality control processes in place won't allow bits to be released without them being tested. Once you involve testing, we are back to square one, where we are not sure if the bits are final. Or, am I missing anything? Nope, you are correct and I agree with that policy. It's what we do at Sonatype as well as Maven. When a release is staged to Nexus, our QA thoroughly checks out that build. Those exact binaries are what eventually get promoted assuming they pass. I guess what I'm saying is that with the current maven release process, you don't run RC's exactly the same way you do the final release. You need to rebuild it when you move from the RC to the release unfortunately, but you do still test the final binaries before promoting it. This is exactly what the Nexus staging is about, it lets you test the binaries before you promote it to your release repo, where it's too late to pull it back. Thanks, Sahoo Brian Fox wrote: First, I'll acknowledge that it's not easy/possible to promote an artifact from one version to another - say 1.0-RC-10 to 1.0. Lets just accept that for now as it's a known issue that will be resolved down the road. Lets instead discuss a few ways to work within those bounds, since discussing what could be doesn't help the issue now (which i believe this thread derived from the discussion on commons-dev regarding a pending release). There are two approaches to this process, both are valid and I think you could pick one based on your requirements: The first is to append a build number to your version that is always incremented. So instead of 1.0 you have 1.0-1 or 1.0-b1. You increment this forever until you have a release that is good and that's the one that stays, it could be 1.0-b10 or 1.0-500. I've used this approach before and it's similar to what many commercial orgs do (if you look under the hood at MS versions for example, Vista SP1 is 6001.16659.070916-1443). In other words, the marketing for a release might be 1.0 but the actual version of the files might be 1.0-. This may be ok for things where the end result is a war or ear but probably not as desirable for projects like commons that release jars that are intended to be consumed. The approach we use in the Maven project is slightly different. We used to stage versions like 2.0.8 over and over until we got it right. The problems with this approach where: 1) you need to rollback the tag and versions every time and 2) someone may have an artifact called 2.0.8 that was actually not the final 2.0.8. This was a bigger problem when we wanted to start getting maven-users involved to test the release candidates. We instead use the RC versions (eg 2.0.9-RC10) until we get to a release that we decide is ready to do. The versions are all staged on Nexus and the binaries are ditched each time we rebuild, but the tags stay in place. Since each release is uniquely versioned, we no longer have to revert the versions and we don't have to worry about someone having an RC and thinking it's a final release. Since it's not possible currently to promote an actual RC to the final release (eg 2.0.9-RC10 to 2.0.9), we simply rebuild and restage one final time using the new release number (eg 2.0.9). The original RCs were never called for formal votes as we know it's unlikely to pass, think of them as tagged snapshots. Only the final release is voted upon and in this fashion, by the time we reach the final release it's highly unlikely we will find any showstoppers, since the release process was followed for each RC (a practice run 10+ times if you will). Yes there are issues where someone _could_ make a change in between the last RC and the final release, but when we are in this cycle it is expected that only the RM is making changes to that branch (once the RC process starts, it's moved to a separate branch) and it's watched very closely. In reality it's not an issue. Hope that helps. Brian On Thu, May 14, 2009 at 5:35 AM, Anders Hammar and...@hammar.net wrote: Hi, I don't mean to hijack this thread, but my experience is that test people love traceability. Thus, I
Re: Referencing plugin properties
Hi Brian,
I don't want to set the value, I want to get the value.
According to the Maven webpage, it seems that was possible in Maven 1.
2009/5/14 Brian Fox bri...@infinity.nu
You can't reference it from another property. Why don't you just set it to
the new value?
On Thu, May 14, 2009 at 11:08 AM, Bocalinda bocali...@gmail.com wrote:
Hi List,
It is possible to reference pom properties with ${project.version} for
example.
But how can I reference plugin properties?
I would like to reference the webapp directory. The property is called
webappDirectory, but I can't seem to get it's value.
Thanks.
Re: Scope import and importing provided dependencies
My bad. I didn't see that you had attached the files. From what I understand, the import will only work with the dependency management (dep. mgmt) section. My guess is that it's being ignored with how you have your pom's. You could remove it and see if you get the same result. My mental definitation for the dep. mgmt section is if you're going to use this artifact, use this version, scope, exclusions, etc. I don't think that transitive dependencies are ever pulled across. I understand what you're trying to do, but I don't think that it's possible with maven today. What you'll have to do is move your dependencies from your a-pom into the dep mgmt section, import them into the b-pom's dep mgmt section, and then have them as dependencies by just listing the groupId, artifactId, and possibly the classifier. It's not as neat in some ways, but it also means that you don't *have* to pull in a dependency from the a-pom if you don't to use it. I thought that the dep mgmt import thing was weird / strange at first, but it's very, very useful. Cleans the pom's up a bunch too. Jim On Thu, May 14, 2009 at 11:19 AM, Nick Stolwijk nick.stolw...@gmail.comwrote: On Thu, May 14, 2009 at 5:00 PM, Jim Sellers jim.sell...@gmail.com wrote: Just a note: import is a scope used in the dependency management section, so I found your original question confusing. I had attached the a and b pom, but I did import the the pom in the dependencies section and it worked mostly. So, why is this only to be used in the dependency management section? What I want to achieve is a coupling of dependencies, so the project that depends on these coupling can depend on one dependency, instead of the group of dependencies. So, project A is the coupling project which has dependencies on X, Y and Z. Project B needs X, Y and Z, but instead of depending on the three of them, I want it as a package, thus A. I have inserted project A as a dependency with scope import in B and for most of the dependencies defined in A, project B now works, except for the provided dependency. Is this use case supported? With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Referencing plugin properties
Right, you can't get the value via a property. Maven 1 was totally different
and cross plugin dependencies like that were a big problem and it was
designed out.
On Thu, May 14, 2009 at 4:14 PM, Bocalinda bocali...@gmail.com wrote:
Hi Brian,
I don't want to set the value, I want to get the value.
According to the Maven webpage, it seems that was possible in Maven 1.
2009/5/14 Brian Fox bri...@infinity.nu
You can't reference it from another property. Why don't you just set it
to
the new value?
On Thu, May 14, 2009 at 11:08 AM, Bocalinda bocali...@gmail.com wrote:
Hi List,
It is possible to reference pom properties with ${project.version} for
example.
But how can I reference plugin properties?
I would like to reference the webapp directory. The property is called
webappDirectory, but I can't seem to get it's value.
Thanks.
properties vs pluginManagement
Hi all. I've got a question for how to best configure plugins in a corporate parent pom. One way is to configure the plug in the pluginManagement section, the other is to use the properties that the plugin uses. eg. build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId configuration wtpmanifesttrue/wtpmanifest wtpapplicationxmltrue/wtpapplicationxml wtpversion2.0/wtpversion /configuration /plugin /plugins /pluginManagement /build vs properties !-- WTP properties used by the maven-eclipse-plugin -- eclipse.wtpmanifesttrue/eclipse.wtpmanifest eclipse.wtpapplicationxmltrue/eclipse.wtpapplicationxml wtpversion2.0/wtpversion /properties Is there any advantage of one over the other? Thanks for your time, Jim
RE: properties vs pluginManagement
-Original Message- From: Jim Sellers [mailto:jim.sell...@gmail.com] Sent: Thursday, May 14, 2009 1:38 PM To: Maven Users List Subject: properties vs pluginManagement Hi all. I've got a question for how to best configure plugins in a corporate parent pom. One way is to configure the plug in the pluginManagement section, the other is to use the properties that the plugin uses. snip I strongly prefer the pluginManagement approach. For one thing, it makes very clear that the property is intended for a plugin, and what plugin it's intended for, instead of leaving you guessing. Imagine that you were using the properties approach for a couple years, then someone handed you the job of eliminating the properties that weren't being used. -- Bryan This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Problem with appassembler-maven-plugin
Hi,
i have a working maven project which has no modules ...
I'm using things like Assembly-Plugin to create a binary package etc.
But now i have decided to use the appassembler-maven-plugin and tried to
configure the plugin
and it doesn't work...
Here you can find the appropriate pom:
http://svn.supose.org/supose/trunk/pom.xml
I have tried to configure it for packaging:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdappassembler-maven-plugin/artifactId
version1.0/version
configuration
binPrefixSupoSE/binPrefix
assembleDirectory${project.build.directory}/supose-assembler/assembleDirectory
extraJvmArguments-Xms512m -Xmx1024m/extraJvmArguments
generateRepositoryfalse/generateRepository
repositoryNamelib/repositoryName
repositoryLayoutflat/repositoryLayout
includeConfigurationDirectoryInClasspathtrue/includeConfigurationDirectoryInClasspath
platforms
platformwindows/platform
platformunix/platform
/platforms
programs
program
mainClasscom.soebes.supose.cli.SuposeCLI/mainClass
namesupose/name
/program
/programs
executions
execution
phasepackage/phase
goals
goalassemble/goal
/goals
/execution
/executions
/configuration
/plugin
So i would like to run it before the assembly plugin to package the bin
package containing the script's which have been created by the
appassembler plugin...
But i can't get it to work with:
mvn package
I can call it manually: mvn appassembler:assemble
So did i oversight something ? Wrong Configuration ?
Does someone has a hint ?
Many thanks in advance...
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with appassembler-maven-plugin
Hi,
sorry missed to add the pom.xml file.
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdcom.soebes/groupId
artifactIdsupose/artifactId
version0.5.3-SNAPSHOT/version
packagingjar/packaging
nameSubversion Repository Search Engine/name
descriptionSupoSE is an approache to scan a whole Subversion Repository an put all needed information
into an Lucene Index to do search queris on it later./description
urlhttp://www.supose.org/url
licenses
license
nameThe GNU General Public License Version 2/name
urlhttp://www.gnu.org/licenses/gpl-2.0.txt/url
distributionrepo/distribution
!-- commentsComments/comments --
/license
/licenses
properties
maven-license-plugin.version1.4.0/maven-license-plugin.version
quartz.version1.6.4/quartz.version
ini4j.version0.5.1/ini4j.version
lucene.version2.4.0/lucene.version
tika.version0.3/tika.version
/properties
organization
nameSoftwareEntwicklung Beratung Schulung/name
urlhttp://www.soebes.de/url
/organization
developers
developer
idkama/id
nameKarl Heinz Marbase/name
emailk...@soebes.de/email
timezone+1/timezone
roles
roleproject lead/role
rolecommiter/role
/roles
/developer
/developers
contributors
contributor
emailmsu...@redhat.com/email
roles
rolereporter/role
roletester/role
/roles
/contributor
contributor
emailbill@sungardhe.com/email
roles
rolereporter/role
roletester/role
/roles
/contributor
contributor
nameMark Schlieker/name
roles
rolereporter/role
roletester/role
/roles
/contributor
/contributors
issueManagement
systemRedmine/system
urlhttp://www.supose.org/url
/issueManagement
ciManagement
systemHudson/system
url${cimanagement.url}/url
/ciManagement
scm
connectionscm:svn:http://svn.serverix/supose//connection
developerConnectionscm:svn:http://svn.serverix/supose/trunk/developerConnection
urlhttp://www.supose.org/repositories/show/supose/url
/scm
build
finalName${project.artifactId}-${project.version}-${buildNumber}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.2/version
executions
execution
phaseclean/phase
configuration
tasks unless=maven.test.skip
echoSCM URL: ${system.scm.url}/echo
echoSCM DEV: ${system.scm.dev}/echo
echoSCM CON: ${system.scm.connection}/echo
echo DI URL: ${system.site.deployment}/echo
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
plugin
artifactIdmaven-clean-plugin/artifactId
configuration
filesets
fileset
directorytest-output/directory
/fileset
/filesets
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
debugtrue/debug
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-resources-plugin/artifactId
version2.3/version
configuration
encodingUTF-8/encoding
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.4.3/version
configuration
forkModeonce/forkMode
printSummarytrue/printSummary
useFiletrue/useFile
testFailureIgnoretrue/testFailureIgnore
suiteXmlFiles
suiteXmlFilesrc/test/resources/test-all.xml/suiteXmlFile
/suiteXmlFiles
/configuration
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
/plugin
!-- to be sure the created file of the coverage report will be delted --
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdcobertura-maven-plugin/artifactId
version2.2/version
executions
execution
idclean/id
goals
goalclean/goal
/goals
/execution
/executions
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-3/version
configuration
descriptors
descriptorsrc/main/assembly/bin.xml/descriptor
descriptorsrc/main/assembly/src.xml/descriptor
/descriptors
/configuration
executions
execution
phasepackage/phase
goals
goalsingle/goal
/goals
Re: subproject dependency
If I run theinstall command with -e flag then I dont get this error please tell me why I get error without -e flag ? fachhoch wrote: I created a maven project which has three sub projects one for ear , one for war and one for jar.War has dependency to jar and ear has dependency to war. When I try to install project i get this error Reason: Failed to copy file for artifact[active project artifact: artifact = gov.audit:audit.jar:jar:1:compile; project: MavenProject: gov.audit:audit.jar:1 @ E:\dev\eclipse\Audit\Audit.gov\audit.jar\pom.xml] I tried in other way first build jar , it works fine then when I build war I get this error The following mojo encountered an error while executing: Group-Id: org.apache.maven.plugins Artifact-Id: maven-war-plugin Version: 2.1-alpha-1 Mojo: war brought in via: packaging: war While building project: Group-Id: gov.audit Artifact-Id: audit.war Version: 1 From file: E:\dev\eclipse\Audit\Audit.gov\audit.war\pom.xml Reason: Failed to copy file for artifact[gov.audit:audit.jar:jar:1:compile] also pom file for my war project ?xml version=1.0 encoding=UTF-8?project parent artifactIdAudit.gov/artifactId groupIdgov.audit/groupId version1/version /parent modelVersion4.0.0/modelVersion groupIdgov.audit/groupId artifactIdaudit.war/artifactId packagingwar/packaging nameaudit.war Maven Webapp/name version1/version urlhttp://maven.apache.org/url build finalNameaudit/finalName /build dependencies dependency groupIdgov.audit/groupId artifactIdaudit.jar/artifactId version1/version /dependency /dependencies /project please tell me if i specified correctly dependency for my sub project ? -- View this message in context: http://www.nabble.com/subproject-dependency-tp23484464p23549820.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: Deploy an EAR into Websphere Application Server 6.1 using maven plugins
I don't know about WAS 6.1 but in WAS 6.02 you can't use the deployment ant task in a regular ant version you have to use the ws-ant utility supplied with Websphere. You could try having a separate build.xml with the deployment stuff in it and use the ant exec task to run ws-ant in its own JVM. Thanks. --Lee On Thu, May 14, 2009 at 2:16 PM, Martín Bárcenas martin.barce...@carmeth.com wrote: I'm trying to deploy on websphere 6.1 using the *maven-antrun-plugin* but I have a trouble executing the tasks displaying the following error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An Ant BuildException has occured: Unable to parse setupCmdLine:null\bin\setupCmdLine.bat (The system cannot find the path specified.) This error appears because somewhere on the maven lifecycle lost the wasHome, I couldn't continue... I also tried to deploy it using was6-maven-plugin but it gives me other error, I already asked about it but it haven't been answered yet... I have been looking for information or documentation but I didn't found anything... Someone know what is happening? Any idea? Thanks. -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com
Re: How would you approach this?
Maybe you can solve this by using multiple WAR projects that the EAR project depends on. -- Lee On Thu, May 14, 2009 at 9:51 AM, Brian Fox bri...@infinity.nu wrote: On Tue, May 12, 2009 at 1:58 PM, Doug Hughes dhug...@alagad.com wrote: Hi, I've been writing to the list off and on over the past few days. I'm a ColdFusion developer and I'm looking at Maven for a few different reasons. Mainly, I'm exploring the option of using Groovy+Spring+Hibernate to create the service layers and models for my applications. ColdFusion is simply a JEE app that can compile CFML code to Java bytecode and execute it. A typicaly ColdFuson developer would treat ColdFusion similar to how a PHP developer might. IE, they'd connect ColdFusion (running in its container) to a web server like Apache and have it compile and run CFML source code. However, because CF is Java we also have the ability to easily instantiate Java classes and work with them. CF is great for presentation work and many OO development tasks, but it's interpreted nature can sometimes cause issues. So there's a bit of a moment to look at Groovy to create a Java-based, compiled model and then using MVC frameworks in ColdFusion for presentation. This also makes a nice way to share an application's model between Flex and HTML UIs. Anyhow, ColdFusion itself can be deployed as a WAR or EAR file. If you do a WAR deployment there's actually both a cfusion.war and rds.war file. Both are needed to get the full range of features of the language and server. If I deployed the ear file both war files are included in it. If I were to deply war files to Jboss, for example, I'd put both war files (epanded) into the /server/default/deploy directory. When working with Maven, I'm not quite sure how to accomplish this. I've found that if I can expand the cfusion.war into the default webapp archetype's src/main/webapp directory and it will just work. However, I'm not sure where to put the rds.war, or if it's even possible to run more than on war file through maven. How would you do this? I'm not sure what you mean by run more than one through Maven My ultimate goal would be to have something like this: A parent project to build everything. A child project for my Groovy/Java code. This gets compiled into a jar and used by my next child project. Another child project which would be a webapp with the cfusion.war and rds.war deployed into it, along with any CFML code and the jar created in the first child project. This would be built into well, I'm not 100% sure. :) Probably a war file that would be deployed to a server but maybe it would really just be one war which as CF, my jar, and CFML code. The second rds.war would be used essentialy as-is. Are you talking about building something using the Coldfusion wars, or deploying it. I'm confused. Anyhow, I'd appreciate your feedback and suggestions. Thanks, Doug Hughes -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com
Re: Failed to load plugin descriptor for: com.google.code.maven-license-plugin:maven-license-plugin:check
I don't want to send a blank message just to see whether I can post to
mailing list. There is some traffic and I cannot imagine that such
experts couldn't solve my problem :) Honestly all my efforts are
wasted and don't know what to do.
I'm following setup from zero tutorial and one one the point contains
following phrase:
import all projects to Eclipse then select all of them and click Maven /
enable dependency management.
Unfortunately this generates following output:
12.05.09 15:03:16 CEST: [INFO]
12.05.09 15:03:16 CEST: [INFO] Building jAgE applications vanilla-genetic
12.05.09 15:03:16 CEST: [INFO]
12.05.09 15:03:16 CEST: [INFO] Id:
org.jage.student:jage-applications-vanilla-genetic:jar:2.2.0
12.05.09 15:03:16 CEST: [INFO] task-segment: [process-resources]
12.05.09 15:03:16 CEST: [INFO]
12.05.09 15:03:16 CEST: [INFO] Attempting to resolve a version for plugin:
com.google.code.maven-license-plugin:maven-license-plugin using
meta-version: LATEST
12.05.09 15:03:16 CEST: [INFO] Attempting to resolve a version for plugin:
com.google.code.maven-license-plugin:maven-license-plugin using
meta-version: RELEASE
12.05.09 15:03:16 CEST: Adding resource folder
/jage-applications-vanilla-genetic/src/main/resources
12.05.09 15:03:16 CEST: Build error for
/jage-applications-vanilla-genetic/pom.xml;
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to construct
build plan for: jAgE applications vanilla-genetic
Id: org.jage.student:jage-applications-vanilla-genetic:jar:2.2.0
task-segment: [process-resources]. Reason: Failed to load plugin descriptor
for: com.google.code.maven-license-plugin:maven-license-plugin:check. Cannot
discover it's default phase, specified in its plugin descriptor.
12.05.09 15:03:16 CEST: Setting source compatibility: 1.5
12.05.09 15:03:16 CEST: Setting target compatibility: 1.5
Search result for -
http://www.google.pl/search?q=Failed+to+load+plugin+descriptor+for%3A+com.google.code.maven-license-plugin%3Amaven-license-plugin%3Acheck.ie=utf-8oe=utf-8aq=trls=org.mozilla:pl:officialclient=firefox-a
- doesn't bring any answers.
I also tried commenting this part of pom.xml:
!-- check license --
plugin
groupIdcom.google.code.maven-license-plugin/groupId
artifactIdmaven-license-plugin/artifactId
configuration
basedir${basedir}/basedir
headersrc/etc/license.txt/header
quietfalse/quiet
failIfMissingfalse/failIfMissing
includes
includesrc/**/*.java/include
includesrc/**/*.html/include
include**/test/**/*.java/include
/includes
useDefaultExcludestrue/useDefaultExcludes
useDefaultMappingtrue/useDefaultMapping
encodingUTF-8/encoding
/configuration
executions
execution
goals
goalcheck/goal
/goals
/execution
/executions
/plugin
I also tried adding this:
dependency
groupIdcom.google.code.maven-license-plugin/groupId
artifactIdmaven-license-plugin/artifactId
version1.4.0/version
/dependency
Nothing works and I'm making blind guesses, but I'm sure that solution
is obvious :/
Best regards
Michał Stefanów
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Deploy an EAR into Websphere Application Server 6.1 using maven plugins
Yeah, I forgot to comment that... And you're right everything it's fine when I build my EAR with ws-ant in a separate script... Probably I sound like I'd be obsessed if I insist but that's because I use to work with maven always I've needed to develop an J2EE application... I don't know It's just that I would like to know if it has solution... Thanks. On Thu, May 14, 2009 at 5:05 PM, Lee Meador l...@leemeador.com wrote: I don't know about WAS 6.1 but in WAS 6.02 you can't use the deployment ant task in a regular ant version you have to use the ws-ant utility supplied with Websphere. You could try having a separate build.xml with the deployment stuff in it and use the ant exec task to run ws-ant in its own JVM. Thanks. --Lee On Thu, May 14, 2009 at 2:16 PM, Martín Bárcenas martin.barce...@carmeth.com wrote: I'm trying to deploy on websphere 6.1 using the *maven-antrun-plugin* but I have a trouble executing the tasks displaying the following error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An Ant BuildException has occured: Unable to parse setupCmdLine:null\bin\setupCmdLine.bat (The system cannot find the path specified.) This error appears because somewhere on the maven lifecycle lost the wasHome, I couldn't continue... I also tried to deploy it using was6-maven-plugin but it gives me other error, I already asked about it but it haven't been answered yet... I have been looking for information or documentation but I didn't found anything... Someone know what is happening? Any idea? Thanks. -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com
Re: Failed to load plugin descriptor for: com.google.code.maven-license-plugin:maven-license-plugin:check
Ok remove the dependency block. Then put version 1.4.0 elements in the
plugin section (not required, but a best practice[1][2]) . Then the error is
implying that the plugin has no default phase to run it in. You have bound
the plugin via the execution and told it to run the check goal, but you
didn't specify a phase. Add something like phasevalidatephase inside the
execution element. That will solve your problem. There's a free maven
book[3] and some more how-tos[4] that's worth looking at if you're new to
maven.
[1] http://www.sonatype.com/people/2008/04/maven-209-released/
[2]
http://www.sonatype.com/people/2008/05/optimal-maven-plugin-configuration/
[3] http://www.sonatype.com/products/maven/documentation/book-defguide
[4] http://www.sonatype.com/people/2009/04/summary-of-maven-how-tos/
2009/5/14 Michał Stefanów mstefa...@gmail.com
I don't want to send a blank message just to see whether I can post to
mailing list. There is some traffic and I cannot imagine that such
experts couldn't solve my problem :) Honestly all my efforts are
wasted and don't know what to do.
I'm following setup from zero tutorial and one one the point contains
following phrase:
import all projects to Eclipse then select all of them and click Maven /
enable dependency management.
Unfortunately this generates following output:
12.05.09 15:03:16 CEST: [INFO]
12.05.09 15:03:16 CEST: [INFO] Building jAgE applications vanilla-genetic
12.05.09 15:03:16 CEST: [INFO]
12.05.09 15:03:16 CEST: [INFO] Id:
org.jage.student:jage-applications-vanilla-genetic:jar:2.2.0
12.05.09 15:03:16 CEST: [INFO] task-segment: [process-resources]
12.05.09 15:03:16 CEST: [INFO]
12.05.09 15:03:16 CEST: [INFO] Attempting to resolve a version for
plugin:
com.google.code.maven-license-plugin:maven-license-plugin using
meta-version: LATEST
12.05.09 15:03:16 CEST: [INFO] Attempting to resolve a version for
plugin:
com.google.code.maven-license-plugin:maven-license-plugin using
meta-version: RELEASE
12.05.09 15:03:16 CEST: Adding resource folder
/jage-applications-vanilla-genetic/src/main/resources
12.05.09 15:03:16 CEST: Build error for
/jage-applications-vanilla-genetic/pom.xml;
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
construct
build plan for: jAgE applications vanilla-genetic
Id: org.jage.student:jage-applications-vanilla-genetic:jar:2.2.0
task-segment: [process-resources]. Reason: Failed to load plugin
descriptor
for: com.google.code.maven-license-plugin:maven-license-plugin:check.
Cannot
discover it's default phase, specified in its plugin descriptor.
12.05.09 15:03:16 CEST: Setting source compatibility: 1.5
12.05.09 15:03:16 CEST: Setting target compatibility: 1.5
Search result for -
http://www.google.pl/search?q=Failed+to+load+plugin+descriptor+for%3A+com.google.code.maven-license-plugin%3Amaven-license-plugin%3Acheck.ie=utf-8oe=utf-8aq=trls=org.mozilla:pl:officialclient=firefox-a
- doesn't bring any answers.
I also tried commenting this part of pom.xml:
!-- check license --
plugin
groupIdcom.google.code.maven-license-plugin/groupId
artifactIdmaven-license-plugin/artifactId
configuration
basedir${basedir}/basedir
headersrc/etc/license.txt/header
quietfalse/quiet
failIfMissingfalse/failIfMissing
includes
includesrc/**/*.java/include
includesrc/**/*.html/include
include**/test/**/*.java/include
/includes
useDefaultExcludestrue/useDefaultExcludes
useDefaultMappingtrue/useDefaultMapping
encodingUTF-8/encoding
/configuration
executions
execution
goals
goalcheck/goal
/goals
/execution
/executions
/plugin
I also tried adding this:
dependency
groupIdcom.google.code.maven-license-plugin/groupId
artifactIdmaven-license-plugin/artifactId
version1.4.0/version
/dependency
Nothing works and I'm making blind guesses, but I'm sure that solution
is obvious :/
Best regards
Michał Stefanów
-
To unsubscribe, e-mail:
Re: Failed to load plugin descriptor for: com.google.code.maven-license-plugin:maven-license-plugin:check
I don't want to send a blank message just to see whether I can post to mailing list. There is some traffic and I cannot imagine that such experts couldn't solve my problem :) Honestly all my efforts are wasted and don't know what to do. Next time you're unsure if a message went through to a list, you should check the email list archives at Nabble.com. If Nabble has it, then the message went through. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven continuously initiates transfer of jars
Well the first and earliest ERROR line I get from my Eclipse IDE Console shows this : 10:17:09,078 ERROR [org.springframework.web.context.ContextLoader] Context initialization failed java.lang.NoClassDefFoundError: org/apache/commons/collections15/Closure but I made sure (and double-checked!) that I have collections-generic-4.01.jar in my \WEB-INF classpath together with commons-collections-3.2.jar and commons-logging-1.1.1.jar. -- View this message in context: http://www.nabble.com/Maven-continuously-initiates-transfer-of-jars-tp23534377p23552308.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
