Dave,
IMHO, artifacts produced by proprietary tools have no
business being in CVS at Eclipse unless all committers on the project have (free)
access to the tools that produce/maintain them. We’re actually in the
process of removing the .emx files from the UML2 component; they’ll still
be used as the source for the diagrams in the UML specification, but they’ll
be maintained in an OMG location (e.g. on a wiki) managed by the UML RTF (members
of which are to be given licenses to RSx)…
Cheers,
Kenn
Hussey
Program Manager, Modeling and Design Solutions
Embarcadero Technologies, Inc. | www.embarcadero.com
82 Peter Street, Second Floor | Toronto, ON
M5V 2G5
Kenn.Hussey@xxxxxxxxxxxxxxx
Office: 416-593-1585 x9296 Mobile: 613-301-9105
From:
mdt-sbvr.dev-bounces@xxxxxxxxxxx [mailto:mdt-sbvr.dev-bounces@xxxxxxxxxxx] On
Behalf Of Dave Carlson
Sent: Wednesday, October 22, 2008 10:40 AM
To: 'SBVR developer list'
Subject: RE: [mdt-sbvr.dev] Build configuration
This project's current code requires only the *released* Ganymede
platform for all components. The easiest way to get a complete
environment is to download the Eclipse Modeling Tools package from http://www.eclipse.org/downloads/.
That is what I have used since it was released end of June. If you want
to create a customized smaller environment, simply use the released build of
Ganymede components. The single download of the Eclipse Modeling Tools
package should be sufficient to build and run all code in this project's CVS.
This does not include the open source UML diagram editor,
Papyrus. For that, I have used Papyrus 1.9.1. But this is only
required to open and edit the diagrams. The project's .uml models can be
processed using only Eclipse MDT Ganymede. I hope that by early next
year, we will have the "new" Papyrus available under Eclipse MDT
(approved, but no code so far). But that may require the next Eclipse
generation, Galileo, when we'll need to agree on a new coordinated set of
milestone components. I intend to postpone that until it's required.
IBM released RSM and RSA 7.5 on Oct 1st and it is based on
Ganymede. I already use RSM 7.5 for my other work and will try to
test it this week with the projects in CVS. It should be fully
compatible, except for the UML diagrams that require Papyrus, and it should be
possible to install Papyrus into RSM/A.
For myself, I would be happier to use IBM's RSM/A, instead of
Papyrus, for creating metamodel diagrams in this project. I believe
that you, Stan, and myself all use RSM/A. But I wanted to create a
project environment that required only open source development tools.
Does anyone else on this list feel strongly about *not* migrating the model
diagrams/editing to RSM 7.5? If we made that change, then we must follow
the process of Eclipse UML2 project where the RSM .emx model files are exported
to .uml each time models are checked into CVS. Then others could use
other UML tools to create diagrams for those .uml model files.
-----Original Message-----
From: mdt-sbvr.dev-bounces@xxxxxxxxxxx [mailto:mdt-sbvr.dev-bounces@xxxxxxxxxxx]
On Behalf Of Mark H Linehan
Sent: Tuesday, October 21, 2008 2:43 PM
To: mdt-sbvr.dev@xxxxxxxxxxx
Subject: [mdt-sbvr.dev] Build configuration
It would be very helpful if someone could post on the MDT/SBVR WIKI page a
list of the build dependencies for the checked in code. I'm asking because the
code must be dependent upon EMF and through that upon a particular level of
Eclipse. The trial-and-error approach to figuring out what combination works is
very time-consuming and a barrier to getting started.
I'm also asking because normally I work with IBM's RSA but it is back-level
with request to the latest-and-greatest in Ganymede and EMF. So knowing the
build dependencies helps me figure out whether I can use what I have or have to
install some combination of Ganymede+EMF+Papyrus plus whatever else in order to
get a working UML modeling environment that will also build the SBVR code.