Re: tomcat-m-p war dependency
Hello, I have added a comment in the jira issue. It sounds more reasonnable to have a new mojo for this with a more simple syntax which could executed from the cli. Feel free to add an other comment. Thanks, -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy 2011/1/13 Ryan Connolly ryn...@gmail.com: Ok, my patch has been submitted: http://jira.codehaus.org/browse/MTOMCAT-74 Please do take a peek at it. It would be great to see this in 1.2 if at all possible! -Ryan On Tue, Jan 11, 2011 at 5:27 PM, Olivier Lamy ol...@apache.org wrote: Patchs are always welcome :-) 2011/1/11 Ryan Connolly ryn...@gmail.com: Thanks for the reply, Olivier. I'll give your suggestion a try. Would it be worth my time trying to create a patch for this feature or would rather just a feature request in JIRA? Thanks again. -Ryan On Jan 11, 2011 5:09 PM, Olivier Lamy ol...@apache.org wrote: Hello, It's not supported currently (btw it's a good idea). You can use copy goal [1] from dependency plugin to get your artifact and use deploy-only mojo from t-m-p [1] http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-artifacts.html 2011/1/11 Ryan Connolly ryn...@gmail.com: Hi: Does anyone happen to know whether it is possible to configure tomcat:run to deploy a defined war dependency as well as run the current project as a dynamic web app in the embedded container? I've tried setting the addContextWarDependenciestrue/addContextWarDependencies configuration option and have declared a war dependency in the tomcat-m-p but the dependency does not appear to deploy to the embedded container. Has anyone else tried a similar configuration? Any advice would be appreciated. An example of what I thought might work follows: plugin groupIdorg.codehaus.mojo/groupId artifactIdtomcat-maven-plugin/artifactId version1.1/version configuration addContextWarDependenciestrue/addContextWarDependencies /configuration dependencies dependency groupIdcom.mycompany/groupId artifactIdwar-artifactid/artifactId version1.0/version typewar/type /dependency /dependencies /plugin Thanks, -Ryan -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin Execution Config : Remove Duplication
Thanks Mike. Defining in a Parent POM was what i was thinking but am unsure exactly how this might look. I will have a play about with it and see how it goes. Alan -- View this message in context: http://maven.40175.n5.nabble.com/Plugin-Execution-Config-Remove-Duplication-tp3338224p3339431.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: Artifact not getting downloaded from my-won-remote-repository
Here's one: Ditch the web server and get a real repo manager. I suggest Nexus, but there others. They all have free OSS versions, so there is absolutely no reason to not use them. Ron (one guy on this list) can tell you how they lost two years not using one. :-) /Anders On Thu, Jan 13, 2011 at 07:10, amaresh mourya amaresh.mou...@gmail.comwrote: Hi All, * Case* : I installed apache server and created a repository there in dir : C:\Program Files\Apache Group\Apache2\htdocs\repository\ I put some artifacts in there, I installed artifacts via (mvn install -DcreateChecksum=true) in this repository. These artifacts are basically some plugins that I want to use in my POM Then I specified one of the plugin in my POM and also this repository (that is http://localhost/repository) *Problem*: When I run mvn package on this POM, I was expecting the plugin to get installed in my local repository but only the plugin.pom and plugin.pom.sha1 are getting downloaded from my-remote-repository( http://localhost/repository). It is not downloading the actual JAR that is :plugin.jar Any pointers will be helpful.. Thanks, Amaresh
Re: Artifact not getting downloaded from my-won-remote-repository
On 13 January 2011 08:58, Anders Hammar and...@hammar.net wrote: Here's one: Ditch the web server and get a real repo manager. I suggest Nexus, but there others. They all have free OSS versions, so there is absolutely no reason to not use them. Ron (one guy on this list) can tell you how they lost two years not using one. :-) Yeah but he'll have to put up with the sales pitch for Eclipse/STS and projects that collect dependencies (thereby rendering the very very useful dependency:analyze less useful) ;-) -Stephen /Anders On Thu, Jan 13, 2011 at 07:10, amaresh mourya amaresh.mou...@gmail.comwrote: Hi All, * Case* : I installed apache server and created a repository there in dir : C:\Program Files\Apache Group\Apache2\htdocs\repository\ I put some artifacts in there, I installed artifacts via (mvn install -DcreateChecksum=true) in this repository. These artifacts are basically some plugins that I want to use in my POM Then I specified one of the plugin in my POM and also this repository (that is http://localhost/repository) *Problem*: When I run mvn package on this POM, I was expecting the plugin to get installed in my local repository but only the plugin.pom and plugin.pom.sha1 are getting downloaded from my-remote-repository( http://localhost/repository). It is not downloading the actual JAR that is :plugin.jar Any pointers will be helpful.. Thanks, Amaresh - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Cobertura and Surefire
Stephen Connolly wrote: Because people who have not read and understood concurrency in practice often do not understand how the synchronization points affect jvm sequencing, people often wrongly suspect that result of instrumented and non-instrumented code is the same. I'm not sure, why caring about concurrency is important in this context. I'm not using Maven 3 (so no concurrent builds) and I'm not using concurrent tests with JUnit. But it's quite plain to me it is possible, that instrumented code behaves different to uninstrumented code, so testing the instrumented code can pass the tests while uninstrumented fail. (i.e. because of attributes added by instrumentation, which are unexpected when working with reflection on these attributes) But I think it doesn't happen on a regular basis, that the instrumented code pass or fails the tests, where the uninstrumented doesn't. But sadly it's more regular in our team, that the Cobertura-step fails (not because failing tests but because of too low coverage). Wayne Fay wrote: Perhaps bind something to your scm commit hook so the code simply can't make it into your SCM tool without meeting certain standards for coverage? That would mean, that during the commit we should run all the tests? I'm not sure, I want the commit to last about two minutes. Beside this, we have to use Synergy/CM as SCM tool, which is not capable of pre-commit-hooks (as far as I know). Hilco Wijbenga wrote: A normal unit test should run once, more is just a waste of time. The fact that Maven will run unit tests multiple times is a bug that we apparently have to live with. It is not a feature. If this bug were fixed and you still wanted to run your unit tests twice then you could configure that quite easily in your POM. Everybody happy I don't really like that Maven needs to run tests twice (or more often), too. But I see it is neccessary regarding Cobertura, because -- as stated to Stephen -- it can't be guaranteed, that the instrumented code behaves the same as the uninstrumented. Because of this it is not sufficient to run the tests only on the instrumented code. So this is not a bug in Maven but a problem with Cobertura. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven release:perform deploy failed access denied
Hi,
I'm trying to build my first release of my multi-modules projects.
In my settings.xml :
server
idmy-releases/id
usernamedeployer/username
password123/password
/server
in my main pom.xml :
distributionManagement
repository
idmy-releases/id
nameRepository Nexus/name
urlhttp://serverIp/nexus/content/groups/MyRepositories//url
/repository
/distributionManagement
Unfortunately, I've got this error :
INFO] [INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Uploading:
http://serverIp/nexus/content/groups/MyRepositories//com/project/Parent/0.0.5/Parent-0.0.5.pom
[INFO] [INFO]
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
[INFO] [INFO] Error deploying artifact: Authorization failed: Access denied
to:
http://serverIp/nexus/content/groups/MyRepositories/com/project/Parent/0.0.5/Parent-0.0.5.pom
[INFO]
[INFO] [INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Maven execution
failed, exit code: '1'
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
what's wrong ??
Thx !
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3339497.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: Cobertura and Surefire
On 13 January 2011 09:50, Stefan Schulze algr...@gmx.de wrote: Stephen Connolly wrote: Because people who have not read and understood concurrency in practice often do not understand how the synchronization points affect jvm sequencing, people often wrongly suspect that result of instrumented and non-instrumented code is the same. I'm not sure, why caring about concurrency is important in this context. I'm not using Maven 3 (so no concurrent builds) and I'm not using concurrent tests with JUnit. Between synchronization points, the JVM is allowed to re-order operations as long as the end result remains the same. Cobertura puts a synchronization point in between every line and branch point. Thus the re-ordering of lines cannot take place any more. Start up a JVM and have a look at how many threads are running Still think you are in a single threaded world? Also some simple libraries use threads behind your back... and even the Java Runtime Libraries do that too... Still think you don't have to know/worry about concurrency? I shall repeat... We had some appears to be simple single threaded code that we were testing with a simple test case. The tests were only being run instrumented... the tests were passing the bug was there... seen in production system by big customer... in the end of the day, this was identified as the original author not understanding about the JVM's contract w.r.t. re-ordering operations in-between synchronization points and the fact that using cobertura introduced a synchronization point at every line so that the code as written could only work when instrumented. Run the damn tests at least twice. (I'd like to say run them on multiple JVMs too but Oracle seems intent on merging all the JVMs into openjdk) -Stephen But it's quite plain to me it is possible, that instrumented code behaves different to uninstrumented code, so testing the instrumented code can pass the tests while uninstrumented fail. (i.e. because of attributes added by instrumentation, which are unexpected when working with reflection on these attributes) But I think it doesn't happen on a regular basis, that the instrumented code pass or fails the tests, where the uninstrumented doesn't. But sadly it's more regular in our team, that the Cobertura-step fails (not because failing tests but because of too low coverage). It happens when you least expect it. Wayne Fay wrote: Perhaps bind something to your scm commit hook so the code simply can't make it into your SCM tool without meeting certain standards for coverage? That would mean, that during the commit we should run all the tests? I'm not sure, I want the commit to last about two minutes. Beside this, we have to use Synergy/CM as SCM tool, which is not capable of pre-commit-hooks (as far as I know). Hilco Wijbenga wrote: A normal unit test should run once, more is just a waste of time. The fact that Maven will run unit tests multiple times is a bug that we apparently have to live with. It is not a feature. If this bug were fixed and you still wanted to run your unit tests twice then you could configure that quite easily in your POM. Everybody happy I don't really like that Maven needs to run tests twice (or more often), too. But I see it is neccessary regarding Cobertura, because -- as stated to Stephen -- it can't be guaranteed, that the instrumented code behaves the same as the uninstrumented. Because of this it is not sufficient to run the tests only on the instrumented code. So this is not a bug in Maven but a problem with Cobertura. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl - 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: Cobertura and Surefire
Stephen Connolly wrote: [...] Run the damn tests at least twice. Ok, I see your point. But I never tried to run the tests only instrumented. I just want to execute the more-likely-failing tests earlier in the lifecycle and the not-so-likely-failing tests later. So of course I want to execute both uninstrumented _and_ instrumented tests. -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release:perform on a submodule using git
On 01/12/2011 09:57 PM, Olivier Lamy wrote: Hello, Have a look at http://jira.codehaus.org/browse/MRELEASE-457 That looks like what I want. Thanks. Joachim - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release:perform on a submodule using git
On 01/12/2011 09:59 PM, Jon Paynter wrote: Joachim, ditto on the git-submodule support (but that goes in a different thread). can you try running release:perform on the isolated submodule projects, instead of the superproject? I was doing it on the subproject. I guess the http://jira.codehaus.org/browse/MRELEASE-457 would be a suitable fix. Thanks, Joachim On Wed, Jan 12, 2011 at 12:54 PM, Joachim Van der Auwera joac...@progs.bewrote: I have a large project with many independently releasable submodules. They are stored in one large git repository. When I want to release an individual module, the release:prepare seems to work fine, but the release:perform tries to run a deploy on the entire project. Is there a way to indicate to the relesae plugin what the base directory is for the module inside the repository? I can work around this by interrupting the release:perform and doing a manual mvn -DperformRelease deploy in the proper subdirectory of target/checkout of the module, but it would be nice if the release:perform would just work. (I understand this using one large git repository is against the git philosophy, but git submodule are difficult/unpractical to use and badly supported in IDEs. Joachim - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven JBoss Plugin - Best Plugin to use
Hi, I want to deploy the artifacts to JBoss AS using maven plug-in. I came across two plug-in for this use case (Cargo Plug-in and Jboss-Maven-Plug-in from Codehaus). Please suggest which one is best? Regards, Tirumal Reddy M
Re: Cobertura and Surefire
IMO solution is simple - discipline your developers to run verify before commiting. CI should help you determine whom to blame when build is broken and then you can apply disciplinary meassures. Regards, Stevo. On Thu, Jan 13, 2011 at 11:24 AM, Stefan Schulze algr...@gmx.de wrote: Stephen Connolly wrote: [...] Run the damn tests at least twice. Ok, I see your point. But I never tried to run the tests only instrumented. I just want to execute the more-likely-failing tests earlier in the lifecycle and the not-so-likely-failing tests later. So of course I want to execute both uninstrumented _and_ instrumented tests. -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven JBoss Plugin - Best Plugin to use
Which car is the best, A or B? What's your needs? /Anders On Thu, Jan 13, 2011 at 11:43, Tirumal Reddy Moolamalla t.moolama...@zensar.com wrote: Hi, I want to deploy the artifacts to JBoss AS using maven plug-in. I came across two plug-in for this use case (Cargo Plug-in and Jboss-Maven-Plug-in from Codehaus). Please suggest which one is best? Regards, Tirumal Reddy M
Re: Maven release:perform deploy failed access denied
You don't have access?
I suggest you have a look in the Nexus logs. It will tell you what it
doesn't like with your credentials.
/Anders
On Thu, Jan 13, 2011 at 10:54, jeb001 jeremy.jar...@gmail.com wrote:
Hi,
I'm trying to build my first release of my multi-modules projects.
In my settings.xml :
server
idmy-releases/id
usernamedeployer/username
password123/password
/server
in my main pom.xml :
distributionManagement
repository
idmy-releases/id
nameRepository Nexus/name
url
http://serverIp/nexus/content/groups/MyRepositories//url
/repository
/distributionManagement
Unfortunately, I've got this error :
INFO] [INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Uploading:
http://serverIp/nexus/content/groups/MyRepositories//com/project/Parent/0.0.5/Parent-0.0.5.pom
[INFO] [INFO]
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
[INFO] [INFO] Error deploying artifact: Authorization failed: Access denied
to:
http://serverIp/nexus/content/groups/MyRepositories/com/project/Parent/0.0.5/Parent-0.0.5.pom
[INFO]
[INFO] [INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Maven execution
failed, exit code: '1'
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
what's wrong ??
Thx !
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3339497.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
how to patch releases
Hi all, this might be a simple one and if there is documentation about it I'm happy to read that. Its a basic understanding question: I have a maven project and do a release - lets say 1.1 The maven release plugin manipulates the poms and tags the software in the scm. the trunk itself has e.g. 1.2-SNAPSHOT - everything is fine and the release is done How is the procedure if one needs to patch 1.1 to 1.1.1 ? I guess one has to create a branch from the tagged version. Then the version in the poms have to be set to 1.1.1-SNAPSHOT and then development starts. Is this process only doable by hand or is there also maven tools for that ? And how about releasing it ? Can I use the release plugin again ? does it understand that in the scm tag there is now branches/xxx instead of trunk ? is it the same procedure ? Thanks for any clarification or any link Emerson
Re: Maven release:perform deploy failed access denied
Hum, ok... but, I'm using a distant nexus server.. I'm not administrator... Is there a way for me to see those logs ? thx -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3339723.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : how to patch releases
Hi, I guess one has to create a branch from the tagged version. Then the version in the poms have to be set to 1.1.1-SNAPSHOT and then development starts. Also don't forget to update the scm section of your pom. Your description of the process is good, but I don't know if there is a fully automated way (there is release:branch but AFAIK this is to create a branch from trunk, not a branch from tag). And how about releasing it ? Can I use the release plugin again ? does it understand that in the scm tag there is now branches/xxx instead of trunk ? Yes, release plugin works fine. Regards, Julien - Message d'origine De : mremerson...@aim.com mremerson...@aim.com À : users@maven.apache.org Envoyé le : Jeu 13 janvier 2011, 13h 42min 01s Objet : how to patch releases Hi all, this might be a simple one and if there is documentation about it I'm happy to read that. Its a basic understanding question: I have a maven project and do a release - lets say 1.1 The maven release plugin manipulates the poms and tags the software in the scm. the trunk itself has e.g. 1.2-SNAPSHOT - everything is fine and the release is done How is the procedure if one needs to patch 1.1 to 1.1.1 ? I guess one has to create a branch from the tagged version. Then the version in the poms have to be set to 1.1.1-SNAPSHOT and then development starts. Is this process only doable by hand or is there also maven tools for that ? And how about releasing it ? Can I use the release plugin again ? does it understand that in the scm tag there is now branches/xxx instead of trunk ? is it the same procedure ? Thanks for any clarification or any link Emerson - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how to patch releases
Am Donnerstag 13 Januar 2011, 13:42:01 schrieb mremerson...@aim.com: Hi all, this might be a simple one and if there is documentation about it I'm happy to read that. Its a basic understanding question: I have a maven project and do a release - lets say 1.1 The maven release plugin manipulates the poms and tags the software in the scm. the trunk itself has e.g. 1.2-SNAPSHOT - everything is fine and the release is done How is the procedure if one needs to patch 1.1 to 1.1.1 ? I guess one has to create a branch from the tagged version. Then the version in the poms have to be set to 1.1.1-SNAPSHOT and then development starts. Is this process only doable by hand or is there also maven tools for that ? versions-maven-plugin might be useful for setting the versions with a single command. hth, - martin signature.asc Description: This is a digitally signed message part.
Re: : how to patch releases
Hi Julien Thanks for your mail. You are right the scm section has to be changed too. I will just try with a dummy project how release:branch works. But its good to know that the release plugin then works fine Cheers -Original Message- From: Julien HENRY henr...@yahoo.fr To: Maven Users List users@maven.apache.org Sent: Thu, Jan 13, 2011 1:54 pm Subject: Re : how to patch releases Hi, I guess one has to create a branch from the tagged version. Then the version in the poms have to be set to 1.1.1-SNAPSHOT and then development starts. Also don't forget to update the scm section of your pom. Your description of the process is good, but I don't know if there is a fully automated way (there is release:branch but AFAIK this is to create a branch from trunk, not a branch from tag). And how about releasing it ? Can I use the release plugin again ? does it understand that in the scm tag there is now branches/xxx instead of trunk ? Yes, release plugin works fine. Regards, Julien - Message d'origine De : mremerson...@aim.com mremerson...@aim.com À : users@maven.apache.org Envoyé le : Jeu 13 janvier 2011, 13h 42min 01s Objet : how to patch releases Hi all, this might be a simple one and if there is documentation about it I'm happy to read that. Its a basic understanding question: I have a maven project and do a release - lets say 1.1 The maven release plugin manipulates the poms and tags the software in the scm. the trunk itself has e.g. 1.2-SNAPSHOT - everything is fine and the release is done How is the procedure if one needs to patch 1.1 to 1.1.1 ? I guess one has to create a branch from the tagged version. Then the version in the poms have to be set to 1.1.1-SNAPSHOT and then development starts. Is this process only doable by hand or is there also maven tools for that ? And how about releasing it ? Can I use the release plugin again ? does it understand that in the scm tag there is now branches/xxx instead of trunk ? is it the same procedure ? Thanks for any clarification or any link Emerson - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Deploy .war to shared hosting 'remote server'
Thanks for your reply. Maybe I had misunderstood - the maven-deploy-plugin information I had read. For example - chapter 2.14 in the book Java Power Tools. I will have a look at Cargo. Thanks for your help
Re: Artifact not getting downloaded from my-won-remote-repository
Hi All, With too much of tinkering I found out that nothing was wrong about using apache server and I had to just specify my repository under pluginRepositories section rather than repositories. Problem solved. Thanks to all. On Thu, Jan 13, 2011 at 2:55 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 13 January 2011 08:58, Anders Hammar and...@hammar.net wrote: Here's one: Ditch the web server and get a real repo manager. I suggest Nexus, but there others. They all have free OSS versions, so there is absolutely no reason to not use them. Ron (one guy on this list) can tell you how they lost two years not using one. :-) Yeah but he'll have to put up with the sales pitch for Eclipse/STS and projects that collect dependencies (thereby rendering the very very useful dependency:analyze less useful) ;-) -Stephen /Anders On Thu, Jan 13, 2011 at 07:10, amaresh mourya amaresh.mou...@gmail.com wrote: Hi All, * Case* : I installed apache server and created a repository there in dir : C:\Program Files\Apache Group\Apache2\htdocs\repository\ I put some artifacts in there, I installed artifacts via (mvn install -DcreateChecksum=true) in this repository. These artifacts are basically some plugins that I want to use in my POM Then I specified one of the plugin in my POM and also this repository (that is http://localhost/repository) *Problem*: When I run mvn package on this POM, I was expecting the plugin to get installed in my local repository but only the plugin.pom and plugin.pom.sha1 are getting downloaded from my-remote-repository( http://localhost/repository). It is not downloading the actual JAR that is :plugin.jar Any pointers will be helpful.. Thanks, Amaresh - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Artifact not getting downloaded from my-won-remote-repository
On 13/01/2011 4:25 AM, Stephen Connolly wrote: On 13 January 2011 08:58, Anders Hammarand...@hammar.net wrote: Here's one: Ditch the web server and get a real repo manager. I suggest Nexus, but there others. They all have free OSS versions, so there is absolutely no reason to not use them. Ron (one guy on this list) can tell you how they lost two years not using one. :-) +1 Yeah but he'll have to put up with the sales pitch for Eclipse/STS and projects that collect dependencies (thereby rendering the very very useful dependency:analyze less useful) ;-) A IDE with full GUI support for Maven is a real help. (thereby rendering the very very useful dependency:analyze less useful) should be (thereby rendering the very very useful dependency:analyze required less often) Ron -Stephen /Anders On Thu, Jan 13, 2011 at 07:10, amaresh mouryaamaresh.mou...@gmail.comwrote: Hi All, * Case* : I installed apache server and created a repository there in dir : C:\Program Files\Apache Group\Apache2\htdocs\repository\ I put some artifacts in there, I installed artifacts via (mvn install -DcreateChecksum=true) in this repository. These artifacts are basically some plugins that I want to use in my POM Then I specified one of the plugin in my POM and also this repository (that is http://localhost/repository) *Problem*: When I run mvn package on this POM, I was expecting the plugin to get installed in my local repository but only theplugin.pom and plugin.pom.sha1 are getting downloaded from my-remote-repository( http://localhost/repository). It is not downloading the actual JAR that is :plugin.jar Any pointers will be helpful.. Thanks, Amaresh - 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
How to override the default logger?
Hi there, I would like to verride Maven's default logger with my own. How to do this? I see that Mojo has a setLog() method, so I was thinking of making a mojo that executes in the first phase (validate), it would set the log with setLog()... and then all the other mojos that execute in the later phases would use this logger. Would this work? Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Cobertura and Surefire
Perhaps a different CI job structuring? This has worked well for me at many customers: Have a CI job for only compile and unit tests - this maintains the most important very fast turnaround. Have a second CI job for (longer running) IT tests that only runs with success of the first. Have a third job for coverage, standalone or as part of a full system site gen or using Sonar or other... On Thu, Jan 13, 2011 at 5:14 AM, Stevo Slavić ssla...@gmail.com wrote: IMO solution is simple - discipline your developers to run verify before commiting. CI should help you determine whom to blame when build is broken and then you can apply disciplinary meassures. Regards, Stevo. On Thu, Jan 13, 2011 at 11:24 AM, Stefan Schulze algr...@gmx.de wrote: Stephen Connolly wrote: [...] Run the damn tests at least twice. Ok, I see your point. But I never tried to run the tests only instrumented. I just want to execute the more-likely-failing tests earlier in the lifecycle and the not-so-likely-failing tests later. So of course I want to execute both uninstrumented _and_ instrumented tests. -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:perform deploy failed access denied
Nope. You need either os access or ui/rest access. /Anders On Thu, Jan 13, 2011 at 13:45, jeb001 jeremy.jar...@gmail.com wrote: Hum, ok... but, I'm using a distant nexus server.. I'm not administrator... Is there a way for me to see those logs ? thx -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3339723.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: Cobertura and Surefire
Jeff Jensen wrote: Perhaps a different CI job structuring? This has worked well for me at many customers: Have a CI job for only compile and unit tests - this maintains the most important very fast turnaround. Have a second CI job for (longer running) IT tests that only runs with success of the first. Have a third job for coverage, standalone or as part of a full system site gen or using Sonar or other... Sounds nice, but this doesn't meet my requirement, that the tests with coverage-checks (and only one time, not twice) should run, when the developers do mvn test. We have a quite small difference between coverage-threshold and actual coverage, so I think it's important, that the developers check their coverage during development, so they can react early. Another problem to your solution is, that we unfortunately don't use a regular CI-server but a bunch of shellscripts and cron-jobs. So it's not as trivial as with Hudson (Jenkins?) to use this kind of build-pipeline. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
why does maven use /bin/sh -c ls -1lna /djb3/... just to get a file attribute?
On OpenVMS, with JDK 1.5, and maven 3.0 I can download now perfectly forcing basic authentication toward our proxy server. But as downloading artefacts from repositories works now perfect, I want to do bigger steps. i.e. building the svnkit so here we go IA64mvn -Dhttp.auth.preference=Basic --version Apache Maven 3.0 (r1036088; 2010-11-23 18:19:59+0100) Java version: 1.5.0 Java home: /dkb3/java$150/jre Default locale: en, platform encoding: ISO8859-1 OS name: openvms version: v8.3-1h1 arch: ia64 Family: openvms IA64 IA64 set default dkb3:[sw-projekte.asf.svnkit.tags.1_3_3] IA64 IA64mvn -Dhttp.auth.preference=Basic clean install [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building SVNKit 1.3.3 [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ svnkit --- [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ svnkit --- [WARNING] Using platform encoding (ISO8859-1 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ svnkit --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ svnkit --- [WARNING] Using platform encoding (ISO8859-1 actually) to copy filtered resources, i.e. build is platform dependent! [INFO] skip non existing resourceDirectory /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/src/test/resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ svnkit --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.5:test (default-test) @ svnkit --- [INFO] No tests to run. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ svnkit --- [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 6.099s [INFO] Finished at: Thu Jan 13 14:05:34 CET 2011 [INFO] Final Memory: 4M/62M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:2.3.1:jar (default-jar) on project svnkit: Error assembling JAR: Failed to read filesystem attributes for: /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlad /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml': Error while executing process. Child creation error: no such file or directory - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException IA64dir :-( How can java catch file system attributes better? Why do we use a Unix shell command to create a child prozess (sub-process in openvms) by Java just to catch a file system attribute? Creating child processes is an overkill and slows down maven and other SW when used. This claim is placed - because not every operating system has by default - a Unix command shell - to create a child process - to execute a directory command - just to get a file system attribute! But it seems that on my OpenVMS with default DCL command language, the maven version 3 under java and a JVM attempts to place a command which should create a child process just to execute a ls command used to retrieve a file attribute. I call it a style break, we should not do it from Java and not assume Unix or the like shells avail, or we are at risk that over time fewer system will support what maven attempts to do. Josef.Stadelmann @axa-winterthur.ch
AW: Cobertura and Surefire
Jeff Jensen wrote: Perhaps a different CI job structuring? This has worked well for me at many customers: Have a CI job for only compile and unit tests - this maintains the most important very fast turnaround. Have a second CI job for (longer running) IT tests that only runs with success of the first. Have a third job for coverage, standalone or as part of a full system site gen or using Sonar or other... Sounds nice, but this doesn't meet my requirement, that the tests with coverage-checks (and only one time, not twice) should run, when the developers do mvn test. We have a quite small difference between coverage-threshold and actual coverage, so I think it's important, that the developers check their coverage during development, so they can react early. Another problem to your solution is, that we unfortunately don't use a regular CI-server but a bunch of shellscripts and cron-jobs. So it's not as trivial as with Hudson (Jenkins?) to use this kind of build-pipeline. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to write a plugin that generates source files based on the source in the project?
Hi I'm trying to write a plugin which does the following: - Check the classes in the project and keep all classes that implement interface X. - For all X, get the fields, and if a field has a certain annotation, generate a class containing some constant information. Normally the plugin should be bound to the phase 'generate-sources'. However, the classes of the project aren't compiled yet at that moment, so I can't just get them from the classpath, right? Does anyone have a good idea or pointers how to do this correctly? Thanks best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Deploy .war to shared hosting 'remote server'
Maybe I had misunderstood - the maven-deploy-plugin information I had read. For example - chapter 2.14 in the book Java Power Tools. I found that book on Amazon and was able to dig inside it a little bit to look at chapter 2.14. You simply don't know/understand that the use of the word deploy in Maven is different from what you generally understand it to mean, and the author doesn't appear to take the time to explain it in that section either, or if he did, I missed it. Deploy in Maven means upload an artifact to a remote Maven repo using the Maven repo structure/layout so others using Maven can find and use it. That is exactly what the maven-deploy-plugin is doing for you. You can think of deploy in Maven to mean essentially mvn install to a remote server. The next section in the book 2.15 talks about deploying your app to various app servers using Cargo. This is the kind of deployment you are looking for. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to write a plugin that generates source files based on the source in the project?
xdoclet is a tool for parsing java and also generate java, but it is kind of old now /Lucas On 01/13/2011 04:48 PM, Lewis, Eric wrote: Hi I'm trying to write a plugin which does the following: - Check the classes in the project and keep all classes that implement interface X. - For all X, get the fields, and if a field has a certain annotation, generate a class containing some constant information. Normally the plugin should be bound to the phase 'generate-sources'. However, the classes of the project aren't compiled yet at that moment, so I can't just get them from the classpath, right? Does anyone have a good idea or pointers how to do this correctly? Thanks best regards, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Lucas Persson | Principal Member of Technical Staff Phone: +4684773644 | | | Mobile: +46730946656 Oracle Communications Platform ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm Oracle Svenska AB, Kronborgsgrnd 17, S-164 28 KISTA, reg.no. 556254-6746 Oracle is committed to developing practices and products that help protect the environment
RE: Deploy .war to shared hosting 'remote server'
Thanks for your time much appreciated. I am looking a Cargo but in the simple case I have the 'shared hosting' remote server does not give me access to 'tomcat/manager' so I think this will not work either but I have only just started looking. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: 13 January 2011 15:48 To: Maven Users List Subject: Re: Deploy .war to shared hosting 'remote server' Maybe I had misunderstood - the maven-deploy-plugin information I had read. For example - chapter 2.14 in the book Java Power Tools. I found that book on Amazon and was able to dig inside it a little bit to look at chapter 2.14. You simply don't know/understand that the use of the word deploy in Maven is different from what you generally understand it to mean, and the author doesn't appear to take the time to explain it in that section either, or if he did, I missed it. Deploy in Maven means upload an artifact to a remote Maven repo using the Maven repo structure/layout so others using Maven can find and use it. That is exactly what the maven-deploy-plugin is doing for you. You can think of deploy in Maven to mean essentially mvn install to a remote server. The next section in the book 2.15 talks about deploying your app to various app servers using Cargo. This is the kind of deployment you are looking for. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
MacPorts Maven
Does anyone install maven via macports??? If so you might be interested in some tickets I've just submitted: #27944 - Upgrade maven3 to 3.0.2 #27946 - maven_select (similar to python_select, so you can easly switch between maven2 and maven3) #27947 - maven3 update to use maven_select #27948 - maven2 update to use maven_select Do people still use maven 1.x? Just wondering if I should spend anytime on getting that to the latest version and integrated into maven_select. John - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : How to write a plugin that generates source files based on the source in the project?
Hi, You should try to use new JDK 1.6 annotation processor utilities. The only constraint I see is that each class you want to parse must be annotated. Regards, Julien - Message d'origine De : Lewis, Eric eric.le...@ipi.ch À : users@maven.apache.org users@maven.apache.org Envoyé le : Jeu 13 janvier 2011, 16h 48min 14s Objet : How to write a plugin that generates source files based on the source in the project? Hi I'm trying to write a plugin which does the following: - Check the classes in the project and keep all classes that implement interface X. - For all X, get the fields, and if a field has a certain annotation, generate a class containing some constant information. Normally the plugin should be bound to the phase 'generate-sources'. However, the classes of the project aren't compiled yet at that moment, so I can't just get them from the classpath, right? Does anyone have a good idea or pointers how to do this correctly? Thanks best regards, Eric - 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: Deploy .war to shared hosting 'remote server'
On Thu, Jan 13, 2011 at 11:19 AM, Nigel Weinronk nweinr...@btinternet.com wrote: Thanks for your time much appreciated. I am looking a Cargo but in the simple case I have the 'shared hosting' remote server does not give me access to 'tomcat/manager' so I think this will not work either but I have only just started looking. If you just want to upload a file to an arbitrary place on some remote server, see if the wagon plugin will help. http://mojo.codehaus.org/wagon-maven-plugin/usage.html -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Cobertura and Surefire
Sounds nice, but this doesn't meet my requirement, that the tests with coverage-checks (and only one time, not twice) should run, when the developers do mvn test. It sounds like Maven cannot, for whatever reason, meet your requirement. We have a quite small difference between coverage-threshold and actual coverage, so I think it's important, that the developers check their coverage during development, so they can react early. It seems like you are only running into this problem because your coverage is running arbitrarily close to the 80% cutoff that you defined for test coverage. Perhaps you should instead focus some energies on bumping your test coverage a lot so you are not so close to the cutoff (so people aren't casually bumping into it so regularly), or knock the cutoff down to 75% or so to give some breathing room? Another problem to your solution is, that we unfortunately don't use a regular CI-server but a bunch of shellscripts and cron-jobs. So it's not as trivial as with Hudson (Jenkins?) to use this kind of build-pipeline. Why can't you set up a more formal CI server like Hudson? This is solution proposed by Jeff is a reasonable one and I know this same strategy is used by a lot of groups doing CI. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Deploy .war to shared hosting 'remote server'
Thanks I will look at this. -Original Message- From: Wendy Smoak [mailto:wsm...@gmail.com] Sent: 13 January 2011 16:50 To: Maven Users List Subject: Re: Deploy .war to shared hosting 'remote server' On Thu, Jan 13, 2011 at 11:19 AM, Nigel Weinronk nweinr...@btinternet.com wrote: Thanks for your time much appreciated. I am looking a Cargo but in the simple case I have the 'shared hosting' remote server does not give me access to 'tomcat/manager' so I think this will not work either but I have only just started looking. If you just want to upload a file to an arbitrary place on some remote server, see if the wagon plugin will help. http://mojo.codehaus.org/wagon-maven-plugin/usage.html -- Wendy - 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: why does maven use /bin/sh -c ls -1lna /djb3/... just to get a file attribute?
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:2.3.1:jar (default-jar) on project svnkit: Error assembling JAR: Failed to read filesystem attributes for: /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlad /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml': Error while executing process. Child creation error: no such file or directory - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] Well, what does it look like when you run with -e or -X? Don't send the full output back to the list -- post it at pastebin.org and send us a link, unless you can chop it down to the bare minimum of info yourself. How can java catch file system attributes better? Why do we use a Unix shell command to create a child prozess (sub-process in openvms) by Java just to catch a file system attribute? You'd have to ask the JDK folks these questions. What JDK are you using, and from what vendor? But it seems that on my OpenVMS with default DCL command language, the maven version 3 under java and a JVM attempts to place a command which should create a child process just to execute a ls command used to retrieve a file attribute. Most likely the Java code written by the Maven team (or Java code being used in Maven that is actually from plexus-utils or another library) is simply leveraging standard Java file io routines which happen to use the child process to execute ls etc. If there was a better way to get this information, I'd expect it would have been implemented, or perhaps OpenVMS is just not very well supported by the Java platform? Maybe you could dig deep into the code (debug Maven, plexus, and the jdk itself in Netbeans or something), find where this child process thing is coming from, and offer up a patch to the appropriate party? I call it a style break, we should not do it from Java and not assume Unix or the like shells avail, or we are at risk that over time fewer system will support what maven attempts to do. This has very little to do with Maven, and is primarily the fault of the JDK on OpenVMS. I would assume that a better approach to finding the file attributes is available, but no one cares enough about OpenVMS to implement it or pay for it? You are literally the only person I've seen post questions on this list about OpenVMS (Nabble archives reveal 1 other person has posted about it minimally) so it seems to be a pretty low-use OS, at least as far as Maven is concerned. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: why does maven use /bin/sh -c ls -1lna /djb3/... just to get a file attribute?
Hi, Wayne; this has nothing to do with the JDK and everything to do with Plexus. http://plexus.codehaus.org/plexus-components/plexus-io/xref/org/codehaus/plexus/components/io/attributes/PlexusIoResourceAttributeUtils.html#255 Best, Laird On Thu, Jan 13, 2011 at 1:51 PM, Wayne Fay wayne...@gmail.com wrote: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:2.3.1:jar (default-jar) on project svnkit: Error assembling JAR: Failed to read filesystem attributes for: /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlad /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml': Error while executing process. Child creation error: no such file or directory - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] Well, what does it look like when you run with -e or -X? Don't send the full output back to the list -- post it at pastebin.org and send us a link, unless you can chop it down to the bare minimum of info yourself. How can java catch file system attributes better? Why do we use a Unix shell command to create a child prozess (sub-process in openvms) by Java just to catch a file system attribute? You'd have to ask the JDK folks these questions. What JDK are you using, and from what vendor? But it seems that on my OpenVMS with default DCL command language, the maven version 3 under java and a JVM attempts to place a command which should create a child process just to execute a ls command used to retrieve a file attribute. Most likely the Java code written by the Maven team (or Java code being used in Maven that is actually from plexus-utils or another library) is simply leveraging standard Java file io routines which happen to use the child process to execute ls etc. If there was a better way to get this information, I'd expect it would have been implemented, or perhaps OpenVMS is just not very well supported by the Java platform? Maybe you could dig deep into the code (debug Maven, plexus, and the jdk itself in Netbeans or something), find where this child process thing is coming from, and offer up a patch to the appropriate party? I call it a style break, we should not do it from Java and not assume Unix or the like shells avail, or we are at risk that over time fewer system will support what maven attempts to do. This has very little to do with Maven, and is primarily the fault of the JDK on OpenVMS. I would assume that a better approach to finding the file attributes is available, but no one cares enough about OpenVMS to implement it or pay for it? You are literally the only person I've seen post questions on this list about OpenVMS (Nabble archives reveal 1 other person has posted about it minimally) so it seems to be a pretty low-use OS, at least as far as Maven is concerned. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: MacPorts Maven
No, ignore Maven 1. /Anders On Thu, Jan 13, 2011 at 17:24, John Patrick nhoj.patr...@gmail.com wrote: Does anyone install maven via macports??? If so you might be interested in some tickets I've just submitted: #27944 - Upgrade maven3 to 3.0.2 #27946 - maven_select (similar to python_select, so you can easly switch between maven2 and maven3) #27947 - maven3 update to use maven_select #27948 - maven2 update to use maven_select Do people still use maven 1.x? Just wondering if I should spend anytime on getting that to the latest version and integrated into maven_select. John - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: tomcat-m-p war dependency
Olivier, Not sure if you are being alerted of comments on the JIRA or not but in case you are not I've commented in more detail there. Thanks for taking a look! -Ryan On Jan 13, 2011 3:33 AM, Olivier Lamy ol...@apache.org wrote: Hello, I have added a comment in the jira issue. It sounds more reasonnable to have a new mojo for this with a more simple syntax which could executed from the cli. Feel free to add an other comment. Thanks, -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy 2011/1/13 Ryan Connolly ryn...@gmail.com: Ok, my patch has been submitted: http://jira.codehaus.org/browse/MTOMCAT-74 Please do take a peek at it. It would be great to see this in 1.2 if at all possible! -Ryan On Tue, Jan 11, 2011 at 5:27 PM, Olivier Lamy ol...@apache.org wrote: Patchs are always welcome :-) 2011/1/11 Ryan Connolly ryn...@gmail.com: Thanks for the reply, Olivier. I'll give your suggestion a try. Would it be worth my time trying to create a patch for this feature or would rather just a feature request in JIRA? Thanks again. -Ryan On Jan 11, 2011 5:09 PM, Olivier Lamy ol...@apache.org wrote: Hello, It's not supported currently (btw it's a good idea). You can use copy goal [1] from dependency plugin to get your artifact and use deploy-only mojo from t-m-p [1] http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-artifacts.html 2011/1/11 Ryan Connolly ryn...@gmail.com: Hi: Does anyone happen to know whether it is possible to configure tomcat:run to deploy a defined war dependency as well as run the current project as a dynamic web app in the embedded container? I've tried setting the addContextWarDependenciestrue/addContextWarDependencies configuration option and have declared a war dependency in the tomcat-m-p but the dependency does not appear to deploy to the embedded container. Has anyone else tried a similar configuration? Any advice would be appreciated. An example of what I thought might work follows: plugin groupIdorg.codehaus.mojo/groupId artifactIdtomcat-maven-plugin/artifactId version1.1/version configuration addContextWarDependenciestrue/addContextWarDependencies /configuration dependencies dependency groupIdcom.mycompany/groupId artifactIdwar-artifactid/artifactId version1.0/version typewar/type /dependency /dependencies /plugin Thanks, -Ryan -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Cobertura and Surefire
On Thu, Jan 13, 2011 at 9:01 AM, Schulze, Stefan (EXTERN: CKC) extern.stefan.schul...@volkswagen.de wrote: Jeff Jensen wrote: Perhaps a different CI job structuring? This has worked well for me at many customers: Have a CI job for only compile and unit tests - this maintains the most important very fast turnaround. Have a second CI job for (longer running) IT tests that only runs with success of the first. Have a third job for coverage, standalone or as part of a full system site gen or using Sonar or other... Sounds nice, but this doesn't meet my requirement, that the tests with coverage-checks (and only one time, not twice) should run, when the developers do mvn test. There is no acceptable solution to this requirement. Many of us would like to not run them twice, and in actuality running them twice is not a problem for things like site gen. However, my thinking is to separate the two runs anyway, as coverage is not needed with each local build. Run mvn test until the tests all pass and the developer thinks there is reasonable coverage, then run mvn cobertura:cobertura and view the results. I think running coverage all the time is not necessary until ready to inspect it, particularly when I know I have a lots of work to do on the story/feature; coverage is irrelevant at the start with full TDD (tests exist, no code exists, compile errors exist) and until I am ready to see the needed additional cases. That's for me; YMMV! :-) We have a quite small difference between coverage-threshold and actual coverage, so I think it's important, that the developers check their coverage during development, so they can react early. What IDE is in use? If Eclipse, consider using eCobertura, a Cobertura Eclipse plugin, to run the tests in Eclipse and visually see the coverage as needed. Another problem to your solution is, that Actually, it is a problem with your environment/practices, not with the solution! ;-) we unfortunately don't use a regular CI-server but a bunch of shellscripts and cron-jobs. So it's not as trivial as with Hudson (Jenkins?) to use this kind of build-pipeline. Looks like it is time to invest a couple of days and set it up! Your work life will be easier and maintenance cheaper.
Using profiles to control execution of a maven build (conditional execution)
I need to modify the maven build for a large project to skip certain steps during typical development builds (i.e. don't build the *-source.jar files). I've searched for conditional execution for maven, but haven't found anything. A dev profile sounds like the intuitive way to do this - but I don't know how intuitive maven is. The docs for profiles show how to set different properties (i.e. database connection parameters) for different profiles. I suppose I could set a property and then test if that property is set in the maven-source-plugin - executions - execution tag. Is this the right way to do conditional execution in maven? What's the right way to do this in maven? Thanks.
Problem Building a JIRA Plugin
Hi, I’m trying to use Maven / Eclipse to build a skeleton Atlassian JIRA plugin and I'm coming up against some errors. The ff. is what I get in the logs: 13/01/11 3:01:09 MST PM: Maven Builder: FULL_BUILD requireFullBuild 13/01/11 3:01:09 MST PM: [WARN] 13/01/11 3:01:09 MST PM: [WARN] Some problems were encountered while building the effective model for com.enabil.jira.plugins:AssignIssueByField:atlassian-plugin:1.0-SNAPSHOT 13/01/11 3:01:09 MST PM: [WARN] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 54, column 21 13/01/11 3:01:09 MST PM: [WARN] 13/01/11 3:01:09 MST PM: [WARN] It is highly recommended to fix these problems because they threaten the stability of your build. 13/01/11 3:01:09 MST PM: [WARN] 13/01/11 3:01:09 MST PM: [WARN] For this reason, future Maven versions might no longer support building such malformed projects. 13/01/11 3:01:09 MST PM: [WARN] 13/01/11 3:01:10 MST PM: [WARN] The POM for javax.transaction:jta:jar:1.0.1b is missing, no dependency information available 13/01/11 3:01:10 MST PM: [WARN] The POM for jndi:jndi:jar:1.2.1 is missing, no dependency information available 13/01/11 3:01:10 MST PM: [WARN] The POM for jta:jta:jar:1.0.1 is missing, no dependency information available 13/01/11 3:01:10 MST PM: Build errors for AssignIssueByField; org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.atlassian.maven.plugins:maven-jira-plugin:3.2.3:copy-bundled-dependencies (default-copy-bundled-dependencies) on project AssignIssueByField: Unable to execute mojo Could someone tell me what the message in line 4 above means? How do I fix the missing dependency problem? And for the last line, since it doesn't look Maven-specific, could someone tell me how to interpret the message? Understanding it will make it easier for me to ask the question from the JIRA forums. Thanks! -- Richard Plana
Re: Using profiles to control execution of a maven build (conditional execution)
You might want to look in the list archives, there was a discussion in which I learned a lot from others on the list about the pros and cons of using profiles versus using separate (nearly identical) POMs. My takeaway was that if one just jumps on profiles as the solution to every conditional situation, the build will grow a second head like a hydra in a bad horror flick and you'll really regret it. The point is that profiles are often an expedient substitute for using Maven correctly. They should always be considered last resort unless you know what you are getting yourself into. In my situation, I wanted to have a whole subtree of sources compiled if they were there, otherwise fetched from Nexus if needed. Profiles work great for that, but I can see exactly where the hydra head fits on the beast now and don't intend on doing anything more with them unless absolutely necessary. $0.02... On Jan 13, 2011, at 5:10 PM, Dean Schulze wrote: I need to modify the maven build for a large project to skip certain steps during typical development builds (i.e. don't build the *-source.jar files). I've searched for conditional execution for maven, but haven't found anything. A dev profile sounds like the intuitive way to do this - but I don't know how intuitive maven is. The docs for profiles show how to set different properties (i.e. database connection parameters) for different profiles. I suppose I could set a property and then test if that property is set in the maven-source-plugin - executions - execution tag. Is this the right way to do conditional execution in maven? What's the right way to do this in maven? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using profiles to control execution of a maven build (conditional execution)
On Jan 13, 2011, at 5:10 PM, Dean Schulze wrote: I need to modify the maven build for a large project to skip certain steps during typical development builds (i.e. don't build the *-source.jar files). I've searched for conditional execution for maven, but haven't found anything. Building the source JARs is not something that happens by default, typically this happens in a release profile that is triggered by the release plugin. Conditional logic is generally frowned upon in Maven whereas layering the functionality you need in profiles that can be activated conditionally is the way to go. A dev profile sounds like the intuitive way to do this - but I don't know how intuitive maven is. The docs for profiles show how to set different properties (i.e. database connection parameters) for different profiles. I suppose I could set a property and then test if that property is set in the maven-source-plugin - executions - execution tag. You can specify plugins in profiles too, which is typically where the maven-source-plugin is configured. Is this the right way to do conditional execution in maven? Profiles that are activated explicitly, with a property, the presence of a specific file. What's the right way to do this in maven? If the source JARs are being created then you need to find out which POM it's in and if it's in a profile that is activated by default, then activating another profile will deactivate that profile which should knock out the source JAR generation. If it's not in a profile then that POM will need to be changed so that it is in a profile so that behaviour can be conditionally activated. Thanks. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt
Code coverage for Invoker pre/post build Groovy scripts
Has anyone done this before? Any tricks or hints? I was hoping to use JaCoCo, but other tool ideas are welcome. Links: http://maven.apache.org/plugins/maven-invoker-plugin/examples/post-build-script.html http://jacoco.org/jacoco/index.html -- View this message in context: http://maven.40175.n5.nabble.com/Code-coverage-for-Invoker-pre-post-build-Groovy-scripts-tp3340603p3340603.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: why does maven use /bin/sh -c ls -1lna /djb3/... just to get a file attribute?
Thanks Laird! I actually looked (very briefly) for this code but I was looking in plexus-utils, not plexus-components, doh. Surely there is a better way to implement this. I need to trace this code around and figure out why its doing this and see if maybe we can use another approach to get the same results, without invoking a child shell to exec ls etc. Wayne On Thu, Jan 13, 2011 at 1:00 PM, Laird Nelson ljnel...@gmail.com wrote: Hi, Wayne; this has nothing to do with the JDK and everything to do with Plexus. http://plexus.codehaus.org/plexus-components/plexus-io/xref/org/codehaus/plexus/components/io/attributes/PlexusIoResourceAttributeUtils.html#255 Best, Laird On Thu, Jan 13, 2011 at 1:51 PM, Wayne Fay wayne...@gmail.com wrote: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-jar-plugin:2.3.1:jar (default-jar) on project svnkit: Error assembling JAR: Failed to read filesystem attributes for: /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlad /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml': Error while executing process. Child creation error: no such file or directory - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] Well, what does it look like when you run with -e or -X? Don't send the full output back to the list -- post it at pastebin.org and send us a link, unless you can chop it down to the bare minimum of info yourself. How can java catch file system attributes better? Why do we use a Unix shell command to create a child prozess (sub-process in openvms) by Java just to catch a file system attribute? You'd have to ask the JDK folks these questions. What JDK are you using, and from what vendor? But it seems that on my OpenVMS with default DCL command language, the maven version 3 under java and a JVM attempts to place a command which should create a child process just to execute a ls command used to retrieve a file attribute. Most likely the Java code written by the Maven team (or Java code being used in Maven that is actually from plexus-utils or another library) is simply leveraging standard Java file io routines which happen to use the child process to execute ls etc. If there was a better way to get this information, I'd expect it would have been implemented, or perhaps OpenVMS is just not very well supported by the Java platform? Maybe you could dig deep into the code (debug Maven, plexus, and the jdk itself in Netbeans or something), find where this child process thing is coming from, and offer up a patch to the appropriate party? I call it a style break, we should not do it from Java and not assume Unix or the like shells avail, or we are at risk that over time fewer system will support what maven attempts to do. This has very little to do with Maven, and is primarily the fault of the JDK on OpenVMS. I would assume that a better approach to finding the file attributes is available, but no one cares enough about OpenVMS to implement it or pay for it? You are literally the only person I've seen post questions on this list about OpenVMS (Nabble archives reveal 1 other person has posted about it minimally) so it seems to be a pretty low-use OS, at least as far as Maven is concerned. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem Building a JIRA Plugin
13/01/11 3:01:09 MST PM: [WARN] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 54, column 21 Honestly, read the error and then take a wild guess what this means, and you are probably correct. (Here's a hint: open the project's pom.xml file and look around line 54 for a plugin/ declaration that uses maven-compiler-plugin -- then look for a version/ node. I'm guessing you won't find one. This is regarded as a problem.) 13/01/11 3:01:10 MST PM: [WARN] The POM for javax.transaction:jta:jar:1.0.1b is missing, no dependency information available 13/01/11 3:01:10 MST PM: [WARN] The POM for jndi:jndi:jar:1.2.1 is missing, no dependency information available 13/01/11 3:01:10 MST PM: [WARN] The POM for jta:jta:jar:1.0.1 is missing, no dependency information available These jars cannot be distributed by Maven Central due to licensing constraints. You will need to manually download and install them using mvn install:install-file. 13/01/11 3:01:10 MST PM: Build errors for AssignIssueByField; org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.atlassian.maven.plugins:maven-jira-plugin:3.2.3:copy-bundled-dependencies (default-copy-bundled-dependencies) on project AssignIssueByField: Unable to execute mojo I am going to guess this mojo failed due to the missing dependencies. If you fix them, this will probably execute ok. But I am not familiar with that mojo so I can't say for sure. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
antlr-3.1.3 depends on antlr-2.7.7.
The antlr-3.1.3 depends on antlr-runtime-3.1.3, which depends on stringtemplate-3.2, and stringtemplate depends on antlr-2.7.7; the dependency scope is all compile. I got two versions of antlr, when I using 'mvn dependency:copy-dependencies'. I'm looking for a way to use only one antlr by using dependencyManagement or other methods. Could you help me? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: antlr-3.1.3 depends on antlr-2.7.7.
http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html#Dependency_Exclusions You would then exclude antlr-2.7.7 as you don't want it. I'm somewhat surprise of this problem though. I would expect that antlr-3.1.3 would have this exclusion in place allready, as it would affect them too (antlr-3.1.3 shouldn't have a indirect dependency to antlr-2.7.7). /Anders On Fri, Jan 14, 2011 at 05:40, Hayarobi Park hayarobip...@gmail.com wrote: The antlr-3.1.3 depends on antlr-runtime-3.1.3, which depends on stringtemplate-3.2, and stringtemplate depends on antlr-2.7.7; the dependency scope is all compile. I got two versions of antlr, when I using 'mvn dependency:copy-dependencies'. I'm looking for a way to use only one antlr by using dependencyManagement or other methods. Could you help me? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using profiles to control execution of a maven build (conditional execution)
Please also understand that having the sources jars for releases is actually very good. Anyone using your artifacts would have great use of them when debugging for example. What is the actual problem? Is it that sources jars exist, or something completely different (the build taking too long?)? /Anders On Thu, Jan 13, 2011 at 23:41, Jason van Zyl ja...@maven.org wrote: On Jan 13, 2011, at 5:10 PM, Dean Schulze wrote: I need to modify the maven build for a large project to skip certain steps during typical development builds (i.e. don't build the *-source.jar files). I've searched for conditional execution for maven, but haven't found anything. Building the source JARs is not something that happens by default, typically this happens in a release profile that is triggered by the release plugin. Conditional logic is generally frowned upon in Maven whereas layering the functionality you need in profiles that can be activated conditionally is the way to go. A dev profile sounds like the intuitive way to do this - but I don't know how intuitive maven is. The docs for profiles show how to set different properties (i.e. database connection parameters) for different profiles. I suppose I could set a property and then test if that property is set in the maven-source-plugin - executions - execution tag. You can specify plugins in profiles too, which is typically where the maven-source-plugin is configured. Is this the right way to do conditional execution in maven? Profiles that are activated explicitly, with a property, the presence of a specific file. What's the right way to do this in maven? If the source JARs are being created then you need to find out which POM it's in and if it's in a profile that is activated by default, then activating another profile will deactivate that profile which should knock out the source JAR generation. If it's not in a profile then that POM will need to be changed so that it is in a profile so that behaviour can be conditionally activated. Thanks. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt
Re: Maven release:perform deploy failed access denied
Hum... no other suggestions ? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3340910.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:perform deploy failed access denied
Go talk to your Nexus admins? /Anders On Fri, Jan 14, 2011 at 08:15, jeb001 jeremy.jar...@gmail.com wrote: Hum... no other suggestions ? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3340910.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: why does maven use /bin/sh -c ls -1lna /djb3/... just to get a file attribute?
I have looked at this code earlier, and it actually forks *2* shells to get file attributes when creating any kind of xAR archive. There is definitely room for improvement here, especially on the posix implementation. The last time I googled this it was not as trivial as one could think. It's quite far down on the list of my priorities, but if anyone makes a patch for this it *will* be reviewed ;) Kristian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
