On 2013-04-12 1:12 PM, Thomas Hallgren wrote:
Question to Igor: If I specify maven.pomderived = "false" or don't
specify maven.pomderived at all, why doesn't m2e leave the entry unaltered?
This is likely a bug, m2e is expected to preserve classpath entries not
marked as maven.pomderived. At lea
Hi Adrien,
Thanks for the pointer. I understand the motivation behind the current
behavior but I agree with you, not checking in the .classpath is not an
option for us. The current behavior is IMO a bug.
Question to Igor: If I specify maven.pomderived = "false" or don't
specify maven.pomderi
The .classpath project does not reflect what really happen with m2e, it
will do exactly like the command line.
Without m2e, it will not work and there is no way around this. Your only
option it to not commit the .classpath and let others people generate their
own.(Not really an option IMO)
See the
On 2013-04-12 18:11, Igor Fedorenko wrote:
src/main/resources directory is not on project compile classpath during
command line build, so I believe "m2e updates my classpathentry in
accordance with what I've specified in the POM" describes m2e
behaviour.
I'm sorry, but no. It doesn't matter what
src/main/resources directory is not on project compile classpath during
command line build, so I believe "m2e updates my classpathentry in
accordance with what I've specified in the POM" describes m2e
behaviour.
--
Regards,
Igor
On 2013-04-12 11:08 AM, Thomas Hallgren wrote:
Hi,
m2e changes my
