On 2/22/06, Michael Wechner <[EMAIL PROTECTED]> wrote:
> Bob Harner wrote:
>
> >On 2/21/06, Michael Wechner <[EMAIL PROTECTED]> wrote:
> >
> >
> >>Bob Harner wrote:
> >>
> >>
> >>
> >>>On 2/21/06, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
> >>>
> >>>
> >>>
> >>>
> >>>>El mar, 21-02-2006 a las 09:05 -0500, Bob Harner escribió:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>Hello all,
> >>>>>
> >>>>>I checked out the latest Lenya 1.4 (trunk) from the Apache SVN this
> >>>>>weekend, and when trying to build a fresh Lenya 1.4.x (trunk) I get
> >>>>>this when running build.bat:
> >>>>>
> >>>>> Buildfile: build.xml
> >>>>>
> >>>>> BUILD FAILED
> >>>>> C:\src\lenya-1.4.x\src\targets\properties-build.xml:137:
> >>>>> taskdef class org.apache.lenya.cms.ant.CopyJavaSourcesTask
> >>>>> cannot be found
> >>>>>
> >>>>>In response to a similar error message back in July 2005, Michael
> >>>>>Wechner said on the mailing list "You have to have
> >>>>>{cocoon-home}/tools/anttasks on your classpath". Is this the issue?
> >>>>>If so, shouldn't this be done automatically by the build process?
> >>>>>
> >>>>>This is with Cocoon 2.1.x (trunk), also freshly downloaded.
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>hmm, weird.
> >>>>
> >>>>http://lenya.zones.apache.org/log/lenya.trunk.update.log
> >>>>
> >>>>I reckon you are using this task in custom code, can be?
> >>>>
> >>>>salu2
> >>>>--
> >>>>thorsten
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>No, this is an attempt to do a clean and simple out-of-the-box build
> >>>of the trunk. Nothing unusual. I just checked out a fresh cocoon
> >>>trunk into c:\src\cocoon-1.4.x and a fresh lenya trunk into
> >>>c:\src\lenya-1.4.x, copied Lenya's build.properties to
> >>>local.build.properties, edited it to have
> >>>cocoon.src.dir=../cocoon-1.4.x then ran build.bat (per instructions in
> >>>INSTALL-SRC.txt). JDK 1.4.2 by the way.
> >>>
> >>>
> >>>
> >>>
> >>cocoon-1.4.x ? Is this a typo?
> >>
> >>Lenya 1.4-dev is based on Cocoon-2.1.8-dev.
> >>
> >>Michi
> >>
> >>
> >
> >Sorry, yes, a typo. I meant cocoon-2.1.x. But now I'm confused. I
> >don't see any Cocoon-2.1.8-dev in the apache SVN, just the trunk and
> >the BRANCH_2_1_X.
> >
>
> please apologize for this typo: I meant Cocoon-2.1.9-dev which is the
>
> https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X
>
> > I'm assuming my mistake is in using the trunk
> >rather than BRANCH_2_1_X. I'll try the latter in a little while.
> >
> >Note that INSTALL-SRC.txt says to use Cocoon 2.1.5.1. Yes, I knew
> >that was wrong :-)
> >
> >
>
> thanks for pointing this out. I just fixed it.
>
> >The Cocoon developers are currently voting on the release of Cocoon
> >2.1.9. Once that is out, will Lenya 1.4 development switch to using
> >that released version of Cocoon? Previous messages on this list
> >seemed to lean that way.
> >
> >
>
> we actually agreed to stay on the branch during development.
> For the release it should be different.
>
> Michi
>
Okay, but for my own education can anyone explain why this is the
preferred approach? Doesn't it mean that everytime you want to do a
release you have to first either 1) wait for the next release of
Cocoon, or 2) fall back to the most recent Cocoon release and then do
a great deal of testing on a previously unsuppoprted combination of
Lenya/Cocoon and fix/remove anything that depends on the unreleased
Cocoon code? That makes releases harder (and less frequent?). Also,
developers are then subjected to unexpected bugs introduced by new
Cocoon code. Finally, it means that every Lenya developer is working
from a (slightly) different version of the Cocoon trunk, so a Lenya
svn update can cause breakage too.
It seems to me the only benefit to developing with the Cocoon trunk is
so that the developers can "work ahead" to make Lenya work with
upcoming Cocoon changes.
I understand that the Lenya PMC may decide that a particular key
feature of a not-yet-released version of Cocoon is critical to the
next release of Lenya. That makes sense, and it's what seems to have
happened recently with the new JCR functionality which will be in
Cocoon 2.1.9. But once 2.1.9 is out...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
