You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by jsoula <js...@gmail.com> on 2008/07/24 16:05:07 UTC

Re: System dependencies as dependency management

I try the 2.0.10-RC2 and the pb disappear. Is there a regression in 
maven 2.0.9 fixed in 2.0.10? I don't find a related bug.

jsoula a écrit :
> Hello,
>
> I try to upgrade maven from 2.0.8 to 2.0.9. I have pb with a system 
> dependency:
> Here are the dependencies in a parent pom:
>   <dependencyManagement>
>           <dependency>
>               <groupId>com.sun</groupId>
>               <artifactId>tools</artifactId>
>               <version>1.4.2</version>
>               <scope>system</scope>
>               <systemPath>${java.home}/../lib/tools.jar</systemPath>
>           </dependency>

> And here are the declaration in child pom:
        <dependency>
            <groupId>com.sun</groupId>
            <artifactId>tools</artifactId>
        </dependency>
> When i try to compile a child project of this pom, i have this error:
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) com.sun:tools:jar:1.4.2
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
>     mvn install:install-file -DgroupId=com.sun -DartifactId=tools 
> -Dversion=1.4.2 -Dpackaging=jar -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file 
> there:
>     mvn deploy:deploy-file -DgroupId=com.sun -DartifactId=tools 
> -Dversion=1.4.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
> -DrepositoryId=[id]
>
> Path to dependency:
>       1) com.xxxxxxx:common:jar:2.1-SNAPSHOT
>       2) com.sun:tools:jar:1.4.2
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> com.xxxxxxx:common:jar:2.1-SNAPSHOT
>
> from the specified remote repositories:
> repository-snapshots
> repository-releases
>
>
> Is there a known bugs of this (i found nothing in JIRA) ? Or there is 
> a thing to do when i upgrade?
>
> Thanks for Help
>
> Jérémy SOULA
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>



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


RE: System dependencies as dependency management

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
It most likely has to do with the changes to when the properties are resolved.

-----Original Message-----
From: jsoula [mailto:jsoula.liste@gmail.com] 
Sent: Thursday, July 24, 2008 10:05 AM
To: Maven Users List; Maven Developers List
Subject: Re: System dependencies as dependency management

I try the 2.0.10-RC2 and the pb disappear. Is there a regression in 
maven 2.0.9 fixed in 2.0.10? I don't find a related bug.

jsoula a écrit :
> Hello,
>
> I try to upgrade maven from 2.0.8 to 2.0.9. I have pb with a system 
> dependency:
> Here are the dependencies in a parent pom:
>   <dependencyManagement>
>           <dependency>
>               <groupId>com.sun</groupId>
>               <artifactId>tools</artifactId>
>               <version>1.4.2</version>
>               <scope>system</scope>
>               <systemPath>${java.home}/../lib/tools.jar</systemPath>
>           </dependency>

> And here are the declaration in child pom:
        <dependency>
            <groupId>com.sun</groupId>
            <artifactId>tools</artifactId>
        </dependency>
> When i try to compile a child project of this pom, i have this error:
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) com.sun:tools:jar:1.4.2
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
>     mvn install:install-file -DgroupId=com.sun -DartifactId=tools 
> -Dversion=1.4.2 -Dpackaging=jar -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file 
> there:
>     mvn deploy:deploy-file -DgroupId=com.sun -DartifactId=tools 
> -Dversion=1.4.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
> -DrepositoryId=[id]
>
> Path to dependency:
>       1) com.xxxxxxx:common:jar:2.1-SNAPSHOT
>       2) com.sun:tools:jar:1.4.2
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> com.xxxxxxx:common:jar:2.1-SNAPSHOT
>
> from the specified remote repositories:
> repository-snapshots
> repository-releases
>
>
> Is there a known bugs of this (i found nothing in JIRA) ? Or there is 
> a thing to do when i upgrade?
>
> Thanks for Help
>
> Jérémy SOULA
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>



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


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


RE: System dependencies as dependency management

Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
It most likely has to do with the changes to when the properties are resolved.

-----Original Message-----
From: jsoula [mailto:jsoula.liste@gmail.com] 
Sent: Thursday, July 24, 2008 10:05 AM
To: Maven Users List; Maven Developers List
Subject: Re: System dependencies as dependency management

I try the 2.0.10-RC2 and the pb disappear. Is there a regression in 
maven 2.0.9 fixed in 2.0.10? I don't find a related bug.

jsoula a écrit :
> Hello,
>
> I try to upgrade maven from 2.0.8 to 2.0.9. I have pb with a system 
> dependency:
> Here are the dependencies in a parent pom:
>   <dependencyManagement>
>           <dependency>
>               <groupId>com.sun</groupId>
>               <artifactId>tools</artifactId>
>               <version>1.4.2</version>
>               <scope>system</scope>
>               <systemPath>${java.home}/../lib/tools.jar</systemPath>
>           </dependency>

> And here are the declaration in child pom:
        <dependency>
            <groupId>com.sun</groupId>
            <artifactId>tools</artifactId>
        </dependency>
> When i try to compile a child project of this pom, i have this error:
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) com.sun:tools:jar:1.4.2
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
>     mvn install:install-file -DgroupId=com.sun -DartifactId=tools 
> -Dversion=1.4.2 -Dpackaging=jar -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the file 
> there:
>     mvn deploy:deploy-file -DgroupId=com.sun -DartifactId=tools 
> -Dversion=1.4.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
> -DrepositoryId=[id]
>
> Path to dependency:
>       1) com.xxxxxxx:common:jar:2.1-SNAPSHOT
>       2) com.sun:tools:jar:1.4.2
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> com.xxxxxxx:common:jar:2.1-SNAPSHOT
>
> from the specified remote repositories:
> repository-snapshots
> repository-releases
>
>
> Is there a known bugs of this (i found nothing in JIRA) ? Or there is 
> a thing to do when i upgrade?
>
> Thanks for Help
>
> Jérémy SOULA
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>



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


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