Eclipse Community Forums: M2T (model-to-text transformation) » [Acceleo 3] continuous integration on acceleo projects

Home » Modeling » M2T (model-to-text transformation) » [Acceleo 3] continuous integration on acceleo projects(automate acceleo project builds to use with a continuous integration server)

[Acceleo 3] continuous integration on acceleo projects [message #641129]

Wed, 24 November 2010 06:02

Eclipse User

Hi,

I want to set up a continuous integration server (hudson) to check the health of acceleo projects.

Let's take a classical configuration:

a source code management system (svn)
one (or several) project(s) with metamodel(s)
one (or several) acceleo project(s) with modules/templates
one (or several) project(s) with models used to test accede generation

What is continuous integration (CI)? If a commit occurs on the SVN, the CI server checks the latest revision (project sources) out, launches the build and the test suite.

In order to be able to do that with acceleo, I need to be able to build (outside eclipse) and package (jar) in an automated way acceleo projects. Then, I need to run acceleo projects on input models for test purposes.

What is the good way to do that?
Is an integration with maven possible?

Thanks,
Christophe.

Re: [Acceleo 3] continuous integration on acceleo projects [message #641139 is a reply to message #641129]

Wed, 24 November 2010 06:52

Eclipse User

Hello,
Continuous Integration is possible with maven :
First make a wrapper (Ant or maven) for acceleo compiler (packaged in AcceleoParser jar file).
Build your mtl files with this compiler.
Write a maven plugin for you acceleo project.
Use this plugin to generate code from your model

That's it

Sebastien

Re: [Acceleo 3] continuous integration on acceleo projects [message #641160 is a reply to message #641139]

Wed, 24 November 2010 08:11

Eclipse User

Sebastien Roy wrote on Wed, 24 November 2010 06:52

Hello,
Continuous Integration is possible with maven :
First make a wrapper (Ant or maven) for acceleo compiler (packaged in AcceleoParser jar file).

I saw there is already an ant task: http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.m2t/org .eclipse.acceleo/plugins/org.eclipse.acceleo.parser/src-ant/ org/eclipse/acceleo/parser/compiler/AcceleoCompiler.java?vie w=markup&revision=1.14&root=Modeling_Project
Is it usable?

Quote:

Build your mtl files with this compiler.
Write a maven plugin for you acceleo project.
Use this plugin to generate code from your model

What about dependencies? Is there a maven/ivy repository with acceleo and all its dependencies available? If not, is it possible to publish it?
If this is not possible, what are the required dependencies for a standalone execution of acceleo?

Regards,
Christophe.

Re: [Acceleo 3] continuous integration on acceleo projects [message #641354 is a reply to message #641160]

Thu, 25 November 2010 02:45

Eclipse User

This is a multi-part message in MIME format.
--------------020205030505000402010405
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Christophe,

I believe that Sebastien could help more than myself, since he managed
to get the compilation running standalone in his environment. I had
written this part of the FAQ :
http://wiki.eclipse.org/Acceleo/FAQ#How_can_I_compile_my_mtl _files_in_a_standalone_environment.3F
with information on this if it can help.

Laurent Goubet
Obeo

On 24/11/2010 14:11, Christophe Demarey wrote:
> Sebastien Roy wrote on Wed, 24 November 2010 06:52
>> Hello,
>> Continuous Integration is possible with maven :
>> First make a wrapper (Ant or maven) for acceleo compiler (packaged in
>> AcceleoParser jar file).
>
> I saw there is already an ant task:
> http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.m2t/org .eclipse.acceleo/plugins/org.eclipse.acceleo.parser/src-ant/ org/eclipse/acceleo/parser/compiler/AcceleoCompiler.java?vie w=markup&revision=1.14&root=Modeling_Project
>
> Is it usable?
>
> Quote:
>> Build your mtl files with this compiler.
>> Write a maven plugin for you acceleo project.
>> Use this plugin to generate code from your model
>
>
> What about dependencies? Is there a maven/ivy repository with acceleo
> and all its dependencies available? If not, is it possible to publish it?
> If this is not possible, what are the required dependencies for a
> standalone execution of acceleo?
>
> Regards,
> Christophe.

--------------020205030505000402010405
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="laurent_goubet.vcf"

YmVnaW46dmNhcmQNCmZuOkxhdXJlbnQgR291YmV0DQpuOkdvdWJldDtMYXVy ZW50DQpvcmc6
PGEgaHJlZj0iaHR0cDovL3d3dy5vYmVvLmZyIj5PYmVvPC9hPg0KZW1haWw7 aW50ZXJuZXQ6
bGF1cmVudC5nb3ViZXRAb2Jlby5mcg0KdXJsOmh0dHA6Ly93d3cub2Jlby5m cg0KdmVyc2lv
bjoyLjENCmVuZDp2Y2FyZA0KDQo=
--------------020205030505000402010405--

Re: [Acceleo 3] continuous integration on acceleo projects [message #641472 is a reply to message #641160]

Thu, 25 November 2010 10:33

Eclipse User

Hello,
I use the AcceleoCompiler class through a delegation mechanism.
The reason is to register the resources before actual execution of AcceleoCompiler task.

Here is my code :

public class MavenMtlCompiler extends AbstractMojo {
	
	/**
	 * @parameter property="sourceFolders"
	 */
	private String sourceFolders;
	
	AcceleoCompiler acceleoCompiler = new AcceleoCompiler();
	
	public MavenMtlCompiler() {
		
	}
	
	public void setSourceFolders(String value) {
		acceleoCompiler.setSourceFolders(value);
	}
		
	
    public void execute() throws MojoExecutionException {  
    	//displayClassPath();
    	registerLibraries();
    	acceleoCompiler.execute();
    }
    
	private void displayClassPath() {
        ClassLoader sysClassLoader = ClassLoader.getSystemClassLoader();

        //Get the URLs
        URL[] urls = ((URLClassLoader)this.getClass().getClassLoader()).getURLs();

        getLog().info("----------------------- Classpath --------------------");
        for(int i=0; i< urls.length; i++) {
            getLog().info(urls[i].getFile());
        }       		
        getLog().info("------------------------------------------------------");
		
	}    
    
    
    private void registerLibraries() {
		Resource.Factory.Registry.INSTANCE.getExtensionToFactoryMap().put("ecore", new EcoreResourceFactoryImpl());
		Resource.Factory.Registry.INSTANCE.getExtensionToFactoryMap().put("uml", UMLResource.Factory.INSTANCE);
		Resource.Factory.Registry.INSTANCE.getExtensionToFactoryMap().put("emtl", new EMtlResourceFactoryImpl());
		
		EPackage.Registry.INSTANCE.put(UMLPackage.eNS_URI, UMLPackage.eINSTANCE);
		EPackage.Registry.INSTANCE.put("http://www.eclipse.org/uml2/2.1.0/UML", UMLPackage.eINSTANCE);
		
		CodeSource acceleoModel = MtlPackage.class.getProtectionDomain().getCodeSource();
		if (acceleoModel != null) {
			String libraryLocation = acceleoModel.getLocation().toString();
			if (libraryLocation.endsWith(".jar")) {
				libraryLocation = "jar:" + libraryLocation + '!';
			}
			
			URIConverter.URI_MAP.put(URI.createURI("http://www.eclipse.org/acceleo/mtl/3.0/mtlstdlib.ecore"), URI.createURI(libraryLocation + "/model/mtlstdlib.ecore"));
			URIConverter.URI_MAP.put(URI.createURI("http://www.eclipse.org/acceleo/mtl/3.0/mtlnonstdlib.ecore"), URI.createURI(libraryLocation + "/model/mtlnonstdlib.ecore"));
		} else {
			getLog().error("Coudln't retrieve location of plugin 'org.eclipse.acceleo.model'.");
		}
    	
    }

}

I made my own maven repository with acceleo dependencies :

	<dependencies>
		<!-- Acceleo -->
		<dependency>
			<groupId>org.eclipse.acceleo</groupId>
			<artifactId>org.eclipse.acceleo.engine</artifactId>
			<version>${acceleoVersion}</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse.acceleo</groupId>
			<artifactId>org.eclipse.acceleo.model</artifactId>
			<version>${acceleoVersion}</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse.acceleo</groupId>
			<artifactId>org.eclipse.acceleo.common</artifactId>
			<version>${acceleoVersion}</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse.acceleo</groupId>
			<artifactId>org.eclipse.acceleo.parser</artifactId>
			<version>${acceleoVersion}</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse.acceleo</groupId>
			<artifactId>acceleoCompiler</artifactId>
			<version>${acceleoVersion}</version>
		</dependency>

		<!-- EMF -->
		<dependency>
			<groupId>org.eclipse.emf</groupId>
			<artifactId>org.eclipse.emf.ecore</artifactId>
			<version>${emfVersion260}</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse.emf</groupId>
			<artifactId>org.eclipse.emf.ecore.xmi</artifactId>
			<version>${emfVersion250}</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse.emf</groupId>
			<artifactId>org.eclipse.emf.common</artifactId>
			<version>${emfVersion260}</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse.emf</groupId>
			<artifactId>org.eclipse.emf.codegen.ecore</artifactId>
			<version>${emfVersion260}</version>
		</dependency>
		<!-- UML2 -->
		<dependency>
			<groupId>org.eclipse.uml2</groupId>
			<artifactId>org.eclipse.uml2.uml</artifactId>
			<version>${uml2UmlVersion}</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse.uml2</groupId>
			<artifactId>org.eclipse.uml2.common</artifactId>
			<version>${uml2CommonVersion}</version>
		</dependency>
		<!-- OCL -->
		<dependency>
			<groupId>org.eclipse.ocl</groupId>
			<artifactId>org.eclipse.ocl</artifactId>
			<version>${oclVersion}</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse.ocl</groupId>
			<artifactId>org.eclipse.ocl.ecore</artifactId>
			<version>${oclVersion}</version>
		</dependency>
		<!-- Eclipse -->
		<dependency>
			<groupId>org.eclipse.core</groupId>
			<artifactId>org.eclipse.core.runtime</artifactId>
			<version>${eclipseRuntimeVersion}</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse.equinox</groupId>
			<artifactId>org.eclipse.equinox.common</artifactId>
			<version>${equinoxVersion}</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse.equinox</groupId>
			<artifactId>org.eclipse.equinox.registry</artifactId>
			<version>${equinoxRegistryVersion}</version>
		</dependency>
		<dependency>
			<groupId>org.eclipse</groupId>
			<artifactId>org.eclipse.osgi</artifactId>
			<version>${osgiVersion}</version>
		</dependency>
		<!-- Misc -->
		<dependency>
			<groupId>net.sourceforge.lpg</groupId>
			<artifactId>lpg.runtime.java</artifactId>
			<version>${lpgVersion}</version>
		</dependency>
	</dependencies>

With the versions :

		<acceleoVersion>3.0.1.v201011180511</acceleoVersion>
		<emfVersion260>2.6.0.v20100614-1136</emfVersion260>
		<emfVersion250>2.5.0.v20100521-1846</emfVersion250>
		<uml2UmlVersion>3.1.0.v201006071150</uml2UmlVersion>
		<uml2CommonVersion>1.5.0.v201005031530</uml2CommonVersion>
		<oclVersion>3.0.0.v201005061704</oclVersion>
		<lpgVersion>2.0.17.v201004271640</lpgVersion>
		<osgiVersion>3.6.0.v20100517</osgiVersion>
		<equinoxVersion>3.6.0.v20100503</equinoxVersion>
		<equinoxRegistryVersion>3.5.0.v20100503</equinoxRegistryVersion>
		<eclipseRuntimeVersion>3.6.0.v20100505</eclipseRuntimeVersion>

Here is a script to deploy your packages (package must be present in the script directory):

set REPO=V:/mvn_rep/releases
set INSTALL=install:install-file
set DEPLOY=deploy:deploy-file
set TASK=%DEPLOY%
set COMMON_ARGS= %TASK% -Dpackaging=jar -DrepositoryId=starsRep -Durl=file:%REPO%

rem Acceleo
set ACCELEO_VERSION=3.0.1.v201011180511
set EMF_VERSION_260=2.6.0.v20100614-1136
set EMF_VERSION_250=2.5.0.v20100521-1846
set UML2_UML_VERSION=3.1.0.v201006071150
set UML2_COMMON_VERSION=1.5.0.v201005031530
set OCL_VERSION=3.0.0.v201005061704
set LPG_VERSION=2.0.17.v201004271640
set OSGI_VERSION=3.6.0.v20100517
set EQUINOX_VERSION=3.6.0.v20100503
set EQUINOX_REGISTRY_VERSION=3.5.0.v20100503
set ECLIPSE_RUNTIME_VERSION=3.6.0.v20100505

call mvn %COMMON_ARGS% -DgroupId=org.eclipse.acceleo -DartifactId=org.eclipse.acceleo.engine -Dversion=%ACCELEO_VERSION% -Dfile=org.eclipse.acceleo.engine_%ACCELEO_VERSION%.jar 
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.acceleo -DartifactId=org.eclipse.acceleo.model -Dversion=%ACCELEO_VERSION% -Dfile=org.eclipse.acceleo.model_%ACCELEO_VERSION%.jar
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.acceleo -DartifactId=org.eclipse.acceleo.parser -Dversion=%ACCELEO_VERSION% -Dfile=org.eclipse.acceleo.parser_%ACCELEO_VERSION%.jar
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.acceleo -DartifactId=org.eclipse.acceleo.common -Dversion=%ACCELEO_VERSION% -Dfile=org.eclipse.acceleo.common_%ACCELEO_VERSION%.jar
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.acceleo -DartifactId=acceleoCompiler -Dversion=%ACCELEO_VERSION% -Dfile=acceleoCompiler_%ACCELEO_VERSION%.jar
rem uml2
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.uml2 -DartifactId=org.eclipse.uml2.uml -Dversion=%UML2_UML_VERSION% -Dfile=org.eclipse.uml2.uml_%UML2_UML_VERSION%.jar 
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.uml2 -DartifactId=org.eclipse.uml2.common -Dversion=%UML2_COMMON_VERSION% -Dfile=org.eclipse.uml2.common_%UML2_COMMON_VERSION%.jar

rem emf
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.emf -DartifactId=org.eclipse.emf.common -Dversion=%EMF_VERSION_260% -Dfile=org.eclipse.emf.common_%EMF_VERSION_260%.jar
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.emf -DartifactId=org.eclipse.emf.ecore -Dversion=%EMF_VERSION_260% -Dfile=org.eclipse.emf.ecore_%EMF_VERSION_260%.jar
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.emf -DartifactId=org.eclipse.emf.ecore.xmi -Dversion=%EMF_VERSION_250% -Dfile=org.eclipse.emf.ecore.xmi_%EMF_VERSION_250%.jar
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.emf -DartifactId=org.eclipse.emf.codegen.ecore -Dversion=%EMF_VERSION_260% -Dfile=org.eclipse.emf.codegen.ecore_%EMF_VERSION_260%.jar

rem ocl
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.ocl -DartifactId=org.eclipse.ocl.ecore -Dversion=%OCL_VERSION% -Dfile=org.eclipse.ocl.ecore_%OCL_VERSION%.jar
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.ocl -DartifactId=org.eclipse.ocl -Dversion=%OCL_VERSION% -Dfile=org.eclipse.ocl_%OCL_VERSION%.jar
rem misc
call mvn %COMMON_ARGS% -DgroupId=net.sourceforge.lpg -DartifactId=lpg.runtime.java -Dversion=%LPG_VERSION% -Dfile=lpg.runtime.java_%LPG_VERSION%.jar
rem osgi
call mvn %COMMON_ARGS% -DgroupId=org.eclipse -DartifactId=org.eclipse.osgi -Dversion=%OSGI_VERSION% -Dfile=org.eclipse.osgi_%OSGI_VERSION%.jar
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.core -DartifactId=org.eclipse.core.runtime -Dversion=%ECLIPSE_RUNTIME_VERSION% -Dfile=org.eclipse.core.runtime_%ECLIPSE_RUNTIME_VERSION%.jar
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.equinox -DartifactId=org.eclipse.equinox.common -Dversion=%EQUINOX_VERSION% -Dfile=org.eclipse.equinox.common_%EQUINOX_VERSION%.jar
call mvn %COMMON_ARGS% -DgroupId=org.eclipse.equinox -DartifactId=org.eclipse.equinox.registry -Dversion=%EQUINOX_REGISTRY_VERSION% -Dfile=org.eclipse.equinox.registry_%EQUINOX_REGISTRY_VERSION%.jar

I hope it will help

Re: [Acceleo 3] continuous integration on acceleo projects [message #643882 is a reply to message #641129]

Wed, 08 December 2010 10:32

Eclipse User

Hi,

Thanks for all the posts on this topic, I also am trying to set up a hudson CI build to

1) compile the MTL files
2) compile associated .java files
3) execute the code generator

using this thread and an earlier one I have almost achieved the goal.

final issue is that my source .uml file "MyModel.uml" references another .uml file that is an associated profile - "MyProfile.uml".

When executing the code generator (using the exec:java plugin for maven and the acceleo 'Generate.class' file for my templates) I get an error:

"Package with uri 'http:///schemas/MyProfile/_uxGMcPi2Ed-z3tfFFpxgGA/0' not found. (file:.../MyModel.uml)"

of course everything works fine from within eclipse. My guess is that the profile needs to be registered...but is not all the needed info in the MyModel.uml file?

what am I missing?

many thanks

Re: [Acceleo 3] continuous integration on acceleo projects [message #643888 is a reply to message #643882]

Wed, 08 December 2010 10:37

Eclipse User

This is a multi-part message in MIME format.
--------------030906040605020506050308
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

We've had a few people ask here how to use Acceleo in standalone with
profiled UML models ... And I must admit I don't know the exact things
that are to be done in order to register UML profiles. You should ask
this on the eclipse.modeling.mdt.uml newsgroup.

When you do get a valid answer on this point, could you point me to the
exact code needed for the registration for further reference?

Laurent Goubet
Obeo

On 08/12/2010 16:32, D.H.Akehurst wrote:
> Hi,
>
> Thanks for all the posts on this topic, I also am trying to set up a
> hudson CI build to
>
> 1) compile the MTL files
> 2) compile associated .java files
> 3) execute the code generator
>
>
> using this thread and an earlier one I have almost achieved the goal.
>
> final issue is that my source .uml file "MyModel.uml" references another
> .uml file that is an associated profile - "MyProfile.uml".
>
> When executing the code generator (using the exec:java plugin for maven
> and the acceleo 'Generate.class' file for my templates) I get an error:
>
> "Package with uri 'http:///schemas/MyProfile/_uxGMcPi2Ed-z3tfFFpxgGA/0'
> not found. (file:.../MyModel.uml)"
>
> of course everything works fine from within eclipse. My guess is that
> the profile needs to be registered...but is not all the needed info in
> the MyModel.uml file?
>
> what am I missing?
>
> many thanks

--------------030906040605020506050308
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="laurent_goubet.vcf"

YmVnaW46dmNhcmQNCmZuOkxhdXJlbnQgR291YmV0DQpuOkdvdWJldDtMYXVy ZW50DQpvcmc6
PGEgaHJlZj0iaHR0cDovL3d3dy5vYmVvLmZyIj5PYmVvPC9hPg0KZW1haWw7 aW50ZXJuZXQ6
bGF1cmVudC5nb3ViZXRAb2Jlby5mcg0KdXJsOmh0dHA6Ly93d3cub2Jlby5m cg0KdmVyc2lv
bjoyLjENCmVuZDp2Y2FyZA0KDQo=
--------------030906040605020506050308--

Re: [Acceleo 3] continuous integration on acceleo projects [message #643914 is a reply to message #641129]

Wed, 08 December 2010 11:55

Eclipse User

It appears that you don't need to do anything different to register a profile.

Provided there is a full path name to the main model.

The acceleo Generate.java:main method takes two arguments. The first is the filename of the model to generate over. When this is a relative path, it can't find the referenced profile, when it is a full path name, the profile is found fine.

Re: [Acceleo 3] continuous integration on acceleo projects [message #644046 is a reply to message #643914]

Thu, 09 December 2010 03:45

Eclipse User

This is a multi-part message in MIME format.
--------------060403030504020903010006
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

And thanks, at least this gives me a potential answer for the people
who'll come after you :).

Laurent Goubet
Obeo

On 08/12/2010 17:55, D.H.Akehurst wrote:
> It appears that you don't need to do anything different to register a
> profile.
>
> Provided there is a full path name to the main model.
>
> The acceleo Generate.java:main method takes two arguments. The first is
> the filename of the model to generate over. When this is a relative
> path, it can't find the referenced profile, when it is a full path name,
> the profile is found fine.
>
>

--------------060403030504020903010006
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="laurent_goubet.vcf"

YmVnaW46dmNhcmQNCmZuOkxhdXJlbnQgR291YmV0DQpuOkdvdWJldDtMYXVy ZW50DQpvcmc6
PGEgaHJlZj0iaHR0cDovL3d3dy5vYmVvLmZyIj5PYmVvPC9hPg0KZW1haWw7 aW50ZXJuZXQ6
bGF1cmVudC5nb3ViZXRAb2Jlby5mcg0KdXJsOmh0dHA6Ly93d3cub2Jlby5m cg0KdmVyc2lv
bjoyLjENCmVuZDp2Y2FyZA0KDQo=
--------------060403030504020903010006--

Re: [Acceleo 3] continuous integration on acceleo projects [message #644149 is a reply to message #644046]

Thu, 09 December 2010 11:53

Eclipse User

Hi Laurent

This may be another symptom of Bug 318137 and/or Bug 306692.

Regards

Ed

On 09/12/2010 08:45, Laurent Goubet wrote:
> Hi,
>
> And thanks, at least this gives me a potential answer for the people
> who'll come after you :).
>
> Laurent Goubet
> Obeo
>
> On 08/12/2010 17:55, D.H.Akehurst wrote:
>> It appears that you don't need to do anything different to register a
>> profile.
>>
>> Provided there is a full path name to the main model.
>>
>> The acceleo Generate.java:main method takes two arguments. The first is
>> the filename of the model to generate over. When this is a relative
>> path, it can't find the referenced profile, when it is a full path name,
>> the profile is found fine.
>>
>>
>

Re: [Acceleo 3] continuous integration on acceleo projects [message #644782 is a reply to message #644149]

Tue, 14 December 2010 03:44

Eclipse User

This is a multi-part message in MIME format.
--------------090500000401050007070608
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Ed,

Doesn't look like it.

Laurent Goubet
Obeo

On 09/12/2010 17:53, Ed Willink wrote:
> Hi Laurent
>
> This may be another symptom of Bug 318137 and/or Bug 306692.
>
> Regards
>
> Ed
>
> On 09/12/2010 08:45, Laurent Goubet wrote:
>> Hi,
>>
>> And thanks, at least this gives me a potential answer for the people
>> who'll come after you :).
>>
>> Laurent Goubet
>> Obeo
>>
>> On 08/12/2010 17:55, D.H.Akehurst wrote:
>>> It appears that you don't need to do anything different to register a
>>> profile.
>>>
>>> Provided there is a full path name to the main model.
>>>
>>> The acceleo Generate.java:main method takes two arguments. The first is
>>> the filename of the model to generate over. When this is a relative
>>> path, it can't find the referenced profile, when it is a full path name,
>>> the profile is found fine.
>>>
>>>
>>
>

--------------090500000401050007070608
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="laurent_goubet.vcf"

YmVnaW46dmNhcmQNCmZuOkxhdXJlbnQgR291YmV0DQpuOkdvdWJldDtMYXVy ZW50DQpvcmc6
PGEgaHJlZj0iaHR0cDovL3d3dy5vYmVvLmZyIj5PYmVvPC9hPg0KZW1haWw7 aW50ZXJuZXQ6
bGF1cmVudC5nb3ViZXRAb2Jlby5mcg0KdXJsOmh0dHA6Ly93d3cub2Jlby5m cg0KdmVyc2lv
bjoyLjENCmVuZDp2Y2FyZA0KDQo=
--------------090500000401050007070608--

Previous Topic:	Acceleo Compiler
Next Topic:	[Acceleo] Nested model transformation

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 06 22:34:28 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter