Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
Sender: jcarman@carmanconsulting.com
In-Reply-To: <AANLkTikoFvDXFJrH4D-GF_1Kcx2uVZt_DaOVqgUVSP0k@mail.gmail.com>
References: <AANLkTik8FR5H0v5Ko-=naWUpgFk9Vn2oC8_4hcDdtFCj@mail.gmail.com>
 <AANLkTikoFvDXFJrH4D-GF_1Kcx2uVZt_DaOVqgUVSP0k@mail.gmail.com>
From: James Carman <james@carmanconsulting.com>
Date: Sun, 7 Nov 2010 21:48:12 -0500
Message-ID: <AANLkTi=R=uY-sLy=UcLTx=+2rHcqX+s9W5B8LBT8P6ww@mail.gmail.com>
Subject: Re: [VFS] Maven groupId problem?
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Nov 7, 2010 at 9:43 PM, Henning Schmiedehausen
<henning@schmiedehausen.org> wrote:
> This is an old, buggy location and it should be cleaned up over time.
> Being locked into the mistakes of the past because some tool can not
> understand it, doesn't seem to be reasonable to me.
>

The cat's sort of out of the bag now.  It pisses people (well at least
it does me) off when you start moving stuff around on them.  All of a
sudden, you start seeing "blah blah moved to blah blah" in your build
output.  VFS apparently wasn't a Maven 2 project at the time it was
released.  The source distribution doesn't contain a pom.xml file.
I'm more worried about how the tag is out of sync with the "official"
released source.  That's not good.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org