You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lenya.apache.org by Hubertus Groepper <hu...@groepper.com> on 2005/01/26 21:48:38 UTC

source install / docs

I have a couple of questions before attempting a patch to the source 
install document:

1. Is web.app.server mandatory? What happens when all entries are 
commented? (or uncommented?)
2. ./build.sh install gives:
		Buildfile: build.xml
		BUILD FAILED
		Target `install' does not exist in this project.

    Is this being replaced by build.sh without option but web.app.server 
in place?

3. What targets are available? It was discussed and agreed upon to 
provide a way for creating war-files to be deployed on a remote server. 
I assume that target "war" is what I need in this case. Build is 
successful, but an quite a lot of warnings occur. Should "war" go into 
the doc as option 3?
4. I still wonder about step 6 in tomcat install (Clear Tomcat work 
directory). Reset after a build will delete $TOMCAT_HOME/lenya, so 
reset should be issued only before installing a never version of lenya, 
or do I misunderstand this?
5. Is it still necessary to check all the endorsed libs? I know this 
has been a problem in the past, but more recently, I didn't notice any 
such errors being reported on the lists.

thanks,
hubertus


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: source install / docs

Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Michael Wechner wrote:

> yes, that's the idea, because the "install" target was only used for 
> Tomcat and hence a bit misleading. Also the "reset" target is only used 
> for Tomcat and should be integrated into the "clean" target

can you update the install instructions accordingly?


-- 
Gregor J. Rothfuss
COO, Wyona       Content Management Solutions    http://wyona.com
Apache Lenya                              http://lenya.apache.org
gregor.rothfuss@wyona.com                       gregor@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: source install / docs

Posted by Michael Wechner <mi...@wyona.com>.
Gregor J. Rothfuss wrote:

>
>>    Is this being replaced by build.sh without option but 
>> web.app.server in place?
>
>
> not that i know. michi?


yes, that's the idea, because the "install" target was only used for 
Tomcat and hence a bit misleading. Also the "reset" target is only used 
for Tomcat and should be integrated into the "clean" target

Michi


-- 
Michael Wechner
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: source install / docs

Posted by Michael Wechner <mi...@wyona.com>.
Gregor J. Rothfuss wrote:

> Hubertus Groepper wrote:
>
>> Hmm. I did a complete fresh checkout on a newly installed server  
>> (linux), and it doesn't work. Strange. Anybody else with that 
>> problem?  It used to work before for me, too.
>
>
> you are right. i didnt have the latest. this seems to be a regression.
>
>> so no install target here. Is this list complete otherwise?
>
>
> yes


the list is being automatically, whereas targets without a "description" 
will not be listed.

>>
>> The build process goes on with Generating Javadoc, and this is where 
>> I  get 71 warnings.
>> (random pick:  
>> /home/hubertus/lenya/BRANCH_1_2_X/build/lenya/src/org/apache/lenya/cms/ 
>> scheduler/AbstractSchedulerListener.java:68: warning - Tag @see: 
>> can't  find triggersResumed(java.lang.String, java.lang.String) in  
>> org.quartz.SchedulerListener)
>

because the Javadocs are not correct and need to be updated

>> Why do I need the javadocs?
>

because they used to be part of the documentation, which used to be 
shiped with the war file

>> In the end, finally:
>> war:
>> Created dir:  
>> /home/hubertus/lenya/BRANCH_1_2_X/dist/apache-lenya-1.2.2-dev-bin
>> Building jar:  
>> /home/hubertus/lenya/BRANCH_1_2_X/dist/apache-lenya-1.2.2-dev-bin/ 
>> lenya.war
>>
>> BUILD SUCCESSFUL
>
>
> michi, can you take a look? looks like your changes broke things


I don't think so, but I will take a look at it. I would rather assume, 
that the "war" target is out of sync, because everyone is using the 
"webapp" target, which is the default target.

Michi

>
>
>
>


-- 
Michael Wechner
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: source install / docs

Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Hubertus Groepper wrote:

> Hmm. I did a complete fresh checkout on a newly installed server  
> (linux), and it doesn't work. Strange. Anybody else with that problem?  
> It used to work before for me, too.

you are right. i didnt have the latest. this seems to be a regression.

> so no install target here. Is this list complete otherwise?

yes

> I did hubertus@hg:~/lenya/BRANCH_1_2_X$ ./build.sh war
> I get
> - check cocoon
> - init
> - prepare cocoon
> - do-not-patch-lucene
> - build-custom-tasks
> - prepare-src
> - compile
> - webapp
> Until here, everythings fine from my limited understanding of the build  
> process. Now, why's the  next step
> - install-tomcat (Copying 10106 files to /opt/tomcat/webapps/lenya) and
> - successfully-built-message-tomcat
> when I want to get a war-file?
> The build process goes on with Generating Javadoc, and this is where I  
> get 71 warnings.
> (random pick:  
> /home/hubertus/lenya/BRANCH_1_2_X/build/lenya/src/org/apache/lenya/cms/ 
> scheduler/AbstractSchedulerListener.java:68: warning - Tag @see: can't  
> find triggersResumed(java.lang.String, java.lang.String) in  
> org.quartz.SchedulerListener)
> Why do I need the javadocs?
> In the end, finally:
> war:
> Created dir:  
> /home/hubertus/lenya/BRANCH_1_2_X/dist/apache-lenya-1.2.2-dev-bin
> Building jar:  
> /home/hubertus/lenya/BRANCH_1_2_X/dist/apache-lenya-1.2.2-dev-bin/ 
> lenya.war
> 
> BUILD SUCCESSFUL

michi, can you take a look? looks like your changes broke things




-- 
Gregor J. Rothfuss
COO, Wyona       Content Management Solutions    http://wyona.com
Apache Lenya                              http://lenya.apache.org
gregor.rothfuss@wyona.com                       gregor@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: source install / docs

Posted by Hubertus Groepper <hu...@groepper.com>.
Am 26.01.2005 um 23:51 schrieb Gregor J. Rothfuss:

> Hubertus Groepper wrote:
>> I have a couple of questions before attempting a patch to the source  
>> install document:
>> 1. Is web.app.server mandatory? What happens when all entries are  
>> commented? (or uncommented?)
>> 2. ./build.sh install gives:
>>         Buildfile: build.xml
>>         BUILD FAILED
>>         Target `install' does not exist in this project.
>
> i just tried build.bat install on 1.2, and it worked
Hmm. I did a complete fresh checkout on a newly installed server  
(linux), and it doesn't work. Strange. Anybody else with that problem?  
It used to work before for me, too.
>
>>    Is this being replaced by build.sh without option but  
>> web.app.server in place?
>
> not that i know. michi?
Some small hint in the docs would be appreciated.
>
>> 3. What targets are available?
>
> run build -projecthelp to find out
thanks.
hubertus@hg:~/lenya/BRANCH_1_2_X$ ./build.sh -projecthelp gives
Buildfile: build.xml
Main targets:

  check-cocoon            Check if Cocoon webapp exists
  clean                   Cleans the build directories
  cocoon-does-not-exist   Check if Cocoon webapp exists
  compile                 Compile the sources
  deprecation             Compile the sources with deprecation messages
  dist                    Build all distribution relevant tarballs
  dist-bin                Build a regular binary distribution tar ball
  dist-src                Builds a regular tar ball containing the  
sources for developers
  eclipse-project         Generate the Eclipse project files
  eclipse-webapp-prepare  Prepares the webapp directory to make it  
usable within Eclipse
  export                  Exports a publication to static HTML.
  install-pub             Install a publication into servlet engine  
context. Usage: -Dpub.prefix=blog
  install-tomcat          Install the webapp into Tomcat servlet engine  
context
  javadocs                Generates the API documentation
  kupu                    Build Kupu
  reset                   Resets the deployment by also cleaning the  
servlet engine context
  snapshot-bin            Build a snapshot binary distribution tar ball  
(the same as 'dist' except for the filename)
  snapshot-src            Builds a snapshot tar ball containing the  
sources for developers (the same as 'dist-src' except for the filename)
  test                    Runs all tests
  war                     Builds the deployable war file
  webapp                  Builds the webapp directory ready to be linked  
into a servlet engines context directory
  zip-webapp              Zips the webapp in order to deploy within  
another servlet container
Default target: webapp

so no install target here. Is this list complete otherwise?
>
>> It was discussed and agreed upon to provide a way for creating  
>> war-files to be deployed on a remote server. I assume that target  
>> "war" is what I need in this case. Build is successful, but an quite  
>> a lot of warnings occur. Should "war" go into the doc as option 3?
>
> sure. what errors do you get?
I did hubertus@hg:~/lenya/BRANCH_1_2_X$ ./build.sh war
I get
- check cocoon
- init
- prepare cocoon
- do-not-patch-lucene
- build-custom-tasks
- prepare-src
- compile
- webapp
Until here, everythings fine from my limited understanding of the build  
process. Now, why's the  next step
- install-tomcat (Copying 10106 files to /opt/tomcat/webapps/lenya) and
- successfully-built-message-tomcat
when I want to get a war-file?
The build process goes on with Generating Javadoc, and this is where I  
get 71 warnings.
(random pick:  
/home/hubertus/lenya/BRANCH_1_2_X/build/lenya/src/org/apache/lenya/cms/ 
scheduler/AbstractSchedulerListener.java:68: warning - Tag @see: can't  
find triggersResumed(java.lang.String, java.lang.String) in  
org.quartz.SchedulerListener)
Why do I need the javadocs?
In the end, finally:
war:
Created dir:  
/home/hubertus/lenya/BRANCH_1_2_X/dist/apache-lenya-1.2.2-dev-bin
Building jar:  
/home/hubertus/lenya/BRANCH_1_2_X/dist/apache-lenya-1.2.2-dev-bin/ 
lenya.war

BUILD SUCCESSFUL


>
>> 4. I still wonder about step 6 in tomcat install (Clear Tomcat work  
>> directory). Reset after a build will delete $TOMCAT_HOME/lenya, so  
>> reset should be issued only before installing a never version of  
>> lenya, or do I misunderstand this?
>
> cocoon stores compiled classes obtained from xsp in work, among other  
> things. you want to be sure that you don't have stale files sitting  
> around
Sorry, I don't understand. Does this mean I have to clear the  
work-directory after every lenya (re-)install? And then, why does this  
wipe away the entire installation in TOMCAT_HOME/webapps/lenya? Still  
confused as to the order of install / reset.
>
>> 5. Is it still necessary to check all the endorsed libs? I know this  
>> has been a problem in the past, but more recently, I didn't notice  
>> any such errors being reported on the lists.
>
> better to be extra sure. i think its mostly gone, but then i don't  
> deal with tomcat..
OK.
>
thanks,
hubertus
> -- 
> Gregor J. Rothfuss
> COO, Wyona       Content Management Solutions    http://wyona.com
> Apache Lenya                              http://lenya.apache.org
> gregor.rothfuss@wyona.com                       gregor@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: source install / docs

Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Hubertus Groepper wrote:
> I have a couple of questions before attempting a patch to the source 
> install document:
> 
> 1. Is web.app.server mandatory? What happens when all entries are 
> commented? (or uncommented?)
> 2. ./build.sh install gives:
>         Buildfile: build.xml
>         BUILD FAILED
>         Target `install' does not exist in this project.

i just tried build.bat install on 1.2, and it worked

>    Is this being replaced by build.sh without option but web.app.server 
> in place?

not that i know. michi?

> 3. What targets are available? 

run build -projecthelp to find out

> It was discussed and agreed upon to 
> provide a way for creating war-files to be deployed on a remote server. 
> I assume that target "war" is what I need in this case. Build is 
> successful, but an quite a lot of warnings occur. Should "war" go into 
> the doc as option 3?

sure. what errors do you get?

> 4. I still wonder about step 6 in tomcat install (Clear Tomcat work 
> directory). Reset after a build will delete $TOMCAT_HOME/lenya, so reset 
> should be issued only before installing a never version of lenya, or do 
> I misunderstand this?

cocoon stores compiled classes obtained from xsp in work, among other 
things. you want to be sure that you don't have stale files sitting around

> 5. Is it still necessary to check all the endorsed libs? I know this has 
> been a problem in the past, but more recently, I didn't notice any such 
> errors being reported on the lists.

better to be extra sure. i think its mostly gone, but then i don't deal 
with tomcat..

-- 
Gregor J. Rothfuss
COO, Wyona       Content Management Solutions    http://wyona.com
Apache Lenya                              http://lenya.apache.org
gregor.rothfuss@wyona.com                       gregor@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Windows log4j-Bug

Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Gregor J. Rothfuss wrote:
> Michael Wechner wrote:
> 
>> Patches welcome ;-) whereas this path setting should become obsolete
>> in the near future since we are currently introducing "LogEnabled".
> 
> 
> actually, it only needs the patch to web.xml to make log4j the default

this has now be done. we may want to apply

http://issues.apache.org/bugzilla/show_bug.cgi?id=32434

at some point. currently, all log messages go into one file, log4j.log


-- 
Gregor J. Rothfuss
COO, Wyona       Content Management Solutions    http://wyona.com
Apache Lenya                              http://lenya.apache.org
gregor.rothfuss@wyona.com                       gregor@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Windows log4j-Bug

Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Michael Wechner wrote:

> Patches welcome ;-) whereas this path setting should become obsolete
> in the near future since we are currently introducing "LogEnabled".

actually, it only needs the patch to web.xml to make log4j the default

-- 
Gregor J. Rothfuss
COO, Wyona       Content Management Solutions    http://wyona.com
Apache Lenya                              http://lenya.apache.org
gregor.rothfuss@wyona.com                       gregor@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Windows log4j-Bug

Posted by Michael Wechner <mi...@wyona.com>.
Michael Pohl wrote:

>
>
> I couldn't find the place where log4j.log.file is set...


build.properties resp. local.build.properties

Patches welcome ;-) whereas this path setting should become obsolete
in the near future since we are currently introducing "LogEnabled".

Michi

>
> Yours,
> Michael Pohl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>


-- 
Michael Wechner
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Windows log4j-Bug

Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Michael Pohl wrote:
> I found a Bug concerning Windows and log4j:
> 
> When log4j is first invoked by Lenya, I got following message (I think 
> it's in all versions, but for sure it's in the SVN-Checkout from 
> yesterday):
> 
> log4j:ERROR setFile(null,true) call failed.
> java.io.FileNotFoundException: 
> C:srclenya-1.2.x\build\lenya\webapp\WEB-INF\logs\log4j.log  [...]

i need to switch 1.2 to use a relative log4j path (already implemented 
in trunk)


-- 
Gregor J. Rothfuss
COO, Wyona       Content Management Solutions    http://wyona.com
Apache Lenya                              http://lenya.apache.org
gregor.rothfuss@wyona.com                       gregor@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Windows log4j-Bug

Posted by Michael Pohl <Po...@gmx.net>.
I found a Bug concerning Windows and log4j:

When log4j is first invoked by Lenya, I got following message (I think 
it's in all versions, but for sure it's in the SVN-Checkout from yesterday):

log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: 
C:srclenya-1.2.x\build\lenya\webapp\WEB-INF\logs\log4j.log  [...]

I had a look at the build\lenya\webapp\WEB-INF\classes\log4j.properties 
and there I found:

log4j.appender.A1.File=C:\src\lenya-1.2.x/build/lenya/webapp/WEB-INF/logs/log4j.log

So the first part of the path is Windows-style and should also be 
UNIX-style. I found after some looking in src\targets\init-build.xml 
(quite trimmed):

<project name="init">
  <target name="prepare-src" depends="prepare, build-custom-tasks">
     <xslt
         in="${java.dir}/log4j-properties.xsl"
         out="${build.src}/log4j.properties"
         style="${java.dir}/log4j-properties.xsl"
         force="false"
         >
       <param name="log4j-rollingFileAppender-File"
	expression="${log4j.log.file}"/>
     </xslt>
  </target>
</project>

I couldn't find the place where log4j.log.file is set...

Yours,
Michael Pohl

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: source install / docs

Posted by Michael Wechner <mi...@wyona.com>.
Hubertus Groepper wrote:

> I have a couple of questions before attempting a patch to the source 
> install document:
>
> 1. Is web.app.server mandatory?


kind of, whereas Jetty is default and basically corresponds to no 
special setup except the log4j path, which should become obsolete soon.

> What happens when all entries are commented? (or uncommented?)


to be honest, I don't know. Just give it a try ;-)

> 2. ./build.sh install gives:
>         Buildfile: build.xml
>         BUILD FAILED
>         Target `install' does not exist in this project.
>
>    Is this being replaced by build.sh without option but 
> web.app.server in place?


right (needs to be documented though)

>
>
> 3. What targets are available?


ant -projecthelp

> It was discussed and agreed upon to provide a way for creating 
> war-files to be deployed on a remote server. I assume that target 
> "war" is what I need in this case.


yes, if the Servlet Engine is left to be open. As mentioned above, the 
log4j path needs to be modified by hand

     WEB-INF/classes/log4j.properties

after unpacking the war file

> Build is successful, but an quite a lot of warnings occur. Should 
> "war" go into the doc as option 3?


probably makes sense

> 4. I still wonder about step 6 in tomcat install (Clear Tomcat work 
> directory). Reset after a build will delete $TOMCAT_HOME/lenya, so 
> reset should be issued only before installing a never version of 
> lenya, or do I misunderstand this?


no, that's correct, but beware that also the data will be deleted if the 
"exclude" properties are not set.

> 5. Is it still necessary to check all the endorsed libs? I know this 
> has been a problem in the past, but more recently, I didn't notice any 
> such errors being reported on the lists.


yes, I would recommend so

HTH

Michi

>
>
> thanks,
> hubertus
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>


-- 
Michael Wechner
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
michael.wechner@wyona.com                        michi@apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org