[ https://jira.jboss.org/jira/browse/JBIDE-5691?page=com.atlassian.jira.plu... ] Fred Bricon updated JBIDE-5691: ------------------------------- Description: I'm investigating ways to implement SAR support in m2eclipse (for selfish motivations I agree). See https://issues.sonatype.org/browse/MNGECLIPSE-1984. A SAR project would need to export dependencies in a lib folder, inside the archive. During my investigation, I tried to use the JBT 3.1.CR1 module assembly page, which would, from my understanding, allow me to reach the desired effect. So I've created sample maven-less projects : -sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The resulting org.eclipse.wst.common.component contains : {noformat} <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="sarproject"> <wb-resource deploy-path="/" source-path="/src"/> <dependent-module archiveName="junit.jar" deploy-path="/" handle="module:/classpath/var/JUNIT_HOME/junit.jar"> <dependency-type>uses</dependency-type> </dependent-module> </wb-module> </project-modules> {noformat} -earproject : needed so sarproject can be a Module project (which totally sucks). I've manually tweaked org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed. Here is the end result : {noformat} <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="earproject"> <wb-resource deploy-path="/" source-path="/EarContent"/> <dependent-module archiveName="sarproject.sar" deploy-path="/" handle="module:/resource/sarproject/sarproject"> <dependency-type>uses</dependency-type> </dependent-module> </wb-module> </project-modules> {noformat} Now, when exporting earproject.ear, there's no junit.jar to be found in sarproject.sar (not expected) nor in the ear (expected). When using export module on sarproject, the resulting file doesn't contain junit.jar either. This looks like a bug I've opened at eclipse's bugzilla for Connector projects : https://bugs.eclipse.org/bugs/show_bug.cgi?id=298735 The module assembly page looks very promising in theory, as it would allow support for any kind of archives (sar, har ...) but from what I understand it's only usable for ear and war projects. This bug should probably be opened at eclipse.org or is totally a duplicate of #298735 (you tell me), but I think the module assembly page should not be visible on unsupported projects. regards, Fred Bricon was: I'm investigating ways to implement SAR support in m2eclipse (for selfish motivations I agree). A SAR project would need to export dependencies in a lib folder, inside the archive. During my investigation, I tried to use the JBT 3.1.CR1 module assembly page, which would, from my understanding, allow me to reach the desired effect. So I've created sample maven-less projects : -sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The resulting org.eclipse.wst.common.component contains : {noformat} <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="sarproject"> <wb-resource deploy-path="/" source-path="/src"/> <dependent-module archiveName="junit.jar" deploy-path="/" handle="module:/classpath/var/JUNIT_HOME/junit.jar"> <dependency-type>uses</dependency-type> </dependent-module> </wb-module> </project-modules> {noformat} -earproject : needed so sarproject can be a Module project (which totally sucks). I've manually tweaked org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed. Here is the end result : {noformat} <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="earproject"> <wb-resource deploy-path="/" source-path="/EarContent"/> <dependent-module archiveName="sarproject.sar" deploy-path="/" handle="module:/resource/sarproject/sarproject"> <dependency-type>uses</dependency-type> </dependent-module> </wb-module> </project-modules> {noformat} Now, when earproject.ear, there's no junit.jar to be found in sarproject.sar (not expected) nor in the ear (expected). When using export module on sarproject, the resulting file doesn't contain junit.jar either. This looks like a bug I've opened at eclipse's bugzilla for Connector projects : https://bugs.eclipse.org/bugs/show_bug.cgi?id=298735 The module assembly page looks very promising in theory, as it would allow support for any kind of archives (sar, har ...) but from what I understand it's only usable for ear and war projects. This bug should probably be opened at eclipse.org or is totally a duplicate of #298735 (you tell me), but I think the module assembly page should not be visible on unsupported projects. regards, Fred Bricon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5691?page=com.atlassian.jira.plu... ] Fred Bricon commented on JBIDE-5691: ------------------------------------ It really seems to be a problem with variable based dependencies. After using a 'mvn dependency:copy-dependencies' trick to copy create / populate a physical lib folder within my project, it was properly exported when creating my ear, or using the module export menu. I really hope it gets fixed and backported to WTP, as it opens up lots of possibilities for users and developpers (not just m2eclipse's) regards, Fred Bricon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5691?page=com.atlassian.jira.plu... ] Fred Bricon commented on JBIDE-5691: ------------------------------------ Unfortunately no, I tested it afterwards. Published projects lack the variable based dependencies. Actually that's even a bigger deal than the export problem. Whenever I need to export something, I use maven. But publishing via WTP is what I need when actually developing stuff. You should be able to see it with the previously attached test projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5691?page=com.atlassian.jira.plu... ] Fred Bricon commented on JBIDE-5691: ------------------------------------ well that sucks. Damn, if I could find a way to lobby eclipse.org ... ;-) I know the best way to get it done would be to fix it myself and provide a patch, but it's highly unlikely, so I'll shut up and wait. If you think this bug is a direct result of https://bugs.eclipse.org/bugs/show_bug.cgi?id=298735 , you might as well close it, since the eclipse bug's been affected already. thanks Rob. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5691?page=com.atlassian.jira.plu... ] Rob Stryker updated JBIDE-5691: ------------------------------- Fix Version/s: 3.6-Helios (was: 3.1.0.CR2) targeting to helios - sorry =/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5691?page=com.atlassian.jira.plu... ] Fred Bricon commented on JBIDE-5691: ------------------------------------ FWIW, a patch's been provided for https://bugs.eclipse.org/bugs/show_bug.cgi?id=298735. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5691?page=com.atlassian.jira.plu... ] Fred Bricon commented on JBIDE-5691: ------------------------------------ Successfully tested the attached projects against Helios WTP M7. However, I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=312176 since Ear module assembly page doesn't like .sar extensions (when set manually) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira