Re: how to specify dependencies between test classes

[Tony Chemit]

Le Thu, 18 Jun 2009 11:19:56 -0400,
"Gul Onural"  a écrit :

> 
> Hi,
> 
> In the project I am working on, there is a need to specify
> dependencies between the test source directories.
> 
> The project tree looks like similar to this :
> 
> - componentA
>- src
>   - main
>   - test
> - aCommonComponent
>- src
>   - main
>   - test
> 
> In the JUNIT test cases defined under componentA/test, I want to be
> able to use a Java class defined under aCommonComponent/test.
> Defining a dependency to aCommonComponent inside componentA's pom file
> doesn't help because the class I want to use is under test directory
> of the aCommonComponent.
> 
> What is the proper way of doing this in maven2 ? 
> 
> Thanks,
> 
> Gul
> 
You can expose your aCommonComponent in the classifier test




 maven-jar-plugin
 
   
  attach-test
  
 test-jar
  
  

 



and use it in your componentA


${project.groupId}
aCommonComponent
${project.version}
test
tests


This should works :)

Best regards,

tony.

> -
> This transmission (including any attachments) may contain
> confidential information, privileged material (including material
> protected by the solicitor-client or other applicable privileges), or
> constitute non-public information. Any use of this information by
> anyone other than the intended recipient is prohibited. If you have
> received this transmission in error, please immediately reply to the
> sender and delete this information from your system. Use,
> dissemination, distribution, or reproduction of this transmission by
> unintended recipients is not authorized and may be unlawful.
> 
> -----
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 



-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: change outputfile name

[Tony Chemit]

Le Thu, 18 Jun 2009 08:44:59 -0700 (PDT),
huser  a écrit :

> 
> Hi,
> 
> I have a maven module which builds moduleA-1.0-SNAPSHOT.jar. I need
> the output file name to be moduleA.jar. How can I do this via CLI or
> POM change ?
> 
> Thanks

override the property project.build.finalName will works :) in your pom



moduleA.jar
...



I wonder why it does not work in a commandline ? Any ideas ?

I tried : 

mvn package -Dproject.build.finalName=yo, but still use the default
final name...

For my part, I don't think this is a good idea what you want to do,
since you loose the version information and can not distinguish between
2 versions of your jar... but I'm not a maven expert...

Best regards.

-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: change outputfile name

[Tony Chemit]

Le Thu, 18 Jun 2009 13:14:31 -0400,
"Todd Thiessen"  a écrit :

> I believe changing the finalname property only changes the name of
> the artifact packaged in the target directory. The artifacts
> installed/deployed to the local/remo repos still has the version
> appended.
> 
and your're wright :)

> ---
> Todd Thiessen
>  
> 
> > -Original Message-
> > From: Tony Chemit [mailto:che...@codelutin.com] 
> > Sent: Thursday, June 18, 2009 1:10 PM
> > To: users@maven.apache.org
> > Subject: Re: change outputfile name
> > 
> > Le Thu, 18 Jun 2009 08:44:59 -0700 (PDT), huser 
> >  a écrit :
> > 
> > > 
> > > Hi,
> > > 
> > > I have a maven module which builds moduleA-1.0-SNAPSHOT.jar. I
> > > need the output file name to be moduleA.jar. How can I do this 
> > via CLI or 
> > > POM change ?
> > > 
> > > Thanks
> > 
> > override the property project.build.finalName will works :) 
> > in your pom
> > 
> > 
> > 
> > moduleA.jar
> > ...
> > 
> > 
> > 
> > I wonder why it does not work in a commandline ? Any ideas ?
> > 
> > I tried : 
> > 
> > mvn package -Dproject.build.finalName=yo, but still use the 
> > default final name...
> > 
> > For my part, I don't think this is a good idea what you want 
> > to do, since you loose the version information and can not 
> > distinguish between
> > 2 versions of your jar... but I'm not a maven expert...
> > 
> > Best regards.
> > 
> > -- 
> > 
> > Tony Chemit
> > 
> > tél: +33 (0) 2 40 50 29 28
> > email: che...@codelutin.com
> > http://www.codelutin.com 
> > 
> > -----
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> > 
> > 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 



-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Can not use the plexus component org.sonatype.plexus.components.sec.dispatcher.SecDispatcher since maven 2.2.0

[Tony Chemit]

Hi,

Since maven 2.1.0, I use in a mojo the

org.sonatype.plexus.components.sec.dispatcher.SecDispatcher

from the artifact org.sonatype.plexus:plexus-sec-dispatcher:1.3.1

to decrypt password in my settings.xml

I recently change to maven 2.2.1, but my mojo does not anylonger works fine 
(same result with 2.2.0) :


Caused by: org.codehaus.plexus.component.composition.CompositionException: 
Composition failed of field sec in object of type 
org.nuiton.mail.plugin.SendEmailMojo because the requirement 
ComponentRequirement{role='org.sonatype.plexus.components.sec.dispatcher.SecDispatcher',
 roleHint='default', fieldName='sec'} was missing
at 
org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:154)
at 
org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
at 
org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
at 
org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
at 
org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
... 26 more
Caused by: 
org.codehaus.plexus.component.repository.exception.ComponentLookupException: 
Unable to lookup component 
'org.sonatype.plexus.components.sec.dispatcher.SecDispatcherdefault', it could 
not be started
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:339)
at 
org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:129)
... 30 more
Caused by: 
org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: 
Error starting component
at 
org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:109)
at 
org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95)
at 
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
... 31 more
Caused by: 
org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecutionException: 
Error composing component
at 
org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:33)
at 
org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101)
at 
org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105)
... 34 more
Caused by: org.codehaus.plexus.component.composition.CompositionException: 
Composition failed for the field _cipher in object of type 
org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher
at 
org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:144)
at 
org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
at 
org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
at 
org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
at 
org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
... 36 more
Caused by: java.lang.IllegalArgumentException: Can not set 
org.sonatype.plexus.components.cipher.PlexusCipher field 
org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher._cipher to 
org.sonatype.plexus.components.cipher.DefaultPlexusCipher
at 
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:146)
at 
sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:150)
at 
sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:63)
at java.lang.reflect.Field.set(Field.java:657)
at 
org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:137)
... 40 more

I read in the release note of maven 2.2.0 that something has changed for these 
plexus component, but can't find what ?

What is the catch ? Does I miss something when upgrading to maven 2.2.X ?

Thanks for your replies.

-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

---

Re: Can not use the plexus component org.sonatype.plexus.components.sec.dispatcher.SecDispatcher since maven 2.2.0

[Tony Chemit]

Le Fri, 25 Sep 2009 15:17:04 +0200,
Tony Chemit  a écrit :

> Hi,
> 
> Since maven 2.1.0, I use in a mojo the
> 
> org.sonatype.plexus.components.sec.dispatcher.SecDispatcher
> 
> from the artifact org.sonatype.plexus:plexus-sec-dispatcher:1.3.1
> 
> to decrypt password in my settings.xml
> 
> I recently change to maven 2.2.1, but my mojo does not anylonger works fine
> (same result with 2.2.0) :
> 
> 
> Caused by: org.codehaus.plexus.component.composition.CompositionException:
> Composition failed of field sec in object of type
> org.nuiton.mail.plugin.SendEmailMojo because the requirement
> ComponentRequirement{role='org.sonatype.plexus.components.sec.dispatcher.SecDispatcher',
> roleHint='default', fieldName='sec'} was missing at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:154)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
> at
> org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
> at
> org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
>  ...
> 26 more Caused by:
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Unable to lookup component
> 'org.sonatype.plexus.components.sec.dispatcher.SecDispatcherdefault', it
> could not be started at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:339)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:129)
>  ...
> 30 more Caused by:
> org.codehaus.plexus.component.repository.exception.ComponentLifecycleException:
> Error starting component at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:109)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95)
> at
> org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
> at
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
>  ...
> 31 more Caused by:
> org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecutionException:
> Error composing component at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:33)
> at
> org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:101)
> at
> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:105)
>  ...
> 34 more Caused by:
> org.codehaus.plexus.component.composition.CompositionException: Composition
> failed for the field _cipher in object of type
> org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:144)
> at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent(FieldComponentComposer.java:73)
> at
> org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent(DefaultComponentComposerManager.java:68)
> at
> org.codehaus.plexus.DefaultPlexusContainer.composeComponent(DefaultPlexusContainer.java:1486)
> at
> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute(CompositionPhase.java:29)
>  ...
> 36 more Caused by: java.lang.IllegalArgumentException: Can not set
> org.sonatype.plexus.components.cipher.PlexusCipher field
> org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher._cipher to
> org.sonatype.plexus.components.cipher.DefaultPlexusCipher at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:146)
> at
> sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:150)
> at
> sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:63)
> at java.lang.reflect.Field.set(Field.java:657) at
> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField(FieldComponentComposer.java:137)
>  ...
> 40 more
> 
> I read in the release note of maven 2.2.0 that something has changed for
> these plexus component, but can't find what ?
> 
> What is the catch ? Does I miss something when upgr

Re: Can not use the plexus component org.sonatype.plexus.components.sec.dispatcher.SecDispatcher since maven 2.2.0

[Tony Chemit]

Le Mon, 28 Sep 2009 09:35:00 +1000,
Brett Porter  a écrit :

> It looks like when they were added, they were not properly "hidden"  
> from plugin classes. So you will need to ensure you use the exact  
> version of the library that is used in Maven.
>
On which artifact should I look on ? maven-core ?
 
> Please report this at http://jira.codehaus.org/browse/MNG so it can be  
> corrected in future.
> 
ok I will do this.

> Thanks,
> Brett
> 
> On 26/09/2009, at 3:19 AM, Tony Chemit wrote:
> 
> > Le Fri, 25 Sep 2009 15:17:04 +0200,
> > Tony Chemit  a écrit :
> >
> >> Hi,
> >>
> >> Since maven 2.1.0, I use in a mojo the
> >>
> >> org.sonatype.plexus.components.sec.dispatcher.SecDispatcher
> >>
> >> from the artifact org.sonatype.plexus:plexus-sec-dispatcher:1.3.1
> >>
> >> to decrypt password in my settings.xml
> >>
> >> I recently change to maven 2.2.1, but my mojo does not anylonger  
> >> works fine
> >> (same result with 2.2.0) :
> >>
> >>
> >> Caused by:  
> >> org.codehaus.plexus.component.composition.CompositionException:
> >> Composition failed of field sec in object of type
> >> org.nuiton.mail.plugin.SendEmailMojo because the requirement
> >> ComponentRequirement 
> >> {role='org.sonatype.plexus.components.sec.dispatcher.SecDispatcher',
> >> roleHint='default', fieldName='sec'} was missing at
> >> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField
> >>  
> >> (FieldComponentComposer.java:154)
> >> at
> >> org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent
> >>  
> >> (FieldComponentComposer.java:73)
> >> at
> >> org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent
> >>  
> >> (DefaultComponentComposerManager.java:68)
> >> at
> >> org.codehaus.plexus.DefaultPlexusContainer.composeComponent 
> >> (DefaultPlexusContainer.java:1486)
> >> at
> >> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute
> >>  
> >> (CompositionPhase.java:29) ...
> >> 26 more Caused by:
> >> org.codehaus.plexus.component.repository.exception.ComponentLookupException
> >>  
> >> :
> >> Unable to lookup component
> >> 'org.sonatype.plexus.components.sec.dispatcher.SecDispatcherdefault 
> >> ', it
> >> could not be started at
> >> org.codehaus.plexus.DefaultPlexusContainer.lookup 
> >> (DefaultPlexusContainer.java:339)
> >> at
> >> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField
> >>  
> >> (FieldComponentComposer.java:129) ...
> >> 30 more Caused by:
> >> org.codehaus.plexus.component.repository.exception.ComponentLifecycleException
> >>  
> >> :
> >> Error starting component at
> >> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle
> >>  
> >> (AbstractComponentManager.java:109)
> >> at
> >> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance
> >>  
> >> (AbstractComponentManager.java:95)
> >> at
> >> org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent
> >>  
> >> (ClassicSingletonComponentManager.java:92)
> >> at
> >> org.codehaus.plexus.DefaultPlexusContainer.lookup 
> >> (DefaultPlexusContainer.java:331) ...
> >> 31 more Caused by:
> >> org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecutionException
> >>  
> >> :
> >> Error composing component at
> >> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute
> >>  
> >> (CompositionPhase.java:33)
> >> at
> >> org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start 
> >> (AbstractLifecycleHandler.java:101)
> >> at
> >> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle
> >>  
> >> (AbstractComponentManager.java:105) ...
> >> 34 more Caused by:
> >> org.codehaus.plexus.component.composition.CompositionException:  
> >> Composition
> >> failed for the field _cipher in object of type
> >> org.sonatype.plexus.components.sec.dispatcher.DefaultSecDispatcher at
> >> org.codehaus.plexus.compo

Re: Can not use the plexus component org.sonatype.plexus.components.sec.dispatcher.SecDispatcher since maven 2.2.0

[Tony Chemit]

Le Mon, 28 Sep 2009 09:43:06 +0200,
Tony Chemit  a écrit :

> Le Mon, 28 Sep 2009 09:35:00 +1000,
> Brett Porter  a écrit :
> 
> > It looks like when they were added, they were not properly "hidden"  
> > from plugin classes. So you will need to ensure you use the exact  
> > version of the library that is used in Maven.
> >
> On which artifact should I look on ? maven-core ?
>  
> > Please report this at http://jira.codehaus.org/browse/MNG so it can be  
> > corrected in future.
> > 
> ok I will do this.
> 
done in http://jira.codehaus.org/browse/MNG-4384 


> > Thanks,
> > Brett
> > 
> > On 26/09/2009, at 3:19 AM, Tony Chemit wrote:
> > 
> > > Le Fri, 25 Sep 2009 15:17:04 +0200,
> > > Tony Chemit  a écrit :
> > >
> > >> Hi,
> > >>
> > >> Since maven 2.1.0, I use in a mojo the
> > >>
> > >> org.sonatype.plexus.components.sec.dispatcher.SecDispatcher
> > >>
> > >> from the artifact org.sonatype.plexus:plexus-sec-dispatcher:1.3.1
> > >>
> > >> to decrypt password in my settings.xml
> > >>
> > >> I recently change to maven 2.2.1, but my mojo does not anylonger  
> > >> works fine
> > >> (same result with 2.2.0) :
> > >>
> > >>
> > >> Caused by:  
> > >> org.codehaus.plexus.component.composition.CompositionException:
> > >> Composition failed of field sec in object of type
> > >> org.nuiton.mail.plugin.SendEmailMojo because the requirement
> > >> ComponentRequirement 
> > >> {role='org.sonatype.plexus.components.sec.dispatcher.SecDispatcher',
> > >> roleHint='default', fieldName='sec'} was missing at
> > >> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField
> > >>  
> > >> (FieldComponentComposer.java:154)
> > >> at
> > >> org.codehaus.plexus.component.composition.FieldComponentComposer.assembleComponent
> > >>  
> > >> (FieldComponentComposer.java:73)
> > >> at
> > >> org.codehaus.plexus.component.composition.DefaultComponentComposerManager.assembleComponent
> > >>  
> > >> (DefaultComponentComposerManager.java:68)
> > >> at
> > >> org.codehaus.plexus.DefaultPlexusContainer.composeComponent 
> > >> (DefaultPlexusContainer.java:1486)
> > >> at
> > >> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute
> > >>  
> > >> (CompositionPhase.java:29) ...
> > >> 26 more Caused by:
> > >> org.codehaus.plexus.component.repository.exception.ComponentLookupException
> > >>  
> > >> :
> > >> Unable to lookup component
> > >> 'org.sonatype.plexus.components.sec.dispatcher.SecDispatcherdefault 
> > >> ', it
> > >> could not be started at
> > >> org.codehaus.plexus.DefaultPlexusContainer.lookup 
> > >> (DefaultPlexusContainer.java:339)
> > >> at
> > >> org.codehaus.plexus.component.composition.FieldComponentComposer.assignRequirementToField
> > >>  
> > >> (FieldComponentComposer.java:129) ...
> > >> 30 more Caused by:
> > >> org.codehaus.plexus.component.repository.exception.ComponentLifecycleException
> > >>  
> > >> :
> > >> Error starting component at
> > >> org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle
> > >>  
> > >> (AbstractComponentManager.java:109)
> > >> at
> > >> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance
> > >>  
> > >> (AbstractComponentManager.java:95)
> > >> at
> > >> org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent
> > >>  
> > >> (ClassicSingletonComponentManager.java:92)
> > >> at
> > >> org.codehaus.plexus.DefaultPlexusContainer.lookup 
> > >> (DefaultPlexusContainer.java:331) ...
> > >> 31 more Caused by:
> > >> org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecutionException
> > >>  
> > >> :
> > >> Error composing component at
> > >> org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPhase.execute
> > >>  
> > >> (Composi

Re: Get dependencies in generate-sources phase?

[Tony Chemit]

Le Wed, 30 Sep 2009 16:27:54 +0200,
"Lewis, Eric"  a écrit :

> Hi
> 
> I'm trying to access my project's classpath in a plugin I'm writing, which
> should generate JPA's persistence.xml file from JPA entities found on the
> classpath. To work, this should run during the generate-sources phase, but do
> I have access to the projects dependencies (transivite dependencies, if
> possible) at that point?
> 
> Best regards,
> Eric
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 

You can use the annotation @requiresDependencyResolution  
[0] on your mojo

Then you should be able to access the project dependencies


[0] 
http://www.sonatype.com/books/maven-book/reference/writing-plugins-sect-class-annotations.html
 
-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Is a Mojo default execution goal possible, leaving out the executions goal part in the pom?

[Tony Chemit]

Le Wed, 14 Oct 2009 12:30:28 +0200,
Martijn Morriën  a écrit :

> Hi,
> 
> I'm writing a mojo that generates source files. Is it possible to get rid of
> the required executions part in the pom?
> My mojo already defines it should be used in the generate-sources phase. And
> my plugin only contains 1 mojo.
> 
> /**
>  * @goal mycodegenerator
>  * @phase generate-sources
>  * @requiresProject false
>  */
> public class MyCodeGenerator extends AbstractMojo
> 
> I use it as follows:
> 
>   
> 
>   
> mytest
> mycodegenerator
> 0.0.1-SNAPSHOT
> 
>   
> 
>   mycodegenerator
> 
>   
> 
>   
> 
>   
> 
> I would prefer to us it as follows, but it doesn't work for me:
> 
>   
> 
>   
> mytest
> mycodegenerator
> 0.0.1-SNAPSHOT
>   
> 
>   
> 
> Is this possible? I do not want to introduce a new packaging type.
> 
> Thank you, Martijn

You want to modify the default lifecycle mappings to integrate your goal for a 
given phase.

The lifecycle is explained in the maven guide [1] .

Have a look at [2] which explain how to do this.

Tony.

[1] http://www.sonatype.com/books/maven-book/reference/lifecycle.html 

[2] 
http://www.sonatype.com/people/2009/08/create-a-customized-build-process-in-maven/

-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Is a Mojo default execution goal possible, leaving out the executions goal part in the pom?

[Tony Chemit]

Le Wed, 14 Oct 2009 13:02:20 +0200,
Martijn Morriën  a écrit :

> On Wed, Oct 14, 2009 at 12:40, Tony Chemit  wrote:
> 
> > Le Wed, 14 Oct 2009 12:30:28 +0200,
> > Martijn Morriën  a écrit :
> >
> > > Hi,
> > >
> > > I'm writing a mojo that generates source files. Is it possible to get rid
> > of
> > > the required executions part in the pom?
> > > My mojo already defines it should be used in the generate-sources phase.
> > And
> > > my plugin only contains 1 mojo.
> > >
> > > /**
> > >  * @goal mycodegenerator
> > >  * @phase generate-sources
> > >  * @requiresProject false
> > >  */
> > > public class MyCodeGenerator extends AbstractMojo
> > >
> > > I use it as follows:
> > >
> > >   
> > > 
> > >   
> > > mytest
> > > mycodegenerator
> > > 0.0.1-SNAPSHOT
> > > 
> > >   
> > > 
> > >   mycodegenerator
> > > 
> > >   
> > > 
> > >   
> > > 
> > >   
> > >
> > > I would prefer to us it as follows, but it doesn't work for me:
> > >
> > >   
> > > 
> > >   
> > > mytest
> > > mycodegenerator
> > > 0.0.1-SNAPSHOT
> > >   
> > > 
> > >   
> > >
> > > Is this possible? I do not want to introduce a new packaging type.
> > >
> > > Thank you, Martijn
> >
> > You want to modify the default lifecycle mappings to integrate your goal
> > for a given phase.
> >
> > The lifecycle is explained in the maven guide [1] .
> >
> > Have a look at [2] which explain how to do this.
> >
> > Tony.
> >
> > [1] http://www.sonatype.com/books/maven-book/reference/lifecycle.html
> >
> > [2]
> > http://www.sonatype.com/people/2009/08/create-a-customized-build-process-in-maven/
> >
> > --
> >
> > Tony Chemit
> > 
> > tél: +33 (0) 2 40 50 29 28
> > email: che...@codelutin.com
> > http://www.codelutin.com
> >
> > ---------
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> Thank you Tony,
> 
> I've looked and tested my own lifecycle definition, however it requires the
> change of a packaging type. or am I wrong?
> I do not want to change the packaging type. So should I redefine existing
> packaging types I want to support?
> E.g. if I want to support jar, is it allowed to use
> jar ?
I don't known in fact (I have not done this yet :)), but it must be able to use 
the jar role-hint in the default lifecycle ?

> 
> Martijn



-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Is a Mojo default execution goal possible, leaving out the executions goal part in the pom?

[Tony Chemit]

Le Wed, 14 Oct 2009 13:15:35 +0200,
Tony Chemit  a écrit :

> Le Wed, 14 Oct 2009 13:02:20 +0200,
> Martijn Morriën  a écrit :
> 
> > On Wed, Oct 14, 2009 at 12:40, Tony Chemit  wrote:
> > 
> > > Le Wed, 14 Oct 2009 12:30:28 +0200,
> > > Martijn Morriën  a écrit :
> > >
> > > > Hi,
> > > >
> > > > I'm writing a mojo that generates source files. Is it possible to get
> > > > rid
> > > of
> > > > the required executions part in the pom?
> > > > My mojo already defines it should be used in the generate-sources phase.
> > > And
> > > > my plugin only contains 1 mojo.
> > > >
> > > > /**
> > > >  * @goal mycodegenerator
> > > >  * @phase generate-sources
> > > >  * @requiresProject false
> > > >  */
> > > > public class MyCodeGenerator extends AbstractMojo
> > > >
> > > > I use it as follows:
> > > >
> > > >   
> > > > 
> > > >   
> > > > mytest
> > > > mycodegenerator
> > > > 0.0.1-SNAPSHOT
> > > > 
> > > >   
> > > > 
> > > >   mycodegenerator
> > > > 
> > > >   
> > > > 
> > > >   
> > > > 
> > > >   
> > > >
> > > > I would prefer to us it as follows, but it doesn't work for me:
> > > >
> > > >   
> > > > 
> > > >   
> > > > mytest
> > > > mycodegenerator
> > > > 0.0.1-SNAPSHOT
> > > >   
> > > >     
> > > >   
> > > >
> > > > Is this possible? I do not want to introduce a new packaging type.
> > > >
> > > > Thank you, Martijn
> > >
> > > You want to modify the default lifecycle mappings to integrate your goal
> > > for a given phase.
> > >
> > > The lifecycle is explained in the maven guide [1] .
> > >
> > > Have a look at [2] which explain how to do this.
> > >
> > > Tony.
> > >
> > > [1] http://www.sonatype.com/books/maven-book/reference/lifecycle.html
> > >
> > > [2]
> > > http://www.sonatype.com/people/2009/08/create-a-customized-build-process-in-maven/
> > >
> > > --
> > >
> > > Tony Chemit
> > > 
> > > tél: +33 (0) 2 40 50 29 28
> > > email: che...@codelutin.com
> > > http://www.codelutin.com
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: users-h...@maven.apache.org
> > >
> > >
> > Thank you Tony,
> > 
> > I've looked and tested my own lifecycle definition, however it requires the
> > change of a packaging type. or am I wrong?
> > I do not want to change the packaging type. So should I redefine existing
> > packaging types I want to support?
> > E.g. if I want to support jar, is it allowed to use
> > jar ?
> I don't known in fact (I have not done this yet :)), but it must be able to
> use the jar role-hint in the default lifecycle ?
> 
Sorry for the false hope... It seems not to be able to override an already 
defined lifecycle.

My idea was to override the default lifecycle for the jar role-hint (I just try 
it and it does not works...)

Moreover I read in [3] this : 



So it is explicit :)

> > 
> > Martijn
> 
> 
> 


[3] 
http://svn.apache.org/repos/asf/maven/maven-2/tags/maven-2.2.0/maven-core/src/main/resources/META-INF/plexus/components.xml
 
-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [FATAL ERROR] SiteMojo#execute() caused a linkage error (NoClassDefFoundError: org/apache/commons/lang/ArrayUtils)

[Tony Chemit]

gt; org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.evaluate(ASTReference.java:396)
> at
> org.apache.velocity.runtime.parser.node.ASTOrNode.evaluate(ASTOrNode.java:99)
> at
> org.apache.velocity.runtime.parser.node.ASTExpression.evaluate(ASTExpression.java:64)
> at
> org.apache.velocity.runtime.parser.node.ASTNotNode.evaluate(ASTNotNode.java:64)
> at
> org.apache.velocity.runtime.parser.node.ASTExpression.evaluate(ASTExpression.java:64)
> at
> org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:86)
> at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74)
> at
> org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:88)
> at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74)
> at
> org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:88)
> at
> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318)
> at
> org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:194)
> at
> org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170)
> at
> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318)
> at org.apache.velocity.Template.merge(Template.java:254) at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.processTemplate(DefaultSiteRenderer.java:542)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.writeTemplate(DefaultSiteRenderer.java:508)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.generateDocument(DefaultSiteRenderer.java:485)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:176)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
> at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) at
> org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at
> org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at
> java.lang.reflect.Method.invoke(Unknown Source) at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at
> org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at
> org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by:
> java.lang.ClassNotFoundException: org.apache.commons.lang.ArrayUtils at
> java.net.URLClassLoader$1.run(Unknown Source) at
> java.security.AccessController.doPrivileged(Native Method) at
> java.net.URLClassLoader.findClass(Unknown Source) at
> java.lang.ClassLoader.loadClass(Unknown Source) at
> org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195)
> at
> org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255)
> at
> org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274)
> at
> org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214)
> at java.lang.ClassLoader.loadClass(Unknown Source) at
> java.lang.ClassLoader.loadClassInternal(Unknown Source) ... 44 more
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 



-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [FATAL ERROR] SiteMojo#execute() caused a linkage error (NoClassDefFoundError: org/apache/commons/lang/ArrayUtils)

[Tony Chemit]

Le Fri, 23 Oct 2009 20:47:21 +0100,
Niall Pemberton  a écrit :

> Merci Beaucoup - thats fixed it. Still not sure why it just started
> happening though.
> 
You're welcome.

Have you try to clean your local repository ? this could fix your problem ?

> Niall
> 
> On Fri, Oct 23, 2009 at 8:18 PM, Tony Chemit  wrote:
> > Le Fri, 23 Oct 2009 20:04:32 +0100,
> > Niall Pemberton  a écrit :
> >
> >> I'm getting the following error when I try to run mvn site on Commons
> >> Beanutils[1]
> >>
> >> I'm using maven 2.2.1 - it was working fine a week or so ago. I've
> >> been playing with maven 3.x though and have just switched back to
> >> 2.2.1, so I'm wondering if thats the cause. Any ideas
> >>
> >> I've searched the archives and this type of error seems to come up
> >> quite a but, but
> >>
> >> Niall
> >
> > Hi,
> >
> > I already had this problem, There is a pb with the dependency of
> > commons-lang used somewhere in site plugin dependencies, I just add a
> > dependency to site-plugin with a version of commons-lang which include the
> > method (the version 2.4 works fine).
> >
> > Tony.
> >
> >
> >>
> >>
> >> [1] http://svn.apache.org/repos/asf/commons/proper/beanutils/trunk/
> >>
> >>
> >> [INFO] Generating "Project Team" report.
> >> [FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused
> >> a linkage error (java.lang.NoClassDefFoundError) and may be
> >> out-of-date. Check the realms:
> >> [FATAL ERROR] Plugin realm =
> >> app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.0.1]
> >> urls[0] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.0.1/maven-site-plugin-2.0.1.jar
> >> urls[1] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar
> >> urls[2] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.0/doxia-module-xhtml-1.0.jar
> >> urls[3] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-core/1.0/doxia-core-1.0.jar
> >> urls[4] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0/doxia-decoration-model-1.0.jar
> >> urls[5] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.0/doxia-site-renderer-1.0.jar
> >> urls[6] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
> >> urls[7] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar
> >> urls[8] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
> >> urls[9] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
> >> urls[10] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/commons-lang/commons-lang/2.1/commons-lang-2.1.jar
> >> urls[11] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
> >> urls[12] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.0/doxia-module-apt-1.0.jar
> >> urls[13] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.0/doxia-module-fml-1.0.jar
> >> urls[14] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.0/doxia-module-xdoc-1.0.jar
> >> urls[15] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.0.2/maven-doxia-tools-1.0.2.jar
> >> urls[16] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
> >> urls[17] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
> >> urls[18] = file:/C:/Documents and
> >> Settings/niall.pemberton/.m2/repository/org/mortbay/

Re: Not a v4.0.0 POM error

[Tony Chemit]

Le Wed, 11 Nov 2009 17:00:51 -0600,
Gerardo Corro  a écrit :

> 
> Hi all,
> 
> 
> Today, I was using Maven as usual in my Ubuntu laptop, then I decided to
> update Ubuntu to the 9.10 version, after that I tried to use maven as usual
> but now I get this error all the times I try to compile or install anything:
> 

I suggest you to delete the directory in your local repository

/data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/

anyway, for me nothing to see with ubuntu (I works on it too)

I already had such errors when a download of an artifact failed (for multiple 
reason...)

hope it will help you.

Cheers,

Tony.

> 
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '��
' - RETRYING
> Downloading:
> https://www.mycomp.com/maven2/repository/public/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> 1K downloaded  (maven-install-plugin-2.3.pom) [WARNING] *** CHECKSUM FAILED -
> Checksum failed on download: local =
> 'e6084a3bb5d435dcb42378cd3273f5db433cb944'; remote = '��
' - IGNORING [INFO]
> 
> [ERROR] BUILD ERROR [INFO]
> 
> [INFO] Error building POM (may not be this project's POM).
> 
> 
> Project ID: org.apache.maven.plugins:maven-install-plugin
> POM
> Location: 
> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> 
> Reason: Not a v4.0.0 POM. for project
> org.apache.maven.plugins:maven-install-plugin
> at 
> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> 
> 
> 
> if using the -e version I get:
> 
> [INFO]
> 
> [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable
> to build project for plugin 'org.apache.maven.plugins:maven-install-plugin':
> Not a v4.0.0 POM. for project org.apache.maven.plugins:maven-install-plugin
> at 
> /data/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1557)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1851)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1275)
> 
> 
> 
> Caused by: org.apache.maven.plugin.InvalidPluginException: Unable to build
> project for plugin 'org.apache.maven.plugins:maven-install-plugin': Not a
> v4.0.0 POM. for project org.apache.maven.plugins:maven-install-plugin
> at 
> /data/colibria/repository/org/apache/maven/plugins/maven-install-plugin/2.3/maven-install-plugin-2.3.pom
> at
> org.apache.maven.plugin.DefaultPluginManager.checkRequiredMavenVersion(DefaultPluginManager.java:293)
> at
> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:205)
> 
> 
> 
> Please assist. Thanks!
> 
> 
> 
> 
> 
> 
> _____
> Windows Live: Keep your friends up to date with what you do online.
> http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_1:092010


-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Using property name/value to activate profile

[Tony Chemit]

Le Wed, 11 Nov 2009 18:07:31 -0500,
Yaakov Chaikin  a écrit :

> Hmm... Just tried specifying false in my
> settings.xml and it STILL does NOT activate any profiles! Anyone has
> any idea of what's going on here?
> 
> Thanks in advance for your help.
> 
It seems weird to me to use 2 profile to do the same thing ?

why do you want to use 2 profiles ? Moreover why using a profile ?

Could you not just use your property createDb ? and override it in your child 
pom ?

Can you post the complete example of your poms and give the maven version you 
are using, it could help I think.

Sorry to not have a magic solution for you (perharps a maven expert could you 
help you more...)

Cheers,

Tony.

> Yaakov.
> 
> On Wed, Nov 11, 2009 at 5:44 PM, Yaakov Chaikin
>  wrote:
> > Hi,
> >
> > I am clearly not understanding how properties propagate in maven...
> >
> > I have a multi-module project where I have a root pom.xml
> > (pom) and a number of child modules.
> >
> > In my root pom.xml I have this:
> > 
> >  false
> > 
> >
> >
> > In one of the my child module's pom.xml I have the following:
> >
> > ...
> > 
> >  
> >    SkipDbCreationIsTrue
> >    
> >        
> >           createDb
> >           false
> >        
> >     
> >     
> >         true
> >     
> >   
> >
> >    
> >    SkipDbCreationIsFalse
> >    
> >        
> >           createDb
> >           true
> >        
> >     
> >     
> >         false
> >     
> >   
> > 
> > ...
> >
> > When I do mvn help:active-profiles neither of these profiles are
> > active! However, when I specify the property directly on the command
> > line, depending on its value, the correct profile gets activated. It's
> > as if 'createDb' property, which I am using to do activation, is not
> > there at the time maven decides which profiles to use.
> >
> > I could place the 'createDb' property into settings.xml, but I don't
> > want to do that for reasons outside the scope of this question.
> >
> > Can anyone spot what I am doing wrong here? I already checked the
> > spelling of the property in both places and it's correct...
> >
> > Any ideas anyone?
> >
> > Thanks,
> > Yaakov.
> >
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 



-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Accessing MavenSession from a plugin component

[Tony Chemit]

Le Fri, 1 Jan 2010 01:25:21 +0100,
Olivier Lamy  a écrit :

> Hi,
> 
> Maybe :
> 
> /**
>  * The Maven Session Object
>  *
>  * @parameter expression="${session}"
>  * @required
>  * @readonly
>  */
> protected MavenSession session;
> 
> ?
> 
and for sure adding the maven-core as a dependency of your mojo artifact ?
> HTH,
> --
> Olivier
> 
> 2009/12/31 Stevo Slavić :
> > Hello Maven users,
> >
> > Can anyone please point me to some docs or example on how one can access a
> > maven session from a plugin plexus.component?
> >
> > Regards,
> > Stevo.
> >
> 
> 
> 



-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Multi Module: Deploy and failing modules

[Tony Chemit]

Le Thu, 07 Jan 2010 17:04:30 +0100,
Johannes Schneider  a écrit :

> Hi,
> 
> how do you solve that scenario:
> 
> Multi module project that I try to deploy/install after a refactoring.
> Unfortunately one of the later modules fails. Now I have some sort of
> inconsistent snapshot repository. The artifacts within are no longer
> compatible.
> 
> I'd prefer a method that first builds all modules and then deploys them
> together...
> 
You can do a mvn install and if everything is ok then do a mvn deploy ?

I don't think there is another way to do it...
-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Problems with Dependencies and Classpath

[Tony Chemit]

Le Mon, 8 Mar 2010 15:03:07 +0100,
"Matthias Hofmann"  a écrit :

> Hi,
> 
> currently i am trying to get my Java program running outside of the
> Netbeans IDE. Within Netbeans, it works well, all dependencies are
> correctly loaded and executed.
> But if i try to run the program from the console with java -cp or java
> -jar, i get NoClassFoundDefError concerning the dependencies of the
> project.
> 
- Use the plugin dependencies to obtain all required jar (for example put it in 
target/lib)


maven-dependency-plugin



copy-dependencies



${project.build.directory}/lib





- then in jar plugin tells it to use your prefix


maven-jar-plugin



...omitted...
true
./lib/





Then you can launch your application via java -jar tar/XXX.jar

Works fine for us :) hope it will help you.


> My pom.xml uses
> 
> 
> org.apache.maven.plugins
> maven-jar-plugin
> 
> 
> 
> ...omitted...
> true
> 
> 
> 
> 
> 
> as buildoptions
> 
> Any ideas concerning this issue? Most likely, sth. with the classpath is
> wrong, but i can't figure it out.
> 
> Best regards and thank you,
> 
> Matthias
> 
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 



-- 

Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: junit 4.8.1 - org.junit cannot be resolved

[Tony Chemit]

Le Wed, 28 Apr 2010 09:59:05 +0200,
Dirk Olmes  a écrit :

> On 04/28/2010 08:46 AM, ykyuen wrote:
> > 
> > i try to use junit 4.8.1 in my maven project by adding the following
> > dependency in the pom.xml
> > 
> >junit
> >junit
> >4.8.1
> >test
> > 
> > 
> > when i try to write the test case, the org.junit cannot be resolved(i.e.
> > error at "import org.junit.Assert"). but if i change the junit version to
> > 4.7. no problem at all.
> > 
> > did i do anything wrong?
When you have this error, is it in a IDEA ? or when you launch a maven build ?

> 
> No, it's just that JUnit 4.8.1 isn't available in the central repo (for
> now).

I can see it on central here : 

http://repo1.maven.org/maven2/junit/junit/4.8.1/ 

> 
> -dirk
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: junit 4.8.1 - org.junit cannot be resolved

[Tony Chemit]

Le Wed, 28 Apr 2010 10:52:48 +0200,
Nick Stolwijk  a écrit :

> It seems the 4.8.1 version in central is borked. It doesn't contain
> any classes. That would explain why your imports can't be resolved. I
> don't know who did the upload of this artifact, but it is certainly
> wrong.
Nope, there is some classes inside the jar.

For me there is nothing wrong with the artifact on central.

> 
> With regards,
> 
> Nick Stolwijk
> ~Java Developer~
> 
> IPROFS BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> http://www.iprofs.nl
> 
> 
> 
> On Wed, Apr 28, 2010 at 10:22 AM, ykyuen  wrote:
> >
> > Yes. i can see the junit-4.8.1.jar in "Maven Dependencies" of my eclipse
> > project. so i am sure the maven did download the 4.8.1 jar.
> >
> >
> >
> > Tony Chemit wrote:
> >>
> >> Le Wed, 28 Apr 2010 09:59:05 +0200,
> >> Dirk Olmes  a écrit :
> >>
> >>> On 04/28/2010 08:46 AM, ykyuen wrote:
> >>> >
> >>> > i try to use junit 4.8.1 in my maven project by adding the following
> >>> > dependency in the pom.xml
> >>> > 
> >>> >    junit
> >>> >    junit
> >>> >    4.8.1
> >>> >    test
> >>> > 
> >>> >
> >>> > when i try to write the test case, the org.junit cannot be
> >>> resolved(i.e.
> >>> > error at "import org.junit.Assert"). but if i change the junit version
> >>> to
> >>> > 4.7. no problem at all.
> >>> >
> >>> > did i do anything wrong?
> >> When you have this error, is it in a IDEA ? or when you launch a maven
> >> build ?
> >>
> >>>
> >>> No, it's just that JUnit 4.8.1 isn't available in the central repo (for
> >>> now).
> >>
> >> I can see it on central here :
> >>
> >> http://repo1.maven.org/maven2/junit/junit/4.8.1/
> >>
> >>>
> >>> -dirk
> >>>
> >>> -
> >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >>> For additional commands, e-mail: users-h...@maven.apache.org
> >>>
> >>
> >>
> >>
> >> --
> >> Tony Chemit
> >> 
> >> tél: +33 (0) 2 40 50 29 28
> >> email: che...@codelutin.com
> >> http://www.codelutin.com
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >>
> >
> > --
> > View this message in context: 
> > http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28386045.html
> > Sent from the Maven - Users mailing list archive at Nabble.com.
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: junit 4.8.1 - org.junit cannot be resolved

[Tony Chemit]

Le Wed, 28 Apr 2010 11:07:02 +0200,
Nick Stolwijk  a écrit :

> That depends on where you look. ;)
> 
> Take a look at 
> http://repository.sonatype.org/index.html#nexus-search;gav~~junit~4.8.1~~
> 
> That one certainly is borked. See also the jira issue in my other
> mail. There are different versions of this artifact in
> central/mirrors. As long as not all mirrors purge their old version, I
> wouldn't trust this version. Normally, central had a very strict
> policy, what is on central, stays on central, but it seems someone
> slipped this time.
> 
Ok I tought that only http://repo1.maven.org/maven2/ was central, and mirrors 
could be cleaned. (but still respects the policy of central)...


> With regards,
> 
> Nick Stolwijk
> ~Java Developer~
> 
> IPROFS BV.
> Claus Sluterweg 125
> 2012 WS Haarlem
> http://www.iprofs.nl
> 
> 
> 
> On Wed, Apr 28, 2010 at 11:01 AM, Tony Chemit  wrote:
> > Le Wed, 28 Apr 2010 10:52:48 +0200,
> > Nick Stolwijk  a écrit :
> >
> >> It seems the 4.8.1 version in central is borked. It doesn't contain
> >> any classes. That would explain why your imports can't be resolved. I
> >> don't know who did the upload of this artifact, but it is certainly
> >> wrong.
> > Nope, there is some classes inside the jar.
> >
> > For me there is nothing wrong with the artifact on central.
> >
> >>
> >> With regards,
> >>
> >> Nick Stolwijk
> >> ~Java Developer~
> >>
> >> IPROFS BV.
> >> Claus Sluterweg 125
> >> 2012 WS Haarlem
> >> http://www.iprofs.nl
> >>
> >>
> >>
> >> On Wed, Apr 28, 2010 at 10:22 AM, ykyuen  wrote:
> >> >
> >> > Yes. i can see the junit-4.8.1.jar in "Maven Dependencies" of my eclipse
> >> > project. so i am sure the maven did download the 4.8.1 jar.
> >> >
> >> >
> >> >
> >> > Tony Chemit wrote:
> >> >>
> >> >> Le Wed, 28 Apr 2010 09:59:05 +0200,
> >> >> Dirk Olmes  a écrit :
> >> >>
> >> >>> On 04/28/2010 08:46 AM, ykyuen wrote:
> >> >>> >
> >> >>> > i try to use junit 4.8.1 in my maven project by adding the following
> >> >>> > dependency in the pom.xml
> >> >>> > 
> >> >>> >    junit
> >> >>> >    junit
> >> >>> >    4.8.1
> >> >>> >    test
> >> >>> > 
> >> >>> >
> >> >>> > when i try to write the test case, the org.junit cannot be
> >> >>> resolved(i.e.
> >> >>> > error at "import org.junit.Assert"). but if i change the junit 
> >> >>> > version
> >> >>> to
> >> >>> > 4.7. no problem at all.
> >> >>> >
> >> >>> > did i do anything wrong?
> >> >> When you have this error, is it in a IDEA ? or when you launch a maven
> >> >> build ?
> >> >>
> >> >>>
> >> >>> No, it's just that JUnit 4.8.1 isn't available in the central repo (for
> >> >>> now).
> >> >>
> >> >> I can see it on central here :
> >> >>
> >> >> http://repo1.maven.org/maven2/junit/junit/4.8.1/
> >> >>
> >> >>>
> >> >>> -dirk
> >> >>>
> >> >>> -
> >> >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> >>> For additional commands, e-mail: users-h...@maven.apache.org
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Tony Chemit
> >> >> 
> >> >> tél: +33 (0) 2 40 50 29 28
> >> >> email: che...@codelutin.com
> >> >> http://www.codelutin.com
> >> >>
> >> >> -
> >> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> >> For additional commands, e-mail: users-h...@maven.apache.org
> >> >>
> >> >>
> >> >>
> >> >
> >> > --
> >> > View this message in context: 
> >> > http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28386045.html
> >> > Sent from the Maven - Users mailing list archive at Nabble.com.
> >> >
> >> >
> >> > -
> >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> > For additional commands, e-mail: users-h...@maven.apache.org
> >> >
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >
> >
> >
> > --
> > Tony Chemit
> > 
> > tél: +33 (0) 2 40 50 29 28
> > email: che...@codelutin.com
> > http://www.codelutin.com
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Skip tests on release

[Tony Chemit]

Le Tue, 10 Aug 2010 12:32:55 -0400,
"C. Benson Manica"  a écrit :

> mvn -DskipTests=true -Dmaven.test.skip=true release:perform still insists on
> running the unit tests.  Why?  They already ran on release:prepare, I
> really, really, really get annoyed sitting through five minutes of unit
> tests that I know pass because I just ran them.
> 

When doing a mvn release:perform, the plugin just launch another instance of 
maven with by default this command : 

mvn deploy site-deploy -DperformRelease

So you will never be able to change this behaviour like you are trying to do.

To make this possible you can use one of the release:perform parameter.

Before shouting after maven, just try to understand it :) and have a look to 
the documentation.

In your case, this the page [0]

What your are doing seems not natural to me, one of my best-pratice is to 
ALWAYS release with tests done, otherwise, the generated ste (and the surefire 
report) will say : no tests passed, is it really what you want ?

[0] http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html


-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Skip tests on release

[Tony Chemit]

Le Tue, 10 Aug 2010 13:25:41 -0400,
"C. Benson Manica"  a écrit :

> I do pretty much always want to release with the tests done, but why do they
> have to run twice for essentially the same process, i.e. prepare and
> perform?  They take a long time, and are they really likely to fail between
> prepare and perform?  I guess if I'm stuck, I'm stuck, but this seems
> gratuitous.

perform goal is here to check if you can do a release.

perform really do the release.

Perharps in your case there is no impact from prepare to perform, but for us it 
is not the case, we really need to pass it in release stage too.

for information, when a release stage, you can see that tests are done twice : 
one for the deploy and one for the site-deploy (in fact for the surefire 
report).

I know sometime it can be a pain (and long...) but I don't think there is 
another to do it.

If there is anoter way, perharps maven guys can tell you more ? 

Sorry not to have a wonderfull solution for you.

> 
> On Tue, Aug 10, 2010 at 12:40 PM, Tony Chemit  wrote:
> 
> > Le Tue, 10 Aug 2010 12:32:55 -0400,
> > "C. Benson Manica"  a écrit :
> >
> > > mvn -DskipTests=true -Dmaven.test.skip=true release:perform still insists
> > on
> > > running the unit tests.  Why?  They already ran on release:prepare, I
> > > really, really, really get annoyed sitting through five minutes of unit
> > > tests that I know pass because I just ran them.
> > >
> >
> > When doing a mvn release:perform, the plugin just launch another instance
> > of maven with by default this command :
> >
> > mvn deploy site-deploy -DperformRelease
> >
> > So you will never be able to change this behaviour like you are trying to
> > do.
> >
> > To make this possible you can use one of the release:perform parameter.
> >
> > Before shouting after maven, just try to understand it :) and have a look
> > to the documentation.
> >
> > In your case, this the page [0]
> >
> > What your are doing seems not natural to me, one of my best-pratice is to
> > ALWAYS release with tests done, otherwise, the generated ste (and the
> > surefire report) will say : no tests passed, is it really what you want ?
> >
> > [0] http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html
> >
> >
> > --
> > Tony Chemit
> > 
> > tél: +33 (0) 2 40 50 29 28
> > email: che...@codelutin.com
> > http://www.codelutin.com
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [ANN] Release Maven Site Plugin 3.0-beta-1 for maven 3

[Tony Chemit]

Le Wed, 11 Aug 2010 00:25:42 +0200,
Olivier Lamy  a écrit :

> The Maven team is pleased to announce the release of the Maven Site
> Plugin, version 3.0-beta-1 for Maven 3.
> This version is intended to be the first version of the Maven Site
> Plugin for Maven 3 and it currently only works with Apache Maven
> 3.0-beta-2.
> 
> The Site Plugin is used to generate a site for the project. The
> generated site also includes the project's reports that were configured
> in the  section of the POM.
> 
> The 3.x version of the Site Plugin has changed the way you configure
> reports. You can read more about the new configuration mode at [1].
> 
> You should specify the version in the  section of your project's POM:
> 
> 
>  org.apache.maven.plugins
>  maven-site-plugin
>  3.0-beta-1
> 
> 
> Release Notes - Maven Site Plugin - Version 3.0-beta-1
> 
> Bug
> MSITE-456 - regression Site navigation not generated
> MSITE-460 - error when using Maven 3.x with maven-site-plugin 3.x
> MSITE-477 -  href's drop the leading character in
> the href when staging a site
> MSITE-490 - WARNING Deprecated API called - not
> org.apache.maven.doxia.sink.Sink instance and no SinkFactory
> available. Please update this plugin.
> 
> Improvement
> MSITE-436 - regenerate every page when site.xml (direct or parent) is changed
> New Feature
> MSITE-463 - Lithuanian translation
> MSITE-465 - Add a site:effective-site goal (similar to help:effective-pom)
> 
> Task
> MSITE-478 - Attach site descriptor as an artifact, not metadata, to the 
> project
> MSITE-482 - Update to Doxia 1.1.3
> MSITE-487 - upgrade source to java 5
> 
> Users interested in testing this beta release should have a glance at
> the compatibility notes for known differences between Maven 3.0 and
> Maven 2.x:
> https://cwiki.apache.org/confluence/x/sokr
> 
> 
> Know limitations :
> * deployment vith dav currently doesn't work.
> 
> You must note that the default execution of site:attach-descriptor has
> been removed from the built-in lifecycle bindings for projects with
> packaging "pom".
> So now, you have to define the following goal execution to restore the
> intended behavior:
> 
> 
>   
> maven-site-plugin
> 3.0-beta-1
> 
>   
> attach-descriptor
> 
>   attach-descriptor
> 
>   
> 
>   
> 

there is an error in this configuration (the *plugins* section is missing) , it 
should be :

  

  
maven-site-plugin
3.0-beta-1

  
attach-descriptor

  attach-descriptor

  

  

  
> 
> On the wiki page [2], you will find more information on how to
> configure your POM in order to be able to continue building site with
> both Maven 2.x and Maven 3.
> 
> You must note this version is a beta. You will find more informations
> on migration [4]
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Skip tests on release

[Tony Chemit]

Le Wed, 11 Aug 2010 08:33:06 -0400,
"C. Benson Manica"  a écrit :

> Thanks, this seems to be what I was looking for.
Yeah, as it was written in the link I gave you...

> 
> On Tue, Aug 10, 2010 at 1:35 PM, Larry Shatzer, Jr. wrote:
> 
> > I've seen it like this in a parent corporate pom:
> >
> > In the release plugin configuration:
> >
> >  
> >org.apache.maven.plugins
> > maven-release-plugin
> >
> >  clean install
> >  deploy -P release
> >
> >  
> >
> > Then later on:
> >
> >
> >  
> >  release
> >  
> >true
> >  
> >
> >
> > On Tue, Aug 10, 2010 at 11:25 AM, C. Benson Manica 
> > wrote:
> > > I do pretty much always want to release with the tests done, but why do
> > they
> > > have to run twice for essentially the same process, i.e. prepare and
> > > perform?  They take a long time, and are they really likely to fail
> > between
> > > prepare and perform?  I guess if I'm stuck, I'm stuck, but this seems
> > > gratuitous.
> > >
> > > On Tue, Aug 10, 2010 at 12:40 PM, Tony Chemit 
> > wrote:
> > >
> > >> Le Tue, 10 Aug 2010 12:32:55 -0400,
> > >> "C. Benson Manica"  a écrit :
> > >>
> > >> > mvn -DskipTests=true -Dmaven.test.skip=true release:perform still
> > insists
> > >> on
> > >> > running the unit tests.  Why?  They already ran on release:prepare, I
> > >> > really, really, really get annoyed sitting through five minutes of
> > unit
> > >> > tests that I know pass because I just ran them.
> > >> >
> > >>
> > >> When doing a mvn release:perform, the plugin just launch another
> > instance
> > >> of maven with by default this command :
> > >>
> > >> mvn deploy site-deploy -DperformRelease
> > >>
> > >> So you will never be able to change this behaviour like you are trying
> > to
> > >> do.
> > >>
> > >> To make this possible you can use one of the release:perform parameter.
> > >>
> > >> Before shouting after maven, just try to understand it :) and have a
> > look
> > >> to the documentation.
> > >>
> > >> In your case, this the page [0]
> > >>
> > >> What your are doing seems not natural to me, one of my best-pratice is
> > to
> > >> ALWAYS release with tests done, otherwise, the generated ste (and the
> > >> surefire report) will say : no tests passed, is it really what you want
> > ?
> > >>
> > >> [0]
> > http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html
> > >>
> > >>
> > >> --
> > >> Tony Chemit
> > >> 
> > >> tél: +33 (0) 2 40 50 29 28
> > >> email: che...@codelutin.com
> > >> http://www.codelutin.com
> > >>
> > >> -
> > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > >> For additional commands, e-mail: users-h...@maven.apache.org
> > >>
> > >>
> > >
> > >
> > > --
> > > C. Benson Manica
> > > cbman...@gmail.com
> > >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Decrypting server password

[Tony Chemit]

Le Sat, 28 Aug 2010 16:22:29 +0200,
Simone Tripodi  a écrit :

> Hi all guys,
> a friend of mine and I are developing a maven plugin that needs to
> acces to a server credentials specified in the settings.xml; no
> problem since the org.apache.maven.settings.Server class exposes
> methods to retrieve username/password, the problem comes when
> passwords are encrypted using the method described in the
> guide-encryption[1].
> How can we decrypt the password inside the plugin code? Thanks in advance!

Otherwise you change the goal share-server-secret of the 
org.nuiton:maven-helper-plugin which does it for you and make it avaible in 
your maven build. [2] and [3]

And look at the code of mojo as well :) [4]

> All the best,
> Simo
> 
> [1] http://maven.apache.org/guides/mini/guide-encryption.html

[2] http://repo2.maven.org/maven2/org/nuiton/maven-helper-plugin/1.2.6/ 
[3] 
http://maven-site.nuiton.org/maven-helper-plugin/share-server-secret-mojo.html 
[4] 
http://www.nuiton.org/repositories/entry/maven-helper-plugin/tags/maven-helper-plugin-1.2.6/src/main/java/org/nuiton/helper/plugin/ShareServerSecretPlugin.java
 
> 
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 

-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [PLEASE TEST] Apache Maven 3.0-RC2

[Tony Chemit]

Le Wed, 22 Sep 2010 20:44:14 +0200,
Benjamin Bentmann  a écrit :

> Hi,
> 
works fine except for a regression I already noticed (and tells in beta-2).

The problem occurs when you use more than one plugin execution declared in 
different profile.

I will make a little example to explain it better and post it to JIRA.

 
> in preparation for the release of Apache Maven 3.0, the Maven team is 
> seeking your help to discover regressions since Maven 2.x. Everybody 
> interested in taking a preview of the upcoming release for a test drive 
> can get source and binary bundles from this URL:
> 
> https://repository.apache.org/content/repositories/maven-006/org/apache/maven/apache-maven/3.0-RC2/
> 
> Before reporting any issues found during testing, please be sure to have 
> a close look at the compatibility notes for Maven 3.x:
> 
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes
> 
> If you encounter unexpected build issues, please fill a report in JIRA 
> that provides sufficient information to reproduce and analyze the issue:
> 
> http://jira.codehaus.org/browse/MNG
> 
> The fixes contained in this release candidate since the 3.0-beta-3 
> release and the previous RC1 can also be seen in JIRA:
> 
> http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=PRIR5ueW-i&version=13142&styleName=Text&projectId=10500&Create=Create
> 
> Thanks,
> 
> 
> -The Maven team
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com  
http://www.codelutin.com 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] License maven plugin 1.4 released

[Tony Chemit]

Hi,

The Mojo team is pleased to announce the release of the License 
Maven Plugin, version 1.4. 

This plugin manages the license of a maven project and its dependencies
(update file headers, download dependencies licenses, check thirdparty
licenses, ...).

This License Plugin has the following goals:

* license:add-third-party
  Goal to generate the third-party license file. This file contains a list of
  the dependencies and their licenses. Each dependency and it's license is
  displayed on a single line in the format
  
   ()  :: -
  
  It will also copy it in the class-path (says add the generated directory as a
  resource of the build).

* license:aggregate-add-third-party
  This aggregator goal (will be executed only once and only on pom projects)
  executed the add-third-party on all his modules (in a parellel build cycle)
  then aggreates all the third-party files in final one in the pom project.

* license:check-file-header
  The goal to check if the state of header on project source files.

* license:comment-style-list
  Displays all the available comment style to box file headers.

* license:download-licenses
  Download the license files of all the current project's dependencies, and
  generate a summary file containing a list of all dependencies and their
  licenses.

* license:license-list
  Display all available licenses.

* license:third-party-report
  Generates a report of all third-parties detected in the module.

* license:update-file-header
  The goal to update (or add) the header on project source files. This goal
  replace the update-header goal which can not deal with Copyright. This goal
  use a specific project file descriptor project.xml to describe all files to
  update for a whole project.

* license:update-project-license
  Updates (or creates) the main project license file according to the given
  license defines as licenseName. Can also generate a bundled license file (to
  avoid collision names in class-path). This file is by default generated in
  META-INF class-path directory.

Some useful links:

Documentation: http://mojo.codehaus.org/license-maven-plugin
JIRA: http://jira.codehaus.org/browse/MLICENSE
svn:  https://svn.codehaus.org/mojo/tags/license-maven-plugin-1.4

To get this update, simply specify the version in your project's plugin
configuration: 


  org.codehaus.mojo
  license-maven-plugin
  1.4


The artifacts have been deployed to the mojo repository and will be
mirrored to central.

Release Notes - Mojo's License Maven Plugin - Version 1.4

** Bug
* [MLICENSE-48] - No support for proxy settings
* [MLICENSE-50] - settings.xml file and pom example for license resolver 
use invalid file url
* [MLICENSE-51] - Incorrect information on example usage pages
* [MLICENSE-54] - Incorrect command line and broken links in online 
documentation
* [MLICENSE-56] - SQL header not compatible with MySQL
* [MLICENSE-58] - Doc improvements
* [MLICENSE-59] - Dead links on example page(s)
* [MLICENSE-61] - New year bug in it update-file-header/test-mojo

** Improvement
* [MLICENSE-53] - Allow "includedLicenses" to be specified in sub-tags
* [MLICENSE-63] - Please allow 'quiet' configuration option to disable 
excess messages
* [MLICENSE-64] - Please allow multiple additive licenseMerge elements

** New Feature
* [MLICENSE-60] - Provide mechanism for shared data store for 'missing' 
licenses

** Task
* [MLICENSE-57] - Updates dependencies


Enjoy,

The Mojo team.

tony

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Animal sniffer signatures-parent 1.2 released

[Tony Chemit]

The Mojo team is pleased to announce the release of the 
Animal Sniffer signatures-parent version 1.2.

The Animal Scents project contains a number of projects which generate 
signatures 
of various APIs, such as the Java Runtime. 
These signatures are generated by and consumed by the Animal Sniffer project.

The artifacts have been deployed to the mojo repository and will be
mirrored to central.

Learn more here:
http://mojo.codehaus.org/signatures


Release Notes - Maven 2.X Animal Sniffer signatures-parent - Version 1.2

** Task

* [MANIMALSNIFFER-32] Updates mojo-parent to 31
* [MANIMALSNIFFER-33] Updates animal-sniffer-m-p to 1.9

The Mojo Team

tony.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Animal Sniffer signature java16 1.1 released

[Tony Chemit]

The Mojo team is pleased to announce the release of the 
Animal Sniffer java16 version 1.1.

Java 1.6 Runtime Signatures excluding vendor 
specific implementation classes.

This new release permits to use some API changes after jdk 1.6u18.

The package was build using oracle jdk 1.6u43

Learn more here:
http://mojo.codehaus.org/signatures/java16 


The artifacts have been deployed to the mojo repository and will be
mirrored to central.

Release Notes - Maven 2.X Animal Sniffer signature java16 - Version 1.1

** Task

* [MANIMALSNIFFER-31] Update Java 6 signature to contain new StAX methods

The Mojo Team

tony.

-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com
http://www.codelutin.com

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Animal Sniffer signature java17 1.0 released

[Tony Chemit]

The Mojo team is pleased to announce the release of the 
Animal Sniffer java17 version 1.0.

Java 1.7 Runtime Signatures excluding vendor 
specific implementation classes

This is a new signature :)

The package was build using oracle jdk 1.7u47

Learn more here:
http://mojo.codehaus.org/signatures/java17


The artifacts have been deployed to the mojo repository and will be
mirrored to central.

Release Notes - Maven 2.X Animal Sniffer signature java17 - Version 1.0

** Task

* [MANIMALSNIFFER-22] Add java7 signature

The Mojo Team

tony.

-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com
http://www.codelutin.com

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] License Maven Plugin 1.5 released

[Tony Chemit]

The Mojo team is pleased to announce the release of the License 
Maven Plugin, version 1.5. 

This plugin manages the license of a maven project and its dependencies
(update file headers, download dependencies licenses, check thirdparty
licenses, ...).

Roadmap
---

Note that next version should be the 2.0 with this main features:

- rethink the way to grab the license of a dependency

  o from pom
  o from a local missing file
  o from a local global missing file
  o from a remote missing file

- unify configuration between the download-licenses and other goals 
(*-third-party goals)
- improve the way to define license categories (update-*-license goals)

Configuration won't probably be compatible with version 1.5, but a migration 
guide 
will be added to help you.

Any good new ideas for the next major version are of course welcome.

Description
---

This License Plugin has the following goals:

* license:add-third-party
  Goal to generate the third-party license file. This file contains a list of
  the dependencies and their licenses. Each dependency and it's license is
  displayed on a single line in the format
  
   ()  :: -
  
  It will also copy it in the class-path (says add the generated directory as a
  resource of the build).

* license:aggregate-add-third-party
  This aggregator goal (will be executed only once and only on pom projects)
  executed the add-third-party on all his modules (in a parellel build cycle)
  then aggreates all the third-party files in final one in the pom project.

* license:check-file-header
  The goal to check if the state of header on project source files.

* license:comment-style-list
  Displays all the available comment style to box file headers.

* license:download-licenses
  Download the license files of all the current project's dependencies, and
  generate a summary file containing a list of all dependencies and their
  licenses.

* license:license-list
  Display all available licenses.

* license:third-party-report
  Generates a report of all third-parties detected in the module.

* license:update-file-header
  The goal to update (or add) the header on project source files. This goal
  replace the update-header goal which can not deal with Copyright. This goal
  use a specific project file descriptor project.xml to describe all files to
  update for a whole project.

* license:update-project-license
  Updates (or creates) the main project license file according to the given
  license defines as licenseName. Can also generate a bundled license file (to
  avoid collision names in class-path). This file is by default generated in
  META-INF class-path directory.

Useful links


Documentation: http://mojo.codehaus.org/license-maven-plugin
JIRA: http://jira.codehaus.org/browse/MLICENSE
svn:  https://svn.codehaus.org/mojo/tags/license-maven-plugin-1.5

To get this update, simply specify the version in your project's plugin
configuration: 


  org.codehaus.mojo
  license-maven-plugin
  1.5


The artifacts have been deployed to the mojo repository and will be
mirrored to central.


Release Notes
-

** Bug
* [MLICENSE-70] - Proxy settings causing NPE
* [MLICENSE-74] - If inceptionYear isn't set then an unhelpful message is 
produced.
* [MLICENSE-77] - acceptPomPackaging option must be compliant with 
aggregate-add-third-party goal

** Improvement
* [MLICENSE-71] - Can merge a license twice
* [MLICENSE-75] - Add skip parameter for goals

Enjoy,

The Mojo team.

tony


-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: chemit at codelutin dot com
http://www.codelutin.com

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven 2.x Keytool Plugin version 1.3 released

[Tony Chemit]

The Mojo team is pleased to announce the release of the Maven 2.x Keytool 
Plugin version 1.3

A plugin that wraps the keytool program bundled with Oracle's Java SDK. Allows 
to
  manipulate keystores.

Description
---

This Keytool Plugin has the 17 following goals:

keytool:changeAlias
  To change an entry alias into a keystore. Implemented as a wrapper around the
  SDK keytool -keyclone (jdk 1.5) or keytool -changealias (jdk 1.6) command. See
  keystore documentation.

keytool:changeKeyPassword
  To change the key password of an entry of a keystore. Implemented as a wrapper
  around the SDK keytool -keypasswd command. See keystore documentation.

keytool:changeStorePassword
  To change the store password of a keystore. Implemented as a wrapper around
  the SDK keytool -storepasswd command. See keystore documentation.

keytool:clean
  A Mojo that deletes a generated keystore file.

keytool:deleteAlias
  To delete an entry alias from a keystore. Implemented as a wrapper around the
  SDK keytool -delete command. See keystore documentation.

keytool:exportCertificate
  To export a certificate from a keystore. Implemented as a wrapper around the
  SDK keytool -export command. See keystore documentation.

keytool:generateCertificate
  To generate certificate from a certificate request from a keystore.
  Implemented as a wrapper around the SDK keytool -gencert command. Note This
  operation was not implemented by the keytool before jdk 1.7. See keystore
  documentation.

keytool:generateCertificateRequest
  To generate certificate request. Implemented as a wrapper around the SDK
  keytool -certreq command. See keystore documentation.

keytool:generateKeyPair
  To generate a key pair into a keystore. Implemented as a wrapper around the
  SDK keytool -genkey (jdk 1.5) keytool -genkeypair (jdk 1.6) command. See
  keystore documentation.

keytool:generateSecretKey
  To generate a secret key into a keystore. Implemented as a wrapper around the
  SDK keytool -genseckey command. See keystore documentation.

keytool:help
  Display help information on keytool-maven-plugin.
  Call mvn keytool:help -Ddetail=true -Dgoal= to display parameter
  details.

keytool:importCertificate
  To import a certificate into a keystore. Implemented as a wrapper around the
  SDK keytool -import (jdk 1.5) or keytool -importcert (jdk 1.6) command. See
  keystore documentation. Since version 1.2, this mojo replace the mojo import.

keytool:importKeystore
  To import all entries of a keystore to another keystore. Implemented as a
  wrapper around the SDK keytool -importkeystore command. Note This operation
  was not implemented by the keytool before jdk 1.6. See keystore documentation.

keytool:list
  To list entries in a keystore. Implemented as a wrapper around the SDK keytool
  -list (jdk 1.5) command. See keystore documentation.

keytool:printCertificate
  To print the content of a certificate. Implemented as a wrapper around the SDK
  keytool -printcert command. See keystore documentation.

keytool:printCertificateRequest
  To print the content of a certificate request. Implemented as a wrapper around
  the SDK keytool -printcertreq command. Note This operation was not implemented
  by the keytool before jdk 1.7. See keystore documentation.

keytool:printCRLFile
  To print the content of a CRL file. Implemented as a wrapper around the SDK
  keytool -printcrl command. Note This operation was not implemented by the
  keytool before jdk 1.7. See keystore documentation.

Useful links


Documentation: http://mojo.codehaus.org/keytoolkeytool-maven-plugin
JIRA: http://jira.codehaus.org/browse/MKEYTOOL
svn:  https://svn.codehaus.org/mojo/tags/keytool-1.3

To get this update, simply specify the version in your project's plugin
configuration: 


  org.codehaus.mojo
  keytool-maven-plugin
  1.3


The artifacts have been deployed to the mojo repository and will be
mirrored to central.

Release Notes
-

** Bug
* [MKEYTOOL-27] - Can't import a keystore

** Improvement
* [MKEYTOOL-26] - Introduce an keytool-api for jdk 7
* [MKEYTOOL-28] - Fails mojo when operation is not supported by keytool 
implementation

** Task
* [MKEYTOOL-22] - use maven-plugin-tools' java 5 annotations
* [MKEYTOOL-23] - Remove deprecated mojo
* [MKEYTOOL-29] - Improve api tests

Enjoy,

The Mojo team.

tony

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Mojo's Webstart Maven Plguin version 1.0-beta-4 Released

[Tony Chemit]

Bonsoir,

The Mojo team is pleased to announce the release of the Webstart
Maven Plugin version 1.0-beta-4

The Webstart Maven Plugin generates application bundles that can be
deployed via Web Start. The plugin can be used to prepare standalone
Web Start applications or Web Start applications bundled in WAR files
(with or without Sun's Download Servlet). It handles the generation of
JNLP files and optional version.xml files, using Velocity templates. It
also handles the selection and preparation of the dependencies,
performing signing, unsigning and Pack200 compression when required.

Important changes in this new version:

The mojo POM configuration lay have changed, 
please read the following page about it:

http://mojo.codehaus.org/webstart/webstart-maven-plugin/upgrade.html 

This new version permits you to generate some jnlp files acceptable with jdk >= 
1.7u45, 
more detail here:

http://jira.codehaus.org/browse/MWEBSTART-213 

You can also now use a keystore from any url, more details here:
http://jira.codehaus.org/browse/MWEBSTART-39 

To get this update, simply specify the version in your project's
plugin configuration:


  org.codehaus.mojo
  webstart-maven-plugin
  1.0-beta-4


Roadmap:

Next release (1.0-beta-5) will appear soon, the issue MWEBSTART-221 has 
been fixed to make possible usage of versionned resources. 

I expect to do this new release in the folowwing weeks.

Some links:

Documentation: http://mojo.codehaus.org/webstart/webstart-maven-plugin
JIRA: http://jira.codehaus.org/browse/MWEBSTART
svn:  https://svn.codehaus.org/mojo/tags/webstart-1.0-beta-4


Release Notes - Maven 2.x Webstart Plugin - Version 1.0-beta-4

** Bug
* [MWEBSTART-127] - unsignAlreadySignedJars sometimes removes manifest 
information
* [MWEBSTART-132] - Unsigning already signed jars doesn't work when libPath 
used
* [MWEBSTART-138] - The number of signed artifacts differ from the number 
of modified artifacts
* [MWEBSTART-144] - Jar Unsigning Does Not Work
* [MWEBSTART-152] - Jar unsign does not remove certificate : comparison is 
case sensitive against "DSA", "RSA" and "SF" file extensions
* [MWEBSTART-186] - While parsing JNLPConf default value of 
templateDirectory is wrong
* [MWEBSTART-196] - Jar signing fails if path contains parentheses
* [MWEBSTART-198] - verify via jarsigner not working
* [MWEBSTART-218] - Can't build project with jdk1.5
* [MWEBSTART-219] - Transitive dependencies not included in generated jnlp 
files and version.xml

** Improvement
* [MWEBSTART-39] - Allow keystore to be: a file, classpath resource or 
remote resource (not only a file)
* [MWEBSTART-50] - AbstractJnlpMojo hardcode's webstart archive
* [MWEBSTART-121] - The plugin should pick up jars from sister projects 
* [MWEBSTART-145] - Dependencies (jar resources) from the webstart plugin 
are not resolved using the reactor, so "mvn clean package" will not work. Then, 
"mvn release:prepare" will not work either.
* [MWEBSTART-200] - Allow to pass arbitrary properties into velocity 
template for JNLP file
* [MWEBSTART-206] - Upgrade code to java 5
* [MWEBSTART-207] - Source code formatting
* [MWEBSTART-212] - support for --pass-file= (of the pack200 
command)
* [MWEBSTART-213] - Enable Manipulation of the manifest from dependend jars
* [MWEBSTART-220] - Allow to pass arbitrary properties into velocity 
template for jnlp-download-servlet mojo JNLP file

** Task
* [MWEBSTART-20] - sort out potential licensing issue of the pack200 tasks
* [MWEBSTART-217] - Use java 5 maven plugin annotations


Have Fun!
--
The Mojo team.


-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
http://www.codelutin.com
email: che...@codelutin.com
twitter: https://twitter.com/tchemit

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Jarsigner 1.1 Released

[Tony Chemit]

The Maven team is pleased to announce the release of the Maven JArsigner,  
version 1.1

This component provides some utilities to sign/verify jars/files in your Mojos.

http://maven.apache.org/shared/maven-jarsigner/

To use the Maven Jarsigner, add the following dependency to your project:

   
 org.apache.maven.shared
 maven-jarsinger
 1.1
   


Release Notes - Maven Shared Components - Version maven-jarsigner-1.1

** Bug
* [MSHARED-214] - Method 'JarSignerUtil.isSignatureFile( String entryName 
)' needs to also account for files ending in '.EC'.
* [MSHARED-277] - JarSignerUtil.unsignArchive invalid entry compressed size

** Improvement
* [MSHARED-300] - Update javadoc links

** New Feature
* [MSHARED-213] - Please add a method to class JarSignerUtil to test an 
archive to contain signature files.
* [MSHARED-299] - Add support for -tsa during signing (Trusted Timestamping)


Enjoy,

-The Maven team

tony.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Jarsigner 1.1 Released

[Tony Chemit]

The Maven team is pleased to announce the release of the Maven JArsigner,  
version 1.1

This component provides some utilities to sign/verify jars/files in your Mojos.

http://maven.apache.org/shared/maven-jarsigner/

To use the Maven Jarsigner, add the following dependency to your project:

   
 org.apache.maven.shared
 maven-jarsinger
 1.1
   


Release Notes - Maven Shared Components - Version maven-jarsigner-1.1

** Bug
* [MSHARED-214] - Method 'JarSignerUtil.isSignatureFile( String entryName 
)' needs to also account for files ending in '.EC'.
* [MSHARED-277] - JarSignerUtil.unsignArchive invalid entry compressed size

** Improvement
* [MSHARED-300] - Update javadoc links

** New Feature
* [MSHARED-213] - Please add a method to class JarSignerUtil to test an 
archive to contain signature files.
* [MSHARED-299] - Add support for -tsa during signing (Trusted Timestamping)


Enjoy,

-The Maven team

tony.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: [ANN] Maven Jarsigner 1.1 Released

[Tony Chemit]

On Tue, 12 Nov 2013 23:59:06 +0100
Tony Chemit  wrote:

> The Maven team is pleased to announce the release of the Maven JArsigner,  
> version 1.1
> 
> This component provides some utilities to sign/verify jars/files in your 
> Mojos.
> 
> http://maven.apache.org/shared/maven-jarsigner/
> 
> To use the Maven Jarsigner, add the following dependency to your project:
> 
>
>  org.apache.maven.shared
>  maven-jarsinger
>  1.1
>

The dependency is *maven-jarsigner* and not *maven-jarsinger*, 

   
 org.apache.maven.shared
 maven-jarsigner
 1.1
   

tony.

-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
http://www.codelutin.com
email: che...@codelutin.com
twitter: https://twitter.com/tchemit

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] MojoHaus License Maven Plugin Version 1.9 Released

[Tony Chemit]

Hi,

The Mojo team is pleased to announce the release of the new License Maven 
Plugin version 1.9

Web Site:
http://www.mojohaus.org/license-maven-plugin



   org.codehaus.mojo
   license-maven-plugin
   1.9



The Release Notes:
https://github.com/mojohaus/license-maven-plugin/issues?q=milestone%3A1.9

http://www.mojohaus.org/license-maven-plugin/github-report.html


Kind Regards
Tony Chemit
-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
http://www.codelutin.com
email: che...@codelutin.com
twitter: https://twitter.com/tchemit

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] MojoHaus License Maven Plugin Version 1.10 Released

[Tony Chemit]

Hi,

The Mojo team is pleased to announce the release of the License Maven Plugin 
version 1.10. 

This plugin manages the license of a maven project and its dependencies (update 
file headers, 
download dependencies licenses, check thirdparty licenses, ...)


Web Site:
http://www.mojohaus.org/license-maven-plugin

To get this update, simply specify the version in your project's plugin 
configuration: 

  
org.codehaus.mojo
license-maven-plugin
1.10
  

The Release Notes:
https://github.com/mojohaus/license-maven-plugin/issues?q=milestone%3A1.10

http://www.mojohaus.org/license-maven-plugin/github-report.html



Enjoy and Share,

The Mojo team.
 
Tony.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] MojoHaus License Maven Plugin Version 1.10 Released

[Tony Chemit]

Hi,

The Mojo team is pleased to announce the release of the License Maven Plugin
version 1.10. 

This plugin manages the license of a maven project and its dependencies (update
file headers, download dependencies licenses, check thirdparty licenses, ...)


Web Site:
http://www.mojohaus.org/license-maven-plugin

To get this update, simply specify the version in your project's plugin
configuration: 

  
org.codehaus.mojo
license-maven-plugin
1.10
  

The Release Notes:
https://github.com/mojohaus/license-maven-plugin/issues?q=milestone%3A1.10

http://www.mojohaus.org/license-maven-plugin/github-report.html



Enjoy and Share,

The Mojo team.
 
Tony.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] MojoHaus License Maven Plugin Version 1.11 Released

[Tony Chemit]

Hi, 

The Mojo team is pleased to announce the release of the License Maven 
Plugin version 1.11. 

This plugin manages the license of a maven project and its dependencies 
(update file headers, 
download dependencies licenses, check thirdparty licenses, ...) 

Web Site: 
http://www.mojohaus.org/license-maven-plugin 

To get this update, simply specify the version in your project's plugin 
configuration: 

   
org.codehaus.mojo 
license-maven-plugin 
1.1A 
   

The Release Notes: 
https://github.com/mojohaus/license-maven-plugin/issues?q=milestone%3A1.1 

1

http://www.mojohaus.org/license-maven-plugin/github-report.html 

Enjoy and Share, 

The Mojo team. 
  
Tony. 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] MojoHaus License Maven Plugin Version 1.12 Released

[Tony Chemit]

Hi, 

The Mojo team is pleased to announce the release of the License Maven 
Plugin version 1.12. 

This plugin manages the license of a maven project and its dependencies 
(update file headers, 
download dependencies licenses, check thirdparty licenses, ...) 

Web Site: 
http://www.mojohaus.org/license-maven-plugin 

To get this update, simply specify the version in your project's plugin 
configuration: 

   
org.codehaus.mojo 
license-maven-plugin 
1.12 
   

The Release Notes: 
https://github.com/mojohaus/license-maven-plugin/issues?q=milestone%3A1.12

http://www.mojohaus.org/license-maven-plugin/github-report.html 

Enjoy and Share, 

The Mojo team. 
  
Tony. 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Shared Utils 0.5 released

[Tony Chemit]

The Apache Maven team is pleased to announce the release of the 
maven-shared-utils, version 0.5

This project aims to be a functional replacement for
{{{http://plexus.codehaus.org/plexus-utils}plexus-utils}} in Maven.

It is not a 100% API compatible replacement though but a replacement
:
lots of methods got cleaned up, generics got added and we dropped a
lot of unused code. Although all
the classes are in different packages from plexus-utils, if the method
is present it will have the same
semantics, facilitating easy conversion.

http://maven.apache.org/shared/maven-shared-utils/

The version 0.5 brings in a new API to execute java tools of the jdk 
(jarsinger, keytool, ...).

Release Notes - Maven Shared Components - Version maven-shared-utils-0.5

** New Feature
* [MSHARED-304] - Create a API for java tool

Enjoy,

-The Apache Maven team

tony.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Shared Jarsigner 1.2 Released

[Tony Chemit]

The Maven team is pleased to announce the release of the Apache Maven 
Jarsigner,  
version 1.2

This component provides some utilities to sign/verify jars/files in your Mojos.

http://maven.apache.org/shared/maven-jarsigner/

To use the Maven Jarsigner, add the following dependency to your project:

   
 org.apache.maven.shared
 maven-jarsigner
 1.2
   

Release Notes - Maven Shared Components - Version maven-jarsigner-1.2

** Improvement
* [MSHARED-306] - keystore and alias parameters can be used for both sign 
and verify jarsigner tool

** Task
* [MSHARED-301] - use plexus java 5 annotations instead of plexus javadoc 
tags
* [MSHARED-302] - Use java 5 codestyle
* [MSHARED-303] - Jar Signer does not support protected authentication path
* [MSHARED-305] - Use maven-shared-utils javatool API

Enjoy,

-The Maven team

tony.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven 2.x Keytool Plugin version 1.4 released

[Tony Chemit]

The Mojo team is pleased to announce the release of the Maven 2.x Keytool 
Plugin version 1.4

A plugin that wraps the keytool program bundled with Oracle's Java SDK. Allows 
to
  manipulate keystores.

Description
---

This Keytool Plugin has the 17 following goals:

keytool:changeAlias
  To change an entry alias into a keystore. Implemented as a wrapper around the
  SDK keytool -keyclone (jdk 1.5) or keytool -changealias (jdk 1.6) command. See
  keystore documentation.

keytool:changeKeyPassword
  To change the key password of an entry of a keystore. Implemented as a wrapper
  around the SDK keytool -keypasswd command. See keystore documentation.

keytool:changeStorePassword
  To change the store password of a keystore. Implemented as a wrapper around
  the SDK keytool -storepasswd command. See keystore documentation.

keytool:clean
  A Mojo that deletes a generated keystore file.

keytool:deleteAlias
  To delete an entry alias from a keystore. Implemented as a wrapper around the
  SDK keytool -delete command. See keystore documentation.

keytool:exportCertificate
  To export a certificate from a keystore. Implemented as a wrapper around the
  SDK keytool -export command. See keystore documentation.

keytool:generateCertificate
  To generate certificate from a certificate request from a keystore.
  Implemented as a wrapper around the SDK keytool -gencert command. Note This
  operation was not implemented by the keytool before jdk 1.7. See keystore
  documentation.

keytool:generateCertificateRequest
  To generate certificate request. Implemented as a wrapper around the SDK
  keytool -certreq command. See keystore documentation.

keytool:generateKeyPair
  To generate a key pair into a keystore. Implemented as a wrapper around the
  SDK keytool -genkey (jdk 1.5) keytool -genkeypair (jdk 1.6) command. See
  keystore documentation.

keytool:generateSecretKey
  To generate a secret key into a keystore. Implemented as a wrapper around the
  SDK keytool -genseckey command. See keystore documentation.

keytool:help
  Display help information on keytool-maven-plugin.
  Call mvn keytool:help -Ddetail=true -Dgoal= to display parameter
  details.

keytool:importCertificate
  To import a certificate into a keystore. Implemented as a wrapper around the
  SDK keytool -import (jdk 1.5) or keytool -importcert (jdk 1.6) command. See
  keystore documentation. Since version 1.2, this mojo replace the mojo import.

keytool:importKeystore
  To import all entries of a keystore to another keystore. Implemented as a
  wrapper around the SDK keytool -importkeystore command. Note This operation
  was not implemented by the keytool before jdk 1.6. See keystore documentation.

keytool:list
  To list entries in a keystore. Implemented as a wrapper around the SDK keytool
  -list (jdk 1.5) command. See keystore documentation.

keytool:printCertificate
  To print the content of a certificate. Implemented as a wrapper around the SDK
  keytool -printcert command. See keystore documentation.

keytool:printCertificateRequest
  To print the content of a certificate request. Implemented as a wrapper around
  the SDK keytool -printcertreq command. Note This operation was not implemented
  by the keytool before jdk 1.7. See keystore documentation.

keytool:printCRLFile
  To print the content of a CRL file. Implemented as a wrapper around the SDK
  keytool -printcrl command. Note This operation was not implemented by the
  keytool before jdk 1.7. See keystore documentation.

Useful links


Documentation: http://mojo.codehaus.org/keytoolkeytool-maven-plugin
JIRA: http://jira.codehaus.org/browse/MKEYTOOL
svn:  https://svn.codehaus.org/mojo/tags/keytool-1.4

To get this update, simply specify the version in your project's plugin
configuration: 


  org.codehaus.mojo
  keytool-maven-plugin
  1.4


The artifacts have been deployed to the mojo repository and will be
mirrored to central.

Release Notes
-

** New Feature
* [MKEYTOOL-34] - Add ToolChain support

** Task
* [MKEYTOOL-31] - Migrates to maven-shared-utils (replace plexus-utils)
* [MKEYTOOL-32] - use java 5 plexus annotations
* [MKEYTOOL-33] - Use JavaTool API from maven-shared-utils component

** Wish
* [MKEYTOOL-30] - Add m2e lifecycle mapping metadata

Enjoy,

The Mojo team.

tony

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Jarsigner Plugin 1.3 Released

[Tony Chemit]

The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.3.

This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:

http://maven.apache.org/plugins/maven-jarsigner-plugin/

This plugin is meant to supercede the existing jar:sign and
jar:verify goals from the Maven Jar Plugin which will be deprecated
in a future release.

To use the updated plugin in your projects, you need to add the 
following snippet to the plugins or plugin management section of your POM:


  org.apache.maven.plugins
  maven-jarsigner-plugin
  1.3
  
...
  


Release Notes - Maven Jar Signer Plugin - Version 1.3

** Bug
* [MJARSIGNER-13] - signing in multi-module project fails on windows
* [MJARSIGNER-21] - jars signed using Java 7 have "invalid SHA1 signature"
* [MJARSIGNER-26] - Jar Signer does not support protected authentication 
path
* [MJARSIGNER-29] - verbose parameter is not filled in jarsigner requests

** Improvement
* [MJARSIGNER-28] - verify mojo can also use keystore and alias parameters

** New Feature
* [MJARSIGNER-12] - It should be possible to save the keystore in one 
location for multi module projects
* [MJARSIGNER-16] - Add the option -tsa to the configuration
* [MJARSIGNER-18] - Support for Jar plugin's "errorWhenNotSigned" option
* [MJARSIGNER-24] - Use Password Encryption in pom.xml

** Task
* [MJARSIGNER-9] - Add toolchain in JarSignMojo.java#getJDKCommandExe()
* [MJARSIGNER-22] - Add french translations
* [MJARSIGNER-25] - use maven-plugin-tools' java 5 annotations
* [MJARSIGNER-27] - Use maven-jarsigner 1.3
* [MJARSIGNER-31] - Update maven-shared-utils to 0.5
* [MJARSIGNER-32] - Update requirements to maven 2.1.0

Enjoy,

The Maven team.

-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
http://www.codelutin.com
email: che...@codelutin.com
twitter: https://twitter.com/tchemit

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Shared Jarsigner 1.3.1 Released

[Tony Chemit]

The Maven team is pleased to announce the release of the Apache Maven 
Jarsigner,  
version 1.3.1

This component provides some utilities to sign/verify jars/files in your Mojos.

http://maven.apache.org/shared/maven-jarsigner/

To use the Maven Jarsigner, add the following dependency to your project:

   
 org.apache.maven.shared
 maven-jarsigner
 1.3.1
   

Release Notes - Maven Shared Components - Version maven-jarsigner-1.3.1

** Bug
* [MSHARED-315] - Unsign jars are still not ok

Enjoy,

-The Maven team

tony.


-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
http://www.codelutin.com
email: che...@codelutin.com
twitter: https://twitter.com/tchemit

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Jarsigner Plugin 1.3.1 Released

[Tony Chemit]

The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.3.1.

This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:

http://maven.apache.org/plugins/maven-jarsigner-plugin/

This plugin is meant to supercede the existing jar:sign and
jar:verify goals from the Maven Jar Plugin which will be deprecated
in a future release.

To use the updated plugin in your projects, you need to add the 
following snippet to the plugins or plugin management section of your POM:


  org.apache.maven.plugins
  maven-jarsigner-plugin
  1.3.1
  
...
  


Release Notes - Maven Jar Signer Plugin - Version 1.3.1

** Bug
* [MJARSIGNER-33] - Sign already signed jar still does not work

Enjoy,

The Maven team.

-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
http://www.codelutin.com
email: che...@codelutin.com
twitter: https://twitter.com/tchemit

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Jarsigner Plugin 1.3.1 Released

[Tony Chemit]

The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.3.1.

This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:

http://maven.apache.org/plugins/maven-jarsigner-plugin/

This plugin is meant to supercede the existing jar:sign and
jar:verify goals from the Maven Jar Plugin which will be deprecated
in a future release.

To use the updated plugin in your projects, you need to add the 
following snippet to the plugins or plugin management section of your POM:


  org.apache.maven.plugins
  maven-jarsigner-plugin
  1.3.1
  
...
  


Release Notes - Maven Jar Signer Plugin - Version 1.3.1

** Bug
* [MJARSIGNER-33] - Sign already signed jar still does not work

Enjoy,

The Maven team.

-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
http://www.codelutin.com
email: che...@codelutin.com
twitter: https://twitter.com/tchemit

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Shared Utils 0.6 released

[Tony Chemit]

The Apache Maven team is pleased to announce the release of the 
maven-shared-utils, version 0.6

This project aims to be a functional replacement for
{{{http://plexus.codehaus.org/plexus-utils}plexus-utils}} in Maven.

It is not a 100% API compatible replacement though but a replacement
:
lots of methods got cleaned up, generics got added and we dropped a
lot of unused code. Although all
the classes are in different packages from plexus-utils, if the method
is present it will have the same
semantics, facilitating easy conversion.

http://maven.apache.org/shared/maven-shared-utils/

Release Notes - Maven Shared Components - Version maven-shared-utils-0.6

** Improvement
* [MSHARED-320] - Be able to mask some arguments in the commandLine API

Enjoy,

-The Apache Maven team

tony.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Apache Maven Shared Jarsigner 1.3.2 Released

[Tony Chemit]

The Maven team is pleased to announce the release of the Apache Maven 
Jarsigner,  
version 1.3.2

This component provides some utilities to sign/verify jars/files in your Mojos.

http://maven.apache.org/shared/maven-jarsigner/

To use the Maven Jarsigner, add the following dependency to your project:

   
 org.apache.maven.shared
 maven-jarsigner
 1.3.2
   

Release Notes - Maven Shared Components - Version maven-jarsigner-1.3.2

** Bug
* [MSHARED-316] - Can not pass storetype nor storepass to a verify request

** Improvement
* [MSHARED-321] - Mask passwords in logs

** Task
* [MSHARED-322] - Use maven-shared-utils 0.6

Enjoy,

-The Maven team

tony.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Maven Jarsigner Plugin 1.3.2 Released

[Tony Chemit]

The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.3.2.

This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:

http://maven.apache.org/plugins/maven-jarsigner-plugin/

This plugin is meant to supercede the existing jar:sign and
jar:verify goals from the Maven Jar Plugin which will be deprecated
in a future release.

To use the updated plugin in your projects, you need to add the 
following snippet to the plugins or plugin management section of your POM:


  org.apache.maven.plugins
  maven-jarsigner-plugin
  1.3.2
  
...
  


Release Notes - Maven Jar Signer Plugin - Version 1.3.2

** Bug
* [MJARSIGNER-34] - The 'verify' goal of the plugin is passing '-keystore' 
but not '-storetype'.
* [MJARSIGNER-35] - verbose mode shows keystore password in clear text

** Task
* [MJARSIGNER-36] - Use maven-shared-utils 0.6 and maven-jarsigner 1.3.2

Enjoy,

The Maven team.

tony.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] License Maven Plugin 1.8 released

[Tony Chemit]

The Mojo team is pleased to announce the release of the License Maven Plugin, 
version 1.8. 

This plugin manages the license of a maven project and its dependencies
(update file headers, download dependencies licenses, check thirdparty
licenses, ...).

Description
---

This License Plugin has the following goals:

* license:add-third-party
  Goal to generate the third-party license file. This file contains a list of
  the dependencies and their licenses. Each dependency and it's license is
  displayed on a single line in the format

   ()  :: -
  
  It will also copy it in the class-path (says add the generated directory as a
  resource of the build).

* license:aggregate-add-third-party
  This aggregator goal (will be executed only once and only on pom projects)
  executed the add-third-party on all his modules (in a parellel build cycle)
  then aggreates all the third-party files in final one in the pom project.

* license:check-file-header
  The goal to check if the state of header on project source files.

* license:comment-style-list
  Displays all the available comment style to box file headers.

* license:download-licenses
  Download the license files of all the current project's dependencies, and
  generate a summary file containing a list of all dependencies and their
  licenses.

* license:license-list
  Display all available licenses.

* license:third-party-report
  Generates a report of all third-parties detected in the module.

* license:update-file-header
  The goal to update (or add) the header on project source files. This goal
  replace the update-header goal which can not deal with Copyright. This goal
  use a specific project file descriptor project.xml to describe all files to
  update for a whole project.

* license:update-project-license
  Updates (or creates) the main project license file according to the given
  license defines as licenseName. Can also generate a bundled license file (to
  avoid collision names in class-path). This file is by default generated in
  META-INF class-path directory.

Useful links


Documentation: http://mojo.codehaus.org/license-maven-plugin
JIRA: http://jira.codehaus.org/browse/MLICENSE
svn:  https://svn.codehaus.org/mojo/tags/license-maven-plugin-1.8

To get this update, simply specify the version in your project's plugin
configuration: 


  org.codehaus.mojo
  license-maven-plugin
  1.8


The artifacts have been deployed to the mojo repository and will be
mirrored to central.

Release Notes
-

** Bug
* [MLICENSE-108] - copyright owner is not working properly
* [MLICENSE-113] - Eclipse Public License includes Eclipse Distribution 
License by mistake

Enjoy,

The Mojo team.

tony


-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
http://www.codelutin.com
email: che...@codelutin.com
twitter: https://twitter.com/tchemit

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Animal Sniffer 1.13 Released

[Tony Chemit]

Hi,

The Mojo team is pleased to announce the release of Animal Sniffer version 1.13.

Animal Sniffer provides tools to assist verifying that classes
compiled with a newer JDK/API are compatible with an older JDK/API.

The following tools are provided by animal sniffer:

* A command line tool to dump the class file version number
(http://mojo.codehaus.org/animal-sniffer/animal-sniffer/index.html).
This helps you track down the offending jar file when you see
UnsupportedClassVersionError.

* A set of ANT tasks
(http://mojo.codehaus.org/animal-sniffer/animal-sniffer-ant-tasks/index.html
)
for verifying that your classes comply with an API signature as well
as tasks for creating API signatures from a JDK, or a collection or
jar and class files, or a collection of other API signature files, or
combination of these elements.

* A rule for use in the maven-enforcer-plugin
(
http://mojo.codehaus.org/animal-sniffer/animal-sniffer-enforcer-rule/index.html
)
for verifying that your classes comply with an API signature .

* A maven plugin
(http://mojo.codehaus.org/animal-sniffer-maven-plugin/index.html) for
verifying that your classes comply with an API signature as well as
for creating API signatures from a JDK, or the current module's
classes, or the current module's dependencies, or a collection of
other API signature files, or combination of these elements.

The artifacts have are available from the Maven Central repository.

Release Notes - Mojo's Animal Sniffer - Version 1.13

** New Feature
 * [MANIMALSNIFFER-48] - Resolve signature version from dependencies / 
dependencyManagement if unspecified

The Mojo Team.

-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
http://www.codelutin.com
email: che...@codelutin.com
twitter: https://twitter.com/tchemit

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] License Maven Plugin 1.0-beta-3 Released

[Tony Chemit]

Hi,

The Mojo team is pleased to announce the release of the License Maven
Plugin version 1.0-beta-3.
Site : http://mojo.codehaus.org/license-maven-plugin/

To get this update, simply specify the version in your project's
plugin configuration:


  org.codehaus.mojo
  license-maven-plugin
  1.0-beta-3


Release Notes - Mojo - Version license-maven-plugin-beta-3

** Bug
* [MOJO-1674] - license-maven-plugin tries downloading license
  files even in offline mode
* [MOJO-1716] - missing third party file are regenerated when using
  none jar dependencies


** Improvement
* [MOJO-1713] - Add license header on jsp files using jsp comments
* [MOJO-1715] - Some Documentations are wrong
* [MOJO-1717] - When module has no missing dependency, check to
  remove the missing file

** Wish
* [MOJO-1625] - Filter dependencies by scope

Have Fun,
--
The Mojo team.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] webstart-maven-plugin-1.0-beta-2 Released

[Tony Chemit]

Hi,

The Mojo team is pleased to announce the release of the
webstart-maven-plugin version 1.0-beta-2. 

The Webstart Maven Plugin generates application bundles that can be
deployed via Web Start. The plugin can be used to prepare standalone
Web Start applications or Web Start applications bundled in WAR files
(with or without Sun's Download Servlet). It handles the generation of
JNLP files and optional version.xml files, using Velocity templates. It
also handles the selection and preparation of the dependencies,
performing signing, unsigning and Pack200 compression when required.

Some links :

Documentation: http://mojo.codehaus.org/webstart
JIRA: http://jira.codehaus.org/browse/MWEBSTART
svn:  https://svn.codehaus.org/mojo/tags/webstart-1.0-beta-2

To get this update, simply specify the version in your project's plugin
configuration: 


org.codehaus.mojo.webstart
webstart
1.0-beta-2


Some configuration may have changed since 1.0-beta-1, especially
concerning the codebase of generated jnlp components files (and the
report).

Please checkout this in your configuration if something is wrong before
all.

Release Notes - Maven 2.x Webstart Plugin - Version 1.0-beta-2

** Bug
* [MWEBSTART-134] - jnlp resources are in libPath
* [MWEBSTART-138] - The number of signed artifacts differ from the
number of modified artifacts
* [MWEBSTART-148] - Fix dependency resolution/handling
* [MWEBSTART-151] - offlineAllowed and allPermissions don't have
any effect
* [MWEBSTART-154] - Some links are broken on the site of beta-1
* [MWEBSTART-155] - it002 and it003 are broken
* [MWEBSTART-159] - JARs are not Pack200-compressed if libPath is set 
* [MWEBSTART-160] - Maven 3.0 Compatibility Issue
* [MWEBSTART-161] - Transitive dependencies specified in profile
don't get  included
* [MWEBSTART-163] - Webstart zip contains Maven jars that are not
  required for the webstart app

** Improvement
* [MWEBSTART-158] - Customize code base
* [MWEBSTART-168] - Make mojo and reports unified
* [MWEBSTART-171] - Improve pack200 integration

** New Feature
* [MWEBSTART-14] - support component extension mecanism for
   already signed jars
* [MWEBSTART-156] - Generate extension files
* [MWEBSTART-157] - Add makeArchive and attachArchive parameter to
mojo
* [MWEBSTART-169] - Add french report translations
* [MWEBSTART-170] - Add a canSign parameter to authorize or forbbid
unsigning of  already signed jar

** Task
* [MWEBSTART-99] - Add an integration test for the report mojo

Enjoy,

The Mojo team.
 
Tony Chemit

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] license-maven-plugin-1.0 Released

[Tony Chemit]

Hi,

The Mojo team is pleased to announce the release of the
license-maven-plugin version 1.0. 

This plugin manages the license of a maven project and its dependencies
(update file headers, download dependencies licenses, check thirdparty
licenses, ...).

Some links :

Documentation: http://mojo.codehaus.org/license-maven-plugin
JIRA: http://jira.codehaus.org/browse/MLICENSE
svn:  https://svn.codehaus.org/mojo/tags/license-maven-plugin-1.0

To get this update, simply specify the version in your project's plugin
configuration: 


org.codehaus.mojo
license-maven-plugin
1.0


Please checkout this in your configuration if something is wrong before
all.

Release Notes - Mojo's License Maven Plugin - Version 1.0

** Bug
* [MLICENSE-3] - license.canUpdateCopyright does not work
* [MLICENSE-5] - Overriding bundleLicensePath does not work
* [MLICENSE-6] - Adding license header on sh files breaks the
 shebang

** Improvement
* [MLICENSE-15] - Check that all files are present in the license
  store
* [MLICENSE-16] - Add new missing file headers (for freemarker for
  example)
* [MLICENSE-23] - Entries of licenseMerges should be unique

** New Feature
* [MLICENSE-10] - license-maven-plugin should allow configuring the
  location of license and header files

** Task
* [MLICENSE-12] - Clean pom
* [MLICENSE-13] - remove french documentation
* [MLICENSE-14] - Updates nuiton-processor to 1.2.2

Enjoy,

The Mojo team.
 
Tony Chemit

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] Release Mojo's Webstart Maven Plguin version 1.0-beta-3

[Tony Chemit]

Bonsoir,

The Mojo team is pleased to announce the release of the Webstart
Maven Plugin version 1.0-beta-3

The Webstart Maven Plugin generates application bundles that can be
deployed via Web Start. The plugin can be used to prepare standalone
Web Start applications or Web Start applications bundled in WAR files
(with or without Sun's Download Servlet). It handles the generation of
JNLP files and optional version.xml files, using Velocity templates. It
also handles the selection and preparation of the dependencies,
performing signing, unsigning and Pack200 compression when required.

Due to MWEBSTART-192, the groupId of the plugin has changed and has 
come back to *org.codehaus.mojo*.

To get this update, simply specify the version in your project's
plugin configuration:


  org.codehaus.mojo
  webstart-maven-plugin
  1.0-beta-3


Some links :

Documentation: http://mojo.codehaus.org/webstart/webstart-maven-plugin
JIRA: http://jira.codehaus.org/browse/MWEBSTART
svn:  https://svn.codehaus.org/mojo/tags/webstart-1.0-beta-3


Release Notes - Maven 2.x Webstart Plugin - Version 1.0-beta-3

** Bug
* [MWEBSTART-112] - commas in dname should be escaped when generating keys
* [MWEBSTART-130] - webstart dont generate *.jar.pack.gz files
* [MWEBSTART-172] - French translation are not well encoded
* [MWEBSTART-174] - jnlp.packEnabled option is not enabled when generating 
pack200 archives
* [MWEBSTART-175] - integration tests fail on Mac OS X because tools.jar
* [MWEBSTART-193] - Relative links in APT docs to other pages are incorrect.

** Improvement
* [MWEBSTART-149] - Add parameter maxMemory to the 
org.codehaus.mojo.webstart.JarSignMojoConfig fields
* [MWEBSTART-173] - Change the plugin's groupId to org.codehaus.mojo
* [MWEBSTART-177] - Remove Utils class and use directly FileUtils instead
* [MWEBSTART-178] - Use maven-jarsigner component instead of 
maven-jar-plugin
* [MWEBSTART-180] - Use the shared api of keytool instead of mojo
* [MWEBSTART-181] - Improve the pack200 api
* [MWEBSTART-182] - Remove the jarsigner-api module
* [MWEBSTART-187] - Encoding should be configurable for jnlp template file
* [MWEBSTART-191] - Use the keytool-api

** New Feature
* [MWEBSTART-87] - incorporate changes from codecrate maven plugin


** Task
* [MWEBSTART-183] - Remove deprecated modules
* [MWEBSTART-192] - Use groupId org.codehaus.mojo

Have Fun!
--
The Mojo team.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] License Maven plugin 1.1 Released

[Tony Chemit]

Hi,

The Mojo team is pleased to announce the release of the License
Maven plugin version 1.1

This plugin manages the license of a maven project and its dependencies
(update file headers, download dependencies licenses, check thirdparty
licenses, ...).

To get this update, simply specify the version in your project's
plugin configuration:


org.codehaus.mojo
license-maven-plugin
1.1


Some links :

Documentation: http://mojo.codehaus.org/license-maven-plugin
JIRA: http://jira.codehaus.org/browse/MLICENSE
svn:  https://svn.codehaus.org/mojo/tags/license-maven-plugin-1.1

Release Notes - Mojo's License Maven Plugin - Version 1.1

** Bug
* [MLICENSE-25] - license:add-third-party should operate on projects with 
"pom" packaging
* [MLICENSE-34] - Multi-line copyright holders cannot be updated

** Improvement
* [MLICENSE-26] - The title of the site pages don't display the plugin name
* [MLICENSE-27] - How to configure start and end process tags
* [MLICENSE-30] - Allow template for description section that can include 
variables for filename, creation time etc.
* [MLICENSE-33] - Add report goal license:third-party-report
* [MLICENSE-35] - Clean code
* [MLICENSE-36] - Create fromat string for dependencies' licenses list entry
* [MLICENSE-37] - Make it possible to restrict which licenses are allowed 
in a project

** Task
* [MLICENSE-38] - Fix PMD, CPD and some checkstyle (license header for 
example).

Have Fun!

--
The Mojo team.

-- 
Tony Chemit

email: chemit at codelutin dot com
http://www.codelutin.com

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

[ANN] License Maven Plugin 1.2 Released

[Tony Chemit]

Hi,

The Mojo team is pleased to announce the release of the License
Maven plugin version 1.2

This plugin manages the license of a maven project and its dependencies
(update file headers, download dependencies licenses, check thirdparty
licenses, ...).

To get this update, simply specify the version in your project's
plugin configuration:


org.codehaus.mojo
license-maven-plugin
1.2


What's new in version 1.2 ?
---

- A new goal was introduced (check-file-header) to check that files have a 
license header.
- Can now generate a java license header after the package statement (as used 
in codehaus)
- Usage of maven-plugin-plugin 3.1 and his nice java annotations (thanks to 
Maven guys :))
- and some fixes and improvements...

Some links
--

Documentation: http://mojo.codehaus.org/license-maven-plugin
JIRA: http://jira.codehaus.org/browse/MLICENSE
svn:  https://svn.codehaus.org/mojo/tags/license-maven-plugin-1.2

Release Notes - Mojo's License Maven Plugin - Version 1.2

** Bug
* [MLICENSE-44] - Filter content is not reset after the description 
template is rendered for each file

** Improvement
* [MLICENSE-28] - aggregate-add-third-party should be able to use a 
THIRD-PARTY.properties for the aggreated licences
* [MLICENSE-41] - Use maven 3 plugin api

** New Feature
* [MLICENSE-39] - Be able to generate the file header for java files after 
the package statement
* [MLICENSE-40] - Introduce new goal license:check-file-header


** Task
* [MLICENSE-42] - Remove the updateCopyright property on update-file-header 
mojo
* [MLICENSE-43] - Remove deprecated AddThirdParty#groupByLicense property


Have Fun!

--
The Mojo team.

-- 
Tony Chemit

email: chemit at codelutin dot com
http://www.codelutin.com

-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com
http://www.codelutin.com

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org