1: could be a slip of the keyboard. I'm not sure.
2: linux, no not needed. only the java files of eclipse are needed.

Regarding the error.

[java] /home/agaton/projects/jbpm.3/designer/jpdl/org.jbpm.gd.jpdl.build/genericTargets.xml:63:
 Unable to find plug-in: org.jbpm.gd.jpdl_0.0.0. Please check the error log for more details.

copies generated GPD jars and makes eclipse distribution ready to use ONLY for Windows.

Disabling building GPD certainly helped, now I have some artifacts built, but not all, e.g bamconsole and jboss.
I know that bamconsole is work in progress and that maybe is not integrated yet. But what is the case with jboss folder?

But then I added few nodes: task node, new ESB node, mail node and nothing happens when I double click them, also I see no option when I right-click on them, so I cannot define task in a tasknode. Also, I cannot add swimlane.
Any idea, why is this happening?

Hi Ronald,

It seems to be that the build problem is more then a more then a “shortâ€� refactoring problem.
I am using windows XP , ant 1.7 and java 5 and have the same problem since a month.

It would be grate if somebody would fix the broken build and add gpd to hudson.jboss.org so it is visible to all if the build is broken.

Regards Philipp

Nice UTF-8 support here, don't you think?

I'm updating my tree at the moment and will try a build then.... Windows 2000, Java 5, ant 1.6.4.

Hi all,

when compiling jBpm CVS HEAD, I stumbled upon the same problem, "Missing required plug-in org.jbpm.gd.common_0.0.0", but managed to get the build run to completion with some "manual intervention".

Steps to reproduce (jbpm.3 is the local CVS module root folder):

• 
  
• Set up a copy of Eclipse SDK 3.3.1.1, unzip dtp-sdk_1.5.1, emf-sdo-xsd-SDK-2.3.1, GEF-SDK-3.3.1, wtp-sdk-R-2.0.1-20070926042742 (all from the local jBPM repo) into the eclipse dir, and switch to a clean workspace.
  
• Import the projects under jbpm.3/designer (org.jbpm.gd.bpel, org.jbpm.gd.bpel.runtime, org.jbpm.gd.common, org.jbpm.gd.pf).
  
• All projects should build, except org.jbpm.gd.bpel.runtime, which depends on org.eclipse.bpel, so I installed the BPEL plugins from http://download.eclipse.org/technology/bpel/update-site.
  
• For some strange reason, org.jbpm.gd.bpel.runtime still does not compile, having troubles with "The import org.eclipse.bpel cannot be resolved", although the plugin is there, and I reloaded the target platform under Preferences / Plug-in Development / Target Platform, but still no luck. Can anyone help here?
  
• Export org.jbpm.gd.common (File / Export / Deployable plug-ins and fragments) to jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\target\workspace, deselect option "Package plug-ins as individual JAR archives".
  
  
  By the way, I found that when checking out jBpm HEAD inside Eclipse, not all folders are checked out, so I used cvs command line client to check out the complete source.
  
  What was missing from the build was jbpm.sar, which I built using the following steps:
  
  • 
    
  • Run jbpm.3\jpdl\jar>ant config.profile.datasource. Although this is marked as old stuff in the main build.xml, it seems to work.
    
  • Manually copy jbpm.3\jpdl\jar\target\profiles\jbpm.config.profile.datasource.jar to JBPM_REPO\jbpm\jpdl\3.2.2\lib\jbpm.config.profile.datasource.jar
    
  • Run the package target in jboss/sar: jbpm.3\jboss\sar>ant package
    
    
    Testing jbpm.sar:
    
    • 
      
    • Copy jbpm.sar from jbpm.3\jboss\sar\target to jboss-4.2.2.GA\server\default\deploy
      
    • Copy jbpm-ds.xml from jbpm.3\jboss\configuration\4.2.2.GA\target\configuration\deploy to jboss-4.2.2.GA\server\default\deploy
      
    • Copy the application-policy name="jbpm" from jbpm.3\jboss\configuration\4.2.2.GA\target\configuration\conf\login-config.xml into jboss-4.2.2.GA\server\default\conf\login-config.xml
      
    • Copy jbpmDB.properties and jbpmDB.script from jbpm.3\jboss\configuration\4.2.2.GA\target\configuration\data\hypersonic to jboss-4.2.2.GA\server\default\data\hypersonic
      
    • Copy the JbpmCommandQueue and JbpmJobQueue mbean definitions from jbpm.3\jboss\configuration\4.2.2.GA\target\configuration\deploy\jms\jbossmq-destinations-service.xml to jboss-4.2.2.GA\server\default\deploy\jms\jbossmq-destinations-service.xml
      
    • Copy jbpm-console.war from jbpm.3\console\target\jbossas-4.2.x to jboss-4.2.2.GA\server\default\deploy
      
    • Start jboss-4.2.2.GA
      
    • jbpm-console should be functional
      
    • JNDIView should show the JbpmService MBean under jboss.jbpm:name=DefaultJbpm,service=JbpmService
      
      
      And, seriously folks, what about migrating the build process to maven 2? With the current build system, several targets get re-run over and over again during a build, hinting at broken dependency checking of build artifacts, and resulting in unneccessary long build times. As far as I can see, JBoss is gradually moving all project builds to maven, so this might be worth considering (I know, the current build system has certainly taken lots of time and energy, but maven does this, well, even better).
      
      regards,
      Karl
      
      Karl Traunmueller
      
      Objectbay Software & Consulting GmbH
      Softwarepark 35
      4232 Hagenberg, Austria
      www.objectbay.com
      

It's of course jmx-console, not JNDI View. JNDI View should show jbpm/JbpmConfiguration under the java: namespace.

regards,
Karl

Hi Karl,

Thanks for your response. I can reproduce your problem after building the org.jbpm.gd.bpel.runtime the import org.eclipse.bpel cannot be resolved.

Do you try to build org.jbpm.gd.jpdl? If I import the project in eclipse there is another missing dependency "Cannot find the class file for org.eclipse.jface.text.source.projection.ProjectionViewer".

Can any one help here?
Please Koen give us a hint!! (or sign ;-)

I agree maven would be a big help. But its looks like tom decided to use ivy. In the new repository the builds are done with ivy and ant (http://anonsvn.jboss.org/repos/jbpm/tempranillo/jpdl/trunk).

Regards philipp

Hi Philipp,

right, I get the same error.

If I add org.eclipse.jface.text in the Dependencies section of the plugin.xml editor (jface.text was clearly missing), add dom4j-1.4.jar under Java Build Path / Libraries / Add Jars / org.jbpm.gd.bpel/lib, reorganize the imports (Ctrl + Shift + O), add org.dom4j.Element, I still get a single compile error "The method getAttribute(String) is undefined for the type Element" in JpdlContentProvider.java.

Strange.

Karl

Try to check out the version labelled 3.2.2 and not use cvs-head. There are some changes going on currently that can make building impossible the coming days

Hi all,

in the developer forum Koen has answered my post and he will fix that problem ( http://jboss.org/index.html?module=bb&op=viewtopic&t=127556 ).

Regards Philipp

I think these are/were two separate problems. One in because of the GPD, the other because of a webservice frontend being added to jBPM

Hi Ronald,

I don't think so. This Thread is about build problems in two flavours ant and eclipse build problems and both in the gpd.
The linked thread was initially about news in gpd. But how it is possible to test the news without compiling the source ;-).

And after a comment from koen I am sure he will fix that problem and will post the result in the linked thread.

Regards Philipp