I'm sorry, I really do not understand what you mean by "only supports WAR packaging".
Could you please elaborate a bit? -Chris Igor Fedorenko-4 wrote: > > Chris, > > Our WTP integration requires WTP version 2.0 or 3.0, it does not work > with earlier versions of WTP. I think it is possible to update m2eclipse > to work with WTP 1.5, but at this point we do not have development > resources for this. I however will be able to provide pointers and other > help if you're interested to help. > > Also note that in general, m2eclipse only supports WAR packaging. Please > open enhancements requests in JIRA to support EAR and EJB packaging and > I will have a look. > > [EMAIL PROTECTED] wrote: >> Hi all. >> >> I have the standard J2EE type project, the EAR, EJB, WAR and a resource >> Jar. All m2eclipse enabled. >> >> For the EJB project: >> >> The Enable workspace resolution/Resolve dependencies from Workspace >> projects is enabled. >> >> The EJB project has the resource jar listed as a dependency in the pom >> file (using a 1.0-SNAPSHOT version). >> >> It correctly shows the resource jar (as a Project icon, not a jar icon) >> in >> the list of jars under the Maven Dependencies classpath container. >> >> For the WAR project: >> >> The Enable workspace resolution/Resolve dependencies from Workspace >> projects is enabled. >> >> The WAR project has Resource and EJB projects listed as dependencies in >> the POM. >> >> Neither of these projects appear in the Maven Dependencies classpath >> container at all. >> >> This is not what I'd have expected. >> >> I've had to manually add them as Projects on the Classpath, as opposed to >> the maven pom based one. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > -- View this message in context: http://www.nabble.com/resolving-workspace-artifacts-tp17816088p17847750.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email