OK, let's see.
The composite update site builder hasn't been updated in a bit, and is doing the
old-style dist... /release/dev/ svn manipulations; this will cause 2 svn commits
to the .../dev/... spot when you run.
It is probably best if I fix this to follow what the (new) main parent pom does
for non-componsite update sites (where we no longer do these svn manipulations.)
I think you did the proper preparation.
I'm guessing that you don't want to run this, however, until *after* the new
subsite is out there. I think the Eclipse build *might* read some data from the
subsites.
There's a pending VOTE on releasing the uima-build-helper-plugin, which when
done, will enable the update / release of the parent-pom, which, when done,
might have a common fix for part of the Eclipse Update Site generation (common
among both the subsite generation and the composite site generation). Note that
this last bit isn't yet done...
So, preferred order for maximum reuse :-):
- Vote on uima-build-helper-maven-plugin
- Update parent-pom to reference v 7 of uima-build-helper-maven-plugin
- Update parent-pom (as needed) to have common factored out part of
Eclipse Update Site, for both composite site and subsite
- Vote / Release parent-pom
- Update uima-eclipse-composite-update-site to use new parent-pom, and remove
redundant
or out-of-date build steps
- Release Ruta next version with eclipse subsite
- build/test composite update site; if OK, release
-Marshall
On 9/11/2013 12:48 PM, Peter Klügl wrote:
> I have read http://uima.apache.org/eclipse-update-site.html , but the
> process is yet not completely clear to me.
>
> Marshall, can you give me a hint before I do something stupid?
>
> I changed the version number of the composite repository and added a new
> subsite in the build script.
>
> Should I now mvn clean install -Papache-release on the composite
> repository project? And then mvn clean install -Papache-release on my
> update site project? Or vise versa?
>
> Sorry, I am a bit slow on the uptake...
>
> Peter
>