[ https://jira.jboss.org/jira/browse/JBIDE-4319?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-4319: ----------------------------------- As of today we have: build.xml and launcher build.properties for building on Fedora (uses 4 reqs: Eclipse, WTP, EMF, XSD) partial map file (see TODOs in that file) missing "all tests" feature incomplete details in testing.properties re: which test plugins and which suites to run (see TODOs in that file) Work will progress in here: https://svn.jboss.org/repos/jbosstools/trunk/jbpm/releng/org.jboss.tools.... Once the map is complete, we can try building w/o the tests, but ultimately we need the tests to be built & run too. Note that *running* tests only works on Linux at the moment, but I have a feeling that they'll work on Mac OS X Server too (I discovered you can install X, so maybe we can also have multiple display ports active on a Mac server, if not a Mac desktop.) Cannot run on Windows until I translate runtests.sh into runtests.cmd (as a simple Ant wrapper for runtests.xml) -- 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-4319?page=com.atlassian.jira.plu... ] Koen Aers commented on JBIDE-4319: ---------------------------------- I have updated the jbpm4.map file: - removed the plugins and features that only relate to jbpm3: org.jbpm.gd.jpdl* and org.jboss.tools.jbpm.convert* - added the reference to the bad guys causing the problem: * feature@org.jboss.tools.flow.common.feature=SVN,,http://anonsvn.jboss.org/repos,,jbosstools/trunk/flow/featuresorg.jboss.tools.flow.common.feature * plugin@org.jboss.tools.flow.common=SVN,,http://anonsvn.jboss.org/repos,,jbosstools/trunk/flow/plugins/org.jboss.tools.flow.common * plugin@org.jboss.tools.flow.common.test=SVN,,http://anonsvn.jboss.org/repos,,jbosstools/trunk/flow/tests/org.jboss.tools.flow.common.test I tried to run the build after that but it failed because it lacks some property: [build] /Users/koen/Workspace/Eclipse/3.5RC3/GPD-4.x/org.eclipse.dash.common.releng/tools/scripts/getDependenciesHelper.xml:13: The following error occurred while executing this line: [build] /Users/koen/Workspace/Eclipse/3.5RC3/GPD-4.x/org.eclipse.dash.common.releng/tools/scripts/getDependenciesHelper.xml:78: java.net.MalformedURLException: no protocol: ${eclipse.SDK.url} [build] Total time: 1 minute 10 seconds Do I need to set this one somewhere? I also have an additional question: during the 'convertRawCheckoutToFeaturesAndPluginsDirs' task, the script seems to copy everything that is in my workspace to a temporary folder, even the projects that are not supposed to be part of the build. Is that on purpose, or do I need to have an additional setting? I'll attach the console log for my build. -- 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-4319?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-4319: ----------------------------------- Re: jbpm3 features/plugins Did you also remove them from the .sdk.feature/feature.xml? Your build will fail if PDE sees refs to things you seem to want to build but for which it can't resolve sources. Re: ${eclipse.SDK.url} Check the build.cfg file in the build folder (probably /tmp/build/N20090612hhmm-jbpm4/build.cfg) If you don't see the eclipse.DK.url, but something else similar, there's a bug. Or you don't have the latest version of o.e.dash.common.releng. Refresh from HEAD. Re: copying of Eclipse workspace to working workspace... this is because I'm trying to bridge three "workspace" concepts: 1) a Hudson workspace, which is a dump of sources 2) a PDE "buildDirectory" which is a dump of sources in ./plugins/ and ./features/ 3) an Eclipse workspace, which is a flat set of projects (plugins, features) which PDE UI & JDT know how to manipulate as plugin projects/features) If you only want a subset of your workspace copied over, you have two choices: a) use a different workspace for building b) use a nested tree structure (repository dump) as I do, so that your plugins and features can be contained in a single folder; then use that folder as the localSourceCheckoutDir -- see the build.properties.example.linux for how I'm pointing at a portion of my SVN tree dump. If you go the (a) route, you can still share those projects in your main workspace; just import them (without copy) from workspace-for-building into workspace-for-everything-else. Eclipse will link the projects in ~/workspace2 from ~/workspace1 If you go the (b) route, to avoid having duplicate copies of the same projects in your workspace (some in the root and others nested in the tree), close the SVN tree project once it's checked out. Then, you can import from that tree into your workspace so that the files in the tree used for building are equal to the projects in the root of your workspace. (If Eclipse understood arbitrarily deep nested projects w/o this hackaround, you wouldn't need this.) If any of the above is unclear, I'll blog a more detailed set of instructions - I'm sure others will be confused by this setup requirement. -- 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-4319?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-4319: ----------------------------------- That was a mistake. Please correct it and fix the map files accordingly. As to the ${eclipse.SDK.url} thing, I don't get that anymore here, so I suspect you need an updated org.eclipse.dash.common.releng. What's in your build.properties? Did you see the mac example I added? -- 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-4319?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-4319: ----------------------------------- These files were added/modified to hook jbpm4 builder into the uberbuilder. $ svn ci -m "" Adding builders/jbpm4 Adding builders/jbpm4/build.properties Adding builders/jbpm4/build.requires Adding builders/jbpm4/customTargets.xml Adding builders/jbpm4/jbpm4.local.map Adding builders/jbpm4/jbpm4.map Sending builders/product/build.properties Sending builders/product/buildResults/buildResults-internal.html Sending builders/product/buildResults/buildResults.html Sending builders/product/buildResults/download-template.xml Sending builders/product/updateSite/jbds/site.xml Sending builders/product/updateSite/jbosstools/site.xml Sending builders/product/versionTags/jbds/3.0.0.M2.tags Sending builders/product/versionTags/jbosstools/3.1.0.M2.tags -- 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-4319?page=com.atlassian.jira.plu... ] Max Rydahl Andersen resolved JBIDE-4319. ---------------------------------------- Resolution: Done they are back -- 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