[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| Re: [starter-dev] Some updates on the progress made lately | 
  
  
    Hi all,
      I followed this project and the discussion in the last view weeks.
      I also agree that this idea of a starter page is really great. And
      it's important to give new developers (who haven't been using Java
      EE for the last 10 years) a starting point. 
      
      For us here, everything that is on the starter page is completely
      clear and the "The Jakarta® EE Tutorial" explains the rest. But
      what I observe is that many new developers have absolutely no
      patience anymore. So I think it would be good to offer not only a
      selection of platforms, but also a small selection of minimalist
      project templates. For example, a simple RestAPI example with a
      Swagger UI or a minimal JPA example.  Some time ago I had
      assembled something like this for a customer in a draft version
      including a Dockerfile to provide a simple start with a default
      runtime:
      
      https://github.com/rsoika/ralphs-microservices
      
      The goal was to show that Jakarta EE brings a lot of additional
      functionality if you combine it for example with Eclipse
      Microprofile. I don't know what you think about a Dockerfiles with
      a Wildfly or Payara Runtime? Or whether you consider Eclipse
      Microprofiles to be overloaded here?
    But I think that at least we should somehow give the
      profile/template selection a dynamically reloaded README.md file
      that explains a bit what the template consists of. It may be
      enough to point the developer to the corresponding sections in the
      "The Jakarta® EE Tutorial".
      
      For example:
    This example contains a Rest Service called '/hello' which is
        defined in the class RestResource. You can add additional GET,
        POST and DELETE resources. Find out more about the Jakarta EE
        Rest API here.
      
      If you want to load or store your data from a Database you
        can use the Jakarat
          EE Persistence API.
      
    
    I know you think this is idiotic, but for many new developers
      these very simple hints are important to survive the first half
      hour ;-)
    
    
    ===
      Ralph
    
    Am 11.11.22 um 08:22 schrieb Ivar
      Grimstad:
    
    
      
      Greetings Committers and Contributors,
        
        
        I am super excited to see the starter project moving
          forward after a little standstill. There has been some great
          progress made lately! New contributors and committers are on
          board. We now have a simple UI available at 
https://start.jakarta.ee that
          generates a simple project for Jakarta EE 8, Jakarta EE 9.1,
          and Jakarta EE 10. The feedback I have received from the
          community when demoing it has been 100% positive.
        
        The UI uses bare-minimum archetypes to generate the code.
          The next steps would be to add support for runtimes and
          possibly explore creating a CLI as an alternative to the Web
          UI.
        
        
        In addition to the UI, there are also several archetypes
          that generate more extensive examples being worked on. Since
          everything is based on archetypes, adding these and
          potentially other archetypes created by the community
          should be fairly straightforward.
        
        
        The archetypes for EE 8, 9.1, and 10 could be
          mashed together as one with the conditional logic inside the
          archetype. I am not sure if this is the right thing to do,
          though. 
        Keep in mind that as we go forward with EE 11, 12, 13, ...
          the older versions won't need much attention. Sometimes, a
          little duplication is favorable over adding another branch in
          the logic (even if it is just another if-statement...).
        
        
        
          The option of creating a server-based solution to
            generate the starter projects is still an option if someone
            wants to pursue this. It is always good to have options.
          Personally, I think the approach to base the starter on
            archetypes is a better and more flexible way to go. The only
            server needed is Maven Central, and that is already there
            and not our problem to maintain. And it provides the option
            for developers to consume the archetypes directly, via our
            UI, potentially a CLI, or directly in IDEs.
          
          
         
        Ivar
        -- 
        
          
            
              
                  Ivar Grimstad
                  Jakarta EE Developer Advocate | Eclipse Foundation
Eclipse
                      Foundation - Community. Code. Collaboration. 
                 
             
           
         
      
      
      _______________________________________________
starter-dev mailing list
starter-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/starter-dev
    
    -- 
      
        Imixs Software Solutions GmbH
        
        Web: www.imixs.com Phone:
        +49 (0)89-452136 16 
        Timezone: Europe/Berlin - CET/CEST
        Office: Agnes-Pockels-Bogen 1, 80992 München
        Registergericht: Amtsgericht Muenchen, HRB 136045
        Geschaeftsführer: Gaby Heinle u. Ralph Soika
      
      
        Imixs is an open source company, read more: www.imixs.org