You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Nicola Ken Barozzi <ni...@apache.org> on 2002/11/04 11:50:25 UTC
Forrest fast edit-check cycle with Jetty committed
I've committed the Jetty stuff to see changes in the editing right away.
What you need to do is to build the shbat distro, and from the project
to see do a "forrest run".
Point the browser to http://localhost:8888/index.html and see your stuff
being rendered realtime.
I hope I committed it all, please check.
The wiki stuff is still on my HD, I have to finish a stylesheet and then
it can be committed as alpha stuff.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Forrest fast edit-check cycle with Jetty committed
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Keiron Liddle wrote:
> On Mon, 2002-11-04 at 11:50, Nicola Ken Barozzi wrote:
>
>>I've committed the Jetty stuff to see changes in the editing right away.
>>
>>What you need to do is to build the shbat distro, and from the project
>>to see do a "forrest run".
>>
>>Point the browser to http://localhost:8888/index.html and see your stuff
>>being rendered realtime.
>>
>>I hope I committed it all, please check.
>
>
> There appears to be some problem:
>
> Exception in thread "main" java.lang.UnsupportedClassVersionError:
> org/mortbay/util/FileResource (Unsupported major.minor version 48.0)
> at java.lang.ClassLoader.defineClass0(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:248)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
> at org.mortbay.jetty.Server.<init>(Server.java:68)
> at org.mortbay.jetty.Server.main(Server.java:397)
Ok, I've committed *more* than all :-/
I deleted the non-1.2 version of the jetty libs, see if this works.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Forrest fast edit-check cycle with Jetty committed
Posted by Keiron Liddle <ke...@aftexsw.com>.
On Mon, 2002-11-04 at 11:50, Nicola Ken Barozzi wrote:
>
> I've committed the Jetty stuff to see changes in the editing right away.
>
> What you need to do is to build the shbat distro, and from the project
> to see do a "forrest run".
>
> Point the browser to http://localhost:8888/index.html and see your stuff
> being rendered realtime.
>
> I hope I committed it all, please check.
There appears to be some problem:
Exception in thread "main" java.lang.UnsupportedClassVersionError:
org/mortbay/util/FileResource (Unsupported major.minor version 48.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:486)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:111)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:248)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286)
at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
at org.mortbay.jetty.Server.<init>(Server.java:68)
at org.mortbay.jetty.Server.main(Server.java:397)
Re: Forrest fast edit-check cycle with Jetty committed
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
On Monday 04 November 2002 11:50, Nicola Ken Barozzi wrote:
> I've committed the Jetty stuff to see changes in the editing right away.
>. . .
Works here (Linux / JDK1.3.1), cool!
(almost-) zero-install Forrest is alive...
Minor issue: here http://localhost:8888/ is redirected to
http://localhost:8888index.html which is invalid, / missing after port number.
> do a "forrest run".
Funny, I had to type "run, Forrest, run!" instead
(Just kidding. Can't resist ;-)
-Bertrand
Re: Forrest fast edit-check cycle with Jetty committed
Posted by Jeff Turner <je...@apache.org>.
On Tue, Nov 05, 2002 at 12:23:44PM +0100, Steven Noels wrote:
> Ant- and webapp-gurus, hear:
>
> I was wondering why we are still copying the content away to a
> {project.home}/build/webapp environment when using 'forrest run':
> wouldn't it be easier to just go and fetch the content from the
> {project.home}/src/documentation directory?
The problem is that some files need Ant @tokens@ replaced - notably:
1) src/resources/skins/forrest-site/scripts/breadcrumbs.js:
if(!("@skinconfig.trail.link1.name@"=="")){
PREPREND_CRUMBS.push( new Array(
"@skinconfig.trail.link1.name@", "@skinconfig.trail.link1.href@"
) );
}
2) src/documentation/conf/cocoon.xconf currently has:
<skin>@skin@</skin>
which is a temporary hack until we get XMLModule reading the selected
skin from an XML file.
3) Before modules, we had @skin@ tokens in sitemaps. I suspect some
people with custom sitemaps are still relying on their sitemaps being
filter-copied.
The cleanest solution might be to have a FilterReplacerTransformer that
converts @tokens@ to values on the fly.
> Also, I would suggest to make the default build target directory
> something like {project.home}/build/forrest/webapp, since I gather a lot
> of projects will already use build/webapp for something else.
+1
> For that matter, maybe also use {}/build/forrest/tmp instead.
Or just say that anything Forrest produces lives under build/forrest/*,
just like Cocoon puts stuff in build/cocoon/*.
--Jeff
Re: Forrest fast edit-check cycle with Jetty committed
Posted by Steven Noels <st...@outerthought.org>.
Ant- and webapp-gurus, hear:
I was wondering why we are still copying the content away to a
{project.home}/build/webapp environment when using 'forrest run':
wouldn't it be easier to just go and fetch the content from the
{project.home}/src/documentation directory?
Also, I would suggest to make the default build target directory
something like {project.home}/build/forrest/webapp, since I gather a lot
of projects will already use build/webapp for something else.
For that matter, maybe also use {}/build/forrest/tmp instead.
I'm trying to live through this avalanche, so sorry for not committing
patches myself - it is too much of a moving target for me currently (no
critique, just the realisation of me being a slow learner!)
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
stevenn@outerthought.org stevenn@apache.org
Re: Forrest fast edit-check cycle with Jetty committed
Posted by Jeff Turner <je...@apache.org>.
On Mon, Nov 04, 2002 at 11:50:25AM +0100, Nicola Ken Barozzi wrote:
>
> I've committed the Jetty stuff to see changes in the editing right away.
>
> What you need to do is to build the shbat distro, and from the project
> to see do a "forrest run".
>
> Point the browser to http://localhost:8888/index.html and see your stuff
> being rendered realtime.
>
> I hope I committed it all, please check.
Wohoo! :)
Nice work..
--Jeff
> The wiki stuff is still on my HD, I have to finish a stylesheet and then
> it can be committed as alpha stuff.
>
> --
> Nicola Ken Barozzi nicolaken@apache.org
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>