You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Bertrand Delacretaz <bd...@apache.org> on 2005/10/06 11:52:38 UTC
add --noconfig as a default ant option in build.sh?
Sandor Spruit suggests this, see
http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=112858673106600&w=2
Any objections to make this the default when ant is called from
build.sh?
If not I'll add it to the branch and trunk builds.
What the option does for ant is:
--noconfig suppress sourcing of /etc/ant.conf,
$HOME/.ant/ant.conf, and $HOME/.antrc
configuration files
-Bertrand
Re: add --noconfig as a default ant option in build.sh?
Posted by Carsten Ziegeler <cz...@apache.org>.
Bertrand Delacretaz wrote:
> Le 10 oct. 05, à 12:28, Carsten Ziegeler a écrit :
>
>>...I just added "servlet" being the default parameter for the cocoon
>>script. As I can't test this on unix right now, I only changed the
>>windows scripts...so if someone wants to have a look at it... :)
>
>
> done, "servlet" is now the default action for cocoon.sh in trunk and
> 2.1 branch.
>
Thanks Bertrand!
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: add --noconfig as a default ant option in build.sh?
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 10 oct. 05, à 12:28, Carsten Ziegeler a écrit :
> ...I just added "servlet" being the default parameter for the cocoon
> script. As I can't test this on unix right now, I only changed the
> windows scripts...so if someone wants to have a look at it... :)
done, "servlet" is now the default action for cocoon.sh in trunk and
2.1 branch.
-Bertrand
Re: add --noconfig as a default ant option in build.sh?
Posted by Carsten Ziegeler <cz...@apache.org>.
Carsten Ziegeler schrieb:
> Bertrand Delacretaz wrote:
>
>>Le 6 oct. 05, à 11:52, Bertrand Delacretaz a écrit :
>>
>>
>>
>>>Sandor Spruit suggests this, see
>>>http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=112858673106600&w=2
>>
>>
>>done for build.sh in trunk and BRANCH_2_1_X
>>
>>I haven't changed the windows build scripts as I cannot test them, if
>>someone can do it it would be good (assuming the option makes sense
>>under windows).
>>
>
> I will do this for windows then.
>
Ok, this was easy, the windows scripts do not support "--noconfig" :(
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: add --noconfig as a default ant option in build.sh?
Posted by Carsten Ziegeler <cz...@apache.org>.
Bertrand Delacretaz wrote:
> Le 6 oct. 05, à 11:52, Bertrand Delacretaz a écrit :
>
>
>>Sandor Spruit suggests this, see
>>http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=112858673106600&w=2
>
>
> done for build.sh in trunk and BRANCH_2_1_X
>
> I haven't changed the windows build scripts as I cannot test them, if
> someone can do it it would be good (assuming the option makes sense
> under windows).
>
I will do this for windows then.
I just added "servlet" being the default parameter for the cocoon
script. As I can't test this on unix right now, I only changed the
windows scripts...so if someone wants to have a look at it... :)
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: add --noconfig as a default ant option in build.sh?
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 6 oct. 05, à 11:52, Bertrand Delacretaz a écrit :
> Sandor Spruit suggests this, see
> http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=112858673106600&w=2
done for build.sh in trunk and BRANCH_2_1_X
I haven't changed the windows build scripts as I cannot test them, if
someone can do it it would be good (assuming the option makes sense
under windows).
-Bertrand
Re: add --noconfig as a default ant option in build.sh?
Posted by Upayavira <uv...@odoko.co.uk>.
Bertrand Delacretaz wrote:
> Sandor Spruit suggests this, see
> http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=112858673106600&w=2
>
> Any objections to make this the default when ant is called from build.sh?
>
> If not I'll add it to the branch and trunk builds.
>
> What the option does for ant is:
>
> --noconfig suppress sourcing of /etc/ant.conf,
> $HOME/.ant/ant.conf, and $HOME/.antrc
> configuration files
>
Makes a lot of sense. This would explain why some people seem to have
trouble with our ant build.
Regards, Upayavira