You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Dave Brondsema <da...@brondsema.net> on 2004/10/22 17:39:02 UTC
Re: build system (was: [proposal] SVN restructure for subprojects)
Quoting Nicola Ken Barozzi <ni...@apache.org>:
> Notice the 'bin' directory where users would think of finding it, as a
> single thing to add to the system path variable. the trunk would become
> the new FORREST_HOME
>
> Also, this would mean that we have to rethink our build system.
I would like to see a SVN restructure in the near future, with minimal changes
to the build system. Discussion and implementation of changes to FORREST_HOME,
the bin location, and the build system in general will take *much* longer.
> - Please no flame wars -
>
> As I see it we have two options: Ant and Maven.
>
> For Ant I am willing to help set it up in a way that it makes it easy to
> do the above multi-project. I see it as a must that we use a lib
> download system ALA Maven.
>
> Other than this, I'm really open to any sensible technical comment on
> this, along with proposals in helping out.
>
With my experience and understanding of maven, we would have to write plugins to
do what we want. Our software is not a simple standard java package, since we
do a lot with cocoon, copyless issues, and skin/plugin fetching. Since this is
so unique to our project, I don't think maven's standard build system will help
us much.
Matching a standard directory structure is certainly good. Not sure about
automatically downloading jars. That could be good, but I don't see a real need
for it; things work fine how they are.
Another alternative to consider is to use a real scripting language instead of
Ant to do our builds. In my experience with skin fetching, ant simply isn't
designed to do the things we want to do. I am not familiar with python, but I
think it would be a good candidate.
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org
Re: build system
Posted by Dave Brondsema <da...@brondsema.net>.
David Crossley wrote:
> Dave Brondsema wrote:
>>Another alternative to consider is to use a real scripting language instead of
>>Ant to do our builds. In my experience with skin fetching, ant simply isn't
>>designed to do the things we want to do. I am not familiar with python, but I
>>think it would be a good candidate.
>
>
> Is Ant able to call a python script to do certain tasks?
>
Ant can embed scripting. I can't believe I forgot about this. I've
used rhino (a Javascript implementation in Java) at work to do this. It
can be a real pain to debug because it's embedded, but it does make
stuff easier.
See http://ant.apache.org/manual/OptionalTasks/script.html (and
scriptdef and macrodef).
It looks like python, java, groovy, and other less popular languages are
supported.
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
Re: build system
Posted by Nicola Ken Barozzi <ni...@apache.org>.
David Crossley wrote:
> Dave Brondsema wrote:
>
>>Quoting Nicola Ken Barozzi:
...
>>>For Ant I am willing to help set it up in a way that it makes it easy to
>>>do the above multi-project. I see it as a must that we use a lib
>>>download system ALA Maven.
>
> Why is it a *must*?
:-)
OTOMH
1. It's not reasonable for a Maven user to have to redownload the libs
we use just because we don't use a repository
2. The downloaded jars can be shared easily between Forrest projects
easily without having to put them all in the classpath or having to
declare them by hand in the ant scripts
3. The downloaded jars can come from mirrors even for those tat use the
trunk
...
>>With my experience and understanding of maven, we would have to write plugins to
>>do what we want. Our software is not a simple standard java package, since we
>>do a lot with cocoon, copyless issues, and skin/plugin fetching. Since this is
>>so unique to our project, I don't think maven's standard build system will help
>>us much.
>
> I don't know much about Maven, but resonate with Dave's comments.
>
> Are there simple repository systems that we could use
> for the "lib download" aspect.
> e.g. Apache Depot http://incubator.apache.org/depot/
+1
>>Matching a standard directory structure is certainly good. Not sure about
>>automatically downloading jars. That could be good, but I don't see a real need
>>for it; things work fine how they are.
>>
>>Another alternative to consider is to use a real scripting language instead of
>>Ant to do our builds. In my experience with skin fetching, ant simply isn't
>>designed to do the things we want to do. I am not familiar with python, but I
>>think it would be a good candidate.
>
> Is Ant able to call a python script to do certain tasks?
Yup, embedded.
Now I can say that I'm fully +1 for using Ant. I wanted to be sure I
didn't step on other's toes by assuming it per default :-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: build system (was: [proposal] SVN restructure for subprojects)
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
> Quoting Nicola Ken Barozzi:
>
> > Notice the 'bin' directory where users would think of finding it, as a
> > single thing to add to the system path variable. the trunk would become
> > the new FORREST_HOME
> >
> > Also, this would mean that we have to rethink our build system.
>
> I would like to see a SVN restructure in the near future, with minimal changes
> to the build system. Discussion and implementation of changes to FORREST_HOME,
> the bin location, and the build system in general will take *much* longer.
Yes do it in stages.
> > - Please no flame wars -
> >
> > As I see it we have two options: Ant and Maven.
> >
> > For Ant I am willing to help set it up in a way that it makes it easy to
> > do the above multi-project. I see it as a must that we use a lib
> > download system ALA Maven.
Why is it a *must*?
> > Other than this, I'm really open to any sensible technical comment on
> > this, along with proposals in helping out.
> >
>
> With my experience and understanding of maven, we would have to write plugins to
> do what we want. Our software is not a simple standard java package, since we
> do a lot with cocoon, copyless issues, and skin/plugin fetching. Since this is
> so unique to our project, I don't think maven's standard build system will help
> us much.
I don't know much about Maven, but resonate with Dave's comments.
Are there simple repository systems that we could use
for the "lib download" aspect.
e.g. Apache Depot http://incubator.apache.org/depot/
> Matching a standard directory structure is certainly good. Not sure about
> automatically downloading jars. That could be good, but I don't see a real need
> for it; things work fine how they are.
>
> Another alternative to consider is to use a real scripting language instead of
> Ant to do our builds. In my experience with skin fetching, ant simply isn't
> designed to do the things we want to do. I am not familiar with python, but I
> think it would be a good candidate.
Is Ant able to call a python script to do certain tasks?
--
David Crossley