2015-05-03 19:21 GMT+02:00 Gary Gregory :
> The new class DefaultParser does not use generics to define the options
> List, that is suspicious. Looking closer, the list can hold a mix of
> OptionGroup and String instances. Really? Looking at Options I see the list
> defined as List. This avoids co
Strange? Building the site with:
Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
2015-04-22T13:57:37+02:00)
Maven home: /usr/local/Cellar/maven/3.3.3/libexec
Java version: 1.7.0_75, vendor: Oracle Corporation
Java home:
/Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home/
Hello Jacopo,
2015-05-03 18:20 GMT+02:00 Jacopo Cappellato :
> On May 3, 2015, at 12:54 PM, Benedikt Ritter wrote:
>
> > Sounds good to me. Go for it!
>
> I have attached a patch for one (but will resolve two) of the issues in
> the list:
>
> https://issues.apache.org/jira/browse/CLI-179
>
> I a
Hi Benedikt,
i have opened a new pull request
https://github.com/apache/commons-lang/pull/78 which is based against
the master branch, contains only a single commit and fixes the issues
you named.
Hope thats ok ...
Thanks
Hendrik
On Sun, Apr 26, 2015 at 11:40 AM, Benedikt Ritter wrote:
> Hello
Well, we just followed Gary and Benedikt recommendation to adopt the
current components' style. For us as podling is fine whatever you decide,
we just need a decision (an permission to deploy over it).
On Sun, May 3, 2015 at 9:33 PM, Phil Steitz wrote:
> On 5/3/15 12:26 PM, Jochen Wiedmann wrote
On 5/3/15 12:26 PM, Jochen Wiedmann wrote:
> On Sun, May 3, 2015 at 9:03 PM, Phil Steitz wrote:
>> On 5/3/15 11:56 AM, Jochen Wiedmann wrote:
>>> On Sun, May 3, 2015 at 4:44 PM, Sergio Fernández wrote:
we're discussing our first incubating release, and we came to the issue
that we are n
On Sun, May 3, 2015 at 9:03 PM, Phil Steitz wrote:
> On 5/3/15 11:56 AM, Jochen Wiedmann wrote:
>> On Sun, May 3, 2015 at 4:44 PM, Sergio Fernández wrote:
>>> we're discussing our first incubating release, and we came to the issue
>>> that we are not grant with permissions to deploy maven artifac
On 5/3/15 11:56 AM, Jochen Wiedmann wrote:
> On Sun, May 3, 2015 at 4:44 PM, Sergio Fernández wrote:
>> we're discussing our first incubating release, and we came to the issue
>> that we are not grant with permissions to deploy maven artifacts to the
>> org.apache.commons groupId [1].
> Why org.ap
On Sun, May 3, 2015 at 4:44 PM, Sergio Fernández wrote:
> we're discussing our first incubating release, and we came to the issue
> that we are not grant with permissions to deploy maven artifacts to the
> org.apache.commons groupId [1].
Why org.apache.commons, and not, say, org.apache.commons.rd
Just FYI, the site does builds but logs errors with Maven 3.3.3, I think
this might be a known issue. This means some reports do not get created. I
do not think there is anything we can do except make a not of which Maven
versions we know work. Maven 3.2.5 works fine for example.
With Maven 3.3.3:
The new class DefaultParser does not use generics to define the options
List, that is suspicious. Looking closer, the list can hold a mix of
OptionGroup and String instances. Really? Looking at Options I see the list
defined as List. This avoids compiler warnings but is nasty. This
is probably what
On May 3, 2015, at 12:54 PM, Benedikt Ritter wrote:
> Sounds good to me. Go for it!
I have attached a patch for one (but will resolve two) of the issues in the
list:
https://issues.apache.org/jira/browse/CLI-179
I am not sure if it is the right direction but this is what I could do today,
so
Hi,
We have fixed quite a few bugs and added some significant enhancements
since CLI 1.2 was released and the Groovy Project is asking for a new
release, so I would like to release CLI 1.3. The most notable change is the
introduction of a new API for creating Option instances.
CLI 1.3 RC1 is avai
Hi,
we're discussing our first incubating release, and we came to the issue
that we are not grant with permissions to deploy maven artifacts to the
org.apache.commons groupId [1].
The path of the project of graduating as a Commons components has not
changed. So we have agreed to keep compatible w
+1 (non-binding)
On Sun, May 3, 2015 at 11:43 AM, Benedikt Ritter wrote:
> Hi all,
>
> the Commons RDF project has discovered a problem with the Commons Skin when
> using it with a base url different from commons.apache.org (see
> COMMONSSITE-82 [1]). To fix this, I'd like to call a vote by lazy
2015-05-03 12:38 GMT+02:00 Jacopo Cappellato :
> On May 3, 2015, at 11:04 AM, Benedikt Ritter wrote:
>
> > Hi Jacopo,
> >
> > I was expecting you! ;-)
>
> Hi Benedikt,
>
> I just saw your email after I have sent mine! But yeah, it seems we are on
> the same page :-)
> Thanks for the information:
On May 3, 2015, at 11:04 AM, Benedikt Ritter wrote:
> Hi Jacopo,
>
> I was expecting you! ;-)
Hi Benedikt,
I just saw your email after I have sent mine! But yeah, it seems we are on the
same page :-)
Thanks for the information: I will review the list of pending items and if
there is anything
2015-05-03 11:31 GMT+02:00 Gary Gregory :
> Wow, we use an old version of Bootstrap!
>
Yes, that's true. My plan for the long term is to use npm + browserify or
webjars to pull in the bootstrap dependency. I think the skin needs a
general clean up, but working on the skin is really one of my lowe
Hi all,
the Commons RDF project has discovered a problem with the Commons Skin when
using it with a base url different from commons.apache.org (see
COMMONSSITE-82 [1]). To fix this, I'd like to call a vote by lazy consensus
to release commons-skin-4.1 based on RC1. The only change to commons-skin-
Wow, we use an old version of Bootstrap!
Gary
On Sun, May 3, 2015 at 2:27 AM, wrote:
> Author: britter
> Date: Sun May 3 09:27:02 2015
> New Revision: 1677379
>
> URL: http://svn.apache.org/r1677379
> Log:
> Creating commons-skin-4.1-RC1 tag
>
> Added:
> commons/proper/commons-skin/tags/co
Hi Jacopo,
I was expecting you! ;-)
Here is the list of stuff that should be resolved [1]. I'm not sure about
CLI-249 because I currently don't know how the API for that should look
like.
Note that Apache Commons Project has granted write access to all ASF
committers a while back [2]. So if you l
Hello Charles,
nice first implementation of LANG-1127. However it looks somehow
complicated to me.
When I wrote the ticket, I was thinking of a base class like:
public class LocaleAndTimeZoneBaseTest {
private static final Locale DEFAULT_LOCALE = Locale.getDefault();
private static final
Hi guys,
any news on this? If there are pending tickets that are blocking the release I
could try to help to resolve them.
Thanks,
Jacopo
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-m
23 matches
Mail list logo
