Hi!
But at least some poms needed to be updated and my understand was, that
core and core15 were released together. This morning I learned the truth
In fact I think it was my fault as Matthias told me that there is
something wrong with the poms and I haven't thought about it any further.
On 10/19/07, Simon Kitching <[EMAIL PROTECTED]> wrote:
ie soon core15 will be released (hopefully). Is this release going to be:
a) "core15-1.0", with core not being re-released, or
+1
b) "core15-1.1" plus "core1.1", even if core has not changed?
-1
Make core, core15, sandbox and examples depend on myfaces-orchestra-maven 1.0,
not 1.1-SNAPSHOT.
+1
Reset sandbox to depend on core15 1.0-snapshot.
The sandbox and the examples should always use the latest snapshots. I
think we will never release the sandbox nor the examples, no?
====
Oddly, core15, sandbox and examples currently do not have a version# in the
pom. I guess they are inheriting
the one from the parent, but that isn't right AIUI: the parent pom is being
used here just to control
what reports, buildsettings, etc are used - not defining the actual version of
the module being built.
Yep, this is something I discovered during the release process and then
forgot to change the other modules.
So - to sum up what I think it should look like:
* everything depends on maven 1.0
* core15 on core 1.0 - core15 should be released as core15 1.0
* examples, sandbox depends on core15 1.0-snapshot and core 1.1-snapshot
Ciao,
Mario
