On 26 May 2011, at 10:06, Onkar Shinde <[email protected]> wrote:

> On Wed, May 25, 2011 at 10:06 PM, Damien Raude-Morvan
> <[email protected]> wrote:
>> Hi Tony,
>> 
>> On Wed, 25 May 2011 08:34:29 -0700, tony mancill <[email protected]>
>> wrote:
>>> It might be better that it's not named jstl.jar, as it doesn't seem to
>>> provide
>>> all of the classes that other JARs floating around with that name
>> provide.
>>> Specifically, I was hoping that wiring up Tomcat to this JAR would solve
>>> the
>>> issue with the tag plugin examples in tomcat6-examples and
>> tomcat7-examples
>>> (#606768).  But tomcat still needs something to provide the
>>> javax.servlet.jsp.jstl.* classes.
>> 
>> JFTR, I know two things named "JSTL" :
>> 
>> - javax.servlet.jsp.jstl.* (JavaServer Pages Standard Tag Library)
>>  - http://mvnrepository.com/artifact/jstl/jstl/1.1.2
>>  - Homepage: http://java.sun.com/products/jsp/jstl/
>> 
>> - org.apache.taglibs.standard.* (Apache Standard Taglib)
>>  - http://mvnrepository.com/artifact/taglibs/standard/1.0.6
>>  - Homepage: http://tomcat.apache.org/taglibs/index.html
> 
> The link with title 'Apache Standard Taglib' on the second page
> actually leads to a download which contains both Apache Standard
> Taglib (standard.jar) and reference implementation of JSTL (jstl.jar)
> http://tomcat.apache.org/taglibs/standard/
> 
> I have a half-done package of this taglib I mention lying on my
> machine. The package builds fine but I haven't completed the
> debian/copyright file. I will try to complete it over weekend and
> upload it on mentors.d.n for sponsorship. Worst case I will at least
> push everything to SVN/GIT so that someone else can continue.


I also did some packaging work on this as part of the work I have done on 
Jenkins

It's probably worth versioning the library in the same way that jsp and servlet 
are e.g libjstl1.1-java for the 1.1 spec.

My packaging work can be found here http://launchpad.net/~hudson-ubuntu under 
the code section.

HTH

James





--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to