db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlos Sanchez" <car...@carlossanchez.eu>
Subject Re: Automatically generated POM for JDO (Maven 1 project)
Date Fri, 14 Nov 2008 18:04:46 GMT
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!
>
>

Mime
View raw message