You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Thorsten Scherler <th...@juntadeandalucia.es> on 2004/05/24 09:27:08 UTC

Build.sh and build.bat creating just JAR

Hello group,

anybody having the same problem like I do:

If I use the build.sh (Debain@work) or the build.bat (XP@home) the just 
create the
- /build/xml-forrest.jar
- /build/classes

...but the "build/dist/shbat" is missing.

What is wrong and what can I do to get the "build/dist/shbat"?

NOTE:
This I noticed the first time at the weekend. I am using current SVN-Head.

-- 
Thorsten Scherler

Departamento de Desarrollo de Proyectos
Sociedad Andaluza para el Desarrollo de la Sociedad de la Información S.A.U.
Avda. de la Arboleda s/n
41940 - Tomares,  (Sevilla)
Tlfn: (+34) 955 062 627
e-mail: thorsten.scherler.ext@juntadeandalucia.es

Este correo electrónico y, en su caso, cualquier fichero anexo al mismo,
contiene información de carácter confidencial exclusivamente dirigida a su
destinatario o destinatarios. Queda prohibida su divulgación, copia o
distribución a terceros sin la previa autorización escrita de "Sociedad
Andaluza para el Desarrollo de la Sociedad de la Información, S.A.U.". Si no
es Ud. el destinatario del mensaje le ruego lo destruya sin hacer copia
digital o física, comunicando a Sociedad Andaluza para el Desarrollo de la
Sociedad de la Información S.A.U. vía e-mail o fax la recepción del presente
mensaje. Toda declaración de voluntad contenida deberá ser tenida por no
producida. Gracias.
____________________________________________________________________________
___________________

The information in this e-mail and in any attachments is confidential and
solely for the attention and use of the named addressee(s). You are hereby
notified that any dissemination, distribution or copy of this communication
is prohibited without the prior written consent of "Sociedad Andaluza para
el Desarrollo de la Sociedad de la Información, S.A.U.". If you are not the
formal receiver of this message please destroy it without making any digital
or physical copy and inform "Sociedad Andaluza para el Desarrollo de la
Sociedad de la Información S.A.U." , by e-mail or fax, of the reception of
the present message. Any whatsoever involuntary declaration contained
herewith must be taken as having no legal effect. Thank you.



Re: Build.sh and build.bat creating just JAR

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
Yup (on 5 minutes old SVN). Passing 'dist' as a command line argument to
build.sh, gave them to me.

regards

Adam
----- Original Message ----- 
From: "Thorsten Scherler" <th...@juntadeandalucia.es>
To: <fo...@xml.apache.org>
Sent: Monday, May 24, 2004 1:27 AM
Subject: Build.sh and build.bat creating just JAR


> Hello group,
>
> anybody having the same problem like I do:
>
> If I use the build.sh (Debain@work) or the build.bat (XP@home) the just
> create the
> - /build/xml-forrest.jar
> - /build/classes
>
> ...but the "build/dist/shbat" is missing.
>
> What is wrong and what can I do to get the "build/dist/shbat"?
>
> NOTE:
> This I noticed the first time at the weekend. I am using current SVN-Head.
>
> -- 
> Thorsten Scherler
>
> Departamento de Desarrollo de Proyectos
> Sociedad Andaluza para el Desarrollo de la Sociedad de la Información
S.A.U.
> Avda. de la Arboleda s/n
> 41940 - Tomares,  (Sevilla)
> Tlfn: (+34) 955 062 627
> e-mail: thorsten.scherler.ext@juntadeandalucia.es
>
> Este correo electrónico y, en su caso, cualquier fichero anexo al mismo,
> contiene información de carácter confidencial exclusivamente dirigida a su
> destinatario o destinatarios. Queda prohibida su divulgación, copia o
> distribución a terceros sin la previa autorización escrita de "Sociedad
> Andaluza para el Desarrollo de la Sociedad de la Información, S.A.U.". Si
no
> es Ud. el destinatario del mensaje le ruego lo destruya sin hacer copia
> digital o física, comunicando a Sociedad Andaluza para el Desarrollo de la
> Sociedad de la Información S.A.U. vía e-mail o fax la recepción del
presente
> mensaje. Toda declaración de voluntad contenida deberá ser tenida por no
> producida. Gracias.
>
____________________________________________________________________________
> ___________________
>
> The information in this e-mail and in any attachments is confidential and
> solely for the attention and use of the named addressee(s). You are hereby
> notified that any dissemination, distribution or copy of this
communication
> is prohibited without the prior written consent of "Sociedad Andaluza para
> el Desarrollo de la Sociedad de la Información, S.A.U.". If you are not
the
> formal receiver of this message please destroy it without making any
digital
> or physical copy and inform "Sociedad Andaluza para el Desarrollo de la
> Sociedad de la Información S.A.U." , by e-mail or fax, of the reception of
> the present message. Any whatsoever involuntary declaration contained
> herewith must be taken as having no legal effect. Thank you.
>
>


Re: Build.sh and build.bat creating just JAR

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> The copyless branch works by parsing forrest.properties and using that
> directly without ANT, while before you could set the properties and have
> Ant insert them.
>
> Guys, is this a feature we want to keep?

I was using it. It allowed me to set these values dynamically (from the Gump
workspace). Can you think of an alternative approach for me? I'd hate to
have to parse/re-write forrest.properties on the fly.

regards

Adam


Re: Build.sh and build.bat creating just JAR

Posted by Nicola Ken Barozzi <ni...@apache.org>.
Adam R. B. Jack wrote:
...
> but Gump's "content" (dir above content/xdocs) is in forrest-work/ not
> forrest-work/src/documentation. I found the forrest.properties file was
> commented out (nothing explicitly set) but see I set it on commandline. It
> seems like the commandline options is being ignored, or similar.

Correct.

The copyless branch works by parsing forrest.properties and using that 
directly without ANT, while before you could set the properties and have 
Ant insert them.

Guys, is this a feature we want to keep?

> BTW: Whilst I am here (and for Gump running forrest) is there an exit code
> difference from 'failed to build one page of your many' and 'failed to build
> any pages' (due to a validation error)? Right now Gump can't tell the
> difference, so sometimes gets/gives empty sites.

There is no difference AFAIK now, but it should be different... please 
file a bug report.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


Re: Build.sh and build.bat creating just JAR

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> > The files (images, RSS, Atom) I put into content/X/Y/Z/ get transferred
> > across, but not files I
> > put into content/xdocs/ (to get converted from xdocs to HTML).
>
> I don't get this part... they should be *generated* by Forrest, not
> "transferred across".

Clearly this isn't my day for communications (first Gump Storm, then apology
blog goes belly up, now this). Let me try one more time...

I put content that I do NOT ask Forrest to generate into ./content [e.g.
./content/ant/rss.xml  and ./content/ant/atom.xml] and the content I DO ask
Forrest to generate into ./content/xdocs [e.g.
./content/xdocs/ant/index.xml.] Forrest transfers the things I produce (the
rss.xml atom.xml are mine, not from Forrest) and it generates index.html
giving me:

        {site}/ant/rss.xml
        {site}/ant/atom.xml
and
        {site}/ant/index.html

What I am saying is the transfer occurs (I get the first two) but not the
last one. As this is an ant copy (I think), that makes some sense.

BTW: I tried getting a password reminded for cocoon's JIRA and it crashed w/
a NPE. I'll try to get the bug/enhancement report (for two exit codes for
some vs none) when I can.

regards

Adam


Re: Build.sh and build.bat creating just JAR

Posted by Nicola Ken Barozzi <ni...@apache.org>.
Adam R. B. Jack wrote:
...
>>>>Hmm, also, when I set project.content-dir in the forrest.properties
>> and use
>>>this manually, I seem to get the content/** files transferred, but not
>>>content/xdoc/** ones. I get the www site structure w/o any *.html files.
>>
>>Transferred? You mean rendered or something else?
> 
> The files (images, RSS, Atom) I put into content/X/Y/Z/ get transferred
> across, but not files I
> put into content/xdocs/ (to get converted from xdocs to HTML).

I don't get this part... they should be *generated* by Forrest, not 
"transferred across".

> Is the 'copy
> raw contents' aspects still using Ant, and hence accepting commandline
> overrides?

Yes, that's correct. What I still don't get is why the files are not 
generated by forrest even if you put a forrest.properties file that 
tells where to find them.

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


Re: Build.sh and build.bat creating just JAR

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> > Hmm, also, when I set project.content-dir in the forrest.properties and
use
> > this manually, I seem to get the content/** files transferred, but not
> > content/xdoc/** ones. I get the www site structure w/o any *.html files.
>
> Transferred? You mean rendered or something else?
>
> -- 
> Nicola Ken Barozzi                   nicolaken@apache.org
>              - verba volant, scripta manent -
>     (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
> > > Hmm, also, when I set project.content-dir in the forrest.properties
and
use
> > this manually, I seem to get the content/** files transferred, but not
> > content/xdoc/** ones. I get the www site structure w/o any *.html files.
>
> Transferred? You mean rendered or something else?

The files (images, RSS, Atom) I put into content/X/Y/Z/ get transferred
across, but not files I
put into content/xdocs/ (to get converted from xdocs to HTML). Is the 'copy
raw contents' aspects still using Ant, and hence accepting commandline
overrides?

regards,

Adam


Re: Build.sh and build.bat creating just JAR

Posted by Nicola Ken Barozzi <ni...@apache.org>.
Adam R. B. Jack wrote:

>>Executing:
>> 
>> forrest -Djava.awt.headless=true -Dproject.content-dir=. -Dproject.site-dir=
>>/homelocal/build/gump/local/gump-ws/forrest-staging
> 
> Hmm, also, when I set project.content-dir in the forrest.properties and use
> this manually, I seem to get the content/** files transferred, but not
> content/xdoc/** ones. I get the www site structure w/o any *.html files.

Transferred? You mean rendered or something else?

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


Re: Build.sh and build.bat creating just JAR

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> Executing:
>
forrest -Djava.awt.headless=true -Dproject.content-dir=. -Dproject.site-dir=
> /homelocal/build/gump/local/gump-ws/forrest-staging

Hmm, also, when I set project.content-dir in the forrest.properties and use
this manually, I seem to get the content/** files transferred, but not
content/xdoc/** ones. I get the www site structure w/o any *.html files.

regards,

Adam


Re: Build.sh and build.bat creating just JAR

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> To use the new Forrest launch "build" as you already have done, and then
>   change FORREST_HOME to point to [forrest]/src/core.

Ok, so I ignored what I wrote & tried this.

> We need more testing to check that all remaining issues are ironed out
> before a release, so bug reports and suggestions are welcome :-)

We'll, I was about to say it worked for me, but although it did (manually),
it didn't work from Gump. Gump executed:

Executing:
forrest -Djava.awt.headless=true -Dproject.content-dir=. -Dproject.site-dir=
/homelocal/build/gump/local/gump-ws/forrest-staging

and received:

X [0]                                     index.html    BROKEN:
/homelocal/build
/gump/local/gump-ws/forrest-work/src/documentation/skinconf.xml (No such
file or
 directory)
Total time: 0 minutes 7 seconds,  Site size: 0 Site pages: 0

but Gump's "content" (dir above content/xdocs) is in forrest-work/ not
forrest-work/src/documentation. I found the forrest.properties file was
commented out (nothing explicitly set) but see I set it on commandline. It
seems like the commandline options is being ignored, or similar.

BTW: Whilst I am here (and for Gump running forrest) is there an exit code
difference from 'failed to build one page of your many' and 'failed to build
any pages' (due to a validation error)? Right now Gump can't tell the
difference, so sometimes gets/gives empty sites.

regards,

Adam


Re: Build.sh and build.bat creating just JAR

Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> As soon I come home I will apply the patch and see what will happen with 
> my (so far) halfbaked skin ;-). Will let you know about any success or 
> failure related to FOR-146.

The "patch" is already in the trunk head. It was applied
to the "copyless" branch and recently merged back. So you
already have it.

--David



Re: Build.sh and build.bat creating just JAR

Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
David Crossley wrote:

>Scherler, Thorsten wrote:
>  
>
>>Nicola Ken Barozzi wrote:
>>    
>>
>>>[...] 
>>>We need more testing to check that all remaining issues are ironed out 
>>>before a release, so bug reports and suggestions are welcome :-)
>>>      
>>>
>>So far everything works great!
>>    
>>
>
>Good to hear. If there are any tips that you can add to
>upgrading_06.xml then please do.
>
>  
>

Yeah will do as soon as I figured out *how* exactly I can update from 04 
to 06 ;-).
It is quite tricky because we (the lenya project) used our own forrest 
dis within a lenya pub. I haven't really figured out how this exactly 
works,  so I decided to build from the ground up.  ...to get some 
practical knowlege about forrest. I did it like this:
(1) forrest seed
(2) copy the relevant lenya-xdocs to the xdocs folder of the new seed
(3) get the lenya skin working (I am now here since a while) ;-)

>You said that you are using your own skin. Please see the notes
>in the "Upgrading" and "Changes" documents about FOR-146 issue.
>It warns people to check that this part of skin changes does not
>affect your project. It would be nice to hear whether or not it did.
>
>  
>

As soon I come home I will apply the patch and see what will happen with 
my (so far) halfbaked skin ;-). Will let you know about any success or 
failure related to FOR-146.

>>Cheers you guys, keep it up ;-)
>>    
>>
>
>Yes please. Everyone who discusses on this forrest-dev
>is one of "you guys", not just the committers.
>
>  
>

Yeah, you are right but this time especially the guys who implemented 
the copyless branch ;-).
 
...and I am feeling to become one of "you guys" too :) LOL ;-)

>--David
>
>
>
>
>  
>


-- 
Thorsten Scherler

Departamento de Desarrollo de Proyectos
Sociedad Andaluza para el Desarrollo de la Sociedad de la Información S.A.U.
Avda. de la Arboleda s/n
41940 - Tomares,  (Sevilla)


Re: Build.sh and build.bat creating just JAR

Posted by David Crossley <cr...@apache.org>.
Scherler, Thorsten wrote:
> Nicola Ken Barozzi wrote:
> 
> > We have just included in the trunk the changes done on the copyless 
> > branch. In essence, Forrest does not create a dist anymore, and uses 
> > itself in place. No more useless copying, no more backcopying bugfixes, 
> > all is used live.
> 
> Jupp, that is great! I am trying to get the lenya-site to the newest 
> SVN-Head of forrest! I had some problems with the skins so I copied the 
> "lenya-site" (skin) into the "src/core/context/skins". Then I had to 
> build all the time the new forrest because had to use a step by step 
> approach to find the code that is causing the problem! ...but that 
> (building all the time) is gone now! *GREAT* -> it saves me heaps of time!
> 
> >[...] 
> > We need more testing to check that all remaining issues are ironed out 
> > before a release, so bug reports and suggestions are welcome :-)
> 
> So far everything works great!

Good to hear. If there are any tips that you can add to
upgrading_06.xml then please do.

You said that you are using your own skin. Please see the notes
in the "Upgrading" and "Changes" documents about FOR-146 issue.
It warns people to check that this part of skin changes does not
affect your project. It would be nice to hear whether or not it did.

> Cheers you guys, keep it up ;-)

Yes please. Everyone who discusses on this forrest-dev
is one of "you guys", not just the committers.

--David



Re: Build.sh and build.bat creating just JAR

Posted by "Scherler, Thorsten" <th...@apache.org>.
Nicola Ken Barozzi wrote:

> Thorsten Scherler wrote:
> 
>> Hello group,
>>
>> anybody having the same problem like I do:
>>
>> If I use the build.sh (Debain@work) or the build.bat (XP@home) the 
>> just create the
>> - /build/xml-forrest.jar
>> - /build/classes
>>
>> ...but the "build/dist/shbat" is missing.
>>
>> What is wrong and what can I do to get the "build/dist/shbat"?
>>
>> NOTE:
>> This I noticed the first time at the weekend. I am using current 
>> SVN-Head.
> 
> 
> This is a new feature :-)
> 

LOL -> It is not a bug, it's a feature! ...but this time it is true :)

> We have just included in the trunk the changes done on the copyless 
> branch. In essence, Forrest does not create a dist anymore, and uses 
> itself in place. No more useless copying, no more backcopying bugfixes, 
> all is used live.
> 

Jupp, that is great! I am trying to get the lenya-site to the newest 
SVN-Head of forrest! I had some problems with the skins so I copied the 
"lenya-site" (skin) into the "src/core/context/skins". Then I had to 
build all the time the new forrest because had to use a step by step 
approach to find the code that is causing the problem! ...but that 
(building all the time) is gone now! *GREAT* -> it saves me heaps of time!

>[...] 
> We need more testing to check that all remaining issues are ironed out 
> before a release, so bug reports and suggestions are welcome :-)
> 

So far everything works great!

Cheers you guys, keep it up ;-)

King regards
thorsten
-- 
<thorsten>
  <name>Thorsten Scherler</name>
  <country>Spain</country>
  <@mail> thorsten@apache.org</...@mail>
  <@cocoon-WIKI> 
http://wiki.cocoondev.org/Wiki.jsp?page=Scherler</...@cocoon-WIKI>
  <http>http://www.target-x.de</http>
</thorsten>



Re: Build.sh and build.bat creating just JAR

Posted by Nicola Ken Barozzi <ni...@apache.org>.
Thorsten Scherler wrote:
> Hello group,
> 
> anybody having the same problem like I do:
> 
> If I use the build.sh (Debain@work) or the build.bat (XP@home) the just 
> create the
> - /build/xml-forrest.jar
> - /build/classes
> 
> ...but the "build/dist/shbat" is missing.
> 
> What is wrong and what can I do to get the "build/dist/shbat"?
> 
> NOTE:
> This I noticed the first time at the weekend. I am using current SVN-Head.

This is a new feature :-)

We have just included in the trunk the changes done on the copyless 
branch. In essence, Forrest does not create a dist anymore, and uses 
itself in place. No more useless copying, no more backcopying bugfixes, 
all is used live.

To use the new Forrest launch "build" as you already have done, and then 
  change FORREST_HOME to point to [forrest]/src/core.

We need more testing to check that all remaining issues are ironed out 
before a release, so bug reports and suggestions are welcome :-)

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------


Re: Build.sh and build.bat creating just JAR

Posted by Dave Brondsema <da...@brondsema.net>.
The 'copyless' branch got merged into the HEAD.  It improved the build
process a lot.

Set FORREST_HOME to .../src/core instead of .../build/dist/shbat
And make sure PATH gets update to use the new $FORREST_HOME/bin

Dave

On Mon, 24 May 2004, Thorsten Scherler wrote:

> Hello group,
>
> anybody having the same problem like I do:
>
> If I use the build.sh (Debain@work) or the build.bat (XP@home) the just
> create the
> - /build/xml-forrest.jar
> - /build/classes
>
> ...but the "build/dist/shbat" is missing.
>
> What is wrong and what can I do to get the "build/dist/shbat"?
>
> NOTE:
> This I noticed the first time at the weekend. I am using current SVN-Head.
>
>

-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org