About downloading artifacts from remote repositories
Hi, I want download artifacts from my server so I modified my mirror: mirror idmaven/id mirrorOfmaven/mirrorOf namemaven/name urlhttp://10.10.100.22/maven/url /mirror And I deployed junit-3.8.1.jar into server with runed deploy:deploy-file. But it always downloaded the pom from http://repo1.maven.org/maven2 when I runned . D:\workspace\maven_itmsmvn compile [INFO] Scanning for projects... [INFO] [INFO] Building maven_itms Maven Webapp [INFO]task-segment: [compile] [INFO] Downloading: http://repo1.maven.org/maven2/junit/junit/3.8.1/junit-3.8.1.pom 145b downloaded [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://10.10.100.22/maven/junit/junit/3.8.1/junit-3.8.1.jar 118K downloaded [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 11 seconds [INFO] Finished at: Fri Jan 19 15:31:25 CST 2007 [INFO] Final Memory: 4M/9M [INFO] why? and how I to do? -- View this message in context: http://www.nabble.com/About-downloading-artifacts--from-remote-repositories-tf3038777s177.html#a8445554 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: {m1} running java from maven.xml
Hey Folks, Any tips / pointers for calling Java code from Jelly / Maven's maven.xml? I'm having classpath issues and don't want to expose it as a plugin, rather just call it from maven.xml... ta diyfiesta wrote: Hi Folks, I've writen a POJO to do something useful and wanted to use it as part of my build. So I thought I'd try and kick it off form the maven.xml. So, I did something similar to this; goal name=myGoal j:jelly xmlns:j=jelly:core xmlns:define=jelly:define xmlns:my=myTag define:taglib uri=myTag define:jellybean name=foo className=com.foo.MyTask method=execute/ /define:taglib my:foo x=x outputDir=docs / /j:jelly /goal But I get ClassNotFoundException for com.foo.MyTask, which I guess is reasonable as I havn't set the classpath. I spotted you can add a Classloader attribute to the jellybean element, but I wouldn't know what to set this to... So, can I call Java from maven.xml or do I have to create a new plugin? I don't want to create a new maven plugin if I can help it (I want this utility class as part of my application rather than a seperate source tree). Thanks in advance, -- Toby -- View this message in context: http://www.nabble.com/%7Bm1%7D-running-java-from-maven.xml-tf3022149s177.html#a8446070 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven2 and unknown protocol: e
Hi, Thanks for your contribution. When I tape mvn --version I receive : Maven version 2.0.4. In my classpath of Eclipse I defined a variable : M2_REPO = C:/Documents and Settings/user/.m2/repository When I run mvn -X + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settin gs\user\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'E:\Softs\maven-2.0.4\ bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] You must specify at least one goal. Try 'install' [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: You must specify at least one goal. Try 'install' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:132) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.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) I still have the same exception Thanks for help. -Message d'origine- De : Dário Luís Coneglian Oliveros [mailto:[EMAIL PROTECTED] Envoyé : jeudi 18 janvier 2007 20:24 À : Maven Users List Objet : RE: Maven2 and unknown protocol: e It seems like your maven installation at E:\Softs\maven-2.0.4 is not 2.0.4, but 1.0.2. The reason why is Maven 2 uses classworlds to load some classes instead of Forehead, which is not the case as shown in the stack trace below. Besides Maven 2 does not come with endorsed dir under lib. Also the default local repository for Maven 2 is located by default at user home/.m2/repository. Hope it helps. Dário -Original Message- From: Khabot, Zakaria [mailto:[EMAIL PROTECTED] Sent: quinta-feira, 18 de janeiro de 2007 16:53 To: Maven Users List Subject: Maven2 and unknown protocol: e Hi all, I was using Maven 1.0.2 and it works fine. I migrated to maven 2.0.4 but when I try to execute a goal I have this exception: File or url 'E:\Softs\maven-2.0.4/lib/endorsed/xml-apis-1.0.b2.jar' could not be found java.net.MalformedURLException: unknown protocol: e at java.net.URL.init(URL.java:574) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at com.werken.forehead.Forehead.loadFileOrUrl(Forehead.java:403) at com.werken.forehead.Forehead.load(Forehead.java:322) at com.werken.forehead.Forehead.config(Forehead.java:245) at com.werken.forehead.Forehead.config(Forehead.java:131) at com.werken.forehead.Forehead.main(Forehead.java:579) I specified that my repo is user\.maven\repository The jar exists in this repo but why is he searching in 'E:\Softs\maven-2.0.4/lib Thanks in advance. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven2 and unknown protocol: e
That's an expected behaviour. You must provide at least one goal when running 'mvn'. If you already have a maven 2 project, change to its directory and run 'mvn clean' or 'mvn install'. -Original Message- From: Khabot, Zakaria [mailto:[EMAIL PROTECTED] Sent: sexta-feira, 19 de janeiro de 2007 07:29 To: Maven Users List Subject: RE: Maven2 and unknown protocol: e Hi, Thanks for your contribution. When I tape mvn --version I receive : Maven version 2.0.4. In my classpath of Eclipse I defined a variable : M2_REPO = C:/Documents and Settings/user/.m2/repository When I run mvn -X + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settin gs\user\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'E:\Softs\maven-2.0.4\ bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] You must specify at least one goal. Try 'install' [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: You must specify at least one goal. Try 'install' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:132) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.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) I still have the same exception Thanks for help. -Message d'origine- De : Dário Luís Coneglian Oliveros [mailto:[EMAIL PROTECTED] Envoyé : jeudi 18 janvier 2007 20:24 À : Maven Users List Objet : RE: Maven2 and unknown protocol: e It seems like your maven installation at E:\Softs\maven-2.0.4 is not 2.0.4, but 1.0.2. The reason why is Maven 2 uses classworlds to load some classes instead of Forehead, which is not the case as shown in the stack trace below. Besides Maven 2 does not come with endorsed dir under lib. Also the default local repository for Maven 2 is located by default at user home/.m2/repository. Hope it helps. Dário -Original Message- From: Khabot, Zakaria [mailto:[EMAIL PROTECTED] Sent: quinta-feira, 18 de janeiro de 2007 16:53 To: Maven Users List Subject: Maven2 and unknown protocol: e Hi all, I was using Maven 1.0.2 and it works fine. I migrated to maven 2.0.4 but when I try to execute a goal I have this exception: File or url 'E:\Softs\maven-2.0.4/lib/endorsed/xml-apis-1.0.b2.jar' could not be found java.net.MalformedURLException: unknown protocol: e at java.net.URL.init(URL.java:574) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at com.werken.forehead.Forehead.loadFileOrUrl(Forehead.java:403) at com.werken.forehead.Forehead.load(Forehead.java:322) at com.werken.forehead.Forehead.config(Forehead.java:245) at com.werken.forehead.Forehead.config(Forehead.java:131) at com.werken.forehead.Forehead.main(Forehead.java:579) I specified that my repo is user\.maven\repository The jar exists in this repo but why is he searching in 'E:\Softs\maven-2.0.4/lib Thanks in advance. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - 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]
The skin does not exist
I've started getting a new error message during my project build.The error says : [ERROR] BUILD FAILURE [INFO] [INFO] The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins-DartifactId=maven-default-skin \ -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file org.apache.maven.skins:maven-default-skin:jar:RELEASE What is causing this? -- Jeff Mutonho Cape Town South Africa GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042
RE: Maven2 and unknown protocol: e
When I execute mvn clean I receive: File or url 'E:\Softs\maven-2.0.4/lib/ant-optional-1.5.3-1.jar' could not be found java.net.MalformedURLException: unknown protocol: e at java.net.URL.init(URL.java:574) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at com.werken.forehead.Forehead.loadFileOrUrl(Forehead.java:403) at com.werken.forehead.Forehead.load(Forehead.java:322) at com.werken.forehead.Forehead.config(Forehead.java:245) at com.werken.forehead.Forehead.config(Forehead.java:131) at com.werken.forehead.Forehead.main(Forehead.java:579) -Message d'origine- De : Dário Luís Coneglian Oliveros [mailto:[EMAIL PROTECTED] Envoyé : vendredi 19 janvier 2007 09:49 À : Maven Users List Objet : RE: Maven2 and unknown protocol: e That's an expected behaviour. You must provide at least one goal when running 'mvn'. If you already have a maven 2 project, change to its directory and run 'mvn clean' or 'mvn install'. -Original Message- From: Khabot, Zakaria [mailto:[EMAIL PROTECTED] Sent: sexta-feira, 19 de janeiro de 2007 07:29 To: Maven Users List Subject: RE: Maven2 and unknown protocol: e Hi, Thanks for your contribution. When I tape mvn --version I receive : Maven version 2.0.4. In my classpath of Eclipse I defined a variable : M2_REPO = C:/Documents and Settings/user/.m2/repository When I run mvn -X + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settin gs\user\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'E:\Softs\maven-2.0.4\ bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] You must specify at least one goal. Try 'install' [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: You must specify at least one goal. Try 'install' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:132) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.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) I still have the same exception Thanks for help. -Message d'origine- De : Dário Luís Coneglian Oliveros [mailto:[EMAIL PROTECTED] Envoyé : jeudi 18 janvier 2007 20:24 À : Maven Users List Objet : RE: Maven2 and unknown protocol: e It seems like your maven installation at E:\Softs\maven-2.0.4 is not 2.0.4, but 1.0.2. The reason why is Maven 2 uses classworlds to load some classes instead of Forehead, which is not the case as shown in the stack trace below. Besides Maven 2 does not come with endorsed dir under lib. Also the default local repository for Maven 2 is located by default at user home/.m2/repository. Hope it helps. Dário -Original Message- From: Khabot, Zakaria [mailto:[EMAIL PROTECTED] Sent: quinta-feira, 18 de janeiro de 2007 16:53 To: Maven Users List Subject: Maven2 and unknown protocol: e Hi all, I was using Maven 1.0.2 and it works fine. I migrated to maven 2.0.4 but when I try to execute a goal I have this exception: File or url 'E:\Softs\maven-2.0.4/lib/endorsed/xml-apis-1.0.b2.jar' could not be found java.net.MalformedURLException: unknown protocol: e at java.net.URL.init(URL.java:574) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at com.werken.forehead.Forehead.loadFileOrUrl(Forehead.java:403) at com.werken.forehead.Forehead.load(Forehead.java:322) at com.werken.forehead.Forehead.config(Forehead.java:245) at com.werken.forehead.Forehead.config(Forehead.java:131) at com.werken.forehead.Forehead.main(Forehead.java:579) I specified that my repo is user\.maven\repository The jar exists in this repo but why is he searching in 'E:\Softs\maven-2.0.4/lib Thanks in advance. This e-mail and
Re: {m1} running java from maven.xml
Your jelly code seems wrong. You have to declare your namespace in the tag project : project xmlns:j=jelly:core xmlns:u=jelly:util xmlns:x=jelly:xml xmlns:ant=jelly:ant xmlns:maven=jelly:maven... /project Your class is in your project ? Thus you have to build it before to call your goal (with the jar goal for example). I think that your classes are defined in the default classloader. Arnaud diyfiesta wrote: Hey Folks, Any tips / pointers for calling Java code from Jelly / Maven's maven.xml? I'm having classpath issues and don't want to expose it as a plugin, rather just call it from maven.xml... ta diyfiesta wrote: Hi Folks, I've writen a POJO to do something useful and wanted to use it as part of my build. So I thought I'd try and kick it off form the maven.xml. So, I did something similar to this; goal name=myGoal j:jelly xmlns:j=jelly:core xmlns:define=jelly:define xmlns:my=myTag define:taglib uri=myTag define:jellybean name=foo className=com.foo.MyTask method=execute/ /define:taglib my:foo x=x outputDir=docs / /j:jelly /goal But I get ClassNotFoundException for com.foo.MyTask, which I guess is reasonable as I havn't set the classpath. I spotted you can add a Classloader attribute to the jellybean element, but I wouldn't know what to set this to... So, can I call Java from maven.xml or do I have to create a new plugin? I don't want to create a new maven plugin if I can help it (I want this utility class as part of my application rather than a seperate source tree). Thanks in advance, -- Toby -- View this message in context: http://www.nabble.com/%7Bm1%7D-running-java-from-maven.xml-tf3022149s177.html#a8446714 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: {m1} running java from maven.xml
You can try the classloader named root.maven Arnaud diyfiesta wrote: hmmm, in the partial listing below, for namespaces I have; xmlns:j=jelly:core xmlns:define=jelly:define declared, is that all I need? I've moved this to project with the same results. It seems to run ok (no problems with namespaces I mean), as I say, the error is a classpath one when running it (see below). BUILD FAILED File.. C:\workspaces\spikes\...\maven.xml Element... define:jellybean Line.. 23 Column 27 Could not find class: com.foo.util.MyTask using ClassLoader: null and above that I get a Java stack track with java.lang.ClassNotFoundException... The class is indeed in my project and I built the project (java:compile) before running my goal below (I thought I'd run it interactively first to get it working before attached to a preGoal or whatever). Have you got any examples or people doing a similar thing? Cheers, Arnaud HERITIER wrote: Your jelly code seems wrong. You have to declare your namespace in the tag project : project xmlns:j=jelly:core xmlns:u=jelly:util xmlns:x=jelly:xml xmlns:ant=jelly:ant xmlns:maven=jelly:maven... /project Your class is in your project ? Thus you have to build it before to call your goal (with the jar goal for example). I think that your classes are defined in the default classloader. Arnaud diyfiesta wrote: Hey Folks, Any tips / pointers for calling Java code from Jelly / Maven's maven.xml? I'm having classpath issues and don't want to expose it as a plugin, rather just call it from maven.xml... ta diyfiesta wrote: Hi Folks, I've writen a POJO to do something useful and wanted to use it as part of my build. So I thought I'd try and kick it off form the maven.xml. So, I did something similar to this; goal name=myGoal j:jelly xmlns:j=jelly:core xmlns:define=jelly:define xmlns:my=myTag define:taglib uri=myTag define:jellybean name=foo className=com.foo.MyTask method=execute/ /define:taglib my:foo x=x outputDir=docs / /j:jelly /goal But I get ClassNotFoundException for com.foo.MyTask, which I guess is reasonable as I havn't set the classpath. I spotted you can add a Classloader attribute to the jellybean element, but I wouldn't know what to set this to... So, can I call Java from maven.xml or do I have to create a new plugin? I don't want to create a new maven plugin if I can help it (I want this utility class as part of my application rather than a seperate source tree). Thanks in advance, -- Toby -- View this message in context: http://www.nabble.com/%7Bm1%7D-running-java-from-maven.xml-tf3022149s177.html#a8446981 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: {m1} running java from maven.xml
yep, ${root.maven} and just root.maven in the jellybean classLoader attribute gave the same results :( Arnaud HERITIER wrote: You can try the classloader named root.maven Arnaud diyfiesta wrote: hmmm, in the partial listing below, for namespaces I have; xmlns:j=jelly:core xmlns:define=jelly:define declared, is that all I need? I've moved this to project with the same results. It seems to run ok (no problems with namespaces I mean), as I say, the error is a classpath one when running it (see below). BUILD FAILED File.. C:\workspaces\spikes\...\maven.xml Element... define:jellybean Line.. 23 Column 27 Could not find class: com.foo.util.MyTask using ClassLoader: null and above that I get a Java stack track with java.lang.ClassNotFoundException... The class is indeed in my project and I built the project (java:compile) before running my goal below (I thought I'd run it interactively first to get it working before attached to a preGoal or whatever). Have you got any examples or people doing a similar thing? Cheers, Arnaud HERITIER wrote: Your jelly code seems wrong. You have to declare your namespace in the tag project : project xmlns:j=jelly:core xmlns:u=jelly:util xmlns:x=jelly:xml xmlns:ant=jelly:ant xmlns:maven=jelly:maven... /project Your class is in your project ? Thus you have to build it before to call your goal (with the jar goal for example). I think that your classes are defined in the default classloader. Arnaud diyfiesta wrote: Hey Folks, Any tips / pointers for calling Java code from Jelly / Maven's maven.xml? I'm having classpath issues and don't want to expose it as a plugin, rather just call it from maven.xml... ta diyfiesta wrote: Hi Folks, I've writen a POJO to do something useful and wanted to use it as part of my build. So I thought I'd try and kick it off form the maven.xml. So, I did something similar to this; goal name=myGoal j:jelly xmlns:j=jelly:core xmlns:define=jelly:define xmlns:my=myTag define:taglib uri=myTag define:jellybean name=foo className=com.foo.MyTask method=execute/ /define:taglib my:foo x=x outputDir=docs / /j:jelly /goal But I get ClassNotFoundException for com.foo.MyTask, which I guess is reasonable as I havn't set the classpath. I spotted you can add a Classloader attribute to the jellybean element, but I wouldn't know what to set this to... So, can I call Java from maven.xml or do I have to create a new plugin? I don't want to create a new maven plugin if I can help it (I want this utility class as part of my application rather than a seperate source tree). Thanks in advance, -- Toby -- View this message in context: http://www.nabble.com/%7Bm1%7D-running-java-from-maven.xml-tf3022149s177.html#a8447001 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: {m1} running java from maven.xml
hmmm, in the partial listing below, for namespaces I have; xmlns:j=jelly:core xmlns:define=jelly:define declared, is that all I need? I've moved this to project with the same results. It seems to run ok (no problems with namespaces I mean), as I say, the error is a classpath one when running it (see below). BUILD FAILED File.. C:\workspaces\spikes\...\maven.xml Element... define:jellybean Line.. 23 Column 27 Could not find class: com.foo.util.MyTask using ClassLoader: null and above that I get a Java stack track with java.lang.ClassNotFoundException... The class is indeed in my project and I built the project (java:compile) before running my goal below (I thought I'd run it interactively first to get it working before attached to a preGoal or whatever). Have you got any examples or people doing a similar thing? Cheers, Arnaud HERITIER wrote: Your jelly code seems wrong. You have to declare your namespace in the tag project : project xmlns:j=jelly:core xmlns:u=jelly:util xmlns:x=jelly:xml xmlns:ant=jelly:ant xmlns:maven=jelly:maven... /project Your class is in your project ? Thus you have to build it before to call your goal (with the jar goal for example). I think that your classes are defined in the default classloader. Arnaud diyfiesta wrote: Hey Folks, Any tips / pointers for calling Java code from Jelly / Maven's maven.xml? I'm having classpath issues and don't want to expose it as a plugin, rather just call it from maven.xml... ta diyfiesta wrote: Hi Folks, I've writen a POJO to do something useful and wanted to use it as part of my build. So I thought I'd try and kick it off form the maven.xml. So, I did something similar to this; goal name=myGoal j:jelly xmlns:j=jelly:core xmlns:define=jelly:define xmlns:my=myTag define:taglib uri=myTag define:jellybean name=foo className=com.foo.MyTask method=execute/ /define:taglib my:foo x=x outputDir=docs / /j:jelly /goal But I get ClassNotFoundException for com.foo.MyTask, which I guess is reasonable as I havn't set the classpath. I spotted you can add a Classloader attribute to the jellybean element, but I wouldn't know what to set this to... So, can I call Java from maven.xml or do I have to create a new plugin? I don't want to create a new maven plugin if I can help it (I want this utility class as part of my application rather than a seperate source tree). Thanks in advance, -- Toby -- View this message in context: http://www.nabble.com/%7Bm1%7D-running-java-from-maven.xml-tf3022149s177.html#a8446907 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
acegi-security dependency to spring
hi, how can i override the acegi-security dependency on spring 1.2.8 to a higher value, say 2.0.2? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: acegi-security dependency to spring
Maven use a dependency conflit resolution based on nearer dependencies : if your project depends on acegi, that depends on spring 1.2.8, 1.2.8 is a second level dependency. if your project also set dependency on spring 2.0.2, 2.0.2 is a 'first level dependency and will be used. Nico. 2007/1/19, Peter Mihalik [EMAIL PROTECTED]: hi, how can i override the acegi-security dependency on spring 1.2.8 to a higher value, say 2.0.2? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: acegi-security dependency to spring
sure, i know that. but my project has a dependency on spring but does not have a dependency on spring-remoting which acegi has so i get a app containing spring-2.0.2 jar and some spring-something-1.2.8 jars i know about 2 options to resolve this: 1/ exclude the acegi dependencies and everything will be ok, because of the spring dependency which covers all the acegi ones 2/ remove my spring dep and add some spring-all_the_things_i_need and spring_all_the_things_acegi_needs deps and i will get only v. 2.0.2 spring jars so my questions are: is there a way to say maven that spring.jar covers all the spring-something.jar s or is there a way to override the version of acegi spring dependencies? nicolas de loof wrote: Maven use a dependency conflit resolution based on nearer dependencies : if your project depends on acegi, that depends on spring 1.2.8, 1.2.8 is a second level dependency. if your project also set dependency on spring 2.0.2, 2.0.2 is a 'first level dependency and will be used. Nico. 2007/1/19, Peter Mihalik [EMAIL PROTECTED]: hi, how can i override the acegi-security dependency on spring 1.2.8 to a higher value, say 2.0.2? - 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]
Jboss:deploy behaviour
Hi, I'm trying to use the jboss:deploy goal to deploy my latest .ear file and am finding the following behaviour: When I start jboss (outside of maven) and do jboss:deploy I get an error message returned from the server (http 500). I then do jboss:undeploy which executes ok but seems to have no effect on jboss. I then do jboss:deploy again which deploys correctly. I can then do deploy as many times as I like and it works. This seems a little strange to me Is this expected behaviour or am I doing something wrong? Thanks, Nathan Jboss v. 4.05 Maven v. 2.04 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven2 maven-release-plugin release:prepare - changing current dir for scm operations
I am using svn. My project structure on disk: dir myproject dir myproject/design dir myproject/impl file myproject/impl/pom.xml dir myproject/impl/src ... How is the above structure mapped in svn: myproject/trunk/impl The reason for such mapping is that svn contains some other things (design dir) apart from standard project maven structure. The problem is: when I use the maven-release-plugin, the maven working directory is impl (because pom is in impl) and all svn operations use dot for source when using 'svn copy' ('svn copy . .../myproject/tags/0.1'). This does not work for me, because it puts in tag only content of the impl dir, not content of the myproject dir. Can I somehow persuade the plugin to use parent project for svn operations? -- View this message in context: http://www.nabble.com/Maven2-maven-release-plugin-release%3Aprepare---changing-current-dir-for-scm-operations-tf3039641s177.html#a8448312 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: acegi-security dependency to spring
The only override mecanism is the nearer dependency resolution. I discourage using the spring(full) jar as you will get such conflicts. Make a dependency on a top level spring-xxx-2.0.2 that will import other necessary spring artifacts with correct version. For unexpected artifact from acegi, use exclusions. Acegi POM should refer to spring-remoting dependency as optional, so you may post on acegi forum about this. 2007/1/19, Peter Mihalik [EMAIL PROTECTED]: sure, i know that. but my project has a dependency on spring but does not have a dependency on spring-remoting which acegi has so i get a app containing spring-2.0.2 jar and some spring-something-1.2.8 jars i know about 2 options to resolve this: 1/ exclude the acegi dependencies and everything will be ok, because of the spring dependency which covers all the acegi ones 2/ remove my spring dep and add some spring-all_the_things_i_need and spring_all_the_things_acegi_needs deps and i will get only v. 2.0.2 spring jars so my questions are: is there a way to say maven that spring.jar covers all the spring-something.jar s or is there a way to override the version of acegi spring dependencies? nicolas de loof wrote: Maven use a dependency conflit resolution based on nearer dependencies : if your project depends on acegi, that depends on spring 1.2.8, 1.2.8 is a second level dependency. if your project also set dependency on spring 2.0.2, 2.0.2 is a 'first level dependency and will be used. Nico. 2007/1/19, Peter Mihalik [EMAIL PROTECTED]: hi, how can i override the acegi-security dependency on spring 1.2.8 to a higher value, say 2.0.2? - 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]
RE: Maven2 maven-release-plugin release:prepare - changing current dir for scm operations
Hi, davy123 wrote on Friday, January 19, 2007 1:39 PM: I am using svn. My project structure on disk: dir myproject dir myproject/design dir myproject/impl file myproject/impl/pom.xml dir myproject/impl/src ... How is the above structure mapped in svn: myproject/trunk/impl The reason for such mapping is that svn contains some other things (design dir) apart from standard project maven structure. The problem is: when I use the maven-release-plugin, the maven working directory is impl (because pom is in impl) and all svn operations use dot for source when using 'svn copy' ('svn copy . .../myproject/tags/0.1'). This does not work for me, because it puts in tag only content of the impl dir, not content of the myproject dir. Can I somehow persuade the plugin to use parent project for svn operations? No, because the pom.xml must reside in the root of a project. Perfoming the release Maven checks out from the generated tag and rund an embedded build from that directory (this ensures that you build from the tagged sources). The only option you have is to move the pom.xml one level above and configure the paths in the pom to use that impl/xxx directory structure. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] subversion repository upload using webdav
Hi, (crossposting to users@maven.apache.org and maven-wagon-users) as Brett Porter suggested (/Storing your Maven Repository in CVS/Subversion, /http://blogs.codehaus.org/people/brett/archives/001066_storing_your_maven_repository_in_cvssubversion.html) I would like to maintain the corporate maven repositories of my company in our subversion system. My questions are: -- Does anyone succeeded to configure m2 (and subversion) to upload artifacts in a subversion repository using the maven webdav support? -- Are there any preconditions on the subversion installation? -- Are there any related open bugs? -- Any common pitfalls? I appreciate any hints. (In case it works I will provide a corresponding wiki page. :)) Best regards, Alex
[m2] subversion repository upload using webdav
Hi, (crossposting to and maven-wagon-users) as Brett Porter suggested (Storing your Maven Repository in CVS/Subversion, http://blogs.codehaus.org/people/brett/archives/001066_storing_your_maven_repository_in_cvssubversion.html http://blogs.codehaus.org/people/brett/archives/001066_storing_your_maven_repository_in_cvssubversion.html) I would like to maintain the corporate maven repositories of my company in our subversion system. My questions are: -- Does anyone succeeded to configure m2 (and subversion) to upload artifacts to a subversion repository using the maven webdav support? -- Are there any preconditions on the subversion installation? -- Are there any related open bugs? -- Any common pitfalls? I appreciate any hints. (In case it works I will provide a corresponding wiki page. :)) Best regards, Alex
Profile property is not resolved
I have a parent Maven project which has 3 modules. In an active profile I define 3 properties. When I do a reactor build, the modules build correctly. When I try to build the modules separately, the properties which I defined in the profile are not resolved. Here is what I tried to do to solve this: * Create a properties block in the parent project with properties name${name}/name !--where name is defined in the profile-- /properties * Create a properties block in the module project with properties name${name}/name !--where name is defined in the profile and the parent project-- /properties Both options failed. Please suggest what I could do or whether you think this is a bug. Thanks. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
[m2] BUILD ERROR maven-changelog-plugin does not exist
I got this error, what is wrong? [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-changelog-plugin' does not exist or no valid version could be found [INFO] I have this configuration plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId configuration typerange/type range90/range /configuration /plugin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Collecting ant build results with maven into an ear
Hello fellow maven users, I'm stuck with a legacy application that is built with ant and uses lots of custom ant tasks. There is no time to create maven plugins for this legacy project instead. Anyway.. The project I'm working on consists of two major artifacts. - one ear with the legacy application (client) - one ear with our new application (server) I would like to build them together with maven, so i created a POM-packaged parent and seperate child modules for the new stuff and one child module for the legacy application. I use the antrun plugin to build the legacy ear, which seems to work just fine.. The next step is to tell maven to recognize the ear that is produced by the ant build as a regular maven artifact and install it in the maven repository. Another possibility might be to produce the contents of the ear, but not yet package it, so maven can package it and install the ear artifact in the repo. Any ideas? I'm kind of in the dark here.. PS. Maven 2.0.4 Thanks! Jo
RE: [m2] BUILD ERROR maven-changelog-plugin does not exist
Put this in the pom.xml. pluginRepositories ... pluginRepository idapache.snapshots/id urlhttp://people.apache.org/maven-snapshot-repository//url /pluginRepository /pluginRepositories In the reporting section of your pom.xml: reporting ... plugins ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId version2.0-SNAPSHOT/version /plugin /plugins /reporting That worked for me. Apparently the changelog plugin has not been released which is why it is not in the main maven repository. - Tom -Original Message- From: Riboe, Jens [mailto:[EMAIL PROTECTED] Sent: Friday, January 19, 2007 8:30 AM To: Maven Users List Subject: [m2] BUILD ERROR maven-changelog-plugin does not exist I got this error, what is wrong? [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-changelog-plugin' does not exist or no valid version could be found [INFO] I have this configuration plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId configuration typerange/type range90/range /configuration /plugin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] == This communication, together with any attachments hereto or links contained herein, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments hereto or links herein, from your system. == The St. Paul Travelers e-mail system made this annotation on 01/19/07, 09:41:11. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] SCM support for sspi?
We use SSPI to connect to our CVS repository, which does not seem to work with Maven2's SCM plugin. It is not mentioned as a supported protocol in the SCM plugin docs, and I found nothing in the list archives nor an issue in JIRA. When I tried, I just got this exception: org.apache.maven.scm.repository.ScmRepositoryException: The scm url is invalid. The relevant section of my POM is: scm connectionscm:cvs:sspi:myserver/repository/pm/productmachine/connection /scm (I tried developerConnection as well). Is it true that SSPI connections to CVS are not currently supported? If so, are there any plans to support SSPI? Does anyone have a work-around they could recommend (I'm not very experienced with CVS administration)? -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Collecting ant build results with maven into an ear
you can attach the final Ant ear artifact to maven project so that it can be installed/deployed as normal maven artifacts using build-helper-maven-plugin. The draw back is the deployed pom has pom packaging. I dont know what would be the impact http://mojo.codehaus.org/build-helper-maven-plugin -Dan On 1/19/07, Jo Vandermeeren [EMAIL PROTECTED] wrote: Hello fellow maven users, I'm stuck with a legacy application that is built with ant and uses lots of custom ant tasks. There is no time to create maven plugins for this legacy project instead. Anyway.. The project I'm working on consists of two major artifacts. - one ear with the legacy application (client) - one ear with our new application (server) I would like to build them together with maven, so i created a POM-packaged parent and seperate child modules for the new stuff and one child module for the legacy application. I use the antrun plugin to build the legacy ear, which seems to work just fine.. The next step is to tell maven to recognize the ear that is produced by the ant build as a regular maven artifact and install it in the maven repository. Another possibility might be to produce the contents of the ear, but not yet package it, so maven can package it and install the ear artifact in the repo. Any ideas? I'm kind of in the dark here.. PS. Maven 2.0.4 Thanks! Jo
Re: Adding Logo In My Site
Post a bug in JIRA or it will (most likely) never happen. Wayne On 1/19/07, Subhash Chandran [EMAIL PROTECTED] wrote: Thanks, I got the poweredBy syntax from here: http://svn.sourceforge.net/viewvc/spring-rich-c/trunk/spring-richclient/src/site/site.xml?revision=1633view=markup But why is this not explained here: http://maven.apache.org/guides/mini/guide-site.html I think someone needs to update this. Subhash. On 1/19/07, Geoffrey De Smet [EMAIL PROTECTED] wrote: poweredBy will probably be more what you want, so it's like the spring and sourceforge icon on http://spring-rich-c.sourceforge.net/ Jiaqi Guo schreef: Subhash Chandran wrote: Hi, I host my project with BerliOS.de. They have provided this code for placing the logo in my site: a href=http://developer.berlios.de; img src=http://developer.berlios.de/bslogo.php?group_id=0; width=124 height=32 border=0 alt=BerliOS Logo //a https://developer.berlios.de/docman/display_doc.php?docid=55group_id=2 Is there any possibility of getting this generated in APT? Try adding this into src/site/site.xml. project bannerLeft nameBerliOS.de/name srchttp://developer.berlios.de/bslogo.php?group_id=0/src hrefhttp://developer.berlios.de/href /bannerLeft body links ... ... Good luck - Jiaqi Guo http://www.cyclopsgroup.org -- With kind regards, Geoffrey De Smet - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] SCM support for sspi?
It isn't supported because it isn't a standard cvs protocol. If you have docs about the CVSROOT format for this protocol, file an issue and we'll look at it. All docs about sspi are welcome. Emmanuel Siegmann Daniel, NY a écrit : We use SSPI to connect to our CVS repository, which does not seem to work with Maven2's SCM plugin. It is not mentioned as a supported protocol in the SCM plugin docs, and I found nothing in the list archives nor an issue in JIRA. When I tried, I just got this exception: org.apache.maven.scm.repository.ScmRepositoryException: The scm url is invalid. The relevant section of my POM is: scm connectionscm:cvs:sspi:myserver/repository/pm/productmachine/connection /scm (I tried developerConnection as well). Is it true that SSPI connections to CVS are not currently supported? If so, are there any plans to support SSPI? Does anyone have a work-around they could recommend (I'm not very experienced with CVS administration)? -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - 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]
Re: Adding Logo In My Site
FYI: http://jira.codehaus.org/browse/MPSITE-57 Subhash. On 1/19/07, Wayne Fay [EMAIL PROTECTED] wrote: Post a bug in JIRA or it will (most likely) never happen. Wayne On 1/19/07, Subhash Chandran [EMAIL PROTECTED] wrote: Thanks, I got the poweredBy syntax from here: http://svn.sourceforge.net/viewvc/spring-rich-c/trunk/spring-richclient/src/site/site.xml?revision=1633view=markup But why is this not explained here: http://maven.apache.org/guides/mini/guide-site.html I think someone needs to update this. Subhash. On 1/19/07, Geoffrey De Smet [EMAIL PROTECTED] wrote: poweredBy will probably be more what you want, so it's like the spring and sourceforge icon on http://spring-rich-c.sourceforge.net/ Jiaqi Guo schreef: Subhash Chandran wrote: Hi, I host my project with BerliOS.de. They have provided this code for placing the logo in my site: a href=http://developer.berlios.de; img src=http://developer.berlios.de/bslogo.php?group_id=0; width=124 height=32 border=0 alt=BerliOS Logo //a https://developer.berlios.de/docman/display_doc.php?docid=55group_id=2 Is there any possibility of getting this generated in APT? Try adding this into src/site/site.xml. project bannerLeft nameBerliOS.de/name srchttp://developer.berlios.de/bslogo.php?group_id=0/src hrefhttp://developer.berlios.de/href /bannerLeft body links ... ... Good luck - Jiaqi Guo http://www.cyclopsgroup.org -- With kind regards, Geoffrey De Smet - 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] - 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]
Setting up Maven with archiva
We are trying to setup archiva with maven. We are able to setup some proxy repositories successfully for all the external (internet) repositories we are using. However, there is a place where we are using a dependency whose pom.xml has a external repository defined. But, this is still one of the proxy repos we have configured. Also, we have set up a global mirror setting of all the URLs to route via our proxy, like the one below mirror idmirror-central/id nameMirror/name urlhttp://localhost:8080/proxy/test//url mirrorOf*/mirrorOf /mirror But, when I run the maven build, the dependency tries to get another pom file directly from internet site and fails. Doesn't go through the mirror settings we have configured in our setting.xml. Is there anything I am missing in my configuration. Regards, Rohit Sharma GDC Contractor - Infosys Tech Ltd. London, UK Desk: (+44) 207 174 5352 mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority.
Re: Setting up Maven with archiva
I'm not using mirrors right now so I may be incorrect here... But I'm wondering where you got that mirrorOf*/ syntax? I've never seen it before and assume it is wrong. Wayne On 1/19/07, Sharma, Rohit [EMAIL PROTECTED] wrote: We are trying to setup archiva with maven. We are able to setup some proxy repositories successfully for all the external (internet) repositories we are using. However, there is a place where we are using a dependency whose pom.xml has a external repository defined. But, this is still one of the proxy repos we have configured. Also, we have set up a global mirror setting of all the URLs to route via our proxy, like the one below mirror idmirror-central/id nameMirror/name urlhttp://localhost:8080/proxy/test//url mirrorOf*/mirrorOf /mirror But, when I run the maven build, the dependency tries to get another pom file directly from internet site and fails. Doesn't go through the mirror settings we have configured in our setting.xml. Is there anything I am missing in my configuration. Regards, Rohit Sharma GDC Contractor - Infosys Tech Ltd. London, UK Desk: (+44) 207 174 5352 mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Setting up Maven with archiva
http://maven.apache.org/guides/mini/guide-mirror-settings.html But available only from 2.0.5 :-(. Regards, Rohit Sharma GDC Contractor - Infosys Tech Ltd. London, UK Desk: (+44) 207 174 5352 mailto: [EMAIL PROTECTED] -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: 19 January 2007 16:41 To: Maven Users List Subject: Re: Setting up Maven with archiva I'm not using mirrors right now so I may be incorrect here... But I'm wondering where you got that mirrorOf*/ syntax? I've never seen it before and assume it is wrong. Wayne On 1/19/07, Sharma, Rohit [EMAIL PROTECTED] wrote: We are trying to setup archiva with maven. We are able to setup some proxy repositories successfully for all the external (internet) repositories we are using. However, there is a place where we are using a dependency whose pom.xml has a external repository defined. But, this is still one of the proxy repos we have configured. Also, we have set up a global mirror setting of all the URLs to route via our proxy, like the one below mirror idmirror-central/id nameMirror/name urlhttp://localhost:8080/proxy/test//url mirrorOf*/mirrorOf /mirror But, when I run the maven build, the dependency tries to get another pom file directly from internet site and fails. Doesn't go through the mirror settings we have configured in our setting.xml. Is there anything I am missing in my configuration. Regards, Rohit Sharma GDC Contractor - Infosys Tech Ltd. London, UK Desk: (+44) 207 174 5352 mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] subversion repository upload using webdav
i have used wagon-scm (only implemented with subversion) although I'd say is alpha/beta quality, never tried wagon-webdav for svn On 1/19/07, Alexander Schwartz [EMAIL PROTECTED] wrote: Hi, (crossposting to users@maven.apache.org and maven-wagon-users) as Brett Porter suggested (/Storing your Maven Repository in CVS/Subversion, /http://blogs.codehaus.org/people/brett/archives/001066_storing_your_maven_repository_in_cvssubversion.html) I would like to maintain the corporate maven repositories of my company in our subversion system. My questions are: -- Does anyone succeeded to configure m2 (and subversion) to upload artifacts in a subversion repository using the maven webdav support? -- Are there any preconditions on the subversion installation? -- Are there any related open bugs? -- Any common pitfalls? I appreciate any hints. (In case it works I will provide a corresponding wiki page. :)) Best regards, Alex -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting up Maven with archiva
Well that explains it! You can pull 2.0.5 from trunk and build it yourself, if you really need that functionality today. Wayne On 1/19/07, Sharma, Rohit [EMAIL PROTECTED] wrote: http://maven.apache.org/guides/mini/guide-mirror-settings.html But available only from 2.0.5 :-(. Regards, Rohit Sharma GDC Contractor - Infosys Tech Ltd. London, UK Desk: (+44) 207 174 5352 mailto: [EMAIL PROTECTED] -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: 19 January 2007 16:41 To: Maven Users List Subject: Re: Setting up Maven with archiva I'm not using mirrors right now so I may be incorrect here... But I'm wondering where you got that mirrorOf*/ syntax? I've never seen it before and assume it is wrong. Wayne On 1/19/07, Sharma, Rohit [EMAIL PROTECTED] wrote: We are trying to setup archiva with maven. We are able to setup some proxy repositories successfully for all the external (internet) repositories we are using. However, there is a place where we are using a dependency whose pom.xml has a external repository defined. But, this is still one of the proxy repos we have configured. Also, we have set up a global mirror setting of all the URLs to route via our proxy, like the one below mirror idmirror-central/id nameMirror/name urlhttp://localhost:8080/proxy/test//url mirrorOf*/mirrorOf /mirror But, when I run the maven build, the dependency tries to get another pom file directly from internet site and fails. Doesn't go through the mirror settings we have configured in our setting.xml. Is there anything I am missing in my configuration. Regards, Rohit Sharma GDC Contractor - Infosys Tech Ltd. London, UK Desk: (+44) 207 174 5352 mailto: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority. - 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]
Re: Maven 2 mirror on downloads.planetmirror.com
Carlos, thanks for removing the planetmirror mirror from the list, but you might also notice it is still there on the page in the section above the list demonstrating how to set up a mirror: http://maven.apache.org/guides/mini/guide-mirror-settings.html Ideally we'd swap that out with ibiblio, lsu, etc. Or else I'm afraid this issue will pop up again in the (near) future on this list. Wayne On 1/10/07, Carlos Sanchez [EMAIL PROTECTED] wrote: Removed from the M2 page of mirrors On 1/10/07, Wayne Fay [EMAIL PROTECTED] wrote: Until these issues are cleared up, the Maven team should remove the site from their list of available mirrors. It would save a lot of headaches! I'll go open a JIRA issue for this unless one is already there. Wayne On 1/9/07, Stephen Coy [EMAIL PROTECTED] wrote: Hi, After following the trials and tribulations of JavierL earlier today, I recalled that I had experienced the same problems some time go. The so-called maven 2 mirror at http://downloads.planetmirror.com/ pub/maven2 is wrapped in pretty html which essentially kills any kind of automated download process. The download result corrupts your local repository. Use this mirror at your peril. Steve C. - 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] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - 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]
AspectJ and Eclipse plugin: Support of aspect libraries
Hi, I created a library (let's call it project-a) to provide aspects (AspectJ is meant here) to other modules. To use that library as an aspect library I would create a pom for some project-b as follows: ?xml version=1.0? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdsandbox/groupId artifactIdproject-b/artifactId packagingjar/packaging version1.0-SNAPSHOT/version nameproject-b/name dependencies dependency groupIdaspectj/groupId artifactIdaspectjrt/artifactId version[1.5,)/version /dependency dependency groupIdsandbox/groupId artifactIdproject-a/artifactId version1.0-SNAPSHOT/version /dependency dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies build plugins plugin artifactIdmaven-eclipse-plugin/artifactId configuration additionalProjectnatures projectnatureorg.eclipse.ajdt.ui.ajnature/projectnature /additionalProjectnatures buildcommands buildcommandorg.eclipse.ajdt.core.ajbuilder/buildcommand /buildcommands /configuration /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdaspectj-maven-plugin/artifactId configuration aspectLibraries aspectLibrary groupIdsandbox/groupId artifactIdproject-a/artifactId /aspectLibrary /aspectLibraries complianceLevel1.5/complianceLevel /configuration executions execution goals goalcompile/goal goaltest-compile/goal /goals /execution /executions /plugin /plugins /build /project Then I would like to use eclipse to work on project-b. so I set it up using the eclipse plugin. That works fine except for configuring project-a as an aspect library. This causes no aspects to be woven into classes of project-b. Did I miss something in setting up my poms? thanks in advance for any hints! -Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] where do i put hibernate-properties-ProviderHistory.xml to get merged?
Can someone please help me as I can't find this info anywhere... I am using xdoclet 1, not xdoclet2 On 1/18/07, Mick Knutson [EMAIL PROTECTED] wrote: I am still using XDoclet 1 and want to create an entry for hibernate-properties-ProviderHistory.xml but am not sure where to put that file to get picked up during a merge... Can anyone please help ? -- Thanks DJ MICK (Mick Knutson) http://www.djmick.com http://www.myspace.com/djmick_dot_com http://www.thumpradio.com -- Thanks DJ MICK (Mick Knutson) http://www.djmick.com http://www.myspace.com/djmick_dot_com http://www.thumpradio.com
Maven2 (and plugins) need to be released frequently to make maven interesting
My project is using maven2 and the release plugin. However, the release plugin only works with released plugins (otherwise, our release builds are not reproducible). We've had to locally patch a half-dozen plugins just to mark them as released just in order to be able to do a release build of our project. Furthermore, there are many core and non-core plugins that have plenty of bugs fixed that we still experience today in their SNAPSHOTs. But we can't use these. There is no shortage of numbers in the world. What is the problem with releasing often? So what if a bug occasionally gets its way into a release -- you can always specify an older version of a plugin that didn't have some new bug. True, a lot of plugins are under 3rd party control and not part of the core maven. But if the core maven team starts releasing more often and understands why releases are important, many of the 3rd parties will follow suit. Right now maven seems more like a toy and is constantly frustrating when trying to use it on a real project (due largely to known bugs many of which have been fixed in SNAPSHOTs for over 6-months now and/ or several plugins that have produced SNAPSHOT builds but no released version). BTW, My project releases weekly. So far we have 0.5-rc1, 0.5-rc2, 0.5- rc3, ... 0.5-rc9. And we have SNAPSHOTs in between that we never deploy to production but which developers work with. Cheers, Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Weird classpath problem (servlet-api)
Hi All, I have a web application which uses Maven2. It was working fine until I started to add additional features which requires more 3rd-party libraries. After I added these libraries to my dependency list, Maven couldn't compile the application because servlet-api was not on the classpath anymore. But servlet-api is still in my dependency list and its scope is set to provided. If I remove these libraries, servlet-api will again get back to the classpath. And it seems this is not related to a particular library. It is completely random. It will get to a point that servlet-api will get removed when I add a random library to the dependency list. I am completely lost and frustrated. Could someone please help me? Thanks much! Kenny pgpWxWJgZM9q5.pgp Description: signature
Re: categorizing tests
On 1/18/07, Jiaqi Guo [EMAIL PROTECTED] wrote: Dmitry Beransky wrote: Just finished reading an article on test categorization: http://www-128.ibm.com/developerworks/java/library/j-cq10316/index.html?ca=drs-. Any recommendations how how to implement this in Maven? Although I don't 100% percent agree with the article, I believe technically multiple test case file pattern can be defined for each sunfire-plugin in multiple profiles. Thanks, that's an interesting idea and got me thinking... Ideally, I wish I could annotate tests with a type (e.g. @Test(type=component) public void testSomeFunction() {...}) and have the test framework pick the tests out for me. Lacking above, it's probably a good idea to break tests into multiple directories based on their type (could be a good idea regardless), and then simply modify test source directory based on the same system property your recommended: build testSourceDirectorysrc/test/java/${test.category}/testSourceDirectory /build can I define a default value for ${test.category} in POM and then override it at runtime with -Dtest.category=value? or is profiles still a preferred way of approaching this and if so, why? thanks d. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FtpWagon.java error
Hi, I'm getting an NullPointerException error FtpWagon.java when I execute the following maven command, mvn clean antrun:run install. It seems that the plugin is not reading my settings.xml. I have the csdpRepository id defined inside the settings.xml.I've searched in google for FtpWagon.java error, but the solution offered doesn't seem to work, at least for me. Any help is greatly appreciated. Thanks. repositories repository idcspdRepository/id nameCSDP Repository/name url ftp://ausgsa.austin.ibm.com/projects/c/csdpbuildrepository/maven/repository /url /repository /repositories settings.xml: server idcsdpRepository/id usernameegaona/username passwordpassword/password /server [EMAIL PROTECTED] prereq.kb]# mvn clean antrun:run install [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'antrun'. [INFO] [INFO] Building KB Prerequisite Files [INFO]task-segment: [clean, antrun:run, install] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /build/continuum/app/working-directory/1/com.ibm.mbps.i2c.ui/I2CProject/prereqs/prereq.kb/target [INFO] Deleting directory /build/continuum/app/working-directory/1/com.ibm.mbps.i2c.ui/I2CProject/prereqs/prereq.kb/target/classes [INFO] Deleting directory /build/continuum/app/working-directory/1/com.ibm.mbps.i2c.ui/I2CProject/prereqs/prereq.kb/target/test-classes [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection(FtpWagon.java:127) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:354) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:282) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:244) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:124) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:467) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:225) at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:102) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:275) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:67) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:182) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1117) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:366) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at
Re: Maven 2 mirror on downloads.planetmirror.com
done On 1/19/07, Wayne Fay [EMAIL PROTECTED] wrote: Carlos, thanks for removing the planetmirror mirror from the list, but you might also notice it is still there on the page in the section above the list demonstrating how to set up a mirror: http://maven.apache.org/guides/mini/guide-mirror-settings.html Ideally we'd swap that out with ibiblio, lsu, etc. Or else I'm afraid this issue will pop up again in the (near) future on this list. Wayne On 1/10/07, Carlos Sanchez [EMAIL PROTECTED] wrote: Removed from the M2 page of mirrors On 1/10/07, Wayne Fay [EMAIL PROTECTED] wrote: Until these issues are cleared up, the Maven team should remove the site from their list of available mirrors. It would save a lot of headaches! I'll go open a JIRA issue for this unless one is already there. Wayne On 1/9/07, Stephen Coy [EMAIL PROTECTED] wrote: Hi, After following the trials and tribulations of JavierL earlier today, I recalled that I had experienced the same problems some time go. The so-called maven 2 mirror at http://downloads.planetmirror.com/ pub/maven2 is wrapped in pretty html which essentially kills any kind of automated download process. The download result corrupts your local repository. Use this mirror at your peril. Steve C. - 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] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - 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] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] subversion repository upload using webdav
wagon-webdav is only for level 1 dav servers. in other words, it is not for subversion. If you want to use subversion as a repository, something I highly *discourage*, use the wagon-scm provider. - Joakim Erdfelt Alexander Schwartz wrote: Hi, (crossposting to and maven-wagon-users) as Brett Porter suggested (Storing your Maven Repository in CVS/Subversion, http://blogs.codehaus.org/people/brett/archives/001066_storing_your_maven_repository_in_cvssubversion.html http://blogs.codehaus.org/people/brett/archives/001066_storing_your_maven_repository_in_cvssubversion.html) I would like to maintain the corporate maven repositories of my company in our subversion system. My questions are: -- Does anyone succeeded to configure m2 (and subversion) to upload artifacts to a subversion repository using the maven webdav support? -- Are there any preconditions on the subversion installation? -- Are there any related open bugs? -- Any common pitfalls? I appreciate any hints. (In case it works I will provide a corresponding wiki page. :)) Best regards, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: categorizing tests
Dmitry Beransky wrote: Ideally, I wish I could annotate tests with a type (e.g. @Test(type=component) public void testSomeFunction() {...}) and have the test framework pick the tests out for me. Lacking above, it's probably a good idea to break tests into multiple directories based on their type (could be a good idea regardless), and then simply modify test source directory based on the same system property your recommended: build testSourceDirectorysrc/test/java/${test.category}/testSourceDirectory /build can I define a default value for ${test.category} in POM and then override it at runtime with -Dtest.category=value? or is profiles still a preferred way of approaching this and if so, why? thanks d. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Hi Dmitry, If you want to categorize the tests with your own Annotation, you will definitely need to write you own plugin to run these test cases since sunfire-plugin has no knowledge of those Annotations. Then it would be problem to make plugins like clover to work with your own test plugin. The testSourceDirectory is sort of coded in maven-model (http://svn.apache.org/repos/asf/maven/components/trunk/maven-model/maven.mdo), it could be a mess to change it and add multiple test source directories into POM model. This left the profile the only option that I could come up with. Even within a profile, you can't define a different testSourceDirectory according to http://maven.apache.org/guides/introduction/introduction-to-profiles.html. So I had to make the categorization base on file pattern. In my example code, without specifying -Dtest.category, no profile will be activated, so the build directly under project will count in that case. Best regards -- Jiaqi Guo http://www.cyclopsgroup.org [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FtpWagon.java error
What is the version of your wagon-ftp? Thanks Enrique Gaona wrote: Hi, I'm getting an NullPointerException error FtpWagon.java when I execute the following maven command, mvn clean antrun:run install. It seems that the plugin is not reading my settings.xml. I have the csdpRepository id defined inside the settings.xml.I've searched in google for FtpWagon.java error, but the solution offered doesn't seem to work, at least for me. Any help is greatly appreciated. Thanks. repositories repository idcspdRepository/id nameCSDP Repository/name url ftp://ausgsa.austin.ibm.com/projects/c/csdpbuildrepository/maven/repository /url /repository /repositories settings.xml: server idcsdpRepository/id usernameegaona/username passwordpassword/password /server [EMAIL PROTECTED] prereq.kb]# mvn clean antrun:run install [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'antrun'. [INFO] [INFO] Building KB Prerequisite Files [INFO]task-segment: [clean, antrun:run, install] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /build/continuum/app/working-directory/1/com.ibm.mbps.i2c.ui/I2CProject/prereqs/prereq.kb/target [INFO] Deleting directory /build/continuum/app/working-directory/1/com.ibm.mbps.i2c.ui/I2CProject/prereqs/prereq.kb/target/classes [INFO] Deleting directory /build/continuum/app/working-directory/1/com.ibm.mbps.i2c.ui/I2CProject/prereqs/prereq.kb/target/test-classes [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.wagon.providers.ftp.FtpWagon.openConnection(FtpWagon.java:127) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:354) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:282) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:244) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:124) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:467) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:225) at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:102) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:275) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:67) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:182) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1117) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:366) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
Re: Maven2 (and plugins) need to be released frequently to make maven interesting
Eric Brown wrote: There is no shortage of numbers in the world. What is the problem with releasing often? So what if a bug occasionally gets its way into a release -- you can always specify an older version of a plugin that didn't have some new bug. True, a lot of plugins are under 3rd party control and not part of the core maven. But if the core maven team starts releasing more often and understands why releases are important, many of the 3rd parties will follow suit. Right now maven seems more like a toy and is constantly frustrating when trying to use it on a real project (due largely to known bugs many of which have been fixed in SNAPSHOTs for over 6-months now and/ or several plugins that have produced SNAPSHOT builds but no released version). I would like to second the motion... Over here, I'm constantly teetering on the edge of dropping maven altogether. I really really want to like it, but it is a hard sell to developers, especially if they have to end up writing ant tasks after all... -- cg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FtpWagon.java error
Jiaqi Guo [EMAIL PROTECTED] wrote on 01/19/2007 02:02:24 PM: What is the version of your wagon-ftp? Thanks Jiaqi, Here are the versions of the wagon jarfiles. Thanks wagon-file-1.0-alpha-7.jar wagon-ftp-1.0-alpha-6.jar wagon-http-lightweight-1.0-alpha-6.jar wagon-provider-api-1.0-alpha-6.jar wagon-ssh-1.0-alpha-7.jar wagon-ssh-external-1.0-alpha-6.jar Enrique Enrique Gaona wrote: Hi, I'm getting an NullPointerException error FtpWagon.java when I execute the following maven command, mvn clean antrun:run install. It seems that the plugin is not reading my settings.xml. I have the csdpRepository id defined inside the settings.xml.I've searched in google for FtpWagon.java error, but the solution offered doesn't seem to work, at least for me. Any help is greatly appreciated. Thanks. repositories repository idcspdRepository/id nameCSDP Repository/name url ftp://ausgsa.austin.ibm.com/projects/c/csdpbuildrepository/maven/repository /url /repository /repositories settings.xml: server idcsdpRepository/id usernameegaona/username passwordpassword/password /server [EMAIL PROTECTED] prereq.kb]# mvn clean antrun:run install [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'antrun'. [INFO] [INFO] Building KB Prerequisite Files [INFO]task-segment: [clean, antrun:run, install] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /build/continuum/app/working-directory/1/com.ibm.mbps.i2c. ui/I2CProject/prereqs/prereq.kb/target [INFO] Deleting directory /build/continuum/app/working-directory/1/com.ibm.mbps.i2c. ui/I2CProject/prereqs/prereq.kb/target/classes [INFO] Deleting directory /build/continuum/app/working-directory/1/com.ibm.mbps.i2c. ui/I2CProject/prereqs/prereq.kb/target/test-classes [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.wagon.providers.ftp.FtpWagon. openConnection(FtpWagon.java:127) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.artifact.manager.DefaultWagonManager. getRemoteFile(DefaultWagonManager.java:354) at org.apache.maven.artifact.manager.DefaultWagonManager. getArtifact(DefaultWagonManager.java:282) at org.apache.maven.artifact.manager.DefaultWagonManager. getArtifact(DefaultWagonManager.java:244) at org.apache.maven.artifact.resolver.DefaultArtifactResolver. resolve(DefaultArtifactResolver.java:124) at org.apache.maven.artifact.resolver.DefaultArtifactResolver. resolve(DefaultArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder. findModelFromRepository(DefaultMavenProjectBuilder.java:467) at org.apache.maven.project.DefaultMavenProjectBuilder. buildFromRepository(DefaultMavenProjectBuilder.java:225) at org.apache.maven.project.artifact.MavenMetadataSource. retrieve(MavenMetadataSource.java:102) at org.apache.maven.artifact.resolver.DefaultArtifactCollector. recurse(DefaultArtifactCollector.java:275) at org.apache.maven.artifact.resolver.DefaultArtifactCollector. collect(DefaultArtifactCollector.java:67) at org.apache.maven.artifact.resolver.DefaultArtifactResolver. resolveTransitively(DefaultArtifactResolver.java:223) at org.apache.maven.artifact.resolver.DefaultArtifactResolver. resolveTransitively(DefaultArtifactResolver.java:211) at org.apache.maven.artifact.resolver.DefaultArtifactResolver. resolveTransitively(DefaultArtifactResolver.java:182) at org.apache.maven.plugin.DefaultPluginManager. resolveTransitiveDependencies(DefaultPluginManager.java:1117) at org.apache.maven.plugin.DefaultPluginManager. executeMojo(DefaultPluginManager.java:366) at org.apache.maven.lifecycle.DefaultLifecycleExecutor. executeGoals(DefaultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor. executeStandaloneGoal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor. executeGoal(DefaultLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor. executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor. executeTaskSegments(DefaultLifecycleExecutor.java:273) at
Re: Maven2 (and plugins) need to be released frequently to make maven interesting
This was recently discussed on Maven Developer's list in the thread titled calling vote for 2.0.5. You are welcome to read that thread and get up to speed on various plans and issues related to more frequent releases. Wayne On 1/19/07, Christian Goetze [EMAIL PROTECTED] wrote: Eric Brown wrote: There is no shortage of numbers in the world. What is the problem with releasing often? So what if a bug occasionally gets its way into a release -- you can always specify an older version of a plugin that didn't have some new bug. True, a lot of plugins are under 3rd party control and not part of the core maven. But if the core maven team starts releasing more often and understands why releases are important, many of the 3rd parties will follow suit. Right now maven seems more like a toy and is constantly frustrating when trying to use it on a real project (due largely to known bugs many of which have been fixed in SNAPSHOTs for over 6-months now and/ or several plugins that have produced SNAPSHOT builds but no released version). I would like to second the motion... Over here, I'm constantly teetering on the edge of dropping maven altogether. I really really want to like it, but it is a hard sell to developers, especially if they have to end up writing ant tasks after all... -- cg - 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]
Plugin to find updated versions of dependencies?
I have a variety of dependencies declared in my largish J2EE project and I'm wondering if perhaps there's a plugin or something available that would run out to the Maven repo, check my declared dependencies and versions against those available in the repo, and let me know which ones seem to have updates available. Ideally it would produce a list like: groupId/artifactId --- my declared version -- other versions available xml-apis/xml-apis: 1.0.b2 [1.3.02, 1.3.03, 1.3.04] org.codehaus.woodstox/wstx-asl: 3.0.0 [3.0.1, 3.0.2, 3.0.3, 3.1.0, 3.1.1, 3.2.0] etc Obviously I can do this myself manually (and I do now and then) but it would be nice if this was available in an easy to use plugin available from the command line. I don't necessarily always want to use the latest and greatest version of all my dependencies, but if I've declared 3.0.0 and a new version 3.0.4 is available (with bugfixes etc) then I should probably know about it, test my app to make it doesn't break anything, and plan to include it in a future version of my app. If it doesn't already exist, I'll have to start looking into implementing this myself, I suppose. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin to find updated versions of dependencies?
Hi Wayne, On 19/01/07, Wayne Fay [EMAIL PROTECTED] wrote: I have a variety of dependencies declared in my largish J2EE project and I'm wondering if perhaps there's a plugin or something available that would run out to the Maven repo, check my declared dependencies and versions against those available in the repo, and let me know which ones seem to have updates available. Ideally it would produce a list like: groupId/artifactId --- my declared version -- other versions available xml-apis/xml-apis: 1.0.b2 [1.3.02, 1.3.03, 1.3.04] org.codehaus.woodstox/wstx-asl: 3.0.0 [3.0.1, 3.0.2, 3.0.3, 3.1.0, 3.1.1, 3.2.0] etc Obviously I can do this myself manually (and I do now and then) but it would be nice if this was available in an easy to use plugin available from the command line. I don't necessarily always want to use the latest and greatest version of all my dependencies, but if I've declared 3.0.0 and a new version 3.0.4 is available (with bugfixes etc) then I should probably know about it, test my app to make it doesn't break anything, and plan to include it in a future version of my app. If it doesn't already exist, I'll have to start looking into implementing this myself, I suppose. I don't believe such a plugin exists yet, but it would indeed be very handy. I'd suggest adding it to the dependency plugin after my recent thread regarding other dependency management goals [1]. Cheers, Mark [1] http://www.nabble.com/-m2--Adding-further-dependency-goals-tf3029137s177.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] subversion repository upload using webdav
Carlos Sanchez-4 wrote: i have used wagon-scm (only implemented with subversion) although I'd say is alpha/beta quality, never tried wagon-webdav for svn thank's for the hint. My first attempts to configure wagon-scm were not successful. I added the following to the pom.xml: ... distributionManagement snapshotRepository uniqueVersionfalse/uniqueVersion nameMy SVN Snapshot Repo/name idsvnrepo/id urlscm:svn:file:///H:/MySvnRepository/Playground/m2-repo/url /snapshotRepository /distributionManagement ... build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-scm/artifactId version1.0-beta-2-SNAPSHOT/version /extension extension groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-svnexe/artifactId version1.0-SNAPSHOT/version /extension /extensions The logs: [INFO] [deploy:deploy] altDeploymentRepository = null [INFO] Retrieving previous build number from svnrepo [INFO] Executing: svn --non-interactive checkout file:///H:/MySvnRepository/Playground/m2-repo/net/sf/jgabl2/net.sf.jgabl2.core/0.8.0-SNAPSHOT 0.8.0-SNAPSHOT [INFO] Working directory: e:\JavaDev\EclipseWorkspaces\workspace_3.2\net.sf.jgabl5\modules\core\target\checkout\net\sf\jgabl2\net.sf.jgabl2.core Uploading: scm:svn:file:///H:/MySvnRepository/Playground/m2-repo/net/sf/jgabl2/net.sf.jgabl2.core/0.8.0-SNAPSHOT/net.sf.jgabl2.core-0.8.0-SNAPSHOT.jar [INFO] Executing: svn --non-interactive list file:///H:/MySvnRepository/Playground/m2-repo/. [INFO] Working directory: f:\tmp [INFO] Executing: svn --non-interactive checkout file:///H:/MySvnRepository/Playground/m2-repo checkout [INFO] Working directory: e:\JavaDev\EclipseWorkspaces\workspace_3.2\net.sf.jgabl5\modules\core\target [INFO] Executing: svn add --non-recursive net.sf.jgabl2.core-0.8.0-SNAPSHOT.jar [INFO] Working directory: e:\JavaDev\EclipseWorkspaces\workspace_3.2\net.sf.jgabl5\modules\core\target\checkout [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unable to add file to SCM: target\checkout\net\sf\jgabl2\net.sf.jgabl2.core\0.8.0-SNAPSHOT\net.sf.jgabl2.core-0.8.0-SNAPSHOT.jar; see error messages above for more information I assume I did not configured it correctly, or there is a bug in wagon-scm. -- Alex -- View this message in context: http://www.nabble.com/-m2--subversion-repository-upload-using-webdav-tf3039813s177.html#a8457694 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] subversion repository upload using webdav
Joakim Erdfelt-2 wrote: wagon-webdav is only for level 1 dav servers. in other words, it is not for subversion. If you want to use subversion as a repository, something I highly *discourage*, use the wagon-scm provider. - Joakim Erdfelt thank's for the hint -- I will use wagon-scm. I know there are several good arguments *not* to store a repository using subversion. -- Alex -- View this message in context: http://www.nabble.com/-m2--subversion-repository-upload-using-webdav-tf3039847.html#a8457790 Sent from the Wagon - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: APT Images With URL
Subhash Chandran wrote: The APT format guide here: http://maven.apache.org/guides/mini/guide-apt-format.html speaks only of image display. This is done like: [path/to/image.ext] Is there any possibility of having a link on the image? Is there a possibility of somehow having HTML code rendered from inside APT? This would ease most of my frustrations with APT. The full guide to the apt format can be found on the Doxia site: http://maven.apache.org/doxia/format.html -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FtpWagon.java error
Hi Enrique, http://svn.apache.org/repos/asf/maven/wagon/tags/wagon-1.0-alpha-6/wagon-providers/wagon-ftp/src/main/java/org/apache/maven/wagon/providers/ftp/FtpWagon.java line 127. I suspect that you didn't specify the username or password, can you check that? Regards Enrique Gaona wrote: Jiaqi Guo [EMAIL PROTECTED] wrote on 01/19/2007 02:02:24 PM: What is the version of your wagon-ftp? Thanks Jiaqi, Here are the versions of the wagon jarfiles. Thanks wagon-file-1.0-alpha-7.jar wagon-ftp-1.0-alpha-6.jar wagon-http-lightweight-1.0-alpha-6.jar wagon-provider-api-1.0-alpha-6.jar wagon-ssh-1.0-alpha-7.jar wagon-ssh-external-1.0-alpha-6.jar Enrique Enrique Gaona wrote: Hi, I'm getting an NullPointerException error FtpWagon.java when I execute the following maven command, mvn clean antrun:run install. It seems that the plugin is not reading my settings.xml. I have the csdpRepository id defined inside the settings.xml.I've searched in google for FtpWagon.java error, but the solution offered doesn't seem to work, at least for me. Any help is greatly appreciated. Thanks. repositories repository idcspdRepository/id nameCSDP Repository/name url ftp://ausgsa.austin.ibm.com/projects/c/csdpbuildrepository/maven/repository /url /repository /repositories settings.xml: server idcsdpRepository/id usernameegaona/username passwordpassword/password /server [EMAIL PROTECTED] prereq.kb]# mvn clean antrun:run install [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'antrun'. [INFO] [INFO] Building KB Prerequisite Files [INFO]task-segment: [clean, antrun:run, install] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /build/continuum/app/working-directory/1/com.ibm.mbps.i2c. ui/I2CProject/prereqs/prereq.kb/target [INFO] Deleting directory /build/continuum/app/working-directory/1/com.ibm.mbps.i2c. ui/I2CProject/prereqs/prereq.kb/target/classes [INFO] Deleting directory /build/continuum/app/working-directory/1/com.ibm.mbps.i2c. ui/I2CProject/prereqs/prereq.kb/target/test-classes [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.wagon.providers.ftp.FtpWagon. openConnection(FtpWagon.java:127) at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:143) at org.apache.maven.artifact.manager.DefaultWagonManager. getRemoteFile(DefaultWagonManager.java:354) at org.apache.maven.artifact.manager.DefaultWagonManager. getArtifact(DefaultWagonManager.java:282) at org.apache.maven.artifact.manager.DefaultWagonManager. getArtifact(DefaultWagonManager.java:244) at org.apache.maven.artifact.resolver.DefaultArtifactResolver. resolve(DefaultArtifactResolver.java:124) at org.apache.maven.artifact.resolver.DefaultArtifactResolver. resolve(DefaultArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder. findModelFromRepository(DefaultMavenProjectBuilder.java:467) at org.apache.maven.project.DefaultMavenProjectBuilder. buildFromRepository(DefaultMavenProjectBuilder.java:225) at org.apache.maven.project.artifact.MavenMetadataSource. retrieve(MavenMetadataSource.java:102) at org.apache.maven.artifact.resolver.DefaultArtifactCollector. recurse(DefaultArtifactCollector.java:275) at org.apache.maven.artifact.resolver.DefaultArtifactCollector. collect(DefaultArtifactCollector.java:67) at org.apache.maven.artifact.resolver.DefaultArtifactResolver. resolveTransitively(DefaultArtifactResolver.java:223) at org.apache.maven.artifact.resolver.DefaultArtifactResolver. resolveTransitively(DefaultArtifactResolver.java:211) at org.apache.maven.artifact.resolver.DefaultArtifactResolver. resolveTransitively(DefaultArtifactResolver.java:182) at org.apache.maven.plugin.DefaultPluginManager. resolveTransitiveDependencies(DefaultPluginManager.java:1117) at org.apache.maven.plugin.DefaultPluginManager. executeMojo(DefaultPluginManager.java:366) at org.apache.maven.lifecycle.DefaultLifecycleExecutor. executeGoals(DefaultLifecycleExecutor.java:534) at
Re: The skin does not exist
Jeff Mutonho wrote: I've started getting a new error message during my project build.The error says : [ERROR] BUILD FAILURE [INFO] [INFO] The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins-DartifactId=maven-default-skin \ -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file org.apache.maven.skins:maven-default-skin:jar:RELEASE What is causing this? Something in your build is trying to use maven-default-skin with the version RELEASE which can not be found. Try running mvn help:effective-pom to see if that can give you a clue to who is doing this. Another option is to run mvn -X ... to turn on debugging. That might also give you some hints. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2 (and plugins) need to be released frequently to make maven interesting
Eric Brown wrote: My project is using maven2 and the release plugin. However, the release plugin only works with released plugins (otherwise, our release builds are not reproducible). We've had to locally patch a half-dozen plugins just to mark them as released just in order to be able to do a release build of our project. Furthermore, there are many core and non-core plugins that have plenty of bugs fixed that we still experience today in their SNAPSHOTs. But we can't use these. There is no shortage of numbers in the world. What is the problem with releasing often? So what if a bug occasionally gets its way into a release -- you can always specify an older version of a plugin that didn't have some new bug. True, a lot of plugins are under 3rd party control and not part of the core maven. But if the core maven team starts releasing more often and understands why releases are important, many of the 3rd parties will follow suit. Right now maven seems more like a toy and is constantly frustrating when trying to use it on a real project (due largely to known bugs many of which have been fixed in SNAPSHOTs for over 6-months now and/or several plugins that have produced SNAPSHOT builds but no released version). BTW, My project releases weekly. So far we have 0.5-rc1, 0.5-rc2, 0.5-rc3, ... 0.5-rc9. And we have SNAPSHOTs in between that we never deploy to production but which developers work with. Cheers, Eric Hi Eric, During the last couple of months a lot of work has gone into releasing new versions of the plugins that are used during the release process. When all these plugins have been released, less time and effort will be needed to release something. So then we will be able to do more frequent releases of plugins. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin to find updated versions of dependencies?
Wayne Fay wrote: I have a variety of dependencies declared in my largish J2EE project and I'm wondering if perhaps there's a plugin or something available that would run out to the Maven repo, check my declared dependencies and versions against those available in the repo, and let me know which ones seem to have updates available. Ideally it would produce a list like: groupId/artifactId --- my declared version -- other versions available xml-apis/xml-apis: 1.0.b2 [1.3.02, 1.3.03, 1.3.04] org.codehaus.woodstox/wstx-asl: 3.0.0 [3.0.1, 3.0.2, 3.0.3, 3.1.0, 3.1.1, 3.2.0] etc Obviously I can do this myself manually (and I do now and then) but it would be nice if this was available in an easy to use plugin available from the command line. I don't necessarily always want to use the latest and greatest version of all my dependencies, but if I've declared 3.0.0 and a new version 3.0.4 is available (with bugfixes etc) then I should probably know about it, test my app to make it doesn't break anything, and plan to include it in a future version of my app. If it doesn't already exist, I'll have to start looking into implementing this myself, I suppose. Wayne Hi Wayne, This is an interesting idea. At my day job we have something like this for our ant builds. After every release build a report is generated which shows, among other things, precisely this. It is currently text based and looks like this: - Product XYZ is not using the latest version of these dependencies - Dependency Used Latest - jakarta-commons-logging.jar1.0.41.1 junit.jar 3.8.13.8.2 Perhaps I can use some of this reporting code and turn it into a plugin. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin to find updated versions of dependencies?
Dennis, that is great. I feel like I spend a non-trivial amount of time tracking artifact versions etc and am especially concerned about bug fixes that may be available etc. I'm going to take a look at the dependency plugin as Mark suggested but it would also be nice if you could see about perhaps adapting and donating your code. Wayne On 1/19/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Wayne Fay wrote: I have a variety of dependencies declared in my largish J2EE project and I'm wondering if perhaps there's a plugin or something available that would run out to the Maven repo, check my declared dependencies and versions against those available in the repo, and let me know which ones seem to have updates available. Ideally it would produce a list like: groupId/artifactId --- my declared version -- other versions available xml-apis/xml-apis: 1.0.b2 [1.3.02, 1.3.03, 1.3.04] org.codehaus.woodstox/wstx-asl: 3.0.0 [3.0.1, 3.0.2, 3.0.3, 3.1.0, 3.1.1, 3.2.0] etc Obviously I can do this myself manually (and I do now and then) but it would be nice if this was available in an easy to use plugin available from the command line. I don't necessarily always want to use the latest and greatest version of all my dependencies, but if I've declared 3.0.0 and a new version 3.0.4 is available (with bugfixes etc) then I should probably know about it, test my app to make it doesn't break anything, and plan to include it in a future version of my app. If it doesn't already exist, I'll have to start looking into implementing this myself, I suppose. Wayne Hi Wayne, This is an interesting idea. At my day job we have something like this for our ant builds. After every release build a report is generated which shows, among other things, precisely this. It is currently text based and looks like this: - Product XYZ is not using the latest version of these dependencies - Dependency Used Latest - jakarta-commons-logging.jar1.0.41.1 junit.jar 3.8.13.8.2 Perhaps I can use some of this reporting code and turn it into a plugin. -- Dennis Lundberg - 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]
scm plugin with subversion
I've got an automated build on my project and the scm:update fails after a couple of successful builds saying that the working copy is locked. How do i get around this?
Re: Inheriting profiles
there was a thread about this last week (Jan 10 - Profile inheritance) On 1/18/07, Geoffrey De Smet [EMAIL PROTECTED] wrote: Is there any way to inherit profiles - more specifically their activation? In a multiproject I have a parent pom that has 2 profiles: development and production. Development needs to be activated by default everywhere. Now I found myself repeating the activation in each child pom. -- With kind regards, Geoffrey De Smet - 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]
openejb-core tests
Hi All, While looking over a patch today, I have ran into a situation that I cannot explain and I was hoping someone might be able to help. If I run mvn test from openejb3/container/openejb-core, the tests all run properly and pass. If I run mvn test from openejb3/, the previously passing tests of openejb-core fail for some reason. No code changes, no environment changes or anything else. I have reproduced this on Windows and Mac. I have tried David Blevins' local repository. I have recreated my OpenEJB working copy. I have reinstalled Maven 2.0.4 and I have even reinstall Java. I have basically eliminated everything but the operating system and the internet, although I do know I am not behind any proxy or firewall. Now that you know my situation, have any of you ran into this with OpenEJB or any other Maven-based project? Got any suggestions? Thanks for entertaining what may sound crazy but I assure you, this is really happening. Here is the error output from Maven and the content within the surefire text file: Maven Output: http://rifers.org/paste/show/3300 Surefire Output: http://rifers.org/paste/show/3299 Take care, Jeremy
How To: Autocomplete dependencies with Mevenide2 + Netbeans
Hi All, How do I setup autocomplete with my project depenedencies in mevenide2+netbeans? It seems that I have to create a library group, add all the dependency jars up and use the library group as part of my netbeans project. Is there a more easier way in which it could find all jar files under dependencies? Thanks! Cheers, lemon.dumpling
Re: How To: Autocomplete dependencies with Mevenide2 + Netbeans
not sure what the question is about. what is a library group? autocompletion in pom.xml should work on dependency groupid/artifactid/version values (where the values are taken from the local repo index) but it currently doesn't work due to a bug in nb 5.5 (which is a regression bug from 5.0) Milos On 1/20/07, lemon dumpling [EMAIL PROTECTED] wrote: Hi All, How do I setup autocomplete with my project depenedencies in mevenide2+netbeans? It seems that I have to create a library group, add all the dependency jars up and use the library group as part of my netbeans project. Is there a more easier way in which it could find all jar files under dependencies? Thanks! Cheers, lemon.dumpling - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]