Leo, At the time I changed this shared-trunk pointed to shared 2.0.x. Later this was changed so that shared-trunk points to 4.0.x (committed by user lu4242 on revision 943327, see [1]), that's why the svn-external on current is wrong, because no-one changed this on current!
Furthermore I changed this, because we have 3 folders: current, current12 and current20. With those 3 it should IMHO be JSF 1.1 on current, JSF 1.2 on current12 and JSF 2.0 on current20. However I agree that introducing a current11 folder and putting current11, current12 and current20 into the current folder would be a better option! Regards, Jakob [1] http://www.svnsearch.org/svnsearch/repos/ASF/search?from=943327&to=943327 2010/8/26 Leonardo Uribe <lu4...@gmail.com> > Hi > > 2010/8/26 Grant Smith <work.gr...@gmail.com> > > I also have not added the GSOC build yet, I'll do that once I figure out >> why myfaces-current isnt compiling (looks like a dependency to >> shared-impl-2.0.12-SNAPSHOT, which for some reason is not incorporating >> automatically from the externs. The externs are probably wrong) >> >> > Yes, current folder points to shared 4.0.x but on core it points to 1.1.x ? > The last time I saw that it was not working in that way. I see the following > comment on the svn log by user jakobk: > > "...Changed core version to 1.1.x in current, because current includes > shared 2.0.x and not shared 4.0.x which is needed for core 2.0 (core 2.0 can > be found in current20)...." > > Current should point to myfaces core trunk (2.0.x) and myfaces shared trunk > (4.0.x). It is possible orchestra could introduce a dependency to shared > 2.0.x. So to solve this problem we should include on nightly build current11 > and current12 folders (maybe current should point to current11, current12 > and current20?). > > regards, > > Leonardo Uribe > -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
