JiBX

ant default task doesn't build jars correctly

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: JiBX 1.1
  • Fix Version/s: JiBX 1.1.2
  • Component/s: core
  • Labels:
    None
  • Environment:
    Linux 2.4.20-8, ant 1.6.5, java 1.5.0_02
  • Number of attachments :
    0

Description

When trying to do a new build from a fresh download (I downloaded and extracted jibx_1_1.zip from sourceforge), if I go to the "build" subdirectory and just type "ant", it invokes the "current" task as its default. However, because this task doesn't have a dependency on the "basenames" target, the properies "bindname", "runname" and "extrasname" never get set, so I end up with:

lib/$

{bindname}

.jar
lib/$

{runname}

.jar
lib/$

{extrasname}

.jar

instead of jibx-bind.jar, jibx-run.jar, jibx-extras.jar, etc.

The "distrib" task works fine. I don't quite follow the intent of the "current" taks, but normally I'd expect "ant" by itself to produce something useful.

Activity

Hide
Permalink
Dennis Sosnoski added a comment -

Fixed this in the current CVS code. The default "current" task just builds the jars without running the full set of tests. That's perhaps not as useful as some of the other targets, but at least it should work now.

Show
Dennis Sosnoski added a comment - Fixed this in the current CVS code. The default "current" task just builds the jars without running the full set of tests. That's perhaps not as useful as some of the other targets, but at least it should work now.

People

  • Assignee:
    Dennis Sosnoski
    Reporter:
    Joshua Davies
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: