On Aug 5, 2008, at 12:52 AM, Grzegorz Kossakowski wrote:
Just checkout trunk (master in Git) and say:
mvn clean install [-P allblocks]
This -P allblocks switch is optional and probably self-explaining.
right... been there and done that, but I didn't know that this built
the samples too (ha
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=106668&projectId=51
Build statistics:
State: Ok
Previous State: Failed
Started at: Tue 5 Aug 2008 15:19:35 -0700
Finished at: Tue 5 Aug 2008 15:31:53 -0700
Total time: 12m 17s
Build Trigger: Schedule
Build Numb
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=106631&projectId=51
Build statistics:
State: Failed
Previous State: Ok
Started at: Tue 5 Aug 2008 13:09:55 -0700
Finished at: Tue 5 Aug 2008 13:10:13 -0700
Total time: 17s
Build Trigger: Schedule
Build Number:
Gregorz,
I'm not really sure if I have the karma to do that as well, but I just
changed the one in
http://svn.apache.org/repos/asf/cocoon/trunk/commons/KEYS
Did you copy it from there, or is the KEYS file in the dist folder
located elsewhere in the SVN?
Regards,
Jeroen
David Crossley wro
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=106628&projectId=51
Build statistics:
State: Ok
Previous State: Failed
Started at: Tue 5 Aug 2008 11:08:57 -0700
Finished at: Tue 5 Aug 2008 11:22:52 -0700
Total time: 13m 55s
Build Trigger: Schedule
Build Numb
On Tue, Aug 5, 2008 at 8:07 AM, Grzegorz Kossakowski <[EMAIL PROTECTED]> wrote:
> Hello,
>
> As discussed in thread "Cocoon-jms-sample requires Java >= 1.5"[1] there are
> more and more problems with keeping Java 1.4 compatibility in trunk.
>
> After a while it turned out that everybody agrees on t
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=106615&projectId=51
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 5 Aug 2008 09:53:49 -0700
Finished at: Tue 5 Aug 2008 09:54:20 -0700
Total time: 31s
Build Trigger: Schedule
Build Numb
Grzegorz Kossakowski escribió:
Hello,
As discussed in thread "Cocoon-jms-sample requires Java >= 1.5"[1]
there are more and more problems with keeping Java 1.4 compatibility
in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility and in th
I'm a bit confused.
I fact this commit should 'revert' commit r682756 (and I can't see any difference) but with rr682754 my trunk is
building whereas I can't build trunk with rr682756:
$ svn up
$ svn up -r 682754 parent/pom.xml
$ mvn clean install --> works
$ svn up -r 682756 parent/pom.xml
$ m
Grzegorz Kossakowski wrote:
[EMAIL PROTECTED] pisze:
Author: cziegeler
Date: Mon Aug 4 11:49:15 2008
New Revision: 682461
URL: http://svn.apache.org/viewvc?rev=682461&view=rev
Log:
Move api from impl to api.
Sorry for this - damn Eclipse is not telling you when a commit is
failing. It preten
Hi,
2008/8/5 Grzegorz Kossakowski <[EMAIL PROTECTED]>:
> After a while it turned out that everybody agrees on the need for dropping
> Java 1.4 compatibility and in that case, switching to Java 1.5 as minimal
> required version seems to be the best solution.
+1
Andrew.
--
[EMAIL PROTECTED] / [E
+1
Grzegorz Kossakowski wrote:
Hello,
As discussed in thread "Cocoon-jms-sample requires Java >= 1.5"[1]
there are more and more problems with keeping Java 1.4 compatibility
in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility and in t
Grzegorz Kossakowski wrote:
I believe that this dependency was stored on our snapshots repository,
but now it seems to be empty, see:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/commons/javaflow/
More interesting thing is that, it seems to be empty for any other
artifact.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Andrew Savory
> Sent: dinsdag 5 augustus 2008 6:09
> To: dev@cocoon.apache.org
> Subject: Re: [Vote] Jasha Joachimsthal as new Cocoon committer
>
> Hi,
>
> 2008/7/29 Andrew Savory <[EMAIL PROTECTED]>:
Grzegorz Kossakowski wrote:
Please cast your votes:
+1
Regards,
Jeroen Reijn
Reinhard Pötz pisze:
Grzegorz Kossakowski wrote:
Hello,
As discussed in thread "Cocoon-jms-sample requires Java >= 1.5"[1]
there are more and more problems with keeping Java 1.4 compatibility
in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 comp
Grzegorz Kossakowski wrote:
Hello,
As discussed in thread "Cocoon-jms-sample requires Java >= 1.5"[1] there
are more and more problems with keeping Java 1.4 compatibility in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility and in that c
Grzegorz Kossakowski wrote
Please cast your votes:
+1
Jeroen
Grzegorz Kossakowski skrev:
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility and in that case, switching to Java
1.5 as minimal required version seems to be the best solution.
+1
/Daniel
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility and in that case, switching to Java
1.5 as minimal required version seems to be the best solution.
+1
Felix
Grzegorz Kossakowski wrote:
Hello,
As discussed in thread "Cocoon-jms-sample requires Java >= 1.5"[1] there
are more and more problems with keeping Java 1.4 compatibility in trunk.
After a while it turned out that everybody agrees on the need for
dropping Java 1.4 compatibility and in that c
Hello,
As discussed in thread "Cocoon-jms-sample requires Java >= 1.5"[1] there are more and more problems
with keeping Java 1.4 compatibility in trunk.
After a while it turned out that everybody agrees on the need for dropping Java 1.4 compatibility
and in that case, switching to Java 1.5 as
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=106557&projectId=51
Build statistics:
State: Failed
Previous State: Failed
Started at: Tue 5 Aug 2008 05:41:12 -0700
Finished at: Tue 5 Aug 2008 05:54:49 -0700
Total time: 13m 36s
Build Trigger: Schedule
Build
[EMAIL PROTECTED] pisze:
Author: cziegeler
Date: Mon Aug 4 11:49:15 2008
New Revision: 682461
URL: http://svn.apache.org/viewvc?rev=682461&view=rev
Log:
Move api from impl to api.
Carsten, this commit seems to break our build:
[ERROR] BUILD FAILURE
[INFO] ---
Hello,
I noticed that fresh build with allblocks enabled of Cocoon's trunk does not work because of missing
dependency:
[INFO]
[ERROR] BUILD ERROR
[INFO]
Daniel Fagerstrom wrote:
it's great to see you here again!
Reinhard Pötz skrev:
Carsten Ziegeler wrote:
Reinhard Pötz wrote:
You guys have finally convinced me. Let's use 3.0.x for Corona,
clearly state that it is alpha software on the website in the
README.txt of each release artifact and
Reinhard Pötz skrev:
Carsten Ziegeler wrote:
Reinhard Pötz wrote:
You guys have finally convinced me. Let's use 3.0.x for Corona,
clearly state that it is alpha software on the website in the
README.txt of each release artifact and see what's happening.
Then we only need to find a package na
ServletSource cannot be used outside of pipeline context
Key: COCOON-2231
URL: https://issues.apache.org/jira/browse/COCOON-2231
Project: Cocoon
Issue Type: Bug
Components: *
Carsten Ziegeler wrote:
Reinhard Pötz wrote:
You guys have finally convinced me. Let's use 3.0.x for Corona,
clearly state that it is alpha software on the website in the
README.txt of each release artifact and see what's happening.
Then we only need to find a package name that isn't used in
Mark Lundquist pisze:
Hi, how can I build my own samples webapp? I guess it can be done:
http://cocoon.zones.apache.org/demos/trunk/
:-)
I thought maybe "mvn install" in dists/cocoon-dist-samples, but no go;
it was missing these dependencies:
org.apache.cocoon:cocoon-blocks-fw-demo
Reinhard Pötz wrote:
You guys have finally convinced me. Let's use 3.0.x for Corona,
clearly state that it is alpha software on the website in the
README.txt of each release artifact and see what's happening.
Then we only need to find a package name that isn't used in trunk
because Corona sho
31 matches
Mail list logo
