Xavier Hanin wrote:
Hi,
I think we are not too far to be able to make a first attempt at releasing
2.0 alpha 1.
My last questions are for some minor things I'm still wondering about:
- I'd like to rename the CHANGES.txt file to CHANGES. Indeed, it's the only
root documentaiton file with a .txt extension. Maarten, any objection?
- shall we put this release on the maven 2 repository, and in this case,
what do we need to do?
+1, though they prefer not to have alpha cuts on the public repository.
Ask on [EMAIL PROTECTED] for the details of publishing to the snapshot
repository
I think making Ivy available on maven 2 repository would be a good sign of
our integration, and would also help users who depend on Ivy as an external
dependency. This last point is not critical for this release, since it's
oly
an alpha release, the API is still subject to change. So, I'm not sure
if we
should release this version on maven 2 repo... I'd really like to make this
release soon, and there would be work to do to provide the release on maven
2 repository. But on the other hand, we need to provide an http accessible
ivy jar, at least to update go-ivy example and ivy build itself, and it
would be nice to use maven 2 repo for that. Any suggestion?
The maven/repo people have quite a strict process for getting apache
artifacts up there; its intended to be secure and stop early releases
accidentally making it out. There is a snapshot repo for interim stuff.
regarding the POM: go write one. Have a look at how we do it in Ant,
where we have template poms with ${something.version} variables
inside...we <copy> these with an <expandproperties> filter to get all
the values expanded.
Because we aren't using the POMs for building, only downstream
dependencies, we keep the dependency list to the minimum needed to use
the things, not to build and test them.
-steve
