On Fri, Apr 23, 2021 at 5:06 AM Eric Bresie wrote:
> Just to understand the problem being discussed
>
> There are Netbeans wrapper plugins (I.e. Netbeans specific artifacts) like
> the JavaFX or Java EE plugins
> These plug-ins have dependencies on third party libraries which (possibly
> dependin
ards
> Eric
>
>
>
> -Message d'origine-
> De : Sean Carrick mailto:s...@pekinsoft.com)>
> Envoyé : jeudi 22 avril 2021 21:11
> À : dev@netbeans.apache.org (mailto:dev@netbeans.apache.org)
> Objet : Re: Netbeans "owning" Maven archetypes
>
>
ssage d'origine-
De : Sean Carrick
Envoyé : jeudi 22 avril 2021 21:11
À : dev@netbeans.apache.org
Objet : Re: Netbeans "owning" Maven archetypes
Will,
When looking for old source from websites that are no longer around, I usually
have pretty good luck on The Wayback Machine (ht
Will,
When looking for old source from websites that are no longer around, I
usually have pretty good luck on The Wayback Machine
(http://web.archive.org).
-SC
On 4/22/21 11:26 AM, Will Hartung wrote:
> On Thu, Apr 22, 2021 at 8:50 AM Geertjan Wielenga
> wrote:
>
>> Probably the archetypes are
In that case, makes sense to recreate the Maven archetypes and publish them
to Maven Central.
Gj
On Thu, Apr 22, 2021 at 6:27 PM Will Hartung wrote:
> On Thu, Apr 22, 2021 at 8:50 AM Geertjan Wielenga
> wrote:
>
> > Probably the archetypes are open source and you'd provide pull requests
> to
>
On Thu, Apr 22, 2021 at 8:50 AM Geertjan Wielenga
wrote:
> Probably the archetypes are open source and you'd provide pull requests to
> them.
>
The problem is that the ones we used in the past have vanished. That's why
the NB 8.x wizards are failing, the archetypes were hosted by codehaus, and
t
Probably the archetypes are open source and you'd provide pull requests to
them.
Gj
On Thu, Apr 22, 2021 at 5:37 PM Will Hartung wrote:
> On Thu, Apr 22, 2021 at 7:29 AM Geertjan Wielenga
> wrote:
>
> > There's so much we don't own. We integrate. Yes, that has disadvantages,
> > but also the a
On Thu, Apr 22, 2021 at 7:29 AM Geertjan Wielenga
wrote:
> There's so much we don't own. We integrate. Yes, that has disadvantages,
> but also the advantage that we can help users with actually existing, e.g.,
> Maven archetypes, rather than those made specifically for NetBeans.
>
> On the other
BTW - looking at the JavaFX archetype resources[1], there's
javafx-maven-plugin configured ...
... which could nicely plug into
https://issues.apache.org/jira/browse/NETBEANS-5394 that will be
probably implemented.
Additional action mappings would be then activated by e.g. plugin
presence in
There's so much we don't own. We integrate. Yes, that has disadvantages,
but also the advantage that we can help users with actually existing, e.g.,
Maven archetypes, rather than those made specifically for NetBeans.
On the other hand, there's nothing stopping anyone from providing pull
requests f
On Wed, Apr 21, 2021 at 11:39 PM Geertjan Wielenga
wrote:
> Indeed, if there's a particular technology that isn't supported correctly
> in NetBeans or is outdated, just create an issue and let's work on it.
>
> Can we do that, point to a specific problem that needs to be fixed?
>
I would take a
On Thu, 22 Apr 2021 at 10:26, Johan Vos wrote:
> If this can be made easier if the archetype has a nbactions.xml that is not
> causing regression for other IDE's or CLI, I think we should consider it,
Short term that would be great. The last time this came up, Jaroslav
sent me an off-list reply
Talking about the OpenJFX specifically case:
I am personally open to make it as easy as possible to leverage the openjfx
javafx-maven-artifact in NetBeans. Actually, it is the main procedure I use
whenever I create a new JavaFX project: create a new project from an
archetype, specify the org.openjf
NetBeans is full of references and usages of third party technologies.
Indeed, if there's a particular technology that isn't supported correctly
in NetBeans or is outdated, just create an issue and let's work on it.
Can we do that, point to a specific problem that needs to be fixed?
Gj
On Thu,
On Wed, Apr 21, 2021 at 12:22 PM Ernie Rael wrote:
> The point is that depending on a 3rd party project for functionality
> that NetBeans provides is a problem. But there is push back to provide
> even simple maven archetypes. And, at least possibly until now, little
> interest in supplying arche
IMHO, NB should
"own" that archetype, publish, and maintain it
Couldn't agree more.
But here's one case study that shows some of the problems that might be
faced.
When I fixed javafx-maven to "run/debug out of the box", I created a
very small independent (not a fork) github project for java
16 matches
Mail list logo
