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

[Maarten Coene]

Thanks Jaikiran! :-)
I'll try to review it ...
kind regards,Maarten

  Van: Jaikiran Pai 
 Aan: dev@ant.apache.org 
 Verzonden: woensdag 7 december 18:17 2016
 Onderwerp: Re: AW: Ivy - any future or is it also going to be retired?
   
Thank you. Given that there does seem to be willingness to do something 
to move things forward with the project, I have now submitted a PR for 
one of the open JIRAs https://github.com/apache/ant-ivy/pull/10 in an 
attempt to fix it.

Over the weekend, I'll see if I can come up with a list of JIRAs which 
might be worth to be included in the proposed release (whenever next it 
happens). Of course, someone who has more knowledge about the project 
can do this and I'll happily step aside from that task.

-Jaikiran

On Wednesday 07 December 2016 08:41 PM, Jan Matèrne (jhm) wrote:
>> 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?
> Apache hosts a Jenkins instance with several slaves we could use.
> We already have some Ivy jobs:
>
> https://builds.apache.org/view/All/job/Ivy/
> Build Ivy on Ubuntu
> JDK 1.6, Ubuntu
> git: Recursively update submodules
> runs: @hourly
> run: Ant (latest)
> Target: clean jar sources
> archive: build/artifact/**
>
>
> https://builds.apache.org/view/All/job/Ivy-check/
> Checks of the Ivy codebase: Findbugs, RAT - Release Auditing Tool, Checkstyle
> JDK 1.6, Ubuntu
> git: clean before checkout
> run: seems to be just run manually
> run-1: Ant (latest): findbugs checkstyle-internal
> run-2: Ant (latest): rat
> check for TODOs
>
> https://builds.apache.org/view/All/job/Ivy-tests/
> seems to be a "test-job" of mine ...
> git: clean before checkout, Recursively update submodules
> matrix: (atm only JDK1.5)
>
> https://builds.apache.org/view/All/job/Ivy-tests-matrix/
> run tests
> triggerd by stable "Ivy" job
> git: clean before checkout, Recursively update submodulesrun: Ant(latest): 
> clean test-report
>
>
>
> Jan
>
>
>
> -
> 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: AW: Ivy - any future or is it also going to be retired?

[Jaikiran Pai]

Thank you. Given that there does seem to be willingness to do something 
to move things forward with the project, I have now submitted a PR for 
one of the open JIRAs https://github.com/apache/ant-ivy/pull/10 in an 
attempt to fix it.


Over the weekend, I'll see if I can come up with a list of JIRAs which 
might be worth to be included in the proposed release (whenever next it 
happens). Of course, someone who has more knowledge about the project 
can do this and I'll happily step aside from that task.


-Jaikiran

On Wednesday 07 December 2016 08:41 PM, Jan Matèrne (jhm) wrote:

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?

Apache hosts a Jenkins instance with several slaves we could use.
We already have some Ivy jobs:

https://builds.apache.org/view/All/job/Ivy/
Build Ivy on Ubuntu
JDK 1.6, Ubuntu
git: Recursively update submodules
runs: @hourly
run: Ant (latest)
Target: clean jar sources
archive: build/artifact/**


https://builds.apache.org/view/All/job/Ivy-check/
Checks of the Ivy codebase: Findbugs, RAT - Release Auditing Tool, Checkstyle
JDK 1.6, Ubuntu
git: clean before checkout
run: seems to be just run manually
run-1: Ant (latest): findbugs checkstyle-internal
run-2: Ant (latest): rat
check for TODOs

https://builds.apache.org/view/All/job/Ivy-tests/
seems to be a "test-job" of mine ...
git: clean before checkout, Recursively update submodules
matrix: (atm only JDK1.5)

https://builds.apache.org/view/All/job/Ivy-tests-matrix/
run tests
triggerd by stable "Ivy" job
git: clean before checkout, Recursively update submodulesrun: Ant(latest): 
clean test-report



Jan



-
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

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

[jhm]

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

Apache hosts a Jenkins instance with several slaves we could use.
We already have some Ivy jobs:

https://builds.apache.org/view/All/job/Ivy/
Build Ivy on Ubuntu
JDK 1.6, Ubuntu
git: Recursively update submodules
runs: @hourly
run: Ant (latest) 
Target: clean jar sources
archive: build/artifact/**


https://builds.apache.org/view/All/job/Ivy-check/
Checks of the Ivy codebase: Findbugs, RAT - Release Auditing Tool, Checkstyle
JDK 1.6, Ubuntu
git: clean before checkout
run: seems to be just run manually
run-1: Ant (latest): findbugs checkstyle-internal
run-2: Ant (latest): rat
check for TODOs

https://builds.apache.org/view/All/job/Ivy-tests/
seems to be a "test-job" of mine ...
git: clean before checkout, Recursively update submodules
matrix: (atm only JDK1.5)

https://builds.apache.org/view/All/job/Ivy-tests-matrix/
run tests
triggerd by stable "Ivy" job
git: clean before checkout, Recursively update submodulesrun: Ant(latest): 
clean test-report



Jan



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

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

[jhm]

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

I don't know.
But haven't thought to retire Ivy itself.


Jan


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

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

[jhm]

> 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

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

[Jaikiran Pai]

On Monday 05 December 2016 01:25 PM, Jan Matèrne (jhm) wrote:

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.
I have tried more than once (in this very own mailing list), but without 
someone who "owns" the project and has the time and dedication to 
develop and release the project, the questions/efforts have gone no where.



"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?
Right now I don't have specific bugs that are open that impact me or the 
project I use. I do have some enhancements that I would like to be done. 
But the real issue I have with the Ivy project is, its development has 
practically gone stagnant. I have been watching the JIRA reports (there 
are some open issue for over a year which are big ones) and have been 
watching the mailing list and based on that, my opinion is that Ivy is 
no longer being developed. When there's no community around a project 
and the fact that there have been no releases (last one was 2 years back 
http://ant.apache.org/ivy/history/2.4.0/release-notes.html) for a while 
or any indication that there will be one anytime, it's hard to 
rationalize using that project (as critical as a build system).


I can understand that projects have a lifetime and it's reasonable to 
expect that after a certain period it may no longer be feasible to put 
in efforts into it. I don't know if that's the case with Ivy. But every 
time I ask about the roadmap/future, the answer seems to suggest that it 
does have a future. However, with more than a year since I last asked 
this question (in this mailing list) and with no real development or 
releases during that period, I don't believe that's the case.


-Jaikiran



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

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

[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