Bug 515137 - publish a pom as a kind of target platform definition for maven consumers
Summary: publish a pom as a kind of target platform definition for maven consumers
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.7   Edit
Hardware: PC Linux
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-11 15:45 EDT by Stephan Herrmann CLA
Modified: 2017-04-19 13:43 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Herrmann CLA 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)