Return-Path: 
 <jdo-dev-return-7769-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org>
Delivered-To: apmail-db-jdo-dev-archive@www.apache.org
Received: (qmail 75589 invoked from network); 14 Nov 2008 18:05:48 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 14 Nov 2008 18:05:48 -0000
Received: (qmail 65232 invoked by uid 500); 14 Nov 2008 18:05:32 -0000
Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:jdo-dev-help@db.apache.org>
List-Unsubscribe: <mailto:jdo-dev-unsubscribe@db.apache.org>
List-Post: <mailto:jdo-dev@db.apache.org>
List-Id: <jdo-dev.db.apache.org>
Reply-To: jdo-dev@db.apache.org
Delivered-To: mailing list jdo-dev@db.apache.org
Received: (qmail 65219 invoked by uid 99); 14 Nov 2008 18:05:32 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Nov 2008 10:05:32 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of carlossg@gmail.com designates
 209.85.200.171 as permitted sender)
Received: from [209.85.200.171] (HELO wf-out-1314.google.com) (209.85.200.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Nov 2008 18:04:12 +0000
Received: by wf-out-1314.google.com with SMTP id 26so1629251wfd.13
        for <jdo-dev@db.apache.org>; Fri, 14 Nov 2008 10:04:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:sender
         :to:subject:cc:in-reply-to:mime-version:content-type
         :content-transfer-encoding:content-disposition:references
         :x-google-sender-auth;
        bh=4tbRC9cnTPmkid3HiHuZVDlNDdsfbT9qWU9fdvyWzOg=;
        b=Lzef0sY4TejWYTYSdEhaHQAxECIA1CzxduorYvQ40iaQL1+eydJvxKhmOK3uiTWhql
         /5yc5+s6sxmB6rCdRCXvWliPRc6TrJ9+V9uwdLA7795droB73wZdIupZtA/0bR7VW/3Q
         nOSiOjUawK/Fdpmo7SSmFJVfXbxStD8zxxUak=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=mtQ7npdclctlN7roD4RAPz6Tq2DGBp1G++unb75T5HfZyGc9WGaB3gquN8QOUZyllL
         fit+6LuIvlqJPRt8Bn0dxhXP01i0Q2tbrDKPoAqlJhvcG9+/WAAXtz2aBVxV0o7cKNS/
         uKr/qkS+uU4G6p0gv0Pdfn6j8KbtSLuMhyJUQ=
Received: by 10.142.58.5 with SMTP id g5mr526960wfa.170.1226685886623;
        Fri, 14 Nov 2008 10:04:46 -0800 (PST)
Received: by 10.142.245.4 with HTTP; Fri, 14 Nov 2008 10:04:46 -0800 (PST)
Message-ID: <1a5b6c410811141004s3e72976k2fb4b10cda04989e@mail.gmail.com>
Date: Fri, 14 Nov 2008 10:04:46 -0800
From: "Carlos Sanchez" <carlos@carlossanchez.eu>
Sender: carlossg@gmail.com
To: repository@apache.org
Subject: Re: Automatically generated POM for JDO (Maven 1 project)
Cc: jdo-dev@db.apache.org
In-Reply-To: <416D019C-F696-426E-A29C-899A68468CD9@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <c84a50780811140906s4b6235e0n4bb1d8ced18e47ab@mail.gmail.com>
	 <1a5b6c410811140928v3fb10574p6e0b31f0ddde9296@mail.gmail.com>
	 <416D019C-F696-426E-A29C-899A68468CD9@Sun.COM>
X-Google-Sender-Auth: e1916a37848d39a8
X-Virus-Checked: Checked by ClamAV on apache.org

I have commented in https://issues.apache.org/jira/browse/JDO-612
you can do that with

    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>3.8.1</version>
      <properties>
        <scope>test</scope>
      </properties>
    </dependency>



On Fri, Nov 14, 2008 at 10:02 AM, Craig L Russell <Craig.Russell@sun.com> wrote:
> Hi Carlos,
>
> Thanks for the information. We did figure that the project.xml "is converted
> to Maven 2 and propagated" but this seems to be error-prone.
>
> Maven 1 doesn't have the notion of scoped dependencies, and the issue here
> is that the junit and ant are test dependencies. So they should not be
> included in the maven 2 pom unless they are scoped to test.
>
> We are looking at how to fix this in future, since we can't simply add a
> <scope>test</scope> to the project.xml (maven complains about the unknown
> tag).
>
> The maven 1 repo has a pom in maven 1 format so there doesn't seem to be a
> place for an automatic conversion. Seems like we need to publish to the
> maven 2 repository directly.
>
> WDYT?
>
> Craig
>
> On Nov 14, 2008, at 9:28 AM, Carlos Sanchez wrote:
>
>> Hi Craig
>>
>> Michelle Caisse added the files to the apache Maven 1 repository, that
>> is converted to Maven 2 and propagated to the central maven repository
>> and mirrors
>> See below
>>
>> Unfortunately there's no easy way to fix it as it has been propagated
>> to all mirrors, downstream users,... already. You could either do a
>> new official release (2.2.1, 2.2.0.1, ...) or just copy the jar and
>> the good pom as 2.2-1 (naming convention used before to fix bad poms
>> with the same jar)
>>
>> btw for Apache Maven repository issues, the best contact is
>> <repository@apache.org>
>>
>>
>> On Fri, Oct 24, 2008 at 5:15 PM,  <bayard@apache.org> wrote:
>>>
>>> Repository changed
>>> ==================
>>>
>>> Repository: /www/people.apache.org/repo/m1-ibiblio-rsync-repository/
>>>
>>> Added
>>> -----
>>> [mcaisse] org.apache.jdo/jars/jdo2-util-2.2.jar.md5
>>> [mcaisse] org.apache.jdo/jars/jdo2-enhancer-2.2.jar.asc
>>> [mcaisse] org.apache.jdo/jars/jdo2-enhancer-2.2.jar.md5
>>> [mcaisse] org.apache.jdo/jars/jdo2-model-2.2.jar
>>> [mcaisse] org.apache.jdo/jars/jdo2-model-2.2.jar.asc
>>> [mcaisse] org.apache.jdo/jars/jdo2-model-2.2.jar.md5
>>> [mcaisse] org.apache.jdo/jars/jdo2-util-2.2.jar
>>> [mcaisse] org.apache.jdo/jars/jdo2-util-2.2.jar.asc
>>> [mcaisse] org.apache.jdo/jars/jdo2-enhancer-2.2.jar
>>> [mcaisse] org.apache.jdo/poms/jdo2-util-2.2.pom.md5
>>> [mcaisse] org.apache.jdo/poms/jdo2-enhancer-2.2.pom.asc
>>> [mcaisse] org.apache.jdo/poms/jdo2-enhancer-2.2.pom.md5
>>> [mcaisse] org.apache.jdo/poms/jdo2-model-2.2.pom
>>> [mcaisse] org.apache.jdo/poms/jdo2-model-2.2.pom.asc
>>> [mcaisse] org.apache.jdo/poms/jdo2-model-2.2.pom.md5
>>> [mcaisse] org.apache.jdo/poms/jdo2-util-2.2.pom
>>> [mcaisse] org.apache.jdo/poms/jdo2-util-2.2.pom.asc
>>> [mcaisse] org.apache.jdo/poms/jdo2-enhancer-2.2.pom
>>> [mcaisse] javax.jdo/jars/jdo2-api-2.2.jar
>>> [mcaisse] javax.jdo/jars/jdo2-api-2.2.jar.asc
>>> [mcaisse] javax.jdo/jars/jdo2-api-2.2.jar.md5
>>> [mcaisse] javax.jdo/jars/jdo2-api-legacy-2.2.jar
>>> [mcaisse] javax.jdo/jars/jdo2-api-legacy-2.2.jar.asc
>>> [mcaisse] javax.jdo/jars/jdo2-api-legacy-2.2.jar.md5
>>> [mcaisse] javax.jdo/poms/jdo2-api-2.2.pom
>>> [mcaisse] javax.jdo/poms/jdo2-api-2.2.pom.asc
>>> [mcaisse] javax.jdo/poms/jdo2-api-2.2.pom.md5
>>> [mcaisse] javax.jdo/poms/jdo2-api-legacy-2.2.pom
>>> [mcaisse] javax.jdo/poms/jdo2-api-legacy-2.2.pom.asc
>>> [mcaisse] javax.jdo/poms/jdo2-api-legacy-2.2.pom.md5
>>>
>>
>>
>>
>>
>> On Fri, Nov 14, 2008 at 9:06 AM, Steve Loughran
>> <steve.loughran@gmail.com> wrote:
>>>
>>> Dont think Craig is too happy.
>>>
>>> -------- Original Message --------
>>> Subject: Fwd: Automatically generated POM for JDO (Maven 1 project)
>>> Date: Fri, 14 Nov 2008 09:00:37 -0800
>>> From: Craig L Russell <Craig.Russell@Sun.COM>
>>> To: infrastructure@apache.org
>>> References: <4122A2A0-7558-4197-B1CD-FD4137DEF5CF@SUN.com>
>>>
>>> Can someone in the repository infrastructure please let us know where/
>>> how the JDO Maven 2 pom.xml is being generated, how to fix it, and how
>>> to prevent this from occurring in future?
>>>
>>> Thanks,
>>>
>>> Craig
>>>
>>> Begin forwarded message:
>>>
>>>> From: Craig L Russell <Craig.Russell@Sun.COM>
>>>> Date: November 6, 2008 5:34:45 AM PST
>>>> To: Maven Users List <users@maven.apache.org>
>>>> Cc: Apache JDO project <jdo-dev@db.apache.org>
>>>> Subject: Automatically generated POM for JDO (Maven 1 project)
>>>> Reply-To: jdo-dev@db.apache.org
>>>>
>>>> Hi,
>>>>
>>>> Can you please take a look at this issue? And reply to the jdo-dev
>>>> alias since we're not subscribed to maven users.
>>>>
>>>> Thanks,
>>>>
>>>> Craig
>>>>
>>>> M2 pom is incorrect, result in problems with transitive dependencies
>>>> --------------------------------------------------------------------
>>>>
>>>>              Key: JDO-612
>>>>              URL: https://issues.apache.org/jira/browse/JDO-612
>>>>          Project: JDO
>>>>       Issue Type: Bug
>>>>       Components: api2
>>>>         Reporter: Andy Jefferson
>>>>          Fix For: JDO 2 maintenance release 3
>>>>
>>>> Craig L Russell
>>>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>>> P.S. A good JDO? O, Gasp!
>>>>
>>>
>>> Craig L Russell
>>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>> P.S. A good JDO? O, Gasp!
>>>
>
> Craig L Russell
> Architect, Sun Java Enterprise System http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>