[ https://jira.jboss.org/jira/browse/JBDS-483?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBDS-483: ------------------------------------- Description: Currently it seems only the AS part of the additional runtimes are setup. That is only the right behavior when you choose an AS installation. For EAP and SOA-P additonal setup needs to be done. Seam: if it is a EAP or SOA-P it should setup seam and seamfp in seam settings (remember to give it unique names) jBPM: This is only for SOA-P; SOA-P has a jbpm runtime that needs to be configured out of the box too. Drools: This is only for SOA-P; Drools have recently added runtime support, we should investigate how that is going to be setup was: Currently it seems only the AS part of the additional runtimes are setup. That is only the right behavior when you choose an AS installation. For EAP and SOA-P additonal setup needs to be done. Seam: if it is a EAP or SOA-P it should setup seam and seamfp in seam settings (remember to give it unique names) jBPM: This is only for SOA-P; SOA-P has a jbpm runtime that needs to be configured out of the box too. Drools: Drools have recently added runtime support, we should investigate how that is going to be setup -- 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/JBDS-483?page=com.atlassian.jira.plugi... ] Kris Verlaenen commented on JBDS-483: ------------------------------------- For Drools, there are two things you might want to do (and both can simply be called using a utility class): - If you don't have a Drools runtime set up, you could create a new one on the file system using DroolsRuntimeManager.createDefaultRuntime(path). This simply creates a runtime on the file system, nothing more. However, the SOA-P probably wants to provide their own set of jars. In that case, simply copying all the required jars to a directory on the file system is sufficient (at this point) to be able to use them as a Drools runtime. - You need to register the known runtimes, using DroolsRuntimeManager.setDroolsRuntimes(DroolsRuntime[] runtimes). This will register the runtimes in the eclipse preferences. A DroolsRuntime is just a combination of a unique name and a path. One of the runtimes should also be marked as default. To verify that it worked, simply create a new Drools project. The Drools classpath container should show up in that project and point to the jars (on your file system) from the default runtime. Max, is that the info you need? Kris -- 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/JBDS-483?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBDS-483: ------------------------------------------ Koen et.al. https://svn.jboss.org/repos/jbosstools/trunk/jst/plugins/org.jboss.tools.... contains the setup code we currently have. It is named such because it was iniitally just for AS setup, but for now we just need to gather the proper things we want configured and we will take it from there. -- 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/JBDS-483?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBDS-483: ------------------------------------------ the best would be if we could do it without a hard dependency that would force a load of the plugin. But now we know where the code is we can look into it. -- 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/JBDS-483?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBDS-483: -------------------------------- I could try to extract the relevant code in its own plugin. Would that work? I planned to work today and tomorrow on the JBDS/JBT requests so I might be able to fit it in. -- 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/JBDS-483?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBDS-483: -------------------------------- Okay, but it's not a matter of how many times it is executed but rather on how easy/difficult it is to maintain the code, right? ;-) -- 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/JBDS-483?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBDS-483: ------------------------------------ JBDS uses the org.drools.eclipse plugin (5.0.0.23197.MR2 tag) which doesn't contain the DroolsRuntimeManager class. This class exists in the trunk. -- 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/JBDS-483?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBDS-483: ------------------------------------ I have created the org.jboss.tools.runtime plugin and committed it to <devstudio>/trunk/product/plugins. The plugin uses the application_platform.properties file and adds runtimes (Seam, JBoss AS, jbpm) for all the servers the user adds when installing JBDS as well as for EAP included into JBDS. The plugin needs to be in the <JBDS_HOME>/studio/eclipse/plugins directory. It works in a similar way as o.j.t.j.firstrun Since I haven't succeeded to find drools libraries within the SOA-P distribution, I haven't added any drools runtime. When building JBDS, it is necessary to take into consideration that the plugin requires o.j.t.seam.core, org.jbpm.gd.jpdl, org.jboss.tools.common and org.drools.eclipse. If we add this plugin, o.j.t.j.firstrun can be removed (or its 'startup' extension point) as well as the code that creates Seam Runtimes in the SeamFacetPreferenceInitializer class. -- 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/JBDS-483?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBDS-483: --------------------------------- Build 1274 failed: [java] generateScript: [java] [eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied. [java] [eclipse.buildScript] Bundle org.jboss.tools.runtime: [java] [eclipse.buildScript] Missing required plug-in org.jbpm.gd.jpdl_0.0.0. [java] Java Result: 13 [echo] [echo] The builder <b>runtime</b> failed to compile with the following results:<br/><br/> [echo] [echo] <pre> [echo] BUILD FAILED [echo] http://hudson.qa.jboss.com/hudson/job/devstudio-nightly/ws/jbds-build/cle... :24: The following error occurred while executing this line: [echo] http://hudson.qa.jboss.com/hudson/job/devstudio-nightly/ws/jbds-build/cle... :64: The following error occurred while executing this line: [echo] http://hudson.qa.jboss.com/hudson/job/devstudio-nightly/ws/org.jboss.ide.... :12: The following error occurred while executing this line: [echo] /qa/services/hudson/hudson_workspace/workspace/devstudio-nightly/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/genericTargets.xml:88: Bundle org.jboss.tools.runtime_0.0.0 failed to resolve.: [echo] Missing required plug-in org.jbpm.gd.jpdl_0.0.0. Also, 404 on skipped tests: /qa/services/hudson/hudson_workspace/workspace/devstudio-nightly/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:100: java.io.FileNotFoundException: http://hudson.qa.jboss.com/hudson/job/devstudio-nightly/ws/jbds-build/2.0... (No such file or directory) -- 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/JBDS-483?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBDS-483: --------------------------------- Fixed in http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly/1..., http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly/1275/ -- 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/JBDS-483?page=com.atlassian.jira.plugi... ] Anton Klimkovich closed JBDS-483. --------------------------------- jbdevstudio-win32-2.0.0.CR2-N200901142241 -- 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