jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-678) Invalid maven2 pom for jackrabbit 1.1 in the ibiblio repository
Date Sat, 16 Dec 2006 17:09:22 GMT
     [ http://issues.apache.org/jira/browse/JCR-678?page=all ]

Jukka Zitting resolved JCR-678.
-------------------------------

    Resolution: Won't Fix
      Assignee: Jukka Zitting

The Jackrabbit artifacts so far have been deployed primary to the Maven 1 repository, and
the Maven 2 POMs have been automatically converted from the Maven 1 POMs. Thus the Maven 2
POMs are not fully accurate.

I'm resolving this as Won't Fix since Jackrabbit 1.2 will fix this by being primarily based
on Maven 2 and there is a workaround by overriding the dependencies locally until Jackrabbit
1.2 is available. I believe it is also the policy of the Maven repository to prefer releasing
a new version instead of modifying an existing artifact.

> Invalid maven2 pom for jackrabbit 1.1 in the ibiblio repository
> ---------------------------------------------------------------
>
>                 Key: JCR-678
>                 URL: http://issues.apache.org/jira/browse/JCR-678
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 1.1
>            Reporter: Mike Bowler
>         Assigned To: Jukka Zitting
>
> The maven2 pom that is in the ibiblio repository is invalid as it points to dependencies
that don't exist.  The file is http://www.ibiblio.org/maven2/org/apache/jackrabbit/jackrabbit-jcr-server/1.1/jackrabbit-jcr-server-1.1.pom
> The specific entries are 
>     <dependency>
>       <groupId>org.apache.jackrabbit</groupId>
>       <artifactId>jackrabbit-jcr-commons</artifactId>
>       <version>${jackrabbit.build.version.jackrabbit}</version>
>     </dependency>
>     <dependency>
>       <groupId>jsr170</groupId>
>       <artifactId>jcr</artifactId>
>       <version>${jackrabbit.build.version.jcr}</version>
>     </dependency>
> Neither one of these can be loaded by maven2.  I hacked my local copy of the pom as shown
below and this appeared to fix the dependency issues.  I'm not sure, however, if these are
the correct values that should be used.
>     <dependency>
>       <groupId>org.apache.jackrabbit</groupId>
>       <artifactId>jackrabbit-jcr-commons</artifactId>
>       <version>${project.version}</version>
>     </dependency>
>     <dependency>
>       <groupId>javax/jcr</groupId>
>       <artifactId>jcr</artifactId>
>       <version>1.0</version>
>     </dependency>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message