[seam-dev] Example names
Shane Bryzak
sbryzak at redhat.com
Fri Mar 25 19:10:37 EDT 2011
I'd rather keep everything related to a single module contained within a
single group. Having artifacts spread across multiple groups doesn't
seem tidy to me.
On 25/03/11 23:12, Brian Leathem wrote:
> Should we also change the maven groupId in the examples' poms? I
> suggest adding a "examples" at the end of the regular module groupId.
> This would tidy up the artifacts in maven repositories.
>
> Brian Leathem
>
> On 02/27/2011 05:48 AM, Shane Bryzak wrote:
>> What I propose to clean this up is to prefix the
>> example name with the module name - e.g:
>>
>> helloworld becomes remoting-helloworld
>> simple becomes security-simple
>>
>> You get the idea. Also, the Maven artifact names for the examples
>> should be standardised too. We currently have all sorts of variations
>> here also, so how about we use seam-{module}-example-{name}, as this
>> seems to be what most people are already using (and therefore would
>> require the least work).
>>
>> Using the previous two examples, that would give us artifact names like so:
>>
>> seam-remoting-example-helloworld
>> seam-security-example-simple
>>
>> What do you think?
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
More information about the seam-dev
mailing list