On 3/4/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Jason van Zyl wrote:
>
> On 3 Mar 07, at 4:57 PM 3 Mar 07, Arnaud HERITIER wrote:
>
>> Jason,
>>
>> Couldn't we enforce the usage of something like jdiff to check if
>> there's
>> an incompatibility between releases.
>
> Yup, we could use
Oh yeah, that works too :) I use CDC so much that I forget (but even
then, you can merge in the extra def).
- Brett
On 04/03/2007, at 5:58 PM, Andrew Williams wrote:
I had a more cunning plan...
I can just advertise it over both hints in the components.xml
(works in the tests I have done her
I had a more cunning plan...
I can just advertise it over both hints in the components.xml
(works in the tests I have done here :) ).
Andy
On 5 Mar 2007, at 01:56, Brett Porter wrote:
I agree - it's going to enable plugins that reference it
successfully by role alone now to continue working.
I agree - it's going to enable plugins that reference it successfully
by role alone now to continue working.
However, something may reference it directly by the maven role-hint:
I suggest a subclass with not modifications except the alternate role-
hint be made (and deprecated) for that case
On 04/03/2007, at 4:05 PM, Dennis Lundberg wrote:
I found a couple of other bugs while testing, that I also fixed. I
feel pretty much done now. Snapshots have been deployed so that'll
give it some testing.
cool, thanks for this!
How about moving the plugin into the same source tree and
Brett Porter wrote:
Is the patch on -16 any good? That's the only one I'd move to fix.
It was already fixed in SVN.
-14 can probably be closed - it's either a findbugs problem, or a
duplicate of -11.
-14 and -11 were similar. I have fixed both of them.
The rest are feature requests, so I'
+1
On 04/03/2007, at 3:54 PM, Dennis Lundberg wrote:
Hi
The maven-shared-components pom needs to be released so that the
shared components can take advantage of the new release tool chain.
Revision: 514495
A SNAPSHOT has been deployed to our snapshot-repository.
The vote will be open for
Hi
The maven-shared-components pom needs to be released so that the shared
components can take advantage of the new release tool chain.
Revision: 514495
A SNAPSHOT has been deployed to our snapshot-repository.
The vote will be open for 72 hours.
Here is my +1
--
Dennis Lundberg
-
On 4 Mar 07, at 12:50 PM 4 Mar 07, Brett Porter wrote:
On 04/03/2007, at 7:26 AM, Jason van Zyl wrote:
You might want to sync up with raphael over in mojo where he's
taking a swing at a new version of archetype.
Raphael - can you tell us what is happening over here? (Pretty sure
you're s
On 04/03/2007, at 7:26 AM, Jason van Zyl wrote:
You might want to sync up with raphael over in mojo where he's
taking a swing at a new version of archetype.
Raphael - can you tell us what is happening over here? (Pretty sure
you're still subscribed). Wendy's asked me to look at something, a
-1
Agreeing with Daniel - AFAICT the POMs are not correctly configured
to generate the proper license files, etc. on release.
If you could update the parents and either stage a release or deploy
snapshots with the release profile turned on, then I'm +1.
Thanks!
- Brett
On 04/03/2007, at
On 04/03/2007, at 6:41 AM, Dennis Lundberg wrote:
Can you point to some specific Apache rule that says so? There have
been discussions on this topic before, but I have yet to see
someone point me to the source for this rule. I don't disagree with
the sentiment of this, I just want to know
On 04/03/2007, at 1:51 AM, Dennis Lundberg wrote:
Is that because maven-plugin-descriptor-2.0.5.jar is in M2_HOME/lib ?
yes
How does plugin updates work in a situation like this? Say we have
a user that is running maven 2.0.4. He/she issues "mvn -U site" on
a project that requires mave
The new plugin descriptor (for @since, and the implementation tag).
On 04/03/2007, at 3:36 AM, Andrew Williams wrote:
just out of interest, what part of 2.0.5 is required now?
Andy
On 4 Mar 2007, at 11:28, [EMAIL PROTECTED] wrote:
Author: dennisl
Date: Sun Mar 4 03:27:56 2007
New Revision:
The Archetype plugin has lost the ability to "package" non-Java
resources. It looks like this happened with the addition of 'sub
packages' for Java sources.
For example, you might want to place App.properties in
src/main/resources/com/example/App.properties in the generated app, as
a companion t
You might want to sync up with raphael over in mojo where he's taking
a swing at a new version of archetype. He doesn't have access at
Apache so he's doing it at Mojo.
Jason.
On 3 Mar 07, at 8:39 AM 3 Mar 07, [EMAIL PROTECTED] wrote:
Author: wsmoak
Date: Sat Mar 3 08:39:09 2007
New Revisi
On 4 Mar 07, at 6:41 AM 4 Mar 07, Dennis Lundberg wrote:
Daniel Kulp wrote:
+1
However, by apache rules we should be voting on staged artifacts,
not snapshots. The snapshots don't meet apache release
requirements so technically, any vote on them should be an
immediate -1. Plus, things
On 4 Mar 07, at 3:18 AM 4 Mar 07, Andrew Williams wrote:
Are there an objections, or reasons not to change the role-hint of
MavenMetadataSource
in maven-project from "maven" to "default".
I think that's fine, but we should also annotating all the plexus
components and I think we can make
Daniel Kulp wrote:
+1
However, by apache rules we should be voting on staged artifacts, not
snapshots. The snapshots don't meet apache release requirements so
technically, any vote on them should be an immediate -1. Plus, things
like the gpg signatures and stuff are not available to verify
+1
However, by apache rules we should be voting on staged artifacts, not
snapshots. The snapshots don't meet apache release requirements so
technically, any vote on them should be an immediate -1. Plus, things
like the gpg signatures and stuff are not available to verify and such.
For Jaso
Jason van Zyl wrote:
On 3 Mar 07, at 4:57 PM 3 Mar 07, Arnaud HERITIER wrote:
Jason,
Couldn't we enforce the usage of something like jdiff to check if
there's
an incompatibility between releases.
Yup, we could use that or Clirr as Vincent suggested. That's one part of
the answer. The
Hi,
I'd like to release maven-plugin-tools-2.1. The previous release was 2.0.5.
This release is a preparation for a new release of the maven-plugin-plugin.
I could not find any project in JIRA where issues for this component
would be, but the differences that can be found between the last rele
just out of interest, what part of 2.0.5 is required now?
Andy
On 4 Mar 2007, at 11:28, [EMAIL PROTECTED] wrote:
Author: dennisl
Date: Sun Mar 4 03:27:56 2007
New Revision: 514383
URL: http://svn.apache.org/viewvc?view=rev&rev=514383
Log:
o Update prerequisites to 2.0.5.
Modified:
maven
+1
Stéphane
On 3/3/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Hi,
I'd like to release maven-model-converter. The last release was 2.0.4.
Back then it resided in maven components. It has now moved to maven
shared.
This release is a preparation for a release of the maven-one-plugin.
The i
Are there an objections, or reasons not to change the role-hint of
MavenMetadataSource
in maven-project from "maven" to "default".
The latest plexus code (will shortly...) be more strict on hints and
no longer allow components
to grab "whatever is configured", if a hint exists it must be
ho
Is that because maven-plugin-descriptor-2.0.5.jar is in M2_HOME/lib ?
How does plugin updates work in a situation like this? Say we have a
user that is running maven 2.0.4. He/she issues "mvn -U site" on a
project that requires maven-plugin-plugin-2.3, which in turn has 2.0.5
as a prerequisite
26 matches
Mail list logo
