+1
On Mon, Sep 15, 2008 at 4:12 PM, John Casey <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> After fixing 70 issues and spending about 2 months going through release
> candidate after release candidate, we finally have a stable codebase!
>
> To that end, I'd like to put Maven 2.1.0-M1 up for a vot
+1
Thanks,
Deng
On Mon, Sep 15, 2008 at 8:29 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Hi
>
> Here's another parent in need of a release.
>
> Diff for the pom.xml:
>
> http://svn.eu.apache.org/viewvc/maven/plugins/trunk/pom.xml?r1=646036&r2=695450&diff_format=h
>
> Diff for the site.xml:
Hi everyone,
After fixing 70 issues and spending about 2 months going through release
candidate after release candidate, we finally have a stable codebase!
To that end, I'd like to put Maven 2.1.0-M1 up for a vote. The release
notes are here:
http://jira.codehaus.org/secure/ReleaseNote.jspa
Hi,
Someone can explain why this failed in hudson ?
The build.log of the it says :
Caused by: org.codehaus.plexus.component.composition.CompositionException:
Composition failed of field velocity in object of type
org.apache.maven.plugin.announcement.AnnouncementMojo because the
requirement
Compon
You're right, and I forgot about the separation. I think the verifier
needs to be a regular shared component (not plugin as I stated)
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2008 2:14 PM
To: Maven Developers List
Subject: Re: releasin
Alrighty then +1 from me.
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2008 2:08 PM
To: Maven Developers List
Subject: Re: [VOTE] Release maven-plugins parent POM 12
No, that was really someone elses itch.
Like you said before, another p
Brian E. Fox wrote:
>> If the only dependency for integration tests is the verifier, then
>> there's not much point in moving it into its own SVN structure, IMO.
>
> I think the verifier _is_ useful in Its outside of maven core itself.
> Case in point: Nexus. We should move the verifier to be a f
No, that was really someone elses itch.
Like you said before, another parent release can be made later on for
those who needs it. We need to release more often.
Brian E. Fox wrote:
> I thought you wanted to get the parent v10 done before pushing out to
> all the plugins? I need one more vote for
>If the only dependency for integration tests is the verifier, then
>there's not much point in moving it into its own SVN structure, IMO.
I think the verifier _is_ useful in Its outside of maven core itself.
Case in point: Nexus. We should move the verifier to be a full-fledged
plugin.
You're telling Maven that you are offline. Deploying is an Online
behavior, therefore they are mutually exclusive. Also, this is a user
list question as it doesn't relate to the development of Maven itself.
-Original Message-
From: jbrady3324 [mailto:[EMAIL PROTECTED]
Sent: Monday, Septem
I thought you wanted to get the parent v10 done before pushing out to
all the plugins? I need one more vote for enforcer, then we can update
v10 and stage that immediately.
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2008 8:30 AM
To: Mave
I'm +1 for consolidating the helper and archetype/sample stuff into a
SVN tree, then releasing all that stuff. I'd probably agree that the
verifier needs to stay separate, though, since it's not specific to
maven's ITs anymore.
Also, (another tangent) we need to look into how we could start
r
I'm running on half a brain today (allergies), but I do want to make one
point that I feel is pretty important:
IMO we need to move away from generalized test plugins for use in the
maven core ITs ASAP. Normal object-oriented design concerns don't apply
well here, and factoring behavior into e
On Tue, May 22, 2007 at 7:05 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
> Ok, there seems to be some interest. I will spend some time putting the code
> into a suitable packaging / licensing structure and post it for a vote.
There was some interest in a conversion tool on #maven this morning.
Did
This is the error I get:
[INFO] Installing C:\dev\eclipse\mops2.0\mops\pom.xml to C:\Documents and
Settings\jxbrady\.m2\repository\com\putnam\mops\mops\2.0-SNAPSHOT\mops-2.0-SNAPSHOT.pom
altDeploymentRepository = null
[ERROR]
The following mojo encountered an error while executing:
Group-Id: or
On 15/09/2008, at 10:40 PM, Jason van Zyl wrote:
It would still be separate. What I'm really suggesting is putting
the helper (abstract test base class, used by both Maven's test
suite and NMaven's test suite), in with the verifier and releasing
them together. Shared is fine too, but I w
Yes, please include support for prepare-package. We still will have to wait
for jar/war plugins to support it, but it will then makes possible to
implement web application post-processing (I think about javascript and css
compression) and similmar stuff.
Nicolas
2008/9/14 Brett Porter <[EMAIL PRO
On 15-Sep-08, at 11:55 AM, Brett Porter wrote:
On 15/09/2008, at 6:47 PM, Jason van Zyl wrote:
I honestly don't think this is necessary. The real problem is lack
of consistency in deploying the IT ball. And honestly the IT ball
is fine for casual people trying to test things but is inef
18 matches
Mail list logo
