[
https://issues.apache.org/jira/browse/UIMA-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500227#comment-13500227
]
Peter Klügl commented on UIMA-2475:
-----------------------------------
Sorry for the late response.
about 1)
I totally agree with you on the matter of binaries in SVN, but building
something each time for all different versions is neither a good/clean solution
in my opinion. Maybe we find a better solution in future :-)
about 2)
+1, good idea
Just another comment about the composite repository: With this approach, we can
also easily separate the bundles with different release cycles, e.g., uima-as
could get its own update site. I am also thinking of the TextMarker update
site, of course.
The future layout of the repository could look something like:
composite repository
- legacy
- uima-{version}
- uima-as-{version}
- ... other stuff like uima-textmarker-{version}
A single update site project like uimaj-eclipse-update-site (for
uima-{version}) would then only build the current version and could copy and
add itself to the composite repository in the packagings project during the
"deploy" phase.
So, how to proceed from here? Are there any objections about the general
layout/structure? Would it be ok to double release the bundles, to add a child
p2 repository for the 2.4.0 release respectively, or do we have to wait for the
next release?
> eclipse p2 update site instead of old-style update site
> -------------------------------------------------------
>
> Key: UIMA-2475
> URL: https://issues.apache.org/jira/browse/UIMA-2475
> Project: UIMA
> Issue Type: Bug
> Components: Eclipse plugins
> Reporter: Steven Bethard
> Assignee: Peter Klügl
> Attachments: uimaj-eclipse-update-site.zip
>
>
> The UIMA Eclipse update site (www.apache.org/dist/uima/eclipse-update-site)
> is an Eclipse 3.3 (or older) update site. Since Eclipse 3.4, the recommended
> update site layout is p2:
> http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Releng#Why_should_I_make_changes_to_adopt_p2.3F
> I've been bitten by this update site issue because old-style update sites
> make it impossible to resolve build-time dependencies when building Eclipse
> plugins:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=380438#c3
> Could the UIMA update site be modernized to the p2 layout?
--
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
