ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Louis Boudart <jeanlouis.boud...@gmail.com>
Subject Re: archiving EasyAnt
Date Mon, 09 Jan 2017 20:23:18 GMT
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.
There was also other plugins that couldn't be hosted on ASF side mostly
because of incompatible licenses, and we wanted to have one entrypoint to
fetch both "Apache plugins" and "non Apache plugins".
So we started evaluating our options including moving from selfhosted to
bintray [1], we kickstarted it but never finished the transition (mostly
lack of time on my side).

Not sure it would be to complex to finish this migration if it still make
sense.

That's why i said "for good of bad reasons" in my previous emails :).


[1]
http://ant.1045680.n5.nabble.com/Evaluating-Bintray-as-a-distribution-platform-for-easyant-plugins-td5714096.html

2017-01-06 8:03 GMT+01:00 Jan Matèrne (jhm) <apache@materne.de>:

> > 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 https://github.com/apache/ant-easyant-
> > core/blob/master/ivysettings.xml  and related discussion
> > http://ant.1045680.n5.nabble.com/Evaluating-Bintray-as-a-distribution-
> > platform-for-easyant-plugins-td5714096.html).
> > Note that with the sources on apache side we should still be able to
> > rebuild everything.
> >
> > I always thought apache projects needs to be "buildable"  during long
> > (that's why we have dist.apache.org and archive.apache.org) available,
> > but what is the point of having them available if we even don"t have
> > the available ressources to use it like the website/doc and so on ?? I
> > mean all this contribute to the history of the project and turning off
> > all those components/resource will clearly definitively kill the
> > project.
> >
> > I may be nostalgic on that topic but do we really want to do that ?
> >
> > If you all believe we should stop thoses resources/components down,
> > then fine i'll turn off everything, otherwise i will try to keep them
> > up  (domain included) as much as i can.
> >
> > WDYT ?
>
>
> I wasn't aware that the *.easyant.org resources were required for
> building EA.
> Being able to build even an archived project is valuable as you said -
> even if _I_ think,
> that we don't get new committers ...
>
> But when these resources are required for building EA, why aren't they
> hosted on Apache infrastructure?
> ATM we rely on external resources...
>
>
> Jan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>


-- 
Jean Louis Boudart

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message