You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by matthewadams <ma...@yahoo.com> on 2007/01/05 20:55:00 UTC

Using version range fails build, but exact version works

Hi all,

I'm using Maven 2.0.4 and the maven-antrun-plugin, and I express a
dependency on a version of an artifact in the plugin.  If I use an exact
version number for that artifact, Maven2 succeeds.  If I change the version
number from an exact version to a version range, Maven fails to resolve the
artifact.

More specifics:

My <project> uses the version range string successfully:
<project>
    ...
    <dependencies>
        <dependency>
            <groupId>com.xcalia</groupId>
            <artifactId>xic</artifactId>
            <version>[4.3.1-1250,)</version>
        </dependency>
        ...
    </dependencies>
    ...

When I use the same dependency in the maven-antrun-plugin, Maven fails to
resolve the artifact.  Here's my <plugin> element:
            <plugin>
                <artifactId>maven-antrun-plugin</artifactId>
                <executions>
                    <execution>
                        <id>enhance-and-create-database</id>
                        <phase>process-classes</phase>
                        <configuration>
                            <tasks>
                                <ant antfile="enhance.mvn.ant.xml"
dir="${basedir}" inheritAll="true" inheritRefs="true"/>
                            </tasks>
                        </configuration>
                        <goals>
                            <goal>run</goal>
                        </goals>
                    </execution>
                </executions>
                <dependencies>
                    <dependency>
                        <groupId>com.xcalia</groupId>
                        <artifactId>xic</artifactId>
<!-- USING VERSION RANGE HERE CAUSES FAILURE TO RESOLVE ARTIFACT -->
                        <version>[4.3.1-1250,)</version>
                    </dependency>
                </dependencies>
            </plugin>

How do I get this to work?

Thanks in advance,
Matthew
-- 
View this message in context: http://www.nabble.com/Using-version-range-fails-build%2C-but-exact-version-works-tf2927616s177.html#a8184722
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Using version range fails build, but exact version works

Posted by matthewadams <ma...@yahoo.com>.
Thanks, Dawn!  I filed it already:  http://jira.codehaus.org/browse/MNG-2742

I sure hope it's not me using a bad configuration!  Anyone see anything
wrong with it?

--matthew


dawn.angelito wrote:
> 
> Hi,
> 
> Not sure if this one's a bug because it should be working. However, you
> may file an issue to: http://jira.codehaus.org/browse/MNG for this to be
> fixed.
> 
> Dawn
> 
> 
> matthewadams wrote:
>> 
>> Hi all,
>> 
>> I'm using Maven 2.0.4 and the maven-antrun-plugin, and I express a
>> dependency on a version of an artifact in the plugin.  If I use an exact
>> version number for that artifact, Maven2 succeeds.  If I change the
>> version number from an exact version to a version range, Maven fails to
>> resolve the artifact.
>> 
>> More specifics:
>> 
>> My <project> uses the version range string successfully:
>> <project>
>>     ...
>>     <dependencies>
>>         <dependency>
>>             <groupId>com.xcalia</groupId>
>>             <artifactId>xic</artifactId>
>>             <version>[4.3.1-1250,)</version>
>>         </dependency>
>>         ...
>>     </dependencies>
>>     ...
>> 
>> When I use the same dependency in the maven-antrun-plugin, Maven fails to
>> resolve the artifact.  Here's my <plugin> element:
>>             <plugin>
>>                 <artifactId>maven-antrun-plugin</artifactId>
>>                 <executions>
>>                     <execution>
>>                         <id>enhance-and-create-database</id>
>>                         <phase>process-classes</phase>
>>                         <configuration>
>>                             <tasks>
>>                                 <ant antfile="enhance.mvn.ant.xml"
>> dir="${basedir}" inheritAll="true" inheritRefs="true"/>
>>                             </tasks>
>>                         </configuration>
>>                         <goals>
>>                             <goal>run</goal>
>>                         </goals>
>>                     </execution>
>>                 </executions>
>>                 <dependencies>
>>                     <dependency>
>>                         <groupId>com.xcalia</groupId>
>>                         <artifactId>xic</artifactId>
>> <!-- USING VERSION RANGE HERE CAUSES FAILURE TO RESOLVE ARTIFACT -->
>>                         <version>[4.3.1-1250,)</version>
>>                     </dependency>
>>                 </dependencies>
>>             </plugin>
>> 
>> How do I get this to work?
>> 
>> Thanks in advance,
>> Matthew
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Using-version-range-fails-build%2C-but-exact-version-works-tf2927616s177.html#a8222556
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Using version range fails build, but exact version works

Posted by "dawn.angelito" <da...@simulalabs.com>.
Hi,

Not sure if this one's a bug because it should be working. However, you may
file an issue to: http://jira.codehaus.org/browse/MNG for this to be fixed.

Dawn


matthewadams wrote:
> 
> Hi all,
> 
> I'm using Maven 2.0.4 and the maven-antrun-plugin, and I express a
> dependency on a version of an artifact in the plugin.  If I use an exact
> version number for that artifact, Maven2 succeeds.  If I change the
> version number from an exact version to a version range, Maven fails to
> resolve the artifact.
> 
> More specifics:
> 
> My <project> uses the version range string successfully:
> <project>
>     ...
>     <dependencies>
>         <dependency>
>             <groupId>com.xcalia</groupId>
>             <artifactId>xic</artifactId>
>             <version>[4.3.1-1250,)</version>
>         </dependency>
>         ...
>     </dependencies>
>     ...
> 
> When I use the same dependency in the maven-antrun-plugin, Maven fails to
> resolve the artifact.  Here's my <plugin> element:
>             <plugin>
>                 <artifactId>maven-antrun-plugin</artifactId>
>                 <executions>
>                     <execution>
>                         <id>enhance-and-create-database</id>
>                         <phase>process-classes</phase>
>                         <configuration>
>                             <tasks>
>                                 <ant antfile="enhance.mvn.ant.xml"
> dir="${basedir}" inheritAll="true" inheritRefs="true"/>
>                             </tasks>
>                         </configuration>
>                         <goals>
>                             <goal>run</goal>
>                         </goals>
>                     </execution>
>                 </executions>
>                 <dependencies>
>                     <dependency>
>                         <groupId>com.xcalia</groupId>
>                         <artifactId>xic</artifactId>
> <!-- USING VERSION RANGE HERE CAUSES FAILURE TO RESOLVE ARTIFACT -->
>                         <version>[4.3.1-1250,)</version>
>                     </dependency>
>                 </dependencies>
>             </plugin>
> 
> How do I get this to work?
> 
> Thanks in advance,
> Matthew
> 

-- 
View this message in context: http://www.nabble.com/Using-version-range-fails-build%2C-but-exact-version-works-tf2927616s177.html#a8212112
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org