This does make it look easy...but it's not...since
Tycho/maven p2 repo builds/deploys do different things wrt
signing, shape of build artifacts (pom, jar, source,
javadoc), signing of artifacts, other aspects of build,
authentication on deploy. For example, we've had a build
script that worked with ossrh maven central deploy for 10+
years...doesn't work with central deploy now as it uses
maven sign-and-deploy-file task. Using the
automatic-publishing as an additional maven plugin as
above doesn't currently work with our build.
I await a working really easy example to clone.
+1 for that. Perhaps our EF employees could respond to
a multi-project (community) need?
(Emulating EMF is well worthwhile since Ed Merks has
much wider awareness and the influence to encourage
others to solve problems.)
Regards
Ed Willink
On 02/07/2025 21:24, Tamás Cservenák via
eclipse.org-committers wrote:
Hi,
given you have a Maven (Tycho) build, simplest would be to use Njord.
But I am not quite in Tycho, so Christoph Laubrich should chime in here.
For me, as ASF Maven dev and PMC (also on Eclipse Sisu) that bit is really hazy:
"This is necessary for Maven to push the build to the proper Maven
Central release staging area."
Thanks
T
On Wed, Jul 2, 2025 at 9:32 PM Laurent Redor via
eclipse.org-committers <eclipse.org-committers@xxxxxxxxxxx> wrote:
Hi,
I'm taking the liberty of transferring here a topic posted to the Help Desk channel in case this topic speaks to one of you: Issue 6329 "What is the best way to publish an Eclipse repository version (update site and products) AND a Maven repository version ?".
Thank you in advance for any answers.
Regards,
Laurent Redor
_______________________________________________
eclipse.org-committers mailing list
eclipse.org-committers@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-committers