[
https://issues.apache.org/jira/browse/UIMA-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504578#comment-13504578
]
Peter Klügl commented on UIMA-2475:
-----------------------------------
I updated the legacy update site now and hope that I have not forgot anything.
I don't have the rights to access the published update site directly, as far as
I know, so I crawled it.
The signing and the categories of the new p2 repository are still missing. I
think it should be signed just before it is copied to the server. About the
categories: I have to read a bit more to find/weigh possible solutions.
What are the next steps? Can someone test the update site for different
configurations (OS)? Seems to work for Win7 64bit.
> 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