Re: Class vise dependency exclusion in maven
I'm new to maven. I need to know whether it is possible to exclude a particular class from a dependency. Not in a particularly easy or straight-forward manner, especially not for a beginner. You're better off simply manually adjusting the jar yourself, deploying it to your corporate repo under a different groupId, and depending on that artifact plus using exclusions to get rid of the other one if other dependencies want to use the original unchanged artifact. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Class vise dependency exclusion in maven
Maven operates on the artifact level and usually artifact is a jar file. The only option you have is to package your classes so that you can manipulate them on the same level. Maven assembly plugin can help with that. Regards, Oleg Denis Weerasiri wrote: Hi, I'm new to maven. I need to know whether it is possible to exclude a particular class from a dependency. Regards, Denis Weerasiri. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
project exists in cvs; how to check whether there are updates and then build?
I suspect this is a solved problem, but I can't find an example or description. I am starting to use Maven2. I have a java project that is in cvs. I want to use mvn to check whether there are any change in the cvs repository and, if so, update, and build. I managed to get the scm:bootstrap goal to get a local copy of the project, in the targets directory. Thanks.
maven-site-plugin pre 2.0 not in maven-metadata.xml
We are still using maven 2.0.4 and we depend on maven-site-plugin pre 2.0 (some of the beta). The repository location repo1 /maven2/org/apache/maven/plugins/maven-site-plugin/ contains the beta versions, but the file maven-metadata.xml only references the version 2.0. Should it not reference the other versions as well ? After a download via the maven proxy, the file maven-metada from repo1 was loaded locally and the previous versions (that we have locally) are not found anymore ny maven. Jean-Marc
Regarding different directory structure for web application using Maven2
Hi, Ours is a web application. We have different directory structure and we need to follow it. How to specify this directory in Pom.xml file of Maven2. Immediate help will be appreciated. Rgds Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
Re: Regarding different directory structure for web application using Maven2
To change the location of the src/main/webapp directory take a look at the War plugin [1]. Or did you mean the other basic directories, src/main/java, src/main/test, src/main/resources, src/test/resources? [1] http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#warSourceDirectory Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Fri, Mar 13, 2009 at 8:07 AM, kuncham.sari...@wipro.com wrote: Hi, Ours is a web application. We have different directory structure and we need to follow it. How to specify this directory in Pom.xml file of Maven2. Immediate help will be appreciated. Rgds Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Releasing under 2.0.10 loses interactive mode
http://jira.codehaus.org/browse/MNG-4085 2009/3/12 Mark Hobson markhob...@gmail.com: Hi there, I've just tried to release a project using Maven 2.0.10 and get the following warning: [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance. This can be a problem when deployment requires interactivity due to SVN certificates, etc. I retried under 2.0.9 and it works as expected. I couldn't see this in JIRA, is this a known issue or shall I raise one? Cheers, Mark - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Several questions regarding release-plugin/scm/multi-module
Hi, sorry for starting my newbie-career with a lot of questions... All my steps were taken with Maven 2.0.9, Java 1.6.0_07, Mac OS X 10.5.6 x86. The layout is like this Variant A) testA/ testA/pom.xml testMain/ testMain/pom.xml Variant B) testMain/ testMain/pom.xml testMain/testA/ (via svn:externals) testMain/testA/pom.xml where testMain/pom.xml hast defined testA as submodule (../testA). Now the bunch of questions/oddities: - On mvn release:prepare -Ddry-run=true the POMs are changed and testMain is checked (so no dry-run). - How can I exclude modules from being versioned/tagged? - The scm-element is ignored in the submodule. In either variant testA is not tagged in subversion, in variant B) the externals point to trunk/testA (absolute path) or to tags/testA (relative path, not existent). - Is there a way to call release:prepare on each (sub-)module while updating the changed dependencies? The reasons for using externals 1) tagging a set of modules using testMain's pom just for convenience and 2) refactoring takes place immediately on affected modules. I hope I'm not too confusing. Any help is greatly appreciated. Florian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Several questions regarding release-plugin/scm/multi-module
- On mvn release:prepare -Ddry-run=true the POMs are changed and testMain is checked (so no dry-run). I think that's because you should use -DdryRun=true. Thanks Adam -Original Message- From: Dev at weitling [mailto:d...@weitling.net] Sent: 13 March 2009 10:57 To: users@maven.apache.org Subject: Several questions regarding release-plugin/scm/multi-module Hi, sorry for starting my newbie-career with a lot of questions... All my steps were taken with Maven 2.0.9, Java 1.6.0_07, Mac OS X 10.5.6 x86. The layout is like this Variant A) testA/ testA/pom.xml testMain/ testMain/pom.xml Variant B) testMain/ testMain/pom.xml testMain/testA/ (via svn:externals) testMain/testA/pom.xml where testMain/pom.xml hast defined testA as submodule (../testA). Now the bunch of questions/oddities: - On mvn release:prepare -Ddry-run=true the POMs are changed and testMain is checked (so no dry-run). - How can I exclude modules from being versioned/tagged? - The scm-element is ignored in the submodule. In either variant testA is not tagged in subversion, in variant B) the externals point to trunk/testA (absolute path) or to tags/testA (relative path, not existent). - Is there a way to call release:prepare on each (sub-)module while updating the changed dependencies? The reasons for using externals 1) tagging a set of modules using testMain's pom just for convenience and 2) refactoring takes place immediately on affected modules. I hope I'm not too confusing. Any help is greatly appreciated. Florian - 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: Several questions regarding release-plugin/scm/multi-module
Adam Leggett wrote: I think that's because you should use -DdryRun=true. Thanks, seems I'm becoming old... I'm lucky if the other problems are as easy to solve! Regards, Florian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Several questions regarding release-plugin/scm/multi-module
Adam Leggett wrote: How can I exclude modules from being versioned/tagged You could use a profile where you specify a set of modules you want to activate for the release. Ok, I have to admit, I forgot this option. But what in this scenario: testMain is in version 1.5 testA is in version 1.3 testB is in version 1.2 I make tag-worth changes to testB, so its number should increase as well as the number of testMain as its set. I can't create a profile for any combination. Why not ask for every module if it should be tagged at all? Or detect which modules have changed and tagged to tag their set-parent as well? :-? Florian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-compiler-plugin - where does it take compiler from?
Hello, I've got some questions about maven-compiler-plugin regarding compiler. It seems it is not clarified well on documentation - please help me with those questions as I think they seem important. I would like to be able to know what compiler version is used how to change it in case sources need different version. I know from the (maven-compiler-plugin) documentation that there is some builtin compiler in maven-compiler-plugin? What is the version ? Does it change every time new release of JDK ? How to check what is the current default version of the compiler ? There is often a need to compile sources with a specific version of Java compiler then how can I specify a compiler version ? For example in my case is that I need to use: jdk1.6.0 u12 How can I do it ? Should I install this JDK on my machine or it exist somwhere packaged as an artifact(s) ? This is important as I would like to be sure that all developers will compile sources with correct version of Java compiler and there is always a consistent build. Thank you in advance! Tomasz Junak -- View this message in context: http://www.nabble.com/maven-compiler-plugin---where-does-it-take-compiler-from--tp22495176p22495176.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-compiler-plugin - where does it take compiler from?
It will use the build-in compiler in your JDK you are using to run Maven. So just make sure every developer uses the right JDK version. With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Fri, Mar 13, 2009 at 1:09 PM, tjunak tju...@tlen.pl wrote: Hello, I've got some questions about maven-compiler-plugin regarding compiler. It seems it is not clarified well on documentation - please help me with those questions as I think they seem important. I would like to be able to know what compiler version is used how to change it in case sources need different version. I know from the (maven-compiler-plugin) documentation that there is some builtin compiler in maven-compiler-plugin? What is the version ? Does it change every time new release of JDK ? How to check what is the current default version of the compiler ? There is often a need to compile sources with a specific version of Java compiler then how can I specify a compiler version ? For example in my case is that I need to use: jdk1.6.0 u12 How can I do it ? Should I install this JDK on my machine or it exist somwhere packaged as an artifact(s) ? This is important as I would like to be sure that all developers will compile sources with correct version of Java compiler and there is always a consistent build. Thank you in advance! Tomasz Junak -- View this message in context: http://www.nabble.com/maven-compiler-plugin---where-does-it-take-compiler-from--tp22495176p22495176.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Several questions regarding release-plugin/scm/multi-module
How can I exclude modules from being versioned/tagged You could use a profile where you specify a set of modules you want to activate for the release. -Original Message- From: Dev at weitling [mailto:d...@weitling.net] Sent: 13 March 2009 10:57 To: users@maven.apache.org Subject: Several questions regarding release-plugin/scm/multi-module Hi, sorry for starting my newbie-career with a lot of questions... All my steps were taken with Maven 2.0.9, Java 1.6.0_07, Mac OS X 10.5.6 x86. The layout is like this Variant A) testA/ testA/pom.xml testMain/ testMain/pom.xml Variant B) testMain/ testMain/pom.xml testMain/testA/ (via svn:externals) testMain/testA/pom.xml where testMain/pom.xml hast defined testA as submodule (../testA). Now the bunch of questions/oddities: - On mvn release:prepare -Ddry-run=true the POMs are changed and testMain is checked (so no dry-run). - How can I exclude modules from being versioned/tagged? - The scm-element is ignored in the submodule. In either variant testA is not tagged in subversion, in variant B) the externals point to trunk/testA (absolute path) or to tags/testA (relative path, not existent). - Is there a way to call release:prepare on each (sub-)module while updating the changed dependencies? The reasons for using externals 1) tagging a set of modules using testMain's pom just for convenience and 2) refactoring takes place immediately on affected modules. I hope I'm not too confusing. Any help is greatly appreciated. Florian - 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-compiler-plugin - where does it take compiler from?
2009/3/13 Nick Stolwijk nick.stolw...@gmail.com: It will use the build-in compiler in your JDK you are using to run Maven. So just make sure every developer uses the right JDK version. And if you want to enforce it, use the maven-enforcer-plugin to make sure builds only take place in the correct JDK version: http://maven.apache.org/plugins/maven-enforcer-plugin/ Look for requireJavaVersion in the docs. Ringo - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Several questions regarding release-plugin/scm/multi-module
Hi, Hi, sorry for starting my newbie-career with a lot of questions... All my steps were taken with Maven 2.0.9, Java 1.6.0_07, Mac OS X 10.5.6 x86. The layout is like this Variant A) testA/ testA/pom.xml testMain/ testMain/pom.xml Variant B) testMain/ testMain/pom.xml testMain/testA/ (via svn:externals) testMain/testA/pom.xml where testMain/pom.xml hast defined testA as submodule (../testA). Now the bunch of questions/oddities: - On mvn release:prepare -Ddry-run=true the POMs are changed and testMain is checked (so no dry-run). You got the spelling wrong, it's -DdryRun. See http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html - How can I exclude modules from being versioned/tagged? You don't. You need to group your projects by release cycles - only projects that share a common release cycle should be placed under the same parent (at least that's what I always do). - The scm-element is ignored in the submodule. In either variant testA is not tagged in subversion, in variant B) the externals point to trunk/testA (absolute path) or to tags/testA (relative path, not existent). Since those projects should share the same release cycle , tagging individual sub-projects separately makes no sense (they all share the same version number anyway). Regards, Tobias - Is there a way to call release:prepare on each (sub-)module while updating the changed dependencies? The reasons for using externals 1) tagging a set of modules using testMain's pom just for convenience and 2) refactoring takes place immediately on affected modules. I hope I'm not too confusing. Any help is greatly appreciated. Florian - 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: Several questions regarding release-plugin/scm/multi-module
Tobias Gierke wrote: You got the spelling wrong, it's -DdryRun. See http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html Thanks, got it. - How can I exclude modules from being versioned/tagged? You don't. You need to group your projects by release cycles - only projects that share a common release cycle should be placed under the same parent (at least that's what I always do). - The scm-element is ignored in the submodule. In either variant testA is not tagged in subversion, in variant B) the externals point to trunk/testA (absolute path) or to tags/testA (relative path, not existent). Since those projects should share the same release cycle , tagging individual sub-projects separately makes no sense (they all share the same version number anyway) Afaik, that's not correct (rather bold for a newbie, isn't he ;-) The sub-projects only share the same version number if you set autoVersionSubmodules=true. Btw, keeping things modular means that modules may be used in several projects. It's important for our business to keep the different module-sets versioned, so if one module is tagged/versioned the whole set is tagged. It doesn't make sense to me to tag every module when changing only one because it implies that every module has been changed. Sorry for the project/module naming mess. Regards, Florian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: first use of Maven -- how to check cvs repository and build when something has changed
Thanks for the pointer. I'll read the continuum docs and join that list if necessary. On Thu, Mar 12, 2009 at 10:47 PM, Wendy Smoak wsm...@gmail.com wrote: On Thu, Mar 12, 2009 at 8:30 PM, Chris Stoughton chris.stough...@gmail.com wrote: I have continuum installed, but I need to install a Maven2 build. 1. Does continuum detect that there is a change in cvs? 2. Given that there is a change, what phase of maven does the cvs checkout? Probably best to come join us on us...@continuum then, instead of the maven list. :) Generally you add the project to the CI server, and it does the initial checkout. Then periodically it wakes up and updates the checkout. If there are changes, it builds. If not, it waits for the next scheduled build time. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Central repository for snapshots?
Hello all, I am trying to compile the latest trunk version of maven-archetype, which uses maven-parent-11-SNAPSHOT. Of course, this maven-parent-11-SNAPSHOT does not exist in the central repository because it is a SNAPSHOT, and therefore the build fails. Is there a repository I can put in my settings.xml that contains this and other necessary artifacts to build maven-archetype? Thanks. -- Jason Voegele Snow Day -- stay home. signature.asc Description: This is a digitally signed message part.
Re: Central repository for snapshots?
Hi Jason, you should add: http://repository.apache.org/snapshots/ There lives the snapshots from the apache projects. HTH, Marco Jason Voegele wrote: Hello all, I am trying to compile the latest trunk version of maven-archetype, which uses maven-parent-11-SNAPSHOT. Of course, this maven-parent-11-SNAPSHOT does not exist in the central repository because it is a SNAPSHOT, and therefore the build fails. Is there a repository I can put in my settings.xml that contains this and other necessary artifacts to build maven-archetype? Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Central repository for snapshots?
On Friday 13 March 2009 10:15:42 am Marco Huber wrote: Hi Jason, you should add: http://repository.apache.org/snapshots/ There lives the snapshots from the apache projects. Thank you, Marco. Works like a charm. -- Jason Voegele When the going gets tough, the tough get empirical. -- Jon Carroll signature.asc Description: This is a digitally signed message part.
Re: Several questions regarding release-plugin/scm/multi-module
Hi, You don't. You need to group your projects by release cycles - only projects that share a common release cycle should be placed under the same parent (at least that's what I always do). - The scm-element is ignored in the submodule. In either variant testA is not tagged in subversion, in variant B) the externals point to trunk/testA (absolute path) or to tags/testA (relative path, not existent). Since those projects should share the same release cycle , tagging individual sub-projects separately makes no sense (they all share the same version number anyway) Afaik, that's not correct (rather bold for a newbie, isn't he ;-) The sub-projects only share the same version number if you set autoVersionSubmodules=true. My statement was made under the assumption the release plugin is unable to correctly increment version numbers of sub-projects that use a version number other than that of the parent. At least last year I was unable to get such a setup to work *unless* I used the parent project's version number in all sub-projects as well. Quite some time has passed and if I remember correctly, I used property expressions to propagate version numbers, so maybe my problem was caused by those and not related to the actual numbers being different. Personally, I've never used module sets to create a release from. I think the Maven Way is to create a meta-project (applicationserver , webserver etc.) and make this meta-project depend on the actual artifacts. Then you use the assembly-plugin ( or dependency plugin) to actually gather the different artifacts and combine them into a single archive/directory/whatever. But I'm not claiming to be a Maven expert - maybe it's me that got it wrong ;) Regards, Tobias Btw, keeping things modular means that modules may be used in several projects. It's important for our business to keep the different module-sets versioned, so if one module is tagged/versioned the whole set is tagged. It doesn't make sense to me to tag every module when changing only one because it implies that every module has been changed. Sorry for the project/module naming mess. Regards, Florian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Problem with the BuildNumber plugin
I've been trying to get my project to build using Hudson running as a
Window service but I keep getting an authorization failed when my
BuildNumber plugin tries to perform an svn update. Could someone tell
my why this is happening? Below is a snippet from the output generated
by running Maven with the -X switch.
[DEBUG] Configuring mojo
'org.codehaus.mojo:maven-buildnumber-plugin:0.9.4:create' --
[DEBUG] (s) basedir =
C:\developer\hudson\jobs\PACBridge\workspace\fine\utilities
[DEBUG] (s) doCheck = false
[DEBUG] (s) doUpdate = true
[DEBUG] (f) project = MavenProject: fine:utilities:5.0.0 @
C:\developer\hudson\jobs\PACBridge\workspace\fine\utilities\pom.xml
[DEBUG] (s) urlScm =
scm:svn:http://elmer/svn/umsrepo/trunk/fine/utilities
[DEBUG] -- end configuration --
[INFO] [buildnumber:create {execution: default}]
[INFO] Executing: svn --non-interactive update
[INFO] Working directory:
C:\developer\hudson\jobs\PACBridge\workspace\fine\utilities
Provider message:
The svn command failed.
Command output:
svn: OPTIONS of 'http://elmer/svn/umsrepo/trunk/fine/utilities':
authorization failed (http://elmer)
[HUDSON] Archiving
C:\developer\hudson\jobs\PACBridge\workspace\fine\utilities\pom.xml to
c:\developer\hudson\jobs\PACBridge\modules\fine$utilities\builds\2009-03
-13_09-46-35\archive\fine\utilities\5.0.0\pom.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Couldn't update project.
Embedded error: Error!
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Couldn't update
project.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:142)
at
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(Lifecycl
eExecutorInterceptor.java:65)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:158)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:162)
at
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:5
79)
at
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:5
25)
at hudson.remoting.UserRequest.perform(UserRequest.java:92)
at hudson.remoting.UserRequest.perform(UserRequest.java:46)
at hudson.remoting.Request$2.run(Request.java:236)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecuto
r.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.ja
va:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.maven.plugin.MojoExecutionException: Couldn't
update project.
at
org.codehaus.mojo.buildNumber.BuildNumberMojo.update(BuildNumberMojo.jav
a:374)
at
org.codehaus.mojo.buildNumber.BuildNumberMojo.execute(BuildNumberMojo.ja
va:295)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:451)
at
hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInt
erceptor.java:182)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:558)
... 28 more
Caused by: org.apache.maven.scm.ScmException: Error!
at
Re: Problem with the BuildNumber plugin
you may have to run your hudson under a known admin account. not the
default system account
On Fri, Mar 13, 2009 at 9:08 AM, Dave Rathnow dave.rath...@zedi.ca wrote:
I've been trying to get my project to build using Hudson running as a
Window service but I keep getting an authorization failed when my
BuildNumber plugin tries to perform an svn update. Could someone tell
my why this is happening? Below is a snippet from the output generated
by running Maven with the -X switch.
[DEBUG] Configuring mojo
'org.codehaus.mojo:maven-buildnumber-plugin:0.9.4:create' --
[DEBUG] (s) basedir =
C:\developer\hudson\jobs\PACBridge\workspace\fine\utilities
[DEBUG] (s) doCheck = false
[DEBUG] (s) doUpdate = true
[DEBUG] (f) project = MavenProject: fine:utilities:5.0.0 @
C:\developer\hudson\jobs\PACBridge\workspace\fine\utilities\pom.xml
[DEBUG] (s) urlScm =
scm:svn:http://elmer/svn/umsrepo/trunk/fine/utilities
[DEBUG] -- end configuration --
[INFO] [buildnumber:create {execution: default}]
[INFO] Executing: svn --non-interactive update
[INFO] Working directory:
C:\developer\hudson\jobs\PACBridge\workspace\fine\utilities
Provider message:
The svn command failed.
Command output:
svn: OPTIONS of 'http://elmer/svn/umsrepo/trunk/fine/utilities':
authorization failed (http://elmer)
[HUDSON] Archiving
C:\developer\hudson\jobs\PACBridge\workspace\fine\utilities\pom.xml to
c:\developer\hudson\jobs\PACBridge\modules\fine$utilities\builds\2009-03
-13_09-46-35\archive\fine\utilities\5.0.0\pom.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Couldn't update project.
Embedded error: Error!
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Couldn't update
project.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:142)
at
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(Lifecycl
eExecutorInterceptor.java:65)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:158)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:162)
at
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:5
79)
at
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:5
25)
at hudson.remoting.UserRequest.perform(UserRequest.java:92)
at hudson.remoting.UserRequest.perform(UserRequest.java:46)
at hudson.remoting.Request$2.run(Request.java:236)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecuto
r.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.ja
va:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.maven.plugin.MojoExecutionException: Couldn't
update project.
at
org.codehaus.mojo.buildNumber.BuildNumberMojo.update(BuildNumberMojo.jav
a:374)
at
org.codehaus.mojo.buildNumber.BuildNumberMojo.execute(BuildNumberMojo.ja
va:295)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:451)
at
hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInt
erceptor.java:182)
at
Profile with non existing property
We could activate a profile if a property exist or if this property exist and it's value match some string. http://maven.apache.org/guides/introduction/introduction-to-profiles.html But could we activave a profile if a property doesn't exist ? Regards - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
changelog plugin SVN issue
Hi,
I added the ChangeLog Plugin in Maven2. But I get the following error:
[INFO] Executing: svn --non-interactive log -v -r {2009-02-11 16:57:46
+}:{
2009-03-14 16:57:46 +} https://my-co-srvr/ABC_tools/ABC-tool
s-src/ABC-maven/jarred-test-wsdls
[INFO] Working directory:
C:\ABC_tools\ABC-tools-src\ABC-maven\trunk\jarred-test
-wsdls
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn:
'/ABC_tools/!svn/bc/39/ABC-tools-src/ABC-maven/jarred-test-wsdls' p
ath not found
This is because the correct paths need to be svn --non-interactive log -v
-r {2009-02-11 16:57:46 +}:{
2009-03-14 16:57:46 +} https://my-co-srvr/ABC_tools/ABC-tool
s-src/ABC-maven/trunk/jarred-test-wsdls
How can I pass the branch name as trunk ? My POM.xml looks like this:
scm
connection
scm:svn:https://my-co-srvr/ABC_tools/ABC-tools-src/ABC-maven
/connection
developerConnection
scm:svn:https://my-co-srvr/atx_tools/ABC-tools-src/ABC-maven/trunk
/developerConnection
tagHEAD/tag
urlhttps://my-co-srvr/ABC_tools/ABC-tools-src/ABC-maven/url
/scm
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-svnexe/artifactId
version1.1/version
/dependency
/dependencies
properties
maven-scm.version1.0-beta-4/maven-scm.version
/properties
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changelog-plugin/artifactId
configuration
/configuration
/plugin
--
View this message in context:
http://www.nabble.com/changelog-plugin-SVN-issue-tp22500898p22500898.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven adding wrong jar files in war lib
The jar file listed on mvn dependency:tree and jar files inside the war file are different. If I create an empty project and use the pom file the maven packages the correct jar files, otherwise it adds about 7 extra jar files which makes my webapp fail when I deploy it in jboss. But if I copy the correct jar files created by the empty project with the original pom file, everything works fine in jboss. I am using hibernate, spring, and jaxb. The jar files added by maven during package phase are asm, asm-attrs, xml-apis, .. Is there a way to make maven stop adding extra jar files? Thanks, Let me know if I need to attach pom file -- View this message in context: http://www.nabble.com/maven-adding-wrong-jar-files-in-war-lib-tp22500900p22500900.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: Is there a way to exclude a source root in the compiler plugin ?
On Fri, Mar 13, 2009 at 10:24 AM, Balasubramanian, Ravi Shankar rbala...@informatica.com wrote: I want to know if there is a way to exclude a source root when the compiler plugin executes. Ravi, you sent this exact same email 16hrs ago. This is very poor manners on a mailing list. If and when someone can answer your question, they will do so. No one is getting paid to be here. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
cobertura 1.9.1 in the maven plugin?
How can I use the new 1.9.1 version of Cobertura in Maven? --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Twitter: http://twitter.com/mickknutson Vacation Rental: http://tahoe.baselogic.com ---
Cobertua error when running site on DBUnit Test
*When I run mvn site -e -X I get the following error that Cobertura can not find a class which exists in two places* *[myproject] DEBUG [main] Ejb3Configuration.configure(158) | Creating Factory: ApplicationEntityManager* *[INFO] * *[ERROR] FATAL ERROR* *[INFO] * *[INFO] [PersistenceUnit: ApplicationEntityManager] class or package not found* *com.baselogic.domain.IdentifiedObject* *[INFO] * *[DEBUG] Trace* *javax.persistence.PersistenceException: [PersistenceUnit: ApplicationEntityManager] class or package not found* *at org.hibernate.ejb.Ejb3Configuration.addNamedAnnotatedClasses(Ejb3Configuration.java:1093) * *at org.hibernate.ejb.Ejb3Configuration.addClassesToSessionFactory(Ejb3Configuration.java:871) * *at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:758)* *at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:191)* *at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:253)* *at org.codehaus.mojo.hibernate3.configuration.JPAComponentConfiguration.createConfiguration(JPAComponentConfiguration.java:28) * *at org.codehaus.mojo.hibernate3.configuration.AbstractComponentConfiguration.getConfiguration(AbstractComponentConfiguration.java:51) * *at org.codehaus.mojo.hibernate3.exporter.Hbm2DDLExporterMojo.doExecute(Hbm2DDLExporterMojo.java:87) * *at org.codehaus.mojo.hibernate3.HibernateExporterMojo.execute(HibernateExporterMojo.java:152) * *at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:925) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:768) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:550) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) * *at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) * *at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)* *at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)* *at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)* *at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)* *at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) * *at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) * *at java.lang.reflect.Method.invoke(Method.java:597)* *at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)* *at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)* *at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)* *at org.codehaus.classworlds.Launcher.main(Launcher.java:375)* *Caused by: java.lang.ClassNotFoundException: com.baselogic.domain.IdentifiedObject* Now this object lives in two places when I run site: 1. *C:\opt\projects\grd\trunk\data-services\target\classes \com\baselogic\domain\IdentifiedObject.class* 2. *C:\opt\projects\grd\trunk\data-services\ target\generated-classes\cobertura \com\baselogic\domain\IdentifiedObject.class* Here is my plugin: * plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId configuration instrumentation /instrumentation /configuration executions execution goals goalclean/goal /goals /execution /executions dependencies dependency groupIdnet.sourceforge.cobertura/groupId artifactIdcobertura/artifactId version1.9rc1/version /dependency /dependencies
Is there a mavenized library for copying files?
I am writing a plugin which needs to copy files. Since the File.rename() command can fail if source and target are on different drives, and since I don't want to write my own byte mover loop, I wonder whether there is an out-of-the-box file copy / file move library that I can just call?
RE: Is there a mavenized library for copying files?
Look at the maven-dependency-plugin -Original Message- From: Markus KARG [mailto:markus.k...@gmx.net] Sent: Friday, March 13, 2009 3:06 PM To: 'Maven Users List' Subject: Is there a mavenized library for copying files? I am writing a plugin which needs to copy files. Since the File.rename() command can fail if source and target are on different drives, and since I don't want to write my own byte mover loop, I wonder whether there is an out-of-the-box file copy / file move library that I can just call? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Is there a mavenized library for copying files?
Markus KARG wrote: I am writing a plugin which needs to copy files. Since the File.rename() command can fail if source and target are on different drives, and since I don't want to write my own byte mover loop, I wonder whether there is an out-of-the-box file copy / file move library that I can just call? Try FileUtils.moveFile from the apache commons-io library (version 1.4). It's not 'mavenized' but I think it will do the trick. Regards, Mihailo - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven adding wrong jar files in war lib
I can use mvn dependency:copy-dependencies -DincludeScope=compile
(http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html)
to get the correct jar files that I want, but I don't know how to delete the
jar files from the war file and replace it with the ones generated by the
above command.
shouldn't the plugin below produce the same output as the output generated
by command above??
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idcopy-dependencies/id
phasepackage/phase
goals
goalcopy-dependencies/goal
/goals
configuration
outputDirectory${project.build.directory}/alternateLocation/outputDirectory
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotstrue/overWriteSnapshots
includeScopecompile/includeScope
/configuration
/execution
/executions
/plugin
--
View this message in context:
http://www.nabble.com/maven-adding-wrong-jar-files-in-war-lib-tp22500900p22501463.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: changelog plugin SVN issue
Any ideas anyone ? The code is under trunk. How/Where can I change the path
for Maven to look at the correct path ?
Thanks,
huser wrote:
Hi,
I added the ChangeLog Plugin in Maven2. But I get the following error:
[INFO] Executing: svn --non-interactive log -v -r {2009-02-11 16:57:46
+}:{
2009-03-14 16:57:46 +} https://my-co-srvr/ABC_tools/ABC-tool
s-src/ABC-maven/jarred-test-wsdls
[INFO] Working directory:
C:\ABC_tools\ABC-tools-src\ABC-maven\trunk\jarred-test
-wsdls
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn:
'/ABC_tools/!svn/bc/39/ABC-tools-src/ABC-maven/jarred-test-wsdls' p
ath not found
This is because the correct paths need to be svn --non-interactive log -v
-r {2009-02-11 16:57:46 +}:{
2009-03-14 16:57:46 +} https://my-co-srvr/ABC_tools/ABC-tool
s-src/ABC-maven/trunk/jarred-test-wsdls
How can I pass the branch name as trunk ? My POM.xml looks like this:
scm
connection
scm:svn:https://my-co-srvr/ABC_tools/ABC-tools-src/ABC-maven
/connection
developerConnection
scm:svn:https://my-co-srvr/atx_tools/ABC-tools-src/ABC-maven/trunk
/developerConnection
tagHEAD/tag
urlhttps://my-co-srvr/ABC_tools/ABC-tools-src/ABC-maven/url
/scm
dependency
groupIdorg.apache.maven.scm/groupId
artifactIdmaven-scm-provider-svnexe/artifactId
version1.1/version
/dependency
/dependencies
properties
maven-scm.version1.0-beta-4/maven-scm.version
/properties
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changelog-plugin/artifactId
configuration
/configuration
/plugin
--
View this message in context:
http://www.nabble.com/changelog-plugin-SVN-issue-tp22500898p22501667.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
Problem in release:prepare
Hi, I am trying to push a release of Apache RAT to the Nexus staging repository, following the instructions from http://maven.apache.org/developers/release/releasing.html The first steps, up and including release:clean are working well. However, when I finally run release:prepare, then I receive the following error message. Any ideas what might be wrong? (Btw, Maven version is 2.0.10) Thanks, Jochen [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /home/jwi/workspace/apache-rat-project svn --non-interactive commit --file /tmp/maven-scm-1143199004.commit --targets /tmp/maven-scm-1258219989504464972-targets [INFO] Working directory: /home/jwi/workspace/apache-rat-project [INFO] Tagging release with the label apache-rat-project-0.6... [INFO] Executing: /bin/sh -c cd /home/jwi/workspace/apache-rat-project svn --non-interactive copy --file /tmp/maven-scm-697373102.commit . https://svn.apache.org/repos/asf/incubator/rat/main/tags/apache-rat-project-0.6 [INFO] Working directory: /home/jwi/workspace/apache-rat-project [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: File '/repos/asf/incubator/rat/main/tags/apache-rat-project-0.6/apache-rat/pom.xml' already exists -- I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone. -- (Bjarne Stroustrup, http://www.research.att.com/~bs/bs_faq.html#really-say-that My guess: Nokia E50) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Problem in release:prepare
This looks like http://jira.codehaus.org/browse/SCM-406. Run svn up and rerun release:prepare. -Original Message- From: Jochen Wiedmann [mailto:jochen.wiedm...@gmail.com] Sent: Friday, March 13, 2009 6:40 PM To: Maven Users List Subject: Problem in release:prepare Hi, I am trying to push a release of Apache RAT to the Nexus staging repository, following the instructions from http://maven.apache.org/developers/release/releasing.html The first steps, up and including release:clean are working well. However, when I finally run release:prepare, then I receive the following error message. Any ideas what might be wrong? (Btw, Maven version is 2.0.10) Thanks, Jochen [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /home/jwi/workspace/apache-rat-project svn --non-interactive commit --file /tmp/maven-scm-1143199004.commit --targets /tmp/maven-scm-1258219989504464972-targets [INFO] Working directory: /home/jwi/workspace/apache-rat-project [INFO] Tagging release with the label apache-rat-project-0.6... [INFO] Executing: /bin/sh -c cd /home/jwi/workspace/apache-rat-project svn --non-interactive copy --file /tmp/maven-scm-697373102.commit . https://svn.apache.org/repos/asf/incubator/rat/main/tags/apache-rat-proj ect-0.6 [INFO] Working directory: /home/jwi/workspace/apache-rat-project [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: File '/repos/asf/incubator/rat/main/tags/apache-rat-project-0.6/apache-rat/po m.xml' already exists -- I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone. -- (Bjarne Stroustrup, http://www.research.att.com/~bs/bs_faq.html#really-say-that My guess: Nokia E50) - 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 in release:prepare
it's a bug with subversion 1.5.1+ when using the neon transport against http or https repositories if you use svn 1.4 you are fine if you recompile your svn binaries to use the other transport for http / https you should be fine too and the solution is just to run svn update and then mvn release:prepare release:perform will continue where it left off Sent from my [rhymes with myPod] ;-) On 13 Mar 2009, at 22:43, Edelson, Justin justin.edel...@mtvstaff.com wrote: This looks like http://jira.codehaus.org/browse/SCM-406. Run svn up and rerun release:prepare. -Original Message- From: Jochen Wiedmann [mailto:jochen.wiedm...@gmail.com] Sent: Friday, March 13, 2009 6:40 PM To: Maven Users List Subject: Problem in release:prepare Hi, I am trying to push a release of Apache RAT to the Nexus staging repository, following the instructions from http://maven.apache.org/developers/release/releasing.html The first steps, up and including release:clean are working well. However, when I finally run release:prepare, then I receive the following error message. Any ideas what might be wrong? (Btw, Maven version is 2.0.10) Thanks, Jochen [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /home/jwi/workspace/apache-rat-project svn --non-interactive commit --file /tmp/maven-scm-1143199004.commit --targets /tmp/maven-scm-1258219989504464972-targets [INFO] Working directory: /home/jwi/workspace/apache-rat-project [INFO] Tagging release with the label apache-rat-project-0.6... [INFO] Executing: /bin/sh -c cd /home/jwi/workspace/apache-rat-project svn --non-interactive copy --file /tmp/maven-scm-697373102.commit . https://svn.apache.org/repos/asf/incubator/rat/main/tags/apache-rat-proj ect-0.6 [INFO] Working directory: /home/jwi/workspace/apache-rat-project [INFO] --- - [ERROR] BUILD FAILURE [INFO] --- - [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: File '/repos/asf/incubator/rat/main/tags/apache-rat-project-0.6/apache- rat/po m.xml' already exists -- I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone. -- (Bjarne Stroustrup, http://www.research.att.com/~bs/bs_faq.html#really-say-that My guess: Nokia E50) - 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: project.build.directory not set properly for ant
Hello,
I did not hear from anyone regarding this so assumed no one has seen it. I
went ahead and opened a bug for it a couple of days ago:
http://jira.codehaus.org/browse/MNG-4083
It occurred to me that I should post this to the list in case someone searches
and sees this problem, they will know what happened with it. Sorry for the
noise.
-Jim
-Original Message-
From: Jim McCaskey [mailto:jim.mccas...@pervasive.com]
Sent: Tuesday, March 10, 2009 12:53 PM
To: 'users@maven.apache.org'
Subject: project.build.directory not set properly for ant
Hello,
We are currently using Maven 2.0.7 and I am working on upgrading us to Maven
2.0.10. I ran into a problem which I think is in maven-antrun-plugin, but
can't be sure.
I do not think it is interpreting ${project.build.directory} properly. In a lot
of our POM's we override the output directories to shovel stuff out of the
source directory. I stripped down a pom to show the problem below. Where I
have the ant echo's below, we would typically do other things, but those
things are breaking because the ${project.build.directory} is incorrectly set.
As you can see from my test output below, 2.0.7 and 2.0.8 work fine, but
starting with 2.0.9 and carried over to 2.0.10 things don't work so well. It
looks like it is prepending ${basedir} even though we don't want that.
I should also note that the output is going where I expect. In other words all
the .class and .jar files are being pushed out to the E:\obj directory as my
pom specifies. It's just within ant that the values don't seem correct.
I tried searching Jira for any problems like this, and found some that are
around this area. This one for example seems to have some similarity, but not
exactly (and it's resolution seems to be in the Maven 2.1 code):
http://jira.codehaus.org/browse/MNG-3475
A work around is obviously just to hand roll the paths we need, but I wanted to
see if this change in behavior was intentional. Am I doing something wrong or
should I just open a bug for this?
-Jim
Test POM:
?xml version=1.0 encoding=UTF-8?
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
groupIdtest/groupId
artifactIdtest/artifactId
packagingjar/packaging
version1.0.0/version
nameFoo/name
properties
djobjE:\obj/djobj
/properties
build
defaultGoalpackage/defaultGoal
outputDirectory${djobj}/${project.artifactId}/classes/outputDirectory
testOutputDirectory${djobj}/${project.artifactId}/test-classes/testOutputDirectory
directory${djobj}/${project.artifactId}/directory
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasepackage/phase
configuration
tasks
echo message=Debug data/
echo message=basedir =
${basedir}/
echo message=djobj = ${djobj}/
echo message=project.build.sourceDirectory =
${project.build.sourceDirectory}/
echo message=project.build.scriptSourceDirectory =
${project.build.scriptSourceDirectory}/
echo message=project.build.testSourceDirectory =
${project.build.testSourceDirectory}/
echo message=project.build.outputDirectory =
${project.build.outputDirectory}/
echo message=project.build.testOutputDirectory =
${project.build.testOutputDirectory}/
echo message=project.build.directory =
${project.build.directory}/
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
/build
/project
Test output:
Maven 2.0.7
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] Debug data
[echo] basedir = E:\foo
[echo] djobj = E:\obj
[echo] project.build.sourceDirectory = E:\foo\src\main\java
[echo] project.build.scriptSourceDirectory = src/main/scripts
[echo] project.build.testSourceDirectory = E:\foo\src\test\java
[echo] project.build.outputDirectory = E:\obj/test/classes
[echo] project.build.testOutputDirectory = E:\obj/test/test-classes
[echo] project.build.directory = E:\obj/test
[INFO] Executed tasks
Maven 2.0.8
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[echo] Debug data
[echo] basedir = E:\foo
[echo] djobj = E:\obj
[echo] project.build.sourceDirectory = E:\foo\src\main\java
[echo] project.build.scriptSourceDirectory = src/main/scripts
RE: Is there a mavenized library for copying files?
Sorry I misunderstood the question. Plexus-utils has a fileUtils.move (or something similar, don't have the source in front of me) -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: Friday, March 13, 2009 4:05 PM To: Maven Users List Subject: RE: Is there a mavenized library for copying files? Look at the maven-dependency-plugin -Original Message- From: Markus KARG [mailto:markus.k...@gmx.net] Sent: Friday, March 13, 2009 3:06 PM To: 'Maven Users List' Subject: Is there a mavenized library for copying files? I am writing a plugin which needs to copy files. Since the File.rename() command can fail if source and target are on different drives, and since I don't want to write my own byte mover loop, I wonder whether there is an out-of-the-box file copy / file move library that I can just call? - 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
Newbie Question: Dependencies among Sibling Projects?
I have a software project that is roughly organized like this: master (aggregation project) librarya libraryb (depends on librarya) It seems that I need to install librarya before libraryb will compile. Is there any way to define dependencies among sibling projects like this (that are part of the same aggregation group) so that they do not need to be individually installed (preferably not installed at all) and Maven can auto-detect dependencies and properly build/rebuild? Also, during development, I do not update the version tag during every single build/debug cycle. Will Maven properly detect source changes, rebuild necessary libraries, and update the local repository? -- View this message in context: http://n2.nabble.com/Newbie-Question%3A-Dependencies-among-Sibling-Projects--tp2477109p2477109.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: Newbie Question: Dependencies among Sibling Projects?
It seems that I need to install librarya before libraryb will compile. This is correct. Unless you are running mvn compile from the top parent/aggregation pom. Is there any way to define dependencies among sibling projects like this (that are part of the same aggregation group) so that they do not need to be individually installed (preferably not installed at all) and Maven can auto-detect dependencies and properly build/rebuild? Yes, if you run compile from the top parent. Also, during development, I do not update the version tag during every single build/debug cycle. Will Maven properly detect source changes, rebuild necessary libraries, and update the local repository? Yes, but make sure you are using x.y.z-SNAPSHOT until you ready to freeze a version number. In the Maven world (and its a good policy in general), there is only ONE true artifact for a given groupId/artifactId/version (GAV) combination. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
