You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2008/09/10 15:43:46 UTC
[heads-up] merging our branch Cocoon-2.1
I will get on with merging the branch, hopefully tomorrow.
I expect it to be smooth going, as people have been
working in other parts of the repository.
-David
Re: [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
Gavin wrote:
>
> 'forrest seed site'
>
> that all fell apart strangely. The site seeded but nothing built
> at all, hundreds of errors -- all of them related to all the
> different *.xmap files.
>
> I then did 'forrest run' right after and it worked.
> I then did a 'forrest site' and it worked
>
> Were you being pseudo with 'forrest seed site' in one go or is
> that supposed to work?
It did used to work. I haven't tried it for ages
so don't know how long this has been broken.
Yes it spews the sames for me. Something about
"No pipeline matched request: module.properties.properties"
Don't worry about it for now.
-David
RE: [heads-up] merging our branch Cocoon-2.1
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Thursday, 11 September 2008 4:13 PM
> To: dev@forrest.apache.org
> Subject: Re: [heads-up] merging our branch Cocoon-2.1
>
> Gavin wrote:
> >
> > Well, I thought I'd try this right away, tell you it works
> > fine then I can carry on with what I was doing.
> >
> > My first report after an 'svn up' of trunk is a failure.
> > Not a major problem I'm sure, just thought I'd throw it
> > in right away and then have a look to see what the problem is.
>
> Thanks for being so prompt. Forrestbot on our zone is
> yelling at us now. We will see if the dispatcher-based
> one does too.
>
> > Steps I took so far:-
> >
> > 1. cd trunk; svn up
> >
> > 2. cd main; build clean; build
> >
> > All ok except warnings, I'll put them here anyway :-
>
> They can be ignored. See previous discussion.
>
> > 3. cd to project home; forrest clean; forrest.
> >
> > X [0] linkmap.html BROKEN:
> >
> D:\Apache2\forrest\main\webapp\.\D:\Apache2\project\trunk\project\build\tm
> p\
> > D:\Apache2\forrest\build\plugins\dataModel.xmap (The filename, directory
> > name, or volume label syntax is incorrect)
> > Logging Error: Writing event to closed stream.
> > Total time: 0 minutes 9 seconds, Site size: 0 Site pages: 0
>
> Is that the only break?
On this one yes, but due to it no site got built, so no pages at all.
>
> Did the normal 'forrest seed site' work for you, i.e. no dispatcher?
No,
I did it in two stages earlier -
'forrest seed-sample' , then 'forrest run' then 'forrest site'
that all worked great.
I tried it your way in one hit (in a new directory)
'forrest seed site'
that all fell apart strangely. The site seeded but nothing built
at all, hundreds of errors -- all of them related to all the
different *.xmap files.
I then did 'forrest run' right after and it worked.
I then did a 'forrest site' and it worked
Were you being pseudo with 'forrest seed site' in one go or is
that supposed to work?
>
> Does it help to do a 'forrest clean-work' in your project home?
No, no difference to me -- also note that site-author is giving me
the same trouble, yet an 'svn st' shows it to be the same.
So. Im manually deleting all work/build files and will try again.
Gav...
>
> -David
>
>
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.6.17 - Release Date: 9/5/2008 12:00
> AM
Re: [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
Gavin wrote:
>
> Well, I thought I'd try this right away, tell you it works
> fine then I can carry on with what I was doing.
>
> My first report after an 'svn up' of trunk is a failure.
> Not a major problem I'm sure, just thought I'd throw it
> in right away and then have a look to see what the problem is.
Thanks for being so prompt. Forrestbot on our zone is
yelling at us now. We will see if the dispatcher-based
one does too.
> Steps I took so far:-
>
> 1. cd trunk; svn up
>
> 2. cd main; build clean; build
>
> All ok except warnings, I'll put them here anyway :-
They can be ignored. See previous discussion.
> 3. cd to project home; forrest clean; forrest.
>
> X [0] linkmap.html BROKEN:
> D:\Apache2\forrest\main\webapp\.\D:\Apache2\project\trunk\project\build\tmp\
> D:\Apache2\forrest\build\plugins\dataModel.xmap (The filename, directory
> name, or volume label syntax is incorrect)
> Logging Error: Writing event to closed stream.
> Total time: 0 minutes 9 seconds, Site size: 0 Site pages: 0
Is that the only break?
Did the normal 'forrest seed site' work for you, i.e. no dispatcher?
Does it help to do a 'forrest clean-work' in your project home?
-David
Windows issues with new Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> Thorsten Scherler wrote:
> > Gavin wrote:
> > ...
> > > > X [0] linkmap.html BROKEN:
> > > > D:\Apache2\forrest\main\webapp\.\D:\Apache2\project\trunk\project\build\tm
> > > > p\
> > > > D:\Apache2\forrest\build\plugins\dataModel.xmap (The filename, directory
> > > > name, or volume label syntax is incorrect)
> > > > Logging Error: Writing event to closed stream.
> > > > Total time: 0 minutes 9 seconds, Site size: 0 Site pages: 0
> >
> > That is a dispatcher project, right? The location of the dataModel.xmap
> > is definitely wrong.
>
> That reads for me:
> /home/thorsten/src/apache/forrest-trunk/build/plugins/org.apache.forrest.plugin.internal.dispatcher/dataModel.xmap
>
> It seems to be a combination of three locations
> D:\Apache2\forrest\main\webapp\.
> D:\Apache2\project\trunk\project\build\tmp\
> D:\Apache2\forrest\build\plugins\dataModel.xmap
>
> Need to go to sleep now but finding locations in our code that is using
> three variables will reduce the possibilities.
We need a clear report from someone on Windows about
what is broken for them. My main question: is it just
the "linkmap.html" or other docs too? That document
has special processing.
Does this happen only for the dispatcher-based sites
or also for the skins-based sites?
]$ cd $FORREST_HOME/main
]$ build test > test-output.txt
... and attach to a Jira issue. That test runs the
sample site in skins mode, then again in dispatcher mode.
NOTE: Calling all Windows-based developers here, not just
the overworked committers.
-David
RE: [heads-up] merging our branch Cocoon-2.1
Posted by Thorsten Scherler <th...@apache.org>.
On Thu, 2008-09-11 at 09:00 +0200, Thorsten Scherler wrote:
> On Thu, 2008-09-11 at 16:07 +1000, Gavin wrote:
> ...
> > >
> > > X [0] linkmap.html BROKEN:
> > > D:\Apache2\forrest\main\webapp\.\D:\Apache2\project\trunk\project\build\tm
> > > p\
> > > D:\Apache2\forrest\build\plugins\dataModel.xmap (The filename, directory
> > > name, or volume label syntax is incorrect)
> > > Logging Error: Writing event to closed stream.
> > > Total time: 0 minutes 9 seconds, Site size: 0 Site pages: 0
>
> That is a dispatcher project, right? The location of the dataModel.xmap
> is definitely wrong.
That reads for me:
/home/thorsten/src/apache/forrest-trunk/build/plugins/org.apache.forrest.plugin.internal.dispatcher/dataModel.xmap
It seems to be a combination of three locations
D:\Apache2\forrest\main\webapp\.
D:\Apache2\project\trunk\project\build\tmp\
D:\Apache2\forrest\build\plugins\dataModel.xmap
Need to go to sleep now but finding locations in our code that is using
three variables will reduce the possibilities.
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
RE: [heads-up] merging our branch Cocoon-2.1
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Thursday, 11 September 2008 6:37 PM
> To: dev@forrest.apache.org
> Subject: Re: [heads-up] merging our branch Cocoon-2.1
>
> What Java version do you have there, Gavin?
I am using 1.5 , have been for more than year.
Gav...
>
> -David
>
>
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.6.17 - Release Date: 9/5/2008 12:00
> AM
Re: [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
What Java version do you have there, Gavin?
-David
RE: [heads-up] merging our branch Cocoon-2.1
Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
On Thu, 2008-09-11 at 16:07 +1000, Gavin wrote:
...
> >
> > X [0] linkmap.html BROKEN:
> > D:\Apache2\forrest\main\webapp\.\D:\Apache2\project\trunk\project\build\tm
> > p\
> > D:\Apache2\forrest\build\plugins\dataModel.xmap (The filename, directory
> > name, or volume label syntax is incorrect)
> > Logging Error: Writing event to closed stream.
> > Total time: 0 minutes 9 seconds, Site size: 0 Site pages: 0
That is a dispatcher project, right? The location of the dataModel.xmap
is definitely wrong.
...
> I just tested on site-author and that fails also with lots of :-
>
> X [0]
> pluginDocs/plugins_0_70/pluginInfrastr
> ucture.html BROKEN:
> D:\Apache2\forrest\main\webapp\.\D:\Apache2\forrest\site
> -author\build\tmp\D:\Apache2\forrest\build\plugins\svnHelper.xmap (The
> filename,
> directory name, or volume label syntax is incorrect)
>
> the above is true for every file on the site.
>
> Seems to be doubling up of paths somewhere.
The path is definitely very wrong in all the possible ways. It not only
doubles the path but as well svnHelper.xmap is in the projectInfo plugin
as David pointed out but it is not trying to read it from there. It
seems something is wrong with plugin.
Sorry for not being a bigger help.
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
Re: [heads-up] merging our branch Cocoon-2.1
Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
On Thu, 2008-09-11 at 16:34 +1000, David Crossley wrote:
...
> Would other people test ASAP too please.
fresh-site (skins): run and site work as expected
site-author (skins): run and site work as expected
fresh-site (dispatcher): run and site work as expected
I do not see any issues.
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
Re: [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
Gavin wrote:
>
> No idea yet, but thought I'd mention that seeding a seed-sample site
> from the new trunk works fine - I thought it was broken at first it
> was so damn quick - around ~1 second to do a seed-sample.
If your talking about 'forrest seed' being quick
then that does not use Cocoon. It is only when
doing 'forrest site' or 'forrest run' that it
comes into play.
> I tested various pages and PDFs and all work fine and fast -- all the images
> appear great in the PDFs too.
>
> I just tested on site-author and that fails also with lots of :-
>
> X [0]
> pluginDocs/plugins_0_70/pluginInfrastr
> ucture.html BROKEN:
> D:\Apache2\forrest\main\webapp\.\D:\Apache2\forrest\site
> -author\build\tmp\D:\Apache2\forrest\build\plugins\svnHelper.xmap (The
> filename,
> directory name, or volume label syntax is incorrect)
>
> the above is true for every file on the site.
>
> Seems to be doubling up of paths somewhere.
Hmmm "svnHelper.xmap" is only in the "projectInfo" plugin.
Your error message is more strange than just that double-up.
The last part of the path should be
...build/plugins/org.apache.forrest.plugin.input.projectInfo/svnHelper.xmap
At least that is where it is on my system.
Of course i did extensive testing before my commit
so it all works here on Mac OS X.
What platform are you on?
Would other people test ASAP too please.
-David
RE: [heads-up] merging our branch Cocoon-2.1
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Gavin [mailto:gavin@16degrees.com.au]
> Sent: Thursday, 11 September 2008 3:48 PM
> To: dev@forrest.apache.org
> Subject: RE: [heads-up] merging our branch Cocoon-2.1
>
>
>
> > -----Original Message-----
> > From: David Crossley [mailto:crossley@apache.org]
> > Sent: Thursday, 11 September 2008 2:35 PM
> > To: dev@forrest.apache.org
> > Subject: Re: [heads-up] merging our branch Cocoon-2.1
> >
> > David Crossley wrote:
> > > I will get on with merging the branch, hopefully tomorrow.
> > >
> > > I expect it to be smooth going, as people have been
> > > working in other parts of the repository.
> >
> > No worries. That is done now. And FOR-955 is closed.
> >
> > I will proceed to document this, probably in
> > the "upgrading_09.html" doc.
> >
> > When you first use this in your projects, there
> > will probably be a message about a certain cache item.
> > On the second run all is well. A way to avoid that
> > would be to do 'forrest clean-work' in each of your
> > projects to remove the Cocoon cache.
>
> Well, I thought I'd try this right away, tell you it works
> fine then I can carry on with what I was doing.
>
> My first report after an 'svn up' of trunk is a failure.
> Not a major problem I'm sure, just thought I'd throw it
> in right away and then have a look to see what the problem is.
>
> Steps I took so far:-
>
> 1. cd trunk; svn up
>
> 2. cd main; build clean; build
>
> All ok except warnings, I'll put them here anyway :-
>
> compile:
> Created dir: D:\Apache2\forrest\build\classes
> Compiling 32 source files to D:\Apache2\forrest\build\classes
> D:\Apache2\forrest\main\java\org\apache\forrest\log\ForrestLogTargetFactor
> y.
> java
> :22: warning: [deprecation] org.apache.cocoon.util.log.CocoonTargetFactory
> in or
> g.apache.cocoon.util.log has been deprecated
> import org.apache.cocoon.util.log.CocoonTargetFactory;
> ^
> D:\Apache2\forrest\main\java\org\apache\forrest\log\ForrestLogTargetFactor
> y.
> java
> :30: warning: [deprecation] org.apache.cocoon.util.log.CocoonTargetFactory
> in or
> g.apache.cocoon.util.log has been deprecated
> extends CocoonTargetFactory {
>
> 3. cd to project home; forrest clean; forrest.
>
> X [0] linkmap.html BROKEN:
> D:\Apache2\forrest\main\webapp\.\D:\Apache2\project\trunk\project\build\tm
> p\
> D:\Apache2\forrest\build\plugins\dataModel.xmap (The filename, directory
> name, or volume label syntax is incorrect)
> Logging Error: Writing event to closed stream.
> Total time: 0 minutes 9 seconds, Site size: 0 Site pages: 0
>
> ...
>
> BUILD FAILED
> D:\Apache2\forrest\main\targets\site.xml:183: Error building site.
>
> There appears to be a problem with your site build.
>
> Output of /brokenlinks.xml:-
>
> <broken-links>
> <link
> message="D:\Apache2\forrest\main\webapp\.\D:\Apache2\project\trunk\project
> \b
> uild\tmp\D:\Apache2\forrest\build\plugins\dataModel.xmap (The filename,
> directory name, or volume label syntax is incorrect)">linkmap.html</link>
> </broken-links>
>
> So, I'm not going to revert just yet, I'll have a look around, but if
> anyone
> has any ideas ...
>
No idea yet, but thought I'd mention that seeding a seed-sample site
from the new trunk works fine - I thought it was broken at first it
was so damn quick - around ~1 second to do a seed-sample.
I tested various pages and PDFs and all work fine and fast -- all the images
appear great in the PDFs too.
I just tested on site-author and that fails also with lots of :-
X [0]
pluginDocs/plugins_0_70/pluginInfrastr
ucture.html BROKEN:
D:\Apache2\forrest\main\webapp\.\D:\Apache2\forrest\site
-author\build\tmp\D:\Apache2\forrest\build\plugins\svnHelper.xmap (The
filename,
directory name, or volume label syntax is incorrect)
the above is true for every file on the site.
Seems to be doubling up of paths somewhere.
Cheers
> Gav...
>
> >
> > -David
> >
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG.
> > Version: 7.5.524 / Virus Database: 270.6.17 - Release Date: 9/5/2008
> 12:00
> > AM
>
>
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.6.17 - Release Date: 9/5/2008 12:00
> AM
RE: [heads-up] merging our branch Cocoon-2.1
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Thursday, 11 September 2008 2:35 PM
> To: dev@forrest.apache.org
> Subject: Re: [heads-up] merging our branch Cocoon-2.1
>
> David Crossley wrote:
> > I will get on with merging the branch, hopefully tomorrow.
> >
> > I expect it to be smooth going, as people have been
> > working in other parts of the repository.
>
> No worries. That is done now. And FOR-955 is closed.
>
> I will proceed to document this, probably in
> the "upgrading_09.html" doc.
>
> When you first use this in your projects, there
> will probably be a message about a certain cache item.
> On the second run all is well. A way to avoid that
> would be to do 'forrest clean-work' in each of your
> projects to remove the Cocoon cache.
Well, I thought I'd try this right away, tell you it works
fine then I can carry on with what I was doing.
My first report after an 'svn up' of trunk is a failure.
Not a major problem I'm sure, just thought I'd throw it
in right away and then have a look to see what the problem is.
Steps I took so far:-
1. cd trunk; svn up
2. cd main; build clean; build
All ok except warnings, I'll put them here anyway :-
compile:
Created dir: D:\Apache2\forrest\build\classes
Compiling 32 source files to D:\Apache2\forrest\build\classes
D:\Apache2\forrest\main\java\org\apache\forrest\log\ForrestLogTargetFactory.
java
:22: warning: [deprecation] org.apache.cocoon.util.log.CocoonTargetFactory
in or
g.apache.cocoon.util.log has been deprecated
import org.apache.cocoon.util.log.CocoonTargetFactory;
^
D:\Apache2\forrest\main\java\org\apache\forrest\log\ForrestLogTargetFactory.
java
:30: warning: [deprecation] org.apache.cocoon.util.log.CocoonTargetFactory
in or
g.apache.cocoon.util.log has been deprecated
extends CocoonTargetFactory {
3. cd to project home; forrest clean; forrest.
X [0] linkmap.html BROKEN:
D:\Apache2\forrest\main\webapp\.\D:\Apache2\project\trunk\project\build\tmp\
D:\Apache2\forrest\build\plugins\dataModel.xmap (The filename, directory
name, or volume label syntax is incorrect)
Logging Error: Writing event to closed stream.
Total time: 0 minutes 9 seconds, Site size: 0 Site pages: 0
...
BUILD FAILED
D:\Apache2\forrest\main\targets\site.xml:183: Error building site.
There appears to be a problem with your site build.
Output of /brokenlinks.xml:-
<broken-links>
<link
message="D:\Apache2\forrest\main\webapp\.\D:\Apache2\project\trunk\project\b
uild\tmp\D:\Apache2\forrest\build\plugins\dataModel.xmap (The filename,
directory name, or volume label syntax is incorrect)">linkmap.html</link>
</broken-links>
So, I'm not going to revert just yet, I'll have a look around, but if anyone
has any ideas ...
Gav...
>
> -David
>
>
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.6.17 - Release Date: 9/5/2008 12:00
> AM
Re: [heads-up] merging our branch Cocoon-2.1
Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
On Thu, 2008-09-11 at 14:35 +1000, David Crossley wrote:
> David Crossley wrote:
> > I will get on with merging the branch, hopefully tomorrow.
> >
> > I expect it to be smooth going, as people have been
> > working in other parts of the repository.
>
> No worries. That is done now. And FOR-955 is closed.
Thank you very much David. I tested on ubuntu and it works as expected.
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
Re: [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> I will get on with merging the branch, hopefully tomorrow.
>
> I expect it to be smooth going, as people have been
> working in other parts of the repository.
No worries. That is done now. And FOR-955 is closed.
I will proceed to document this, probably in
the "upgrading_09.html" doc.
When you first use this in your projects, there
will probably be a message about a certain cache item.
On the second run all is well. A way to avoid that
would be to do 'forrest clean-work' in each of your
projects to remove the Cocoon cache.
-David
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Brian M Dube <bd...@apache.org>.
On Thu, Sep 11, 2008 at 07:40:48PM +1000, David Crossley wrote:
> The new trunk using Cocoon-2.1 is working fine
> on these systems:
>
> Ubuntu - okay
> Mac OS X Tiger - okay
> Solaris10 - okay
>
> We have reports from one person with unknown troubles.
> Not sure what operating system (Windows?).
>
> Would other people test ASAP please.
It appears to work on Debian with Java 1.5, though the PDF
issue I'm trying to resolve still gets in the way of testing
properly.
Brian
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Sjur Moshagen <sj...@mac.com>.
Den 11. sep. 2008 kl. 12.40 skrev David Crossley:
> The new trunk using Cocoon-2.1 is working fine
> on these systems:
>
> Ubuntu - okay
> Mac OS X Tiger - okay
> Solaris10 - okay
forrest run
tested on MacOS X Leopard - okay
(can't test forrest site in my project, because of known i18n issues
with the CLI, but I would be surprised if the results differ from Tiger)
Sjur
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Please provide the error.log ... If it is too big
> then create a Jira Issue.
>
> After doing:
> ]$ cd main
> ]$ build test
>
https://issues.apache.org/jira/browse/FOR-1108
RE: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Friday, 12 September 2008 11:56 PM
> To: dev@forrest.apache.org
> Subject: Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
>
> David Crossley wrote:
> > Ross Gardler wrote:
> > > David Crossley wrote:
> > > >Or any other Windows developer can answer really.
> > >
> > > I'm afraid I can't right now. SVN is down./ If it comes up within the
> > > hour I should be able to test.
> >
> > Thanks.
> >
> > Yes, SVN still down:
> > http://apache.org/dev/#status
>
> You can switch to use the new Europoean SVN mirror.
> svn.eu.apache.org
> IIUC you cannot commit via there, only read.
> But i might be wrong.
You can commit to it, those in Europe might find it quicker, I didn't even
when it hardly being used.
Gav...
>
> -David
>
>
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.6.17/1657 - Release Date: 9/6/2008
> 8:07 PM
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Ross Gardler wrote:
> > David Crossley wrote:
> > >Or any other Windows developer can answer really.
> >
> > I'm afraid I can't right now. SVN is down./ If it comes up within the
> > hour I should be able to test.
>
> Thanks.
>
> Yes, SVN still down:
> http://apache.org/dev/#status
You can switch to use the new Europoean SVN mirror.
svn.eu.apache.org
IIUC you cannot commit via there, only read.
But i might be wrong.
-David
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> David Crossley wrote:
> >Or any other Windows developer can answer really.
>
> I'm afraid I can't right now. SVN is down./ If it comes up within the
> hour I should be able to test.
Thanks.
Yes, SVN still down:
http://apache.org/dev/#status
-David
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Or any other Windows developer can answer really.
I'm afraid I can't right now. SVN is down./ If it comes up within the
hour I should be able to test.
Ross
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
Jeremias Maerki wrote:
> Running on WinXP and Sun Java 1.4.2_16, I get failures, too. Here's an
> excerpt from the log doing "build test":
> ...
> These NPEs occur a number of times but the run continues and the skinned
> site completes.
>
> For the dispatcher site:
> ...
> ------------------------------------------------------------------------
> X [0] linkmap.html BROKEN: C:\Dev\apache.org\rw\forrest-trunk\main\webapp\.\C:\Dev\apache.org\rw\forrest-trunk\build\test_d
> ispatcher_site\build\tmp\C:\Dev\apache.org\rw\forrest-trunk\build\plugins\dataModel.xmap (The filename, directory name, or volume label syntax is incorrect)
That document is the first to be processed, so i suppose
that the same thing would happen if you changed the
"start-uri" in forrest.properties to be say index.html
meaning that it is not only related to the special "linkmap"
document.
Now that we have a captive tester :-)
Or any other Windows developer can answer really.
Please provide the error.log ... If it is too big
then create a Jira Issue.
After doing:
]$ cd main
]$ build test
It is at:
build/test_dispatcher_site/build/webapp/WEB-INF/logs/error.log
-David
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
Jeremias Maerki wrote:
> Sorry for not being reponsive enough. Still recovering from the flu and
> having a lot on my plate.
>
> Image loading has indeed changed in FOP 0.95. That's why the error
> messages can be different (hopefully more useful, too).
>
> I have no clue as to how the FOP upgrade can trigger that NPE. I thought
> it had something to do with the Cocoon version change, but apparently
> that's not the case. Shall I revert the FOP upgrade?
I reckon don't revert.
We need to get those errors to go into our logging
system rather than to standard output.
-David
> David Crossley wrote:
> > David Crossley wrote:
> > > Jeremias Maerki wrote:
> > > > ...
> > > > excerpt from the log doing "build test":
> > > >
> > > > ERROR - Image not found: cocoon:/images/icon-b.png
> > > > ERROR - Image not found: cocoon:/images/icon-b.png
> > > > java.lang.NullPointerException
> > > > at org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563)
> > > > at org.apache.cocoon.environment.wrapper.MutableEnvironmentFacade.release(MutableEnvironmentFacade.java:314)
> > > > at org.apache.cocoon.generation.FileGenerator.recycle(FileGenerator.java:64)
> > > > ...
> > >
> > > I get this issue too now. It was okay before but
> > > started now after your update commit of the fop-0.95.jar etc.
> >
> > Some clarification:
> >
> > Prior to today's fop-0.95 upgrade and since the fop-0.94 upgrade
> > we used to get a single error reported:
> > ERROR - Image not available: cocoon:/images/icon-b.png
> >
> > Now the error is reported differently.
> >
> > -David
>
> Jeremias Maerki
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Sorry for not being reponsive enough. Still recovering from the flu and
having a lot on my plate.
Image loading has indeed changed in FOP 0.95. That's why the error
messages can be different (hopefully more useful, too).
I have no clue as to how the FOP upgrade can trigger that NPE. I thought
it had something to do with the Cocoon version change, but apparently
that's not the case. Shall I revert the FOP upgrade?
On 12.09.2008 13:42:26 David Crossley wrote:
> David Crossley wrote:
> > Jeremias Maerki wrote:
> > > ...
> > > excerpt from the log doing "build test":
> > >
> > > ERROR - Image not found: cocoon:/images/icon-b.png
> > > ERROR - Image not found: cocoon:/images/icon-b.png
> > > java.lang.NullPointerException
> > > at org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563)
> > > at org.apache.cocoon.environment.wrapper.MutableEnvironmentFacade.release(MutableEnvironmentFacade.java:314)
> > > at org.apache.cocoon.generation.FileGenerator.recycle(FileGenerator.java:64)
> > > ...
> >
> > I get this issue too now. It was okay before but
> > started now after your update commit of the fop-0.95.jar etc.
>
> Some clarification:
>
> Prior to today's fop-0.95 upgrade and since the fop-0.94 upgrade
> we used to get a single error reported:
> ERROR - Image not available: cocoon:/images/icon-b.png
>
> Now the error is reported differently.
>
> -David
Jeremias Maerki
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Jeremias Maerki wrote:
> > ...
> > excerpt from the log doing "build test":
> >
> > ERROR - Image not found: cocoon:/images/icon-b.png
> > ERROR - Image not found: cocoon:/images/icon-b.png
> > java.lang.NullPointerException
> > at org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563)
> > at org.apache.cocoon.environment.wrapper.MutableEnvironmentFacade.release(MutableEnvironmentFacade.java:314)
> > at org.apache.cocoon.generation.FileGenerator.recycle(FileGenerator.java:64)
> > ...
>
> I get this issue too now. It was okay before but
> started now after your update commit of the fop-0.95.jar etc.
Some clarification:
Prior to today's fop-0.95 upgrade and since the fop-0.94 upgrade
we used to get a single error reported:
ERROR - Image not available: cocoon:/images/icon-b.png
Now the error is reported differently.
-David
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
Jeremias Maerki wrote:
> ...
> excerpt from the log doing "build test":
>
> ERROR - Image not found: cocoon:/images/icon-b.png
> ERROR - Image not found: cocoon:/images/icon-b.png
> java.lang.NullPointerException
> at org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563)
> at org.apache.cocoon.environment.wrapper.MutableEnvironmentFacade.release(MutableEnvironmentFacade.java:314)
> at org.apache.cocoon.generation.FileGenerator.recycle(FileGenerator.java:64)
> ...
I get this issue too now. It was okay before but
started now after your update commit of the fop-0.95.jar etc.
-David
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Running on WinXP and Sun Java 1.4.2_16, I get failures, too. Here's an
excerpt from the log doing "build test":
* [20/50] [0/0] 0.047s 200b skin/images/rc-b-r-5-1header-2tab-selected-3tab-selected.png
* [21/49] [0/0] 0.141s 6.8Kb samples-b/svg.pdf
* [22/49] [1/31] 0.39s 16.9Kb samples-b/howto-howto.html
* [23/48] [0/0] 0.219s 11.2Kb samples-c/index.pdf
* [24/47] [0/0] 0.234s 10.4Kb
* [25/46] [0/0] 0.032s 2.6Kb samples-b/xinclude.xml
* [26/45] [0/0] 0.031s 214b skin/images/rc-t-r-5-1header-2searchbox-3searchbox.png
* [27/44] [0/0] 0.047s 214b skin/images/rc-t-r-5-1header-2tab-unselected-3tab-unselected.png
* [28/43] [0/0] 0.172s 1.9Kb samples-b/ellipse.png
* [29/43] [1/34] 1.515s 12.1Kb samples-b/locationmap/index.html
* [30/42] [0/0] 0.297s 31.5Kb samples-b/howto-howto.pdf
* [31/41] [0/0] 0.047s 390b skin/images/rc-t-r-15-1body-2menu-3menu.png
* [32/41] [1/20] 1.016s 61.7Kb pluginDocs/plugins_0_90/index.html
^ pluginDocs/plugins_0_90/
^ samples-b/
* [33/54] [14/50] 0.437s 31.1Kb samples-b/linking.html
* [34/53] [0/0] 0.094s 1.9Kb /images/sub-dir/icon-c.png
* [35/52] [0/0] 0.031s 2.0Kb ../images/icon-b.png
* [36/51] [0/0] 0.078s 2.0Kb samples-b/icon-d.png
* [37/50] [0/0] 0.031s 1.1Kb hello.pdf
* [39/48] [0/0] 0.157s 1.9Kb /images/ellipse-2.png
ERROR - Image not found: cocoon:/images/icon-b.png
ERROR - Image not found: cocoon:/images/icon-b.png
java.lang.NullPointerException
at org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563)
at org.apache.cocoon.environment.wrapper.MutableEnvironmentFacade.release(MutableEnvironmentFacade.java:314)
at org.apache.cocoon.generation.FileGenerator.recycle(FileGenerator.java:64)
at org.apache.avalon.excalibur.pool.InstrumentedResourceLimitingPool.put(InstrumentedResourceLimitingPool.java:407)
at org.apache.avalon.excalibur.component.PoolableComponentHandler.doPut(PoolableComponentHandler.java:212)
at org.apache.avalon.excalibur.component.ComponentHandler.put(ComponentHandler.java:425)
at org.apache.avalon.excalibur.component.ExcaliburComponentSelector.release(ExcaliburComponentSelector.java:307)
at org.apache.cocoon.components.ExtendedComponentSelector.release(ExtendedComponentSelector.java:301)
at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.recycle(AbstractProcessingPipeline.java:723)
at org.apache.cocoon.components.pipeline.impl.BaseCachingProcessingPipeline.recycle(BaseCachingProcessingPipeline.java:78)
at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.recycle(AbstractCachingProcessingPipeline.java:1130)
at org.apache.avalon.excalibur.pool.InstrumentedResourceLimitingPool.put(InstrumentedResourceLimitingPool.java:407)
at org.apache.avalon.excalibur.component.PoolableComponentHandler.doPut(PoolableComponentHandler.java:212)
at org.apache.avalon.excalibur.component.ComponentHandler.put(ComponentHandler.java:425)
at org.apache.avalon.excalibur.component.ExcaliburComponentSelector.release(ExcaliburComponentSelector.java:307)
at org.apache.cocoon.components.ExtendedComponentSelector.release(ExtendedComponentSelector.java:301)
at org.apache.cocoon.components.EnvironmentDescription.release(CocoonComponentManager.java:695)
at org.apache.cocoon.components.CocoonComponentManager.endProcessing(CocoonComponentManager.java:262)
at org.apache.cocoon.Cocoon.process(Cocoon.java:739)
at org.apache.cocoon.bean.CocoonWrapper.getPage(CocoonWrapper.java:514)
at org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:499)
at org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:356)
at org.apache.cocoon.Main.main(Main.java:321)
java.lang.NullPointerException
at org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563)
at org.apache.cocoon.environment.wrapper.MutableEnvironmentFacade.release(MutableEnvironmentFacade.java:314)
at org.apache.cocoon.transformation.TraxTransformer.recycle(TraxTransformer.java:549)
at org.apache.avalon.excalibur.pool.InstrumentedResourceLimitingPool.put(InstrumentedResourceLimitingPool.java:407)
at org.apache.avalon.excalibur.component.PoolableComponentHandler.doPut(PoolableComponentHandler.java:212)
at org.apache.avalon.excalibur.component.ComponentHandler.put(ComponentHandler.java:425)
at org.apache.avalon.excalibur.component.ExcaliburComponentSelector.release(ExcaliburComponentSelector.java:307)
at org.apache.cocoon.components.ExtendedComponentSelector.release(ExtendedComponentSelector.java:301)
at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.recycle(AbstractProcessingPipeline.java:735)
at org.apache.cocoon.components.pipeline.impl.BaseCachingProcessingPipeline.recycle(BaseCachingProcessingPipeline.java:78)
at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.recycle(AbstractCachingProcessingPipeline.java:1130)
at org.apache.avalon.excalibur.pool.InstrumentedResourceLimitingPool.put(InstrumentedResourceLimitingPool.java:407)
at org.apache.avalon.excalibur.component.PoolableComponentHandler.doPut(PoolableComponentHandler.java:212)
at org.apache.avalon.excalibur.component.ComponentHandler.put(ComponentHandler.java:425)
at org.apache.avalon.excalibur.component.ExcaliburComponentSelector.release(ExcaliburComponentSelector.java:307)
at org.apache.cocoon.components.ExtendedComponentSelector.release(ExtendedComponentSelector.java:301)
at org.apache.cocoon.components.EnvironmentDescription.release(CocoonComponentManager.java:695)
at org.apache.cocoon.components.CocoonComponentManager.endProcessing(CocoonComponentManager.java:262)
at org.apache.cocoon.Cocoon.process(Cocoon.java:739)
at org.apache.cocoon.bean.CocoonWrapper.getPage(CocoonWrapper.java:514)
at org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:499)
at org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:356)
at org.apache.cocoon.Main.main(Main.java:321)
java.lang.NullPointerException
at org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563)
at org.apache.cocoon.environment.wrapper.MutableEnvironmentFacade.release(MutableEnvironmentFacade.java:314)
These NPEs occur a number of times but the run continues and the skinned
site completes.
For the dispatcher site:
Finished copying the non-generated resources.
Now Cocoon will generate the rest.
Static site will be generated at:
C:\Dev\apache.org\rw\forrest-trunk\build\test_dispatcher_site\build\site
Cocoon will report the status of each document:
- in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
------------------------------------------------------------------------
cocoon 2.1.12-dev
Copyright (c) 1999-2007 Apache Software Foundation. All rights reserved.
------------------------------------------------------------------------
X [0] linkmap.html BROKEN: C:\Dev\apache.org\rw\forrest-trunk\main\webapp\.\C:\Dev\apache.org\rw\forrest-trunk\build\test_d
ispatcher_site\build\tmp\C:\Dev\apache.org\rw\forrest-trunk\build\plugins\dataModel.xmap (The filename, directory name, or volume label syntax is incorrect)
Logging Error: Writing event to closed stream.
Total time: 0 minutes 1 seconds, Site size: 0 Site pages: 0
Java Result: 1
Copying broken links file to site root.
Copying 1 file to C:\Dev\apache.org\rw\forrest-trunk\build\test_dispatcher_site\build\site
BUILD FAILED
C:\Dev\apache.org\rw\forrest-trunk\main\build.xml:371: The following error occurred while executing this line:
C:\Dev\apache.org\rw\forrest-trunk\main\build.xml:373: The following error occurred while executing this line:
C:\Dev\apache.org\rw\forrest-trunk\main\build.xml:383: The following error occurred while executing this line:
C:\Dev\apache.org\rw\forrest-trunk\main\targets\site.xml:183: Error building site.
There appears to be a problem with your site build.
Read the output above:
* Cocoon will report the status of each document:
- in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
* Even if only one link is broken, you will still get "failed".
* Your site would still be generated, but some pages would be broken.
- See C:\Dev\apache.org\rw\forrest-trunk\build\test_dispatcher_site\build\site/broken-links.xml
Total time: 46 seconds
HTH
On 12.09.2008 00:22:53 Ross Gardler wrote:
> David Crossley wrote:
> > The new trunk using Cocoon-2.1 is working fine
> > on these systems:
> >
> > Ubuntu - okay
> > Mac OS X Tiger - okay
> > Solaris10 - okay
> >
> > We have reports from one person with unknown troubles.
> > Not sure what operating system (Windows?).
> >
> > Would other people test ASAP please.
>
> I can report that it *fails* on windows + cygwin at the dipatcher test.
>
> I'm currently building and deploying a production site and immediately
> reverted using the same command line shell so can't post the logs right now.
>
> Why do these things always occur at critical times? (that is not a
> complaint, merely an observation about life in an open source world, I
> am very grateful for the work David and Thorsten have done on this, I'm
> particularly grateful for Davids thoughtful post indicating which
> version I should revert to in order to get working, another observation
> about life in an open source world).
>
> I'll try and do a test again soon and send the log output.
>
> I'm afraid I'm unlikely to be able to debug it for at least a week
> though (although I will try)
>
> Ross
Jeremias Maerki
RE: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Tuesday, 23 September 2008 12:52 PM
> To: dev@forrest.apache.org
> Subject: Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
>
> Gavin wrote:
> >
> > I installed VMWare, now I have a dedicated Windows with the Forrest
> Trunk
> > installed (forrest_new). My other machine has the older currently
> working
> > with windows version (forrest_old).
>
> Just a note to ensure that you (and archive readers)
> know that one does not need a separate machine to run
> separate versions of Forrest. At least on UNIX-like systems.
>
> In two different directories, do separate svn checkouts
> of forrest trunk. Now "update" the "forrest_old" back to
> that certain revision 'svn up -r######'.
>
> In different shells, set $FORREST_HOME and $PATH to the
> relevant version of forrest.
Thanks, in Windows it seems one would need to manually set these each time a
new shell is opened, is it the same for unix-like ?
No problem though I created a simple setenv.bat file to set FORREST_HOME,
ANT_HOME & PATH.
>
> See the section "Multiple working copies":
> http://forrest.apache.org/howto-dev.html#multiple
That could do with expanding sometime I guess, all is really says it how to
store two different versions of Forrest, not how to run them as separate
entities.
Anyway, more testing underway, but that's for another thread.
Gav...
>
> -David
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.6.21 - Release Date: 9/11/2008
> 12:00 AM
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
Gavin wrote:
>
> I installed VMWare, now I have a dedicated Windows with the Forrest Trunk
> installed (forrest_new). My other machine has the older currently working
> with windows version (forrest_old).
Just a note to ensure that you (and archive readers)
know that one does not need a separate machine to run
separate versions of Forrest. At least on UNIX-like systems.
In two different directories, do separate svn checkouts
of forrest trunk. Now "update" the "forrest_old" back to
that certain revision 'svn up -r######'.
In different shells, set $FORREST_HOME and $PATH to the
relevant version of forrest.
See the section "Multiple working copies":
http://forrest.apache.org/howto-dev.html#multiple
-David
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> Gavin wrote:
> ...
> > Doing a 'forrest' or 'forrest site' on any site that only involves the pdf
> > plugin will work fine for both forrest_old and forrest_new generated sites
> > when run against the forrest_new trunk.
>
> Hmm, one thing is different from the pdf plugin in comparison with the
> e.g. dispatcher ones: it is not in the whiteboard.
>
> I wonder if any other plugin like e.g
> org.apache.forrest.plugin.output.Text is working as well.
>
> If so then we need to compare the difference between whiteboard and
> official plugin mounting.
Ah, good observations. So that is why the "site-author"
documentation would work - it uses various plugins, but
none of them are in the whiteboard.
-David
RE: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Thorsten Scherler <th...@apache.org>.
On Sun, 2008-09-21 at 14:13 +1000, Gavin wrote:
...
> Doing a 'forrest' or 'forrest site' on any site that only involves the pdf
> plugin will work fine for both forrest_old and forrest_new generated sites
> when run against the forrest_new trunk.
Hmm, one thing is different from the pdf plugin in comparison with the
e.g. dispatcher ones: it is not in the whiteboard.
I wonder if any other plugin like e.g
org.apache.forrest.plugin.output.Text is working as well.
If so then we need to compare the difference between whiteboard and
official plugin mounting.
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
RE: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Gavin [mailto:gavin@16degrees.com.au]
> Sent: Sunday, 21 September 2008 12:47 PM
> To: dev@forrest.apache.org
> Subject: RE: [STATUS] [heads-up] merging our branch Cocoon-2.1
>
>
>
> > -----Original Message-----
> > From: Thorsten Scherler [mailto:thorsten@apache.org]
> > Sent: Friday, 12 September 2008 8:45 AM
> > To: dev@forrest.apache.org
> > Subject: Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
> >
> > On Thu, 2008-09-11 at 23:22 +0100, Ross Gardler wrote:
> > > Why do these things always occur at critical times?
> >
> > Because it seems we failed to test on windows in the branch.
> >
> > David reports
> > > Ubuntu - okay
> > > Mac OS X Tiger - okay
> > > Solaris10 - okay
> >
> > Gavin tested and reported a fail and yourself confirmed that now.
> >
> > Ideally that have been spotted this problem in the branch and fixed it
> > there - not breaking trunk. Ideally.
> >
> > Many of us are not using windows at all that makes testing on windows so
> > much harder. Need to install vmware again.
> >
> > Will now review Gavins mail again.
>
> I installed VMWare, now I have a dedicated Windows with the Forrest Trunk
> installed (forrest_new). My other machine has the older currently working
> with windows version (forrest_old).
>
> I have done some scenarios, and basically they are that on both the
> forrest_old and forrest_new the conclusion is the same - plugins do not
> seem
> to work on forrest_new whether generated originally from forrest_new or
> forrest_old.
>
> forrest_old generated sites (including seed-basic and seed-sample) WILL
> work
> on forrest_new (trunk) as long as ONLY the PDF plugin is enabled. ANY
> other
> plugins will break forrest.
>
> Not has time to test much further yet.
To expand a little,
doing forrest run on a site and you can navigate all the html pages no
problem, but as soon as you request a page that involves a plugin - such as
.odt, .pod, .txt, whatever it will generate the error earlier described --
except the .pdf which still works fine.
Doing a forrest run on a dispatcher site will fails right away dur to the
plugin being in use even for html pages.
Doing a 'forrest' or 'forrest site' on any site that only involves the pdf
plugin will work fine for both forrest_old and forrest_new generated sites
when run against the forrest_new trunk.
Involve any other plugins whether generated with forrest_old or forrest_new
will fail with forrest_new.
Sites generated with forrest_new will build against forrest_old.
I looked through and there seems to be no difference in the generated sites,
it is only the involvement of plugins which break things. I hope this
narrows it down a little and that it is not a wild goose chase.
>
> Gav...
>
> >
> > salu2
> > --
> > Thorsten Scherler thorsten.at.apache.org
> > Open Source Java consulting, training and solutions
> >
> >
> > --
> > No virus found in this incoming message.
> > Checked by AVG.
> > Version: 7.5.524 / Virus Database: 270.6.17/1657 - Release Date:
> 9/6/2008
> > 8:07 PM
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.6.21 - Release Date: 9/11/2008
> 12:00 AM
RE: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Thorsten Scherler [mailto:thorsten@apache.org]
> Sent: Friday, 12 September 2008 8:45 AM
> To: dev@forrest.apache.org
> Subject: Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
>
> On Thu, 2008-09-11 at 23:22 +0100, Ross Gardler wrote:
> > Why do these things always occur at critical times?
>
> Because it seems we failed to test on windows in the branch.
>
> David reports
> > Ubuntu - okay
> > Mac OS X Tiger - okay
> > Solaris10 - okay
>
> Gavin tested and reported a fail and yourself confirmed that now.
>
> Ideally that have been spotted this problem in the branch and fixed it
> there - not breaking trunk. Ideally.
>
> Many of us are not using windows at all that makes testing on windows so
> much harder. Need to install vmware again.
>
> Will now review Gavins mail again.
I installed VMWare, now I have a dedicated Windows with the Forrest Trunk
installed (forrest_new). My other machine has the older currently working
with windows version (forrest_old).
I have done some scenarios, and basically they are that on both the
forrest_old and forrest_new the conclusion is the same - plugins do not seem
to work on forrest_new whether generated originally from forrest_new or
forrest_old.
forrest_old generated sites (including seed-basic and seed-sample) WILL work
on forrest_new (trunk) as long as ONLY the PDF plugin is enabled. ANY other
plugins will break forrest.
Not has time to test much further yet.
Gav...
>
> salu2
> --
> Thorsten Scherler thorsten.at.apache.org
> Open Source Java consulting, training and solutions
>
>
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.6.17/1657 - Release Date: 9/6/2008
> 8:07 PM
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Ross Gardler <rg...@apache.org>.
Thorsten Scherler wrote:
> On Thu, 2008-09-11 at 23:22 +0100, Ross Gardler wrote:
>> Why do these things always occur at critical times?
>
> Because it seems we failed to test on windows in the branch.
:-)
Fair comment (I'm especially glad I emphasised that I wasn't complaining
now - shame you stripped that - I look an ass in the archives now -
again I'm not complaining - I'm emarassed that I didn't test on windows
prior to the merge)
Ross
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Thorsten Scherler <th...@apache.org>.
On Thu, 2008-09-11 at 23:22 +0100, Ross Gardler wrote:
> Why do these things always occur at critical times?
Because it seems we failed to test on windows in the branch.
David reports
> Ubuntu - okay
> Mac OS X Tiger - okay
> Solaris10 - okay
Gavin tested and reported a fail and yourself confirmed that now.
Ideally that have been spotted this problem in the branch and fixed it
there - not breaking trunk. Ideally.
Many of us are not using windows at all that makes testing on windows so
much harder. Need to install vmware again.
Will now review Gavins mail again.
salu2
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
Re: [STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> The new trunk using Cocoon-2.1 is working fine
> on these systems:
>
> Ubuntu - okay
> Mac OS X Tiger - okay
> Solaris10 - okay
>
> We have reports from one person with unknown troubles.
> Not sure what operating system (Windows?).
>
> Would other people test ASAP please.
I can report that it *fails* on windows + cygwin at the dipatcher test.
I'm currently building and deploying a production site and immediately
reverted using the same command line shell so can't post the logs right now.
Why do these things always occur at critical times? (that is not a
complaint, merely an observation about life in an open source world, I
am very grateful for the work David and Thorsten have done on this, I'm
particularly grateful for Davids thoughtful post indicating which
version I should revert to in order to get working, another observation
about life in an open source world).
I'll try and do a test again soon and send the log output.
I'm afraid I'm unlikely to be able to debug it for at least a week
though (although I will try)
Ross
[STATUS] [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
The new trunk using Cocoon-2.1 is working fine
on these systems:
Ubuntu - okay
Mac OS X Tiger - okay
Solaris10 - okay
We have reports from one person with unknown troubles.
Not sure what operating system (Windows?).
Would other people test ASAP please.
-David
RE: [heads-up] merging our branch Cocoon-2.1
Posted by Gavin <ga...@16degrees.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Thursday, 11 September 2008 4:16 PM
> To: dev@forrest.apache.org
> Subject: Re: [heads-up] merging our branch Cocoon-2.1
>
> If anyone who uses trunk in production, urgently needs
> to get back to a working version, then do
>
> svn update -r 693831
Yep, working again now, I'll try head again over the next few days.
Gav...
>
> -David
>
>
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 270.6.17 - Release Date: 9/5/2008 12:00
> AM
Re: [heads-up] merging our branch Cocoon-2.1
Posted by David Crossley <cr...@apache.org>.
If anyone who uses trunk in production, urgently needs
to get back to a working version, then do
svn update -r 693831
-David