+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" <[EMAIL PROTECTED]>
To: "Commons-Dev (E-mail)" <[EMAIL PROTECTED]>
Sent: Wednesday, December 17, 2003 10:04 AM
omething 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:[EMAIL PROTECTED]
Sent: Thursday, December 18, 2003 11:28 AM
To: Jakarta Commons Developers List
anged
post whatever the copyright date is, then updates it...
Eric
-Original Message-
From: Emmanuel Bourg [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 18, 2003 11:28 AM
To: Jakarta Commons Developers List
Subject: Re: [VOTE] Promote Configuration to Commons Proper
r
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
Eric Pugh wrote:
[... a good list of reasons to move Configuration to Commons ...]
+1
> The initial committers on the DBUtils component shall be:
^
|
???
--- Noel
--
+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 versi
It says 'DBUtils' at the bottom of the proposal :)
That said, I'm in favour of promotion. +1
Hen
On Wed, 17 Dec 2003, Shapira, Yoav wrote:
>
> Hi,
> I wouldn't call it mature yet, but it meets the criteria for promotion
> IMHO. BTW, sorry for not contributing more, but I do plan to use it at
+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 pr
