I'm mystified too. Other reactor poms work fine like this. david jencks
On Jul 6, 2012, at 1:20 PM, Holly Cummins wrote: > Hi Jeremy, > > I noticed the tagging oddness as well and mentioned it on the > discussion thread for the original vote. My feeling was that it was > better to go with what was produced by the release plugin than try and > play around with the tags, since it's an issue which only affects > util. I assumed it was just a function of util being a reactor pom. > I've checked the scm elements in the util pom, and they seem correct. > > Cheers, > Holly > > On Fri, Jul 6, 2012 at 5:39 PM, Jeremy Hughes <[email protected]> wrote: >> Things still feel a bit odd in Util. The release is for >> org.apache.aries.util-parent 1.0.0 (when we released 0.4 it was >> org.apache.aries.util but then I know we've changed util to be a multi >> module project). >> >> But, the tag for the release which is: >> >> https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.util-parent-1.0.0/ >> >> contains an entire copy of trunk. It seems the release plugin did the >> commit, but the util/pom.xml seems ok - it points to >> http://svn.apache.org/repos/asf/aries/tags/org.apache.aries.util-parent-1.0.0/util >> >> The source for the bundle is in a different artifactId to the binary, >> but I can live with that I guess. Before we go changing anything, can >> anyone explain why Maven is tagging the entire trunk for this? >> >> Thanks, >> Jeremy >> >> On 5 July 2012 22:20, Holly Cummins <[email protected]> wrote: >>> I've staged a second release candidate for the Aries 1.0.0 util and >>> blueprint.api bundles. The difference between this candidate and the >>> first candidate is that the javadoc for the org.apache.aries.util >>> bundle documents *all* the classes in that bundle, rather than just >>> the ones in the util/util project. >>> >>> The modules are staged and tagged in >>> >>> https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.util-parent-1.0.0/ >>> https://svn.apache.org/repos/asf/aries/tags/org.apache.aries.blueprint.api-1.0.0/ >>> >>> Instructions for verifying the release are at >>> http://aries.apache.org/development/verifyingrelease.html. >>> Alternately, cut and paste the following to run a full check: >>> >>> wget --no-check-certificate >>> https://svn.apache.org/repos/asf/aries/scripts/verify_staged_release.sh >>> chmod a+x verify_staged_release.sh >>> ./verify_staged_release.sh 032 mytempdirectory 2>&1 | tee verifyresults.txt >>> grep FAIL verifyresults.txt >>> grep ERROR verifyresults.txt >>> >>> Failures are reported since there are no SHAs for the >>> archetype-catalog.xml file in the repository, but I believe this is >>> acceptable (and I can update the script to filter these out if >>> everyone else agrees). >>> >>> Artifacts are in one staged >>> repo,https://repository.apache.org/content/repositories/orgapachearies-032/. >>> >>> Links to the *.zip files for each module are provided below. >>> >>> https://repository.apache.org/content/repositories/orgapachearies-032/org/apache/aries/blueprint/org.apache.aries.blueprint.api/1.0.0/org.apache.aries.blueprint.api-1.0.0-source-release.zip >>> https://repository.apache.org/content/repositories/orgapachearies-032/org/apache/aries/org.apache.aries.util-parent/1.0.0/org.apache.aries.util-parent-1.0.0-source-release.zip >>> >>> The RAT and IANAL build checks passed. >>> >>> The vote will be open for 72 hours. >>> >>> [ ] +1 >>> [ ] 0 >>> [ ] -1
