m2e is expected to detect maven plugin configuration change and create "Stale project configuration" error marker. The idea is to let the user decide the right time to update project configuration. Changing project configuration automatically during the build is a bad idea as it may destroy manual configuration done by the user. It is also prone to endless builds because configuration changes often trigger build.
-- Regards, Igor On 11-07-26 10:12 AM, Pino Silvaggio wrote:
Here's an example, i got a jaxb2 connector which verifies change in xsd(s) and build/refresh if necessary. However, what if I change the catalog parameter or the packageName in the configuration of the plugin? My question, do we have to check every possible parameters and if so, how do we do that? i.e.: check for pom.xml (effective) change? It looks that if we want to have a better integration for eclipse we need to take all the valid parameters into account... Maybe I am mistaken? _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
