[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: AW: [jwt-dev] JWT Galileo M6 build
|
Hello Florian, all,
Please see comments inlined:
in my opinion the following topics should be included in the Galileo
release:
* Everything that is already in the JWT feature, i.e.
* JWT Workflow Editor
* JWT Workflow Editor - Aspect extensions
* JWT Workflow Editor - UML Activity Diagram view
* JWT Workflow Editor - EPC view
* JWT Workflow Editor - HTML documentation
* JWT Workflow Editor - new View Editor (will be uploaded to IPZilla today)
* JWT Transformation - base for transformations
* JWT Transformation - XSL Tools
* JWT Transformation - JWT to XPDL transformation
* JWT Transformation - JWT to BPMN transformation
* JWT Transformation - BPMN to JWT transformation
* JWT Transformation - JWT to STP-IM transformation
* JWT WAM - Monitoring base
* JWT Feature - Branding
I agree for all but I'am not sure about the monitoring base. I do not
think it can be added into the feature in its current state, then I
imagine you have planned to work on it and get a mature version before
M7+3 (6th May) ?
What I would not include is:
* a BPMN view (We have not even started on that!)
* the new view mechanism currently in development by Chris (would mean an
adaptation of all existing plugins and therefore still A LOT OF WORK and I
would prefer to get the existing things stable and mature!)
* the new converter which only makes sense with the new view mechanism
Ok.
What I can not decide yet:
* JWT Transformation - JWT to jPDL transformation (I don't know how stable
this is, whether it is already usable, will be further maintained, e.g. by
people from JBoss, etc.).
It is not mature, they are only basis for this transformation, and I
think the decision to include it or not depends on whether JBoss' guys
have planned to work on it.
* JWT Transformation - Properties (what is this? Found it in the CVS by
purpose...).
This is a generic transformation to extract additional data from model
(ie aspects) into a .properties file. It is described in bug 266465. It
is used by Bonita4 Bar export transformation, and since it is quite
generic, it fits into WE better than into Scarbo. However, it has no
purpose on itself, it is only a tool for transformations, then it should
not be part of feature.
It is a kind of plugins that are not released, but available for
extenders and clients.
* JWT Runtime - Task Engine Framework (Does it make sense to provide it in
the release or shall it only be available on CVS for other people to have a
framework for their implementations?)
IMHO, releasing it as a plugin does not make sense while it is not used
in Eclipse. Then it shouldn't be part of the feature.
* JWT Workflow Editor - Helpers for Application and File (Should those be
included - what do other people think about them?)
These are helpers that replace all properties editors for files by
browser and that facilitate the design of application thanks to a basic
class introspection when possible.
I think they are useful enough to be included.
I guess - having a look at the list of features/plugins above - we already
have quite a lot of things that we contribute to Galileo. So our first
priority should be to make them work, fix any bugs that still exist or
extend these plugins to improve their usability and last but not least to
work on the user documentation (write articles, have presentations,
webinars, etc.).
Totally agree.
Regards,
Mickael
