Also, I thought having the archetype catalog online was a pre-
requisite to this release?
- Brett
On 04/05/2009, at 4:01 AM, Brian E. Fox wrote:
-1 we need to produce source archives for all releases based on the
recent discussions on some other lists. I'm experimenting with some
ways to m
On 04/05/2009, at 1:47 PM, Jason van Zyl wrote:
- the model builder should stand-alone to build fully inherited/
interpolated models
- the project builder should bring in any runtime information in the
form of properties, and really should be a very thin layer over the
model builder
+1
-
It's fine to fix this temporarily like this, but ultimately here I'm
just trying to give the project/model builder all the information it
needs and the merging of any bits should only be in the model builder.
Merging of any configuration should also definitely not happen in the
plugin manag
On 3-May-09, at 6:15 PM, Brett Porter wrote:
On 04/05/2009, at 12:15 AM, Jason van Zyl wrote:
That error above, you sure you're not pulling in two shaded versions?
That would be the case - the shaded version in ant tasks, and the
shaded version in Maven itself.
So that they can all use
On 04/05/2009, at 12:15 AM, Jason van Zyl wrote:
That error above, you sure you're not pulling in two shaded versions?
That would be the case - the shaded version in ant tasks, and the
shaded version in Maven itself.
So that they can all use their own version, what is needed is for the
On 03/05/2009, at 6:58 AM, John Casey wrote:
The ITs all looked fine with this commit, so it looks like this
stuff won't cause too much grief...but hopefully the testing of the
RC will tell.
I've created a 2.2.0-RC branch for subsequent RCs and the final
release of 2.2.0, so we can conti
Once the plugin merging is done correctly outside the plugin manger
this processing will take into account all the methods commented out
at the bottom of the class. Need to look at required/editable/default
values for each parameter.
On 3-May-09, at 4:02 PM, bentm...@apache.org wrote:
Aut
-1 we need to produce source archives for all releases based on the
recent discussions on some other lists. I'm experimenting with some
ways to make this inherited but for now you can bind the assembly
plugin with the src descriptor to produce the correct zip of the
sources.
--Brian (mobi
Hi,
We solved 11 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14254&styleName=Html&projectId=11095
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11095&status=1
Staging repo:
https://repository.apache.org/
Yeah, we're using the version '2.2.0' partially because JDK 1.5 is a
requirement for one of the regression fixes.
Jason van Zyl wrote:
On 2-May-09, at 1:58 PM, John Casey wrote:
The ITs all looked fine with this commit, so it looks like this stuff
won't cause too much grief...but hopefully t
On 2-May-09, at 1:58 PM, John Casey wrote:
The ITs all looked fine with this commit, so it looks like this
stuff won't cause too much grief...but hopefully the testing of the
RC will tell.
If it was decided that this should run in only in 1.5 and you don't
have to worry about a 1.4 run
On 1-May-09, at 12:30 PM, Paul Gier wrote:
The maven ant tasks currently creates a shaded jar that combines
several of the dependencies into one jar. While working on
MANTTASKS-106 (using ant tasks inside ant-run) I noticed that the
plexus utils classes are relocated to hidden.org.plexus.
On 1-May-09, at 2:05 PM, Paul Gier wrote:
Ok, I was kind of wondering about that. When I first tried trunk it
was not building and had some outdated stuff in there, but I
committed changes in both places to be safe.
I'll stop committing to trunk, and then we can start fresh after
2.0.10
On 1-May-09, at 1:56 PM, Hervé BOUTEMY wrote:
I don't think merging changes to ant-tasks/trunk is worth the effort
now.
Trunk was created in r524632, in april 2007, when Maven 2.0.x and
Maven 2.1.x
started 2 different branches. Changes were done by Jason in ant-
tasks/trunk
to match Maven
14 matches
Mail list logo
