On May 3, 2007, at 13:10 , Oliver Lietz wrote:
Am Donnerstag, 3. Mai 2007 schrieb Grégory Joseph:
Hijacking a thread from the user list:
Hi Oliver,
On May 3, 2007, at 10:43 , Oliver Lietz wrote:
I hope that custom node types and namespaces will be part of 3.1.
So I think
it will be more useful to port/refactor my working products module
which
relies on MAGNOLIA-1346, MAGNOLIA-1348 and multi value properties
from
client's namespace to info.magnolia and from java5 to 1.4.
I'm not sure this can be part of 3.1 (for time reasons, nothing
else;)). I guess we'd all like to see this happen, but I don't think
we have lots of time to test and play with this at the moment. Maybe
you could branch the trunk, apply your patches there and we'd see how
it goes?
I fear that branching
svn cp http://.../trunk http://.../branch/my-sexy-branch
and merging
<checkout trunk again>
svn merge -r 1234:1267 http://.../branch/my-sexy-branch
is too much extra work for me at the moment.
Maybe Will's suggestion of documenting this stuff on a Wiki page is
indeed
the way to go for now. Although there isn't really much to do, just
apply all
patches from MAGNOLIA-1346 and MAGNOLIA-1348 and copy the two new
classes.
A project with a products module should go live next month and the
features
mentioned above are essential. It's not a problem for me to use
trunk for
that because I'm building and bootstrapping Magnolia nearly every day.
So it doesn't make a big difference to me if this stuff is part of
3.1 or not.
Just thought I would be easier for others to use it.
Would it help to provide a "big" diff against trunk and the
mentioned products
module for testing?
That's what merging the potential branch would do, but instead of
having a patch file lying around and taking care not to commit those
changes, there would be buildable code.
Cheers
g
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
