UIMA
  1. UIMA
  2. UIMA-1865

lock down transitive dependency version for Eclipse components

    Details

      Description

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

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Closed Closed
        50m 30s 1 Marshall Schor 07/Sep/10 21:34
        Marshall Schor made changes -
        Fix Version/s 2.3.1AS [ 12315335 ]
        Fix Version/s 2.3.1SDK [ 12315344 ]
        Marshall Schor made changes -
        Field Original Value New Value
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Hide
        Marshall Schor added a comment -

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

        Show
        Marshall Schor added a comment - 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...
        Marshall Schor created issue -

          People

          • Assignee:
            Marshall Schor
            Reporter:
            Marshall Schor
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development