Re: cocoon 2.1 release...

ON THU, 2008-01-03 AT 23:45 +0100, ANDREAS HARTMANN WROTE:
> ANDREAS HARTMANN SCHRIEB:
> > ANDREAS HARTMANN SCHRIEB:
> >> JöRN NETTINGSMEIER SCHRIEB:
> >>> ANDREAS HARTMANN WROTE:
> >>>> THORSTEN SCHERLER SCHRIEB:
> >>>>> NO, WE WILL STICK TO OUR DECISION
AND RELEASE WITH COCOON HEAD.
> >>>> SINCE COCOON 2.1.11 HAS BEEN TAGGED,
SHALL WE SET THE SVN:EXTERNALS IN
> >>>> RELEASE_2_0 TO THIS TAG, OR SHALL WE
KEEP IT AT BRANCH_2_1_X?
> >>>
> >>> RELEASE. IT MIGHT BE NECESSARY TO ROLL
LENYA-2.0A TARBALLS IF
> >>> SIGNIFICANT CHANGES CROP UP DURING THE
COCOON RELEASE, BUT I DOUBT IT'S
> >>> GOING TO HAPPEN.
> >>
> >> IT LOOKS AS IF THERE HAVE BEEN SOME CHANGES TO
THE BUILD PROCESS. THE 
> >> XALAN JAR IS NOT COPIED TO WEB-INF/LIB
ANYMORE, WHICH MAKES THE TESTS 
> >> FAIL AND PREVENTS LENYA FROM STARTING UP. I'LL
TRY TO FIND OUT WHAT 
> >> GOES WRONG.
> > 
> > THE ENDORSED LIBS ARE NOW ONLY IN
WEB-INF/LIB/ENDORSED. APART FROM THAT, 
> > EXTERNALS/COCOON_2_1_X IS HARD-CODED IN LENYA.SH.
CAN WE CHANGE THIS TO 
> > THE FOLLOWING DECLARATION?
> > 
> >  
ENDORSED_LIBS="$/WEB-INF/LIB/ENDORSE
D"
> 
> IT MIGHT BE A BIT RISKY TO TWEAK OUR TAGGED VERSION TO
WORK WITH COCOON 
> 2.1.11. I SEE TWO OPTIONS:
> 
> A) RELEASE THE ALREADY TAGGED VERSION WITH A COCOON
REVISION BEFORE THE
>     CRITICAL CHANGES
> 
> B) UPDATE LENYA TO WORK WITH COCOON 2.1.11 AND DO
ANOTHER RC


I WOULD PREFER B) SINCE IT WOULD BE SO MUCH NICER TO RELEASE
2.0 WITH A
STABLE COCOON 2.1.11.

SALU2
-- 
THORSTEN SCHERLER                                
THORSTEN.AT.APACHE.ORG
OPEN SOURCE JAVA                      CONSULTING, TRAINING
AND SOLUTIONS


------------------------------------------------------------
---------
TO UNSUBSCRIBE, E-MAIL: DEV-UNSUBSCRIBELENYA.APACHE.ORG
FOR ADDITIONAL COMMANDS, E-MAIL: DEV-HELPLENYA.APACHE.ORG