In a pinch, you can always use the Maven antrun plugin, overriding the run
target to build all the NBMs and unpack them into some directory
*$YOUR_CLUSTER* - which can be anywhere on your disk you want. Then, using
a *copy* of NetBeans, not the IDE you're running, or strange things will
happen, ad
Seems I've made some mistakes in configuration, probably because of some
copy/paste done wrong.
Am 05.06.2018 um 12:33 schrieb Peter Nabbefeld:
Other strange things now happen, like duplicated jar files (using
different names) and duplicated clusters (default one + one with
artifact name). If
Hi Geertjan,
the Maven "NetBeans Application" project type states: "The platform is
loaded entirely from a Maven repository." - that's not what I want.
Also, I don't want to modify anything of the IDE. I'll try the tutorial
probably some time later.
The "nbm-suite-root" plugin is working in
Other strange things now happen, like duplicated jar files (using
different names) and duplicated clusters (default one + one with
artifact name). If I need the archetype "nbm-suite-root",
I'll have to investigate those further. So going to try two other
possible options.
Peter
Am 05.06.2018
The archetype is working, but only without "useOSGiDependencies".
When adding new modules to some POM project (like the one generated by
"nbm-suite-root"), usually "Allow OSGi modules as dependencies" is
selected by default, adding a configuration parameter entry
"true" to the created POM fo
Hello Geertjan,
I'll go to try that later today, probably this evening.
Kind regards
Peter
Am 05.06.2018 um 11:53 schrieb Geertjan Wielenga:
Just follow the tutorial -- yes, it requires 8.1 or above, I think it's not
a problem.
Rather than figuring various things out, can you follow the tu
Just follow the tutorial -- yes, it requires 8.1 or above, I think it's not
a problem.
Rather than figuring various things out, can you follow the tutorial first,
and then see what's missing for you after that?
Thanks,
Gj
On Tue, Jun 5, 2018 at 11:24 AM, Peter Nabbefeld
wrote:
>
> Hi Geertja
Hi Geertjan, thank You!
At the beginning of the tutorial I found a little mistake:
While the "sticker" says, "Requires NetBeans 8.1", there's a "Note:
**This document uses NetBeans Platform 7.2 and NetBeans IDE 7.2. If you
are using an earlier version, see the previous version of this documen
Really, all you should need is to "run" a module that depends on all the
others you need.
-Tim
On Tue, Jun 5, 2018 at 2:17 AM, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:
> Tutorial: https://platform.netbeans.org/tutorials/nbm-maven-
> quickstart.html
>
> Gj
>
> On Tue, Jun 5, 2
Tutorial: https://platform.netbeans.org/tutorials/nbm-maven-quickstart.html
Gj
On Tue, Jun 5, 2018 at 8:09 AM, Peter Nabbefeld
wrote:
>
> Thank You, Tim! What does an application project make so special? I guess,
> it's not "only" the branding? BTW, can I drop it, to turn the application
> proj
Thank You, Tim! What does an application project make so special? I
guess, it's not "only" the branding? BTW, can I drop it, to turn the
application project into a suite?
Regards
Peter
Am 05.06.2018 um 07:59 schrieb Tim Boudreau:
Suites were really invented for Ant projects, and just happ
Suites were really invented for Ant projects, and just happen to output a
cluster because a suite is usually a group of interdependent modules, so
most of the time mapping that to a cluster makes sense.
http://wiki.netbeans.org/DevFaqSuitesVsClusters
For Maven projects, if one is an "application"
Hello,
using Maven, there's a project type for NetBeans Applications, but not
for a NetBeans Module Suites.
So I created a POM project and added some NetBeans Modules. But I cannot
start it.
The POM project cannot be started with NetBeans, and the single modules
aren't required (though d
13 matches
Mail list logo
