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
Dne sobota 24. listopadu 2018 19:52:02 CET, Matthias Bläsing napsal(a):
> Hi,
>
> Am Samstag, den 24.11.2018, 10:35 -0800 schrieb Laszlo Kishalmi:
> > Hi all PR-973 broke HTML5, PHP. Going to revert the patch from
> > release100
>
> please wait and give Svatopluk some time to react - else I see t
I noticed that in my 82 maven based platform application the Intent API is
available for deactivation and uninstallation. Doing so will render the
application useless since there are dependencies for the Intent API.
I have created a sample project available at
https://github.com/trixon/netbeans-in
Thanks, both of you.
Don't know if "working with NB sources" is described anywhere else than
here:
https://netbeans.apache.org/participate/build-run-debug-tutorials.html but
that one for sure need an update. As a short term solution just put a note
on the page.
Here's a PR for that:
https://gith
Hi,
Am Samstag, den 24.11.2018, 10:35 -0800 schrieb Laszlo Kishalmi:
> Hi all PR-973 broke HTML5, PHP. Going to revert the patch from
> release100
please wait and give Svatopluk some time to react - else I see the next
one voting -1 because the old Javascript parser is bundled (with GPLv2-
CPE li
To add smth more here, it could be the same for PHP. In General you choose PHP
and on the later steps you choose the Framework like Doctrine or WordPress or
whatever. So this could be the same for Java Description could be: „Create Java
applications with your favorite Tools. Ant, Maven, Gradle,
Hi all PR-973 broke HTML5, PHP. Going to revert the patch from release100
On 11/22/18 10:51 PM, Geertjan Wielenga wrote:
Hi all,
From the discussions over the last day or two, it seems we need to put
together 10-vc5.
AFAIK, the issues that need to be addressed in 10-vc5 are:
1. nb-javac inst
>
> From within NB IDE 8.2
>
There's your problem. Use Apache NetBeans 9 or higher.
Gj
On Sat, Nov 24, 2018 at 7:14 PM Matthias Bläsing
wrote:
> Hey Lars,
>
> the NetBeans top-level directory layout was incompatibility changed.
> Before the change all modules were at the top-level directory, a
+1 from my side too for chaning the UI of the Project wizard, but, please give
it not only the Name Java, say Java Maven instead. Not only Java and Java Ant.
A lot of People who wants to start programming with Java they probably heard of
Ant and Maven, Maybe gradle etc. and Maybe of pom, but oft
Hey Lars,
the NetBeans top-level directory layout was incompatibility changed.
Before the change all modules were at the top-level directory, after
the change, the modules were moved into a per-cluster directory.
You need NetBeans 9 to open the modules.
HTH
Matthias
Am Samstag, den 24.11.2018,
I'm an infrequent contributor to Apache NetBeans. It has been a while,
about 9 months, and I realize I no longer know how to open a specific
NetBeans module and work on that.
Here's what I do:
1. Clone Apache NetBeans from GitHub
2. Run "ant" from the root of the clone. It takes some 10 minutes t
Yes, corrupted class file bugs (Absent Code attribute, Duplicate method name
etc.) was the one major problem for me going from NetBeans 8.2 to 9.0.
> I'd try to make a fix, but this is one of those bugs that involves an
> interaction between several far-flung components (maven project plugin,
>
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
34 matches
Mail list logo
