Re: [starter-dev] Starter archetypes / GUI / Issue #67

[Ivo Woltring <ivo@xxxxxxxxx>]

Can you create a org.eclipse.starter::jakartaee9 repo so that I can fork it and create a PR on that one or make me a committer (presumptuous, I know)?

I would start with a really barebones version the almost but not quite trivial one.

On 30 Apr 2022, at 09:39, Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx> wrote:

On Sat, Apr 30, 2022 at 9:20 AM Ivo Woltring <ivo@xxxxxxxxx> wrote:

This is actually what I ment with my multiple archetypes idea.

Applying the WET Principle here is probably the best option and as they should be separately maintained that should not be a problem.

Doing this in one repo is a problem though.

Agree!

And luckily, requesting more repositories is a simple thing for Eclipse projects

Ivar 

On 30 Apr 2022, at 08:03, Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx> wrote:

We need to be able to support multiple versions of Jakarta EE at the same time. 

Support for EE 9 and EE 10 is crucial to get out ASAP. For this we have two options:

1. One archetype that supports the generation of multiple Jakarta EE versions

2. One archetype per Jakarta EE version

I think that 2) will get us there faster, and also reduce the complexity of the archetype. Thus apply WET rather than DRY. It would also be clear for the user which version is being generated by this being reflected in the maven coordinates. For example:

org.eclipse.starter::jakartaee8

org.eclipse.starter::jakartaee9

org.eclipse.starter::jakartaee10

...

Ivar

On Fri, Apr 29, 2022 at 9:41 PM Reza Rahman <reza_rahman@xxxxxxxxx> wrote:

Certainly a welcome idea, though hopefully not an "as-is" donation but a merge?

For example, are separate Archetypes really needed? I think for folks using it from the command line and IDE, just one Archetype would be far easier. As such, it is very easy to modularize Archetypes instead of exposing the user to the complexity of multiple Archetypes I think (you can hopefully see that in the code currently in the main branch and various runtime support). 

On 4/29/22 3:06 PM, Ivo Woltring wrote:

Hi y’all,

A Couple of weeks ago I was triggered by the new https://start.jakarta.ee/ archetype and have been playing with it.

The last couple of years I have maintained a couple of javaEE/jakartaEE maven archetypes and exposed them to the web: https://ivonet.github.io/archetype/

Just now I saw the issue created by Ivar https://github.com/eclipse-ee4j/starter/issues/67 and that made me think.

If the community is open to it, I would love to join the effort and possibly ”donate" all my archetype related material.

It is already open source but right now under the Apache2 license. That is also open to change as I am the sole committer on these projects.

Please let me know what you think.

Kind regards,

Ivo Woltring.

https://www.ivonet.nl/

@ivonet

_______________________________________________
starter-dev mailing list
starter-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/starter-dev

_______________________________________________
starter-dev mailing list
starter-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/starter-dev

-- 

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 

-- 

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration.