Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 434164

Summary:	Unable to retrieve SWT from Maven Central due to POM group ID mismatch
Product:	[Eclipse Project] Platform	Reporter:	Benedict L. <benedictleejh>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	akurtakov, kkpshibi, Lars.Vogel
Version:	4.3.2	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Benedict L.

2014-05-06 03:43:08 EDT

I'm trying to use SWT in a project, with Gradle as my build system. When I add SWT as a dependency, Gradle gives the following error on build: 

inconsistent module metadata found. Descriptor: org.eclipse.swt:org.eclipse.swt.gtk.linux.x86:4.3 Errors: bad group: expected='org.eclipse.swt.org.eclipse.swt.gtk.linux.x86.4.3.swt' found='org.eclipse.swt'

After much searching, it seems that the groupID given in the POM is 'org.eclipse.swt', whereas the groupID registered by Maven Central is 'org.eclipse.swt.org.eclipse.swt.gtk.linux.x86.4.3.swt'. Changing the groupID to 'org.eclipse.swt' just results in it not being found.

Steps to reproduce:
1) Create a new gradle Java project
2) Add `compile "org.eclipse.swt.org.eclipse.swt.gtk.linux.x86.4.3.swt:org.eclipse.swt.gtk.linux.x86:4.3"` as a dependency
3) Execute `gradle build` in a terminal


Actual Results:
The following error is given:

inconsistent module metadata found. Descriptor: org.eclipse.swt:org.eclipse.swt.gtk.linux.x86:4.3 Errors: bad group: expected='org.eclipse.swt.org.eclipse.swt.gtk.linux.x86.4.3.swt' found='org.eclipse.swt'

Expected Results:
The dependency is resolved, and SWT is retrieved from Maven Central

Comment 1 Alexander Kurtakov

2014-05-07 02:38:38 EDT

SWT doesn't upload any artifacts to Maven central. And people decided to upload using random groupIds which caused this sad state. Sadly no one stepped in to help improve the build system and automate uploading artifacts, verify that our tycho poms are good for pure maven usage and etc. 
This is clearly a "helpwanted" item as all the current contributors using tycho and resolving from p2 repositories makes it impossible to see such issues nor we know the best practices in other communities. So until someone joins to try to resolve these issues chances for work on this is very small as we have hard time even adding support and fixing problems for/with latest versions of various OS and libraries.

Comment 2 Lars Vogel

2016-11-02 05:30:27 EDT

I think Bug 484004 contains more information on recent work about this.

*** This bug has been marked as a duplicate of bug 484004 ***