AW: archiving EasyAnt

2017-01-16 Thread jhm
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-13225

Re: archiving EasyAnt

2017-01-09 Thread Jean-Louis Boudart
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 applicable.

Re: archiving EasyAnt

2017-01-09 Thread Jean-Louis Boudart
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 project. > > I

Re: archiving EasyAnt

2017-01-07 Thread 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 project. I really wish you had said this when we voted on retiring EasyAnt. > Even if i

AW: archiving EasyAnt

2017-01-05 Thread jhm
> 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.easyant.org > (see

Re: archiving EasyAnt

2017-01-05 Thread Jean-Louis Boudart
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 down home

Re: archiving EasyAnt

2017-01-05 Thread Stefan Bodewig
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:

AW: archiving EasyAnt

2017-01-05 Thread jhm
Current status: Jan Retire: Version Control --- Most of our source code is in git, only "site" and "sandbox" use subversion. --> only git for sources. Homepage in svn. --> update EA-homepage --> Should we only place a note on the hp or completely remove them. I prefer

Re: archiving EasyAnt

2017-01-04 Thread Stefan Bodewig
On 2017-01-04, Jan Matèrne (jhm) wrote: > --> Should we only place a note on the hp or completely remove them. > I prefer removing the complete homepage. I'd leave behind a note and point to the read-only SCMs so people who want to pick up development again have a starting point. > Retire:

AW: archiving EasyAnt

2017-01-04 Thread jhm
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

Re: archiving EasyAnt

2016-12-13 Thread Stefan Bodewig
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. Stefan

archiving EasyAnt

2016-12-13 Thread jhm
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 mark