Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7869277
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 3, 20262026-06-03T01:16:07+00:00 2026-06-03T01:16:07+00:00

Our build process constructs several products out of a relatively small set of plugins.

  • 0

Our build process constructs several products out of a relatively small set of plugins. To trigger the build, we have an Ant file that just iterates through the names of the products, like so:

    <for list="all,client1,client1_64,client2,client2_64,rob" param="feature">
        <sequential>
            <java jar="${eclipse.launcher}" fork="true" dir="${basedir}" failonerror="true">
                <arg value="-application" />
                <arg value="org.eclipse.ant.core.antRunner" />
                <arg value="-buildfile" />
                <arg value="${eclipse.pde.build}/scripts/productBuild/productBuild.xml" />
                <arg value="-DbaseLocation=${eclipse.dir}" />
                <arg value="-Dproduct=${feature.dir}/@{feature}/my.product" />
                <arg value="-DbuildLabel=@{feature}-${build.timestamp}" />
                <arg value="-DbuildId=My_@{feature}_${release.name}-${build.timestamp}" />
                <arg value="-Dtimestamp=${release.name}-${build.timestamp}" />
                <arg value="-DbuildDirectory=${build.dir}" />
            </java>
        </sequential>
    </for>

Not surprisingly perhaps, the ‘all’ product includes every one of our plugins, the others some subset. My problem is that each iteration through this loop recompiles and packages every plugin, throwing out work that was done previously. Not a big deal at a couple of products, but now most of our build time is spent recompiling and packaging plugins.

Can someone point me to a better way of making the build process build plugins only once as all these products are packaged?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-03T01:16:09+00:00Added an answer on June 3, 2026 at 1:16 am

    Since the “all” product includes everything, I would suggest breaking it out separate from the other products.

    Once the “all” product is built, you can take the output of that and make it available to the other product builds. If your “all” product build is producing p2 metadata, you can use repoBaseLocation and transformedRepoLocation, otherwise you can use pluginPath.

    For the subsequent product builds, use a new empty buildDirectory so that they don’t see the source for the bundles, only the binary output from the “all” product. If everything these products need is available in binary form, then no compilation will be necessary and these builds essentially become packaging operations.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

As part of our web application's build process, I have set up our XSLT
I am currently migrating our build process from Eclipse/Ant to Maven/M2Eclipse/Artifactory. I have a
We are using ANT for our build process and don't have plans to change
I have been tasked with automating our build process with msbuild. We have about
Currently i have a build process in place for all of our apps using
OUR CURRENT BUILD PROCESS We're a small team of developers (2 to 4 people
As part of our build process we have to create an Access ACCDB (2007)
I am trying to revamp our build process, which is currently a gigantic Ant
Lately, I have been trying to automate our build process on Amazon EC2 and
During our build process, we run sqlldr to populate our database with some sample

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.