Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Pom-less builds (recent Maven version 3.3.x required)

This is a great simplification that will allow to avoid thr too-common errors of forgetting to update the pom.xml version and only catching it when the verify build fails.

Thanks for getting this done!


From: Marc-André Laperle
Sent: Feb 13, 2017 22:26
To: CDT General developers list.
Subject: Re: [cdt-dev] Pom-less builds (recent Maven version 3.3.x required)

The patch has been merged (Thanks Marc K. for the review!). Just a reminder, Maven 3.3.x is required.

Also, a few test plugins were renamed in the process so you might have to re-import them in your workspace if you had them before.



From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx>
Sent: Friday, February 10, 2017 10:49:49 AM
To: CDT General developers list.
Subject: [cdt-dev] Pom-less builds (recent Maven version 3.3.x required)


I posted a patch on Gerrit that removes a lot of pom.xml from the source tree. [1]

This is using the "pomless" Tycho functionality [2]. One advantage of this is that you do not need to update the version in the pom.xml when you change it in the MANIFEST.MF because the pom.xml is automatically generated. This also reduces a lot of the duplicated information and pom.xml duplication.

How does it work? If a plugin or feature follows a basic, common pattern, you can get the pom generated. For plug-ins/features that have more complex pom.xml, it is a bit more tricky and not always worth it. But it was possible to do it for most of CDT.

For this pom-less support to work, you need to build using Maven 3.3.x or later. I have also modified the root pom.xml to enforce this so that it is obvious if that requirement is not respected. This shouldn't be a problem unless you are using an old Linux distribution which packages an old version. If that's the case, you can pretty easily download a new version [3], extract it and add it to the PATH.

Let me know if you have any questions or concerns,

Thank you,


Back to the top