Bug 547865 - EPP 2019-06 Jubula can not start because javax.xml.bind via two dependency chains
Summary: EPP 2019-06 Jubula can not start because javax.xml.bind via two dependency ch...
Status: CLOSED FIXED
Alias: None
Product: Jubula (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: 7.0   Edit
Hardware: All All
: P1 blocker (vote)
Target Milestone: ---   Edit
Assignee: Marvin Mueller CLA
QA Contact: Elena Pister CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-03 05:50 EDT by Marvin Mueller CLA
Modified: 2019-08-06 02:34 EDT (History)
3 users (show)

See Also:

Attachments
error log (4.56 KB, text/plain)
2019-06-03 05:50 EDT, Marvin Mueller CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marvin Mueller CLA 2019-06-03 05:50:46 EDT 
Created attachment 278805 [details]
error log

When starting eclipse for testers 2019-m3 all jubula relate plugins are not resolved because javax.xml.bind can be found via two dependency chains(see attached log)
Comment 1 Marvin Mueller CLA 2019-06-03 09:44:44 EDT 
As i understand this at the moment the org.eclipse.osgi is serving the javax.xml.bind and the javax.xml.bind itself. I am unsure why this is pulled into eclipse for testers at the moment. 
I assume it has something to do with the removal of these packages in java 11
Comment 2 Andrey Loskutov CLA 2019-06-03 10:40:53 EDT 
In org.eclipse.jubula.client.core, can you add explicit dependency to com.sun.xml.bind;bundle-version="2.2.0" ? Would this be a solution here?
Comment 4 Marvin Mueller CLA 2019-06-04 05:06:50 EDT 
Thanks for the information, i have now added javax.xml.bind as required bundles to the projects which are using org.dom4j. In my local tests this did work fine. I have pushed the changes
Comment 5 Marvin Mueller CLA 2019-08-06 02:34:14 EDT 
This is working now to i close this