RE: maven version management in ant
It is in the docs, but a second set of eyes never hurt.
http://maven.apache.org/ant-tasks.html
Glad I could help.
Chris
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 09 January, 2007 12:26
> To: Maven Users List
> Subject: RE: maven version management in ant
>
> That seems to be working!
>
> Thank you so much for this!
>
> How was one to know that pathId existed?
>
> -Original Message-
> From: Chris Hilton [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 09, 2007 11:16 AM
> To: Maven Users List
> Subject: RE: maven version management in ant
>
> Perhaps I'm not following, but how is the
> my.compile.dependency.fileset different from what you want?
> Unless you really wanted a path reference, in which case you
> replace filesetId with pathId. Or you want that in a
> property? Then add:
>
> refid="my.compile.dependency.fileset"/>
>
> Am I missing something here?
>
> Chris
>
> > -Original Message-
> > From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, 09 January, 2007 09:24
> > To: Maven Users List
> > Subject: RE: maven version management in ant
> >
> > All of these are blank:
> > ${maven.dependency.classpath}
> > ${maven.compile.classpath}
> > ${maven.runtime.classpath}
> > ${maven.test.classpath}
> > ${maven.plugin.classpath}
> >
> > Here is my full target:
> >
> >
> >
> > > filesetId="my.compile.dependency.fileset"
> > usescope="compile" verbose="true">
> >
> >
> > The version is ${project.version}
> > ${project.build.directory}
> > ${project.name}
> > ${project.dependencies}
> > ${maven.dependency.classpath}
> > ${maven.compile.classpath}
> > ${maven.runtime.classpath}
> > ${maven.test.classpath}
> > ${maven.plugin.classpath}
> >
> >
> >
> > As a crappy hack, from:
> >
> > > filesetId="my.compile.dependency.fileset"
> > usescope="compile" verbose="true">
> >
> >
> >
> > I can use that as a fileset to copy from the m2 repository to some
> > local folder for building (and then I'll just include
> anything in that
> > folder).
> >
> > But this stinks as when we have 10 projects, these
> dependent jars will
> > be all over the place.
> >
> > This feels like a bug and limited functionality when using the
> > following technique to build with ant and manage dependencies with
> > maven2:
> >
> > > xmlns:artifact="antlib:org.apache.maven.artifact.ant">
> >
> > -Original Message-
> > From: Barrett Nuzum [mailto:[EMAIL PROTECTED]
> > Sent: Monday, January 08, 2007 11:10 AM
> > To: Maven Users List
> > Subject: RE: maven version management in ant
> >
> > EJ:
> >
> > Unsure if it's the same in maven2, but "maven.dependency.classpath"
> > contained dependencies in m1.
> > I have a feeling you'll have to splice
> maven.compile.classpath in with
> > it, though.
> >
> > http://wiki.astrogrid.org/bin/view/Astrogrid/UsefulMavenNotes#
> > How_to_fin
> > d_out_what_is_actually
> >
> > HTH
> >
> > Barrett
> >
> > ::
> > Barrett Nuzum
> > Consultant, Skill Development
> > Direct: 918.640.4414
> > Fax: 972.789.1340
> >
> > Valtech Technologies, Inc.
> > 5080 Spectrum Drive
> > Suite 700 West
> > Addison, Texas 75001
> > www.valtech.com <http://www.valtech.com>
> > making IT business friendly
> >
> >
> >
> >
> > From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> > Sent: Mon 1/8/2007 8:19 AM
> > To: Maven Users List
> > Subject: RE: maven version management in ant
> >
> >
> >
> > Bump - I could really use some feed back here people, this has me
> > completely wedged...
> >
> > -Original Message-
> > From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> > Sent: Friday, January 05, 2007 3:56 PM
> > To: Maven Users List
> > Subject: RE: maven version management in ant
> >
> > I made it a bit further:
> >
> > > xmlns:artifact="antlib:org.apache.maven.artifact.ant">
>
RE: maven version management in ant
That seems to be working!
Thank you so much for this!
How was one to know that pathId existed?
-Original Message-
From: Chris Hilton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 09, 2007 11:16 AM
To: Maven Users List
Subject: RE: maven version management in ant
Perhaps I'm not following, but how is the my.compile.dependency.fileset
different from what you want? Unless you really wanted a path reference,
in which case you replace filesetId with pathId. Or you want that in a
property? Then add:
Am I missing something here?
Chris
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 09 January, 2007 09:24
> To: Maven Users List
> Subject: RE: maven version management in ant
>
> All of these are blank:
> ${maven.dependency.classpath}
> ${maven.compile.classpath}
> ${maven.runtime.classpath}
> ${maven.test.classpath}
> ${maven.plugin.classpath}
>
> Here is my full target:
>
>
>
> filesetId="my.compile.dependency.fileset"
> usescope="compile" verbose="true">
>
>
> The version is ${project.version}
> ${project.build.directory}
> ${project.name}
> ${project.dependencies}
> ${maven.dependency.classpath}
> ${maven.compile.classpath}
> ${maven.runtime.classpath}
> ${maven.test.classpath}
> ${maven.plugin.classpath}
>
>
>
> As a crappy hack, from:
>
> filesetId="my.compile.dependency.fileset"
> usescope="compile" verbose="true">
>
>
>
> I can use that as a fileset to copy from the m2 repository to
> some local folder for building (and then I'll just include
> anything in that folder).
>
> But this stinks as when we have 10 projects, these dependent
> jars will be all over the place.
>
> This feels like a bug and limited functionality when using
> the following technique to build with ant and manage
> dependencies with maven2:
>
> xmlns:artifact="antlib:org.apache.maven.artifact.ant">
>
> -Original Message-
> From: Barrett Nuzum [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 08, 2007 11:10 AM
> To: Maven Users List
> Subject: RE: maven version management in ant
>
> EJ:
>
> Unsure if it's the same in maven2, but "maven.dependency.classpath"
> contained dependencies in m1.
> I have a feeling you'll have to splice
> maven.compile.classpath in with it, though.
>
> http://wiki.astrogrid.org/bin/view/Astrogrid/UsefulMavenNotes#
> How_to_fin
> d_out_what_is_actually
>
> HTH
>
> Barrett
>
> ::
> Barrett Nuzum
> Consultant, Skill Development
> Direct: 918.640.4414
> Fax: 972.789.1340
>
> Valtech Technologies, Inc.
> 5080 Spectrum Drive
> Suite 700 West
> Addison, Texas 75001
> www.valtech.com <http://www.valtech.com>
> making IT business friendly
>
>
>
>
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Mon 1/8/2007 8:19 AM
> To: Maven Users List
> Subject: RE: maven version management in ant
>
>
>
> Bump - I could really use some feed back here people, this
> has me completely wedged...
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 05, 2007 3:56 PM
> To: Maven Users List
> Subject: RE: maven version management in ant
>
> I made it a bit further:
>
> xmlns:artifact="antlib:org.apache.maven.artifact.ant">
>
>
>
> The version is ${project.version}
> ${project.build.directory}
> ${project.name}
> ${project.dependencies}
>
>
>
>
>
> destdir="target/classes"
> includes="**/*.java"
> classpathref="maven.project.classpath"
> debug="on"
> />
>
>
> Is the actual classpath used for compiling unavailable to ant
> as a property?
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 05, 2007 2:07 PM
> To: Maven Users List
> Subject: RE: maven version management in ant
>
> New question, so I'm loading via a pom.xml file, how can I
> reference the classpath (filled with dependencies)?
>
> xmlns:artifact="antlib:org.apache.maven.artifact.ant">
>
>
>
> The version is ${project.version}
> ${project.build.directory}
>
RE: maven version management in ant
Perhaps I'm not following, but how is the my.compile.dependency.fileset
different from what you want? Unless you really wanted a path reference,
in which case you replace filesetId with pathId. Or you want that in a
property? Then add:
Am I missing something here?
Chris
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 09 January, 2007 09:24
> To: Maven Users List
> Subject: RE: maven version management in ant
>
> All of these are blank:
> ${maven.dependency.classpath}
> ${maven.compile.classpath}
> ${maven.runtime.classpath}
> ${maven.test.classpath}
> ${maven.plugin.classpath}
>
> Here is my full target:
>
>
>
> filesetId="my.compile.dependency.fileset"
> usescope="compile" verbose="true">
>
>
> The version is ${project.version}
> ${project.build.directory}
> ${project.name}
> ${project.dependencies}
> ${maven.dependency.classpath}
> ${maven.compile.classpath}
> ${maven.runtime.classpath}
> ${maven.test.classpath}
> ${maven.plugin.classpath}
>
>
>
> As a crappy hack, from:
>
> filesetId="my.compile.dependency.fileset"
> usescope="compile" verbose="true">
>
>
>
> I can use that as a fileset to copy from the m2 repository to
> some local folder for building (and then I'll just include
> anything in that folder).
>
> But this stinks as when we have 10 projects, these dependent
> jars will be all over the place.
>
> This feels like a bug and limited functionality when using
> the following technique to build with ant and manage
> dependencies with maven2:
>
> xmlns:artifact="antlib:org.apache.maven.artifact.ant">
>
> -Original Message-
> From: Barrett Nuzum [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 08, 2007 11:10 AM
> To: Maven Users List
> Subject: RE: maven version management in ant
>
> EJ:
>
> Unsure if it's the same in maven2, but "maven.dependency.classpath"
> contained dependencies in m1.
> I have a feeling you'll have to splice
> maven.compile.classpath in with it, though.
>
> http://wiki.astrogrid.org/bin/view/Astrogrid/UsefulMavenNotes#
> How_to_fin
> d_out_what_is_actually
>
> HTH
>
> Barrett
>
> ::
> Barrett Nuzum
> Consultant, Skill Development
> Direct: 918.640.4414
> Fax: 972.789.1340
>
> Valtech Technologies, Inc.
> 5080 Spectrum Drive
> Suite 700 West
> Addison, Texas 75001
> www.valtech.com <http://www.valtech.com>
> making IT business friendly
>
>
>
>
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Mon 1/8/2007 8:19 AM
> To: Maven Users List
> Subject: RE: maven version management in ant
>
>
>
> Bump - I could really use some feed back here people, this
> has me completely wedged...
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 05, 2007 3:56 PM
> To: Maven Users List
> Subject: RE: maven version management in ant
>
> I made it a bit further:
>
> xmlns:artifact="antlib:org.apache.maven.artifact.ant">
>
>
>
> The version is ${project.version}
> ${project.build.directory}
> ${project.name}
> ${project.dependencies}
>
>
>
>
>
> destdir="target/classes"
> includes="**/*.java"
> classpathref="maven.project.classpath"
> debug="on"
> />
>
>
> Is the actual classpath used for compiling unavailable to ant
> as a property?
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 05, 2007 2:07 PM
> To: Maven Users List
> Subject: RE: maven version management in ant
>
> New question, so I'm loading via a pom.xml file, how can I
> reference the classpath (filled with dependencies)?
>
> xmlns:artifact="antlib:org.apache.maven.artifact.ant">
>
>
>
> The version is ${project.version}
> ${project.build.directory}
>
>
>
>
>
> destdir="target/classes"
> includes="**/*.java"
> classpathref="maven.project.classpath"
> debug="on"
> />
RE: maven version management in ant
All of these are blank:
${maven.dependency.classpath}
${maven.compile.classpath}
${maven.runtime.classpath}
${maven.test.classpath}
${maven.plugin.classpath}
Here is my full target:
The version is ${project.version}
${project.build.directory}
${project.name}
${project.dependencies}
${maven.dependency.classpath}
${maven.compile.classpath}
${maven.runtime.classpath}
${maven.test.classpath}
${maven.plugin.classpath}
As a crappy hack, from:
I can use that as a fileset to copy from the m2 repository to some local
folder for building (and then I'll just include anything in that
folder).
But this stinks as when we have 10 projects, these dependent jars will
be all over the place.
This feels like a bug and limited functionality when using the following
technique to build with ant and manage dependencies with maven2:
-Original Message-
From: Barrett Nuzum [mailto:[EMAIL PROTECTED]
Sent: Monday, January 08, 2007 11:10 AM
To: Maven Users List
Subject: RE: maven version management in ant
EJ:
Unsure if it's the same in maven2, but "maven.dependency.classpath"
contained dependencies in m1.
I have a feeling you'll have to splice maven.compile.classpath in with
it, though.
http://wiki.astrogrid.org/bin/view/Astrogrid/UsefulMavenNotes#How_to_fin
d_out_what_is_actually
HTH
Barrett
::
Barrett Nuzum
Consultant, Skill Development
Direct: 918.640.4414
Fax: 972.789.1340
Valtech Technologies, Inc.
5080 Spectrum Drive
Suite 700 West
Addison, Texas 75001
www.valtech.com <http://www.valtech.com>
making IT business friendly
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Mon 1/8/2007 8:19 AM
To: Maven Users List
Subject: RE: maven version management in ant
Bump - I could really use some feed back here people, this has me
completely wedged...
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 3:56 PM
To: Maven Users List
Subject: RE: maven version management in ant
I made it a bit further:
The version is ${project.version}
${project.build.directory}
${project.name}
${project.dependencies}
Is the actual classpath used for compiling unavailable to ant as a
property?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 2:07 PM
To: Maven Users List
Subject: RE: maven version management in ant
New question, so I'm loading via a pom.xml file, how can I reference the
classpath (filled with dependencies)?
The version is ${project.version}
${project.build.directory}
???
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 3:49 PM
To: Maven Users List
Subject: RE: maven version management in ant
Sorry - I'm building with jdk 1.5.1 now and this is gone.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 1:03 PM
To: Maven Users List
Subject: RE: maven version management in ant
I'm trying this out with a VERY simple example (download one
dependency), but I'm getting this:
BUILD FAILED
java.lang.NoSuchMethodError
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1225)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut
or.java:40)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
--- Nested Exception ---
java.lang.NoSuchMethodError
at
org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
on.(ComponentConfigurationException.java:24)
at
org.codehaus.plexus.component.configurator.converters.basic.IntConverter
.fromString(IntConverter.java:46)
at
org.codehaus.plexus.component.configurator.converters.basic.AbstractBasi
cConverter.fromConfiguration(AbstractBasicConverter.java:61)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSett
er.configure(ComponentValueSetter.java:207)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
thFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:1
37)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
nfigureComponent(BasicComponentConfigurator.java:56)
at
org.codehaus.plexus.c
RE: maven version management in ant
This is a bit backward, I'm using ant to build and maven to manage
dependencies.
See:
http://maven.apache.org/ant-tasks.html
-Original Message-
From: Sean Hennessy [mailto:[EMAIL PROTECTED]
Sent: Monday, January 08, 2007 1:30 PM
To: Maven Users List
Subject: RE: maven version management in ant
FWIW
snippet of working maven pom.xml and ant build.xml
# pom.xml partial
[snip]
maven-antrun-plugin
pre-site
pom.xml: timestamp ${TODAY_UK}
run
[snip]
# build.xml
[snip]
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Monday, January 08, 2007 6:19 AM
To: Maven Users List
Subject: RE: maven version management in ant
Bump - I could really use some feed back here people, this has me
completely wedged...
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 3:56 PM
To: Maven Users List
Subject: RE: maven version management in ant
I made it a bit further:
The version is ${project.version}
${project.build.directory}
${project.name}
${project.dependencies}
Is the actual classpath used for compiling unavailable to ant as a
property?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 2:07 PM
To: Maven Users List
Subject: RE: maven version management in ant
New question, so I'm loading via a pom.xml file, how can I reference the
classpath (filled with dependencies)?
The version is ${project.version}
${project.build.directory}
???
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 3:49 PM
To: Maven Users List
Subject: RE: maven version management in ant
Sorry - I'm building with jdk 1.5.1 now and this is gone.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 1:03 PM
To: Maven Users List
Subject: RE: maven version management in ant
I'm trying this out with a VERY simple example (download one
dependency), but I'm getting this:
BUILD FAILED
java.lang.NoSuchMethodError
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1225)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut
or.java:40)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
--- Nested Exception ---
java.lang.NoSuchMethodError
at
org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
on.(ComponentConfigurationException.java:24)
at
org.codehaus.plexus.component.configurator.converters.basic.IntConverter
.fromString(IntConverter.java:46)
at
org.codehaus.plexus.component.configurator.converters.basic.AbstractBasi
cConverter.fromConfiguration(AbstractBasicConverter.java:61)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSett
er.configure(ComponentValueSetter.java:207)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
thFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:1
37)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
nfigureComponent(BasicComponentConfigurator.java:56)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:54)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:47)
at
org.codehaus.plexus.personality.plexus.lifecycle.phase.AutoConfigurePhas
e.execute(AutoConfigurePhase.java:39)
at
org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif
ecycleHandler.java:101)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.startComp
onentLifecycle(AbstractComponentManager.java:105)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.createCom
ponentInstance(AbstractComponentManager.java:95)
at
org.codehaus.plexus.component.manager.ClassicSingletonCompo
RE: maven version management in ant
FWIW
snippet of working maven pom.xml and ant build.xml
# pom.xml partial
[snip]
maven-antrun-plugin
pre-site
pom.xml: timestamp ${TODAY_UK}
run
[snip]
# build.xml
[snip]
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Monday, January 08, 2007 6:19 AM
To: Maven Users List
Subject: RE: maven version management in ant
Bump - I could really use some feed back here people, this has me
completely wedged...
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 3:56 PM
To: Maven Users List
Subject: RE: maven version management in ant
I made it a bit further:
The version is ${project.version}
${project.build.directory}
${project.name}
${project.dependencies}
Is the actual classpath used for compiling unavailable to ant as a
property?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 2:07 PM
To: Maven Users List
Subject: RE: maven version management in ant
New question, so I'm loading via a pom.xml file, how can I reference the
classpath (filled with dependencies)?
The version is ${project.version}
${project.build.directory}
???
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 3:49 PM
To: Maven Users List
Subject: RE: maven version management in ant
Sorry - I'm building with jdk 1.5.1 now and this is gone.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 1:03 PM
To: Maven Users List
Subject: RE: maven version management in ant
I'm trying this out with a VERY simple example (download one
dependency), but I'm getting this:
BUILD FAILED
java.lang.NoSuchMethodError
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1225)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut
or.java:40)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
--- Nested Exception ---
java.lang.NoSuchMethodError
at
org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
on.(ComponentConfigurationException.java:24)
at
org.codehaus.plexus.component.configurator.converters.basic.IntConverter
.fromString(IntConverter.java:46)
at
org.codehaus.plexus.component.configurator.converters.basic.AbstractBasi
cConverter.fromConfiguration(AbstractBasicConverter.java:61)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSett
er.configure(ComponentValueSetter.java:207)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
thFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:1
37)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
nfigureComponent(BasicComponentConfigurator.java:56)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:54)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:47)
at
org.codehaus.plexus.personality.plexus.lifecycle.phase.AutoConfigurePhas
e.execute(AutoConfigurePhase.java:39)
at
org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif
ecycleHandler.java:101)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.startComp
onentLifecycle(AbstractComponentManager.java:105)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.createCom
ponentInstance(AbstractComponentManager.java:95)
at
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.g
etComponent(ClassicSingletonComponentManager.java:92)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:331)
at
org.codehaus.plexus.DefaultPlexusContainer.initializeLoggerManager(Defau
ltPlexusContainer.j
RE: maven version management in ant
EJ:
Unsure if it's the same in maven2, but "maven.dependency.classpath" contained
dependencies in m1.
I have a feeling you'll have to splice maven.compile.classpath in with it,
though.
http://wiki.astrogrid.org/bin/view/Astrogrid/UsefulMavenNotes#How_to_find_out_what_is_actually
HTH
Barrett
::
Barrett Nuzum
Consultant, Skill Development
Direct: 918.640.4414
Fax: 972.789.1340
Valtech Technologies, Inc.
5080 Spectrum Drive
Suite 700 West
Addison, Texas 75001
www.valtech.com <http://www.valtech.com>
making IT business friendly
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Mon 1/8/2007 8:19 AM
To: Maven Users List
Subject: RE: maven version management in ant
Bump - I could really use some feed back here people, this has me
completely wedged...
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 3:56 PM
To: Maven Users List
Subject: RE: maven version management in ant
I made it a bit further:
The version is ${project.version}
${project.build.directory}
${project.name}
${project.dependencies}
Is the actual classpath used for compiling unavailable to ant as a
property?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 2:07 PM
To: Maven Users List
Subject: RE: maven version management in ant
New question, so I'm loading via a pom.xml file, how can I reference the
classpath (filled with dependencies)?
The version is ${project.version}
${project.build.directory}
???
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 3:49 PM
To: Maven Users List
Subject: RE: maven version management in ant
Sorry - I'm building with jdk 1.5.1 now and this is gone.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 1:03 PM
To: Maven Users List
Subject: RE: maven version management in ant
I'm trying this out with a VERY simple example (download one
dependency), but I'm getting this:
BUILD FAILED
java.lang.NoSuchMethodError
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1225)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut
or.java:40)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
--- Nested Exception ---
java.lang.NoSuchMethodError
at
org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
on.(ComponentConfigurationException.java:24)
at
org.codehaus.plexus.component.configurator.converters.basic.IntConverter
.fromString(IntConverter.java:46)
at
org.codehaus.plexus.component.configurator.converters.basic.AbstractBasi
cConverter.fromConfiguration(AbstractBasicConverter.java:61)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSett
er.configure(ComponentValueSetter.java:207)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
thFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:1
37)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
nfigureComponent(BasicComponentConfigurator.java:56)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:54)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:47)
at
org.codehaus.plexus.personality.plexus.lifecycle.phase.AutoConfigurePhas
e.execute(AutoConfigurePhase.java:39)
at
org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif
ecycleHandler.java:101)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.startComp
onentLifecycle(AbstractComponentManager.java:105)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.createCom
ponentInstance(AbstractComponentManager.java:95)
at
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.g
etComponent(ClassicSingletonComponentManager.java:92)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:331)
at
org.codehaus.plexus.DefaultPlexusContainer.initializeLoggerManager(Defau
ltPlexusContainer.java:1204)
at
org.codehaus.plexus.DefaultPlexusContainer.initializ
RE: maven version management in ant
Bump - I could really use some feed back here people, this has me
completely wedged...
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 3:56 PM
To: Maven Users List
Subject: RE: maven version management in ant
I made it a bit further:
The version is ${project.version}
${project.build.directory}
${project.name}
${project.dependencies}
Is the actual classpath used for compiling unavailable to ant as a
property?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 2:07 PM
To: Maven Users List
Subject: RE: maven version management in ant
New question, so I'm loading via a pom.xml file, how can I reference the
classpath (filled with dependencies)?
The version is ${project.version}
${project.build.directory}
???
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 3:49 PM
To: Maven Users List
Subject: RE: maven version management in ant
Sorry - I'm building with jdk 1.5.1 now and this is gone.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 1:03 PM
To: Maven Users List
Subject: RE: maven version management in ant
I'm trying this out with a VERY simple example (download one
dependency), but I'm getting this:
BUILD FAILED
java.lang.NoSuchMethodError
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1225)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut
or.java:40)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
--- Nested Exception ---
java.lang.NoSuchMethodError
at
org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
on.(ComponentConfigurationException.java:24)
at
org.codehaus.plexus.component.configurator.converters.basic.IntConverter
.fromString(IntConverter.java:46)
at
org.codehaus.plexus.component.configurator.converters.basic.AbstractBasi
cConverter.fromConfiguration(AbstractBasicConverter.java:61)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSett
er.configure(ComponentValueSetter.java:207)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
thFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:1
37)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
nfigureComponent(BasicComponentConfigurator.java:56)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:54)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:47)
at
org.codehaus.plexus.personality.plexus.lifecycle.phase.AutoConfigurePhas
e.execute(AutoConfigurePhase.java:39)
at
org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif
ecycleHandler.java:101)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.startComp
onentLifecycle(AbstractComponentManager.java:105)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.createCom
ponentInstance(AbstractComponentManager.java:95)
at
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.g
etComponent(ClassicSingletonComponentManager.java:92)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:331)
at
org.codehaus.plexus.DefaultPlexusContainer.initializeLoggerManager(Defau
ltPlexusContainer.java:1204)
at
org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusConta
iner.java:642)
at org.codehaus.plexus.embed.Embedder.start(Embedder.java:216)
at org.codehaus.plexus.embed.Embedder.start(Embedder.java:183)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.getEmbedder(AbstractA
rtifactTask.java:312)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.lookup(AbstractArtifa
ctTask.java:276)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.createLocalArtifactRe
pository(AbstractArtifactTask.java:78)
at
org.apache.maven.artifact.ant.DependenciesTask.doExecute(DependenciesTas
k.java:75)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtif
actTask.java:451)
at
org.apache.tools.ant.Un
RE: maven version management in ant
I made it a bit further:
The version is ${project.version}
${project.build.directory}
${project.name}
${project.dependencies}
Is the actual classpath used for compiling unavailable to ant as a
property?
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, January 05, 2007 2:07 PM
To: Maven Users List
Subject: RE: maven version management in ant
New question, so I'm loading via a pom.xml file, how can I reference the
classpath (filled with dependencies)?
The version is ${project.version}
${project.build.directory}
???
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 3:49 PM
To: Maven Users List
Subject: RE: maven version management in ant
Sorry - I'm building with jdk 1.5.1 now and this is gone.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 1:03 PM
To: Maven Users List
Subject: RE: maven version management in ant
I'm trying this out with a VERY simple example (download one
dependency), but I'm getting this:
BUILD FAILED
java.lang.NoSuchMethodError
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1225)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut
or.java:40)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
--- Nested Exception ---
java.lang.NoSuchMethodError
at
org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
on.(ComponentConfigurationException.java:24)
at
org.codehaus.plexus.component.configurator.converters.basic.IntConverter
.fromString(IntConverter.java:46)
at
org.codehaus.plexus.component.configurator.converters.basic.AbstractBasi
cConverter.fromConfiguration(AbstractBasicConverter.java:61)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSett
er.configure(ComponentValueSetter.java:207)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
thFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:1
37)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
nfigureComponent(BasicComponentConfigurator.java:56)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:54)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:47)
at
org.codehaus.plexus.personality.plexus.lifecycle.phase.AutoConfigurePhas
e.execute(AutoConfigurePhase.java:39)
at
org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif
ecycleHandler.java:101)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.startComp
onentLifecycle(AbstractComponentManager.java:105)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.createCom
ponentInstance(AbstractComponentManager.java:95)
at
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.g
etComponent(ClassicSingletonComponentManager.java:92)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:331)
at
org.codehaus.plexus.DefaultPlexusContainer.initializeLoggerManager(Defau
ltPlexusContainer.java:1204)
at
org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusConta
iner.java:642)
at org.codehaus.plexus.embed.Embedder.start(Embedder.java:216)
at org.codehaus.plexus.embed.Embedder.start(Embedder.java:183)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.getEmbedder(AbstractA
rtifactTask.java:312)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.lookup(AbstractArtifa
ctTask.java:276)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.createLocalArtifactRe
pository(AbstractArtifactTask.java:78)
at
org.apache.maven.artifact.ant.DependenciesTask.doExecute(DependenciesTas
k.java:75)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtif
actTask.java:451)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at
org.apache.tools.ant.Project.
RE: maven version management in ant
New question, so I'm loading via a pom.xml file, how can I reference the
classpath (filled with dependencies)?
The version is ${project.version}
${project.build.directory}
???
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 3:49 PM
To: Maven Users List
Subject: RE: maven version management in ant
Sorry - I'm building with jdk 1.5.1 now and this is gone.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 03, 2007 1:03 PM
To: Maven Users List
Subject: RE: maven version management in ant
I'm trying this out with a VERY simple example (download one
dependency), but I'm getting this:
BUILD FAILED
java.lang.NoSuchMethodError
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1225)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut
or.java:40)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
--- Nested Exception ---
java.lang.NoSuchMethodError
at
org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
on.(ComponentConfigurationException.java:24)
at
org.codehaus.plexus.component.configurator.converters.basic.IntConverter
.fromString(IntConverter.java:46)
at
org.codehaus.plexus.component.configurator.converters.basic.AbstractBasi
cConverter.fromConfiguration(AbstractBasicConverter.java:61)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSett
er.configure(ComponentValueSetter.java:207)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
thFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:1
37)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
nfigureComponent(BasicComponentConfigurator.java:56)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:54)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent(AbstractComponentConfigurator.java:47)
at
org.codehaus.plexus.personality.plexus.lifecycle.phase.AutoConfigurePhas
e.execute(AutoConfigurePhase.java:39)
at
org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif
ecycleHandler.java:101)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.startComp
onentLifecycle(AbstractComponentManager.java:105)
at
org.codehaus.plexus.component.manager.AbstractComponentManager.createCom
ponentInstance(AbstractComponentManager.java:95)
at
org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.g
etComponent(ClassicSingletonComponentManager.java:92)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:331)
at
org.codehaus.plexus.DefaultPlexusContainer.initializeLoggerManager(Defau
ltPlexusContainer.java:1204)
at
org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusConta
iner.java:642)
at org.codehaus.plexus.embed.Embedder.start(Embedder.java:216)
at org.codehaus.plexus.embed.Embedder.start(Embedder.java:183)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.getEmbedder(AbstractA
rtifactTask.java:312)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.lookup(AbstractArtifa
ctTask.java:276)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.createLocalArtifactRe
pository(AbstractArtifactTask.java:78)
at
org.apache.maven.artifact.ant.DependenciesTask.doExecute(DependenciesTas
k.java:75)
at
org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtif
actTask.java:451)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut
or.java:40)
at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.
RE: maven version management in ant
Sorry - I'm building with jdk 1.5.1 now and this is gone. -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 03, 2007 1:03 PM To: Maven Users List Subject: RE: maven version management in ant I'm trying this out with a VERY simple example (download one dependency), but I'm getting this: BUILD FAILED java.lang.NoSuchMethodError at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1225) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut or.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) --- Nested Exception --- java.lang.NoSuchMethodError at org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti on.(ComponentConfigurationException.java:24) at org.codehaus.plexus.component.configurator.converters.basic.IntConverter .fromString(IntConverter.java:46) at org.codehaus.plexus.component.configurator.converters.basic.AbstractBasi cConverter.fromConfiguration(AbstractBasicConverter.java:61) at org.codehaus.plexus.component.configurator.converters.ComponentValueSett er.configure(ComponentValueSetter.java:207) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWi thFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:1 37) at org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co nfigureComponent(BasicComponentConfigurator.java:56) at org.codehaus.plexus.component.configurator.AbstractComponentConfigurator .configureComponent(AbstractComponentConfigurator.java:54) at org.codehaus.plexus.component.configurator.AbstractComponentConfigurator .configureComponent(AbstractComponentConfigurator.java:47) at org.codehaus.plexus.personality.plexus.lifecycle.phase.AutoConfigurePhas e.execute(AutoConfigurePhase.java:39) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif ecycleHandler.java:101) at org.codehaus.plexus.component.manager.AbstractComponentManager.startComp onentLifecycle(AbstractComponentManager.java:105) at org.codehaus.plexus.component.manager.AbstractComponentManager.createCom ponentInstance(AbstractComponentManager.java:95) at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.g etComponent(ClassicSingletonComponentManager.java:92) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:331) at org.codehaus.plexus.DefaultPlexusContainer.initializeLoggerManager(Defau ltPlexusContainer.java:1204) at org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusConta iner.java:642) at org.codehaus.plexus.embed.Embedder.start(Embedder.java:216) at org.codehaus.plexus.embed.Embedder.start(Embedder.java:183) at org.apache.maven.artifact.ant.AbstractArtifactTask.getEmbedder(AbstractA rtifactTask.java:312) at org.apache.maven.artifact.ant.AbstractArtifactTask.lookup(AbstractArtifa ctTask.java:276) at org.apache.maven.artifact.ant.AbstractArtifactTask.createLocalArtifactRe pository(AbstractArtifactTask.java:78) at org.apache.maven.artifact.ant.DependenciesTask.doExecute(DependenciesTas k.java:75) at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtif actTask.java:451) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut or.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) Total time: 0 seconds Any suggestions? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 26, 2006 4:14 PM To: Maven Users List Subject: RE: maven version management in ant That's it - thank you! -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 26, 2006 1:53 PM To: Maven Users Lis
RE: maven version management in ant
I'm trying this out with a VERY simple example (download one dependency), but I'm getting this: BUILD FAILED java.lang.NoSuchMethodError at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1225) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut or.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) --- Nested Exception --- java.lang.NoSuchMethodError at org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti on.(ComponentConfigurationException.java:24) at org.codehaus.plexus.component.configurator.converters.basic.IntConverter .fromString(IntConverter.java:46) at org.codehaus.plexus.component.configurator.converters.basic.AbstractBasi cConverter.fromConfiguration(AbstractBasicConverter.java:61) at org.codehaus.plexus.component.configurator.converters.ComponentValueSett er.configure(ComponentValueSetter.java:207) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWi thFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:1 37) at org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co nfigureComponent(BasicComponentConfigurator.java:56) at org.codehaus.plexus.component.configurator.AbstractComponentConfigurator .configureComponent(AbstractComponentConfigurator.java:54) at org.codehaus.plexus.component.configurator.AbstractComponentConfigurator .configureComponent(AbstractComponentConfigurator.java:47) at org.codehaus.plexus.personality.plexus.lifecycle.phase.AutoConfigurePhas e.execute(AutoConfigurePhase.java:39) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLif ecycleHandler.java:101) at org.codehaus.plexus.component.manager.AbstractComponentManager.startComp onentLifecycle(AbstractComponentManager.java:105) at org.codehaus.plexus.component.manager.AbstractComponentManager.createCom ponentInstance(AbstractComponentManager.java:95) at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.g etComponent(ClassicSingletonComponentManager.java:92) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer .java:331) at org.codehaus.plexus.DefaultPlexusContainer.initializeLoggerManager(Defau ltPlexusContainer.java:1204) at org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusConta iner.java:642) at org.codehaus.plexus.embed.Embedder.start(Embedder.java:216) at org.codehaus.plexus.embed.Embedder.start(Embedder.java:183) at org.apache.maven.artifact.ant.AbstractArtifactTask.getEmbedder(AbstractA rtifactTask.java:312) at org.apache.maven.artifact.ant.AbstractArtifactTask.lookup(AbstractArtifa ctTask.java:276) at org.apache.maven.artifact.ant.AbstractArtifactTask.createLocalArtifactRe pository(AbstractArtifactTask.java:78) at org.apache.maven.artifact.ant.DependenciesTask.doExecute(DependenciesTas k.java:75) at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtif actTask.java:451) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecut or.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.Main.runBuild(Main.java:668) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67) Total time: 0 seconds Any suggestions? -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 26, 2006 4:14 PM To: Maven Users List Subject: RE: maven version management in ant That's it - thank you! -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 26, 2006 1:53 PM To: Maven Users List Subject: Re: maven version management in ant On 12/26/06, EJ Ciramella <[EMAIL PROTECTED]> wrote: > A while back, I stumbled across a page on the maven 2 site explaining > how to use maven's nice dependency management from with
RE: maven version management in ant
That's it - thank you! -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 26, 2006 1:53 PM To: Maven Users List Subject: Re: maven version management in ant On 12/26/06, EJ Ciramella <[EMAIL PROTECTED]> wrote: > A while back, I stumbled across a page on the maven 2 site explaining > how to use maven's nice dependency management from within ant. > > I can no longer find this link, has this functionality been abandoned or > can someone reply with the url? This? http://maven.apache.org/ant-tasks.html (It's linked from the Maven home page, at the top right under 'Maven Tasks for Ant'.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven version management in ant
On 12/26/06, EJ Ciramella <[EMAIL PROTECTED]> wrote: A while back, I stumbled across a page on the maven 2 site explaining how to use maven's nice dependency management from within ant. I can no longer find this link, has this functionality been abandoned or can someone reply with the url? This? http://maven.apache.org/ant-tasks.html (It's linked from the Maven home page, at the top right under 'Maven Tasks for Ant'.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
