>> It is written to stop searching when it finds a build path folder,
>> with the assumption that nobody would put a model in their build
>> path, but maybe that's not true in maven?
>
> I tried to remove the src/main/resources folder from the build path
> and voilą. Entity Modeler get back working. So, yes, this
> performance improvement is a problem for Maven users, since
> m2eclipse will add automatically every resource folder to the build
> path.
This seems wrong to me ... resources is not a build path item. Kind
of sucks to give up a pretty nice performance increase (we don't have
to scan a bunch of Java packages looking for models) because the maven
plugin is doing something wrong.
ms
This archive was generated by hypermail 2.0.0 : Thu Nov 20 2008 - 16:52:49 EST