Re: [GUMP] Build Failure - jakarta-taglibs-standard

[Christopher Lenz <cm...@gmx.de>]

Hi all,

I'm investigating an integration problem detected by Gump:

Ted Husted wrote:
> ----------------------------------------------------
> This email is autogenerated from the output from:
> <http://cvs.apache.org/builds/gump/2003-04-07/jakarta-taglibs-standard.html>
> ----------------------------------------------------

[snip]

> compileJaxp12:
>      [echo] java.home /usr/java/j2sdk1.4.1_02/jre
>      [echo] xalan.jar /home/rubys/jakarta/xml-xalan/java/build/xalan.jar
>     [javac] Compiling 235 source files to /home/rubys/jakarta/jakarta-taglibs/build/standard/standard
>     [javac] /home/rubys/jakarta/jakarta-taglibs/standard/src/org/apache/taglibs/standard/extra/spath/SPathFilter.java:113: cannot resolve symbol
>     [javac] symbol  : method getDefaultMethodProperties (java.lang.String)
>     [javac] location: class org.apache.xalan.templates.OutputProperties
>     [javac] 	    (OutputProperties.getDefaultMethodProperties("xml"));
>     [javac]                              ^
>     [javac] Note: /home/rubys/jakarta/jakarta-taglibs/standard/src/org/apache/taglibs/standard/tag/common/core/ParamSupport.java uses or overrides a deprecated API.
>     [javac] Note: Recompile with -deprecation for details.
>     [javac] 1 error
> 
> BUILD FAILED
> /home/rubys/jakarta/jakarta-taglibs/standard/build.xml:133: Compile failed; see the compiler error output for details.
> 
> Total time: 12 seconds

Apparently, the cause of this failure is this change:

   <http://marc.theaimsgroup.com/?l=xalan-cvs&m=104922819625557&w=2>

which removed the public method getDefaultMethodProperties(String) of 
the class org.apache.xalan.templates.OutputProperties, or rather moved 
the method to the org.apache.xml.serializer.OutputPropertiesFactory 
class (IIUC).

Now, the Jakarta-Taglibs "Standard" Tag-Library is using that method in 
org.apache.taglibs.standard.extra.spath.SPathFilter, which is causing 
the Gump failure above.

This raises several questions:

1) If the OutputProperties class is considered public API, shouldn't the 
method be deprecated and potentially reimplemented using delegation 
before it gets removed?

2) If the OutputProperties class is *not* considered public API, where 
is this documented?

3) As an extension of case #2, if the SPathFilter is misusing an 
internal API, could the usage be replaced with an equivalent from a 
public API?

4) The entire SPath package looks very old (and this failure was the 
first time I even noticed it). Is it maybe obsolete and should be moved 
into the Attic?

-chris