All joking aside, 2.0.9 and 2.0.10 have proven to be very stable. We
need to keep the same bar for 2.0.11 especially if we intend this to
be the end of 2.0.x. That means we need lots of participation during
the rc process.
--Brian (mobile)
On Nov 20, 2009, at 4:23 PM, Brett Porter wrote:
Hi,
This is the first of a series of releases to get Maven Site Plugin 2.1
released.
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=14385
There are no issues left in JIRA!
Staging repo:
https://repository.apache.org/content/repositories/maven-014/
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11137&version=13995
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11137&status=1
Staging repo:
https://repository.apache.org/content/repositori
done
Dennis Lundberg wrote:
Hi
When staging the site for maven-changes-plugin-2.2 I came across a bunch
of plugin sites that have wrong permissions on them. Can the persons
owning these directories please fix the permissions?
See stage number 2 at
http://maven.apache.org/developers/release/mav
Yup.
An old bug in fact :-).
Yes, I prefer this too.
--
Olivier
2009/11/20 Brett Porter :
> That sounds like a bug in the plugin that presents differently under the two
> versions. Shouldn't it be ${basedir}/LICENSE.txt, and not fail if it is
> missing & default?
>
> - Brett
>
> On 21/11/2009,
2009/11/20 Brett Porter :
>
> On 21/11/2009, at 9:40 AM, Paul Gier wrote:
>
>>> Well, for 2.0.x, it is :)
>>> - Brett
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@
On 21/11/2009, at 9:40 AM, Paul Gier wrote:
>> Well, for 2.0.x, it is :)
>> - Brett
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>
> There isn't a
That sounds like a bug in the plugin that presents differently under the two
versions. Shouldn't it be ${basedir}/LICENSE.txt, and not fail if it is missing
& default?
- Brett
On 21/11/2009, at 9:33 AM, Olivier Lamy wrote:
> Hi,
>
> The mojo parameter regarding headerLocation contains
> *
Brett Porter wrote:
On 21/11/2009, at 8:53 AM, Wendy Smoak wrote:
On Fri, Nov 20, 2009 at 2:46 PM, Michael wrote:
Brian Fox schrieb:
oh wait oh wait, but i've got 15 things.
Which are?
He's kidding. :) It seems like every time someone tries to release
something around here, there is a
Dennis Lundberg schrieb:
Hi,
We solved 18 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&version=14696
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11212&status=1
Staging repo:
https://repository.a
Hi,
The mojo parameter regarding headerLocation contains
* @parameter expression="${checkstyle.header.file}"
default-value="LICENSE.txt"
*/
private String headerLocation;
This means it's never empty and the mojo search it.
With mvn 2.x, the one from the distribution can be used
Rem
On 21/11/2009, at 8:53 AM, Wendy Smoak wrote:
> On Fri, Nov 20, 2009 at 2:46 PM, Michael wrote:
>> Brian Fox schrieb:
>>>
>>> oh wait oh wait, but i've got 15 things.
>>
>> Which are?
>
> He's kidding. :) It seems like every time someone tries to release
> something around here, there is
Hi
When staging the site for maven-changes-plugin-2.2 I came across a bunch
of plugin sites that have wrong permissions on them. Can the persons
owning these directories please fix the permissions?
See stage number 2 at
http://maven.apache.org/developers/release/maven-plugin-release.html for
inst
Hi,
We solved 18 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&version=14696
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11212&status=1
Staging repo:
https://repository.apache.org/content/repositor
On Fri, Nov 20, 2009 at 2:46 PM, Michael wrote:
> Brian Fox schrieb:
>>
>> oh wait oh wait, but i've got 15 things.
>
> Which are?
He's kidding. :) It seems like every time someone tries to release
something around here, there is a chorus of "but wait, one more
thing!" as if it will be the l
Brian Fox schrieb:
oh wait oh wait, but i've got 15 things.
Which are?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
oh wait oh wait, but i've got 15 things.
;-)
On Fri, Nov 20, 2009 at 4:23 PM, Brett Porter wrote:
> Yes, it's been tagged a while too. I was planning to start the RC process
> today.
>
> On 21/11/2009, at 8:04 AM, Michael wrote:
>
>> Hi folks,
>>
>> all issues for Maven 2.0.11 have been clo
Yes, it's been tagged a while too. I was planning to start the RC process today.
On 21/11/2009, at 8:04 AM, Michael wrote:
> Hi folks,
>
> all issues for Maven 2.0.11 have been closed since August [1].
> Why hasn't this relese been pushed so far?
>
>
> Thanks,
>
> Mike
>
> [1]
> http://jira
Hi folks,
all issues for Maven 2.0.11 have been closed since August [1].
Why hasn't this relese been pushed so far?
Thanks,
Mike
[1]
http://jira.codehaus.org/secure/IssueNavigator.jspa?sorter/field=updated&sorter/order=DESC
--
Why is this needed?
Shouldn't the license be included by the apache-jar-resource-bundle that
is being injected by maven-remote-resources-plugin?
ol...@apache.org wrote:
> Author: olamy
> Date: Wed Nov 18 23:01:52 2009
> New Revision: 881985
>
> URL: http://svn.apache.org/viewvc?rev=881985&view=r
Brian Fox wrote:
What is the behavior in an embedded env like M2e? Since it's not going
to execute the full lifecycle, it probably needs to have the same
logic regardless to look at the lifecycle and pick the right version
of a plugin it does run.
Not sure I understand that question. Embedders
> What about users doing multi-machine builds? Earlier this week I wrote that
> users desiring to do multi-machine parallelism should deploy their builds to
> a remote repository shared between the machines. Should their tests run
> post-deploy?
>
I think what you meant is "my" tests should run
On Thu, Nov 19, 2009 at 1:24 PM, Benjamin Bentmann
wrote:
> Brian Fox wrote:
>
>> I guess what I had in mind was given a single reactor build:
>> A : Jar
>> B: War but binds jar to a phase.
>>
>> Will B always get the same version of the jar plugin as A?
>
> No, the projects are handled independen
I'm conceptually using the transactional "local" repository as a
get-out-of-jail card for possible violations of contract,
the full build must be ok for the real repository update to
come through, creating any publicly visible artifacts.
Obviously, you're right, the tests should be pushed
to after
The Maven team is pleased to announce the release of the Maven Plugin
Testing, version 2.0-alpha-1.
This harness assists in creating unit or integration tests for Maven
plugins. See the component's site for more details:
http://maven.apache.org/plugin-testing/
This new version of the harne
I've been meaning to reply to your earlier emails (it's been a busy week);
to this I'll just say that moving the "test" phase after the "install"
phase is a fascinating idea, which I personally like, but it seems like a
big violation of the contract for the lifecycle, and I suspect it won't be
-- Forwarded message --
From: Dipankar Das
Date: Fri, Nov 20, 2009 at 3:31 AM
Subject: Urgent-kindly help in installing maven assembly plugin
To: bri...@apache.org, br...@apache.org
Dear Sir,
I am using both of the following packages (apache-maven-2.2.1-bin
apache-maven-2.0.10-b
I've been thinking further about parallelity within maven. The proposed
solution to MNG-3004
achieves parallelity by analyzing inter-module dependencies and scheduling
parallel dependencies in parallel.
A simple further evolution of this would be to collect and download all
external dependencies
f
28 matches
Mail list logo
