Given that the one and only release was 3 years ago,
that sort of sounds like there is not a lot of activity on that project,
but haven't looked in code repo or anything. [I was not able to find who (if anyone) is a current
committer or project lead, but assume they are aware of this plan and agree
its ok ... ]
Just makes me wonder if it (the current subproject
of MDT) should "move" to be a proper part of BPMN2 Modeler project?
You could still basically use "as is" if
it suits your needs, but ... would give more opportunity to correct errors
if any found ... and I am pretty sure there are some ... as the latest
"repo report"  shows you both are missing some "about.html"
files (I'm assuming "both" just going by version numbers of bundles).
Missing about.html in file: org.eclipse.bpmn2.edit_0.7.0.201308220617.jar
Missing about.html in file: org.eclipse.bpmn2.editor_0.7.0.201308220617.jar
Missing about.html in file: org.eclipse.bpmn2.modeler.help_18.104.22.168312131338.jar
Missing about.html in file: org.eclipse.bpmn2.modeler.wsil_22.214.171.124312131338.jar
Missing about.html in file: org.eclipse.bpmn2_0.7.0.201308220617.jar
Plus, given that BPMN2 Modeler has "graduated"
from incubation, I think it gives you a chance to drive the "mdt"
piece to graduation, give it a "1.0" version, so you do not have
to "contaminate" any names/labels by putting "incubating"
back in. Naturally, this means you really would/could maintain it, etc.
Wayne Beaton <wayne@xxxxxxxxxxx>
Bob Brodt <bbrodt@xxxxxxxxxx>,
12/13/2013 08:23 AM
Are project dependencies required to participate
On 12/13/2013 07:49 AM, Bob Brodt wrote:
The BPMN2 Modeler project will be participating in the Luna release. This
project depends on the MDT BPMN2 project which is currently not part of
any release train. My question: is MDT BPMN2 also required to be part of
Luna, and does it need to be included in the simrel aggregator?
Robert ("Bob") Brodt
Senior Software Engineer
JBoss by Red Hat