Board index » Android Coding Problems » SDK/ADT/Emulator Problems

Skip to content

Problem using external APIS

Common bugs/problems with the Android SDK the Emulator and the ADT-Plugin.
Post a reply

Problem using external APIS

Postby Helios » Wed Feb 18, 2009 10:07 pm

Hi everyone, I have the following problem. I am trying to create an application that uses external java classes which I can build correctly in a separate eclipse java project. The problem is, that in order to build this classes I have to import the jaxb-api.jar which causes a building problem when I import it to my android project. To solve this, I am trying to use the "retrotranslator" which as I understand using compiled java classes generates a .jar file which can be used on an android application. My problem is that I tried using this tool but I couldn't generate the .jar file. Does any one knows how to do this? (I have already read the retrotranslator manual I mean something less general)

I have read that you can use a build.xml file like the one below, but I don't understand how to do this.

Thanks in advance.

Regards,
Helios

Syntax: [ Download ] [ Hide ]
Using xml Syntax Highlighting
  1. <!--
  2. You may freely edit this file. See commented blocks below for
  3. -->
  4. <!-- some examples of how to customize the build. -->
  5. −
  6. <!--
  7. (If you delete it and reopen the project it will be recreated.)
  8. -->
  9. −
  10. <project name="JAXB_Android" default="default" basedir=".">
  11. <description>Builds, tests, and runs the project JAXB Android.</description>
  12. <import file="nbproject/build-impl.xml"/>
  13. −
  14. <!--
  15.  
  16.  
  17.    There exist several targets which are by default empty and which can be
  18.    used for execution of your tasks. These targets are usually executed
  19.    before and after some main targets. They are:
  20.  
  21.      -pre-init:                 called before initialization of project properties
  22.      -post-init:                called after initialization of project properties
  23.      -pre-compile:              called before javac compilation
  24.      -post-compile:             called after javac compilation
  25.      -pre-compile-single:       called before javac compilation of single file
  26.      -post-compile-single:      called after javac compilation of single file
  27.      -pre-compile-test:         called before javac compilation of JUnit tests
  28.      -post-compile-test:        called after javac compilation of JUnit tests
  29.      -pre-compile-test-single:  called before javac compilation of single JUnit test
  30.      -post-compile-test-single: called after javac compilation of single JUunit test
  31.      -pre-jar:                  called before JAR building
  32.      -post-jar:                 called after JAR building
  33.      -post-clean:               called after cleaning build products
  34.  
  35.    (Targets beginning with '-' are not intended to be called on their own.)
  36.  
  37.    Example of inserting an obfuscator after compilation could look like this:
  38.  
  39.        <target name="-post-compile">
  40.            <obfuscate>
  41.                <fileset dir="${build.classes.dir}"/>
  42.            </obfuscate>
  43.        </target>
  44.  
  45.    For list of available properties check the imported
  46.    nbproject/build-impl.xml file.
  47.  
  48.  
  49.    Another way to customize the build is by overriding existing main targets.
  50.    The targets of interest are:
  51.  
  52.      -init-macrodef-javac:     defines macro for javac compilation
  53.      -init-macrodef-junit:     defines macro for junit execution
  54.      -init-macrodef-debug:     defines macro for class debugging
  55.      -init-macrodef-java:      defines macro for class execution
  56.      -do-jar-with-manifest:    JAR building (if you are using a manifest)
  57.      -do-jar-without-manifest: JAR building (if you are not using a manifest)
  58.      run:                      execution of project
  59.      -javadoc-build:           Javadoc generation
  60.      test-report:              JUnit report generation
  61.  
  62.    An example of overriding the target for project execution could look like this:
  63.  
  64.        <target name="run" depends="JAXB_Android-impl.jar">
  65.            <exec dir="bin" executable="launcher.exe">
  66.                <arg file="${dist.jar}"/>
  67.            </exec>
  68.         </target>      
  69.    Notice that the overridden target depends on the jar target and not only on
  70.    the compile target as the regular run target does. Again, for a list of available
  71.    properties which you can use, check the target you are overriding in the
  72.    nbproject/build-impl.xml file.
  73.  
  74.    
  75. -->
  76. −
  77. <target name="-post-compile" depends="-do-compile">
  78. <property name="original-classes" value="${build.classes.dir}/original-classes"/>
  79. <property name="outdir-classes" value="${build.classes.dir}"/>
  80. −
  81. <move todir="${original-classes}">
  82. <fileset dir="${outdir-classes}"/>
  83. </move>
  84. <mkdir dir="${outdir-classes}"/>
  85. −
  86. <taskdef name="retrotranslator" classname="net.sf.retrotranslator.transformer.RetrotranslatorTask">
  87. −
  88. <classpath>
  89. <fileset dir="Retrotranslator-1.2.6-bin" includes="*.jar"/>
  90. </classpath>
  91. </taskdef>
  92. <retrotranslator target="1.5" embed="support" reflection="safe" stripannot="true" srcdir="${original-classes}" destdir="${outdir-classes}"/>
  93. </target>
  94. </project>
  95.  
Parsed in 0.004 seconds, using GeSHi 1.0.8.4
Helios
Junior Developer
Junior Developer
 
Posts: 23
Joined: Sat Jan 17, 2009 7:11 am
Top
Top
Post a reply

Return to SDK/ADT/Emulator Problems

Who is online

Users browsing this forum: No registered users and 38 guests

Board index The team • Delete all board cookies • All times are UTC + 1 hour