[
https://issues.apache.org/jira/browse/UIMA-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-2970.
----------------------------------
Resolution: Fixed
Fix Version/s: parent-pom-5
2.4.1SDK
To use for building an Eclipse update subsite, you need to do the following in
the update site project:
* add a file "marker-file-identifying-eclipse-update-site" at the top level
* add propertyies
* <eclipseUpdateSiteComponent>SUBSITE-NAME</eclipseUpdateSiteComponent>
*
<eclipseUpdateSubSite>${project.build.directory}/eclipse-update-site/${eclipseUpdateSiteComponent}</eclipseUpdateSubSite>
* if you category.xml wants to use the update site project's version for its
version, put it in src/main/resources/category.xml - that will be filtered to
the top level allowing substituting the project's version.
* The POM's build step needs to have one plugin: the dependency plugin,
configured to copy just the versions being added to the update site of the
plugins and features for the update site. (Old versions are not included in
this configuration). This is typically set up once, using maven properties for
the project.version, allowing this to be substituted from the update project's
version.
You can run this with -Papache-release if you want the checksums and gpg
signatures to be done. See the uimaj/uimaj-eclipse-update-site project for an
example.
The output will be in target/eclipse-update-site/subsite, and the files will be
ready for svn checkin to the dist.apache.org .../dev/... site. (In Eclipse,
you can multi-select all the files / folders and say "commit").
After a vote passes, you can multi-select the files/folders in Eclipse and use
"switch" to change to the .../release/... spot, and when you commit, the new
and changed files will be committed to the release spot.
Any older versions of features and plugins won't be changed. The only altered
files are the content.jar and artifacts.jar (and their checksums/signatures);
these are "appended" by the build process to add the new version being released.
> Improve release of Eclipse Update sub-sites
> -------------------------------------------
>
> Key: UIMA-2970
> URL: https://issues.apache.org/jira/browse/UIMA-2970
> Project: UIMA
> Issue Type: Improvement
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 2.4.1SDK, parent-pom-5
>
>
> Take advantage of the existence of the Apache dist.apache.org SVN site used
> for releases to reduce the release work for new versions of existing update
> subsites.
> A subsite is typically a collection of features and plugins, at various
> "versions", plus metadata that catalogs these items in two files:
> contents.jar and artifacts.jar. The subsite also has pack.gz versions of the
> plugin Jars, and checksums and signatures for the Jars and pack.gz things.
> With each new version, the old versions of the features and plugins do not
> change; just new versions are added and the metadata files are updated; all
> new and changed files get new checksums/signatures.
> Change the build process to:
> a) checkout the existing subsite
> b) build just the new versions
> c) compute the new metadata and use the "append" facility to add to the
> existing metadata
> d) allow "committing" just the new/changed files to the dist repo after the
> vote passes.
> Since the update site build process no longer has any need of information
> about previous versions, change the update-site organization and POM to have
> less special updates needed (previously, it needed lists of previous
> versions, etc), and make it align with the conventional way other projects
> are built, where possible.
> Make the category.xml a filtered file - substituting the "version" from the
> POM instead of hard-coding it.
> Incorporate checksums and signings into the normal mvn build process, under
> the apache-release profile (so other builders don't need to do this part).
> Add the common part of all update subsite building to the uima-wide parent
> pom; activate by having a file named
> "marker-file-identifying-eclipse-update-site"
--
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
