On Thu, Mar 26, 2009 at 11:45 PM, Todd Volkert <[email protected]> wrote:
> 1) I understand that the release archive must contain the word
> "apache" in the filename.  What about the JAR files contained within
> the archive?  For example, is "pivot-core.jar" ok, or does it have to
> be "pache-pivot-core.jar"?

Strongly recommended for trademark reasons. With Apache in the name,
we don't risk of intruding on other people's trademarks in the
software field.

> 2) Same question as above, but with the word "incubating".  Is it ok
> if our jar looks like "[apache-]pivot-wtk.jar", or must it be
> "[apache-]pivot-wtk_incubating.jar"?

Incubating MUST be part of the file names.

> 3) We'd like to keep version numbers out of our JAR files, but I see
> that it's common practice to include version numbers in JAR files.  Is
> there a really compelling reason to include the version numbers?  For
> example, we'd like to use "pivot-core.jar" vs. "pivot-core-1.1.jar".

Versions MUST be part of the tarball, which is the actual release.
If you also publish Maven artifacts, Maven will require the version to
be part of the name, and you will get a great deal of assistance from
Maven to manage that, so jars inside your tarball is a no-brainer.
With Ant is a bit more tedious to set it up, but not really a big deal
either. I recommend the version in all jars, for the sake of long-term
sanity of downstream users.

> 4) Must each JAR file contained in the release archive contain a
> LICENSE and NOTICE file, even if our release archive itself contains
> these files?

Only a MUST if the Jar files are published through the Maven
repository system. But it is highly recommended that it is done
anyway, because it is likely that someone else will publish your Jars
via Maven.

Also, don't forget DISCLAIMER file. That is part of Incubator and not
Apache per se, hence missing in your references cited.


And Yes, I agree that it is a pain to do releases...

Cheers
Niclas
-- 
http://www.qi4j.org - New Energy for Java

Reply via email to