Re: [ease-dev] Eclipse Marker from EASE Script

[Felix Dorner <felix.dorner@xxxxxxxxx>]

I actually wonder, does a marker-only kind event really trigger a rebuild?

Maybe not possible at the moment but how about executing your script in the context of a builder itself, one which runs after the pde manifest builder?

On Jun 6, 2017 08:14, <Christian.Pontesegger@infineon.com> wrote:

Typically a builder on a resource deletes its resource markers upon a build.
So I see 2 options:

a) disable the builder that deletes the markers (I guess it would be the
Plugin manifest builder)
b) define your own marker type and cross your fingers that the builder will
leave them intact on a build process. Here you might also have the problem
that you need to display your markers somehow. Not sure if yourError markers
will get displayed, even when they inherit from the default error marker.

Christian

-----Original Message-----
From: ease-dev-bounces@xxxxxxxxxxx [mailto:ease-dev-bounces@eclipse.org] On
Behalf Of Raphael Geissler
Sent: Sunday, June 04, 2017 8:37 AM
To: ease developer discussions
Subject: Re: [ease-dev] Eclipse Marker from EASE Script

Hi Jonah,

thanks for the hint. I tried your example and it's working fine.

However, if I try to add a Warning Marker to a MANIFEST.MF file, it is no
shown. Maybe it is immediately deleted, because a change in the MANIFEST.MF
file triggers a new build.

Any ideas how to get this working?

_______________________________________________
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ease-dev