UIMA
  1. UIMA
  2. UIMA-1768

bundle build failing for cas editor due to maybe wrong eclipse dependency

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.3
    • Fix Version/s: 2.3.1SDK
    • Labels:
      None

      Description

      When I build using my m2eclipse environment, I get a report that the dependency for
      <groupId>org.eclipse.swt</groupId>
      <artifactId>org.eclipse.swt.win32.win32.x86</artifactId>

      and

      <groupId>org.eclipse.ui</groupId>
      <artifactId>views</artifactId>

      both of which specify version

      <version>[3.3.0.0,4.0.0)</version>

      can't be resolved, because there isn't any version that matches in the repositories. If I change the lower bound to 3.2.0 - it works.

      The eclipse stuff seems to be in the

      repo1.maven.org/eclipse/org/eclipse ... etc. and if you look there, there are only the 3.2.0 and 3.2.1 versions, which is why changing this to 3.2.0 as the lower bound makes it work.

      Is this ok to change?

        Activity

        Hide
        Marshall Schor added a comment -

        It turns out that maven 2.2.1 had a behavior that ended up not reporting a version mismatch, but maven 3 changed that and now reports an error.

        Some experiments:

        Using the [3.3.0.0 minimum version for these dependencies (which isn't available in the repos):

        using maven 2.2.1: deleting the .m2 eclipse repo, and running mvn dependency:tree on the cas editor:

        • causes the 3.2.1 version to be downloaded, and shown in the dependency tree with no error shown. Of course, this should be an error, because the POM was saying the minimum version level was 3.3.0.0

        Switching to maven 3, and redoing, gives this error:

        [ERROR] Failed to execute goal on project uimaj-ep-cas-editor: Couldn't find a version in [3.2.0, 3.2.1] to match range [3.3.0.0,4.0.0)
          org.eclipse.swt:org.eclipse.swt.win32.win32.x86:jar:null
        
        from the specified remote repositories:
          eclipsePlugins (http://repo1.maven.org/eclipse, releases=true, snapshots=false),
          central (http://repo1.maven.org/maven2, releases=true, snapshots=false),
          apache.snapshots (http://repository.apache.org/snapshots, releases=false, snapshots=true)
        
        Show
        Marshall Schor added a comment - It turns out that maven 2.2.1 had a behavior that ended up not reporting a version mismatch, but maven 3 changed that and now reports an error. Some experiments: Using the [3.3.0.0 minimum version for these dependencies (which isn't available in the repos): using maven 2.2.1: deleting the .m2 eclipse repo, and running mvn dependency:tree on the cas editor: causes the 3.2.1 version to be downloaded, and shown in the dependency tree with no error shown. Of course, this should be an error, because the POM was saying the minimum version level was 3.3.0.0 Switching to maven 3, and redoing, gives this error: [ERROR] Failed to execute goal on project uimaj-ep-cas-editor: Couldn't find a version in [3.2.0, 3.2.1] to match range [3.3.0.0,4.0.0) org.eclipse.swt:org.eclipse.swt.win32.win32.x86:jar:null from the specified remote repositories: eclipsePlugins (http://repo1.maven.org/eclipse, releases=true, snapshots=false), central (http://repo1.maven.org/maven2, releases=true, snapshots=false), apache.snapshots (http://repository.apache.org/snapshots, releases=false, snapshots=true)
        Hide
        Joern Kottmann added a comment -

        I think the change is fine, as long as it still compiles. The eclipse OSGi runtime will make sure that the correct version is used when the plugin is deployed.

        Show
        Joern Kottmann added a comment - I think the change is fine, as long as it still compiles. The eclipse OSGi runtime will make sure that the correct version is used when the plugin is deployed.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development