[ 
https://issues.apache.org/jira/browse/UIMA-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484268#comment-13484268
 ] 

Peter Klügl commented on UIMA-2475:
-----------------------------------

I created and tested the composite repository now (win64bit). It works, but we 
will have to think carefully about how this influences our current build 
process and the historical versions of the features.

The actual update site we build in future then only contains the features of 
one release. However, we have to build the composite repository for all 
releases of the updatesites. I think this will be possible by only providing 
the features in the build process (I'm not sure). The result (updated composite 
repo and new updatesite) could then be copied to the server.

Some comments:
- the child repository currently still contains all features (like our update 
site right now).
- the composite repository provides no categories yet. I have searched, but 
have not found a good solution to provide/generate this information in our 
build process.
- when I tested the updatesites, the composite repository was much faster then 
the updatesite of the release. Maybe there is still some optimization missing.
- I have not yet tested the updatesite for p2 compliance.
- I have not found a straightforward solution to generate the composite 
repository with our maven build. Right now, maven calls (in an ant task) an ant 
runner in an osgi environment which executes an ant build script with 
properties defined in the pom.

My next step would be to adapt the build process in order to provide an update 
site for each release. Marshall, what is the best way to discuss my changes of 
the pom? Should I attach a patch? I do not like to commit unstable stuff.


                
> 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
>
> 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

Reply via email to