[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ant-dev
Subject:    RE: [VOTE] Accept EasyAnt as a subproject - take 2
From:       Tim Enderling <T.Enderling () intershop ! de>
Date:       2013-02-28 14:09:52
Message-ID: 81454BDF21961D4FA3014B5291F8091401D1E9 () jenmbs02 ! ad ! intershop ! net
[Download RAW message or body]

Hi,

that's great news! We will we very happy to provide you with feedback.

Best Regards,
Tim

PS: Odd thing aside: I worked on a company intern concept to modularize Ant builds of \
software enriched with Ivy-meta data for a few months now (without tying us to \
Maven). Not knowing that there was EasyAnt and working on the basis of only Ant and \
Ivy I came to very similar conclusions regarding the design. Some of the technical \
details are even identical! - like providing paths to artifacts of a build module's \
dependencies in Ant paths like "acme#foo.foo.properties.file" to use them in Ant \
imports/includes. And I already stumbled upon the extension you brought into Ant and \
Ivy and was going to rely on them, not knowing where they actually came from. I'm \
very pleased to see, that someone has shared my thoughts and brought them a lot \
further :-)

> -----Original Message-----
> From: Jean-Louis Boudart [mailto:jeanlouis.boudart@gmail.com]
> Sent: Donnerstag, 28. Februar 2013 12:05
> To: Ant Developers List
> Subject: Re: [VOTE] Accept EasyAnt as a subproject - take 2
> 
> We will publish a updated documentation soon (probably tonight).
> 
> Currently, the community is really small as prior releases was using
> patched version of Ant and Ivy (mainly to introduce missing features sur as
> extensionPoints in Ant, or module inheritence in Ivy). This was probably a
> major issue, and explain why we didn't communicate too much outside of
> ant-dev mailing list about it.
> 
> We've made lot of work to contribute back our modifications to both tools
> and we now use official releases. In future we plan to bring more valuable
> features to both Ant and Ivy. This is one of the main reason motivating us
> to enter in ASF.
> In the meantime we changed a lot of structuring stuff in easyant itself to
> remain flexible and easier to use.
> 
> This release is a huge step for the project. And it's now time to promote
> EasyAnt as a usable tool and to widen the community.
> 
> Your feedback will be really appreciated.
> 
> 
> 2013/2/28 Tim Enderling <T.Enderling@intershop.de>
> 
> > Hi,
> > 
> > I didn't know that EasyAnt is still alive. EasyAnt might be exactly what
> > we are looking for in a solution to modularize our build system and
> > software. Some questions:
> > 
> > Is there a more up-to-date documentation than the one at
> > 
> http://incubator.apache.org/easyant/history/trunk/reference.html?Fromskimmi
> ng through (and besides there a quite a few obvious mistakes in it)
> > it seems to refer to a release prior to 0.9.
> > 
> > Also: How large is the community of EasyAnt, are there any references for
> > software projects using it? (I tried to get an idea for that by searching
> > for EasyAnt on stackoverflow, but that didn't turn out well.)
> > 
> > Thanks a lot
> > Tim Enderling
> > 
> > > -----Original Message-----
> > > From: Nicolas Lalevée [mailto:nicolas.lalevee@hibnet.org]
> > > Sent: Mittwoch, 27. Februar 2013 19:44
> > > To: Ant Developers List
> > > Subject: [VOTE] Accept EasyAnt as a subproject - take 2
> > > 
> > > Hi,
> > > 
> > > This is the come back of the proposal of bringing EasyAnt under the
> > > umbrella of the Ant PMC.
> > > 
> > > There were some discussion on incubator-general about the incubating
> > > hcatalog project being "graduated" under the umbrella of the Hive PMC.
> I
> > > think that our case is more clear and more standard regarding the ASF
> > > rules, but I'll remind here what is at stake, so there is no
> > > misunderstanding (I include myself on the potentially misunderstanding
> > > people).
> > > 
> > > EasyAnt code will be brought into Ant's svn tree.
> > > EasyAnt committers will become Ant committers but not part of the PMC
> > (on 5
> > > committers, 3 are already Ant ones, and 2 are part of Ant's PMC)
> > > The Ant PMC will be responsible for the code, the community, the next
> > > releases of EasyAnt.
> > > 
> > > Just like for Ivy. And I like the way it worked. Further more
> considering
> > > my path, I think it is good that there is no special right management
> in
> > > svn. I started as an IvyDE committer, I ended improving myself Ivy and
> > Ant.
> > > 
> > > Since the last vote tentative, the activity on EasyAnt remained the
> same,
> > > somehow low but continuous, not much less than Ant developers activity.
> > And
> > > lately we succeeded to get a release out.
> > > 
> > > To get yourself an opinion, here are some links:
> > > - the EasyAnt project incubator page:
> > > http://incubator.apache.org/projects/easyant.html
> > > - the archive of the mailing lists
> > > http://mail-archives.apache.org/mod_mbox/incubator-easyant-commits/
> > > http://mail-archives.apache.org/mod_mbox/incubator-easyant-dev/
> > > - the release
> > > http://www.apache.org/dist/incubator/easyant
> > > 
> > > So, should we accept EasyAnt as a subproject ?
> > > Please, cast your votes:
> > > [ ] +1, I accept
> > > [ ] +0, OK, but..
> > > [ ] -1, I disapprove, because..
> > > 
> > > Nicolas
> > > 
> > > 
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > > For additional commands, e-mail: dev-help@ant.apache.org
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > For additional commands, e-mail: dev-help@ant.apache.org
> > 
> > 
> 
> 
> --
> Jean Louis Boudart
> Independent consultant
> Apache EasyAnt commiter http://incubator.apache.org/easyant/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]