release plugin 2.0-beta-5
Hi all, If I visit the site of Maven Release Plugin I can see the following goals: Goals Overview * release:clean Clean up after a release preparation. * release:perform Perform a release from SCM * release:prepare Prepare for a release in SCM. * release:rollback Rollback a previous relase. When I try to use roolback I get the following error: Required goal not found It seems that the site is aligned to version 2.0-beta-5 against the code (in ibiblio repository) to version 2.0-beta-4. Is this true ? Where can I find the BETA-5 code ??? Thanks in advance -- View this message in context: http://www.nabble.com/release-plugin-2.0-beta-5-tf3636799s177.html#a10155454 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem in packaging multiple directories
Yes I got the solution. I modified POM.xml ( tag) to take the sources from required location. Thanks & Regards Ramesh Babu.P -Original Message- From: Ramesh Babu Pokala - TLS, Chennai Sent: Tuesday, April 24, 2007 10:32 AM To: Maven Users List Subject: RE: Problem in packaging multiple directories Hi, One small query: my-app > |-- pom.xml > `-- src >-- main > `-- java > `-- package1 > `-- package2 > `-- package3 > | `-- App.java > `-- package4 > `-- MyClass.java Is that main/java mandotory in package structure...? Can I have src/package1/package2/.. Instead of src/main/java/package1/package2/..? If I don't have main/java, maven -e compile goal saying no sources to compile. Thanks & Regards Ramesh Babu.P -Original Message- From: Tim Kettler [mailto:[EMAIL PROTECTED] Sent: Monday, April 23, 2007 7:53 PM To: Maven Users List Subject: RE: Problem in packaging multiple directories Hi, There only ever is one 'pom.xml' per project. The project structure below really shows all essential file needed. I suggest you set up a simple test project up-to the point where you can successfully compile and package it and then venture on from this starting point. The test project would have one 'pom.xml' in it's root directory and a 'src/main/java' directory containing the java classes and packages. Once you have that up and running you can extend you example like described in Point III. from my last mail. What you will have then is a working multi-module project (I don't know if that's the official term but it's what I'm calling it). And again like in the example for the simple (one-module) project all relevant files are shown in my last mail. One point I think you are confused with is the difference between a multi-module (aggregation) project and pom inheritance (parent pom). In a multi-module project there is no parent pom involved per se. You just have a set of (concrete) projects where the actual code is compiled and one or more aggregation projects (with a packaging of type pom) that _aggregate_ the build of the concrete projects via the tag in the pom. No parent poms involved here. A parent pom is something analogue to a superclass in java it captures portions of common configuration. For example if you have multiple projects depending on the same library, you could create a parent pom which declares that library as a dependency and let all projects needing that library inherit from the parent pom via the tag. -Tim Am Montag, den 23.04.2007, 18:40 +0530 schrieb Ramesh Babu Pokala - TLS, Chennai: > Thanks for your response. > I am following the following structure as u mentioned > > my-app > |-- pom.xml > `-- src >-- main > `-- java > `-- package1 > `-- package2 > `-- package3 > | `-- App.java > `-- package4 > `-- MyClass.java > > > Then what should be my parent POM.xml? > How many poms I need. Do I need poms for package3 as well as package4 > along with main pom? > ` > > Thanks & Regards > Ramesh Babu.P > > -Original Message- > From: Tim Kettler [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 21, 2007 11:42 PM > To: Maven Users List > Subject: Re: Problem in packaging multiple directories > > Hi, > > I. Maven Directory Layout > > If you follow the 'Getting Started Guide' you should have a directory > structure like the one below: > > my-app > |-- pom.xml > `-- src > |-- main > | `-- java > | `-- package1 > | `-- package2 > | `-- package3 > | | `-- App.java > | `-- package4 > | `-- MyClass.java > `-- test > `-- java > `-- packakag1 > `-- package2 > `-- package3 > `-- AppTest.java > > This is the default layout maven expects. If you are not converting > from a legacy project and absolutely need a different directory layout > you should stick to this default. That will save you from much hassle. > > If you really can't follow that proposed structure, you have to > override the maven default values in the pom (see [1], [2] and [3] for > a complete description of the pom). > > For example, to override the default source directory you would have > something like this in your pom: > > > ... > > > my/non/standard/source/directory > ... > > ... > > > > II. Multiple Source Directories Per Project > > Maven has a one-set-of-sources-per-project philosophy so if you really > need multiple source directories you are somewhat working against the > spirit of maven. Instead you should organize
Re: Problem in packaging multiple directories
Maven2 requires Java source code to be in: my-app/src/main/java You can change some settings in the pom so your source directory is app/src/java for example, but you'll need to figure this out on your own -- its documented on the Maven site. I suggest you don't head down the path of changing all these values if you want to keep your sanity. Wayne On 4/24/07, Ramesh Babu Pokala - TLS, Chennai <[EMAIL PROTECTED]> wrote: Hi, One small query: my-app > |-- pom.xml > `-- src >-- main > `-- java > `-- package1 > `-- package2 > `-- package3 > | `-- App.java > `-- package4 > `-- MyClass.java Is that main/java mandotory in package structure...? Can I have src/package1/package2/.. Instead of src/main/java/package1/package2/..? If I don't have main/java, maven -e compile goal saying no sources to compile. Thanks & Regards Ramesh Babu.P -Original Message- From: Tim Kettler [mailto:[EMAIL PROTECTED] Sent: Monday, April 23, 2007 7:53 PM To: Maven Users List Subject: RE: Problem in packaging multiple directories Hi, There only ever is one 'pom.xml' per project. The project structure below really shows all essential file needed. I suggest you set up a simple test project up-to the point where you can successfully compile and package it and then venture on from this starting point. The test project would have one 'pom.xml' in it's root directory and a 'src/main/java' directory containing the java classes and packages. Once you have that up and running you can extend you example like described in Point III. from my last mail. What you will have then is a working multi-module project (I don't know if that's the official term but it's what I'm calling it). And again like in the example for the simple (one-module) project all relevant files are shown in my last mail. One point I think you are confused with is the difference between a multi-module (aggregation) project and pom inheritance (parent pom). In a multi-module project there is no parent pom involved per se. You just have a set of (concrete) projects where the actual code is compiled and one or more aggregation projects (with a packaging of type pom) that _aggregate_ the build of the concrete projects via the tag in the pom. No parent poms involved here. A parent pom is something analogue to a superclass in java it captures portions of common configuration. For example if you have multiple projects depending on the same library, you could create a parent pom which declares that library as a dependency and let all projects needing that library inherit from the parent pom via the tag. -Tim Am Montag, den 23.04.2007, 18:40 +0530 schrieb Ramesh Babu Pokala - TLS, Chennai: > Thanks for your response. > I am following the following structure as u mentioned > > my-app > |-- pom.xml > `-- src >-- main > `-- java > `-- package1 > `-- package2 > `-- package3 > | `-- App.java > `-- package4 > `-- MyClass.java > > > Then what should be my parent POM.xml? > How many poms I need. Do I need poms for package3 as well as package4 > along with main pom? > ` > > Thanks & Regards > Ramesh Babu.P > > -Original Message- > From: Tim Kettler [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 21, 2007 11:42 PM > To: Maven Users List > Subject: Re: Problem in packaging multiple directories > > Hi, > > I. Maven Directory Layout > > If you follow the 'Getting Started Guide' you should have a directory > structure like the one below: > > my-app > |-- pom.xml > `-- src > |-- main > | `-- java > | `-- package1 > | `-- package2 > | `-- package3 > | | `-- App.java > | `-- package4 > | `-- MyClass.java > `-- test > `-- java > `-- packakag1 > `-- package2 > `-- package3 > `-- AppTest.java > > This is the default layout maven expects. If you are not converting > from a legacy project and absolutely need a different directory layout > you should stick to this default. That will save you from much hassle. > > If you really can't follow that proposed structure, you have to > override the maven default values in the pom (see [1], [2] and [3] for > a complete description of the pom). > > For example, to override the default source directory you would have > something like this in your pom: > > > ... > > > my/non/standard/source/directory > ... > > ... > > > > II. Multiple Source Directories Per Project > > Maven has a one-set-of-sources-per-project philosophy so if you really > need multiple source directories you are somew
RE: Problem in packaging multiple directories
Hi, One small query: my-app > |-- pom.xml > `-- src >-- main > `-- java > `-- package1 > `-- package2 > `-- package3 > | `-- App.java > `-- package4 > `-- MyClass.java Is that main/java mandotory in package structure...? Can I have src/package1/package2/.. Instead of src/main/java/package1/package2/..? If I don't have main/java, maven -e compile goal saying no sources to compile. Thanks & Regards Ramesh Babu.P -Original Message- From: Tim Kettler [mailto:[EMAIL PROTECTED] Sent: Monday, April 23, 2007 7:53 PM To: Maven Users List Subject: RE: Problem in packaging multiple directories Hi, There only ever is one 'pom.xml' per project. The project structure below really shows all essential file needed. I suggest you set up a simple test project up-to the point where you can successfully compile and package it and then venture on from this starting point. The test project would have one 'pom.xml' in it's root directory and a 'src/main/java' directory containing the java classes and packages. Once you have that up and running you can extend you example like described in Point III. from my last mail. What you will have then is a working multi-module project (I don't know if that's the official term but it's what I'm calling it). And again like in the example for the simple (one-module) project all relevant files are shown in my last mail. One point I think you are confused with is the difference between a multi-module (aggregation) project and pom inheritance (parent pom). In a multi-module project there is no parent pom involved per se. You just have a set of (concrete) projects where the actual code is compiled and one or more aggregation projects (with a packaging of type pom) that _aggregate_ the build of the concrete projects via the tag in the pom. No parent poms involved here. A parent pom is something analogue to a superclass in java it captures portions of common configuration. For example if you have multiple projects depending on the same library, you could create a parent pom which declares that library as a dependency and let all projects needing that library inherit from the parent pom via the tag. -Tim Am Montag, den 23.04.2007, 18:40 +0530 schrieb Ramesh Babu Pokala - TLS, Chennai: > Thanks for your response. > I am following the following structure as u mentioned > > my-app > |-- pom.xml > `-- src >-- main > `-- java > `-- package1 > `-- package2 > `-- package3 > | `-- App.java > `-- package4 > `-- MyClass.java > > > Then what should be my parent POM.xml? > How many poms I need. Do I need poms for package3 as well as package4 > along with main pom? > ` > > Thanks & Regards > Ramesh Babu.P > > -Original Message- > From: Tim Kettler [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 21, 2007 11:42 PM > To: Maven Users List > Subject: Re: Problem in packaging multiple directories > > Hi, > > I. Maven Directory Layout > > If you follow the 'Getting Started Guide' you should have a directory > structure like the one below: > > my-app > |-- pom.xml > `-- src > |-- main > | `-- java > | `-- package1 > | `-- package2 > | `-- package3 > | | `-- App.java > | `-- package4 > | `-- MyClass.java > `-- test > `-- java > `-- packakag1 > `-- package2 > `-- package3 > `-- AppTest.java > > This is the default layout maven expects. If you are not converting > from a legacy project and absolutely need a different directory layout > you should stick to this default. That will save you from much hassle. > > If you really can't follow that proposed structure, you have to > override the maven default values in the pom (see [1], [2] and [3] for > a complete description of the pom). > > For example, to override the default source directory you would have > something like this in your pom: > > > ... > > > my/non/standard/source/directory > ... > > ... > > > > II. Multiple Source Directories Per Project > > Maven has a one-set-of-sources-per-project philosophy so if you really > need multiple source directories you are somewhat working against the > spirit of maven. Instead you should organize your project in multiple > modules (see below) and make them depend on each other. > > If you really need to have more than one set of sources in a single > project you can attach an additional source directory using the > build-helper-maven-plugin [4]. > > > III. Multi-Module Projects > > Multi-Module proje
"Some inter-plug-in dependencies have not been satisfied." error when building eclipse RCP App.
Hi All, The following errors are coming while trying to build Eclipse RCP Application using pde-maven-plugin. I have not at all used the plugins those are listed as missing in the log below. But it is asking these plugin. What might be the problem...any gusses? * LOG D:\CIATool_New\Workbench>mvn -e install + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [INFO] Building Simple Product PDE Example [INFO]task-segment: [install] [INFO] [INFO] [pde:ext] [INFO] java -classpath D:\eclipse\startup.jar org.eclipse.core.launcher.Main -application org.eclipse.ant.core.antRunner -buildfi le D:\eclipse\plugins\org.eclipse.pde.build_3.2.0.v20060603\scripts\product Build\productBuild.xml -Dbuilder=D:\CIATool_New\Workbe nch\buildConfiguration -DbuildDirectory=D:\CIATool_New\Workbench\..\.. -DbuildTempFolder=D:\CIATool_New\Workbench\target\pdeTemp -DjavacFailOnError=true Buildfile: D:\eclipse\plugins\org.eclipse.pde.build_3.2.0.v20060603\scripts\product Build\productBuild.xml main: preBuild: preSetup: checkLocalMaps: getMapFiles: [concat] No existing files and no nested text, doing nothing postSetup: checkLocalBase: getBaseComponents: generateFeature: [eclipse.generateFeature] An error occured while generating manifest for D:\CIATool_New\Workbench\..\... [eclipse.generateFeature] Could not read: file:D:/CIATool_New/Workbench/../../features/org.eclipse.pde.build.conta iner.feature/fe ature.xml. fetch: generateFeature: [eclipse.generateFeature] An error occured while generating manifest for D:\CIATool_New\Workbench\..\... [eclipse.generateFeature] Some inter-plug-in dependencies have not been satisfied. [eclipse.generateFeature] Bundle org.eclipse.jdt.source.macosx.carbon.ppc: [eclipse.generateFeature] Host plug-in org.eclipse.jdt.source_3.2.1.r321_v20060905-R4CM1Znkvre9wC- has not been found. [eclipse.generateFeature] Bundle org.eclipse.platform.source.hpux.motif.PA_RISC: [eclipse.generateFeature] Host plug-in org.eclipse.platform.source_3.2.1.r321_v20060921-b_XVA-INSQSyMtx has not been found. [eclipse.generateFeature] Bundle org.eclipse.platform.source.linux.gtk.ppc: [eclipse.generateFeature] Host plug-in org.eclipse.platform.source_3.2.1.r321_v20060921-b_XVA-INSQSyMtx has not been found. [eclipse.generateFeature] Bundle org.eclipse.platform.source.linux.gtk.x86: [eclipse.generateFeature] Host plug-in org.eclipse.platform.source_3.2.1.r321_v20060921-b_XVA-INSQSyMtx has not been found. [eclipse.generateFeature] Bundle org.eclipse.platform.source.linux.gtk.x86_64: [eclipse.generateFeature] Host plug-in org.eclipse.platform.source_3.2.1.r321_v20060921-b_XVA-INSQSyMtx has not been found. [eclipse.generateFeature] Bundle org.eclipse.platform.source.linux.motif.x86: [eclipse.generateFeature] Host plug-in org.eclipse.platform.source_3.2.1.r321_v20060921-b_XVA-INSQSyMtx has not been found. [eclipse.generateFeature] Bundle org.eclipse.platform.source.macosx.carbon.ppc: [eclipse.generateFeature] Host plug-in org.eclipse.platform.source_3.2.1.r321_v20060921-b_XVA-INSQSyMtx has not been found. [eclipse.generateFeature] Bundle org.eclipse.platform.source.win32.win32.x86: [eclipse.generateFeature] Another singleton version selected: org.eclipse.platform.source.win32.win32.x86_3.2.1.r321_v20060 921-b_XVA-INSQSyMtx [eclipse.generateFeature] Bundle org.eclipse.platform.source.win32.win32.x86: [eclipse.generateFeature] Host plug-in org.eclipse.platform.source_3.2.1.r321_v20060921-b_XVA-INSQSyMtx has not been found. [eclipse.generateFeature] Bundle org.eclipse.rcp.source.aix.motif.ppc: [eclipse.generateFeature] Host plug-in org.eclipse.rcp.source_3.2.1.r321_v20060801-2ekW2BxmcpPUOoq has not been found. [eclipse.generateFeature] Bundle org.eclipse.rcp.source.hpux.motif.PA_RISC: [eclipse.generateFeature] Host plug-in org.eclipse.rcp.source_3.2.1.r321_v20060801-2ekW2BxmcpPUOoq has not been found. [eclipse.generateFeature] Bundle org.eclipse.rcp.source.linux.gtk.ppc: [eclipse.generateFeature] Host plug-in org.eclipse.rcp.source_3.2.1.r321_v20060801-2ekW2BxmcpPUOoq has not been found. [eclipse.generateFeature] Bundle org.eclipse.rcp.source.linux.gtk.x86: [eclipse.generateFeature] Host plug-in org.eclipse.rcp.source_3.2.1.r321_v20060801-2ekW2BxmcpPUOoq has not been found. [eclipse.generateFeature] Bundle org.eclipse.rcp.source.linux.gtk.x86_64: [eclipse.generateFeature] Host plug-in org.eclipse.rcp.source_3.2.1.r321_v20060801-2ekW2BxmcpPUOoq has not been found. [eclipse.generateFeature] Bundle org.eclipse.rcp.source.linux.motif.x86: [eclipse.generateFeature] Host plug-in org.eclipse.rcp.source_3.2.1.r321_v20060801-2ekW2BxmcpPUOoq has not been found. [eclipse.generateFeature] Bundle org.ecli
Re: Quality level attribute during version selection process?
Great thread - with a lot going on. A significant part of the discussion is about how to make sure one's overall Maven system is in a known state with known quality. That then brings up who establishes that quality and what is the governance around it and whether all that process will limit folks ability to work within the system. In an open source community I would not expect folks to jump into all that too willingly :-). But, in a corporate environment it is much more desirable and possibly required to govern how shared components reach certain levels of quality. In such an environment it is possible to establish quality states like ALPHA, BETA, RELEASE, etc., govern how components reach those levels of quality, and to then expect the version selection process to use those states. As I mentioned I modified the version selection process in our local Maven system to match a quality qualifier but I did have to leave the "standard" algorithm in place to support how Maven finds its own components (plugins). Ultimately the answer will probably to have the version selection process be plugable or otherwise extendable. Different software development lifecycles (open source vs. corporate for example) require different component selection processes depending on how they test and manage for quality. Wayne Fay wrote: > > This should give you a start... > http://www.nabble.com/Remove-auto-resolution-of-plugin-versions-from-Maven-2.1-tf3560617s177.html#a10144515 > > Wayne > > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> Sorry to be a NewB, I'm having trouble finding the @dev discussion. >> >> A couple weeks back I downloaded and modified the 2.0.6 source to do what >> I >> need. It was nothing too complicated but since it is core code and a >> fundamental shift in how folks expect version selection to work, I can >> understand the resistance to change in that area. >> >> >> Wayne Fay wrote: >> > >> > You'll need to read the thread on dev@ to see how people have >> > responded thus far. But based on the initial response, I just don't >> > see it happening. >> > >> > Admittedly, this issue hasn't had a terribly thorough discussion etc >> > so feel free to take that on if you are seriously interested. I just >> > think its going to be a seriously uphill battle to make this happen in >> > the forseeable future. >> > >> > Wayne >> > >> > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> >> >> So, what would it take to get this sort of thing in place? It's not >> such >> >> a >> >> futuristic need - some of the big budget SCM tools allow for the >> >> component >> >> query to include a quality level and indeed Ivy allows for this as >> well. >> >> Is >> >> the reasoning in the Maven community that this is not necessary or >> that >> >> it >> >> can be accomplished in other ways? >> >> Thanks >> >> >> >> >> >> Wayne Fay wrote: >> >> > >> >> > is certainly not currently available. And I doubt it will >> >> > be available at any time in the future. It was simply a suggestion >> >> > from a user on the dev@ list. >> >> > >> >> > This is like seeing a movie on Sci Fi channel about flying cars and >> >> > asking GM where you can buy one. ;-) >> >> > >> >> > Wayne >> >> > >> >> > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> I saw a post recently that referred to a attribute being >> >> used >> >> >> during plugin resolution. The purpose of the attribute was to make >> >> sure >> >> >> that only "released" or "beta", etc. versions were selected rather >> >> than >> >> >> alpha or lower level qualtiy. >> >> >> >> >> >> As far as I can tell Maven doesn't use a quality level for version >> >> >> selection. There are version number qualifiers but that's >> different >> >> than >> >> >> using something like a attribute in conjuction with >> >> , >> >> >> etc. >> >> >> >> >> >> In any case, having something like is really important >> (at >> >> >> least >> >> >> to my company). Ivy does this and in fact allows users to set up >> >> their >> >> >> own >> >> >> set of ordered quality levels to choose from. >> >> >> >> >> >> So: am I missing something and Maven in fact does do quality level >> >> >> selection >> >> >> (I don't see it in the code). Or, is this something Maven can do >> in >> >> the >> >> >> future? >> >> >> >> >> >> Thanks >> >> >> -- >> >> >> View this message in context: >> >> >> >> >> >> http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10146036 >> >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> >> >> - >> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> >> >> >> > >> >> > >> - >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> > For additional commands, e-mai
Re: Maven with remote repositories on https servers
Hi, You can set the username and password either in your $M2_HOME/conf/settings.xml or in ${user.dir}/.m2/settings.xml For more info about this, please see: http://maven.apache.org/settings.html Thanks, Deng [EMAIL PROTECTED] wrote: Hi Everyone, Can someone tell me how do i get Maven to connect to a windows https: remote server. Can I pass the username and password? Thanks, David !DSPAM:602,462ce87616831855215190! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Quality level attribute during version selection process?
This should give you a start... http://www.nabble.com/Remove-auto-resolution-of-plugin-versions-from-Maven-2.1-tf3560617s177.html#a10144515 Wayne On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: Sorry to be a NewB, I'm having trouble finding the @dev discussion. A couple weeks back I downloaded and modified the 2.0.6 source to do what I need. It was nothing too complicated but since it is core code and a fundamental shift in how folks expect version selection to work, I can understand the resistance to change in that area. Wayne Fay wrote: > > You'll need to read the thread on dev@ to see how people have > responded thus far. But based on the initial response, I just don't > see it happening. > > Admittedly, this issue hasn't had a terribly thorough discussion etc > so feel free to take that on if you are seriously interested. I just > think its going to be a seriously uphill battle to make this happen in > the forseeable future. > > Wayne > > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> So, what would it take to get this sort of thing in place? It's not such >> a >> futuristic need - some of the big budget SCM tools allow for the >> component >> query to include a quality level and indeed Ivy allows for this as well. >> Is >> the reasoning in the Maven community that this is not necessary or that >> it >> can be accomplished in other ways? >> Thanks >> >> >> Wayne Fay wrote: >> > >> > is certainly not currently available. And I doubt it will >> > be available at any time in the future. It was simply a suggestion >> > from a user on the dev@ list. >> > >> > This is like seeing a movie on Sci Fi channel about flying cars and >> > asking GM where you can buy one. ;-) >> > >> > Wayne >> > >> > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> >> >> I saw a post recently that referred to a attribute being >> used >> >> during plugin resolution. The purpose of the attribute was to make >> sure >> >> that only "released" or "beta", etc. versions were selected rather >> than >> >> alpha or lower level qualtiy. >> >> >> >> As far as I can tell Maven doesn't use a quality level for version >> >> selection. There are version number qualifiers but that's different >> than >> >> using something like a attribute in conjuction with >> , >> >> etc. >> >> >> >> In any case, having something like is really important (at >> >> least >> >> to my company). Ivy does this and in fact allows users to set up >> their >> >> own >> >> set of ordered quality levels to choose from. >> >> >> >> So: am I missing something and Maven in fact does do quality level >> >> selection >> >> (I don't see it in the code). Or, is this something Maven can do in >> the >> >> future? >> >> >> >> Thanks >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10146036 >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> - >> >> 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] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10150722 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> 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] > > > -- View this message in context: http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10153097 Sent from the Maven - Users mailing list archive at Nabble.com. - 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: Quality level attribute during version selection process?
Sorry to be a NewB, I'm having trouble finding the @dev discussion. A couple weeks back I downloaded and modified the 2.0.6 source to do what I need. It was nothing too complicated but since it is core code and a fundamental shift in how folks expect version selection to work, I can understand the resistance to change in that area. Wayne Fay wrote: > > You'll need to read the thread on dev@ to see how people have > responded thus far. But based on the initial response, I just don't > see it happening. > > Admittedly, this issue hasn't had a terribly thorough discussion etc > so feel free to take that on if you are seriously interested. I just > think its going to be a seriously uphill battle to make this happen in > the forseeable future. > > Wayne > > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> So, what would it take to get this sort of thing in place? It's not such >> a >> futuristic need - some of the big budget SCM tools allow for the >> component >> query to include a quality level and indeed Ivy allows for this as well. >> Is >> the reasoning in the Maven community that this is not necessary or that >> it >> can be accomplished in other ways? >> Thanks >> >> >> Wayne Fay wrote: >> > >> > is certainly not currently available. And I doubt it will >> > be available at any time in the future. It was simply a suggestion >> > from a user on the dev@ list. >> > >> > This is like seeing a movie on Sci Fi channel about flying cars and >> > asking GM where you can buy one. ;-) >> > >> > Wayne >> > >> > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> >> >> I saw a post recently that referred to a attribute being >> used >> >> during plugin resolution. The purpose of the attribute was to make >> sure >> >> that only "released" or "beta", etc. versions were selected rather >> than >> >> alpha or lower level qualtiy. >> >> >> >> As far as I can tell Maven doesn't use a quality level for version >> >> selection. There are version number qualifiers but that's different >> than >> >> using something like a attribute in conjuction with >> , >> >> etc. >> >> >> >> In any case, having something like is really important (at >> >> least >> >> to my company). Ivy does this and in fact allows users to set up >> their >> >> own >> >> set of ordered quality levels to choose from. >> >> >> >> So: am I missing something and Maven in fact does do quality level >> >> selection >> >> (I don't see it in the code). Or, is this something Maven can do in >> the >> >> future? >> >> >> >> Thanks >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10146036 >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> - >> >> 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] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10150722 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> 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] > > > -- View this message in context: http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10153097 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] cobertura-maven-plugin specify: '-Dinstrumentation=VALUE'
I checked the user@ archive and sure enough, this is a bug in the documentation -- you must wrap the nodes insides . Same with and I assume . Wayne On 4/23/07, Wayne Fay <[EMAIL PROTECTED]> wrote: Any reason you're using 2.0 instead of 2.1? Give it a try and see if it works any better. Also, perhaps try wrapping your ignore node(s) inside an ignores node: ... Wayne On 4/22/07, Adrian Herscu <[EMAIL PROTECTED]> wrote: > Hi all, > > I am using the cobertura-maven-plugin 2.0 and I want to make it ignore > the classes in some package, so I am specifying: > > > org.foo.* > > > This causes the build to fail with the following message: > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to configure plugin parameters for: > org.codehaus.mojo:cobertura-maven-plugin:2.0 > > on the command line, specify: '-Dinstrumentation=VALUE' > > Cause: Cannot find setter nor field in > org.codehaus.mojo.cobertura.configuration.ConfigInstrumentation for 'ignore' > > Adrian. > > > - > 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] cobertura-maven-plugin specify: '-Dinstrumentation=VALUE'
Any reason you're using 2.0 instead of 2.1? Give it a try and see if it works any better. Also, perhaps try wrapping your ignore node(s) inside an ignores node: ... Wayne On 4/22/07, Adrian Herscu <[EMAIL PROTECTED]> wrote: Hi all, I am using the cobertura-maven-plugin 2.0 and I want to make it ignore the classes in some package, so I am specifying: org.foo.* This causes the build to fail with the following message: [ERROR] BUILD ERROR [INFO] [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:cobertura-maven-plugin:2.0 on the command line, specify: '-Dinstrumentation=VALUE' Cause: Cannot find setter nor field in org.codehaus.mojo.cobertura.configuration.ConfigInstrumentation for 'ignore' Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-assembly-plugin: doesn't work from a reactor build
Are you sure Assembly is finding the assembly.xml you've specified during the reactor build? I know paths specified in child pom plugins sometimes don't work as expected during reactor builds, etc. As a test, rename the assembly.xml file to .blah and run from child. If the assembly plugin "looks" the same as when executed from the parent directory, I'd assume this is what's going on. Wayne On 4/23/07, Graham Leggett <[EMAIL PROTECTED]> wrote: Hi all, I have an assembly linked into the mvn build lifecycle like below using the "attached" goal. When mvn install is run from the assembly artifact, the assembly is built correctly. If however mvn install is run from the root pom (ie a reactor build), the assembly plugin goes through the motions, but the assembly created is empty. Does the "attached" goal work in multi-module / reactor builds? maven-assembly-plugin 2.2-beta-1 assembly.xml make-assembly package attached Regards, Graham -- - 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]
Moving and artifact
Hi, If in addition to publishing an artifact to a repository I wanted to move the artifact to a remote server after the build which plugin would be best suited for this? Thanks Larry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Simple example for maven 2 release goals?
Yes and yes, plus longer questions are less likely to be answered than shorter ones. Also it feels like you haven't done all of your own homework on these issues, so rather than trying things out and then asking for specific help with things when you're stuck, you're just throwing it out there to the world and hoping someone will help you in general. Finally, its not entirely clear what you are looking for. Even after reading the email in its entirety, I'm not entirely sure what kind of response you want/need other than "working examples of everything I need". This is not a great way to use this list, it seems. Wayne On 4/23/07, Baz <[EMAIL PROTECTED]> wrote: Is the question too general or too open ended? On 4/22/07, Baz <[EMAIL PROTECTED]> wrote: > All, > > I would like to obtain simple instructions of incoroperating the use > of release goals in my build system that consists of CruiseControl or > Continuum and Maven 2. I have read the pages in > http://maven.apache.org/plugins/maven-release-plugin/ and > understanding that could simplify my life but still not exactly how to > use it. I wonder if someone can give me some sort of working example > and templates. > > Here are the things that I would like to do: > > Environment: > 1. Perforce. > 2. Continuum/CruiseControl. > 3. Maven 2. > 4. Windows OS. > > Build types: > > 1.Continuous builds. > - Build tree resides in build machine itself. > - Maven 2 site generation. > - External webpages point directly to the generated pages within the > build tree for reports. > - P4 labelling? Not necessary. > - Archiving? Not necessary. > - Version: SNAPSHOT. > > 2. Nightly/Daily builds. > - Build tree build in build machine, then archive into file share location. > - Maven 2 site generation. > - External webpages point to the generated pages build tree that > reside in the archive file share location. I am assuming that we > keeping 7 days of daily builds. Builds are overwritting each others. > - P4 labelling? Yes. > - Archiving? Yes. > - Version: I dont know what is the best practice here? I dont want to > use snapshot and I would like to use time stamp as part of the file > name, is it possible? For example, package-070102.*. > > 3. Ad-hoc/release builds. > - Build tree build in build machine, then archive into file share location. > - Maven 2 site generation. > - External webpages point to the generated pages build tree that > reside in the archive file share location. I am assuming that we keep > 30 builds. > - P4 labelling? Yes. > - Archiving? Yes. > - Version: dont know what is the best practice here? I dont want to > use snapshot and I would like to use time stamp as part of the file > name, is it possible? For example, package-070102.*. > > Thank you and please comment. > > A. > - 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: Quality level attribute during version selection process?
You'll need to read the thread on dev@ to see how people have responded thus far. But based on the initial response, I just don't see it happening. Admittedly, this issue hasn't had a terribly thorough discussion etc so feel free to take that on if you are seriously interested. I just think its going to be a seriously uphill battle to make this happen in the forseeable future. Wayne On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: So, what would it take to get this sort of thing in place? It's not such a futuristic need - some of the big budget SCM tools allow for the component query to include a quality level and indeed Ivy allows for this as well. Is the reasoning in the Maven community that this is not necessary or that it can be accomplished in other ways? Thanks Wayne Fay wrote: > > is certainly not currently available. And I doubt it will > be available at any time in the future. It was simply a suggestion > from a user on the dev@ list. > > This is like seeing a movie on Sci Fi channel about flying cars and > asking GM where you can buy one. ;-) > > Wayne > > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> I saw a post recently that referred to a attribute being used >> during plugin resolution. The purpose of the attribute was to make sure >> that only "released" or "beta", etc. versions were selected rather than >> alpha or lower level qualtiy. >> >> As far as I can tell Maven doesn't use a quality level for version >> selection. There are version number qualifiers but that's different than >> using something like a attribute in conjuction with , >> etc. >> >> In any case, having something like is really important (at >> least >> to my company). Ivy does this and in fact allows users to set up their >> own >> set of ordered quality levels to choose from. >> >> So: am I missing something and Maven in fact does do quality level >> selection >> (I don't see it in the code). Or, is this something Maven can do in the >> future? >> >> Thanks >> -- >> View this message in context: >> http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10146036 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> 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] > > > -- View this message in context: http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10150722 Sent from the Maven - Users mailing list archive at Nabble.com. - 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: Quality level attribute during version selection process?
So, what would it take to get this sort of thing in place? It's not such a futuristic need - some of the big budget SCM tools allow for the component query to include a quality level and indeed Ivy allows for this as well. Is the reasoning in the Maven community that this is not necessary or that it can be accomplished in other ways? Thanks Wayne Fay wrote: > > is certainly not currently available. And I doubt it will > be available at any time in the future. It was simply a suggestion > from a user on the dev@ list. > > This is like seeing a movie on Sci Fi channel about flying cars and > asking GM where you can buy one. ;-) > > Wayne > > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> I saw a post recently that referred to a attribute being used >> during plugin resolution. The purpose of the attribute was to make sure >> that only "released" or "beta", etc. versions were selected rather than >> alpha or lower level qualtiy. >> >> As far as I can tell Maven doesn't use a quality level for version >> selection. There are version number qualifiers but that's different than >> using something like a attribute in conjuction with , >> etc. >> >> In any case, having something like is really important (at >> least >> to my company). Ivy does this and in fact allows users to set up their >> own >> set of ordered quality levels to choose from. >> >> So: am I missing something and Maven in fact does do quality level >> selection >> (I don't see it in the code). Or, is this something Maven can do in the >> future? >> >> Thanks >> -- >> View this message in context: >> http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10146036 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> 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] > > > -- View this message in context: http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10150722 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Correct location for properies files
Yes. Thank you. That worked. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marcelo Colomer Cornejo Sent: Monday, April 23, 2007 3:30 PM To: Maven Users List Subject: RE: Correct location for properies files We put them into src/main/resources. The package goal copy them into Web-inf/classes. src/main/java target/${artifactId}-${version}/WEB-INF/classes src/main/resources target ${artifactId}-${version} war -Mensaje original- De: Holt, Jack C. [mailto:[EMAIL PROTECTED] Enviado el: lunes, 23 de abril de 2007 23:34 Para: users@maven.apache.org Asunto: Correct location for properies files Where is the correct location in the project directory tree for properties files? For instance, I am using a file I call message_en.properties that is used to contain the i18n messages that I want to access using resource bundles. In other words, it contains the English version of internationalized text. Currently, I'm putting them in my src/main/java directory and Eclipse is automatically copying them into the directory with my test app server needs them. However, maven doesn't seem to know where to put them on its own. - 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]
Accessing an execution id from pom
Is there a way I can access the current execution ID if I have multiple executions of a plugin? I have multiple executions of the surefire plugin, and I would like the output to go to a different directory for each execution. So in my plugin configuration I would like to have something like: |surefire-reports/${executionId}| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Correct location for properies files
We put them into src/main/resources. The package goal copy them into Web-inf/classes. src/main/java target/${artifactId}-${version}/WEB-INF/classes src/main/resources target ${artifactId}-${version} war -Mensaje original- De: Holt, Jack C. [mailto:[EMAIL PROTECTED] Enviado el: lunes, 23 de abril de 2007 23:34 Para: users@maven.apache.org Asunto: Correct location for properies files Where is the correct location in the project directory tree for properties files? For instance, I am using a file I call message_en.properties that is used to contain the i18n messages that I want to access using resource bundles. In other words, it contains the English version of internationalized text. Currently, I'm putting them in my src/main/java directory and Eclipse is automatically copying them into the directory with my test app server needs them. However, maven doesn't seem to know where to put them on its own. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Simple example for maven 2 release goals?
Is the question too general or too open ended? On 4/22/07, Baz <[EMAIL PROTECTED]> wrote: All, I would like to obtain simple instructions of incoroperating the use of release goals in my build system that consists of CruiseControl or Continuum and Maven 2. I have read the pages in http://maven.apache.org/plugins/maven-release-plugin/ and understanding that could simplify my life but still not exactly how to use it. I wonder if someone can give me some sort of working example and templates. Here are the things that I would like to do: Environment: 1. Perforce. 2. Continuum/CruiseControl. 3. Maven 2. 4. Windows OS. Build types: 1.Continuous builds. - Build tree resides in build machine itself. - Maven 2 site generation. - External webpages point directly to the generated pages within the build tree for reports. - P4 labelling? Not necessary. - Archiving? Not necessary. - Version: SNAPSHOT. 2. Nightly/Daily builds. - Build tree build in build machine, then archive into file share location. - Maven 2 site generation. - External webpages point to the generated pages build tree that reside in the archive file share location. I am assuming that we keeping 7 days of daily builds. Builds are overwritting each others. - P4 labelling? Yes. - Archiving? Yes. - Version: I dont know what is the best practice here? I dont want to use snapshot and I would like to use time stamp as part of the file name, is it possible? For example, package-070102.*. 3. Ad-hoc/release builds. - Build tree build in build machine, then archive into file share location. - Maven 2 site generation. - External webpages point to the generated pages build tree that reside in the archive file share location. I am assuming that we keep 30 builds. - P4 labelling? Yes. - Archiving? Yes. - Version: dont know what is the best practice here? I dont want to use snapshot and I would like to use time stamp as part of the file name, is it possible? For example, package-070102.*. Thank you and please comment. A. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Correct location for properies files
src/main/resources Add this path to your source folders in Eclipse, then both Eclipse and Maven will be happy with you. Holt, Jack C. wrote: Where is the correct location in the project directory tree for properties files? For instance, I am using a file I call message_en.properties that is used to contain the i18n messages that I want to access using resource bundles. In other words, it contains the English version of internationalized text. Currently, I'm putting them in my src/main/java directory and Eclipse is automatically copying them into the directory with my test app server needs them. However, maven doesn't seem to know where to put them on its own. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Correct location for properies files
Where is the correct location in the project directory tree for properties files? For instance, I am using a file I call message_en.properties that is used to contain the i18n messages that I want to access using resource bundles. In other words, it contains the English version of internationalized text. Currently, I'm putting them in my src/main/java directory and Eclipse is automatically copying them into the directory with my test app server needs them. However, maven doesn't seem to know where to put them on its own.
Re: Depending on snapshots
Yes, just use the unique version of the snapshot like you would do for a release version: 4.1.2-20070321.174345-38 Kalle On 4/23/07, Borut Bolčina <[EMAIL PROTECTED]> wrote: Hello, how can I use last known good snapshot, if the latest isn't working? Let's say a third party or in-house snapshot jar is downloaded to my local repo which brakes my application. If I don't want to use for example: tapestry-framework-4.1.2-SNAPSHOT.jar and instead want a few days older one tapestry-framework-4.1.2-20070321.174345-38.jar What should my dependency section look like? Is it possible to use jars based on date/time? Thanks, Borut
Re: LifecycleExecutionException: The packaging for this project did not assign a file to the build artifact
I'd like to preface my answer below with the small fact that we don't actually deploy our eclipse plugins in-house, and hence we had not encountered this issue at the time of writing the article. We have build machines that run Continuum and locally we all simply do "mvn clean install" on all our projects. We don't use deployment as we need to create all sorts of assemblies with our plugins so we orchestrate the process slightly differently. That being said, this is truly an issue with maven's deploy plugin. There is a hard-coded line in their Mojo, that checks to see if the packaging type of the project is "pom". If it is, the Mojo will deploy the artifact one way, and for anything else it expects a file (jar, war, etc.) associated with what it is deploying. A binary-plugin is really a kind-of "pom" packaging, in that it really has no code and thus no artifact file associated with it. This is also how it is defined in the components.xml file by giving it an extension of "pom". There are few ways to work around this if you really need to deploy and not install. You could modify the deploy mojo so that it understands a binary-plugin and then include your modified Mojo in the lifecycle defined for a binary-plugin in components.xml. We will also be revisiting our code now that we have given it to codehaus.org (under the m2eclipse project) and we will be sure to fix this issue in the near term. Michael Maven wrote: > > I'm trying to use the psteclipse plugin to generate my plugins. I've read > the Eclipse Corner Article and generated an example archetype project, > my-binary-plugin. I'm getting a LifecycleExecutionException: The > packaging for this project did not assign a file to the build artifact > exception out of the build. Here's the POM and build output below. Where > am I supposed to specify the missing name? When I specify the packaging > as 'jar' the deploy works. Also, the jar file with the correct plugin > Manafest is built in the target\pde-test directory. Is that all I can > expect/WAD? > > Best Regards, > Michael > > C:\Development\my-binary-plugin>mvn -e deploy > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] > - > --- > [INFO] Building my-binary-plugin > [INFO]task-segment: [deploy] > [INFO] > - > --- > [INFO] [psteclipse:update {execution: update}] > [INFO] Defaulting prefixes to the single prefix 'my-binary-plugin'. > [INFO] [psteclipse:testPackage {execution: test-package}] > [INFO] [site:attach-descriptor] > [INFO] [psteclipse:install] > [INFO] Installing C:\Development\my-binary-plugin\pom.xml to C:\Documents > and Se > ttings\user\.m2\repository\com\mycompany\app\my-binary-plugin\1.0-SNAPSHOT\my- > binary-plugin-1.0-SNAPSHOT.pom > [INFO] [deploy:deploy] > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] The packaging for this project did not assign a file to the build > artifac > t > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: The packaging for > this p > roject did not assign a file to the build artifact > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:564) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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.codeh
Test classpath
Under Maven v2.0.6, with Surefire plugin v2.3, the directory containing the .class files generated by the test-compile phase (${basedir}/target/test-classes/) is not included in java.class.path when I run "mvn test". (I got this info from the target/surefire-reports/TEST-.xml file for a failing test class.) This is a problem for me because one of my tests expects to be able to find the test .class files in the classpath, but can't under Maven 2, and so is failing. Under both Maven 1.1-beta-3 and IntelliJ IDEA, the generated test class files directory is included in java.class.path, so my test is succeeding. Is there anything I can do to change this? Explicitly including target/test-classes in the surefire plugin's configuration seems to have no effect. Thanks, Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Depending on snapshots
Hello, how can I use last known good snapshot, if the latest isn't working? Let's say a third party or in-house snapshot jar is downloaded to my local repo which brakes my application. If I don't want to use for example: tapestry-framework-4.1.2-SNAPSHOT.jar and instead want a few days older one tapestry-framework-4.1.2-20070321.174345-38.jar What should my dependency section look like? Is it possible to use jars based on date/time? Thanks, Borut
Re: Quality level attribute during version selection process?
is certainly not currently available. And I doubt it will be available at any time in the future. It was simply a suggestion from a user on the dev@ list. This is like seeing a movie on Sci Fi channel about flying cars and asking GM where you can buy one. ;-) Wayne On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: I saw a post recently that referred to a attribute being used during plugin resolution. The purpose of the attribute was to make sure that only "released" or "beta", etc. versions were selected rather than alpha or lower level qualtiy. As far as I can tell Maven doesn't use a quality level for version selection. There are version number qualifiers but that's different than using something like a attribute in conjuction with , etc. In any case, having something like is really important (at least to my company). Ivy does this and in fact allows users to set up their own set of ordered quality levels to choose from. So: am I missing something and Maven in fact does do quality level selection (I don't see it in the code). Or, is this something Maven can do in the future? Thanks -- View this message in context: http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10146036 Sent from the Maven - Users mailing list archive at Nabble.com. - 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]
Multi-Project Release and Version Numbering
Hi, I'm trying to work out using the release-plugin with a multi-project setup. All of my sub-projects refer to the parent project and inherit its version - not declaring one of their own. I use ${project.version} in my dependencies so that inter-project dependencies can refer to the current version of the other sub-projects, and so forth. I have two questions about doing the release: 1) The release:prepare always asks me for release and new snapshot versions for each sub-project. Is there not some way to make it only ask me for the parent and have that value propagate through the whole build? 2) It seems that the default new snapshot versions increments the minor version number automatically. This isn't the behavior that I want as we use the iteration number as our version number. This wouldn't be so bad if we didn't have to enter it for every sub-project. So, is there some way to change this behavior? Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Quality level attribute during version selection process?
I saw a post recently that referred to a attribute being used during plugin resolution. The purpose of the attribute was to make sure that only "released" or "beta", etc. versions were selected rather than alpha or lower level qualtiy. As far as I can tell Maven doesn't use a quality level for version selection. There are version number qualifiers but that's different than using something like a attribute in conjuction with , etc. In any case, having something like is really important (at least to my company). Ivy does this and in fact allows users to set up their own set of ordered quality levels to choose from. So: am I missing something and Maven in fact does do quality level selection (I don't see it in the code). Or, is this something Maven can do in the future? Thanks -- View this message in context: http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10146036 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Questions about surefire plugin
How do I change the log level of the surefire plugin? I would like to change the log level from DEBUG to INFO. If I have multiple execution IDs in my surefire configuration, is there a way to run just one of the executions? I could do it using profiles, but I was wondering if there is an easier way. Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Testing plugins
I am using the maven-plugin-testing-harness for general unit-testing of my plugins, but I find that I need something to test how I am processing dependencies. Does anybody have a good strategy for unit-testing behavior that depends on the dependencies? Thanks Liz [EMAIL PROTECTED]
Maven with remote repositories on https servers
Hi Everyone, Can someone tell me how do i get Maven to connect to a windows https: remote server. Can I pass the username and password? Thanks, David
Re: [m2] [WARNING] Removing: java from forked lifecycle, to prevent recursive invocation.
Hi Wayne, mvn -X looks like this (I think it's the relevant portion -- if you need the entire log please let me know): [INFO] Preparing exec:java [WARNING] Removing: java from forked lifecycle, to prevent recursive invocation. [INFO] No goals needed for project - skipping [DEBUG] org.acme.lang.compiler:acme-lang-compiler:jar:1.0-alpha-1-SNAPSHOT (selected for null) [DEBUG] org.acme.lang.decompiler:acme-lang-decompiler:jar:1.0-alpha-1-SNAPSHOT:test (selected for test) [DEBUG] junit:junit:jar:3.8.1:test (selected for test) [DEBUG] xmlunit:xmlunit:jar:1.0:test (selected for test) [DEBUG] commons-io:commons-io:jar:1.3.1:compile (selected for compile) [DEBUG] org.acme.samples:acme-samples:war:1.0-alpha-3-SNAPSHOT:test (selected for test) [DEBUG] antlr:antlr:jar:2.7.7:compile (selected for compile) [DEBUG] org.codehaus.mojo:exec-maven-plugin:maven-plugin:1.1-beta-1:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.ant:ant-parent::1.7.0 for project: org.apache.ant:ant:jar:1.7.0 from the repository. [DEBUG] org.apache.ant:ant:jar:1.7.0:compile (selected for compile) [DEBUG] Retrieving parent-POM: org.apache.ant:ant-parent::1.7.0 for project: org.apache.ant:ant-launcher:jar:1.7.0 from the repository. [DEBUG] org.apache.ant:ant-launcher:jar:1.7.0:compile (selected for compile) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9:runtime (selected for runtime) [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.1) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for project: null:maven-project:jar:2.0.4 from the repository. [DEBUG] Adding managed depedendencies for unknown:maven-project [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-7 [DEBUG] org.apache.maven.wagon:wagon-ssh-external:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-7 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-6 [DEBUG] org.apache.maven:maven-project:jar:2.0.4:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for project: null:maven-settings:jar:2.0.4 from the repository. [DEBUG] Adding managed depedendencies for unknown:maven-settings [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-7 [DEBUG] org.apache.maven.wagon:wagon-ssh-external:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-7 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-6 [DEBUG] org.apache.maven:maven-settings:jar:2.0.4:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for project: org.apache.maven:maven-model:jar:2.0.4 from the repository. [DEBUG] Adding managed depedendencies for org.apache.maven:maven-model [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-7 [DEBUG] org.apache.maven.wagon:wagon-ssh-external:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-7 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-6 [DEBUG] org.apache.maven:maven-model:jar:2.0.4:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for project: null:maven-profile:jar:2.0.4 from the repository. [DEBUG] Adding managed depedendencies for unknown:maven-profile [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1 [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-ssh:jar:1.0-alpha-7 [DEBUG] org.apache.maven.wagon:wagon-ssh-external:jar:1.0-alpha-6 [DEBUG] org.apache.maven.wagon:wagon-file:jar:1.0-alpha-7 [DEBUG] org.apache.maven.wagon:wagon-http-lightweight:jar:1.0-alpha-6 [DEBUG] org.apache.maven:maven-profile:jar:2.0.4:runtime (selected for runtime) [DEBUG] org.apache.maven:maven-model:jar:2.0.4:runtime (selected for runtime) [DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for project: org.apache.maven:maven-artifact-manager:jar:2.0.4 from the reposi
Re: Exception: Cannot checkout sources. 7
Yes it does work in the same server for the same user! and exactly the same configuration for maven. Wayne Fay wrote: > > Does it work from Maven on the same server, with the same user? > > Wayne > > On 4/23/07, monsterkhan <[EMAIL PROTECTED]> wrote: >> >> Thanks for the reply Wayne. This works in maven on commandline perfectly, >> its >> only after the maven/mks integration has matured have we moved on to >> Continuum. Any more valuable suggestions are welcome. >> >> >> >> Wayne Fay wrote: >> > >> > I'd make this SCM w/MKS work in Maven first, then worry about making >> > it work in Continuum. Or does it work fine in Maven (stand alone from >> > command line) but not Continuum? >> > >> > Wayne >> > >> > On 4/23/07, monsterkhan <[EMAIL PROTECTED]> wrote: >> >> >> >> That is something that I get in the failed build list on the front-end >> >> and >> >> not in the stack trace :) apologies for not making that clear in the >> >> first >> >> go. >> >> >> >> >> >> >> >> Emmanuel Venisse wrote: >> >> > >> >> > I don't see "Cannot checkout sources" messages in this stacktrace. >> >> > >> >> > Emmanuel >> >> > >> >> > monsterkhan a écrit : >> >> >> Hi Emmanuel, >> >> >>Well the stack trace doesnt look too helpful to me, what >> >> exactly I >> >> >> was looking for was the list of descriptions of different continuum >> >> >> exceptions as that might make it easy to analyse the causes of the >> >> >> exceptions. >> >> >> >> >> >> To the best of my guess theres some issue in the way I am giving >> the >> >> path >> >> >> to >> >> >> the SCM i.e MKS, But what exactly is the reason is beating me. If >> >> someone >> >> >> gets an idea from this please help :) >> >> >> >> >> >> Here is the relevant part of pom.xml config tht I think is causing >> the >> >> >> trouble. >> >> >> test-continuum >> >> >> jar >> >> >> 1.0-SNAPSHOT >> >> >> test-continuum >> >> >> http://maven.apache.org >> >> >> >> >> >> >> >> >> >> >> >> scm:mks|hostname="hostName"|port="1234"|username="XX"|password="something"|project=/repos/XYZ/ABC/test-continuum/project.pj|devpath=|revision= >> >> >> >> >> >> >> >> >> scm:mks|hostname="hostName"|port="1234"|username="XX"|password="something"|project=|devpath=|revision= >> >> >> >> >> hostName:port/repos/ABC/XYZ/test-continuum/project.pj >> >> >> >> >> >> >> >> >> And here is the stack trace... >> >> >> >> >> >> 23 09:09:18,716 [Thread-2] INFO ContinuumScm - >> >> >> Checking >> >> >> out project: 'test-continuum', id: '26' to >> >> >> >> >> >> 'C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\26'. >> >> >> INFO | jvm 3| 2007/04/23 09:09:18 | 2007-04-23 09:09:18,746 >> >> >> [SocketListener0-0] WARN SQL- Object >> with >> >> id >> >> >> "0" not found ! >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,536 >> >> >> [SocketListener0-1] WARN SQL- Object >> with >> >> id >> >> >> "0" not found ! >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,536 >> >> >> [SocketListener0-1] WARN ViewContextPopulator - Cannot >> find >> >> a >> >> >> value for the expression getProject(#id)in >> >> >> [EMAIL PROTECTED] >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,546 >> >> >> [SocketListener0-1] WARN SQL- Object >> with >> >> id >> >> >> "0" not found ! >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,546 >> >> >> [SocketListener0-1] WARN ViewContextPopulator - Cannot >> find >> >> a >> >> >> value for the expression getBuildResultsForProject(#id)in >> >> >> [EMAIL PROTECTED] >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,566 >> >> >> [SocketListener0-1] ERROR VelocityComponent - Method >> >> >> addPathInfo threw exception for reference $link in template >> >> >> screens/ProjectBuilds.vm at [14,26] >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,566 >> >> >> [SocketListener0-1] ERROR Renderer:velocity - Error >> >> >> rendering >> >> >> template: >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 | >> >> java.lang.NullPointerException >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> >> >> >> org.codehaus.plexus.summit.util.UriBuilder.addPathInfo(UriBuilder.java:263) >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> >> >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> >> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> java.lang.reflect.Method.invoke(Method.java:324) >> >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >>
RE: scm of maven
Have you tried this. mvn -e scm:checkout -DcheckoutDirectory=src/main/java -Dincludes=*.java -DscmVersion=My_Release_1_0 -DscmVersionType=branch -Dmaven.scm.provider.cvs.implementation=cvs_native -DconnectionUrl=scm:cvs:pserver:user_name:[EMAIL PROTECTED]:my_cvs_home_path:my_cvs_module_path The cvs_native forces it to use CVSNT location for login data. Otherwise maven looks in the user home and the .cvspass doesn't exist there, since CVSNT uses the registery. Cheers, Jim -Original Message- From: yi bo [mailto:[EMAIL PROTECTED] Sent: Monday, April 23, 2007 2:24 AM To: users@maven.apache.org Subject: scm of maven Hey, all. I can't for the life of me figure out why the CVS SCM provider can't check out my source files from CVS. I noticed in a couple prior posts that the CVSNT executable requires a login from the same shell prior to starting Continuum. I've done this, yet I still get a build error with "Username isn't defined." as the cause. Here's my SCM url with username/password/host sanitized. scm:cvs:pserver:myuser:[EMAIL PROTECTED]:/Root/projects/project001 waiting for your help ___ 抢注雅虎免费邮箱-3.5G容量,20M附件! http://cn.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Exception: Cannot checkout sources. 7
Does it work from Maven on the same server, with the same user? Wayne On 4/23/07, monsterkhan <[EMAIL PROTECTED]> wrote: Thanks for the reply Wayne. This works in maven on commandline perfectly, its only after the maven/mks integration has matured have we moved on to Continuum. Any more valuable suggestions are welcome. Wayne Fay wrote: > > I'd make this SCM w/MKS work in Maven first, then worry about making > it work in Continuum. Or does it work fine in Maven (stand alone from > command line) but not Continuum? > > Wayne > > On 4/23/07, monsterkhan <[EMAIL PROTECTED]> wrote: >> >> That is something that I get in the failed build list on the front-end >> and >> not in the stack trace :) apologies for not making that clear in the >> first >> go. >> >> >> >> Emmanuel Venisse wrote: >> > >> > I don't see "Cannot checkout sources" messages in this stacktrace. >> > >> > Emmanuel >> > >> > monsterkhan a écrit : >> >> Hi Emmanuel, >> >>Well the stack trace doesnt look too helpful to me, what >> exactly I >> >> was looking for was the list of descriptions of different continuum >> >> exceptions as that might make it easy to analyse the causes of the >> >> exceptions. >> >> >> >> To the best of my guess theres some issue in the way I am giving the >> path >> >> to >> >> the SCM i.e MKS, But what exactly is the reason is beating me. If >> someone >> >> gets an idea from this please help :) >> >> >> >> Here is the relevant part of pom.xml config tht I think is causing the >> >> trouble. >> >> test-continuum >> >> jar >> >> 1.0-SNAPSHOT >> >> test-continuum >> >> http://maven.apache.org >> >> >> >> >> >> >> scm:mks|hostname="hostName"|port="1234"|username="XX"|password="something"|project=/repos/XYZ/ABC/test-continuum/project.pj|devpath=|revision= >> >> >> >> >> scm:mks|hostname="hostName"|port="1234"|username="XX"|password="something"|project=|devpath=|revision= >> >> >> hostName:port/repos/ABC/XYZ/test-continuum/project.pj >> >> >> >> >> >> And here is the stack trace... >> >> >> >> 23 09:09:18,716 [Thread-2] INFO ContinuumScm - >> >> Checking >> >> out project: 'test-continuum', id: '26' to >> >> >> 'C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\26'. >> >> INFO | jvm 3| 2007/04/23 09:09:18 | 2007-04-23 09:09:18,746 >> >> [SocketListener0-0] WARN SQL- Object with >> id >> >> "0" not found ! >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,536 >> >> [SocketListener0-1] WARN SQL- Object with >> id >> >> "0" not found ! >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,536 >> >> [SocketListener0-1] WARN ViewContextPopulator - Cannot find >> a >> >> value for the expression getProject(#id)in >> >> [EMAIL PROTECTED] >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,546 >> >> [SocketListener0-1] WARN SQL- Object with >> id >> >> "0" not found ! >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,546 >> >> [SocketListener0-1] WARN ViewContextPopulator - Cannot find >> a >> >> value for the expression getBuildResultsForProject(#id)in >> >> [EMAIL PROTECTED] >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,566 >> >> [SocketListener0-1] ERROR VelocityComponent - Method >> >> addPathInfo threw exception for reference $link in template >> >> screens/ProjectBuilds.vm at [14,26] >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,566 >> >> [SocketListener0-1] ERROR Renderer:velocity - Error >> >> rendering >> >> template: >> >> INFO | jvm 3| 2007/04/23 09:10:00 | >> java.lang.NullPointerException >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> org.codehaus.plexus.summit.util.UriBuilder.addPathInfo(UriBuilder.java:263) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> java.lang.reflect.Method.invoke(Method.java:324) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:267) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:197) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> org.apache.velocity.runtime.parser.node.ASTReference.value(ASTRe
Re: Dynamic jar manifest classpath based on groupId, artifactId and version in repository
On 4/23/07, Geoffrey De Smet <[EMAIL PROTECTED]> wrote: I also have a dependency on spring-core: /repo/org/springframework/spring-core/2.0.2/spring-core-2.0.2.jar So I need a different classpathPrefix depending on the dependency. what is your use case ? I am not sure that the repository-like structure allowed by the assembly plugin was designed to allow you to run your app from the generated repository. Some suggestions: 1- don't assemble as a maven repository (do you really need it ?) 2- don't depend on the generated classpath (e.g. use a wrapper to start your app) 3- rewrite the generated classpath once your repository has been created. 4- patch the jar plugin to accept a classpath generator that matches your requirement I would pick option 1 or 3. Cheers, J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Exception: Cannot checkout sources. 7
Thanks for the reply Wayne. This works in maven on commandline perfectly, its only after the maven/mks integration has matured have we moved on to Continuum. Any more valuable suggestions are welcome. Wayne Fay wrote: > > I'd make this SCM w/MKS work in Maven first, then worry about making > it work in Continuum. Or does it work fine in Maven (stand alone from > command line) but not Continuum? > > Wayne > > On 4/23/07, monsterkhan <[EMAIL PROTECTED]> wrote: >> >> That is something that I get in the failed build list on the front-end >> and >> not in the stack trace :) apologies for not making that clear in the >> first >> go. >> >> >> >> Emmanuel Venisse wrote: >> > >> > I don't see "Cannot checkout sources" messages in this stacktrace. >> > >> > Emmanuel >> > >> > monsterkhan a écrit : >> >> Hi Emmanuel, >> >>Well the stack trace doesnt look too helpful to me, what >> exactly I >> >> was looking for was the list of descriptions of different continuum >> >> exceptions as that might make it easy to analyse the causes of the >> >> exceptions. >> >> >> >> To the best of my guess theres some issue in the way I am giving the >> path >> >> to >> >> the SCM i.e MKS, But what exactly is the reason is beating me. If >> someone >> >> gets an idea from this please help :) >> >> >> >> Here is the relevant part of pom.xml config tht I think is causing the >> >> trouble. >> >> test-continuum >> >> jar >> >> 1.0-SNAPSHOT >> >> test-continuum >> >> http://maven.apache.org >> >> >> >> >> >> >> scm:mks|hostname="hostName"|port="1234"|username="XX"|password="something"|project=/repos/XYZ/ABC/test-continuum/project.pj|devpath=|revision= >> >> >> >> >> scm:mks|hostname="hostName"|port="1234"|username="XX"|password="something"|project=|devpath=|revision= >> >> >> hostName:port/repos/ABC/XYZ/test-continuum/project.pj >> >> >> >> >> >> And here is the stack trace... >> >> >> >> 23 09:09:18,716 [Thread-2] INFO ContinuumScm - >> >> Checking >> >> out project: 'test-continuum', id: '26' to >> >> >> 'C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\26'. >> >> INFO | jvm 3| 2007/04/23 09:09:18 | 2007-04-23 09:09:18,746 >> >> [SocketListener0-0] WARN SQL- Object with >> id >> >> "0" not found ! >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,536 >> >> [SocketListener0-1] WARN SQL- Object with >> id >> >> "0" not found ! >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,536 >> >> [SocketListener0-1] WARN ViewContextPopulator - Cannot find >> a >> >> value for the expression getProject(#id)in >> >> [EMAIL PROTECTED] >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,546 >> >> [SocketListener0-1] WARN SQL- Object with >> id >> >> "0" not found ! >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,546 >> >> [SocketListener0-1] WARN ViewContextPopulator - Cannot find >> a >> >> value for the expression getBuildResultsForProject(#id)in >> >> [EMAIL PROTECTED] >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,566 >> >> [SocketListener0-1] ERROR VelocityComponent - Method >> >> addPathInfo threw exception for reference $link in template >> >> screens/ProjectBuilds.vm at [14,26] >> >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,566 >> >> [SocketListener0-1] ERROR Renderer:velocity - Error >> >> rendering >> >> template: >> >> INFO | jvm 3| 2007/04/23 09:10:00 | >> java.lang.NullPointerException >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> org.codehaus.plexus.summit.util.UriBuilder.addPathInfo(UriBuilder.java:263) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> java.lang.reflect.Method.invoke(Method.java:324) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:267) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:197) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:327) >> >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> >> >> org.apache.velocity.runtime.parser.node
Re : >>Proximity::Maven2::Eclipse::Proximity<
sorry, I thought I've sent the first mail to the proximity list so I sent this one to the maven list due to the fact that I'm feeling like it's a maven's configuration related because it's just a proxy configuration I think ! isn't it Mr Wayne ? :-) have you experienced using the eclipse plugin please ? thanks for helping me - Message d'origine De : Wayne Fay <[EMAIL PROTECTED]> À : Maven Users List Envoyé le : Lundi, 23 Avril 2007, 15h38mn 06s Objet : Re: >>Proximity::Maven2::Eclipse::Proximity<< 1. You sent this same exact email to this list 2hrs ago. Do NOT resend emails repeatedly to this list, its just rude. Your problem is no more important than anyone else's. 2. For all intents, your questions are entirely Proximity related. Send them to the Proximity User list. Wayne On 4/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi all, > I'm really newbie with maven2 and Proximity, but I > have to set up an inhouse repository architecture by putting some > libraries (artifacts--jars) on a local web server. > We were first > using Ant, so the jars was just in a lib directory ! but now I think > that maven have more complicated way to store liraries : > .../groupid/artifactid/version/artifact > > I downloaded and installed the maven2 eclipse plugin, downloaded and > installed Proximity with Tomcat 6, but the problem is : > > Can I use proximity to store artifacts wich was developed by our company, or > other 3rd party jars ? (if yes, how will I do ?) > Can I access Proximity from myeclipse maven2 plugin ? (if yes, how will I do > ?) > > > Please > help me I feel so confused with all this, because I tried to play with > config files, reading the doc, looking in the forums but I think my > mind is still blocking :-) > > Nawfel > > > > > ___ > Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! > Profitez des connaissances, des opinions et des expériences des internautes > sur Yahoo! Questions/Réponses > http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Re: Exception: Cannot checkout sources. 7
I'd make this SCM w/MKS work in Maven first, then worry about making it work in Continuum. Or does it work fine in Maven (stand alone from command line) but not Continuum? Wayne On 4/23/07, monsterkhan <[EMAIL PROTECTED]> wrote: That is something that I get in the failed build list on the front-end and not in the stack trace :) apologies for not making that clear in the first go. Emmanuel Venisse wrote: > > I don't see "Cannot checkout sources" messages in this stacktrace. > > Emmanuel > > monsterkhan a écrit : >> Hi Emmanuel, >>Well the stack trace doesnt look too helpful to me, what exactly I >> was looking for was the list of descriptions of different continuum >> exceptions as that might make it easy to analyse the causes of the >> exceptions. >> >> To the best of my guess theres some issue in the way I am giving the path >> to >> the SCM i.e MKS, But what exactly is the reason is beating me. If someone >> gets an idea from this please help :) >> >> Here is the relevant part of pom.xml config tht I think is causing the >> trouble. >> test-continuum >> jar >> 1.0-SNAPSHOT >> test-continuum >> http://maven.apache.org >> >> >> scm:mks|hostname="hostName"|port="1234"|username="XX"|password="something"|project=/repos/XYZ/ABC/test-continuum/project.pj|devpath=|revision= >> >> scm:mks|hostname="hostName"|port="1234"|username="XX"|password="something"|project=|devpath=|revision= >> hostName:port/repos/ABC/XYZ/test-continuum/project.pj >> >> >> And here is the stack trace... >> >> 23 09:09:18,716 [Thread-2] INFO ContinuumScm - >> Checking >> out project: 'test-continuum', id: '26' to >> 'C:\continuum-1.0.3\bin\win32\..\..\apps\continuum\working-directory\26'. >> INFO | jvm 3| 2007/04/23 09:09:18 | 2007-04-23 09:09:18,746 >> [SocketListener0-0] WARN SQL- Object with id >> "0" not found ! >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,536 >> [SocketListener0-1] WARN SQL- Object with id >> "0" not found ! >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,536 >> [SocketListener0-1] WARN ViewContextPopulator - Cannot find a >> value for the expression getProject(#id)in >> [EMAIL PROTECTED] >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,546 >> [SocketListener0-1] WARN SQL- Object with id >> "0" not found ! >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,546 >> [SocketListener0-1] WARN ViewContextPopulator - Cannot find a >> value for the expression getBuildResultsForProject(#id)in >> [EMAIL PROTECTED] >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,566 >> [SocketListener0-1] ERROR VelocityComponent - Method >> addPathInfo threw exception for reference $link in template >> screens/ProjectBuilds.vm at [14,26] >> INFO | jvm 3| 2007/04/23 09:10:00 | 2007-04-23 09:10:00,566 >> [SocketListener0-1] ERROR Renderer:velocity - Error >> rendering >> template: >> INFO | jvm 3| 2007/04/23 09:10:00 | java.lang.NullPointerException >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> org.codehaus.plexus.summit.util.UriBuilder.addPathInfo(UriBuilder.java:263) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> java.lang.reflect.Method.invoke(Method.java:324) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:267) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:197) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:327) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:51) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:95) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:70) >> INFO | jvm 3| 2007/04/23 09:10:00 |at >> org.apache.velocity.runtime.parser.node.SimpleNode.render(Si
Re: [m2] [WARNING] Removing: java from forked lifecycle, to prevent recursive invocation.
What's mvn -X look like? Wayne On 4/23/07, Adrian Herscu <[EMAIL PROTECTED]> wrote: Hi all, Using Maven 2.0.6 and the exec-maven-plugin 1.1-beta-1, the following messages appear during the java goal execution: [INFO] Preparing exec:java [WARNING] Removing: java from forked lifecycle, to prevent recursive invocation. [INFO] No goals needed for project - skipping [INFO] [exec:java {execution: default}] Buildfile: C:\documents\pm\backyard\some-ant-build.xml The effect is that the build lifecycle ends immediately after the execution of the java goal :-( What should I check? Please help, Adrian. - 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: >>Proximity::Maven2::Eclipse::Proximity<
1. You sent this same exact email to this list 2hrs ago. Do NOT resend emails repeatedly to this list, its just rude. Your problem is no more important than anyone else's. 2. For all intents, your questions are entirely Proximity related. Send them to the Proximity User list. Wayne On 4/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Hi all, I'm really newbie with maven2 and Proximity, but I have to set up an inhouse repository architecture by putting some libraries (artifacts--jars) on a local web server. We were first using Ant, so the jars was just in a lib directory ! but now I think that maven have more complicated way to store liraries : .../groupid/artifactid/version/artifact I downloaded and installed the maven2 eclipse plugin, downloaded and installed Proximity with Tomcat 6, but the problem is : Can I use proximity to store artifacts wich was developed by our company, or other 3rd party jars ? (if yes, how will I do ?) Can I access Proximity from myeclipse maven2 plugin ? (if yes, how will I do ?) Please help me I feel so confused with all this, because I tried to play with config files, reading the doc, looking in the forums but I think my mind is still blocking :-) Nawfel ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: update maven from 1.0 to maven 2.x
For a starter, see http://maven.apache.org/guides/mini/guide-m1-m2.html. For subscribing to the mailing list, see http://maven.apache.org/mail-lists.html. HTH, -Lukas jill han wrote: Thanks for your reply. Here is the part of project.xml ../project.xml NEO NEO c:\Tomcat4_1_27\webapps commons-codec 1.0-dev true commons-fileupload 1.0-rc1 http://jakarta.apache.org/commons/fileupload/index.html true . Would you please specify the steps that I should follow to make the process easier? And please help me to join the maven user list. I tried, but I don't know why my name still is not in the list. I have to copy and paste from the archive to check and reply the mail. --- Arnaud HERITIER <[EMAIL PROTECTED]> wrote: 1.1 RC1 I suppose .. if you didn't customised a lot maven 1 you can use mvn one:convert to transform your POM. Regards Arnaud On 23/04/07, jill han <[EMAIL PROTECTED]> wrote: I have maven 1.0-rc1 on the system. Is there any easy way to upgrade to maven2? Thanks for the help as always. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven2::Eclipse::Proximity
Please send all Proximity User questions to the Proximity list... Wayne On 4/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Hi all, I'm really newbie with maven2 and Proximity, but I have to set up an inhouse repository architecture by putting some libraries (artifacts--jars) on a local web server. We were first using Ant, so the jars was just in a lib directory ! but now I think that maven have more complicated way to store liraries : .../groupid/artifactid/version/artifact I downloaded and installed the maven2 eclipse plugin, downloaded and installed Proximity with Tomcat 6, but the problem is : Can I use proximity to store artifacts wich was developed by our company, or other 3rd party jars ? (if yes, how will I do) Can I access Proximity from myeclipse maven2 plugin ? (if yes, how will I do) Please help me I feel so confused with all this, because I tried to play with config files, reading the doc, looking in the forums but I think my mind is still blocking :-) Nawfel ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do Archiva Proxied Repositories work?
Archiva downloads artifacts on demand via HTTP using wagon-http. I use a similar config with no issue, but I don't have any proxy to set to access repo1. AFAIK rsync is not yet available. 2007/4/23, M Wurm <[EMAIL PROTECTED]>: Hi there, I've set up Archiva and (almost everything) works fine. I can retrieve artifacts I deployed manually, can deploy artifacts via webdav, but proxied repositories don't seem to work. Now I wanted to ask how Archiva proxies a repository. Somewhere I've read Archiva loads artifacts from demand, so I guess it recognizes a HTTP GET on a directory that doesn't exists and tries to retrieve that artifact from one of the repositories listed under "proxied repositories". Is this correct? If so, how is the proxied repository being accessed? Via http? Or is rsync used in some way? I need to specify a http proxy (which I did in the Archiva settings), but rsync is disabled on the machine that hosts Archiva. Can this be a problem? I'm proxying http://repo1.maven.org/maven2/ but can't get it work. Maven tells me it could not download a dependency via my managed repository and falls back to the default repository. Any ideas? Best Regards, Matthias
>>Proximity::Maven2::Eclipse::Proximity<
Hi all, I'm really newbie with maven2 and Proximity, but I have to set up an inhouse repository architecture by putting some libraries (artifacts--jars) on a local web server. We were first using Ant, so the jars was just in a lib directory ! but now I think that maven have more complicated way to store liraries : .../groupid/artifactid/version/artifact I downloaded and installed the maven2 eclipse plugin, downloaded and installed Proximity with Tomcat 6, but the problem is : Can I use proximity to store artifacts wich was developed by our company, or other 3rd party jars ? (if yes, how will I do ?) Can I access Proximity from myeclipse maven2 plugin ? (if yes, how will I do ?) Please help me I feel so confused with all this, because I tried to play with config files, reading the doc, looking in the forums but I think my mind is still blocking :-) Nawfel ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
How do Archiva Proxied Repositories work?
Hi there, I've set up Archiva and (almost everything) works fine. I can retrieve artifacts I deployed manually, can deploy artifacts via webdav, but proxied repositories don't seem to work. Now I wanted to ask how Archiva proxies a repository. Somewhere I've read Archiva loads artifacts from demand, so I guess it recognizes a HTTP GET on a directory that doesn't exists and tries to retrieve that artifact from one of the repositories listed under "proxied repositories". Is this correct? If so, how is the proxied repository being accessed? Via http? Or is rsync used in some way? I need to specify a http proxy (which I did in the Archiva settings), but rsync is disabled on the machine that hosts Archiva. Can this be a problem? I'm proxying http://repo1.maven.org/maven2/ but can't get it work. Maven tells me it could not download a dependency via my managed repository and falls back to the default repository. Any ideas? Best Regards, Matthias
Howto setup log4j to work properly with maven test ?
Hello, i have a problem with the test plugin of maven (1.x). When i add log4j configuration to project, it seems part of output that should go in test-report/xxx.yyy.TestZzz.txt does in fact go out on the user console. This is a problem because we get the test report stripped out of most of it's output. Example, if my log4j.xml is empty, i get this: maven test -Dmaven.junit.usefile=true -Dmaven.junit.fork=true -Dmaven.junit.forkmode=perTest test:test: [junit] Running be.dissco.slide.SlideFopDriverTest [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 4,799 sec [junit] 23 Apr 2007 16:46:15 - org.apache.slide.common.Domain - WARNING - Access denied on /users by user *** Could not determine principal *** for action /actions/read [junit] 23 Apr 2007 16:46:15 - org.apache.slide.common.Domain - WARNING - Access denied on /users by user *** Could not determine principal *** for action /actions/read [junit] [ERROR] TEST be.dissco.slide.SlideFopDriverTest FAILED [junit] Running be.rmi.intranet.db.V4_newsServiceTest However, if my log4j.xml contains console appenders, i get this: test:test: [junit] Running be.dissco.slide.SlideFopDriverTest [junit] 0[main] DEBUG be.dissco.slide.SlideFopDriverTest - remove store dir [junit] 3[main] DEBUG be.dissco.slide.SlideFopDriverTest - remove work dir [junit] 1223 [main] INFO be.dissco.common.Dissco - Start DISSCO configuration initialization [junit] 1226 [main] DEBUG be.dissco.common.configuration.ConfigurationLoader - properties defined : configuration.resource=dissco.xml, [junit] 1227 [main] INFO be.dissco.common.configuration.ConfigurationLoader - load configuration from :: systemId = file:/home/delbd/dev/workspaces/intranet/RMI_intranet/target/test-classes/dissco.xml publicId = null Obviously, those log entries should go in test-report not screen! How to solve thise, is there a specific appender to use? Thanks for help. (part of log4j.xml below) http://jakarta.apache.org/log4j/"; debug="false" threshold="debug"> . If i type in console: maven test -Dmaven.junit.usefile=true -Dmaven.junit.fork=true i get this: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: update maven from 1.0 to maven 2.x
Thanks for your reply. Here is the part of project.xml ../project.xml NEO NEO c:\Tomcat4_1_27\webapps commons-codec 1.0-dev true commons-fileupload 1.0-rc1 http://jakarta.apache.org/commons/fileupload/index.html true . Would you please specify the steps that I should follow to make the process easier? And please help me to join the maven user list. I tried, but I don't know why my name still is not in the list. I have to copy and paste from the archive to check and reply the mail. --- Arnaud HERITIER <[EMAIL PROTECTED]> wrote: > 1.1 RC1 I suppose .. > > if you didn't customised a lot maven 1 you can use mvn one:convert to > transform your POM. > > Regards > > Arnaud > > On 23/04/07, jill han <[EMAIL PROTECTED]> wrote: > > > > I have maven 1.0-rc1 on the system. Is there any easy way to > upgrade to > > maven2? > > > > Thanks for the help as always. > > > > >
Re: how to exclude modules
1. Move to Subversion. File refactoring does not lose history. 2. There is no module excludes. Instead we have a notion of profiles in M2. So you would set your default in the top parent pom.xml to have say either zero or very few modules defined, and then in a separate profile (call it "all"), you would have all modules listed. Thus when you normally built your project from the top parent dir, only the default modules would be built. But then when you specified -Pall, all your modules would be built. Perhaps this gives you something to think about. I'm not sure if it solves all your problems. Wayne On 4/23/07, Daniel Beland <[EMAIL PROTECTED]> wrote: Hi, I have some questions about aggregation modules in maven2. Let me explain how we were working with maven 1.1 and why I don`t fully understand how we should work with maven 2. We have some maven 1 multi-projects saved in CVS as a single project. A developer checks out the complete project in 1 operation. Most of the time, it consists of N jar artifacts to be included in a webapp. Since we do not modify all the N artifacts but just a subset of them between each release, we would work intensively with the maven.multiproject.excludesproperty to set only the projects we want to build between each release (projects that are SNAPSHOT and are needed in the webapp project.xml, and it means we reset the value to all projects every time we release a beta). Since the rest is already released (be it production version or previous unchanged beta), there is no need to compile and deploy them again the next time. Now in maven 2, there is no such property. After a release, everything is put back to SNAPSHOT, even all the dependencies in the webapp pom (as I understand it would do). How can I release a project and have only each artifact's current version set to SNAPSHOT, but have the webapp dependencies left to the just released version? (Keep in mind I didn't release an aggregation module with inter-dependencies yet and maybe it is not what it does). How can I have something similar to maven.multiproject.excludes? Should I comment the modules I don't want to compile in the pom? Finally, is it in your opinion better to simply have N projects in CVS other than a big aggregation project to achieve what I want? (But would still use the same parent pom, I would just release each sub-module independently and have better control on what to release each time). My only concern with that is the major refactoring of the CVS modules and losing all the file history. Thanks for your input, Daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Prompt user for variable?
Simple question, is there anyway to get Maven to prompt the user to input a variable? The scenario is that I have a proxy server that requires a username and password, I do not want to store the password on the file system and would like to have Maven prompt for it whenever mvn is run and the ${password} variable is needed. The inputing of the password should be masked as well. I was thinking of creating a plugin to do this but what was wondering if there is something available for this already. Thanks, Gerald
RE: Problem in packaging multiple directories
Hi, There only ever is one 'pom.xml' per project. The project structure below really shows all essential file needed. I suggest you set up a simple test project up-to the point where you can successfully compile and package it and then venture on from this starting point. The test project would have one 'pom.xml' in it's root directory and a 'src/main/java' directory containing the java classes and packages. Once you have that up and running you can extend you example like described in Point III. from my last mail. What you will have then is a working multi-module project (I don't know if that's the official term but it's what I'm calling it). And again like in the example for the simple (one-module) project all relevant files are shown in my last mail. One point I think you are confused with is the difference between a multi-module (aggregation) project and pom inheritance (parent pom). In a multi-module project there is no parent pom involved per se. You just have a set of (concrete) projects where the actual code is compiled and one or more aggregation projects (with a packaging of type pom) that _aggregate_ the build of the concrete projects via the tag in the pom. No parent poms involved here. A parent pom is something analogue to a superclass in java it captures portions of common configuration. For example if you have multiple projects depending on the same library, you could create a parent pom which declares that library as a dependency and let all projects needing that library inherit from the parent pom via the tag. -Tim Am Montag, den 23.04.2007, 18:40 +0530 schrieb Ramesh Babu Pokala - TLS, Chennai: > Thanks for your response. > I am following the following structure as u mentioned > > my-app > |-- pom.xml > `-- src >-- main > `-- java > `-- package1 > `-- package2 > `-- package3 > | `-- App.java > `-- package4 > `-- MyClass.java > > > Then what should be my parent POM.xml? > How many poms I need. Do I need poms for package3 as well as package4 > along with main pom? > ` > > Thanks & Regards > Ramesh Babu.P > > -Original Message- > From: Tim Kettler [mailto:[EMAIL PROTECTED] > Sent: Saturday, April 21, 2007 11:42 PM > To: Maven Users List > Subject: Re: Problem in packaging multiple directories > > Hi, > > I. Maven Directory Layout > > If you follow the 'Getting Started Guide' you should have a directory > structure like the one below: > > my-app > |-- pom.xml > `-- src > |-- main > | `-- java > | `-- package1 > | `-- package2 > | `-- package3 > | | `-- App.java > | `-- package4 > | `-- MyClass.java > `-- test > `-- java > `-- packakag1 > `-- package2 > `-- package3 > `-- AppTest.java > > This is the default layout maven expects. If you are not converting from > a legacy project and absolutely need a different directory layout you > should stick to this default. That will save you from much hassle. > > If you really can't follow that proposed structure, you have to override > the maven default values in the pom (see [1], [2] and [3] for a complete > description of the pom). > > For example, to override the default source directory you would have > something like this in your pom: > > > ... > > > my/non/standard/source/directory > ... > > ... > > > > II. Multiple Source Directories Per Project > > Maven has a one-set-of-sources-per-project philosophy so if you really > need multiple source directories you are somewhat working against the > spirit of maven. Instead you should organize your project in multiple > modules (see below) and make them depend on each other. > > If you really need to have more than one set of sources in a single > project you can attach an additional source directory using the > build-helper-maven-plugin [4]. > > > III. Multi-Module Projects > > Multi-Module projects are a set of maven projects (logical!!, not > necessarily physical on disk) organized as a tree. The nodes in the > logical tree are projects with a packaging of type pom with the leaves > of the tree containing the projects where you actual build your > artifacts (jar, war, ...). > > A typical layout could look like this: > > my-app > |-- pom.xml > |-- subproject1 > | |-- pom.xml > | `-- src > | `-- main > | `-- java > | `-- package1 > | `-- package2 > | `-- package3 > | `-- App.java > `-- subproject1 > |-- pom.xml > `-- src > `-- main > `-- java > `-- package1 > `
Howto setup log4j to work properly with maven test ?
Hello, i have a problem with the test plugin of maven (1.x). When i add log4j configuration to project, it seems part of output that should go in test-report/xxx.yyy.TestZzz.txt does in fact go out on the user console. This is a problem because we get the test report stripped out of most of it's output. Example, if my log4j.xml is empty, i get this: maven test -Dmaven.junit.usefile=true -Dmaven.junit.fork=true -Dmaven.junit.forkmode=perTest test:test: [junit] Running be.dissco.slide.SlideFopDriverTest [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 4,799 sec [junit] 23 Apr 2007 16:46:15 - org.apache.slide.common.Domain - WARNING - Access denied on /users by user *** Could not determine principal *** for action /actions/read [junit] 23 Apr 2007 16:46:15 - org.apache.slide.common.Domain - WARNING - Access denied on /users by user *** Could not determine principal *** for action /actions/read [junit] [ERROR] TEST be.dissco.slide.SlideFopDriverTest FAILED [junit] Running be.rmi.intranet.db.V4_newsServiceTest However, if my log4j.xml contains console appenders, i get this: test:test: [junit] Running be.dissco.slide.SlideFopDriverTest [junit] 0[main] DEBUG be.dissco.slide.SlideFopDriverTest - remove store dir [junit] 3[main] DEBUG be.dissco.slide.SlideFopDriverTest - remove work dir [junit] 1223 [main] INFO be.dissco.common.Dissco - Start DISSCO configuration initialization [junit] 1226 [main] DEBUG be.dissco.common.configuration.ConfigurationLoader - properties defined : configuration.resource=dissco.xml, [junit] 1227 [main] INFO be.dissco.common.configuration.ConfigurationLoader - load configuration from :: systemId = file:/home/delbd/dev/workspaces/intranet/RMI_intranet/target/test-classes/dissco.xml publicId = null Obviously, those log entries should go in test-report not screen! How to solve thise, is there a specific appender to use? Thanks for help. (part of log4j.xml below) http://jakarta.apache.org/log4j/"; debug="false" threshold="debug"> . If i type in console: maven test -Dmaven.junit.usefile=true -Dmaven.junit.fork=true i get this: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dynamic jar manifest classpath based on groupId, artifactId and version in repository
I also have a dependency on spring-core: /repo/org/springframework/spring-core/2.0.2/spring-core-2.0.2.jar So I need a different classpathPrefix depending on the dependency. With kind regards, Geoffrey De Smet Ian Springer schreef: Hi, Add: ../../../../org/ggg/ggg-core/1.0/ as a child element of the element. Ian Geoffrey De Smet wrote: Hi all, With the assembly plugin I can put all my module jars in repository like structure: /repo/org/ggg/ggg-core/1.0/ggg-core-1.0.jar /repo/org/ggg/ggg-ftp-app/1.0/ggg-ftp-app-1.0.jar depends on ggg-core /repo/org/ggg/ggg-http-app/1.0/ggg-http-app-1.0.jar depends on ggg-core I've configured the maven-jar-plugin as such: org.apache.maven.plugins maven-jar-plugin org.ggg.ftpapp.FtpMain true And now the manifest contains an entry "ggg-core-1.0.jar". The problem is that this needs to be "../../../../org/ggg/ggg-core/1.0/ggg-core-1.0.jar" How I make that happen? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-assembly-plugin: doesn't work from a reactor build
Hi all, I have an assembly linked into the mvn build lifecycle like below using the "attached" goal. When mvn install is run from the assembly artifact, the assembly is built correctly. If however mvn install is run from the root pom (ie a reactor build), the assembly plugin goes through the motions, but the assembly created is empty. Does the "attached" goal work in multi-module / reactor builds? maven-assembly-plugin 2.2-beta-1 assembly.xml make-assembly package attached Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dynamic jar manifest classpath based on groupId, artifactId and version in repository
Hi, Add: ../../../../org/ggg/ggg-core/1.0/ as a child element of the element. Ian Geoffrey De Smet wrote: Hi all, With the assembly plugin I can put all my module jars in repository like structure: /repo/org/ggg/ggg-core/1.0/ggg-core-1.0.jar /repo/org/ggg/ggg-ftp-app/1.0/ggg-ftp-app-1.0.jar depends on ggg-core /repo/org/ggg/ggg-http-app/1.0/ggg-http-app-1.0.jar depends on ggg-core I've configured the maven-jar-plugin as such: org.apache.maven.plugins maven-jar-plugin org.ggg.ftpapp.FtpMain true And now the manifest contains an entry "ggg-core-1.0.jar". The problem is that this needs to be "../../../../org/ggg/ggg-core/1.0/ggg-core-1.0.jar" How I make that happen? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
update maven from 1.0 to maven 2.x
I have maven 1.0-rc1 on the system. Is there any easy way to upgrade to maven2? Thanks for the help as always.
Re: update maven from 1.0 to maven 2.x
1.1 RC1 I suppose .. if you didn't customised a lot maven 1 you can use mvn one:convert to transform your POM. Regards Arnaud On 23/04/07, jill han <[EMAIL PROTECTED]> wrote: I have maven 1.0-rc1 on the system. Is there any easy way to upgrade to maven2? Thanks for the help as always.
Dynamic jar manifest classpath based on groupId, artifactId and version in repository
Hi all, With the assembly plugin I can put all my module jars in repository like structure: /repo/org/ggg/ggg-core/1.0/ggg-core-1.0.jar /repo/org/ggg/ggg-ftp-app/1.0/ggg-ftp-app-1.0.jar depends on ggg-core /repo/org/ggg/ggg-http-app/1.0/ggg-http-app-1.0.jar depends on ggg-core I've configured the maven-jar-plugin as such: org.apache.maven.plugins maven-jar-plugin org.ggg.ftpapp.FtpMain true And now the manifest contains an entry "ggg-core-1.0.jar". The problem is that this needs to be "../../../../org/ggg/ggg-core/1.0/ggg-core-1.0.jar" How I make that happen? -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem in packaging multiple directories
Thanks for your response. I am following the following structure as u mentioned my-app |-- pom.xml `-- src -- main `-- java `-- package1 `-- package2 `-- package3 | `-- App.java `-- package4 `-- MyClass.java Then what should be my parent POM.xml? How many poms I need. Do I need poms for package3 as well as package4 along with main pom? ` Thanks & Regards Ramesh Babu.P -Original Message- From: Tim Kettler [mailto:[EMAIL PROTECTED] Sent: Saturday, April 21, 2007 11:42 PM To: Maven Users List Subject: Re: Problem in packaging multiple directories Hi, I. Maven Directory Layout If you follow the 'Getting Started Guide' you should have a directory structure like the one below: my-app |-- pom.xml `-- src |-- main | `-- java | `-- package1 | `-- package2 | `-- package3 | | `-- App.java | `-- package4 | `-- MyClass.java `-- test `-- java `-- packakag1 `-- package2 `-- package3 `-- AppTest.java This is the default layout maven expects. If you are not converting from a legacy project and absolutely need a different directory layout you should stick to this default. That will save you from much hassle. If you really can't follow that proposed structure, you have to override the maven default values in the pom (see [1], [2] and [3] for a complete description of the pom). For example, to override the default source directory you would have something like this in your pom: ... my/non/standard/source/directory ... ... II. Multiple Source Directories Per Project Maven has a one-set-of-sources-per-project philosophy so if you really need multiple source directories you are somewhat working against the spirit of maven. Instead you should organize your project in multiple modules (see below) and make them depend on each other. If you really need to have more than one set of sources in a single project you can attach an additional source directory using the build-helper-maven-plugin [4]. III. Multi-Module Projects Multi-Module projects are a set of maven projects (logical!!, not necessarily physical on disk) organized as a tree. The nodes in the logical tree are projects with a packaging of type pom with the leaves of the tree containing the projects where you actual build your artifacts (jar, war, ...). A typical layout could look like this: my-app |-- pom.xml |-- subproject1 | |-- pom.xml | `-- src | `-- main | `-- java | `-- package1 | `-- package2 | `-- package3 | `-- App.java `-- subproject1 |-- pom.xml `-- src `-- main `-- java `-- package1 `-- package2 `-- UtilityClass.java The content of the poms would then look like this: my-app/pom.xml: com.mycompany.app 1.0-SNAPSHOT app pom subproject1 subproject2 subproject1/pom.xml: com.mycompany.app subproject1 1.0-SNAPSHOT jar com.mycompany.app subproject1 1.0-SNAPSHOT subproject2/pom.xml: com.mycompany.app subproject2 1.0-SNAPSHOT jar Hope this gets you started -Tim [1] http://maven.apache.org/guides/introduction/introduction-to-the-pom.html [2] http://maven.apache.org/pom.html [3] http://maven.apache.org/ref/current/maven-model/maven.html [4] http://mojo.codehaus.org/build-helper-maven-plugin/howto.html Am Samstag, den 21.04.2007, 20:42 +0530 schrieb Ramesh Babu Pokala - TLS, Chennai: > Hi, > I was unable to compile multi directory project... I tried in > different ways (follwed from maven - getting started site) but still > did not get the solution. > > I have directory structure like > > > abc > | > |___src >| >|_xxx > | > |__yyy > | > |_zzz > | > > |aaa --> java files > | > > |bbb --> java files > | > > |ccc --> java files > > > Now i want to compile sources in all the packages xxx.yyy.zzz.aaa, > xxx.yyy.zzz.bbb and xxx.yyy.zzz.ccc. > > > Tries..
Maven2::Eclipse::Proximity
Hi all, I'm really newbie with maven2 and Proximity, but I have to set up an inhouse repository architecture by putting some libraries (artifacts--jars) on a local web server. We were first using Ant, so the jars was just in a lib directory ! but now I think that maven have more complicated way to store liraries : .../groupid/artifactid/version/artifact I downloaded and installed the maven2 eclipse plugin, downloaded and installed Proximity with Tomcat 6, but the problem is : Can I use proximity to store artifacts wich was developed by our company, or other 3rd party jars ? (if yes, how will I do) Can I access Proximity from myeclipse maven2 plugin ? (if yes, how will I do) Please help me I feel so confused with all this, because I tried to play with config files, reading the doc, looking in the forums but I think my mind is still blocking :-) Nawfel ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
Execute a Maven plugin from another Plugin
Hi all, I have developed a Maven 2 plugin. This plugin modifies some files created by the Maven Eclipse plugin. Thus, for the moment, I need to execute the following commands: mvn eclipse:clean mvn eclipse:eclipse mvn myplugin:mygoal Now, I want to have both 'clean' and 'eclipse' goals of Maven Eclipse plugin executed every time I execute my plugin. In others words, when I launch the command 'mvn myplugin:mygoal', it must first execute eclipse:clean, then eclipse:eclipse, and finally my myplugin:mygoal command. Of course I can do that using a batch file, but it is not a real solution... My question is then: How I can launch other plugins from my plugin ? Thanks in advance for your answers. -- View this message in context: http://www.nabble.com/Execute-a-Maven-plugin-from-another-Plugin-tf3630759s177.html#a10138316 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Loading property from specific file
Try using this plugin: http://individual.utoronto.ca/zarar/properties-maven-plugin/site/introdu ction.html Regards, Ravi -Original Message- From: Depthblue [mailto:[EMAIL PROTECTED] Sent: Monday, April 23, 2007 4:13 PM To: users@maven.apache.org Subject: Loading property from specific file Hi everybody, I need loading my property build.number from my file data.txt to Maven. And I need using this property in scm:tag for set tag name. Thanks -- View this message in context: http://www.nabble.com/Loading-property-from-specific-file-tf3630468s177. html#a10137472 Sent from the Maven - Users mailing list archive at Nabble.com. - 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 exclude modules
Hi, I have some questions about aggregation modules in maven2. Let me explain how we were working with maven 1.1 and why I don`t fully understand how we should work with maven 2. We have some maven 1 multi-projects saved in CVS as a single project. A developer checks out the complete project in 1 operation. Most of the time, it consists of N jar artifacts to be included in a webapp. Since we do not modify all the N artifacts but just a subset of them between each release, we would work intensively with the maven.multiproject.excludesproperty to set only the projects we want to build between each release (projects that are SNAPSHOT and are needed in the webapp project.xml, and it means we reset the value to all projects every time we release a beta). Since the rest is already released (be it production version or previous unchanged beta), there is no need to compile and deploy them again the next time. Now in maven 2, there is no such property. After a release, everything is put back to SNAPSHOT, even all the dependencies in the webapp pom (as I understand it would do). How can I release a project and have only each artifact's current version set to SNAPSHOT, but have the webapp dependencies left to the just released version? (Keep in mind I didn't release an aggregation module with inter-dependencies yet and maybe it is not what it does). How can I have something similar to maven.multiproject.excludes? Should I comment the modules I don't want to compile in the pom? Finally, is it in your opinion better to simply have N projects in CVS other than a big aggregation project to achieve what I want? (But would still use the same parent pom, I would just release each sub-module independently and have better control on what to release each time). My only concern with that is the major refactoring of the CVS modules and losing all the file history. Thanks for your input, Daniel
Include optional dependencies
Hi, I am presently converting our projects from maven 1.1 to maven 2. I must say that the transitive dependencies help a lot to reduce the pom and makes upgrades easier. But I would like to include optional dependencies as well, without having to explicitly include them myself in the pom. For example, I use hibernate 3.2.1.ga, it has an optional dependency on jgroups-all-2.2.8. I would like to be able to add an includes statement on the hibernate lib to tell that I want to include jgroups as well. The main reason for this, is that I want the same version as specified in the hibernate pom. This way, upgrading hibernate would also upgrade my version of jgroups at the same time. The only problem I can see though, is how can we set if this dependency should be optional or not when this artifact is used in another project. We would have to be able to set optional on the included transitive dependency. So I thought it could probably be better if we could set the dependency explicitly in the pom without specifying the version and have maven resolve the version from the nearest source (as it does normally) and fail if no other source of the lib can be found in the resolution tree. But this would mean more flexibility on the pom and could be hard to implement. Otherwise, I know we can use a dependencyManagement on a parent pom. But if I set this in the parent pom: jgroups jgroups-all 2.2.8 and don't set the version in my project, how will maven react when hibernate upgrades the dependency? Will it use the parent pom version or the hibernate version as the nearest source? What are your thoughts on the subject? Is this something other people would find useful as well? Am I bothering about something that does not happen often with maven 2 and should take it as it is? Thanks for your input, Daniel
Re: Loading property from specific file
Hi, You can refer to this document, in the "How do I filter resource files?" section: http://maven.apache.org/guides/getting-started/index.html Thanks, Deng Depthblue wrote: Hi everybody, I need loading my property build.number from my file data.txt to Maven. And I need using this property in scm:tag for set tag name. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] maven-antlr-plugin searches for generated files in the source directory
Hi all, Using Maven 2.0.6 and maven-antlr-plugin 2.0-beta-2-SNAPSHOT configured as follows: ${basedir}/src/main/antlr/com/acme/lang/compiler ${basedir}/src/main/antlr/com/acme/lang/compiler super.g ext1.g super.g ext2.g super.g Otherwise I get the following errors: [INFO] [antlr:generate {execution: default}] [INFO] Using Antlr grammar: C:\documents\pm\backyard\compiler\src\main\antlr\com\acme\lang\compiler\super.g ANTLR Parser Generator Version 2.7.4 1989-2004 jGuru.com [INFO] Using Antlr grammar: C:\documents\pm\backyard\compiler\src\main\antlr\com \acme\lang\compiler\ext1.g ANTLR Parser Generator Version 2.7.4 1989-2004 jGuru.com error: cannot find/copy importVocab file C:\documents\pm\backyard\compiler\src\m ain\antlr\com\acme\lang\compiler\SuperTokenTypes.txt error: cannot find/copy importVocab file C:\documents\pm\backyard\compiler\src\m ain\antlr\com\acme\lang\compiler\SuperTokenTypes.txt C:\documents\pm\backyard\compiler\target\generated-sources\antlr\com\acme\lang \compiler\expandedext1.g:17:9: warning:Redefinition of token in toke ns {...}: BLOCK ...and many other redefinition warnings ... The same error is generated for each extN. Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Loading property from specific file
Hi everybody, I need loading my property build.number from my file data.txt to Maven. And I need using this property in scm:tag for set tag name. Thanks -- View this message in context: http://www.nabble.com/Loading-property-from-specific-file-tf3630468s177.html#a10137472 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven 1.0.2 to 1.1 beta 3
3Ms is certainly a big file especially since the raw reports are probably bigger... did you try already to disable some of the checks? I just ran checkstyle on a project with 207 files, the checkstyle-summary-report.xml is 5450 bytes and it took exactly 1 minute, so 4mins for your project doesn't surprise me. -Lukas emerson cargnin wrote: i found out that the part that takes the most of time (4 minutes for 500 files) is that's the raw report... and the file generated has 3088523 bytes. Is it normal? thanks emerson On 23/04/07, emerson cargnin <[EMAIL PROTECTED]> wrote: anyone has any clue how I could investigate this better??? thanks On 20/04/07, emerson cargnin <[EMAIL PROTECTED]> wrote: > ok > > thanks a lot > > would anyone else have a clue why my build hangs for so long on the > following point? > > [exec] checkstyle:report-internal: > [exec] [mkdir] Created dir: > /subversion/users/client/cruise/checkout/build-projet/modules/com.company.java/target/generated-xdocs/checkstyle > > > > On 20/04/07, Lukas Theussl <[EMAIL PROTECTED]> wrote: > > > > > > emerson cargnin wrote: > > > Thanks for the reply lukas. > > > > > > 1) do you run checkstyle? if so, you didn't noticed it takes a quite > > > while to generate the reports? > > > in this line it stops for 3 or 4 minutes > > > > > > [exec] [checkstyle] Running Checkstyle 4.1 on 416 files > > > [exec] checkstyle:report-internal: > > > [exec] [mkdir] Created dir: > > > /subversion/users/svnclient/cruise/checkout/build-ucssearch/modules/com.yell.searchengine/target/generated-xdocs/checkstyle > > > > Yes I do run checkstyle, and as I said, I haven't noticed any > > performance problems. However, if I understand correctly from your > > snippet, your build hangs in the checkstyle:report-internal goal. This > > goal is run after checkstyle has processed the source code and all it > > does is generate the xdocs from the checkstyle xml output via some jelly > > scripts. So the problem doesn't seem to be related to checkstyle, but I > > have no idea what it could be... > > > > > 2) Do you need to put the emma.jar in your jre lib/ext ??? > > > > No, I just downloaded the emma plugin (maven plugin:download) and ran > > 'maven emma'. No other preparation needed. > > > > -Lukas > > > > - > > 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: maven 1.0.2 to 1.1 beta 3
i found out that the part that takes the most of time (4 minutes for 500 files) is that's the raw report... and the file generated has 3088523 bytes. Is it normal? thanks emerson On 23/04/07, emerson cargnin <[EMAIL PROTECTED]> wrote: anyone has any clue how I could investigate this better??? thanks On 20/04/07, emerson cargnin <[EMAIL PROTECTED]> wrote: > ok > > thanks a lot > > would anyone else have a clue why my build hangs for so long on the > following point? > > [exec] checkstyle:report-internal: > [exec] [mkdir] Created dir: > /subversion/users/client/cruise/checkout/build-projet/modules/com.company.java/target/generated-xdocs/checkstyle > > > > On 20/04/07, Lukas Theussl <[EMAIL PROTECTED]> wrote: > > > > > > emerson cargnin wrote: > > > Thanks for the reply lukas. > > > > > > 1) do you run checkstyle? if so, you didn't noticed it takes a quite > > > while to generate the reports? > > > in this line it stops for 3 or 4 minutes > > > > > > [exec] [checkstyle] Running Checkstyle 4.1 on 416 files > > > [exec] checkstyle:report-internal: > > > [exec] [mkdir] Created dir: > > > /subversion/users/svnclient/cruise/checkout/build-ucssearch/modules/com.yell.searchengine/target/generated-xdocs/checkstyle > > > > Yes I do run checkstyle, and as I said, I haven't noticed any > > performance problems. However, if I understand correctly from your > > snippet, your build hangs in the checkstyle:report-internal goal. This > > goal is run after checkstyle has processed the source code and all it > > does is generate the xdocs from the checkstyle xml output via some jelly > > scripts. So the problem doesn't seem to be related to checkstyle, but I > > have no idea what it could be... > > > > > 2) Do you need to put the emma.jar in your jre lib/ext ??? > > > > No, I just downloaded the emma plugin (maven plugin:download) and ran > > 'maven emma'. No other preparation needed. > > > > -Lukas > > > > - > > 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 : Re : Re : Re : Proximity
OK ! So what can you advise me to get it working ? (don't forget that I'm a newbie ;-) ) Thanks Nawfel - Message d'origine De : Mykel Alvis <[EMAIL PROTECTED]> À : Maven Users List Envoyé le : Vendredi, 20 Avril 2007, 19h26mn 22s Objet : Re: Re : Re : Re : Proximity My $.02 (that's "my 2 cents worth" for the non-Americans, which a euphemism for "my unsolicited and free opinion which is worth what you paid for it" :) ) Having set up a couple of fairly complex proximity instance, I can tell you that until recently I had very little luck publishing via dav directly into proximity. I know Tamas is working on that issue, but it does sort of tie you more into Proximity if the proximity app is the actual DAV provider. My solution was to have all my repositories be filesystem DAV repositories setup within Apache and then have Proximity consider them all to be remote repositories and therefore reads from them into its own cache. I know it's circumventing some of the things that Proximity does for you, but it's extremely safe and allows you to replace your proxy (or upgrade/change it) without worrying about what your proxy might be doing to your deployed artifacts. Of course, this means that you're storing up to 2x the number of artifacts (one in your deployed dav repo and possibly one cached in the proximity repo), but it also means that your proximity repo is easily replaced in the event of some catastrophe. Thus you only have to back up the filesystem that hosts your DAV repos. I know this is almost semantic, but it's been very useful to me. In my case, the dav repos are actually on another box entirely that gets backed up frequently while my proximity instance gets backed up only when it changes (very infrequently) and the proximity cache never gets backed up at all. Actually, I'm trying to make a drawing of this entire thing for my current employer. If I can get it done I'll post it somewhere. On 4/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > in my settings.xml there's only this : > > > > > > > > proximity > > ilem.ma (local) Proximity instance > > http://localhost:8080/px-webapp-default-1.0.0-RC8/repository > > * > > > > > > every thing else is set to default ==nothing (^_^) > > > > Nice week-end everybody ;-) > > > > Nawfel > www.ilem.ma > > - Message d'origine > De : Wayne Fay <[EMAIL PROTECTED]> > À : Maven Users List > Envoyé le : Vendredi, 20 Avril 2007, 18h09mn 38s > Objet : Re: Re : Re : Proximity > > "access denied to" seems like you need to check your file system > permissions on those directories. I'd guess that the user running > Proximity does not have the right privileges to write to those > directories. Not sure, but that's my guess. > > Wayne > > On 4/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I've tried this : (but I think I'm so far of the right way :-( !) > > > > >mvn deploy:deploy-file -Dfile=./lib/asm-1.5.3.jar-DrepositoryId=proximity \ > > -Durl= > http://localhost:8080/px-webapp-default-1.0.0-RC8/px-webapp/dav/public \ > > -DartifactId=asm -DgroupId=asm -Dversion=1.5.3 -Dpackaging=jar > -e > > + Error stacktraces are turned on. > > [INFO] Scanning for projects... > > [INFO] Searching repository for plugin with prefix: 'deploy'. > > [INFO] > - > > --- > > [INFO] Building Unnamed - com:TutelecOJV-v1.3:jar:1.3 > > [INFO]task-segment: [deploy:deploy-file] (aggregator-style) > > [INFO] > - > > --- > > [INFO] [deploy:deploy-file] > > Uploading: > http://localhost:8080/px-webapp-default-1.0.0-RC8/px-webapp/dav/publi > > c/asm/asm/1.5.3/asm-1.5.3.jar > > 25K uploaded > > [INFO] > > > [ERROR] BUILD ERROR > > [INFO] > > > [INFO] Error deploying artifact: Authorization failed: Access denied to: > http:// > > localhost:8080/px-webapp-default-1.0.0-RC8 > /px-webapp/dav/public/asm/asm/1.5.3/as > > m-1.5.3.jar > > > > [INFO] > > > [INFO] Trace > > org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying > artifact > > : Authorization failed: Access denied to: > http://localhost:8080/px-webapp-defaul > > t-1.0.0-RC8/px-webapp/dav/public/asm/asm/1.5.3/asm-1.5.3.jar > >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > > ultLifecycleExecutor.java:564) > >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone > > Goal(DefaultLifecycleExecutor.java:493) > >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > > ltLifecycleExecutor.java:463) > >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
Re: maven 1.0.2 to 1.1 beta 3
anyone has any clue how I could investigate this better??? thanks On 20/04/07, emerson cargnin <[EMAIL PROTECTED]> wrote: ok thanks a lot would anyone else have a clue why my build hangs for so long on the following point? [exec] checkstyle:report-internal: [exec] [mkdir] Created dir: /subversion/users/client/cruise/checkout/build-projet/modules/com.company.java/target/generated-xdocs/checkstyle On 20/04/07, Lukas Theussl <[EMAIL PROTECTED]> wrote: > > > emerson cargnin wrote: > > Thanks for the reply lukas. > > > > 1) do you run checkstyle? if so, you didn't noticed it takes a quite > > while to generate the reports? > > in this line it stops for 3 or 4 minutes > > > > [exec] [checkstyle] Running Checkstyle 4.1 on 416 files > > [exec] checkstyle:report-internal: > > [exec] [mkdir] Created dir: > > /subversion/users/svnclient/cruise/checkout/build-ucssearch/modules/com.yell.searchengine/target/generated-xdocs/checkstyle > > Yes I do run checkstyle, and as I said, I haven't noticed any > performance problems. However, if I understand correctly from your > snippet, your build hangs in the checkstyle:report-internal goal. This > goal is run after checkstyle has processed the source code and all it > does is generate the xdocs from the checkstyle xml output via some jelly > scripts. So the problem doesn't seem to be related to checkstyle, but I > have no idea what it could be... > > > 2) Do you need to put the emma.jar in your jre lib/ext ??? > > No, I just downloaded the emma plugin (maven plugin:download) and ran > 'maven emma'. No other preparation needed. > > -Lukas > > - > 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]
Active profiles in settings.xml are wrong in maven-embedder
Hi, I've defined in settings.xml file (under M2_HOME/conf/) a profile (my-profile) and set it to be activated. I removed file "C:\Documents and Settings\\.m2\settings.xml". When I run build using maven, it knows to uses my-profile, but when I create a maven project using the maven-embedder, it doesn't have any active profiles. Please help, Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven 1.0.2 to 1.1 beta 3
i get this error while executing the site: [exec] [junitreport] [Fatal Error] :-1:-1: Premature end of file. [exec] [junitreport] The file /subversion/users/svnclient/cruise/checkout/build-module1/modules/com.mycompany.indexing/target/test-reports/TEST-com.mycompany.indexing.framework.batch.MainTest.xml is not a valid XML document. It is possibly corrupted. [exec] [junitreport] [Fatal Error] :-1:-1: Premature end of file. [exec] [junitreport] The file /subversion/users/svnclient/cruise/checkout/build-module1/modules/com.mycompany.indexing/target/test-reports/TEST-com.mycompany.indexing.xmldatafeed.MainTest.xml is not a valid XML document. It is possibly corrupted. the file mentioned has 0 bytes. does anyone have seem this? emerson On 20/04/07, Lukas Theussl <[EMAIL PROTECTED]> wrote: See the bottom of this page: http://maven.apache.org/maven-1.x/using/resources.html HTH, -Lukas emerson cargnin wrote: > actually it was for not having the node insde the > :) and maven 1.0.2 didn't complain of this... > > now i got another challenge. I had the following: > >src/main/java > > >src/main/filters/local.properties > > > but now maven doesn't recognise the tag. > In this page: > http://maven.apache.org/maven-1.x/reference/project-descriptor.html#class_Build > > it just shows a tag, which is only a boolean. How i get > the same behaviour of the other one? > > - 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] adding classpathentry with maven-eclipse-plugin
Solved by adding that classpath using the build-helper-maven-plugin. Thorsten Heit wrote: Hi Adrian, Is there some way to add a classpathentry such as to the .classpath file? It seems that the plugin knows only about classpath containers :-( AFAIK no. The plugin only adds all the dependencies contained in your pom.xml to the .classpath file. Just for curiosity: What's your use case? Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: scm of maven
what is your SCM plugin version? Emmanuel yi bo a écrit : > Hey, all. I can't for the life of me figure out why the CVS SCM provider > can't check out my source files from CVS. I noticed in a couple prior posts > that the CVSNT executable requires a login from the same shell prior to > starting Continuum. I've done this, yet I still get a build error with > "Username isn't defined." as the cause. > > Here's my SCM url with username/password/host sanitized. > > scm:cvs:pserver:myuser:[EMAIL > PROTECTED]:/Root/projects/project001 > > > waiting for your help > > > ___ > 抢注雅虎免费邮箱-3.5G容量,20M附件! > http://cn.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] [WARNING] Removing: java from forked lifecycle, to prevent recursive invocation.
Hi all, Using Maven 2.0.6 and the exec-maven-plugin 1.1-beta-1, the following messages appear during the java goal execution: [INFO] Preparing exec:java [WARNING] Removing: java from forked lifecycle, to prevent recursive invocation. [INFO] No goals needed for project - skipping [INFO] [exec:java {execution: default}] Buildfile: C:\documents\pm\backyard\some-ant-build.xml The effect is that the build lifecycle ends immediately after the execution of the java goal :-( What should I check? Please help, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
scm of maven
Hey, all. I can't for the life of me figure out why the CVS SCM provider can't check out my source files from CVS. I noticed in a couple prior posts that the CVSNT executable requires a login from the same shell prior to starting Continuum. I've done this, yet I still get a build error with "Username isn't defined." as the cause. Here's my SCM url with username/password/host sanitized. scm:cvs:pserver:myuser:[EMAIL PROTECTED]:/Root/projects/project001 waiting for your help ___ 抢注雅虎免费邮箱-3.5G容量,20M附件! http://cn.mail.yahoo.com
[ANN] Clover plugin v2.4 released
The Maven team is pleased to announce the release of the Maven Clover plugin, version 2.4. You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: org.apache.maven.plugins maven-clover-plugin 2.4 Here are the release notes for 2.4: ** Bug * [MCLOVER-45] - Excluded files should be added to compiled sources * [MCLOVER-53] - Clover plugin installs clover instrumented source in local repository * [MCLOVER-66] - The report goal doesn't support a user-provided Clover license * [MCLOVER-68] - XDoclet plugin executes before the Clover plugin in the lifecycle forked by the latter ** Improvement * [MCLOVER-38] - Allow check Mojo to be overriden by a failOnViolation parameter in the same way PMD and Checkstyle can * [MCLOVER-65] - Clover license has expired ** Task * [MCLOVER-67] - Remove deprecated licenseFile configuration parameter Enjoy! -The Maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is maven can auto checkout sourcecode from CVS-Server ?
You can look at the Maven-SCM plugin : http://maven.apache.org/scm/plugins/index.html Emmanuel yi bo a écrit : > Hey: >Everyone!I have paid attention to maven for some time.But now i have > some problems. >Awaiting for your help! > >i want to kown: >Is maven can auto checkout project's sourcecode from CVS-Server ?? > At the same time ,we don't use the tools like cruisecontrol or Continuum . > But we configure the project's pom.xml like: > > > scm:cvs:pserver:name:[EMAIL > PROTECTED]:/root/project1 > scm:cvs:pserver:name:[EMAIL > PROTECTED]:/root/project1 > HEAD > > > > Awaiting for your help! > > > ___ > 抢注雅虎免费邮箱-3.5G容量,20M附件! > http://cn.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Getting index.html of site generated automatically
Ok, just did those things. URL for output is http://rafb.net/p/Kf10Cs17.html There was no particular reason - I guess I got into the habit of it and didn't go back! This output was running "mvn site -X" Regards, Ian - Message from "Wendy Smoak" <[EMAIL PROTECTED]> on Sun, 22 Apr 2007 18:03:52 -0700 - To: "Maven Users List" Subject: Re: Getting index.html of site generated automatically On 4/22/07, Ian Rowlands <[EMAIL PROTECTED]> wrote: > Any other suggestions? Declare a version number for the site plugin: 2.0-beta-5 Then paste the output of 'mvn site -X' (use http://rafb.net/paste as it will be too long to include) and let's see if there's anything interesting in that. Is there any reason you're using site:site (single goal) rather than just 'site' (lifecycle phase)? -- Wendy Disclaimer: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. Privacy: If you are responding to this email or providing personal information to the SRO for the purposes of one of the Acts it administers, such information is used only for the purpose for which it was collected ( administration of SRO legislation ) and is protected by the Information Privacy Act 2000 and secrecy provisions contained in legislation administered by SRO. It is not disclosed otherwise than in accordance with the law. If you would like a copy of the SRO Privacy Policy please refer to SRO website (www.sro.vic.gov.au) or contact SRO on 9628 0556 and request a copy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]