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

Marshall Schor commented on UIMA-1865:
--------------------------------------

I noticed that the uimaj-ep-cas-editor doesn't have an issue with this problem. 
 Investigating further (using mvn dependency:tree ) that it refers to different 
eclipse artifacts.

For instance, a common artifact that was having issues with the other plugins 
was the core runtime.

In the CasEditor:  
this is referred to using org.eclipse.core:runtime and gets version 
3.3.100-v20070530

In the Cde,
this is referred to using org.eclipse.core:org.eclipse.core.runtime and gets 
version 3.2.0

In the maven central repo (located: http://repo1.maven.org/maven2/)  under 
org/eclipse/core, there is both a
runtime/ and a org.eclipse.core.runtime/ (this latter one is the corrupt 
version)

In the other repo for eclipse components (located: 
http://repo1.maven.org/eclipse/) there is both a 
runtime/ and an org.eclipse.core.runtime/

Don't know what to make of all this...  except without locking things down, a 
future corrupted upload to maven central can break things...

> lock down transitive dependency version for Eclipse components
> --------------------------------------------------------------
>
>                 Key: UIMA-1865
>                 URL: https://issues.apache.org/jira/browse/UIMA-1865
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Build, Packaging and Test, Eclipse plugins
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>
> Someone uploaded corrupted versions of Eclipse 3.6 artifacts to maven central 
> today, and it broke our builds for things like eclipse plugins, which 
> transitively reference artifacts which are being resolved to the corrupted 
> versions.
> To work around this and prevent this in the future, lock down all the 
> transitive dependencies (or at least the ones affected now), to versions 
> which "work".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to