I don't know - we should just be doing the same copy of files as before.
Did you import the same project ?
Yes it is the "same" project. This means it uses exactly the same subversion repository to check out a project.
It is an ear project assembled from maven:
what comes after maven: ?
I would need to know more about what is failing.
are you using the same workspace ?
Any file differences ?
Does it happen on non-maven projects ?
Hello Thanks for the answer.
I try to explain:
1. Checking out the project (choosing a different directory for europa/ganymede
2. run the following commands
3. In a fresh workspace import the project into eclipse.
As you can see, we are generating the eclipse artefacts (.project etc) from maven. Perhaps this introtuces the problem?
Europa uses WTP2 and Ganymede uses WTP3
And maven can only generate WTP2 artefacts
Yes, unless you are using the *same* project i'm inclined to say Maven's generation is broken.
What happens if you simply use the same workspace you used in Europe with Ganymede ?
I have copied my Europa workspace and used the copy with ganymede. The same result/problem.
ZThe only thing that is working is to generate a new seam project with JBT inside ganymede
So i fear that i must go back to europa. I can not change the way our eclipse artefacts are generated:-(
well I would really like to know why the same project in europe doesn't work on ganymede.
Could you create the *simplest* project that illustrates this and report it in jira ?
Would like to know if it is something that changed in Eclipse or in JBoss Tools that causes it.