+1 for not removing Ant support or Ant New project creation.
I personnally still use Ant for my projects
Le 22/04/2021 à 03:40, Owen Thomas a écrit :
> If one wants to create an Ant project from within NetBeans, then one
> should be able to do that.
>
> I've encountered both Maven and Gradle (Gra
You are welcome!
If this is linked from a tutorial you may want:
a) To update the link in the tutorial page (you can modify it in github
using the "edit" button).
b) To upload the sample somewhere (github? gitlab?) and then send a link
to the repository.
By doing so the next person will ha
If one wants to create an Ant project from within NetBeans, then one should
be able to do that.
I've encountered both Maven and Gradle (Gradle when developing for Android
on IntelliJ... another anecdote about frustration), and I can see their use
when one has to manage one's code base against diff
> On Apr 21, 2021, at 2:15 AM, Owen Thomas wrote:
>
> 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 a
Perfect! Thank you.
On 2021/04/21 21:00:55, antonio wrote:
> Yep
>
> http://web.archive.org/web/2012060100*/https://netbeans.org/projects/samples/downloads/download/Samples%2FJava%2FDeploymentTutorial.zip
>
> El 21/4/21 a las 20:16, Peter Ream escribió:
> > I am looking at the netbeans web
Yep
http://web.archive.org/web/2012060100*/https://netbeans.org/projects/samples/downloads/download/Samples%2FJava%2FDeploymentTutorial.zip
El 21/4/21 a las 20:16, Peter Ream escribió:
I am looking at the netbeans website “Java SE Learning Trail”,
specifically “Packaging and Distributing Ja
I am looking at the netbeans website “Java SE Learning Trail”, specifically
“Packaging and Distributing Java Desktop Application.” There is a reference
to “Deployment Tutorial Source Files” :
https://netbeans.org/projects/samples/downloads/download/Samples%252FJava%252FDeploymentTutorial.zip
Does
On Tue, Apr 20, 2021 at 11:43 PM Thomas Kellerer wrote:
> Another +1 for NOT removing Ant support.
>
Nobody is talking about removing Ant support completely.
As far as the "New Project" dialog is concerned:
>
> What about creating a new category "Other" (or maybe even "Legacy") that
> in turn c
On Wed, Apr 21, 2021 at 4:51 AM Sean Carrick wrote:
> You have given a very well thought out answer to my message and I
> appreciate that. Now, let me ask you this: do you maintain legacy systems
> that were built with the Swing Application Framework? If so, were you able
> to convert them to usi
> No, those projects were not left in the lurch by NetBeans dropping
> support for it. Projects were left in the lurch by NetBeans providing
> support for it for too early.
+1
This is all too true. However, it /does/ make a nice, light-weight
library for smaller applications...
No, those projects were not left in the lurch by NetBeans dropping support
for it. Projects were left in the lurch by NetBeans providing support for
it for too early.
Gj
On Wed, Apr 21, 2021 at 2:24 PM Sean Carrick wrote:
> GJ,
>
> I think one of the biggest mistakes in the history of NetBeans
GJ,
> I think one of the biggest mistakes in the history of NetBeans was to
> provide support for the JSR 296 Swing Application Framework (SAF). We
> should have waited until it was no longer a JSR.
With this statement, I could not agree more strongly with you. NB should
have waited to support App
Wayne,
>
> Another issue is that you can't keep it in version control and deploy
> to multiple team members very easily. Minor filesystem differences
> make that sort of thing impossible to do out of the box.
>
This is easily handled in an Ant project when you create the project at
the beginning. I
Hi all,
This message is in violation of the Apache Software Foundation Code of
Conduct.
We expect participants in our community to meet these standards in all
their interactions and to help others to do so as well.
Thanks,
Antonio
[1]
https://www.apache.org/foundation/policies/conduct
On
I have used Netbeans longer than it has been called Netbeans. It has
been remarkably stable and some of my projects rely on its ability to
include other projects. All of the included projects are Ant-based.
Dropping support for Ant probably won't hurt since I can always keep the
existing ver
I think one of the biggest mistakes in the history of NetBeans was to
provide support for the JSR 296 Swing Application Framework (SAF). We
should have waited until it was no longer a JSR. It should only have been
supported in NetBeans once it became part of the JDK. Since it in the end
didn't beco
Will,
You have given a very well thought out answer to my message and I
appreciate that. Now, let me ask you this: do you maintain legacy
systems that were built with the Swing Application Framework? If so,
were you able to convert them to using Maven?
I have a couple of legacy applications that
No, you don't, for the Oracle JS Parser, if you have a problem with that,
it means you're using an old version of NetBeans. Currently that parser is
bundled with NetBeans, so installing it or downloading it separately is not
needed.
Gj
On Wed, Apr 21, 2021 at 1:31 PM Sean Carrick wrote:
> I nee
I need to install the Oracle JS Parser for Netbeans which I cannot
do so because the site - plugins.netbeans.org is down.
You need to go to: https://plugins.netbeans.apache.org/
The netbeans.org site was decommissioned last month...
-SC
Crikey! Looks like I'll have to migrate to Maven then. When in Rome.
On Wed, 21 Apr 2021 at 19:20, John Burgess
wrote:
> +1 also for me to not eliminating Ant support for new (or existing)
> projects.
>
> -Original Message-
> From: Marco Rossi
> Sent: 20 April 2021 20:10
> To: Mitch Cla
+1 also for me to not eliminating Ant support for new (or existing) projects.
-Original Message-
From: Marco Rossi
Sent: 20 April 2021 20:10
To: Mitch Claborn
Cc: users@netbeans.apache.org
Subject: Re: removing the "new project" support for Ant projects
+1 also for me to not eliminating
Speaking of gutter criticism, no more e-mails like this to this mailing
list, Som Lima: we want nothing like this at all here (or anywhere).
Gj
On Wed, 21 Apr 2021 at 11:01, Som Lima wrote:
> I don't know why you bother responding to this kind of gutter criticism.
>
> It is just the way these
Completely agree. Ant works and doesn’t require you to write plugins just to
customise the build process.
From: David
Sent: 20 April 2021 23:04
To: Lisa Ruby ; users@netbeans.apache.org
Subject: Re: removing the "new project" support for Ant projects
+1!
On Tue, 2021-04-20 at 17:10 +, Lis
I don't know why you bother responding to this kind of gutter criticism.
It is just the way these Indians try to impose their "expertise" in IT.
By finding faults. Solutions which is beyond their control.
On Wed, 21 Apr 2021, 09:43 Geertjan Wielenga,
wrote:
> You need to move away from 11
You need to move away from 11.1.
When you do that, this problem will be solved. Ideally, use 12.3, the
latest release.
Gj
On Wed, 21 Apr 2021 at 10:36, Pradyut Bhattacharya
wrote:
> I'm using Netbeans 11.1 and need to a open a JS file in my project.
>
> I need to install the Oracle JS Parser f
I'm using Netbeans 11.1 and need to a open a JS file in my project.I need to install the Oracle JS Parser for Netbeans which I cannot do so because the site - plugins.netbeans.org is down. I'm getting this error - "Networking problem in http://plugins.netbeans.org/nbpluginportal/files/nbms/15523953
Surely the issue with any feature or function or tool is whether there is
sufficient Dev support to fix emerging bugs, properly adapt to latest
versions of Java lang, JFX, JLink etc and answer tricky questions from
users.
If Ant Dev expertise and time is getting harder to find it makes sense to
pl
On Wed, 21 Apr 2021 at 06:32, Sean Carrick wrote:
> Actually, I have always been of the philosophy that "if it ain't broke,
> don't fix it." This seems to be a philosophy lost in today's modern world.
> Your comments show your bias toward always being on the bleeding edge of
> technology. Persona
28 matches
Mail list logo