[ http://jira.codehaus.org/browse/MNGECLIPSE-4?page=comments#action_55659 ]
Eugene Kuleshov commented on MNGECLIPSE-4: ------------------------------------------ I am not very familiar with ejb3 packaging types and I also found this [blog entry|http://weblogs.java.net/blog/ss141213/archive/2005/12/do_i_need_par_f.html] which saying that these archive types are not needed. So, it seems that jar packaging should be used for these types and we can apply suggested patch to do not add other archive types to the Eclipse build path. Dmitry, can you please take a look if there is some Eclipse API to verify if given archive type is suported, so we won't hardcode their extensions. > Problems with dependencies other that jar and war (ie. par, ejb3) > ----------------------------------------------------------------- > > Key: MNGECLIPSE-4 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-4 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Versions: 0.0.3 > Environment: MS Windows XP, Eclipse 3.2M2, plugin ver. 0.0.3 > Reporter: Piotr Bzdyl > Assignee: Dmitri Maximovich > Fix For: 0.0.4 > Attachments: MNGECLIPSE-4.jpg, patch.txt, test-projects-MNGECLIPSE-4.zip > > > I found a problem in eclipse with projects producing artifacts with other > than war and jar types. I use mvn eclipse:eclipse to generate .project and > .classpath on the pom.xml with <packaging>war</packaging> which contains > dependency to the mymodel.par artifact (Persistence archive jar file) (I > still don't know how to open project in eclipse with only pom.xml - no > .project and .classpath files), then I import this project to the workspace. > Until now everything is working fine. Then I use context menu on the project > and select Maven 2 -> Enable. I got errors with duplicated dependencies (in > .classpath and in the Maven2 Dependencies node) so I remove duplicated > entries from eclipse java build path. Then I have one more error which I > can't remove: Illegal type of archive for required library: 'C:\Documents and > Settings\piotr\.m2\repository\com\example\mymodel\1.0\mymodel-1.0.par' in > project mywar. How to cope with this error? I think that maven2 plugin should > try to treat all dependencies as jar files and if it fails generate this > error. This same occurs with mylogic.ejb3 (plain jar file with EJB3 session > beans). -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
