Re: [m2e-dev] Scanning for changed files in a m2e compatible Maven plugi

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

No, you just use BuildContext. DefaultBuildContext is used when the
build runs on command line and m2e will inject workspace-aware
implementation when the build is invoked as part of workspace build.

--
Regards,
Igor

On 12-08-02 11:22 AM, Anders Hammar wrote:
> I'm trying to make the JAXB Maven Plugin of Codehaus Mojo compatible
> with m2e as outlined in [1].
>
> I'd like the plugin to skip execution when there are no changes to the
> sources even when run from command-line (which there is already
> support). Hoping to be able to use the BuildContext features for this,
> I see that the DefaultBuildContext implementation does not support
> this (it will always say all files are newly created).
>
> So, my question is, do I need to implement two different code logics
> to decide if the sources have changed? I.e., when
> BuildContext.isIncremental() returns true I can use BuildContext, but
> when it returns false I have to implement some other logic.
>
> /Anders
>
> [1] http://wiki.eclipse.org/M2E_compatible_maven_plugins
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev