-
1. Re: 3.3M4 deployment problem
maxandersen Dec 23, 2011 7:32 AM (in response to apolci)Please try just released M5 - in here we fixed https://issues.jboss.org/browse/JBIDE-8863 which I *think* should cover your problem based on your description.
If not - please open jira with details in https://jira.jboss.org/jira/browse/JBIDE on how to reproduce - thanks!
-
2. Re: 3.3M4 deployment problem
apolci Dec 23, 2011 9:08 AM (in response to maxandersen)I upgraded to M5 but the problem seems to remain.
About jira I'm not sure on how to reproduce the problem since I have other projects with similar structure and they work just fine and I don't understand what is triggering it.
I'm also quite sure that the same project worked fine a few days ago and I didn't changed anything important in the configuration. I'll try to revert old source to be sure.
Thanks for the help.
Andrea
-
3. Re: 3.3M4 deployment problem
maxandersen Dec 26, 2011 6:15 PM (in response to apolci)just noticed you mentioend maven - do you have latest version of eclipse m2e/wtp installed to be sure it actually configures m2e properly to work with WTP style projects?
-
4. Re: 3.3M4 deployment problem
apolci Jan 5, 2012 4:52 AM (in response to maxandersen)I have m2e 1.0.100 and wtp 3.3.1, they are the latest right?
I tried to revert to a version of my project that I knew was working and the problem remain the same, so it have to be something in eclipse.
I should try to delete the workspace and recreate it, but actually I'm working on a different project. Will try when I switch again to that project.
Thanks again,
Andrea
-
5. Re: 3.3M4 deployment problem
apolci Jan 9, 2012 4:46 AM (in response to apolci)Finally I figured out the problem.
For some reason the C project (the utility module) had wrong configuration in Deployment Assembly section of the project properties.
The /src/ folder was mapped on / deploy path. Instead the /src/main/java forlder should be mapped on / deploy path.
I still don't know how this happened (neved changed this section manually). May be there was a problem with the eclipse project configuration generation from maven configuration, but I don't know.
Thanks for the help,
Andrea