Hi all,

Another thing is really strange. I've a version of my project that was working fine, so I did a fresh install from this good version with the last maven version but I still have the project facet problem. To solve this problem, I put an old .m2 repository and so it works fine. So I conclude that it comes from maven and its way to parse the pom and to link the dependencies.

Do you have any idea what is happening with the new maven, and how I could solve this issue?

Thanks all


Harold CAPITAINE a écrit :
More over I have the same problem on the branch 3.0 of magnolia

Harold CAPITAINE a écrit :
Hi all,

I would like to know if someone has already encountered my problem.
So I'm developing my own modules and after doing a "mvn eclipse:eclipse -Dwtpversion=1.0" with mvn 2.0.5, I launch eclipse WTP 3.2 and try to add the project to a tomcat server but unfortunately I can't, because it tells me that the project facet of my project is 1.5 instead of being 1.4.2. I think that it comes from maven and I check if on the magnolia pom it's specified 1.4 and it is. So is it a bad parsing from maven or something else?

Thanks for your ideas.

CAPITAINE Harold


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------




----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------




----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------

Reply via email to