-
1. Re: jBPM Designer bug [http://jira.jboss.com/jira/browse/GPD
koen.aers Nov 15, 2007 10:25 AM (in response to bgeorges)Hi Bruno,
I originally planned to do a release of 3.1.1 tomorrow. I don't know if I will make it though...
Other possibility: build the plugin yourself:cvs -d :pserver:anonymous@anoncvs.forge.jboss.com:/cvsroot/jbpm checkout jbpm.3/designer/jpdl/org.jbpm.gd.jpdl.build cd jbpm.3/designer/jpdl/org.jbpm.gd.jpdl.build/ ant
Warning: if you run the above code, it will download and install eclipse in default locations that are specified in the build.xml. You might want to edit those if you want them to be downloaded and installed at other locations or if you have them already somewhere on your disk.
Regards,
Koen -
2. Re: jBPM Designer bug [http://jira.jboss.com/jira/browse/GPD
koen.aers Nov 15, 2007 10:27 AM (in response to bgeorges)PS. There is a version check in the build... It will automatically erase and redownload/re-expand the eclipse dependencies if something doesn't match.
-
3. Re: jBPM Designer bug [http://jira.jboss.com/jira/browse/GPD
pobrien Nov 15, 2007 6:58 PM (in response to bgeorges)Hi Koen,
Bruno was kind enough to post the above message for me. Thanks Bruno! And thanks Koen for your response.
I have previously tried to do a build as you describe and had problems with it trying to replace my linux eclipse installation with a windows version. Is there a way to let it know I have a linux installation?
Regards,
Phil O'Brien -
4. Re: jBPM Designer bug [http://jira.jboss.com/jira/browse/GPD
koen.aers Nov 16, 2007 3:16 AM (in response to bgeorges)Hi Phil,
You shouldn't let the build system replace your eclipse installation. Use the downloaded eclipse only to compile the jBPM plugin. It is sufficient to point the build file to some workfolder where this installation can stick around without disturbing the rest of your system. It doesn't matter that this Eclipse is the Windows variant, it is only used to perform headless compilation so the Windows specific libraries are never used. On my Fedora installation this works fine.
Regards,
Koen -
5. Re: jBPM Designer bug [http://jira.jboss.com/jira/browse/GPD
pobrien Nov 18, 2007 11:34 PM (in response to bgeorges)Hi Koen,
I built the designer over the weekend and deployed it, however GPD-169 does not seem to be fixed.
The test I did to check whether the bug had been fixed was to create a simple process flow, save it, close it, reopen it, add a new node, save it, close it, open it. The result was a jumbled process flow as previously encountered and as reported in bug GPD-169.
It's quite possible that I've done something wrong in building and deploying, so here's what I did: I followed your instructions above for building the designer (downloading 260 MB of files in the process). This resulted in a jbpm-jpdl-designer.zip file that I unzipped into a directory. I created a fresh installation of eclipse 3.3, with clean .eclipse directory and new workspace, and added the new designer as a plugin via the eclipse gui.
Regards,
Phil O'Brien -
6. Re: jBPM Designer bug [http://jira.jboss.com/jira/browse/GPD
koen.aers Nov 19, 2007 4:02 AM (in response to bgeorges)Hi Phil,
Sorry for the inconvenience. Apparently the version and tag info in the build.xml file were not updated to 3.1.1 and HEAD respectively. If you try again now it should be okay.
Regards,
Koen -
7. Re: jBPM Designer bug [http://jira.jboss.com/jira/browse/GPD
pobrien Nov 21, 2007 9:57 PM (in response to bgeorges)Hi Koen,
I am still getting the bug. When I look in the jbpm-jpdl-designer.zip that I built the version of the plugin and feature still appear to be 3.1.0.SP1.
Regards
Phil -
8. Re: jBPM Designer bug [http://jira.jboss.com/jira/browse/GPD
koen.aers Nov 24, 2007 5:48 PM (in response to bgeorges)Are you sure? I did a build earlier this week and it seems ok...