I did not test it yet on Eclipse 3.2.0. First trying to get the features
implemented ;-)
The list of correct Eclipse drivers is included in the manifest file of the
plugin. It is indeed a good suggestion to mention them in the release notes.
Only problem is that this is again a thing that could
[EMAIL PROTECTED] wrote :
| You can find the current dependencies on Eclipse in the
dependencies.properties file which is in the org.jbpm.gd.jpdl.build project
Thanks Koen. I'll try upgrading to eclipse 3.2.1 along with the rest of the
dependencies you mentioned. I suspect that this
Bill,
You can find the current dependencies on Eclipse in the dependencies.properties
file which is in the org.jbpm.gd.jpdl.build project (right next to the
org.jbpm.gd.jpdl plugin project).
For your convenience, the relevant excerpt from this file:
# Eclipse filename and version info
|
Koen,
What would you think of such a move?
I don't really know enough to have anything useful to say. I fear a lot of
merge-induced churn without much forward progress, and I fear a lot of refocus
toward pageflow support to the detriment of BPM - but this is based on nothing
but guesswork.
Hi Ed,
I am not very active at the moment in Eclipse JWT mainly because of time
constraints as I have to work on the GPD ;-) But I definitely am following the
evolution quite closely as JWT is somewhat the graphical couterpart of what
jBPM is trying to do on the runtime side.
On the other
[EMAIL PROTECTED] wrote :
| I did not yet try to do a build of the designer after I merged the two
plugins. How did you build it exactly?
|
I've tried both ant and the direct method using eclipse. The same anomalies
show up in either case.
anonymous wrote :
| Of course you need to
Just to clarify, the 3.0.13.1 version is shipping with jBPM 3.2GA, while the
3.1.0.alpha3 version of the designer is building on cvs HEAD. (But the 3.2GA
target still contains 3.0.13.1, so there's no confusion for end users, only us
wannabees)
View the original post :
I have a very related question.
I assumed that the jpdl 3.2 tag of jbpm.3 was the full GA tree.
When I checked it out, I found that the designer was in an intermediate,
unbuildable state (missing files, etc.).
It looks like there's no single branch or tag for 3.2.
So... what should be checked out
To work on the head of the designer you should checkout the org.jbpm.gd.jpdl
project in the module jbpm.3/designer/jpdl. The build script of jpdl 3.2
fetches the already built designer (3.0.13.1)from the repository.
Regards,
Koen
View the original post :
Thanks, Koen.
Two more quick (I think!) questions:
Does org.jbpm.gd.jpdl have dependencies on other portions of the jbpm.3 tree?
If so, can the head be used, or is some other tag required?
-Ed Staub
View the original post :
[EMAIL PROTECTED] wrote : To work on the head of the designer you should
checkout the org.jbpm.gd.jpdl project in the module jbpm.3/designer/jpdl. The
build script of jpdl 3.2 fetches the already built designer (3.0.13.1)from the
repository.
|
| Regards,
| Koen
Thanks alot for taking
Hi guys,
@Bill:
I did not yet try to do a build of the designer after I merged the two plugins.
How did you build it exactly?
I still have to adapt the org.jbpm.gd.build project AFAIR. A quick patch would
be to import the org.jbpm.gd.jpdl project in your workspace and do an export.
Of
12 matches
Mail list logo
