|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Is there a headless feature fur running MWE2 workflows? [message #1067933 is a reply to message #1067771] |
Thu, 11 July 2013 10:44 |
Marcel Abou Khalil Messages: 15 Registered: July 2013 |
Junior Member |
|
|
My local workflow is:
- Clone Repository
- Import existing project into Eclipse
- Run MWE2 Workflow
- Run Unit Tests
This works fine but the MWE2 Workflow has dependencies on classes in my project (Generator and GeneratorFragment). Eclipse seems to not mind much. I guess it performs a partial build as soon as you import the project, showing errors for everything it couldn't build but allows the use of classes for the MWE2 workflow that were fine.
In Buckminster (from what I understand) a build is either complete or it fails. So I can't tell Buckminster to build it but ignore all errors, then run the MWE2 workflow with everything that was built successfully and then build again, this time not ignoring any errors. Is my understanding correct?
[Updated on: Thu, 11 July 2013 10:45] Report message to a moderator
|
|
|
Re: Is there a headless feature fur running MWE2 workflows? [message #1068415 is a reply to message #1067933] |
Sat, 13 July 2013 07:44 |
|
Hi Marcel
see comments inline
On 11/07/2013 12:44, Marcel Abou Khalil wrote:
> My local workflow is:
>
>
> Clone Repository
> Import existing project into Eclipse
> Run MWE2 Workflow
> Run Unit Tests
>
>
> This works fine but the MWE2 Workflow has dependencies on classes in my
> project (Generator and GeneratorFragment). Eclipse seems to not mind
> much. I guess it performs a partial build as soon as you import the
> project, showing errors for everything it couldn't build but allows the
> use of classes that were fine in the MWE2 workflow.
>
you could put Generator and GeneratorFragment into a separate project.
These classes do not depend on the classes that MWE2 Workflow generates,
do they? They do not have dependencies on the Xtext projects either, do
they?
You could do a first buckminster run: import this separate bundle and
build it.
Then you do another buckminster run which imports the other projects,
launch the MWE2 workflow etc.
(of course you might want to first try this as a local workflow in Eclipse).
If on the contrary, by cyclic dependency you actually mean that
Generator actually depends on the generated classes, then I wouldn't
know how to do that...
> In Buckminster (from what I understand) a build is either complete or it
> fails. So I can't tell Buckminster to build it, ignore all errors, then
> run the MWE2 workflow with everything that was built successfully and
> then build again, this time not ignoring any errors. Is my understanding
> correct?
When you tell buckminster to "build" does it create the .class files for
your Generator and GeneratorFragment? If it does, you could run
buckminster a second time to execute MWE2 workflow and then go on...
By the way, would it really be a problem to put the generated sources in
the git repository? I usually prefer to put them in the repo, and also
many other (including the Xtext guys).
hope this helps
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
|
Powered by
FUDForum. Page generated in 0.04818 seconds