Well done. This is a huge undertaking and mass effort to make this happen.
> On 17 Feb 2018, at 01:35, Geertjan Wielenga
> wrote:
>
> The Apache NetBeans team is proud to announce the release of Apache
> NetBeans (incubating) 9.0 Beta.
>
> Apache NetBeans (incubating) 9.0 Beta constitutes all
The Apache NetBeans team is proud to announce the release of Apache
NetBeans (incubating) 9.0 Beta.
Apache NetBeans (incubating) 9.0 Beta constitutes all the modules in
the Apache NetBeans Git repo, which together provide the NetBeans
Platform (i.e., the underlying application framework), which wa
Such a positive reply email!
I don't have much experience in the Compile on Save / Maven area but I'll try
in the coming weeks, when I get some spare time, to look into it.
Thanks for reporting the issue.
--emi
Original Message
On 15 February 2018 10:30 PM, Mátyás Bene wro
Try to create a small reproducible suite with this problem.
In theory what you did is correct and you don't have a duplicate of
commons-configuration but it's hard to debug this over email with partial info.
Also try looking at the actual build output JARs that you have, I'm not
entirely certai
Hi,
Yes that is what I think too.
I changed my architecture since I posted my issue.
I still have the issue but I think the best is to explain the module hierarchy :
- I have module A (netbeans module)
- the module A has a maven dependency to module B
- the module B has a dependency to a librar
