Hi List
I have just installed my dev env on a new machine and so I'm running
jdk1.6.0_16, eclipse gannymede, and the latest versions of WTP, WST, JST
etc, and m2eclipse 0.9.8.200905041414.
I have a new webapp project which I created from scratch, copying the
dependencies into the POM, and copying in the src files. At some point
soon after opening up eclipse, I get a compile error as m2eclipse loses
track of a dependency.
I'm using commons-io 1.3.2 and its entry in the POM is as a standard
compile time dependency. However m2eclipse has entered it in the
project's Maven Dependencies folder with the location
"/home/adam/projects/pattern-repo/target/"
In fact it is in there twice - once as "commons-io-commons-io-1.3.2" and
once as "org.apache.commons-commons-io-1.3.2", both located in target
and not in my local repo like all the others.
Then at some point during development work, about every hour or so,
m2eclipse loses the dependency altogther and I get the compile errors. I
haven't worked out yet why or when but I'm working on it. Cleaning the
project, closing it, cleaning the project from the command line and then
reopening it seems to sort out the compile errors temporarily.
commons-io-1.3.2 does now appear at org.apache.commons as well as
commons-io/commons-io, unlike previous versions (work-around?) so I
think maybe their POMs are slightly wrong and m2eclipse can't deal with it?
Anybody else had this?
Thanks
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
