Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cross-project-issues-dev] Building update jars

Thanks, David and I just got through IMing about this and we'll switch over now (which also will solve a similar bug we have regarding duplicate src.zips
Of course, it would still be nice if basebuilder would transparently produce the pack200 jars as well, imo.

From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent: Wednesday, May 03, 2006 12:46 PM
To: Cross project issues
Cc: Cross project issues; cross-project-issues-dev-bounces@xxxxxxxxxxx
Subject: Re: [cross-project-issues-dev] Building update jars

The build.update.jar target generated in build.xml for plugin and feature is deprecated and should not be used (see bug #139268).
In order to produce jars for an update site you should be setting the property called outputUpdateJars

Richard Gronback <richard.gronback@xxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

05/03/2006 12:18 PM

Please respond to
Cross project issues

Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
[cross-project-issues-dev] Building update jars

As I mentioned on the call, the generated build scripts for
plugins/features from pde basebuilder includes a build.update.jar target
(see generated build.xml for your features/plugins).  This is what the
GMF build uses (and I assumed most/all projects used).

To me, the pack200 steps could be included in what's generated by the
basebuilder (although honestly, I haven't looked into the details of it

In a customTarget.xml file, you can call this target using something
like this:

<!-- ===================================================================== -->
   <!-- Steps to do after the build is done. -->
   <!-- ===================================================================== -->
   <target name="postBuild">
       <antcall target="gatherLogs" />
       <!-- A temporary directory leftover? -->
       <delete dir="${buildDirectory}/org.eclipse.gmf"
       <antcall target="publish"/>      
       <antcall target="generateUpdateSite"/>
   <!-- ===================================================================== -->
   <!-- Update the update site. -->
   <!-- ===================================================================== -->  
   <target name="generateUpdateSite">
         <!-- Create the directory structure -->
         <mkdir dir="${buildUpdateSitePath}/features"/>
         <mkdir dir="${buildUpdateSitePath}/plugins"/>
         <!-- Build the jar files -->
         <antcall target="allElements">
           <param name="genericTargets"
           <param name="target" value="updateSiteExport"/>
   <target name="updateSiteExport">
     <ant antfile="build.xml" dir="${buildDirectory}/features/${id}/"
       <property name="feature.destination"
       <property name="plugin.destination"
         <!-- Override the default temp.folder location, as it is too deep by default               on Windows, causing missing files in jars. -->
         <property name="temp.folder" value="${buildRoot}/temp.folder"/>

I'll post this to the tips section on the wiki.

cross-project-issues-dev mailing list

Back to the top