You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Henri Yandell <ba...@generationjava.com> on 2003/08/11 20:44:12 UTC
[docs] Crappy build system
Jakarta Commons build system for the website is very very crappy.
Regardless of whether things move to Maven or some other look and feel,
I'd like to check in the jars needed so that people don't have to go
around hunting in jakarta-velocity, jakarta-site2 and who knows where
else.
Is anyone against this? Is there some reason for the current confusing
setup?
Hen
Re: [docs] Crappy build system
Posted by Vic Cekvenich <ce...@baseBeans.com>.
Database makes it easy to mananage. (This runs on pgSQL, which is free)
Web app makes it easy to edit, via a browser you can cut/paste etc.
Somce kind of CMS would help, and bP's goal is to be the simplest CMS
out there.
Look at Zope, Plone, PHP-Nukes.. etc.
bP is based on Struts and Tomcat 5. It goes w/ the dogdoof concept.
I could do a demo to anyone how easy it is to manage content w/it. (also
there is an avi video in the docs).
Static pages are not static.... they change from time to time, and CMS
makes it easy.
.V
dion@multitask.com.au wrote:
> Do we really need a webapp and database for static content?
> --
> dIon Gillard, Multitask Consulting
> Blog: http://blogs.codehaus.org/people/dion/
>
>
> news <ne...@sea.gmane.org> wrote on 13/08/2003 10:40:49 AM:
>
>
>>One way to maintain Jakarta web sites, such as commons, of course is to
>>use a CMS system.
>>Store XML in a database (such as PostgreSQL), and edit remotely, flag as
>
>
>>approved, have it pre-render to HTML, and have a jSTL emit it. Since
>>content is in DB, it is easy to manager. Since it's a web app, it is
>>easy to modify. Of course, ver fast.
>>Here is one example of Open Source CMS w/ a working URL:
>>http://basicportal.com/do/cmsPg?content=DEVELOPMENT
>>
>>See the url?
>>This makes a call to db to retrieve this content where = "DEVELOPMENT".
>>(Of course DB is cached auto by DAO so no ping if no change)
>>Realy, change the web site is easy, it's a lot like Wiki, except it has
>>J2EE JDBC realms as to who can author and who can approve.
>>
>>.V
>>
>>
>>Craig R. McClanahan wrote:
>>
>>
>>>On Mon, 11 Aug 2003, Glenn Nielsen wrote:
>>>
>>>
>>>
>>>>Date: Mon, 11 Aug 2003 21:56:46 -0500
>>>>From: Glenn Nielsen <gl...@mail.more.net>
>>>>Reply-To: Jakarta Commons Developers List
>
> <co...@jakarta.apache.org>
>
>>>>To: Jakarta Commons Developers List <co...@jakarta.apache.org>
>>>>Subject: Re: [docs] Crappy build system
>>>>
>>>>Henri Yandell wrote:
>>>>
>>>>
>>>>>Jakarta Commons build system for the website is very very crappy.
>>>>>Regardless of whether things move to Maven or some other look and
>
> feel,
>
>>>>>I'd like to check in the jars needed so that people don't have to go
>>>>>around hunting in jakarta-velocity, jakarta-site2 and who knows where
>>>>>else.
>>>>>
>>>>>Is anyone against this? Is there some reason for the current
>
> confusing
>
>>>>>setup?
>>>>>
>>>>
>>>>-1 to checking the jars into CVS
>>>
>>>
>>>Agreed. Changing the site generaton process to use Maven would
>
> eliminate
>
>>>any need for this.
>>>
>>>Of course, so would using standard XML technologies like XSLT, but I'm
>
> not
>
>>>going to volunteer to maintain the Commons site sources, so I'm not
>
> going
>
>>>to go there :-).
>>>
>>>Craig
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [docs] Crappy build system
Posted by Vic Cekvenich <ce...@baseBeans.com>.
Database makes it easy to mananage. (This runs on pgSQL, which is free)
Web app makes it easy to edit, via a browser you can cut/paste etc.
Somce kind of CMS would help, and bP's goal is to be the simplest CMS
out there.
Look at Zope, Plone, PHP-Nukes.. etc.
bP is based on Struts and Tomcat 5. It goes w/ the dogdoof concept.
I could do a demo to anyone how easy it is to manage content w/it. (also
there is an avi video in the docs).
Static pages are not static.... they change from time to time, and CMS
makes it easy.
.V
dion@multitask.com.au wrote:
> Do we really need a webapp and database for static content?
> --
> dIon Gillard, Multitask Consulting
> Blog: http://blogs.codehaus.org/people/dion/
>
>
> news <ne...@sea.gmane.org> wrote on 13/08/2003 10:40:49 AM:
>
>
>>One way to maintain Jakarta web sites, such as commons, of course is to
>>use a CMS system.
>>Store XML in a database (such as PostgreSQL), and edit remotely, flag as
>
>
>>approved, have it pre-render to HTML, and have a jSTL emit it. Since
>>content is in DB, it is easy to manager. Since it's a web app, it is
>>easy to modify. Of course, ver fast.
>>Here is one example of Open Source CMS w/ a working URL:
>>http://basicportal.com/do/cmsPg?content=DEVELOPMENT
>>
>>See the url?
>>This makes a call to db to retrieve this content where = "DEVELOPMENT".
>>(Of course DB is cached auto by DAO so no ping if no change)
>>Realy, change the web site is easy, it's a lot like Wiki, except it has
>>J2EE JDBC realms as to who can author and who can approve.
>>
>>.V
>>
>>
>>Craig R. McClanahan wrote:
>>
>>
>>>On Mon, 11 Aug 2003, Glenn Nielsen wrote:
>>>
>>>
>>>
>>>>Date: Mon, 11 Aug 2003 21:56:46 -0500
>>>>From: Glenn Nielsen <gl...@mail.more.net>
>>>>Reply-To: Jakarta Commons Developers List
>
> <co...@jakarta.apache.org>
>
>>>>To: Jakarta Commons Developers List <co...@jakarta.apache.org>
>>>>Subject: Re: [docs] Crappy build system
>>>>
>>>>Henri Yandell wrote:
>>>>
>>>>
>>>>>Jakarta Commons build system for the website is very very crappy.
>>>>>Regardless of whether things move to Maven or some other look and
>
> feel,
>
>>>>>I'd like to check in the jars needed so that people don't have to go
>>>>>around hunting in jakarta-velocity, jakarta-site2 and who knows where
>>>>>else.
>>>>>
>>>>>Is anyone against this? Is there some reason for the current
>
> confusing
>
>>>>>setup?
>>>>>
>>>>
>>>>-1 to checking the jars into CVS
>>>
>>>
>>>Agreed. Changing the site generaton process to use Maven would
>
> eliminate
>
>>>any need for this.
>>>
>>>Of course, so would using standard XML technologies like XSLT, but I'm
>
> not
>
>>>going to volunteer to maintain the Commons site sources, so I'm not
>
> going
>
>>>to go there :-).
>>>
>>>Craig
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>
>
Re: [docs] Crappy build system
Posted by Yoav Shapira <yo...@apache.org>.
Howdy,
I would think we really don't ;) I like Henri's simplification ideas. I
would add something that interested me last night:
I had to update both the main (jakarta.apache.org) and commons
(jakarta.apache.org/commons) sites. I committed my changes into CVS, no
problem. Simply running ant (no args) on jakarta-site2 works, and it
uses anakia/velocity as well. The same thing didn't work for commons, as
it couldn't find the Anakia taskdef. Would simply copying the relevant
part's from jakarta-site2's build.xml work for us? We wouldn't even have
to re-invent the wheel ;)
Yoav Shapira
On Wed, 13 Aug 2003 dion@multitask.com.au wrote:
> Do we really need a webapp and database for static content?
> --
> dIon Gillard, Multitask Consulting
> Blog: http://blogs.codehaus.org/people/dion/
>
>
> news <ne...@sea.gmane.org> wrote on 13/08/2003 10:40:49 AM:
>
> > One way to maintain Jakarta web sites, such as commons, of course is to
> > use a CMS system.
> > Store XML in a database (such as PostgreSQL), and edit remotely, flag as
>
> > approved, have it pre-render to HTML, and have a jSTL emit it. Since
> > content is in DB, it is easy to manager. Since it's a web app, it is
> > easy to modify. Of course, ver fast.
> > Here is one example of Open Source CMS w/ a working URL:
> > http://basicportal.com/do/cmsPg?content=DEVELOPMENT
> >
> > See the url?
> > This makes a call to db to retrieve this content where = "DEVELOPMENT".
> > (Of course DB is cached auto by DAO so no ping if no change)
> > Realy, change the web site is easy, it's a lot like Wiki, except it has
> > J2EE JDBC realms as to who can author and who can approve.
> >
> > .V
> >
> >
> > Craig R. McClanahan wrote:
> >
> > > On Mon, 11 Aug 2003, Glenn Nielsen wrote:
> > >
> > >
> > >>Date: Mon, 11 Aug 2003 21:56:46 -0500
> > >>From: Glenn Nielsen <gl...@mail.more.net>
> > >>Reply-To: Jakarta Commons Developers List
> <co...@jakarta.apache.org>
> > >>To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> > >>Subject: Re: [docs] Crappy build system
> > >>
> > >>Henri Yandell wrote:
> > >>
> > >>>Jakarta Commons build system for the website is very very crappy.
> > >>>Regardless of whether things move to Maven or some other look and
> feel,
> > >>>I'd like to check in the jars needed so that people don't have to go
> > >>>around hunting in jakarta-velocity, jakarta-site2 and who knows where
> > >>>else.
> > >>>
> > >>>Is anyone against this? Is there some reason for the current
> confusing
> > >>>setup?
> > >>>
> > >>
> > >>-1 to checking the jars into CVS
> > >
> > >
> > > Agreed. Changing the site generaton process to use Maven would
> eliminate
> > > any need for this.
> > >
> > > Of course, so would using standard XML technologies like XSLT, but I'm
> not
> > > going to volunteer to maintain the Commons site sources, so I'm not
> going
> > > to go there :-).
> > >
> > > Craig
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [docs] Crappy build system
Posted by Yoav Shapira <yo...@apache.org>.
Howdy,
I would think we really don't ;) I like Henri's simplification ideas. I
would add something that interested me last night:
I had to update both the main (jakarta.apache.org) and commons
(jakarta.apache.org/commons) sites. I committed my changes into CVS, no
problem. Simply running ant (no args) on jakarta-site2 works, and it
uses anakia/velocity as well. The same thing didn't work for commons, as
it couldn't find the Anakia taskdef. Would simply copying the relevant
part's from jakarta-site2's build.xml work for us? We wouldn't even have
to re-invent the wheel ;)
Yoav Shapira
On Wed, 13 Aug 2003 dion@multitask.com.au wrote:
> Do we really need a webapp and database for static content?
> --
> dIon Gillard, Multitask Consulting
> Blog: http://blogs.codehaus.org/people/dion/
>
>
> news <ne...@sea.gmane.org> wrote on 13/08/2003 10:40:49 AM:
>
> > One way to maintain Jakarta web sites, such as commons, of course is to
> > use a CMS system.
> > Store XML in a database (such as PostgreSQL), and edit remotely, flag as
>
> > approved, have it pre-render to HTML, and have a jSTL emit it. Since
> > content is in DB, it is easy to manager. Since it's a web app, it is
> > easy to modify. Of course, ver fast.
> > Here is one example of Open Source CMS w/ a working URL:
> > http://basicportal.com/do/cmsPg?content=DEVELOPMENT
> >
> > See the url?
> > This makes a call to db to retrieve this content where = "DEVELOPMENT".
> > (Of course DB is cached auto by DAO so no ping if no change)
> > Realy, change the web site is easy, it's a lot like Wiki, except it has
> > J2EE JDBC realms as to who can author and who can approve.
> >
> > .V
> >
> >
> > Craig R. McClanahan wrote:
> >
> > > On Mon, 11 Aug 2003, Glenn Nielsen wrote:
> > >
> > >
> > >>Date: Mon, 11 Aug 2003 21:56:46 -0500
> > >>From: Glenn Nielsen <gl...@mail.more.net>
> > >>Reply-To: Jakarta Commons Developers List
> <co...@jakarta.apache.org>
> > >>To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> > >>Subject: Re: [docs] Crappy build system
> > >>
> > >>Henri Yandell wrote:
> > >>
> > >>>Jakarta Commons build system for the website is very very crappy.
> > >>>Regardless of whether things move to Maven or some other look and
> feel,
> > >>>I'd like to check in the jars needed so that people don't have to go
> > >>>around hunting in jakarta-velocity, jakarta-site2 and who knows where
> > >>>else.
> > >>>
> > >>>Is anyone against this? Is there some reason for the current
> confusing
> > >>>setup?
> > >>>
> > >>
> > >>-1 to checking the jars into CVS
> > >
> > >
> > > Agreed. Changing the site generaton process to use Maven would
> eliminate
> > > any need for this.
> > >
> > > Of course, so would using standard XML technologies like XSLT, but I'm
> not
> > > going to volunteer to maintain the Commons site sources, so I'm not
> going
> > > to go there :-).
> > >
> > > Craig
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
>
Re: [docs] Crappy build system
Posted by di...@multitask.com.au.
Do we really need a webapp and database for static content?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
news <ne...@sea.gmane.org> wrote on 13/08/2003 10:40:49 AM:
> One way to maintain Jakarta web sites, such as commons, of course is to
> use a CMS system.
> Store XML in a database (such as PostgreSQL), and edit remotely, flag as
> approved, have it pre-render to HTML, and have a jSTL emit it. Since
> content is in DB, it is easy to manager. Since it's a web app, it is
> easy to modify. Of course, ver fast.
> Here is one example of Open Source CMS w/ a working URL:
> http://basicportal.com/do/cmsPg?content=DEVELOPMENT
>
> See the url?
> This makes a call to db to retrieve this content where = "DEVELOPMENT".
> (Of course DB is cached auto by DAO so no ping if no change)
> Realy, change the web site is easy, it's a lot like Wiki, except it has
> J2EE JDBC realms as to who can author and who can approve.
>
> .V
>
>
> Craig R. McClanahan wrote:
>
> > On Mon, 11 Aug 2003, Glenn Nielsen wrote:
> >
> >
> >>Date: Mon, 11 Aug 2003 21:56:46 -0500
> >>From: Glenn Nielsen <gl...@mail.more.net>
> >>Reply-To: Jakarta Commons Developers List
<co...@jakarta.apache.org>
> >>To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> >>Subject: Re: [docs] Crappy build system
> >>
> >>Henri Yandell wrote:
> >>
> >>>Jakarta Commons build system for the website is very very crappy.
> >>>Regardless of whether things move to Maven or some other look and
feel,
> >>>I'd like to check in the jars needed so that people don't have to go
> >>>around hunting in jakarta-velocity, jakarta-site2 and who knows where
> >>>else.
> >>>
> >>>Is anyone against this? Is there some reason for the current
confusing
> >>>setup?
> >>>
> >>
> >>-1 to checking the jars into CVS
> >
> >
> > Agreed. Changing the site generaton process to use Maven would
eliminate
> > any need for this.
> >
> > Of course, so would using standard XML technologies like XSLT, but I'm
not
> > going to volunteer to maintain the Commons site sources, so I'm not
going
> > to go there :-).
> >
> > Craig
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
Re: [docs] Crappy build system
Posted by Vic Cekvenich <ce...@baseBeans.com>.
One way to maintain Jakarta web sites, such as commons, of course is to
use a CMS system.
Store XML in a database (such as PostgreSQL), and edit remotely, flag as
approved, have it pre-render to HTML, and have a jSTL emit it. Since
content is in DB, it is easy to manager. Since it's a web app, it is
easy to modify. Of course, ver fast.
Here is one example of Open Source CMS w/ a working URL:
http://basicportal.com/do/cmsPg?content=DEVELOPMENT
See the url?
This makes a call to db to retrieve this content where = "DEVELOPMENT".
(Of course DB is cached auto by DAO so no ping if no change)
Realy, change the web site is easy, it's a lot like Wiki, except it has
J2EE JDBC realms as to who can author and who can approve.
.V
Craig R. McClanahan wrote:
> On Mon, 11 Aug 2003, Glenn Nielsen wrote:
>
>
>>Date: Mon, 11 Aug 2003 21:56:46 -0500
>>From: Glenn Nielsen <gl...@mail.more.net>
>>Reply-To: Jakarta Commons Developers List <co...@jakarta.apache.org>
>>To: Jakarta Commons Developers List <co...@jakarta.apache.org>
>>Subject: Re: [docs] Crappy build system
>>
>>Henri Yandell wrote:
>>
>>>Jakarta Commons build system for the website is very very crappy.
>>>Regardless of whether things move to Maven or some other look and feel,
>>>I'd like to check in the jars needed so that people don't have to go
>>>around hunting in jakarta-velocity, jakarta-site2 and who knows where
>>>else.
>>>
>>>Is anyone against this? Is there some reason for the current confusing
>>>setup?
>>>
>>
>>-1 to checking the jars into CVS
>
>
> Agreed. Changing the site generaton process to use Maven would eliminate
> any need for this.
>
> Of course, so would using standard XML technologies like XSLT, but I'm not
> going to volunteer to maintain the Commons site sources, so I'm not going
> to go there :-).
>
> Craig
Re: [docs] Crappy build system
Posted by Vic Cekvenich <ce...@baseBeans.com>.
One way to maintain Jakarta web sites, such as commons, of course is to
use a CMS system.
Store XML in a database (such as PostgreSQL), and edit remotely, flag as
approved, have it pre-render to HTML, and have a jSTL emit it. Since
content is in DB, it is easy to manager. Since it's a web app, it is
easy to modify. Of course, ver fast.
Here is one example of Open Source CMS w/ a working URL:
http://basicportal.com/do/cmsPg?content=DEVELOPMENT
See the url?
This makes a call to db to retrieve this content where = "DEVELOPMENT".
(Of course DB is cached auto by DAO so no ping if no change)
Realy, change the web site is easy, it's a lot like Wiki, except it has
J2EE JDBC realms as to who can author and who can approve.
.V
Craig R. McClanahan wrote:
> On Mon, 11 Aug 2003, Glenn Nielsen wrote:
>
>
>>Date: Mon, 11 Aug 2003 21:56:46 -0500
>>From: Glenn Nielsen <gl...@mail.more.net>
>>Reply-To: Jakarta Commons Developers List <co...@jakarta.apache.org>
>>To: Jakarta Commons Developers List <co...@jakarta.apache.org>
>>Subject: Re: [docs] Crappy build system
>>
>>Henri Yandell wrote:
>>
>>>Jakarta Commons build system for the website is very very crappy.
>>>Regardless of whether things move to Maven or some other look and feel,
>>>I'd like to check in the jars needed so that people don't have to go
>>>around hunting in jakarta-velocity, jakarta-site2 and who knows where
>>>else.
>>>
>>>Is anyone against this? Is there some reason for the current confusing
>>>setup?
>>>
>>
>>-1 to checking the jars into CVS
>
>
> Agreed. Changing the site generaton process to use Maven would eliminate
> any need for this.
>
> Of course, so would using standard XML technologies like XSLT, but I'm not
> going to volunteer to maintain the Commons site sources, so I'm not going
> to go there :-).
>
> Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [docs] Crappy build system
Posted by Henri Yandell <ba...@generationjava.com>.
On Mon, 11 Aug 2003, Craig R. McClanahan wrote:
> On Mon, 11 Aug 2003, Henri Yandell wrote:
>
> > Anything wrong with placing the jars on the Commons site somewhere [a non
> > publicised directory] and putting a comment in build.properties.sample to
> > the effect that people should download them from there?
> >
>
> They already exist at ibiblio (default source for Maven), don't they? I
> can't see why we would need to redundantly store them here.
Will paste the urls for the ibiblio jars into build.properties.sample as
the canonical way in which to build things.
Hadn't thought of coupling things to ibiblio in this way, but all the
maven builds are anyway so why not.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [docs] Crappy build system
Posted by Henri Yandell <ba...@generationjava.com>.
On Mon, 11 Aug 2003, Craig R. McClanahan wrote:
> On Mon, 11 Aug 2003, Henri Yandell wrote:
>
> > Anything wrong with placing the jars on the Commons site somewhere [a non
> > publicised directory] and putting a comment in build.properties.sample to
> > the effect that people should download them from there?
> >
>
> They already exist at ibiblio (default source for Maven), don't they? I
> can't see why we would need to redundantly store them here.
Will paste the urls for the ibiblio jars into build.properties.sample as
the canonical way in which to build things.
Hadn't thought of coupling things to ibiblio in this way, but all the
maven builds are anyway so why not.
Hen
Re: [docs] Crappy build system
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Mon, 11 Aug 2003, Henri Yandell wrote:
> Date: Mon, 11 Aug 2003 23:13:33 -0400 (EDT)
> From: Henri Yandell <ba...@generationjava.com>
> Reply-To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> Subject: Re: [docs] Crappy build system
>
>
>
> On Mon, 11 Aug 2003, Craig R. McClanahan wrote:
>
> > On Mon, 11 Aug 2003, Glenn Nielsen wrote:
> >
> > > Date: Mon, 11 Aug 2003 21:56:46 -0500
> > > From: Glenn Nielsen <gl...@mail.more.net>
> > >
> > > -1 to checking the jars into CVS
> >
> > Agreed. Changing the site generaton process to use Maven would eliminate
> > any need for this. ....
>
> I'll remove them.
>
> Anything wrong with placing the jars on the Commons site somewhere [a non
> publicised directory] and putting a comment in build.properties.sample to
> the effect that people should download them from there?
>
They already exist at ibiblio (default source for Maven), don't they? I
can't see why we would need to redundantly store them here.
> Hen
Craig
Re: [docs] Crappy build system
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Mon, 11 Aug 2003, Henri Yandell wrote:
> Date: Mon, 11 Aug 2003 23:13:33 -0400 (EDT)
> From: Henri Yandell <ba...@generationjava.com>
> Reply-To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> Subject: Re: [docs] Crappy build system
>
>
>
> On Mon, 11 Aug 2003, Craig R. McClanahan wrote:
>
> > On Mon, 11 Aug 2003, Glenn Nielsen wrote:
> >
> > > Date: Mon, 11 Aug 2003 21:56:46 -0500
> > > From: Glenn Nielsen <gl...@mail.more.net>
> > >
> > > -1 to checking the jars into CVS
> >
> > Agreed. Changing the site generaton process to use Maven would eliminate
> > any need for this. ....
>
> I'll remove them.
>
> Anything wrong with placing the jars on the Commons site somewhere [a non
> publicised directory] and putting a comment in build.properties.sample to
> the effect that people should download them from there?
>
They already exist at ibiblio (default source for Maven), don't they? I
can't see why we would need to redundantly store them here.
> Hen
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [docs] Crappy build system
Posted by Henri Yandell <ba...@generationjava.com>.
On Mon, 11 Aug 2003, Craig R. McClanahan wrote:
> On Mon, 11 Aug 2003, Glenn Nielsen wrote:
>
> > Date: Mon, 11 Aug 2003 21:56:46 -0500
> > From: Glenn Nielsen <gl...@mail.more.net>
> >
> > -1 to checking the jars into CVS
>
> Agreed. Changing the site generaton process to use Maven would eliminate
> any need for this. ....
I'll remove them.
Anything wrong with placing the jars on the Commons site somewhere [a non
publicised directory] and putting a comment in build.properties.sample to
the effect that people should download them from there?
Hen
Re: [docs] Crappy build system
Posted by Henri Yandell <ba...@generationjava.com>.
On Mon, 11 Aug 2003, Craig R. McClanahan wrote:
> On Mon, 11 Aug 2003, Glenn Nielsen wrote:
>
> > Date: Mon, 11 Aug 2003 21:56:46 -0500
> > From: Glenn Nielsen <gl...@mail.more.net>
> >
> > -1 to checking the jars into CVS
>
> Agreed. Changing the site generaton process to use Maven would eliminate
> any need for this. ....
I'll remove them.
Anything wrong with placing the jars on the Commons site somewhere [a non
publicised directory] and putting a comment in build.properties.sample to
the effect that people should download them from there?
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [docs] Crappy build system
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Mon, 11 Aug 2003, Glenn Nielsen wrote:
> Date: Mon, 11 Aug 2003 21:56:46 -0500
> From: Glenn Nielsen <gl...@mail.more.net>
> Reply-To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> Subject: Re: [docs] Crappy build system
>
> Henri Yandell wrote:
> > Jakarta Commons build system for the website is very very crappy.
> > Regardless of whether things move to Maven or some other look and feel,
> > I'd like to check in the jars needed so that people don't have to go
> > around hunting in jakarta-velocity, jakarta-site2 and who knows where
> > else.
> >
> > Is anyone against this? Is there some reason for the current confusing
> > setup?
> >
>
> -1 to checking the jars into CVS
Agreed. Changing the site generaton process to use Maven would eliminate
any need for this.
Of course, so would using standard XML technologies like XSLT, but I'm not
going to volunteer to maintain the Commons site sources, so I'm not going
to go there :-).
Craig
Re: [docs] Crappy build system
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Mon, 11 Aug 2003, Glenn Nielsen wrote:
> Date: Mon, 11 Aug 2003 21:56:46 -0500
> From: Glenn Nielsen <gl...@mail.more.net>
> Reply-To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> To: Jakarta Commons Developers List <co...@jakarta.apache.org>
> Subject: Re: [docs] Crappy build system
>
> Henri Yandell wrote:
> > Jakarta Commons build system for the website is very very crappy.
> > Regardless of whether things move to Maven or some other look and feel,
> > I'd like to check in the jars needed so that people don't have to go
> > around hunting in jakarta-velocity, jakarta-site2 and who knows where
> > else.
> >
> > Is anyone against this? Is there some reason for the current confusing
> > setup?
> >
>
> -1 to checking the jars into CVS
Agreed. Changing the site generaton process to use Maven would eliminate
any need for this.
Of course, so would using standard XML technologies like XSLT, but I'm not
going to volunteer to maintain the Commons site sources, so I'm not going
to go there :-).
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [docs] Crappy build system
Posted by Glenn Nielsen <gl...@mail.more.net>.
Henri Yandell wrote:
> Jakarta Commons build system for the website is very very crappy.
> Regardless of whether things move to Maven or some other look and feel,
> I'd like to check in the jars needed so that people don't have to go
> around hunting in jakarta-velocity, jakarta-site2 and who knows where
> else.
>
> Is anyone against this? Is there some reason for the current confusing
> setup?
>
-1 to checking the jars into CVS
Re: [docs] Crappy build system
Posted by Glenn Nielsen <gl...@mail.more.net>.
Henri Yandell wrote:
> Jakarta Commons build system for the website is very very crappy.
> Regardless of whether things move to Maven or some other look and feel,
> I'd like to check in the jars needed so that people don't have to go
> around hunting in jakarta-velocity, jakarta-site2 and who knows where
> else.
>
> Is anyone against this? Is there some reason for the current confusing
> setup?
>
-1 to checking the jars into CVS
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [docs] Crappy build system
Posted by Robert Leland <rl...@apache.org>.
Henri Yandell wrote:
>Jakarta Commons build system for the website is very very crappy.
>Regardless of whether things move to Maven or some other look and feel,
>I'd like to check in the jars needed so that people don't have to go
>around hunting in jakarta-velocity, jakarta-site2 and who knows where
>else.
>
Contributions are always welcome, then maybe the Commons build system
for the web
site will go from being very very crappy, to just crappy. ;-) !
Could you elaborate on this ? When you say jars what are you referring to ?
>
>Is anyone against this? Is there some reason for the current confusing
>setup?
>
We didn't have you to help us out before :-) !
>Hen
>
>
--
Robert Leland Robert@free2create.org
------------------------------------------
Java, J2EE, Struts, Web Application Development
804 N. Kenmore Street +01-703-525-3580
Arlington VA 22201
Re: [docs] Crappy build system
Posted by Robert Leland <rl...@apache.org>.
Henri Yandell wrote:
>Jakarta Commons build system for the website is very very crappy.
>Regardless of whether things move to Maven or some other look and feel,
>I'd like to check in the jars needed so that people don't have to go
>around hunting in jakarta-velocity, jakarta-site2 and who knows where
>else.
>
Contributions are always welcome, then maybe the Commons build system
for the web
site will go from being very very crappy, to just crappy. ;-) !
Could you elaborate on this ? When you say jars what are you referring to ?
>
>Is anyone against this? Is there some reason for the current confusing
>setup?
>
We didn't have you to help us out before :-) !
>Hen
>
>
--
Robert Leland Robert@free2create.org
------------------------------------------
Java, J2EE, Struts, Web Application Development
804 N. Kenmore Street +01-703-525-3580
Arlington VA 22201
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org