You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by tc...@apache.org on 2007/04/18 01:46:13 UTC
svn commit: r529805 - in /jakarta/commons/proper/jci/trunk/src/site:
site.xml xdoc/faq.xml
Author: tcurdt
Date: Tue Apr 17 16:46:08 2007
New Revision: 529805
URL: http://svn.apache.org/viewvc?view=rev&rev=529805
Log:
rephrased a few o=paragraphs,
fixed broken links
Modified:
jakarta/commons/proper/jci/trunk/src/site/site.xml
jakarta/commons/proper/jci/trunk/src/site/xdoc/faq.xml
Modified: jakarta/commons/proper/jci/trunk/src/site/site.xml
URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/src/site/site.xml?view=diff&rev=529805&r1=529804&r2=529805
==============================================================================
--- jakarta/commons/proper/jci/trunk/src/site/site.xml (original)
+++ jakarta/commons/proper/jci/trunk/src/site/site.xml Tue Apr 17 16:46:08 2007
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
+<?xml version="1.0"?>
<project name="Jakarta Commons JCI">
<bannerRight>
<name>Jakarta Commons JCI</name>
@@ -7,10 +7,10 @@
</bannerRight>
<body>
<menu name="Jakarta Commons JCI">
- <item name="About" href="index.html"/>
- <item name="Usage" href="usage.html"/>
- <item name="FAQ" href="faq.html"/>
- <item name="Downloads" href="downloads.html"/>
+ <item name="About" href="http://jakarta.apache.org/commons/jci/index.html"/>
+ <item name="Usage" href="http://jakarta.apache.org/commons/jci/usage.html"/>
+ <item name="FAQ" href="http://jakarta.apache.org/commons/jci/faq.html"/>
+ <item name="Downloads" href="http://jakarta.apache.org/commons/jci/downloads.html"/>
</menu>
<menu ref="modules"/>
</body>
Modified: jakarta/commons/proper/jci/trunk/src/site/xdoc/faq.xml
URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/src/site/xdoc/faq.xml?view=diff&rev=529805&r1=529804&r2=529805
==============================================================================
--- jakarta/commons/proper/jci/trunk/src/site/xdoc/faq.xml (original)
+++ jakarta/commons/proper/jci/trunk/src/site/xdoc/faq.xml Tue Apr 17 16:46:08 2007
@@ -7,11 +7,11 @@
<body>
<section name="FAQ">
<subsection name="Isn't compiler support integrated with Java6 (JSR199)?">
- Yes, it is now. JSR199 that in the end brought the official java compiler tools
- with Mustang had stalled for many years. This is how JCI was born. JCI provided
- what was missing from the JDK. And it provides it also for earlier versions.
- The main author of JCI has later joined the EG and will make sure there is also
- a bridge to the JSR199 API.
+ Yes, it is now. JSR199 in the end brought the official java compiler tools that
+ now come with Mustang. Progress on this had stalled for many years. This is how
+ JCI was born. JCI provided what was missing from the JDK. And it still provides
+ it also for earlier versions. The main author of JCI has later on joined the EG
+ and will make sure there is a bridge to the JSR199 API.
</subsection>
<subsection name="Doesn't JSR199 already deprecate JCI?">
Well, as said before ...there are no backports so far. And if you give the
@@ -20,15 +20,14 @@
</subsection>
<subsection name="How well tested is the code?">
Well, there are a couple of projects out there using this code already for
- quite some time in production. Drools and Cocoon to name just a few know Open
+ quite some time in production. Drools and Cocoon to name just a few well known Open
Source projects. Code coverage is not bad at all ...but there still a few things
on the TODO list and contributions are always welcome.
</subsection>
<subsection name="Will the ... compiler be supported?">
- There is always room for more. And if the compiler supports compilation to
- java bytecode there is a good chance it can be added. There are currently
- already a few candidates out there. But it all comes down to the need and
- the time to implement.
+ There is always room for new implementations. And if the compiler supports compilation to
+ java bytecode, there is also a good chance it can be added. There are currently already a
+ few potential candidates out there. But it all comes down to the need and the time to implement.
</subsection>
</section>
</body>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: svn commit: r529805 - in /jakarta/commons/proper/jci/trunk/src/site: site.xml xdoc/faq.xml
Posted by Rahul Akolkar <ra...@gmail.com>.
On 4/23/07, Dennis Lundberg <de...@apache.org> wrote:
> Rahul Akolkar wrote:
> > On 4/23/07, Dennis Lundberg <de...@apache.org> wrote:
> >> tcurdt@apache.org wrote:
> >> > Author: tcurdt
> >> > Date: Tue Apr 17 16:46:08 2007
> >> > New Revision: 529805
> >> >
> >> > URL: http://svn.apache.org/viewvc?view=rev&rev=529805
> >> > Log:
> >> > rephrased a few o=paragraphs,
> >> > fixed broken links
> >> >
<snip/>
> >>
> >> This should not be necessary. If you use full URLs like this, you won't
> >> be able to navigate a locally built site correctly. What kind of
> >> problems did you run into? You stated "broken links" as the reason for
> >> the change in the commit message.
> >>
> > <snip/>
> >
> > Apparently, the site.xml "inheritance" does not tweak relative URLs as
> > needed (and expected).
> >
> > -Rahul
>
> So, the sub modules of jci are getting menu links that doesn't work?
>
<snap/>
Before, yes.
-Rahul
> --
> Dennis Lundberg
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: svn commit: r529805 - in /jakarta/commons/proper/jci/trunk/src/site:
site.xml xdoc/faq.xml
Posted by Dennis Lundberg <de...@apache.org>.
Rahul Akolkar wrote:
> On 4/23/07, Dennis Lundberg <de...@apache.org> wrote:
>> tcurdt@apache.org wrote:
>> > Author: tcurdt
>> > Date: Tue Apr 17 16:46:08 2007
>> > New Revision: 529805
>> >
>> > URL: http://svn.apache.org/viewvc?view=rev&rev=529805
>> > Log:
>> > rephrased a few o=paragraphs,
>> > fixed broken links
>> >
>> >
>> > Modified:
>> > jakarta/commons/proper/jci/trunk/src/site/site.xml
>> > jakarta/commons/proper/jci/trunk/src/site/xdoc/faq.xml
>> >
>> > Modified: jakarta/commons/proper/jci/trunk/src/site/site.xml
>> > URL:
>> http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/src/site/site.xml?view=diff&rev=529805&r1=529804&r2=529805
>>
>> >
>> ==============================================================================
>>
>> > --- jakarta/commons/proper/jci/trunk/src/site/site.xml (original)
>> > +++ jakarta/commons/proper/jci/trunk/src/site/site.xml Tue Apr 17
>> 16:46:08 2007
>> > @@ -1,4 +1,4 @@
>> > -<?xml version="1.0" encoding="ISO-8859-1"?>
>> > +<?xml version="1.0"?>
>> > <project name="Jakarta Commons JCI">
>> > <bannerRight>
>> > <name>Jakarta Commons JCI</name>
>> > @@ -7,10 +7,10 @@
>> > </bannerRight>
>> > <body>
>> > <menu name="Jakarta Commons JCI">
>> > - <item name="About" href="index.html"/>
>> > - <item name="Usage" href="usage.html"/>
>> > - <item name="FAQ" href="faq.html"/>
>> > - <item name="Downloads" href="downloads.html"/>
>> > + <item name="About"
>> href="http://jakarta.apache.org/commons/jci/index.html"/>
>> > + <item name="Usage"
>> href="http://jakarta.apache.org/commons/jci/usage.html"/>
>> > + <item name="FAQ"
>> href="http://jakarta.apache.org/commons/jci/faq.html"/>
>> > + <item name="Downloads"
>> href="http://jakarta.apache.org/commons/jci/downloads.html"/>
>>
>> This should not be necessary. If you use full URLs like this, you won't
>> be able to navigate a locally built site correctly. What kind of
>> problems did you run into? You stated "broken links" as the reason for
>> the change in the commit message.
>>
> <snip/>
>
> Apparently, the site.xml "inheritance" does not tweak relative URLs as
> needed (and expected).
>
> -Rahul
So, the sub modules of jci are getting menu links that doesn't work?
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: svn commit: r529805 - in /jakarta/commons/proper/jci/trunk/src/site: site.xml xdoc/faq.xml
Posted by Rahul Akolkar <ra...@gmail.com>.
On 4/23/07, Dennis Lundberg <de...@apache.org> wrote:
> tcurdt@apache.org wrote:
> > Author: tcurdt
> > Date: Tue Apr 17 16:46:08 2007
> > New Revision: 529805
> >
> > URL: http://svn.apache.org/viewvc?view=rev&rev=529805
> > Log:
> > rephrased a few o=paragraphs,
> > fixed broken links
> >
> >
> > Modified:
> > jakarta/commons/proper/jci/trunk/src/site/site.xml
> > jakarta/commons/proper/jci/trunk/src/site/xdoc/faq.xml
> >
> > Modified: jakarta/commons/proper/jci/trunk/src/site/site.xml
> > URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/src/site/site.xml?view=diff&rev=529805&r1=529804&r2=529805
> > ==============================================================================
> > --- jakarta/commons/proper/jci/trunk/src/site/site.xml (original)
> > +++ jakarta/commons/proper/jci/trunk/src/site/site.xml Tue Apr 17 16:46:08 2007
> > @@ -1,4 +1,4 @@
> > -<?xml version="1.0" encoding="ISO-8859-1"?>
> > +<?xml version="1.0"?>
> > <project name="Jakarta Commons JCI">
> > <bannerRight>
> > <name>Jakarta Commons JCI</name>
> > @@ -7,10 +7,10 @@
> > </bannerRight>
> > <body>
> > <menu name="Jakarta Commons JCI">
> > - <item name="About" href="index.html"/>
> > - <item name="Usage" href="usage.html"/>
> > - <item name="FAQ" href="faq.html"/>
> > - <item name="Downloads" href="downloads.html"/>
> > + <item name="About" href="http://jakarta.apache.org/commons/jci/index.html"/>
> > + <item name="Usage" href="http://jakarta.apache.org/commons/jci/usage.html"/>
> > + <item name="FAQ" href="http://jakarta.apache.org/commons/jci/faq.html"/>
> > + <item name="Downloads" href="http://jakarta.apache.org/commons/jci/downloads.html"/>
>
> This should not be necessary. If you use full URLs like this, you won't
> be able to navigate a locally built site correctly. What kind of
> problems did you run into? You stated "broken links" as the reason for
> the change in the commit message.
>
<snip/>
Apparently, the site.xml "inheritance" does not tweak relative URLs as
needed (and expected).
-Rahul
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: svn commit: r529805 - in /jakarta/commons/proper/jci/trunk/src/site:
site.xml xdoc/faq.xml
Posted by Dennis Lundberg <de...@apache.org>.
tcurdt@apache.org wrote:
> Author: tcurdt
> Date: Tue Apr 17 16:46:08 2007
> New Revision: 529805
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=529805
> Log:
> rephrased a few o=paragraphs,
> fixed broken links
>
>
> Modified:
> jakarta/commons/proper/jci/trunk/src/site/site.xml
> jakarta/commons/proper/jci/trunk/src/site/xdoc/faq.xml
>
> Modified: jakarta/commons/proper/jci/trunk/src/site/site.xml
> URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/src/site/site.xml?view=diff&rev=529805&r1=529804&r2=529805
> ==============================================================================
> --- jakarta/commons/proper/jci/trunk/src/site/site.xml (original)
> +++ jakarta/commons/proper/jci/trunk/src/site/site.xml Tue Apr 17 16:46:08 2007
> @@ -1,4 +1,4 @@
> -<?xml version="1.0" encoding="ISO-8859-1"?>
> +<?xml version="1.0"?>
> <project name="Jakarta Commons JCI">
> <bannerRight>
> <name>Jakarta Commons JCI</name>
> @@ -7,10 +7,10 @@
> </bannerRight>
> <body>
> <menu name="Jakarta Commons JCI">
> - <item name="About" href="index.html"/>
> - <item name="Usage" href="usage.html"/>
> - <item name="FAQ" href="faq.html"/>
> - <item name="Downloads" href="downloads.html"/>
> + <item name="About" href="http://jakarta.apache.org/commons/jci/index.html"/>
> + <item name="Usage" href="http://jakarta.apache.org/commons/jci/usage.html"/>
> + <item name="FAQ" href="http://jakarta.apache.org/commons/jci/faq.html"/>
> + <item name="Downloads" href="http://jakarta.apache.org/commons/jci/downloads.html"/>
This should not be necessary. If you use full URLs like this, you won't
be able to navigate a locally built site correctly. What kind of
problems did you run into? You stated "broken links" as the reason for
the change in the commit message.
> </menu>
> <menu ref="modules"/>
> </body>
>
> Modified: jakarta/commons/proper/jci/trunk/src/site/xdoc/faq.xml
> URL: http://svn.apache.org/viewvc/jakarta/commons/proper/jci/trunk/src/site/xdoc/faq.xml?view=diff&rev=529805&r1=529804&r2=529805
> ==============================================================================
> --- jakarta/commons/proper/jci/trunk/src/site/xdoc/faq.xml (original)
> +++ jakarta/commons/proper/jci/trunk/src/site/xdoc/faq.xml Tue Apr 17 16:46:08 2007
> @@ -7,11 +7,11 @@
> <body>
> <section name="FAQ">
> <subsection name="Isn't compiler support integrated with Java6 (JSR199)?">
> - Yes, it is now. JSR199 that in the end brought the official java compiler tools
> - with Mustang had stalled for many years. This is how JCI was born. JCI provided
> - what was missing from the JDK. And it provides it also for earlier versions.
> - The main author of JCI has later joined the EG and will make sure there is also
> - a bridge to the JSR199 API.
> + Yes, it is now. JSR199 in the end brought the official java compiler tools that
> + now come with Mustang. Progress on this had stalled for many years. This is how
> + JCI was born. JCI provided what was missing from the JDK. And it still provides
> + it also for earlier versions. The main author of JCI has later on joined the EG
> + and will make sure there is a bridge to the JSR199 API.
> </subsection>
> <subsection name="Doesn't JSR199 already deprecate JCI?">
> Well, as said before ...there are no backports so far. And if you give the
> @@ -20,15 +20,14 @@
> </subsection>
> <subsection name="How well tested is the code?">
> Well, there are a couple of projects out there using this code already for
> - quite some time in production. Drools and Cocoon to name just a few know Open
> + quite some time in production. Drools and Cocoon to name just a few well known Open
> Source projects. Code coverage is not bad at all ...but there still a few things
> on the TODO list and contributions are always welcome.
> </subsection>
> <subsection name="Will the ... compiler be supported?">
> - There is always room for more. And if the compiler supports compilation to
> - java bytecode there is a good chance it can be added. There are currently
> - already a few candidates out there. But it all comes down to the need and
> - the time to implement.
> + There is always room for new implementations. And if the compiler supports compilation to
> + java bytecode, there is also a good chance it can be added. There are currently already a
> + few potential candidates out there. But it all comes down to the need and the time to implement.
> </subsection>
> </section>
> </body>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org