Bertrand Delacretaz wrote:
On 10/31/06, Reinhard Poetz <[EMAIL PROTECTED]> wrote:
...I entered
0 1,5,9,13,17,21 * * * /home/maven/continuum-project-builder/run.sh >
/home/maven/cron.log
Isn't that missing a field? You should have 5 values or stars, with
hours in second position:
* 0 1,5,9,1
On 10/31/06, Reinhard Poetz <[EMAIL PROTECTED]> wrote:
...I entered
0 1,5,9,13,17,21 * * * /home/maven/continuum-project-builder/run.sh >
/home/maven/cron.log
Isn't that missing a field? You should have 5 values or stars, with
hours in second position:
* 0 1,5,9,13,17,21 * * *
And this shou
Reinhard Poetz wrote:
I need some help with crontab at the Cocoon zone. I want to add the
script /home/maven/continuum-project-builder/run.sh to the crontab of
the Maven user.
I tried
0 0 0/4 * * /home/maven/continuum-project-builder/run.sh >
/home/maven/cron.log
I entered
0 1,5,9,13,17
I need some help with crontab at the Cocoon zone. I want to add the script
/home/maven/continuum-project-builder/run.sh to the crontab of the Maven user.
I tried
0 0 0/4 * * /home/maven/continuum-project-builder/run.sh > /home/maven/cron.log
but this results in following error message:
cron
+1
Before we start changing directory structures, I think it makes
sense to
vote.
The proposal is to use the following directory structure inside a
block jar:
COB-INF - resources
META-INF/cocoon/xconf/**
META-INF/cocoon/spring/**
META-INF/cocoon/properties/**
Please cast your votes.
--
On 31.10.2006 08:59, Carsten Ziegeler wrote:
The proposal is to use the following directory structure inside a block jar:
COB-INF - resources
META-INF/cocoon/xconf/**
META-INF/cocoon/spring/**
META-INF/cocoon/properties/**
+1
Jörg
2006/10/31, Carsten Ziegeler <[EMAIL PROTECTED]>:
Before we start changing directory structures, I think it makes sense to
vote.
The proposal is to use the following directory structure inside a block jar:
COB-INF - resources
META-INF/cocoon/xconf/**
META-INF/cocoon/spring/**
META-INF/cocoon/pr
how why?!
if I use it outside cocoon with a server.xml enty
username
memyself
marcel_011 wrote:
why I get this msg when I try to connect to domino database the same way a I
do with mySQL?:
java.lang.AbstractMethodError:
lotus.jdbc.domino.DominoConnection.prepareStatement(Ljava/lang/String;II)Ljava/sql/PreparedStatement;
You need to implement this method in your JDBC dri
Carsten Ziegeler wrote:
Before we start changing directory structures, I think it makes sense to
vote.
The proposal is to use the following directory structure inside a block jar:
COB-INF - resources
META-INF/cocoon/xconf/**
META-INF/cocoon/spring/**
META-INF/cocoon/properties/**
Please cast y
why I get this msg when I try to connect to domino database the same way a I
do with mySQL?:
java.lang.AbstractMethodError:
lotus.jdbc.domino.DominoConnection.prepareStatement(Ljava/lang/String;II)Ljava/sql/PreparedStatement;
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Daniel Fagerstrom wrote:
Alexander Klimetschek skrev:
the ResourceReader must throw any IOException caught in generate()
(line 349). This is currently not done because it looks like there are
cases, where a failed generate should be silently ignored. The debug
message says "Received an IOExcep
On 10/31/06, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
Before we start changing directory structures, I think it makes sense to
vote.
The proposal is to use the following directory structure inside a block jar:
COB-INF - resources
META-INF/cocoon/xconf/**
META-INF/cocoon/spring/**
META-INF/co
While I found it strange that a "mvn clean" complains about a missing
plugin that should be built through maven itself, a "mvn install"
seems to get me further ...but obviously now our xreporter and daisy
deps are gone.
Downloading:
http://repo1.maven.org/maven2/xreporter/xreporter-expression/r6
On 10/31/06, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
...The proposal is to use the following directory structure inside a block jar:
COB-INF - resources
META-INF/cocoon/xconf/**
META-INF/cocoon/spring/**
META-INF/cocoon/properties/**...
+1
-Bertrand
Carsten Ziegeler wrote:
Before we start changing directory structures, I think it makes sense to
vote.
The proposal is to use the following directory structure inside a block jar:
COB-INF - resources
META-INF/cocoon/xconf/**
META-INF/cocoon/spring/**
META-INF/cocoon/properties/**
Please cast y
Carsten Ziegeler wrote:
> Before we start changing directory structures, I think it makes sense to
> vote.
>
> The proposal is to use the following directory structure inside a block jar:
>
> COB-INF - resources
> META-INF/cocoon/xconf/**
> META-INF/cocoon/spring/**
> META-INF/cocoon/properties/*
Just doing a "mvn clean" I get
...
[INFO] [clean:clean]
[INFO] Deleting directory
/Users/tcurdt/Development/cocoon/trunk/tools/cocoon-block-deployer/cocoon-deployer-plugin/target
[INFO] Deleting directory
/Users/tcurdt/Development/cocoon/trunk/tools/cocoon-block-deployer/cocoon-deployer-plugin/ta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carsten Ziegeler wrote:
> Before we start changing directory structures, I think it makes sense to
> vote.
>
> The proposal is to use the following directory structure inside a block jar:
>
> COB-INF - resources
> META-INF/cocoon/xconf/**
> META-IN
On 10/31/06, David Crossley <[EMAIL PROTECTED]> wrote:
...It is very important to acknowledge everyone who is involved,
otherwise a community cannot be built...
Agreed, I like these lists too.
I agree with Antonio that "other contributors" is not perfect wording,
but I can't think of anything
Before we start changing directory structures, I think it makes sense to
vote.
The proposal is to use the following directory structure inside a block jar:
COB-INF - resources
META-INF/cocoon/xconf/**
META-INF/cocoon/spring/**
META-INF/cocoon/properties/**
Please cast your votes.
Carsten
--
Ca
21 matches
Mail list logo
