Eclipse Community Forums: Plugin Development Environment (PDE) » Using different JDKs for Building my Application with ANT

Home » Eclipse Projects » Plugin Development Environment (PDE) » Using different JDKs for Building my Application with ANT

Show: Today's Messages :: Show Polls :: Message Navigator

Using different JDKs for Building my Application with ANT [message #509828]

Mon, 25 January 2010 14:45

Messages: 62
Registered: November 2009

Member

Hi,

I have some problems with the headless build of my application. At the moment I am building my application with some ant scripts and everything works well.

I would like to launch my application in German. Because of this I downloaded some babel language plug-ins and added some properties.

When I run the ant-scripts with the German babel plug-ins there are some problems and the application is in English and not in German.

I analyzed the problem and recognized that the jarsigner causes these problems.

In my build.properties I have the following code:

Quote:

signJars=true
sign.alias=abc
sign.keystore=${buildDirectory}/builder/.keystore
sign.storepass=ABCABC

The Jarsigner signs my own plug-ins and features correctly but overrides the Information in the Manifest.mf file of the language plug-ins.

I found out, that this bug is fixed with JDK 1.6.x.
Unfortunately I have to use JDK 1.5.x to build my application.

Is there any possibility to build my application with JDK 1.5. but sign the jars with JDK 1.6 ?

Report message to a moderator

Re: Using different JDKs for Building my Application with ANT [message #510327 is a reply to message #509828]

Wed, 27 January 2010 09:36

Peter Kullmann

Messages: 240
Registered: July 2009

Senior Member

You could sign the jars "by hand" when you use a customAssembly.xml
(this is from the thread "Headless signing just our JARs" by Ben Vitale
on this group):

<target name="post.gather.bin.parts">
<signjar alias="arenae.developer.key"
keystore="my.development.keystore"
storepass="pass" keypass="pass"
preservelastmodified="true" lazy="true" >
<path>
<fileset dir="${buildDirectory}/buildRepo/plugins">
<include name="**/ch.arenae.*.jar"/>
</fileset>
<fileset dir="${buildDirectory}/buildRepo/features"
includes="**/ch.arenae.*.jar" />
</path>
</signjar>
</target>

In this way you can control which jars are signed. Usually you don't
want to re-sign signed jars from eclipse.org.

Regards,
Peter

TW schrieb:
> Hi,
>
> I have some problems with the headless build of my application. At the
> moment I am building my application with some ant scripts and everything
> works well.
>
> I would like to launch my application in German. Because of this I
> downloaded some babel language plug-ins and added some properties.
> When I run the ant-scripts with the German babel plug-ins there are some
> problems and the application is in English and not in German.
> I analyzed the problem and recognized that the jarsigner causes these
> problems.
>
> In my build.properties I have the following code:
> Quote:
>> signJars=true
>> sign.alias=abc
>> sign.keystore=${buildDirectory}/builder/.keystore
>> sign.storepass=ABCABC
>
>
> The Jarsigner signs my own plug-ins and features correctly but overrides
> the Information in the Manifest.mf file of the language plug-ins.
>
> I found out, that this bug is fixed with JDK 1.6.x. Unfortunately I have
> to use JDK 1.5.x to build my application.
> Is there any possibility to build my application with JDK 1.5. but sign
> the jars with JDK 1.6 ?
>

Report message to a moderator

Previous Topic:	view need to other types of projects too
Next Topic:	Using different JDKs for Building my Application with ANT

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 21:11:06 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter