Looks like something like this will actually work (so inline profiles
can override distributionManagement):
<distributionManagement>
<!-- Null out inherited apache distribution repo by default -->
<repository>
<id>dummy</id>
<name>Dummy to avoid accidental deploys</name>
<url></url>
</repository>
</distributionManagement>
<profiles>
<profile>
<id>release</id>
<distributionManagement>
<repository>
<!-- Activate apache distribution repo -->
<id>apache.releases</id>
<name>Apache Release Distribution Repository</name>
<url>scp://people.apache.org...m2-ibiblio-rsync-repository</url>
</repository>
</distributionManagement>
</profile>
</profiles>
I checked this locally and using mvn help:effective-pom. If I add the
above to the commons-parent, then "mvn -Prelease deploy" will work to
deploy and "mvn deploy" will fail if the version is not a snap and it
is trying to deploy to the rsynched repo. This is a little awkward
and it requires that we maintain the rsynch url in the commons POM,
but it does protect against accidental deploys. Any better ideas?
I have thought about adding a check to the nightly script to grep out
the version and fail the deploy if it is not a snapshot, but that does
not protect us from other "accidents." So unless someone has a better
idea, I am inclined to make the change above to the commons-parent
POM.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
