Use Advanced Search to search the entire archive.
[jsr363-experts] Re: "External" JAR compiling
- From: Werner Keil <
>
- To: "
" <
>
- Subject: [jsr363-experts] Re: "External" JAR compiling
- Date: Tue, 3 Feb 2015 01:04:35 +0100
Profiles could be one approach.
See more onn compiler args including a different rt.jar here
http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html
Tamaya raised my attention to Maven Toolchains, another option to decide
between different JVMs and various options.
This Codehaus list of various toolchains
http://docs.codehaus.org/display/MAVEN/Toolchains
even mentions a "J2ME Plugin"
http://mojo.codehaus.org/j2me-maven-plugin/howto.html but I have no idea,
if that might do us any good with Java ME 8. Worth a look anyway.
Werner
On Tue, Feb 3, 2015 at 12:56 AM, Martin Desruisseaux <
>
wrote:
>
Le 03/02/15 00:50, Leonardo Lima a écrit :
>
>
> Yes!
>
>
>
> Using a specific .jar instead of the default "rt.jar" from the JDK.
>
>
with javac?
>
>
If this is about using an other "rt.jar" file when compiling the code
>
with javac, then you want to set the "bootstrap classpath". This can be
>
done in Maven with a profile like below:
>
>
<profiles>
>
<profile>
>
<activation>
>
<property>
>
<name>bootclasspath</name>
>
</property>
>
</activation>
>
<build>
>
<plugins>
>
<plugin>
>
<artifactId>maven-compiler-plugin</artifactId>
>
<configuration>
>
<compilerArgs>
>
<arg>-bootclasspath</arg>
>
<arg>${bootclasspath}</arg>
>
</compilerArgs>
>
</configuration>
>
</plugin>
>
</plugins>
>
</build>
>
</profile>
>
</profiles>
>
>
Then, when launching Maven, just pass the
>
-Dbootclasspath=/path/to/your/rt.jar option to Maven.
>
>
Martin
>
>