archiving EasyAnt

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 RETIRED_PROJECT file on th

Re: archiving EasyAnt

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 --

Re: Ivy - Proposal for reviving the project and moving towards a release

On 2016-12-12, Maarten Coene wrote: > We also have to find a release manager. I did it in the past when we > were on SVN, but I don't have enough GIT knowledge (and I don't have > the time to look into it) to do a new release. Maarten, is this

Re: IvyDE status

On 2016-12-11, Gintautas Grigelionis wrote: > I have a question, too: perhaps the entire ivyde site repo could be > converted to Git? The "ivyde site" is only a subdirectory of the whole of the Ant project website. Back when we migrated to git the way the ASF web hosting worked meant the site ha

Re: IvyDE status

Thanks for clarification. There are lots of duplications around there, and the overall process would surely benefit from some restructuring. I took the liberty of extracting the commits particular to style subdirectory (there are three of them, identical in ivy/source and ivyde/source trees). I wou

Re: Ivy - Proposal for reviving the project and moving towards a release

Maarten, thanks for volunteering to review the PRs. One of them has a test case. I will add a test for the other one. It looks like you have been involved with Ivy development and releases before, so I think you would be in a better position to decide if it should be 2.5.0 or 2.4.1. I personally p