RE: Is there GWT in repository?
GWT is not going to be in the Maven repository because it has a license that must be agreed to. The plugin is designed to link GWT into the Maven development cycle. -Original Message- From: majecek [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 04, 2006 08:51 To: users@maven.apache.org Subject: Re: Is there GWT in repository? I have found this webpage but it seems that it is not in repository. http://codehaus.org/~shinobu/gwt-maven-plugin/ http://codehaus.org/~shinobu/gwt-maven-plugin/ Does anyone used GWT with maven2 ? majecek wrote: Hi is there Google Web Toolkit in maven2 repository? I couldn't find it. Thanks -- View this message in context: http://www.nabble.com/Is-there-GWT-in-repository--tf2381784.html#a663893 9 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Need Some Basic Help, I Think
I downloaded the WAR file from the apache snapshot repository dated 16-Aug-2006 and it seems to be working better. I'm not sure if it is because I have two managed repositories (release and snapshot) or if it is because I have been restarting Tomcat after every configuration change (that seems to be the only way to make the change take effect). Next basic question: How do I get Archiva to log but ignore checksum problems? I am unable to build the project site because of a checksum mismatch on the project-info plugin's maven-metadata.xml file. -Original Message- From: Mohni, Daniel [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 03, 2006 01:33 To: archiva-users@maven.apache.org Subject: RE: Need Some Basic Help, I Think Hello Bob tryed a setup like yours with the daily build from yesterday, and this looks fine here when I try this url http://localhost:8080/archiva/proxy/maven_release/org/apache/maven/ plugins/maven-metadata.xml my proxied repository to ibiblio is named 'maven_release' did you also try this url on your system http://www.home.net:8082/archiva/proxy/remote/org/apache/maven/ plugins/maven-metadata.xml you need the name of the repository to identify where to search for artifacts hth Daniel -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Monday, October 02, 2006 11:30 PM To: archiva-users@maven.apache.org Subject: Need Some Basic Help, I Think I am trying to get Archiva to work, and am having problems I can't solve. I am hoping that someone can see what I am doing wrong and help me get this working. I had downloaded the source and built it at the end of August, but am just trying to get it working. (I am currently downloading the current code in case that has something to do with my problems.) I installed a new Tomcat 5.5 instance (running on http://www.home.net:8082/;) and deployed the web application to it as /archiva. I created just one managed repository named remote. I added one proxied repository named central with a URL of http://www.ibiblio.org/maven2;. In my settings.xml file, I defined a mirror of central with a URL of http://www.home.net:8082/archiva/proxy; (I have also tried adding /remote to the end of the URL). Every time I try to build something in Maven with the mirror defined (and no local repository), I get a build failure because no plugins can be found. The build works fine if the mirror to central is not defined. If I try to access http://www.home.net:8082/archiva/proxy/org/apache/maven/plugi ns/maven-m etadata.xml in my browser, I get a 404 error. If I access http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven- metadata.x ml in my browser, I get the XML file. Anybody got an idea of what I am doing wrong? This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
Need Some Basic Help, I Think
I am trying to get Archiva to work, and am having problems I can't solve. I am hoping that someone can see what I am doing wrong and help me get this working. I had downloaded the source and built it at the end of August, but am just trying to get it working. (I am currently downloading the current code in case that has something to do with my problems.) I installed a new Tomcat 5.5 instance (running on http://www.home.net:8082/;) and deployed the web application to it as /archiva. I created just one managed repository named remote. I added one proxied repository named central with a URL of http://www.ibiblio.org/maven2;. In my settings.xml file, I defined a mirror of central with a URL of http://www.home.net:8082/archiva/proxy; (I have also tried adding /remote to the end of the URL). Every time I try to build something in Maven with the mirror defined (and no local repository), I get a build failure because no plugins can be found. The build works fine if the mirror to central is not defined. If I try to access http://www.home.net:8082/archiva/proxy/org/apache/maven/plugins/maven-m etadata.xml in my browser, I get a 404 error. If I access http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-metadata.x ml in my browser, I get the XML file. Anybody got an idea of what I am doing wrong? This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
RE: Strange Compile Error
Yes, the jar has the class files. As I said in the first sentence of my email, this has been working fine on another machine with the exact same jars and sources. The jar came with the toolkit. One thing I forgot to check yesterday was the Java version. I knew both systems were running JDK 5 but hadn't check to see if the version were identical. The old system is running: java version 1.5.0_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-b05) Java HotSpot(TM) Client VM (build 1.5.0_05-b05, mixed mode, sharing) The new system is running: java version 1.5.0_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08) Java HotSpot(TM) Server VM (build 1.5.0_01-b08, mixed mode) -Original Message- From: Max Cooper [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 19, 2006 22:45 To: Maven Users List Subject: Re: Strange Compile Error I don't know the solution to your problem, but I have some info and ideas that might help you find a solution... It looks like the compiler is finding .java files in the gwt-user-1.1.10.jar dependency. I read recently that google puts the source code some libs in the jar, and it looks like this is one such case. I am not sure quite what the compiler error means, but it seems like it is perhaps trying to compile the sources from the dependency jar, which seems odd. It seems like having source in the jar would not be a problem, but perhaps it is. Does the jar also contain the .class files (you could look inside the jar to verify), or does it only contain source? Perhaps the problem is that it is ONLY a source jar, and does not contain the .class files. That is just a guess, but it is something I would check. I don't see that jar on ibiblio. How did it get into your local repository? I would examine where the jar came from carefully -- perhaps it is incompatible with maven for some reason. Does the jar also contain the class files (you could look inside the one you have), or does it only contain source? And maybe there is a compatible version of the same lib available by some other means. -Max Allison, Bob wrote: I have been using one machine for development and having no problem. I copied my development tree to another machine and tried to build my project; the compiler created a bunch of errors because of source files in a jar on the class path. I ran mvn -X compile on both the old machine and the new machine and compared the output from the two runs. The only differences between the logs (until the compile error) consisted of differences in paths because of a different home directory. I have verified that the jar holding the sources is the same on both machines. I have included the complete log from the failed compile in the hopes that someone can figure out where I should start looking to figure out what is wrong. + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/home/allisord/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/opt/maven/2/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Searching for parent-POM: qaccess:webapp::5.0-SNAPSHOT of project: qaccess:mit:war:5.0-SNAPSHOT in relative path: ../webapp/pom.xml [DEBUG] Using parent-POM from the project hierarchy at: '../webapp/pom.xml' for project: qaccess:mit:war:5.0-SNAPSHOT [DEBUG] Searching for parent-POM: qaccess:product::5.0-SNAPSHOT of project: qaccess:webapp:pom:5.0-SNAPSHOT in relative path: ../product/pom.xml [DEBUG] Using parent-POM from the project hierarchy at: '../product/pom.xml' for project: qaccess:webapp:pom:5.0-SNAPSHOT [INFO] [INFO] Building Manual ITs [INFO]task-segment: [compile] [INFO] [DEBUG] maven-resources-plugin: resolved to version 2.2 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-resources-plugin:maven-plugin:2.2 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [DEBUG] maven-compiler-plugin: resolved to version 2.0.1 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-compiler-plugin:maven-plugin:2.0.1 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project
RE: Strange Compile Error
It looks like this was caused by a problem fixed between JDK 5.0u1 and JDK 5.0u5. I installed the latest JDK 5 on my new machine and the problem went away. -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 05:38 To: Maven Users List Subject: RE: Strange Compile Error Yes, the jar has the class files. As I said in the first sentence of my email, this has been working fine on another machine with the exact same jars and sources. The jar came with the toolkit. One thing I forgot to check yesterday was the Java version. I knew both systems were running JDK 5 but hadn't check to see if the version were identical. The old system is running: java version 1.5.0_05 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-b05) Java HotSpot(TM) Client VM (build 1.5.0_05-b05, mixed mode, sharing) The new system is running: java version 1.5.0_01 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08) Java HotSpot(TM) Server VM (build 1.5.0_01-b08, mixed mode) -Original Message- From: Max Cooper [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 19, 2006 22:45 To: Maven Users List Subject: Re: Strange Compile Error I don't know the solution to your problem, but I have some info and ideas that might help you find a solution... It looks like the compiler is finding .java files in the gwt-user-1.1.10.jar dependency. I read recently that google puts the source code some libs in the jar, and it looks like this is one such case. I am not sure quite what the compiler error means, but it seems like it is perhaps trying to compile the sources from the dependency jar, which seems odd. It seems like having source in the jar would not be a problem, but perhaps it is. Does the jar also contain the .class files (you could look inside the jar to verify), or does it only contain source? Perhaps the problem is that it is ONLY a source jar, and does not contain the .class files. That is just a guess, but it is something I would check. I don't see that jar on ibiblio. How did it get into your local repository? I would examine where the jar came from carefully -- perhaps it is incompatible with maven for some reason. Does the jar also contain the class files (you could look inside the one you have), or does it only contain source? And maybe there is a compatible version of the same lib available by some other means. -Max Allison, Bob wrote: I have been using one machine for development and having no problem. I copied my development tree to another machine and tried to build my project; the compiler created a bunch of errors because of source files in a jar on the class path. I ran mvn -X compile on both the old machine and the new machine and compared the output from the two runs. The only differences between the logs (until the compile error) consisted of differences in paths because of a different home directory. I have verified that the jar holding the sources is the same on both machines. I have included the complete log from the failed compile in the hopes that someone can figure out where I should start looking to figure out what is wrong. + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/home/allisord/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/opt/maven/2/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Searching for parent-POM: qaccess:webapp::5.0-SNAPSHOT of project: qaccess:mit:war:5.0-SNAPSHOT in relative path: ../webapp/pom.xml [DEBUG] Using parent-POM from the project hierarchy at: '../webapp/pom.xml' for project: qaccess:mit:war:5.0-SNAPSHOT [DEBUG] Searching for parent-POM: qaccess:product::5.0-SNAPSHOT of project: qaccess:webapp:pom:5.0-SNAPSHOT in relative path: ../product/pom.xml [DEBUG] Using parent-POM from the project hierarchy at: '../product/pom.xml' for project: qaccess:webapp:pom:5.0-SNAPSHOT [INFO] [INFO] Building Manual ITs [INFO]task-segment: [compile] [INFO] [DEBUG] maven-resources-plugin: resolved to version 2.2 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-resources-plugin:maven-plugin:2.2 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [DEBUG] maven-compiler-plugin: resolved to version 2.0.1 from repository central [DEBUG] Retrieving parent-POM
Strange Compile Error
I have been using one machine for development and having no problem. I copied my development tree to another machine and tried to build my project; the compiler created a bunch of errors because of source files in a jar on the class path. I ran mvn -X compile on both the old machine and the new machine and compared the output from the two runs. The only differences between the logs (until the compile error) consisted of differences in paths because of a different home directory. I have verified that the jar holding the sources is the same on both machines. I have included the complete log from the failed compile in the hopes that someone can figure out where I should start looking to figure out what is wrong. + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/home/allisord/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/opt/maven/2/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Searching for parent-POM: qaccess:webapp::5.0-SNAPSHOT of project: qaccess:mit:war:5.0-SNAPSHOT in relative path: ../webapp/pom.xml [DEBUG] Using parent-POM from the project hierarchy at: '../webapp/pom.xml' for project: qaccess:mit:war:5.0-SNAPSHOT [DEBUG] Searching for parent-POM: qaccess:product::5.0-SNAPSHOT of project: qaccess:webapp:pom:5.0-SNAPSHOT in relative path: ../product/pom.xml [DEBUG] Using parent-POM from the project hierarchy at: '../product/pom.xml' for project: qaccess:webapp:pom:5.0-SNAPSHOT [INFO] [INFO] Building Manual ITs [INFO]task-segment: [compile] [INFO] [DEBUG] maven-resources-plugin: resolved to version 2.2 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-resources-plugin:maven-plugin:2.2 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [DEBUG] maven-compiler-plugin: resolved to version 2.0.1 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-compiler-plugin:maven-plugin:2.0.1 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [DEBUG] maven-checkstyle-plugin: resolved to version 2.1 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-checkstyle-plugin:maven-plugin:2.1 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [DEBUG] maven-release-plugin: resolved to version 2.0-beta-4 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-release-plugin:maven-plugin:2.0-beta-4 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [DEBUG] maven-surefire-plugin: resolved to version 2.2 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-surefire-plugin:maven-plugin:2.2 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [DEBUG] cobertura-maven-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::7 for project: null:cobertura-maven-plugin:maven-plugin:2.0 from the repository. [DEBUG] maven-war-plugin: resolved to version 2.0.1 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-war-plugin:maven-plugin:2.0.1 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project:
GWT Toolkit Plugin
I was starting to use the GWT plugin in the Mojo sandbox, and find that it doesn't work the way I expected. I have been rewriting it to work the way I expect it, and am wondering if I am doing something strange. My expectation of the plugin is to be part of a build for a WAR. The toolkit is used to compile the user interface of the application into JavaScript which is then included in the WAR as it is assembled. It looks like the plugin was written with the expectation of the GWT-derived stuff being in a separate project from the WAR (or whatever is using the pages). I was wondering if anyone else is using the plugin and how they are arranging their projects to use it. This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Installing a File From a Plugin
I am working with a plugin which connects Maven to a third-party tool kit (GWT) that the user must download separately. I would like to write a Mojo that takes the directory where the kit was installed and the version of the kit and installs the required jars into the Maven repository (or maybe deploys to a corporate one). The basic operation of the Mojo would be as a script which does mvn install:install-file on the jars in the installation directory when the user enters the command mvn gwt:install. Anybody have a good idea or two on how to accomplish this task? This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Instructions, Anyone?
I have been looking through the Maven web site and the archiva source tree but have, as yet, been unable to locate any instructions on how to use this. Could someone kindly point me to the documentation? This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
RE: [m204] Error with compiler plugin with new project...
[Snipped most of the message to shorten this reply...] I am using Maven 2.0.4 with modules running Java 5. I am not having any problems. One big difference I see between your POM and mine is that I do not specify compilerVersion at all. The one JDK on the machine is 1.5.0_05, so Maven is using it as well. -Original Message- From: Mick Knutson [mailto:[EMAIL PROTECTED] Sent: Monday, June 26, 2006 17:14 To: users@maven.apache.org Subject: Re: [m204] Error with compiler plugin with new project... This issue is really PISSING me off now. I have removed everything except a single module as I need touse modules with this. I have also tried: compilerVersion1.5/compilerVersion source1.5/source !-- - This should not be needed, but Maven throws an exception - if this is not specified when source=5: -- target1.5/target as well as compilerVersion5/compilerVersion source5/source !-- - This should not be needed, but Maven throws an exception - if this is not specified when source=5: -- target5/target Can someone please assist me on this. --- Thank You Mick Knutson BASE logic, inc. (415) 648-1804 (San Francisco, CA) http://www.BASELogic.com http://www.djmick.com --- This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How do I use the output of a maven build as a resources of another.
If the applet is supposed to be downloadable from within the web application, though, this won't work since things under WEB-INF are not reachable from the browser. How would you get the applet jar placed in the web application so that the browser can get to it? -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Friday, June 23, 2006 8:10 PM To: Maven Users List Subject: Re: How do I use the output of a maven build as a resources of another. On 6/23/06, Steve Menke [EMAIL PROTECTED] wrote: I am using maven 2.0 to build a jar file of applet classes. I need to include this output as resource / file in a web application which is also built with maven 2.0. Does anyone know the best and hopefully easiest way of doing this? In the webapp module, declare a dependency on your applet jar, and Maven will include it in WEB-INF/lib. Make sure you build the applet jar with 'mvn install' (not just 'mvn package') so it will be present in your local repository. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] No Java test frameworks found?
I had this problem and resolved it by placing an explicit dependency on JUnit. It seems that something in one of the other plugins I have been using had a reference to JUnit which made everything work right. The updated plugins removed that indirect reference and caused the problem. -Original Message- From: Morgan Rachell [mailto:[EMAIL PROTECTED] Sent: Thursday, May 25, 2006 14:49 To: users@maven.apache.org Subject: [m2] No Java test frameworks found? I had setup my project a few weeks ago and was running 'mvn install' (with JUnit tests, etc.) without problems. Someone new just joined my project and just did a 'mvn install', which first downloaded all plugins and dependencies, but then he got this error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] No Java test frameworks found [INFO] We can reproduce the error with just a 'mvn test' command too. I noticed that his download was getting maven-surefire-plugin version 2.2. I was unable to duplicate the problem on my machine because I had version 2.1.3 of the plugin. When I deleted version 2.1.3 from local repository (actually, I foolishly deleted my entire local repo!) I got the same error. Now we're stuck and cannot get past this error. I should also mention that we use a mirror pointing to http://repo.mergere.com/maven2. It's much faster than ibiblio. Has anyone else experienced this problem or know how to get past it? Thanks, Morgan -- View this message in context: http://www.nabble.com/-m2-+No+Java+test+frameworks+found--t1682690.html# a4564033 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2.0.4] OutOfMemoryError
I suspect that the change was caused by a recent change to the test plugin to fork by default (I believe the default changed from never to once). -Original Message- From: Dave Hoffer [mailto:[EMAIL PROTECTED] Sent: Friday, May 12, 2006 07:10 To: Maven Users List Subject: RE: [m2.0.4] OutOfMemoryError Bob, Thanks for the clarification. One thing I still don't understand is that when I first had trouble running my tests (getting out of memory errors), people in this mail list said to set MAVEN_OPTS and it did solve my problem. Now, I may have been executing the tests thru continuum or maven directly, I don't remember for sure. In any case, it solved the problem. I now find that running tests directly thru maven requires 'argLine' usage. Any thoughts? -dh -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Friday, May 12, 2006 6:53 AM To: Maven Users List Subject: RE: [m2.0.4] OutOfMemoryError For everyone else following this thread, the reason you need to use the argLine rather than MAVEN_OPTS is that tests are forked so they run in their own JVM. Setting MAVEN_OPTS sets the heap limit for the JVM running Maven, but not the JVM running the tests. The argLine configuration sets additional arguments for the JVM that is running the tests. -Original Message- From: Dave Hoffer [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 21:55 To: Maven Users List Subject: RE: [m2.0.4] OutOfMemoryError Dan, I think you are right! I just added this to one of the failing projects and it works. For me maven is ignoring the MAVEN_OPTS setting. Using 'argLine' my memory usage is now reported to be 300MB where it was stuck just shy of 64MB. Thanks a bunch. -dh -Original Message- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 4:47 PM To: users@maven.apache.org Cc: Kris Nuttycombe Subject: Re: [m2.0.4] OutOfMemoryError You can use the argLine configuration option for surefire plugin to add JVM args. Things like -ea to enable the assertions that you should be testing are also good things to put on that line. Dan On Thursday 11 May 2006 16:40, Kris Nuttycombe wrote: I have a related question to this: Is it possible to specify the memory footprint except using the MAVEN_OPTS environment variable? It would be useful to have this as an option for the surefire plugin, at least if the tests are running in a separate JVM. Kris Dave Hoffer wrote: For some of my projects that use a lot of memory when running unit tests I set MAVEN_OPTS to -Xmx1024m to get all the tests to not throw OutOfMemoryErrors. I now have a maven project that has a dependency on the prior component but I do get an OutOfMemoryError when I run the unit tests. I have tried to set -Xmx to larger values with no success, as it always fails. The poms are all but identical, why should one fail? Also, in the process viewer I see that when running the tests there are two java processes. One reports using about 90MB and the other about 64MB. Why are there two? These numbers are way lower than the max java heap size specified. Any ideas? -dh - 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] -- J. Daniel Kulp [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] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - 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.0.4] OutOfMemoryError
For everyone else following this thread, the reason you need to use the argLine rather than MAVEN_OPTS is that tests are forked so they run in their own JVM. Setting MAVEN_OPTS sets the heap limit for the JVM running Maven, but not the JVM running the tests. The argLine configuration sets additional arguments for the JVM that is running the tests. -Original Message- From: Dave Hoffer [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 21:55 To: Maven Users List Subject: RE: [m2.0.4] OutOfMemoryError Dan, I think you are right! I just added this to one of the failing projects and it works. For me maven is ignoring the MAVEN_OPTS setting. Using 'argLine' my memory usage is now reported to be 300MB where it was stuck just shy of 64MB. Thanks a bunch. -dh -Original Message- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Thursday, May 11, 2006 4:47 PM To: users@maven.apache.org Cc: Kris Nuttycombe Subject: Re: [m2.0.4] OutOfMemoryError You can use the argLine configuration option for surefire plugin to add JVM args. Things like -ea to enable the assertions that you should be testing are also good things to put on that line. Dan On Thursday 11 May 2006 16:40, Kris Nuttycombe wrote: I have a related question to this: Is it possible to specify the memory footprint except using the MAVEN_OPTS environment variable? It would be useful to have this as an option for the surefire plugin, at least if the tests are running in a separate JVM. Kris Dave Hoffer wrote: For some of my projects that use a lot of memory when running unit tests I set MAVEN_OPTS to -Xmx1024m to get all the tests to not throw OutOfMemoryErrors. I now have a maven project that has a dependency on the prior component but I do get an OutOfMemoryError when I run the unit tests. I have tried to set -Xmx to larger values with no success, as it always fails. The poms are all but identical, why should one fail? Also, in the process viewer I see that when running the tests there are two java processes. One reports using about 90MB and the other about 64MB. Why are there two? These numbers are way lower than the max java heap size specified. Any ideas? -dh - 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] -- J. Daniel Kulp [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] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] starteam release goal error
Check out http://maven.apache.org/guides/development/guide-testing-development-plu gins.html -Original Message- From: Dave Hoffer [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 14:57 To: Maven Users List Subject: RE: [m2] starteam release goal error I got the following error when I pasted the dependency into my pom. [ERROR] BUILD ERROR [INFO] - [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-release-plugin Version: 2.0-beta-4-SNAPSHOT Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-release-plugin:pom:2.0-beta-4-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) -dh -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 2:46 PM To: Maven Users List Subject: Re: [m2] starteam release goal error snapshot already deployed at snapshot repo, just enter the plugin version in the pom. -D On 5/9/06, Dave Hoffer [EMAIL PROTECTED] wrote: Your suspicion seems to be right; beta-3 does not support starteam yet, only cvs and svn. Do you have a 2.0-beta-4-SNAPSHOT.jar I could install? If not how do I get this project to build and install? -dh -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 1:25 PM To: Maven Users List Subject: Re: [m2] starteam release goal error It is possible that beta-3 does not support starteam yet, one way to findout is to inspect beta-3's pom.xml to see it has starteam provider as dependency any how, beta-4 is about to be released. You can help with testing by placing build plugins plugin artifactIdmaven-release-plugin/artifactId version2.0-beta-4-SNAPSHOT/version /plugin /plugins /build in your root pom. -D On 5/9/06, Dave Hoffer [EMAIL PROTECTED] wrote: I see I have maven-release-plugin 2.0-beta-3 in my user-dir repository. Is that what I should have? By the way, I was doing a dryRun when I got this error. -dh -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 12:52 PM To: Maven Users List Subject: Re: [m2] starteam release goal error I just run a release:perform using the latest snapshot of release plugin against starteam, it ran fine. what version of release plugin do you have? -D On 5/9/06, Dave Hoffer [EMAIL PROTECTED] wrote: Using 2.0.4 running release:prepare goal I get the following error. Embedded error: Can't load the scm provider. No such provider: 'starteam' I have my scm specified in my project's pom file. I have the starteam command line exe in my path and starteam works with Continuum. Why do I get this error running maven2 on the command line? -dh - 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] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: scm url in continuum
Try removing the scm:svn: in front of the URL. -Original Message- From: Vandermi Joao da Silva [mailto:[EMAIL PROTECTED] Sent: Thursday, April 27, 2006 09:23 To: continuum-users@maven.apache.org Subject: RE: scm url in continuum Sorry imagem can't send. see below: my url scm:svn:https://www.mysite.com.br/repos/cms/cms_src/trunk/ continuum say Enter the URL to the Maven 2 POM[ You must provide a valid url ] Regards Vandermi Silva RD MAO - Core Engines BenQ Eletroeletrônica Ltda. TEL +55(92) 2127-8015 Mobile: +55(92) 8125-2248 FAX +55(92) 2127-8102 [EMAIL PROTECTED] www.BenQMobile.com Av. Djalma Batista, 536 - São Geraldo Manaus-AM Brasil From: Vandermi Joao da Silva [mailto:[EMAIL PROTECTED] Sent: Thursday, April 27, 2006 9:16 AM To: continuum-users@maven.apache.org Subject: scm url in continuum Hello everyone, I have a problem when work with maven modules projects in the continumm 1.0.3-SNAPSHOT I need config my scm url because using module is impossible use local pom.xml. But continuum say invalid url . See below. What the correct url to maven2 projects? That url is same examples of scm and maven home page. I use subversion. Best Regards Vandermi Silva RD MAO - Core Engines BenQ Eletroeletrônica Ltda. TEL +55(92) 2127-8015 Mobile: +55(92) 8125-2248 FAX +55(92) 2127-8102 [EMAIL PROTECTED] www.BenQMobile.com Av. Djalma Batista, 536 - São Geraldo Manaus-AM Brasil This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
RE: xdoclet-maven-plugin configuration question.
The Maven2 plugin for XDoclet uses the Ant XML configuration, exactly as it is documented on the XDoclet home page (http://xdoclet.sourceforge.net/xdoclet/index.html). You do not have to do any task definitions like in Ant, just define the task configurations like webdoclet.../webdoclet or ejbdoclet.../ejbdoclet. The Maven plugin configuration looks like this: build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdxdoclet-maven-plugin/artifactId executions execution phasegenerate-sources/phase goals goalxdoclet/goal /goals configuration tasks ... Desired XDoclet XML fragment ... /tasks /configuration /execution /executions /plugin /plugins /build -Original Message- From: Sean McNamara [mailto:[EMAIL PROTECTED] Sent: Friday, April 21, 2006 16:05 To: Maven Users List Subject: Re: xdoclet-maven-plugin configuration question. In re-reading my message, I wasn't really clear on what I'm trying to do. I'm building some EJBs using xdoclet. My bean with XDoclet tags lives at: com.foo.bar.ejb.MyBean When I generate the bean files via XDoclet, they get put by default in: com.foo.bar.ejb.MyBean com.foo.bar.ejb.MyBeanHome I need to do a couple things here: 1. Get it to generate the MyBeanUtil file. 2. Have the generated interfaces put in the com.foo.bar.interfaces package. 3. Keep the generated bean file in com.foo.bar.ejb This is done under M1 using the following settings: maven.xdoclet.ejbdoclet.session.0=true maven.xdoclet.ejbdoclet.packageSubstitution.0=true maven.xdoclet.ejbdoclet.packageSubstitution.0.packages=ejb maven.xdoclet.ejbdoclet.packageSubstitution.0.substituteWith=interfaces I'm not sure why it doesn't generate the Util class since it used to, but perhaps the defaults have changed. Thanks for any pointers. --- Sean McNamara [EMAIL PROTECTED] wrote: I'm finding the documentation for the xdoclet plugin for M2 to be a little sparse and am hoping someone here can point me in the right direction. Can anyone point me to a list of valid configuration parameters for the plugin? I'm trying to change the package definitions for generated classes. I was able to do this under M1, but I'm not seeing a clear way to do this in the M2 POM format. If someone can point me to docs, or if anyone knows of how to map M1 property settings into M2 XML in a generic way, that would help a lot! Thanks, -Sean P.S. No takers on my previous site generation question? :-) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Maven Surefire Report plugin 2.0 released
I updated my POM and did a mvn -U site and got this exception: java.lang.NoSuchMethodError: org.apache.maven.doxia.siterenderer.Renderer.render(Ljava/util/Collectio n;Lorg/apache/maven/doxia/siterenderer/SiteRenderingContext;Ljava/io/Fil e;Ljava/lang/String;)V at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:121) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:412) Is there something else that needs to be updated for this to work? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Sanchez Sent: Thursday, April 20, 2006 20:56 To: announce@maven.apache.org; Maven Users List Subject: [ANN] Maven Surefire Report plugin 2.0 released Maven Surefire Report plugin 2.0 has been released. You can use it by adding it to the reporting section of your pom reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-report-plugin/artifactId version2.0/version /plugin /plugins /reporting Changelog: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11222styleNa me=Htmlversion=12481 * [MSUREFIREREP-2] - test failures causes report not to be generated * [MSUREFIREREP-9] - surefire-report-maven-plugin: don't add report for non java projects * [MSUREFIREREP-11] - [surefire-report] not contains package name and testcase details * [MSUREFIREREP-13] - NPE with svn version of surefire-report-maven-plugin * [MSUREFIREREP-15] - Add integration logic that allows report to be created for junit OR testng * [MSUREFIREREP-17] - Use javascript to show/hide failure details -- 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]
RE: mvn2, dependincies, javadoc plugin and links...
It has been requested in several forms. I posted a JIRA (MNG-1732) that had a means to provide this kind of information. It was intended to solve two problems: -- Packaging of WAR dependencies in an EAR (putting the dependency in the EAR's package instead of the WAR) without requiring that the dependency be listed in the EAR -- Providing a means for extra information about a dependency for use inside plugins (in my case, it was the location to install the jar in the RPM) The answer I basically got was go jump in a lake. Well, Brett was more polite than that. The gist of the argument, as I recall, was that the devs got rid of attaching properties to dependencies because they caused problems. The RPM plugin has been stalled because I have been trying to come up with a way to collect the packaging information for dependencies without the user needing to define the whole dependency.../dependency information twice (once for Maven, once in the plugin configuration to define packaging). -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, April 13, 2006 19:29 To: Maven Users List Subject: Re: mvn2, dependincies, javadoc plugin and links... This feature has certainly been requested (should be in jira somewhere), but is not currently implemented. - Brett On 4/14/06, Jules Gosnell [EMAIL PROTECTED] wrote: I was thinking... My pom.xml has a load of explicit dependencies which are used to form the classpath. My javadoc-plugin clause has a load of links which correspond to the same dependencies. How about having e.g. a javadoc-url sub-elt in each dependency that the javadoc-plugin could read and automatically (if e.g. automagic-linking=true) . This would ensure that deps and links were consistant with each other and would probably result in much better javadoc linkage... Of course, this may have already been done - if so, what is the syntax ? Thanks for your time, Jules -- Open Source is a self-assembling organism. You dangle a piece of string into a super-saturated solution and a whole operating-system crystallises out around it. /** * Jules Gosnell * Partner * Core Developers Network (Europe) * *www.coredevelopers.net * * Open Source Training Support. **/ - 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: Internal (intranet) repositories
I assume that version[1.2.2]/version works in plugin, dependencyManagement, and pluginManagement to accomplish the same effect for plugin versions and inherited version information. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, April 07, 2006 00:31 To: Maven Users List Subject: Re: Internal (intranet) repositories Unfortunately, ibiblio is super busy most hours of the day as it is a shared resource. This is the price we pay for using it. You can use a Central mirror instead by configuring your settings.xml. The occasional 503 on ibiblio is really no big deal imo. Especially considering that you can run offline with -o once your dependencies are all downloaded into your repo. For 90% of maven builds, you really don't need to go out to the net to check for updates of dependencies etc. In fact, I might even suggest you use [x.y.z] to lock in versions for dependencies just to prevent Maven from having to go out to ibiblio etc to find updates, and also to prevent changes in new versions of dependencies from breaking your build. Especially when you are dealing with code that's in production -- the last thing you'd want is for Maven to autodownload the latest JDO files which might not be 100% compatible with the version you were running before. Enabling this can be as simple as tweaking your dependencies as follows: dependency ... version[1.2.2]/version /dependency This locks the dependency version to 1.2.2 so Maven does not check ibiblio for updates. When you just use version1.2.2/version, Maven will go out and check ibiblio for updates and pull them down automatically for you. Go here to read more about configuring versions: http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict +Resolution Wayne On 4/6/06, EJ Ciramella [EMAIL PROTECTED] wrote: For the record, this is why I want to avoid going to remote server for the repository: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Error transferring file commons-io:commons-io:jar:1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) Path to dependency: 1) org.apache.maven.plugins:maven-resources-plugin:maven-plugin:2.1 2) commons-io:commons-io:jar:1.0 Caused by I/O exception: Server returned HTTP response code: 503 for URL: http://www.ibiblio.org/maven2/commons-io/commons-io/1.0/commons-io-1.0. jar.sha1 Re-running produces a working build. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Thursday, April 06, 2006 6:16 PM To: Maven Users List Subject: RE: Internal (intranet) repositories Here is my pom file. The directory in the url below is a shared folder on a different machine. project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.ejstools.tool1/groupId artifactIdtool1/artifactId packagingjar/packaging version1.0-SNAPSHOT/version nameEJs Tools/name urlhttp://build2.corp.upromise.com:8080/url descriptionThis project is simply here to lean about maven and eventually will be used to build EJs Java tools./description repositories repository idlocal/id nameUpromise Maven Repository/name urlfile:///servernamehere/mavenrepository/url /repository /repositories dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies build resources resource directorysrc/main/resources/directory filteringtrue/filtering /resource /resources /build /project -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, April 06, 2006 6:12 PM To: Maven Users List Subject: Re: Internal (intranet) repositories Where exactly were you putting that repository section? In your pom.xml? Or in another configuration file? Wayne On 4/6/06, EJ Ciramella [EMAIL PROTECTED] wrote: None of this explains why it didn't use my repo and simply ignored it completely. This is the more important part of the puzzle. - 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
RE: [m2.0.3] Scanning for projects... hangs
Is there a reason to protect against the following:
connection${project.scm.developerConnection}/xx/connection
developerConnection${project.scm.connection}/xx/developerConnection
Looking at John's patch, it would not catch this kind of configuration
issue. What I have above is certainly fabricated and is unlikely to
occur. But I can see the possibility of circular references like this
cropping up from cut-n-paste errors which may not be obvious because
they are not in adjacent lines.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 05, 2006 20:02
To: Maven Users List
Subject: Re: [m2.0.3] Scanning for projects... hangs
John has fixed this and will post a new RC shortly.
On 4/5/06, Allison, Bob [EMAIL PROTECTED] wrote:
And yes it hangs in the 2.0.4 RC
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 19:10
To: Maven Users List
Subject: RE: [m2.0.3] Scanning for projects... hangs
It doesn't require child projects. The following POM hangs in 2.0.3
(I
haven't downloaded the 2.0.4 RC yet):
?xml version=1.0 encoding=UTF-8?
project
modelVersion4.0.0/modelVersion
groupIdtest/groupId
artifactIdtest/artifactId
packagingpom/packaging
nameTest Hang/name
version1.0-SNAPSHOT/version
scm
connection${project.scm.connection}/xx/connection
developerConnection${project.scm.developerConnection}/xx/developerCon
nection
url${project.scm.url}/xx/url
/scm
/project
Notice that project.scm.url contains ${project.scm.url} and likewise
for
the other two SCM entries. I believe that this is what is causing the
hang. I suspect what Jens is trying to do is get the value of
project.scm.* from the parent project.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 17:48
To: Maven Users List
Subject: Re: [m2.0.3] Scanning for projects... hangs
what about the hang?
On 4/5/06, Jens Zastrow [EMAIL PROTECTED] wrote:
Neither with the 2.0.4-SNAPSHOT.
To test this just add teh following to a child-pom.
scm
connection${project.scm.connection}/xxx/connection
developerConnection${project.scm.developerConnection}/xxx/developerCo
nnection
url${project.scm.url}/xxx/url
/scm
-
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]
RE: [m2.0.3] Scanning for projects... hangs
Verified that the POM causes an exception rather than hanging.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 06, 2006 11:40
To: Maven Users List
Subject: Re: [m2.0.3] Scanning for projects... hangs
Alright, this should be fixed now. Can you give the latest RC a try?
It's here:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-2006
0406.131501.tar.gz
Thanks,
John
Allison, Bob wrote:
It doesn't require child projects. The following POM hangs in 2.0.3
(I
haven't downloaded the 2.0.4 RC yet):
?xml version=1.0 encoding=UTF-8?
project
modelVersion4.0.0/modelVersion
groupIdtest/groupId
artifactIdtest/artifactId
packagingpom/packaging
nameTest Hang/name
version1.0-SNAPSHOT/version
scm
connection${project.scm.connection}/xx/connection
developerConnection${project.scm.developerConnection}/xx/developerCon
nection
url${project.scm.url}/xx/url
/scm
/project
Notice that project.scm.url contains ${project.scm.url} and likewise
for
the other two SCM entries. I believe that this is what is causing the
hang. I suspect what Jens is trying to do is get the value of
project.scm.* from the parent project.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 17:48
To: Maven Users List
Subject: Re: [m2.0.3] Scanning for projects... hangs
what about the hang?
On 4/5/06, Jens Zastrow [EMAIL PROTECTED] wrote:
Neither with the 2.0.4-SNAPSHOT.
To test this just add teh following to a child-pom.
scm
connection${project.scm.connection}/xxx/connection
developerConnection${project.scm.developerConnection}/xxx/developerCo
nnection
url${project.scm.url}/xxx/url
/scm
-
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.0.3] Scanning for projects... hangs
It doesn't require child projects. The following POM hangs in 2.0.3 (I
haven't downloaded the 2.0.4 RC yet):
?xml version=1.0 encoding=UTF-8?
project
modelVersion4.0.0/modelVersion
groupIdtest/groupId
artifactIdtest/artifactId
packagingpom/packaging
nameTest Hang/name
version1.0-SNAPSHOT/version
scm
connection${project.scm.connection}/xx/connection
developerConnection${project.scm.developerConnection}/xx/developerCon
nection
url${project.scm.url}/xx/url
/scm
/project
Notice that project.scm.url contains ${project.scm.url} and likewise for
the other two SCM entries. I believe that this is what is causing the
hang. I suspect what Jens is trying to do is get the value of
project.scm.* from the parent project.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 17:48
To: Maven Users List
Subject: Re: [m2.0.3] Scanning for projects... hangs
what about the hang?
On 4/5/06, Jens Zastrow [EMAIL PROTECTED] wrote:
Neither with the 2.0.4-SNAPSHOT.
To test this just add teh following to a child-pom.
scm
connection${project.scm.connection}/xxx/connection
developerConnection${project.scm.developerConnection}/xxx/developerCo
nnection
url${project.scm.url}/xxx/url
/scm
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2.0.3] Scanning for projects... hangs
And yes it hangs in the 2.0.4 RC
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 19:10
To: Maven Users List
Subject: RE: [m2.0.3] Scanning for projects... hangs
It doesn't require child projects. The following POM hangs in 2.0.3 (I
haven't downloaded the 2.0.4 RC yet):
?xml version=1.0 encoding=UTF-8?
project
modelVersion4.0.0/modelVersion
groupIdtest/groupId
artifactIdtest/artifactId
packagingpom/packaging
nameTest Hang/name
version1.0-SNAPSHOT/version
scm
connection${project.scm.connection}/xx/connection
developerConnection${project.scm.developerConnection}/xx/developerCon
nection
url${project.scm.url}/xx/url
/scm
/project
Notice that project.scm.url contains ${project.scm.url} and likewise for
the other two SCM entries. I believe that this is what is causing the
hang. I suspect what Jens is trying to do is get the value of
project.scm.* from the parent project.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 04, 2006 17:48
To: Maven Users List
Subject: Re: [m2.0.3] Scanning for projects... hangs
what about the hang?
On 4/5/06, Jens Zastrow [EMAIL PROTECTED] wrote:
Neither with the 2.0.4-SNAPSHOT.
To test this just add teh following to a child-pom.
scm
connection${project.scm.connection}/xxx/connection
developerConnection${project.scm.developerConnection}/xxx/developerCo
nnection
url${project.scm.url}/xxx/url
/scm
-
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: Repository Problem with Release Plugin
Anybody have any ideas? I can file a JIRA on this but I don't know if the problem is that the release plugin is building a bad POM or if the POM is not getting parsed correctly (or if I'm just doing something stupid which is always a possibility). -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 29, 2006 12:23 To: Maven Users List Subject: Repository Problem with Release Plugin I am starting to try to use the release plugin to do releases, and I am finding a problem. I'm not sure if this is a bug with the release plugin, some other part of Maven 2.0.3, or just a bad POM. My original POM defined the deployment repository as: repository idtheid/id namethename/name urlfile:///the/url/url releases enabledtrue/enabled /releases snapshots enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyfail/checksumPolicy /snapshots /repository When the release plugin gets done making the new POM, the id, name, and url get moved to the end of the repository stanza and the releases.../releases lines are converted to releases / (diff attached below). Once this happens, modules of this project are no longer looking at any repositories other than central for releases. I discovered this when I upgraded from 2.0.2 to 2.0.3 and cleared my local repository to ensure that I had the latest plugins; my released projects failed to even parse because the released parent project could no longer be found (those projects access the repository via http; the diff below came from a sample I created to test the problem which accesses a temporary repository via file). Does anybody have a clue what might be wrong? -- Diff of changes made by release plugin -- --- ../../save/parent-pom.xml.orig 2006-03-29 08:55:22.0 -0700 +++ pom.xml 2006-03-29 09:03:07.0 -0700 @@ -1,12 +1,11 @@ -?xml version=1.0 encoding=UTF-8? -project +?xml version=1.0 encoding=UTF-8?project modelVersion4.0.0/modelVersion groupIdtest/groupId artifactIdparent/artifactId packagingpom/packaging nameRelease Test Parent/name - version1.0/version - urlhttp://www.home.com//url + version1.1-SNAPSHOT/version + urlhttp://www.home.com/url inceptionYear2004/inceptionYear developers developer @@ -43,94 +42,81 @@ /modules repositories repository - iddev/id - nameTest Development Repository/name - urlfile:///tmp/snapshot/url releases enabledfalse/enabled /releases snapshots -enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyfail/checksumPolicy /snapshots + iddev/id + nameTest Development Repository/name + urlfile:///tmp/snapshot/url /repository repository - idrel/id - nameTest Release Repository/name - urlfile:///tmp/release/url - releases -enabledtrue/enabled - /releases + releases / snapshots enabledfalse/enabled /snapshots + idrel/id + nameTest Release Repository/name + urlfile:///tmp/release/url /repository /repositories pluginRepositories pluginRepository - idrel/id - nameTest Release Repository/name - urlfile:///tmp/release/url - releases -enabledtrue/enabled - /releases + releases / snapshots enabledfalse/enabled /snapshots + idrel/id + nameTest Release Repository/name + urlfile:///tmp/release/url /pluginRepository pluginRepository - iddev/id - nameTest Development Repository/name - urlfile:///tmp/snapshot/url releases enabledfalse/enabled /releases snapshots -enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyfail/checksumPolicy /snapshots + iddev/id + nameTest Development Repository/name + urlfile:///tmp/snapshot/url /pluginRepository pluginRepository - idcodehaus-plugins/id - urlhttp://dist.codehaus.org//url + releases / snapshots -enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyfail/checksumPolicy /snapshots - releases -enabledtrue/enabled - /releases + idcodehaus-plugins/id + urlhttp://dist.codehaus.org//url /pluginRepository /pluginRepositories reporting plugins plugin -groupIdorg.codehaus.mojo/groupId -artifactIdsurefire-report-maven-plugin/artifactId - /plugin - plugin -groupIdorg.apache.maven.plugins/groupId -artifactIdmaven-project-info-reports-plugin/artifactId - /plugin - plugin -groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId /plugin plugin -groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId
RE: POM : Not a v4.0.0 POM / Error building POM (may not be this proj ect's POM)
IE doesn't VALIDATE to XML, just display it.
-Original Message-
From: Sharma, Jaikumar [mailto:[EMAIL PROTECTED]
Sent: Monday, April 03, 2006 07:00
To: Maven Users List
Subject: RE: POM : Not a v4.0.0 POM / Error building POM (may not be this proj
ect's POM)
After copying the plugins section inside the build section, same error is
there, even IE is able to parse this XML file correctly, does not show any
problems.
Any Idea ?
Regards.
-Original Message-
From: Alexandre Poitras [mailto:[EMAIL PROTECTED]
Sent: Monday, April 03, 2006 4:14 PM
To: Maven Users List
Subject: Re: POM : Not a v4.0.0 POM / Error building POM (may not be this
proj ect's POM)
Your plugins section is not inside the build section. An XML aware editor
could help you there :)
On 4/3/06, Sharma, Jaikumar [EMAIL PROTECTED] wrote:
Dear Maven users,
When trying to execute : mvn compile I get the following error, I am
not sure I am missing something or what is wrong . Could somebody help
on this please ? Regards.
__
_
[INFO] Scanning for projects...
[INFO]
--
--
[ERROR] FATAL ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: unknown
POM Location: D:\Users\Alpha0\pom.xml
Reason: Not a v4.0.0 POM.
__
_
project xmlns=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/POM/4.0.0
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
http://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd
http://maven.apache.org/maven-v4_0_0.xsd
modelVersion4.0/modelVersion
groupIdcom.mycompany.sample/groupId
artifactIdtest/artifactId
packagingpom/packaging
nametest/name
version4.0/version
properties
subsystem.home${basedir}/subsystem.home
/properties
plugins
plugin
groupIdorg.apache.maven.plugins.maven-archetype-plugin.1.0-alpha-3/
groupI
d
artifactIdmaven-archetype-plugin-1.0-alpha-3.jar/artifactId
version1.0-alpha-3/version
/plugin
plugin
groupIdorg.apache.maven.plugins.maven-compiler-plugin.2.0/groupId
artifactIdmaven-compiler-plugin-2.0.jar/artifactId
version2.0/version
/plugin
plugin
groupIdorg.apache.maven.plugins.maven-install-plugin.2.1/groupId
artifactIdmaven-install-plugin-2.1.jar/artifactId
version2.1/version
/plugin
plugin
groupIdorg.apache.maven.plugins.maven-jar-plugin.2.0/groupId
artifactIdmaven-compiler-plugin-2.0.jar/artifactId
version2.0/version
/plugin
plugin
groupIdorg.apache.maven.plugins.maven-resources-plugin.2.1/groupId
artifactIdmaven-resources-plugin-2.1.jar/artifactId
version2.1/version
/plugin
plugin
groupIdorg.apache.maven.plugins.maven-surefire-plugin.2.1.2/groupId
artifactIdmaven-compiler-plugin-2.1.2.jar/artifactId
version2.1.2/version
/plugin
/plugins
organization
namemy company/name
urlhttp://www.mycompany.com/url
/organization
modules
module${basedir}/java/BusinessLogic//module
module${basedir}/java/ClientUI//module
/modules
build
sourceDirectory${basedir}/java/BusinessLogic/src//sourceDirectory
outputDirectory${basedir}/java/BusinessLogic/classes//outputDirecto
ry
sourceDirectory${basedir}/java/ClientUI//sourceDirectory
outputDirectory${basedir}/java/ClientUI/classes//outputDirectory
defaultGoalcompile/defaultGoal
/build
/project
__
__
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message
is privileged and confidential, and is intended only for the use of
the
addressee(s) named above and others who have been specifically authorized
to
receive it. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this message and/or
attachments is strictly prohibited. The company accepts no liability for
any
damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liability for any delays. If you have
received this message in error, please contact the sender and delete the
message. Thank you.
--
Alexandre Poitras
Québec, Canada
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- - - - - - -
RE: [m2] reporting plugin extensions/additional dependencies
Here's what I do in my parent POM file: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId dependencies dependency groupIdmy.group/groupId artifactIdbuild-tools/artifactId version1.0-SNAPSHOT/version /dependency /dependencies /plugin /plugins /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration configLocationstyle/my-style.xml/configLocation headerLocationstyle/header.java/headerLocation /configuration /plugin /plugins /reporting I will admit that I have not closely checked that it is actually using the custom configuration (I have been too busy recently getting other documentation together), but the checkstyle plugin does not complain about missing configuration files. HTH -Original Message- From: Robert Biernat [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 29, 2006 23:42 To: 'users@maven.apache.org' Subject: [m2] reporting plugin extensions/additional dependencies Hi, I'm using maven on a number of different projects. These projects all generate websites containing reports generated by the checkstyle, pmd, and jdepend report plugins. The checkstyle and pmd plugins reference config files that are tailored to my organisations coding standards. At the moment each project that wishes to use these standard config files needs to include them within their project so theyre available when the plugin runs. I am wondering whether its possible to create a seperate project that contains these resources, install the jar into the repository and have the various report plugins use it. I noticed that for report plugins I cannot specify additional dependencies like I can with regular build plugins, so I'm sort of stuck as to how I would do it. Rob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Repository Problem with Release Plugin
I am starting to try to use the release plugin to do releases, and I am finding a problem. I'm not sure if this is a bug with the release plugin, some other part of Maven 2.0.3, or just a bad POM. My original POM defined the deployment repository as: repository idtheid/id namethename/name urlfile:///the/url/url releases enabledtrue/enabled /releases snapshots enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyfail/checksumPolicy /snapshots /repository When the release plugin gets done making the new POM, the id, name, and url get moved to the end of the repository stanza and the releases.../releases lines are converted to releases / (diff attached below). Once this happens, modules of this project are no longer looking at any repositories other than central for releases. I discovered this when I upgraded from 2.0.2 to 2.0.3 and cleared my local repository to ensure that I had the latest plugins; my released projects failed to even parse because the released parent project could no longer be found (those projects access the repository via http; the diff below came from a sample I created to test the problem which accesses a temporary repository via file). Does anybody have a clue what might be wrong? -- Diff of changes made by release plugin -- --- ../../save/parent-pom.xml.orig 2006-03-29 08:55:22.0 -0700 +++ pom.xml 2006-03-29 09:03:07.0 -0700 @@ -1,12 +1,11 @@ -?xml version=1.0 encoding=UTF-8? -project +?xml version=1.0 encoding=UTF-8?project modelVersion4.0.0/modelVersion groupIdtest/groupId artifactIdparent/artifactId packagingpom/packaging nameRelease Test Parent/name - version1.0/version - urlhttp://www.home.com//url + version1.1-SNAPSHOT/version + urlhttp://www.home.com/url inceptionYear2004/inceptionYear developers developer @@ -43,94 +42,81 @@ /modules repositories repository - iddev/id - nameTest Development Repository/name - urlfile:///tmp/snapshot/url releases enabledfalse/enabled /releases snapshots -enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyfail/checksumPolicy /snapshots + iddev/id + nameTest Development Repository/name + urlfile:///tmp/snapshot/url /repository repository - idrel/id - nameTest Release Repository/name - urlfile:///tmp/release/url - releases -enabledtrue/enabled - /releases + releases / snapshots enabledfalse/enabled /snapshots + idrel/id + nameTest Release Repository/name + urlfile:///tmp/release/url /repository /repositories pluginRepositories pluginRepository - idrel/id - nameTest Release Repository/name - urlfile:///tmp/release/url - releases -enabledtrue/enabled - /releases + releases / snapshots enabledfalse/enabled /snapshots + idrel/id + nameTest Release Repository/name + urlfile:///tmp/release/url /pluginRepository pluginRepository - iddev/id - nameTest Development Repository/name - urlfile:///tmp/snapshot/url releases enabledfalse/enabled /releases snapshots -enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyfail/checksumPolicy /snapshots + iddev/id + nameTest Development Repository/name + urlfile:///tmp/snapshot/url /pluginRepository pluginRepository - idcodehaus-plugins/id - urlhttp://dist.codehaus.org//url + releases / snapshots -enabledtrue/enabled updatePolicydaily/updatePolicy checksumPolicyfail/checksumPolicy /snapshots - releases -enabledtrue/enabled - /releases + idcodehaus-plugins/id + urlhttp://dist.codehaus.org//url /pluginRepository /pluginRepositories reporting plugins plugin -groupIdorg.codehaus.mojo/groupId -artifactIdsurefire-report-maven-plugin/artifactId - /plugin - plugin -groupIdorg.apache.maven.plugins/groupId -artifactIdmaven-project-info-reports-plugin/artifactId - /plugin - plugin -groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId /plugin plugin -groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId /plugin plugin -groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId /plugin plugin +artifactIdmaven-project-info-reports-plugin/artifactId + /plugin + plugin groupIdorg.codehaus.mojo/groupId artifactIdjxr-maven-plugin/artifactId /plugin + plugin +groupIdorg.codehaus.mojo/groupId +
RE: Plugin JAR : bug maven.jar.final.name
Actually, it is not just the JAR plugin. ALL plugins do this so that
Maven can find things in the Repository at a later date.
-Original Message-
From: Ruel Loehr [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 14, 2006 10:14
To: Maven Users List
Subject: RE: Plugin JAR : bug maven.jar.final.name
You can't.
You cannot alter the name it uses to install the jar. This is my
biggest complaint about the jar plugin. It's very stringent.
Ruel Loehr
JBoss QA
-
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel
-Original Message-
From: Blaise Gosselin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 14, 2006 8:28 AM
To: users@maven.apache.org
Subject: Plugin JAR : bug maven.jar.final.name
Hello,
I set the JAR variable maven.jar.final.name =
${pom.artifactId}-client-${pom.currentVersion}.jar.
When I make a jar:install, I have this jar in my target directory, but
the jar installed in my local repository is
${pom.artifactId}-${pom.currentVersion}.jar.
What should I do in order to install the jar generated with the good
name ?
Thanks in advance.
_ _ _
bgOnline
-
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: plugin use in multiprojects seems broken
Bugs like this are one of the reasons the plugin is still alpha. Although, I have to admit that I did not expect the plugin to get used like this since I figured each project that wanted to be able to build an RPM would need an individual configuration; I wasn't expecting anyone to want to use an identical configuration for the plugin on every project. I'll take a look at some of the other plugins and figure out how to do this check and update the sources to make this work. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Friday, March 10, 2006 20:44 To: Maven Users List Subject: Re: plugin use in multiprojects seems broken You'll need to provide more details. Why doesn't it work if you don't put it in the parent? Where do you put it if not in the parent? Regardless, it should work in the parent. It's a bug in the rpm plugin if it attempts to produce an rpm for a pom - it should be testing the packaging. - Brett On 3/11/06, Xavier Toth [EMAIL PROTECTED] wrote: Maybe I'm missing something but the use of plugins in multiprojects seems broken to me. I've got three projects that build rpms so I made a parent projects to run them all. However unless I add the plugin into the parent as in : modules modulemicro_proxy/module modulesocks/module modulejwss/module /modules build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdrpm-maven-plugin/artifactId version1.0-alpha-2-SNAPSHOT/version configuration release1/release mappings /mappings /configuration /plugin /plugins /build the submodules won't build. I really don't want to run the plugin (rpm:rpm) goal in the parent project. It seem to me that a mulitproject parent ought to be able to ignore plugin goals that it doesn't have build information for and simple pass them along to its submodules. Xavier - 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: rpm-plugin mapping file rename
Looking at the sources, it looks like it will not rename the file. If ../../micro_proxy is a directory, then the file micro_proxy.xinetd in that directory will be installed in the destination (/etc/xinetd.d) with the name micro_proxy.xinetd. If ../../micro_proxy is a file, then that file will be installed in the destination with the name micro_proxy (the includes will be ignored). My suggestion on how to do this would be to have a directory in the project src/main/xinetd and place the file micro_proxy in that directory. You can then instruct the RPM plugin to just place everything in the source directory into the destination (no need for includes in this case). -Original Message- From: Xavier Toth [mailto:[EMAIL PROTECTED] Sent: Friday, March 10, 2006 08:52 To: Maven Users List Subject: Re: rpm-plugin mapping file rename I'm not sure how I'd do a rename. Here is an example where I'd like what ends up in /etc/xinetd.d to be simple micro_proxy and not micro_proxy.xinetd, any idea how I'd do this? mapping directory/etc/xinetd.d/directory filemode755/filemode sources source location../../micro_proxy/location includes includemicro_proxy.xinetd/include /includes /source /sources /mapping On 3/10/06, Allison, Bob [EMAIL PROTECTED] wrote: I believe the answer is that it will not unless the item to be renamed is the item specified in the mapping. I would say to give it a try and let me know if it works or doesn't work. If it works, I can add that information to the docs; if it doesn't work, send me more info on what you are doing and I can see what I might be able to do so it will. -Original Message- From: Xavier Toth [mailto:[EMAIL PROTECTED] Sent: Thursday, March 09, 2006 4:31 PM To: Maven Users List Subject: rpm-plugin mapping file rename Can the mapping element be used to rename a file being installed? Xavier - 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: rpm plugin location
The links on that page were automatically created from information inherited from the sandbox parent. I think the sandbox parent was updated since then to provide the correct links, but I haven't regenerated the site since then. I'll try to get this updated. -Original Message- From: Edwin Punzalan [mailto:[EMAIL PROTECTED] Sent: Friday, March 10, 2006 21:55 To: Maven Users List Subject: Re: rpm plugin location That page is wrong. It should be: svn://svn.codehaus.org/mojo/scm/trunk/mojo/mojo-sandbox/rpm-maven-plugin Xavier Toth wrote: I can't find the rpm plugin source. The links and svn commands at http://www.codehaus.org/~boba/rpm-plugin/source-repository.html don't work. Anyone know where this plugin is now? - 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: rpm-plugin mapping file rename
I believe the answer is that it will not unless the item to be renamed is the item specified in the mapping. I would say to give it a try and let me know if it works or doesn't work. If it works, I can add that information to the docs; if it doesn't work, send me more info on what you are doing and I can see what I might be able to do so it will. -Original Message- From: Xavier Toth [mailto:[EMAIL PROTECTED] Sent: Thursday, March 09, 2006 4:31 PM To: Maven Users List Subject: rpm-plugin mapping file rename Can the mapping element be used to rename a file being installed? Xavier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] multiproject using plugin
I am guessing that you need to specify the groupId and artifactId of the RPM plugin in any project that uses it. I think you can only inherit the version with the pluginManagement in the parent POM. Of course, in the case of the RPM plugin, the configuration is likely to be different for each project, so I would assume you still have the RPM plugin configuration in each project. -Original Message- From: Xavier Toth [mailto:[EMAIL PROTECTED] Sent: Friday, March 10, 2006 9:34 AM To: Maven Users List Subject: [m2] multiproject using plugin I have a project that builds an rpm with the rpm plugin which works fine. Now I want to build several rpms so I've made several projects and a parent project to run them all. However when I run the parent (mvn -o clean rpm:rpm) I get the following output: NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] micro_proxy [INFO] sockd [INFO] JWSS [INFO] rpm [INFO] Searching repository for plugin with prefix: 'rpm'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-rpm-plugin' does not exist or no valid version could be found [INFO] My parent pom looks like: 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 groupIdorg.jcdx.jwss/groupId artifactIdrpm/artifactId version1.0/version packagingpom/packaging namerpm/name urlhttp://jcdx.org/url parent groupIdorg.jcdx.jwss/groupId artifactIdjwss/artifactId version1.0.0/version /parent modules modulemicro_proxy/module modulesocks/module modulejwss/module /modules build pluginManagement plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdrpm-maven-plugin/artifactId version1.0-alpha-2-SNAPSHOT/version /plugin /plugins /pluginManagement /build /project I don't think the pluginManagement does anything in this instance. I can run this command successfully in the suprojects why doesn't it work from the parent? Is there a way in the parent to specify the goals for the children? Xavier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Question About Deploying Project Sites
I want to create a web site that looks like this:
index.html
+--parent-1.0/index.html
+--proj1-1.0/index.html
+--proj1-1.1/index.html
+--proj2-1.0/index.html
and so on... Basically, I wanted each version of each project to deploy
its site to a different directory. This also means that SNAPSHOT
versions deploy in a different directory than releases.
My parent project and all of its modules are peer directories in the
build directories, so the parent project has
module../proj1/module.
In the parent project, I defined the site deployment URL to be
file://${user.home}/public_html/projects/${project.artifactId}-${projec
t.version}. Each of the other projects inherit this definition. When
I do a site:deploy, I get the following structure:
/home/allisord/public_html/projects/index.html
+--parent-1.0/index.html
+--proj1-1.0
+--proj1/index.html
+--proj2-1.0
+--proj2/index.html
I get the module name tacked on to the end of the inherited string,
which I guess is expected since the URL is inherited. I guess I have
two questions:
1) I noticed some discussion (I think on the dev@ list) that the desired
path for a subproject site in this case should be
.../projects/parent/child/... rather than .../projects/child/... that
was generated. Is this correct?
2) I am guessing that if I put the URL string in each subproject, then
the URL won't be mangled since it won't be inherited. Is there some
other way to accomplish the web site I am looking for?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Question About Deploying Project Sites
I just realized that my first question is slightly wrong. It turns out
that I did get the child sites deployed to
.../projects/parent/child/... except that the definition of parent
changes from project to project because of the substitutions. It also
means that the module links in the site generated for the parent are
wrong (in parent, the link to proj1 points to
projects/parent-1.0/proj1/index.html while the site is in
projects/proj1-1.0/proj1/index.html).
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 09:14
To: Maven Users List
Subject: Question About Deploying Project Sites
I want to create a web site that looks like this:
index.html
+--parent-1.0/index.html
+--proj1-1.0/index.html
+--proj1-1.1/index.html
+--proj2-1.0/index.html
and so on... Basically, I wanted each version of each project to deploy
its site to a different directory. This also means that SNAPSHOT
versions deploy in a different directory than releases.
My parent project and all of its modules are peer directories in the
build directories, so the parent project has
module../proj1/module.
In the parent project, I defined the site deployment URL to be
file://${user.home}/public_html/projects/${project.artifactId}-${projec
t.version}. Each of the other projects inherit this definition. When
I do a site:deploy, I get the following structure:
/home/allisord/public_html/projects/index.html
+--parent-1.0/index.html
+--proj1-1.0
+--proj1/index.html
+--proj2-1.0
+--proj2/index.html
I get the module name tacked on to the end of the inherited string,
which I guess is expected since the URL is inherited. I guess I have
two questions:
1) I noticed some discussion (I think on the dev@ list) that the desired
path for a subproject site in this case should be
.../projects/parent/child/... rather than .../projects/child/... that
was generated. Is this correct?
2) I am guessing that if I put the URL string in each subproject, then
the URL won't be mangled since it won't be inherited. Is there some
other way to accomplish the web site I am looking for?
-
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: Question About Deploying Project Sites
Question two also has a problem. If I put the URL in each subproject,
then the links in the web site are wrong because parent points to
projects/parent-1.0/proj1/index.html while proj1 is built to
projects/proj1-1.0/index.html.
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 10:25
To: Maven Users List
Subject: RE: Question About Deploying Project Sites
I just realized that my first question is slightly wrong. It turns out
that I did get the child sites deployed to
.../projects/parent/child/... except that the definition of parent
changes from project to project because of the substitutions. It also
means that the module links in the site generated for the parent are
wrong (in parent, the link to proj1 points to
projects/parent-1.0/proj1/index.html while the site is in
projects/proj1-1.0/proj1/index.html).
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 08, 2006 09:14
To: Maven Users List
Subject: Question About Deploying Project Sites
I want to create a web site that looks like this:
index.html
+--parent-1.0/index.html
+--proj1-1.0/index.html
+--proj1-1.1/index.html
+--proj2-1.0/index.html
and so on... Basically, I wanted each version of each project to deploy
its site to a different directory. This also means that SNAPSHOT
versions deploy in a different directory than releases.
My parent project and all of its modules are peer directories in the
build directories, so the parent project has
module../proj1/module.
In the parent project, I defined the site deployment URL to be
file://${user.home}/public_html/projects/${project.artifactId}-${projec
t.version}. Each of the other projects inherit this definition. When
I do a site:deploy, I get the following structure:
/home/allisord/public_html/projects/index.html
+--parent-1.0/index.html
+--proj1-1.0
+--proj1/index.html
+--proj2-1.0
+--proj2/index.html
I get the module name tacked on to the end of the inherited string,
which I guess is expected since the URL is inherited. I guess I have
two questions:
1) I noticed some discussion (I think on the dev@ list) that the desired
path for a subproject site in this case should be
.../projects/parent/child/... rather than .../projects/child/... that
was generated. Is this correct?
2) I am guessing that if I put the URL string in each subproject, then
the URL won't be mangled since it won't be inherited. Is there some
other way to accomplish the web site I am looking for?
-
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]
Problem With Release Plugin
I have a development tree that looks like this: toplevel +-- pom.xml +-- module1 +-- pom.xml +-- module2 +-- pom.xml I would like to make a release of module1. When I do mvn release:prepare, the POM is updated with the release version and committed then I get the error svn: Cannot copy path '.' into its own child '../tags/module1-1.0' My subversion repository looks like: product +-- trunk +-- toplevel +-- module1 +-- tags Is there any way to tell the release plugin where the tagged stuff should go? It just assumed that it should go in '../tags' rather than asking me. Or am I stuck with not being able to use the release plugin? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to make Continuum respect maven installation-wide settings.xml?
I have done the same thing in the past. Continuum does not display the
interpolated values on its web pages but it does end up using them during
operation.
-Original Message-
From: Michael Böckling [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 06:03
To: continuum-users@maven.apache.org
Subject: Re: How to make Continuum respect maven installation-wide settings.xml?
Thank you Emmanuel for your help, but unfortunately, this isn't working,
it still says ${curr-scm-root}Build/Parent-Project in the Continuum
project info page.
When I go to /opt/continuum-1.0.2/apps/continuum/working-directory/6817
and type mvn help:effective-pom, everything looks right, the element
project.scm.connection is properly interpolated. Could it be that
Continuum does not interpolate pom values upon project import?
Regards,
Michael
You must copy your settings.xml in
${continuum.home}/bin/YOUR_OS/conf/settings.xml.
Absolute path of settings.xml is written in your continuum logs.
Why don't you define it in ${user.home}/.m2/settings.xml?
Emmanuel
Michael Böckling a écrit :
Hi,
in have a settings.xml in my maven installation directory where I
define an active profile:
activeProfiledev/activeProfile
My SCM information in the POM depend on a profile being activated,
because I want to be able to switch between different repository
roots depending on the environment (dev/int/prod).
When I try to import a project to Continuum, the profile does not get
activated, because the settings.xml in the Maven installation
directory is obviously not being read, resulting in a SCM url like
this: ${curr-scm-root}Build/Parent-Project. The property
${curr-scm-root}is not interpolated, because the profile is not
activated.
Is there a way to configure Continuum such that it reads
maven-2.0.2/conf/settings.xml, or must I copy settings.xml somewhere
in my continuum installation so it gets picked up?
Regards,
Michael
--
Giniality AG - Michael Böckling; Steinenberg 21, CH-4051 Basel
P: +41 61 226 99 63 - F: +41 61 226 99 69
[EMAIL PROTECTED]; http://www.giniality.com/
OT: Servlet 2.4/JSP 2.0 Testing
Does anybody know of a means to do unit testing of web servlets which are coded to the Servlet 2.4 specification and JSPs coded to the JSP 2.0 specification? Cactus doesn't seem to be there yet in any release I could find and I have been unable to build Cactus in a manner which would provide this capability (although it looks like it might be partially present). I asked this question on the Cactus user list and have not gotten any responses so I thought I would try here and see if any Maven users have done anything like this. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Servlet 2.4/JSP 2.0 Testing
Hi Vincent. My problems with your suggestions are: * Cactus does not support the stated specifications; from what I see in the docs and source, it stops at Servlet 2.3 and JSP 1.2 (as far as released binaries, I have not been able to successfully build the J2EE 1.4 version and no one on the Cactus list answers my questions) * It seems like it would be much easier to use an embedded Jetty 5.x server rather than using Cargo and an external container; too bad Cactus' JettyTestSetup class doesn't support jetty 5.x * I'm not sure if linking surefire into the integration test phase will work; it looks like there is currently nothing tied to that phase as part of war packaging so there wouldn't be any conflicts, but I'm not sure if it has any dependencies on what phase it is running in -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Monday, February 06, 2006 08:35 To: 'Maven Users List' Subject: RE: Servlet 2.4/JSP 2.0 Testing Hi Bob, -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: lundi 6 février 2006 14:04 To: Maven Users List Subject: OT: Servlet 2.4/JSP 2.0 Testing Does anybody know of a means to do unit testing of web servlets which are coded to the Servlet 2.4 specification and JSPs coded to the JSP 2.0 specification? Cactus doesn't seem to be there yet in any release I could find and I have been unable to build Cactus in a manner which would provide this capability (although it looks like it might be partially present). I asked this question on the Cactus user list and have not gotten any responses so I thought I would try here and see if any Maven users have done anything like this. AFAIK Alexander is working on a Cactus m2 plugin. Also you should be able to use the Cactus cactifywar goal using the Antrun m2 plugin. Then you can use the Cargo plugin to start/stop/deploy the cactified war. You could try binding the cactification to the pre-integration-test phase and then bind cargo:start also in the same phase (but define after so that the order is preserved). One issue will be that the current surefire plugin has no goal to run junit tests in the integration-test phase... But at least this is how I think it could be supported easily. Thanks -Vincent - 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 xdoclet jsptaglib How?
I am not sure what the problem is, but it is definitely an XDoclet problem, not
a Maven problem. You might get better answers on an XDoclet forum.
-Original Message-
From: Grégory Joseph [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 18, 2006 06:20
To: Maven Users List
Subject: Re: Maven2 xdoclet jsptaglib How?
Hi,
I could only advise to try out xdoclet2 and its fresh maven2 plugin ;-)
See http://xdoclet.codehaus.org/Maven2+Plugin for some incomplete
info. I'll be glad to hear your comments. Can't update the docs right
now though, our confluence seems to be having a hard time.
On 18/01/06, MiSt [EMAIL PROTECTED] wrote:
I am trying to generate tld files with xdoclet plugin , but I get tld
file only with name and version but without definitions.
I have got three java files with jsp tags.
Problem exists in maven 2.0, 2.0.1, 2.0.2
My pom.xml:
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdxdoclet-maven-plugin/artifactId
executions
execution
phasegenerate-resources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks
mkdir
dir=${project.build.directory}/generated-resources/MATA-INF/
webdoclet
destdir=${project.build.directory}/generated-resources/MATA-INF
excludedtags= verbose=true force=true
addedTags=
jsptaglib jspversion=1.1 taglibversion=1.2
shortname=jsp-utils filename=jsp-utils.tld /
fileset dir=${project.build.sourceDirectory}
include name=**/*.java/
/fileset
/webdoclet
/tasks
/configuration
/execution
/executions
/plugin
/plugins
Generated jsp-utils.tld file :
?xml version=1.0 encoding=UTF-8?
!DOCTYPE taglib PUBLIC -//Sun Microsystems, Inc.//DTD JSP Tag Library
1.1//EN http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd;
taglib
tlibversion1.2/tlibversion
jspversion1.1/jspversion
shortnamejsp-utils/shortname
/taglib
Maven messages:
[DEBUG] Configuring mojo
'org.codehaus.mojo:xdoclet-maven-plugin:1.0-alpha-2:xdoclet' --
[DEBUG] (f) classRealm = [EMAIL PROTECTED]
[DEBUG] (f) generatedSourcesDirectory =
/home/mist/workspace/web_utils/target/generated-sources/xdoclet
[DEBUG] (f) project = [EMAIL PROTECTED]
[DEBUG] (f) sourceDirectory = /home/mist/workspace/web_utils/src/main/java
[DEBUG] (f) tasks =
[DEBUG] -- end configuration --
[INFO] [xdoclet:xdoclet {execution: default}]
[INFO] Initializing DocletTasks!!!
[INFO] Executing tasks
[DEBUG] getProperty(ns=null, name=ant.reuse.loader, user=false)
[mkdir] Created dir:
/home/mist/workspace/web_utils/target/generated-resources/MATA-INF
2006-01-18 11:27:30 xdoclet.XDocletMain start
INFO: Running jsptaglib/
Generating jsp-utils.tld.
[INFO] Executed tasks
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 7 seconds
[INFO] Finished at: Wed Jan 18 11:27:30 CET 2006
[INFO] Final Memory: 4M/8M
[INFO]
--
Michał Steiner
-
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 xdoclet jsptaglib How?
Just for grins and giggles, try replacing the source directory in the fileset
tag with src/main/java. That will determine of the
${project.build.sourceDirectory} is being interpolated correctly.
-Original Message-
From: MiSt [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 18, 2006 08:14
To: Maven Users List
Subject: Re: Maven2 xdoclet jsptaglib How?
Allison, Bob napisał(a):
I am not sure what the problem is, but it is definitely an XDoclet problem,
not a Maven problem. You might get better answers on an XDoclet forum.
I am not sure.
xdoclet-maven-plugin is based on antrun plugin. Children of element
tasks in configuration are ant task. I have copied them from my ant
script. Before I moved to maven I had used this script and it worked fine.
From other hand I use similiar configuration to generate ejb
descriptors and it works...
It looks like xdoclet don't find java files.
Does anyone know how to make xdoclet to print which files it scans for
tags ?
configuration
tasks
mkdir
dir=${project.build.directory}/generated-resources/MATA-INF/
webdoclet
destdir=${project.build.directory}/generated-resources/MATA-INF
excludedtags= verbose=true force=true
addedTags=
jsptaglib jspversion=1.1 taglibversion=1.2
shortname=jsp-utils filename=jsp-utils.tld /
fileset dir=${project.build.sourceDirectory}
include name=**/*.java/
/fileset
/webdoclet
/tasks
/configuration
--
Michał Steiner
-
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]
Problem With Maven 2.0.2
I upgraded to Maven 2.0.2 this morning, and started getting the problem with the CheckStyle plugin and Jdk14Logger class (MCHECKSTYLE-24), so I adjusted things to be able to use CheckStyle 2.0-beta-2-SNAPSHOT (added the snapshot repository, updated the CheckStyle plugin version, etc.). Now I get an error saying: The skin does not exist: Unable to determine the release version org.apache.maven.skins:maven-default-skin:jar:RELEASE I searched all of the POMs that have been downloaded and can't find which project specifies this dependency. Running mvn -X does not shed any light on the matter. Anybody have any clues how to resolve this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem With Maven 2.0.2
Already tried this. Also tried building and installing the default skin from SVN; still no help. -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 14:22 To: Maven Users List Subject: RE: Problem With Maven 2.0.2 Bob, I got the same problem when I used a local snapshot of the site plugin. Deleting maven-site-plugin in my local repo so it used the latest release solved the problem. -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 12:27 PM To: Maven Users List Subject: Problem With Maven 2.0.2 I upgraded to Maven 2.0.2 this morning, and started getting the problem with the CheckStyle plugin and Jdk14Logger class (MCHECKSTYLE-24), so I adjusted things to be able to use CheckStyle 2.0-beta-2-SNAPSHOT (added the snapshot repository, updated the CheckStyle plugin version, etc.). Now I get an error saying: The skin does not exist: Unable to determine the release version org.apache.maven.skins:maven-default-skin:jar:RELEASE I searched all of the POMs that have been downloaded and can't find which project specifies this dependency. Running mvn -X does not shed any light on the matter. Anybody have any clues how to resolve this? - 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: Problem With Maven 2.0.2
Since the skin tag does not appear in the documentation yet, where does it belong? I tried adding it after the reporting section, but it complained that skin is an unrecognized tag. Also, is the model still 4.0.0? -Original Message- From: Arnd Brusdeilins [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 14:29 To: Maven Users List Subject: Re: Problem With Maven 2.0.2 i got the same problem and defined a skin in my site.xml like project ... skin groupIdorg.apache.maven.skins/groupId artifactIdmaven-stylus-skin/artifactId version1.0-SNAPSHOT/version /skin ... /project now it works Allison, Bob wrote: I upgraded to Maven 2.0.2 this morning, and started getting the problem with the CheckStyle plugin and Jdk14Logger class (MCHECKSTYLE-24), so I adjusted things to be able to use CheckStyle 2.0-beta-2-SNAPSHOT (added the snapshot repository, updated the CheckStyle plugin version, etc.). Now I get an error saying: The skin does not exist: Unable to determine the release version org.apache.maven.skins:maven-default-skin:jar:RELEASE I searched all of the POMs that have been downloaded and can't find which project specifies this dependency. Running mvn -X does not shed any light on the matter. Anybody have any clues how to resolve this? - 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: Problem With Maven 2.0.2
Missed that. My bad. With the stuff in the site.xml, things seem to be working correctly now. Thanks for your help! -Original Message- From: Mike Perham [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 14:55 To: Maven Users List Subject: RE: Problem With Maven 2.0.2 Note he said site.xml, not pom.xml. -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 1:47 PM To: Maven Users List Subject: RE: Problem With Maven 2.0.2 Since the skin tag does not appear in the documentation yet, where does it belong? I tried adding it after the reporting section, but it complained that skin is an unrecognized tag. Also, is the model still 4.0.0? -Original Message- From: Arnd Brusdeilins [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 14:29 To: Maven Users List Subject: Re: Problem With Maven 2.0.2 i got the same problem and defined a skin in my site.xml like project ... skin groupIdorg.apache.maven.skins/groupId artifactIdmaven-stylus-skin/artifactId version1.0-SNAPSHOT/version /skin ... /project now it works Allison, Bob wrote: I upgraded to Maven 2.0.2 this morning, and started getting the problem with the CheckStyle plugin and Jdk14Logger class (MCHECKSTYLE-24), so I adjusted things to be able to use CheckStyle 2.0-beta-2-SNAPSHOT (added the snapshot repository, updated the CheckStyle plugin version, etc.). Now I get an error saying: The skin does not exist: Unable to determine the release version org.apache.maven.skins:maven-default-skin:jar:RELEASE I searched all of the POMs that have been downloaded and can't find which project specifies this dependency. Running mvn -X does not shed any light on the matter. Anybody have any clues how to resolve this? - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using multiple source directories to produce on artefact
By default (or maybe it is by design) the XDoclet plugin wants it generated output to go in target/generated-sources/xdoclet and it AUTOMATICALLY adds this path to the source directory list. It is bad practice to have XDoclet (or any other code generator) place its output under src. In NetBeans, the NetBeans plugin creates a separate source tree entry for the generated sources; I would think that the Eclipse plugin does the same (or it should if it doesn't). If you put the generated output where it belongs (in target, not in src), the problems you detailed will disappear, I believe. -Original Message- From: Peschier J. (Jeroen) [mailto:[EMAIL PROTECTED] Sent: Monday, January 16, 2006 07:25 To: Maven Users List Subject: RE: Using multiple source directories to produce on artefact I agree that a mavenized build probably does not need multiple source dirs. However, for most of us Maven is not the only tool we use. My use-case for multiple source dirs is to separate XDoclet-generated code. The Maven build will indeed perform fine with the generated source in the same directory as the main sources, but consider what happens outside Maven: (1) In Eclipse you get everything in a single source dir creating a huge tree in the Package Explorer. I know it's possible to filter out the generated source packages but it's not practical unless the maven-eclipse-plugin facilitates this by excluding them from the view for me. (2) When using SCM within Eclipse: because everything is in a single source dir you need to tell Eclipse (for ALL AND EVERY generated package) you want the generated sources excluded from SCM. Again, very impractical. Unless the maven-eclipse-plugin can exclude generated sources from SCM I want it in a separate directory. This separate directory can conveniently be excluded from SCM with a single ignore entry. Although I have things working like I want using the build-helper-maven-plugin I'd still like to be able to set multiple source dirs in the POM as it is much cleaner. I really don't see the argument against multiple source dirs in the POM either. True best-practices evangelists can still continue to use (and preach :) single source directory projects. Nothing is lost with multiple source dirs, it's just convenience that is gained. -Oorspronkelijk bericht- Van: dan tran [mailto:[EMAIL PROTECTED] Verzonden: donderdag 12 januari 2006 17:23 Aan: Maven Users List; [EMAIL PROTECTED] Onderwerp: Re: Using multiple source directories to produce on artefact Yes, build-helper is there for legacy build. However, if a build is completely mavenized, I see no need to have more than one primary source trees and adding a generated source tree the project , shoud be done by the generated source plugin itself. For now, i dont see a way out until at least 2.1, if it supports multiple main source trees ;-) -D - 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: Continuum, Maven2 settings.xml
Can you resolve the host name repo1.maven.org on the same machine but outside of Continuum? This looks like a DNS configuration problem to me. -Original Message- From: Christian Mouttet [mailto:[EMAIL PROTECTED] Sent: Monday, January 16, 2006 10:45 To: continuum-users@maven.apache.org Subject: Continuum, Maven2 settings.xml Hi all, where do I have to place the file 'settings.xml' to configure my proxy, repository mirrors etc.? After adding a Maven2 project I get java.net.UnknownHostException: repo1.maven.org. Any help would be appreciated. regards -chris ** Diese E-Mail wurde auf Viren ueberprueft. [EMAIL PROTECTED] **
RE: maven2 equivalent of dependency properties
No, there is no equivalent in Maven2. I wish there was since some of the stuff I want to do would greatly benefit from this feature. What are you trying to do that needs such properties? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, January 16, 2006 15:37 To: Maven Users List Subject: Re: maven2 equivalent of dependency properties Dennis wrote: Maybe this can help? http://maven.apache.org/guides/mini/guide-configuring-plugins.html Thanks, Dennis. What I'm not seeing (and I realize this could be right under my nose but I just don't know it yet) is how dependency-specific plugin properties are set. I'll quote the version 3.0 schema for the properties element in the Dependency type: Properties about the dependency. Various plugins allow you to mark dependencies with properties. For example the a href=/plugins/war/index.htmlwar/a plugin looks for a war.bundle property, and if found will include the dependency in WEB-INF/lib. For example syntax, check the war plugin docs. Is there an equivalent to this feature in m2? Thanks again. -- Jack Unrue [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: (Strictly limited) circular dependencies with M2
The normal way of handling this kind of dependency tree is to put the common stuff (each service's interface and DTOs) is a separate project. Then each service's project depends on this common stuff project. Make sense? -Original Message- From: andrew cooke [mailto:[EMAIL PROTECTED] Sent: Saturday, January 14, 2006 09:14 To: users@maven.apache.org Subject: (Strictly limited) circular dependencies with M2 Hi, I have been asked to configure Maven 2 for our new project at work. The project architecture is a set of services, each of which will be a separate sub-project in Maven 2. However, each service depends on the *external interfaces* of the services it connects to. I know that generally circular dependencies are a bad thing, so I want to explain carefully why the dependency we have is not: Each service has a contract that it implements. A calling (dependent) service depends on this contract. If the contract is broken, the system will fail. Since the contract is critical, it makes sense to test it as early as possible. Preferably at compile time. We can do this (to a limited extent) by expressing the contract as an interface. So any code that uses service X compiles againts the interface that X provides. We can then insert proxies and messaging so that the services can exist on different machines, etc. More details at http://www.acooke.org/cute/MuleJavaIn0.html Of course, we do not want deep dependencies of one service on another, so the external interfaces are restricted to: - Java interfaces that the service implements - Data transfer objects (serializable, simple beans) How should this be structured? Since the data transfer objects are shared between services and have some additional constraints from the messaging technology (serializable; it would also be useful to have a carefully designed inheritance hierarchy for simplifying routing decisions based on class) I think they should go into a separate messaging project. The interfaces that each service provides, however, belong in the appropriate service. So we have the package structure: project +- messaging | +- data transfer objects +- service 1 | +- external interface | +- implementation +- service 2 . +- external interface . +- implementation +... To build this I need to: - compile messaging (data transfer objects) - compile external interfaces for each service - package external interfaces and message objects (necessary for the messaging system) - compile implementations for each service - package each service (both interface and implementation) (I may also need to package services as ejb3 beans) If I do this, all dependencies are resolved correctly. My question, then, is how do I do this with Maven 2? Sorry I had to write so much to ask it, and further apopolgies if this is really obvious. I've looked around the documentation, but can't see how this level of control is provided. Thanks, Andrew -- ` __ _ __ ___ ___| |_ personal site: http://www.acooke.org/andrew / _` / _/ _ \/ _ \ / / -_) blog: http://www.acooke.org/cute \__,_\__\___/\___/_\_\___| aim: acookeorg; skype: andrew-cooke - 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: Using multiple source directories to produce on artefact
A repost from yesterday...
The XDoclet plugin for Maven expects to place the generated sources in
target/generated-sources/xdoclet and adds it to the compile source list.
If you are specifying a different destination, that may be part of the
problem if the plugin is not doing things quite right. Try changing
your output directory to match the one mentioned above and see if that
helps.
-Original Message-
From: Andreas Zschorn [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 12, 2006 03:08
To: users@maven.apache.org
Subject: Using multiple source directories to produce on artefact
Hi,
I have a question regarding maven 2 and the use of multiple source
directories.
I want to migrate from ant to maven and have a problem with compiling 2
source directories to one output directory.
Directory structure is the following.
./src/ -- with the main source files
./gen-src/ -- with generated ejb-source files from xdoclet.
./target/ -- target of compiled files
In the build section I can only state on source-directory.
The documentation
under
http://maven.apache.org/guides/mini/guide-using-one-source-directory.htm
l
state there is no problem in using several source directories but they
forgot to say how.
Quote:
There should be no limitations in this approach. Maven natively
supports
multiple source directories for the purposes of generated sources.:
I already tried the approach to include the directories in the
configuration
section. The result was, that maven always reported that no files have
changed.
plugins
plugin
artifactIdmaven-compiler-plugin/artifactId
configuration
includes
include${basedir}/src/include
include${basedir}/gen-src/include
/includes
/configuration
/plugin
/plugins
I already searched for a solution but the most answers were to change
the
directory layout which is in my case not possible.
I really appreciate your help.
Another question regarding documentation. Perhaps I was to stupid to
find
it, but is there any good documentation, or book out there for maven 2.
The
current docu on the website does not have the deep I would expect, for
example a good plugin howto or an overview which xml-configurations tags
are
available for a plugin.
Andreas
-
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] Unavoidable multiple source directories: src/sandbox/java
The XDoclet plugin for Maven expects to place the generated sources in target/generated-sources/xdoclet and adds it to the compile source list. If you are specifying a different destination, that may be part of the problem if the plugin is not doing things quite right. Try changing your output directory to match the one mentioned above and see if that helps. BTW, it is not a good idea, usually, to place generated files in the src tree. -Original Message- From: Karthik V [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 11, 2006 12:07 To: Maven Users List Subject: Re: [m2] Unavoidable multiple source directories: src/sandbox/java I am using xdoclet from codehaus in the generate-sources phase... but durin the compile phase, i get errors that all those classes r missing ... On 1/11/06, dan tran [EMAIL PROTECTED] wrote: the xdocdet mojo, if available, will add the generated source automatically However, if you are using antrun plugin to generate source, it can do that for you http://maven.apache.org/plugins/maven-antrun-plugin/run-mojo.html -D On 1/11/06, Karthik V [EMAIL PROTECTED] wrote: I need to add the sources generated thru xdoclet (its in a separate folder).. is there a cleaner way of adding it, other than using this build-helper? On 1/11/06, dan tran [EMAIL PROTECTED] wrote: http://mojo.codehaus.org/build-helper-maven-plugin/ On 1/11/06, Geoffrey [EMAIL PROTECTED] wrote: Hi, What is the best practice to add a second source directory? I am aware it is not recommended to have more then one, but it's unavoidable at this time in the project: src/main/java src/sandbox/java There are cyclic dependencies between both, so making a separate project for both is not an option it seems. -- 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]
RE: unclear explanation in Guide to Developing Java Plugins
Take a look at http://maven.apache.org/guides/introduction/introduction-to-plugin-prefi x-mapping.html -Original Message- From: Rice Yeh [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 10, 2006 04:29 To: Maven Users List Subject: Re: unclear explanation in Guide to Developing Java Plugins Hi Allan, My question is how the prefix hello gotten in the example? Regards, Rice On 1/10/06, Allan Ramirez [EMAIL PROTECTED] wrote: Hi Rice, When executing -DupdateReleaseInfo=true, you are actually forcing to use the latest version of the plugin. And by adding the groupId in the pluginGroups you are saving it so maven can identify where your plugin belongs. Now, Since maven already knows your plugin, Instead of executing it in a long way mvn groupId:artifactId:version:goal, you can now execute it by calling mvn prefix:goal only I hope this helps. Regards, -allan Rice Yeh wrote: Hi, When studing the article Guide to Developing Java Plugins http://maven.apache.org/guides/plugin/guide-java-plugin-development.html in http://maven.apache.org/guides/plugin/guide-java-plugin-development.htm l, there is unclear part on the explanation: the command used to execute a goal is mvn groupID:artifactID:version:goal. In the example, it is mvn sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi. The goal form can be shortened by mvn -DupdateReleaseInfo=true install to save the version part, and add the following to your settings.xmlfile: pluginGroups pluginGroupsample.plugin/pluginGroup /pluginGroups to save the groud part, then the shortened command should be mvn maven-hello-plugin:sayhi . Why does it become mvn hello:sayhi in the article? Can anyone explain it? Regards, Rice --- - No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.16/225 - Release Date: 1/9/2006 - 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: [m201] Plugin Dependency Configuration
Yes. That does work. For anyone following this thread, using Brett's suggestion involves duplicating the plugin stanza from the reporting stanza so it is under buildplugins; after copying the XML, remove the configuration section from the copy in buildplugins and the dependencies section from the copy in reporting. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, January 09, 2006 16:37 To: Maven Users List Subject: Re: [m201] Plugin Dependency Configuration We should also allow them in the reporting section I imagine, for consistency. I will file it in JIRA. However, it should still take effect if you put a plugin definition in your build section with the dependencies and the rest remains in the reporting section. - Brett On 1/9/06, Kees de Kooter [EMAIL PROTECTED] wrote: According to the maven xsd dependencies are not allowed inside reporting/plugins/plugin tags. - 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: Trouble in generating source files
For an example, let's say you have a Java source at
src/main/java/com/junk/JunkBean.java
For it to compile correctly, it needs to have a package com.junk; in
it, right?
When XDoclet walks the source starting at src/main, it find a source
file that identifies itself as being in package com.junk but it finds
the source in package java.com.junk. Since the two don't match,
XDoclet assumes that there is a serious problem with the source file and
ignores it.
-Original Message-
From: Karthik V [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 10, 2006 12:48
To: Maven Users List
Subject: Re: Trouble in generating source files
weird, but i found the answer myself ... changed the line
fileset dir=src/main
to
fileset dir=src/main/java
and it worked. What I dont understand is, why doesnt the line
include name=**/beans/**/*Bean.java/
search inside the main folder and locate the source files? Does it
really
make a difference when I add the subfolder java when I use **/** ?
On 1/10/06, Karthik V [EMAIL PROTECTED] wrote:
Below is a snippet from my m2 project pom. I used this fine in m1 (in
the
form of project.properties) and generated source using xdoclet. But
now, I
dont get a single java file, though I get some required xml files.
execution
phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks
ejbdoclet
ejbSpec=2.0
excludedtags=@version,@author
addedtags=@xdoclet-generated at ${TODAY}
destdir=target/gen-src
fileset dir=src/main
include name=**/beans/**/*Bean.java/
/fileset
utilobject cacheHomes=true/
remoteinterface /
localinterface /
homeinterface /
localhomeinterface /
valueobject /
/tasks
/configuration
/execution
The output goes like this -
[INFO] [xdoclet:xdoclet {execution: default}]
[INFO] Initializing DocletTasks!!!
[INFO] Executing tasks
INFO:Some classes refer to other classes that were not found among
the
sources or on the classpath.
(Perhaps the referred class doesn't exist? Hasn't been
generated
yet?)
The referring classes do not import any fully qualified
classes
matching these classes.
However, since no packages are imported, xjavadoc has assumed
that the referred classes
belong to the same package as the referring class. The
classes
are:
(this goes on with some lines like)
C:\src\main\java\abc\def\pojo\ABC.java -- RequestObject qualified to
abc.def.pojo.RequestObject
[INFO] Executed tasks
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Then it goes on to the compiler:compile task, breaking the build.
Can some one help?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m201] Plugin Dependency Configuration
Anybody have any idea what I am doing wrong? -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Friday, January 06, 2006 06:52 To: Maven Users List Subject: [m201] Plugin Dependency Configuration I am trying to configure a plugin with dependencies. According to the current project descriptor document (http://maven.apache.org/maven-model/maven.html), I should do the following: project build plugins plugin groupId/ artifactId/ dependencies dependency groupId/ artifactId/ /dependency /dependencies configuration/ /plugin /plugins /build /project When I do this, I get a parse error on the POM that the dependencies tag within the plugin is unrecognized. - 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: [m201] Plugin Dependency Configuration
?xml version=1.0 encoding=ISO-8859-1? project modelVersion4.0.0/modelVersion groupIdqaccess/groupId artifactIdtoplevel/artifactId packagingpom/packaging nameBob's Maven 2.0 Experiment/name version3.0-SNAPSHOT/version urlhttp://qadev-home.dev.qintra.com//url issueManagement systemMantis/system urlhttp://qadev-home.dev.qintra.com/mantis/url /issueManagement ciManagement systemcontinuum/system notifiers notifier typemail/type address[EMAIL PROTECTED]/address /notifier /notifiers /ciManagement inceptionYear2004/inceptionYear developers developer idallisord/id nameBob Allison/name email[EMAIL PROTECTED]/email organizationQwest/organization roles roleDeveloper/role /roles timezone-5/timezone /developer /developers contributors /contributors licenses license nameQwest Proprietary/name urlhttp://qadev-home.dev.qintra.com/m2/LICENSE.txt/url distributionmanual/distribution /license /licenses scm connectionscm:svn:file:///svn/qaccess/trunk/connection developerConnectionscm:svn:file:///svn/qaccess/trunk/developerConnect ion /scm organization nameQwest/name urlhttp://www.qwest.com//url /organization build defaultGoaltest/defaultGoal pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-deploy-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.4/source target1.4/target /configuration /plugin /plugins /pluginManagement /build dependencies /dependencies reporting plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId dependencies dependency groupIdqaccess/groupId artifactIdbuild-tools/artifactId version3.0-SNAPSHOT/version /dependency /dependencies configuration configLocationstyle/Q.Access.xml/configLocation headerLocationLICENSE.txt/headerLocation /configuration /plugin /plugins /reporting /project -Original Message- From: Kees de Kooter [mailto:[EMAIL PROTECTED] Sent: Monday, January 09, 2006 05:24 To: Maven Users List Subject: Re: [m201] Plugin Dependency Configuration On 1/9/06, Allison, Bob [EMAIL PROTECTED] wrote: Anybody have any idea what I am doing wrong? Could you please post your pom? - 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]
[m201] Plugin Dependency Configuration
I am trying to configure a plugin with dependencies. According to the current project descriptor document (http://maven.apache.org/maven-model/maven.html), I should do the following: project build plugins plugin groupId/ artifactId/ dependencies dependency groupId/ artifactId/ /dependency /dependencies configuration/ /plugin /plugins /build /project When I do this, I get a parse error on the POM that the dependencies tag within the plugin is unrecognized. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven2 + XDoclet
Here's an example from something I am playing with at home. It
generates both the ejb and client jars. I use the two properties at the
top just to simplify the stuff in the ejbdoclet definition:
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;
properties
xdocletSource${project.build.directory}/generated-sources/xdoclet/xdo
cletSource
xdocletXML${project.build.outputDirectory}/META-INF/xdocletXML
/properties
modelVersion4.0.0/modelVersion
groupIdaddrbook/groupId
artifactIdaddrbook-ejb/artifactId
packagingejb/packaging
version1.0-SNAPSHOT/version
nameFamily Address Book EJBs/name
urlhttps://sd.no-ip.biz/addrbook/url
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
dependency
groupIdJBoss/groupId
artifactIdjboss-j2ee/artifactId
version4.0.3SP1/version
scopeprovided/scope
/dependency
/dependencies
build
finalNameaddrbook-ejb/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb-plugin/artifactId
configuration
generateClienttrue/generateClient
/configuration
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdxdoclet-maven-plugin/artifactId
executions
execution
phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks
ejbdoclet
destdir=${xdocletSource}
excludedtags=@version,@author
ejbspec=2.0
mergedir=src/xdoclet
force=${xdoclet.force}
fileset dir=src/main/java
include name=**/ejb/*Bean.java/
/fileset
packageSubstitution packages=ejb
substituteWith=ejbif/
remoteinterface/
homeinterface/
localinterface/
localhomeinterface/
entitypk/
entitybmp/
entitycmp/
utilobject cacheHomes=true kind=physical/
valueobject
packageSubstitution packages=ejb
substituteWith=data/
/valueobject
deploymentdescriptor destdir=${xdocletXML}/
!-- AS 4/29/02 Do not validate XML files because
JBoss 3.0 message driven will
report an wrong error because it uses the wrong
jboss.dtd --
jboss version=4.0
xmlencoding=UTF-8
typemapping=PostgreSQL
datasource=java:AddrBookDS
destdir=${xdocletXML}
validateXml=false
/
/ejbdoclet
/tasks
/configuration
/execution
/executions
/plugin
/plugins
/build
/project
-Original Message-
From: Dmitriy D. [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 05, 2006 03:06
To: users@maven.apache.org
Subject: Maven2 + XDoclet
Hi!
Has anyone experienced using xdoclet plugin on maven2? I need to perform
several xdoclet tasks in my build (generate hbm.xml, struts-config.xml
etc). Which plugin (group-id, artifact-id, version) should I use? I
would really appreciate if you could write some example pom or point to
some existing guidelines on the web.
Thanks in advance!
Best regards,
Dmitriy
-
Don't limit your challenges,
Challenge your limits!
-
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: How can I create ejb-jar and ejb-client-jar withmaven-ejb-plugin in Maven 2?
To generate both jars, you need to tell the plugin that you want both of them as follows: project ... build ... plugins ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient /configuration /plugin ... plugins ... /build ... /project -Original Message- From: Stefan Rademacher [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 03:14 To: Maven Users List Subject: How can I create ejb-jar and ejb-client-jar withmaven-ejb-plugin in Maven 2? Hello, Could anyone provide me with a working example of a project, which uses the maven-ejb-plugin to generate jar files for the ejb-module and for the ejb-client? (I use the xdoclet-maven-plugin to generate the ejb artifacts to the folder 'targets/generated-sources/xdoclet') I'm quite new to maven and don't understand the usage example given on plugins' webpage (http://maven.apache.org/plugins/maven-ejb-plugin/howto.html). When I integrate that XML to my POM, nothing happens. Only calling 'mvn ejb:ejb' manually works, as long as I copy the META-INF-folder from 'target/generated-sources/xdoclet' to 'target/classes' first. How can I integrate this into my build process (mvn package: ejb-jar and ejb-client-jar are generated. mvn install: ejb-jar and ejb-client-jar are copied to my local repository...)? Thanks a lot in advance! Regards, Stefan - 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: Antw: RE: How can I create ejb-jar and ejb-client-jarwithmaven-ejb-plugin in Maven 2?
You need to specify the destdir attribute of the deploymentDescriptor subtask to point it to the correct location. -Original Message- From: Stefan Rademacher [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 08:12 To: users@maven.apache.org Subject: Antw: RE: How can I create ejb-jar and ejb-client-jarwithmaven-ejb-plugin in Maven 2? Hello, thank you. I already had this code in my POM but the packaging was set to jar. Now I changed it to ejb and it works fine. Now there is one more problem. The maven-ejb-plugin doesn't find the deployment descriptors. It searches in target/classes/META-INF but the files are generated by xdoclet-maven-plugin to target/generated-sources/xdoclet/META-INF. What is the right way to make the maven-ejb-plugin find the deployment descriptors? Thanks for your help! Bye, Stefan [EMAIL PROTECTED] 05.01.2006 12:24:48 To generate both jars, you need to tell the plugin that you want both of them as follows: project ... build ... plugins ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient /configuration /plugin ... plugins ... /build ... /project -Original Message- From: Stefan Rademacher [mailto:[EMAIL PROTECTED] Sent: Thursday, January 05, 2006 03:14 To: Maven Users List Subject: How can I create ejb-jar and ejb-client-jar withmaven-ejb-plugin in Maven 2? Hello, Could anyone provide me with a working example of a project, which uses the maven-ejb-plugin to generate jar files for the ejb-module and for the ejb-client? (I use the xdoclet-maven-plugin to generate the ejb artifacts to the folder 'targets/generated-sources/xdoclet') I'm quite new to maven and don't understand the usage example given on plugins' webpage (http://maven.apache.org/plugins/maven-ejb-plugin/howto.html). When I integrate that XML to my POM, nothing happens. Only calling 'mvn ejb:ejb' manually works, as long as I copy the META-INF-folder from 'target/generated-sources/xdoclet' to 'target/classes' first. How can I integrate this into my build process (mvn package: ejb-jar and ejb-client-jar are generated. mvn install: ejb-jar and ejb-client-jar are copied to my local repository...)? Thanks a lot in advance! Regards, Stefan - 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]
RE: [M2] SerialVersionUID solution / Maven compiler settings
IIRC, a serializable class which does not define its serialVersionUID gets a new one every time it is compiled, regardless of what compiler is being used. What I had read as the correct solution is for the class to explicitly define serialVersionUID. Of course, doing that means that you lose the protection that the class hasn't been changed. The only other solution is to ensure that the unit tests run from Eclipse use the same class files that were sent to the application server. -Original Message- From: Peschier J. (Jeroen) [mailto:[EMAIL PROTECTED] Sent: Thursday, December 01, 2005 09:37 To: users@maven.apache.org Subject: [M2] SerialVersionUID solution / Maven compiler settings My use-case: I build an EAR using Maven 2 and the Sun SDK 1.4.2. For testing I tend to run a few JUnit tests from Eclipse. These tests typically invoke some remote beans on the application server. This gives me the dreaded InvalidClassException because the local serialVersionUID differs from the remote serialVersionUID. Evalution: I think most of us dealing with RMI have encountered this problem before. It is known that different compilers generate different serialVersionUIDs for the same class. In my case the remote classes are generated with the Sun JavaC while the local classes are generated by Eclipse JDT. Plan: Although this problem is not actually a Maven 2 issue, I was thinking Maven 2 could assist in the solution to the problem. The maven-compiler-plugin has a compilerId setting which seems to indicate it can be reconfigured to use another compiler. Would it be possible for M2 to use the Eclipse compiler so that the artifacts will have the same serialVersionUID as in Eclipse? If so, how would I go about this? P.S. I know I can manually add serialVersionUIDs to serializable classes, but this is not an option as most of my serializable classes are value objects generated by XDoclet. XDoclet does not have a way of specifying serialVersionUID for generated value objects. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2] Repository
How do I get access to the recent snapshot? The downloads on the download page are from May and the CVS information doesn't work: $ cvs -d :pserver:[EMAIL PROTECTED]:/scm/maven-proxy/ co maven-proxy /scm/maven-proxy/: no such repository -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Monday, November 28, 2005 03:07 To: Maven Users List Subject: RE: [M2] Repository Law Green-A20134 wrote on Monday, November 28, 2005 6:28 AM: Jason, Thank you so much for your patient reply! I have updated the diagram as per your comments, please let me know if it need further update. [snip] Funny. This is quite the same setup I created also some weeks ago. We just use two local repos, one for released artitacts and one for snapshots. And I guess it would be better to fake a sample suite to reflect the topology, including settings.xml, pom.xml, maven-proxy.properties. I would like to help with this task. For M2 support of maven-proxy, it is essential currently to use a recent snapshout (because of MAVENPROXY-34) and possibly apply (MAVENPROPXY-36). - Jörg - 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] Repository
When I do that, I get three files: maven-proxy-webapp/0.1/maven-proxy-webapp-0.1.pom, maven-proxy-core/0.1/maven-proxy-core-0.1.pom, and maven-proxy-standalone/0.1/maven-proxy-standalone-0.1.pom. The POMs do not have any dependencies (they are bare-bones POMs with just group, artifact, and version). There are no source files. Is something missing in the repository? -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Monday, November 28, 2005 08:12 To: Maven Users List Subject: RE: [M2] Repository Hi Bob, Allison, Bob wrote on Monday, November 28, 2005 1:25 PM: How do I get access to the recent snapshot? The downloads on the download page are from May and the CVS information doesn't work: $ cvs -d pserver:[EMAIL PROTECTED]:/scm/maven-pro xy/ co maven-proxy /scm/maven-proxy/: no such repository svn co svn://svn.codehaus.org/maven/scm/repository/maven-proxy ;-) - Jörg -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Monday, November 28, 2005 03:07 To: Maven Users List Subject: RE: [M2] Repository Law Green-A20134 wrote on Monday, November 28, 2005 6:28 AM: Jason, Thank you so much for your patient reply! I have updated the diagram as per your comments, please let me know if it need further update. [snip] Funny. This is quite the same setup I created also some weeks ago. We just use two local repos, one for released artitacts and one for snapshots. And I guess it would be better to fake a sample suite to reflect the topology, including settings.xml, pom.xml, maven-proxy.properties. I would like to help with this task. For M2 support of maven-proxy, it is essential currently to use a recent snapshout (because of MAVENPROXY-34) and possibly apply (MAVENPROPXY-36). - Jörg - 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]
RE: [M2] Repository
For anyone following this thread, the final correct command is: cvs -d :pserver:[EMAIL PROTECTED]:/home/projects/maven-proxy/scm co maven-proxy -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Monday, November 28, 2005 09:46 To: Maven Users List Subject: RE: [M2] Repository Hi Bob, sorry for my misinformation, the svn address below was actually a pointer in the POM repository of maven. I switched there by accident since the directory is also called maven-proxy. $ cvs -d pserver:[EMAIL PROTECTED]:/scm/maven-pro xy/ co maven-proxy /scm/maven-proxy/: no such repository It should be: cvs -d pserver:[EMAIL PROTECTED]:/scm/maven-proxy/scm co maven-proxy = snip === $ cat CVS/Root :pserver:[EMAIL PROTECTED]:/home/projects/maven-proxy/scm $ cat CVS/Repository maven-proxy = snip === - Jörg - 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: RPM Plugin not cleaning its includes
The first line of output tells me that you didn't run mvn rpm:rpm,
since it was looking for a prefix of jar instead of rpm. If you did
try to run mvn rpm:rpm, please send me a copy of your pom.xml so I can
see what is wrong.
You probably don't want to try to build the pieces, since there are a
couple different projects extracted from various places that you need to
build. Since these are updates to the current release, they (and a few
of their dependencies) have versions ending in SNAPSHOT; this is why the
checks for updates, I believe.
-Original Message-
From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED]
Sent: Friday, November 25, 2005 07:02
To: Maven Users List
Subject: Re: RPM Plugin not cleaning its includes
After unipping to my directory I am getting :
Searching repository for plugin with prefix: 'jar'.
[INFO] org.apache.maven.plugins: checking for updates from central
[INFO] org.codehaus.mojo: checking for updates from central
[INFO] artifact org.apache.maven.plugins:maven-jar-plugin: checking
for updates from central
[INFO] artifact org.codehaus.mojo:rpm-maven-plugin: checking for
updates from central
Could you zip the project for me and I'll build and install it locally?
Thx
On 24/11/05, Allison, Bob [EMAIL PROTECTED] wrote:
I think I have the problem with the RPM plugin solved and I updated
the
ZIP file[1]. Could you please download the current version, unpack
the
ZIP file at the top of your Maven 2 repository, and let me know if
this
solves the problem for you?
[1] http://beaver.codehaus.org/~boba/rpm-plugin.zip
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 13:36
To: Maven Users List
Subject: RE: RPM Plugin not cleaning its includes
I found the problem. Now I just need to figure out a solution. I'll
let you know when I get this figured out (probably over the weekend).
-Original Message-
From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 11:07
To: Maven Users List
Subject: Re: RPM Plugin not cleaning its includes
Hi Bob,
We are trying to do the following :
-- Install ${basedir}/src/main/bin/* at /usr/local/amf/bin
${basedir}/src/main/bin/* -- /usr/local/amf/bin
-- Install ${basedir}/target/*.jar at /usr/local/amf/plugin/core/lib
${basedir}/target/*.jar -- /usr/local/amf/plugin/core/lib
We are using the following mappings fragment having looked at your
suggestions regarding the filename elemnt and still the contents of
the first mapping turn when copying the contents for the second
mapping.
mappings
mapping
directory/usr/local/amf/bin/directory
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
include*/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
/excludes
/source
/sources
/mapping
mapping
directory/usr/local/amf/plugin/core/lib/directory
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationtarget/location
includes
include*.jar/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
exclude*/*/exclude
/excludes
/source
/sources
/mapping
Any ideas?
Thanks in advance
Regards
On 23/11/05, Allison, Bob [EMAIL PROTECTED] wrote:
Well, I see a couple problems with your configuration. As I read
the
two mappings, they should do the following:
-- Install ${basedir}/src/main/bin/* at /usr/local (for example,
${basedir}/src/main/bin/myprog will be installed at
/usr/local/myprog)
-- Install ${basedir}/target/*.jar at /usr/local (for example,
${basedir}/target/myprog.jar will be installed at
/usr/local/myprog.jar)
You are getting the two mappings muddled because
RE: RPM Plugin not cleaning its includes
I think I have the problem with the RPM plugin solved and I updated the
ZIP file[1]. Could you please download the current version, unpack the
ZIP file at the top of your Maven 2 repository, and let me know if this
solves the problem for you?
[1] http://beaver.codehaus.org/~boba/rpm-plugin.zip
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 13:36
To: Maven Users List
Subject: RE: RPM Plugin not cleaning its includes
I found the problem. Now I just need to figure out a solution. I'll
let you know when I get this figured out (probably over the weekend).
-Original Message-
From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 11:07
To: Maven Users List
Subject: Re: RPM Plugin not cleaning its includes
Hi Bob,
We are trying to do the following :
-- Install ${basedir}/src/main/bin/* at /usr/local/amf/bin
${basedir}/src/main/bin/* -- /usr/local/amf/bin
-- Install ${basedir}/target/*.jar at /usr/local/amf/plugin/core/lib
${basedir}/target/*.jar -- /usr/local/amf/plugin/core/lib
We are using the following mappings fragment having looked at your
suggestions regarding the filename elemnt and still the contents of
the first mapping turn when copying the contents for the second
mapping.
mappings
mapping
directory/usr/local/amf/bin/directory
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
include*/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
/excludes
/source
/sources
/mapping
mapping
directory/usr/local/amf/plugin/core/lib/directory
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationtarget/location
includes
include*.jar/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
exclude*/*/exclude
/excludes
/source
/sources
/mapping
Any ideas?
Thanks in advance
Regards
On 23/11/05, Allison, Bob [EMAIL PROTECTED] wrote:
Well, I see a couple problems with your configuration. As I read the
two mappings, they should do the following:
-- Install ${basedir}/src/main/bin/* at /usr/local (for example,
${basedir}/src/main/bin/myprog will be installed at /usr/local/myprog)
-- Install ${basedir}/target/*.jar at /usr/local (for example,
${basedir}/target/myprog.jar will be installed at
/usr/local/myprog.jar)
You are getting the two mappings muddled because they specify the same
destination. You will probably almost never need to specify the
filename parameter. Instead, the directory parameters should be
specified as /usr/local/amf/bin and /usr/local/amf/plugin/core/lib.
-Original Message-
From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 08:38
To: users@maven.apache.org
Subject: RPM Plugin not cleaning its includes
Hi Bob,
It appears that the RPM plugin cumulatively includes the contents of
includes when dealing wiith mappings. For example, the following 2
mappings cause thhe contents of the first ampping, a bunch of scripts
from the bin directory, to be copied into the next filename/
specified amf/plugin/core/lib.
Any ideas would be appreciated.
Regards
mappings
mapping
directory/usr/local/directory
filenameamf/bin/filename
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
RE: RPM Plugin not cleaning its includes
I found the problem. Now I just need to figure out a solution. I'll
let you know when I get this figured out (probably over the weekend).
-Original Message-
From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 11:07
To: Maven Users List
Subject: Re: RPM Plugin not cleaning its includes
Hi Bob,
We are trying to do the following :
-- Install ${basedir}/src/main/bin/* at /usr/local/amf/bin
${basedir}/src/main/bin/* -- /usr/local/amf/bin
-- Install ${basedir}/target/*.jar at /usr/local/amf/plugin/core/lib
${basedir}/target/*.jar -- /usr/local/amf/plugin/core/lib
We are using the following mappings fragment having looked at your
suggestions regarding the filename elemnt and still the contents of
the first mapping turn when copying the contents for the second
mapping.
mappings
mapping
directory/usr/local/amf/bin/directory
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
include*/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
/excludes
/source
/sources
/mapping
mapping
directory/usr/local/amf/plugin/core/lib/directory
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationtarget/location
includes
include*.jar/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
exclude*/*/exclude
/excludes
/source
/sources
/mapping
Any ideas?
Thanks in advance
Regards
On 23/11/05, Allison, Bob [EMAIL PROTECTED] wrote:
Well, I see a couple problems with your configuration. As I read the
two mappings, they should do the following:
-- Install ${basedir}/src/main/bin/* at /usr/local (for example,
${basedir}/src/main/bin/myprog will be installed at /usr/local/myprog)
-- Install ${basedir}/target/*.jar at /usr/local (for example,
${basedir}/target/myprog.jar will be installed at
/usr/local/myprog.jar)
You are getting the two mappings muddled because they specify the same
destination. You will probably almost never need to specify the
filename parameter. Instead, the directory parameters should be
specified as /usr/local/amf/bin and /usr/local/amf/plugin/core/lib.
-Original Message-
From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 08:38
To: users@maven.apache.org
Subject: RPM Plugin not cleaning its includes
Hi Bob,
It appears that the RPM plugin cumulatively includes the contents of
includes when dealing wiith mappings. For example, the following 2
mappings cause thhe contents of the first ampping, a bunch of scripts
from the bin directory, to be copied into the next filename/
specified amf/plugin/core/lib.
Any ideas would be appreciated.
Regards
mappings
mapping
directory/usr/local/directory
filenameamf/bin/filename
filemode755/filemode
usernameroot/username
groupnamesystem/groupname
sources
source
locationsrc/main/bin/location
includes
include*/include
/includes
excludes
excludeCVS/exclude
excludeCVS/*/exclude
/excludes
/source
/sources
/mapping
mapping
directory/usr
RE: [m2] Copy the dependencies of a project in a custom plugin
The tag @requiresDependencyResolution has to be on the class, not the
parameter.
-Original Message-
From: Wim Deblauwe [mailto:[EMAIL PROTECTED]
Sent: Monday, November 21, 2005 06:41
To: Maven Users List
Subject: Re: [m2] Copy the dependencies of a project in a custom plugin
The collection of artifacts is empty. When I was using dependencies, it
was
not empty. What am I doing wrong? This is my code:
/**
* @goal process-resources
* @description Copy the dependencies for the InstallShield Merge Module
*/
public class MsmProcessResourcesMojo extends AbstractMojo
{
/**
* @parameter expression=${project.artifacts}
* @requiresDependencyResolution
*/
private Collection artifacts;
/**
* @parameter expression=${project.build.directory}/resources
*/
private File targetDirectory;
public MsmProcessResourcesMojo()
{
}
public void execute() throws MojoExecutionException,
MojoFailureException
{
try
{
getLog().info( Process Resources for InstallShield Merge Module... );
Iterator iterator = artifacts.iterator();
while (iterator.hasNext())
{
Artifact artifact = (Artifact)iterator.next();
FileUtils.copyFileToDirectory( artifact.getFile(), new File(
targetDirectory, artifact.getType() + s ) );
}
}
catch (IOException e)
{
throw new MojoExecutionException( Error copying artifacts, e );
}
}
}
thank you,
Wim
2005/11/21, Brett Porter [EMAIL PROTECTED]:
maven-artifact and maven-project (though you may not need the project
dependency if you are just using the expression below as it is
runtime, and Mavne provides it).
- Brett
On 11/21/05, Wim Deblauwe [EMAIL PROTECTED] wrote:
What dependency do I need for the Artifact and Project classes in my
Mojo?
2005/11/21, Brett Porter [EMAIL PROTECTED]:
On 11/21/05, Wim Deblauwe [EMAIL PROTECTED] wrote:
Hi,
I'm writing a custom plugin and I need to copy the project's
dependencies
from the local repository to a certain directory. How can I do
this
best?
You should use ${project.artifacts} instead which includes all the
transitive artifacts, and for which you can call
artifact.getFile().
Make sure you include @requiresDependencyResolution
question 2:
When my plugin works, it will produce a different artifact
(.msm),
how
should I handle the 'instal' and 'deploy' of that artifact? Do I
need to
write my own custom mojo for that or can I re-use the plugins
already
written for .jar files?
You can reuse the mojos, but you will still need to define the
customisations, which will require a plugin. There are examples in
the
introduction to the build lifecycle.
Cheers,
Brett
-
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]
[m2] RPM Plugin Source [was: Plugin Unit Tests?]
The plugin is in the Mojo (http://mojo.codehaus.org/) project's sandbox. Which download link on which site doesn't work? -Original Message- From: Sena Gbeckor-Kove [mailto:[EMAIL PROTECTED] Sent: Friday, November 18, 2005 09:08 To: Maven Users List Subject: Re: Plugin Unit Tests? Hi Bob, I am trying to use your RPM plugin but can't find th code in svn and the download link on the site doesn't work. Are you still working on it? Thx On 15/11/05, Allison, Bob [EMAIL PROTECTED] wrote: That was it. Thanks! -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 11:35 To: Maven Users List Subject: Re: Plugin Unit Tests? -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The sandbox got moved out of /components/trunk... :-) New URL is: https://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-it-plugin/ HTH, - -john Allison, Bob wrote: | OK. Maybe I'm not checking out the correct maven2 trunk. | | The URL I am using is | http://svn.apache.org/repos/asf/maven/components/trunk; (which is the | URL specified in the Building Maven 2.0 document. In the top | directory of the stuff checked out are benchmark, bootstrap, | examples, integration-tests, a few files, and a number of | directories named maven- There is no directory named sandbox or | components or plugins and the maven-plugins directory does not | have anything named sandbox. | | Please tell me what I am missing. | | -Original Message- | From: Vincent Massol [mailto:[EMAIL PROTECTED] | Sent: Tuesday, November 15, 2005 10:19 | To: 'Maven Users List' | Subject: RE: Plugin Unit Tests? | | | Bob, | | |-Original Message- |From: Allison, Bob [mailto:[EMAIL PROTECTED] |Sent: mardi 15 novembre 2005 15:51 |To: Maven Users List |Subject: RE: Plugin Unit Tests? | |I don't see maven-components/sandbox or anything named it in |mojo/mojo-sandbox. | |Could you be a little more specific where the plugin is located? | | | It's not in mojo, it's in the maven2 trunk. If you check it out you'll | see a | components/sandbox/plugins dir | | -Vincent | | |-Original Message- |From: Vincent Massol [mailto:[EMAIL PROTECTED] |Sent: Tuesday, November 15, 2005 09:46 |To: 'Maven Users List' |Subject: RE: Plugin Unit Tests? | | |Hi Bob, | |To test a plugin the best solution is to use the it plugin in |components/sandbox/plugins. | |It allows you to put test projects in src/test/it. | |-Vincent | | |-Original Message- |From: Allison, Bob [mailto:[EMAIL PROTECTED] |Sent: mardi 15 novembre 2005 15:35 |To: Maven Users List |Subject: Plugin Unit Tests? | |I was trying to build some unit tests for the RPM plugin and am | |running | |into a chicken-and-egg problem. To test the newly-compiled plugin, | | it | |seems that I need to complete the install phase so that the plugin | | is | |available for the tests to run. If I alter the configuration to | | skip | |the unit tests, it will install the new plugin but I can't run any | |tests | |(since they are skipped). | |Am I taking the wrong approach? | | | | - | |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] | | | - | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDeg4AK3h2CZwO/4URAtXeAJ9wxilZQT33kiZWQ2yxb3PeOZ47YwCgpFh7 vsbbuhRAuJPgjZN4lag0zUI= =gKKP -END PGP SIGNATURE- - 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]
RE: [M2] Xdoclet plugin and hibernate task
A couple questions: Where does BaseObject come from? According to the error message, it is not in the source tree and not on the class path. If should be in the source tree, there is something wrong with that source file. If it comes from Hibernate, you need to import the class (NOT the package) for XDoclet to work correctly. Do these four classes compile correctly if you skip running XDoclet? To do this, comment out the XDoclet stuff from your pom.xml and try mvn compile again. If they do not compile for reasons other than missing classes that XDoclet would be providing, you need to fix these errors before XDoclet will work without problems. There are a number of compile problems that XDoclet won't mind but there are some (like unknown classes) which prevent XDoclet from being able to work properly. -Original Message- From: Srepfler Srgjan [mailto:[EMAIL PROTECTED] Sent: Friday, November 18, 2005 11:42 To: Maven Users List Subject: [M2] Xdoclet plugin and hibernate task Hi, I've been trying the xdoclet plugin 1.0-alpha-2 from org.codehaus.mojo ; I've tried to compile some standard hibernate annotated classes from the appfuse project and I'm getting this error: Below is the pom.xml, any ideas why am I getting this error message? Thanks in advance, keep up the good work with maven2 and does anyone know will there be soon a plugin for xdoclet2? [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'xdoclet'. [INFO] [INFO] Building jspArt EJB Module [INFO]task-segment: [xdoclet:xdoclet] [INFO] [WARNING] This artifact has been relocated to javax.sql:jdbc-stdext:2.0. [INFO] [xdoclet:xdoclet] [INFO] Initializing DocletTasks!!! [INFO] Executing tasks (XDocletMain.start 47 ) Running hibernate/ INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Add ress.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Rol e.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Use r.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Use rCookie.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Add ress.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Rol e.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Use r.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Use rCookie.java -- BaseObject qualified to org.appfuse.model.BaseObject [INFO] Executed tasks [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Fri Nov 18 17:37:15 CET 2005 [INFO] Final Memory: 3M/7M [INFO] here is my project's pom.xml: 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 groupIdit.sigmalab.jspart/groupId artifactIdjspArtEjb/artifactId packagingejb/packaging version1.0-SNAPSHOT/version namejspArt EJB Module/name urlhttp://www.sigmalab.net/jspart/url build pluginManagement plugins plugin artifactIdxdoclet-maven-plugin/artifactId groupIdorg.codehaus.mojo/groupId version1.0-alpha-2/version executions execution goals goalxdoclet/goal /goals /execution
RE: [M2] Xdoclet plugin and hibernate task
So do all five classes compile without using XDoclet? -Original Message- From: Srepfler Srgjan [mailto:[EMAIL PROTECTED] Sent: Friday, November 18, 2005 12:00 To: Maven Users List Subject: Re: [M2] Xdoclet plugin and hibernate task BaseObject is in the same folter as the model objects. Allison, Bob wrote: A couple questions: Where does BaseObject come from? According to the error message, it is not in the source tree and not on the class path. If should be in the source tree, there is something wrong with that source file. If it comes from Hibernate, you need to import the class (NOT the package) for XDoclet to work correctly. Do these four classes compile correctly if you skip running XDoclet? To do this, comment out the XDoclet stuff from your pom.xml and try mvn compile again. If they do not compile for reasons other than missing classes that XDoclet would be providing, you need to fix these errors before XDoclet will work without problems. There are a number of compile problems that XDoclet won't mind but there are some (like unknown classes) which prevent XDoclet from being able to work properly. -Original Message- From: Srepfler Srgjan [mailto:[EMAIL PROTECTED] Sent: Friday, November 18, 2005 11:42 To: Maven Users List Subject: [M2] Xdoclet plugin and hibernate task Hi, I've been trying the xdoclet plugin 1.0-alpha-2 from org.codehaus.mojo ; I've tried to compile some standard hibernate annotated classes from the appfuse project and I'm getting this error: Below is the pom.xml, any ideas why am I getting this error message? Thanks in advance, keep up the good work with maven2 and does anyone know will there be soon a plugin for xdoclet2? [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'xdoclet'. [INFO] --- - [INFO] Building jspArt EJB Module [INFO]task-segment: [xdoclet:xdoclet] [INFO] --- - [WARNING] This artifact has been relocated to javax.sql:jdbc-stdext:2.0. [INFO] [xdoclet:xdoclet] [INFO] Initializing DocletTasks!!! [INFO] Executing tasks (XDocletMain.start 47 ) Running hibernate/ INFO:Some classes refer to other classes that were not found among the sources or on the classpath. (Perhaps the referred class doesn't exist? Hasn't been generated yet?) The referring classes do not import any fully qualified classes matching these classes. However, since no packages are imported, xjavadoc has assumed that the referred classes belong to the same package as the referring class. The classes are: C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Ad d ress.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Ro l e.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Us e r.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Us e rCookie.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Ad d ress.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Ro l e.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Us e r.java -- BaseObject qualified to org.appfuse.model.BaseObject C:\Documents and Settings\User Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Us e rCookie.java -- BaseObject qualified to org.appfuse.model.BaseObject [INFO] Executed tasks [INFO] --- - [INFO] BUILD SUCCESSFUL [INFO] --- - [INFO] Total time: 4 seconds [INFO] Finished at: Fri Nov 18 17:37:15 CET 2005 [INFO] Final Memory: 3M/7M [INFO] --- - here is my project's pom.xml: 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 groupIdit.sigmalab.jspart/groupId artifactIdjspArtEjb/artifactId packagingejb/packaging version1.0-SNAPSHOT/version namejspArt EJB Module/name urlhttp://www.sigmalab.net/jspart/url build
RE: [M2] Xdoclet plugin and hibernate task
I'm not really sure why the messages from XDoclet, since the classes
look fine. My guess is that XDoclet is ignoring abstract classes in
deciding if it can find the class. I think this is something you need
to take to the XDoclet list, since I don't think it is a maven problem.
-Original Message-
From: Srepfler Srgjan [mailto:[EMAIL PROTECTED]
Sent: Friday, November 18, 2005 12:03
To: Maven Users List
Subject: Re: [M2] Xdoclet plugin and hibernate task
The classes compile just fine, here's a a class and the baseobject;
User.java:
package org.appfuse.model;
import java.io.Serializable;
import java.util.HashSet;
import java.util.Set;
import org.apache.commons.lang.builder.EqualsBuilder;
import org.apache.commons.lang.builder.HashCodeBuilder;
import org.apache.commons.lang.builder.ToStringBuilder;
import org.apache.commons.lang.builder.ToStringStyle;
/**
* User class
*
* This class is used to generate the Struts Validator Form as well as
the
* Hibernate mapping file.
*
* pa href=User.java.htmliView Source/i/a/p
*
* @author a href=mailto:[EMAIL PROTECTED]Matt Raible/a
* Updated by Dan Kibler ([EMAIL PROTECTED])
*
* @struts.form include-all=true extends=BaseForm
* @hibernate.class table=app_user
*/
public class User extends BaseObject implements Serializable {
private static final long serialVersionUID = 3832626162173359411L;
protected String username;
protected String password;
protected String confirmPassword;
protected String firstName;
protected String lastName;
protected Address address = new Address();
protected String phoneNumber;
protected String email;
protected String website;
protected String passwordHint;
protected Integer version;
protected Set roles = new HashSet();
protected Boolean enabled;
/**
* Returns the username.
*
* @return String
*
* @struts.validator type=required
* @hibernate.id column=username length=20
generator-class=assigned
* unsaved-value=version
*/
public String getUsername() {
return username;
}
/**
* Returns the password.
* @return String
*
* @struts.validator type=required
* @struts.validator type=twofields msgkey=errors.twofields
* @struts.validator-args arg1resource=userForm.password
* @struts.validator-args arg1resource=userForm.confirmPassword
* @struts.validator-var name=secondProperty
value=confirmPassword
* @hibernate.property column=password not-null=true
*/
public String getPassword() {
return password;
}
/**
* Returns the confirmedPassword.
* @return String
*
* @struts.validator type=required
*/
public String getConfirmPassword() {
return confirmPassword;
}
/**
* Returns the firstName.
* @return String
*
* @struts.validator type=required
* @hibernate.property column=first_name not-null=true
length=50
*/
public String getFirstName() {
return firstName;
}
/**
* Returns the lastName.
* @return String
*
* @struts.validator type=required
* @hibernate.property column=last_name not-null=true
length=50
*/
public String getLastName() {
return lastName;
}
public String getFullName() {
return firstName + ' ' + lastName;
}
/**
* Returns the address.
*
* @return Address
*
* @hibernate.component
*/
public Address getAddress() {
return address;
}
/**
* Returns the email. This is an optional field for specifying a
* different e-mail than the username.
*
* @return String
*
* @struts.validator type=required
* @struts.validator type=email
* @hibernate.property name=email not-null=true unique=true
*/
public String getEmail() {
return email;
}
/**
* Returns the phoneNumber.
*
* @return String
*
* @struts.validator type=mask msgkey=errors.phone
* @struts.validator-var name=mask value=${phone}
* @hibernate.property column=phone_number not-null=false
*/
public String getPhoneNumber() {
return phoneNumber;
}
/**
* Returns the website.
*
* @return String
*
* @struts.validator type=required
* @hibernate.property column=website not-null=false
*/
public String getWebsite() {
return website;
}
/**
* Returns the passwordHint.
*
* @return String
*
* @struts.validator type=required
* @hibernate.property column=password_hint not-null=false
*/
public String getPasswordHint() {
return passwordHint;
}
/**
* Returns the user's roles.
*
* @return Set
*
* @hibernate.set table=user_role cascade=save-update
lazy=false
* @hibernate.collection-key column=username
*
RE: MNG-1427 status
Try http://maven.apache.org/guides/introduction/introduction-to-dependency-m echanism.html -Original Message- From: Serge Bogatyrjov [mailto:[EMAIL PROTECTED] Sent: Thursday, November 17, 2005 11:27 To: users@maven.apache.org Subject: MNG-1427 status Hi http://jira.codehaus.org/browse/MNG-1427 The issue is marked as closed, but the page http://maven.apache.org/maven2/dependency-mechanism.html is still unavailable. (I encountered this issue while googling maven2 dependency scope). Serge Bogatyrjov. - 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 Unit Tests?
I was trying to build some unit tests for the RPM plugin and am running into a chicken-and-egg problem. To test the newly-compiled plugin, it seems that I need to complete the install phase so that the plugin is available for the tests to run. If I alter the configuration to skip the unit tests, it will install the new plugin but I can't run any tests (since they are skipped). Am I taking the wrong approach? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Plugin Unit Tests?
I don't see maven-components/sandbox or anything named it in mojo/mojo-sandbox. Could you be a little more specific where the plugin is located? -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 09:46 To: 'Maven Users List' Subject: RE: Plugin Unit Tests? Hi Bob, To test a plugin the best solution is to use the it plugin in components/sandbox/plugins. It allows you to put test projects in src/test/it. -Vincent -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: mardi 15 novembre 2005 15:35 To: Maven Users List Subject: Plugin Unit Tests? I was trying to build some unit tests for the RPM plugin and am running into a chicken-and-egg problem. To test the newly-compiled plugin, it seems that I need to complete the install phase so that the plugin is available for the tests to run. If I alter the configuration to skip the unit tests, it will install the new plugin but I can't run any tests (since they are skipped). Am I taking the wrong approach? - 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: Plugin Unit Tests?
OK. Maybe I'm not checking out the correct maven2 trunk. The URL I am using is http://svn.apache.org/repos/asf/maven/components/trunk; (which is the URL specified in the Building Maven 2.0 document. In the top directory of the stuff checked out are benchmark, bootstrap, examples, integration-tests, a few files, and a number of directories named maven- There is no directory named sandbox or components or plugins and the maven-plugins directory does not have anything named sandbox. Please tell me what I am missing. -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 10:19 To: 'Maven Users List' Subject: RE: Plugin Unit Tests? Bob, -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: mardi 15 novembre 2005 15:51 To: Maven Users List Subject: RE: Plugin Unit Tests? I don't see maven-components/sandbox or anything named it in mojo/mojo-sandbox. Could you be a little more specific where the plugin is located? It's not in mojo, it's in the maven2 trunk. If you check it out you'll see a components/sandbox/plugins dir -Vincent -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 09:46 To: 'Maven Users List' Subject: RE: Plugin Unit Tests? Hi Bob, To test a plugin the best solution is to use the it plugin in components/sandbox/plugins. It allows you to put test projects in src/test/it. -Vincent -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: mardi 15 novembre 2005 15:35 To: Maven Users List Subject: Plugin Unit Tests? I was trying to build some unit tests for the RPM plugin and am running into a chicken-and-egg problem. To test the newly-compiled plugin, it seems that I need to complete the install phase so that the plugin is available for the tests to run. If I alter the configuration to skip the unit tests, it will install the new plugin but I can't run any tests (since they are skipped). Am I taking the wrong approach? - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Plugin Unit Tests?
That was it. Thanks! -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 11:35 To: Maven Users List Subject: Re: Plugin Unit Tests? -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The sandbox got moved out of /components/trunk... :-) New URL is: https://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-it-plugin/ HTH, - -john Allison, Bob wrote: | OK. Maybe I'm not checking out the correct maven2 trunk. | | The URL I am using is | http://svn.apache.org/repos/asf/maven/components/trunk; (which is the | URL specified in the Building Maven 2.0 document. In the top | directory of the stuff checked out are benchmark, bootstrap, | examples, integration-tests, a few files, and a number of | directories named maven- There is no directory named sandbox or | components or plugins and the maven-plugins directory does not | have anything named sandbox. | | Please tell me what I am missing. | | -Original Message- | From: Vincent Massol [mailto:[EMAIL PROTECTED] | Sent: Tuesday, November 15, 2005 10:19 | To: 'Maven Users List' | Subject: RE: Plugin Unit Tests? | | | Bob, | | |-Original Message- |From: Allison, Bob [mailto:[EMAIL PROTECTED] |Sent: mardi 15 novembre 2005 15:51 |To: Maven Users List |Subject: RE: Plugin Unit Tests? | |I don't see maven-components/sandbox or anything named it in |mojo/mojo-sandbox. | |Could you be a little more specific where the plugin is located? | | | It's not in mojo, it's in the maven2 trunk. If you check it out you'll | see a | components/sandbox/plugins dir | | -Vincent | | |-Original Message- |From: Vincent Massol [mailto:[EMAIL PROTECTED] |Sent: Tuesday, November 15, 2005 09:46 |To: 'Maven Users List' |Subject: RE: Plugin Unit Tests? | | |Hi Bob, | |To test a plugin the best solution is to use the it plugin in |components/sandbox/plugins. | |It allows you to put test projects in src/test/it. | |-Vincent | | |-Original Message- |From: Allison, Bob [mailto:[EMAIL PROTECTED] |Sent: mardi 15 novembre 2005 15:35 |To: Maven Users List |Subject: Plugin Unit Tests? | |I was trying to build some unit tests for the RPM plugin and am | |running | |into a chicken-and-egg problem. To test the newly-compiled plugin, | | it | |seems that I need to complete the install phase so that the plugin | | is | |available for the tests to run. If I alter the configuration to | | skip | |the unit tests, it will install the new plugin but I can't run any | |tests | |(since they are skipped). | |Am I taking the wrong approach? | | | | - | |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] | | | - | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDeg4AK3h2CZwO/4URAtXeAJ9wxilZQT33kiZWQ2yxb3PeOZ47YwCgpFh7 vsbbuhRAuJPgjZN4lag0zUI= =gKKP -END PGP SIGNATURE- - 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 Execution Problem
I am having some trouble executing a plugin I am building, and I'm not sure where to look to find the problem. If anyone can provide some pointers on what to examine, I would be very grateful. I am building an RPM plugin with a single goal rpm:rpm. The goal is implemented by the class org.codehaus.mojo.rpm.RPMMojo. The jar built for the plugin contains: 0 Mon Nov 14 07:09:12 MST 2005 META-INF/ 377 Mon Nov 14 07:09:10 MST 2005 META-INF/MANIFEST.MF 0 Mon Nov 14 07:05:54 MST 2005 META-INF/maven/ 0 Mon Nov 14 07:05:58 MST 2005 org/ 0 Mon Nov 14 07:05:58 MST 2005 org/codehaus/ 0 Mon Nov 14 07:05:58 MST 2005 org/codehaus/mojo/ 0 Mon Nov 14 07:05:58 MST 2005 org/codehaus/mojo/rpm/ 9698 Mon Nov 14 07:09:04 MST 2005 META-INF/maven/plugin.xml 1567 Mon Nov 14 07:09:08 MST 2005 org/codehaus/mojo/rpm/Source.class 939 Mon Nov 14 07:09:08 MST 2005 org/codehaus/mojo/rpm/RPMMojo$StdoutConsumer.class 939 Mon Nov 14 07:09:08 MST 2005 org/codehaus/mojo/rpm/RPMMojo$StderrConsumer.class 10189 Mon Nov 14 07:09:08 MST 2005 org/codehaus/mojo/rpm/RPMMojo.class 3237 Mon Nov 14 07:05:58 MST 2005 org/codehaus/mojo/rpm/Mapping.class 0 Mon Nov 14 07:09:12 MST 2005 META-INF/maven/org.codehaus.mojo/ 0 Mon Nov 14 07:09:12 MST 2005 META-INF/maven/org.codehaus.mojo/rpm-maven-plugin/ 7269 Mon Nov 14 07:09:10 MST 2005 META-INF/maven/org.codehaus.mojo/rpm-maven-plugin/pom.xml 133 Mon Nov 14 07:09:10 MST 2005 META-INF/maven/org.codehaus.mojo/rpm-maven-plugin/pom.properties When I try to use the plugin, I get the following (with -X): + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: '/home/allisord/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/opt/maven/2/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: qaccess.rpm:base:pom:1.0-SNAPSHOT [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: qaccess:rpm:pom:1.0-SNAPSHOT [INFO] Searching repository for plugin with prefix: 'rpm'. [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository qadev-r [DEBUG] Skipping disabled repository central [DEBUG] rpm-maven-plugin: resolved to version 1.0-alpha-1-20051114.140910-1 from repository qadev [DEBUG] Retrieving parent-POM from the repository for project: null:rpm-maven-plugin:maven-plugin:1.0-alpha-1-20051114.140910-1 [DEBUG] rpm-maven-plugin: resolved to version 1.0-alpha-1-20051114.140910-1 from repository qadev [DEBUG] rpm-maven-plugin: resolved to version 1.0-alpha-1-20051114.140910-1 from repository qadev [DEBUG] Retrieving parent-POM from the repository for project: null:rpm-maven-plugin:maven-plugin:1.0-alpha-1-20051114.140910-1 [DEBUG] rpm-maven-plugin: resolved to version 1.0-alpha-1-20051114.140910-1 from repository qadev [INFO] [INFO] Building Q.Access Base RPM [INFO]task-segment: [rpm:rpm] [INFO] [DEBUG] org.codehaus.mojo:rpm-maven-plugin:maven-plugin:1.0-alpha-1-20051114.140 910-1 (selected for runtime) [DEBUG] Skipping disabled repository central [DEBUG] plexus-archiver: resolved to version 1.0-alpha-4-20051114.140433-1 from repository qadev [DEBUG] Retrieving parent-POM from the repository for project: null:plexus-archiver:jar:1.0-alpha-4-20051114.140433-1 [DEBUG] Retrieving parent-POM from the repository for project: org.codehaus.plexus:plexus-components:pom:1.1.4 [DEBUG] org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-4-SNAPSHOT (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime) [DEBUG] junit:junit:jar:3.8.1 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-plugin-api:jar:2.0 [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 (selected for runtime) [DEBUG] plexus-archiver: resolved to version 1.0-alpha-4-20051114.140433-1 from repository qadev - this realm = app0.child-container[org.codehaus.mojo:rpm-maven-plugin] urls[0] = file:/home/allisord/.m2/repository/org/codehaus/mojo/rpm-maven-plugin/1. 0-alpha-1-SNAPSHOT/rpm-maven-plugin-1.0-alpha-1-SNAPSHOT.jar urls[1] = file:/home/allisord/.m2/repository/org/codehaus/plexus/plexus-archiver/1 .0-alpha-4-SNAPSHOT/plexus-archiver-1.0-alpha-4-SNAPSHOT.jar Number of imports: 0 this realm = plexus.core.maven urls[0] = file:/opt/maven/2/lib/maven-core-2.0.jar urls[1] = file:/opt/maven/2/lib/maven-plugin-parameter-documenter-2.0.jar urls[2] =
RE: Plugin Execution Problem
I got the plugin to work by changing the project description to be on one line. The POM when it contained [1] and when it worked contained [2]. The difference this created was to keep the description and /description in the plugin.xml on the same line. Is the plugin.xml file parsed with a regular XML parser? [1] description Maven plugin which assembles files into an RPM package for installation On various target UNIX systems. /description [2] description Maven plugin which assembles files into an RPM package /description -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Monday, November 14, 2005 09:20 To: Maven Users List Subject: Plugin Execution Problem I am having some trouble executing a plugin I am building, and I'm not sure where to look to find the problem. If anyone can provide some pointers on what to examine, I would be very grateful. I am building an RPM plugin with a single goal rpm:rpm. The goal is implemented by the class org.codehaus.mojo.rpm.RPMMojo. The jar built for the plugin contains: 0 Mon Nov 14 07:09:12 MST 2005 META-INF/ 377 Mon Nov 14 07:09:10 MST 2005 META-INF/MANIFEST.MF 0 Mon Nov 14 07:05:54 MST 2005 META-INF/maven/ 0 Mon Nov 14 07:05:58 MST 2005 org/ 0 Mon Nov 14 07:05:58 MST 2005 org/codehaus/ 0 Mon Nov 14 07:05:58 MST 2005 org/codehaus/mojo/ 0 Mon Nov 14 07:05:58 MST 2005 org/codehaus/mojo/rpm/ 9698 Mon Nov 14 07:09:04 MST 2005 META-INF/maven/plugin.xml 1567 Mon Nov 14 07:09:08 MST 2005 org/codehaus/mojo/rpm/Source.class 939 Mon Nov 14 07:09:08 MST 2005 org/codehaus/mojo/rpm/RPMMojo$StdoutConsumer.class 939 Mon Nov 14 07:09:08 MST 2005 org/codehaus/mojo/rpm/RPMMojo$StderrConsumer.class 10189 Mon Nov 14 07:09:08 MST 2005 org/codehaus/mojo/rpm/RPMMojo.class 3237 Mon Nov 14 07:05:58 MST 2005 org/codehaus/mojo/rpm/Mapping.class 0 Mon Nov 14 07:09:12 MST 2005 META-INF/maven/org.codehaus.mojo/ 0 Mon Nov 14 07:09:12 MST 2005 META-INF/maven/org.codehaus.mojo/rpm-maven-plugin/ 7269 Mon Nov 14 07:09:10 MST 2005 META-INF/maven/org.codehaus.mojo/rpm-maven-plugin/pom.xml 133 Mon Nov 14 07:09:10 MST 2005 META-INF/maven/org.codehaus.mojo/rpm-maven-plugin/pom.properties When I try to use the plugin, I get the following (with -X): + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: '/home/allisord/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/opt/maven/2/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: qaccess.rpm:base:pom:1.0-SNAPSHOT [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: qaccess:rpm:pom:1.0-SNAPSHOT [INFO] Searching repository for plugin with prefix: 'rpm'. [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository qadev-r [DEBUG] Skipping disabled repository central [DEBUG] rpm-maven-plugin: resolved to version 1.0-alpha-1-20051114.140910-1 from repository qadev [DEBUG] Retrieving parent-POM from the repository for project: null:rpm-maven-plugin:maven-plugin:1.0-alpha-1-20051114.140910-1 [DEBUG] rpm-maven-plugin: resolved to version 1.0-alpha-1-20051114.140910-1 from repository qadev [DEBUG] rpm-maven-plugin: resolved to version 1.0-alpha-1-20051114.140910-1 from repository qadev [DEBUG] Retrieving parent-POM from the repository for project: null:rpm-maven-plugin:maven-plugin:1.0-alpha-1-20051114.140910-1 [DEBUG] rpm-maven-plugin: resolved to version 1.0-alpha-1-20051114.140910-1 from repository qadev [INFO] [INFO] Building Q.Access Base RPM [INFO]task-segment: [rpm:rpm] [INFO] [DEBUG] org.codehaus.mojo:rpm-maven-plugin:maven-plugin:1.0-alpha-1-20051114.140 910-1 (selected for runtime) [DEBUG] Skipping disabled repository central [DEBUG] plexus-archiver: resolved to version 1.0-alpha-4-20051114.140433-1 from repository qadev [DEBUG] Retrieving parent-POM from the repository for project: null:plexus-archiver:jar:1.0-alpha-4-20051114.140433-1 [DEBUG] Retrieving parent-POM from the repository for project: org.codehaus.plexus:plexus-components:pom:1.1.4 [DEBUG] org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-4-SNAPSHOT (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime) [DEBUG] junit:junit:jar:3.8.1 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-plugin-api:jar:2.0 [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 (selected
RE: Where can I get a list of the supported project packaging types
Those are the major ones. Because it is possible for a plugin to create its own packaging, it might be rather difficult to have a list that covers everything. -Original Message- From: Stephen Cowx [mailto:[EMAIL PROTECTED] Sent: Monday, November 14, 2005 10:28 To: Maven Users List Subject: Where can I get a list of the supported project packaging types I cannot find a list. I know of the following JAR EAR WAR POM thanks Stephen - 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]
Jar Manifest Problems
It looks like we have some problems with the contents of manifests in jar files. According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced: 1) All text must be UTF-8 2) Lines are limited to 72 characters; longer lines must be continued 3) Sections are divided by blank lines Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking. Example: The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded. Workarounds for the present: -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters. -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] How to inject values into a bean within a collection definedas a plugin parameter?
The configuration should look like (assuming that your definition of
parameter directory is actually specified as private String
directory):
options
option
directory/a/b/c/directory
/option
option
directory/d/e/f/directory
/option
/options
I don't think that the expressions and default values available in the
Mojo are available in the classes used in this manner. A workaround
might be to place variables which require an expression as a parameter
in the Mojo itself and have a way to propagate it to the sub-objects.
-Original Message-
From: Richard Allen [mailto:[EMAIL PROTECTED]
Sent: Monday, November 14, 2005 14:59
To: users@maven.apache.org
Subject: [m2] How to inject values into a bean within a collection
definedas a plugin parameter?
I have an array (same question applies to Java Collections) that is
defined as a parameter of a Mojo:
public class MyMojo extends AbstractMojo {
...
/**
* @parameter
* @required
*/
private Options[] optionsArray;
...
}
and within the Options bean, I would like to inject properties from
Maven:
public class Options {
...
/**
* @parameter expression=${project.build.directory}
*/
private directory;
...
}
such that the plugin can be configured like:
plugin
...
executions
execution
...
configuration
optionsArray
options
...
/options
options
...
/options
/compilations
/configuration
...
/execution
/executions
/plugin
Is there a way to make this happen? It seems like I should be able to do
this since Maven is creating and populating the bean classes (Options
class).
Thanks,
Richard Allen
-
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] How to inject values into a bean within a collection definedasa plugin parameter?
I think that such a process is in the works, but I can't find the JIRA
issue on it.
-Original Message-
From: Richard Allen [mailto:[EMAIL PROTECTED]
Sent: Monday, November 14, 2005 15:27
To: Maven Users List
Subject: Re: [m2] How to inject values into a bean within a collection
definedasa plugin parameter?
For now, I've added a set method on the Options class for setting a
default directory, which I get from a parameter in the Mojo. This is
essentially what you suggested I could do. I just don't think it is very
clean, and I see how it could be useful (and in this case cleaner) if
Maven could process annotations on beans in collections that are defined
as Mojo parameters.
Thanks,
Richard Allen
Allison, Bob wrote:
The configuration should look like (assuming that your definition of
parameter directory is actually specified as private String
directory):
options
option
directory/a/b/c/directory
/option
option
directory/d/e/f/directory
/option
/options
I don't think that the expressions and default values available in the
Mojo are available in the classes used in this manner. A workaround
might be to place variables which require an expression as a parameter
in the Mojo itself and have a way to propagate it to the sub-objects.
-Original Message-
From: Richard Allen [mailto:[EMAIL PROTECTED]
Sent: Monday, November 14, 2005 14:59
To: users@maven.apache.org
Subject: [m2] How to inject values into a bean within a collection
definedas a plugin parameter?
I have an array (same question applies to Java Collections) that is
defined as a parameter of a Mojo:
public class MyMojo extends AbstractMojo {
...
/**
* @parameter
* @required
*/
private Options[] optionsArray;
...
}
and within the Options bean, I would like to inject properties from
Maven:
public class Options {
...
/**
* @parameter expression=${project.build.directory}
*/
private directory;
...
}
such that the plugin can be configured like:
plugin
...
executions
execution
...
configuration
optionsArray
options
...
/options
options
...
/options
/compilations
/configuration
...
/execution
/executions
/plugin
Is there a way to make this happen? It seems like I should be able to
do
this since Maven is creating and populating the bean classes (Options
class).
Thanks,
Richard Allen
-
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]
RE: quesiton about maven 2 projects with modules
The way I have done it is as follows: -- Make a copy of the parent POM (the one with the modules info) -- Alter the copy to remove the modules and packaging (or change packaging to jar -- Use this altered POM to create a Continuum project -- Modify the project to remove the --non-recursive option When Continuum does the download of the project, it will get the committed POM from SCM which has the correct packaging and module list. By removing the option, Maven will run through all of the modules correctly. -Original Message- From: Frank Zhao [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 09, 2005 17:34 To: continuum-users@maven.apache.org Subject: quesiton about maven 2 projects with modules It seems for each modules, Continuum creates a seperate project for it. Is there a way to disable this feature since I only need one continuum project which can build very modules defined in the POM. Thanks, Frank
RE: [m2] Inherited plugin execution order
Since you missed this in the SortedMap definition (which TreeMap implements): A map that further guarantees that it will be in ascending key order, sorted according to the natural ordering of its keys (see the Comparable interface), or by a comparator provided at sorted map creation time. This order is reflected when iterating over the sorted map's collection views (returned by the entrySet, keySet and values methods). This means that the values retrieved ARE in the order defined by the keys. -Original Message- From: David Jackman [mailto:[EMAIL PROTECTED] Sent: Thursday, November 10, 2005 12:34 To: Maven Users List Subject: RE: [m2] Inherited plugin execution order Actually, it appears even the docs aren't correct. I moved the javadoc plugin to the parent and left my plugin in the subproject, and it still doesn't work. It only works if nothing is in the parent and both plugins are listed (with the javadoc plugin first) in the subproject POM. Upon closer inspection, it appears that the order will be as listed if there aren't any plugins inherited from the parent. If inheritance is involved, then the ordering is arbitrary. Looking at org.apache.maven.project.ModelUtils, it looks like the plugin lists are merged using a TreeMap, which sorts the entries by the natural ordering of the keys. Since at the end of the merge process we take the values list, this will be completely arbitrary. I wrote a bug on this (MNG-1499). ..David.. -Original Message- From: David Jackman [mailto:[EMAIL PROTECTED] Sent: Thursday, November 10, 2005 9:33 AM To: Maven Users List Subject: [m2] Inherited plugin execution order According to the docs (http://maven.apache.org/guides/introduction/introduction-to-the-lifecyc le.html): When multiple executions are given that match a particular phase, they are executed in the order specified in the POM, with inherited executions running first. This much seems to be true. However, how can I determine/specify the order that inherited executions run? I thought it would be the order specified in the parent POM, but that doesn't seem to be the case. My plugin needs to run after the javadoc plugin (but really ought to be in the same phase), but I can't seem to make this happen for inherited projects. ..David.. - 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] Inherited plugin execution order
But that is not the completely arbitrary you described earlier. I think that completely arbitrary and not correct are very different things. -Original Message- From: David Jackman [mailto:[EMAIL PROTECTED] Sent: Thursday, November 10, 2005 13:30 To: Maven Users List Subject: RE: [m2] Inherited plugin execution order I didn't miss that. The problem is that the natural ordering of the keys is not the correct order. The current ordering will be alphabetically by plugin groupId and artifactId. What it should be is the ordering as listed in the parent POM followed by the ordering as listed in the project POM (with any of the project-specified plugins removed if they are covered by the parent's list). ..David.. -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Thursday, November 10, 2005 10:57 AM To: Maven Users List Subject: RE: [m2] Inherited plugin execution order Since you missed this in the SortedMap definition (which TreeMap implements): A map that further guarantees that it will be in ascending key order, sorted according to the natural ordering of its keys (see the Comparable interface), or by a comparator provided at sorted map creation time. This order is reflected when iterating over the sorted map's collection views (returned by the entrySet, keySet and values methods). This means that the values retrieved ARE in the order defined by the keys. -Original Message- From: David Jackman [mailto:[EMAIL PROTECTED] Sent: Thursday, November 10, 2005 12:34 To: Maven Users List Subject: RE: [m2] Inherited plugin execution order Actually, it appears even the docs aren't correct. I moved the javadoc plugin to the parent and left my plugin in the subproject, and it still doesn't work. It only works if nothing is in the parent and both plugins are listed (with the javadoc plugin first) in the subproject POM. Upon closer inspection, it appears that the order will be as listed if there aren't any plugins inherited from the parent. If inheritance is involved, then the ordering is arbitrary. Looking at org.apache.maven.project.ModelUtils, it looks like the plugin lists are merged using a TreeMap, which sorts the entries by the natural ordering of the keys. Since at the end of the merge process we take the values list, this will be completely arbitrary. I wrote a bug on this (MNG-1499). ..David.. -Original Message- From: David Jackman [mailto:[EMAIL PROTECTED] Sent: Thursday, November 10, 2005 9:33 AM To: Maven Users List Subject: [m2] Inherited plugin execution order According to the docs (http://maven.apache.org/guides/introduction/introduction-to-the-lifecyc le.html): When multiple executions are given that match a particular phase, they are executed in the order specified in the POM, with inherited executions running first. This much seems to be true. However, how can I determine/specify the order that inherited executions run? I thought it would be the order specified in the parent POM, but that doesn't seem to be the case. My plugin needs to run after the javadoc plugin (but really ought to be in the same phase), but I can't seem to make this happen for inherited projects. ..David.. - 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]
Sanity Check Regarding Launching External Tools
I just wanted to make sure that I am doing things correctly before I go too far on the RPM plugin... 1) To build the RPM, I need to run the command rpmbuild. Based on what I saw in the release plugin, I am using classes in package org.codehaus.plexus.util.cli (in org.codehaus.plexus:plexus-utils) to run the command and forward the command output to the build log. Is this the best practice for a Mojo to run command-line tools? 2) I am going to use a plexus archiver component (DirectoryArchiver) to do the copying of files into the RPM work area. To get this reference, I have the following (adapted from other plugins): /** * @component role=org.codehaus.plexus.archiver.Archiver *roleHint=dir */ private DirectoryArchiver dirarchiver; This provides a reference, as intended, but I wanted to make sure that this was the best way of doing things. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Strange Build Error
I figured out what caused this: A jar file listed as a plugin in your POM that does not contain META-INF/maven/plugin.xml -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Thursday, November 03, 2005 11:09 To: Maven Users List Subject: [m2] Strange Build Error I am experimenting with a directory archiver for plexus, and built a new snapshot version of the component. When I did a mvn install in that directory, the install placed the jar where I expected it: [INFO] [install:install] [INFO] Installing /net/home/allisord/src/plugins/plexus-archiver/target/plexus-archiver-1. 0-alpha-4-SNAPSHOT.jar to /home/allisord/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-al pha-4-SNAPSHOT/plexus-archiver-1.0-alpha-4-SNAPSHOT.jar The strange part is when I went to compile against the component. I changed the project to declare a dependency to org.codehaus.plexus:plexus-archiver:1.0-alpha-4-SNAPSHOT (instead of 1.0-alpha-3) and got the following: [EMAIL PROTECTED] rpm]$ mvn -X compile + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: '/home/allisord/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/opt/maven/2/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: qaccess.plugins:maven-rpm-plugin:maven-plugin:1.0.0 [INFO] [INFO] Building RPM Plugin for Maven [INFO]task-segment: [compile] [INFO] [DEBUG] maven-plugin-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-plugin-plugin:maven-plugin:2.0 [DEBUG] maven-resources-plugin: resolved to version 2.1 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-resources-plugin:maven-plugin:2.1 [DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-compiler-plugin:maven-plugin:2.0 [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository central [DEBUG] plexus-archiver: using locally installed snapshot [DEBUG] Retrieving parent-POM from the repository for project: null:plexus-archiver:jar:1.0-alpha-4-SNAPSHOT [DEBUG] Retrieving parent-POM from the repository for project: org.codehaus.plexus:plexus-components:pom:1.1.4 [DEBUG] plexus-archiver: using locally installed snapshot [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [DEBUG] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginMana ger.java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Defau ltPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM anager.java:163) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default LifecycleExecutor.java:1095) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycl e(DefaultLifecycleExecutor.java:1060) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa ppings(DefaultLifecycleExecutor.java:869) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:301) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO
[m2] Strange Build Error
I am experimenting with a directory archiver for plexus, and built a new snapshot version of the component. When I did a mvn install in that directory, the install placed the jar where I expected it: [INFO] [install:install] [INFO] Installing /net/home/allisord/src/plugins/plexus-archiver/target/plexus-archiver-1. 0-alpha-4-SNAPSHOT.jar to /home/allisord/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-al pha-4-SNAPSHOT/plexus-archiver-1.0-alpha-4-SNAPSHOT.jar The strange part is when I went to compile against the component. I changed the project to declare a dependency to org.codehaus.plexus:plexus-archiver:1.0-alpha-4-SNAPSHOT (instead of 1.0-alpha-3) and got the following: [EMAIL PROTECTED] rpm]$ mvn -X compile + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: '/home/allisord/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/opt/maven/2/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for project: qaccess.plugins:maven-rpm-plugin:maven-plugin:1.0.0 [INFO] [INFO] Building RPM Plugin for Maven [INFO]task-segment: [compile] [INFO] [DEBUG] maven-plugin-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-plugin-plugin:maven-plugin:2.0 [DEBUG] maven-resources-plugin: resolved to version 2.1 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-resources-plugin:maven-plugin:2.1 [DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-compiler-plugin:maven-plugin:2.0 [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository central [DEBUG] plexus-archiver: using locally installed snapshot [DEBUG] Retrieving parent-POM from the repository for project: null:plexus-archiver:jar:1.0-alpha-4-SNAPSHOT [DEBUG] Retrieving parent-POM from the repository for project: org.codehaus.plexus:plexus-components:pom:1.1.4 [DEBUG] plexus-archiver: using locally installed snapshot [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [DEBUG] Trace java.lang.NullPointerException at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginMana ger.java:292) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(Defau ltPluginManager.java:198) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM anager.java:163) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default LifecycleExecutor.java:1095) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycl e(DefaultLifecycleExecutor.java:1060) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa ppings(DefaultLifecycleExecutor.java:869) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:301) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Thu Nov 03 08:56:09 MST 2005 [INFO] Final Memory: 3M/55M [INFO] -
RE: deploying error
There are two different repositories you deal with in Maven:
-- The local repository is the one that is located in
${user.home}/.m2/repository by default. This is a place where artifacts needed
for the build are stored, and cannot be shared between users. When you do an
install, the artifact is placed in this repository.
-- The remote repository is one located somewhere else, usually on a central
server (whether central to your company or home or the world is not important
to this discussion). This is a place where artifacts to be shared are stored;
artifacts are downloaded from this repository to your local repository when you
need them for a build. When you do a deploy, the artifact is placed in this
repository.
Also note that it is quite reasonable to have a number of remote repositories.
Does this help clear up the confusion?
-Original Message-
From: Luca Gmail [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 02, 2005 11:05
To: 'Maven Users List'
Subject: RE: deploying error
But what is the meaning of deploy plugin?
If I follow the maven doc I sould use the deploy plugin if I want to deploy
my artifact to the remote repository. Why you said using the install plugin?
I don't understand. It's seems all so random!!!
tnx,
Luca
-Original Message-
From: Yudong Wang [mailto:[EMAIL PROTECTED]
Sent: mercoledì 2 novembre 2005 16.05
To: Maven Users List
Subject: Re: deploying error
Or even simpler:
mvn install
This will install the file in your local repo as defined in your pom.xml.
Otherwise you have to provide all these parameters as Anuerin mentioned.
Yudong
On 11/2/05, Anuerin Diaz [EMAIL PROTECTED] wrote:
hi,
check your command again to ensure that you are using
install:install-file as shown in
http://maven.apache.org/maven2/guides/mini/guide-coping-with-sun-jars.html
.
i encountered that error a while ago and the cause was i did not type
the -file part of the goal. :D
ciao!
On 11/2/05, Luca Gmail [EMAIL PROTECTED] wrote:
Im trying to deploy my artifact to my internal repositpry. When I
exceuted
mvn deploy I ahd this error:
[INFO] The packaging for this project did not assign a file to the build
artifact.
snip
--
Programming, an artform that fights back
Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do
-
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: deploying error
Actually, no I didn't say anything about doing an install. If you look back
at the earlier messages, the comment about install came from Anuerin Diaz. I
was just commenting on the difference between install and deploy to help clear
up some apparent confusion.
-Original Message-
From: Luca Gmail [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 02, 2005 11:22
To: 'Maven Users List'
Subject: RE: deploying error
Yes Bob, but in the first mail i asked that i had an error deploying (to
remote as you said and as I expected) my artifact. You answered me to use
the install pugin. Why?
First install locally and the deploy remotely? In such a way?
I created my artifact (a jar file). I would like to share and reuse inside
other project. How can do it? If I read doc I have ti use deploy plugin.
Hope being clear :-)
Tnx,
Luca
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: mercoledì 2 novembre 2005 17.11
To: Maven Users List
Subject: RE: deploying error
There are two different repositories you deal with in Maven:
-- The local repository is the one that is located in
${user.home}/.m2/repository by default. This is a place where artifacts
needed for the build are stored, and cannot be shared between users. When
you do an install, the artifact is placed in this repository.
-- The remote repository is one located somewhere else, usually on a
central server (whether central to your company or home or the world is not
important to this discussion). This is a place where artifacts to be shared
are stored; artifacts are downloaded from this repository to your local
repository when you need them for a build. When you do a deploy, the
artifact is placed in this repository.
Also note that it is quite reasonable to have a number of remote
repositories.
Does this help clear up the confusion?
-Original Message-
From: Luca Gmail [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 02, 2005 11:05
To: 'Maven Users List'
Subject: RE: deploying error
But what is the meaning of deploy plugin?
If I follow the maven doc I sould use the deploy plugin if I want to deploy
my artifact to the remote repository. Why you said using the install plugin?
I don't understand. It's seems all so random!!!
tnx,
Luca
-Original Message-
From: Yudong Wang [mailto:[EMAIL PROTECTED]
Sent: mercoledì 2 novembre 2005 16.05
To: Maven Users List
Subject: Re: deploying error
Or even simpler:
mvn install
This will install the file in your local repo as defined in your pom.xml.
Otherwise you have to provide all these parameters as Anuerin mentioned.
Yudong
On 11/2/05, Anuerin Diaz [EMAIL PROTECTED] wrote:
hi,
check your command again to ensure that you are using
install:install-file as shown in
http://maven.apache.org/maven2/guides/mini/guide-coping-with-sun-jars.html
.
i encountered that error a while ago and the cause was i did not type
the -file part of the goal. :D
ciao!
On 11/2/05, Luca Gmail [EMAIL PROTECTED] wrote:
Im trying to deploy my artifact to my internal repositpry. When I
exceuted
mvn deploy I ahd this error:
[INFO] The packaging for this project did not assign a file to the build
artifact.
snip
--
Programming, an artform that fights back
Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Build problem
It looks like there is a problem checking out your sources. Please make sure that the SCM information in the project is correct and that you can use the same information to check out the project from the command line. -Original Message- From: Malcolm Wong Ho [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 01, 2005 07:01 To: continuum-users@maven.apache.org Subject: Build problem Continuum build failing, not sure what the cause is. Using Maven2 and Continuum1. Log :- jvm 1| 2005-11-01 09:00:00,013 [scheduler1_Worker-11] INFO SchedulesActivator - Executing build job (DEFAULT_SCHEDULE)... jvm 1| 2005-11-01 09:00:00,053 [scheduler1_Worker-11] INFO Continuum - Enqueuing 'Maven Quick Start Archetype' (Build definition id=10 . jvm 1| 2005-11-01 09:00:00,154 [Thread-1] INFO ContinuumScm - Checking out project: 'Maven Quick Start Archetype', id: '10' to 'C:\blackb ird\continuum-1.0\bin\win32\..\..\apps\continuum\working-directory\10'. jvm 1| 2005-11-01 09:00:00,234 [Thread-1] WARN ConfigurationService - Error reading build output for build '25'. jvm 1| java.io.FileNotFoundException: C:\blackbird\continuum-1.0\bin\win32\..\..\apps\continuum\build-output-d irectory\10\25.log.txt (The system cannot find the file specified) jvm 1| at java.io.FileInputStream.open(Native Method) jvm 1| at java.io.FileInputStream.init(FileInputStream.java:106) jvm 1| at org.codehaus.plexus.util.FileUtils.fileRead(FileUtils.java:269) jvm 1| at org.codehaus.plexus.util.FileUtils.fileRead(FileUtils.java:261) jvm 1| at org.apache.maven.continuum.configuration.DefaultConfigurationService.get BuildOutput(DefaultConfigurationService.java:167) jvm 1| at org.apache.maven.continuum.notification.DefaultContinuumNotificationDisp atcher.sendNotification(DefaultContinuumNotificationDispatcher.java:1 29) jvm 1| at org.apache.maven.continuum.notification.DefaultContinuumNotificationDisp atcher.buildComplete(DefaultContinuumNotificationDispatcher.java:96) jvm 1| at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:261) jvm 1| at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.exec uteTask(BuildProjectTaskExecutor.java:53) jvm 1| at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Execut orRunnable.run(ThreadedTaskQueueExecutor.java:103) jvm 1| at java.lang.Thread.run(Thread.java:595) Malcolm Wong Ho An investment in knowledge always pays the best interest. -- Benjamin Franklin This e-mail is sent on the Terms and Conditions that can be accessed by Clicking on this link http://www.vodacom.net/legal/email.aspx
RE: Build Error
I'm using Linux, not Windows, so this may not be 100% correct. As I recall, if you want to put the drive designator in the SCM URL, you need to use something other than ':' as a delimiter. Try connectionscm|local|C:\Documents and Settings\WongHoma\.m2\repository|status-change/connection -Original Message- From: Malcolm Wong Ho [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 01, 2005 13:53 To: continuum-users@maven.apache.org Subject: RE: Build Error Here is a code snippet of my pom.xml file, I'm trying to use mavens local repository. Does the pom.xml file look right? pom.xml :- scm connectionscm:local:C:\Documents and Settings\WongHoma\.m2\repository:status-change/connection /scm This e-mail is sent on the Terms and Conditions that can be accessed by Clicking on this link http://www.vodacom.net/legal/email.aspx
RE: [M2] Too heavy load for ibiblio?
One problem I have been having with maven-proxy is that I find that once a jar's metadata is downloaded, it never seems to be updated. I noticed this when Maven 2.0 was released. Soon after that, a few plugins had new versions released but my Maven 2.0 never updated, even using -U and blasting the repository. Only by stopping the proxy, blasting it's cache, and restarting it was I able to get the updated plugins. I think there may need to be a serious code review of this to make sure that it is working correctly with m2 before it is heavily advertised. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jörg Schaible Sent: Friday, October 28, 2005 15:24 To: users@maven.apache.org Subject: Re: [M2] Too heavy load for ibiblio? Hi Jason, Jason van Zyl wrote: On Fri, 2005-10-28 at 08:46 +0200, Dietrich Schulten wrote: Hi, Mvn is having trouble to download commons-codec from ibiblio. Browsing showed that yesterday something was updated there, but I cannot download manually. Is there something broken or are there just too many connections? During peak hours (the afternoon in US TZs) Ibiblio can get rather bogged down. Now that the main push for Maven and Continuum releases have been done we can now focus on some infrastructure issues like repository maintenance and repository distribution. We definitely need to move toward a CPAN like distribution of artifacts. It would be good to advertise maven-proxy much more. It works really fine even for M2. Especially for companies or other big organizations it can decrease the traffic significantly. What's missing: A proper guide how to make use of it in M2 (it took me some time to get the home/.m2/settings.xml right, so that artifacts and plugins will use the proxy) and special hints in the M2 docs for its existence. - Jörg - 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: Installing Commercial Jars and missing POM XML files
A much better choice would be to allow install:install-file to optionally create a POM for the file it is installing. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, October 24, 2005 09:43 To: Maven Users List Subject: Re: Installing Commercial Jars and missing POM XML files From: Pilgrim, Peter [EMAIL PROTECTED] My question is, how do I tell maven not to going looking remotely for POM XML files for the commercial jars since I installed them locally on my machine? http://www.mail-archive.com/users%40maven.apache.org/msg26066.html I've just been creating a pom for them with just the group/artifact/version and Maven stops complaining. Should we submit poms for these non-distributable commercial libraries, so that they're in the repository like the ones for Sun .jars (and we can come to some agreement on the group/artifact ids?) -- Wendy Smoak - 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: Installing Commercial Jars and missing POM XML files
I agree that you would need to add dependencies manually, but you have to do that anyway so that is not an additional burden. Having the minimal POM generated would probably eliminate about 75% of the POM problems. The BEST way for this to happen is to have the VENDOR ship a POM with its libraries. Since that is not likely to ever happen, we will just need to muddle along. I would not want to decide within the Maven community on official group and artifact IDs because that starts to become a nightmare. You need to create a registry for the IDs, you need someone to maintain the registry, you need some sort of approval process to add entries to the registry, etc. The only libraries where this might start to make some sense is ones that are required to make plugins work. In this case, though, I would prefer that the plugin author documents the need to download the jar, where to find it, and how to install it locally so that the plugin works. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, October 24, 2005 09:55 To: Maven Users List Subject: Re: Installing Commercial Jars and missing POM XML files From: Allison, Bob [EMAIL PROTECTED] A much better choice would be to allow install:install-file to optionally create a POM for the file it is installing. It could create the minimal one that I'm doing manually now, but it couldn't know about the dependencies. In addition, it would be nice to officially decide on group and artifact IDs for these things, as well as version numbers (IBM tends to ship .jar files with no manifest so it's hard to tell what you've got.) -- Wendy - 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]
Maven 2 and NetBeans
OK. I know I am weird because I use NetBeans instead of Eclipse, but... The guide for using Maven 2 with NetBeans shows using the netbeans-freeform plugin but does not indicate how to install the plugin in the first place. Not a major item, but it probably should be corrected. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 2 and NetBeans
Built from SVN where? -Original Message- From: Milos Kleint [mailto:[EMAIL PROTECTED] Sent: Monday, October 24, 2005 14:20 To: Maven Users List Subject: Re: Maven 2 and NetBeans unfortunately it wasn't releases AFAIK. i've built it myself localy from svn. works ok.. Milos On 10/24/05, Allison, Bob [EMAIL PROTECTED] wrote: OK. I know I am weird because I use NetBeans instead of Eclipse, but... The guide for using Maven 2 with NetBeans shows using the netbeans-freeform plugin but does not indicate how to install the plugin in the first place. Not a major item, but it probably should be corrected. - 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]
