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 release the 1 jar.
> > > 2) Split them; do not release a beanutils.jar (or if we do, it's
> > > beanutils-core renamed) and setup beanutils-collections as a separate
> > > component in Commons or as a child of beanutils with core as an
> > > equivalent child (ie: Maven2 multiproject).
> >
> > I don't want to do a maven multi-project - but I also don't see whats
> > wrong with releasing the three jars as they were last time - as I said
> > eariler in this thread - merge in the bean-collections sub-project,
> > but use an assembly to re-create the core and bean-collections jars.
> > As attached artifacts then people would have the option to depend on
> > those if they so desired (as my understanding of maven goes).
>
> 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 [obviously]. I think we should keep it simple.
As the majority are in favour and with no-one vetoing this proposal -
I'll go ahead and do this later tonight. I created a Jira issue[1] to
document this (since they're far easier to find later down the road
than mailing list threads)
[1] https://issues.apache.org/jira/browse/BEANUTILS-290
Niall
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
