Hi Bill!
thanks for the evaluable feedbacks, I stopped indeed developing
whatever would have worked with com.sun.** dependency - I was looking
for javax.annotation.processing.** backport to JDK5 but without
success, so I guess I have to evaluate to release the Annotation
Processor as a separate mo
I'd like to release the next version of CP, i.e. 23.
Changes since 22 are:
New features:
o added java-1.7 profile
o added ssh/scp support to maven-site-plugin in Maven3
Changes:
o moved buildNumber plugin to profile activated by presence
of .svn directory
I did some experimenting with BeanProcessor to see what would be
involved in providing Java 1.5 support.
As part of this, I tried commenting out the new code that requires Java 1.6.
All tests still worked.
I then commented out most of the rest of the else if clauses in the
processColumn method,
On Fri, Jan 6, 2012 at 5:36 AM, sebb wrote:
> I'd like to release the next version of CP, i.e. 23.
>
> Changes since 22 are:
>
>
>
> New features:
> o added java-1.7 profile
> o added ssh/scp support to maven-site-plugin in Maven3
>
> Changes:
> o moved buildNum
On Fri, Jan 6, 2012 at 11:36 AM, sebb wrote:
> I'd like to release the next version of CP, i.e. 23.
>
> Changes since 22 are:
>
>
>
> New features:
> o added java-1.7 profile
> o added ssh/scp support to maven-site-plugin in Maven3
>
nice, but it works only for deploying
Any reason why some plugin versions are in properties and others not?
Gary
On Fri, Jan 6, 2012 at 5:36 AM, sebb wrote:
> I'd like to release the next version of CP, i.e. 23.
>
> Changes since 22 are:
>
>
>
> New features:
> o added java-1.7 profile
> o added ssh/scp sup
On 6 January 2012 13:16, Simone Tripodi wrote:
> On Fri, Jan 6, 2012 at 11:36 AM, sebb wrote:
>> I'd like to release the next version of CP, i.e. 23.
>>
>> Changes since 22 are:
>>
>>
>>
>> New features:
>> o added java-1.7 profile
>> o added ssh/scp support to maven-site
On 6 January 2012 14:39, Gary Gregory wrote:
> Any reason why some plugin versions are in properties and others not?
I think the properties are mainly needed for plugins that can be used
in both reporting and build sections.
Are there any missing properties you wish to add?
> Gary
>
> On Fri, J
Hi Nick,
I did some work on [validator] for the release but did not get through
the issues since I'm not so familiar to [validator] so much... if you
could have a look at them, I can continue providing my help.
Thanks,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal
>>> o added ssh/scp support to maven-site-plugin in Maven3
>>>
>>
>> nice, but it works only for deploying the sites to people.apache.org.
>> More than half of our components are still NOT deployed via Nexus but
>> via scp, so the wagon plugin shall be plugged as extension rather that
>>
On Fri, Jan 6, 2012 at 10:23 AM, sebb wrote:
> On 6 January 2012 14:39, Gary Gregory wrote:
> > Any reason why some plugin versions are in properties and others not?
>
> I think the properties are mainly needed for plugins that can be used
> in both reporting and build sections.
>
> Are there an
On 6 January 2012 15:55, Simone Tripodi wrote:
o added ssh/scp support to maven-site-plugin in Maven3
>>>
>>> nice, but it works only for deploying the sites to people.apache.org.
>>> More than half of our components are still NOT deployed via Nexus but
>>> via scp, so the wago
> Again, how do I do that?
:| you just did it in the site-plugin... which part of `same for
deploy-plugin` causes troubles?
> And how to test it?
a fake RC of a component that doesn't use Nexus, that will be rolled back?
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.c
On 6 January 2012 17:44, Simone Tripodi wrote:
>> Again, how do I do that?
> :| you just did it in the site-plugin...
That was not me, that was Gary.
> which part of `same for deploy-plugin` causes troubles?
>> And how to test it?
>
> a fake RC of a component that doesn't use Nexus, that will b
Do you really want two commas in a row:
+
<_removeheaders>JAVA_1_3_HOME,JAVA_1_4_HOME,JAVA_1_5_HOME,JAVA_1_6_HOME,,JAVA_1_7_HOME
?
Gary
On Fri, Jan 6, 2012 at 3:13 PM, wrote:
>
> Author: sebb
> Date: Fri Jan 6 20:13:12 2012
> New Revision: 1228379
>
> URL: http://svn.apache.org/vie
On 6 January 2012 20:22, Gary Gregory wrote:
> Do you really want two commas in a row:
>
> +
> <_removeheaders>JAVA_1_3_HOME,JAVA_1_4_HOME,JAVA_1_5_HOME,JAVA_1_6_HOME,,JAVA_1_7_HOME
> ?
Not really.
I prefer RC3 anyway ...
Thanks for spotting this.
> Gary
>
> On Fri, Jan 6, 2012 at
This is a VOTE to release commons-parent 23 based on RC3.
As agreed previously, commons parent release votes operate on lazy
consensus, i.e. the vote is assumed to have passed if 72 hours have
elapsed without an objection.
Release notes (including changes):
https://svn.apache.org/repos/asf/commo
-0
> Note: I did not update the Maven-3 section to configure the deploy> plugin,
> because I'm not able to test the change.
that is the reason, with mvn3 we cannot deploy artifacts for
components that don't support Nexus yet, and we are forced to switch
to mvn2.
of course there are turnarounds
On 6 January 2012 23:06, Simone Tripodi wrote:
> -0
>
>> Note: I did not update the Maven-3 section to configure the deploy> plugin,
>> because I'm not able to test the change.
>
> that is the reason, with mvn3 we cannot deploy artifacts for
> components that don't support Nexus yet, and we are f
On Sat, Jan 7, 2012 at 12:12 AM, sebb wrote:
> On 6 January 2012 23:06, Simone Tripodi wrote:
>> -0
>>
>>> Note: I did not update the Maven-3 section to configure the deploy> plugin,
>>> because I'm not able to test the change.
>>
>> that is the reason, with mvn3 we cannot deploy artifacts for
>
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-digester3 has an issue affecting its community integration.
This i
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-exec-test has an issue affecting its community integration.
This i
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-sanselan-test has an issue affecting its community integration.
Th
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
24 matches
Mail list logo
