Command line building with antRunner and "external" in bundle-classpath [message #334062] |
Sat, 17 January 2009 01:09 ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Nadeem Aboobaker![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=nadeem.aboobaker%40oracle.com) Messages: 20 Registered: July 2009 |
Junior Member |
|
|
Hi all,
I have an Ant command line build for my plugins using the
org.eclipse.ant.core.antRunner application. Everything was working great
until now. I had to create a plugin that has code that depends on jars
specified by using the "external" keyword in the MANIFEST.MF
Bundle-ClassPath entry. Additionally, the location of the jars is
specified by a variable:
Bundle-ClassPath: external:$jar.location$/jarA.jar,
external:$jar.location$/jarB.jar,
external:$jar.location$/jarC.jar
The first problem is the scarcity of documentation on the "external"
keyword, which almost seems to be intentional since it probably should be
used as a last resort. The second problem is that I can't find any
documentation about how to do a build with antRunner when plugins use
"external" in the MANIFEST.MF
I can get the build to work if I replace $jar.location$ with the actual
location (i.e., c:/jar/location). But I can't figure out how to get it
work with the variable. The build fails when it finds something that
references classes in the jar files.
I've tried from the command line, calling java using the
-Djar.location=... vm arg, and I've tried various things in my Ant build
script (using <java> to launch, <sysproperty> or <jvmarg> or <arg> to set
the value). No luck.
Any ideas?
Thanks,
Nadeem
|
|
|
Re: Command line building with antRunner and "external" in bundle-classpath [message #334089 is a reply to message #334062] |
Tue, 20 January 2009 00:16 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Nadeem Aboobaker![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=nadeem.aboobaker%40oracle.com) Messages: 20 Registered: July 2009 |
Junior Member |
|
|
I was able to get my build working by temporarily copying a MANIFEST.MF
with the variable expanded into the plugin, running the build, and then
restoring the MANIFEST.MF with the variable.
While this works, it isn't exactly a clean solution. Any help?
Thanks,
Nadeem
Nadeem wrote:
> Hi all,
> I have an Ant command line build for my plugins using the
> org.eclipse.ant.core.antRunner application. Everything was working great
> until now. I had to create a plugin that has code that depends on jars
> specified by using the "external" keyword in the MANIFEST.MF
> Bundle-ClassPath entry. Additionally, the location of the jars is
> specified by a variable:
> Bundle-ClassPath: external:$jar.location$/jarA.jar,
> external:$jar.location$/jarB.jar,
> external:$jar.location$/jarC.jar
> The first problem is the scarcity of documentation on the "external"
> keyword, which almost seems to be intentional since it probably should be
> used as a last resort. The second problem is that I can't find any
> documentation about how to do a build with antRunner when plugins use
> "external" in the MANIFEST.MF
> I can get the build to work if I replace $jar.location$ with the actual
> location (i.e., c:/jar/location). But I can't figure out how to get it
> work with the variable. The build fails when it finds something that
> references classes in the jar files.
> I've tried from the command line, calling java using the
> -Djar.location=... vm arg, and I've tried various things in my Ant build
> script (using <java> to launch, <sysproperty> or <jvmarg> or <arg> to set
> the value). No luck.
> Any ideas?
> Thanks,
> Nadeem
|
|
|
|
Powered by
FUDForum. Page generated in 0.03151 seconds