[tracecompass-dev] Changes to handling of pom.xml files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[tracecompass-dev] Changes to handling of pom.xml files

From: Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx>
Date: Wed, 6 Jan 2016 23:13:49 +0000
Accept-language: en-US
Delivered-to: tracecompass-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/tracecompass-dev>
List-help: <mailto:tracecompass-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/tracecompass-dev>, <mailto:tracecompass-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/tracecompass-dev>, <mailto:tracecompass-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: AQHRSNfmwEhxYO+tzkGnu7WBJufA2A==
Thread-topic: Changes to handling of pom.xml files

Hi,

A change has just been merged so that almost all plugins do not have pom.xml anymore. This means that if you make a patch that changes a plugin version, in MANIFEST.MF, you will most likely not need to update the version in the pom.xml.
See https://git.eclipse.org/r/#/c/63050/

This change requires the use of Maven version 3.3 and up (see previous email).

Regards,
Marc-Andre

Prev by Date: Re: [tracecompass-dev] Question about importing a multi-cpu perf capture in TraceCompass
Next by Date: [tracecompass-dev] Building against Eclipse Neon (including Eclipse 4.6 platform)
Previous by thread: [tracecompass-dev] Heads up: Minimum Maven version change (3.0 to 3.3.x)
Next by thread: [tracecompass-dev] Building against Eclipse Neon (including Eclipse 4.6 platform)
Index(es):
- Date
- Thread

Breadcrumbs