| commit | 4baa4584051a71c697087adeec48fed9ee49ba58 | [log] [tgz] |
|---|---|---|
| author | Mickael Istria <mistria@redhat.com> | Tue Feb 01 12:55:11 2022 +0100 |
| committer | Mickael Istria <mistria@redhat.com> | Tue Feb 01 07:58:33 2022 -0500 |
| tree | b6fee090b2afa4f32b692e3c17d806815226a02b | |
| parent | 328d0d89f9993bd30476cae8efea02fae0974c74 [diff] |
Bug 578449 - Use same groupId in production pom than in consumer pom PDE artifacts are published on Maven Central with org.eclipse.pde 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: Iefbbac454d52f61a6805c46449ff75ffa2f63535 Reviewed-on: https://git.eclipse.org/r/c/pde/eclipse.pde.ui/+/190228 Tested-by: PDE Bot <pde-bot@eclipse.org> Reviewed-by: Sravan Kumar Lakkimsetti <sravankumarl@in.ibm.com> Reviewed-by: Mickael Istria <mistria@redhat.com>
Thanks for your interest in this project.
The PDE project the Eclipse tooling to develop plug-ins and OSGI bundles.
Website: https://www.eclipse.org/pde/
Contributions to PDE are most welcome. There are many ways to contribute, from entering high quality bug reports, to contributing code or documentation changes. For a complete guide, see the [How to Contribute] 1 page on the team wiki.
Information regarding source code management, builds, coding standards, and more.
Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).
You need Maven 3.3.1 installed. After this you can run the build via the following command:
mvn clean verify -Pbuild-individual-bundles
This project uses Bugzilla to track ongoing development and issues.
Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!
Contact the project developers via the project's “dev” list.