Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [emft-dev] MWE dependencies was Re: [dash-dev] Hudson build jobs dependencies

Hi Sven,

My only usage is for my converted pre1.0.0 xtext projects. When I try to launch an mwe2 for the first time, I get a msg saying "please put bundle ..emf.mwe2.launch on your project's classpath". As you say, I couldn't see any reason why there had to be a runtime or build time dependency on MWE2, but I assumed that there had to be a reason, so I just threw it into my required bundles. I guess I should just put it into my .classpath instead?

In a previous attempt at the build before I went to trying to get the lcoal builds, I used the milestones, and that gave me everything but ..launch, so my guess is that that will do the trick.



On Apr 6, 2010, at 11:17 AM, Sven Efftinge wrote:

Hi Miles,

neither Xtext nor Xpand have a dependency to the mwe2 language (including the launch bundle as well as the editor bundle).
At least not a mandatory java compile time dependency. This is because we would run into bootstrapping problems, since mwe2 language is built on and therefore needs Xtext.
What we have a dependency on is mwe2 runtime, which is a slim library mainly containing the IWorkflowComponent interface.

The build order is as follows:

What exactly are you looking for? Which java classes do you need at compile time?


On Apr 6, 2010, at 7:55 PM, Miles Parker wrote:

Hi all,

Please see below for context.

Where should I be getting the MWE2 launch and runtime plugins?

The integration dependencies that are listed on the xtext and xpand dependencies are only snapshots and in any case they are dead links.

On Apr 6, 2010, at 8:30 AM, David Carver wrote:

The problem here is that none of those files are archived for cbi-emft-mwe-0.7.   If you go and visit:

You will notice that there is no ZIP files listed in the archived artifacts for the build.  Only the build.cfg file is listed there.  So the link you tried to use returns a 404 error because it can't find the requested files.

OK, I thought that I couldn't see the file because of an external security issue, i.e. that the builder could access the files form within hudson but not from an external source. So the next question is why these dependencies work for Xtext and not for me. 


On 04/05/2010 10:23 PM, Miles Parker wrote:
Hi guys,

I've just updated my dependencies to use xtext, mwe, and xpand 1.0.0, and I'm having a real time of it trying to get the new dependencies. I tried the regular download sites, but I think that the MWE2 stuff is only available on the hudson build system itself (?) So I thought I'd just follow the xpand and xtext setup but that doesn't seem to be working for me either..

I just copied the depdendency URLs from the xtext build..

And stuck them in mine:


But I get:

/opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/org.eclipse.dash.common.releng/tools/scripts/buildAllHelper.xml:3176: Can't get to /opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/workspace/build/downloads/

Should this be as straightforward as it looks, or am I perhaps just missing some kind of setup that is needed to make consuming other hudson build artifacts work?



_______________________________________________ dash-dev mailing list dash-dev@xxxxxxxxxxx

dash-dev mailing list

emft-dev mailing list

emft-dev mailing list

Back to the top