the difference between these:
(looking at uima v2)
The uimaj-eclipse-update-site could have used the common build pom for the step
"BuildUpdateSite-pack-svnget-buildMetadata-commit-to-dev"
except for one "improvement", which was done after the uima-wide pom release 12
happened.
This is the bit that tests dropPrevVersions:
line 153: <equals arg1="${dropPrevVersions}" arg2="false" />
It allows a programmatic way to skip checking out previous versions when you
want to "clean up" the eclipse update site for your project. For uima v3, this
was used to support a different update site for those plugins.
I'm guessing you won't need this, though.
You do need the rest of the config in the eclipse-update-site, of course, which
configures what features/plugins go into the site.
See also https://uima.apache.org/dev-eclipse-plugin-archiving
-Marshall
On 1/5/2019 11:38 AM, Peter Klügl wrote:
> Hi,
>
>
> I currently try to provide an RC for ruta and I try to think about the
> required changes to the maven build process of the update site. Taking a
> look at the uimaj-eclipse-update-site and the UIMA wide parent pom, is
> the configuration in the uimaj-eclipse-update-site really necessary, or
> did I miss something?
>
>
> Best,
>
>
> Peter
>
>
