Bug 55766 - Xslt task to allow use of catalog properties file
Summary: Xslt task to allow use of catalog properties file
Status: NEW
Alias: None
Product: Ant
Classification: Unclassified
Component: Core tasks (show other bugs)
Version: 1.9.4
Hardware: PC All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Ant Notifications List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-11 12:32 UTC by Richard K
Modified: 2014-05-06 03:20 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard K 2013-11-11 12:32:03 UTC
Currently Ant's xslt task's xmlcatalog parameter element takes as its contents the location of the XML catalog file to be used.

The resolver itself (resolver.jar) can take a property file, typically called CatalogManager.properties.  Using this mechanism via Saxon (via a Java task) the resolver jar's location and the location of the property file are passed in.  Using it via Ant's xslt task the locations of the resolver and the catalog itself are passed in.
In Saxon if a catalog is to be used the location of the catalog is held within the properties file.

I should like to be able to use a properties file when accessing XSLT via the xslt task.  My particular reason for this is that among the properties which may be set is a verbosity setting for the diagnostics.  At the moment I am having considerable problems getting the catalog to work and I would like to set the verbosity so that I can see from the resolver itself whether it is active and what it thinks it is doing.
Comment 1 Antoine Levy-Lambert 2013-12-23 17:57:53 UTC
would you like to create a patch for this bug report ?