| Hmm what if we had had no dependencies except for maven and just made simple archetypes for each version? Hmm would life be easier? No updating deps no updating versions. just release a new one on each version and maybe a bug fix once in a while. No server needed. Just a bit of _javascript_ on a markdown page and some archetypes 🤔. Sounds like a novel idea to me. 🥰 
 It is not too late 😂! come back from the dark side and lets go towards the light together and KISS.  Ivo. On 29 Sep 2024, at 19:01, Reza Rahman via starter-dev <starter-dev@xxxxxxxxxxx> wrote:
 

  
    
  
  
     OK. In that case I can aim to do a bit more like updating the
      Maven dependencies and runtime versions. Do LMK when you get to it and send me the war offline. I'll
      update the cloud deployment ASAP.
 On 9/29/2024 11:49 AM, Jeyvison
      Nascimento wrote:
 
      
      _______________________________________________starter-dev mailing liststarter-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/starter-devHi, Reza.
         
 I'm out of home and will be back only next
          Friday. I can try to deploy in the next weekend 
 
        
        Jeyvison,
 Bazlur fixed the issue and I have tested it. Can we urgently
          have a
 release of the Archetype and UI please? This will minimize
          disruption
 for users.
 
 Thanks,
 
 Reza
 
 On 9/28/2024 7:47 AM, Reza Rahman wrote:
 > Bazlur,
 >
 > Starting a parallel thread. Do you want to just replace
          that
 > functionality with vanilla Java or vanilla Groovy? Maybe
          it's a bad
 > idea to have that dependency anyway? It would not
          actually be that
 > complex and it is always good to have one less external
          thing to
 > depend on (case in point maybe). I ask since you are
          actually the
 > original author of the code. Alternatively, you can see
          if you can
 > figure out a fix?
 >
 > Really need to get some sleep now. I somehow saw your
          Slack message in
 > the middle of the night and checked that the CI build has
          actually
 > been broken for the same reason.
 >
 > Cheers,
 >
 > Reza
 >
 > On 9/28/2024 7:29 AM, Reza Rahman wrote:
 >> Hi there!
 >>
 >> I am writing on behalf of the official Jakarta EE
          Starter project:
 >> https://start.jakarta.ee.
          We make use of Maven Archetypes in the
 >> Starter under the hood.
 >>
 >> We are pretty dependent on Groovy and
 >> use groovy.text.SimpleTemplateEngine for some
          critical functionality:
 >> https://github.com/eclipse-ee4j/starter/blob/ca9b5028b7fe3b47ecf4b5e5c22e89bc941e99a0/archetype/src/main/resources/META-INF/archetype-post-generate.groovy#L144.
 >>
 >> A few days ago we noticed that the Archetype is
          suddenly broken with
 >> the following error: unable to resolve class
 >> groovy.text.SimpleTemplateEngine. This seems to
          coincide with the
 >> 3.3.0 release of maven-archetype-plugin. Any idea
          what is going on
 >> and how to fix this?
 >>
 >> Thanks in advance,
 >>
 >> Reza
 >>
 
 |