> ==== important
>
> (1)
> in the impl jar, file META-INF/standard-faces-config.xml has a few
> component entries like this:
>     <property>
>          <description>
>                 &lt;p&gt;
>                 The URL of the image. If the URL starts with a '/', it
> is relative
>                 to the context path of the web application.
>                 &lt;/p&gt;
>                 &lt;p&gt;
>                 This attribute is an alias for the "value" property.
>                 &lt;/p&gt;
>
>             </description>
>          <property-name>url</property-name>
>          <property-class>java.lang.String</property-class>
>       </property>
>
> Will this cause problems? I don't know what the "description" field in a
> standard-faces-config file is used for..

that is only for DT important.
Not sure, if there will ever be a spec/RI for the dt things,
but it is not effected to RT.

>
> (2)
> Can we please hava a CLIRR report to check for binary incompatibilities?
>
> See clirr.sourceforge.net
>
> ==== less important
>
> (3)
> Normally in commons, the following entries are also added to manifests:
> x-java-source
> X-java-target
> so that it is clear which versions of java this is compatible with.
>
> Neither the shared, api nor impl jars have these entries.
>
> The bytecode version in the classes is 49, ie java5 which is fine.
>
> (4)
> The MANIFEST.MF file for the shared-core-sources has no version info at
> all.
>
> (5)
> The api jar has a strange META-INF/rsc subdirectory.
>
> (6)
> the impl jar has "myfaces_core.tld" but "myfaces-html.tld".

? both are in. I don't get this message.

I also noticed that there where Notice/License files missing
in api-test.
and there is no javadoc.jar

but these are minor... to me.

-Matthias

>
> Not a problem AFAIK, but a little inconsistent.
>
>
>
>
> Nothing else significant that I can see in the binaries.
>
> Apart from the oddity in the standard-faces-config (which might not
> actually cause a problem) none of the above seems worth blocking a
> release for.
>
> BTW, is there going to be a tgz "download bundle"? If so, do you have a
> link to the RC for that?
>
> Regards,
>
> Simon
>
>
>
>



-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org

Reply via email to