[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi... ] Robert (Bob) Brodt commented on JBIDE-11121: -------------------------------------------- Thanks Mickael. I would like to try and do this myself to get a better understanding of what's going on here... You can "teach a man to fish" and help me out here by filling in the holes in my understanding, indicated by <hole></hole> below... So, I need to: 1. copy the file jbosstools-build/target-platforms/soatools-4.2.1.a/soa-extensions.target from your github repo to the BPEL and BPMN2 editor project <hole>which directories, project root only, or every plugin directory?</hole> 2. make the changes to the pom.xml in the BPEL and BPMN2 project roots as you described <hole>I will only be able to do this locally because I don't want to push these pom.xml changes to eclipse.org, right?</hole> 3. test the BPEL and BPMN2 editor builds using <hole>"mvn verify" and a bunch of other options, which are...?</hole> 4. attach the build log to this JIRA FYI, the projects at eclipse are here: https://git.eclipse.org/c/bpel/org.eclipse.bpel.git/ https://git.eclipse.org/c/bpmn2-modeler/org.eclipse.bpmn2-modeler.git/ The BPEL editor also has a required plugin which lives at github because it uses some JBoss libraries and therefore can't be included in the git.eclipse.org repo; that plugin is here: https://github.com/jbosstools/jbosstools-bpel -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira