[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4319) Include jbpm4 into build

[Nick Boldt (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12471964#action_12471964 ] 

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.

> Include jbpm4 into build
> ------------------------
>
>                 Key: JBIDE-4319
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4319
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: Build/Releng, jbpm
>            Reporter: Max Rydahl Andersen
>            Assignee: Koen Aers
>             Fix For: 3.1.0.M2
>
>         Attachments: build0.txt
>
>
> We should get jbpm4 into the jbosstools build so it becomes accessible and available for testing.
> As discussed on phone we will initially just want this in the JBT build, but not in JBDS and we are ok with having jbpm3 and jpbm4 overlap with functionallity for a while as long as when we reach GA the two will be aligned/compatible.
> Koen, first step is for you to add info here on which svn/cvs plugins/features we need to include and then reassign this to Nick who can help out integrate it into our current 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