Skip to content
This repository has been archived by the owner on May 18, 2020. It is now read-only.

p2publish: Deployment of dependencies #8

Open
michael-barth-elco opened this issue Feb 28, 2017 · 1 comment
Open

p2publish: Deployment of dependencies #8

michael-barth-elco opened this issue Feb 28, 2017 · 1 comment
Assignees
Projects
Milestone

Comments

@michael-barth-elco
Copy link
Contributor

michael-barth-elco commented Feb 28, 2017

p2publish can be extended processing the last prerequisite step 'Providing 3rd party dependencies'. This are dependencies taken from Maven repositories (instead of P2 repositories how it mirrorP2repository does). They will be provided as Maven repository (for gradle) and P2 repository (for Eclipse). The artefacts must be renamed be adding a prefix avoiding resolution against mcentral or jcenter. The dependencies in the manifests must contain this prefix too.

@michael-barth-elco michael-barth-elco added this to the First release milestone Feb 28, 2017
@michael-barth-elco michael-barth-elco added this to TODO in Repository Mar 2, 2017
@michael-barth-elco michael-barth-elco moved this from TODO to In Progress in Repository Mar 8, 2017
@michael-barth-elco michael-barth-elco self-assigned this Mar 8, 2017
@michael-barth-elco
Copy link
Contributor Author

There is a new plugin MavenArtefactsPlugin, which implements this requirements. Its better to split it into two plugins, because the configurations are quite different.

@michael-barth-elco michael-barth-elco moved this from In Progress to Resolved in Repository Mar 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Repository
Resolved
Development

No branches or pull requests

1 participant