Hi Simon,
Sorry, I've been rather busy lately too and I just realized I haven't responded in...wow, almost two weeks!
As you probably already know, it is strictly verboten (or at least sternly frowned upon ;) ) for an eclipse plug-in to reference another plug-in's packages that have "internal" in their names. The BPEL extensions sample plug-in probably needs to be reworked to remove these dependencies, and to bring it up to date with Helios (eclipse 3.6). In fact, there is a lot of other work that still needs to be done on the BPEL Designer (bug fixes, new features, documentation, etc.) but not enough hands to help.
Unfortunately, there are very few committers and even fewer that have been actively contributing to the BPEL Designer project lately - I'm one of them ;) If you have the time and desire to help out with some of the work that needs to be done, I'd be happy to work with you to get your contributions into the code.
Hope to hear from you soon!
_______________________________________
Robert ("Bob") Brodt
Senior Software Engineer, JBoss Riftsaw
JBoss by Red Hat
----- "Simon Franz" <franz@xxxxxxxxxxxxxxxxxxx> wrote:
> Hi again,
> thanks for the help. It's very helpful for me that everybody has that problem.
>
> Because of the name of the package "org.eclipse.bpel.extensionssample.ui" I'm assuming that the whole project should work even with closed project. As "dirty" hack I also tried to add "org.eclipse.wst._javascript_.core" and "org.eclipse.wst._javascript_.ui" from
http://www.mirrorservice.org/sites/download.eclipse.org/eclipseMirror/releases/ganymede/plugins/%5Bpage=20%5D . Therefore the errors dissappeard. This was just for testing for further errors in the projects.
>
> Additionally to the errors I get a lot of warnings for example in "org.eclipse.bpel.model/src/org/eclipse/bpel/model/BPELPlugin.java" on line 15 "import org.eclipse.core.internal.runtime.RuntimeLog;". The warning is "Discouraged access: The type RuntimeLog is not accessible due to restriction on required library <path of eclipse>\plugins\org.eclipse.equinox.common_3.6.0.v20100503.jar"
>
It seems that the library has access policies so the internal-path can't be used. The access policies can't be modified so the warnings are still there. Do I have to change anything here for a successful build?
>
> When I close the projects "/org.eclipse.bpel.examples.extensionPoints" and "org.eclipse.bpel.extensionssample.ui" there are no errors left. The question for me is: how can I build the whole project?
>
> Best Regards
> Simon
>
>
> On Thu, Aug 5, 2010 at 8:39 PM, Bob Brodt
<bbrodt@xxxxxxxxxx> wrote:
>
> I have to admit, I haven't been able to get this plugin to load either. This is partly because org.eclipse.wst._javascript_ plugins have been removed in WTP 3.0 and replaced with org.eclipse.wst.jsdt. Even after rewriting the _javascript_TextEditor class I was not able to get it to load successfully - there must be a remaining dependency issue I'm not seeing...
>
> Anyway, the plugin just illustrates how to implement the BPEL editor palette and _expression_ editor extension points, but it is not required to get the editor up and running. Let me know if you can get the examples plugin to load correctly - I'll keep investigating this.
>
>
> _______________________________________
> Robert ("Bob") Brodt
> Senior Software Engineer, JBoss Riftsaw
> JBoss by Red Hat
>
>
----- "Simon Franz" <
franz@xxxxxxxxxxxxxxxxxxx> wro!
te:
>
> > Hi Bob,
> >
> > Thanks for your fast response and sorry for my late response.
> > Finally most of the errors are solved.
> > Only one error is open. In package "org.eclipse.bpel.examples.extensionPoints" Java cannot find package "org.eclipse.wst._javascript_.ui.internal.editor.JSEditor".
>
>
Do you know where to find it?
> >
> > Best Regards
> > Simon Franz
> >
> >
> > On Thu, Jul 29, 2010 at 3:42 PM, Bob Brodt
<bbrodt@xxxxxxxxxx> wrote:
>
>
> >
>
Hi Simon,
> >
> > Development on the BPEL editor project has slowed during the last few years and the build instructions are probably a little out of date. Is there a reason why you are using eclipse 3.4.2 instead of a more recent release?
>
>
> > I am currently building the editor on eclipse 3.6 - if you download the "Eclipse IDE for Java EE Developers" package, it should have all of the compatible bits that you need to build the BPEL editor.
>
>
> >
Here's my build environment:
> > EMF 2.6.0
> > GEF 3.6.0 and GMF 1.3.0
> > DTP 1.8.0
> > WTP 3.2.0
> >
> > Let me know if you still have problems building the editor and I'll be happy to help.
>
> _______________________________________
> >
Robert ("Bob") Brodt
> > Senior Software Engineer, JBoss Riftsaw
> > JBoss by Red Hat
> >
> > ----- "Simon Franz" <
franz@xxxxxxxxxxxxxxxxxxx> wrote:
> >
> > Hi There,
> > >
> > > We're students from Germany and want to try to compile the BPEL-Project by ourselself.
> > > We tried to install the target-platform with the following plugins and versions:
>
>
> Eclipse 3.4.2
> > > EMF 2.4.2
> > >
GEF 3.4.2
> > > DTP 1.6.0 - 1.6.2 + Features
> > > WTP 2.0.0 and 2.0.3
> > >
> > > But there were errors installing WTP 2.0.x. We run in some weird dependencies. Some packages required org.eclipse.core.resources v3.2.0-3.4.0, other want the version 3.5.0-4.0.0.
>
>
>
Is there some way to set up the target-platform to compile the BPEL source code?
> > >
> > > Best Regards
> > > Simon Franz
> > >
> >
> _______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
> > _______________________________________________
> >
bpel-dev mailing list
> >
bpel-dev@xxxxxxxxxxx
> >
https://dev.eclipse.org/mailman/listinfo/bpel-dev
> >
> >
> >
> > _______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
> _______________________________________________
>
bpel-dev mailing list
>
bpel-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/bpel-dev
>
>
>
> _______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
