Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: Fwd: [] Can MDT/OCL make MDT/UML2-Tools useable on Helios?


Thanks to Kenn and others,
I have finally just completed U2T build available at

In order to make an update site and promote it, I need an ssh access to build server as the promotion scripts don't work from web UI.


On Wed, Jul 7, 2010 at 8:47 PM, Kenn Hussey <kenn.hussey@xxxxxxxxx> wrote:
Note that the dependencies (among many other things) for the build can be modified by changing the files in the org.eclipse.uml2tools.releng project (for which I don't have permission). In particular, see builder/runtime/customTargets.xml and builder/sdk/customTargets.xml.



On Wed, Jul 7, 2010 at 9:58 AM, Anthony Hunter <anthonyh@xxxxxxxxxx> wrote:

Hi Michael,

For Helios, if your uml2tools Build needs to depend on both GMF Tooling and GMF Runtime, you only need to use the gmf-sdk from GMF Tooling as it packages the GMF Runtime as well (so it is 100% backward compatible with previous releases).

Anthony Hunter mailto:anthonyh@xxxxxxxxxx
Software Development Manager
IBM Rational Software: Aurora / Modeling Tools
Phone: 613-270-4613

Inactive hide details for Michael Golubev ---07/07/2010 09:22:34 AM---Sorry, just forwarding to mdt.devMichael Golubev ---07/07/2010 09:22:34 AM---Sorry, just forwarding to


Michael Golubev <borlander@xxxxxxxxx>


MDT developers <>


07/07/2010 09:22 AM


Fwd: [] Can MDT/OCL make MDT/UML2-Tools useable on Helios?

Sorry, just forwarding to

---------- Forwarded message ----------
Michael Golubev <borlander@xxxxxxxxx>
Date: Wed, Jul 7, 2010 at 3:20 PM
Subject: Re: [] Can MDT/OCL make MDT/UML2-Tools useable on Helios?
To: Kenn Hussey <


Thanks, much better now.
Still no luck yet,

I guess the main problem for now is that there are now 2 different gmf packs after GMF to GMP split, while the build continue to use only the one (gmf runtime one).
At least in the build.cfg ( there are no gmf tooling part.
I tried to check how ecore tools is built but they have already migrated to different build so their logs/cfgs seems to be not related.

Does anyone know how to fix that?

Thanks for you help,


On Wed, Jul 7, 2010 at 4:06 AM, Kenn Hussey <
kenn.hussey@xxxxxxxxx> wrote:

    From that log, it appeared that the version, branch, and javaHome variables were not being set correctly. When I looked in CVS at /modeling/mdt/uml2tools/build/_common.php I saw that the server name for the options that appear on the build page wasn't updated during the transition from to

    I made the correction, committed the file, updated the CVS copy on, and voila, the options are now appearing correctly on the build page. Do you want to try running the build again?



    On Tue, Jul 6, 2010 at 1:41 PM, Michael Golubev <borlander@xxxxxxxxx> wrote:

    Thanks Alex, but the problem with U2T build has nothing to do with any kind of credentials.
    E.g, here are results from the build I tried to spin yesterday:

    So at least simply redoing the same steps as a year ago doesn't work.



    On Tue, Jul 6, 2010 at 7:27 PM, Alexander Igdalov <alexander.igdalov@xxxxxxxxx> wrote:
      Hi Michael,

      I have just successfully logged on to the using the common MDT user credentials. I think here is all you need to launch the build.

      Go to

      Use the login/password file attached.

      Please let me know whether it suits you.

      - Alex.

      On Tue, Jul 6, 2010 at 12:41 PM, Ed Willink <ed@xxxxxxxxxxxxx> wrote:
      Hi Nick

      On 06/07/2010 15:33, Nick Boldt wrote:
          Possibly. But surely there's more value in having all the Modeling project builds using the same technology (namely, Buckminster) ?
      Indeed, I'm sure that's what most of us would do if we had to.
          Also, how did UML2 Tools miss Helios? It's not like the schedule was a secret, or that this is the first year there's been a coordinated release...
      Unfortunately MDT/UML2-Tools is dying because Borland have terminated their support; there has been no build since about M4. It is hoped that Papyrus will take over for Indigo, but in the interim we have a gap that causes at least significant user disappointment/concern and a dilemma about Helios adoption.

      We would therefore like a one-off Helios build. Migrating the build technology does not seem justified if the old technology can work. See Sergey's encouraging observation below.


              Ed Willink

      On 06/07/2010 17:24, Sergey Boyko wrote:

_______________________________________________ mailing list

_______________________________________________ mailing list

_______________________________________________ mailing list

GIF image

GIF image

Back to the top