6 Apr
2011
6 Apr
'11
10:51 a.m.
+0, using artifactid is longer, but a clear rule. And you have
auto-completion and IDE, so why fear longer name ?
Denis
On Tue, Apr 5, 2011 at 15:49, Marius Dumitru Florea <
mariusdumitru.florea(a)xwiki.com> wrote:
Same as Sergiu, I prefer shorter names but artifactId
is not that bad. So
0.
Thanks,
Marius
On 04/05/2011 02:19 PM, Jerome Velociter wrote:
Same as Sergiu, I would prefer shorter names ; but no strong feelings either.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO
On Tue, Apr 5, 2011 at 11:36 AM, Sergiu
Dumitriu<sergiu(a)xwiki.com>
wrote:
> On 04/05/2011 11:03 AM, Vincent Massol
wrote:
>> Hi devs,
>>
>> The proposal is to use artifactid as directory names.
>>
>> Note that this is what I did for commons and rendering when I did the
move
to top level project. You can check how it looks like here:
>>
http://svn.xwiki.org/svnroot/xwiki/commons/
>> http://svn.xwiki.org/svnroot/xwiki/rendering/
>>
>> I suggest we keep one strategy only for consistency.
>>
>> Some discussion here too:
>>
http://www.sonatype.com/people/2011/01/maven-tip-project-directories-and-ar…
>>
>> I know there are some cons (see my comment in the link above) but
overall
I find it simple to implement and with autocompletion not such a big
issue.
WDYT?
0. I'd prefer shorter names, but I don't have a strong preference for
it. Either way works. 0
Jerome
>
>> If you don't like this then please propose an alternative solution and
remember that we'll need to refactor commons and rendering in this case too.
Thanks
-Vincent
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs