Hi Luciano,
There was some progress today. I added the retrotranslator-maven-plugin
(excerpt show below) to the pom.xml files for all modules. I was able to
build (including retrotranslation) with no problems with:
mvn clean install -Dtest=no
mvn -Peclipse eclipse:eclipse -Dtest=no
However, it's not as simple as only these two steps in maven. Even though
the modules will be retrotranslated with no problems, a user looking to
reproduce the workspace will still need to add the projects to Eclipse and
go through the steps in the retrotranslator_readme. This includes building
all projects in Eclipse which will unfortunately "undo" the retrotranslation
done with Maven. IMO it's still easier to run retrotranslator on the trunk
or workspace.
Additionally, the android sandbox would need to be integrated. Currently, it
is checked out separately and put together with the other modules until
projects are imported into Eclipse.
Below are the extra lines for the pom.xml files. I'm currently checking out
if the reflection and stripannot options are available in the plugin as they
are not documented in the plugin project page [1].
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>retrotranslator-maven-plugin</artifactId>
<executions>
<execution>
<phase>process-classes</phase>
<goals>
<goal>translate</goal>
</goals>
<configuration>
<filesets>
<fileset>
<directory>${project.build.outputDirectory}</directory>
<includes>
<include>**/*.class</include>
</includes>
</fileset>
</filesets>
<target>1.5</target>
<reflection>safe</reflection>
<stripannot>true</stripannot>
<verbose>true</verbose>
</configuration>
</execution>
</executions>
</plugin>
[1]
http://mojo.codehaus.org/retrotranslator-maven-plugin/translate-mojo.html
On Thu, Jul 17, 2008 at 7:37 PM, Luciano Resende <[EMAIL PROTECTED]>
wrote:
> Any progress on getting "these instructions" down to a simple maven
> command like :
>
> mvn clean install
> mvn -o -Peclipse eclipse:eclipse
>
>
>
--
best,
-oscar
Oscar Castañeda
