ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée <>
Subject Re: [VOTE] IvyDE 2.0.0-final Release
Date Fri, 19 Jun 2009 15:37:06 GMT

On Fri, 19 Jun 2009 14:07:58 +0200, Stefan Bodewig <>
> On 2009-06-19, Stefan Bodewig <> wrote:
>> I'm collecting issues and will come back with a consolidated list
>> since I dont intend to play "fetch me a rock" with you,
> Things you should fix before I can vote in favor of a release (only
> easy to do things, but important legally):
> * create a tag in svn

Actually I was going to do one as soon as the release is accepted, just
like we always did for each release of both Ivy and IvyDE.
But I took time to re-read the ASF documentation about releasing, we
effectively should create tags.
Then I will also update Ivy and IvyDE release docs.

> * source zip needs NOTICE and LICENSE files in the root directory

I'll fix that

> * the binary zip needs NOTICE and LICENSE files in the root directory

I'll fix that

> * digest.xml in needs a license header, the whole zip needs
>   LICENSE and NOTICE files.

I'll fix that. I hope I can script this easily as both are generated by the
Eclipse builder.

> and a few questions:
> * source zip only contains a subset of files in
>   trunk (e.g. org.apache.ivyde.feature/LICENSE is not there, the
>   doc and test dirs are missing).
>   Why?

I tried to make a target that zip the sources while trying avoid embedding
the .class that have have been generate there and elsewhere. And I didn't
maintain it that well. We should switch to a much simpler packaging: a zip
of a svn export + NOTICE and LICENSE

> * are the .project and .classpath files in various places really
>   needed or should they be "svn ignore"d?

I think .project file are good to share, it makes import in Eclipse easier.
Having the .classpath make the Eclipse import straight forward, but it
depends more on the environment it is running into. IvyDE has a very simple
classpath so I don't think it is an issue.

> * The files in
>   would probably require license headers unless they can be ignored
>   anyway.

These settings are more usefull I think. It configures the code formatting
and the compiler in Eclipse. So people patching IvyDE will automatically
use the formatting we are using. I will add the headers.

> Sorry for being a pain

Don't be. And first, thank you for looking closely at it.

Actually while re-reading the ASF doc about releasing, it reminds me that
we don't publish the release notes other than into the jars. I will take
some time to have them published into the IvyDE documentation (it was a
TODO for some time now).


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message