Hi Eric
On 2023-12-04, Eric Milles wrote:
> It sounds to me like Ivy and IvyDE -- even as a retired subproject -- should
> move out from under Apache Ant. Just for my clarity, is Apache Ivy a
> top-level project or a subproject of Apache Ant?
The top level ASF project here is "Apache Ant"
If this happens I will donate and admin a new MySDK.org website for the ASF
FOSS user group community. I am a major fan of ANT and see IVY and Eclipse
IDE bridge as critical. I will set up an email contact for me tonight at
r...@mysdk.org if you to reach me in the future. Kind regards.
Hello,
I was just made aware of this discussion and thought I would share a bit. We
use Ant+Ivy and Eclipse+IvyDE here (Thomson Reuters) to support dozens of java
projects. IvyDE has been working very well for the past many years and I have
only minor issues with it form time to time. Mostly
Hi Stefan:
Thanks for trying this out.
I can confirm that I was able to just now update my version of the ivy
lib+ant tasks to latest 2.5.2 with Eclipse 2022-03, using the updatesite
you published at the URL you linked in the last message.
However, the updatesite you generated contained only
> Le 19 nov. 2023 à 18:16, Stefan Bodewig a écrit :
>
> On 2023-09-05, Nicolas Lalevée wrote:
>
>> And we tried our best to be opened on how to build and release the
>> plugin and the updatesite, it is documented [2]. On my machine which
>> just have Ant and Java installed, I just tried and
On 2023-09-05, Nicolas Lalevée wrote:
> And we tried our best to be opened on how to build and release the
> plugin and the updatesite, it is documented [2]. On my machine which
> just have Ant and Java installed, I just tried and I have been able to
> build of the updatesite with the last
Hi there,
I used to be involved, especially in IvyDE, and as many, my build tools and my
IDE changed (for the IDE I am glad, not for the build tools…). So I had no
particular interest of doing any maintenance, so much that lost track of the
last releases of Ivy, where I could help. Many many
On 2023-08-28, Cohen, Ross wrote:
> Perhaps someone from the Ant team can poke the Eclipse people and tell
> them that there are devs/teams that will simply move to another IDE
> rather than give up Ant/Ivy/IvyIDE; it might be very much in their
> best interest to put a dev part time on
...@infass.com.INVALID
Sent: Tuesday, August 22, 2023 12:45 PM
To: ivy-u...@ant.apache.org; dev@ant.apache.org
Cc: u...@ant.apache.org
Subject: RE: Future of Ivy and IvyDE
This email originated from outside of the organization. Use caution
when replying, opening attachment(s), and/or clicking
I was a long-time Ant + Ivy and IvyDE. At work, we finally switched one of
our products to Maven. We have at least one other product that still uses
Ant + Ivy, I'm not sure what that team operates as an IDE.
>From my POV, you can't effectively and sanely develop using Ivy *without*
IDE support,
On 2023-08-22, Jason Guild wrote:
> I can confirm that in the not very distant past there were multiple
> people (including myself) who submitted pull requests for Ivy to both
> make improvements as well as address bugs. They were left to rot for
> far too long.
This is unfortunate. In a way
Hi
sorry for my bad timing sending out an email and then being unbale to
answer for days. This is not what I intended.
Let me try to answer what I've seen so far. And I'll try to keep my
personal opinion out this time.
It is pretty obvious Ivy is used today and maybe even loved by
some. This is
ore.
> >
> > So I hope Ivy has a future.
> >
> > Martin
> >
> > -Original Message-
> > From: s.an...@infass.com.INVALID
> > Sent: Tuesday, August 22, 2023 12:45 PM
> > To: ivy-u...@ant.apache.org; dev@ant.apache.org
> > Cc: u...@an
Please read the following in full, as I am starting my argument not at Ivy
itself, but it is still the focus of this response.
I think the core shortcoming of Ant is its inability to bootstrap easily in
a portable manner. You cannot simply use a build file and say 'go build' as
you have to
I agree with what Stefan notes in his mail. Some years back when I
started contributing to Ivy, I realized that the documentation (formal
or informal) related to the internal implementation details of Ivy is
non-existent. Sometimes I had to select a file, go over its commit
history then go
ge-
> From: s.an...@infass.com.INVALID
> Sent: Tuesday, August 22, 2023 12:45 PM
> To: ivy-u...@ant.apache.org; dev@ant.apache.org
> Cc: u...@ant.apache.org
> Subject: [**EXTERNAL**] RE: Future of Ivy and IvyDE
>
> Hi,
>
> I can't really discuss how many
Hi all:
IMO, it would be a shame to lose Ivy as a much simpler alternative to Maven.
It works well and I think there is very much still room for a dependency
management tool that focuses on just that and not all the other things
that Maven does. I am thankful for your work on it, Stefan.
I
Cc: u...@ant.apache.org
Subject: [**EXTERNAL**] RE: Future of Ivy and IvyDE
Hi,
I can't really discuss how many developers use Ivy and how it is difficult to
maintain this project if there is not enough maintainers...
But I can give hints about our usage in our companies:
* We love "ant&q
nt.apache.org; ivy-u...@ant.apache.org
Objet : Future of Ivy and IvyDE
Hi all
before I get to the actual content of this mail:
* I'm cross-posting to three lists but I ask you to keep responses to
dev@ant only (and join the list if necessary) if you want to respond.
* what I write is my personal op
Hi all
before I get to the actual content of this mail:
* I'm cross-posting to three lists but I ask you to keep responses to
dev@ant only (and join the list if necessary) if you want to respond.
* what I write is my personal opinion and not shared by the PMC as a
whole. The people on the
20 matches
Mail list logo
