[ http://jira.codehaus.org/browse/MECLIPSE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138704#action_138704 ]
Philip Helger commented on MECLIPSE-458: ---------------------------------------- I have a similar issue on a POM with WAR packaging. To me its seems like this was just introduced in the latest 0.94-20080603 version since the previous versions handled this correctly. Symptoms: - Java dependencies from a WAR-packaged project to other JAR-packaged projects can simply not resolved. - Referenced projects are no in the "Maven Dependencies" list. - If I change packaging from WAR to JAR, dependency resolution works again. I consider this a blocker! > Maven webapp archetype does not create correct project > ------------------------------------------------------ > > Key: MECLIPSE-458 > URL: http://jira.codehaus.org/browse/MECLIPSE-458 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Environment: Eclipse 3.3 (Europa), m2eclipse 0.9.4.200806 > Reporter: Brennan Spies > Attachments: m2_webapp_arch.zip > > > Created a Maven project, selected the Maven webapp archetype. Zipped project > created is attached. > * Missing src/test/java, src/test/resources, and src/main/java source folders > (config in Eclipse) > * Actual folders are not created > * No stack traces in workspace log file -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira