Hi all,
4 years ago I created the jfx archetyes repository,
https://github.com/errael/javafx-maven-archetypes-netbeans, so that jfx
projects would work "out of the box" with debugging, profiling, jlink...
on NetBeans. It's artifact is on maven and used from
javafx/java
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 provid
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
isadvantages,
> > 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
> > re
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 NetBean
ce in POM. Seems to me quite similar to changing the archetype
itself - but NB IDE would then inject its own actions on the fly, and
the user can customize them.
If looks interesting, share your requirements in NETBEANS-5394.
[1]
https://github.com/openjfx/javafx-maven-archetypes/blob/master/j
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 providin
be fixed?
>
I would take a stab at fixing the JEE project wizards, but I'm not willing
to do that if NB can't own the maven archetypes. The archetypes and the
wizards are intertwined, it does not appear to be a simple wrapper around
just invoking the archetype, so one can't be
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
org.openjfx... archetype, and then I manually add
the javafx:run as a NetBeans action.
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,
see
https://github.com/openjfx/javafx-maven-archetypes/iss
ed?
Gj
On Thu, Apr 22, 2021 at 12:28 AM Will Hartung wrote:
> 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
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
not a fork) github project for javafx maven
archetypes, published it to maven central, to replace the ones (from
gluon) used by NetBeans.
I think the PR that used those archetypes was merged somewhat by
accident, since there was immediate objection from some senior PMC
members (it stayed i
I touched on this talking about the EJB new project support and how it's
currently broken.
Fundamental to this is that the IDE relies on the Maven archetype
templating system to generate project artifacts. It also wraps that process
up in some wizard code, and it may well do some other things, I h
Hi Will,
You are correct, we have been talking past each other. As far as I know,
the "Enterprise Application" option of NetBeans is there for historical
purposes. I haven't written enterprise code in that manner for a number of
years, as over the past several years Java EE and Jakarta EE have e
On Thu, Jan 28, 2021 at 7:49 PM Josh Juneau wrote:
> Sorry, but there must be something incorrect with the Java EE 8 project
> archetype that you are using. When I use Apache NetBeans to create a Java
> EE 8 project, I select the following:
>
> - New: "Java with Maven" -> "Web Application"
>
> T
ar that informs the IDE what to do? Does it look for the
> plugin in the pom?
>
> Consider a microprofile project. That would likely just be a standalone
> jar, bundling the microprofile runtime with the application code to make a
> fat jar...I guess. It has different deployment options.
>
&
All that said, I think it would be great to have the Apache NetBeans
> projects generated by Maven archetypes that are all hosted under a standard
> namespace. We should also be updating the archetypes as time goes on, as
> needed. These are community supported, just like Apache Ne
NetBeans. I was hoping that
it would be built upon by the community over time, and even that a better and
more standardized Maven archetype be put into place.
All that said, I think it would be great to have the Apache NetBeans projects
generated by Maven archetypes that are all hosted under a
The JEE Maven archetypes are a bit of a disaster right now, there's
relevant issues in JIRA already.
But it brought up a question.
Historically, and currently, the archetypes used for these projects (I
don't know about others) are not part of Netbeans. They're external
arc
Dear Apache NetBeans community,
Thanks for voting, vote pass.
4+1 binding vote,
lkishalmi (Laszlo Kishalmi)
geertjan (Geertjan Wielenga)
jag (Geertjan Wielenga)
thilina01 (Thilina Ranathunga)
3+1 Non binding vote
Patrick Musembi
Jose Ch
Kai Uwe Pel
I will propagate the maven artefacts to centr
type-1.17
> 2) nbm-suite-root-1.12
> 3) netbeans-platform-app-archetype-1.22
>
> Apache Maven Archetypes are used by Apache NetBeans in the project wizard
> "Java With Maven" to create NetBeans Module and NetBeans Application.
> As the nbm plugin changed we need to up
beans-platform-app-archetype-1.22
Apache Maven Archetypes are used by Apache NetBeans in the project wizard
"Java With Maven" to create NetBeans Module and NetBeans Application.
As the nbm plugin changed we need to update archetype too.
Changes since respective previous version
- Only versio
+1
El vie., 11 oct. 2019 a las 12:40, Patrick Musembi ()
escribió:
> +1
>
>
> On Fri, Oct 11, 2019, 20:31 James Gosling wrote:
>
> > +1
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > For additi
+1
On Fri, Oct 11, 2019, 20:31 James Gosling wrote:
> +1
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about th
+1
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/
> >
> > I want to call a vote on releasing the following Apache NetBeans
> Archetypes:
> >
> > 1) nbm-archetype-1.17
> > 2) nbm-suite-root-1.12
> > 3) netbeans-platform-app-archetype-1.22
> >
> > Apache Maven Archetypes are used by Apache NetBeans
suite-root-1.12
3) netbeans-platform-app-archetype-1.22
Apache Maven Archetypes are used by Apache NetBeans in the project wizard
"Java With Maven" to create NetBeans Module and NetBeans Application.
As the nbm plugin changed we need to update archetype too.
Changes since respective pre
Dear members of Apache NetBeans community.
it's been a long time since last vote call. ( :D )
I want to call a vote on releasing the following Apache NetBeans Archetypes:
1) nbm-archetype-1.17
2) nbm-suite-root-1.12
3) netbeans-platform-app-archetype-1.22
Apache Maven Archetypes are us
Dear Apache NetBeans community,
Thanks for voting,
The vote has reach quorum by 3+1 votes from,
- Geertjan Wielenga
- Thilina Ranathunga
- Eric Barboni
There is also 2+1 non binding vote from,
- Jose Ch
- Kai Uwe Pel
I will propagate the maven artefacts to central and sources to the dist
area.
My self +1
-Message d'origine-
De : Thilina Ranathunga
Envoyé : mercredi 26 juin 2019 12:20
À : dev@netbeans.apache.org
Objet : Re: [VOTE] Maven Archetypes new release
+1
On Tue, Jun 25, 2019, 8:35 PM Eric Barboni wrote:
> Dear members of Apache NetBeans community.
>
s-platform-app-archetype-1.21
>
>
> Apache Maven Archetypes are used by Apache NetBeans in the project wizard
> "Java With Maven" to create NetBeans Module and NetBeans Application
>
> Changes since mojohaus
> - Archetype used plugin are up to date, java 8 minimum
&g
the following Apache NetBeans
> Archetypes
> > (3 at once if possible):
> >
> > 1) nbm-archetype-1.16
> > 2) nbm-suite-root-1.11
> > 3) netbeans-platform-app-archetype-1.21
> >
> >
> > Apache Maven Archetypes are used by Apache NetBeans i
-archetype-1.21
Apache Maven Archetypes are used by Apache NetBeans in the project wizard
"Java With Maven" to create NetBeans Module and NetBeans Application
Changes since mojohaus
- Archetype used plugin are up to date, java 8 minimum
NB
- the file in the respective archetype-resources c
:
>
> 1) nbm-archetype-1.16
> 2) nbm-suite-root-1.11
> 3) netbeans-platform-app-archetype-1.21
>
>
> Apache Maven Archetypes are used by Apache NetBeans in the project wizard
> "Java With Maven" to create NetBeans Module and NetBeans Application
>
> Changes sin
Dear members of Apache NetBeans community.
I want to call a vote on releasing the following Apache NetBeans Archetypes
(3 at once if possible):
1) nbm-archetype-1.16
2) nbm-suite-root-1.11
3) netbeans-platform-app-archetype-1.21
Apache Maven Archetypes are used by Apache NetBeans in the
40 matches
Mail list logo
