In this release, we're hoping to include some things from the sandbox.
Some of these are eclipse plugins (the uima-as Eclipse plugins).
We have a choice: have another Eclipse update site for these, or have
just one update Eclipse update site, with multiple "features" the user
can pick/install.
The 2nd approach seems much better to me. This would make the update
site more like the distribution site for Apache, or the maven
repositories - just another "packaging" that's convenient for
downloading Eclipse plugins related to the Apache UIMA project.
If we were to go to this approach, we would need the process which
computes the update site to do it for all the "features". This process
creates artifacts - 1 for each feature, and one for the overall update
site (listing all the features, at all the versions).
The running of the update site build would then be something done when
either the main UIMA was release, or when a sandbox project that had
artifacts on thie update site, was released.
Does this seem like the right approach, or is there another approach to
take?
-Marshall
- How to manage the uima Eclipse update site with respect t... Marshall Schor
-
