Bug 578449 - Use same groupId in production pom than in consumer
Platform artifacts are published on Maven Central with
org.eclipse.platform
groupId.
To facilitate further work which could allow deploying to p2 and Maven
as
part of the same build, let's use the target/expected buildId directly
so
we don't have to generate a new one later.
artifactId is already 1-1 mapping.
Only versions would then be different between Maven (-SNAPSHOT) and p2
metadata
(.yyyyMMddhhmm)
Change-Id: I601d2d9ec1a016f84806eeb13aa6673c5473a8b4
Reviewed-on: https://git.eclipse.org/r/c/platform/eclipse.platform.text/+/190242
Tested-by: Platform Bot <platform-bot@eclipse.org>
Reviewed-by: Mickael Istria <mistria@redhat.com>
11 files changed
