On 7/19/07, Stephen Colebourne [EMAIL PROTECTED] wrote:
But surely, the problem is that maven will pull in collections.jar when
it pulls in beanutils.jar, which is unnecessary. Its big, unnecessary
dependencies like this that give commons a bad name.
Do you know, that you can exclude
Henri Yandell wrote:
On 7/17/07, Niall Pemberton [EMAIL PROTECTED] wrote:
Assemblies work except you only get a default manifest - not sure
where I got the attachment idea from, can't find any reference to that
- so I think we should keep it simple and stick to option #1
That has my +1
On 7/19/07, Stephen Colebourne [EMAIL PROTECTED] wrote:
Henri Yandell wrote:
On 7/17/07, Niall Pemberton [EMAIL PROTECTED] wrote:
Assemblies work except you only get a default manifest - not sure
where I got the attachment idea from, can't find any reference to that
- so I think we should
On 7/18/07, Henri Yandell [EMAIL PROTECTED] wrote:
On 7/17/07, Niall Pemberton [EMAIL PROTECTED] wrote:
On 7/17/07, Niall Pemberton [EMAIL PROTECTED] wrote:
On 7/17/07, Henri Yandell [EMAIL PROTECTED] wrote:
My view is that we have the following options:
1) Merge em back in and just
On 7/14/07, Stephen Colebourne [EMAIL PROTECTED] wrote:
Henri Yandell wrote:
One area for discussion is the split between the optional Collections
component and the 'Core' beanutils. Do we maintain that, or should we
just fold the code back together?
1.7.0 shipped three versions:
On 7/11/07, Niall Pemberton [EMAIL PROTECTED] wrote:
BeanUtils is getting close to being ready for a 1.8.0 release IMO
(under 10 issues left targeted for 1.8.0).
http://issues.apache.org/jira/browse/BEANUTILS
One thought I had was to do a 1.8.0 Beta release first to (hopefully)
get wider
On 7/17/07, Henri Yandell [EMAIL PROTECTED] wrote:
On 7/11/07, Niall Pemberton [EMAIL PROTECTED] wrote:
BeanUtils is getting close to being ready for a 1.8.0 release IMO
(under 10 issues left targeted for 1.8.0).
http://issues.apache.org/jira/browse/BEANUTILS
One thought I had was to do
On 7/17/07, Henri Yandell [EMAIL PROTECTED] wrote:
On 7/14/07, Stephen Colebourne [EMAIL PROTECTED] wrote:
Henri Yandell wrote:
One area for discussion is the split between the optional Collections
component and the 'Core' beanutils. Do we maintain that, or should we
just fold the code
On 7/17/07, Niall Pemberton [EMAIL PROTECTED] wrote:
On 7/17/07, Henri Yandell [EMAIL PROTECTED] wrote:
On 7/14/07, Stephen Colebourne [EMAIL PROTECTED] wrote:
Henri Yandell wrote:
One area for discussion is the split between the optional Collections
component and the 'Core' beanutils.
On 7/17/07, Niall Pemberton [EMAIL PROTECTED] wrote:
On 7/17/07, Niall Pemberton [EMAIL PROTECTED] wrote:
On 7/17/07, Henri Yandell [EMAIL PROTECTED] wrote:
My view is that we have the following options:
1) Merge em back in and just release the 1 jar.
2) Split them; do not release a
One area for discussion is the split between the optional Collections
component and the 'Core' beanutils. Do we maintain that, or should we
just fold the code back together?
1.7.0 shipped three versions:
commons-beanutils-1.7.0.jar
commons-beanutils-core-1.7.0.jar
Henri Yandell wrote:
One area for discussion is the split between the optional Collections
component and the 'Core' beanutils. Do we maintain that, or should we
just fold the code back together?
1.7.0 shipped three versions:
commons-beanutils-1.7.0.jar
commons-beanutils-core-1.7.0.jar
I've always found it interesting there is a commons-beanutils and
common-beanutils-core deliverable. The name doesn't suggest what makes
the first one different. Usually the core artifact is foundational
(like tapestry-core or struts-core). If it is an API package, I would
add api to the end
Niall Pemberton wrote:
BeanUtils is getting close to being ready for a 1.8.0 release IMO
(under 10 issues left targeted for 1.8.0).
http://issues.apache.org/jira/browse/BEANUTILS
One thought I had was to do a 1.8.0 Beta release first to (hopefully)
get wider testing - thoughts/opinions on
On 7/14/07, Stephen Colebourne [EMAIL PROTECTED] wrote:
Henri Yandell wrote:
One area for discussion is the split between the optional Collections
component and the 'Core' beanutils. Do we maintain that, or should we
just fold the code back together?
1.7.0 shipped three versions:
On 7/14/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
Niall Pemberton wrote:
BeanUtils is getting close to being ready for a 1.8.0 release IMO
(under 10 issues left targeted for 1.8.0).
http://issues.apache.org/jira/browse/BEANUTILS
One thought I had was to do a 1.8.0 Beta release first to
If I understood Henri correctly, his proposal is to distribute one artifact
with optional collection dependencies. True? If so, I am for it. I don't see
any technical advantage in creating collection-free or collection-only jars.
On 7/14/07, Niall Pemberton [EMAIL PROTECTED] wrote:
On 7/14/07,
On 7/14/07, Paul Benedict [EMAIL PROTECTED] wrote:
If I understood Henri correctly, his proposal is to distribute one artifact
with optional collection dependencies. True? If so, I am for it. I don't see
any technical advantage in creating collection-free or collection-only jars.
I was around
On 7/14/07, Niall Pemberton [EMAIL PROTECTED] wrote:
I was around (just) when 1.7.0 was released but I have no recollection
of the decisions made on packaging. I believe the bean-collections
related bean stuff came originally from commons collections - so I
presume this allows people to
BeanUtils is getting close to being ready for a 1.8.0 release IMO
(under 10 issues left targeted for 1.8.0).
http://issues.apache.org/jira/browse/BEANUTILS
One thought I had was to do a 1.8.0 Beta release first to (hopefully)
get wider testing - thoughts/opinions on that welcome.
Niall
On 7/12/07, Niall Pemberton [EMAIL PROTECTED] wrote:
BeanUtils is getting close to being ready for a 1.8.0 release IMO
(under 10 issues left targeted for 1.8.0).
http://issues.apache.org/jira/browse/BEANUTILS
snip/
Thanks for all the work!
One thought I had was to do a 1.8.0 Beta
Great job Niall. Kudos.
On 7/12/07, Rahul Akolkar [EMAIL PROTECTED] wrote:
On 7/12/07, Niall Pemberton [EMAIL PROTECTED] wrote:
BeanUtils is getting close to being ready for a 1.8.0 release IMO
(under 10 issues left targeted for 1.8.0).
http://issues.apache.org/jira/browse/BEANUTILS
22 matches
Mail list logo