On Tue, Sep 22, 2009 at 9:58 PM, Steven D. Majewski sd...@virginia.eduwrote:
We've been using Cocoon 2.1.* for some time now, but we haven't really been
doing a proper build.
We've been building the sample app, and using that as a development base,
adding new pipelines
and sitemaps, and
On Wed, Sep 23, 2009 at 8:22 AM, Dominic Mitchell d...@happygiraffe.netwrote:
My first question would have been: are the dependencies correct? What
happens if you run mvn dependency:tree in the webapp? It should include
spring dependencies.
For reference, this is what I get when running
myBlock1 myBlock2 seem to have all the right dependencies (and they
work on their own),
but myCocoonWebapp has only the jars from those two blocks:
[INFO]
[INFO] [dependency:tree {execution: default-cli}]
[INFO]
,
Robby Pelssers
-Original Message-
From: Steven D. Majewski [mailto:sd...@virginia.edu]
Sent: Wednesday, September 23, 2009 6:04 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
myBlock1 myBlock2 seem to have all the right
On Wed, Sep 23, 2009 at 5:03 PM, Steven D. Majewski sd...@virginia.eduwrote:
myBlock1 myBlock2 seem to have all the right dependencies (and they work
on their own),
but myCocoonWebapp has only the jars from those two blocks:
[INFO]
On Sep 23, 2009, at 1:45 PM, Dominic Mitchell wrote:
On Wed, Sep 23, 2009 at 5:03 PM, Steven D. Majewski sd...@virginia.edu
wrote:
myBlock1 myBlock2 seem to have all the right dependencies (and
they work on their own),
but myCocoonWebapp has only the jars from those two blocks:
[INFO]
I can create, 'mvn install' 'mvn jetty:run' both myBlock1 myBlock2.
When I try to connect the two blocks as in http://cocoon.apache.org/2.2/1291_1_1.html
,
I get this error on either a jetty:run or an install:
myBlock1$ mvn jetty:run
[INFO] Scanning for projects...
[INFO]
On Wed, Sep 23, 2009 at 7:22 PM, Steven D. Majewski sd...@virginia.eduwrote:
I can create, 'mvn install' 'mvn jetty:run' both myBlock1 myBlock2.
When I try to connect the two blocks as in
http://cocoon.apache.org/2.2/1291_1_1.html,
I get this error on either a jetty:run or an install:
On Wed, Sep 23, 2009 at 6:50 PM, Steven D. Majewski sd...@virginia.eduwrote:
Thanks. Yes -- I saw that observation in the other message.
However: it wouldn't build doing just a 'mvn install' on the blocks.
Was there a particular reason for the failure when you ran mvn install in
the blocks?
On Sep 23, 2009, at 2:22 PM, Steven D. Majewski wrote:
If I comment out the myBlock2 dependency in myBlock1/pom.xml which I
just added:
!--
dependency
groupIdedu.virginia.lib/groupId
artifactIdmyBlock2/artifactId
version1.0-SNAPSHOT/version
/dependency
--
:23 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
I can create, 'mvn install' 'mvn jetty:run' both myBlock1 myBlock2.
When I try to connect the two blocks as in
http://cocoon.apache.org/2.2/1291_1_1.html
,
I get this error
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you correctly you have one block depending on the
other?
Did you also add the dependency of myblock2 in the pom.xml of
myblock1?
Yes. ( And if I take that dependency out, it runs without complaint. )
I guess so...
On Wed, Sep 23, 2009 at 7:44 PM, Steven D. Majewski sd...@virginia.eduwrote:
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you correctly you have one block depending on the
other?
Did you also add the dependency of myblock2 in the pom.xml of myblock1?
Yes. ( And
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you correctly you have one block depending on the
other?
Did you also add the dependency of myblock2 in the pom.xml
On Sep 23, 2009, at 2:50 PM, Dominic Mitchell wrote:
On Wed, Sep 23, 2009 at 7:44 PM, Steven D. Majewski sd...@virginia.edu
wrote:
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you correctly you have one block depending on the
other?
Did you also add the dependency
On Wed, Sep 23, 2009 at 7:57 PM, Steven D. Majewski sd...@virginia.eduwrote:
On Sep 23, 2009, at 2:50 PM, Dominic Mitchell wrote:
On Wed, Sep 23, 2009 at 7:44 PM, Steven D. Majewski sd...@virginia.edu
wrote:
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you
[mailto:sd...@virginia.edu]
Sent: Wednesday, September 23, 2009 8:45 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out
with
Cocoon 2.2]
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you correctly you have one block depending
this will not work anymore.
So don't think you're there yet ;-)
Robby
-Original Message-
From: Steven D. Majewski [mailto:sd...@virginia.edu]
Sent: Wednesday, September 23, 2009 8:58 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2
]
Sent: Wednesday, September 23, 2009 9:02 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
On Sep 23, 2009, at 2:56 PM, Robby Pelssers wrote:
Ok...
Check in eclipse the value of M2_REPO:
Window - Preferences - Java - Build path
Pelssers [mailto:robby.pelss...@ciber.com]
Sent: Wednesday, September 23, 2009 9:10 PM
To: users@cocoon.apache.org
Subject: RE: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
Aha... so that explains why the myBlock2.jar IS still in the
classpath... lol
If you were to do mvn
...@ciber.com]
Sent: Wednesday, September 23, 2009 9:10 PM
To: users@cocoon.apache.org
Subject: RE: problems with Getting Started 2.2 [was: Starting out
with
Cocoon 2.2]
Aha... so that explains why the myBlock2.jar IS still in the
classpath... lol
If you were to do mvn eclipse:eclipse again
. Majewski [mailto:sd...@virginia.edu]
Sent: Wednesday, September 23, 2009 9:22 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
On Sep 23, 2009, at 3:14 PM, Robby Pelssers wrote:
Ok...here is what I want you to do in this order
To: users@cocoon.apache.org
Subject: RE: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
Could you attach both poms to a reply? I'd love to see if I can track
down some mistake there... It's really getting stranger by the minute...
I wouldn't expect maven to complain without
: problems with Getting Started 2.2 [was: Starting out
with
Cocoon 2.2]
Could you attach both poms to a reply? I'd love to see if I can track
down some mistake there... It's really getting stranger by the
minute...
I wouldn't expect maven to complain without a good reason. Maybe some
small
To: users@cocoon.apache.org
Subject: RE: problems with Getting Started 2.2 [was: Starting out
with
Cocoon 2.2]
Could you attach both poms to a reply? I'd love to see if I can track
down some mistake there... It's really getting stranger by the
minute...
I wouldn't expect maven to complain
On Wed, Sep 23, 2009 at 9:18 PM, Steven D. Majewski sd...@virginia.eduwrote:
Thank You!!
Both 1.0.0 and 1.0-SNAPSHOT are mismatched in the documentation.
I was following the instructions a little too exactly!
I wondered about this mismatch at the time, but I thought that
perhaps SNAPSHOT
@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with Cocoon
2.2]
On Wed, Sep 23, 2009 at 9:18 PM, Steven D. Majewski sd...@virginia.edu wrote:
Thank You!!
Both 1.0.0 and 1.0-SNAPSHOT are mismatched in the documentation.
I
On Sep 23, 2009, at 4:39 PM, Robby Pelssers wrote:
True… the same here… but if I had no prior maven knowledge this
might be a bit trickier to spot. I guess it’s time to have that
documentation published again… HINT HINT.
Robby
This may also need updating:
We've been using Cocoon 2.1.* for some time now, but we haven't really
been doing a proper build.
We've been building the sample app, and using that as a development
base, adding new pipelines
and sitemaps, and eventually, removing the samples directory before
deploying.
I've started to
PS: That
Could not instantiate listener
org.springframework.web.context.ContextLoaderListener
java.lang.ClassNotFoundException:
org.springframework.web.context.ContextLoaderListener
[ ... stack trace ... ]
warning is the first of several messages. There is also:
2009-09-22
.. I always use mvn jetty:run on an
individual block while developing.
Kind regards,
Robby Pelssers
-Original Message-
From: Steven D. Majewski [mailto:sd...@virginia.edu]
Sent: Tuesday, September 22, 2009 11:38 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2
31 matches
Mail list logo
