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

[Anthony Hunter <anthonyh@xxxxxxxxxx>]

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).

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


Michael Golubev ---07/07/2010 09:22:34 AM---Sorry, just forwarding to mdt.dev

From:	Michael Golubev <borlander@xxxxxxxxx>
To:	MDT developers <mdt.dev@xxxxxxxxxxx>
Date:	07/07/2010 09:22 AM
Subject:	Fwd: [mdt.dev] Can MDT/OCL make MDT/UML2-Tools useable on Helios?

---

Sorry, just forwarding to mdt.dev

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


Hello, 

Thanks, much better now. 
Still no luck yet, http://modeling.eclipse.org/modeling/mdt/uml2tools/downloads/drops/0.9.0/N201007070520/buildlog.txt

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 (http://modeling.eclipse.org/modeling/mdt/uml2tools/downloads/drops/0.9.0/N201007070520/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, 
Regards.
Michael


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

Michael,

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 emft.eclipse.org to modeling.eclipse.org.

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

Cheers,

Kenn


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

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: http://modeling.eclipse.org/modeling/mdt/uml2tools/downloads/drops/N201007052144/buildlog.txt.

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

Regards,
Michael



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 modeling.eclipse.org using the common MDT user credentials. I think here is all you need to launch the build.

Go to http://modeling.eclipse.org/modeling/mdt/uml2tools/build/

Use the login/password file attached.

Please let me know whether it suits you.

HTH,
- 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.

    Regards

        Ed Willink


On 06/07/2010 17:24, Sergey Boyko wrote:
Hi,
 
Some times ago I wrote to Michael G. that recently I successfully produced QVTo maintenance build using our old build infrastructure (via http://modeling.eclipse.org/modeling/m2m/qvtoml/build/) and even promote worked as before (one click, no need to ssh ;).
 
So I suggest to try easiest solution with old build infrastructure (ask Nick Bold about possible problems with http://modeling.eclipse.org/modeling/mdt/uml2tools/build/).  Could it be that simply login/password are expired?
 
Regards,
  Sergey.

_______________________________________________
mdt.dev mailing list
mdt.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt.dev