-
1. Re: eclipse designer setup issues
kukeltje Jan 8, 2008 11:36 AM (in response to umasantharam)- do you have eclipse with WTP?
- did you try to start eclipse with the -clean param? -
2. Re: eclipse designer setup issues
umasantharam Jan 9, 2008 5:08 AM (in response to umasantharam)Thx Ronald for the reploy. I downloaded eclipse-SDK-3.3-win32.zip as mentioned in the doc. I am not sure whther it includes WTP. Please confirm whether it is mandatory to install WTP also.
Please eloboare on what clean parameter I have to use to start eclipse -
3. Re: eclipse designer setup issues
kukeltje Jan 9, 2008 11:43 AM (in response to umasantharam)WTP itself is not needed if you have the full install. With the version that does not contain all dependent libs it is needed. Can you confirm you can create a web project in eclipse? or see if the WTP plugin is active in the plugins config screens
-
4. Re: eclipse designer setup issues
koen.aers Jan 14, 2008 6:18 AM (in response to umasantharam)Hi Uma,
Did you try to unzip the downloaded Eclipse archive in the folder D:\jbpm\jbpm-jpdl-suite-3.2.2\jbpm-jpdl-3.2.2\designer that you mentioned?
I just tried it on my (linux) machine again and this works like a charm.
Regards,
Koen -
5. Re: eclipse designer setup issues
umasantharam Jan 22, 2008 4:16 AM (in response to umasantharam)I tried the following now.
I downloaded jbpm-starters-kit-3.1.3 and JBossIDE for Eclipse 2.0.0.Beta2 whcih includes JBPM plugins. With this setup I am able to create BPM project and deploy. I created sample websale project and I could successfully test it.
But when I try to import any exisiting JBPM project, the designer tool fails miserably. It hangs when I access process defintion XMLs.
Can anyone tell me which will be the best versiob of eclipse IDE which can be used to build and deploy.
with rgds
Uma Santharan -
6. Re: eclipse designer setup issues
koen.aers Feb 12, 2008 9:58 AM (in response to umasantharam)Sorry for the late answer.
There *are* issues with importing existing jBPM projects. The problem is related to the defined classpath container in the Eclipse project.
The best way to deal with it is probably to do the following:
- create a new empty jBPM project (this will create a correct classpath container)
- copy over the content of the project you want to migrate to your newly created project
- possibly delete the old project and rename the new project
Let me know if this helps.
Regards,
Koen