Feature #126

Bootstrap mechanism on easyant scripts

Added by Jean-Louis Boudart 3 months ago. Updated 3 months ago.

Status:Closed Start:06/11/2010
Priority:Urgent Due date:
Assigned to:Jason Trump % Done:

100%

Category:core
Target version:easyant-0.8
Votes: 0

Description

We recently introduced kind of bootstrap mechanism in easyant scripts (easyant.sh easyant.bat) to ease development on the core.

Instead of using fixed dependencies in a lib directory, the idea was to use ivy's main class to retrieve all required artifacts (latest easyant-core.jar + dependencies).

This works fine and strongly simplify development on core. By the way this resolution takes time and doesn't make sense for the end user.

Ideally this bootstrap mechanism should be used only for development. The end user should use a fixed set of dependencies (that doesn't require any resolve).


Related issues

related to Bug #133: bootstrap classpath in launch script contains absolute pa... Closed 07/04/2010 07/04/2010

Associated revisions

Revision 534
Added by Jason Trump 3 months ago

compute easyant-core classpath at build time, rather than runtime. also separate dist target from pre-integration-test phase for general cleanliness.
(refs 126)

History

Updated by Jason Trump 3 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 90

moved logic from launch scripts to build script. the launch scripts now have path tokens (e.g. unix.dist.path) that are substituted by the build script. will resolve the issue after hudson build passes and I've tested the generated archive on windows.

Updated by Jason Trump 3 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

build is good, scripts work fine on os x, windows, cygwin

Updated by Jean-Louis Boudart 3 months ago

  • Status changed from Resolved to Closed

Works fine on Ubuntu, Debia, Windows XP and Vista

Also available in: Atom PDF