You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (Jira)" <de...@uima.apache.org> on 2021/03/17 14:15:00 UTC
[jira] [Updated] (UIMA-6341) Try out p2-layout-resolver
[ https://issues.apache.org/jira/browse/UIMA-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Eckart de Castilho updated UIMA-6341:
---------------------------------------------
Description:
Try out p2-layout-resolver for fetching Eclipse dependencies from P2 repositories.
Right now, we get the dependencies for our Eclipse plugins from Maven Central. This is a pain because every time that Eclipse issues a new release, they push new dependencies to Maven Central causing that the dependency ranges we have to resolve to different artifacts and the transitive dependencies of these new artifacts may not be on Maven Central.
If we drop the ranges, we either have to re-add them at a different level (i.e. when generating the Eclipse plugin descriptors) so that users can actually install our plugins in different versions of Eclipse.
The hope is that using the p2-layout-resolve we can:
* obtain the Eclipse artifacts from P2 repository - so we are not limited to what is available on Maven Central
* we can more easily bind to a particular Eclipse release by using the P2 repo of that release
* our builds do not break every few months when new Eclipse releases are pushed to Maven Central
was:
Try out p2-layout-resolver for fetching Eclipse dependencies from P2 repositories
> Try out p2-layout-resolver
> --------------------------
>
> Key: UIMA-6341
> URL: https://issues.apache.org/jira/browse/UIMA-6341
> Project: UIMA
> Issue Type: Improvement
> Components: Ruta
> Reporter: Richard Eckart de Castilho
> Assignee: Richard Eckart de Castilho
> Priority: Major
>
> Try out p2-layout-resolver for fetching Eclipse dependencies from P2 repositories.
> Right now, we get the dependencies for our Eclipse plugins from Maven Central. This is a pain because every time that Eclipse issues a new release, they push new dependencies to Maven Central causing that the dependency ranges we have to resolve to different artifacts and the transitive dependencies of these new artifacts may not be on Maven Central.
> If we drop the ranges, we either have to re-add them at a different level (i.e. when generating the Eclipse plugin descriptors) so that users can actually install our plugins in different versions of Eclipse.
> The hope is that using the p2-layout-resolve we can:
> * obtain the Eclipse artifacts from P2 repository - so we are not limited to what is available on Maven Central
> * we can more easily bind to a particular Eclipse release by using the P2 repo of that release
> * our builds do not break every few months when new Eclipse releases are pushed to Maven Central
--
This message was sent by Atlassian Jira
(v8.3.4#803005)