cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: Solving the store problem and moving forward
Date Mon, 17 May 2004 08:40:26 GMT
Antonio Gallardo wrote:
> 
> Carsten Ziegeler dijo:
> > Antonio Gallardo wrote:
> >>
> >> OK. But can we move the jisp to deprecated?
> >>
> > Yes, we could, but that wouldn't make a difference as the 
> jar needs to 
> > be in the core anyway.
> >
> >> BTW, why deprecated is not a block?
> >>
> > The deprecated part contains some deprecated classes of the core.
> 
> Yep, but this is similar as scratchpard or not? I mean 
> scratchpad also contain some parts of the core (jcs was 
> there). Also we can turn off deprecated support in build.properties.
> 
> This is why I think we can make deprecated a block and let 
> people turn it on and off instead of using build.properties. 
> Please explain a little bit if I am wrong here or if I miss something.
> 
I think technically it's possible to have a "deprecated block", but this
is then not a block in the sense we define blocks.
I understand your concerns and we can think about changing this,
but we shouldn't touch the build system now. Let's wait until we
have the release out. 

Carsten


Mime
View raw message