On 2009-09-08, at 3:11 AM, Brett Porter wrote:
On 08/09/2009, at 8:06 AM, Jason Chaffee wrote:
I understand that you probably don't want to commit to a date or
cause
undue expectations from anyone on this list, so let me ask it in a
slight differently way.
Do you think it might be
On 2009-09-08, at 4:12 AM, Christian Edward Gruber wrote:
On Sep 7, 2009, at 9:52 PM, Ralph Goers wrote:
At one point the pom was going to be redone so that it wasn't
going to be completely compatible. Later, I think the decision was
made to keep it compatible. At one point there was
I don't think changing the POM or metadata formats in 3.0 is a good
idea. 3.0 needs to be release and we watch how it's working and make
any and all corrections to move 2.x users forward in a drop-in
replacement fashion. In the planning for 3.1 we should start talking
about additions to
So - 2 points.
1. Who's saying you have to actually have YAML poms IN the maven
project - as long as I can find a way to (through autodiscovery of
some mechanism) not have to do crazy wrappers. You said these
extension points would be there, so I'm happy. (do note the smiley)
2.
Hello please help me in resolving the below issue, while building a
project
U:\LDN_DATA_RKYC\PilWR\OLayerEJB\Pil_Wrmvn clean install -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Maven Quick Start Archetype
[INFO] Unnamed -
For that to work you'd basically need to be able to round-trip between the
yaml format and the xml format...
otherwise the tooling in IDEs and in plugins like versions-maven-plugin,
maven-release-plugin, etc will make changes and very soon the yaml file is
just the seed file and bares no
On 2009-09-08, at 9:49 AM, Christian Edward Gruber wrote:
So - 2 points.
1. Who's saying you have to actually have YAML poms IN the maven
project - as long as I can find a way to (through autodiscovery of
some mechanism) not have to do crazy wrappers. You said these
extension points
On 2009-09-01, at 7:22 PM, Daniel Kulp wrote:
On Tue September 1 2009 12:58:52 pm Jason van Zyl wrote:
I can't tell from the issue what it is exactly you're trying to
accomplish?
Well, the goal is to eventually be able to use the Apache parent
pom for
CXF. Right now, we cannot.
We
On 08/09/2009, at 5:44 PM, Jason van Zyl wrote:
I don't think changing the POM or metadata formats in 3.0 is a good
idea. 3.0 needs to be release and we watch how it's working and make
any and all corrections to move 2.x users forward in a drop-in
replacement fashion. In the planning for
Hi All,
I am having a property named test.version in pom.xml
properties
test.version8/test.version
/properties
and I have a the below entry in the same pom.xml
dependencies
dependency
groupIdcom.test.data/groupId
artifactIdUtilLibrary/artifactId
This list is for development of maven only. AND i already answered
your question on the user list the last time you asked.
On Tue, Sep 8, 2009 at 7:54 AM, Praveenkumar Kasupraveenkum...@hcl.in wrote:
Hi All,
I am having a property named test.version in pom.xml
properties
Hi,
the archetype plugin sometimes prints:
[ERROR] Found entry
during mvn archetype:generate.
This is irritating since there is no error. In fact, something good
just happened, because the code found an entry it was looking for.
The message should either be removed entirely (which is what the
+1
On Sun, Sep 6, 2009 at 7:24 PM, Arnaud
HERITIERarnaud.herit...@exoplatform.com wrote:
Hi all,
I'd like to propose giving commit access to Stephen Connolly.
He is already a committer @ Mojo for many monthes and did a great work on
several plugins.
He is the author of the very useful
Stefan Sperling wrote:
The message should either be removed entirely (which is what the
patch below does) or changed to 'debug'.
Patches usually go into the issue tracker:
http://jira.codehaus.org/browse/ARCHETYPE
Benjamin
Ok. Sounds workable.
Christian.
On Sep 8, 2009, at 4:00 AM, Jason van Zyl wrote:
On 2009-09-08, at 9:49 AM, Christian Edward Gruber wrote:
So - 2 points.
1. Who's saying you have to actually have YAML poms IN the maven
project - as long as I can find a way to (through autodiscovery of
There you go another reason to use 3.x now.
On 2009-09-08, at 4:33 PM, Benjamin Bentmann wrote:
Jason van Zyl wrote:
And b configures a plugin with dependency foo, and c configures
the same
plugin, but with dependency bar, if I run mvn in c, it works
fine (gets
bar), but if I run from a,
Jason van Zyl wrote:
And b configures a plugin with dependency foo, and c configures the same
plugin, but with dependency bar, if I run mvn in c, it works fine (gets
bar), but if I run from a, it doesn't work right in c. It just gets
foo.
Thus, it works differently depending on where I type
+1
Arnaud HERITIER wrote:
Hi all,
I'd like to propose giving commit access to Stephen Connolly.
He is already a committer @ Mojo for many monthes and did a great work on
several plugins.
He is the author of the very useful versions plugin. He is working on
several others plugins like
On Tue September 8 2009 4:15:05 am Jason van Zyl wrote:
On 2009-09-01, at 7:22 PM, Daniel Kulp wrote:
However, to accomplish that, we HAVE to make sure the remote-
resources is NOT
loaded in buildtools. Otherwise, due to the bug in maven that
doesn't re-
evaluate plugin dependencies
I am trying to run maven-assembly-plugin:2.1 with my custom assembler and
I get the following error:
[INFO] Scanning for projects...
[INFO]
[INFO] Building aviall-ws-ubl-assembly-distribution
[INFO]
[INFO] Id:
On 2009-09-08, at 3:51 PM, Daniel Kulp wrote:
On Tue September 8 2009 4:15:05 am Jason van Zyl wrote:
On 2009-09-01, at 7:22 PM, Daniel Kulp wrote:
However, to accomplish that, we HAVE to make sure the remote-
resources is NOT
loaded in buildtools. Otherwise, due to the bug in maven that
Yep. That's the issue. (I was searching for it, just didn't check the
closed issues. Cool.)
Dan
On Tue September 8 2009 10:33:35 am Benjamin Bentmann wrote:
Jason van Zyl wrote:
And b configures a plugin with dependency foo, and c configures the same
plugin, but with dependency bar,
22 matches
Mail list logo
