Re: mojo help
On 25/05/2010, at 4:11 PM, Stephen Connolly wrote: Dan Tran is pretty darn familiar with mojo development (#2 on http://www.ohloh.net/p/mojo/contributors) Apologies Dan :) I just wasn't getting it. You should start by copying wagon:download and tweak that from there I'm still wondering why various @parameters weren't being initialised - but thanks. I'll start from there. with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mojo help
On 25/05/2010, at 4:26 PM, Jörg Schaible wrote: Lachlan Deck wrote: I'm not sure I understand your question? My dependencies already contains wagon-maven-plugin which is a very bad idea unless you intend to run in Maven 3 only. Nup. 2.1.0 atm. Due to classloader constraints in M2 you should never use a different plugin as dependency. Ah, right. So the annotations don't work unless those classes are in your plugin project. That's a real bummer. Moving forward... thanks. with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
mojo help
Hi there, I'm trying to get a very simple utility working which downloads a zip file for subsequent use. I can successfully do this via an execution in the pom[1] but can't seem to get it working programatically (which I need to be able to run the mojo independently). In order to create a stand alone utility that could run outside a project (mvn some.groupId:project-id:downloadzip ...) I seem to be missing something. i.e., when I've got the mojo with @requiresProject false the 'settings' and 'wagonManager' in AbstractMojo aren't initialised. Thus when I call createWagon(serverId, url) I get a NullPointerException: org.apache.maven.plugin.MojoExecutionException: Unable to create a Wagon instance for scp://foo.bar.net/ at org.codehaus.mojo.wagon.AbstractWagonMojo.createWagon(AbstractWagonMojo:83) ... Caused by: java.lang.NullPointerException at org.apache.maven.artifact.manager.DefaultWagonManager.getWagon(DefaultWagonManager.java:143) at org.apache.maven.artifact.manager.DefaultWagonManager.getWagon(DefaultWagonManager.java:128) at org.codehaus.mojo.wagon.shared.WagonUtils.createWagon(AbstractWagonMojo:53) at org.codehaus.mojo.wagon.AbstractWagonMojo.createWagon(AbstractWagonMojo:79) ... 21 more Essentially, how do I utilise the scp wagon programatically? - if the mojo is running outside a project, how do @component annotated fields (like Settings or WagonManager) get populated? etc Thanks! with regards, -- Lachlan Deck [1] build ... extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-ssh/artifactId version1.0-beta-6/version /extension /extensions plugins ... plugin groupIdorg.codehaus.mojo/groupId artifactIdwagon-maven-download/artifactId version1.0-beta-3/version executions execution idfoo/id phaseverify/phase goals goaldownload/goal /goals configuration serverIdbar/serverId urlscp://bar.foo.net//url fromDir/some/dir//fromDir includesmyzip.zip/includes toDir/tmp/toDir /configuration /execution /executions /plugin /plugins /build - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mojo help
I'm not sure I understand your question? My dependencies already contains wagon-maven-plugin but what java classes are you particularly referring to in order to make this work programatically (rather than via a pom execution)? i.e., to be clearer: I'm writing a mojo, or trying to, that can execute with @requiresProject false etc On 25/05/2010, at 12:46 PM, Dan Tran wrote: is there any reason, you are not using wagon-maven-plugin at MOJO? -Dan On Mon, May 24, 2010 at 6:54 PM, Lachlan Deck lachlan.d...@gmail.com wrote: Hi there, I'm trying to get a very simple utility working which downloads a zip file for subsequent use. I can successfully do this via an execution in the pom[1] but can't seem to get it working programatically (which I need to be able to run the mojo independently). In order to create a stand alone utility that could run outside a project (mvn some.groupId:project-id:downloadzip ...) I seem to be missing something. i.e., when I've got the mojo with @requiresProject false the 'settings' and 'wagonManager' in AbstractMojo aren't initialised. Thus when I call createWagon(serverId, url) I get a NullPointerException: org.apache.maven.plugin.MojoExecutionException: Unable to create a Wagon instance for scp://foo.bar.net/ at org.codehaus.mojo.wagon.AbstractWagonMojo.createWagon(AbstractWagonMojo:83) ... Caused by: java.lang.NullPointerException at org.apache.maven.artifact.manager.DefaultWagonManager.getWagon(DefaultWagonManager.java:143) at org.apache.maven.artifact.manager.DefaultWagonManager.getWagon(DefaultWagonManager.java:128) at org.codehaus.mojo.wagon.shared.WagonUtils.createWagon(AbstractWagonMojo:53) at org.codehaus.mojo.wagon.AbstractWagonMojo.createWagon(AbstractWagonMojo:79) ... 21 more Essentially, how do I utilise the scp wagon programatically? - if the mojo is running outside a project, how do @component annotated fields (like Settings or WagonManager) get populated? etc Thanks! with regards, -- Lachlan Deck [1] build ... extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-ssh/artifactId version1.0-beta-6/version /extension /extensions plugins ... plugin groupIdorg.codehaus.mojo/groupId artifactIdwagon-maven-download/artifactId version1.0-beta-3/version executions execution idfoo/id phaseverify/phase goals goaldownload/goal /goals configuration serverIdbar/serverId urlscp://bar.foo.net//url fromDir/some/dir//fromDir includesmyzip.zip/includes toDir/tmp/toDir /configuration /execution /executions /plugin /plugins /build - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mojo help
On 25/05/2010, at 1:46 PM, Dan Tran wrote: ah sorry, from wagon-maven-plugin, wagon:download can run outside of maven project Yep - but I don't need that. To reiterate: I'm creating my own mojo which will do something similar to start with but will do other things as well ... so my question remains: how can this be done programatically? i.e., in 'java' not via the pom.xml? -Dan On Mon, May 24, 2010 at 8:28 PM, Lachlan Deck lachlan.d...@gmail.com wrote: I'm not sure I understand your question? My dependencies already contains wagon-maven-plugin but what java classes are you particularly referring to in order to make this work programatically (rather than via a pom execution)? i.e., to be clearer: I'm writing a mojo, or trying to, that can execute with @requiresProject false etc On 25/05/2010, at 12:46 PM, Dan Tran wrote: is there any reason, you are not using wagon-maven-plugin at MOJO? -Dan On Mon, May 24, 2010 at 6:54 PM, Lachlan Deck lachlan.d...@gmail.com wrote: Hi there, I'm trying to get a very simple utility working which downloads a zip file for subsequent use. I can successfully do this via an execution in the pom[1] but can't seem to get it working programatically (which I need to be able to run the mojo independently). In order to create a stand alone utility that could run outside a project (mvn some.groupId:project-id:downloadzip ...) I seem to be missing something. i.e., when I've got the mojo with @requiresProject false the 'settings' and 'wagonManager' in AbstractMojo aren't initialised. Thus when I call createWagon(serverId, url) I get a NullPointerException: org.apache.maven.plugin.MojoExecutionException: Unable to create a Wagon instance for scp://foo.bar.net/ at org.codehaus.mojo.wagon.AbstractWagonMojo.createWagon(AbstractWagonMojo:83) ... Caused by: java.lang.NullPointerException at org.apache.maven.artifact.manager.DefaultWagonManager.getWagon(DefaultWagonManager.java:143) at org.apache.maven.artifact.manager.DefaultWagonManager.getWagon(DefaultWagonManager.java:128) at org.codehaus.mojo.wagon.shared.WagonUtils.createWagon(AbstractWagonMojo:53) at org.codehaus.mojo.wagon.AbstractWagonMojo.createWagon(AbstractWagonMojo:79) ... 21 more Essentially, how do I utilise the scp wagon programatically? - if the mojo is running outside a project, how do @component annotated fields (like Settings or WagonManager) get populated? etc Thanks! with regards, -- Lachlan Deck [1] build ... extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-ssh/artifactId version1.0-beta-6/version /extension /extensions plugins ... plugin groupIdorg.codehaus.mojo/groupId artifactIdwagon-maven-download/artifactId version1.0-beta-3/version executions execution idfoo/id phaseverify/phase goals goaldownload/goal /goals configuration serverIdbar/serverId urlscp://bar.foo.net//url fromDir/some/dir//fromDir includesmyzip.zip/includes toDir/tmp/toDir /configuration /execution /executions /plugin /plugins /build - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mojo help
Anyone more familiar with mojo development able to answer? Or am I on the wrong list? On 25/05/2010, at 2:00 PM, Dan Tran wrote: I would suggest you cut and paste wagon:download code then That doesn't help answer my questions below. On Mon, May 24, 2010 at 6:54 PM, Lachlan Deck lachlan.d...@gmail.com wrote: Hi there, I'm trying to get a very simple utility working which downloads a zip file for subsequent use. I can successfully do this via an execution in the pom[1] but can't seem to get it working programatically (which I need to be able to run the mojo independently). In order to create a stand alone utility that could run outside a project (mvn some.groupId:project-id:downloadzip ...) I seem to be missing something. i.e., when I've got the mojo with @requiresProject false the 'settings' and 'wagonManager' in AbstractMojo aren't initialised. Thus when I call createWagon(serverId, url) I get a NullPointerException: org.apache.maven.plugin.MojoExecutionException: Unable to create a Wagon instance for scp://foo.bar.net/ at org.codehaus.mojo.wagon.AbstractWagonMojo.createWagon(AbstractWagonMojo:83) ... Caused by: java.lang.NullPointerException at org.apache.maven.artifact.manager.DefaultWagonManager.getWagon(DefaultWagonManager.java:143) at org.apache.maven.artifact.manager.DefaultWagonManager.getWagon(DefaultWagonManager.java:128) at org.codehaus.mojo.wagon.shared.WagonUtils.createWagon(AbstractWagonMojo:53) at org.codehaus.mojo.wagon.AbstractWagonMojo.createWagon(AbstractWagonMojo:79) ... 21 more Essentially, how do I utilise the scp wagon programatically? - if the mojo is running outside a project, how do @component annotated fields (like Settings or WagonManager) get populated? etc Thanks! with regards, -- Lachlan Deck [1] build ... extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-ssh/artifactId version1.0-beta-6/version /extension /extensions plugins ... plugin groupIdorg.codehaus.mojo/groupId artifactIdwagon-maven-download/artifactId version1.0-beta-3/version executions execution idfoo/id phaseverify/phase goals goaldownload/goal /goals configuration serverIdbar/serverId urlscp://bar.foo.net//url fromDir/some/dir//fromDir includesmyzip.zip/includes toDir/tmp/toDir /configuration /execution /executions /plugin /plugins /build - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
scope misunderstanding
Hi there, I've got a module libs:Foo that depends on a particular third party library 'Bar' with scope compile. All the other projects / modules in the tree all depend on the base module libs:Foo with scope compile. Easy, all's well. Now, in adding another module libs:Test which depends on junit:junit (compile) and also on 'Bar' (compile) I start getting problems: - apps.Baz depends on 'libs.Foo' (compile) and also on 'libs.Test' (test). - but apps.Baz now fails to compile doing $ mvn clean install - it seems to not know anything about stuff in 'libs.Foo' for the classes under /src/main/java However, if I change the scope of the dependencies within the pom for lib:Test to scopeprovided/scope all's well again. Is this expected behaviour? It seems that the classpath is incomplete somehow... now sure how. $ mvn --version Apache Maven 2.2.1 (r801777; 2009-08-07 05:16:01+1000) Java version: 1.6.0_17 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home Default locale: en_AU, platform encoding: MacRoman OS name: mac os x version: 10.6.2 arch: x86_64 Family: mac Thanks. with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mixing Scala and Java in the same project
On 09/12/2009, at 8:23 PM, Pilgrim, Peter wrote: Hi Has anyone got any guidelines for mixing Scala and Java in the same project? This is what I found when looking at the same thing: http://www.scala-tools.org/mvnsites/maven-scala-plugin/usage_java.html Thanks very much in advance with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mysql connector updates lagging
Excellent - thanks Dennis. Good to see someone's onto it. On 02/10/2009, at 6:51 AM, Dennis Lundberg wrote: There's been some kind of problem with the rsync of mysql artifacts. See http://jira.codehaus.org/browse/MAVENUPLOAD-2598 Lachlan Deck wrote: Hi there, anyone know who's previously been responsible for pushing mysql:mysql-connector-java updates to the central repo? The central repo only has 5.1.6 but mysql's connector is up to 5.1.10 now. with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
mysql connector updates lagging
Hi there, anyone know who's previously been responsible for pushing mysql:mysql- connector-java updates to the central repo? The central repo only has 5.1.6 but mysql's connector is up to 5.1.10 now. with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
jxr-maven-plugin 2.1 missing
Hi there, just tried to run mvn site:run and it seems that jxr-maven-plugin 2.1 is missing from the main repo. I can only find 2.0-beta1 via mvnrepository.com etc. Anyone know why the current release for jxr-maven-plugin is missing from the main repo? with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: jxr-maven-plugin 2.1 missing
Thanks. On 30/09/2009, at 3:26 PM, Brett Porter wrote: Try maven-jxr-plugin (group: org.apache.maven.plugins) - Brett On 30/09/2009, at 3:12 PM, Lachlan Deck wrote: Hi there, just tried to run mvn site:run and it seems that jxr-maven-plugin 2.1 is missing from the main repo. I can only find 2.0-beta1 via mvnrepository.com etc. Anyone know why the current release for jxr-maven-plugin is missing from the main repo? with regards, -- Lachlan Deck - 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 with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: OpenSource Maven Repository
dev.java.net On 19/09/2009, at 7:56 AM, UseTheFork wrote: Hi, Does anyone know if there is an open source maven repository where open source project artifacts can be posted? Thanks, UseTheFork -- View this message in context: http://www.nabble.com/OpenSource-Maven-Repository-tp25516101p25516101.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 with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
hudson + build-number-plugin can't find svn
/var/hudson/jobs/WillowFrameworks/workspace/trunk/ishframeworks): java.io.IOException: error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:459) at java.lang.Runtime.exec(Runtime.java:593) at org.codehaus.plexus.util.cli.Commandline.execute(Commandline.java: 692) ... 37 more Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.init(UNIXProcess.java:148) at java.lang.ProcessImpl.start(ProcessImpl.java:65) at java.lang.ProcessBuilder.start(ProcessBuilder.java:452) ... 39 more with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: hudson + build-number-plugin can't find svn
On 16/07/2009, at 12:21 PM, Mohan KR wrote: I don't have access to the project right now. I remember it is the incompatibility with the svn versions. IIRC Hudson built-in (svn kit) uses 1.5, so when it checks out the sources the metadata is 1.5 compatible. So if your /usr/local/svn is 1.4 then you will get the error. Interesting. Makes sense. Our /usr/local/bin/svn is 1.6.3 though. Any suggestions on what to do? Thanks Thanks, mohan kr -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 8:02 PM To: Maven Users List Subject: hudson + build-number-plugin can't find svn Hi there, We've set up hudson on our build server but are invariably finding that it fails to find the svn executable when building (see below stack trace). We've defined in hudson the environment variable 'svn' as /usr/local/ bin/svn. However this doesn't seem to be working (or not always). Does anyone know of a surefire way of setting this up so that svn is found on the path? Thanks. [INFO] Cannot get the revision information from the scm repository : Exception while executing SCM command. java.io.IOException: error=2, No such file or directory [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 703) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 519) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:332) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org .apache .maven .lifecycle .LifecycleExecutorInterceptor .execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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 hudson.maven.agent.Main.launch(Main.java:165) at hudson.maven.MavenBuilder.call(MavenBuilder.java:159) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:601) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:547) at hudson.remoting.UserRequest.perform(UserRequest.java:103) at hudson.remoting.UserRequest.perform(UserRequest.java:47) at hudson.remoting.Request$2.run(Request.java:236) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java: 441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor $Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:502) at org.codehaus.mojo.build.BuildMojo.execute(BuildMojo.java:377) at org .apache .maven .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java: 483) at hudson .maven .agent .PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java: 182) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 678) ... 28 more Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org .apache .maven.scm.command.AbstractCommand.execute(AbstractCommand.java: 59) at org.codehaus.mojo.build.BuildMojo.info(BuildMojo.java:526) at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:494) ... 32 more Caused by: org.apache.maven.scm.ScmException
Re: hudson + build-number-plugin can't find svn
On 16/07/2009, at 12:21 PM, Mohan KR wrote: I don't have access to the project right now. I remember it is the incompatibility with the svn versions. IIRC Hudson built-in (svn kit) uses 1.5, so when it checks out the sources the metadata is 1.5 compatible. Actually we just checked and it's using svnkit-1.3-hudson. SVNKit1.3 is compatible with svn 1.6 AFAIK. So if your /usr/local/svn is 1.4 then you will get the error. Again our /usr/local/bin/svn is 1.6.3 So any other suggestions? Perhaps it's really not finding it on the path? Can it be configured? Thanks, mohan kr -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 8:02 PM To: Maven Users List Subject: hudson + build-number-plugin can't find svn Hi there, We've set up hudson on our build server but are invariably finding that it fails to find the svn executable when building (see below stack trace). We've defined in hudson the environment variable 'svn' as /usr/local/ bin/svn. However this doesn't seem to be working (or not always). Does anyone know of a surefire way of setting this up so that svn is found on the path? Thanks. [INFO] Cannot get the revision information from the scm repository : Exception while executing SCM command. java.io.IOException: error=2, No such file or directory [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 703) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 519) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:332) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org .apache .maven .lifecycle .LifecycleExecutorInterceptor .execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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 hudson.maven.agent.Main.launch(Main.java:165) at hudson.maven.MavenBuilder.call(MavenBuilder.java:159) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:601) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:547) at hudson.remoting.UserRequest.perform(UserRequest.java:103) at hudson.remoting.UserRequest.perform(UserRequest.java:47) at hudson.remoting.Request$2.run(Request.java:236) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java: 441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor $Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:502) at org.codehaus.mojo.build.BuildMojo.execute(BuildMojo.java:377) at org .apache .maven .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java: 483) at hudson .maven .agent .PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java: 182) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 678) ... 28 more Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org .apache .maven.scm.command.AbstractCommand.execute(AbstractCommand.java: 59) at org.codehaus.mojo.build.BuildMojo.info(BuildMojo.java:526
Re: hudson + build-number-plugin can't find svn
On 16/07/2009, at 1:11 PM, Mohan KR wrote: Sorry, I'm looking at the stack trace, it appears the svn executable is not found. How are you launching Hudson? Make sure the startup script that launches Hudson has /usr/local/bin in its PATH. it was already on the path -- but to be sure we added it again PATH= $PATH:/usr/local/bin. I'm now using the maven-antrun-plugin to print out the env.PATH and sure enough it's there twice - but it seems to work for now :-/ It'll probably fail again tomorrow... we'll see. Cheers. -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 9:54 PM To: Maven Users List Subject: Re: hudson + build-number-plugin can't find svn On 16/07/2009, at 12:21 PM, Mohan KR wrote: I don't have access to the project right now. I remember it is the incompatibility with the svn versions. IIRC Hudson built-in (svn kit) uses 1.5, so when it checks out the sources the metadata is 1.5 compatible. So if your /usr/local/svn is 1.4 then you will get the error. Interesting. Makes sense. Our /usr/local/bin/svn is 1.6.3 though. Any suggestions on what to do? Thanks Thanks, mohan kr -Original Message- From: Lachlan Deck [mailto:lachlan.d...@gmail.com] Sent: Wednesday, July 15, 2009 8:02 PM To: Maven Users List Subject: hudson + build-number-plugin can't find svn Hi there, We've set up hudson on our build server but are invariably finding that it fails to find the svn executable when building (see below stack trace). We've defined in hudson the environment variable 'svn' as /usr/local/ bin/svn. However this doesn't seem to be working (or not always). Does anyone know of a surefire way of setting this up so that svn is found on the path? Thanks. [INFO] Cannot get the revision information from the scm repository : Exception while executing SCM command. java.io.IOException: error=2, No such file or directory [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 703) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 519) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:332) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org .apache .maven .lifecycle .LifecycleExecutorInterceptor .execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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 hudson.maven.agent.Main.launch(Main.java:165) at hudson.maven.MavenBuilder.call(MavenBuilder.java:159) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:601) at hudson.maven.MavenModuleSetBuild $Builder.call(MavenModuleSetBuild.java:547) at hudson.remoting.UserRequest.perform(UserRequest.java:103) at hudson.remoting.UserRequest.perform(UserRequest.java:47) at hudson.remoting.Request$2.run(Request.java:236) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java: 441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor $Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot get the revision information from the scm repository : Exception while executing SCM command. at org.codehaus.mojo.build.BuildMojo.getRevision(BuildMojo.java:502) at org.codehaus.mojo.build.BuildMojo.execute(BuildMojo.java:377
Re: Retrieving current revision from SCM
I've been using this:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
version1.0-beta-1/version
executions
execution
phasevalidate/phase
goals
goalcreate/goal
/goals
/execution
/executions
configuration
doCheckfalse/doCheck
doUpdatefalse/doUpdate
/configuration
/plugin
And in a resource properties file that's filtered:
scm.version=${buildNumber}
On 06/05/2009, at 1:20 AM, Allan Ditzel wrote:
Thanks Olivier!
That _almost_ does it. If I don't specify format and items then
I see
the correct revision printed on screen when the module builds. But I
can't
seem to find the right format and items to read the buildNumber in
the file.
Here is what I have in my configuration block for the plugin:
format{0,number}/format
itemsitembuildNumber/item/items
And the file output is:
#maven.buildNumber.plugin properties file
#Tue May 05 11:16:55 EDT 2009
buildNumber=1
I know I have to be missing something rather simple here. Any
thoughts?
Thanks again!
Allan
On Tue, May 5, 2009 at 10:24 AM, Olivier Lamy ol...@apache.org
wrote:
Hi,
Have a look here : http://mojo.codehaus.org/buildnumber-maven-plugin/
HTH,
--
Olivier
2009/5/5 Allan Ditzel allan.dit...@gmail.com:
Hi all,
I'm trying to do the following:
We're using subversion and we need to extract the revision number
of the
working copy and put that in a properties file. Is there an existing
plugin
available to do this? I looked at the documentation for the SCM
plugin
and
it doesn't seem to quite fit the bill in order to do this.
Thanks!
Allan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
with regards,
--
Lachlan Deck
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
going mad :-) testing archetype
just need a sanity check here :-) I'm trying to test some updates to an archetype. So I've edited a particular file, for example, such as the following: $ emacs my-archetype/src/main/resources/archetype-resources/src/main/ resources/Properties I've cleaned my local repo of the artifacts in the same groupId and then re-installed it: $ mvn -o clean install But then when I generate a project from the archetype the adjustments I've made don't appear. $ cd ~/ $ mkdir test cd test $ mvn -o archetype:generate -DarchetypeCatalog=local ... Choose archetype: 1: local - my-archetype (Yada yada) ... Choose a number: (1/2/3/4): 1 Define value for groupId: : my.grouping Define value for artifactId: : myapp Define value for version: 1.0-SNAPSHOT: : Define value for package: my.grouping: : Confirm properties configuration: ... Y: : [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 37 seconds [INFO] Finished at: Wed Apr 22 17:57:04 EST 2009 [INFO] Final Memory: 8M/15M [INFO] $ $ less myapp/src/main/resources/Properties -- still doesn't contain the text I've added :-/ So digging deeper: $ cp ~/.m2/repository/my/groupId/my-archetype/2.0.18-SNAPSHOT/my- archetype-2.0.18-SNAPSHOT.jar . $ mv my-archetype-2.0.18-SNAPSHOT.jar my-archetype-2.0.18-SNAPSHOT.zip $ unzip my-archetype-2.0.18-SNAPSHOT.zip $ less archetype-resources/src/main/resources/Properties -- looks good! There's gotta be something obvious I'm missing ... any clues? Is there some cache I've overlooked? :-) Thanks. Is maven caching the old versions (that I've deleted) somewhere else? How do I ensure that I'm testing what I've installed? Thanks. with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: going mad :-) testing archetype
On 22/04/2009, at 6:35 PM, William Ghelfi wrote: On Wed, Apr 22, 2009 at 10:25 AM, Lachlan Deck lachlan.d...@gmail.com wrote: $ cd ~/ $ mkdir test cd test $ mvn -o archetype:generate -DarchetypeCatalog=local ... Choose archetype: 1: local - my-archetype (Yada yada) ... Choose a number: (1/2/3/4): 1 Define value for groupId: : my.grouping Define value for artifactId: : myapp Define value for version: 1.0-SNAPSHOT: : Define value for package: my.grouping: : Confirm properties configuration: ... Y: : [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 37 seconds [INFO] Finished at: Wed Apr 22 17:57:04 EST 2009 [INFO] Final Memory: 8M/15M [INFO] $ $ less myapp/src/main/resources/Properties -- still doesn't contain the text I've added :-/ Sorry for the question... Not at all... Did you remember to create a new app using the new archetype, and then checked the new app? That's what the output above shows. i.e., me creating a new app after having installed the archetype. Quite strange. with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: going mad :-) testing archetype
On 22/04/2009, at 6:27 PM, Nick Stolwijk wrote: Are there any other version of your archetype in ~/.m2/repository/my/groupId/my-archetype? No. I deleted the dir prior to installing. With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Wed, Apr 22, 2009 at 10:25 AM, Lachlan Deck lachlan.d...@gmail.com wrote: ~/.m2/repository/my/groupId/my-archetype - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: going mad :-) testing archetype
On 22/04/2009, at 7:15 PM, Nick Stolwijk wrote: Could you try it with the debug option (-X). Maybe that shows what jar file gets extracted. I just identified the problem. In a properties file I had the following in the archetype: ## # Some section heading ## some.java.property = foo And in the generated project the '##' were getting stripped. Not sure why. Is this documented somewhere? (These were the only lines I'd added. By adding a bogus java property I see that the file is certainly being used.) with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: archetype-metadata optional filesets?
Thanks. On 09/04/2009, at 8:17 PM, Raphaël Piéroni wrote: Hi Lachlan Deck, Currently, the filesets are not optional. Regards, Raphaël 2009/4/9 Lachlan Deck lachlan.d...@gmail.com: Anyone? On 07/04/2009, at 8:56 AM, Lachlan Deck wrote: Hi there, Just a quick question: say I've got a fileset in the archetype descriptor like so: ?xml version=1.0 encoding=UTF-8? archetype-descriptor name=woapplication-archetype requiredProperties ... /requiredProperties fileSets fileSet filtered=true packaged=true encoding=UTF-8 directorysrc/main/java/directory includes include**/*.java/include /includes /fileSet ... /fileSets /archetype-descriptor Is it possible to define either an include/exlude or an optional fileset that's driven by the properties? Otherwise, how do other people optionally include/exclude files during arhcetype:generate? i.e., based on requiredProperties? Thanks. with regards, -- Lachlan Deck - 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 with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: archetype-metadata optional filesets?
Anyone? On 07/04/2009, at 8:56 AM, Lachlan Deck wrote: Hi there, Just a quick question: say I've got a fileset in the archetype descriptor like so: ?xml version=1.0 encoding=UTF-8? archetype-descriptor name=woapplication-archetype requiredProperties ... /requiredProperties fileSets fileSet filtered=true packaged=true encoding=UTF-8 directorysrc/main/java/directory includes include**/*.java/include /includes /fileSet ... /fileSets /archetype-descriptor Is it possible to define either an include/exlude or an optional fileset that's driven by the properties? Otherwise, how do other people optionally include/exclude files during arhcetype:generate? i.e., based on requiredProperties? Thanks. with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
archetype-metadata optional filesets?
Hi there, Just a quick question: say I've got a fileset in the archetype descriptor like so: ?xml version=1.0 encoding=UTF-8? archetype-descriptor name=woapplication-archetype requiredProperties ... /requiredProperties fileSets fileSet filtered=true packaged=true encoding=UTF-8 directorysrc/main/java/directory includes include**/*.java/include /includes /fileSet ... /fileSets /archetype-descriptor Is it possible to define either an include/exlude or an optional fileset that's driven by the properties? Otherwise, how do other people optionally include/exclude files during arhcetype:generate? Thanks. with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven release plugin addition
Hi there, I'd like to see either an additional goal (e.g., release:deploy) added to the release plugin or perhaps it can be achieved via properties. Essentially, as far as I understand it, the release plugin requires access to an scm repository to commit changes to in addition to deploying the artifacts to the relevant maven repo. There's often projects out there, however, that just don't release their stuff or only provide snapshot builds (e.g., as their primary build system is ant-based).. yet anonymous cvs/svn access is free for all. So, in order to help facilitate deploying psuedo-released versions of such third-party projects to an intranet for example, it'd be a great addition to the release plugin in my view if it were possible to take a snapshot and deploy a release to some repo without the need for scm commits. e.g., the goal would be to deploy a 5.0.0-SNAPSHOT, for example, as 5.0.0.1234 where 1234 is the svn version. I've checked out the source for the release plugin to have a poke around and it appears that the above would be relatively trivial to do. Just wondering if: a) is this already possible? Did I miss something? b) if not already possible, would one of the main contributors to the plugin like to add this -- given you're familiar already with how best to achieve this with the project c) otherwise, any objections to this or other suggestions? Thanks. with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven release plugin addition
On 10/03/2009, at 9:06 PM, Stephen Connolly wrote: ehhh what's wrong with mvn deploy... that will deploy the current version (which should be a -SNAPSHOT)... Because, quite simply, I don't want to link my projects against a snapshot. The svn version is repeatable. in all other cases you should be using a qualifier that identifies you as the builder... for example if I want to deploy my own version of something that is currently 5.0.0-SNAPSHOT I would deploy it as version 5.0.0-onedash- r1234 How are you doing this? where r1234 is the subversion revision... and by way of explanation I own the one-dash.com domain. if you don't use a qualifier you will mess up the maven version determinism or risk a conflict with the real project when they do decide to roll the 1234rd patch of 5·0.0 I can assure you that the projects I have in mind have no intention of releasing maven builds. The main build system is using ant, it's not deployed to a repo, and the pom files in the projects are there to please the maven people - but they remain snapshots. If you are doing this for non-personal use... This is both for my company's intranet repo but also for a community of people using the same projects. Simplicity is key. I would recommend mirroring their svn repo using either git-svn or svnsync or tailor and maintaining your own branch and releasing from that branch... While I appreciate that this might be ideal - that's just more work compared with doing what I suggested which is simple. you'd also want to change the groupId's to belong to your company's domain. Perhaps, again if I wanted more work. The suggested additional goal's description could very well suggest all these things as 'better alternatives' but allow people to run the goal anyway for convenience's sake. It wouldn't be the first maven plugin to do so... -Stephen 2009/3/10 Lachlan Deck lachlan.d...@gmail.com Hi there, I'd like to see either an additional goal (e.g., release:deploy) added to the release plugin or perhaps it can be achieved via properties. Essentially, as far as I understand it, the release plugin requires access to an scm repository to commit changes to in addition to deploying the artifacts to the relevant maven repo. There's often projects out there, however, that just don't release their stuff or only provide snapshot builds (e.g., as their primary build system is ant-based).. yet anonymous cvs/svn access is free for all. So, in order to help facilitate deploying psuedo-released versions of such third-party projects to an intranet for example, it'd be a great addition to the release plugin in my view if it were possible to take a snapshot and deploy a release to some repo without the need for scm commits. e.g., the goal would be to deploy a 5.0.0-SNAPSHOT, for example, as 5.0.0.1234 where 1234 is the svn version. I've checked out the source for the release plugin to have a poke around and it appears that the above would be relatively trivial to do. Just wondering if: a) is this already possible? Did I miss something? b) if not already possible, would one of the main contributors to the plugin like to add this -- given you're familiar already with how best to achieve this with the project c) otherwise, any objections to this or other suggestions? Thanks. with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven release plugin addition
On 11/03/2009, at 9:12 AM, Stephen Connolly wrote: edit the version in thepom andjust run mvn deploy More work? Sure I can create an ant-file that will recursively follow the modules down editing all of them to do this - but that's what the release plugin does already right? A bit of re-use wouldn't go astray here... On 10/03/2009, Lachlan Deck lachlan.d...@gmail.com wrote: On 10/03/2009, at 9:06 PM, Stephen Connolly wrote: ehhh what's wrong with mvn deploy... that will deploy the current version (which should be a -SNAPSHOT)... Because, quite simply, I don't want to link my projects against a snapshot. The svn version is repeatable. in all other cases you should be using a qualifier that identifies you as the builder... for example if I want to deploy my own version of something that is currently 5.0.0-SNAPSHOT I would deploy it as version 5.0.0-onedash- r1234 How are you doing this? where r1234 is the subversion revision... and by way of explanation I own the one-dash.com domain. if you don't use a qualifier you will mess up the maven version determinism or risk a conflict with the real project when they do decide to roll the 1234rd patch of 5·0.0 I can assure you that the projects I have in mind have no intention of releasing maven builds. The main build system is using ant, it's not deployed to a repo, and the pom files in the projects are there to please the maven people - but they remain snapshots. If you are doing this for non-personal use... This is both for my company's intranet repo but also for a community of people using the same projects. Simplicity is key. I would recommend mirroring their svn repo using either git-svn or svnsync or tailor and maintaining your own branch and releasing from that branch... While I appreciate that this might be ideal - that's just more work compared with doing what I suggested which is simple. you'd also want to change the groupId's to belong to your company's domain. Perhaps, again if I wanted more work. The suggested additional goal's description could very well suggest all these things as 'better alternatives' but allow people to run the goal anyway for convenience's sake. It wouldn't be the first maven plugin to do so... -Stephen 2009/3/10 Lachlan Deck lachlan.d...@gmail.com Hi there, I'd like to see either an additional goal (e.g., release:deploy) added to the release plugin or perhaps it can be achieved via properties. Essentially, as far as I understand it, the release plugin requires access to an scm repository to commit changes to in addition to deploying the artifacts to the relevant maven repo. There's often projects out there, however, that just don't release their stuff or only provide snapshot builds (e.g., as their primary build system is ant-based).. yet anonymous cvs/svn access is free for all. So, in order to help facilitate deploying psuedo-released versions of such third-party projects to an intranet for example, it'd be a great addition to the release plugin in my view if it were possible to take a snapshot and deploy a release to some repo without the need for scm commits. e.g., the goal would be to deploy a 5.0.0-SNAPSHOT, for example, as 5.0.0.1234 where 1234 is the svn version. I've checked out the source for the release plugin to have a poke around and it appears that the above would be relatively trivial to do. Just wondering if: a) is this already possible? Did I miss something? b) if not already possible, would one of the main contributors to the plugin like to add this -- given you're familiar already with how best to achieve this with the project c) otherwise, any objections to this or other suggestions? Thanks. with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org with regards, -- Lachlan Deck - 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 with regards, -- Lachlan Deck - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven embedder provided properties?
Hi there, just wondering if there's any properties made available to the maven embedder when inside eclipse? I'm wondering as I'd like to have a profile that's activated if detected that it's running within eclipse. Just trying to save having to define the profile within the gui for each project :-) Thanks with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
pluginManagement help (eclipse problem)
Hi there, I've noticed that with both m2eclipse and q4e that the pluginManagement section of the uppermost parent is not inherited to child modules. So in a child module I have: build plugins artifactIdfoo/artifactId groupIdbar/groupId /plugins /build Building from the command line works no problems. But in eclipse it has all sorts of errors as it's not honouring the version defined in the pluginManagement that ought to have been inherited... and is instead is trying to download :RELEASE. Anyone else seeing this? with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: pluginManagement help (eclipse problem)
Hi Is no one seeing this? On 02/08/2008, at 9:14 PM, Lachlan Deck wrote: Hi there, I've noticed that with both m2eclipse and q4e that the pluginManagement section of the uppermost parent is not inherited to child modules. So in a child module I have: build plugins artifactIdfoo/artifactId groupIdbar/groupId /plugins /build Building from the command line works no problems. But in eclipse it has all sorts of errors as it's not honouring the version defined in the pluginManagement that ought to have been inherited... and is instead is trying to download :RELEASE. Anyone else seeing this? with regards, -- Lachlan Deck with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
org.codehaus.mojo:wsdl2java-maven-plugin repository?
Hi there, does anyone know of a plugin repository that has the above plugin? (It doesn't appear to be on codehaus' repositories nor central) with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: org.codehaus.mojo:wsdl2java-maven-plugin repository?
On 30/07/2008, at 10:49 AM, Lachlan Deck wrote: Hi there, does anyone know of a plugin repository that has the above plugin? (It doesn't appear to be on codehaus' repositories nor central) A bit of cuiling/googling turns up axistools-maven-plugin as a successor it seems. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axistools-maven-plugin (was: org.codehaus.mojo:wsdl2java-maven-plugin repository)
On 30/07/2008, at 10:59 AM, Lachlan Deck wrote: On 30/07/2008, at 10:49 AM, Lachlan Deck wrote: Hi there, does anyone know of a plugin repository that has the above plugin? (It doesn't appear to be on codehaus' repositories nor central) A bit of cuiling/googling turns up axistools-maven-plugin as a successor it seems. Any chance someone can update the docs for axistools-maven-plugin so that there's far less Undocumented features? It'd be great for any others who find the tool for the examples link to work (and / or actually exist). I had to do a bit of googling to figure out what mappings took etc. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axistools-maven-plugin (was: org.codehaus.mojo:wsdl2java-maven-plugin repository)
Anyone know if it's possible to generate axis 1.1 compatible stubs with axistools-maven-plugin? If so -- how might this be done? with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: archetype for creating packaging 'pom'?
Hi Wayne, On 28/04/2008, at 1:49 PM, Wayne Fay wrote: In that case, I would probably just use maven-archetype-quickstart and then edit the pom.xml to change packaging jar to pom. And I might remove the junit dependency that comes in by default. You will also need to add the modules section etc. That's my point - why keep doing something repetitively? I was under the impression that maven was designed to save you from silly repetitive (simple) tasks like this :-) I just assumed that someone by now would have provided a shortcut. Obviously not. But I tend to not use archetypes at all, so... At the very least it would save you having to type those initial xml headers whilst providing a simple starting point. Wayne On 4/27/08, Lachlan Deck [EMAIL PROTECTED] wrote: Hi Wayne, On 27/04/2008, at 11:26 AM, Wayne Fay wrote: What kind of project are you really looking to build? For what purpose? The more detail you provide, the better the answer you will get, generally. Okay - more details... though I thought it was obvious enough :-) There's two scenarios that this is needed: 1) creating an initial multi-module project (where the sub-modules will be created subsequently) $ mvn create rootParentProject 2) creating sub-module group. cd rootParentProject $ mvn create anotherParent $ cd anotherParent $ mvn create someModule $ cd .. $ mvn create yetAnotherParent $ cd yetAnotherParent $ mvn create someModule which would be quite simple (without any editing of files prior to creating a sub-module grouping). The above structure would then be: /pom.xml /anotherParent/pom.xml /anotherParent/someModule/pom.xml /yetAnotherParent/pom.xml /yetAnotherParent/someModule/pom.xml On 4/26/08, Lachlan Deck [EMAIL PROTECTED] wrote: I'm sure this must be a FAQ - but I can't see an answer anywhere. Is there not an archetype for creating a pom.xml with packaging pom? with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: archetype for creating packaging 'pom'?
On 27/04/2008, at 1:29 PM, Wendy Smoak wrote: On Sun, Apr 27, 2008 at 5:48 AM, Lachlan Deck [EMAIL PROTECTED] wrote: I'm sure this must be a FAQ - but I can't see an answer anywhere. Is there not an archetype for creating a pom.xml with packaging pom? Not afaik, it's generally less typing to just copy one and modify it. I thought it would be less typing to simply create a parent pom *without* having to edit it before adding sub-modules. i.e., mvn create cd parentDir mvn create Rather than having to continually edit the parent pom each time you need to create a sub-module grouping. It might be nice to have the values filtered in though... if you'd like to contribute an archetype we can see about adding it to the list. I'll need to get more familiar with maven prior to doing this... I just assumed it would have annoyed enough people by now that someone would have done it already. Obviously not. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: archetype for creating packaging 'pom'?
Hi Wayne, On 27/04/2008, at 11:26 AM, Wayne Fay wrote: What kind of project are you really looking to build? For what purpose? The more detail you provide, the better the answer you will get, generally. Okay - more details... though I thought it was obvious enough :-) There's two scenarios that this is needed: 1) creating an initial multi-module project (where the sub-modules will be created subsequently) $ mvn create rootParentProject 2) creating sub-module group. cd rootParentProject $ mvn create anotherParent $ cd anotherParent $ mvn create someModule $ cd .. $ mvn create yetAnotherParent $ cd yetAnotherParent $ mvn create someModule which would be quite simple (without any editing of files prior to creating a sub-module grouping). The above structure would then be: /pom.xml /anotherParent/pom.xml /anotherParent/someModule/pom.xml /yetAnotherParent/pom.xml /yetAnotherParent/someModule/pom.xml On 4/26/08, Lachlan Deck [EMAIL PROTECTED] wrote: I'm sure this must be a FAQ - but I can't see an answer anywhere. Is there not an archetype for creating a pom.xml with packaging pom? with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
archetype for creating packaging 'pom'?
Hi there, I'm sure this must be a FAQ - but I can't see an answer anywhere. Is there not an archetype for creating a pom.xml with packaging pom? Thanks. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: project.parent.* properties?
Thanks Wayne,
An example of how to do this is found here:
http://blogs.sonatype.com/brian/2008/04/17/120848550.html
On 26/04/2008, at 4:44 PM, Wayne Fay wrote:
I can't solve your specific problem for you, but I would generally
expect that dependency:unpack would be involved in most solutions:
http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html
http://maven.apache.org/plugins/maven-dependency-plugin/usage.html
You are welcome to continue using .. etc. But if you expect your
code to compile as a stand-alone module (eg in a continuous
integration server) then you will need to limit your modules to their
own source code only, plus anything you're bringing in via
dependencies etc.
Wayne
On 4/26/08, Lachlan Deck [EMAIL PROTECTED] wrote:
Hi,
would you mind showing an example of how to achieve this? All
that's in the
../src/main/resources dir is a single file that's being filtered with
properties relevant for each module (rather than having a copy of
the same
file in each module).
On 26/04/2008, at 3:22 PM, Wayne Fay wrote:
This is an anti-pattern in Maven usage.
Modules should be self-contained. If you must include content from
another module, then you should depend on the Jar just like any
other
artifact and use various plugins to unpack the files you need into a
specific area in your project etc. You should not use .. or
hard-code paths etc to access content which belongs to other modules
(parents or children).
Wayne
On 4/25/08, Lachlan Deck [EMAIL PROTECTED] wrote:
Hi there,
If I have the following, all's fine... i.e., the resources are
filtered
and
found in the build output.
resource
targetPathResources/targetPath
filteringtrue/filtering
directory../src/main/resources/directory
/resource
However the following produces no results...
resource
targetPathResources/targetPath
filteringtrue/filtering
directory${project.parent.basedir}/src/main/resources/directory
/resource
What properties are available for referencing the parent?
Thanks.
with regards,
--
Lachlan Deck
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
with regards,
--
Lachlan Deck
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
with regards,
--
Lachlan Deck
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
project.parent.* properties?
Hi there,
If I have the following, all's fine... i.e., the resources are
filtered and found in the build output.
resource
targetPathResources/targetPath
filteringtrue/filtering
directory../src/main/resources/directory
/resource
However the following produces no results...
resource
targetPathResources/targetPath
filteringtrue/filtering
directory${project.parent.basedir}/src/main/resources/directory
/resource
What properties are available for referencing the parent?
Thanks.
with regards,
--
Lachlan Deck
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: project.parent.* properties?
Hi,
would you mind showing an example of how to achieve this? All that's
in the ../src/main/resources dir is a single file that's being
filtered with properties relevant for each module (rather than having
a copy of the same file in each module).
On 26/04/2008, at 3:22 PM, Wayne Fay wrote:
This is an anti-pattern in Maven usage.
Modules should be self-contained. If you must include content from
another module, then you should depend on the Jar just like any other
artifact and use various plugins to unpack the files you need into a
specific area in your project etc. You should not use .. or
hard-code paths etc to access content which belongs to other modules
(parents or children).
Wayne
On 4/25/08, Lachlan Deck [EMAIL PROTECTED] wrote:
Hi there,
If I have the following, all's fine... i.e., the resources are
filtered and
found in the build output.
resource
targetPathResources/targetPath
filteringtrue/filtering
directory../src/main/resources/directory
/resource
However the following produces no results...
resource
targetPathResources/targetPath
filteringtrue/filtering
directory${project.parent.basedir}/src/main/resources/directory
/resource
What properties are available for referencing the parent?
Thanks.
with regards,
--
Lachlan Deck
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
with regards,
--
Lachlan Deck
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependencyManagement help
Hi there, On 24/04/2008, at 4:37 PM, Jörg Schaible wrote: -- root parent pom -- dependencyManagement dependencies dependency groupId.../groupId artifactId.../artifactId type.../type version.../version /dependency /dependencies /dependencyManagement -- /frameworks/pom.xml -- dependencies dependency groupId.../groupId artifactId.../artifactId scopeprovided/scope /dependency /dependencies And so forth. Previously I had no dependencyManagement at all. So the only mention of the version of a dependency is in the management section. However, now when I do a 'mvn clean' I get the following. The two artifacts to not match. An artifact is defined by groupId, artifactId, type and optional classifier. The type defaults to jar. This might give you an idea ;-) Then I'm not seeing what purpose the dependencyManagement section serves if I've still gotta declare pretty much everything apart from 'version' in other dependency declarations? with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [newby] how to include/package private libs/*.jar
Hi Nick, On 24/04/2008, at 6:50 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: It would be something like: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.0/version executions execution idlist-deps/id phasegenerate-resources/phase goals goallist/goal /goals configuration outputFilefoo.txt/outputFile /configuration /execution /executions plugins /build Nice. Thanks for that. And/Or I suppose I could use antrun to transform the output as needed. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly help
Hi Henrique, On 24/04/2008, at 1:06 AM, Henrique Prange wrote: Hi Lachlan, On Tue, Apr 22, 2008 at 9:31 PM, Lachlan Deck [EMAIL PROTECTED] wrote: My dependent frameworks are not of packaging woframework, but jar I think you really should try to use the woframework packaging. You will have to write much less configuration. There was hardly any actually. -- parent pom -- ?xml version=1.0 encoding=UTF-8? project ... ... build sourceDirectorysrc/sourceDirectory testSourceDirectorytests/testSourceDirectory resources resource targetPathResources/targetPath filteringtrue/filtering directory../src/main/resources/directory /resource resource targetPathResources/targetPath filteringfalse/filtering directoryComponents/directory /resource resource targetPathResources/targetPath filteringfalse/filtering directoryResources/directory /resource resource targetPathWebServerResources/targetPath filteringfalse/filtering directoryWebServerResources/directory /resource /resources /build /project Then all the child modules are quite short. - so I can't see what options/configurations to provide to bundle the relevant dependent jars (or indeed - what scope they should be). Why do you need the dependencies packaged inside a woframework jar? The dependencies are declared in the pom.xml. When you declare a woframework as dependency, Maven automatically adds the transitive dependencies to your project. For example, if you have a woframework that depends upon a library A. When you add this woframework to a project, Maven will add the dependency A transitively to your project. Okay. Thanks for the explanation. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly help
Hi Henrique, On 24/04/2008, at 1:23 AM, Henrique Prange wrote: On Wed, Apr 23, 2008 at 2:24 AM, Lachlan Deck [EMAIL PROTECTED] wrote: Okay - making progress... If I create a maven-archetype-j2ee-simple, cd into the dir, comment out the site module from the parent pom and do 'mvn package' it all works without having to install the sub-modules. However, with my structure it doesn't grab the jars from the sub- modules for the app - but complains that they're not installed. The app (with packaging = woapplication) fails to build. Does it fail because Maven cannot find a dependency? Or is it another problem? It fails saying that I should firstly download the dependency and manually install it - but it's one of the modules in the project. My tree is like this: /pom.xml /myframeworks /myframeworks/moduleA ... /app1/pom.xml It's a similar structure to the j2ee-simple example. What am I missing? What's the 'trick' for making this work? Have you tried mvn clean install in the parent module? The package goal doesn't install the jars into the your local repository. I realise that it doesn't install stuff. But that's my point, the j2ee- simple project (which also has sub-modules of modules) didn't need to have the modules installed in order to simply do mvn package right out of the box, so to speak. I'm wondering why it's different here. I'm trying to get away from the old woproject-ant based system where something has to be installed first prior to be able to build the application for testing/deployment. Have you declared the sub-module dependency in your application pom.xml? Yes. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [newby] how to include/package private libs/*.jar
Hi Joshua, On 23/04/2008, at 11:23 PM, Joshua ChaitinPollak wrote: On Apr 23, 2008, at 1:05 AM, Lachlan Deck wrote: - append to the text file a list of the jars bundled (prefixing each with a custom path). That's a tricky one. I'd have to say start with the dependency or assembly plugin and see if they can do what you need. I know one of the plugins can put the jars on your classpath in the Manifest, but we don't use the manifest, so I have no experience with it. Right. This is the bit I'm stuck with... Well, I'm not sure if this is helpful or not, but you can do this: mvn -DoutputFile=foo.txt dependency:list which will put your dependencies in a file called foo.txt. You could then use the exec or groovy plugins to process the output file into the format you want. Interesting. Forgive my ignorance (still a maven newbie) but how might I incorporate that into the build lifecycle? with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
dependencyManagement help
Hi there, I'm trying to utilise dependency management but am obviously missing something. I've got /pom.xml /frameworks/pom.xml /frameworks/fwk1 ... /frameworks/fwkN /app1/pom.xml -- root parent pom -- dependencyManagement dependencies dependency groupId.../groupId artifactId.../artifactId type.../type version.../version /dependency /dependencies /dependencyManagement -- /frameworks/pom.xml -- dependencies dependency groupId.../groupId artifactId.../artifactId scopeprovided/scope /dependency /dependencies And so forth. Previously I had no dependencyManagement at all. So the only mention of the version of a dependency is in the management section. However, now when I do a 'mvn clean' I get the following. What am I missing? Thanks. Obviously - adding the version to the /frameworks/pom.xml's dependencies works but I thought that was the whole idea behind the dependencyManagement declarations in the parent pom? Or is that only relevant for child poms where the packaging is not of type pom? $ mvn clean [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: foo.bar:frameworks POM Location: .../foobar/frameworks/pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for ... [1] 'dependencies.dependency.version' is missing for ... [2] 'dependencies.dependency.version' is missing for ... [3] 'dependencies.dependency.version' is missing for ... Reason: Failed to validate POM for project foo.bar:frameworks at .../ foobar/frameworks/pom.xml [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for project foo.bar:frameworks at .../foobar/frameworks/pom.xml at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:376) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:289) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) 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:585) 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) with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [newby] how to include/package private libs/*.jar
Hi Joshua, On 23/04/2008, at 12:56 AM, Joshua ChaitinPollak wrote: Have you tried, or has anyone suggested using the system scope? I had thought about it, but, unless I'm mistaken, that assumes that the jar will be found in that location at runtime/deployment also (which it won't). On the other hand, what we've done internally is created an inhouse Maven repository with Artifactory, and we uploaded our third party jars to the internal 3rd party jar repository (things like JIDE that aren't externally redistributable) I think you mentioned that solution isn't available to you. I might be able to make it happen... we'll see. The part I'm needing help with now is creating the final assembly/ bundle. Specifically I need to do the following: - filter a text file (replacing certain properties) + - append to the text file a list of the jars bundled (prefixing each with a custom path). Any suggestions? Thanks with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly help
Hi Henrique, On 23/04/2008, at 5:14 AM, Henrique Prange wrote: What do you want to do exactly? It seems that you are trying to package a WebObjects application. Correct :-) Have you tried the maven-wolifecycle-plugin [1]? [1]http://wiki.objectstyle.org/confluence/display/WOL/WOProject-Maven2 I'm trying both. The documentation, for WOProject-Maven2 is not very verbose however. My dependent frameworks are not of packaging woframework, but jar - so I can't see what options/configurations to provide to bundle the relevant dependent jars (or indeed - what scope they should be). I've got the relevant repo and plugin repo declarations in my parent pom but I'm getting this in the app project: Cannot find lifecycle mapping for packaging: 'woapplication'. Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingwoapplication. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [newby] how to include/package private libs/*.jar
Hi Joshua,
On 23/04/2008, at 10:40 AM, Joshua ChaitinPollak wrote:
On Apr 22, 2008, at 8:16 PM, Lachlan Deck wrote:
On 23/04/2008, at 12:56 AM, Joshua ChaitinPollak wrote:
Have you tried, or has anyone suggested using the system scope?
I had thought about it, but, unless I'm mistaken, that assumes that
the jar will be found in that location at runtime/deployment also
(which it won't).
Well, as far as I understand, using the system scope tells Maven not
to do anything with it at release time, so putting the library in
your release bundle, jar, or whatever, and on the classpath would be
your responsiblity.
We get around that by using a custom assembly definition and a
custom shell script to start our application which puts anything in
our libs directory (in our deployed installation) on the classpath.
Okay.
On the other hand, what we've done internally is created an
inhouse Maven repository with Artifactory, and we uploaded our
third party jars to the internal 3rd party jar repository (things
like JIDE that aren't externally redistributable)
I think you mentioned that solution isn't available to you.
I might be able to make it happen... we'll see.
The part I'm needing help with now is creating the final assembly/
bundle.
Specifically I need to do the following:
- filter a text file (replacing certain properties) +
Well, we do this:
resource
directory${basedir}/src/main/resources/directory
filteringtrue/filtering
/resource
and then we have a version.properties file that looks like:
[EMAIL PROTECTED]:~/src/$ cat src/main/resources/pkg/spec/
version.properties
application.repository.version=${buildNumber}
application.releasenumber=${project.version}
application.customer=${customer}
application.repository.url=${project.scm.connection}
Those properties are supplied by Maven. I believe you can refer to
anything in the properties block in this fashion as well.
Oh, doing that is the easy part. What I'm referring to is filtering
the file in such that it dynamically inserts a list of all
dependencies prefixed by a custom prefix.
What you've mentioned doesn't appear to achieve this.
- append to the text file a list of the jars bundled (prefixing
each with a custom path).
That's a tricky one. I'd have to say start with the dependency or
assembly plugin and see if they can do what you need. I know one of
the plugins can put the jars on your classpath in the Manifest, but
we don't use the manifest, so I have no experience with it.
Right. This is the bit I'm stuck with...
with regards,
--
Lachlan Deck
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly help
Hi again, On 23/04/2008, at 5:14 AM, Henrique Prange wrote: What do you want to do exactly? It seems that you are trying to package a WebObjects application. Have you tried the maven- wolifecycle-plugin [1]? [1]http://wiki.objectstyle.org/confluence/display/WOL/WOProject-Maven2 Okay - making progress... If I create a maven-archetype-j2ee-simple, cd into the dir, comment out the site module from the parent pom and do 'mvn package' it all works without having to install the sub-modules. However, with my structure it doesn't grab the jars from the sub- modules for the app - but complains that they're not installed. The app (with packaging = woapplication) fails to build. What am I missing? What's the 'trick' for making this work? with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
property toLowerCase?
Hi there, Anyone know how to set a property that is lower/upper case of another property? Thanks. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
assembly help
Hi there, I'm still quite new to maven... so any demos appreciated :-) I'm needing to create a directory-based assembly (ideally it would be tgz or zipped up afterwards) - but I'm not quite sure how to go about the following. The project looks like this: /pom.xml frameworks/ pom.xml moduleA etc apps/ app1 etc The apps need to be built as application bundles...e.g., finalName.someExtension/ Dependencies/*.jar !-- all but system/test scoped dependencies -- Resources/Java/finalName.jar etc I also need to append to a textfile the list of dependencies prefixed by a custom path (one entry per line). Any examples/ideas? Thanks with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: very new to maven Eclipse and java
Hi Hossain, On 20/04/2008, at 4:27 PM, hossainsaad wrote: I have wrote one test case in my new work place. now i have seen in other codes they have POM.xml. ques # 1==Could anybody tell me what exactly I have to put there to run my test. I am adding a pom.xml which i tried but did not work. let me know what i have to add. We are using Spring jdbc template. I am adding the test code and the pom.xml. I'm also relatively new to maven... but I think you'll find that you'll have better success if you do the tutorial here: http://maven.apache.org/guides/getting-started/index.html There's one bug in the tutorial under 'How do I create documentation?' you should type the following rather than what's written. mvn site:site the rough pom i have wrote is //Ques#2:what should be groupID?? if my folder name is Sadd Think of groupId like packages in java. It's up to you - but you'd normally use your reverse domain, for example. artifactIdsimple/artifactId // Ques#3what should I put here in artifactId, what does it mean Something that uniquely identifies your project/artifact (i.e., the thing you're building) from other artifacts that might live one day in a repository. dependency groupIdSadd/groupId // Ques#4 Again if my folder name is Sadd, am i doing right? Doesn't hurt. But it doesn't matter. artifactIdcom.core/artifactId // Ques#5my Sadd folder is dependant on com.core, am i doing right?? Check the pom declaration for core. They should match. artifactIds shouldn't have '.'s in them. They're usually the final part of a fully qualified id. It sounds like the group id for core should be Sadd.com i.e., artifactIdcore/artifactId groupIdSadd.com/groupId Sorry if my questions are too imple or stupid. I wanted to learn maven by actually doing a project. thats wht i m trying to do. if anybody could help me thank you in advance. I think maven is one of those things that you really need to do some reading first - before trying to piece things together like you've attempted to. See the tutorial link above... you should find after going through it bit by bit that you'll have a better idea of things. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [newby] how to include/package private libs/*.jar
Hi Henrique, On 19/04/2008, at 6:52 AM, Henrique Prange wrote: It is not recommended that you store your jars in SVN. So, there is no simple way to do what you want with Maven. Recommended or not - I simply cannot go another route. The project needs to be self-contained which requires another developer to check it out via svn without any further hassles. Similarly a build server needs to be able to svn up build... Putting it in my local repository seems kind of pointless as it's not in subversion and the project will fail to build elsewhere. It also seems to assume that the repo is publicly available (or at least on vpn). This seems more like a philosophical limitation, if I can put it that way :-) i.e., it seems to me that there's nothing technically difficult for maven to support this: dependency systemPath.../systemPath /dependency i.e., where artifactId, groupId, and version are optional if the systemPath is supplied - seeing as it's kind of redundant when systemPath is supplied as far as I can see. But you can create a repository to share your own libraries (Maven can generate the pom.xml for you). Take a look at [1] and [2]. [1]http://maven.apache.org/guides/introduction/introduction-to-repositories.html [2]http://maven.apache.org/guides/mini/guide-3rd-party-jars- remote.html Thanks for those links. I had already seen the first and a variation on the 2nd... perhaps I can create a local repo for that framework with the localRepositoryPath etc options http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html Seems like it's a bit over the top - but if it works then that's Good Enough For Now(tm). Cheers from your WO friend, ;) :-) Henrique Lachlan Deck wrote: Hi there, I'm quite new to maven, but I would have thought this question would have been included on the FAQ page for maven - but it's not. I've googled around but mustn't be putting in the right search phrase or something... as obviously I've not found the answer :-) The simple question is how do I define dependencies on libs/*.jar for one of my projects where I have jars from a 3rd party (a payment gateway) in the project's lib folder. These libs live in svn with the project - not in a repo (and don't have a version or a pom of their own - they're just libs). i.e., they obviously need to be on the classpath + packaged with the final jar? I'm sure it's something simple... thanks in advance. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [newby] how to include/package private libs/*.jar
Hi Mark, On 19/04/2008, at 5:13 PM, Mark Struberg wrote: To be more specific: Look at the maven-deploy-plugin http://maven.apache.org/plugins/maven-deploy-plugin/usage.html and use the mvn deploy:deploy-file mojo Example: mvn deploy:deploy-file -DrepositoryId=myrepo.id \ -Dfile=myjartoupload.jar \ -DgroupId=my.groupId \ -DartifactId=my-artifactId \ -Dversion=myversion \ -Dpackaging=jar \ You can use this mojo from everywhere, since it is marked as '@requiresProject false'. If this was successfull (check your ~/.m2/repository), you may remove this jar from your lib folder and add the dependency in your pom. I'm wondering how this helps another developer who checks out the project? Or indeed if my system gets somehow hosed? I have no permissions to be creating a shared repo. Thus I need to be able to keep the jars with the project. With ant this was completely simple (one of the few nice things about ant)... so I don't quite appreciate why it needs to be so complex with maven? Fair enough for world-sharable jars (i.e., all the various open-source projects out there) - but for a private jar I can't see the sense in it (at least yet). Thanks... with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [newby] how to include/package private libs/*.jar
Hi Stephen, On 19/04/2008, at 6:10 PM, Stephen Connolly wrote: The following is _not_ recommended. Once you get more used to Maven you will realize that storing your binary artifacts in SVN is a bad thing. Fundamentally, they are a different creature from the source code. I mostly concur - however in this case, the particular jar files of interest seem more like a static resource as they're provided by a 3rd party, will rarely be updated, and come pre-built. They simply need to be on the classpath at compile/runtime. What you should do is use a Maven repository manager (e.g. Nexus, Artifactory, etc) and deploy your binary artifacts to that manager. Not possible in this scenario... for better or worse. There is a poor man's solution to your problem... and that is to fake a remote repository in subversion providing your subversion is served over http (if Maven 2.0) or https (if Maven 2.0.5) You add a repository definition where the repository URL is the place in SVN where you are keeping your remote repository Basically, you'd be doing similar to what has been done at https://maven2-repository.dev.java.net That way your binaries are kept in SVN, but the developer does not check out the trunk of that repository, only accesses it via HTTP Just to be clear - the only jars that'll be in this psuedo repo will be those used by the project. But what you're suggesting would be quite useful. Naturally that'll require authentication in each persons settings file. No problems. Okay I think my next question would be: is there an easy maven command for culling jars prior to a certain version from a repository? e.g., say I've added versions 1, 2, 3 and 4 to the repository (such as nightly builds or something)... is there a command that would easily remove versions prior to 3? Thanks again... with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [newby] how to include/package private libs/*.jar
On 19/04/2008, at 8:51 PM, Stephen Connolly wrote: Okay I think my next question would be: is there an easy maven command for culling jars prior to a certain version from a repository? e.g., say I've added versions 1, 2, 3 and 4 to the repository (such as nightly builds or something)... is there a command that would easily remove versions prior to 3? And now you see why keeping a repository in SVN is a bad thing! Yep. It's worth saying, however, that there's the ideal and then... there's management ;-) Once they go into SVN they can never be removed... (OK, so you can hide them, but they are still in your SVN repository, so why even bother hiding them, you're not going to ever be able to reclaim that space from your SV repository) Good point - but space is really not my concern. Space is relatively cheap. A Maven Repository Manager can store the artifacts on a file system and you can delete old -SNAPSHOTs (which is allowed) How is this done? Deleting old releases is not really the way a repository is designed to work. Not really - but is there a command for doing so? Thanks again. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [newby] how to include/package private libs/*.jar
Hi Wayne, On 20/04/2008, at 1:35 AM, Wayne Fay wrote: You also need to quite simply understand that Maven is not Ant (!). While there are some similarities in the two (they both build Java code), there are far more dissimilarities. I do understand this actually ... and from what I've seen so far I'm liking what maven has to offer (especially all the out-of-the-box stuff that comes for free - which a little hunting). Maven has certain beliefs based on best practices about how builds should be organized and performed. One of those best practices is jars shouldn't go into SCM. So, you won't find a lot of support for this feature in Maven. Fair enough. In general, Maven is less flexible than Ant. For example, Maven expects a certain project structure for your code. While you can adjust (through configuration) the location of source code etc, it makes things a little more complex and increases the size of your pom, plus you may run into issues with certain plugins etc. I'm quite a fan of conventions actually... but obviously there's a mind-shift that I needed to grapple with and have questions answered... [1] If you are used to and require a large amount of flexibility in your builds, then please stick with Ant. Those of us who have migrated to Maven generally believe we are better off as a result, but there is a transition period and the mindset is a bit different. Yep. I'm getting there. I'm also curious -- why are you moving to Maven for this particular project? Because I, personally, was fed up with ant. For some of the simplest things I had to write my own plugin to achieve what should just work - but even then, for the particular environment I'm working in, it was too system dependent (e.g., on external configs etc... long story). So I started looking at maven slowly on the side at first (as obviously there's a bit of reading to do in order to understand the thing and so forth). In the end I liked what I saw and quite quickly saw the potential for less pain + lots of extras ;-) Was a mandate handed down from someone above you, or did a customer ask for it, or was it simply personal interest? You mention that you have no ability to create a shared repo etc, so I wonder where all this is coming from... [1] Yeah, my questions were really in anticipation of questions that I know will come from up the chain, so to speak. Why can't we just put them in subversion?! etc etc I could go on... but essentially I need to have enough good reasons for moving in another direction. With a better understanding now of how to create a repository, it turns out I might very well be able to set up a shared one after all. I'm thinking that I could maybe set up the remote one as a mirror of a custom repo on my local system (at first) and rsync the two when needed. The pom could reference the remote repo but perhaps in my settings.xml file I could override the location to point to my local copy when offline(?) Any suggestions on this? with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[newby] how to include/package private libs/*.jar
Hi there, I'm quite new to maven, but I would have thought this question would have been included on the FAQ page for maven - but it's not. I've googled around but mustn't be putting in the right search phrase or something... as obviously I've not found the answer :-) The simple question is how do I define dependencies on libs/*.jar for one of my projects where I have jars from a 3rd party (a payment gateway) in the project's lib folder. These libs live in svn with the project - not in a repo (and don't have a version or a pom of their own - they're just libs). i.e., they obviously need to be on the classpath + packaged with the final jar? I'm sure it's something simple... thanks in advance. with regards, -- Lachlan Deck - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
