+1<br><br><div class="gmail_quote">On Fri, Mar 25, 2011 at 09:29, George Gastaldi <span dir="ltr"><<a href="mailto:gastaldi@apache.org">gastaldi@apache.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
+1 on Brian idea also<div><div></div><div class="h5"><br><br><div class="gmail_quote">2011/3/25 Brian Leathem <span dir="ltr"><<a href="mailto:bleathem@gmail.com" target="_blank">bleathem@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Should we also change the maven groupId in the examples' poms? I<br>
suggest adding a "examples" at the end of the regular module groupId.<br>
This would tidy up the artifacts in maven repositories.<br>
<font color="#888888"><br>
Brian Leathem<br>
</font><div><div></div><div><br>
On 02/27/2011 05:48 AM, Shane Bryzak wrote:<br>
> What I propose to clean this up is to prefix the<br>
> example name with the module name - e.g:<br>
><br>
> helloworld becomes remoting-helloworld<br>
> simple becomes security-simple<br>
><br>
> You get the idea. Also, the Maven artifact names for the examples<br>
> should be standardised too. We currently have all sorts of variations<br>
> here also, so how about we use seam-{module}-example-{name}, as this<br>
> seems to be what most people are already using (and therefore would<br>
> require the least work).<br>
><br>
> Using the previous two examples, that would give us artifact names like so:<br>
><br>
> seam-remoting-example-helloworld<br>
> seam-security-example-simple<br>
><br>
> What do you think?<br>
> _______________________________________________<br>
> seam-dev mailing list<br>
> <a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div></div></blockquote></div><br>
</div></div><br>_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>
<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>