[ https://issues.jboss.org/browse/JBIDE-11902?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-11902: ------------------------------- Attachment: bpel-patch.txt Patch to fix a few issues in.classpath, manifest.mf, and pom.xml: [^bpel-patch.txt] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11902?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-11902: ------------------------------- Description: Cannot build BPEL component due to new bot test plugin and its dependency on xmlunit. Simplest solution is to build an osgi plugin wrapper for xmlunit (as apodhrad has started) and to add that plugin to the tests/pom.xml; this is a stopgap to allow a quick Beta2 build to be achievable. However, a longer-term solution (which would make Max happy - http://lists.jboss.org/pipermail/jbosstools-dev/2012-May/005253.html) might be to depend directly on the maven artifact, eg by adding this to bpel/tests/org.jboss.tools.bpel.ui.bot.test/pom.xml: {code} + <dependencies> + <dependency> + <groupId>xmlunit</groupId> + <artifactId>xmlunit</artifactId> + <version>1.3</version> + <scope>test</scope> + </dependency> + </dependencies> {code} or else to provide this org.custommonkey.xmlunit plugin via a target platform [1] or on the JBT composite requirements site [2]. [1] http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.SR2/ [2] http://download.jboss.org/jbosstools/updates/indigo/, http://download.jboss.org/jbosstools/updates/indigo/extras/ was: Cannot build BPEL component due to new bot test plugin and its dependency on xmlunit. Simplest solution is to build an osgi plugin wrapper for xmlunit (as apodhrad has started) and to add that plugin to the tests/pom.xml; this is a stopgap to allow a quick Beta2 build to be achievable. However, a longer-term solution might be to depend directly on the maven artifact, eg by adding this to bpel/tests/org.jboss.tools.bpel.ui.bot.test/pom.xml: {code} + <dependencies> + <dependency> + <groupId>xmlunit</groupId> + <artifactId>xmlunit</artifactId> + <version>1.3</version> + <scope>test</scope> + </dependency> + </dependencies> {code} or else to provide this org.custommonkey.xmlunit plugin via a target platform or on the JBT composite requirements site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11902?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-11902: ------------------------------------------- I think that the second solution is better - commited to trunk -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11902?page=com.atlassian.jira.plugi... ] Andrej Podhradsky closed JBIDE-11902. ------------------------------------- The XMLUnit lib was added into the plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira