You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Santiago Gala <sg...@hisitech.com> on 2001/05/14 21:22:59 UTC
Re: build.sh and build.bat
Jason Foster wrote:
>>>3. Prepare the beta version.
>>>
>>Yes. This needs a check if the build.xml can produce the right
>>distribtions anymore.
>>
>
> Not to be too much of a whiner, but could this include finally setting the
> "x" permission on build.sh? I realize that it's a little thing in the big
> picture, but it still rankles.
>
+1 for all the Linux users. It is amazing that in my Linux box, build.sh
in *not* executable, while build.bat *is*.
I see it for every fresh checkout. It looks like you guys do use Windows
to develop. :)
> Jason Foster
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: build.sh and build.bat
Posted by Donald Ball <ba...@webslingerZ.com>.
On Tue, 15 May 2001, Martin Man wrote:
> looking at the repositories @apache.org I see that build.sh is not executable
> even in other projects (whilst build.bat is :-??) is it the policy ???
no, it's just that cvs doesn't offer a good way to reset permissions on
files - the initial set is what you get. and if the initial set was
commited from a windows box, .sh will probably end up being 644 and .bat
755.
- donald
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Protected app. sitemap
Posted by Jason Foster <ja...@uwaterloo.ca>.
I am in the process of creating a sub-sitemap, based on the protected
application sitemap included in the distribution. I was wondering if
anyone knows why of all of the components only the matcher has to be fully
specified?
All of the other components look like:
<map:generators default="file"/>
<map:transformers default="xslt"/>
But the matcher looks like:
<map:matchers default="wildcard">
<map:matcher name="wildcard"
factory="org.apache.cocoon.matching.WildcardURIMatcherFactory"/>
</map:matchers>
I've verified that if this is removed the sitemap cannot compile. So why
are the matchers special?
Thanks!
Jason Foster
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: build.sh and build.bat
Posted by Jason Foster <ja...@uwaterloo.ca>.
> I've made them executable directly in the CVS repo. Try to
> chekout all *.sh files again (deletem them first).
Looks good. Thanks!
Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: build.sh and build.bat
Posted by giacomo <gi...@apache.org>.
On Tue, 15 May 2001, Martin Man wrote:
> On Mon, May 14, 2001 at 09:22:59PM +0200, Santiago Gala wrote:
> > Jason Foster wrote:
> >
> > >>>3. Prepare the beta version.
> > >>>
> > >>Yes. This needs a check if the build.xml can produce the right
> > >>distribtions anymore.
> > >>
> > >
> > > Not to be too much of a whiner, but could this include finally setting the
> > > "x" permission on build.sh? I realize that it's a little thing in the big
> > > picture, but it still rankles.
> > >
> >
> >
> > +1 for all the Linux users. It is amazing that in my Linux box, build.sh
> > in *not* executable, while build.bat *is*.
> >
> > I see it for every fresh checkout. It looks like you guys do use Windows
> > to develop. :)
>
> looking at the repositories @apache.org I see that build.sh is not executable
> even in other projects (whilst build.bat is :-??) is it the policy ???
I've made them executable directly in the CVS repo. Try to
chekout all *.sh files again (deletem them first).
The problem is that it preseves the permission it had at initial
checkout time. You can't change them afterward using a cvs upd, IIRC.
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: build.sh and build.bat
Posted by Martin Man <Ma...@seznam.cz>.
On Mon, May 14, 2001 at 09:22:59PM +0200, Santiago Gala wrote:
> Jason Foster wrote:
>
> >>>3. Prepare the beta version.
> >>>
> >>Yes. This needs a check if the build.xml can produce the right
> >>distribtions anymore.
> >>
> >
> > Not to be too much of a whiner, but could this include finally setting the
> > "x" permission on build.sh? I realize that it's a little thing in the big
> > picture, but it still rankles.
> >
>
>
> +1 for all the Linux users. It is amazing that in my Linux box, build.sh
> in *not* executable, while build.bat *is*.
>
> I see it for every fresh checkout. It looks like you guys do use Windows
> to develop. :)
looking at the repositories @apache.org I see that build.sh is not executable
even in other projects (whilst build.bat is :-??) is it the policy ???
>
>
> > Jason Foster
martin
--
-------------------------------------------------------------------------------
"Only dead fish swims with a stream"
gpg_key_available: http://globales.cz/~mman/martin.man.gpg
gpg_key_fingerprint: 2CC0 4AF6 92DA 5CBF 5F09 7BCB 6202 7024 6E06 0223
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org