uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Klügl <pklu...@uni-wuerzburg.de>
Subject Re: [jira] [Commented] (UIMA-2475) eclipse p2 update site instead of old-style update site
Date Tue, 30 Oct 2012 12:43:03 GMT
Sorry, I won't be able to work on this issue at least for one week 
(health reasons). It has to wait or you could temporarly reassign it.

Peter

Am 26.10.2012 20:45, schrieb Steven Bethard (JIRA):
>      [ https://issues.apache.org/jira/browse/UIMA-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485107#comment-13485107
]
>
> Steven Bethard commented on UIMA-2475:
> --------------------------------------
>
> Well, for the old releases to be valid p2 repositories, yeah, you'd have to supply the
plugins. But I personally think it would be fine if you just made p2 repositories for the
newest versions. I certainly didn't need any of the old ones.
>
> As to the issue with the published update site, I wonder if you could:
>
> (1) Check the current published update site into SVN, say in a 'deploy/legacy' directory.
If possible, run FeaturesAndBundlesPublisher over this. (Though it might not help much since
it sounds like plugins were not properly deployed in the past.)
>
> (2) Use the process I described above to publish new plugins and features, adjusting
the -metadataRepository and -artifactRepository paths to 'deploy/2.4.0-whatever'
>
> (3) Update 'deploy/compositeContent.xml' and 'deploy/compositeArtifacts.xml' to make
sure they include all the sub-directories ('legacy', '2.4.0-whatever', etc.)
>
> (4) Just copy over the entire 'deploy' directory as the published update site.
>
> Would that work?
>                  
>> 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


Mime
View raw message