[
https://issues.apache.org/jira/browse/UIMA-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-3248.
----------------------------------
Resolution: Fixed
Assignee: Marshall Schor
> building Eclipse Update SItes - use better method for release
> -------------------------------------------------------------
>
> Key: UIMA-3248
> URL: https://issues.apache.org/jira/browse/UIMA-3248
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Affects Versions: parent-pom-6
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: parent-pom-7
>
>
> The current build for an Eclipse release achieves "safety" (from accidentally
> promoting a release before it's ready) by doing 2 distr.apache.org..../dev/
> commits: one to delete the current copy of the update-site, the other to
> "copy" the current update site to the /dev/ spot.
> I tried an improved method having 0 commits, which uses "switch" - checkout
> from ...release and then a local switch to ...dev. However that didn't work,
> see the question and response
> here:
> http://markmail.org/thread/xcpyyezj6ourgbez#query:+page:1+mid:2eqyo3xmxldy2uoi+state:results
> So I'm changing this to remove the "safety". This means the update site
> build, when done with -Papache-release (which is applied either by the mvn
> user or by the mvn release:... plugin), will svn checkout into the target
> spot for the eclipse update subsite, the existing update subsite, from
> ...Release.
> Which means, that after the new site has been built, and the release vote has
> passed, you can commit the changes right back to the ...release spot.
> If by accident you commit before you want to, you can always manually fix
> this by reverting that commit. So it doesn't have too much downside - the
> real downside is that SVN hook on commits which launching "mirroring" of the
> changes the 100's of sites mirroring the Apache distribution.
> The update site, when done without -Papache-release, does no svn checkout
> from the .../release update site. Your "test" update site will be OK, but
> will be missing previous releases. If you need the previous releases, run
> with the -Papache-release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira