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-collections has an issue affecting its community integration.
This
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-configuration-test has an issue affecting its community
integrati
On 2009-09-15, Gump wrote:
> Project commons-collections has an issue affecting its community integration.
...
> [javac]
> /srv/gump/public/workspace/apache-commons/collections/src/test/org/apache/commons/collections/TestCollectionUtils.java:275:
> cannot find symbol
> [javac] symbol
Henri Yandell wrote:
> Question becomes what to do with the two JIRA projects that are now one.
You mean the versions of COLLECTIONS project?
> My suggestion:
>
> ---
> Rename 3.3 to 4.0
> Bulk edit Generics version to 4.0
> Delete Generics version
> ---
+1
- Jörg
--
--- On Tue, 9/15/09, Henri Yandell wrote:
> From: Henri Yandell
> Subject: [collections] merging collections - DONE
> To: "Commons Developers List"
> Date: Tuesday, September 15, 2009, 1:07 AM
> On Sun, Sep 13, 2009 at 9:08 PM,
> Henri Yandell
> wrote:
>
> >
> > Tests compile (under Maven).
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-collections has an issue affecting its community integration.
This
The commons parent pom is getting rather out of date, and could do
with a refresh.
What is the procedure for doing this?
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commo
On Tue, Sep 15, 2009 at 1:18 PM, sebb wrote:
> The commons parent pom is getting rather out of date, and could do
> with a refresh.
Yup.
>
> What is the procedure for doing this?
1) Update snapshot version of parent pom as desired and test (iterate
as necessary)
2) Post intent to release so