en Java and Java Ant.
Cheers
Chris
Von: Neil C Smith
Gesendet: Montag, 26. November 2018 14:52
An: dev@netbeans.incubator.apache.org
Betreff: Re: NetBeans - the UI for Maven
On Sun, 25 Nov 2018 at 20:53, Tim Boudreau wrote:
> Ther
This is what I meant, I would prefer also to have Java Maven or smth with Maven
and Java Ant otherwise than only haven Java and Java Ant.
Cheers
Chris
Von: Neil C Smith
Gesendet: Montag, 26. November 2018 14:52
An: dev@netbeans.incubator.apache.org
Betreff: Re: NetBeans - the UI for Maven
On Sun, 25 Nov 2018 at 20:53, Tim Boudreau wrote:
> There's a UI principle Joel Spolsky expounded years ago: Never force the
> user into a choice they don't care about.
Not sure if that was meant as a direct reply to me or not, but I
completely agree with that ...
> A lot of users of NetBeans a
here
NetBeans Modules could be a Sub category too or separated from them.
Cheers
Chris
Von: Anton Epple
Gesendet: Montag, 26. November 2018 12:13
An: dev@netbeans.incubator.apache.org
Betreff: AW: NetBeans - the UI for Maven
Done, I updated the PR:
https://github.com/apache/incubator
atch?v=AbSehcT19u0
>
>
>
> -Ursprüngliche Nachricht-
> Von: Emilian Bold
> Gesendet: Sonntag, 25. November 2018 18:53
> An: NetBeans Dev@
> Betreff: Re: NetBeans - the UI for Maven
>
> I d
t
my
> changes before any user has seen them. If we don't find the time, or
cannot
> find a solution, then at least we've fixed the initial problem.
>
> --Toni
>
> [1] https://www.youtube.com/watch?v=AbSehcT19u0
>
>
>
>
this is great, and it will wipe out my
> changes before any user has seen them. If we don't find the time, or cannot
> find a solution, then at least we've fixed the initial problem.
>
> --Toni
>
> [1] https://www.youtube.com/watch?v=AbSehcT19u0
>
>
>
> -
] https://www.youtube.com/watch?v=AbSehcT19u0
-Ursprüngliche Nachricht-
Von: Emilian Bold
Gesendet: Sonntag, 25. November 2018 18:53
An: NetBeans Dev@
Betreff: Re: NetBeans - the UI for Maven
I don't think there's any kind of rush to have a PR today.
I like Geertjan
On Sun, Nov 25, 2018 at 4:59 PM Geertjan Wielenga
wrote:
> >
> > A lot of users of NetBeans are new to Java or new to programming
> > altogether.
> >
>
> And a lot of users of NetBeans aren't.
Yes, but those users aren't harmed by a simple default workflow, while
newbies are.
-Tim
>
> Gj
>
>
+1 to making Maven the default.
I agree that we should not force users to choose between Maven or Ant when
creating a new project. Just make Maven the default and allow the user the
ability to change to Ant, if desired.
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://w
I think a preference for the default tool would make sense. Or even if it just
remembered your last selection so you don’t have to keep changing it. The
initial default should be Maven at this point, but maybe it could be Gradle if
it ever becomes a first class citizen.
I also agree with Tim
On Sat, 24 Nov 2018 17:02:02 +0100, Martin Desruisseaux
wrote:
Le 24/11/2018 à 16:39, Robert Scholte a écrit :
**If And Only If** you want to make use of single tool invocation for
all you JPMS modules, then you cannot use Maven, it's architecture
doesn't support it and any plugin trying to
>
> A lot of users of NetBeans are new to Java or new to programming
> altogether.
>
And a lot of users of NetBeans aren't.
Gj
On Sun, Nov 25, 2018 at 9:53 PM Tim Boudreau wrote:
> There's a UI principle Joel Spolsky expounded years ago: Never force the
> user into a choice they don't care a
ssage-
From: Jaroslav Tulach
Sent: November 24, 2018 2:54 AM
To: dev@netbeans.incubator.apache.org
Cc: us...@maven.apache.org
Subject: NetBeans - the UI for Maven
Hi guys,
the Apache NetBeans release 10 is (almost) finished and ready for download.
Time to look forward: Long live Apache NetBeans - t
There's a UI principle Joel Spolsky expounded years ago: Never force the
user into a choice they don't care about.
A lot of users of NetBeans are new to Java or new to programming
altogether. They don't know what Ant, Maven or Gradle are, and won't
understand what they are for a long time.
We ow
Hi,
On Sun, 25 Nov 2018 at 17:48, wrote:
> Java Application:
>- Maven based
> - ANT based
>
> This doesn't really move ANT out of sight, and is only slightly better
> than what we have now. It also adds one more click to the wizard.
That's not quite what I envisaged by using the hierar
lot more effort. That's why for now I proposed
> this simple PR which also does the job to change the default Java build
> tool in project wizards from ANT to Maven.
>
>
>
> -Ursprüngliche Nachricht-----
> Von: Neil C Smith
> Gesendet: Sonntag, 25. November 2018 15
the job to change the default Java build tool in project
wizards from ANT to Maven.
-Ursprüngliche Nachricht-
Von: Neil C Smith
Gesendet: Sonntag, 25. November 2018 15:47
An: dev@netbeans.incubator.apache.org
Betreff: Re: NetBeans - the UI for Maven
On Sun, 25 Nov 2018, 14:14 A
Ok, the screenshots are here:
https://github.com/apache/incubator-netbeans/pull/1038
Am 25.11.18, 15:28 schrieb "Oliver Rettig" :
Should'nt it be the same with
Netbeans Platform App?
The wizzard for a maven based Platform app wizzard can be found in the
"Maven" folder
On Sun, 25 Nov 2018, 14:14 Anton Epple Putting all ANT related stuff in its own category has the benefit of
> moving it out of focus, while still keeping it around for those who need
> it.
>
A sub-category could do that too? Been doing that myself recently. Don't
disagree with your point or appro
OK, apparently attachements don't work here... Will upload them to the PR
Am 25.11.18, 15:39 schrieb "Anton Epple" :
Like this (see attached pic)?
Am 25.11.18, 15:28 schrieb "Oliver Rettig" :
Should'nt it be the same with
Netbeans Platform App?
For clarity, also a screenshot of the new "Java" (formerly "Maven") category.
Am 25.11.18, 15:37 schrieb "Anton Epple" :
Like this (see attached pic)?
Am 25.11.18, 15:28 schrieb "Oliver Rettig" :
Should'nt it be the same with
Netbeans Platform App?
Like this (see attached pic)?
Am 25.11.18, 15:28 schrieb "Oliver Rettig" :
Should'nt it be the same with
Netbeans Platform App?
The wizzard for a maven based Platform app wizzard can be found in the
"Maven" folder but
the ant-based Platform app wizzard is in the fol
Should'nt it be the same with
Netbeans Platform App?
The wizzard for a maven based Platform app wizzard can be found in the "Maven"
folder but
the ant-based Platform app wizzard is in the folder "Netbeans Modules".
But I am not sure what should be the default. I feel better with the ant-base
Putting all ANT related stuff in its own category has the benefit of moving it
out of focus, while still keeping it around for those who need it.
--Toni
Am 25.11.18, 14:55 schrieb "Neil C Smith" :
On Sun, 25 Nov 2018, 13:19 Anton Epple I agree that additional/more complex changes, as di
On Sun, 25 Nov 2018, 13:19 Anton Epple I agree that additional/more complex changes, as discussed by Chris and
> Geertjan, make sense in the longer term, but probably require further
> discussion. For now, this is a simple change (mostly branding) which solves
> the basic issue.
>
Well, a simpler
Hi,
I created a PR which does the changes proposed initially:
https://github.com/apache/incubator-netbeans/pull/1038
It changes category "Java" to contain the Maven projects and introduces a new
category "Ant(ic) Java" with former "Java" projects and subcategories "JavaFX"
and "NetBeans Module
I think I agree with Chris -- if we're going to make a change here, let's
do it completely: IMHO there should be a single wizard named "Java SE
Application" and a single wizard named "Java Web Applicaton", both of
which, in step two or three, should let the user choose whether they want
to build th
On Sun, 25 Nov 2018, 02:13 Scott Palmer Gradle is the way forward and so much better.
I can think of a few people on here who'll probably disagree with you! ;-)
Personally I'm not that keen either, even though that link makes some valid
points.
But +1 for Gradle being a first-class citizen if
Ant and Maven projects are dead to me :-)
Gradle is the way forward and so much better. (Plus it could support native
C/C++ as well.)
I know Maven is an Apache project, but quite frankly I agree 100% with this:
http://nealford.com/memeagora/2013/01/22/why_everyone_eventually_hates_maven.html
, can be choosen on
the next steps“.
Cheers
Chris
Von: Christian Lenz
Gesendet: Samstag, 24. November 2018 19:25
An: dev@netbeans.incubator.apache.org
Betreff: AW: NetBeans - the UI for Maven
+1 from my side too for chaning the UI of the Project wizard, but, please give
it not only the Name
*
Cheers
Chris
Von: Martin Desruisseaux
Gesendet: Samstag, 24. November 2018 17:02
An: Robert Scholte; Maven Users List; Jaroslav Tulach;
dev@netbeans.incubator.apache.org
Betreff: Re: NetBeans - the UI for Maven
Le 24/11/2018 à 16:39, Robert Scholte a écrit :
> **If And Only If** you want
Le 24/11/2018 à 16:39, Robert Scholte a écrit :
> **If And Only If** you want to make use of single tool invocation for
> all you JPMS modules, then you cannot use Maven, it's architecture
> doesn't support it and any plugin trying to solve this is a hack.
>
But isn't what you are going to do for
Sounds good to me. I would also suggest that the Gradle plugin should be
part of the base IDE.
I don't thin Maven in classroom is an issue. In ANT they need to download
dependencies as well. In those cases they can install locally from the
provided ones.
On Sat, Nov 24, 2018, 9:44 AM Robert Schol
On Sat, 24 Nov 2018 15:34:51 +0100, Martin Desruisseaux
wrote:
Le 24/11/2018 à 15:10, Robert Scholte a écrit :
Today I started looking at MJAVADOC-449 again and it seems that just
nobody took serious time to solve this. I've been able to create the
proper commandline by moving some classpat
Le 24/11/2018 à 15:10, Robert Scholte a écrit :
> Today I started looking at MJAVADOC-449 again and it seems that just
> nobody took serious time to solve this. I've been able to create the
> proper commandline by moving some classpath entries to the modulepath.
> Now it is a matter of implementin
On Sat, 24 Nov 2018 15:02:08 +0100, Martin Desruisseaux
wrote:
Le 24/11/2018 à 13:53, Robert Scholte a écrit :
With the Java Platform Modular System you'll clearly see different
requirements between library and application developers.
Indeed (e.g. jlink is for application developers), but
Le 24/11/2018 à 13:53, Robert Scholte a écrit :
> With the Java Platform Modular System you'll clearly see different
> requirements between library and application developers.
>
Indeed (e.g. jlink is for application developers), but the requirements
I'm talking about are for library developers.
Le 24/11/2018 à 13:28, Martin Desruisseaux a écrit :
> The key part is "--module-path".
Sorry I mean "--module-source-path" for the compilation and javadoc
generation parts. Likewise I mean "--source-path" instead of
"--classpath" for compilation with pre-jigsaw options.
Martin
---
+1 Agree totally
If you can set some tasks for us to help, would be great. I have developed
some internal plugins but would love to put my grain of salt into this
effort.
El sáb., 24 de nov. de 2018 1:53 a. m., Jaroslav Tulach <
jaroslav.tul...@gmail.com> escribió:
> Hi guys,
> the Apache NetBean
On Sat, 24 Nov 2018 13:28:28 +0100, Martin Desruisseaux
wrote:
Hello Robert
Thanks for your reply.
Le 24/11/2018 à 12:36, Robert Scholte a écrit :
Let me correct this part: there is *no* need to change the folder
structure to work with the Java Platform Modular System. The only
thing you
Hello Jan
Le 24/11/2018 à 12:12, Jan Lahoda a écrit :
> FWIW, there is StandardJavaFileManager.setLocationForModule:
> https://docs.oracle.com/javase/10/docs/api/javax/tools/StandardJavaFileManager.html#setLocationForModule(javax.tools.JavaFileManager.Location,java.lang.String,java.util.Collectio
Hello Enrico
Le 24/11/2018 à 12:13, Enrico Olivelli a écrit :
> Have you already shared your thoughts and needs with Apache Maven group ?
>
Yes, on the mailing list. My feeling is that in order to be convincing,
I need to create a prototype showing the feasibility of my proposal.
This is the inte
Hello Robert
Thanks for your reply.
Le 24/11/2018 à 12:36, Robert Scholte a écrit :
> Let me correct this part: there is *no* need to change the folder
> structure to work with the Java Platform Modular System. The only
> thing you need to do is add a module-info.java to src/main/java and
> ensu
On Sat, 24 Nov 2018 11:29:11 +0100, Martin Desruisseaux
wrote:
I think differently. In Apache SIS for example, we maintain both a Maven
and Ant project. The root source code directory is a classical Maven
project with pom.xml file [1], but we also maintain a sub-directory with
NetBeans Ant pr
+1 on the default project being Maven and not Ant based.
> Finally, I would really vote to make the move from Ant to Maven to build
> Netbeans itself. We then no longer need no use and maintain the
> nam-repository-plugin.
I've also been using more Maven than Ant for NetBeans modules but I
don'
+1 I like this idea of making Maven the default.
I'd also like to see if we could being Gradle support into the IDE by
default as well. I know its worked on as a plugin but I think bringing it
into the standard distribution would be a nice plus to have in the IDE as
well.
Regards
John
On Sat,
Martin,
Il sab 24 nov 2018, 11:29 Martin Desruisseaux <
martin.desruisse...@geomatys.com> ha scritto:
> I think differently. In Apache SIS for example, we maintain both a Maven
> and Ant project. The root source code directory is a classical Maven
> project with pom.xml file [1], but we also main
Hi Martin,
I appreciate that your are using NetBeans - thanks for that!
But, as I understand Jarsolav's proposal, it only proposes to change the
presentation in the "New Project" dialog, so that the (more standard) Maven
projects would be ordered in front of/above the Ant projects. Users would
st
I think differently. In Apache SIS for example, we maintain both a Maven
and Ant project. The root source code directory is a classical Maven
project with pom.xml file [1], but we also maintain a sub-directory with
NetBeans Ant project configuration [2]. The official project
configuration is the Ma
Hi all,
I fuly agree, Ant projects are dead for me. I only use NB Maven projects since
several years now and even if in the beginning the transition was not always
easy when it came to customs builds, now you can do everything you need with
Maven projects as you could with Ant AFAIK.
However,
+1
But also think about users without Internet connection (needed for maven)
when used in a classroom for example
Le sam. 24 nov. 2018 à 09:53, Jaroslav Tulach a
écrit :
> Hi guys,
> the Apache NetBeans release 10 is (almost) finished and ready for
> download.
> Time to look forward: Long live
+1
Am 24.11.18, 08:55 schrieb "Jaroslav Tulach" :
Hi guys,
the Apache NetBeans release 10 is (almost) finished and ready for download.
Time to look forward: Long live Apache NetBeans - the UI for Apache Maven!
NetBeans is known for its excellent Maven support. Time to bring
Great idea.
On Sat, Nov 24, 2018, 11:53 AM Jaroslav Tulach Hi guys,
> the Apache NetBeans release 10 is (almost) finished and ready for
> download.
> Time to look forward: Long live Apache NetBeans - the UI for Apache Maven!
>
> NetBeans is known for its excellent Maven support. Time to bring it
Hi guys,
the Apache NetBeans release 10 is (almost) finished and ready for download.
Time to look forward: Long live Apache NetBeans - the UI for Apache Maven!
NetBeans is known for its excellent Maven support. Time to bring it to new
level - time to lead all NetBeans newbies directly into Maven
55 matches
Mail list logo
