On Wed, Nov 23, 2011 at 8:14 PM, Karl Pauls <karlpa...@gmail.com> wrote:
> On Wed, Nov 23, 2011 at 8:39 PM, Marcel Offermans
> <marcel.offerm...@luminis.nl> wrote:
>> +1, I think providing such a script is a good way to do it, it makes
>> checking and building the individual components a lot easier whilst still
>> maintaining the flexibility of being able to release any subset of
>> artifacts. I also agree that we should correct the oversight of not shipping
>> the pom.xml file as part of the source distribution for future releases.
>
> Yeah, again, that is just a configuration we have to set so that it
> not only generates the -sources.jar but also the -project.{zip,tar.gz}
> just like we do at felix. Without that (and there I totally agree with
> ant and sebb on this one), it sucks rocks as you have to massage the
> stuff quite a bit to get it to work and don't even have the tests,
> etc. :-(.
>
> I think having the -projects plus the two scripts are a good way to go
> (technically, its close to releasing the reactor pom - which would be
> even easier - but this way, we don't have to tag the trunk).
If having the reactor pom would be even easier then why not do that?
This isn't just about making it possible for reviewers to easily build
the release when voting its about having a source release that you can
actually use to do development on the code. If you don't release the
recator pom then for example how do you set up the source in a IDE -
you'd have to manually go into each artifact any type something like
mvn eclipse:eclipse, and even then that would give isolated eclipse
projects so IDE refactoring wouldn't go across the projects and IDE
changes in one project wouldn't be picked up until after a maven build
was done and the projects refreshed, so really not a very practical
approach.
...ant
