Looking for a workaround for MNG-3228 (activate inherited profile)
Any idea? The main reason why we want to do this is to be able to have different types of projects. Each type has different pom settings which we want to maintain in a central place. At the moment we have a master pom per project type which limits us in combination with module builds as Maven doesn't support multiple inheritance at the moment (master pom+ module parent). That's why we want to implement profiles but don't know how to workaround MNG-3228. Any input highly appreciated! Thanks Stefan Original Message Subject: Looking for a workaround for MNG-3228 (activate inherited profile) Date: Wed, 28 Jan 2009 08:11:34 +0100 From: Stefan Fritz sfritz.nos...@gmx.at Reply-To: Maven Users List users@maven.apache.org To: Maven Users List users@maven.apache.org References: 9aec5f50bd7e0f48891ae45adc56118403592...@ldnukms2.caplin.com 562346790901200455i39250a79vd311d152b3884...@mail.gmail.com 9aec5f50bd7e0f48891ae45adc56118403592...@ldnukms2.caplin.com Hi all, We try to define profiles in our master pom. When we trigger a build we want to activate a specific profile via a property in the projects pom. (activation via -P works fine). But it seems we ran into the following issue: http://jira.codehaus.org/browse/MNG-3228 Is there any workaround to be able to activate a profile (defined in a master pom) per project? Thanks Stefan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Looking for a workaround for MNG-3228 (activate inherited profile)
Hi all, We try to define profiles in our master pom. When we trigger a build we want to activate a specific profile via a property in the projects pom. (activation via -P works fine). But it seems we ran into the following issue: http://jira.codehaus.org/browse/MNG-3228 Is there any workaround to be able to activate a profile (defined in a master pom) per project? Thanks Stefan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
java.lang.NoClassDefFoundError: org/codehaus/plexus/util/xml/XmlStreamReader
Hi all, we have a custom Maven plugin to package artifacts for our ESB. The plugin works fine on my Windows machine (WinXP, Maven 2.0.9, Sun JDK 5) but when I package a project on our server it fails. The error occurs on with Sun JDK5/6 on Linux. Does anybody have an idea what the cause of this could be? (see console output below) Thanks Stefan started Checking out https://iocc-svn.asn.lsy.dlh.de/maven/iocc/com.lhsystems.iocc.esb.instances.taoff/taoff-pubweather-opsm-air0001/snapshots/1.0-SNAPSHOT/latest/taoff-pubweather-opsm-air0001 A .project A src A src/main A src/main/ESB A src/main/resources A src/main/resources/Offramp-CrewM-WxCatNotification-OracleAQDataSink.xml A src/main/resources/ESB A src/main/resources/ESB/ExportProperties.xml A pom.xml A deploy A deploy/generated-src A deploy/generated-src/xar A deploy/generated-src/xar/ESB A deploy/generated-src/xar/ESB/Endpoints A deploy/generated-src/xar/ESB/Endpoints/iocc.TechnicalAdapter.Offramp-CrewM-WxCatNotification.xml A deploy/generated-src/xar/ESB/Services A deploy/generated-src/xar/ESB/Services/iocc.TechnicalAdapter.Offramp-CrewM-WxCatNotification.xml At revision 5306 no change for https://iocc-svn.asn.lsy.dlh.de/maven/iocc/com.lhsystems.iocc.esb.instances.taoff/taoff-pubweather-opsm-air0001/snapshots/1.0-SNAPSHOT/latest/taoff-pubweather-opsm-air0001 since the previous build Parsing POMs [taoff-pubweather-opsm-air0001] $ /usr/java/jdk1.5.0_12/bin/java -Xms64m -Xmx256m -cp /users/maven/tools/hudson/war/WEB-INF/lib/maven-agent-1.262.jar:/users/maven/tools/maven2/boot/classworlds-1.1.jar hudson.maven.agent.Main /users/maven/tools/maven2 /users/maven/tools/hudson/war/WEB-INF/lib/remoting-1.262.jar /users/maven/tools/hudson/war/WEB-INF/lib/maven-interceptor-1.262.jar 10078 channel started Executing Maven: -B -B -f /users/maven/tools/hudson/jobs/com.lhsystems.iocc.esb.instances.taoff--taoff-pubweather-opsm-air0001--1.0-SNAPSHOT/workspace/taoff-pubweather-opsm-air0001/pom.xml -e -Dflow-config.mavenpath=/users/maven/tools/maven2/bin/ -Desb.skipExport=true -Desb.failOnExportError=false -U -P development clean install+ Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] snapshot com.lhsystems.iocc.build:pom-esbproject:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.lhsystems.iocc.build:pom-esbproject:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.lhsystems.iocc.build:pom-esbproject:1.0-SNAPSHOT: checking for updates from releases [INFO] snapshot com.lhsystems.iocc.build:pom-java:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.lhsystems.iocc.build:pom-java:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.lhsystems.iocc.build:pom-java:1.0-SNAPSHOT: checking for updates from releases WAGON_VERSION: 1.0-beta-2 [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from releases [INFO] [INFO] Building Unnamed - com.lhsystems.iocc.esb.instances.taoff:taoff-pubweather-opsm-air0001:esb:1.0-SNAPSHOT [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] snapshot com.sonicsw.pso.services:SpringAdapterService:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.pso.services:SpringAdapterService:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.sonicsw.pso.services:SpringAdapterService:1.0-SNAPSHOT: checking for updates from releases [INFO] snapshot com.sonicsw.pso.libraries:JMSAdapter:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.pso.libraries:JMSAdapter:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.sonicsw.pso.libraries:JMSAdapter:1.0-SNAPSHOT: checking for updates from releases [INFO] snapshot com.sonicsw.pso.libraries:OracleConnector:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.pso.libraries:OracleConnector:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.sonicsw.pso.libraries:OracleConnector:1.0-SNAPSHOT: checking for updates from releases [INFO] snapshot com.lhsystems.iocc.esb.common:flow-commons:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.lhsystems.iocc.esb.common:flow-commons:1.0-SNAPSHOT: checking for updates from snapshots [INFO]
Re: java.lang.NoClassDefFoundError: org/codehaus/plexus/util/xml/XmlStreamReader
Good tip but according to the error it seems to have classloading issues with XmlStreamReader which is not part of my JAR. I guess it is part of plexus-utils-1.1.jar which exists under the path printed in the log: this realm = app0.child-container[com.sonicsw.maven.plugins:ESBPlugin] urls[0] =file:/users/maven/.m2/repository/com/sonicsw/maven/plugins/ESBPlugin/1.0-SNAPSHOT/ESBPlugin-1.0-SNAPSHOT.jar urls[1] =file:/users/maven/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar Or do I misinterpret the error? Stefan Anders Hammar wrote: I wild guess would be that you have misspelled some dependency regarding upper/lower case. If you, for instance, specify ESBblabla.jar Windows will match that with the file esbblabla.jar while Linux will not. The same goes for paths. Just something I learned the hard way from an issue we had some weeks ago which cost us quite a few hours to find the cause for. That was for a deployment that worked on Windows but not on Linux. A dependecy for the classpath in one of the manifest files was incorrect regarding upper/lower case. /Anders Stefan Fritz-2 wrote: Hi all, we have a custom Maven plugin to package artifacts for our ESB. The plugin works fine on my Windows machine (WinXP, Maven 2.0.9, Sun JDK 5) but when I package a project on our server it fails. The error occurs on with Sun JDK5/6 on Linux. Does anybody have an idea what the cause of this could be? (see console output below) Thanks Stefan started Checking out https://iocc-svn.asn.lsy.dlh.de/maven/iocc/com.lhsystems.iocc.esb.instances.taoff/taoff-pubweather-opsm-air0001/snapshots/1.0-SNAPSHOT/latest/taoff-pubweather-opsm-air0001 A .project A src A src/main A src/main/ESB A src/main/resources A src/main/resources/Offramp-CrewM-WxCatNotification-OracleAQDataSink.xml A src/main/resources/ESB A src/main/resources/ESB/ExportProperties.xml A pom.xml A deploy A deploy/generated-src A deploy/generated-src/xar A deploy/generated-src/xar/ESB A deploy/generated-src/xar/ESB/Endpoints A deploy/generated-src/xar/ESB/Endpoints/iocc.TechnicalAdapter.Offramp-CrewM-WxCatNotification.xml A deploy/generated-src/xar/ESB/Services A deploy/generated-src/xar/ESB/Services/iocc.TechnicalAdapter.Offramp-CrewM-WxCatNotification.xml At revision 5306 no change for https://iocc-svn.asn.lsy.dlh.de/maven/iocc/com.lhsystems.iocc.esb.instances.taoff/taoff-pubweather-opsm-air0001/snapshots/1.0-SNAPSHOT/latest/taoff-pubweather-opsm-air0001 since the previous build Parsing POMs [taoff-pubweather-opsm-air0001] $ /usr/java/jdk1.5.0_12/bin/java -Xms64m -Xmx256m -cp /users/maven/tools/hudson/war/WEB-INF/lib/maven-agent-1.262.jar:/users/maven/tools/maven2/boot/classworlds-1.1.jar hudson.maven.agent.Main /users/maven/tools/maven2 /users/maven/tools/hudson/war/WEB-INF/lib/remoting-1.262.jar /users/maven/tools/hudson/war/WEB-INF/lib/maven-interceptor-1.262.jar 10078 channel started Executing Maven: -B -B -f /users/maven/tools/hudson/jobs/com.lhsystems.iocc.esb.instances.taoff--taoff-pubweather-opsm-air0001--1.0-SNAPSHOT/workspace/taoff-pubweather-opsm-air0001/pom.xml -e -Dflow-config.mavenpath=/users/maven/tools/maven2/bin/ -Desb.skipExport=true -Desb.failOnExportError=false -U -P development clean install+ Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] snapshot com.lhsystems.iocc.build:pom-esbproject:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.lhsystems.iocc.build:pom-esbproject:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.lhsystems.iocc.build:pom-esbproject:1.0-SNAPSHOT: checking for updates from releases [INFO] snapshot com.lhsystems.iocc.build:pom-java:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.lhsystems.iocc.build:pom-java:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.lhsystems.iocc.build:pom-java:1.0-SNAPSHOT: checking for updates from releases WAGON_VERSION: 1.0-beta-2 [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from releases [INFO] [INFO] Building Unnamed - com.lhsystems.iocc.esb.instances.taoff:taoff-pubweather-opsm-air0001:esb:1.0-SNAPSHOT [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] snapshot com.sonicsw.pso.services:SpringAdapterService:1.0-SNAPSHOT
Re: java.lang.NoClassDefFoundError: org/codehaus/plexus/util/xml/XmlStreamReader
Both machines use Maven 2.0.9: Maven version: 2.0.9 Java version: 1.5.0_12 OS name: linux version: 2.6.9-78.0.5.elsmp arch: i386 Family: unix Maven version: 2.0.9 Java version: 1.5.0_14 OS name: windows xp version: 5.1 arch: x86 Family: windows -Stefan Dennis Lundberg wrote: You need Maven 2.0.6+ to be able to override plexus-utils. Which version of Maven are you using on the Linux server? Stefan Fritz wrote: Hi all, we have a custom Maven plugin to package artifacts for our ESB. The plugin works fine on my Windows machine (WinXP, Maven 2.0.9, Sun JDK 5) but when I package a project on our server it fails. The error occurs on with Sun JDK5/6 on Linux. Does anybody have an idea what the cause of this could be? (see console output below) Thanks Stefan started Checking out https://iocc-svn.asn.lsy.dlh.de/maven/iocc/com.lhsystems.iocc.esb.instances.taoff/taoff-pubweather-opsm-air0001/snapshots/1.0-SNAPSHOT/latest/taoff-pubweather-opsm-air0001 A .project A src A src/main A src/main/ESB A src/main/resources A src/main/resources/Offramp-CrewM-WxCatNotification-OracleAQDataSink.xml A src/main/resources/ESB A src/main/resources/ESB/ExportProperties.xml A pom.xml A deploy A deploy/generated-src A deploy/generated-src/xar A deploy/generated-src/xar/ESB A deploy/generated-src/xar/ESB/Endpoints A deploy/generated-src/xar/ESB/Endpoints/iocc.TechnicalAdapter.Offramp-CrewM-WxCatNotification.xml A deploy/generated-src/xar/ESB/Services A deploy/generated-src/xar/ESB/Services/iocc.TechnicalAdapter.Offramp-CrewM-WxCatNotification.xml At revision 5306 no change for https://iocc-svn.asn.lsy.dlh.de/maven/iocc/com.lhsystems.iocc.esb.instances.taoff/taoff-pubweather-opsm-air0001/snapshots/1.0-SNAPSHOT/latest/taoff-pubweather-opsm-air0001 since the previous build Parsing POMs [taoff-pubweather-opsm-air0001] $ /usr/java/jdk1.5.0_12/bin/java -Xms64m -Xmx256m -cp /users/maven/tools/hudson/war/WEB-INF/lib/maven-agent-1.262.jar:/users/maven/tools/maven2/boot/classworlds-1.1.jar hudson.maven.agent.Main /users/maven/tools/maven2 /users/maven/tools/hudson/war/WEB-INF/lib/remoting-1.262.jar /users/maven/tools/hudson/war/WEB-INF/lib/maven-interceptor-1.262.jar 10078 channel started Executing Maven: -B -B -f /users/maven/tools/hudson/jobs/com.lhsystems.iocc.esb.instances.taoff--taoff-pubweather-opsm-air0001--1.0-SNAPSHOT/workspace/taoff-pubweather-opsm-air0001/pom.xml -e -Dflow-config.mavenpath=/users/maven/tools/maven2/bin/ -Desb.skipExport=true -Desb.failOnExportError=false -U -P development clean install+ Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] snapshot com.lhsystems.iocc.build:pom-esbproject:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.lhsystems.iocc.build:pom-esbproject:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.lhsystems.iocc.build:pom-esbproject:1.0-SNAPSHOT: checking for updates from releases [INFO] snapshot com.lhsystems.iocc.build:pom-java:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.lhsystems.iocc.build:pom-java:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.lhsystems.iocc.build:pom-java:1.0-SNAPSHOT: checking for updates from releases WAGON_VERSION: 1.0-beta-2 [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from releases [INFO] [INFO] Building Unnamed - com.lhsystems.iocc.esb.instances.taoff:taoff-pubweather-opsm-air0001:esb:1.0-SNAPSHOT [INFO]task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] snapshot com.sonicsw.pso.services:SpringAdapterService:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.pso.services:SpringAdapterService:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.sonicsw.pso.services:SpringAdapterService:1.0-SNAPSHOT: checking for updates from releases [INFO] snapshot com.sonicsw.pso.libraries:JMSAdapter:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.pso.libraries:JMSAdapter:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.sonicsw.pso.libraries:JMSAdapter:1.0-SNAPSHOT: checking for updates from releases [INFO] snapshot com.sonicsw.pso.libraries:OracleConnector:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot
Re: java.lang.NoClassDefFoundError: org/codehaus/plexus/util/xml/XmlStreamReader
--* SOLVED *-- I „solved“ it. The issue was that some plugin dependencies couldn't be resolved. I ran help:effective-pom which was identical for Linux and windows, then I ran dependency:resolve-plugins I got no error on both systems although the plugins dependencies list was much shorter on the Linux server. So it seems dependency handling for plugins doesn’t complain if dependencies are missing :-( I changed the settings.xml to include another internal repository and now it works again. Thanks for your tips! Stefan Stefan Fritz wrote: Hi all, we have a custom Maven plugin to package artifacts for our ESB. The plugin works fine on my Windows machine (WinXP, Maven 2.0.9, Sun JDK 5) but when I package a project on our server it fails. The error occurs on with Sun JDK5/6 on Linux. Does anybody have an idea what the cause of this could be? (see console output below) Thanks Stefan started Checking out https://iocc-svn.asn.lsy.dlh.de/maven/iocc/com.lhsystems.iocc.esb.instances.taoff/taoff-pubweather-opsm-air0001/snapshots/1.0-SNAPSHOT/latest/taoff-pubweather-opsm-air0001 A .project A src A src/main A src/main/ESB A src/main/resources A src/main/resources/Offramp-CrewM-WxCatNotification-OracleAQDataSink.xml A src/main/resources/ESB A src/main/resources/ESB/ExportProperties.xml A pom.xml A deploy A deploy/generated-src A deploy/generated-src/xar A deploy/generated-src/xar/ESB A deploy/generated-src/xar/ESB/Endpoints A deploy/generated-src/xar/ESB/Endpoints/iocc.TechnicalAdapter.Offramp-CrewM-WxCatNotification.xml A deploy/generated-src/xar/ESB/Services A deploy/generated-src/xar/ESB/Services/iocc.TechnicalAdapter.Offramp-CrewM-WxCatNotification.xml At revision 5306 no change for https://iocc-svn.asn.lsy.dlh.de/maven/iocc/com.lhsystems.iocc.esb.instances.taoff/taoff-pubweather-opsm-air0001/snapshots/1.0-SNAPSHOT/latest/taoff-pubweather-opsm-air0001 since the previous build Parsing POMs [taoff-pubweather-opsm-air0001] $ /usr/java/jdk1.5.0_12/bin/java -Xms64m -Xmx256m -cp /users/maven/tools/hudson/war/WEB-INF/lib/maven-agent-1.262.jar:/users/maven/tools/maven2/boot/classworlds-1.1.jar hudson.maven.agent.Main /users/maven/tools/maven2 /users/maven/tools/hudson/war/WEB-INF/lib/remoting-1.262.jar /users/maven/tools/hudson/war/WEB-INF/lib/maven-interceptor-1.262.jar 10078 channel started Executing Maven: -B -B -f /users/maven/tools/hudson/jobs/com.lhsystems.iocc.esb.instances.taoff--taoff-pubweather-opsm-air0001--1.0-SNAPSHOT/workspace/taoff-pubweather-opsm-air0001/pom.xml -e -Dflow-config.mavenpath=/users/maven/tools/maven2/bin/ -Desb.skipExport=true -Desb.failOnExportError=false -U -P development clean install+ Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] snapshot com.lhsystems.iocc.build:pom-esbproject:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.lhsystems.iocc.build:pom-esbproject:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.lhsystems.iocc.build:pom-esbproject:1.0-SNAPSHOT: checking for updates from releases [INFO] snapshot com.lhsystems.iocc.build:pom-java:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.lhsystems.iocc.build:pom-java:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.lhsystems.iocc.build:pom-java:1.0-SNAPSHOT: checking for updates from releases WAGON_VERSION: 1.0-beta-2 [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.sonicsw.maven.plugins:ESBPlugin:1.0-SNAPSHOT: checking for updates from releases [INFO] [INFO] Building Unnamed - com.lhsystems.iocc.esb.instances.taoff:taoff-pubweather-opsm-air0001:esb:1.0-SNAPSHOT [INFO] task-segment: [clean, install] [INFO] [INFO] [clean:clean] [INFO] snapshot com.sonicsw.pso.services:SpringAdapterService:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.pso.services:SpringAdapterService:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.sonicsw.pso.services:SpringAdapterService:1.0-SNAPSHOT: checking for updates from releases [INFO] snapshot com.sonicsw.pso.libraries:JMSAdapter:1.0-SNAPSHOT: checking for updates from plugins [INFO] snapshot com.sonicsw.pso.libraries:JMSAdapter:1.0-SNAPSHOT: checking for updates from snapshots [INFO] snapshot com.sonicsw.pso.libraries:JMSAdapter:1.0-SNAPSHOT: checking for updates from releases [INFO] snapshot com.sonicsw.pso.libraries:OracleConnector:1.0-SNAPSHOT: checking for updates from plugins [INFO
Re: How to version modules when using different parents per module
Brett, We thought about adding the version numbers to a master pom but this would cause trouble if we start branching. I guess we will have to move away from our project type specific poms to a single master pom and then we can use the moude-build pom to define the versions. Thanks Stefan Brett Porter wrote: No, there is only single inheritance, so you can't have different inheritance and a central location, unless there is a common ancestor somewhere. The setup you describe sounds rather confusing - Maven inheritance differs from the object oriented concept in that it is largely structural rather than typed. Can you have the types share a single ancestor so the module build and the inheritance hierarchy line up? Cheers, Brett On 25/11/2008, at 8:10 AM, Stefan Fritz wrote: Hi all, We have multiple projects which should be built using a module build. Each project is of a different type and therefore has a different parent pom (not the module build pom!). Now my problem is that I want to maintain the version at a central place. The only solution I could think of is to have one master pom where I define the module versions as properties in this pom. As we will have many module builds this although will lead to a chaos when branching multiple module builds. Is there a way to have: - projects built via a module build - a central place for maintaining the modules version - different parents per project in my module build ? Thanks Stefan -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - 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]
How to version modules when using different parents per module
Hi all, We have multiple projects which should be built using a module build. Each project is of a different type and therefore has a different parent pom (not the module build pom!). Now my problem is that I want to maintain the version at a central place. The only solution I could think of is to have one master pom where I define the module versions as properties in this pom. As we will have many module builds this although will lead to a chaos when branching multiple module builds. Is there a way to have: - projects built via a module build - a central place for maintaining the modules version - different parents per project in my module build ? Thanks Stefan
Rename files after creation via archetype
Hi all, Is there an easy way to automatically rename some files during/after creating a project via an archetype? Thanks Steafn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
trunk/tags/branches: root vs. project level
Hi all, we are in the process of restructuring a subversion repository and Mavenize all projects. The main discussion at the moment is whether to have trunk/tags/branches on the root level or once per project. root: trunk/project1/pom.xml trunk/project2/pom.xml branches/branch1/project1/pom.xml project level project1/trunk/project1/pom.xml project1/branches/branch1/project1/pom.xml root level: pro: all branch/patch related projects in one location easy to navigate easy to update cons: does mvn release:branch work ? mergin can get hard if somebody commits at root level project level. pro: easy to work with mvn release merging should be easy cons: complex for scenarios where you have to deal with multiple projects at once Would be curious about your opinions/comments! Thanks Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: trunk/tags/branches: root vs. project level
The main clincher is that we generally run all our sub-modules as children of a parent super-module. That's only possible with the root approach. or you define trunk/tags/branches per module-group instead of per project as you would do for standalone projects ;-) Thanks Stefan Andy Law wrote: Stefan Fritz-2 wrote: Hi all, we are in the process of restructuring a subversion repository and Mavenize all projects. The main discussion at the moment is whether to have trunk/tags/branches on the root level or once per project. root: trunk/project1/pom.xml trunk/project2/pom.xml branches/branch1/project1/pom.xml project level project1/trunk/project1/pom.xml project1/branches/branch1/project1/pom.xml First comment: Subversion doesn't care. You need to come up with something that fits the way that you work best (I know that's no help!) Secondly: FWIW, *we* use the root approach (with an extra level of parent module). I have never had problems with checkin at the root level, although some of my colleagues occasionally grumble about it. I think that this is more a Netbeans-subversion issue rather than a subversion issue. The main clincher is that we generally run all our sub-modules as children of a parent super-module. That's only possible with the root approach. I can't see anything that you can do with the project approach that you can't do with the root approach but the opposite is not true (see above). And there is nothing in your project approach that wouldn't stop someone checking out and committing at the root level anyway. Later, Andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to release module build projects?
Hi, I try to use mvn release in a multi-module build scenario but I'm not sure whether I go into the right direction. Our standalone projects have the following structure: projA \_trunk \_tags \_branches We also have some multi module projects and I wonder what is the best way to structure these to be able to run a mvn release:perform on the module build pom? My first thought was to have trunk/tags/branches on the module-parent as well: moduleBuild \_trunk | \_pom.xml (which defines the modules via ../projA/trunk etc.) \_tags \_branches \_projA \_trunk \_tags \_branches \_projB \_trunk \_tags \_branches Is that recommended or is there a smarter way to do that? Is there any documentation regarding releasing module builds? Thanks Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Creating Development Environment Repository
Hi, You can use a repository manager to do that e.g. Nexus: http://nexus.sonatype.org/ or http://archiva.apache.org/. We use Nexus so I can only talk about Nexus here. Configure repository groups there and all your repository references (e.g. in the parent poms) should point to the Nexus. hth Stefan rohan chauhan wrote: Hi all, I want to create a maven repository in our organization. Which can work in following manner. All developers first check from our organization repository first. If file is there then they download it to their location.So no need to go on Maven public repository. But if in case file is not available in our organization repository then it is downloaded form Maven public repository and stored in organization's repository. And that file is then transfer to appropriate needed user. So that nest time when any of the developer needs that file it will available. I want above facility. Can u give me information about how to create this kind of repository. 1)Which tool needed to develop this repository. 2)What change needed in Maven to configure this development environment. 3)How to configure that tool for Maven Thank you all Do not follow where the path may lead. Go instead where there is no path and leave a trail ! ! ! * Learn to enjoy every minute of your life. Be happy now. Don't wait for something outside of yourself to make you happy in the future. Think how really precious is the time you have to spend, whether it's at work or with your family. Every minute should be enjoyed and savored by forgetting problems. * - My Thought Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SCM URL resolution/calculation by Maven
Hi all, I want to avoid putting a SCM configuration in every pom. For modules in a module build I found out that maven adds the artifact-id to the module-parent-pom's scm url . I was not able to find any information about the rules of scm URL resolution. What are the rules for SCM URL calculation/resolution? What are my options to define generic scm urls in a parent pom maybe with placeholders for artifactID and groupID? What if my svn structure doesn't 100% match groupID/artifactID (e.g. groupID=com.mycomp -- com/mycomp/ArtifactID)? Thanks Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SCM URL resolution/calculation by Maven
Ok, I tried to test that:
In my parent pom I have defined:
properties
...
urlPattern${groupId}/${artifactId}/urlPattern
/properties
scm
connectionscm:svn:https://myserver/${urlPattern}/trunk/connection
connectionscm:svn:https://myserver/${urlPattern}/trunk/connection
/scm
In my project I have defined this as the parent and added no additional
SCM configuration.
Maven just adds the artifactID to the URL but the project uses
trunk/tags/branches directories.
/groupID/artifactID/trunk/pom.xml
/groupID/artifactID/tags
/groupID/artifactID/branches
Maven resolves the URL to
https://myserver/groupID/artifactID/trunk/artifactID.
It seems that as soon as I want to adhere to the trunk/tags/branches
structure (which I need for the release process) the SCM resolution is
not usable.
Correct or is there a recognizeTrunkTagsBranches switch somewhere? ;-)
Thanks
Stefan
Brett Porter wrote:
On 14/10/2008, at 6:38 PM, Stefan Fritz wrote:
Hi all,
I want to avoid putting a SCM configuration in every pom.
For modules in a module build I found out that maven adds the
artifact-id to the module-parent-pom's scm url .
I was not able to find any information about the rules of scm URL
resolution.
What are the rules for SCM URL calculation/resolution?
They are as you've said.
What are my options to define generic scm urls in a parent pom maybe
with placeholders for artifactID and groupID?
What if my svn structure doesn't 100% match groupID/artifactID (e.g.
groupID=com.mycomp -- com/mycomp/ArtifactID)?
At present there's no facility to do this, so you need to redefine
them correctly for the POMs that don't match the convention.
- Brett
Thanks
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
-
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]
Dependency range resolution resolves to SNAPSHOTS!?
Hi all, We recently (during the last weeks) ran into a situation where version ranges (e.g. [1.0,) ) where resolved to SNAPSHOT versions as well. My understanding was always that if I specify a non-snapshot version in a range that only released version will be resolved. Is my understanding incorrect or is there a bug in dependency resolution? I'm using 2.0.9 Thanks Stefan PS: Sorry if this has already discussed during the last weeks but couldn't find it in the archives - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Best practice for branching projects?
Hi Simone, Thanks a lot haven't thought about ranges for this but now it seems to be the obvious solution :-) I still might have a challenge when I have multiple branches of one artifact (e.g. 1.0-patch-customer1, 1.0-patch-customer2) but in all the other cases it should solve my problem. Regards Stefan Simone Gianni wrote: Hi Stefan, I don't know if I got the problem right and if this could be a solution, but I do as follows (obviously, we are talking about maven branching, not SVN or CVS branching, which is another story) : - setup a developers only maven repository - setup a production only maven repository - use range versions instead of fixed ones .. This means that instead of having a dependency on artifact com.yourcompany:artifact:1.0.0 you have a dependency on com.yourcompany:artifact any version 1.0.0 - when a subproject is buggy, a team (or single developer, or whatever) will start working on it - they will build it on their own computers (in their local repository), so no problem with them testing their own work - they will occasionally deploy it TO THE DEV ONLY repository .. deploying it there, will let the other teams use the new artifact and test that their own work is correct related to the new bugfixes/refactorings and so on .. obviously, when they deploy, they should increment the minor version/revision, but only on that project specific pom (for example 1.0.0-r1 1.0.0-r2 or 1.0.1 1.0.2 etc...) - when the bugs have been fixed, the deploy can be made on the production only maven repository - from there, a complete build and test of the application can be done, and final release (war, jars or whatever) created to send to customers This way, every project can have its own lifecycle, its own releases, and probably its own SVN branches and so on. While using fixed version dependencies is a good practice when linking to something outside your control (artifacts on the main repo), for internal dependencies (artifacts produced inside your company/team) it is a maintenance nightmare and most of the time useless, cause you know when a new version will break compatibility and can adjust versioning only when that happens. Using SNAPSHOTS can save a bit of time making the change the version when sending to other developers step not necessary, but I think that it should be avoided when there is a high number of developers : that step can potentially break the build and stop other developers' work if the new package breaks compatibility when it should not or introduces more bugs than the previous one (which obviously happens :) ), and having also these internal releases versioned is IMHO more time-saving than using automagic snapshot updates. Hope this helps, Simone Stefan Fritz wrote: Hi, We use Maven in an environment where we have ca. 150 projects. One project is the toplevel project (= the final deliverable to the customer/user). This project has dependencies to 10 projects, which have dependencies to other projects etc. In the end we have 150 different projects in the dependency hierachy. The challange now is what happens if in one of the projects on the lowest level is bug. This means we have to branch from our released version to work on a patch and then release the patched version. From my understanding the only way to do that is to branch all projects which depend on the buggy project. And the same has to be done for all levels up to toplevel project. Most low level components are referenced by multiple projects and therefore a patch-branch would afect ca. 30 projects :-( As you can imagine this can end up in a nightmare of manual steps and/or scripting. Therefore I hope anybody has a better approach to that. Is there a simple way to do that? Any automation in Maven? Any best practices? Thanks 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]
Best practice for branching projects?
Hi, We use Maven in an environment where we have ca. 150 projects. One project is the toplevel project (= the final deliverable to the customer/user). This project has dependencies to 10 projects, which have dependencies to other projects etc. In the end we have 150 different projects in the dependency hierachy. The challange now is what happens if in one of the projects on the lowest level is bug. This means we have to branch from our released version to work on a patch and then release the patched version. From my understanding the only way to do that is to branch all projects which depend on the buggy project. And the same has to be done for all levels up to toplevel project. Most low level components are referenced by multiple projects and therefore a patch-branch would afect ca. 30 projects :-( As you can imagine this can end up in a nightmare of manual steps and/or scripting. Therefore I hope anybody has a better approach to that. Is there a simple way to do that? Any automation in Maven? Any best practices? Thanks Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Best practice for branching projects?
Thanks for the reply. Unfortunately we need this kind of granularity and therefore we have to live with the 150 projects :-( No project has more than 3 direct dependencies. Although in the end the complete dependency tree consists of all 150 projects. The basic concept of releasing Maven artifacts (to modify the pom.xml and work on snapshots) is clear to me. ;-) My question was whether there is a magic button which I can press to branch all dependent projects or a best practice approach that worked already in a similar environment. Thanks Stefan 陈思淼 wrote: It's not good you use all the 150 project in a large project. some of the project should be idependent project if it don't have much real relative to other project. other project use dependeces to dependon it. if you have a branch project should under bugfix developement. for example the last version is 1.1, now the new developing version should 1.2-SNAPSHOT. after you finish you development, you modified all the pom.xml which dependent on the fixed version. 2008/10/6 Stefan Fritz [EMAIL PROTECTED] Hi, We use Maven in an environment where we have ca. 150 projects. One project is the toplevel project (= the final deliverable to the customer/user). This project has dependencies to 10 projects, which have dependencies to other projects etc. In the end we have 150 different projects in the dependency hierachy. The challange now is what happens if in one of the projects on the lowest level is bug. This means we have to branch from our released version to work on a patch and then release the patched version. From my understanding the only way to do that is to branch all projects which depend on the buggy project. And the same has to be done for all levels up to toplevel project. Most low level components are referenced by multiple projects and therefore a patch-branch would afect ca. 30 projects :-( As you can imagine this can end up in a nightmare of manual steps and/or scripting. Therefore I hope anybody has a better approach to that. Is there a simple way to do that? Any automation in Maven? Any best practices? Thanks 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]
Maven 2.x Plug-in for Eclipse- internal repositories
Hi all, When I try to add a new dependency in Eclipse, it searches my local repository and the remote Maven repositories but not our internal (remote) repositories. I have configured our internal repositories in the parent pom.xml: repository !-- internal snapshot repository -- idinhouse_snapshot/id nameInhouse Snapshot Repository/name urlscp://myserver/data/maven/repositories/inhouse_snapshot/url releases enabledfalse/enabled /releases snapshots enabledtrue/enabled updatePolicyalways/updatePolicy /snapshots /repository The credentials for scp are defined in my settings.xml. The repositories work with the mvn command line. Does the Maven 2.x Plug-in for Eclipse support searching internal repositories? Regards Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help needed to setup Continuum and Maven 2
I have these files on the server. Why do I get a NullpointerException and no real log mesage? Thanks Stefan Gautham Pamu wrote: Hi You have modules defined in your pom.xml file so it is searching for these files. Do you also have services/pom.xml file on the myserver.com website. Even copy these files on the server. Downloading http://myserver.com/svn/trunk/sonic/src/esb/services/pom.xml?content-type=tex/plain Thanks Gautham Pamu On 3/31/06, Stefan Fritz [EMAIL PROTECTED] wrote: Hi, I try to setup Continuum 1.0.2 on a Linux server. cid:part1.01010605.07040609@gmx.at I have added Maven 2.0.3 to my path export MAVEN_HOME=/data/maven/maven export M2_HOME=/data/maven/maven PATH=$MAVEN_HOME/bin:$M2_HOME/bin:$PATH I copied my settings.xml to ~/.m2/settings.xml -- correct? My pom.xml is in SVN. When I try to add my pom to Continuum with the following URL: http://myserver.com/svn/trunk/sonic/src/pom.xml?content-type=tex/plain I get the: Cannot build maven project from /tmp/continuum-1364.tmp. Check the logs for more details. /tmp/continuum-1364.tmp contains my pom.xml I attached my pom.xml, my settings.xm and the wrapper.log Did I miss something important or is that a bug? Thanks for any advice ;-) Regards Stefan -- -Gautham Pamu
[m2] Continuum HowTo?
Hi all, is ther a step by step HowTo for setting up Continuum with Maven 2? I want to setup Continuum on a Linux box for nightly builds. My projects are in SVN. Regards Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] mvn 2.0.3 eclipse:eclipse not working anymore
Ooops, sorry the problem was a type in one of my root pom files (a few levels up/down). Now it works :-) Stefan Thorsten Heit wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Stefan, My pom is valid and has no duplicate tags! Seems to be a problem with plexus. Any inpput welcome! ;-) Hm, strange, on my machine everything works fine as it did with Maven 2.0.2. Before I restarted a new full build of my project, I cleaned my local repository cache and everything that was downloaded from ibiblio.org on my Maven proxy. Perhaps you should give this a try...? HTH Thorsten -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (MingW32) iD8DBQFEKoVRQvObkgCcDe0RAse2AKDTnaR7U7wFxI0/GKrgH/Q2+FAuKQCaAspk 3I3awn3LMGhbx2NQE5GJz3s= =tuy7 -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]
[m2] mvn 2.0.3 eclipse:eclipse not working anymore
Hi, I'm running maven 2.0.3. I have created a new project and wanted to enable eclipse support with eclipse:eclispe but I get the following error: C:\dev\trunk\connectmvn -e eclipse:eclipse + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: sonic.dev:esb POM Location: C:\dev\trunk\connect\pom.xml Reason: Parse error reading POM. Reason: Duplicated tag: 'artifactId' (position: START_TAG seen ... /version\r\n\t\t\t\tartifactId... @39:17) [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Parse error reading POM. Reason: Duplicated tag: ' artifactId' (position: START_TAG seen .../version\r\n\t\t\t\tartifactId... @39:17) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.InvalidProjectModelException: Parse error reading POM. Reason: D uplicated tag: 'artifactId' (position: START_TAG seen .../version\r\n\t\t\t\tartifactId... @39:1 7) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder. java:1290) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder. java:1250) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBu ilder.java:1067) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBu ilder.java:1155) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBu ilder.java:1155) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuil der.java:672) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMa venProjectBuilder.java:414) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java :190) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) ... 11 more Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: Duplicated tag: 'artifactId' (p osition: START_TAG seen .../version\r\n\t\t\t\tartifactId... @39:17) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parsePlugin(MavenXpp3Reader.java:2865) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseBuild(MavenXpp3Reader.java:753) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2224) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4422) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder. java:1286) ... 21 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Mar 29 09:35:10 CEST 2006 [INFO] Final Memory: 1M/2M [INFO] My pom is valid and has no duplicate tags! Seems to be a problem with plexus. Any inpput welcome! ;-) Cheers Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] eclipse:add-maven-repo fails if pom.xml is in execution directory
Hi all, the eclipse plugin seems to have a similar problme as the archetype plugin. It fails if the command is executed in a directory with a pom.xml file: C:\dev\trunk\mvn eclipse:add-maven-repo -Declipse.workspace=C:\dev\work\test [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: sonic.dev:esb POM Location: C:\dev\trunk\sonic\src\pom.xml Reason: Parse error reading POM. Reason: Duplicated tag: 'artifactId' (position: START_TAG seen ... /version\r\n\t\t\t\tartifactId... @34:17) [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Parse error reading POM. Reason: Duplicated tag: ' artifactId' (position: START_TAG seen .../version\r\n\t\t\t\tartifactId... @34:17) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.InvalidProjectModelException: Parse error reading POM. Reason: D uplicated tag: 'artifactId' (position: START_TAG seen .../version\r\n\t\t\t\tartifactId... @34:1 7) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder. java:1290) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder. java:1250) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBu ilder.java:1067) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBu ilder.java:1155) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuil der.java:672) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMa venProjectBuilder.java:414) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java :190) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) ... 11 more Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: Duplicated tag: 'artifactId' (p osition: START_TAG seen .../version\r\n\t\t\t\tartifactId... @34:17) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parsePlugin(MavenXpp3Reader.java:2865) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseBuild(MavenXpp3Reader.java:753) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2224) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4422) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder. java:1286) ... 20 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Mar 29 08:40:42 CEST 2006 [INFO] Final Memory: 1M/2M [INFO] Is this a known issue? Regards Stefan PS: The pom is valid and has no duplicate tags!! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2]using archetypes in a hierarchical project/pom structure
Brett, will the fixes be in m2 2.0.3? Does anybody know when 2.0.3 will be released? Cheers Stefan Brett Porter wrote: No, it has to be a snapshot. Sorry, I don't have any other suggestions for you at the moment. The code will receive some more testing and polish this week before the next release. - Brett On 3/21/06, Stefan Fritz [EMAIL PROTECTED] wrote: I did what you suggested but I still get the error. In the pom of the archetypes I saw the version is a snapshot version. Might that be the problem? Regards Stefan Brett Porter wrote: svn co http://svn.apache.org/repos/asf/maven/archetype/trunk mvn install Cheers, Brett On 3/21/06, Stefan Fritz [EMAIL PROTECTED] wrote: What do I have to get from SVN to get this fix? The Maven 2.1-SNAPSHOT or just a few plugins? Regards Stefan Brett Porter wrote: Fixed in SVN just today. - Brett On 3/21/06, Stefan Fritz [EMAIL PROTECTED] wrote: Hi, I created a custom archetype. I have a hierarchical project structure: pom.xml | `-- services `-- pom.xml `-- service1 `-- pom.xml `-- service2 `-- pom.xml `-- service3 `-- pom.xml What I want to do is to create a new service under the services folder. I opened a command prompt in the services directory to create service4 structure: mvn archetype:create -DarchetypeGroupId=other.maven.archetypes -DarchetypeArtifactId=mybasicservice -DarchetypeVersion=1.0-SNAPSHOT -DgroupId=services -DartifactId=service4 Then I get the following problem: [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\dev\services\service4\pom.xml'. So it seems the archtype looks for the pom.xml which it should create. Any tips what I can do to be able to create new projects wiht my archtype even if there is a parent pom available? 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] - 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]using archetypes in a hierarchical project/pom structure
Brett, If it is unrelated, should I be able to use the latest archtype snapshot if I add the following to my pom.xml? I downloaded the latest source of the archtype plugin. mvn compile mvn install added the following to my pom.xml: plugin artifactIdmaven-archetype-plugin/artifactId version0.7-SNAPSHOT/version /plugin Tried to create a new archtype (parent pom.xml in the execution directory): C:\dev\trunk\sonic\src\esb\servicesmvn -e archetype:create -DarchetypeGroupId=other.maven.archetype s -DarchetypeArtifactId=sonicbasic -DarchetypeVersion=1.0-SNAPSHOT -DgroupId=sonic.esb.services -Dar tifactId=MyESBService + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\dev\trunk\sonic\src\esb\services\MyESBService\pom.xml'. [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file 'C:\dev\trunk\sonic\ src\esb\services\MyESBService\pom.xml'. at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.ProjectBuildingException: Could not find the model file 'C:\dev\ trunk\sonic\src\esb\services\MyESBService\pom.xml'. at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder. java:1098) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProje ctBuilder.java:289) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java :274) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:491) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) ... 11 more Caused by: java.io.FileNotFoundException: C:\dev\trunk\sonic\src\esb\services\MyESBService\pom.xml ( The system cannot find the path specified) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:106) at java.io.FileReader.init(FileReader.java:55) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder. java:1093) ... 17 more [INFO] [INFO] Total time: 1 second [INFO] Finished at: Mon Mar 27 16:31:15 CEST 2006 [INFO] Final Memory: 1M/2M [INFO] Did I forget anything? Regards Stefan Brett Porter wrote: JUnit 4 support may be in surefire plugin 2.2, which is also separate. It's not yet determined if it will be included - there is a patch there to be tested. POJO, Junit3 and TestNG are correctly supported. - Brett On 3/27/06, Franz Fehringer [EMAIL PROTECTED] wrote: Thanks. Another question: will junit4 be supported in 2.0.3? Greetings Franz Brett Porter schrieb: Development on 2.1 has not begun in earnest yet. Our focus has been on a stable 2.0.3 and set of plugins. - Brett On 3/27/06, Franz Fehringer [EMAIL PROTECTED] wrote: Is there already a release plan/date for 2.1? I consider the use of 2.0.3 but would wait for 2.1 if it arrived in the next two/three weeks or so. Greetings Franz Brett Porter schrieb: 2.0.3 is due tomorrow. This fix is unrelated, and will be a part of an upcoming archetype plugin release. - Brett On 3/27/06, Stefan Fritz [EMAIL PROTECTED] wrote: Brett, will the fixes be in m2 2.0.3? Does anybody know when 2.0.3 will be released? Cheers Stefan Brett Porter wrote: No, it has to be a snapshot. Sorry, I don't have any other suggestions for you at the moment. The code will receive some more
Re: Maven 2 : Jalopy plugin
Teh following works for me:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjalopy-maven-plugin/artifactId
!--version1.0-SNAPSHOT/version--
configuration
!-- convention default:
$basedir/src/main/resources/jalopy.xml--
conventionc:/dev/var/configurations/jalopy.xml/convention
/configuration
executions
execution
idformat-main-src/id
!--phasecompile/phase--
phaseprocess-sources/phase
configuration
!--outputFile${project.build.directory}/checkstyle-result.xml/outputFile--
/configuration
goals
goalformat/goal
/goals
/execution
/executions
/plugin
HTH
Stefan
SiD tourment wrote:
Hey,
I just installed Maven 2 from http://maven.apache.org/
I want to use the Maven Jalopy Plugin, I followed this link :
http://mojo.codehaus.org/jalopy-maven-plugin/howto.html
I tried to add, in my pom.xml :
project
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdmaven-jalopy-plugin/artifactId
version1.0-SNAPSHOT/version
/plugin
/plugins
/build
/project
project
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjalopy-maven-plugin/artifactId
version1.0-SNAPSHOT/version
/plugin
/plugins
/build
/project
But, always the same error :
D:\Documents and Settings\sid\totomvn site
[INFO] Scanning for projects...
[INFO] -
---
[INFO] Building Maven Quick Start Archetype
[INFO]task-segment: [site]
[INFO] -
---
[INFO] -
---
[ERROR] BUILD ERROR
[INFO] -
---
[INFO] Failed to resolve artifact.
GroupId: org.codehaus.mojo
ArtifactId: jalopy-maven-plugin
Version: 1.0-SNAPSHOT
Reason: Unable to download the artifact from any repository
org.codehaus.mojo:jalopy-maven-plugin:pom:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO] -
---
[INFO] For more information, run Maven with the -e switch
[INFO] -
---
[INFO] Total time: 1 second
[INFO] Finished at: Tue Mar 21 12:26:31 CET 2006
[INFO] Final Memory: 1M/4M
[INFO] -
---
Someone can help me ?
Thanks.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2]using archetypes in a hierarchical project/pom structure
Hi, I created a custom archetype. I have a hierarchical project structure: pom.xml | `-- services `-- pom.xml `-- service1 `-- pom.xml `-- service2 `-- pom.xml `-- service3 `-- pom.xml What I want to do is to create a new service under the services folder. I opened a command prompt in the services directory to create service4 structure: mvn archetype:create -DarchetypeGroupId=other.maven.archetypes -DarchetypeArtifactId=mybasicservice -DarchetypeVersion=1.0-SNAPSHOT -DgroupId=services -DartifactId=service4 Then I get the following problem: [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\dev\services\service4\pom.xml'. So it seems the archtype looks for the pom.xml which it should create. Any tips what I can do to be able to create new projects wiht my archtype even if there is a parent pom available? regards Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2]using archetypes in a hierarchical project/pom structure
I did what you suggested but I still get the error. In the pom of the archetypes I saw the version is a snapshot version. Might that be the problem? Regards Stefan Brett Porter wrote: svn co http://svn.apache.org/repos/asf/maven/archetype/trunk mvn install Cheers, Brett On 3/21/06, Stefan Fritz [EMAIL PROTECTED] wrote: What do I have to get from SVN to get this fix? The Maven 2.1-SNAPSHOT or just a few plugins? Regards Stefan Brett Porter wrote: Fixed in SVN just today. - Brett On 3/21/06, Stefan Fritz [EMAIL PROTECTED] wrote: Hi, I created a custom archetype. I have a hierarchical project structure: pom.xml | `-- services `-- pom.xml `-- service1 `-- pom.xml `-- service2 `-- pom.xml `-- service3 `-- pom.xml What I want to do is to create a new service under the services folder. I opened a command prompt in the services directory to create service4 structure: mvn archetype:create -DarchetypeGroupId=other.maven.archetypes -DarchetypeArtifactId=mybasicservice -DarchetypeVersion=1.0-SNAPSHOT -DgroupId=services -DartifactId=service4 Then I get the following problem: [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file 'C:\dev\services\service4\pom.xml'. So it seems the archtype looks for the pom.xml which it should create. Any tips what I can do to be able to create new projects wiht my archtype even if there is a parent pom available? 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2.0.2 SVN ChangeLog
Javed, I have the same problem as you had. If I add the -Dusername and -Dpassword to the mvn command changelog works. I also tried to add username and password properties to the profile but it didn't wokr for me. Did you have success? Regards Stefan javed mandary wrote: The thing is that i dont want to have to type the parameters for svn authentication each time i want to run mvn site . Isnt there a way to store authentication information inside the settings.xmlfile for svn ? regards, Javed On 2/13/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: If you have an anonymous access to your svn, they don't required. If you need them, try the followings parameters to command line : -Dusername=your_username -Dpassword=your_password Emmanuel javed mandary a écrit : Hi All, regarding the changelog and developer activity reports generated , where do you specify the username and password used to access the SCM - SVN ? is that in the settings.xml ... any one has an example? Right now my reports are being generated but without being able to indentify any commits watsoever. regards, Javed - 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] release plugin fails tagging SVN via http
Hi, I just tried the release plugin. When I issue a mvn release:prepare command I get an error. (see error at the bottom) For my scm connection I have configuread a server entry in my settigns file which is correctly used by changelog plugin. so the scm url and the username/password are correct. In the access_log files of my svn server I can see that the release plugin is not using the username/password from the settings.xml file and is using my windows username instead. Is there a way to tell the release plugin the username/password for the tagging? Regards Stefan [INFO] Tagging release with the label my-1.0. Provider message: The svn tag command failed. Command output: svn: PROPFIND request failed on '/svn/tags/sonic/my-1.0' svn: PROPFIND of '/svn/tags/sonic/my-1.0': authorization failed (http://myserer.com) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error is occurred in the tag process. Embedded error: Error! [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred in the tag process. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycl eExecutor.java:485) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor. java:455) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultL ifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleE xecutor.java:216) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java :139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: An error is occurred in the tag process. at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(PrepareReleaseMojo.java:14 14) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:246) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor .java:531) ... 16 more Caused by: org.apache.maven.scm.ScmException: Error! at org.apache.maven.plugins.release.helpers.ScmHelper.checkResult(ScmHelper.java:124) at org.apache.maven.plugins.release.helpers.ScmHelper.tag(ScmHelper.java:226) at org.apache.maven.plugins.release.PrepareReleaseMojo.tagRelease(PrepareReleaseMojo.java:14 10) ... 19 more - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] SCM url: ${groupId} alternative with slashes instead of .
Hi all,
I try to build pom's for my projects and do not want to specify the url
manually for every pom.
My pom.xml:
...
groupIdtest.applications/groupId
artifactIdmyapp/artifactId
...
...scm ...
urlhttp://myserver.com/svn/${groupId
http://myserver.com/svn/$%7BgroupId }/${artifactId}//url
/scm
What I get is http://myserver.com/svn/test.application/myapp/
http://myserver.com/svn/test.application/myapp/ but waht I want is
http://myserver.com/svn/test/application/myapp/
http://myserver.com/svn/test/application/myapp/ (slashes instead of
dots in the groupId).
Is that possible or do I have to do it manually for every pom I have?
Regards
Stefan
RE: [m2] SCM url: ${groupId} alternative with slashes instead of .
I know I could define properties, but I don't want to define it.
I have a hierarchical project/pom structure and want to add this entry in my
root pom and do not want to touch it in every project pom.
That's why I wanted to use the artefactId and the groupId but that doesn't work
because of the dots in the groupID.
So if there would be a replaceDotsWithSlashes( ${groupId} )
Function or another approach that would be great ;-)
Stefan
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 14, 2006 1:45 PM
To: Maven Users List
Subject: Re: [m2] SCM url: ${groupId} alternative with slashes instead of .
It isn't possible, you must define it manually?
You can define test/application as a property of your pom and use it in your
scm url
Emmanuel
Stefan Fritz a écrit :
Hi all,
I try to build pom's for my projects and do not want to specify the url
manually for every pom.
My pom.xml:
...
groupIdtest.applications/groupId
artifactIdmyapp/artifactId
...
...scm ...
urlhttp://myserver.com/svn/${groupId
http://myserver.com/svn/$%7BgroupId }/${artifactId}//url
/scm
What I get is http://myserver.com/svn/test.application/myapp/
http://myserver.com/svn/test.application/myapp/ but waht I want is
http://myserver.com/svn/test/application/myapp/
http://myserver.com/svn/test/application/myapp/ (slashes instead of
dots in the groupId).
Is that possible or do I have to do it manually for every pom I have?
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]
[m2] PMD plugin, ClassNotFoundException
Hi all, I tried to add the PMD plugin to my reports section in the pom.xml. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId configuration rulesets rulesetC:\dev\var\configurations\pmd\rulesets\basic.xml/ruleset /rulesets formatxml/format linkXreftrue/linkXref sourceEncodingutf-8/sourceEncoding minimumTokens100/minimumTokens targetJdk1.4/targetJdk /configuration /plugin When I generate my site I get the following error: [INFO] Generate PMD Report report. java.lang.ClassNotFoundException: net.sourceforge.pmd.rules.UnnecessaryConversionTemporaryRule at java.net.URLClassLoader$1.run(URLClassLoader.java:199) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) Does anybody know what I have to do to fix this issue? Regards Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Jalopy Plugin?
Hi all, ist there already a Jalopy plugin for maven 2? I found http://mojo.codehaus.org/jalopy-maven-plugin/howto.html But it doesn't seem to work: [INFO] The plugin 'org.codehaus.mojo:maven-jalopy-plugin' does not exist or no valid version could be found TIA Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Jalopy Plugin?
Thanks Jurgen, can you tell me what I've to do, to tell maven to download it from this location? Or do I have to build it manually? Stefan -Original Message- From: Jurgen Lust [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 25, 2006 11:26 AM To: Maven Users List Subject: Re: [m2] Jalopy Plugin? It hasn't been released on the central repository yet. You can check it out of subversion though, it works perfectly... https://svn.mojo.codehaus.org/mojo/trunk/mojo/jalopy-maven-plugin Jurgen Stefan Fritz schreef: Hi all, ist there already a Jalopy plugin for maven 2? I found http://mojo.codehaus.org/jalopy-maven-plugin/howto.html But it doesn't seem to work: [INFO] The plugin 'org.codehaus.mojo:maven-jalopy-plugin' does not exist or no valid version could be found TIA Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Among flowers, the cherry blossom. Among men, me. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Jalopy Plugin?
Sorry I'm a newbie: I compiled it and it installed in my local repository. My pom: ... plugin groupIdorg.codehaus.mojo/groupId artifactIdmaven-jalopy-plugin/artifactId version1.0b11/version /plugin ... mvn site [INFO] Scanning for projects... [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [site] [INFO] Downloading: http://repo1.maven.org/maven2/org/codehaus/mojo/maven-jalopy-plugin/1.0b 11/maven-jalopy -plugin-1.0b11.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) Downloading: http://repo1.maven.org/maven2/org/codehaus/mojo/maven-jalopy-plugin/1.0b 11/maven-jalopy -plugin-1.0b11.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.codehaus.mojo ArtifactId: maven-jalopy-plugin Version: 1.0b11 Reason: Unable to download the artifact from any repository org.codehaus.mojo:maven-jalopy-plugin:pom:1.0b11 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Wed Jan 25 11:45:13 CET 2006 [INFO] Final Memory: 3M/5M [INFO] Another tip ? :-) Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Jalopy Plugin?
I chaged it to version1.0-SNAPSHOT/version but it still fails. I think it doesn't look in the local repository first. Do I have to tell maven to look first in my internal repository? Where? C:\dev\esb\services\myservicemvn site [INFO] Scanning for projects... [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [site] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.codehaus.mojo ArtifactId: maven-jalopy-plugin Version: 1.0-SNAPSHOT Reason: Unable to download the artifact from any repository org.codehaus.mojo:maven-jalopy-plugin:pom:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Jan 25 12:41:21 CET 2006 [INFO] Final Memory: 3M/5M [INFO] -Original Message- From: Jurgen Lust [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 25, 2006 11:52 AM To: Maven Users List Subject: Re: [m2] Jalopy Plugin? Stefan Fritz schreef: Sorry I'm a newbie: I compiled it and it installed in my local repository. My pom: ... plugin groupIdorg.codehaus.mojo/groupId artifactIdmaven-jalopy-plugin/artifactId version1.0b11/version /plugin ... You are confusing the jalopy version with the jalopy plugin version. I believe the plugin version should be 1.0-SNAPSHOT (just look in the pom of the plugin) Jurgen -- Among flowers, the cherry blossom. Among men, me. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Jalopy Plugin?
THANKS! :-D From: Jurgen Lust [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 25, 2006 12:57 PM To: Maven Users List Subject: Re: [m2] Jalopy Plugin? Aha, the artifactId is jalopy-maven-plugin, not maven-jalopy-plugin... Jurgen Stefan Fritz schreef: I chaged it to version1.0-SNAPSHOT/version but it still fails. I think it doesn't look in the local repository first. Do I have to tell maven to look first in my internal repository? Where? C:\dev\esb\services\myservicemvn site [INFO] Scanning for projects... [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [site] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.codehaus.mojo ArtifactId: maven-jalopy-plugin Version: 1.0-SNAPSHOT Reason: Unable to download the artifact from any repository org.codehaus.mojo:maven-jalopy-plugin:pom:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Jan 25 12:41:21 CET 2006 [INFO] Final Memory: 3M/5M [INFO] -Original Message- From: Jurgen Lust [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 25, 2006 11:52 AM To: Maven Users List Subject: Re: [m2] Jalopy Plugin? Stefan Fritz schreef: Sorry I'm a newbie: I compiled it and it installed in my local repository. My pom: ... plugin groupIdorg.codehaus.mojo/groupId artifactIdmaven-jalopy-plugin/artifactId version1.0b11/version /plugin ... You are confusing the jalopy version with the jalopy plugin version. I believe the plugin version should be 1.0-SNAPSHOT (just look in the pom of the plugin) Jurgen -- Among flowers, the cherry blossom. Among men, me.
RE: [m2] Jalopy Checkstyle compatible configuraiton files
Hi all, I got Jalopy and Checkstyle running but now I wonder whether anybody can tell where I can get configuration files for Jalopy and Checkstyle which adhere to the same coding convention e.g: sun coding convention. Regards Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] failed to deploy to server via HTTP
Hi all, I try to setup maven 2.0.2 for my team. I have a webserver (apache) which I want to use as our internal repository release/snapshot. In my parent pom.xml I added the following entries: distributionManagement repository idinhouse/id nameInhouse Internal Release Repository/name urlhttp://myserver/maven/inhouse/url /repository snapshotRepository idinhouse_snapshot/id nameInhouse Internal Snapshot Repository/name urlhttp://myserver/maven/inhouse_snapshot/url uniqueVersiontrue/uniqueVersion /snapshotRepository /distributionManagement But when I run 'mvn deploy' I get the following error: C:\devmvn deploy [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Unnamed - com.progress.chat:dev:pom:1.0 [INFO] Unnamed - com.progress.chat.dev:esb:pom:1.0 [INFO] Unnamed - com.progress.chat.dev.esb:services:pom:1.0 [INFO] [INFO] Building Unnamed - com.progress.chat:dev:pom:1.0 [INFO]task-segment: [deploy] [INFO] [INFO] Skipping missing optional mojo: org.apache.maven.plugins:maven-site-plugin:attach-descriptor [INFO] [install:install] [INFO] Installing C:\dev\pom.xml to C:\dev\var\local-repository\com\progress\chat\dev\1.0\dev-1.0.po m [INFO] [deploy:deploy] Uploading: http://myserver/maven/inhouse/com/progress/chat/dev/1.0/dev-1.0.pom 1K uploaded [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unable to transfer file. HttpURLConnection returned the response co de: 405 [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Jan 24 14:58:48 CET 2006 [INFO] Final Memory: 3M/6M [INFO] C:\dev Do I need any special apache settings to be able to upload files with maven/wagon? Regards Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Wagon fails with HTTP destination
Hi all, I try to setup maven 2.0.2 for my team. I have a webserver (apache) which I want to use as our internal repository release/snapshot. In my parent pom.xml I added the following entries: distributionManagement repository idinhouse/id nameInhouse Internal Release Repository/name urlhttp://myserver/maven/inhouse/url /repository snapshotRepository idinhouse_snapshot/id nameInhouse Internal Snapshot Repository/name urlhttp://myserver/maven/inhouse_snapshot/url uniqueVersiontrue/uniqueVersion /snapshotRepository /distributionManagement But when I run 'mvn deploy' I get the following error: C:\devmvn deploy [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Unnamed - com.progress.chat:dev:pom:1.0 [INFO] Unnamed - com.progress.chat.dev:esb:pom:1.0 [INFO] Unnamed - com.progress.chat.dev.esb:services:pom:1.0 [INFO] [INFO] Building Unnamed - com.progress.chat:dev:pom:1.0 [INFO]task-segment: [deploy] [INFO] [INFO] Skipping missing optional mojo: org.apache.maven.plugins:maven-site-plugin:attach-descriptor [INFO] [install:install] [INFO] Installing C:\dev\pom.xml to C:\dev\var\local-repository\com\progress\chat\dev\1.0\dev-1.0.po m [INFO] [deploy:deploy] Uploading: http://myserver/maven/inhouse/com/progress/chat/dev/1.0/dev-1.0.pom 1K uploaded [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Unable to transfer file. HttpURLConnection returned the response co de: 405 [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Jan 24 14:58:48 CET 2006 [INFO] Final Memory: 3M/6M [INFO] C:\dev Do I need any special apache settings to be able to upload files with maven/wagon? Regards Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] Wagon fails with HTTP destination
Yes I'm following this guide but instead of using scp I tried http. It seems nobody has ever tried http. I think I'll try FTP as I was not able to get it working with HTTP. :-( -Original Message- From: Treloar, Barrie (SAPOL) [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 25, 2006 6:51 AM To: 'Maven Users List' Subject: RE: [m2] Wagon fails with HTTP destination distributionManagement repository idinhouse/id nameInhouse Internal Release Repository/name urlhttp://myserver/maven/inhouse/url /repository snapshotRepository idinhouse_snapshot/id nameInhouse Internal Snapshot Repository/name urlhttp://myserver/maven/inhouse_snapshot/url uniqueVersiontrue/uniqueVersion /snapshotRepository /distributionManagement But when I run 'mvn deploy' I get the following error: I know it works via scp. I doubt http worked unless wagon was doing WebDAV stuff, in which case you would have had to setup that in apache. Err, are you following the guide I am writing at nment ?? Let me know if I need to make changes. - 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] Need some direction for my first Maven steps
Hi, I read the getting started guide on the Maven website and searched through the mail archives but I still have no die how to achieve what I'm looking for: What I'd like to do: - Create a central Maven repository in our company. - Have a Super POM which includes our company wide defaults (e.g: force checkstyle, link toour central bug reporting tool) all our project POMs should get the defaults from this pom. - create a custom archtype Open questions: Do I need anything apart from an HTTP/FTP server for the central repository? Will the default repository be overridden if I name our repository location central? Where do I have to place the pom with our defaults? Can anybody send me a sample for a company wide super pom? The Guide to creating Archtypes states that the archtype descriptor should be places into src/main/resources/META-INF/. Which src directory is referred to here? I hope some of the gurus out there can give me some hints or a link to a detailed tutorial for Maven2. Regards Stefan
