You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Eric Pugh <ep...@upstate.com> on 2003/12/17 11:04:53 UTC
[VOTE] Promote Configuration to Commons Proper
Configuration exhibits all of the qualities of a component that should be in
Commons proper:
- It's small and focused.
- It's API is well defined
- It has a group of existing Jakarta committers providing code, ideas, and
support.
- It has good unit test coverage. It has also been tested in real world
database applications.
- It has automated nightly builds, website, and Maven all working
- It has incubated in the sandbox for long enough to become stable
Configuration is a mature component that should move to Commons proper so it
can be released to the public. Here's my +1.
The website has additional information:
http://jakarta.apache.org/commons/sandbox/configuration/index.html
Here's the component proposal for reference:
(0) Rationale
Configuration is a project to provide a generic Configuration interface and
allow the source of the values to vary. It provides easy typed access to
single, as well as lists of configuration values based on a 'key'.
(1) Scope of the Package
This proposal is to create a package of Java utility classes for
implementing a simple Configuration object. Configuration will remain
environment agnostic, focusing on just providing Configuration values. It
does not provide any time of IoC style configuration of objects.
(1.5) Interaction With Other Packages
Configuration relies only on standard Java 1.3 (or later) APIs for
production deployment. It utilizes the JUnit testing framework for
developing and executing unit tests, but this is of interest only to
developers of the component. It is built using Maven.
No external configuration files are utilized.
(2) Initial Source of the Package
This code has been in Sandbox for over a year, and was originally originally
in the Apache JServ project, then in Turbine, then in Velocity, and finally
ended up in the sandbox.
The proposed package name for the new component is
<code>org.apache.commons.configuration</code>.
(3) Required Jakarta-Commons Resources
CVS Repository - New directory dbutils in the jakarta-commons CVS
repository.
Mailing List - Discussions will take place on the general
commons-dev@jakarta.apache.org mailing list. To help list subscribers
identify messages of interest, it is suggested that the message subject of
messages about this component be prefixed with [configuration].
Issue Tracking - Currently scarab on Nagoya is being used
(http://nagoya.apache.org/scarab/servlet/scarab/) however maybe this should
be moved to BugZilla?
(4) Initial Committers
The initial committers on the DBUtils component shall be:
Eric Pugh
Henning P. Schmiedehausen
Martin Poeschl
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE] Promote Configuration to Commons Proper
Posted by Stephen Colebourne <sc...@btopenworld.com>.
+1, with other changes people have mentioned.
I hope that we can promote some other sandbox components too over the next
few months.
Stephen
----- Original Message -----
From: "Eric Pugh" <ep...@upstate.com>
To: "Commons-Dev (E-mail)" <co...@jakarta.apache.org>
Sent: Wednesday, December 17, 2003 10:04 AM
Subject: [VOTE] Promote Configuration to Commons Proper
> Configuration exhibits all of the qualities of a component that should be
in
> Commons proper:
> - It's small and focused.
> - It's API is well defined
> - It has a group of existing Jakarta committers providing code, ideas, and
> support.
> - It has good unit test coverage. It has also been tested in real world
> database applications.
> - It has automated nightly builds, website, and Maven all working
> - It has incubated in the sandbox for long enough to become stable
>
> Configuration is a mature component that should move to Commons proper so
it
> can be released to the public. Here's my +1.
>
> The website has additional information:
> http://jakarta.apache.org/commons/sandbox/configuration/index.html
>
> Here's the component proposal for reference:
> (0) Rationale
>
> Configuration is a project to provide a generic Configuration interface
and
> allow the source of the values to vary. It provides easy typed access to
> single, as well as lists of configuration values based on a 'key'.
>
> (1) Scope of the Package
>
> This proposal is to create a package of Java utility classes for
> implementing a simple Configuration object. Configuration will remain
> environment agnostic, focusing on just providing Configuration values. It
> does not provide any time of IoC style configuration of objects.
>
> (1.5) Interaction With Other Packages
>
> Configuration relies only on standard Java 1.3 (or later) APIs for
> production deployment. It utilizes the JUnit testing framework for
> developing and executing unit tests, but this is of interest only to
> developers of the component. It is built using Maven.
>
> No external configuration files are utilized.
>
> (2) Initial Source of the Package
>
> This code has been in Sandbox for over a year, and was originally
originally
> in the Apache JServ project, then in Turbine, then in Velocity, and
finally
> ended up in the sandbox.
>
> The proposed package name for the new component is
> <code>org.apache.commons.configuration</code>.
>
> (3) Required Jakarta-Commons Resources
>
> CVS Repository - New directory dbutils in the jakarta-commons CVS
> repository.
>
> Mailing List - Discussions will take place on the general
> commons-dev@jakarta.apache.org mailing list. To help list subscribers
> identify messages of interest, it is suggested that the message subject of
> messages about this component be prefixed with [configuration].
>
> Issue Tracking - Currently scarab on Nagoya is being used
> (http://nagoya.apache.org/scarab/servlet/scarab/) however maybe this
should
> be moved to BugZilla?
>
>
> (4) Initial Committers
>
> The initial committers on the DBUtils component shall be:
> Eric Pugh
> Henning P. Schmiedehausen
> Martin Poeschl
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE] Promote Configuration to Commons Proper
Posted by Tim O'Brien <to...@discursive.com>.
+1
Configuration adheres to the Commons charter, and that it has a community.
Tim
Eric Pugh wrote:
>Configuration exhibits all of the qualities of a component that should be in
>Commons proper:
>- It's small and focused.
>- It's API is well defined
>- It has a group of existing Jakarta committers providing code, ideas, and
>support.
>- It has good unit test coverage. It has also been tested in real world
>database applications.
>- It has automated nightly builds, website, and Maven all working
>- It has incubated in the sandbox for long enough to become stable
>
>Configuration is a mature component that should move to Commons proper so it
>can be released to the public. Here's my +1.
>
>The website has additional information:
>http://jakarta.apache.org/commons/sandbox/configuration/index.html
>
>Here's the component proposal for reference:
>(0) Rationale
>
>Configuration is a project to provide a generic Configuration interface and
>allow the source of the values to vary. It provides easy typed access to
>single, as well as lists of configuration values based on a 'key'.
>
>(1) Scope of the Package
>
>This proposal is to create a package of Java utility classes for
>implementing a simple Configuration object. Configuration will remain
>environment agnostic, focusing on just providing Configuration values. It
>does not provide any time of IoC style configuration of objects.
>
>(1.5) Interaction With Other Packages
>
>Configuration relies only on standard Java 1.3 (or later) APIs for
>production deployment. It utilizes the JUnit testing framework for
>developing and executing unit tests, but this is of interest only to
>developers of the component. It is built using Maven.
>
>No external configuration files are utilized.
>
>(2) Initial Source of the Package
>
>This code has been in Sandbox for over a year, and was originally originally
>in the Apache JServ project, then in Turbine, then in Velocity, and finally
>ended up in the sandbox.
>
>The proposed package name for the new component is
><code>org.apache.commons.configuration</code>.
>
>(3) Required Jakarta-Commons Resources
>
>CVS Repository - New directory dbutils in the jakarta-commons CVS
>repository.
>
>Mailing List - Discussions will take place on the general
>commons-dev@jakarta.apache.org mailing list. To help list subscribers
>identify messages of interest, it is suggested that the message subject of
>messages about this component be prefixed with [configuration].
>
>Issue Tracking - Currently scarab on Nagoya is being used
>(http://nagoya.apache.org/scarab/servlet/scarab/) however maybe this should
>be moved to BugZilla?
>
>
>(4) Initial Committers
>
>The initial committers on the DBUtils component shall be:
>Eric Pugh
>Henning P. Schmiedehausen
>Martin Poeschl
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE] Promote Configuration to Commons Proper
Posted by __matthewHawthorne <ma...@phreaker.net>.
+1
Eric Pugh wrote:
> Configuration exhibits all of the qualities of a component that should be in
> Commons proper:
> - It's small and focused.
> - It's API is well defined
> - It has a group of existing Jakarta committers providing code, ideas, and
> support.
> - It has good unit test coverage. It has also been tested in real world
> database applications.
> - It has automated nightly builds, website, and Maven all working
> - It has incubated in the sandbox for long enough to become stable
>
> Configuration is a mature component that should move to Commons proper so it
> can be released to the public. Here's my +1.
>
> The website has additional information:
> http://jakarta.apache.org/commons/sandbox/configuration/index.html
>
> Here's the component proposal for reference:
> (0) Rationale
>
> Configuration is a project to provide a generic Configuration interface and
> allow the source of the values to vary. It provides easy typed access to
> single, as well as lists of configuration values based on a 'key'.
>
> (1) Scope of the Package
>
> This proposal is to create a package of Java utility classes for
> implementing a simple Configuration object. Configuration will remain
> environment agnostic, focusing on just providing Configuration values. It
> does not provide any time of IoC style configuration of objects.
>
> (1.5) Interaction With Other Packages
>
> Configuration relies only on standard Java 1.3 (or later) APIs for
> production deployment. It utilizes the JUnit testing framework for
> developing and executing unit tests, but this is of interest only to
> developers of the component. It is built using Maven.
>
> No external configuration files are utilized.
>
> (2) Initial Source of the Package
>
> This code has been in Sandbox for over a year, and was originally originally
> in the Apache JServ project, then in Turbine, then in Velocity, and finally
> ended up in the sandbox.
>
> The proposed package name for the new component is
> <code>org.apache.commons.configuration</code>.
>
> (3) Required Jakarta-Commons Resources
>
> CVS Repository - New directory dbutils in the jakarta-commons CVS
> repository.
>
> Mailing List - Discussions will take place on the general
> commons-dev@jakarta.apache.org mailing list. To help list subscribers
> identify messages of interest, it is suggested that the message subject of
> messages about this component be prefixed with [configuration].
>
> Issue Tracking - Currently scarab on Nagoya is being used
> (http://nagoya.apache.org/scarab/servlet/scarab/) however maybe this should
> be moved to BugZilla?
>
>
> (4) Initial Committers
>
> The initial committers on the DBUtils component shall be:
> Eric Pugh
> Henning P. Schmiedehausen
> Martin Poeschl
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE] Promote Configuration to Commons Proper
Posted by Emmanuel Bourg <e....@cross-systems.com>.
I think there are 2 copyright statements mixed here :
- the copyright of the ASF license since it's a copyrighted document
from the Apache Foundation. The date on the ASF license shouldn't be
changed, except when it's adapted for a specific component (the "you
must not reuse the project/product name" condition). For example the GPL
license is copyrighted by the FSF with a date set to 1989, 1991 and this
is never changed by projects released under the GPL (and actually they
can't change it since the license of the GPL doesn't allow modifitions).
- the copyright statement of the file, i.e. the date of its
creation/modification and the author of the code. I believe every
contributor retains the copyright on the code submitted but may assign
it to the ASF. I guess that's what happens most of the time and would
explain why a single copyright statement serves 2 purposes.
Emmanuel Bourg
Eric Pugh wrote:
> Re: [VOTE] Promote Configuration to Commons ProperSo, what is the deal with
> copyright, everytime it changes we need to update the date? I don't think
> anyone pays attention to it on a day to day basis.. Sounds like we need
> something like a maven plugin that checks each file, and if it has changed
> post whatever the copyright date is, then updates it...
>
> Eric
> -----Original Message-----
> From: Emmanuel Bourg [mailto:e.bourg@cross-systems.com]
> Sent: Thursday, December 18, 2003 11:28 AM
> To: Jakarta Commons Developers List
> Subject: Re: [VOTE] Promote Configuration to Commons Proper
>
>
> robert burrell donkin wrote:
>
> > i did happen to notice that some of the licenses have copyright ending
> > in 2002.
>
> Actually the copyright doesn't end in 2002 but starts in 2002, it's then
> valid for the lifetime of the author plus a minimum of 50 years after
> his death according to the Berne Convention.
>
> You are right though that some content submitted or modified this year
> doesn't have a copyright assigned in 2003.
>
> Emmanuel Bourg
>
RE: [VOTE] Promote Configuration to Commons Proper
Posted by Eric Pugh <ep...@upstate.com>.
Re: [VOTE] Promote Configuration to Commons ProperSo, what is the deal with
copyright, everytime it changes we need to update the date? I don't think
anyone pays attention to it on a day to day basis.. Sounds like we need
something like a maven plugin that checks each file, and if it has changed
post whatever the copyright date is, then updates it...
Eric
-----Original Message-----
From: Emmanuel Bourg [mailto:e.bourg@cross-systems.com]
Sent: Thursday, December 18, 2003 11:28 AM
To: Jakarta Commons Developers List
Subject: Re: [VOTE] Promote Configuration to Commons Proper
robert burrell donkin wrote:
> i did happen to notice that some of the licenses have copyright ending
> in 2002.
Actually the copyright doesn't end in 2002 but starts in 2002, it's then
valid for the lifetime of the author plus a minimum of 50 years after
his death according to the Berne Convention.
You are right though that some content submitted or modified this year
doesn't have a copyright assigned in 2003.
Emmanuel Bourg
Re: [VOTE] Promote Configuration to Commons Proper
Posted by Emmanuel Bourg <e....@cross-systems.com>.
robert burrell donkin wrote:
> i did happen to notice that some of the licenses have copyright ending
> in 2002.
Actually the copyright doesn't end in 2002 but starts in 2002, it's then
valid for the lifetime of the author plus a minimum of 50 years after
his death according to the Berne Convention.
You are right though that some content submitted or modified this year
doesn't have a copyright assigned in 2003.
Emmanuel Bourg
Re: [VOTE] Promote Configuration to Commons Proper
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
+1
i did find i have a few observations after taking a quick look (but i
don't think that there's anything here to stop promotion)...
i did happen to notice that some of the licenses have copyright ending
in 2002.
i couldn't get the maven documentation build to run. it's probably just
a version issue but it might be worth noting somewhere.
(i'm not sure whether you prefer jira but) i can't see a bugzilla
category.
configuration doesn't have a status file. this is probably ok for
mavenized components (which i think that maven is).
- robert
On 17 Dec 2003, at 10:04, Eric Pugh wrote:
> Configuration exhibits all of the qualities of a component that should
> be in
> Commons proper:
> - It's small and focused.
> - It's API is well defined
> - It has a group of existing Jakarta committers providing code, ideas,
> and
> support.
> - It has good unit test coverage. It has also been tested in real world
> database applications.
> - It has automated nightly builds, website, and Maven all working
> - It has incubated in the sandbox for long enough to become stable
>
> Configuration is a mature component that should move to Commons proper
> so it
> can be released to the public. Here's my +1.
>
> The website has additional information:
> http://jakarta.apache.org/commons/sandbox/configuration/index.html
>
> Here's the component proposal for reference:
> (0) Rationale
>
> Configuration is a project to provide a generic Configuration
> interface and
> allow the source of the values to vary. It provides easy typed access
> to
> single, as well as lists of configuration values based on a 'key'.
>
> (1) Scope of the Package
>
> This proposal is to create a package of Java utility classes for
> implementing a simple Configuration object. Configuration will remain
> environment agnostic, focusing on just providing Configuration values.
> It
> does not provide any time of IoC style configuration of objects.
>
> (1.5) Interaction With Other Packages
>
> Configuration relies only on standard Java 1.3 (or later) APIs for
> production deployment. It utilizes the JUnit testing framework for
> developing and executing unit tests, but this is of interest only to
> developers of the component. It is built using Maven.
>
> No external configuration files are utilized.
>
> (2) Initial Source of the Package
>
> This code has been in Sandbox for over a year, and was originally
> originally
> in the Apache JServ project, then in Turbine, then in Velocity, and
> finally
> ended up in the sandbox.
>
> The proposed package name for the new component is
> <code>org.apache.commons.configuration</code>.
>
> (3) Required Jakarta-Commons Resources
>
> CVS Repository - New directory dbutils in the jakarta-commons CVS
> repository.
>
> Mailing List - Discussions will take place on the general
> commons-dev@jakarta.apache.org mailing list. To help list subscribers
> identify messages of interest, it is suggested that the message
> subject of
> messages about this component be prefixed with [configuration].
>
> Issue Tracking - Currently scarab on Nagoya is being used
> (http://nagoya.apache.org/scarab/servlet/scarab/) however maybe this
> should
> be moved to BugZilla?
>
>
> (4) Initial Committers
>
> The initial committers on the DBUtils component shall be:
> Eric Pugh
> Henning P. Schmiedehausen
> Martin Poeschl
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [VOTE] Promote Configuration to Commons Proper
Posted by "Noel J. Bergman" <no...@devtech.com>.
Eric Pugh wrote:
[... a good list of reasons to move Configuration to Commons ...]
+1
> The initial committers on the DBUtils component shall be:
^
|
???
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org