Community
Participate
Working Groups
The "org.eclipse.jubula.repo.zip" contains the org.eclipse.jdt.annotation plug-in in version 2.0.0. First, it should not be contained there at all and second, version 1.1.0 is required to satisfy the dependencies. MT, can you find out what the cause is?
First of all we had an unnecessary dependency within our feature to that bundle which has been removed with: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=5679cf2f3a9f112cad7d7c9f152212eba479c5be I've also extended the documentation a bit to name the feature that's required within the target platform (definition). I'm still not sure why this is included in version 2.0.0 - I've checked and found out that dependent JDT feature of us has a dependency to that bundle (in version 1.1.0) as explicitly excluding it from the repository leads to: ... [INFO] Resolving dependencies of MavenProject: org.eclipse.jubula:org.eclipse.jubula.repo:3.1.0-SNAPSHOT @ /projects/p21306/Workspace/users/MarkusTiede/repos/org.eclipse.jubula.core/org.eclipse.jubula.repo/pom.xml [exec] [INFO] {osgi.ws=win32, osgi.os=win32, osgi.arch=x86, org.eclipse.update.install.features=true} [exec] [ERROR] Cannot resolve project dependencies: [exec] [ERROR] Software being installed: org.eclipse.jubula.repo raw:3.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):3.1.0-SNAPSHOT [exec] [ERROR] Missing requirement: org.eclipse.jdt.feature.group 3.10.1.v20150204-1700 requires 'org.eclipse.jdt.annotation [1.1.0.v20140129-1625]' but it could not be found [exec] [ERROR] Cannot satisfy dependency: org.eclipse.jubula.feature.launch.java.feature.group 3.1.0.qualifier depends on: org.eclipse.jdt.feature.group 0.0.0 [exec] [ERROR] Cannot satisfy dependency: org.eclipse.jubula.repo raw:3.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):3.1.0-SNAPSHOT depends on: org.eclipse.jubula.feature.launch.java.feature.group [3.1.0,3.1.1) ... Could you please check whether it's now possible to define a dependency to the client API via a target platform definition?
Yes, the dependencies are now correctly resolved. What do we plan to do about the contained plug-in?
I'd like to analyse this in one of the upcoming sprints - I don't think this is critical / requires instant addressing now.
It is also included in mirroring during simrel build.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
