Tobias
Thanks for the suggestion. The link provided a nice elaboration about the candidate architecture.
I am still exploring what I want, i.e. my requirements.
At this moment I am working with the following strategy.
-
First generate code with maven(+tycho) for the Eclipse plugins that contain EMF models.
-
Generate POM’s for the new created eclipse plugins.
-
Run a (2nd ) normal maven(tycho) build to build the application
I wrote a Maven plugin, so that for the developer still uses the regular maven commands, e.g. mvn verify.
The maven plugin executes the above steps. This works for pilot1.
Regards Martien
Van: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx]
Namens Oberlies, Tobias
Verzonden: Thursday, February 27, 2014 4:34 PM
Aan: Tycho user list
Onderwerp: Re: [tycho-user] Howto extending the source path used by Tycho?
Hi Martin,
It seems to me that you want this feature:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=425737
If this is the case, just vote for it and/or add yourself on CC to be notified about any changes to the issue (e.g. change of the target milestone, etc.)
Regards
Tobias
Hi all,
For a project I generate code from an ecore model from within maven.
So I need to “inform” Tycho about the source directory of the generated java code.
One option is to update the build.properties and point to the directory with the generated java code.
That works.
I can of course also copy the code.
The option that I preferred is to inform Tycho through the pom.xml about the additional source directory.
So I used build-helper-maven-plugin to tell maven about the additional directory with java code.
Below is the plugin configuration.
My conclusion (after running “maven compile –X”) is that Tycho only looks at the
source directories specified in build.properties and ignore the addition source directories that
provided with the build-helper-maven-plugin.
Is there an way to inform Tycho through the pom.xml ?
Regards Martien
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<version>1.8</version>
<executions>
<execution>
<phase>process-sources</phase>
<goals>
<goal>add-source</goal>
</goals>
<configuration>
<sources>
<source>../workspaceGen/${project.artifactId}/src</source>
</sources>
</configuration>
</execution>
</executions>
</plugin>