Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Pushing plugins in maven style, which repository to use?


Every Eclipse project can request their own repositories (xxx-releases and xxx-snapshots) to be created by opening a helpdesk issue:

All Jenkins instances are set up to deploy to by default, but the dedicated repositories need to be created first (see above).

Instructions for deploying to can be found here:
* *

We can also assist in setting up deployment to OSSRH/Maven Central.



On 16.12.22 10:38, RADERMACHER Ansgar wrote:
Dear all,

in the context of a collaboration with OBEO, we have dependencies from a non-OSGI project to Eclipse plugins, notably Papyrus SW designer and UML2. This means that we cannot use the available p2 update sites.

In case of Papyrus SW designer, we pushed a snapshot via a "mvn clean deploy" to a subfolder in [1]. In case of UML2, we entered into a discussion what should be the right repository to use, see [2] . The resulting questions are

- Which is the recommended repository and sub-folder for pushing plugins? Is that maven central?

- Do jenkins jobs running on have the right to push/deploy to this repository? This is the case for, but likely not for others

- Is there a particular setup to do (besides adding distributionManagement tags to pom.xml)?

Sorry, if these questions have already been asked, but I could find the information.

Best regards


[1] <> [2] <>

cross-project-issues-dev mailing list
To unsubscribe from this list, visit

Frederic Gurr
Team Lead - Release Engineering | Eclipse Foundation Europe GmbH

Berliner Allee 47, D-64295 Darmstadt
Handelsregister: Darmstadt HRB 92821
Managing Directors: Gaël Blondelle, Mike Milinkovich, Michael Plagge

Back to the top