Hi Benson
Benson Margulies wrote:
On Mon, Sep 12, 2011 at 3:07 AM, Paolo Castagna
<[email protected]> wrote:
Hi Benson,
first of all, thank you for your reply. I followed all of your suggestions [1].
A few comments inline.
Ditto.
Benson Margulies wrote:
the <scm/> element is wrong, it lacks 'trunk'.
No credentials in the maven-release-plugin, use settings.xml instead.
I did not put the credentials in the maven-release-plugin.
I was just pointing to two environment variables: ${env.SF_USERNAME}
and ${env.SF_PASSWORD}. I removed them.
Sorry, I was being brief. I understood what you did, I was just
passing along the usual alternative.
Why the special repo for non-snapshots? Aren't you planning to release
at Apache, too?
The special repo for non-snapshots is just for testing.
Yes, we are planning to release at Apache!
Planning... I'd like to test the maven-release-plugin on the Apache
infrastructure.
The way NexusPro works, you can do this without a custom repo. You
just go ahead and run the release plugin, and you drop the resulting
staging repo.
Good. I was not sure about this. Now it's clear.
This way we can test everything is working with the Apache infrastructure
without the need of a vote. When everything is fine, we can call a vote
on the artifacts in the staging repo.
It is still not clear to me if a multi-module project such as Jena
(which currently has Jena2, ARQ, LARQ, TDB, SDB, etc. modules) can
release just one single module publishing artifacts to the Apache
Maven repository.
You don't aggregate them. You release them one-at-a-time. If you
really want to release them all-at-once, give them a single TTB
structure and aggregate them. Or have one extra thing to release which
builds the release package out of all the others.
Ack
The binaries and sources to be released will probably contains all
the modules.
Modules might have different life-cycles.
Can I release the LARQ module, to test if everything works as expected
and we will release the rest of the modules and the Jena distribution
when they are ready?
See above. Plan to vote to release them one at a time, and then vote
to release a combined package. Or turn them into one branch structure.
I think you could delete the distributionManagement element altogether.
Done.
You shouldn't put that redundant outputDirectory in reporting.
Removed.
If you are going to use the maven-site-plugin, use version 3.0 and
specify the deployment location for it.
I don't think there are currently plans to use the maven-site-plugin.
Not for the site anyway.
However, it might be handy to publish Javadocs, etc.
Is it possible to use the maven-side-plugin to publish stuff into a
just a subdirectory of the website (the Jena project is using the Apache
CMS to manage the website)?
If you know a project using this "mixed" approach, could you please
point me at it?
I'd like to know the answer to this myself.
Thanks again.
Paolo
[1]
http://svn.apache.org/viewvc/incubator/jena/Jena2/LARQ/trunk/pom.xml?r1=1169616&r2=1169615&pathrev=1169616
