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-vfs2 has an issue affecting its community integration.
This issue
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-scxml-test 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-proxy-test has an issue affecting its community integration.
This
I think the time has come to formally vote on the updates to Commons
Skin and Commons Parent.
Maven artifacts:
https://repository.apache.org/content/repositories/orgapachecommons-008/org/apache/commons/
SVN
https://svn.apache.org/repos/asf/commons/proper/commons-skin/tags/commons-skin-3-RC2/
and
Pardon me for being dense, but what do I put in my POM to test this?
Gary
On Mon, Mar 7, 2011 at 3:47 PM, sebb wrote:
> I think the time has come to formally vote on the updates to Commons
> Skin and Commons Parent.
>
> Maven artifacts:
>
>
> https://repository.apache.org/content/repositories/o
On Sat, Mar 5, 2011 at 8:46 AM, Oliver Heger
wrote:
> Two minor points from my side:
>
> - There are still many checkstyle errors in the current code base.
Can be improved but nothing felt hugely critical. A large amount are
lines greater than 120 chars. Looks like SystemUtils has been
formatted
Should we be claiming trademark on 'Commons'?
Like Incubator & Attic it seems like something we want to continue
encouraging as a de facto standard instead of subjecting to trademark
protection.
Hen
On Mon, Mar 7, 2011 at 12:47 PM, sebb wrote:
> I think the time has come to formally vote on the