<div dir="ltr">Sorry to bring that again, but, as a user, I don&#39;t see any difference between code generation and scaffolding... so I don&#39;t understand why there are several projects. If I want to create a n-tier architecture app with a JSF and REST interface I would :<div>
<br></div><div><font face="courier new, monospace">jpa-generate-entities-from-db</font></div><div><font face="courier new, monospace">rest-generate-entdpoints-from-entity</font></div><div><font face="courier new, monospace">jsf-generate-pages-from-entity<br>
</font></div><div><br></div><div>If I want to add a transactional EJB tier I would :</div><div><br></div><div><font face="courier new, monospace">jpa-generate-entities-from-db</font></div><div><font face="courier new, monospace">ejb-generate-services-from-entity</font></div>
<div><div><font face="courier new, monospace">rest-generate-entdpoints-from-service</font></div><div><font face="courier new, monospace">jsf-generate-pages-from-service<br></font></div></div><div><br></div><div>And if I want to see what an Angular front end looks like compare to JSF, I would :</div>
<div><br></div><div><font face="courier new, monospace">angular-generate-pages-from-service</font></div><div><br></div><div>Or if I quickly want to generate an Angular app from entities, I would : </div><div><br></div><div>
<div><font face="courier new, monospace">angular-generate-pages-from-entity</font></div></div><div><br></div><div>I remember talking to Vineet and he had this idea of &quot;you generate code&quot; and you &quot;scaffold an entire project&quot;. If that could be the case, then we would : </div>
<div><br></div><div><font face="courier new, monospace">scaffold-ntier-architecture-from-db</font></div><div><br></div><div>or </div><div><br></div><div><div><font face="courier new, monospace">scaffold-thin-client-from-db</font></div>
</div><div><font face="courier new, monospace">....</font></div><div><br></div><div>My 2 cents</div><div>Antonio</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2014-02-10 13:15 GMT+01:00 George Gastaldi <span dir="ltr">&lt;<a href="mailto:ggastald@redhat.com" target="_blank">ggastald@redhat.com</a>&gt;</span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    Exactly, I think I wasn&#39;t clear at first. Sorry about the confusion.<div><div class="h5"><br>
    <br>
    <div>On 10-02-2014 10:14, Ivan St. Ivanov
      wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">Sorry, George, didn&#39;t get your original intention!
        You plan for generating a scaffolding provider, not for
        scaffold[ed] project. My bad!</div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Mon, Feb 10, 2014 at 2:13 PM, George
          Gastaldi <span dir="ltr">&lt;<a href="mailto:ggastald@redhat.com" target="_blank">ggastald@redhat.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text="#000000" bgcolor="#FFFFFF"> Hi Ivan,<br>
              <br>
              I&#39;d expect it to generate a Maven project with a basic
              implementation of the
              org.jboss.forge.addon.scaffold.spi.ScaffoldProvider
              interface and also depending on the templates addon (with
              some basic templates available - perhaps JSF) . The idea
              is to that this generated addon project could be installed
              and used without modifications.
              <div>
                <div><br>
                  <br>
                  <br>
                  <div>On 10-02-2014 10:08, Ivan St. Ivanov wrote:<br>
                  </div>
                  <blockquote type="cite">
                    <div dir="ltr">Hi George,
                      <div><br>
                      </div>
                      <div>What would you expect for this project type
                        to generate besides the packaging type and maybe
                        a couple of dependencies? Is this something like
                        project-new-project+scaffold-setup?</div>
                      <div><br>
                      </div>
                      <div>BTW, not sure whether this is the right
                        thread for the question: scaffold setup command
                        is not available to my project, even though my
                        ~/.forge/addons directory contains all the
                        necessary scaffold jars.</div>
                      <div><br>
                      </div>
                      <div>Cheers,</div>
                      <div>Ivan</div>
                    </div>
                    <div class="gmail_extra"><br>
                      <br>
                      <div class="gmail_quote">On Mon, Feb 10, 2014 at
                        12:02 PM, Vineet Reynolds Pereira <span dir="ltr">&lt;<a href="mailto:vpereira@redhat.com" target="_blank">vpereira@redhat.com</a>&gt;</span>
                        wrote:<br>
                        <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
                          Yeah, it might make sense. A bit too early to
                          say if we need a scaffold project type in the
                          New Project wizard.<br>
                          <br>
                          We might support creation of new scaffold
                          providers (like Aerogear) that extend existing
                          scaffold providers (AngularJS),<br>
                          and I&#39;m not sure if this can be supported via
                          the wizard. Maybe it is better to revisit this
                          once we&#39;ve stabilized the programming model
                          for scaffold providers sufficiently, to limit
                          rewriting this wizard.<br>
                          <span><font color="#888888"><br>
                              Vineet<br>
                            </font></span>
                          <div>
                            <div><br>
                              ----- Original Message -----<br>
                              &gt; From: &quot;Sebastien Blanc&quot; &lt;<a href="mailto:sblanc@redhat.com" target="_blank">sblanc@redhat.com</a>&gt;<br>
                              &gt; To: <a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
                              &gt; Sent: Monday, February 10, 2014
                              12:05:33 PM<br>
                              &gt; Subject: Re: [forge-dev] New
                              Scaffolds<br>
                              &gt;<br>
                              &gt; On 02/10/2014 03:12 AM, George
                              Gastaldi wrote:<br>
                              &gt; &gt; Hi everyone,<br>
                              &gt; &gt;<br>
                              &gt; &gt; I noticed an increasing demand
                              in the scaffold usage (custom
                              architectures,<br>
                              &gt; &gt; technologies,etc). I was
                              thinking that it would be nice if we had a<br>
                              &gt; &gt; &quot;Scaffold Project&quot; type (similar
                              to a maven archetype) allowing the<br>
                              &gt; &gt; creation of an addon project
                              with available extension points to the<br>
                              &gt; &gt; scaffold addon.<br>
                              &gt; &gt; What do you guys think about it?<br>
                              &gt; &gt;<br>
                              &gt; &gt; Best Regards,<br>
                              &gt; &gt;<br>
                              &gt; &gt; George<br>
                              &gt; &gt;
                              _______________________________________________<br>
                              &gt; &gt; forge-dev mailing list<br>
                              &gt; &gt; <a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
                              &gt; &gt; <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
                              &gt; +1 Sounds good<br>
                              &gt; We had some interesting discussions
                              around this with Vineet  last week<br>
                              &gt; during JUDCon<br>
                              &gt;
                              _______________________________________________<br>
                              &gt; forge-dev mailing list<br>
                              &gt; <a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
                              &gt; <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
                              &gt;<br>
_______________________________________________<br>
                              forge-dev mailing list<br>
                              <a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
                              <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
                            </div>
                          </div>
                        </blockquote>
                      </div>
                      <br>
                    </div>
                    <br>
                    <fieldset></fieldset>
                    <br>
                    <pre>_______________________________________________
forge-dev mailing list
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a></pre>
                  </blockquote>
                  <br>
                </div>
              </div>
            </div>
            <br>
            _______________________________________________<br>
            forge-dev mailing list<br>
            <a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
            <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
forge-dev mailing list
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a></pre>
    </blockquote>
    <br>
  </div></div></div>

<br>_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Antonio Goncalves <br>Software architect and Java Champion<br>
<br><a href="http://www.antoniogoncalves.org/" target="_blank">Web site</a> | <a href="http://twitter.com/agoncal" target="_blank">Twitter</a> | <a href="http://www.linkedin.com/in/agoncal" target="_blank">LinkedIn</a> | <a href="http://www.parisjug.org/" target="_blank">Paris JUG</a> | <a href="http://www.devoxx.fr/" target="_blank">Devoxx France</a>
</div>