Peachtree Road, Suite 820 . Atlanta, GA 30326 . USA
> Tel: +1.404.760.1560
> Email: ggreg...@seagullsoftware.com
> Web: seagull.rocketsoftware.com
>
>
>> -Original Message-
>> From: Ralph Goers [mailto:ralph.go...@dslextreme.com]
>> Sent: Friday, No
m
Web: seagull.rocketsoftware.com
> -Original Message-
> From: Ralph Goers [mailto:ralph.go...@dslextreme.com]
> Sent: Friday, November 12, 2010 21:56
> To: Commons Developers List
> Subject: [VFS] artifactid
>
> I've changed the package name from org.commons.vfs to org.commons.vfs2.
&
On 2010-11-13 15:00, James Carman wrote:
> Change it to be consistent. We've had this discussion before.
+1
Consistence is a good thing.
>
> On Sat, Nov 13, 2010 at 12:56 AM, Ralph Goers
> wrote:
>> I've changed the package name from org.commons.vfs to org.commons.vfs2.
>> However, it isn't
Change it to be consistent. We've had this discussion before.
On Sat, Nov 13, 2010 at 12:56 AM, Ralph Goers
wrote:
> I've changed the package name from org.commons.vfs to org.commons.vfs2.
> However, it isn't necessary to change the artifact id from commons-vfs to
> commons-vfs2 since we are
On 13 November 2010 05:56, Ralph Goers wrote:
> I've changed the package name from org.commons.vfs to org.commons.vfs2.
> However, it isn't necessary to change the artifact id from commons-vfs to
> commons-vfs2 since we are changing the groupId already. The only reason to
> do it is to have i
I've changed the package name from org.commons.vfs to org.commons.vfs2.
However, it isn't necessary to change the artifact id from commons-vfs to
commons-vfs2 since we are changing the groupId already. The only reason to do
it is to have it match the package name.
Thoughts?
Ralph
---
