On Fri, May 22, 2009 at 2:12 AM, Christian Grobmeier
wrote:
>> Another minor glitch I noticed just now. All pages seem to include a
>> green "1.1-SNAPSHOT" in the grey headline, which may come in via the
>> generating style sheet or an ant property (I didn't check how the site
>> is generated).
>
On Fri, May 22, 2009 at 6:14 AM, sebb wrote:
> On 22/05/2009, Rahul Akolkar wrote:
>> On Fri, May 22, 2009 at 7:08 AM, sebb wrote:
>> > On 22/05/2009, Christian Grobmeier wrote:
>> >> > Another minor glitch I noticed just now. All pages seem to include a
>> >> > green "1.1-SNAPSHOT" in the
ith the following tally (marking binding votes
> with *):
>
> +1* Luc Maisonobe
> +1* Henri Yandell
> +1* James Carman
> +1* Brent Worden
> +1 Edward J. Yoon
> +1* Jörg Schaible
> +1 Dimitri Pourbaix (changed from -1 to +1)
>
> +0 Ted Dunning
> +0 Cyril Briquet
Sounds good.
On Sat, May 23, 2009 at 4:02 PM, Craig L Russell wrote:
> Here's my take on graduating Sanselan from incubator to commons.
>
> 1. Sanselan has been accepted by Commons.
> 2. The active committers have been granted write access to the repository.
>
> Remaining issues:
>
> 1. Deciding
On Sat, May 23, 2009 at 5:34 AM, Robert Burrell Donkin
wrote:
> (apologies for jumping in half way through)
>
> luc.maison...@free.fr wrote:
>> Hello,
>>
>> Considering the ongoing discussion in another thread, the current changes
>> that have been done on
>> [math] for the last months belong to
On Sat, May 23, 2009 at 11:30 PM, Phil Steitz wrote:
>> We're the victims of an experiment that was only half completed imo.
>>
>
> +1. I tend to remove the development reports when I cut RCs and roll
> releases. I also favor having the www website focussed on current
> development, with prior
On Sat, May 23, 2009 at 3:33 AM, sebb wrote:
> On 23/05/2009, Henri Yandell wrote:
>> Maven release plugin is the one doing the copy to the branch. So I
>> don't see the commit message (well.. it's probably somewhere in the
>> huge load of text that passes t
I realize this thread went the wrong direction.
Why the green? Just noticed Taglibs has the same problem (it uses the
Commons CSS :) ). Very ugly. Presumably we used to use a different
colour and the CSS has been changed?
Hen
On Fri, May 22, 2009 at 4:08 AM, sebb wrote:
> On 22/05/2009, Christi
On Wed, May 27, 2009 at 5:57 AM, Emmanuel Bourg wrote:
> Could everyone look at their projects and fix the files please?
Just as a note - there's no reason why someone can't do all of them if
they want.
Should be a simple regex.
Hen
On Thu, May 28, 2009 at 3:47 AM, sebb wrote:
> On 28/05/2009, sebb wrote:
>> On 28/05/2009, Henri Yandell wrote:
>> > On Wed, May 27, 2009 at 5:57 AM, Emmanuel Bourg wrote:
>> >
>> > > Could everyone look at their projects and fix the files p
Thanks. Fixed in trunk so that getValue says it returns the value.
On Fri, Jun 5, 2009 at 11:51 AM, Andrew M wrote:
>
>
>
>
> From: NYSE_ARCA [mailto:nyse_a...@oc384.net]
> Sent: Friday, June 05, 2009 1:36 PM
> To: 'dev@commons.apache.org'
> Subject: collections error
>
>
>
> It looks like the jav
I've rewritten StringEscapeUtils by putting a mini-framework underneath it:
https://issues.apache.org/jira/browse/LANG-505
On the one hand, Lang has not been a place for frameworks. On the
other hand, StringEscapeUtils has repeatedly shown a need to be much
more pluggable and not tie the user int
+1.
Sigs good. Archives equivalent. Source builds on Maven2 and Ant [JDK
1.5 on OS X 10.4]. Release notes look good, license/notice looks good
(jars contain both). POOL-144 seems good.
On Sat, Jun 13, 2009 at 1:26 PM, Phil Steitz wrote:
> Pool 1.5 contained a nasty regression (POOL-144) that has
cape.unescape(writer, string);
> }
> }
>
> The would lead to client statements that looked like this, which might be
> useful just for clarity:
>
> StringEscapeUtils.escape(StringEscapes.CSV, myCsvString);
>
> But would also allow for custom implementations:
>
> StringEscape myStringEs
I just committed the new text.translate package to Lang (r787560, see
LANG-505).
It rips the guts out of StringEscapeUtils and Entities, merges them
into a common paradigm and allows for reusable building blocks so the
answer to "I don't want low unicode escaped in my XML" can be "copy
and paste t
The most important part to consider is 'What can go wrong?'.
In the case of making 1.0 and deleting if it fails, let's imagine the
release then pauses. For example Collections 3.3. We would then have
the possibility of a 3.3 tag that people would think meant something.
In the case of making 1.0-r
Now that the StringEscape system has a foundation to support
whatever's needed (one hopes) the next step is to define exactly what
escaping XML should do. As Jörg notes in LANG-66, XML is different for
XML 1.0 and 1.1. Great, let's support both then. StringEscapeUtils can
support the old method (fo
Off the top of my head:
Wiki? JIRA rename/category change? Closing of old mailing list?
Updating Incubator page to indicate graduation?
On Wed, Jul 1, 2009 at 5:41 AM, Carsten Ziegeler wrote:
> Hi,
>
> finally we have passed all votes successfully to graduate Sanselan to
> commons. Thanks for eve
Pondering an idea of a Commons Time package that would sit on top of
Joda Time/JSR 310. Lang's time package functionality would go in
there, along with various enhancement ideas. The less core stuff than
the JSR handles. Items like:
* DateSequence, which would handle an open issue [LANG-347] for a
Until the new time stuff is in Java - I'm hesistant to have it in
Lang. Yet I also don't want to do anymore work on Date based code in
Lang :)
On Sat, Jul 4, 2009 at 7:42 AM, Paul Benedict wrote:
> I'd rather see it in Commons Lang.
>
> On Fri, Jul 3, 2009 at 4:09
On Tue, Jun 30, 2009 at 7:16 AM, John Bollinger wrote:
>
>
>
> Jörg Schaible wrote:
>> As pointed out http://www.w3.org/TR/2006/REC-xml11-20060816/#charsets and
>> http://www.w3.org/TR/2006/REC-xml11-20060816/#charsets define the valid
>> characters for XML 1.0 and 1.1.
>>
>> However, the escape fu
Looks like somebody took care of this, it's now in the table on the
front page of commons.apache.org.
Hen
On Wed, Jul 15, 2009 at 11:40 PM, Ashish wrote:
> Folks,
>
> It will be great if we can add Sanselan to the commons proper list on
> http://commons.apache.org/
>
> Google search still take on
*nominates Gary* :)
aka... not me. I'm still hoping someone else can RM Collections so I
can stay focused on Lang and Taglibs RMing.
On Fri, Jul 17, 2009 at 6:34 PM, Gary
Gregory wrote:
> Hi All:
>
> Do we have a volunteer to act as release manager for Codec 1.4?
>
> Gary
>
>
So some grumbles about the exceptions, and wondering which are worth fixing.
1) All the exceptions are in lang.* rather than lang.exception.*. Now
that the subpackage is pretty empty, it's tempting to move the
exceptions themselves down there. Given that it's going to be a
different package (ie: l
Hi Stephen :)
On Sun, Jul 19, 2009 at 11:35 AM, Stephen
Colebourne wrote:
> Henri Yandell wrote:
>>
>> 1) All the exceptions are in lang.* rather than lang.exception.*. Now
>> that the subpackage is pretty empty, it's tempting to move the
>> exceptions themselves d
On Mon, Jul 20, 2009 at 12:24 PM, Stephen
Colebourne wrote:
> Henri Yandell wrote:
>>>>
>>>> 2) NullArgumentException
>>
>> How about putting in the backcompat?
>
> I would be fine with all four going in the backcompat.
On Wed, Aug 5, 2009 at 6:23 PM, Julius Davies wrote:
>
> Henri seems pretty busy these days.
On that note
2009's actually been a very active year for me code wise:
http://www.svnsearch.org/svnsearch/repos/ASF/search?from=20090101&to=20091231&author=bayard
Split generally between Taglibs and
On Fri, Aug 7, 2009 at 8:31 AM, Rahul Akolkar wrote:
> On Fri, Aug 7, 2009 at 5:09 AM, wrote:
>>
>> - "Jörg Schaible" a écrit :
>>
>>> Hi Phil,
>>>
>>> why are there still 20 issues in JIRA marked as resolved instead of
>>> closed
>>> now?
>>
>> I forgot to close them, sorry.
>> I'll do it in
Please - get involved :)
General gameplan for a long time now has been to be a for user's
contributions; however with 3.0 there's a lot of room for proposing
rewrites of features and killing old APIs that aren't 'right'.
Usual 'rules' - make sure there's a JIRA for anything which is a
change to
On Sun, Aug 9, 2009 at 1:37 PM, Michael Wooten wrote:
> These are several additions that I feel might be useful to the Commons Lang
> Project. Please feel free to provide feedback, and if there is enough
> interest in any of them I will create JIRA entries, code them, and provide
> patches.
>
> Exp
Maybe something for the CompareUtils class proposed in LANG-483:
http://issues.apache.org/jira/browse/LANG-483
I'd prefer compareNullFirst, compareNullLast instead of the boolean param.
Hen
On Mon, Aug 10, 2009 at 5:23 AM, Antony Riley wrote:
> Maybe I'm missing something obvious but commons
On Mon, Aug 10, 2009 at 11:09 PM, Henri Yandell wrote:
> On Sun, Aug 9, 2009 at 1:37 PM, Michael Wooten wrote:
>>
>> I would also like to propose some support be added to Lang for basic event
>> handling. This would be based on the way that PropertyChangeSupport can be
>
+1 to remove.
On Thu, Aug 20, 2009 at 2:32 AM, sebb wrote:
> LANG trunk currently includes some use of JCIP annotations.
>
> The annotations were defined with Runtime retention.
>
> Although the annotation jar is not needed to run applications, it
> turns out that the Sun Java 1.5 compiler reports
TDD and Commons is an interesting subject to consider. Personally I'd
add Lang to your list as it is of the same ilk.
My general belief on TDD has been that it's the right idea but it's a
bit over-hyped. You need a scaffold when writing new code, but there
should be no belief that the test implies
On Sun, Sep 6, 2009 at 1:40 PM, Oliver
Heger wrote:
> Phil Steitz schrieb:
>>
>> Oliver Heger wrote:
>>>
>>> AIUI the mission of commons-lang is to provide extensions and
>>> improvements for existing Java API classes. The concurrent package in
>>> Java 5 is a great step forward in supporting multi
Thought I'd share the status of Lang 3.0.
* 65 resolved issues out of 131. Basically around 50% of the way there.
* 65 contributors involved, with 55 patches and 340 comments. Thanks
to everyone out there for the work so far.
* First commit on 25 Mar 2008, so about 18 months along now. That was
on
On Fri, Sep 11, 2009 at 7:17 AM, Matt Benson wrote:
>
>
>> Henri Yandell commented on COLLECTIONS-110:
>> ---
>>
>> In the absence of anyone being active on a rewrite of
>> Collections for generics, I agree with James that
On Fri, Sep 11, 2009 at 8:58 AM, Matt Benson wrote:
>
>
> --- On Fri, 9/11/09, Henri Yandell wrote:
>
>> From: Henri Yandell
>> Subject: Re: [collections] generics WAS [jira] Commented: (COLLECTIONS-110)
>> Support parametized classes with commons.collections.
&
On Sat, Sep 12, 2009 at 2:00 AM, Henri Yandell wrote:
> On Fri, Sep 11, 2009 at 8:58 AM, Matt Benson wrote:
>>
>>
>> --- On Fri, 9/11/09, Henri Yandell wrote:
>>
>>> First up would be to cp trunk to a 3.x branch. It's also
>>> possible that
>
The former is also crucial for anyone trying to work things out from
your svn logs. Usually the commit message is quite low on information
and having a link to the bugzilla entry or JIRA entry is great.
The latter is less crucial but useful because a) svn commit tab in
JIRA has been known to break
On Sat, Sep 12, 2009 at 7:26 AM, Rahul Akolkar wrote:
> On Sat, Sep 12, 2009 at 5:52 AM, Henri Yandell wrote:
>> On Sat, Sep 12, 2009 at 2:00 AM, Henri Yandell wrote:
>>> On Fri, Sep 11, 2009 at 8:58 AM, Matt Benson wrote:
>>>>
>>>>
>>>> --- O
On Sat, Sep 12, 2009 at 2:05 PM, Henri Yandell wrote:
> On Sat, Sep 12, 2009 at 7:26 AM, Rahul Akolkar wrote:
>> On Sat, Sep 12, 2009 at 5:52 AM, Henri Yandell wrote:
>>> On Sat, Sep 12, 2009 at 2:00 AM, Henri Yandell wrote:
>>>> On Fri, Sep 11, 2009
Side thought if anyone feels like having an opinion.
Which is better?
a) One big commit, merging the branch in in one go (the usual approach).
b) One commit per file, with the commit log including all of the
change history of the file while it was on the branch; except for a
few global commits th
On Sun, Sep 13, 2009 at 12:08 AM, Henri Yandell wrote:
>
> Hopeful that I can resolve the two above over the next couple of nights.
Latest status update (as I'm worried this is the kind of thing that
could fall off my priority list and lots of people are stuck waiting;
no status up
On Sun, Sep 13, 2009 at 5:56 PM, Henri Yandell wrote:
>
> The maven build passes the syntactic part of the compiler, but about
> 16 errors in the semantic part to look at. I'll look at each as it's
> likely it's due to merging issues. Some may be because that code
&g
On Sun, Sep 13, 2009 at 9:08 PM, Henri Yandell wrote:
>
> Tests compile (under Maven). 4 serialization ones fail when running -
> will dig into. Might be a merging issue with .obj files and id values
> in classes.
Fixed these btw by setting serialVersionUIDs to the previous va
orth it in the long term.
Also should mean that JIRA will pick up the merge for each issue too.
On Sun, Sep 13, 2009 at 5:38 PM, Henri Yandell wrote:
> Side thought if anyone feels like having an opinion.
>
> Which is better?
>
> a) One big commit, merging the branch in in one go
Question becomes what to do with the two JIRA projects that are now one.
My suggestion:
---
Rename 3.3 to 4.0
Bulk edit Generics version to 4.0
Delete Generics version
---
Hen
-
To unsubscribe, e-mail: dev-unsubscr...@commons.a
On Tue, Sep 15, 2009 at 10:11 AM, Matt Benson wrote:
>
>
> --- On Tue, 9/15/09, Henri Yandell wrote:
>
>> From: Henri Yandell
>> Subject: [collections] merging collections - DONE
>> To: "Commons Developers List"
>> Date: Tuesday, September 15, 20
Here's an old thought - but why not centralize the javadoc?
Instead of having components managing their release javadoc, instead make a
central library in which the javadoc sites, then deep link to a components
item within it. Then it's pretty easy to find an old release, pull the
javadoc out and
I think we should keep the lights on, but no more. So sites should exist to
that level.
What is the minimum needed on the site for a dormant project?
Pointer to this list, explanation of what it is/was, pointer to old
releases and to the location of the source history.
I'm torn on javadoc; I don
On Sat, Dec 7, 2013 at 12:43 AM, Benedikt Ritter wrote:
>
>
> Send from my mobile device
>
> > Am 06.12.2013 um 18:11 schrieb sebb :
> >
> >> On 6 December 2013 14:11, Duncan Jones wrote:
> >>> On 6 December 2013 12:51, Benedikt Ritter
> wrote:
> >>> 2013/12/6 Gilles
> >>>
> Hi.
>
> >
JIRA issue reopened btw as I noticed it was still resolved.
On Wed, Dec 25, 2013 at 11:10 AM, Jason Pyeron wrote:
> > -Original Message-
> > From: Benedikt Ritter
> > Sent: Wednesday, December 25, 2013 11:53
> >
> > You've set the issue to status resolved. That's propably the
>
> After
+1.
On Sat, Dec 28, 2013 at 9:57 AM, Benedikt Ritter wrote:
> Hi all,
>
> I've fixed the issues, that were identified in RC1:
>
> - Release notes now make explicit that 3.2 at least requires Java 6.0
> - Website now makes explicit that 3.2 at least requires Java 6.0
> - MANIFEST now contains "b
Also +1 to all.
On Thu, Jan 2, 2014 at 6:40 AM, Gary Gregory wrote:
> +1 to it all.
>
> Gary
>
> Original message
> From: Benedikt Ritter
> Date:01/02/2014 05:29 (GMT-05:00)
> To: Commons Developers List
> Subject: [LANG] Next steps
>
> Hi all,
>
> I've successfully gone t
Yes we change the site between releases.
The bigger question is why we have a version number on the website, it
isn't versioned.
Hen
On Thu, Jan 2, 2014 at 6:45 AM, Duncan Jones wrote:
> Hi all,
>
> The top of the commons-lang web page reads:
>
> "Last Published: 01 January 2014 | Version: 3
with the RMing :)
Hen
On Thu, Jan 2, 2014 at 8:56 PM, Henri Yandell wrote:
> Also +1 to all.
>
>
> On Thu, Jan 2, 2014 at 6:40 AM, Gary Gregory wrote:
>
>> +1 to it all.
>>
>> Gary
>>
>> Original message
>> From: Benedikt Ritter
On Fri, Jan 3, 2014 at 2:35 AM, Benedikt Ritter wrote:
> Hello Hen
>
>
> 2014/1/3 Henri Yandell
>
> > Better move quick on 3.2.1. Only bit I don't like about that is that it
> > implies we shouldn't be committing anything that would lead us to want to
ease
> of the code base.
>
> G
>
> Original message
> From: Benedikt Ritter
> Date:01/03/2014 08:12 (GMT-05:00)
> To: Commons Developers List
> Subject: Re: [LANG] Snap-shot version in website header
>
> 2014/1/3 Henri Yandell
>
> >
On Sat, Jan 4, 2014 at 3:14 AM, Benedikt Ritter wrote:
> 2014/1/4 Henri Yandell
>
> > On Fri, Jan 3, 2014 at 2:35 AM, Benedikt Ritter
> > wrote:
> >
> > > Hello Hen
> > >
> > >
> > > 2014/1/3 Henri Yandell
> > >
> > &g
On Sat, Jan 4, 2014 at 11:44 AM, Henri Yandell wrote:
>
>
>
> On Sat, Jan 4, 2014 at 3:14 AM, Benedikt Ritter wrote:
>
>> 2014/1/4 Henri Yandell
>>
>> > On Fri, Jan 3, 2014 at 2:35 AM, Benedikt Ritter
>> > wrote:
>> >
>&g
(non-binding) +1 from me :)
Reviewed the diff between 3.2 and 3.2.1 tags. Source builds happily for me.
Hen
On Sun, Jan 5, 2014 at 10:26 AM, Benedikt Ritter wrote:
> Hi all,
>
> during the vote for Commons Lang 3.2, two issues were identified, namely:
>LANG-937: Fix missing Hamcrest depen
On Mon, Jan 20, 2014 at 8:01 AM, Benedikt Ritter wrote:
> 2014/1/18 Oliver Heger
>
> >
> >
> > Am 18.01.2014 17:40, schrieb Emmanuel Bourg:
> > > Le 18/01/2014 16:04, Benedikt Ritter a écrit :
> > >
> > >> About putting this into codec: I still don't think this is a good fit
> > for
> > >> this
+1. Makes svn blame useless by creating a date in time when everything was
touched.
On Thu, Jan 23, 2014 at 10:07 AM, sebb wrote:
> I think there is a big difference between creating a class with sorted
> methods, and retrospectively sorting methods in an existing class.
>
> That may improve th
In case you didn't get an answer here:
http://stackoverflow.com/questions/304383/how-do-i-edit-a-log-message-that-i-already-committed-in-subversion
$svn propedit -r N --revprop svn:log URL
$svn propset -r N --revprop svn:log "new log message" URL
On Thu, Jan 23, 2014 at 9:17 AM, Benedikt Ritte
Depends whose arguing probably :)
Our license gives us a right to contributions under Apache 2.0 unless
stated otherwise; the ICLA is playing safer. We can also simply take
anything under a compatible license and include (with suitable licensing).
I did that for a method from Spring.
Hen
On Sun
x27;re better of with an ICLA.
>
> Benedikt
>
>
> 2014/1/27 Henri Yandell
>
> > Depends whose arguing probably :)
> >
> > Our license gives us a right to contributions under Apache 2.0 unless
> > stated otherwise; the ICLA is playing safer. We can also simply
+1.
On Thu, Mar 13, 2014 at 11:19 AM, Benedikt Ritter wrote:
> My +1 for the record
>
>
> 2014-03-11 21:08 GMT+01:00 Benedikt Ritter :
>
> > Hi all,
> >
> > as discussed, I'd like to propose to move Apache Commons Betwixt to
> > dormant.
> >
> > Reasons:
> > - no real activity for a long while [
Note that checking out from trunks-proper should check out the same code.
It's a way to check out all of the Commons component's trunks at the same
time.
Hen
On Fri, Apr 4, 2014 at 9:36 AM, Benedikt Ritter wrote:
> Hello Svitana,
>
> you've checken out from the wrong location. The codebase is a
+1 to remove.
On Mon, Apr 21, 2014 at 1:42 PM, Duncan Jones wrote:
> Hi everyone,
>
> The Conversion class has numerous instances in which a value is
> multiplied by one (e.g. line 1054):
>
> shift = i * 1 + dstPos;
>
> I suspect this is a copy/paste issue, since other parts of the class
> foll
On Sat, Oct 18, 2014 at 2:44 PM, Phil Steitz wrote:
> On 10/18/14 2:03 PM, Paul Benedict wrote:
> > You are not including duplicate artifacts, they are totally distinct.
>
> I think Romain's point is that classes that are not changed in the
> different versions are duplicated. It's interesting t
(DNS issues, trying again)
-- Forwarded message --
From: Henri Yandell <[EMAIL PROTECTED]>
Date: Aug 15, 2007 6:56 AM
Subject: [CLI] Getting moving with 2.0
To: Jakarta Commons Developers List , Andrew
Shirley <[EMAIL PROTECTED]>
Two different angles I guess.
First
svn switch doesn't do svn:externals.
I used svn status to figure out which ones I had changes on. I rm'd
the other components, did an svn switch of the trunks-proper
directory, did an svn switch of the components I had local changes on
and then did an svn update to get all of the others.
Hen
On
Hi Gerhard,
Thanks for the suggestion. Could I ask you to create a JIRA item for it?
Lang improvements (as opposed to bugs) tend to be a case of getting
them in JIRA, and then seeing what people think over time.
http://issues.apache.org/jira/browse/LANG
Thanks,
Hen
On 8/15/07, Gerhard Maree <
if [ $? -ne 0 ]
then
echo "Property $j is missing."
else
echo "Property $j is good."
fi
done
done
}
On 8/15/07, sebb <[EMAIL PROTECTED]> wrote:
> On 15/08/07, Henri Yandell <[EMAIL PRO
On 8/17/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> The topic of code style pops up every now and then on this list. Do you
We can't even agree on tags in javadoc :)
Why should I, someone who writes web pages sometimes, write bad HTML
to join the consensus (well, 2 other opinions) that pre
On 8/17/07, Matt Benson <[EMAIL PROTECTED]> wrote:
>
> --- Rahul Akolkar <[EMAIL PROTECTED]> wrote:
>
> > On 8/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> > wrote:
> > > Author: mbenson
> > > Date: Mon Aug 13 17:06:29 2007
> > > New Revision: 565581
> > >
> > > URL:
> > http://svn.apache.org/vie
None that I know of, but sounds like a good idea to me.
Could you open a JIRA for this improvement?
http://issues.apache.org/jira/browse/CLI
Thanks,
Hen
On 8/17/07, David J. Biesack <[EMAIL PROTECTED]> wrote:
>
> Are there plans to add a regular expression based Validator to CLI2?
>
> This wou
Click on Administer Project at https://issues.apache.org/jira/browse/MATH
I just adjusted the members so that every commons developer is a MATH
admin [I'm slowly doing it to all commons projects as I notice].
Hen
On 8/19/07, Luc Maisonobe <[EMAIL PROTECTED]> wrote:
> I recently changed the "Fix
Hope no one minds my having committed this. I don't commit to Digester
very often, but as that one was on a list of interesting issues I'm
working through, I figured I'd go ahead and see if anyone was upset :)
Hen
On 8/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Author: bayard
> Date: T
All M2 projects are now added. 6 have test failures. I think there was
a suggestion that we only add M2 ones, which sounds good. It'll drive
the rest to M2.
Hen
On 8/22/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> FYI - the old machine is scheduled to be taken down in 24 hours, so in
> the inter
'Commons' was removed because it was 50% one way and 50% the other
way. So I went the way easy for me :)
All the Sandbox ones had Commons in front of though, so that would
have swung the numbers if I'd been looking at that.
I'll go ahead and change things back tomorrow.
Hen
On 8/22/07, Ben Spea
*pokes JIRA permissions*
Should be fixed. I'm changing Commons projects so that
commons-developers are admins on each of them. Turns out that admins
don't get all the permissions.
They do now :)
Hen
On 8/22/07, Matt Benson <[EMAIL PROTECTED]> wrote:
> Looks like I can no longer resolve JXPATH i
Anyone know if Continuum has rw access to java.io.tmpdir? Presumably /tmp/ ?
On 8/22/07, [EMAIL PROTECTED] wrote:
> Online report :
> http://vmbuild1.apache.org/continuum/buildResult.action?buildId=2066&projectId=166
>
> Build statistics:
> State: Failed
> Previous Build: No previous build.
Everything seems to build (that's in CI), except:
* Compress - Dennis discovered that this is an EOL issue.
* VFS - has a failing test, both in and out of CI.
* FileUpload - failing tests in CI, works out of CI.
* Configuration - failing tests (55!) in CI, I get 1 failure out of CI.
* JCI - failin
On 8/24/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Henri Yandell wrote:
> > Everything seems to build (that's in CI), except:
> >
> > * Compress - Dennis discovered that this is an EOL issue.
> > * VFS - has a failing test, both in and out of CI.
> &g
On 8/25/07, Martin Cooper <[EMAIL PROTECTED]> wrote:
> On 8/25/07, Phil Steitz <[EMAIL PROTECTED]> wrote:
> >
> > On 8/25/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> > > Martin Cooper wrote:
> > >
> > > > > GUMP builds are deemed non-trusted, since GUMP downloads from
> > > > > non-ASF sites a
We can change CI to use a JDK 1.6 if that's what Configuration's target is.
On 8/28/07, Oliver Heger <[EMAIL PROTECTED]> wrote:
> Just an update: the tests should now run on a JDK 1.6. I was able to get
> rid of these dependencies on static fields. I also applied most of the
> improvements to the
On 8/29/07, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> Can you, or someone else, poke them for me as well (or tell me how
> to). I seem to have lost the ability to deal with [SCXML] tickets as I
> used to.
Done. You weren't in the commons-developer group.
>
> I see an "Administration" tab, click
On 8/30/07, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> On 8/29/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> > On 8/29/07, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
> > >
> > > I see an "Administration" tab, clicking on which lists "a
I've updated it with something a bit more relevant.
On 9/2/07, sebb <[EMAIL PROTECTED]> wrote:
> The top of the index page for Commons downloads:
>
> http://www.apache.org/dist/commons/
>
> says (in part):
>
> >>>
> Apache Commons Project Source Code Distributions
>
> This downloads page includes
Maybe a named anchor?
On 9/6/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> Simon, thanks for pointing that out. I didn't find that obvious :-) Perhaps
> the package documentation could be titled User Guide.
>
> Paul
>
> On 9/6/07, simon <[EMAIL PROTECTED]> wrote:
> >
> > On Tue, 2007-09-04 at 14:
Hey Torsten,
Feedback from the board report; what did you mean by "sponsoring" below?
New Incubator project?
Hen
On 9/13/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
> Apache Commons Board Report, September 2007
>
> Summary
> ===
>
>Not that much happened this month.
>
>o A couple o
> o that the there is no real community behind it
>
> So the idea was to *copy* code from it to help "compression" out in
> areas where it needs help.
> As it is ASL2.0 it should be no problem though.
>
> cheers
> --
> Torsten
>
> On 19.09.2007, at 19:4
Paul
>
> On 9/20/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
> >
> >
> > On 19.09.2007, at 20:56, Henri Yandell wrote:
> >
> > > It would still be code that's not covered by a CLA, so different from
> > > most of the code at the ASF.
> >
&
I think they're an old convenience that people have kept because
that's what people do with things that are not obviously broken.
I'm +1 to getting rid of them, I don't think they buy us anything, and
if they're a mirror issue then the sooner the better.
Anyone against rm'ing them? It should be p
+1 too.
On 9/28/07, Ben Speakmon <[EMAIL PROTECTED]> wrote:
> +1 nonbinding.
>
> On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote:
> >
> > +1
> >
> > On 9/28/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> > > +1
> > >
> >
> > -
o I guess
> we need an official vote thread started after this. Should I go ahead
> and start that now?
>
> On 9/28/07, Luc Maisonobe <[EMAIL PROTECTED]> wrote:
> > +1
> >
> > Henri Yandell wrote:
> > > +1 too.
> > >
> > > On 9/28/07, B
On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote:
> I do not know which of these votes are binding/non-binding.
To figure it out, cross reference with the committee-info.txt file in
svn-private:committers/board/
Though all you really need to do is show that there are 3 binding
votes there when
On 9/28/07, sebb <[EMAIL PROTECTED]> wrote:
> On 29/09/2007, Henri Yandell <[EMAIL PROTECTED]> wrote:
> > On 9/28/07, James Carman <[EMAIL PROTECTED]> wrote:
> >
> > > I do not know which of these votes are binding/non-binding.
> >
> > To figu
801 - 900 of 1072 matches
Mail list logo
