Re: maven artifacts nested dependencies

[Goli]

Thank you for your attention.

regards,
Goli
-- 
View this message in context: 
http://maven.40175.n5.nabble.com/maven-artifacts-nested-dependencies-tp2805767p2826942.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

Re: ScriptRunner exception when calling Rhino script in Ant build from maven antrun plugin

[Jacob Beard]

Hi,

It actually seems that including the Bean Scripting Framework as a
dependency is causing the problems. Consider the following reduced
example. The following succeeds:


 
   
  
maven-antrun-plugin
1.4

  
test
initialize

  
Hello world!

x=0;

Hello world 2!
  


  run

  




rhino
js
1.7R2


  
   
 


And produces the following output:


 [echo] Hello world!
 [echo] Hello world 2!


But when the bsf plugin dependency is turned on, the script tag throws
the ClassNotFoundException with ScriptRunner:


 
   
  
maven-antrun-plugin
1.4

  
test
initialize

  
Hello world!

x=0;

Hello world 2!
  


  run

  



bsf
bsf
2.4.0


rhino
js
1.7R2


  
   
 


[INFO] Executing tasks
 [echo] Hello world!
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] An Ant BuildException has occured:
java.lang.ClassNotFoundException:
org.apache.tools.ant.util.optional.ScriptRunner


I tried ant-nodeps as well, but adding that dependency produced a very
unusual error:


[INFO] [antrun:run {execution: test}]
[FATAL ERROR] org.apache.maven.plugin.antrun.AntRunMojo#execute()
caused a linkage error (java.lang.NoSuchMethodError) and may be
out-of-date. Check the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[org.apache.maven.plugins:maven-antrun-plugin:1.4]
urls[0] = 
file:/home/jacob/.m2/repository/org/apache/maven/plugins/maven-antrun-plugin/1.4/maven-antrun-plugin-1.4.jar
urls[1] = file:/home/jacob/.m2/repository/rhino/js/1.7R2/js-1.7R2.jar
urls[2] = 
file:/home/jacob/.m2/repository/ant/ant-nodeps/1.6.5/ant-nodeps-1.6.5.jar
urls[3] = 
file:/home/jacob/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.5/plexus-utils-2.0.5.jar
urls[4] = 
file:/home/jacob/.m2/repository/org/apache/ant/ant-nodeps/1.8.1/ant-nodeps-1.8.1.jar
urls[5] = file:/home/jacob/.m2/repository/org/apache/ant/ant/1.8.1/ant-1.8.1.jar
urls[6] = 
file:/home/jacob/.m2/repository/org/apache/ant/ant-launcher/1.8.1/ant-launcher-1.8.1.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/usr/share/maven2/lib/maven-debian-uber.jar
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] 
org.apache.tools.ant.launch.Locator.fromJarURI(Ljava/lang/String;)Ljava/lang/String;
[INFO] 
[INFO] Trace
java.lang.NoSuchMethodError:
org.apache.tools.ant.launch.Locator.fromJarURI(Ljava/lang/String;)Ljava/lang/String;
at 
org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:274)
at 
org.apache.tools.ant.helper.ProjectHelper2.parseUnknownElement(ProjectHelper2.java:130)
at 
org.apache.tools.ant.helper.ProjectHelper2.parseAntlibDescriptor(ProjectHelper2.java:110)
at org.apache.tools.ant.taskdefs.Antlib.createAntlib(Antlib.java:91)
at org.apache.tools.ant.taskdefs.Definer.loadAntlib(Definer.java:440)
at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:292)
at 
org.apache.maven.plugin.antrun.AbstractAntMojo.initMavenTasks(AbstractAntMojo.java:346)
at 
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:201)
at org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:81)
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(DefaultLifecycleExecu

Re: Plans to release Maven 3.0

[Yoav Landman]

This may be a result of pom validation checks by Artifactory itself. See:
http://wiki.jfrog.org/confluence/display/RTF/Advanced - suppressing pom
consistency checks. You should see a message in the server log - if you do
try turning it off or deploy a fixed pom version locally.

On Wed, Sep 8, 2010 at 11:31 PM, John Singleton  wrote:

> I have tried to use Maven 3.0 (all beta versions) on our project but the
> build fails due to a metadata error in an artifact in the central
> repository.  The error message is:
>
> Error transferring file: Server returned HTTP response code: 409 for URL:
>
> http://blackbook.jhuapl.edu:8080/artifactory/repo/colt/colt/1.2.0/colt-1.2.0.pom-
> >
> [Help 1]
>
> Is this behavior intended?  (our project builds fine with maven 2.2.1, but
> I
> understand that m3 does more extensive pom verification)
>
> If so, will there be more urgency to fixing bad data in central?  The bad
> colt pom is already identified in MEV-618 (05MAR09) and is still
> unassigned.
>
> Until that happens, what is the recommended fix or workaround?
>
> Thanks,
> John Singleton
>
> On Wed, Sep 8, 2010 at 9:49 AM, Brian Fox  wrote:
>
> > So if you haven't
> > yet, we would like you to grab the latest 3.x build and give us your
> > feedback.
> >
> > --Brian
> > Apache Maven PMC Chair
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>

Re: Archetype plugin 2.0-alpha-6 release?

[Hervé BOUTEMY]

I'll release it soon, in a week or two.
But nobody seem to have tested ARCHETYPE-202: the risk is that the fix doesn't 
work.
Can someone test and report if it is ok?

Regards,

Hervé

Le mercredi 08 septembre 2010, Lóránt Pintér a écrit :
> Hi,
> 
> I'm fighting with http://jira.codehaus.org/browse/ARCHETYPE-202. It
> seems that all issues for 2.0-alpha-6 have been fixed (among then
> ARCHETYPE-202) before 20th Aug. Can 2.0-alpha-6 be released, please?
> 
> Thanks,
> Lóránt
> 
> -
> 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

Re: Plans to release Maven 3.0

[John Singleton]

I have tried to use Maven 3.0 (all beta versions) on our project but the
build fails due to a metadata error in an artifact in the central
repository.  The error message is:

Error transferring file: Server returned HTTP response code: 409 for URL:
http://blackbook.jhuapl.edu:8080/artifactory/repo/colt/colt/1.2.0/colt-1.2.0.pom->
[Help 1]

Is this behavior intended?  (our project builds fine with maven 2.2.1, but I
understand that m3 does more extensive pom verification)

If so, will there be more urgency to fixing bad data in central?  The bad
colt pom is already identified in MEV-618 (05MAR09) and is still unassigned.

Until that happens, what is the recommended fix or workaround?

Thanks,
John Singleton

On Wed, Sep 8, 2010 at 9:49 AM, Brian Fox  wrote:

> So if you haven't
> yet, we would like you to grab the latest 3.x build and give us your
> feedback.
>
> --Brian
> Apache Maven PMC Chair
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

RE: Plans to release Maven 3.0

[Thiebaud, Christophe]

3.0 beta-3 works for me as well.
Thanks a lot
Christophe

-Original Message-
From: Jamie Whitehouse [mailto:basil.whiteho...@gmail.com] 
Sent: Mittwoch, 8. September 2010 20:47
To: Maven Users List
Subject: Re: Plans to release Maven 3.0

On Wed, Sep 8, 2010 at 9:49 AM, Brian Fox  wrote:

> We need your help to determine what
> else needs to be fixed before the final release. So if you haven't
> yet, we would like you to grab the latest 3.x build and give us your
> feedback. You can find the download link here:
> http://maven.apache.org/download.html
>

3.0 beta-3 works well for my internal 100+ module build.  All previous
issues I encountered have been resolved.

Thanks for all the work,
Jamie.

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

Re: Plans to release Maven 3.0

[Jamie Whitehouse]

On Wed, Sep 8, 2010 at 9:49 AM, Brian Fox  wrote:

> We need your help to determine what
> else needs to be fixed before the final release. So if you haven't
> yet, we would like you to grab the latest 3.x build and give us your
> feedback. You can find the download link here:
> http://maven.apache.org/download.html
>

3.0 beta-3 works well for my internal 100+ module build.  All previous
issues I encountered have been resolved.

Thanks for all the work,
Jamie.

Re: Maven Enforcer Plugin, requirePluginVersions, and Maven 3.0

[Trevor Harmon]

On Sep 8, 2010, at 11:14 AM, Brian Fox wrote:

> The workaround is to not use
> this rule in M3 anymore since the core will throw warnings at you
> anyway.

For the requireMavenVersion and requireJavaVersion rules, should I continue 
using Enforcer, or is there a Maven 3 analog for them as well? Thanks,

Trevor


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

Re: Maven Enforcer Plugin, requirePluginVersions, and Maven 3.0

[Anders Hammar]

The difference is that the enforcer rule will prevent a build if plugin
versions aren't locked down. Maven will only give warnings. My experience is
that users don't care about warnings...

/Anders

On Wed, Sep 8, 2010 at 20:14, Brian Fox  wrote:

> This is coming from the enforcer rule itself, since it is coded using
> bits from M2 that aren't present in M3. The workaround is to not use
> this rule in M3 anymore since the core will throw warnings at you
> anyway.
>
> On Wed, Sep 8, 2010 at 12:22 PM, Trevor Harmon  wrote:
> > Hi,
> >
> > I'm trying out Maven 3.0-beta-3, and one of the first things I noticed is
> a new warning message:
> >
> > [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-rules) @
> MyApp ---
> > [WARNING] This rule is not compatible with the current version of Maven.
> The rule is not able to perform any checks.
> >
> > The warning is caused by the presence of the following Maven Enforcer
> rule:
> >
> > 
> >
> > I seem to remember reading somewhere that Maven 3.0 already has the
> functionality of requirePluginVersions. In any case, what's the proper way
> to resolve this warning? Thanks,
> >
> > Trevor
> >
> >
> > -
> > 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
>
>

Re: how to access maven programatically

[Brian Fox]

Use Aether. http://www.sonatype.com/people/2010/08/introducing-aether/

On Wed, Sep 8, 2010 at 10:48 AM, Ernst, Andreas  wrote:
> Hi,
>
> how do i access model information from my local maven repository given a 
> specific artifact. ( I need to compute alle parent artifacts ) .
> Anyone with a simple example?
>
> Thanxs,
>
> Andreas
>
>
> Andreas Ernst
> System Architect
> Technology Management
>
> Phone: +49(0)221/2077-2278
> Fax: +49(0)221/2077-239
> E-Mail: andreas.er...@hrs.de 
>
> HRS - Hotel Reservation Service
> Robert Ragge GmbH
> Blaubach 32 | 50676 Köln | Germany
>
> Geschäftsführer: Robert Ragge und Tobias Ragge
> AG Köln HRB 6099
>
>
> Hotel Reservation Service
> Robert Ragge GmbH, Blaubach 32, 50676 Köln, Deutschland
> Geschäftsführer: Robert Ragge und Tobias Ragge
> AG Köln HRB 6099 USt-IdNr.: DE 122779245
>
> -
> 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

Re: Maven Enforcer Plugin, requirePluginVersions, and Maven 3.0

[Brian Fox]

This is coming from the enforcer rule itself, since it is coded using
bits from M2 that aren't present in M3. The workaround is to not use
this rule in M3 anymore since the core will throw warnings at you
anyway.

On Wed, Sep 8, 2010 at 12:22 PM, Trevor Harmon  wrote:
> Hi,
>
> I'm trying out Maven 3.0-beta-3, and one of the first things I noticed is a 
> new warning message:
>
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-rules) @ MyApp 
> ---
> [WARNING] This rule is not compatible with the current version of Maven. The 
> rule is not able to perform any checks.
>
> The warning is caused by the presence of the following Maven Enforcer rule:
>
> 
>
> I seem to remember reading somewhere that Maven 3.0 already has the 
> functionality of requirePluginVersions. In any case, what's the proper way to 
> resolve this warning? Thanks,
>
> Trevor
>
>
> -
> 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

Maven Enforcer Plugin, requirePluginVersions, and Maven 3.0

[Trevor Harmon]

Hi,

I'm trying out Maven 3.0-beta-3, and one of the first things I noticed is a new 
warning message:

[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-rules) @ MyApp ---
[WARNING] This rule is not compatible with the current version of Maven. The 
rule is not able to perform any checks.

The warning is caused by the presence of the following Maven Enforcer rule:



I seem to remember reading somewhere that Maven 3.0 already has the 
functionality of requirePluginVersions. In any case, what's the proper way to 
resolve this warning? Thanks,

Trevor


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

Re: Is there a plugin to automatically increment pom version ?

[Wendy Smoak]

On Wed, Sep 8, 2010 at 11:20 AM, Prashant Bhate
 wrote:
> ya.. already looked at it.. there is versions:set goal but  user needs to
> provide new version to it.. :(

Well, then, patch it to use a reasonable default?  Perhaps it could
work off of the --batch-mode switch.  If that is active, plugins are
not supposed to prompt for anything.

The logic for incrementing the version is available somewhere, the
release plugin knows how to suggest the "next" version.

-- 
Wendy

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

Re: Is there a plugin to automatically increment pom version ?

[Prashant Bhate]

Yes thats what we thought initially. However Using that is ruled out after
knowing that  there is no support for dynamic clearcase views yet. Writing
plugin is easy we have written couple of them like to wsi-validate wsdls and
stuff like that...
but why reinvent wheels if plan is just to fly ?

Prashant Bhate

On Wed, Sep 8, 2010 at 4:05 PM, Nayan Hajratwala  wrote:

> On Sep 8, 2010, at 11:01 AM, Prashant Bhate wrote:
>
> > Hi,
> >
> > I know release plugin does that for you, but it also performs other scm
> > dependencices that is overkill for the project that I am currently
> working
> > with.
>
> Prashant, based on my experience with the release plugin, it may be worth
> the effort to get it working properly with your simple project. It can be
> tricky to get it working once your project gets more complicated, so the
> earlier the better. Also, it may be quicker than writing your own plugin.
>
> > Is there any plugin / goal that does just what is said in subject line
> > increase major/ minor version number?
> >
> > If not I might actually end up writing a plugin that would use
> >
> http://mojo.codehaus.org/pomtools-maven-plugin/apidocs/org/codehaus/mojo/pomtools/versioning/DefaultVersionInfo.html
> >
> > Posting this q to save that time :)
> >
> > any help be appreciated :)
> >
> > Prashant
>
> ---
> Nayan Hajratwala
> http://agileshrugged.com
> http://twitter.com/nhajratw
> 734.658.6032
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: how to access maven programatically

[Ron Wheeler]

You can use any editor to read a POM file. Eclipse has a really nice POM 
editor.


I am sure that you already knew that but that is the direct answer to 
the question that you actually asked.

What was the real question? What are you really trying to do?

Ron


On 08/09/2010 10:48 AM, Ernst, Andreas wrote:

Hi,

how do i access model information from my local maven repository given a 
specific artifact. ( I need to compute alle parent artifacts ) .
Anyone with a simple example?

Thanxs,

Andreas


Andreas Ernst
System Architect
Technology Management

Phone: +49(0)221/2077-2278
Fax: +49(0)221/2077-239
E-Mail: andreas.er...@hrs.de

HRS - Hotel Reservation Service
Robert Ragge GmbH
Blaubach 32 | 50676 Köln | Germany

Geschäftsführer: Robert Ragge und Tobias Ragge
AG Köln HRB 6099


Hotel Reservation Service
Robert Ragge GmbH, Blaubach 32, 50676 Köln, Deutschland
Geschäftsführer: Robert Ragge und Tobias Ragge
AG Köln HRB 6099 USt-IdNr.: DE 122779245

-
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

Re: Is there a plugin to automatically increment pom version ?

[Prashant Bhate]

ya.. already looked at it.. there is versions:set goal but  user needs to
provide new version to it.. :(


On Wed, Sep 8, 2010 at 4:07 PM, Wendy Smoak  wrote:

> On Wed, Sep 8, 2010 at 11:01 AM, Prashant Bhate
>  wrote:
> > I know release plugin does that for you, but it also performs other scm
> > dependencices that is overkill for the project that I am currently
> working
> > with. Is there any plugin / goal that does just what is said in subject
> line
> > increase major/ minor version number?
>
> See if something in the Versions plugin will do what you want:
> http://mojo.codehaus.org/versions-maven-plugin/
>
> --
> Wendy
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

how to access maven programatically

[Ernst, Andreas]

Hi,
 
how do i access model information from my local maven repository given a 
specific artifact. ( I need to compute alle parent artifacts ) .
Anyone with a simple example?
 
Thanxs,
 
Andreas
 

Andreas Ernst
System Architect
Technology Management

Phone: +49(0)221/2077-2278
Fax: +49(0)221/2077-239
E-Mail: andreas.er...@hrs.de  

HRS - Hotel Reservation Service
Robert Ragge GmbH
Blaubach 32 | 50676 Köln | Germany

Geschäftsführer: Robert Ragge und Tobias Ragge
AG Köln HRB 6099 


Hotel Reservation Service
Robert Ragge GmbH, Blaubach 32, 50676 Köln, Deutschland
Geschäftsführer: Robert Ragge und Tobias Ragge 
AG Köln HRB 6099 USt-IdNr.: DE 122779245

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

Re: Is there a plugin to automatically increment pom version ?

[Wendy Smoak]

On Wed, Sep 8, 2010 at 11:01 AM, Prashant Bhate
 wrote:
> I know release plugin does that for you, but it also performs other scm
> dependencices that is overkill for the project that I am currently working
> with. Is there any plugin / goal that does just what is said in subject line
> increase major/ minor version number?

See if something in the Versions plugin will do what you want:
http://mojo.codehaus.org/versions-maven-plugin/

-- 
Wendy

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

Re: Is there a plugin to automatically increment pom version ?

[Nayan Hajratwala]

On Sep 8, 2010, at 11:01 AM, Prashant Bhate wrote:

> Hi,
> 
> I know release plugin does that for you, but it also performs other scm
> dependencices that is overkill for the project that I am currently working
> with.

Prashant, based on my experience with the release plugin, it may be worth the 
effort to get it working properly with your simple project. It can be tricky to 
get it working once your project gets more complicated, so the earlier the 
better. Also, it may be quicker than writing your own plugin.

> Is there any plugin / goal that does just what is said in subject line
> increase major/ minor version number?
> 
> If not I might actually end up writing a plugin that would use
> http://mojo.codehaus.org/pomtools-maven-plugin/apidocs/org/codehaus/mojo/pomtools/versioning/DefaultVersionInfo.html
> 
> Posting this q to save that time :)
> 
> any help be appreciated :)
> 
> Prashant

---
Nayan Hajratwala
http://agileshrugged.com
http://twitter.com/nhajratw
734.658.6032


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

Is there a plugin to automatically increment pom version ?

[Prashant Bhate]

Hi,

I know release plugin does that for you, but it also performs other scm
dependencices that is overkill for the project that I am currently working
with. Is there any plugin / goal that does just what is said in subject line
increase major/ minor version number?

If not I might actually end up writing a plugin that would use
http://mojo.codehaus.org/pomtools-maven-plugin/apidocs/org/codehaus/mojo/pomtools/versioning/DefaultVersionInfo.html

Posting this q to save that time :)

any help be appreciated :)

Prashant

Re: ScriptRunner exception when calling Rhino script in Ant build from maven antrun plugin

[Jacob Beard]

Seems probable. I'll look into it, thanks.

Jake

On Wed, Sep 8, 2010 at 10:48 AM, Wayne Fay  wrote:
>> Based on my research, it seems that ScriptRunner support is something
>> that needs to be built into Ant at compile-time, so perhaps the
>> version of ant downloaded by maven does not have this support built
>> into it.
>
> This documentation will probably be useful to you:
> http://maven.apache.org/plugins/maven-antrun-plugin/examples/customTasks.html
>
> I assume the Rhino bits are available in ant-nodeps artifact or
> similar, but you'd have to ask the Ant crew or figure it out yourself.
>
> Wayne
>
> -
> 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

Re: ScriptRunner exception when calling Rhino script in Ant build from maven antrun plugin

[Wayne Fay]

> Based on my research, it seems that ScriptRunner support is something
> that needs to be built into Ant at compile-time, so perhaps the
> version of ant downloaded by maven does not have this support built
> into it.

This documentation will probably be useful to you:
http://maven.apache.org/plugins/maven-antrun-plugin/examples/customTasks.html

I assume the Rhino bits are available in ant-nodeps artifact or
similar, but you'd have to ask the Ant crew or figure it out yourself.

Wayne

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

Re: sharing assembly descriptor

[Ron Wheeler]

assembly-desc.xml  != assembly-des.xml

Is this a typo in your e-mail?

You might consider posting your POM and a complete description of your file 
structure.

Ron


On 08/09/2010 4:31 AM, mremerson...@aim.com wrote:

Thanks for that,

but unfortunately its still not working for me.

My "Assembly-Descriptor" project now has the assembly-desc.xml under 
src/main/resources/assemblies. In the resulting jar file I see the package "assemblies" 
with the xml.

In the rest projects i didnt change anything.

My project "Assembly-project" has the dependency to the Descriptor project, but 
I get the same error.

Interesstingly it says

[4] [INFO] Failed to resolve classpath resource: assemblies/assembly-des.xml 
from classloader: org.codehaus.classworlds.realmclassloa...@7c3885


but in the deps of the project there is the descriptor project and with it the 
xml file :-(

I'm using maven2 and the maven-assembly-plugin in 2.2-beta-5.

Anymore hints for that ?

Thanks




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

Plans to release Maven 3.0

[Brian Fox]

On the dev list we've been discussing more formal plans to drive to
the Maven 3.0 final release. The plan is to release weekly release
candidate releases with the goal of having 3.0 final by the beginning
of October. So far Maven 3.0 beta 3 is pretty stable with only a
couple of regressions identified. We need your help to determine what
else needs to be fixed before the final release. So if you haven't
yet, we would like you to grab the latest 3.x build and give us your
feedback. You can find the download link here:
http://maven.apache.org/download.html


--Brian
Apache Maven PMC Chair

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

ScriptRunner exception when calling Rhino script in Ant build from maven antrun plugin

[Jacob Beard]

Hi,

I'm trying to call an ant build file from maven using the antrun
plugin. The task being called contains a Rhino script element, and
it's throwing the following error when attempting to execute it:

java.lang.ClassNotFoundException:
org.apache.tools.ant.util.optional.ScriptRunner

Based on my research, it seems that ScriptRunner support is something
that needs to be built into Ant at compile-time, so perhaps the
version of ant downloaded by maven does not have this support built
into it.

If anyone has any ideas as to how I could make this work, I'd greatly
appreciate it if you could let me know. Thanks,

Jake

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

Re: Build Helper Plugin: remove-project-artifact always removes all versions?

[Jeff MAURY]

Yes, the parameter name is the one used in the configuration section of the
pom.xml file. In order to set it from the command line, the parameter has
also an expression tag that allows to specify the default value (which may
be dynamically computed by Maven at runtime). In our case, the expression is
${buildhelper.removeAll} so you must set a property called
buildhelper.removeAll on the command line in order to set its value.

Regards
Jeff MAURY

On Wed, Sep 8, 2010 at 2:34 PM, Lewis, Eric  wrote:

> Hi Jeff
>
> Thanks, that worked!
>
> However, I'm now confused  :-)
>
> According to
> http://mojo.codehaus.org/build-helper-maven-plugin/remove-project-artifact-mojo.htmlthe
>  parameter is called "removeAll".
> My understanding of plugin parameters on the command line was that you just
> use them with -D
> Am I wrong?
>
> Best regards,
> Eric
>
> -Ursprüngliche Nachricht-
> Von: jeffma...@gmail.com [mailto:jeffma...@gmail.com] Im Auftrag von Jeff
> MAURY
> Gesendet: Mittwoch, 8. September 2010 14:25
> An: Maven Users List
> Betreff: Re: Build Helper Plugin: remove-project-artifact always removes
> all versions?
>
> You should use -Dbuildhelper.removeAll=true instead.
>
> Regards
> Jeff MAURY
>
> On Wed, Sep 8, 2010 at 2:20 PM, Lewis, Eric  wrote:
>
> > Hi
> >
> > I'm trying to remove a certain version of an artifact within my local
> repo.
> > I've written a small test script which downloads joda-time 1.0 and 1.6
> > Both versions exist with their directories in my local repo.
> >
> > Then I download the POM for 1.6 into a temporary directory, enter that
> > directory, delete the  from the POM and then call
> > Maven:
> > mvn build-helper:remove-project-artifact -DremoveAll=false
> >
> > However, that removes *all* versions in the local repo.
> >
> > Unless I understand "removeAll" wrongly, it should only remove 1.6...
> >
> >
> > When running Maven in debug mode, I get
> >
> > [DEBUG] Configuring mojo
> > 'org.codehaus.mojo:build-helper-maven-plugin:1.5:remove-project-artifact'
> > -->
> > [DEBUG]   (f) localRepository =
> > Repository[local|file://C:/jp/maven-repository]
> > [DEBUG]   (f) project = MavenProject: joda-time:joda-time:1.6 @
> > c:\jp\esv-projects\client\temp\pom.xml
> > [DEBUG]   (f) removeAll = true
> > [DEBUG] -- end configuration --
> > [INFO] [build-helper:remove-project-artifact {execution: default-cli}]
> > [INFO] C:\jp\maven-repository\joda-time\joda-time removed.
> >
> > Am I doing something wrong or is this a bug?
> >
> > Best regards,
> > Eric
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
>
> --
> "Legacy code" often differs from its suggested alternative by actually
> working and scaling.
>  - Bjarne Stroustrup
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.twitter.com/jeffmaury
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

AW: Build Helper Plugin: remove-project-artifact always removes all versions?

[Lewis, Eric]

Hi Jeff

Thanks, that worked!

However, I'm now confused  :-)

According to 
http://mojo.codehaus.org/build-helper-maven-plugin/remove-project-artifact-mojo.html
 the parameter is called "removeAll".
My understanding of plugin parameters on the command line was that you just use 
them with -D
Am I wrong?

Best regards,
Eric 

-Ursprüngliche Nachricht-
Von: jeffma...@gmail.com [mailto:jeffma...@gmail.com] Im Auftrag von Jeff MAURY
Gesendet: Mittwoch, 8. September 2010 14:25
An: Maven Users List
Betreff: Re: Build Helper Plugin: remove-project-artifact always removes all 
versions?

You should use -Dbuildhelper.removeAll=true instead.

Regards
Jeff MAURY

On Wed, Sep 8, 2010 at 2:20 PM, Lewis, Eric  wrote:

> Hi
>
> I'm trying to remove a certain version of an artifact within my local repo.
> I've written a small test script which downloads joda-time 1.0 and 1.6
> Both versions exist with their directories in my local repo.
>
> Then I download the POM for 1.6 into a temporary directory, enter that
> directory, delete the  from the POM and then call
> Maven:
> mvn build-helper:remove-project-artifact -DremoveAll=false
>
> However, that removes *all* versions in the local repo.
>
> Unless I understand "removeAll" wrongly, it should only remove 1.6...
>
>
> When running Maven in debug mode, I get
>
> [DEBUG] Configuring mojo
> 'org.codehaus.mojo:build-helper-maven-plugin:1.5:remove-project-artifact'
> -->
> [DEBUG]   (f) localRepository =
> Repository[local|file://C:/jp/maven-repository]
> [DEBUG]   (f) project = MavenProject: joda-time:joda-time:1.6 @
> c:\jp\esv-projects\client\temp\pom.xml
> [DEBUG]   (f) removeAll = true
> [DEBUG] -- end configuration --
> [INFO] [build-helper:remove-project-artifact {execution: default-cli}]
> [INFO] C:\jp\maven-repository\joda-time\joda-time removed.
>
> Am I doing something wrong or is this a bug?
>
> Best regards,
> Eric
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

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

Re: Build Helper Plugin: remove-project-artifact always removes all versions?

[Jeff MAURY]

You should use -Dbuildhelper.removeAll=true instead.

Regards
Jeff MAURY

On Wed, Sep 8, 2010 at 2:20 PM, Lewis, Eric  wrote:

> Hi
>
> I'm trying to remove a certain version of an artifact within my local repo.
> I've written a small test script which downloads joda-time 1.0 and 1.6
> Both versions exist with their directories in my local repo.
>
> Then I download the POM for 1.6 into a temporary directory, enter that
> directory, delete the  from the POM and then call
> Maven:
> mvn build-helper:remove-project-artifact -DremoveAll=false
>
> However, that removes *all* versions in the local repo.
>
> Unless I understand "removeAll" wrongly, it should only remove 1.6...
>
>
> When running Maven in debug mode, I get
>
> [DEBUG] Configuring mojo
> 'org.codehaus.mojo:build-helper-maven-plugin:1.5:remove-project-artifact'
> -->
> [DEBUG]   (f) localRepository =
> Repository[local|file://C:/jp/maven-repository]
> [DEBUG]   (f) project = MavenProject: joda-time:joda-time:1.6 @
> c:\jp\esv-projects\client\temp\pom.xml
> [DEBUG]   (f) removeAll = true
> [DEBUG] -- end configuration --
> [INFO] [build-helper:remove-project-artifact {execution: default-cli}]
> [INFO] C:\jp\maven-repository\joda-time\joda-time removed.
>
> Am I doing something wrong or is this a bug?
>
> Best regards,
> Eric
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
"Legacy code" often differs from its suggested alternative by actually
working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

Build Helper Plugin: remove-project-artifact always removes all versions?

[Lewis, Eric]

Hi

I'm trying to remove a certain version of an artifact within my local repo. 
I've written a small test script which downloads joda-time 1.0 and 1.6
Both versions exist with their directories in my local repo.

Then I download the POM for 1.6 into a temporary directory, enter that 
directory, delete the  from the POM and then call Maven:
mvn build-helper:remove-project-artifact -DremoveAll=false

However, that removes *all* versions in the local repo.

Unless I understand "removeAll" wrongly, it should only remove 1.6...


When running Maven in debug mode, I get

[DEBUG] Configuring mojo 
'org.codehaus.mojo:build-helper-maven-plugin:1.5:remove-project-artifact' -->
[DEBUG]   (f) localRepository = Repository[local|file://C:/jp/maven-repository]
[DEBUG]   (f) project = MavenProject: joda-time:joda-time:1.6 @ 
c:\jp\esv-projects\client\temp\pom.xml
[DEBUG]   (f) removeAll = true
[DEBUG] -- end configuration --
[INFO] [build-helper:remove-project-artifact {execution: default-cli}]
[INFO] C:\jp\maven-repository\joda-time\joda-time removed.

Am I doing something wrong or is this a bug?

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

Archetype plugin 2.0-alpha-6 release?

[Lóránt Pintér]

Hi,

I'm fighting with http://jira.codehaus.org/browse/ARCHETYPE-202. It
seems that all issues for 2.0-alpha-6 have been fixed (among then
ARCHETYPE-202) before 20th Aug. Can 2.0-alpha-6 be released, please?

Thanks,
Lóránt

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

Re: Mavin Dependency Management on Dynamic Web Project

[Justin Edelson]

It's spelled Maven :)

This question would probably be better posed to the m2eclipse mailing list.

But yes, you will either need to change change the warSourceDirectory
parameter of the maven-war-plugin or adopt the Maven directory structure
(src/main/webapp instead of WebContent). The latter would be better from
a Maven perspective.

Justin

On 9/8/10 6:34 AM, relliott wrote:
> 
> Hi, 
> Eclipse Helios 
> mss-1.3.2-jboss-jdk6-5.1.0.GA-1008061811 
> m2eclipse 0.10.0.2 
> mweclipse extras 
> I created a Dynamic WebProject and then Mavin -> Enable Dependency 
> Management. I added my depencies then did Mavin clean and then Mavin 
> Package. I receive the following build error: 
> Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.1- 
> alpha-1:war (default-war) on project : Error assembling WAR: 
> Deployment descriptor: \\WEB-INF\web.xml does not exist. - 
>> [Help 1]. 
> 
> The project wizard created the  web.xml under WebContent\WEB-INF 
> \web.xml. My pom.xml does not contain any path info. Do I need to 
> modify pom.xml? 
> 
> Thanks...


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

Mavin Dependency Management on Dynamic Web Project

[relliott]

Hi, 
Eclipse Helios 
mss-1.3.2-jboss-jdk6-5.1.0.GA-1008061811 
m2eclipse 0.10.0.2 
mweclipse extras 
I created a Dynamic WebProject and then Mavin -> Enable Dependency 
Management. I added my depencies then did Mavin clean and then Mavin 
Package. I receive the following build error: 
Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.1- 
alpha-1:war (default-war) on project : Error assembling WAR: 
Deployment descriptor: \\WEB-INF\web.xml does not exist. - 
> [Help 1]. 

The project wizard created the  web.xml under WebContent\WEB-INF 
\web.xml. My pom.xml does not contain any path info. Do I need to 
modify pom.xml? 

Thanks...
-- 
View this message in context: 
http://maven.40175.n5.nabble.com/Mavin-Dependency-Management-on-Dynamic-Web-Project-tp2807663p2807663.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

[ANN] Release Maven Site Plugin 3.0-beta-2 for maven 3

[Olivier Lamy]

Hi,
The Maven team is pleased to announce the release of the Maven Site
Plugin, version 3.0-beta-2 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-3.

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.

You should specify the version in the  section of your project's POM:


 org.apache.maven.plugins
 maven-site-plugin
 3.0-beta-2


Release Notes - Maven Site Plugin - Version 3.0-beta-2
** Bug
* [MSITE-481] - Deploy site:deploy not working for maven 3 for DAV

** Improvement
* [MSITE-498] - Update to last maven-core 3.0-beta-3

You can read more in the plugin documentation [1]
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.

Have Fun !
-- 
The Maven  Team

[1] http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-2
[2] https://cwiki.apache.org/confluence/x/sokr

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

Re: sharing assembly descriptor

[mremersoncod]

Thanks for that,

but unfortunately its still not working for me.

My "Assembly-Descriptor" project now has the assembly-desc.xml under 
src/main/resources/assemblies. In the resulting jar file I see the package 
"assemblies" with the xml.

In the rest projects i didnt change anything.

My project "Assembly-project" has the dependency to the Descriptor project, but 
I get the same error.

Interesstingly it says

[4] [INFO] Failed to resolve classpath resource: assemblies/assembly-des.xml 
from classloader: org.codehaus.classworlds.realmclassloa...@7c3885

 
but in the deps of the project there is the descriptor project and with it the 
xml file :-(

I'm using maven2 and the maven-assembly-plugin in 2.2-beta-5.

Anymore hints for that ?

Thanks

 


 

 

-Original Message-
From: Vincent Latombe 
To: Maven Users List 
Sent: Tue, Sep 7, 2010 7:26 pm
Subject: Re: sharing assembly descriptor


Hi,



- first, you need to put your assembly under

src/main/resources/*assemblies* (as

indicated in the link you provided)

- then, you should be able to reference either the xml using the descriptor

tag like you did



2010/9/7 



> Hi all,

>

> I'm trying to use a shared assembly descriptor as described in

> http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html

>

> Unfortunately it fails with

>

> Error:

> java.net.MalformedURLException: no protocol: assembly-desc.xml

>

> My setup is:

>

> 1) A project calles "Assembly-Descriptor" which has the file

> "assembly-desc.xml" under src/main/resources. This is packaged in a jar and

> installed in my local repository

> 2) A project called "Assembly-parent" which is the parent pom for all

> projects which require the descriptor. This is packaged as pom and the pom

> contains:

> 

>

>de.test-fw

>Assembly-Descriptor

>0.0.1-SNAPSHOT

>

>

>

>

>

>

>maven-assembly-plugin

>2.2-beta-5

>

>

>assembly-desc.xml

>

>

>

>

>make-assembly

>package

>

>single

>

>

>

>

>

>

>

> 3) A project called "Assembly-project", which finally shall use the shared

> descriptor. Its packaged as jar and has the "Assembly-parent" as parent pom.

> Its pom only contains additionally

> 

>

>

>maven-assembly-plugin

>

>

>

>

> Running this results in the error that it does not find the

> assembly-desc.xml file. The "Assembly-project" does have the dependency to

> the "Assembly-Descriptor" project.

>

> What is going wrong ?

>

> Thanks

>

>

>

>

>

>

>





-- 

Vincent




 

Re: Cargo re-architecture

[Dan Tran]

this must be a bot??

-D

On Tue, Sep 7, 2010 at 9:51 AM, Martin Gainty  wrote:
>
> I spent some refactoring the many impl classes for what seems to be way too 
> many Abstract Classes and interfaces in cargo-plugin
> I'm wondering if a re-architec to placing as much functionality into 
> base-classes or possibly Template which could be concretised using 
> configuration parameters to a more user-configurable templateFactory is a 
> better long-term solution
> This way we could modify the cargo impl classes to only what is absolutely 
> neceesary for weblogic, glassfish, jboss and tomcat deployments
>
> Continously repeating copy/paste operations for identical method bodies for 
> all environments seems more labour-intensive than productive
>
> ?
> Martin Gainty
> __
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
>
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
> sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
> oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich 
> dem Austausch von Informationen und entfaltet keine rechtliche 
> Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen 
> wir keine Haftung fuer den Inhalt uebernehmen.
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
> destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
> l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci 
> est interdite. Ce message sert à l'information seulement et n'aura pas 
> n'importe quel effet légalement obligatoire. Étant donné que les email 
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter 
> aucune responsabilité pour le contenu fourni.
>
>
>

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