Re: Ivy - any future or is it also going to be retired?

[Jaikiran Pai]

+1. Nicolas' mail has some precise things that need to be done. I am 
willing to help out wherever possible on those steps. I think the first 
thing to release probably should be a 2.4.1-Beta-1 just to iron out any 
process and other issues in itself and explicitly tag it as a beta so as 
to maintain the right expectations.


One thing that I think is probably is a priority (based on what I have 
been trying to attempt while helping out with Ivy patches) is that we 
have a central system which builds this project and runs the testsuite 
regularly against a *nix and Windows system. Is this already available 
in the project/Ant ecosystem somewhere? Something like a Jenkins? If 
not, is there any other option we have to make sure we really release  
something that is reproducible?


-Jaikiran

On Wednesday 07 December 2016 05:36 PM, Oulds, Jonathan wrote:

Nicolas raises some great ideas,

I would suggest that we get those into Jira and try to cut a release from the 
current code (just to test the release process).  If that works let's try to 
address one or two simple to fix issues (just to give the release some value) 
and push out 2.4.1.

If there is enough interest we can start implementing some bigger features and 
plan for a 2.5 release next year.



Jonathan Oulds
Snr. Software Engineer
McAfee

-Original Message-
From: Stefan Bodewig [mailto:bode...@apache.org]
Sent: Wednesday, December 7, 2016 10:56 AM
To: dev@ant.apache.org
Subject: Re: Ivy - any future or is it also going to be retired?

On 2016-12-06, Nicolas Lalevée wrote:


These are just ideas poping up my mind to show that if people are
enough motivated, they can make things happen. And obviously, if
things work well, credentials will be granted.

Yes, of course.


I think this is the same for IvyDE, but it requires much more effort
because the build is broken since we migrated to git, and so the
release process has to be reviewed. Too much effort for me.

If our transition to git is causing problems we didn't foresee, we can 
certainly (partially) revert it. Nobody says we need to use the same scm for 
all subprojects of Ant.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, 
e-mail: dev-h...@ant.apache.org

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

RE: Ivy - any future or is it also going to be retired?

[Oulds, Jonathan]

Nicolas raises some great ideas,

I would suggest that we get those into Jira and try to cut a release from the 
current code (just to test the release process).  If that works let's try to 
address one or two simple to fix issues (just to give the release some value) 
and push out 2.4.1.

If there is enough interest we can start implementing some bigger features and 
plan for a 2.5 release next year.



Jonathan Oulds
Snr. Software Engineer
McAfee

-Original Message-
From: Stefan Bodewig [mailto:bode...@apache.org] 
Sent: Wednesday, December 7, 2016 10:56 AM
To: dev@ant.apache.org
Subject: Re: Ivy - any future or is it also going to be retired?

On 2016-12-06, Nicolas Lalevée wrote:

> These are just ideas poping up my mind to show that if people are 
> enough motivated, they can make things happen. And obviously, if 
> things work well, credentials will be granted.

Yes, of course.

> I think this is the same for IvyDE, but it requires much more effort 
> because the build is broken since we migrated to git, and so the 
> release process has to be reviewed. Too much effort for me.

If our transition to git is causing problems we didn't foresee, we can 
certainly (partially) revert it. Nobody says we need to use the same scm for 
all subprojects of Ant.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, 
e-mail: dev-h...@ant.apache.org

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - any future or is it also going to be retired?

[Stefan Bodewig]

On 2016-12-06, Nicolas Lalevée wrote:

> These are just ideas poping up my mind to show that if people are
> enough motivated, they can make things happen. And obviously, if
> things work well, credentials will be granted.

Yes, of course.

> I think this is the same for IvyDE, but it requires much more effort
> because the build is broken since we migrated to git, and so the
> release process has to be reviewed. Too much effort for me.

If our transition to git is causing problems we didn't foresee, we can
certainly (partially) revert it. Nobody says we need to use the same scm
for all subprojects of Ant.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - any future or is it also going to be retired?

[Nicolas Lalevée]

> Le 6 déc. 2016 à 17:21, Stefan Bodewig  a écrit :
> 
> On 2016-12-05, Jaikiran Pai wrote:
> 
>> I have been following the latest emails on retiring sub projects in
>> Ant. I just see a proposal to retire IvyDE (the Eclipse plugin) for
>> valid reasons (given the lack of any real activity in there). Given
>> this, I would like to understand what the future of Ivy project itself
>> is. 
> 
> This isn't easy to answer. It looks as if we could manage to gain
> momentum again. Looking at the number of people who responded in this
> thread, there seems to be enough interest of people willing to get their
> hands dirty.
> 
> For now there we don't intend to retire Ivy, but it sure looks pretty
> much asleep.
> 
> Honestly I don't think the problem is that nobody knows how to cut a
> release, this should be automated mostly anyway and would be extremely
> hard to do without access to ASF infrastructure. What we seem to lack is
> people who actually know the Ivy code base and have the time to review
> patches/develop new features.
> 
> Taking myself as an example I have never looked much at Ivy's code and
> have completely ignored all issues over there. My plate is full anyway
> and I wouldn't know how to find the time needed to learn the ins and
> outs. Of course there is a catch here, if we don't manage to apply
> patches we'll never find people who are willing to contribute.
> 
> Ivy may be in use by other projects (I think gradle 3 has moved off of
> Ivy, may be wrong

As far as I can tell, Ivy is still a dependency for dependency management:
https://github.com/gradle/gradle/blob/master/gradle/dependencies.gradle#L41
https://github.com/gradle/gradle/blob/master/subprojects/dependency-management/dependency-management.gradle#L19

Now to answer to globally to the discussion about Ivy’s future, it is indeed 
not bright.

As pointed, the few people who know the code are still around, so it is not 
technically dead. But it needs more than that to continue to be maintained. To 
continue the point made by Stefan, we need people which understand the code, 
but I think more than providing patches. We need people who code but also can 
decide when to cut a release, do some ticket triage, give some time to answer 
to the user mailing list.

We are in a weird state here because the bylaws of Apache still enforce the 
decisions to be taken by people which are not much active. But if some people 
are willing to contribute and make the Ivy project healthy again, I am sure 
some of us will make the effort to make the transition work.

For instance, if somebody here really want a new release of Ivy happen, there 
are a lot of stuff which doesn’t require to be a committer:
- first it will be great to see a summary of what will be in the release, 
explain if it will a bug fix release, or a major release, or if it requires to 
be a release candidate
- maybe there is some jira triage to do, is there any pending patch we've 
missed which could be easily included in the release
- test if the release process is still working, if there is anything to fix (I 
don’t even remember if we have done our first Ivy release while the sources 
being hosted on git).
- we still have trouble to release the doc I think, because there is a mix of 
svn and git. Probably some work to do here, even maybe suggest a better process
- I think building the release artifacts itself doesn’t require much 
credentials, so anybody could provide some

These are just ideas poping up my mind to show that if people are enough 
motivated, they can make things happen. And obviously, if things work well, 
credentials will be granted.

I think this is the same for IvyDE, but it requires much more effort because 
the build is broken since we migrated to git, and so the release process has to 
be reviewed. Too much effort for me. Note though that we have a process to 
reactivate sub projects, so this is not for life (I kind of hope a reborn, this 
is the project which made me an Apache committer!).

Nicolas


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - any future or is it also going to be retired?

[Stefan Bodewig]

On 2016-12-05, Jaikiran Pai wrote:

> I have been following the latest emails on retiring sub projects in
> Ant. I just see a proposal to retire IvyDE (the Eclipse plugin) for
> valid reasons (given the lack of any real activity in there). Given
> this, I would like to understand what the future of Ivy project itself
> is. 

This isn't easy to answer. It looks as if we could manage to gain
momentum again. Looking at the number of people who responded in this
thread, there seems to be enough interest of people willing to get their
hands dirty.

For now there we don't intend to retire Ivy, but it sure looks pretty
much asleep.

Honestly I don't think the problem is that nobody knows how to cut a
release, this should be automated mostly anyway and would be extremely
hard to do without access to ASF infrastructure. What we seem to lack is
people who actually know the Ivy code base and have the time to review
patches/develop new features.

Taking myself as an example I have never looked much at Ivy's code and
have completely ignored all issues over there. My plate is full anyway
and I wouldn't know how to find the time needed to learn the ins and
outs. Of course there is a catch here, if we don't manage to apply
patches we'll never find people who are willing to contribute.

Ivy may be in use by other projects (I think gradle 3 has moved off of
Ivy, may be wrong) but that still shouldn't stop us from retiring it
once we'd find that we aren't able to fix bugs anymore.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - any future or is it also going to be retired?

[Matt Sicker]

I thought Ivy was used extensively by Gradle? I see generated ivy.xml files
after running a normal Gradle build, so it still seems to be important in
that space.

On 5 December 2016 at 08:58, Oulds, Jonathan 
wrote:

> We use Ant + Ivy extensively in our build system.  I too have noticed the
> lack of development within the Ivy project which is why I recently
> re-joined the community.
>
> I would be happy to contribute patches and or ideas for future development
> if the project is to continue.
>
> Please bear in mind when considering the future status of Ivy that the
> ideas that have been developed within this project have been adopted by
> others such as Gradle and Artifactory, as such it would be a shame to see
> the end of such an influential project.
>
>
>
> Jonathan Oulds
> Snr. Software Engineer
> McAfee
>
>
> -Original Message-
> From: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> Sent: Monday, December 5, 2016 12:47 PM
> To: 'Ant Developers List' 
> Subject: AW: Ivy - any future or is it also going to be retired?
>
> > If you want to push Ivy, you need integrations with IDE.
>
> Yes, I agree. But the problem getting developers to improve IvyDE.
>
>
> > IMHO, IvyDE works well with Eclipse;
>
> IvyDE will be available as it is. We don't delete releases as they are
> archived in the Apache archive.
>
>
> > perhaps its [IvyDE] release cycle needs to be synced with Ivy release
> cycle (which is roughly biannual a this point).
>
> Nice idea - but without enough developers impossible.
>
>
> > Is there a release plan for Ivy, by the way?
>
> No.
>
>
> > When will this  fix be
> released?
>
> Marten has commented "it will be fixed in the next release."
> So first step is getting the change into the code base. 2nd step is
> getting a release out.
>
> I don't know the actual status of #1.
> Currently there is no release planed.
>
>
> > I don't know what a -1 (which is what I would have voted) would do in
> reality.
>
> A '-1' is basically a vote 'against' the suggestion [1]. It must be
> explained so that we could react on the arguments privded. Basically a -1
> could be overriden by enough +1s.
>
> If the decision requires consensus, then its called 'veto' and could not
> be overridden.
> But only the removal of a committer or PMC member requires consesus [2].
>
> [1] http://ant.apache.org/bylaws.html#Voting
> [2] http://ant.apache.org/bylaws.html#Actions
>
>
> > So on one hand I want that project to stay (and hope to be actively
> > developed) and on the other I don't think that's going to be happen even
> if it isn't retired.
>
> Same with us. We don't want to retire subprojects. But have to face the
> facts and get the consequences.
>
>
> > Second, I'm guessing the ivy (and ant) project would very much welcome
> extra hands.
> > So if this project is important to you, and you want a release to happen
> ...
> > why don't you join the effort and help drive it.
>
> Thanks, you're right. ;)
>
>
> > If right now the problem is "there is noone able to create / manage new
> releases"
> > (but some people are still around to watch over the code and fix
> > bugs), maybe someone can step up specifically for the job of release
> manager ...
>
> That's the plan, or the intention ;)
>
>
> > Like I said in my mails, I've tried [contributing].
> > Anyway, here's some previous mails where I tried [1] [2] [3].
> > [1] http://marc.info/?l=ant-dev=143702067424412=2
> > [2] http://marc.info/?l=ant-dev=143765756710466=2
> > [3] http://marc.info/?l=ant-dev=144026083515049=2
>
> Maybe we were sleeping some time. But we are waking up.
> #1 was started on 2015-07-16 and a patch was merged on 2015-08-30.
> #2 was started on 2015-07-23 and last response by Nicolas was that it
> breaks on Windows.
> #3 was started on 2015-08-22 and last answer on 2015-08-30.
>
>
> > Me? I can provide patches and fixes and enhancements for whatever
> > little knowledge I gain by looking at existing code, but my experience
> > with Ivy is just limited to the past few years when I started using it
> as a user.
>
> Experience comes naturally by working with and for Ivy. So creating and
> providing patches further.
> With Ant I started with answering user questions on the user-list. Then
> providing some patches.
>
>
> > there's really nothing to look forward to in terms of roadmap or
> releases or development.
>
> I think the problem is that we lost most of the core developers of Ivy in
> a short timeframe.
> So every development/planning stoped. (Just my personal point of view.)
> Now we are trying to reactivate 'old', aquire 'new' committers and getting
> 'existing'
> (Ant)commmiters be more familiar with the Ivy codebase, so that we could
> do more here.
> (Also my personal point of view.)
>
>
>
> Jan
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For 

RE: Ivy - any future or is it also going to be retired?

[Oulds, Jonathan]

We use Ant + Ivy extensively in our build system.  I too have noticed the lack 
of development within the Ivy project which is why I recently re-joined the 
community.

I would be happy to contribute patches and or ideas for future development if 
the project is to continue.

Please bear in mind when considering the future status of Ivy that the ideas 
that have been developed within this project have been adopted by others such 
as Gradle and Artifactory, as such it would be a shame to see the end of such 
an influential project.



Jonathan Oulds
Snr. Software Engineer
McAfee


-Original Message-
From: Jan Matèrne (jhm) [mailto:apa...@materne.de] 
Sent: Monday, December 5, 2016 12:47 PM
To: 'Ant Developers List' 
Subject: AW: Ivy - any future or is it also going to be retired?

> If you want to push Ivy, you need integrations with IDE. 

Yes, I agree. But the problem getting developers to improve IvyDE.


> IMHO, IvyDE works well with Eclipse;

IvyDE will be available as it is. We don't delete releases as they are archived 
in the Apache archive. 


> perhaps its [IvyDE] release cycle needs to be synced with Ivy release cycle 
> (which is roughly biannual a this point).

Nice idea - but without enough developers impossible. 


> Is there a release plan for Ivy, by the way? 

No.


> When will this  fix be 
> released?

Marten has commented "it will be fixed in the next release."
So first step is getting the change into the code base. 2nd step is getting a 
release out.

I don't know the actual status of #1.
Currently there is no release planed. 


> I don't know what a -1 (which is what I would have voted) would do in 
> reality. 

A '-1' is basically a vote 'against' the suggestion [1]. It must be explained 
so that we could react on the arguments privded. Basically a -1 could be 
overriden by enough +1s.

If the decision requires consensus, then its called 'veto' and could not be 
overridden.
But only the removal of a committer or PMC member requires consesus [2].

[1] http://ant.apache.org/bylaws.html#Voting
[2] http://ant.apache.org/bylaws.html#Actions


> So on one hand I want that project to stay (and hope to be actively 
> developed) and on the other I don't think that's going to be happen even if 
> it isn't retired.

Same with us. We don't want to retire subprojects. But have to face the facts 
and get the consequences.


> Second, I'm guessing the ivy (and ant) project would very much welcome extra 
> hands. 
> So if this project is important to you, and you want a release to happen ...
> why don't you join the effort and help drive it.

Thanks, you're right. ;) 


> If right now the problem is "there is noone able to create / manage new 
> releases" 
> (but some people are still around to watch over the code and fix 
> bugs), maybe someone can step up specifically for the job of release manager 
> ...

That's the plan, or the intention ;)


> Like I said in my mails, I've tried [contributing]. 
> Anyway, here's some previous mails where I tried [1] [2] [3].
> [1] http://marc.info/?l=ant-dev=143702067424412=2
> [2] http://marc.info/?l=ant-dev=143765756710466=2
> [3] http://marc.info/?l=ant-dev=144026083515049=2

Maybe we were sleeping some time. But we are waking up. 
#1 was started on 2015-07-16 and a patch was merged on 2015-08-30.
#2 was started on 2015-07-23 and last response by Nicolas was that it breaks on 
Windows.
#3 was started on 2015-08-22 and last answer on 2015-08-30. 


> Me? I can provide patches and fixes and enhancements for whatever 
> little knowledge I gain by looking at existing code, but my experience 
> with Ivy is just limited to the past few years when I started using it as a 
> user.

Experience comes naturally by working with and for Ivy. So creating and 
providing patches further.  
With Ant I started with answering user questions on the user-list. Then 
providing some patches.


> there's really nothing to look forward to in terms of roadmap or releases or 
> development.

I think the problem is that we lost most of the core developers of Ivy in a 
short timeframe.
So every development/planning stoped. (Just my personal point of view.) Now we 
are trying to reactivate 'old', aquire 'new' committers and getting 'existing' 
(Ant)commmiters be more familiar with the Ivy codebase, so that we could do 
more here.
(Also my personal point of view.)



Jan 
  




-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, 
e-mail: dev-h...@ant.apache.org

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of 

Re: Ivy - any future or is it also going to be retired?

[Jaikiran Pai]

On Monday 05 December 2016 04:17 PM, Johan Corveleyn wrote:

An innocent bystander's opinion (I'm not an ivy / ant developer, but
I'm active in the Apache Subversion community): First of all, this is
a volunteer-driven open source project.

I completely understand.


  You're entirely free to use it
or to use something else ... no hard feelings. Second, I'm guessing
the ivy (and ant) project would very much welcome extra hands. So if
this project is important to you, and you want a release to happen ...
why don't you join the effort and help drive it. IMHO, if serious
projects need it, they should also put in serious time, and start
scratching some of their own itches (and, you know, become a
substantial part of the active community you're asking for here).
Like I said in my mails, I've tried. Anyway, here's some previous mails 
where I tried [1] [2] [3].




If right now the problem is "there is noone able to create / manage
new releases" (but some people are still around to watch over the code
and fix bugs), maybe someone can step up specifically for the job of
release manager ...
It's not just that - it's one thing assigning some release manager and 
another to have someone/team who knows the in and outs of the project 
and has a vision for that project and makes relevant design decisions. 
Me? I can provide patches and fixes and enhancements for whatever little 
knowledge I gain by looking at existing code, but my experience with Ivy 
is just limited to the past few years when I started using it as a user.


Overall, I think my concern is not about why there's no activity in Ivy 
project but the fact that it's being advertised as a project which has a 
future, but as someone who's using/trying to use it, there's really 
nothing to look forward to in terms of roadmap or releases or development.



[1] http://marc.info/?l=ant-dev=143702067424412=2
[2] http://marc.info/?l=ant-dev=143765756710466=2
[3] http://marc.info/?l=ant-dev=144026083515049=2

-Jaikiran



-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - any future or is it also going to be retired?

[Johan Corveleyn]

On Mon, Dec 5, 2016 at 11:33 AM, Jaikiran Pai  wrote:
>
>
> On Monday 05 December 2016 03:26 PM, Gintautas Grigelionis wrote:
>>
>> If you want to push Ivy, you need integrations with IDE.
>
>
> +1
>
> I haven't voted in that mail about retiring IvyDE because I don't know what
> a -1 (which is what I would have voted) would do in reality. As noted in
> that other voting thread, the last release was in 2013 and last real code
> was in 2014. So on one hand I want that project to stay (and hope to be
> actively developed) and on the other I don't think that's going to be happen
> even if it isn't retired.
>
>
> Overall, IMO, if Ivy project itself needs to be used in serious projects,
> there needs to be an active community and usable ecosystem around it, headed
> by developers who are able to invest time and interest in it.

An innocent bystander's opinion (I'm not an ivy / ant developer, but
I'm active in the Apache Subversion community): First of all, this is
a volunteer-driven open source project. You're entirely free to use it
or to use something else ... no hard feelings. Second, I'm guessing
the ivy (and ant) project would very much welcome extra hands. So if
this project is important to you, and you want a release to happen ...
why don't you join the effort and help drive it. IMHO, if serious
projects need it, they should also put in serious time, and start
scratching some of their own itches (and, you know, become a
substantial part of the active community you're asking for here).

If right now the problem is "there is noone able to create / manage
new releases" (but some people are still around to watch over the code
and fix bugs), maybe someone can step up specifically for the job of
release manager ...


-- 
Johan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - any future or is it also going to be retired?

[Jaikiran Pai]

On Monday 05 December 2016 03:26 PM, Gintautas Grigelionis wrote:

If you want to push Ivy, you need integrations with IDE.


+1

I haven't voted in that mail about retiring IvyDE because I don't know 
what a -1 (which is what I would have voted) would do in reality. As 
noted in that other voting thread, the last release was in 2013 and last 
real code was in 2014. So on one hand I want that project to stay (and 
hope to be actively developed) and on the other I don't think that's 
going to be happen even if it isn't retired.



Overall, IMO, if Ivy project itself needs to be used in serious 
projects, there needs to be an active community and usable ecosystem 
around it, headed by developers who are able to invest time and interest 
in it.


-Jaikiran



IMHO, IvyDE works
well with Eclipse;
perhaps its release cycle needs to be synced with Ivy release cycle (which
is roughly biannual a this point).
Is there a release plan for Ivy, by the way? When will this
 fix be released?

Gintas

2016-12-05 8:55 GMT+01:00 Jan Matèrne (jhm) :


We see Ivy as a widely used component. We use archiving some components to
recalibrate our focus.
I don't think that we want to archive Ivy in the near future. Instead we
try to push Ivy.

If you want to help with Ivy, you're welcome.

"It's already a challenge to stick with Ivy build system itself given the
lack of fixes/releases/responses."
What are the problems you think are resolved with new Ivy releases?


Jan




-Ursprüngliche Nachricht-
Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
Gesendet: Montag, 5. Dezember 2016 08:26
An: dev@ant.apache.org
Betreff: Ivy - any future or is it also going to be retired?

I have been following the latest emails on retiring sub projects in
Ant.
I just see a proposal to retire IvyDE (the Eclipse plugin) for valid
reasons (given the lack of any real activity in there). Given this, I
would like to understand what the future of Ivy project itself is. I
have asked this more than once previously in the dev mailing list
during the past year or so and any efforts in reviving the project,
which IMO has seen no real activity. I have even tried contacting some
of the dev team members to try and see if I can help in any way to keep
it active.
But unfortunately, that hasn't generated any kind of changes. There's
been no real code changes, bug fixes or any consistent
help/communication when it comes to user issues.

I would like to see some official word on what the future is for Ivy
itself. Is it going to be retired too? Seeing that IvyDE itself is
being proposed for retirement and the only other IDE plugin is a
IntelliJ one (that I know of), asking (some of our internal users) to
continue using Ivy is going to be challenge. It's already a challenge
to stick with Ivy build system itself given the lack of
fixes/releases/responses. If there's an official word on where it
stands in terms of projects goals, we can officially move to a
different build system.

-Jaikiran

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
commands, e-mail: dev-h...@ant.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org





-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - any future or is it also going to be retired?

[Gintautas Grigelionis]

If you want to push Ivy, you need integrations with IDE. IMHO, IvyDE works
well with Eclipse;
perhaps its release cycle needs to be synced with Ivy release cycle (which
is roughly biannual a this point).
Is there a release plan for Ivy, by the way? When will this
 fix be released?

Gintas

2016-12-05 8:55 GMT+01:00 Jan Matèrne (jhm) :

> We see Ivy as a widely used component. We use archiving some components to
> recalibrate our focus.
> I don't think that we want to archive Ivy in the near future. Instead we
> try to push Ivy.
>
> If you want to help with Ivy, you're welcome.
>
> "It's already a challenge to stick with Ivy build system itself given the
> lack of fixes/releases/responses."
> What are the problems you think are resolved with new Ivy releases?
>
>
> Jan
>
>
>
> > -Ursprüngliche Nachricht-
> > Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> > Gesendet: Montag, 5. Dezember 2016 08:26
> > An: dev@ant.apache.org
> > Betreff: Ivy - any future or is it also going to be retired?
> >
> > I have been following the latest emails on retiring sub projects in
> > Ant.
> > I just see a proposal to retire IvyDE (the Eclipse plugin) for valid
> > reasons (given the lack of any real activity in there). Given this, I
> > would like to understand what the future of Ivy project itself is. I
> > have asked this more than once previously in the dev mailing list
> > during the past year or so and any efforts in reviving the project,
> > which IMO has seen no real activity. I have even tried contacting some
> > of the dev team members to try and see if I can help in any way to keep
> > it active.
> > But unfortunately, that hasn't generated any kind of changes. There's
> > been no real code changes, bug fixes or any consistent
> > help/communication when it comes to user issues.
> >
> > I would like to see some official word on what the future is for Ivy
> > itself. Is it going to be retired too? Seeing that IvyDE itself is
> > being proposed for retirement and the only other IDE plugin is a
> > IntelliJ one (that I know of), asking (some of our internal users) to
> > continue using Ivy is going to be challenge. It's already a challenge
> > to stick with Ivy build system itself given the lack of
> > fixes/releases/responses. If there's an official word on where it
> > stands in terms of projects goals, we can officially move to a
> > different build system.
> >
> > -Jaikiran
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
> > commands, e-mail: dev-h...@ant.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>