Hi Philipp
you should use Maven for releases (also for internal ones, I suggest),
next time try the following:

run "mvn release:prepare" from the root of the trunk

(I just added a new pom there, unfortunately the maven release plugin
can't work correctly if run from a parent module -magnolia-project-
which is at the same level of its children)

It will check that you don't have any locally modified file before
proceeding, then it will ask you the release version for each module
(this time for example you shold use "3.0-m2"). It will change the
version in each pom, then it will ask you the tag name (should be to
"magnolia-3.0-m2").
It will then tag the release in svn, then ask you a new version for
the "next development iteration". This MUST be a -SNAPSHOT, so you can
either enter 3.0-SNAPSHOT again or better 3.0-b1-SNAPSHOT. It will
change the pom once again and recommit everything to trunk.

After the release step you will end up with a release.properties file
in the trunk. At this point just run "mvn release:perform". It will:
-checkout a clean copy from the tag previously created under
target/checkout (this is very important in order to produce clean,
reproducible releases)
- compile, run test, and install jars, wars, javadocs, and sources to
the local repository
- deploy the release to the magnolia repository at sourceforge

Try it, it's magic ;)

fabrizio

PS. do you want me to try it for the first time in order to produce a
better m2 release or we can save it for b1?




On 5/4/06, Philipp Bracher <[email protected]> wrote:
> I killed the hover and selection facility in the list with the last
> commits!
it hovers again: retaged
>

> Philipp Bracher
> obinary ltd.
>
> -----------------------------------------------------
> [EMAIL PROTECTED]       http://obinary.com
> magnolia content management      http://magnolia.info
> -----------------------------------------------------
>
>
>
>
>
> ----------------------------------------------------------------
> for list details see
> http://www.magnolia.info/en/magnolia/developer.html
> ----------------------------------------------------------------

Regards,

Philipp Bracher
obinary ltd.

-----------------------------------------------------
[EMAIL PROTECTED]       http://obinary.com
magnolia content management      http://magnolia.info
-----------------------------------------------------





----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to