Bug 515137

Summary:	publish a pom as a kind of target platform definition for maven consumers
Product:	[Eclipse Project] Platform	Reporter:	Stephan Herrmann <stephan.herrmann>
Component:	Releng	Assignee:	Platform-Releng-Inbox <platform-releng-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	clement, cvgaviao, olivier.cailloux
Version:	4.7
Target Milestone:	---
Hardware:	PC
OS:	Linux
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=510072
Whiteboard:

Description Stephan Herrmann

2017-04-11 15:45:31 EDT

Given the artifacts published to Maven Central use version ranges for dependencies among them, consumers need a way to make their builds reproducible.

In PDE, this would be handled via a target platform definition.

I recently learned, that a pom with only a long list of dependencyManagement with exact versions can play this exact role. This pom would be consumed like this:

       <dependencyManagement>
            <dependencies>
                <dependency>
                    <groupId>org.eclipse.platform</groupId>
                    <artifactId>eclipse-sdk-dependencies</artifactId>
                    <version>4.7.0</version>
                    <scope>import</scope>
                    <type>pom</type>
                </dependency>
            </dependencies>
        </dependencyManagement>

If no one objects, and if we agree on a name for that new artifact/pom, then I offer to try to generate such pom during the publish-to-maven process (in or around bug 510072)