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 (nike.apache.org: local policy)
MIME-Version: 1.0
Sender: jcarman@carmanconsulting.com
In-Reply-To: <AANLkTi=R=uY-sLy=UcLTx=+2rHcqX+s9W5B8LBT8P6ww@mail.gmail.com>
References: <AANLkTik8FR5H0v5Ko-=naWUpgFk9Vn2oC8_4hcDdtFCj@mail.gmail.com>
 <AANLkTikoFvDXFJrH4D-GF_1Kcx2uVZt_DaOVqgUVSP0k@mail.gmail.com>
 <AANLkTi=R=uY-sLy=UcLTx=+2rHcqX+s9W5B8LBT8P6ww@mail.gmail.com>
From: James Carman <james@carmanconsulting.com>
Date: Sun, 7 Nov 2010 21:53:58 -0500
Message-ID: <AANLkTi=J-yMigWDYnkLo9A+E6eJG5JuU8SQtAvAmtEp2@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
Content-Transfer-Encoding: quoted-printable

On Sun, Nov 7, 2010 at 9:48 PM, James Carman <james@carmanconsulting.com> w=
rote:
>
> The cat's sort of out of the bag now. =A0It pisses people (well at least
> it does me) off when you start moving stuff around on them. =A0All of a
> sudden, you start seeing "blah blah moved to blah blah" in your build
> output. =A0VFS apparently wasn't a Maven 2 project at the time it was
> released. =A0The 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. =A0That's not good.
>

The other weird thing here is that there actually *are* pom.xml files
in the core and examples subfolders in the source distribution for
1.0.  So, Maven 2 was at least part of the picture.  Curiouser and
curiouser.

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