Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#1307 closed defect (fixed)

External dependencies throw error and are sometimes not included.

Reported by: Michael Schall Owned by: jkuhnert
Priority: high Milestone:
Component: BuildTools Version: 0.3
Keywords: Cc:
Blocked By: Blocking:

Description

With latest from dojo and mochikit, the following profile reports

compress:
    [echo] profileFile: profiles/atg_framework.profile.js
  [concat] File C:PROJECTSThirdPartydojouildscriptsConversionError: does not exist.
  [concat] File C:PROJECTSThirdPartydojouildscriptsThe does not exist.
  [concat] File C:PROJECTSThirdPartydojouildscriptsundefined does not exist.
  [concat] File C:PROJECTSThirdPartydojouildscriptsvalue does not exist.
  [concat] File C:PROJECTSThirdPartydojouildscriptshas does not exist.
  [concat] File C:PROJECTSThirdPartydojouildscripts
o does not exist.
  [concat] File C:PROJECTSThirdPartydojouildscriptsproperties. does not exist.

However responses with a BUILD SUCCESSFUL. If I include more of the MochiKit? files ("MochiKit?.Logging", "MochiKit?.DateTime?", "MochiKit?.DOM"), Base and the addition files will be included in the build, however the error remains.

var dependencies = [
       "dojo.widget.*",
       "dojo.io.*",
       "dojo.event.*",
       "dojo.date",
       "dojo.validate",
       "dojo.collections.ArrayList",
       "MochiKit.Base"
];

dependencies.prefixes = [
      ['MochiKit', '../mochikit/MochiKit']
];
load("getDependencyList.js");

Change History (6)

comment:1 Changed 13 years ago by dylan

Milestone: 0.4
Version: 0.40.3

comment:2 Changed 13 years ago by Adam Peller

I suspect we should be using failOnError="true" for our Java tasks to prevent this sort of error from compounding in the build.

comment:3 Changed 13 years ago by dylan

Owner: changed from alex to JesseKuhnert

comment:4 Changed 13 years ago by dylan

Owner: changed from JesseKuhnert to jkuhnert

comment:5 Changed 13 years ago by jkuhnert

Resolution: fixed
Status: newclosed

This should be fixed in the latest trunk code. Any build time errors that are possible to catch are properly caught and output meaningful error statements. (as much as we've been able to at least)

comment:6 Changed 13 years ago by (none)

Milestone: 0.4

Milestone 0.4 deleted

Note: See TracTickets for help on using tickets.