Hi Ralph: AFAIK, we can release without problems. But if a xalan version is needed we can request the xalan project for a release.
I already requested for a release to the commons-lang project. They promised a release, but I will remeber them about that. WDYT? Best Regards, Antonio Gallardo. Ralph Goers dijo: > I'm curious about this for a completely different reason. It has been > the stated policy that every attempt will be made to use only formally > released third-party jars in formal releases of Cocoon. Does this mean > that 2.1.6 cannot be released until Xalan 2.6.1 is released? If not, > please make the source this jar was built from available on the Cocoon > site. > > Ralph > > Niclas Hedhman wrote: > >>Your talk is not entirely reflected by the actions of the community. I >> just >>did a svn up on the 2.1 branch; >> >>A lib/endorsed/xalan-2.6.1-dev-20041008T0304.jar >>D lib/endorsed/xalan-2.6.0.jar >> >>Why does the 2.1 branch require a timestamped/snapshot version of Xalan, >> if >>everything is so fine and dandy with it? >>Antonio makes the following motivation in the commit message; >>"Update xalan to 2.6.1-dev-20041008T0304" >> >>Just curious. >>Niclas >> >> >
