On 22.Nov.2001 -- 10:46 AM, Carsten Ziegeler wrote:
> Hi Team,
> 
> some days ago we decided to restructure the repository.
> (see http://marc.theaimsgroup.com/?t=100526384200023&w=2&r=1).
> 
> So let's vote if we want this also happen to 2.0 before
> the final release.(We mummbled that we want this, but I think 
> we should be clear about it.)

Although I think it is a good idea, to have dependancies better
represented than we have today, I believe we should not change
anything that has the potential of introducing new bugs. And I am
under the impression, that this could very well need some tweaking
'til we get it right.

Package names are to some extent independent of the directory
structure. So we could have files from
org.apache.cocoon.transformation in
core/src/org/apache/cocoon/transformation as well as in
opt/something/src/org/apache/cocoon/transformation so this would not
necessarily incur incompatibilities.

Also, we would like to present Cocoon Vers. 2 as ready to rock, and
rock it does. Postponing it further for "cosmetic" changes from an
end users point of view, while we should advertise it so that it gains
the user community that it deserves, seems wrong to me.

Our self set timeframe for a release is only days from now.

I'm -1 on postponing it further.

BTW: For me "build docs" fails to find the catalogs. Applying

--- documentation/cocoon.xconf.orig  Mon Nov 19 11:12:58 2001
+++ documentation/cocoon.xconf     Thu Nov 22 14:53:48 2001
@@ -101,7 +101,7 @@

   -->
   <resolver class="org.apache.cocoon.components.resolver.ResolverImpl">
-   <parameter name="catalog" value="/resources/entities/catalog"/>
+   <parameter name="catalog" value="//resources/entities/catalog"/>
    <parameter name="verbosity" value="2"/>
   </resolver>

resolves :-) the issue for me. Wrong spec or misbehaving source?

        Chris.

-- 
C h r i s t i a n       H a u l
[EMAIL PROTECTED]
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to