[ImageJ-devel] Eclipse hickup with enforcer rules of pom-fiji > 7.2.0
warrick at wisc.edu
Thu Mar 19 06:16:03 CDT 2015
Sorry for all the uses of "once". I had just woken up :-)
> On Mar 19, 2015, at 5:50 AM, Jay Warrick <warrick at wisc.edu> wrote:
> Not sure if this helps... but once when I had issues with maven through eclipse once, I believe I found once that eclipse was running a different version of maven than what I would run at the command line. I think you can have the run be a bit more verbose and it will print you out some information about the maven version being used. Probably not it but might be worth checking.
> In general though, I find fewer issues running maven from command line vs through eclipse. Often not sure exactly why.
>> On Mar 18, 2015, at 10:33 PM, Stephan Saalfeld <saalfelds at janelia.hhmi.org> wrote:
>> Hi ImageJ developers,
>> Eclipse complains
>> Some Enforcer rules have failed. Look above for specific messages
>> explaining why the rule failed.
>> 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,
>> ImageJ-devel mailing list
>> ImageJ-devel at imagej.net
> ImageJ-devel mailing list
> ImageJ-devel at imagej.net
More information about the ImageJ-devel