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 
depending on licenses) are or are not included in the wrapper plug-in.
If included then the wrapper may need updating to reflect newer version when 
developing or packaging the plug-in artifact (to be published someplace like 
maven central)
If not included then they may need to be retrieved from a location in the 
process (either development or runtime) which may no longer be available.

In addition, for a give wrapper plug-in, the intent is for the Netbeans wrapper 
to add additional actions available for use in Netbeans contexts (IDE or 
Platform) to leverage features provided by the third party dependency.

Regarding the dependencies...

Am I seeing this right?
https://mvnrepository.com/search?q=Mojohaus+

Assume the builds from that maybe getting published to a degree as it seems 
like newer artifacts are available here.

https://mvnrepository.com/artifact/org.codehaus.mojo

So do the plug dependencies need to be changed a little to point to some of 
these coordinates?

Are any of the needed external artifact available here?
http://netbeans.osuosl.org/

Eric Bresie
ebre...@gmail.com (mailto:ebre...@gmail.com)

> On April 23, 2021 at 4:34:34 AM CDT, Eric Barboni <sk...@apache.org 
> (mailto:sk...@apache.org)> wrote:
> Hi folks,
>
> Are the archetype you are looking for over here :
> https://github.com/mojohaus?page=3
>
> webapp-javaee6 webapp-javaee7 ... and others.
>
> For me would make sense to migrate to our management. We control release, we 
> can use with trust and we can also look to new version.
> We do this for nbm-maven-plugin we try to get last version on new project 
> creation instead of sticking with default hardcoded one, we can't do that for 
> random archetype outside our control for security reason (what if next 
> version is a unstable, is a virus or whatever)
>
>
> Best Regards
> Eric
>
>
>
> -----Message d'origine-----
> De : Sean Carrick <s...@pekinsoft.com (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
>
> 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
> > <geertjan.wiele...@googlemail.com.invalid 
> > (mailto:geertjan.wiele...@googlemail.com.invalid)> 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 they've gone off line.
> >
> > I'm trying to locate the original sources, but currently they have no
> > home so even if they're found, they need a new one.
> >
> > Is there any reason that NB can be the new home for these?
> >
> > Regards,
> >
> > Will Hartung
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org 
> (mailto:dev-unsubscr...@netbeans.apache.org)
> For additional commands, e-mail: dev-h...@netbeans.apache.org 
> (mailto:dev-h...@netbeans.apache.org)
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org 
> (mailto:dev-unsubscr...@netbeans.apache.org)
> For additional commands, e-mail: dev-h...@netbeans.apache.org 
> (mailto:dev-h...@netbeans.apache.org)
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

Reply via email to