Hi Stephan, > Do you know about this [, do you have an idea what it is[
Probably, this started happening because of this change: https://github.com/scijava/pom-scijava/commit/5e6bddae9fcc965722c0fce1e2996c2e49b60411 Which in general is a _good_ thing because it's better for Eclipse to tell you than for Jenkins to tell you later after you pushed to master. If there are enforcer issues, they should be addressed, or if unaddressable the enforcer can be squelched so that CLI and Jenkins also do not complain. The weird thing here is that your Eclipse is complaining but our CLI is not. Jay may be on to something about a Maven version discrepancy. Why are you still on Kepler? You could try upgrading to Luna—I know of at least one annoying Maven-related bug that was fixed. You could also try using the Run As > Maven build... and specifying the "Debug Output" option (which passes the -X flag to Maven), and see if that tells you anything interesting. Regards, Curtis On Wed, Mar 18, 2015 at 10:33 PM, Stephan Saalfeld < saalfe...@janelia.hhmi.org> wrote: > Hi ImageJ developers, > > Eclipse complains > > Some Enforcer rules have failed. Look above for specific messages > explaining why the rule failed. > > (org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce:enforce-rules:validate) > > in my TrakEM2 master for each module. No further information (neither > above nor below) is provided. > > A terminal `mvn clean install`, however, succeeds without complaints. > So I assume that this is an Eclipse specific quirk. I have Kepler > Service Release 1 installed. > > Do you know about this [, do you have an idea what it is[, and do you > know how to fix it]]]? > > Thanks in any case, > Stephan > > > _______________________________________________ > ImageJ-devel mailing list > ImageJ-devel@imagej.net > http://imagej.net/mailman/listinfo/imagej-devel >
_______________________________________________ ImageJ-devel mailing list ImageJ-devel@imagej.net http://imagej.net/mailman/listinfo/imagej-devel
