Retire: Issue Tracker
-
If the subproject/component has its own issue tracker we have to close that.
It is enough to make it read-only, so these information are longer available.
--> open; use Jira EASYANT
--> asked infra per https://issues.apache.org/jira/browse/INFRA
When migrating the project from selfhosted to apache, we asked ourself
where to host the plugins artifacts, there was some discussion to store
them in apache's nexus instance, but it was not really designed for.
Easyant plugins are not distributed as jar, so maven layout was not really
appli
2017-01-07 19:45 GMT+01:00 Stefan Bodewig :
> On 2017-01-05, Jean-Louis Boudart wrote:
>
> > I'm a little bit puzzled. I still believe there some room to a build tool
> > as easyant, and i expect that in a near future fresh blood will come and
> > resurect the proje
On 2017-01-05, Jean-Louis Boudart wrote:
> I'm a little bit puzzled. I still believe there some room to a build tool
> as easyant, and i expect that in a near future fresh blood will come and
> resurect the project.
I really wish you had said this when we voted on retiring EasyAnt
> Even if i understand the purpose of archiving project without too much
> activity i don't get the point of shutting down home page and all
> related stuff (including old blog or even the domain name).
>
> For good or bad reason easyant build still rely on repo.easy
Hi,
I'm a little bit puzzled. I still believe there some room to a build tool
as easyant, and i expect that in a near future fresh blood will come and
resurect the project.
Even if i understand the purpose of archiving project without too much
activity i don't get the point of shutting
On 2017-01-05, Jan Matèrne (jhm) wrote:
> Retire: Releases
>
> --> open, doesnt have write privilege.
> --> could someone else remove that directory?
done
Stefan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.a
ely remove them.
I prefer removing the complete homepage.
--> done
https://git-wip-us.apache.org/repos/asf
ant-easyant-buildtypes.gitApache EasyAnt build types
ant-easyant-core.gitApache EasyAnt core
ant-easyant-easyant4e.git Apache EasyAnt for Eclipse
The Ant PMC voted [1] to archive the EasyAnt subproject and all its modules.
This means that all its resources are removed or made read only and no
further development will be done.
It also means that, if a community grows, the subproject could reactivated
[2].
Happy new year
Jan Matèrne
int.
> Retire: Announcement
>
> We have to announce the retirement of the subproject at dev@ant,
> announce@apache and the Ant main page.
> --> open
>text proposal:
>"
> The Ant PMC voted [1] to archive the EasyAnt subproject and
Back from holiday I want to do more about archiving EasyAnt.
My todo-list now is... there are some questions open I couldnt answer ...
Jan
Retire: Version Control
---
Most of our source code is in git, only "site" and "sandbox" use subversion.
--&g
On 2016-12-13, Jan Matèrne (jhm) wrote:
> - Gump: it seems, that there is no buildjob for EA
> https://svn.apache.org/viewvc/gump/metadata/profile/gump.xml?view=markup
> @Stefan: as our Gump master ;) please check
True, EasyAnt has never been added to Gump
The vote about archiving EasyAnt passed [1].
So according to [2] the todo list is:
Retire: Version Control
---
Most of our source code is in git, only "site" and "sandbox" use subversion.
--> only git for sources. Homepage in svn.
We place a marker
The vote about archiving EasyAnt starts on 05.December 2016 [1].
The result is:
* binding votes
+1: Jan, Stefan, Nicolas, Conor, Jean-Louis, Dominique
0: --
-1: --
* non binding votes
+1: --
0: --
-1: --
The vote passed and EasyAnt including all its subcomponents will be
+1
On Wed, Dec 7, 2016 at 8:14 AM, Jean-Louis Boudart <
jeanlouis.boud...@gmail.com> wrote:
> +1
>
> 2016-12-07 1:05 GMT+01:00 Conor MacNeill :
>
> > +1
> >
> > Conor
> >
> >
> > On 5 December 2016 at 18:04, Jan Matèrne (jhm)
> wro
+1
2016-12-07 1:05 GMT+01:00 Conor MacNeill :
> +1
>
> Conor
>
>
> On 5 December 2016 at 18:04, Jan Matèrne (jhm) wrote:
> > I start a vote for retiring EasyAnt and all its components:
> >
> > - core
> >
> > - buildtypes
> >
> > - plu
+1
Conor
On 5 December 2016 at 18:04, Jan Matèrne (jhm) wrote:
> I start a vote for retiring EasyAnt and all its components:
>
> - core
>
> - buildtypes
>
> - plugins
>
> - skeletons
>
> - tasks
>
> - easyant4e
>
>
>
> We never had a r
+1
Nicolas
> Le 5 déc. 2016 à 08:04, Jan Matèrne (jhm) a écrit :
>
> I start a vote for retiring EasyAnt and all its components:
>
> - core
>
> - buildtypes
>
> - plugins
>
> - skeletons
>
> - tasks
>
> - easyant4e
>
>
>
> We ne
On 2016-12-05, Jan Matèrne (jhm) wrote:
> I start a vote for retiring EasyAnt and all its components:
> - core
> - buildtypes
> - plugins
> - skeletons
> - tasks
> - easyant4e
+1
Stefan
-
To unsubscribe,
I start a vote for retiring EasyAnt and all its components:
- core
- buildtypes
- plugins
- skeletons
- tasks
- easyant4e
We never had a real release after the incubator.
The last 'real' activity in vcs was in 09/2015 for EA-Core and 07/2013 for
EA4E.
It seems that we
Github user asfgit closed the pull request at:
https://github.com/apache/ant-easyant-core/pull/3
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user asfgit closed the pull request at:
https://github.com/apache/ant-easyant-core/pull/2
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user AQuillet opened a pull request:
https://github.com/apache/ant-easyant-core/pull/3
Fix plugin report information
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/AQuillet/ant-easyant-core feature/EASYANT-77
GitHub user AQuillet opened a pull request:
https://github.com/apache/ant-easyant-core/pull/2
Upgrade Junit: fix Eclipse project classpath
https://issues.apache.org/jira/browse/EASYANT-76
You can merge this pull request into a Git repository by running:
$ git pull https
Github user asfgit closed the pull request at:
https://github.com/apache/ant-easyant-core/pull/1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user AQuillet opened a pull request:
https://github.com/apache/ant-easyant-core/pull/1
Compliance with J2SE 1.7
https://issues.apache.org/jira/browse/EASYANT-75
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/AQuillet/ant
BTW here some issues regarding the EA website
https://issues.apache.org/jira/browse/EASYANT-66
https://issues.apache.org/jira/browse/EASYANT-74
https://issues.apache.org/jira/browse/EASYANT-63
Jan
> -Ursprüngliche Nachricht-
> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
>
I'll tried that also
$ easyant publish-shared
But xooki requires Java 1.6 and I failed to get it running ...
On Windows cmd.exe with Java 1.6:
xooki:generate:
[xooki:generate] processing 65 source files...
[generate] script file ./sources/xooki/xooki.js is not found
[generate] Resul
Hi Nicolas,
Check at the module.ant in the project there is a target there (which
unfortunatly doesn’t contain description) named “generate-site”.
Like ant when you type “easyant -p” you only see target with descriptions.
Cheers,
2015-01-22 23:23 GMT+01:00 Nicolas Lalevée :
> Hi,
&g
Hi,
I tried to fixed the issues raised by Sebb about the links in EasyAnt’s website
and I got issues.
I am not sure which target should be called to get things generated. The
command « easyant -p » is listing the usual targets for a project with a bunch
of code, but this is not helpful and
#x27;
> > Betreff: AW: Build failed in Jenkins: EasyAnt #175
> >
> > Changed the configuration
> > SCM-Git::Additional Behaviour
> > Advanced sub-modules behaviour
> > Recursively update submodules = true
> >
> > Build successful
> > Job failed
All blue now.
Jan
> -Ursprüngliche Nachricht-
> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> Gesendet: Mittwoch, 18. Juni 2014 08:09
> An: 'Ant Developers List'
> Betreff: AW: Build failed in Jenkins: EasyAnt #175
>
> Changed the configuration
Von: Jean-Louis Boudart [mailto:jeanlouis.boud...@gmail.com]
> Gesendet: Dienstag, 17. Juni 2014 21:38
> An: Ant Developers List
> Betreff: Re: Build failed in Jenkins: EasyAnt #175
>
> Hi,
>
> I added xooki as easyant submodule to handle documentation.
> Unfortunatly jenk
Hi,
I added xooki as easyant submodule to handle documentation.
Unfortunatly jenkins doesn't seems to fetch submodules. I haven't enough
karma there to manage job configuration, could someone with enough karma
check the config to see if there is an option to fetch git submodules ?
201
Not sure if there is something to generate with xooki ...
Jan
> Log:
> repo changed to git
>
> Modified:
> ant/site/easyant/sources/Sourcerepository.html
>
> --- ant/site/easyant/sources/Sourcerepository.html (original)
> +++ ant/site/easyant/sources/Sourcereposito
Good catch unfortunatly like you i have no commit access there :/
2014-06-05 8:15 GMT+02:00 Jan Matèrne (jhm) :
> In easyant-core there are two disclaimers (DISCLAIMER, README) saying that
> EA is still in incubation.
>
> I thought i was graduated ... this was also post
In easyant-core there are two disclaimers (DISCLAIMER, README) saying that
EA is still in incubation.
I thought i was graduated ... this was also posted on
http://blog.easyant.org/apache-graduation/
This should be updated.
Jan
Le 19 nov. 2013 à 11:16, Richard C Hidalgo Lorite a écrit :
> hi, is there an eclipse plugin for easyant?
There is one, but it never has been released. Its source can be found there:
https://svn.apache.org/repos/asf/ant/easyant/easyant4e/trunk
Nico
hi, is there an eclipse plugin for easyant? if not, is there a set of
standard ant libraries with typical targets that one can use with ivyide
eclipse plugin? thx in advance
;>
>> Not necessary from my point of view. My only advice is to avoid legacy
>> (or technical debt ;) at such early time.
>>
>> I was suggesting to keep backward compatibility mainly because easyant is
> build by easyant :). Though we need "older" plugins t
l debt ;) at such early time.
>
> I was suggesting to keep backward compatibility mainly because easyant is
build by easyant :). Though we need "older" plugins to build the new
easyant and "vice et versa".
> >> Point 3 : By two steps i meant running a global resolve
I also forgot one comparison.
>From my understaning, please correct me if I'm wrong:
- maven plugins are bound to phases, lifecycles specify the order of the phases
- easyant plugins are bound to extension points, the order derives
from dependencies between the extension points
- mave
on non autorisée ou la copie de ceci
> est interdite. Ce message sert à l'information seulement et n'aura pas
> n'importe quel effet légalement obligatoire. Étant donné que les email
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
>
e sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> From: dridi.boukelmo...@zenika.com
> Date: Mon, 26 Aug 2013 20:31:32 +0200
> Subject: Re: Easyant - Plugin conflict management
> To: dev@ant.apache.org
>
> Hi,
>
> This i
eply to see how it really works.
>
> Nicolas
>
Best Regards,
Dridi
[1] it's just that I don't like it :p
>>
>>
>>
>>
>> 2013/8/17 Nicolas Lalevée
>>
>>> Long overdue response.
>>>
>>> Le 3 août 2013 à 13:33, Jean
; a écrit :
>>
>>> Hi there,
>>>
>>> It becomes necesssary to manage conflicts between plugins.
>>> This issues has been raised many time and is referenced on jira[1].
>>>
>>> Currently easyant offers import task taking some specific attribu
rdue response.
>
> Le 3 août 2013 à 13:33, Jean-Louis Boudart
> a écrit :
>
> > Hi there,
> >
> > It becomes necesssary to manage conflicts between plugins.
> > This issues has been raised many time and is referenced on jira[1].
> >
> > Currently
Long overdue response.
Le 3 août 2013 à 13:33, Jean-Louis Boudart a
écrit :
> Hi there,
>
> It becomes necesssary to manage conflicts between plugins.
> This issues has been raised many time and is referenced on jira[1].
>
> Currently easyant offers import task ta
Hi there,
It becomes necesssary to manage conflicts between plugins.
This issues has been raised many time and is referenced on jira[1].
Currently easyant offers import task taking some specific attributes to
resolve a plugin (mainly organisation, module name and revision).
This task will
ones by having two
> internal repositories :
> - http://repository.easyant.org/apache-easyant/
> - http://repository.easyant.org/community-easyant/
First of all, we'd still distribute all Apache releases via
dist.apache.org, but there isn't any reason why they couldn
Let's first define a few things.
We need to distribute many things :
- easyant distribution itself (shipping ivy, ant and easyant-core.jar
itself). As the entry point of easyant it remains "natural" to be
distributed through dist.apache.org
- additionnal task we may
ot;ASF plugins" not for "outside ASF" ;)
>>
>> Jan
>>
>>> -Ursprüngliche Nachricht-
>>> Von: Antoine Levy Lambert [mailto:anto...@gmx.de]
>>> Gesendet: Freitag, 3. Mai 2013 10:06
>>> An: Ant Developers List
>>> Betreff: Re: E
On 2013-05-03, Jean-Louis Boudart wrote:
> No objections either if both Apache & non Apache plugins are on
> bintray ? :p
Then I must admit I misunderstood your proposal. Why do we need a
separate distribution point for ASF released EasyAnt plugins?
Maybe you need to enlighten those
t; Von: Antoine Levy Lambert [mailto:anto...@gmx.de]
> > Gesendet: Freitag, 3. Mai 2013 10:06
> > An: Ant Developers List
> > Betreff: Re: Evaluating Bintray as a distribution platform for easyant
> > plugins
> >
> > Hello Jean-Louis,
> >
> > I was not a
Bintray as a distribution platform for easyant
> plugins
>
> Hello Jean-Louis,
>
> I was not aware of bintray, I have just looked at the web site.
>
> No objections from me.
>
> Regards,
>
>
> Antoine
> On May 3, 2013, at 2:14 AM, Jean-Louis Boudart wrot
Here is the original thread from easyant-dev ML during apache incubation :
>> http://markmail.org/thread/uv2xkj63rkdh2thh
>> Le 29 avr. 2013 20:53, "Jean-Louis Boudart"
>> a écrit :
>>
>>>
>>>> I would prefer having the artifacts on ASF ser
No objections? :p
Le 29 avr. 2013 20:59, "Jean-Louis Boudart" a
écrit :
> Here is the original thread from easyant-dev ML during apache incubation :
> http://markmail.org/thread/uv2xkj63rkdh2thh
> Le 29 avr. 2013 20:53, "Jean-Louis Boudart"
> a écrit :
>
Here is the original thread from easyant-dev ML during apache incubation :
http://markmail.org/thread/uv2xkj63rkdh2thh
Le 29 avr. 2013 20:53, "Jean-Louis Boudart"
a écrit :
>
> > I would prefer having the artifacts on ASF servers. A (Nexus based)
> &g
eally possible ?
> > As bintray and github supports "Markdown" syntax, i made some
> > experimentation on plugin documentation generation.
>
> Are you writing the markdown by hand or do you generate that from java
> source?
Generated through easyant "plugin
On 2013-04-29, Jan Matèrne (jhm) wrote:
>> I would prefer having the artifacts on ASF servers. A (Nexus based)
>> repository is at https://repository.apache.org/ Ant + Ivy are available
>> at https://repository.apache.org/content/repositories/releases/
> Oh - I mean that only for "ASF plugins".
bility of hosting plugins outside the ASF.
But if possible I would host them at ASF so the community has one
"connection point", especially if EasyAnt is just migrated to ASF.
Jan
-
To unsubscribe, e-mail: dev-unsubs
. But should be possible ...
(maybe we have to ask #infra)
> As bintray and github supports "Markdown" syntax, i made some
> experimentation on plugin documentation generation.
Are you writing the markdown by hand or do you generate that from java
source?
> Result on github : https:
Dear EasyAnters,
I've been working on sonar integration as a plugin for easyant.
Source are hosted on github :https://github.com/easyant/sonar-easyant-plugin
.
Since a few weeks, JFrog (guys behind Artifactory) opened a new online
service for OpenSourcers : Bintray.
Bintray is a social se
Done on trunk
Le 17 avr. 2013 18:32, "Xavier Hanin" a écrit :
> On Tue, Apr 16, 2013 at 8:19 AM, Jean-Louis Boudart <
> jeanlouis.boud...@gmail.com> wrote:
>
> > What is the desired behavior when junit is missing in project classpath ?
> > 1 - ignore test ? maybe with a message @info level ?
> >
Xavier-
in Maven if you have no Junit tests located in .\src\test folf
then all test (test-scoped) dependencies are skipped
the same behaviour should be emulated in 'EasyAnt'
My 2 cents
Martin __
Note de déni et de confidentialitéCe m
On Tue, Apr 16, 2013 at 8:19 AM, Jean-Louis Boudart <
jeanlouis.boud...@gmail.com> wrote:
> What is the desired behavior when junit is missing in project classpath ?
> 1 - ignore test ? maybe with a message @info level ?
> 2 - configure the plugin to use junit version specified in the project. and
to start. Maybe only a link to the plugins repo to
browse the source online could be a good start.
>
>
> > - I've written a small tool to convert basic (very basic I mean) pom
> files
> > to module.ivy, and the result is interesting: on a bunch of modules, not
> >
-Louis Boudart
> Hi Xavier,
>
> Thanks for your feedback !
>
>
> 2013/4/15 Xavier Hanin
>
>>
>> I've been playing a little bit with easyant 0.9 this wek-end, and I have
>> some feedback:
>> - I have some issues with the multi module example:
>>
Hi Xavier,
Thanks for your feedback !
2013/4/15 Xavier Hanin
>
> I've been playing a little bit with easyant 0.9 this wek-end, and I have
> some feedback:
> - I have some issues with the multi module example:
> - if I run "easyant verify" at the root I g
Hi there,
It's been a while :-)
I've been playing a little bit with easyant 0.9 this wek-end, and I have
some feedback:
- I have some issues with the multi module example:
- if I run "easyant verify" at the root I get an error: "The
for must include junit.jar if n
As far as I can tell, the status of EasyAnt on the incubator pages are up to
date, it is not listed anymore as an Incubator project.
There was still things in the svn, kept because we needed to wait for the site
to be moved. I have just completely deleted it cf r1461470.
I also just put in
Do you mean the incubator logo on easyant site? or stuff at
http://incubator.apache.org/projects/easyant.html ?
2013/3/27 Stefan Bodewig
> On 2013-03-27, Jean-Louis Boudart wrote:
>
> > PS: i think we forgot setuping redirection from incubator.a.o/easyant to
> > ant.a.o/e
On 2013-03-27, Jean-Louis Boudart wrote:
> PS: i think we forgot setuping redirection from incubator.a.o/easyant to
> ant.a.o/easyant. I will fix this today
There may be some cleanup to do inside the Incubator site itself as
well.
All infra request are now closed. Migration seems over! Long live
http://ant.apache.org/easyant/
PS: i think we forgot setuping redirection from incubator.a.o/easyant to
ant.a.o/easyant. I will fix this today
Le 23 mars 2013 15:25, "Nicolas Lalevée" a
écrit :
>
> Le 16 m
On 2013-03-23, Nicolas Lalevée wrote:
> We need to give r/w rights to Jérôme Benois (jbenois) and Siddhartha
> Purkayastha (kpsiddharth).
Done
Stefan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For addition
Le 16 mars 2013 à 01:39, Nicolas Lalevée a écrit :
> Finally ! We're there !
>
> Now we need to move stuff. EasyAnt is graduating like Ivy did, so about the
> resources, here is the following suggestions.
>
> * The svn tree
> We will move the svn tree of EasyAnt u
> There is nothing in Gump about EasyAnt
Should it be?
Jan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Le 16 mars 2013 à 09:47, Jan Matèrne (jhm) a écrit :
> Maybe some changes in the Gump metadata and Jenkins jobs?
Good catch. There is nothing in Gump about EasyAnt but there is in Jenkins.
I'll update it too.
Nicolas
>
> Jan
>
>
>> -Ursprüngliche Nac
Maybe some changes in the Gump metadata and Jenkins jobs?
Jan
> -Ursprüngliche Nachricht-
> Von: Stefan Bodewig [mailto:bode...@apache.org]
> Gesendet: Samstag, 16. März 2013 06:49
> An: dev@ant.apache.org
> Betreff: Re: EasyAnt is graduating
>
> On 2013-03-16,
On 2013-03-16, Nicolas Lalevée wrote:
> Finally ! We're there !
Welcome.
> * The svn tree
> We will move the svn tree of EasyAnt under Ant's one. Everything except
> 'KEYS' and 'site' under http://svn.apache.org/repos/asf/incubator/easyant/
> will
Finally ! We're there !
Now we need to move stuff. EasyAnt is graduating like Ivy did, so about the
resources, here is the following suggestions.
* The svn tree
We will move the svn tree of EasyAnt under Ant's one. Everything except 'KEYS'
and 'site' under h
Congratulations EasyAnt,
Antoine
On Mar 6, 2013, at 2:34 PM, Nicolas Lalevée wrote:
> I count:
> - 5 binding +1
> - 1 non-binding +1
>
> The proposition is accepted.
>
> Thank you all.
>
> We'll go now to the incubator mailing lists to clear things up.
>
&
I count:
- 5 binding +1
- 1 non-binding +1
The proposition is accepted.
Thank you all.
We'll go now to the incubator mailing lists to clear things up.
Nicolas
Le 27 févr. 2013 à 19:44, Nicolas Lalevée a écrit :
> Hi,
>
> This is the come back of the proposal of bringing Eas
The Apache EasyAnt project is pleased to announce its 0.9-incubating
release.
Apache Easyant is a toolbox focusing on easing project build processes.
It's based on Apache Ant and Apache Ivy, and allows for maximum flexibily,
improved integration in existing build systems and provides conven
A great big +1.
With Ivy, we decided that having a separate users mailing list made
sense but that we were better off having a single developers mailing
list for both projects. I suggest we do the same again with EasyAnt
assuming the vote is successful this time, unless the EasyAnt committers
e 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"
+1
Would be fine to bring this incubation to an end.
Jan
> -Ursprüngliche Nachricht-
> Von: Antoine Levy Lambert [mailto:anto...@gmx.de]
> Gesendet: Donnerstag, 28. Februar 2013 00:18
> An: Ant Developers List
> Betreff: Re: [VOTE] Accept EasyAnt as a subproject - take 2
ain 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
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
+1
Maarten
From: Nicolas Lalevée
To: Ant Developers List
Sent: Wednesday, February 27, 2013 7:44 PM
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
+1
Nicolas
Le 27 févr. 2013 à 19:44, Nicolas Lalevée a écrit :
> 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
+1 Antoine
On Feb 27, 2013, at 1:44 PM, Nicolas Lalevée wrote:
> 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
[x] +1, I accept
2013/2/27 Nicolas Lalevée
> 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" und
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 mor
Le 15 août 2012 à 23:08, Maarten Coene a écrit :
> Nicolas,
>
> Maybe we could vote again later when there are more people around?
> I haven't been online for about a month, that's why you didn't get my vote.
Yes, this is what have been discussed on an easyant mai
2:41 PM
Subject: [RESULT][VOTE] Accept EasyAnt as a subproject
I am closing the vote. I count 2 binding +1, 1 non binding +1
The proposition failed to be accepted.
Further discussion will happen on easyant mailing lists.
Nicolas
Le 11 juil. 2012 à 10:48, Nicolas Lalevée a écrit :
> EasyAnt is
I am closing the vote. I count 2 binding +1, 1 non binding +1
The proposition failed to be accepted.
Further discussion will happen on easyant mailing lists.
Nicolas
Le 11 juil. 2012 à 10:48, Nicolas Lalevée a écrit :
> EasyAnt is a project based on Ant and Ivy which is in incubation un
-Louis there is no active committer - and for some
extended stretches there hasn't been any development at all. Sounds
familiar, doesn't it?
<http://www.ohloh.net/p/easyant/commits/summary>
The Ant community isn't the most active one by itself, a new project
might trigger more a
+1
On Jul 14, 2012 9:41 PM, "Bruce Atherton" wrote:
> I think this is a great idea, particularly if we can get the committers of
> EasyAnt interested in improving Ant and Ivy.
>
> +1.
>
> Would it be worthwhile to consider all the committers on EasyAnt as
> commi
s to indicate that we do need
the fresh blood that EasyAnt would bring.
Having said that, there do not seem to be the votes required to make
this happen unless others are willing to jump in and vote.
-
To unsubscribe, e-mail: d
1 - 100 of 325 matches
Mail list logo
