You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by "Jan Matèrne (jhm)" <ap...@materne.de> on 2016/12/05 07:04:51 UTC
VOTE Retire IvyDE
I start a vote for retiring IvyDE.
The last release was in 11/2013.
The last 'real' code activity was in 08/2014.
It seems that we havent the community, committers and PMC to hold this
subproject.
The general procedure is described in http://ant.apache.org/processes.html.
I start with my +1.
Jan
AW: VOTE Retire IvyDE - RESULT
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
The vote about archiving IvyDE starts on 05.December 2016 [1].
The result is:
* binding votes
+1: (Jan), (Nicolas), Jean-Louis, Dominique,
0: Stefan
-1: --
asks for cancelling: Nicolas [3], Jan [4]
* non binding votes
+1: --
0: --
-1: Gintas [2]
I interpret the asks for cancelling as changing from a +1 to a -1, so we haven't more +1 than -1.
Therefore the vote failed and IvyDE will be alive as it is.
I am happy that the discussion about archiving brings such an amount of new energy. ;-)
Jan
[1] http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3C001301d24ec5%24e0040790%24a00c16b0%24%40de%3E
[2] http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3CCALVNWHVZs6wSSKqG1wCN8sZsBPApg%3Dg1Q%2B0%3DZqg9h81pOOtpOg%40mail.gmail.com%3E
[3] http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3C2E959BA8-CCBE-4C24-B0A9-831655AD8E9D%40hibnet.org%3E
[4] http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3C002701d2518d%24e827b280%24b8771780%24%40de%3E
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
AW: VOTE Retire IvyDE
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
> Very well, how does one revive a project?
>
> Gintas
If you ask for the process of reactivating it after archiving, that's documented at http://ant.apache.org/processes.html.
But ATM it is still alive - but sleeping. ;-)
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: VOTE Retire IvyDE
Posted by Gintautas Grigelionis <g....@gmail.com>.
Very well, how does one revive a project?
Gintas
2016-12-08 21:01 GMT+01:00 Jan Matèrne (jhm) <ap...@materne.de>:
> > Considering the current discussion around IvyDE and the involvement of
> > Gintas, maybe we could cancel this vote, at least postpone it ?
> >
> > Nicolas
>
>
> Yes, I agree.
> The discussion and the vote about retiring IvyDE had brought much more
> activity than the months before (as I recognized).
>
> But I haven't found any rule about cancelling a vote. Until now we have
> collected enough +1s to archive IvyDE and I don't want to affront somebody.
>
>
> Jan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
AW: VOTE Retire IvyDE
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
> Considering the current discussion around IvyDE and the involvement of
> Gintas, maybe we could cancel this vote, at least postpone it ?
>
> Nicolas
Yes, I agree.
The discussion and the vote about retiring IvyDE had brought much more activity than the months before (as I recognized).
But I haven't found any rule about cancelling a vote. Until now we have collected enough +1s to archive IvyDE and I don't want to affront somebody.
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: VOTE Retire IvyDE
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Considering the current discussion around IvyDE and the involvement of Gintas, maybe we could cancel this vote, at least postpone it ?
Nicolas
> Le 5 déc. 2016 à 08:04, Jan Matèrne (jhm) <ap...@materne.de> a écrit :
>
> I start a vote for retiring IvyDE.
>
> The last release was in 11/2013.
>
> The last 'real' code activity was in 08/2014.
>
>
>
> It seems that we havent the community, committers and PMC to hold this
> subproject.
>
>
>
> The general procedure is described in http://ant.apache.org/processes.html.
>
>
>
>
>
> I start with my +1.
>
>
>
>
>
> Jan
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: IvyDE status (Was: VOTE Retire IvyDE)
Posted by Gintautas Grigelionis <g....@gmail.com>.
AFAICS, Subversion is invoked in one of the targets connected to packaging
of a release, and I'm looking into an equivalent for Git.
What is more interesting is getting all Eclipse components. Current process
depends on finding a "good" mirror, and I'm tempted to investigate a
possibility to use updatesite resolver instead...
The point about using Java 8 is, you need at least Eclipse Mars (or the
other way around), period. And then there's all the GEF 4+ migration...
Gintas
2016-12-08 10:45 GMT+01:00 Nicolas Lalevée <ni...@hibnet.org>:
> I am forking the thread to not pollute the vote.
>
> > Le 7 déc. 2016 à 19:56, Gintautas Grigelionis <g....@gmail.com>
> a écrit :
> >
> > I decided to take a quick look at the build process and it's not broken
> per
> > se, rather it's hardcoded to Eclipse SDK 3.7.1 foe Win32.
>
> You confirm the doc is being correctly build ? If that effectively the
> case, it is good to know, thank you for looking into it.
> But one thing is broken for sure: the Ant targets to build IvyDE for the
> release, because they still assert that the sources are being hosted in
> subversion.
>
> > I would like to
> > make the process to adapt to the build platform. Any suggestions for a
> > reasonable Eclipse baseline? Should we target Java 8, that would be 4.5
> (or
> > maybe even 4.5.2).
>
> Here is what is currently supported:
> http://ant.apache.org/ivy/ivyde/history/trunk/compatibility.html <
> http://ant.apache.org/ivy/ivyde/history/trunk/compatibility.html>
> It certainly can be reviewed.
>
> As a general rule I would make IvyDE support the same version of the JVM
> as Ivy and Eclipse does. A thing to note is that some IvyDE users are
> installing it in their IBM RAD editor, so it would be nice to continue
> supporting if it doesn’t require much effort.
>
> Nicolas
>
>
AW: IvyDE status
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
changed that, thanks
Jan
> -----Ursprüngliche Nachricht-----
> Von: Gintautas Grigelionis [mailto:g.grigelionis@gmail.com]
> Gesendet: Freitag, 16. Dezember 2016 18:22
> An: Ant Developers List
> Betreff: Re: IvyDE status
>
> One more thing: http://ant.apache.org/git.html still links to
> Subversion repo for IvyDE.
>
> Gintas
>
> 2016-12-15 10:13 GMT+01:00 Gintautas Grigelionis
> <g....@gmail.com>:
>
> > Great! May I suggest adding repos ant-site-sources,
> > ant-ivy-site-sources, ant-ivyde-site-sources and ant-site (for
> publishing using the git workflow)?
> >
> > Gintas
> >
> > 2016-12-15 8:43 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
> >
> >> On 2016-12-13, Gintautas Grigelionis wrote:
> >>
> >> > 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 would happily push them to Github if I had a permission to
> >> > https://github.com/apache/any-ivy-site-styles, otherwise you may
> >> > follow this procedure
> >>
> >> github is a read-only mirror of repos hosted at the ASF, even the
> >> Ant/Ivy committers can't directly push there.
> >>
> >> https://github.com/apache/ant-ivy-site-styles is a very curious case
> >> as it claims to mirror a repository that doesn't exist (I wanted to
> >> manually push the svn files there but fail to find the repository).
> >>
> >> It would be good if anybody could ask INFRA in order to figure out
> >> what exactly the repo is mirroring as I don't see anything matching
> >> at https://git-wip-us.apache.org/repos/asf - I'll do so myself at
> the
> >> weekend, if nobody else finds time before that.
> >>
> >> Stefan
> >>
> >> --------------------------------------------------------------------
> -
> >> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For
> additional
> >> commands, e-mail: dev-help@ant.apache.org
> >>
> >>
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Site stuff (in particular Ivy and IvyDE)
Posted by Gintautas Grigelionis <g....@gmail.com>.
Perhaps you're right... I thought of splitting of /sources from SVN site
repo into separate Git repos. Then, pages compiled from /sources and/or
project documentation releases corresponding to /doc will be published to
asf-site branch in respective repo (not unlike gh-pages branch with Github
Pages). Currently existing compiled pages must be commited to the branch as
soon as it is created. That, in turn, will be picked up by gitpubsub and
pushed into repo(s) used by the website (
https://blogs.apache.org/infra/entry/git_based_websites_available). It is
not clear to me whether gitpubsub can aggregate Ant/Ivy/IvyDE. If not, we
might need one site repo for pushing all compiled pages to (instead of
having asf-site branches in every repo).
Gintas
2016-12-20 21:16 GMT+01:00 Jan Matèrne (jhm) <ap...@materne.de>:
> I don't see any benefit of having one repo for all sites as they are built
> differently (ant+velocity, xooki, ...).
> Where we need the sites? Only online or in distros/manuals?
>
> I don't know the git-site-workflow, but I think I had heard something like
> gitpubsub ...
> Alternatively we could commit the generated files into a svn-repo (outch).
>
>
> Jan
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Gintautas Grigelionis [mailto:g.grigelionis@gmail.com]
> > Gesendet: Montag, 19. Dezember 2016 14:15
> > An: Ant Developers List
> > Betreff: Re: Site stuff (in particular Ivy and IvyDE)
> >
> > IvyDE and Ivy share styles. These are not necessary for builds (at
> > least, from what I saw with IvyDE), but it sure helps to be able to get
> > the look and feel.
> >
> > It seems sensible to me to have separate repos for site sources, one
> > per project, and another repo for publishing which would aggregate
> > built sites and all releases for all projects (that's how IvyDE builds
> > work, AFAICS).
> >
> > Gintas
> >
> > 2016-12-19 12:41 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
> >
> > > On 2016-12-15, Gintautas Grigelionis wrote:
> > >
> > > >> 2016-12-15 8:43 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
> > >
> > > >> https://github.com/apache/ant-ivy-site-styles is a very curious
> > > >> case as it claims to mirror a repository that doesn't exist (I
> > > >> wanted to manually push the svn files there but fail to find the
> > repository).
> > >
> > > >> It would be good if anybody could ask INFRA in order to figure out
> > > >> what exactly the repo is mirroring as I don't see anything
> > matching
> > > >> at https://git-wip-us.apache.org/repos/asf - I'll do so myself at
> > > >> the weekend, if nobody else finds time before that.
> > >
> > > > Great! May I suggest adding repos ant-site-sources,
> > > > ant-ivy-site-sources, ant-ivyde-site-sources and ant-site (for
> > > > publishing using the git
> > > workflow)?
> > >
> > > Not exactly weekend anymore :-)
> > >
> > > https://github.com/apache/ant-ivy-site-styles and
> > > https://github.com/apache/any-ivy-site-styles
> > >
> > > seem to be the same and neither has ever been requested by us AFAICT.
> > >
> > > Assuming we wanted to restructure the site stuff, what would it look
> > > like?
> > >
> > > Do we want to move to git? All of it or just parts? How many repos do
> > > we want to use (a single one as we do right now, or one for
> > > Ant+antlibs and several for Ivy and IvyDE)? I'm not familiar with how
> > > the Ivy and IvyDE sites get built.
> > >
> > > Stefan
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
> > > commands, e-mail: dev-help@ant.apache.org
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
AW: Site stuff (in particular Ivy and IvyDE)
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
I don't see any benefit of having one repo for all sites as they are built differently (ant+velocity, xooki, ...).
Where we need the sites? Only online or in distros/manuals?
I don't know the git-site-workflow, but I think I had heard something like gitpubsub ...
Alternatively we could commit the generated files into a svn-repo (outch).
Jan
> -----Ursprüngliche Nachricht-----
> Von: Gintautas Grigelionis [mailto:g.grigelionis@gmail.com]
> Gesendet: Montag, 19. Dezember 2016 14:15
> An: Ant Developers List
> Betreff: Re: Site stuff (in particular Ivy and IvyDE)
>
> IvyDE and Ivy share styles. These are not necessary for builds (at
> least, from what I saw with IvyDE), but it sure helps to be able to get
> the look and feel.
>
> It seems sensible to me to have separate repos for site sources, one
> per project, and another repo for publishing which would aggregate
> built sites and all releases for all projects (that's how IvyDE builds
> work, AFAICS).
>
> Gintas
>
> 2016-12-19 12:41 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
>
> > On 2016-12-15, Gintautas Grigelionis wrote:
> >
> > >> 2016-12-15 8:43 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
> >
> > >> https://github.com/apache/ant-ivy-site-styles is a very curious
> > >> case as it claims to mirror a repository that doesn't exist (I
> > >> wanted to manually push the svn files there but fail to find the
> repository).
> >
> > >> It would be good if anybody could ask INFRA in order to figure out
> > >> what exactly the repo is mirroring as I don't see anything
> matching
> > >> at https://git-wip-us.apache.org/repos/asf - I'll do so myself at
> > >> the weekend, if nobody else finds time before that.
> >
> > > Great! May I suggest adding repos ant-site-sources,
> > > ant-ivy-site-sources, ant-ivyde-site-sources and ant-site (for
> > > publishing using the git
> > workflow)?
> >
> > Not exactly weekend anymore :-)
> >
> > https://github.com/apache/ant-ivy-site-styles and
> > https://github.com/apache/any-ivy-site-styles
> >
> > seem to be the same and neither has ever been requested by us AFAICT.
> >
> > Assuming we wanted to restructure the site stuff, what would it look
> > like?
> >
> > Do we want to move to git? All of it or just parts? How many repos do
> > we want to use (a single one as we do right now, or one for
> > Ant+antlibs and several for Ivy and IvyDE)? I'm not familiar with how
> > the Ivy and IvyDE sites get built.
> >
> > Stefan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
> > commands, e-mail: dev-help@ant.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Site stuff (in particular Ivy and IvyDE)
Posted by Gintautas Grigelionis <g....@gmail.com>.
IvyDE and Ivy share styles. These are not necessary for builds (at least,
from what I saw with IvyDE), but it sure helps to be able to get the look
and feel.
It seems sensible to me to have separate repos for site sources, one per
project, and another repo for publishing which would aggregate built sites
and all releases for all projects (that's how IvyDE builds work, AFAICS).
Gintas
2016-12-19 12:41 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
> On 2016-12-15, Gintautas Grigelionis wrote:
>
> >> 2016-12-15 8:43 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
>
> >> https://github.com/apache/ant-ivy-site-styles is a very curious case as
> >> it claims to mirror a repository that doesn't exist (I wanted to
> >> manually push the svn files there but fail to find the repository).
>
> >> It would be good if anybody could ask INFRA in order to figure out what
> >> exactly the repo is mirroring as I don't see anything matching at
> >> https://git-wip-us.apache.org/repos/asf - I'll do so myself at the
> >> weekend, if nobody else finds time before that.
>
> > Great! May I suggest adding repos ant-site-sources, ant-ivy-site-sources,
> > ant-ivyde-site-sources and ant-site (for publishing using the git
> workflow)?
>
> Not exactly weekend anymore :-)
>
> https://github.com/apache/ant-ivy-site-styles and
> https://github.com/apache/any-ivy-site-styles
>
> seem to be the same and neither has ever been requested by us AFAICT.
>
> Assuming we wanted to restructure the site stuff, what would it look
> like?
>
> Do we want to move to git? All of it or just parts? How many repos do we
> want to use (a single one as we do right now, or one for Ant+antlibs and
> several for Ivy and IvyDE)? I'm not familiar with how the Ivy and IvyDE
> sites get built.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
Site stuff (in particular Ivy and IvyDE)
Posted by Stefan Bodewig <bo...@apache.org>.
On 2016-12-15, Gintautas Grigelionis wrote:
>> 2016-12-15 8:43 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
>> https://github.com/apache/ant-ivy-site-styles is a very curious case as
>> it claims to mirror a repository that doesn't exist (I wanted to
>> manually push the svn files there but fail to find the repository).
>> It would be good if anybody could ask INFRA in order to figure out what
>> exactly the repo is mirroring as I don't see anything matching at
>> https://git-wip-us.apache.org/repos/asf - I'll do so myself at the
>> weekend, if nobody else finds time before that.
> Great! May I suggest adding repos ant-site-sources, ant-ivy-site-sources,
> ant-ivyde-site-sources and ant-site (for publishing using the git workflow)?
Not exactly weekend anymore :-)
https://github.com/apache/ant-ivy-site-styles and
https://github.com/apache/any-ivy-site-styles
seem to be the same and neither has ever been requested by us AFAICT.
Assuming we wanted to restructure the site stuff, what would it look
like?
Do we want to move to git? All of it or just parts? How many repos do we
want to use (a single one as we do right now, or one for Ant+antlibs and
several for Ivy and IvyDE)? I'm not familiar with how the Ivy and IvyDE
sites get built.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: IvyDE status
Posted by Gintautas Grigelionis <g....@gmail.com>.
One more thing: http://ant.apache.org/git.html still links to Subversion
repo for IvyDE.
Gintas
2016-12-15 10:13 GMT+01:00 Gintautas Grigelionis <g....@gmail.com>:
> Great! May I suggest adding repos ant-site-sources, ant-ivy-site-sources,
> ant-ivyde-site-sources and ant-site (for publishing using the git workflow)?
>
> Gintas
>
> 2016-12-15 8:43 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
>
>> On 2016-12-13, Gintautas Grigelionis wrote:
>>
>> > 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 would happily push them to Github if I had a permission to
>> > https://github.com/apache/any-ivy-site-styles, otherwise you may follow
>> > this procedure
>>
>> github is a read-only mirror of repos hosted at the ASF, even the
>> Ant/Ivy committers can't directly push there.
>>
>> https://github.com/apache/ant-ivy-site-styles is a very curious case as
>> it claims to mirror a repository that doesn't exist (I wanted to
>> manually push the svn files there but fail to find the repository).
>>
>> It would be good if anybody could ask INFRA in order to figure out what
>> exactly the repo is mirroring as I don't see anything matching at
>> https://git-wip-us.apache.org/repos/asf - I'll do so myself at the
>> weekend, if nobody else finds time before that.
>>
>> Stefan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>>
>>
>
Re: IvyDE status
Posted by Gintautas Grigelionis <g....@gmail.com>.
Great! May I suggest adding repos ant-site-sources, ant-ivy-site-sources,
ant-ivyde-site-sources and ant-site (for publishing using the git workflow)?
Gintas
2016-12-15 8:43 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
> On 2016-12-13, Gintautas Grigelionis wrote:
>
> > 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 would happily push them to Github if I had a permission to
> > https://github.com/apache/any-ivy-site-styles, otherwise you may follow
> > this procedure
>
> github is a read-only mirror of repos hosted at the ASF, even the
> Ant/Ivy committers can't directly push there.
>
> https://github.com/apache/ant-ivy-site-styles is a very curious case as
> it claims to mirror a repository that doesn't exist (I wanted to
> manually push the svn files there but fail to find the repository).
>
> It would be good if anybody could ask INFRA in order to figure out what
> exactly the repo is mirroring as I don't see anything matching at
> https://git-wip-us.apache.org/repos/asf - I'll do so myself at the
> weekend, if nobody else finds time before that.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
Re: IvyDE status
Posted by Stefan Bodewig <bo...@apache.org>.
On 2016-12-13, Gintautas Grigelionis wrote:
> 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 would happily push them to Github if I had a permission to
> https://github.com/apache/any-ivy-site-styles, otherwise you may follow
> this procedure
github is a read-only mirror of repos hosted at the ASF, even the
Ant/Ivy committers can't directly push there.
https://github.com/apache/ant-ivy-site-styles is a very curious case as
it claims to mirror a repository that doesn't exist (I wanted to
manually push the svn files there but fail to find the repository).
It would be good if anybody could ask INFRA in order to figure out what
exactly the repo is mirroring as I don't see anything matching at
https://git-wip-us.apache.org/repos/asf - I'll do so myself at the
weekend, if nobody else finds time before that.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: IvyDE status
Posted by Gintautas Grigelionis <g....@gmail.com>.
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 would happily push them to Github if I had a permission to
https://github.com/apache/any-ivy-site-styles, otherwise you may follow
this procedure
> svn log http://svn.apache.org/repos/asf/ant/site/ivyde/sources/style
[note the first commit at the bottom which is 501128]
> git svn clone --no-minimize-url -r501128
http://svn.apache.org/repos/asf/ant/site/ivyde/sources/style
> cd style
> GIT_TRACE=1 git svn fetch --log-window-size 100000
then add Github as remote and push (took me less than 5 minutes on a
MacBook).
Gintas
2016-12-13 17:26 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
> 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 had to be in svn - published via svnpubsub. I think there is an
> alternative git workflow by now, but it won't be feasible to convert
> only part of the site. So it would be all or nothing.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
Re: IvyDE status
Posted by Stefan Bodewig <bo...@apache.org>.
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 had to be in svn - published via svnpubsub. I think there is an
alternative git workflow by now, but it won't be feasible to convert
only part of the site. So it would be all or nothing.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: IvyDE status (Was: VOTE Retire IvyDE)
Posted by Gintautas Grigelionis <g....@gmail.com>.
A short report on status (and more detailed answers to Nicholas questions):
- the doc builds correctly once I clone ant-xooki repository on Github
into doc/xooki;
- the style clone on Github is empty; I did "wget -np -nd -r
https://svn.apache.org/repos/asf/ant/site/ivyde/sources/style/
<https://svn.apache.org/repos/asf/ant/site/ivyde/sources/style/>"
following developer doc, but I cannot find xmlverbatim.css and
background.png in there (both files are referred to by style.css and
print-style.css);
- the Subversion-specific part of packaging is "svn export" which has an
equivalent in Git: "git archive"; fairly straightforward to replace once
the details of the distribution process with Git are clear;
- setting up Eclipse PDE is more tricky nowadays because some components
(notably WTP and GEF) are only released as update sites, which complicates
a fully automated setup.
I have a question, too: perhaps the entire ivyde site repo could be
converted to Git?
Gintas
IvyDE status (Was: VOTE Retire IvyDE)
Posted by Nicolas Lalevée <ni...@hibnet.org>.
I am forking the thread to not pollute the vote.
> Le 7 déc. 2016 à 19:56, Gintautas Grigelionis <g....@gmail.com> a écrit :
>
> I decided to take a quick look at the build process and it's not broken per
> se, rather it's hardcoded to Eclipse SDK 3.7.1 foe Win32.
You confirm the doc is being correctly build ? If that effectively the case, it is good to know, thank you for looking into it.
But one thing is broken for sure: the Ant targets to build IvyDE for the release, because they still assert that the sources are being hosted in subversion.
> I would like to
> make the process to adapt to the build platform. Any suggestions for a
> reasonable Eclipse baseline? Should we target Java 8, that would be 4.5 (or
> maybe even 4.5.2).
Here is what is currently supported:
http://ant.apache.org/ivy/ivyde/history/trunk/compatibility.html <http://ant.apache.org/ivy/ivyde/history/trunk/compatibility.html>
It certainly can be reviewed.
As a general rule I would make IvyDE support the same version of the JVM as Ivy and Eclipse does. A thing to note is that some IvyDE users are installing it in their IBM RAD editor, so it would be nice to continue supporting if it doesn’t require much effort.
Nicolas
Re: VOTE Retire IvyDE
Posted by Gintautas Grigelionis <g....@gmail.com>.
I decided to take a quick look at the build process and it's not broken per
se, rather it's hardcoded to Eclipse SDK 3.7.1 foe Win32. I would like to
make the process to adapt to the build platform. Any suggestions for a
reasonable Eclipse baseline? Should we target Java 8, that would be 4.5 (or
maybe even 4.5.2).
Gintas
Re: VOTE Retire IvyDE
Posted by Nicolas Lalevée <ni...@hibnet.org>.
> Le 7 déc. 2016 à 12:34, Gintautas Grigelionis <g....@gmail.com> a écrit :
>
> I would prefer an agreement on status. IvyDE is dependent on Ivy and
> ideally their release cycles should be synced.
> Since there seem to be some changes brewing in Ivy, IvyDE could be used as
> a test case.
Actually there is no need for synchronization between both project, unless there is a new feature in Ivy required for IvyDE. In the Eclipse updatesite there are two separate « Eclipse features », and one is dedicated to the version of Ivy you want to install.
Nicolas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: VOTE Retire IvyDE
Posted by Gintautas Grigelionis <g....@gmail.com>.
I would prefer an agreement on status. IvyDE is dependent on Ivy and
ideally their release cycles should be synced.
Since there seem to be some changes brewing in Ivy, IvyDE could be used as
a test case.
Gintas
2016-12-07 11:37 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
> On 2016-12-07, Gintautas Grigelionis wrote:
>
> > Somebody mentioned that IvyDE build process is broken and I would like to
> > look into that if it could help to prevent retirement.
>
> That would be wonderful, regardless of whether it prevents retirement.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
Re: VOTE Retire IvyDE
Posted by Stefan Bodewig <bo...@apache.org>.
On 2016-12-07, Gintautas Grigelionis wrote:
> Somebody mentioned that IvyDE build process is broken and I would like to
> look into that if it could help to prevent retirement.
That would be wonderful, regardless of whether it prevents retirement.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: VOTE Retire IvyDE
Posted by Gintautas Grigelionis <g....@gmail.com>.
Somebody mentioned that IvyDE build process is broken and I would like to
look into that if it could help to prevent retirement.
Gintas
2016-12-07 10:00 GMT+01:00 Dominique Devienne <dd...@gmail.com>:
> +1
>
> On Wed, Dec 7, 2016 at 8:41 AM, Jean-Louis Boudart <
> jeanlouis.boudart@gmail.com> wrote:
>
> > +1
> >
> > Le 6 déc. 2016 6:51 PM, "Nicolas Lalevée" <ni...@hibnet.org> a
> > écrit :
> >
> > > +1
> > >
> > > Nicolas
> > >
> > > > Le 6 déc. 2016 à 17:22, Stefan Bodewig <bo...@apache.org> a écrit
> :
> > > >
> > > > On 2016-12-05, Jan Matèrne (jhm) wrote:
> > > >
> > > >> I start a vote for retiring IvyDE.
> > > >
> > > > +0
> > > >
> > > > The discussion in the "Ivy" thread makes me think we'd probably want
> to
> > > > update it with new Ivy releases, even if nothing else changes in
> > > > between.
> > > >
> > > > Stefan
> > > >
> > > > ------------------------------------------------------------
> ---------
> > > > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > > > For additional commands, e-mail: dev-help@ant.apache.org
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > > For additional commands, e-mail: dev-help@ant.apache.org
> > >
> > >
> >
>
Re: VOTE Retire IvyDE
Posted by Dominique Devienne <dd...@gmail.com>.
+1
On Wed, Dec 7, 2016 at 8:41 AM, Jean-Louis Boudart <
jeanlouis.boudart@gmail.com> wrote:
> +1
>
> Le 6 déc. 2016 6:51 PM, "Nicolas Lalevée" <ni...@hibnet.org> a
> écrit :
>
> > +1
> >
> > Nicolas
> >
> > > Le 6 déc. 2016 à 17:22, Stefan Bodewig <bo...@apache.org> a écrit :
> > >
> > > On 2016-12-05, Jan Matèrne (jhm) wrote:
> > >
> > >> I start a vote for retiring IvyDE.
> > >
> > > +0
> > >
> > > The discussion in the "Ivy" thread makes me think we'd probably want to
> > > update it with new Ivy releases, even if nothing else changes in
> > > between.
> > >
> > > Stefan
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > > For additional commands, e-mail: dev-help@ant.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > For additional commands, e-mail: dev-help@ant.apache.org
> >
> >
>
Re: VOTE Retire IvyDE
Posted by Jean-Louis Boudart <je...@gmail.com>.
+1
Le 6 déc. 2016 6:51 PM, "Nicolas Lalevée" <ni...@hibnet.org> a
écrit :
> +1
>
> Nicolas
>
> > Le 6 déc. 2016 à 17:22, Stefan Bodewig <bo...@apache.org> a écrit :
> >
> > On 2016-12-05, Jan Matèrne (jhm) wrote:
> >
> >> I start a vote for retiring IvyDE.
> >
> > +0
> >
> > The discussion in the "Ivy" thread makes me think we'd probably want to
> > update it with new Ivy releases, even if nothing else changes in
> > between.
> >
> > Stefan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > For additional commands, e-mail: dev-help@ant.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
Re: VOTE Retire IvyDE
Posted by Nicolas Lalevée <ni...@hibnet.org>.
+1
Nicolas
> Le 6 déc. 2016 à 17:22, Stefan Bodewig <bo...@apache.org> a écrit :
>
> On 2016-12-05, Jan Matèrne (jhm) wrote:
>
>> I start a vote for retiring IvyDE.
>
> +0
>
> The discussion in the "Ivy" thread makes me think we'd probably want to
> update it with new Ivy releases, even if nothing else changes in
> between.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: VOTE Retire IvyDE
Posted by Stefan Bodewig <bo...@apache.org>.
On 2016-12-05, Jan Matèrne (jhm) wrote:
> I start a vote for retiring IvyDE.
+0
The discussion in the "Ivy" thread makes me think we'd probably want to
update it with new Ivy releases, even if nothing else changes in
between.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org