I don't have too much to add to the proposal as Jason has revised it. I'm
not too wild about leaving the CLI invocations to RELEASE metadata...I think
this doesn't account too well for branched activity of plugins, nor for
snapshots (of branches, for that matter). I think we're going to have to
th
Regrettably, I was a bit out of it and forget to bring this one up
f2f. Can we revisit this proposal with the change mentioned?
On 03/05/2007, at 4:31 AM, Jason van Zyl wrote:
Yup, we have two long slots at the TC offices at j1. 14 hours in
total and I would like to talk about plugins, and a
2007/5/3, Brett Porter <[EMAIL PROTECTED]>:
Any other thoughts on this proposal, given that we replace the
packaging plugin concept with a descriptor instead?
Do that mean anything for the archetypes? i use maven-plugin
packaging to have the group metadata for the archetypes.
Raphaël
- Bre
Yup, we have two long slots at the TC offices at j1. 14 hours in
total and I would like to talk about plugins, and artifact resolution.
Jason.
On 3 May 07, at 6:42 AM 3 May 07, Brett Porter wrote:
Any other thoughts on this proposal, given that we replace the
packaging plugin concept with a
Any other thoughts on this proposal, given that we replace the
packaging plugin concept with a descriptor instead?
- Brett
On 21/04/2007, at 10:57 PM, Brett Porter wrote:
Hi,
I thought to gather up that massive thread I've just read, I could
throw out a quick proposal that might summarise
On 22/04/2007, at 4:58 PM, Jason van Zyl wrote:
- require the version in plugin definitions in the POM from
modelVersion 4.1.0+ (for 4.0.0 modelVersions, continue to allow
the RELEASE as the version).
+1
- externalise all packagings/lifecycle definitions (with the
exception of 'pom', pe
On 21 Apr 07, at 4:57 PM 21 Apr 07, Brett Porter wrote:
Hi,
I thought to gather up that massive thread I've just read, I could
throw out a quick proposal that might summarise it and serve as a
discussion point.
Things we know:
- the current situation is problematic
- we can't require ver
Hi,
I thought to gather up that massive thread I've just read, I could
throw out a quick proposal that might summarise it and serve as a
discussion point.
Things we know:
- the current situation is problematic
- we can't require versions for everything (particularly, the implied
plugins f
