Eclipse Community Forums: M2T (model-to-text transformation) » [Acceleo] A question on building product with Maven/Tycho

Home » Modeling » M2T (model-to-text transformation) » [Acceleo] A question on building product with Maven/Tycho

[Acceleo] A question on building product with Maven/Tycho [message #1815593]

Sun, 06 October 2019 11:14

Eclipse User

Dear Acceleo experts,

I have created a Sirius-based DSL editor and associated model transformation with Acceleo and Acceleo UI. I looked for documentation for building a product and found the following section.

https://wiki.eclipse.org/Acceleo/User_Guide#Building_an_Acceleo_generator_with_Maven_and_Tycho

It talks about adding an optional dependency to MANIFEST.MF and generate POMs. The generated POM contains the following part.

 <repositories>
    <repository>
      <id>Indigo Release</id>
      <url>https://raw.github.com/eclipse/acceleo/master/maven/repository/releases/indigo</url>
    </repository>
	<repository>
      <id>Juno Release</id>
      <url>https://raw.github.com/eclipse/acceleo/master/maven/repository/releases/juno</url>
    </repository>
	<repository>
      <id>Snapshots</id>
      <url>https://raw.github.com/eclipse/acceleo/master/maven/repository/snapshots</url>
    </repository>
 </repositories>

Indigo and Juno are old releases. Is the above still valid? I hope the section would be updated soon. And, if there are any recent examples or explanations, please let us know.

Best regards,
Akira

Re: [Acceleo] A question on building product with Maven/Tycho [message #1815598 is a reply to message #1815593]

Sun, 06 October 2019 16:24

Eclipse User

Hi

I strongly recommend that you reconsider what you build manually and what you build automatically.

IIRC from when I was trying to build Acceleo using Buckminster, it is really hard because you are trying to empathize with something that just does magic things remotely. I gave up and treated the Acceleo outputs just like primary source artefacts in GIT for downstream builds.

Maven and Tycho can execute locally so debugging is a bit easier, but the file paths change to include a "target/...." duplicate which is likely to make Acceleo's broken URI resolution even more temperamental.

I really wouldn't waste your time trying to do the near impossible and arguably also the irresponsible. IMHO many auto-generated artefacts should only change for a release, not every build and when they change the change may need API compatibility tweaks. Just not possible with an auto break-the-API Maven re-build.

Regards

Ed Willink

Re: [Acceleo] A question on building product with Maven/Tycho [message #1815606 is a reply to message #1815598]

Mon, 07 October 2019 01:30

Eclipse User

Thank you very much for your recommendation. I will then consider a simpler solution.

Best,
Akira

Re: [Acceleo] A question on building product with Maven/Tycho [message #1815650 is a reply to message #1815606]

Mon, 07 October 2019 16:12

Eclipse User

Hi

To be clear, when I recommend manual building, I do not mean interactive commands. Rather a script, I prefer MWE2, but you might prefer ANT, can be launched to perform the requisite auto-generation predictably and on demand.

Regards

Ed Willink

Previous Topic:	Parsing OCL constraints in Acceleo
Next Topic:	Code Generation via NLP

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jun 15 21:05:04 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter