<div dir="ltr"><div><div><div>+1 to demos in a single sub-directory. This is pretty typical with most projects to have a centralized "examples/" or "showcase/" directory.<br><br></div>Also +1 for import BOM.<br>
<br></div>Finally +1 for stack POMs. This is what I started with the errai-javaee-all module. As far as I know it still works. Very helpful if users can pull in a single dependency and have a working setup on a given container. I think at this point it is safe to assume Servlet 3.0 API as well and use web-fragment.xml to do any necessary servlet configurations. 2.5 config can be documented as things stand now, but 3.0 should be assumed.<br>
<br></div>~Lincoln<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 4, 2013 at 3:37 PM, Jonathan Fuerth <span dir="ltr"><<a href="mailto:jfuerth@redhat.com" target="_blank">jfuerth@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi everyone,<div><br></div><div>Pavel asked for feedback today on what he's done so far with the demos on the 3.0_p branch:</div>
<div><br></div><div> <a href="https://github.com/pslegr/errai/tree/3.0_p/errai-demos" target="_blank">https://github.com/pslegr/errai/tree/3.0_p/errai-demos</a></div><div><br></div><div>As you can see, there's still a subdirectory for errai-bus. Pavel said his intention is to keep the separation between bus, cdi, jpa, and so on.</div>
<div><br></div><div>Here's my feedback on what's there so far:</div><div><br></div><div>I'm not sure I'm keen on this "separation of demo topics" approach. We're not planning to keep a ton of demos in the project (we decided that together in last week's hangout). So I think it would be best to throw all the demo projects under a single directory.</div>
<div><br></div><div>One other thing that I think is different from what we had planned to do: in 3.0_p, the bus demos still depend on a parent POM. JDF required demos to have top-level poms (no reference to a parent), and we were planning to follow that. We can & should still have an errai-demos pom which refers to all the demos as submodules, so the demos are built when we build errai-parent. But we don't want the demo poms pointing back up to that parent.</div>
<div><br></div><div>I *do* think we should develop a 'depchain' or 'BOM' type pom that can be imported. These would be useful for demos, archetypes, and anybody's end-user project. We should probably have a separate depchain for each appserver we support (as7, eap6, tomcat, jetty). We should design these depchains so the demo poms are as small as possible (unfortunately, we can't import plugin configurations, so they will be somewhat larger than what we have now).</div>
<span class="HOEnZb"><font color="#888888"><div><br></div><div>-Jonathan</div></font></span></div><br>_______________________________________________<br>
errai-dev mailing list<br>
<a href="mailto:errai-dev@lists.jboss.org">errai-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/errai-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/errai-dev</a><br></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>
"Simpler is better."
</div>