[ann] Maven 2.0 Beta 3 Released
The Apache Maven team are proud to announce the third beta release of Maven 2.0. Download it from http://maven.apache.org/maven2/download.html Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information. This release includes a number of bug fixes [1] since the previous release on 27 September. Maven 2.0 is a rewrite of the popular Maven application to achieve a number of new goals, and to provide a stable basis to take it into the future. This release is considered stable with a feature set that encompasses and supersedes Maven 1.0. The final release is expected to be backwards compatible with this beta, with a primary goal of bugfixes, usability improvements, and documentation. This core release is independent of the plugins available. Further releases of plugins will be made separately. See Maven Plugin Matrix for more information. We hope you enjoy using Maven! If you have any questions, please consult: * the web site: http://maven.apache.org/maven2/ * the maven-user mailing list: http://maven.apache.org/mail-lists.html For news and information, see: * Maven Blogs: http://www.mavenblogs.com/ [1] http://tinyurl.com/bpa8o [2] http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Matrix - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ann] Maven 2.0 Beta 3 Released
The Apache Maven team are proud to announce the third beta release of Maven 2.0. Wouah, the new CSS is cool! :o) Best Regards / Cordialement, Fabrice BELLINGARD DINQ/DSIN/INSI/EATE/IDVS/AIDV (+33) (01 61) 45 15 91 - [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] running checkstyle as part of a test
I am trying to configure my pom to run the checkstyle plugin when i run the tests. Initially I tried putting this in my POM based on a tutorial I read at http://www.devx.com/Java/Article/28801 build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration propertiesFilecheckstyle-src.xml/propertiesFile failsOnErrortrue/failsOnError /configuration goals goal idtest/id /goal /goals /plugin /plugins /build bu that gave me a warnign that the goals needed to be places within an executions block and anything else had been deprectaed. so a bit of digging turned up http://marc.theaimsgroup.com/?l=turbine-maven-userm=112064009313457w=2 with the suggestion that I arrange my pom.xml more like this: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration propertiesFilecheckstyle-src.xml/propertiesFile failsOnErrortrue/failsOnError /configuration executions execution goals goalTest/goal /goals /execution /executions /plugin /plugins /build but this results in [ERROR] FATAL ERROR [INFO] [INFO] Diagnosis: Goal from the POM 'Test' was not found in the plugin there is a JIRA issue that claims the POM XSD and the docs and the code are all out of sync. http://jira.codehaus.org/browse/MNG-555 so I am left wondering what to do about this... (note i also tried goal names 'test' and 'test:test' I just tried updating to beta 3 today and generating a clean POM with the archetype command but it still references the old - broken XSD file. has anyone got this to work? if so a working example would be very much appreciated. Kind regards, Dave Sag
Re: [m2] running checkstyle as part of a test
I'm not sure where that came from - I don't recall the checkstyle plugin earlier having a separate test goal. This works: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration failsOnErrortrue/failsOnError /configuration !-- These are the lifecycle bindings -- executions execution !-- Execute as part of the test phase -- phasetest/phase goals !-- execute checkstyle:checkstyle -- goalcheckstyle/goal /goals /execution /executions /plugin On 10/5/05, David Sag [EMAIL PROTECTED] wrote: I am trying to configure my pom to run the checkstyle plugin when i run the tests. Initially I tried putting this in my POM based on a tutorial I read at http://www.devx.com/Java/Article/28801 build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration propertiesFilecheckstyle-src.xml/propertiesFile failsOnErrortrue/failsOnError /configuration goals goal idtest/id /goal /goals /plugin /plugins /build bu that gave me a warnign that the goals needed to be places within an executions block and anything else had been deprectaed. so a bit of digging turned up http://marc.theaimsgroup.com/?l=turbine-maven-userm=112064009313457w=2 with the suggestion that I arrange my pom.xml more like this: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration propertiesFilecheckstyle-src.xml/propertiesFile failsOnErrortrue/failsOnError /configuration executions execution goals goalTest/goal /goals /execution /executions /plugin /plugins /build but this results in [ERROR] FATAL ERROR [INFO] [INFO] Diagnosis: Goal from the POM 'Test' was not found in the plugin there is a JIRA issue that claims the POM XSD and the docs and the code are all out of sync. http://jira.codehaus.org/browse/MNG-555 so I am left wondering what to do about this... (note i also tried goal names 'test' and 'test:test' I just tried updating to beta 3 today and generating a clean POM with the archetype command but it still references the old - broken XSD file. has anyone got this to work? if so a working example would be very much appreciated. Kind regards, Dave Sag
Re: [m2] running checkstyle as part of a test
Hey Brett, fantastic - that works fine and now I think I have a better understanding of all those undocumented tags :-) if i get a chance i'll write all this up as there is precious little documentation yet on these matters that i can find. or rather the documentation I have found has been well out of date. Kind regards, Dave Sag Brett Porter [EMAIL PROTECTED] wrote on 05/10/2005 10:25:39 AM: I'm not sure where that came from - I don't recall the checkstyle plugin earlier having a separate test goal. This works: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration failsOnErrortrue/failsOnError /configuration !-- These are the lifecycle bindings -- executions execution !-- Execute as part of the test phase -- phasetest/phase goals !-- execute checkstyle:checkstyle -- goalcheckstyle/goal /goals /execution /executions /plugin On 10/5/05, David Sag [EMAIL PROTECTED] wrote: I am trying to configure my pom to run the checkstyle plugin when i run the tests. Initially I tried putting this in my POM based on a tutorial I read at http://www.devx.com/Java/Article/28801 build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration propertiesFilecheckstyle-src.xml/propertiesFile failsOnErrortrue/failsOnError /configuration goals goal idtest/id /goal /goals /plugin /plugins /build bu that gave me a warnign that the goals needed to be places within an executions block and anything else had been deprectaed. so a bit of digging turned up http://marc.theaimsgroup.com/?l=turbine-maven-userm=112064009313457w=2 with the suggestion that I arrange my pom.xml more like this: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration propertiesFilecheckstyle-src.xml/propertiesFile failsOnErrortrue/failsOnError /configuration executions execution goals goalTest/goal /goals /execution /executions /plugin /plugins /build but this results in [ERROR] FATAL ERROR [INFO] [INFO] Diagnosis: Goal from the POM 'Test' was not found in the plugin there is a JIRA issue that claims the POM XSD and the docs and the code are all out of sync. http://jira.codehaus.org/browse/MNG-555 so I am left wondering what to do about this... (note i also tried goal names 'test' and 'test:test' I just tried updating to beta 3 today and generating a clean POM with the archetype command but it still references the old - broken XSD file. has anyone got this to work? if so a working example would be very much appreciated. Kind regards, Dave Sag
[m2] working on java webservices jaxb xjc plugin
If anyone is interested in working on a plugin for the xjc schema compiler then please let me know as I have one that sort of works and I know that lack of time will mean that I will never bother improving it. For example it only works on Java 5 at them moment as I haven't had time to track down all the necessary (mostly xml) dependencies on ibiblio. Briefly it invokes xjc with just a couple of options at the generate- sources lifecycle phase. If you need such a plugin and would like to help then get in touch with me at [EMAIL PROTECTED] AW - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m1] jalopy plugin how to format generated source
Hi all
i'm using maven-1.1b2, jalopy-plugin-1.3.1 and andromda
the idea is to run andromda on an UML model,
and then format the generated code
my problem is that the jalopy plugin directly uses
pom.build.sourceDirectory
i added a {maven:addPath id=maven.compile.src.set ...} with the
location where my files are generated to allow the compilation
but i can't have the files to be parsed by jalopy!
here's an excerpt from the jalopy-plugin jelly script
ant:jalopy fileformat=${maven.jalopy.fileFormat}
style=${maven.jalopy.style}
history=${maven.jalopy.history}
loglevel=${maven.jalopy.logLevel}
failonerror=${maven.jalopy.failOnError}
threads=${maven.jalopy.nbThread}
classpathref=project.classpath
j:if test=${sourcesPresent == 'true'}
ant:fileset dir=${pom.build.sourceDirectory}
includes=${maven.jalopy.src.filesetInclude}
excludes=${maven.jalopy.src.filesetExclude}/
/j:if
[...]
/ant:jalopy
in my opinion, the fileset should include all path from
maven.compile.src.set !
is there something wrong in my expectations ??
thanks
David
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The simple-webapp example project
The link to the simple-webapp example project on http://maven.apache.org/using/war.html is dead. Can anyone tell me where to find this example? Corné - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] site plugin
I have the following layout src |- site |-xdoc | |-folder1 | |-folder2 |-resources |-images |-logo.gif In site.xml I have the dollowing XML fragment bannerRightsrcimages/logo.gif/src /bannerRight Reaping Business Rewards From CRM Dr Mark KuzmyczPrincipal Consultant Siebel SystemsOne Apple Hill Drive Suite 301 Natick, MA 01760 [EMAIL PROTECTED] tel: fax: +1 508 652 8605+1 508 652 8601 Add me to your address book... Want a signature like this? ___ Siebel IT'S ALL ABOUT THE CUSTOMER Visit www.siebel.com This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Siebel Systems, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation.
[m2-beta-3] Snapshot dependencies with Ant Tasks
I am using SNAPSHOT builds and the Maven dependencies Ant task to synchronise the local and remote repositories. The install/deploy of the snapsot builds works fine, however when I run the Maven dependencies Ant task on the same POMs I get an error Unable to resolve artifact. The Ant dependencies task is attempting to download: groupId/artifactId/1.0-SNAPSHOT/artifactId-1.0-20051005.115507-2.jar However the remote repository only contains the artifact artifactId-1.0-20051005.115507-1.jar Also the maven-metadata.xml contains buildNumber2/buildNumber Is the Ant dependencies task using the wrong build number? Any ideas? Many Thanks Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] site plugin
S orry about that I accident sent the message out early: I have the following layout src |- site |-xdoc | |-folder1 | |-folder2 |-resources |-images |-logo.gif In site.xml I have the dollowing XML fragment bannerRight srcimages/logo.gif/src /bannerRight when I run the site plugin the imige shows for the xml documents in the xdoc folder but not in folder1 or folder2 Is there a way to specify the image (without using an absolute url) so that it shows in documents defined in xdoc, folder1 and folder2? Thanks, Mark. ___ Siebel IT'S ALL ABOUT THE CUSTOMER Visit www.siebel.com This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Siebel Systems, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation.
Re: [m2-beta-3] Snapshot dependencies with Ant Tasks
Yes I've encountered it also - looks like it's related to http://jira.codehaus.org/browse/MNG-1021 On 10/5/05, David Pick [EMAIL PROTECTED] wrote: I am using SNAPSHOT builds and the Maven dependencies Ant task to synchronise the local and remote repositories. The install/deploy of the snapsot builds works fine, however when I run the Maven dependencies Ant task on the same POMs I get an error Unable to resolve artifact. The Ant dependencies task is attempting to download: groupId/artifactId/1.0-SNAPSHOT/artifactId-1.0-20051005.115507-2.jar However the remote repository only contains the artifact artifactId-1.0-20051005.115507-1.jar Also the maven-metadata.xml contains buildNumber2/buildNumber Is the Ant dependencies task using the wrong build number? Any ideas? Many Thanks Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] m1 pom conversion
Hi, I'm trying to resolve MEV-3 which led to this discussion: http://thread.gmane.org/gmane.comp.java.picocontainer.user/723 It appears that multiproject m1 poms and project.properties are the core problems - MAVEN-1390 and friends. What is the official maven stance regarding these features when repocleaning to m2 poms? How can we start to clean these poms up? Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] site plugin
Hi Mark, You are right. Can you file it in JIRA? Regards, Vincent -Original Message- From: Mark Kuzmycz [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 05, 2005 8:09 AM To: users@maven.apache.org Subject: RE: [m2] site plugin S orry about that I accident sent the message out early: I have the following layout src |- site |-xdoc | |-folder1 | |-folder2 |-resources |-images |-logo.gif In site.xml I have the dollowing XML fragment bannerRight srcimages/logo.gif/src /bannerRight when I run the site plugin the imige shows for the xml documents in the xdoc folder but not in folder1 or folder2 Is there a way to specify the image (without using an absolute url) so that it shows in documents defined in xdoc, folder1 and folder2? Thanks, Mark. ___ Siebel IT'S ALL ABOUT THE CUSTOMER Visit www.siebel.com This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Siebel Systems, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2b3] antrun problems
Could someone please tell what's wrong here: I want to execute an ant build file. The filename is build.xml, which is located in the same location as the pom.xml. It has a default target. In pom.xml, I have: . plugin artifactIdmaven-antrun-plugin/artifactId executions execution phasegenerate-sources/phase configuration tasks ant antfile=build.xml/ /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin . When executing (see below) no ant tasks seem to be run. Any ideas? /Mattias C:\work\ratereview\clients\trunkm2 -X antrun:run + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\mattiasar\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\java\MAVEN-~1.0-B\bin\..\conf\plugin-registry.xml' [INFO] Searching repository for plugin with prefix: 'antrun'. [DEBUG] maven-antrun-plugin: resolved to version 1.0-rc1 from repository central [INFO] [INFO] Building RateReview Clients [INFO]task-segment: [antrun:run] [INFO] [DEBUG] eniro-ratereview:ratereview-clients:jar:1.0-SNAPSHOT (selected for null) [DEBUG] axis:axis-wsdl4j:jar:1.5.1 (selected for compile) [DEBUG] axis:axis-jaxrpc:jar:1.2.1 (selected for compile) [DEBUG] axis:axis-saaj:jar:1.2.1 (selected for compile) [DEBUG] commons-discovery:commons-discovery:jar:0.2 (selected for compile) [DEBUG] junit:junit:jar:3.7 (selected for compile) [DEBUG] commons-logging:commons-logging:jar:1.0.3 (selected for compile) [DEBUG] junit:junit:jar:3.7 (removed - nearer found: 3.7) [DEBUG] junit:junit:jar:3.7 (selected for compile) [DEBUG] logkit:logkit:jar:1.0.1 (selected for compile) [DEBUG] log4j:log4j:jar:1.2.6 (selected for compile) [DEBUG] jgoodies:forms:jar:1.0.5 (selected for compile) [DEBUG] axis:axis-ant:jar:1.2.1 (selected for compile) [DEBUG] javax.mail:mail:jar:1.3.2 (selected for compile) [DEBUG] javax.activation:activation:jar:1.0.2 (selected for compile) [DEBUG] axis:axis:jar:1.2.1 (selected for compile) [DEBUG] javax.activation:activation:jar:1.0.2 (removed - nearer found: 1.0.2) [DEBUG] javax.activation:activation:jar:1.0.2 (selected for compile) [DEBUG] org.apache.maven.plugins:maven-antrun-plugin:maven-plugin:1.0-rc1 (selected for runtime) [DEBUG] ant:ant:jar:1.6.5 (selected for runtime) [DEBUG] ant:ant-launcher:jar:1.6.5 (selected for runtime) [INFO] [antrun:run] [INFO] Executing tasks [INFO] Executed tasks [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Oct 05 14:50:21 CEST 2005 [INFO] Final Memory: 1M/4M [INFO]
artifact:dependencies equivalent
Hi, Anyone knows if there is a m2 artifact:dependencies pathId=dependency.classpath equivalent in maven 1 ? If not, how can I create a Ant fileset from a project.xml file with maven 1 ? Best Regards, Antonio ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] site plugin
If it starts with a / and the doc is in a subdirectory, the plugin could add ..'s. For example: bannerRight src/images/logo.gif/src /bannerRight Becomes in /src/site/xdoc: images/logo.gif /src/site/xdoc/folder1: ../images/logo.gif /src/site/xdoc/folder1/folder2: ../../images/logo.gif just / cannot be used as the site might not be deployed in the root of the webserver Geoffrey Vincent Siveton wrote: Hi Mark, You are right. Can you file it in JIRA? Regards, Vincent -Original Message- From: Mark Kuzmycz [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 05, 2005 8:09 AM To: users@maven.apache.org Subject: RE: [m2] site plugin S orry about that I accident sent the message out early: I have the following layout src |- site |-xdoc | |-folder1 | |-folder2 |-resources |-images |-logo.gif In site.xml I have the dollowing XML fragment bannerRight srcimages/logo.gif/src /bannerRight when I run the site plugin the imige shows for the xml documents in the xdoc folder but not in folder1 or folder2 Is there a way to specify the image (without using an absolute url) so that it shows in documents defined in xdoc, folder1 and folder2? Thanks, Mark. ___ Siebel IT'S ALL ABOUT THE CUSTOMER Visit www.siebel.com This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Siebel Systems, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation. -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2b3] antrun problems
Hi Mattias, By phasegenerate-sources/phase , you mean that your configuration must only be used in generate-sources phase (see [1] for details on phases). Calling m2 antrun:run doesn't go into this phase, so it's normal build.xml isn't called. If you want your configuration be always used, put it direclty into plugin : ~ plugin ~artifactIdmaven-antrun-plugin/artifactId ~configuration ~ tasks ~ant antfile=build.xml/ ~ /tasks ~/configuration ~goals ~ goalrun/goal ~/goals ~ /plugin Thinking of it, it's probably the same kind of problem that was reported here : http://marc.theaimsgroup.com/?l=turbine-maven-userm=112835518711351w=2 [1] http://maven.apache.org/maven2/lifecycle.html Regards, Yann --- Mattias Arbin [EMAIL PROTECTED] a écrit : Could someone please tell what's wrong here: I want to execute an ant build file. The filename is build.xml, which is located in the same location as the pom.xml. It has a default target. In pom.xml, I have: . plugin artifactIdmaven-antrun-plugin/artifactId executions execution phasegenerate-sources/phase configuration tasks ant antfile=build.xml/ /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin . When executing (see below) no ant tasks seem to be run. Any ideas? /Mattias C:\work\ratereview\clients\trunkm2 -X antrun:run + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\mattiasar\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\java\MAVEN-~1.0-B\bin\..\conf\plugin-registry.xml' [INFO] Searching repository for plugin with prefix: 'antrun'. [DEBUG] maven-antrun-plugin: resolved to version 1.0-rc1 from repository central [INFO] [INFO] Building RateReview Clients [INFO]task-segment: [antrun:run] [INFO] [DEBUG] eniro-ratereview:ratereview-clients:jar:1.0-SNAPSHOT (selected for null) [DEBUG] axis:axis-wsdl4j:jar:1.5.1 (selected for compile) [DEBUG] axis:axis-jaxrpc:jar:1.2.1 (selected for compile) [DEBUG] axis:axis-saaj:jar:1.2.1 (selected for compile) [DEBUG] commons-discovery:commons-discovery:jar:0.2 (selected for compile) [DEBUG] junit:junit:jar:3.7 (selected for compile) [DEBUG] commons-logging:commons-logging:jar:1.0.3 (selected for compile) [DEBUG] junit:junit:jar:3.7 (removed - nearer found: 3.7) [DEBUG] junit:junit:jar:3.7 (selected for compile) [DEBUG] logkit:logkit:jar:1.0.1 (selected for compile) [DEBUG] log4j:log4j:jar:1.2.6 (selected for compile) [DEBUG] jgoodies:forms:jar:1.0.5 (selected for compile) [DEBUG] axis:axis-ant:jar:1.2.1 (selected for compile) [DEBUG] javax.mail:mail:jar:1.3.2 (selected for compile) [DEBUG] javax.activation:activation:jar:1.0.2 (selected for compile) [DEBUG] axis:axis:jar:1.2.1 (selected for compile) [DEBUG] javax.activation:activation:jar:1.0.2 (removed - nearer found: 1.0.2) [DEBUG] javax.activation:activation:jar:1.0.2 (selected for compile) [DEBUG] org.apache.maven.plugins:maven-antrun-plugin:maven-plugin:1.0-rc1 (selected for runtime) [DEBUG] ant:ant:jar:1.6.5 (selected for runtime) [DEBUG] ant:ant-launcher:jar:1.6.5 (selected for runtime) [INFO] [antrun:run] [INFO] Executing tasks [INFO] Executed tasks [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Oct 05 14:50:21 CEST 2005 [INFO] Final Memory: 1M/4M [INFO] ___ Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger Téléchargez cette version sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SV: [m2b3] antrun problems
Thanks Yann. I will try this. However, what I initially wanted to do was indeed to execute this ant task in the generate-source phase. (It is a java2wsdl task that generates java source) I thought that the configuration previously sent would automatically be executed before the compile phase. So, for instance, if I would type m2 compile the ant task would be executed. But nothing happens at all. Maven does not seem to enter the generate-sources phase. Am I missing something? Thanks, Mattias -Ursprungligt meddelande- Från: Yann Le Du [mailto:[EMAIL PROTECTED] Skickat: den 5 oktober 2005 16:17 Till: Maven Users List Kopia: [EMAIL PROTECTED] Ämne: RE: [m2b3] antrun problems Hi Mattias, By phasegenerate-sources/phase , you mean that your configuration must only be used in generate-sources phase (see [1] for details on phases). Calling m2 antrun:run doesn't go into this phase, so it's normal build.xml isn't called. If you want your configuration be always used, put it direclty into plugin : ~ plugin ~artifactIdmaven-antrun-plugin/artifactId ~configuration ~ tasks ~ant antfile=build.xml/ ~ /tasks ~/configuration ~goals ~ goalrun/goal ~/goals ~ /plugin Thinking of it, it's probably the same kind of problem that was reported here : http://marc.theaimsgroup.com/?l=turbine-maven-userm=112835518711351w=2 [1] http://maven.apache.org/maven2/lifecycle.html Regards, Yann --- Mattias Arbin [EMAIL PROTECTED] a écrit : Could someone please tell what's wrong here: I want to execute an ant build file. The filename is build.xml, which is located in the same location as the pom.xml. It has a default target. In pom.xml, I have: . plugin artifactIdmaven-antrun-plugin/artifactId executions execution phasegenerate-sources/phase configuration tasks ant antfile=build.xml/ /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin . When executing (see below) no ant tasks seem to be run. Any ideas? /Mattias C:\work\ratereview\clients\trunkm2 -X antrun:run + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\mattiasar\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\java\MAVEN-~1.0-B\bin\..\conf\plugin-registry.xml' [INFO] Searching repository for plugin with prefix: 'antrun'. [DEBUG] maven-antrun-plugin: resolved to version 1.0-rc1 from repository central [INFO] [INFO] Building RateReview Clients [INFO]task-segment: [antrun:run] [INFO] [DEBUG] eniro-ratereview:ratereview-clients:jar:1.0-SNAPSHOT (selected for null) [DEBUG] axis:axis-wsdl4j:jar:1.5.1 (selected for compile) [DEBUG] axis:axis-jaxrpc:jar:1.2.1 (selected for compile) [DEBUG] axis:axis-saaj:jar:1.2.1 (selected for compile) [DEBUG] commons-discovery:commons-discovery:jar:0.2 (selected for compile) [DEBUG] junit:junit:jar:3.7 (selected for compile) [DEBUG] commons-logging:commons-logging:jar:1.0.3 (selected for compile) [DEBUG] junit:junit:jar:3.7 (removed - nearer found: 3.7) [DEBUG] junit:junit:jar:3.7 (selected for compile) [DEBUG] logkit:logkit:jar:1.0.1 (selected for compile) [DEBUG] log4j:log4j:jar:1.2.6 (selected for compile) [DEBUG] jgoodies:forms:jar:1.0.5 (selected for compile) [DEBUG] axis:axis-ant:jar:1.2.1 (selected for compile) [DEBUG] javax.mail:mail:jar:1.3.2 (selected for compile) [DEBUG] javax.activation:activation:jar:1.0.2 (selected for compile) [DEBUG] axis:axis:jar:1.2.1 (selected for compile) [DEBUG] javax.activation:activation:jar:1.0.2 (removed - nearer found: 1.0.2) [DEBUG] javax.activation:activation:jar:1.0.2 (selected for compile) [DEBUG] org.apache.maven.plugins:maven-antrun-plugin:maven-plugin:1.0-rc1 (selected for runtime) [DEBUG] ant:ant:jar:1.6.5 (selected for runtime) [DEBUG] ant:ant-launcher:jar:1.6.5 (selected for runtime) [INFO] [antrun:run] [INFO] Executing tasks [INFO] Executed tasks [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Oct 05 14:50:21 CEST 2005 [INFO] Final Memory: 1M/4M [INFO]
[m2] Surefire doesn't discover new tests
I've just installed Maven 2.0 beta-3 and I'm walking through some simple exercises to get a feel for the app. I've used the archetype plugin to create a simple java project and it seems to build fine. However, if I add another test class to the src/test/java directory m2 doesn't seem to detect the new test. When I run m2 test this is the out put I get: [INFO] [compiler:testCompile] Compiling 2 source files to C:\sandbox\eclipse\Roberto\Maven2\my-app\target\test -classes [INFO] [surefire:test] [INFO] Setting reports dir: C:\sandbox\eclipse\Roberto\Maven2\my-app\target/sure fire-reports --- T E S T S --- [surefire] Running com.mycompany.app.AppTest [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0 sec What's interesting is that 2 classes are compiled, but only 1 of the tests is run. Has anyone else experienced this behavior? Am I doning something wrong, or is this the expected behavior? Thanks in advance, Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: SV: [m2b3] antrun problems
Hmm, that's pretty strange, because, according to the Build Lifecycle, calling compile should indeed call generate-sources. I tried it and it's working. What is the type of your artifact, jar or other ? Can you send your whole POM ? Just to be sure... :) did you try to replace your task by a simple echo message=Hello, world !/ Yann --- Mattias Arbin [EMAIL PROTECTED] a écrit : Thanks Yann. I will try this. However, what I initially wanted to do was indeed to execute this ant task in the generate-source phase. (It is a java2wsdl task that generates java source) I thought that the configuration previously sent would automatically be executed before the compile phase. So, for instance, if I would type m2 compile the ant task would be executed. But nothing happens at all. Maven does not seem to enter the generate-sources phase. Am I missing something? Thanks, Mattias -Ursprungligt meddelande- Från: Yann Le Du [mailto:[EMAIL PROTECTED] Skickat: den 5 oktober 2005 16:17 Till: Maven Users List Kopia: [EMAIL PROTECTED] Ämne: RE: [m2b3] antrun problems Hi Mattias, By phasegenerate-sources/phase , you mean that your configuration must only be used in generate-sources phase (see [1] for details on phases). Calling m2 antrun:run doesn't go into this phase, so it's normal build.xml isn't called. If you want your configuration be always used, put it direclty into plugin : ~ plugin ~artifactIdmaven-antrun-plugin/artifactId ~configuration ~ tasks ~ant antfile=build.xml/ ~ /tasks ~/configuration ~goals ~ goalrun/goal ~/goals ~ /plugin Thinking of it, it's probably the same kind of problem that was reported here : http://marc.theaimsgroup.com/?l=turbine-maven-userm=112835518711351w=2 [1] http://maven.apache.org/maven2/lifecycle.html Regards, Yann --- Mattias Arbin [EMAIL PROTECTED] a écrit : Could someone please tell what's wrong here: I want to execute an ant build file. The filename is build.xml, which is located in the same location as the pom.xml. It has a default target. In pom.xml, I have: . plugin artifactIdmaven-antrun-plugin/artifactId executions execution phasegenerate-sources/phase configuration tasks ant antfile=build.xml/ /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin . When executing (see below) no ant tasks seem to be run. Any ideas? /Mattias C:\work\ratereview\clients\trunkm2 -X antrun:run + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\mattiasar\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\java\MAVEN-~1.0-B\bin\..\conf\plugin-registry.xml' [INFO] Searching repository for plugin with prefix: 'antrun'. [DEBUG] maven-antrun-plugin: resolved to version 1.0-rc1 from repository central [INFO] [INFO] Building RateReview Clients [INFO]task-segment: [antrun:run] [INFO] [DEBUG] eniro-ratereview:ratereview-clients:jar:1.0-SNAPSHOT (selected for null) [DEBUG] axis:axis-wsdl4j:jar:1.5.1 (selected for compile) [DEBUG] axis:axis-jaxrpc:jar:1.2.1 (selected for compile) [DEBUG] axis:axis-saaj:jar:1.2.1 (selected for compile) [DEBUG] commons-discovery:commons-discovery:jar:0.2 (selected for compile) [DEBUG] junit:junit:jar:3.7 (selected for compile) [DEBUG] commons-logging:commons-logging:jar:1.0.3 (selected for compile) [DEBUG] junit:junit:jar:3.7 (removed - nearer found: 3.7) [DEBUG] junit:junit:jar:3.7 (selected for compile) [DEBUG] logkit:logkit:jar:1.0.1 (selected for compile) [DEBUG] log4j:log4j:jar:1.2.6 (selected for compile) [DEBUG] jgoodies:forms:jar:1.0.5 (selected for compile) [DEBUG] axis:axis-ant:jar:1.2.1 (selected for compile) [DEBUG] javax.mail:mail:jar:1.3.2 (selected for compile) [DEBUG] javax.activation:activation:jar:1.0.2 (selected for compile) [DEBUG] axis:axis:jar:1.2.1 (selected for compile) [DEBUG] javax.activation:activation:jar:1.0.2 (removed - nearer found: 1.0.2) [DEBUG] javax.activation:activation:jar:1.0.2 (selected for compile) [DEBUG] org.apache.maven.plugins:maven-antrun-plugin:maven-plugin:1.0-rc1 (selected for runtime) [DEBUG] ant:ant:jar:1.6.5 (selected for runtime) [DEBUG] ant:ant-launcher:jar:1.6.5 (selected for
m2: java plugins - configuration and xml
Hi, I'm looking for info that shows how a m2 plugins configuration which is specified in the pom maps to the mojos parameters. For example lets say I had a mojo that had a parameter of type String[] called options. i.e /** * @parameter * private String[] options; What would the xml configuration look like? What about if I had an array that contains one of my plugins own user defined type. Thanks Rob
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
Hi Brett, I finally got the assembly 2.0-beta-2-SNAPSHOT to work this morning after downloading the m2-beta-3. It seems to be working fine except for the fact that it is not including the jars for the modules nor their dependencies. Maybe I am missing something here: At first it was complaining about not being able to find the bin.xml file in the modules. I put a bin.xml just into each one of them containing the dependecySets with the output directory set exactly as it is in the bin.xml that I am pasting below and it started to work but, as I said, without anything from the modules. Here is my root pom symplified: ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.carosys/groupId artifactIdjeeves/artifactId packagingpom/packaging version1.0/version nameJeeves Care/name organization nameCaro Sys/name urlhttp://www.carosys.com/url /organization descriptionA system that is able to produce behaivoral trends as well as point out certain health conditions out of the regular activities of daily living of a person./description developers !-- removed for simplicity -- /developers issueManagement !-- removed for simplicity -- /issueManagement ciManagement !-- removed for simplicity -- /ciManagement scm !-- removed for simplicity -- /scm modules modulejeeves-common/module modulejeeves-hub/module /modules build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.0-beta-2-SNAPSHOT/version configuration descriptorbin.xml/descriptor finalNamejeeves-1.0-beta-1/finalName /configuration /plugin /plugins /build dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.8/version typejar/type /dependency dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version1.0.4/version typejar/type exclusions !-- removed for simplicity -- /exclusions /dependency /dependencies repositories !-- removed for simplicity -- /repositories /project Here is the assembly descriptor. assembly idbin/id formats formatzip/format /formats fileSets fileSet includes includeREADME*/include includeLICENSE*/include includeNOTICE*/include /includes /fileSet fileSet !-- Resources from jeeves-hub-- directoryjeeves-hub/src/main/resources/directory outputDirectoryresources/outputDirectory /fileSet fileSet !-- service-wrapper from jeeves-hub-- directoryjeeves-hub/service-wrapper/directory outputDirectoryservice-wrapper/outputDirectory /fileSet fileSet !-- bat files from jeeves-hub-- directoryjeeves-hub/directory outputDirectory./outputDirectory includes include*.bat/include /includes /fileSet fileSet !-- readme files from jeeves-hub-- directoryjeeves-hub/directory outputDirectory./outputDirectory includes includereadme.*/include /includes /fileSet fileSet !-- xml files from jeeves-common-- directoryjeeves-common/src/main/resources/directory outputDirectoryresources/outputDirectory includes includecommon.properties/include includeAlarmConfig.xml/include includeNewAlarmConfig.xml/include /includes /fileSet /fileSets dependencySets dependencySet outputDirectorylib/outputDirectory /dependencySet /dependencySets /assembly Brett Porter wrote: Tomorrow. On 10/4/05, Erick Dovale [EMAIL PROTECTED] wrote: When is the beta-3 goint to be realeased?? cheers, erick. Brett Porter wrote: .. fixed in SVN for the beta-3 release. On 10/3/05, Brett Porter [EMAIL PROTECTED] wrote: It's a bug. The aggregator isn't forking the package goal first as it should. I will fix it shortly. - Brett On 10/3/05, Erick Dovale [EMAIL PROTECTED] wrote: Hi Brett, I checked out the assembly plugin and was able to build it and
Deployed extensions hardcoded to jar
Hi, I'm using the ant tasks to add dependency management and repositories to my ant project. I'm using the following tasks to deploy a zip that I built to the repository. artifact:pom file=pom.xml id=maven.project/ artifact:deploy file=build/web/foo.zip pom refid=maven.project/ /artifact:deploy When it gets there, though, Maven has changed the extension to .jar and I can't find any way to turn it off. My archive has jsp's in it, so it's not a true jar. The problem gets worse if I want to deploy a document: the document gets its extension changed to .jar. Any help would be appreciated, thanks Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
M2: best way to include property file in a jar artifact?
I am using maven 2 and cannot find an example by which I can have a property file get put into my jar file. I have the property file sitting in with the java code in /src/main/java/com/ Is this best done via pom resource declaration or via pre-compile goals? Is there any complete examples using maven 2? Thanks! Phillip Rhodeshttp://www.jsso.org Open source Java Identity and Authorization Serviceshttp://www.rhoderunner.com Open Source Java Ecommerce Suite - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m102] is there a migration guide to m2?
hello, We are currently using v1.0.2 I looked at the maven2 site but did not see anything that might serve as a guide to migrating from m1 to m2. Is there a helpful guide out there? something that might map m1's project.xml/project.properties/maven.xml to m2's pom.xml/plugins. Thanks for your help. Tom Perry This message is intended for the recipient only and is not meant to be forwarded or distributed in any other format. This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument, or security, or as an official confirmation of any transaction. Putnam does not accept purchase or redemptions of securities, instructions, or authorizations that are sent via e-mail. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of Putnam, LLC (DBA Putnam Investments) and its subsidiaries and affiliates. If you are not the intended recipient of this e-mail, please delete the e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2: best way to include property file in a jar artifact?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Typically, these kinds of non-code jar resources are kept separately under src/main/resources, but you can also specify the following: project ... ~ build ~ ... ~resources ~ resource ~directorysrc/main/java/directory ~excludes ~ exclude**/*.java/exclude ~/excludes ~ /resource ~/resources ~ /build /project If you're using the default location of src/main/resources, this configuration becomes unnecessary. HTH, john phillip rhodes wrote: | I am using maven 2 and cannot find an example by which | I can have a property file get put into my jar file. | I have the property file sitting in with the java code | in /src/main/java/com/ | | Is this best done via pom resource declaration or via | pre-compile goals? | | Is there any complete examples using maven 2? | | Thanks! | | | Phillip Rhodeshttp://www.jsso.org Open source Java Identity and Authorization Serviceshttp://www.rhoderunner.com Open Source Java Ecommerce Suite | | - | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDQ/M+K3h2CZwO/4URAsVLAJ45KaBc7yduu378t8Kbu9OwISDtLwCglzsE mJRew+t7EG9BR+/PiHFbIag= =ZGcA -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Surefire doesn't discover new tests
I believe that the surefire plugin only includes classes with names ending in Test by default. If this is your problem, you can modify this behavior with a configuration section for the surefire plugin... Dan On 10/5/05, Michael Deck [EMAIL PROTECTED] wrote: I've just installed Maven 2.0 beta-3 and I'm walking through some simple exercises to get a feel for the app. I've used the archetype plugin to create a simple java project and it seems to build fine. However, if I add another test class to the src/test/java directory m2 doesn't seem to detect the new test. When I run m2 test this is the out put I get: [INFO] [compiler:testCompile] Compiling 2 source files to C:\sandbox\eclipse\Roberto\Maven2\my-app\target\test -classes [INFO] [surefire:test] [INFO] Setting reports dir: C:\sandbox\eclipse\Roberto\Maven2\my-app\target/sure fire-reports --- T E S T S --- [surefire] Running com.mycompany.app.AppTest [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0 sec What's interesting is that 2 classes are compiled, but only 1 of the tests is run. Has anyone else experienced this behavior? Am I doning something wrong, or is this the expected behavior? Thanks in advance, Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Daniel Krisher - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] project descriptor tags
Just for the archive : the problem is now solved (in m2b3), using the wonderful plugindependencies , instead of extensions Thanks again, Yann --- Yann Le Du [EMAIL PROTECTED] a écrit : Hi Jesse, Yes, my trunk was older than that, that's why the XSD wasn't correct. I'm using beta-1 now. I had put an example of what I'm trying to achieve in the preceding mail - below my signature :) Here's it again : Thanks, Yann ~ project ~ parent ~ artifactIdmyparent/artifactId ~ groupIdcom.corp.myparent/groupId ~ version1.0.0/version ~ /parent ~ ~ modelVersion4.0.0/modelVersion ~ groupIdcom.corp.myparent /groupId ~ artifactIdmyproject/artifactId ~ nameMy project/name ~ version1.0.1-SNAPSHOT/version ~ ~ build ~ extensions ~ extension ~ groupIdant/groupId ~ artifactIdant-nodeps/artifactId ~ version1.6.5/version ~ /extension ~ /extensions ~ ~ [...] ~ ~ plugins ~ plugin ~ artifactIdmaven-antrun-plugin/artifactId ~ ~ executions ~ execution ~ phaseprocess-resources/phase ~ ~ goals ~ goalrun/goal ~ /goals ~ ~ inheritedtrue/inherited ~ ~ configuration ~ tasks ~ ant antfile=replace.xml/ ~ /tasks ~ /configuration ~ /execution ~ /executions ~ /plugin ~ ~ [...] ~ /plugins ~ /build ~ ~ dependencies ~ dependency ~ groupIdant/groupId ~ artifactIdant-nodeps/artifactId ~ version1.6.5/version ~ /dependency ~ ~ [...] ~ /dependencies ~ ~ [...] ~ /project --- Jesse McConnell [EMAIL PROTECTED] a écrit : well, that would depend on how _old_ that trunk version is...I think brett put it in just a month ago or so.. I'll be back in town soon and can help you out on monday maybe.. paste in some examples of what you are trying to do jesse On 9/23/05, Yann Le Du [EMAIL PROTECTED] wrote: Hi Jesse, I happen to try and use the extension mechanism for the antrun-plugin. The ant script I'm trying to run contains regexpmapper tags, so I need ant:ant-nodeps to be available to the plugin (if I add this dependency to antrun-plugin's POM, it's working). A few days ago, Kenney told me about this extension mechanism, but I never get to make it work - I admit now that I was using an ooold trunk version then :) Following your description, I just tried again, but to no avail. Do you see anything wrong in the way I use this mechanism below ? Also, I noticed this issue : http://jira.codehaus.org/browse/MNG-697 Does it mean this extension mechanism isn't operational at the present time ? Thanks, Yann [snip] --- Jesse McConnell [EMAIL PROTECTED] a écrit : sure: this is the pom.xml for the maven-jdbc-plugin...notice there are not dependencies for a database driver in the plugin pom itself. project modelVersion4.0.0/modelVersion parent artifactIdmojo/artifactId groupIdorg.apache.maven.plugins/groupId version1.0.1/version /parent artifactIdmaven-jdbc-plugin/artifactId version0.1-SNAPSHOT/version packagingmaven-plugin/packaging nameMaven JDBC Plugin/name inceptionYear2005/inceptionYear dependencies dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0-beta-1-SNAPSHOT/version /dependency dependency groupIdplexus/groupId artifactIdplexus-utils/artifactId version1.0.1-SNAPSHOT/version /dependency /dependencies /project and here is the pom.xml for something that is using the plugin: project modelVersion4.0.0/modelVersion groupIdg/groupId artifactIdg-db/artifactId packagingjar/packaging version1.0/version nameg - db plugin playground/name parent groupIdg/groupId artifactIdg/artifactId version1.0/version /parent dependencies dependency groupIdoracle/groupId artifactIdoracle/artifactId version9201/version scopecompile/scope /dependency dependency groupIdoracle/groupId artifactIdoracle_nls_charset/artifactId version9201.12/version scopecompile/scope /dependency /dependencies build extensions extension artifactIdoracle/artifactId groupIdoracle/groupId version9201/version /extension extension artifactIdoracle_nls_charset/artifactId groupIdoracle/groupId version9201.12/version /extension /extensions plugins plugin artifactIdmaven-jdbc-plugin/artifactId version1.0-SNAPSHOT/version configuration
Re: Maven 2.0 Cruisecontrol plugin?
According to the plugin matrix (http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Matrix) it hasn't been updated yet, and is listed as low priority. We're going to need it ourselves, so I may just take the time to get some basic functionality. On 10/4/05, Frank Zhao [EMAIL PROTECTED] wrote: We are considering upgrading to Maven 2.0. Can someone tell me whether the current Maven Cruisecontrol plugin v1.7 supprt Maven 2.0 or not? Another question, is there a document showing how to convert Maven 1.0's maven.xml and project.properties files to the pom.xml for Maven 2.0? Thanks in advance, Frank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m20b3] Problems Getting My First Plugin to Work
I am trying to build my first plugin and having a problem. I wrote a plugin which I can run as sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi and that works perfectly. I want to set things up so I can reference the goal as hello:sayhi but can't seem to get it to work. I added sample.plugin as a pluginGroup in my settings.xml file. When I run m2 hello:sayhi, Maven tries to check for updates from central then fails the build when it can't find it on ibiblio even though it was installed into my local repository. Am I missing something vital? On another note, I am trying to use this experience to make a start at the Plugin Development Guide. You can see what I have so far at http://sd.no-ip.biz/maven2pdg/. I welcome any comments, suggestions, and corrections. Right now, it only covers making a plugin with a single mojo that takes no parameters, but I wanted to start simple and add complexities one at a time. This said, the only part of the document that has been started is the part under Your First Plugin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Question on tags for logging
I am creating a plugin and using log:debug and log:info, etc. to get output on the console or in a log file. But I have not been able to find out how to configure maven to output the log messages anywhere. I added a log4j.properties to my user profile folder. I added the log4j.configuration property to my project properties. I get nothing. Any ideas?
Re: [m20b3] Problems Getting My First Plugin to Work
I had a the exact same problem however it went away when I updated to m2b2 and blew away my local repo allowing m2 to recreate it. Since then, it has all work fine. Wb On 10/5/05, Allison, Bob [EMAIL PROTECTED] wrote: I am trying to build my first plugin and having a problem. I wrote a plugin which I can run as sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi and that works perfectly. I want to set things up so I can reference the goal as hello:sayhi but can't seem to get it to work. I added sample.plugin as a pluginGroup in my settings.xml file. When I run m2 hello:sayhi, Maven tries to check for updates from central then fails the build when it can't find it on ibiblio even though it was installed into my local repository. Am I missing something vital? On another note, I am trying to use this experience to make a start at the Plugin Development Guide. You can see what I have so far at http://sd.no-ip.biz/maven2pdg/. I welcome any comments, suggestions, and corrections. Right now, it only covers making a plugin with a single mojo that takes no parameters, but I wanted to start simple and add complexities one at a time. This said, the only part of the document that has been started is the part under Your First Plugin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] pom.xml syntax
Is it possible to customize the syntax of pom.xml without impacting the rest of the Maven2? For example, could one provide a CustomMavenProjectBuilder and then register it as a Plexus MavenProjectBuilder component? How would Maven2 decide which implementation to use, if both the Default and Custom implementations were registered on the M2 classpath? Kind Regards, John Fallows. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] managing transitive dependencies
Suppose I have 3 Maven2 projects, A, B and C. A is self-contained. B depends on A for-implementation-only. C depends on B. My understanding of dependency scopes is that if C depends on B at compile scope, then all of B's compile scope dependencies will also become transitive compile scope dependencies of C. How do I prevent the classes in A from being visible during compilation of C? Is this another usecase for provided scope? Or does marking the A dependency as provided scope may have other implications for project B? I am concerned about the potential to introduce an accidental direct dependency from A to C. Ideally, I'd like project B to control the full set of compile dependencies that are valid exports as transitive dependencies. Although I don't want to expose B's dependencies during compilation of C, some of those dependencies will be necessary at runtime or during unit test execution of C. Perhaps we could specify compile scope for C's dependency on project B itself, but test scope (say) for all of project B's dependencies? Kind Regards, John Fallows. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
bug in DefaultLog
Greetings, The class DefaultLog should protect againg NPE's It is filled with lines like; logger.debug( content.toString(),...) where content can surely be null at times Cheers, -- Chris
Maven era plugin
Hi, (don't know if this is Maven 1.1 specific). The ear plugin doesn't handle type=aop in cactus:generate-ear-descriptor goal. Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven era plugin
It's too late and I made two typos. I am speaking about Maven EAR plugin and EAR:generate-ear-descriptor goal. (the very same problem is in cactus:generate-ear-descriptor goal too) Time to sleep, Jan (don't know if this is Maven 1.1 specific). The ear plugin doesn't handle type=aop in cactus:generate-ear-descriptor goal. Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] pom.xml syntax
On Wed, 2005-10-05 at 18:56 +, John Fallows wrote: Is it possible to customize the syntax of pom.xml without impacting the rest of the Maven2? In theory yes, but would we want to allow that I don't know. What do you want to customize? Is is something generally useful that might be incorporated into Maven itself? For example, could one provide a CustomMavenProjectBuilder and then register it as a Plexus MavenProjectBuilder component? Yes. How would Maven2 decide which implementation to use, if both the Default and Custom implementations were registered on the M2 classpath? Plexus allows multiple implementations of a component which you select by a component id or role hint as we call it in Plexus. You would make your new component and would have to change the components.xml in maven- project and it would work but I don't know if that's something I'd like to see as a common occurrence. Kind Regards, John Fallows. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org you are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] pom.xml syntax
I love maven(2) as it is - but I guess one could come up with a scenario such as database-stored POMs or something of the sort... But I agree this is definitely way out of the main-stream... ;-) On 10/6/05, Jason van Zyl [EMAIL PROTECTED] wrote: On Wed, 2005-10-05 at 18:56 +, John Fallows wrote: Is it possible to customize the syntax of pom.xml without impacting the rest of the Maven2? In theory yes, but would we want to allow that I don't know. What do you want to customize? Is is something generally useful that might be incorporated into Maven itself? For example, could one provide a CustomMavenProjectBuilder and then register it as a Plexus MavenProjectBuilder component? Yes. How would Maven2 decide which implementation to use, if both the Default and Custom implementations were registered on the M2 classpath? Plexus allows multiple implementations of a component which you select by a component id or role hint as we call it in Plexus. You would make your new component and would have to change the components.xml in maven- project and it would work but I don't know if that's something I'd like to see as a common occurrence. Kind Regards, John Fallows. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.org http://maven.apache.org you are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Surefire doesn't discover new tests
On Wed, 2005-10-05 at 11:53 -0400, Daniel Krisher wrote:
I believe that the surefire plugin only includes classes with names
ending in Test by default. If this is your problem, you can modify
this behavior with a configuration section for the surefire
plugin...
The defaults are as follows now:
includes = new ArrayList( Arrays.asList( new String[] { **/Test*.java,
**/*Test.java, **/*TestCase.java } ) );
Dan
On 10/5/05, Michael Deck [EMAIL PROTECTED] wrote:
I've just installed Maven 2.0 beta-3 and I'm walking through some simple
exercises to get a feel for the app. I've used the archetype plugin to
create a simple java project and it seems to build fine. However, if I add
another test class to the src/test/java directory m2 doesn't seem to detect
the new test. When I run m2 test this is the out put I get:
[INFO] [compiler:testCompile]
Compiling 2 source files to
C:\sandbox\eclipse\Roberto\Maven2\my-app\target\test
-classes
[INFO] [surefire:test]
[INFO] Setting reports dir:
C:\sandbox\eclipse\Roberto\Maven2\my-app\target/sure
fire-reports
---
T E S T S
---
[surefire] Running com.mycompany.app.AppTest
[surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0 sec
What's interesting is that 2 classes are compiled, but only 1 of the tests
is run. Has anyone else experienced this behavior? Am I doning something
wrong, or is this the expected behavior?
Thanks in advance,
Mike
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Daniel Krisher
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m102] is there a migration guide to m2?
On Wed, 2005-10-05 at 11:38 -0400, [EMAIL PROTECTED] wrote: hello, We are currently using v1.0.2 I looked at the maven2 site but did not see anything that might serve as a guide to migrating from m1 to m2. We will be releasing tools to help you convert your POMs. Is there a helpful guide out there? something that might map m1's project.xml/project.properties/maven.xml to m2's pom.xml/plugins. Properties are now generally replaced in m2 by plugin configurations, which there are examples of in the getting started guide on the m2 site (http://maven.apache.org/maven2). If you have large maven.xml files those will be a bit trickier as we don't support maven.xml files and are encouraging people to put their logic in plugins immediately. Thanks for your help. Tom Perry This message is intended for the recipient only and is not meant to be forwarded or distributed in any other format. This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument, or security, or as an official confirmation of any transaction. Putnam does not accept purchase or redemptions of securities, instructions, or authorizations that are sent via e-mail. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of Putnam, LLC (DBA Putnam Investments) and its subsidiaries and affiliates. If you are not the intended recipient of this e-mail, please delete the e-mail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: Re: Assembly plugin -- couple of questions [m2a3]]
On Wed, 2005-10-05 at 11:07 -0400, Erick Dovale wrote: Hi Brett, I finally got the assembly 2.0-beta-2-SNAPSHOT to work this morning after downloading the m2-beta-3. It seems to be working fine except for the fact that it is not including the jars for the modules nor their dependencies. Maybe I am missing something here: At first it was complaining about not being able to find the bin.xml file in the modules. I put a bin.xml just into each one of them containing the dependecySets with the output directory set exactly as it is in the bin.xml that I am pasting below and it started to work but, as I said, without anything from the modules. You need to provide the path to the assembly descriptor: build plugins plugin artifactIdmaven-assembly-plugin/artifactId version2.0-beta-1/version configuration descriptorsrc/main/assembly/dep.xml/descriptor /configuration /plugin /plugins /build And you only need to put it in that single location, you don't need to put in each project just the project that is responsible for creating an assembly. -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: m2: java plugins - configuration and xml
On Thu, 2005-10-06 at 00:55 +1000, Robert Biernat wrote: Hi, I'm looking for info that shows how a m2 plugins configuration which is specified in the pom maps to the mojos parameters. For example lets say I had a mojo that had a parameter of type String[] called options. project build plugins plugin artifactIdmaven-magic-plugin/artifactId configuration options option implementation=java.lang.Stringone/option option implementation=java.lang.Stringtwo/option option implementation=java.lang.Stringthree/option /options /configuration /plugin /plugins /build /project Having to specify the implementation there will be fixed shortly but that's what you have to do for now and the fix will be backward compatible we're just going to default to java.lang.String. -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org We all have problems. How we deal with them is a measure of our worth. -- Unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Surefire doesn't discover new tests
Does this go for abstract base classes too? I.e.,
Will surefire find tests defined in a superclass whose name doesn't look
like that?
Dave
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 05, 2005 7:29 PM
To: users@maven.apache.org
Subject: Re: [m2] Surefire doesn't discover new tests
On Wed, 2005-10-05 at 11:53 -0400, Daniel Krisher wrote:
I believe that the surefire plugin only includes classes with names
ending in Test by default. If this is your problem, you can modify
this behavior with a configuration section for the surefire
plugin...
The defaults are as follows now:
includes = new ArrayList( Arrays.asList( new String[] { **/Test*.java,
**/*Test.java, **/*TestCase.java } ) );
Dan
On 10/5/05, Michael Deck [EMAIL PROTECTED] wrote:
I've just installed Maven 2.0 beta-3 and I'm walking through some
simple exercises to get a feel for the app. I've used the archetype
plugin to create a simple java project and it seems to build fine.
However, if I add another test class to the src/test/java directory m2
doesn't seem to detect the new test. When I run m2 test this is the out
put I get:
[INFO] [compiler:testCompile]
Compiling 2 source files to
C:\sandbox\eclipse\Roberto\Maven2\my-app\target\test
-classes
[INFO] [surefire:test]
[INFO] Setting reports dir:
C:\sandbox\eclipse\Roberto\Maven2\my-app\target/sure
fire-reports
---
T E S T S
---
[surefire] Running com.mycompany.app.AppTest
[surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0 sec
What's interesting is that 2 classes are compiled, but only 1 of the
tests is run. Has anyone else experienced this behavior? Am I doning
something wrong, or is this the expected behavior?
Thanks in advance,
Mike
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Daniel Krisher
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
-
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]
[m1.0.2] war file not in dependency list in goal execution
Hi, all,
Due to a particular need of my project, i have to copy some dependencies to
another directory. The dependencies include a war file. I have written this
code fragment in a maven.xml
j:forEach var=lib items=${pom.artifacts}
ant:echo ${lib.name}/ant:echo
j:set var=dep value=${lib.dependency}/
j:set var=group value=${dep.artifactDirectory}/
j:if test=${group=='myprojectA' or group=='myprojectB'}
j:set var=artifact value=${dep.artifact}/
j:set var=type value=${dep.type}/
ant:echoCopy ${artifact} to ${maven.ear.src}/ant:echo
ant:copy toDir=${maven.ear.src}
file=${maven.repo.local}/${group}/${type}s/${artifact}
/
/j:if
/j:forEach
and in my project.xml,
...
dependency
groupIdmyprojectA/groupId
artifactIdmyapp/artifactId
version3.1.4/version
typewar/type
properties
ear.bundletrue/ear.bundle
/properties
/dependency
...
The war file never show up in the above j:forEach/ loop. Why is that? Is
war file not included by default?
Cheers,
AK
RE: [m1.0.2] war file not in dependency list in goal execution
I think I have found out the cause (not the solution, though)
Actually in my dependency list I have these entries:
...
dependency
groupIdmyprojectA/groupId
artifactIdmyapp/artifactId
version3.1.4/version
typeejb/type
/dependency
dependency
groupIdmyprojectA/groupId
artifactIdmyapp/artifactId
version3.1.4/version
typewar/type
properties
ear.bundletrue/ear.bundle
/properties
/dependency
...
Obviously some kind of list building in maven exclude the myapp-3.1.4.war
file from the dependency list. If I introduce a war file of different
groupId and artfactId (says haha), I can see this particular war file
(haha-x.y.z.war) ...
Is it a bug? Is there a workaround of this issue?
Cheers,
AK
-Original Message-
From: Anthony Kong [mailto:[EMAIL PROTECTED]
Sent: Thursday, 6 October 2005 9:32 AM
To: users@maven.apache.org
Subject: [m1.0.2] war file not in dependency list in goal execution
Hi, all,
Due to a particular need of my project, i have to copy some dependencies to
another directory. The dependencies include a war file. I have written this
code fragment in a maven.xml
j:forEach var=lib items=${pom.artifacts}
ant:echo ${lib.name}/ant:echo
j:set var=dep value=${lib.dependency}/
j:set var=group value=${dep.artifactDirectory}/
j:if test=${group=='myprojectA' or group=='myprojectB'}
j:set var=artifact value=${dep.artifact}/
j:set var=type value=${dep.type}/
ant:echoCopy ${artifact} to ${maven.ear.src}/ant:echo
ant:copy toDir=${maven.ear.src}
file=${maven.repo.local}/${group}/${type}s/${artifact}
/
/j:if
/j:forEach
and in my project.xml,
...
dependency
groupIdmyprojectA/groupId
artifactIdmyapp/artifactId
version3.1.4/version
typewar/type
properties
ear.bundletrue/ear.bundle
/properties
/dependency
...
The war file never show up in the above j:forEach/ loop. Why is that? Is
war file not included by default?
Cheers,
AK
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: artifact:dependencies equivalent
maven.dependency.classpath is a pathId of the current project.xml
fileset
j:forEach var=dep items=${dep.artifacts}
pathelement location=${dep.path} /
/j:forEach
/fileset
should do what you need.
- Brett
On 10/5/05, Antonio PAROLINI [EMAIL PROTECTED] wrote:
Hi,
Anyone knows if there is a m2 artifact:dependencies
pathId=dependency.classpath equivalent in maven 1 ?
If not, how can I create a Ant fileset from a project.xml file with
maven 1 ?
Best Regards,
Antonio
**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**
-
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: [m1.0.2] war file not in dependency list in goal execution
I further found out that this problem is solved in m1.1b2.
If I want to, in my custom plugin, to detect maven's version number, how can
I do that? I want to make sure the user runs a maven of version greater than
1.0.2. Anything like this as in perl?
Cheers,
AK
-Original Message-
From: Anthony Kong [mailto:[EMAIL PROTECTED]
Sent: Thursday, 6 October 2005 10:02 AM
To: 'Maven Users List'
Subject: RE: [m1.0.2] war file not in dependency list in goal execution
I think I have found out the cause (not the solution, though)
Actually in my dependency list I have these entries:
...
dependency
groupIdmyprojectA/groupId
artifactIdmyapp/artifactId
version3.1.4/version
typeejb/type
/dependency
dependency
groupIdmyprojectA/groupId
artifactIdmyapp/artifactId
version3.1.4/version
typewar/type
properties
ear.bundletrue/ear.bundle
/properties
/dependency
...
Obviously some kind of list building in maven exclude the myapp-3.1.4.war
file from the dependency list. If I introduce a war file of different
groupId and artfactId (says haha), I can see this particular war file
(haha-x.y.z.war) ...
Is it a bug? Is there a workaround of this issue?
Cheers,
AK
-Original Message-
From: Anthony Kong [mailto:[EMAIL PROTECTED]
Sent: Thursday, 6 October 2005 9:32 AM
To: users@maven.apache.org
Subject: [m1.0.2] war file not in dependency list in goal execution
Hi, all,
Due to a particular need of my project, i have to copy some dependencies to
another directory. The dependencies include a war file. I have written this
code fragment in a maven.xml
j:forEach var=lib items=${pom.artifacts}
ant:echo ${lib.name}/ant:echo
j:set var=dep value=${lib.dependency}/
j:set var=group value=${dep.artifactDirectory}/
j:if test=${group=='myprojectA' or group=='myprojectB'}
j:set var=artifact value=${dep.artifact}/
j:set var=type value=${dep.type}/
ant:echoCopy ${artifact} to ${maven.ear.src}/ant:echo
ant:copy toDir=${maven.ear.src}
file=${maven.repo.local}/${group}/${type}s/${artifact}
/
/j:if
/j:forEach
and in my project.xml,
...
dependency
groupIdmyprojectA/groupId
artifactIdmyapp/artifactId
version3.1.4/version
typewar/type
properties
ear.bundletrue/ear.bundle
/properties
/dependency
...
The war file never show up in the above j:forEach/ loop. Why is that? Is
war file not included by default?
Cheers,
AK
-
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: java plugins - configuration and xml
On 10/6/05, Jason van Zyl [EMAIL PROTECTED] wrote: Having to specify the implementation there will be fixed shortly but that's what you have to do for now and the fix will be backward compatible we're just going to default to java.lang.String. s/will be fixed shortly/was fixed in beta-3/ Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Surefire doesn't discover new tests
Surefire only looks for the other classes to create suites from, but
any tests in superclasses will be used.
- Brett
On 10/6/05, Dave Neuer [EMAIL PROTECTED] wrote:
Does this go for abstract base classes too? I.e.,
Will surefire find tests defined in a superclass whose name doesn't look
like that?
Dave
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 05, 2005 7:29 PM
To: users@maven.apache.org
Subject: Re: [m2] Surefire doesn't discover new tests
On Wed, 2005-10-05 at 11:53 -0400, Daniel Krisher wrote:
I believe that the surefire plugin only includes classes with names
ending in Test by default. If this is your problem, you can modify
this behavior with a configuration section for the surefire
plugin...
The defaults are as follows now:
includes = new ArrayList( Arrays.asList( new String[] { **/Test*.java,
**/*Test.java, **/*TestCase.java } ) );
Dan
On 10/5/05, Michael Deck [EMAIL PROTECTED] wrote:
I've just installed Maven 2.0 beta-3 and I'm walking through some
simple exercises to get a feel for the app. I've used the archetype
plugin to create a simple java project and it seems to build fine.
However, if I add another test class to the src/test/java directory m2
doesn't seem to detect the new test. When I run m2 test this is the out
put I get:
[INFO] [compiler:testCompile]
Compiling 2 source files to
C:\sandbox\eclipse\Roberto\Maven2\my-app\target\test
-classes
[INFO] [surefire:test]
[INFO] Setting reports dir:
C:\sandbox\eclipse\Roberto\Maven2\my-app\target/sure
fire-reports
---
T E S T S
---
[surefire] Running com.mycompany.app.AppTest
[surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0 sec
What's interesting is that 2 classes are compiled, but only 1 of the
tests is run. Has anyone else experienced this behavior? Am I doning
something wrong, or is this the expected behavior?
Thanks in advance,
Mike
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Daniel Krisher
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
-
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] m1 pom conversion
As Joerg mentions, the artifact plugin (1.5.2 for Maven 1.0.2, or 1.6 as included in Maven 1.1 beta 2) now deploys a complete pom instead. I have closed MAVEN-1390 as won't fix. - Brett On 10/5/05, Mark Hobson [EMAIL PROTECTED] wrote: Hi, I'm trying to resolve MEV-3 which led to this discussion: http://thread.gmane.org/gmane.comp.java.picocontainer.user/723 It appears that multiproject m1 poms and project.properties are the core problems - MAVEN-1390 and friends. What is the official maven stance regarding these features when repocleaning to m2 poms? How can we start to clean these poms up? Cheers, Mark - 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] managing transitive dependencies
Sorry, I'm missing something. Why isn't B depending on A with runtime scope? - Brett On 10/6/05, John Fallows [EMAIL PROTECTED] wrote: Suppose I have 3 Maven2 projects, A, B and C. A is self-contained. B depends on A for-implementation-only. C depends on B. My understanding of dependency scopes is that if C depends on B at compile scope, then all of B's compile scope dependencies will also become transitive compile scope dependencies of C. How do I prevent the classes in A from being visible during compilation of C? Is this another usecase for provided scope? Or does marking the A dependency as provided scope may have other implications for project B? I am concerned about the potential to introduce an accidental direct dependency from A to C. Ideally, I'd like project B to control the full set of compile dependencies that are valid exports as transitive dependencies. Although I don't want to expose B's dependencies during compilation of C, some of those dependencies will be necessary at runtime or during unit test execution of C. Perhaps we could specify compile scope for C's dependency on project B itself, but test scope (say) for all of project B's dependencies? Kind Regards, John Fallows. - 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 on tags for logging
These tags should go to the normal output, and are controlled by Maven's log4j.properties. debug is only shown with -X info is suppressed with -q Did you include a dependency on comons-jelly-tags-logging? - Brett On 10/6/05, Weaver, Jonathan [EMAIL PROTECTED] wrote: I am creating a plugin and using log:debug and log:info, etc. to get output on the console or in a log file. But I have not been able to find out how to configure maven to output the log messages anywhere. I added a log4j.properties to my user profile folder. I added the log4j.configuration property to my project properties. I get nothing. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deployed extensions hardcoded to jar
it's controlled by packaging/ in the pom. However, you might need more functionality from the ant task - please file a bug. - Brett On 10/6/05, Daniel Hannum [EMAIL PROTECTED] wrote: Hi, I'm using the ant tasks to add dependency management and repositories to my ant project. I'm using the following tasks to deploy a zip that I built to the repository. artifact:pom file=pom.xml id=maven.project/ artifact:deploy file=build/web/foo.zip pom refid=maven.project/ /artifact:deploy When it gets there, though, Maven has changed the extension to .jar and I can't find any way to turn it off. My archive has jsp's in it, so it's not a true jar. The problem gets worse if I want to deploy a document: the document gets its extension changed to .jar. Any help would be appreciated, thanks Dan - 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] faulty scp protocol handling in wagon?
have jsch indicated when they might include it? is the scpexe protocol a viable alternative for you? - Brett On 10/5/05, Orjan Austvold [EMAIL PROTECTED] wrote: I noticed that sch 0.1.22 got released yesterday. Only to bad that that it did not include a fix for the MNG-678 issue. In the meantime I'm forced to continue providing a modified m2-b2 release containing a patched jsch library for building projects at work. -- Ørjan Brett Porter wrote: This is great. Thanks for your help on this - I'll take a look. - Brett On 9/30/05, Orjan Austvold [EMAIL PROTECTED] wrote: The issue with intermittent failure in ScpWagon seems to have been solved now. To me it seems to be a race condition between the thread running the ScpWagon and the internal jsch thread tracking session events. ScpWagon terminates the exec channel when it discovers that enough bytes have been read/written. This interferes with jsch which could receive an SSH_MSG_CHANNEL_EOF message from the remote server at the same time. I have filed a bug-report to the jsch project and updated the MNG-678 JIRA issue for m2 with a description of what's going on. My guess is that even though this is a failure in jsch, the ScpWagon code should do proper testing for if a session is connected or not before creating a channel. Thanks, Ørjan Brett Porter wrote: I have experienced this too - there is an open bug I believe. I'm not sure if the problem is in jsch, or our use of jsch though. I'd welcome any assistance you can provide. Thanks, Brett On 9/21/05, Orjan Austvold [EMAIL PROTECTED] wrote: Often when downloading new artifacts from a scp repository the build fails with Root error: session is down It could be that my the ssh configuration on the scp repository is faulty, but I thought I'd check here before digging into ssh-debugging. In my pom.xml I have configured repositories repository idsecure-repository/id urlscp:/myhost.com/var/mavenrep/maven2/url layoutdefault/layout snapshotPolicydaily/snapshotPolicy /repository repository idcentral/id urlhttp://ibiblio.org/maven2/url /repository /repositories In my settings.xml I have configured settings servers server idsecure-repository/id usernameme/username privateKey/home/me/.ssh/id_dsa/privateKey passphrasemyPassPhrase/passphrase /server /servers mirrors mirror idcloser-central/id urlhttp://mirrors.sunsite.dk/maven2/url layoutdefault/layout snapshotPolicydaily/snapshotPolicy mirrorOfcentral/mirrorOf /mirror /mirrors /settings Best regards, Ørjan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ørjan Austvold - Senior Software Architect www.colibria.com - putting the presence into messaging - 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] -- Ørjan Austvold - Senior Software Architect www.colibria.com - putting the presence into messaging - 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]
