Released vs Snapshot blocks

[Felix Knecht]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all

I stated some problems using not yet released blocks mixed with the released c22 ones.

Having an application based on the released c22 core stuff but using some non released 'SNAPSHOT blocks I stated that I
wasn't able to use the SNAPSHOT blocks because they are wired with the cocoon-core snapshot.
Building and deploying locally the snapshot blocks and then using them maven also wants to pull in the latest
cocoon-core 2.2.1-SNAPSHOT (probably because of parent poms).

Can't we base for the non released blocks on the released cocoon-core 2.2 where possible?

WDOT?

Felix

PS:
I tried my best to say what I mean but I'm not really sure if it's comprehensible ...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkhqOtQACgkQ2lZVCB08qHHz+gCg2cJhvAWODTmrbCWNACcYI7de
FTsAnAvSWmRyCExIAQp3IIM6CDNyDMnk
=1RLB
-----END PGP SIGNATURE-----

[Felix Knecht-2]

Sorry for the noise!

In spite of checking it several times I haven't seen my misconfiguration
somewhere in the deep :-(

But at least it helped me to write about it - it finally solved my
blindness.

Felix

> Hi all
>
> I stated some problems using not yet released blocks mixed with the
> released c22 ones.
>
> Having an application based on the released c22 core stuff but using
> some non released 'SNAPSHOT blocks I stated that I
> wasn't able to use the SNAPSHOT blocks because they are wired with the
> cocoon-core snapshot.
> Building and deploying locally the snapshot blocks and then using them
> maven also wants to pull in the latest
> cocoon-core 2.2.1-SNAPSHOT (probably because of parent poms).
>
> Can't we base for the non released blocks on the released cocoon-core
> 2.2 where possible?
>
> WDOT?
>
> Felix
>
> PS:
> I tried my best to say what I mean but I'm not really sure if it's
> comprehensible ...