<unsolicited build advice>
I glanced over the pom and have a couple comments:
1. After a lot of discussion on legal discuss the appropriate contents
of LICENSE and NOTICE files is to include only wording that applies to
what is actually in the jars. This is encoded in apache-jar-resource-
bundle-1.4.jar (you use 1.2). In particular unless you are including
the junit jar in one of the generated jars the extra comment is
unnecessary and wrong. The 1.4 resource bundle also generates a
DEPENDENCIES file that lists all the jar's dependencies: this is
purely for user's possible convenience.
2. I recommend listing the plugins in a pluginManagement section and
leaving out the versions in the build and report sections.
3. I strongly recommend setting up a release profile and using the
release plugin. I did this in geronimo and a couple other projects.
The latest is the activemq release profile
https://svn.apache.org/repos/asf/activemq/trunk/pom.xml
This profile does the build, including source and javadoc jars, signs
everything, and uploads to a staging area typically on
people.apache.org. It requires some settings in your settings.xml
file, see intstructions at http://cwiki.apache.org/GMOxPMGT/geronimo-release-process.html
4. The scm info appears to be missing. That makes it really hard for
people to find where the project lives given the pom.
</unsolicited build advice>
thanks
david jencks
On Jun 16, 2008, at 2:00 PM, Robert Burrell Donkin wrote:
On Mon, Jun 16, 2008 at 1:34 PM, Stefano Bagnara <[EMAIL PROTECTED]>
wrote:
Stefano Bagnara ha scritto:
So, back on topic: is there anything else to be done before trying
a 0.2
release for jSieve ?
To help the process I ran "mvn package site" for jsieve and here is
the
output
Packages:
http://people.apache.org/~bago/jsieve/
Site:
http://people.apache.org/~bago/jsieve/site/index.html
I used maven because Norman said we will act as release manager and
he will
use maven: if you are against the use of maven to release jsieve
please
speak now, before people waste more time on details and release
process.
i'm happy
I noticed that the "News" item was incomplete, so I already
committed the
version with the release news (I didn't regenerate the test site
for this
minor issue)
IMO it is ready for a real tag/build/vote process, but maybe you see
something more before Norman will start his work.
i'm happy
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
