Another +1 for NOT removing Ant support.
As far as the "New Project" dialog is concerned:
What about creating a new category "Other" (or maybe even "Legacy") that in
turn contains the "Java with Ant" category to make the "Ant option" less
prominent.
Just my 0.02€
Thomas
Marco Rossi schrieb a
I agree with a lot of what has been said:
* Deprecate ANT - New Project (don't remove)
* Keep ANT for existing projects
Also, I agree that Maven can seem quite overwhelming at first. I have
been using it for only about a year now, and still remember the OMG
experience when I first looked at
I think Ant is lovely. Most of my projects only extend the Java SE API. I
don't see the need to change to a build tool that manages third party
libraries unless and until I need to use third party libraries.
Keep supporting Ant and keep the build process as trivial as it needs to be.
On Wed, 21 A
On Tue, Apr 20, 2021 at 9:32 PM Sean Carrick wrote:
> Explain to me, Scott, why I **need** to learn Maven and dump Ant. Ant has
> served me very well all of these years and has never given me one single
> bit of trouble. Speed? Ant is fast enough for me and my projects. Keeping
> libraries "up-to
It is precisely because you want to focus on getting your software
out that you *need* to learn the modern tools for doing so. Your
Gradle project file could literally be one line, depending on your
needs. Maven is certainly more verbose (My preference is Gradle),
but the projec
On what I hope is a lighter note...I recall being in a session at a JavaOne
years ago when a presenter asked if we knew the difference between Ant and
Maven.
The answer was "the guy who created Ant apologized". (Recall that maven
was a bit slow in the early days when it was just getting popular.)
> On Apr 20, 2021, at 1:10 PM, Lisa Ruby wrote:
>
> For those of you who have used Maven for a long time it may seem simple and
> straightforward, but for those of us who haven't it's not. I've struggled to
> try and understand it and figure out how to use it for my software project
> and
I’m not sure why everyone hates ant so much. I know it’s not perfect but what
build tool really is.
If the preference is not to use ant in the future...when is Netbeans going to
formally change from ant to maven? I know some work has been done in the
branches which assume may have involved some
To be honest, I think removing new projects in Ant might be too drastic
a change altogether. From my perspective, a good lot of people that
might still be using old Netbeans and the straightforward Ant support
might not even know Ant IS an actual thing in the IDE, more so that
their projects ju
GJ,
My apologies! It seems I kicked off more than I expected with my
comments. Feel free to slap me if you ever see me...
-SC
On 4/20/21 2:33 PM, Geertjan Wielenga wrote:
> No one is suggesting removing support for Ant altogether.
>
> The suggestion is to remove the possibility of creating new A
+1!
On Tue, 2021-04-20 at 17:10 +, Lisa Ruby wrote:
>
> For those of you who have used Maven for a long time it may seem
> simple and straightforward, but for those of us who haven't it's
> not. I've struggled to try and understand it and figure out how
> to
> use it for my so
-- Forwarded message -
From: Mail Delivery Subsystem
Date: Tue, Apr 20, 2021 at 1:33 PM
Subject: Delivery Status Notification (Failure)
To:
[image: Error Icon]
Address not found
Your message wasn't delivered to *geertjan.wiele...@googlemail.com.invalid*
because the domain google
A compromise could be just to have Ant projects marked as depricated and to
have a working alternative.
Wayne
On Tue, 20 Apr 2021 at 21:33, Geertjan Wielenga
wrote:
> No one is suggesting removing support for Ant altogether.
>
> The suggestion is to remove the possibility of creating new Ant pr
No one is suggesting removing support for Ant altogether.
The suggestion is to remove the possibility of creating new Ant projects.
Gj
On Tue, 20 Apr 2021 at 21:32, Thomas Wolf wrote:
> +1 for not removing ant support for me as well. I’m admittedly an
> old-timer. My first exposure to a ‘mod
+1 for not removing ant support for me as well. I’m admittedly an
old-timer. My first exposure to a ‘modern’ build tool was on my last job -
the company used gradle. With a background in make and ant, I found its
syntax hard to grok.NB devs clearly like Maven - its syntax seems
straight-for
Another +1 for me to not eliminating Ant support for new and existing
programs. Ant works perfectly well for all my projects too.
Bayless Kirtley
On 4/20/21 2:10 PM, Marco Rossi wrote:
+1 also for me to not eliminating Ant support for new (or existing) projects.
Mark Reds
Il giorno 20 apr
+1 also for me to not eliminating Ant support for new (or existing) projects.
Mark Reds
> Il giorno 20 apr 2021, alle ore 20:08, Mitch Claborn
> ha scritto:
>
> +1 for not eliminating Ant support for new (or existing) projects. We've been
> using Ant for a long time, and it still works just f
I develop small projects and prototypes. I was considering migrating to
Gradle when the time comes to retire Ant support.
I have managed to get OpenJFX and linker working well enough under Ant. It
helps that I was used to object linking in the 1980's on DEC PDP11s.
Personally, I find Maven over
I have an ant-based NB platform application, moving to Maven is on my to-do
list, but I know nothing about Maven. Some time ago I tried to find relevant
help but I just found generic "move to maven" infos, so I gave up.
> That said, perhaps we could get a write up on someone going through the
On Tue, Apr 20, 2021 at 10:10 AM Lisa Ruby
wrote:
> For those of you who have used Maven for a long time it may seem simple
> and straightforward, but for those of us who haven't it's not. I've
> struggled to try and understand it and figure out how to use it for my
> software project and gave up
+1 for not eliminating Ant support for new (or existing) projects. We've
been using Ant for a long time, and it still works just fine for us, so
there is no payback in converting to Maven.
Mitch
On 4/20/21 12:10 PM, Lisa Ruby wrote:
For those of you who have used Maven for a long time it may
For those of you who have used Maven for a long time it may seem simple and
straightforward, but for those of us who haven't it's not. I've struggled to
try and understand it and figure out how to use it for my software project and
gave up. And it's a huge amount of overhead, extra disk space us
GJ,
While I get where you are coming from, there are still a bunch of legacy
applications out there built on the AppFramework, which I do not believe
will be able to be converted to Maven. People are still using NB <= 8.2
simply for the AppFramework IDE integration to maintain those legacy
applica
I agree, the Ant-based project creation should be removed and I disagree
that there should be any kind of conversion between Ant and Maven -- that
simply will never work and we'll spend the rest of our days fixing bugs in
that. To convert from Ant to Maven: create a new Maven project and copy the
J
Honestly, I think NB should have an internal conversation about removing
the "new project" support for Ant projects, while still being able to
open existing ones. It just confuses a lot of people if they're not
going to be supported.
I agree, if and ONLY if you provide at least a rudimentary way t
On Mon, Apr 19, 2021 at 12:55 AM Wayne Gemmell | Connect <
wa...@connect-mobile.co.za> wrote:
> Is the perception that nobody does Maven EAR's anymore or that nobody uses
> EARs? I have a web app that has given me no shortage of issuse with ant.
> I'm trying to move it to Maven. If nobody is using
26 matches
Mail list logo
