On Sun, 2003-06-22 at 23:34, dion gillard wrote:
> Michal Maczka wrote:
> 
> 
> > There is one more mean for realizing such scenario which was not mentioned
> > here:
> > jar overriding mechanism (or more generally artifact overriding mechanism).
> > 
> > I am personally for dropping the jar overriding mechanism.
> > and for replacing them with such "fake remote repository"  as Aslak has
> > described.
> Big, big -1 on this. I have a real need for the jar override facility. 
> We have maven users who run common sql through db2. they each have their 
> own db2 release, and MUST use the jar file that corresponds to their db2 
>   install.

The override is absolutely necessary. You cannot do any sort of
integration build without it. My particular case is Tambora where I pull
in bits and pieces from all over the place and many of the bits have
conflicting versions. Now for me the version overriding would suffice so
we could definitely nudge people to use a repository structure. But
being able to override the version is crucial for integration.

> > This will make the implementation cleaner.
> And less functional.
> 
> > There is a lot of places in maven where the fact that artifact was overriden
> > is simply ignored.
> This is a bug and should be fixed. Before 1.0
> 
> > This feature probably is not used so often but surly plugins like
> > war, ear, eclipse are not aware of the fact that artifact can be overriden!
> > 
> > and what they do is something like:
> > 
> > 
> >        <j:if test="${dep.getProperty('war.bundle')=='true' and dep.type
> > =='jar' }">
> >           <ant:lib dir="${maven.repo.local}/${dep.artifactDirectory}/jars/">
> >             <ant:include name="${dep.artifact}"/>
> >           </ant:lib>
> >         </j:if>
> > 
> > So basiclly they require that artifact must be in local repository.
> Any artifact thats listed as a dependency MUST be available in the local 
> repository.
> 
> > I think that this assumption is correct and it is the idea of jar overriding
> > which is wrong.
> I think this assumption is correct, and that the plugins shouldn't 
> assume this format.
> 
> > Moreover there is no easy way of determining if artifact was overriden or
> > not (it is in maven-new, but that's different story)
> Is it needed?
-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


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

Reply via email to