You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by David Nuescheler <da...@gmail.com> on 2005/02/12 12:04:04 UTC
Fwd: JSR 170: Proposed Final Draft
Hi all,
After quite a bit of licensing discussions I am
happy to report on behalf of the JSR-170 Expert
Group that the "Content Repository API for Java
Technology" Specification has made the next
important step towards its completion.
During this stage according to JCP 2.6 we will
complete the "Reference Implementation" (RI)
and the "Technology Compatibility Kit" (TCK)
which both are under development here in
the jackrabbit project.
Now that the latest version is publically
available I would like to invite everybody to
give us feedback with respect to inconsistencies
or other deficiencies in the spec that may come
up during the implementation or the development
of the TCK, and send those to:
jsr-170-comments@jcp.org
Any feedback is very welcome.
During the completion of the TCK and RI
we will publish updates to the specification
containing minor fixes in the specification
honouring (public) feedback.
I would like to thank everyone for their
contributions and enthusiasm so far and
I am looking forward to see jackrabbit run
faster and further.
regards,
david
---------- Forwarded message ----------
From: Harold Ogle <Ha...@sun.com>
Date: Fri, 11 Feb 2005 09:35:05 -0800
Subject: JSR 170: Proposed Final Draft
To: JCP-INTEREST@java.sun.com
The Expert Group of the following specification:
JSR-000170 Content Repository for Java technology API
has published a Proposed Final Draft.
View the list of Proposed Final Drafts here:
http://jcp.org/en/jsr/stage?listBy=proposed
The Proposed Final Draft is linked from the status table on the JSR
170 detail page:
http://jcp.org/en/jsr/detail?id=170
"Specifies a standard API to access content repositories in Java 2
independently of implementation."
===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the body
of the message "signoff JCP-INTEREST". For general help, send email to
listserv@java.sun.com and include in the body of the message "help".
--
----------------------------------------------------------------------
standardize your content-repository !
http://www.jcp.org/en/jsr/detail?id=170
---------------------------------------< david.nuescheler@day.com >---
This message is a private communication. If you are not the intended
recipient, please do not read, copy, or use it, and do not disclose it
to others. Please notify the sender of the delivery error by replying
to this message, and then delete it from your system. Thank you.
The sender does not assume any liability for timely, trouble free,
complete, virus free, secure, error free or uninterrupted arrival of
this e-mail. For verification please request a hard copy version.
mailto:david.nuescheler@day.com
http://www.day.com
David Nuescheler
Chief Technology Officer
Day Software AG
Barfuesserplatz 6 / Postfach
4001 Basel
Switzerland
T 41 61 226 98 98
F 41 61 226 98 97
Re: BadXSLT in maven.xml
Posted by shannen <sh...@hotmail.com>.
Just want to let the maven developers know that this fails with maven 1.1 beta
release.
I had to reinstall maven 1.02 to buil jackrabbit project...
- shannen -
Re: BadXSLT in maven.xml
Posted by Manoj Prasad <ma...@yahoo.com>.
That worked! Thanks, Jukka.
Yes, I am using JDK 1.5 and I would recommend updating
the README.txt file to include this additional step.
Regards,
Manoj
--- Jukka Zitting <jz...@yukatan.fi> wrote:
> Hi Manoj,
>
> You wrote:
> > I'm eager to try this out, but I'm getting the
> > following build error:
> > [...]
> > I figure it's related to the BadXSLT comment in
> > maven.xml, but not sure how to fix it.
>
> Are you using JDK 1.5?
>
> I believe you are experiencing the exact same
> problem that we had about
> a month ago. It's a known issue with no good
> solution. A workaround is
> to download the Xalan binaries and place xalan.jar
> in
> $MAVEN_HOME/lib/endorsed. For more details, please
> check the longer
> message included below.
>
> PS. Should we place this issue in Jira or in an FAQ?
>
> Best regards,
>
> Jukka Zitting
>
> ----
>
> Hi all,
>
> <summary>
> Place xalan.jar in $MAVEN_HOME/lib/endorsed to build
> the latest (since
> 2004-12-22) Jackrabbit sources with JDK 1.5.
> </summary>
>
> Below is a description of the details of the
> problem. I hope someone
> finds this useful.
>
> I ran into the same problem as Oliver Kiessler after
> updating my source
> tree. I'd like to keep using JDK 1.5, so I first
> traced the problem to
> the following lines in maven.xml (line breaks added
> for clarity):
>
> <!-- The following is a hack to get xslt work with
> maven
> (See: http://maven.apache.org/faq.html#BadXSLT
> ) -->
> ${systemScope.setProperty(
> 'javax.xml.transform.TransformerFactory',
>
>
'org.apache.xalan.processor.TransformerFactoryImpl')}
>
> The JavaCC grammar in src/grammar/xpath makes heavy
> use of XSLT, and the
> following ant:xslt entries in maven.xml handle the
> transformations:
>
> <ant:xslt style="src/grammar/xpath/strip.xsl"
>
> in="src/grammar/xpath/xpath-grammar.xml"
>
> out="src/grammar/xpath/stripped-xpath-grammar.xml"
> force="yes">
> </ant:xslt>
> <ant:xslt
> style="src/grammar/xpath/jjtree-jackrabbit.xsl"
>
> in="src/grammar/xpath/stripped-xpath-grammar.xml"
> out="src/grammar/xpath/XPath.jjt"
> force="yes">
> </ant:xslt>
>
> The systemScope.setProperty() hack is needed to make
> the ant:xslt task
> work properly with Maven (see [1]). However, as
> mentioned in the
> comments of the associated bug entry [2], this hack
> doesn't work with
> JDK 1.5 that uses the new Xalan XSLTC compiler at
>
com.sum.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.
>
> Unfortunately the problem could not be solved by
> simply changing the
> systemScope.setProperty() line because the XSLTC
> version bundled with
> JDK 1.5 has problems with named templates (probably
> bug [3]). Instead of
> the "provider not found" errors from ant:xslt, I now
> received
> NoSuchMethodError exceptions from XSLTC.
>
> As an alternative solution, I then downloaded the
> normal Xalan binaries
> and placed xalan.jar in $MAVEN_HOME/lib/endorsed. I
> was then able to run
> maven jar without problems. Note that the library
> needs to be placed in
> lib/endorsed instead of just lib to make the Xalan
> classes visible for
> the ant:xslt task.
>
> Although this solution is a bit of a hack, I don't
> think a better one is
> possible until either the Maven problem gets solved
> or the JDK XSLTC
> gets fixed.
>
> BR,
>
> Jukka Zitting
>
> [1] http://maven.apache.org/faq.html#BadXSLT
> [2]
>
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-156
> [3] http://issues.apache.org/jira/browse/XALANJ-1994
>
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
Re: BadXSLT in maven.xml
Posted by Jukka Zitting <jz...@yukatan.fi>.
Hi Manoj,
You wrote:
> I'm eager to try this out, but I'm getting the
> following build error:
> [...]
> I figure it's related to the BadXSLT comment in
> maven.xml, but not sure how to fix it.
Are you using JDK 1.5?
I believe you are experiencing the exact same problem that we had about
a month ago. It's a known issue with no good solution. A workaround is
to download the Xalan binaries and place xalan.jar in
$MAVEN_HOME/lib/endorsed. For more details, please check the longer
message included below.
PS. Should we place this issue in Jira or in an FAQ?
Best regards,
Jukka Zitting
----
Hi all,
<summary>
Place xalan.jar in $MAVEN_HOME/lib/endorsed to build the latest (since
2004-12-22) Jackrabbit sources with JDK 1.5.
</summary>
Below is a description of the details of the problem. I hope someone
finds this useful.
I ran into the same problem as Oliver Kiessler after updating my source
tree. I'd like to keep using JDK 1.5, so I first traced the problem to
the following lines in maven.xml (line breaks added for clarity):
<!-- The following is a hack to get xslt work with maven
(See: http://maven.apache.org/faq.html#BadXSLT ) -->
${systemScope.setProperty(
'javax.xml.transform.TransformerFactory',
'org.apache.xalan.processor.TransformerFactoryImpl')}
The JavaCC grammar in src/grammar/xpath makes heavy use of XSLT, and the
following ant:xslt entries in maven.xml handle the transformations:
<ant:xslt style="src/grammar/xpath/strip.xsl"
in="src/grammar/xpath/xpath-grammar.xml"
out="src/grammar/xpath/stripped-xpath-grammar.xml"
force="yes">
</ant:xslt>
<ant:xslt style="src/grammar/xpath/jjtree-jackrabbit.xsl"
in="src/grammar/xpath/stripped-xpath-grammar.xml"
out="src/grammar/xpath/XPath.jjt"
force="yes">
</ant:xslt>
The systemScope.setProperty() hack is needed to make the ant:xslt task
work properly with Maven (see [1]). However, as mentioned in the
comments of the associated bug entry [2], this hack doesn't work with
JDK 1.5 that uses the new Xalan XSLTC compiler at
com.sum.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.
Unfortunately the problem could not be solved by simply changing the
systemScope.setProperty() line because the XSLTC version bundled with
JDK 1.5 has problems with named templates (probably bug [3]). Instead of
the "provider not found" errors from ant:xslt, I now received
NoSuchMethodError exceptions from XSLTC.
As an alternative solution, I then downloaded the normal Xalan binaries
and placed xalan.jar in $MAVEN_HOME/lib/endorsed. I was then able to run
maven jar without problems. Note that the library needs to be placed in
lib/endorsed instead of just lib to make the Xalan classes visible for
the ant:xslt task.
Although this solution is a bit of a hack, I don't think a better one is
possible until either the Maven problem gets solved or the JDK XSLTC
gets fixed.
BR,
Jukka Zitting
[1] http://maven.apache.org/faq.html#BadXSLT
[2] http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-156
[3] http://issues.apache.org/jira/browse/XALANJ-1994
BadXSLT in maven.xml
Posted by Manoj Prasad <ma...@yahoo.com>.
Hi,
I'm eager to try this out, but I'm getting the
following build error:
BUILD FAILED
File...... /root/jackrabbit/maven.xml
Element... ant:xslt
Line...... 146
Column.... 25
Provider
org.apache.xalan.processor.TransformerFactoryImpl not
found
Total time: 9 seconds
Finished at: Sat Feb 12 17:21:22 EST 2005
I figure it's related to the BadXSLT comment in
maven.xml, but not sure how to fix it.
Thanks.
Manoj
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Fwd: JSR 170: Proposed Final Draft
Posted by Stefano Mazzocchi <st...@apache.org>.
David Nuescheler wrote:
> Hi all,
>
> After quite a bit of licensing discussions I am
> happy to report on behalf of the JSR-170 Expert
> Group that the "Content Repository API for Java
> Technology" Specification has made the next
> important step towards its completion.
>
> During this stage according to JCP 2.6 we will
> complete the "Reference Implementation" (RI)
> and the "Technology Compatibility Kit" (TCK)
> which both are under development here in
> the jackrabbit project.
>
> Now that the latest version is publically
> available I would like to invite everybody to
> give us feedback with respect to inconsistencies
> or other deficiencies in the spec that may come
> up during the implementation or the development
> of the TCK, and send those to:
> jsr-170-comments@jcp.org
>
> Any feedback is very welcome.
>
> During the completion of the TCK and RI
> we will publish updates to the specification
> containing minor fixes in the specification
> honouring (public) feedback.
>
> I would like to thank everyone for their
> contributions and enthusiasm so far and
> I am looking forward to see jackrabbit run
> faster and further.
YEY!
--
Stefano.