Even thought this works I do not like this solution at all. It is more a workaround 
that a good solution. In my project I am going to use JOTM and it does not look like 
that in the near future this is added to the repository. But I also do not want the 
user to hassle to download JOTM, install all the archives into the right directory, 
and rename them appropriately in order to make it work with my project because they 
just would skip my project.

I think it would be much more clear to developers and users that the location of some 
artifacts are on the local file system outside of the repository but still allows the 
developer to take advantages of all the possibilities of the POM dependencies like 
properties. Maven will never be able to host all projects and therefore it should 
support local artifacts.

-Andy

-----Original Message-----
From: Carlos Sanchez [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 09, 2004 11:12 AM
To: 'Maven Developers List'
Subject: RE: Adding dependencies places in a project-local directory

Hi,

Don't you use the jar override mechanism?
http://maven.apache.org/reference/user-guide.html#Overriding_Stated_Dependen
cies

Regards

Carlos Sanchez
A Coru�a, Spain

Oness Project
http://oness.sourceforge.net
 

> -----Original Message-----
> From: Andreas Schaefer [mailto:[EMAIL PROTECTED] 
> Sent: Monday, August 09, 2004 8:05 PM
> To: [EMAIL PROTECTED]
> Subject: Adding dependencies places in a project-local directory
> 
> Hi Geeks
>  
> I just want to discuss this before adding it as an 
> enhancement to the project.
>  
> Problem:
> Adding project level archives that I want to distribute with 
> the project and which are not available in the remote 
> repository like JOTM, JAXB etc through the POM dependencies.
>  
> Proposed Solution:
> Adding a flag telling Maven to load the archive from a given URL:
>  
> <dependencies>
>             <dependency>
>                         <groupId>test</groupId>
>                         <artifactId>mytest</artifactId>
>                         <version>1.2</version>
>                         <localCache>file:./lib</localCache>
>             </dependency>
> </dependencies>
>  
> Maven would then try to load 'mytest-1.0.jar' from './lib/test/jars/'
> directory.
>  
> So far I had to add this archives manually by using 
> 'maven:addPath' but I think that declaring it in the POM 
> would make it clearer to the user and would avoid to hassle 
> for the user to place it manually into the local repository.
>  
> What do you think?
>  
> -Andy
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to