If you have already tested the RC1 release (take 1 or take 2), you have to
remove the artifacts from your local repository. Otherwise Maven won't download
them again.
- o -
The proposed release artifacts are available at
xweber pisze:
Hi Grzegorz,
Hi Alex,
RCL [create]:
/home/xweber/tmp/cocoon/test/myBlock1/./target/classes/demo/MyBean.class
2007-06-23 23:11:02.460:/:INFO: Initializing Spring root
WebApplicationContext
2007-06-23 23:11:03.961::WARN: Failed startup of context
[EMAIL PROTECTED]
...
Caused
:
http://www.nabble.com/-test--Cocoon-2.2-RC1---others-%28take-2%29-tf3965214.html#a11274504
Sent from the Cocoon - Dev mailing list archive at Nabble.com.
Thanx for that
Alex
--
View this message in context:
http://www.nabble.com/-test--Cocoon-2.2-RC1---others-%28take-2%29-tf3965214.html#a11275862
Sent from the Cocoon - Dev mailing list archive at Nabble.com.
xweber pisze:
Hi,
I tried to follow the tutorials with latest rc1 files.
(http://cocoon.zones.apache.org/daisy/cdocs/g2/g2/g1/1291.html)
On the connecting example (Connect two blocks) I receive an error like
java.lang.RuntimeException: Cannot invoke listener
[EMAIL PROTECTED]
..
Unable to
configurations from classpath
..
on mvn jetty:run startup
Maybe it is related to the rc1 build.
Alex
--
View this message in context:
http://www.nabble.com/-test--Cocoon-2.2-RC1---others-%28take-2%29-tf3965214.html#a11267783
Sent from the Cocoon - Dev mailing list archive at Nabble.com.
Reinhard Poetz pisze:
The proposed release artifacts are available at
http://people.apache.org/builds/cocoon/.
Except for the archetypes the easiest way to test the artifacts is by
adding a
cocoon-staging profile to your ~/.m2/settings.xml:
snip/
Then change the version number of the
a wanted syntax error for validation to check something.
If you want i can run through all examples in rc1 and give a more complete
list of problems.
Alex
--
View this message in context:
http://www.nabble.com/-test--Cocoon-2.2-RC1---others-%28take-2%29-tf3965214.html#a11268794
Sent from
xweber pisze:
Hi Grzegorz,
Grzegorz Kossakowski wrote:
I think you found little trap in our current setup. When two blocks
containing demo classes are connected they define exactly the same
Spring component (same package and same component id) twice. In my setup
this does not lead to
says:
HTTP ERROR: 503
SERVICE_UNAVAILABLE
RequestURI=/myBlock1/
Powered by jetty://
I even tried it with a clean second dir + attempt to build the steps.
Alex
--
View this message in context:
http://www.nabble.com/-test--Cocoon-2.2-RC1---others-%28take-2%29-tf3965214.html#a11270315
Sent from
The proposed release artifacts are available at
http://people.apache.org/builds/cocoon/.
Except for the archetypes the easiest way to test the artifacts is by adding a
cocoon-staging profile to your ~/.m2/settings.xml:
settings
profiles
profile
idcocoon-staging/id
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
Leszek Gawron wrote:
Reinhard Poetz wrote:
The proposed release artifacts are available at
http://people.apache.org/builds/cocoon/.
Why is there no release of cocoon spring configurator?
because there has already been a final release 1.0.0 of
Reinhard Poetz pisze:
The proposed release artifacts are available at
http://people.apache.org/builds/cocoon/.
Except for the archetypes the easiest way to test the artifacts is by
adding a
cocoon-staging profile to your ~/.m2/settings.xml:
settings
profiles
profile
Grzegorz Kossakowski pisze:
Reinhard Poetz pisze:
POM file of commons-jci-core is not downloaded because
apache-m2-snapshot is not used while searching for this pom file.
However, when Maven tries to download jar file it uses
apache-m2-snpashot repository declared cocoon-rcl-webapp-wrapper.
Reinhard Poetz wrote:
Leszek Gawron wrote:
Reinhard Poetz wrote:
The proposed release artifacts are available at
http://people.apache.org/builds/cocoon/.
Why is there no release of cocoon spring configurator?
because there has already been a final release 1.0.0 of it and there
haven't
The proposed release artifacts are available at
http://people.apache.org/builds/cocoon/.
Except for the archetypes the easiest way to test the artifacts is by adding a
cocoon-staging profile to your ~/.m2/settings.xml:
settings
profiles
profile
idcocoon-staging/id
Reinhard Poetz wrote:
The proposed release artifacts are available at
http://people.apache.org/builds/cocoon/.
Why is there no release of cocoon spring configurator?
--
Leszek Gawron http://www.mobilebox.pl/krs.html
CTO at MobileBox Ltd.
Leszek Gawron wrote:
Reinhard Poetz wrote:
The proposed release artifacts are available at
http://people.apache.org/builds/cocoon/.
Why is there no release of cocoon spring configurator?
because there has already been a final release 1.0.0 of it and there haven't
been any changes that
18 matches
Mail list logo