| Xtext generator vs. buckminster: chickens/eggs and deadlocks... [message #553958] |
Thu, 19 August 2010 14:06  |
 Daniel Weber
Messages: 51
Registered: July 2009 |
Member |
|
|
Hi there,
I am trying to automate builds for an Xtext (1.0.0 i.e. Helios) based project. When trying to run the MWE2 workflow using a buckminster action (using jdt.ant and a script based on [1]), I ran into the first issue. In order to execute a workflow, MWE2 needs it to be on the classpath. So I added an extra build step before running the generator so that the Eclipse build will take care of copying the .mwe2 file to bin/. So far so good, builds worked, Hudson was happy :)
Now that our project evolved, there is code referencing generated classes. From time to time, this makes the initial Eclipse build fail (e.g. if new classes are introduced which are only available after code generation) and buckminster will abort the build and refuse to start the generator. Then I'm stuck with failing builds since only running the generator would solve the compilation errors.
Did anyone set something similar up? We do not submit generated code to the depot, the build should take care of generating everything necessary.
Can I tell buckminster to continue even if an error occurred? This way it could call the generator, followed by an incremental build and then see...
Any help would be greatly appreciated :)
Thanks in advance,
Daniel
[1] http://blogs.itemis.de/feltes/2010/07/02/how-to-run-xtext-an d-other-mwe2-workflows-with-ant/
|
|
|
| Re: Xtext generator vs. buckminster: chickens/eggs and deadlocks... [message #554881 is a reply to message #553958] |
Tue, 24 August 2010 15:24  |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
I will check if we have helped someone set this up.
Regards
- henrik
On 8/19/10 4:06 PM, Daniel Weber wrote:
> Hi there,
>
> I am trying to automate builds for an Xtext (1.0.0 i.e. Helios) based
> project. When trying to run the MWE2 workflow using a buckminster action
> (using jdt.ant and a script based on [1]), I ran into the first issue.
> In order to execute a workflow, MWE2 needs it to be on the classpath. So
> I added an extra build step before running the generator so that the
> Eclipse build will take care of copying the .mwe2 file to bin/. So far
> so good, builds worked, Hudson was happy :)
>
> Now that our project evolved, there is code referencing generated
> classes. From time to time, this makes the initial Eclipse build fail
> (e.g. if new classes are introduced which are only available after code
> generation) and buckminster will abort the build and refuse to start the
> generator. Then I'm stuck with failing builds since only running the
> generator would solve the compilation errors.
>
> Did anyone set something similar up? We do not submit generated code to
> the depot, the build should take care of generating everything necessary.
> Can I tell buckminster to continue even if an error occurred? This way
> it could call the generator, followed by an incremental build and then
> see...
>
> Any help would be greatly appreciated :)
>
> Thanks in advance,
> Daniel
>
>
> [1]
> http://blogs.itemis.de/feltes/2010/07/02/how-to-run-xtext-an d-other-mwe2-workflows-with-ant/
>
|
|
|
| Re: Xtext generator vs. buckminster: chickens/eggs and deadlocks... [message #554972 is a reply to message #554881] |
Wed, 25 August 2010 02:18 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Did you look into using buckminster generator components? There is the
notion of components that are generated - I.e one component has an
action that produces a component that does not otherwise exist.
- henrik
Henrik Lindberg <henrik.lindberg@cloudsmith.com> wrote:
> I will check if we have helped someone set this up.
> Regards
> - henrik
> On 8/19/10 4:06 PM, Daniel Weber wrote:
>> Hi there,
>>
>> I am trying to automate builds for an Xtext (1.0.0 i.e. Helios) based
>> project. When trying to run the MWE2 workflow using a buckminster
> > action
>> (using jdt.ant and a script based on [1]), I ran into the first
> > issue.
>> In order to execute a workflow, MWE2 needs it to be on the classpath.
> > So
>> I added an extra build step before running the generator so that the
>> Eclipse build will take care of copying the .mwe2 file to bin/. So
> > far
>> so good, builds worked, Hudson was happy :)
>>
>> Now that our project evolved, there is code referencing generated
>> classes. From time to time, this makes the initial Eclipse build fail
>> (e.g. if new classes are introduced which are only available after
> > code
>> generation) and buckminster will abort the build and refuse to start
> > the
>> generator. Then I'm stuck with failing builds since only running the
>> generator would solve the compilation errors.
>>
>> Did anyone set something similar up? We do not submit generated code
> > to
>> the depot, the build should take care of generating everything
> > necessary.
>> Can I tell buckminster to continue even if an error occurred? This
> > way
>> it could call the generator, followed by an incremental build and
> > then
>> see...
>>
>> Any help would be greatly appreciated :)
>>
>> Thanks in advance,
>> Daniel
>>
>>
>> [1]
>> http://blogs.itemis.de/feltes/2010/07/02/how-to-run-xtext-an d-other-mwe2-workflows-with-ant/
>>
--
- henrik
|
|
|
|
Powered by
FUDForum. Page generated in 0.04367 seconds
] 
Search
Help
Register
Login
Home
