t; >> one wrapper for all of them.
> >> It depends usage
> >>
> >> Regards
> >> Eric
> >>
> >> -Message d'origine-
> >> De : Matteo Di Giovinazzo
> >> Envoyé : vendredi 25 octobre 2019 16:22
> >>
t; Regards
>> Eric
>>
>> -Message d'origine-
>> De : Matteo Di Giovinazzo
>> Envoyé : vendredi 25 octobre 2019 16:22
>> À : dev@netbeans.apache.org
>> Objet : Re: NetBeans app with Maven with 3rd party libs
>>
>> Thanks Timon for the sug
etbeans.apache.org
> Objet : Re: NetBeans app with Maven with 3rd party libs
>
> Thanks Timon for the suggestion!
> I am used to follow that way using the Ant-based NetBeans
> module/suite/application projects, but I was hoping with Maven that could
> be avoided given that Maven takes c
Giovinazzo
Envoyé : vendredi 25 octobre 2019 16:22
À : dev@netbeans.apache.org
Objet : Re: NetBeans app with Maven with 3rd party libs
Thanks Timon for the suggestion!
I am used to follow that way using the Ant-based NetBeans
module/suite/application projects, but I was hoping with Maven that could
Thanks Timon for the suggestion!
I am used to follow that way using the Ant-based NetBeans
module/suite/application projects, but I was hoping with Maven that could
be avoided given that Maven takes care of dependencies itself. I guess the
problem is that Maven dependencies are transitive whereas
Hi Matteo,
The way to share dependencies between netbeans platform modules is to
create library wrapper modules.
- Create a new netbeans platform module
- add the dependency
- declare public packages
A little more elaborate description can be found here: