Re: Problem with scopes in dependencies

u can't use the dependecyManagement with dependencies that might be used in other scopes. On Mon, Mar 14, 2011 at 2:49 PM, Benjamin Bentmann wrote: > Emmanuel Hugonnet wrote: > >> How can I display the genuine scope of my dependecy ? > > mvn -X ... > > The debug log will print th

Problem with scopes in dependencies

Hi, I am using Maven 3.0.x (2 or 3= and I have the following problem : I use a parent POM with dependency management which is the good way to do this. We are building for JBoss 4 and JBoss 6 and if for JBoss6 XercesImpl is provided, for JBoss4 it is required with the Assembly Plugin. So in my paren

Bring Maven to the Color age

Hi, I have written a patch for plexus ConsoleLogger (PLX-421) so that Maven's output are colorized if you are using a pseud-terminal and have set the system property 'colorized.console' to 'true'. This could provides a solution to http://jira.codehaus.org/browse/MNG-3507. Emmanuel

http://jira.codehaus.org/browse/MCHANGES-78

Hi, I have updated the code for this enhancement. It parses svn messages to produce the changelog in the site. This way you don't have to maintain a changes.xml file. Now it uses Maven-SCM API and it is Java 1.4 compliant. regards, Emmanuel

Re: Changes plugin contribution

Emmanuel Venisse a écrit : Emmanuel Hugonnet a écrit : zze-HUGONNET E ext RD-BIZZ a écrit : Emmanuel Hugonnet a écrit : Stephane Nicoll a écrit : Hi, Where is the source code of your plugin? If it's valuable we can certainly have a look :) Thanks, Stéphane On 5/3/07, ehsavoie &l

Re: Changes plugin contribution

zze-HUGONNET E ext RD-BIZZ a écrit : Emmanuel Hugonnet a écrit : Stephane Nicoll a écrit : Hi, Where is the source code of your plugin? If it's valuable we can certainly have a look :) Thanks, Stéphane On 5/3/07, ehsavoie <[EMAIL PROTECTED]> wrote: Hi, I have developped a Ma

Re: Changes plugin contribution

Emmanuel Hugonnet a écrit : Stephane Nicoll a écrit : Hi, Where is the source code of your plugin? If it's valuable we can certainly have a look :) Thanks, Stéphane On 5/3/07, ehsavoie <[EMAIL PROTECTED]> wrote: Hi, I have developped a Maven2 plugin that build a report equiva

Re: Changes plugin contribution

Stephane Nicoll a écrit : Hi, Where is the source code of your plugin? If it's valuable we can certainly have a look :) Thanks, Stéphane On 5/3/07, ehsavoie <[EMAIL PROTECTED]> wrote: Hi, I have developped a Maven2 plugin that build a report equivalent to the changes report but which uses svn

Maven - Plexus relationship

Hi, We have a problem with ${basedir} evaluation under M$ Windows which gives us a path mixing \ and / when filtering resources. This seems to be coming from plexus-utils (cf. http://jira.codehaus.org/browse/MRESOURCES-10) and looks corrected since plexus-utils 1.2 :o) So I have tried to upgrad

Re: maven-changes-plugin questions

Jeff Jensen a écrit : I like the changes page as a "simplified, user-friendly" list of notable changes made for each release. The defect/RFE tracking system has the details for the initiated users when desired. Quoting Stephane Nicoll <[EMAIL PROTECTED]>: On 12/27/06, Jason van Zyl <[EMAI

Re: Maven properties evaluation

zze- HUGONNET E ext RD-BIZZ a écrit : Hi, It looks like properties and map, as component, are not evaluated in the same way in Maven. I am setting a MavenProject.property in a Mojo to use it in another one in another phase. If I use a Map to pass this value (a String) all is correct but if I us

Maven properties evaluation

Hi, It looks like properties and map, as component, are not evaluated in the same way in Maven. I am setting a MavenProject.property in a Mojo to use it in another one in another phase. If I use a Map to pass this value (a String) all is correct but if I use a Properties the property is not eva

Re: Maven's classpaths (Was: [discuss] Java 5)

[EMAIL PROTECTED] a écrit : Emmanuel Hugonnet <[EMAIL PROTECTED]> schrieb am 28.11.2006 15:54:34: I have to edit the pom.xml of maven-plugin-tools-java to set the version of qdox to 1.6.1 and then all is fine. Hi, This is a temporary solution I use with a pro

Re: [discuss] Java 5

[EMAIL PROTECTED] a écrit : Emmanuel Hugonnet <[EMAIL PROTECTED]> schrieb am 28.11.2006 14:24:44: I have to edit the pom.xml of maven-plugin-tools-java to set the version of qdox to 1.6.1 and then all is fine. My solution in such a case: - Download the source f

Re: [discuss] Java 5

Tom Huybrechts a écrit : On 11/27/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote: This plugin uses sourcelevel 1.5: https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/repositorytools-maven-plugin ... and it does have non-mojo classes that do not have these constraints (see the components

Re: [discuss] Java 5

Tom Huybrechts a écrit : I write all my mojo's with 1.5. You just need to avoid using annotations and generics in the signature of your classes (fields, methods and their annotations). Tom So maybe you can enlight me ;-) : maven-plugin-tools-java (2.0.1 to 2.0.5-SNAPSHOT) has a dependency on q

Re: [discuss] Java 5

Brett Porter a écrit : This would have zero impact on applications built with Maven. I'd been meaning to follow this up. Let me see what happened with the user survey... - Brett On 26/11/2006, at 12:49 PM, Brian E. Fox wrote: Our experience with our products is that not enough of the avail