Referencing a missing file results in "Stream Closed" exception, should identify missing file

Description

When including a changeLog from another changeLog, if the file does not exist, the error is less than helpful:

This can result in a lot of work to track down which file was referenced with an incorrect path and from where.

At a minimum, this should be caught because changeLogStream will be null YamlChangeLogParser.java:61, so throwing an exception there that identified that bad path would be helpful.

Even better would be identifying the file that contains the invalid include.

Environment

JDK 1.7, OS X

Activity

Show:

Details

Reporter

Components

Affects versions

Priority

Created April 8, 2014 at 2:55 PM
Updated April 8, 2014 at 2:55 PM