+1 (binding)
Just a small note:
Please always also link to the source-release as this is what the ASF primarily
ships. All other artifacts are only nice to have goodies (in the legal aspect).
https://repository.apache.org/content/repositories/maven-053/org/apache/maven/release/maven-release/2.
+1
the site problem seems like a sync issue:
http://maven.apache.org/plugins/maven-release-plugin-2.3/css/ is empty, but
p.a.o contains files
I just touch-ed files to force a new sync, the site should be fixed in a couple
of hours (without re-generating anything)
Regards,
Hervé
Le mardi 8 ma
I'm in favour of 2.7.1, given the few changes
and no objection to fast release cycles
Regards,
Hervé
Le mercredi 9 mai 2012 09:44:41 Benson Margulies a écrit :
> A user has asked for a quick turn on a blocking bug with the changes
> plugin when used with JIRA 5. I'm willing to turn the crank.
On May 9, 2012, at 3:30 PM, Mark Derricutt wrote:
> On 10/05/12 7:47 AM, Jason van Zyl wrote:
>> The only thing I would like to sync up on is a couple changes I want to make
>> to the plugin manager to make sure the current plugin packaging, the plugin
>> packaging you're making and the plugin
+1
Robert
Op Thu, 10 May 2012 00:03:07 +0200 schreef John Casey
:
+1
On 5/8/12 11:46 PM, Paul Gier wrote:
Hi,
We solved 5 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=17443
There are still a couple of issues left in JIRA:
https://jira.codehaus.org/se
+1
On 5/8/12 11:46 PM, Paul Gier wrote:
Hi,
We solved 5 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=17443
There are still a couple of issues left in JIRA:
https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MENFORCER+AND+st
+1
I imagine (hope :-) ), you will publish the site from the tag so no issue.
2012/5/8 Robert Scholte :
> Hi,
>
> I'd like to release the maven-release-plugin 2.3
>
> We solved 22 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144&version=18334
>
> There are still a couple
+1
2012/5/9 Paul Gier :
> Hi,
>
> We solved 5 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=17443
>
> There are still a couple of issues left in JIRA:
> https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MENFORCER+AND+status+%
2012/5/9 Jason van Zyl :
>
> On May 9, 2012, at 3:23 PM, Olivier Lamy wrote:
>
>> 2012/5/9 Jason van Zyl :
>>> The only thing I might suggest is that you create a hybrid scanner that can
>>> deal with the old and new. It looks like you've already looked at [1], but
>>> the hybrid scanner is here[
On May 9, 2012, at 3:23 PM, Olivier Lamy wrote:
> 2012/5/9 Jason van Zyl :
>> The only thing I might suggest is that you create a hybrid scanner that can
>> deal with the old and new. It looks like you've already looked at [1], but
>> the hybrid scanner is here[2].
> Thanks but this mix scannin
And btw make changes you need. I have added some its for basic use
cases with annotations.
2012/5/9 Olivier Lamy :
> 2012/5/9 Jason van Zyl :
>> The only thing I might suggest is that you create a hybrid scanner that can
>> deal with the old and new. It looks like you've already looked at [1], bu
On 10/05/12 7:47 AM, Jason van Zyl wrote:
The only thing I would like to sync up on is a couple changes I want to make to
the plugin manager to make sure the current plugin packaging, the plugin
packaging you're making and the plugin packaging I'm working on in Tesla all
work together without
2012/5/9 Jason van Zyl :
> The only thing I might suggest is that you create a hybrid scanner that can
> deal with the old and new. It looks like you've already looked at [1], but
> the hybrid scanner is here[2].
Thanks but this mix scanning is already implemented in the branch.
Currently the onl
Its great to see this teamwork happening from the outside. Keep it up!
manfred
On Wed, May 9, 2012 12:47 pm, Jason van Zyl wrote:
> The only thing I might suggest is that you create a hybrid scanner that
> can deal with the old and new. It looks like you've already looked at [1],
> but the hybrid
The only thing I might suggest is that you create a hybrid scanner that can
deal with the old and new. It looks like you've already looked at [1], but the
hybrid scanner is here[2].
The only thing I would like to sync up on is a couple changes I want to make to
the plugin manager to make sure t
On Tue, 08 May 2012 22:46:26 -0500
Paul Gier wrote:
+1 (non binding)
Works fine on oru projects.
thanks,
tony.
--
Tony Chemit
tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com
http://www.codelutin.com
+1 (non-binding) tested with two pat projects and mojo's
extra-enforcer-rules trunk (all ITs ran successfully).
Regards
Mirko
On Wed, May 9, 2012 at 5:46 AM, Paul Gier wrote:
> Hi,
>
> We solved 5 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=17443
>
> There
Hi,
So I have pushed some stuff on supporting plugin descriptor generation
from annotations as described here [1].
I have added support of having annotations from parent classes even if
they are not in the same project (from reactors and/or dependencies).
BTW we still need to do some javadoc parsin
A user has asked for a quick turn on a blocking bug with the changes
plugin when used with JIRA 5. I'm willing to turn the crank. Does
anyone have strong feelings about 2.8 versus 2.7.1 in this case? Does
anyone object?
-
To unsu
19 matches
Mail list logo
