[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] Building non-Java code, with Project-specific Builders
|
Hi Igor,
thanks for the clear reply.
Having quickly looked at the ATL compiler code, it does not seem to be easlity runnable outside of Eclipse. I'll take this matter up with the ATL community.
Cheers,
Anders
-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
Sent: den 5 mars 2012 11:15
To: tycho-user@xxxxxxxxxxx
Subject: Re: [tycho-user] Building non-Java code, with Project-specific Builders
Tycho does not start eclipse workspace during the build and there is no way to do this. The "right" solution here would be to implement maven "mojo" that generates the code, but I don't know if this is feasible or not.
--
Regards,
Igor
On 12-03-05 4:58 AM, Anders Olsson X wrote:
> Hi,
> We've got a set of plugins, that we've gotten to build into a P2
> Repository fairly easily. However we're realized that we have non-java
> code in the plug-in that aren't being built. More specifically, it's
> ATL code that need to be built into ASM modules. See:
> _http://www.eclipse.org/atl/_ for info on ATL.
> Normally, these modules are built by the ATL builder, and normally not
> checked into source control, since it's marked 'derived'. Our ATL
> projects are also plugin projects and have the following natures:
> org.eclipse.jdt.core.javanature, org.eclipse.pde.PluginNature &
> org.eclipse.m2m.atl.adt.builder.atlNature . And the following builders:
> org.eclipse.jdt.core.javabuilder, org.eclipse.pde.ManifestBuilder,
> org.eclipse.pde.SchemaBuilder & org.eclipse.m2m.atl.adt.builder.atlBuilder .
> Is there any support in Tycho for building with using Eclipse builders?
> As for as I've seem, there's no headless application for calling the
> ATL compiler.
> If it's not possible to do this through Maven/Tycho, is it feasible to
> start an Eclipse instance for a while, so the workspace gets
> completely build? Sounds a bit brittle. An alternative is also to
> check the ASM modules in to source control, but that's risky, since
> you might end up with unbuilt ASM, if you edit the ATL files outside
> of Eclipse, or with automatic build turned of.
> Is this simply a case where Buckminster is better suited for the job?
> Best Regards,
> Anders
>
>
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
