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
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.
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
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
> 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
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
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:
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
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:
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.
Stefan
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
12 matches
Mail list logo