David Crossley | 1 Sep 02:17 2004
Picon

Re: latest forrest can't build incubator site

Rodent of Unusual Size wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> David Crossley wrote:
> >
> > In your output below, "com/ibm/crypto/provider/IBMJCE" is nothing
> > to do with either Forrest or Cocoon.
> 
> [relevant output included below]
> 
> i don't do java, so i don't know what the java messages mean.  *i*
> certainly never typed anything with 'com/ibm/crypto' in it.  not now,
> not when i installed the ibm jdk, and at no time in between. :-(
> 
> my WAG is that my jdk version is too old.  any thoughts on that?
> if that turns out to be the case, maybe a test for that could be
> added to one of the build files so it can say so rather than
> failing mysteriously and spectacularly like this. :-D

Well i did investigate your issue as thoroughly as i could.
Normally i use J2SDK 1.4 but i reverted to 1.3 to test this
and could not reproduce your issue.

Would you please do this:
* In the forrest.properties file uncomment the line
for "forrest.echo=true".
* Do 'forrest -v > log' to trap verbose output.
* Attach that file to the Forrest Issue tracker.

--David
(Continue reading)

David Crossley | 1 Sep 02:40 2004
Picon

Re: latest forrest can't build incubator site

Ah Ken, i see from the incubator CVS messages that
you can now build using the recent Forrest.
Is the "com/ibm/crypto/provider/IBMJCE" issue gone?

However i see that the Derby page is a mess.
http://incubator.apache.org/projects/derby.html

This is because you are using the recent Forrest
but have not updated the configuration files.
I did provide a patch to the general  <at>  incubator list
for this, but it was met with total silence.

--

-- 
David Crossley

David Crossley | 1 Sep 03:08 2004
Picon

RE: latest forrest can't build incubator site

Noel J. Bergman wrote:
> David Crossley wrote:
> > Oh all right, it must be finally time for me contribute a bit
> > more to Incubator.
> 
> How's about you and Berin Lautenbach get together and install forrest under
> ~noel/incubator-site?  I've copied over an early setup that he had done
> elsewhere.  Is group accessible for incubator group, and we can use it for
> site publishing as an interim solution.

I do not understand what is the intention, Noel.
Anyway i will contact Berin and see if we can remove
the hurdles.

--

-- 
David Crossley

Noel J. Bergman | 1 Sep 03:32 2004

RE: latest forrest can't build incubator site

David Crossley wrote:
> i see that the Derby page is a mess.
> http://incubator.apache.org/projects/derby.html

> This is because you are using the recent Forrest
> but have not updated the configuration files.

I have committed your changes to CVS.  Still hoping that you will help us to
setup ~noel/incubator-site as a temporary publishing engine.  There is no
reason everyone to have to track forrest changes, or have to deal with it.
Let's just setup a place where people like Roy, Ken, Ian, Cliff, et al, can
just do the standard update, build, commit cycle.

	--- Noel

David Crossley | 1 Sep 04:27 2004
Picon

RE: latest forrest can't build incubator site

Noel J. Bergman wrote:
> David Crossley wrote:
> > i see that the Derby page is a mess.
> > http://incubator.apache.org/projects/derby.html
> 
> > This is because you are using the recent Forrest
> > but have not updated the configuration files.
> 
> I have committed your changes to CVS.

Good on you, Noel.

> Still hoping that you will help us to
> setup ~noel/incubator-site as a temporary publishing engine.  There is no
> reason everyone to have to track forrest changes, or have to deal with it.
> Let's just setup a place where people like Roy, Ken, Ian, Cliff, et al, can
> just do the standard update, build, commit cycle.

Yes, will do - already emailed Berin to arrange a time
to talk about how to do it.

This is the situation where Forrestbot will help.
However, we have holdups with people, resources, and energy.
So this interim "staging" solution should assist.

--

-- 
David Crossley

issues | 1 Sep 05:11 2004

[issues] New comment: (FOR-245) changing skins and going out in the public view

The following comment has been added to this issue:

     Author: David Crossley
    Created: Wed, 1 Sep 2004 5:10 AM
       Body:
Testing Jira notifications. Please ignore.
---------------------------------------------------------------------
View the issue:

  http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-245

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-245
    Summary: changing skins and going out in the public view
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Forrest
  Component: Forrest skins
    Fix For: 0.6
   Versions:
             HEAD

   Assignee: 
   Reporter: David Crossley

    Created: Thu, 5 Aug 2004 7:51 AM
(Continue reading)

David Crossley | 1 Sep 06:08 2004
Picon

Re: [STATUS] Things remaining for 0.6

Dave Brondsema wrote:
> Nicola Ken Barozzi wrote:
> >
> > Let's see if we can finalize this:
> >
> > 1 - I'm actively working to finish off copyless, and it will involve a
> >      change in Cocoon, that I've already proposed on that list. It
> >      will make it possible for mounted pipelines to return back to the
> >      parent for processing if no match is found.
> >      Besides being able to use it to make the internals cleaner, it
> >      will make it possible for users to actually inject theit sitemaps
> >      without having to copy over our things, making it much more
> >      resilient.
> 
> Great.
> 
> > 2 - Should we switch to pelt after a quick check? it would really be
> >      better to not have to switch skin now and then again in 0.7 if
> >      possible.
> > 
> > 3 - There are some buds that are to be fixed to make the dist.

And the etc/RELEASE_PROCESS.txt needs review and practice.

> > 4 - I'd postpone the remaining non-critical bugs to 0.7.
> 
> Yes.  I'd much rather have a release with some bugs than let 0.6 stagnate
> for more months.

Exactly. Thanks Nicola Ken, i was close to sending a similar email.
(Continue reading)

David Crossley | 1 Sep 06:29 2004
Picon

Re: [STATUS] Things remaining for 0.6

Nicola Ken Barozzi wrote:
> Dave Brondsema wrote:
> ...
> >>5 - I propose that we add two new matches:
> >>
> >>     - *.html (that acts like *.ihtml, which itself will be deprecated)
> >>
> >>              This will make it possible for Forrest to skin any site
> >>              that does not have validation included, even if not made
> >>              explicitly for Forrest
> > 
> > Is this in line with our plan for xhtml2 and namespaces? 
> 
> It does not collide. The idea is to reserve *.xhtml for any proper 
> xhtml, be it 1.1 or 2.

Yes, we discussed this before:
 [VOTE] Finalizing html-ihtml-ehtml
 http://marc.theaimsgroup.com/?t=108141201100001

> > I think using this extension in the 'xdocs' dir will confuse people.
> 
> Ok, but then we have lots of stuff there than are not x(ml)docs.

People are already a bit confused, so a bit more won't hurt :-)
We just need some better documentation and examples.

The "x" in "xdocs" should just be a wild-card.

We should stop calling the "Apache Forrest document" xml format
(Continue reading)

David Crossley | 1 Sep 06:47 2004
Picon

Re: [STATUS] Things remaining for 0.6

Clay Leeds wrote:
> Dave Brondsema wrote:
> > Clay Leeds wrote:
> >>
> >> The primary reason I (and the rest of fop-dev) have been eagerly
> >> awaiting 0.6 is for the aggregate site.pdf output. The thought was 
> >> that
> >> FOP should have an aggregate PDF of the site. If this is not going to
> >> happen, I really need to get on the ball and (sigh) figure out how to
> >> make the current xml-fop work with 0.5 ... <snip/>
> >>
> >> Another alternative is to somehow generate the PDF using 0.5, and
> >> inserting it RAW into the site? Anyone another idea? Is there anything
> >> I can do to 'help' get aggregate into 0.6 (ahem... short of learning
> >> Java)?

You do not need to know Java to use or develop Forrest.
The various XSLT and the Cocoon Sitemap are the keys.

> > Both 0.5.1 and 0.6-dev have problems with the aggregate site.  Your
> > success with either is highly dependent on how you do linking and image
> > references and if you have duplicate names/ids.
> 
> OK... So would (gasp) 0.5 work? As I mentioned, I've been waiting for 
> the 0.6 release. I have a few ideas for content changes to xml-fop but 
> have waited to make any real changes (other than 'emergency' changes 
> which involve the use of vi...) until I have BUILD working.

Why wait? The "whole site capability" is really just an added bonus.

(Continue reading)

David Crossley | 1 Sep 06:57 2004
Picon

RE: [STATUS] Things remaining for 0.6

Hare, Michael wrote:
> I may have missed it, did we ever get 0.6 to run as a webapp under Tomcat
> 5.0.27?

Good on you Michael. We need more people to speak up
when things have been overlooked.

Better still, would you be able to create an issue report:
http://forrest.apache.org/ => Project Tab => Bugs and Issues
Just a short description and link to your email thread.

People, this is the background email to forrest-users:
 http://mail-archives.apache.org/eyebrowse/ReadMsg?listId=260&msgNo=282
 Forrest 0.6 Interaction with Tomcat 5.0.27
 Wed, 4 Aug 2004 10:18:34 -0500

--

-- 
David Crossley


Gmane