robert burrell donkin wrote:
AFAICT the maven build for jsdf and mime4j hits the local filesystem
only and not any ASF servers. opinions differ about whether storing
artifacts in the repository is a good idea but james does so i see no
reasons for infrastructure to object to this arrangement.
Actually we touch ASF servers: in our james-project (parent pom) we
define this repositories:
<repository>
<id>central</id>
<name>Apache Main M2 Repository</name>
<url>http://people.apache.org/repo/m2-ibiblio-rsync-repository</url>
<releases><enabled>true</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</repository>
<repository>
<id>central-m1</id>
<name>Apache Main M1 Repository</name>
<url>http://people.apache.org/repo/m1-ibiblio-rsync-repository</url>
<layout>legacy</layout>
<releases><enabled>true</enabled></releases>
<snapshots><enabled>true</enabled></snapshots>
</repository>
<repository>
<id>apache.snapshots</id>
<name>Apache Snapshot Repository</name>
<url>http://people.apache.org/repo/m2-snapshot-repository</url>
<releases><enabled>false</enabled></releases>
</repository>
Then in the jspf pom we add:
<repository>
<id>local-jspf-3rd-party-m1</id>
<name>Local jSPF third party repository</name>
<url>file://${basedir}/repos/third-party-m1</url>
<layout>legacy</layout>
<releases>
<enabled>true</enabled>
<checksumPolicy>ignore</checksumPolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<checksumPolicy>ignore</checksumPolicy>
</snapshots>
</repository>
Then we put every 3rd party jar (license compatible) that is not already
published in one of the offial ASF repository in the local
${basedir}/repos/third-party-m1 folder (folder that is part of the
checkout).
This mean that after you checked out the source tree for jspf it will do
these things:
1) retrieve org.apache.james:james-project:1.1-SNAPSHOT from
http://people.apache.org/repo/m2-snapshot-repository
2) retrieve any other ASF dependency from the 3 defined ASF repositories
(m1/m2 ibibio-rsync and m2 snapshot)
3) retrieve any missing *m2* *plugin* from ibiblio
4) copy 3rd party jars from the ${basedir}/repos/third-party-m1 to the
user repository.
We could fix 3 to not use ibiblio by adding all of the plugins used by
maven to build jspf to the repos/third-party-m1 but I'm not sure this
would be good because every project would start to add all of the maven
plugins in their own trees. We should wait for the ASF solution to this
issue, but only if this temporary solution allow us to make a release.
BTW using minotaur.apache.org in a pom is not recommended. please use
an appropriate virtual host (for example people.apache.org).
- robert
I use minotaur for the distribution management: in fact we are not using
that part now because we don't use site deployment by maven. Btw I can
fix it: what alias should I use for the server that keep the main
website copy? is people.apache.org the best choice or anything else?
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
