I have now. http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-518
[EMAIL PROTECTED] wrote:
Has anyone raised this in Jira?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.multitask.com.au
Brian Ewins <[EMAIL PROTECTED]> wrote on
Has anyone raised this in Jira?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.multitask.com.au
Brian Ewins <[EMAIL PROTECTED]> wrote on 24/06/2003
01:17:09 AM:
>
>
> Michal Maczka wrote:
>
> > [...]
> >
> >>(or something like t
; internal
> > project at work, but not all dependencies are available
> on
> > ibiblio (some are not open source, etc.) Also it makes
> > sense for us to keep these jars in CVS, to make sure
> they
> > don't get lost, and just because "it works".
> >
>
Michal Maczka wrote:
[...]
(or something like that) - jelly should always use artifacts, not
dependencies, to construct paths. It doesnt stop you naming jars
whatever you like, if they are in the local repo. I had a look over the
broken plugins a while back and I think there was only one case w
[...]
>
> (or something like that) - jelly should always use artifacts, not
> dependencies, to construct paths. It doesnt stop you naming jars
> whatever you like, if they are in the local repo. I had a look over the
> broken plugins a while back and I think there was only one case where it
> wasn
[...]
> Those plugins are unnecessarily wrong though. The offending code in the
> war plugin:
>
>
>
>
>
>
>
>
> Should read:
>
>
>
>
>
>
>
dion gillard wrote:
Michal Maczka wrote:
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:
So basiclly they requ
Otto von Wachter wrote:
What I would like is to specify some "private" jar
dependencies that are stored in a lib dir. Is there a quick
hack that would allow me to do this? If it is, perhaps
documenting it would increase the adoption of maven among
users like me. If not would it be e
Michal Maczka wrote:
> So they just override version? Not paths?
> I am surly +1 for allowing overriding version.
> This is also a must from the perspective of "transitive dependencies"
> There must be some way of setting the preferred version or artifacts
> Even if they are not listed as depende
> -Original Message-
> From: dion gillard [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 23, 2003 5:35 AM
> To: [EMAIL PROTECTED]
> Subject: Re: private jar dependencies
>
> Michal Maczka wrote:
>
>
> > There is one more mean for realizing such s
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 overri
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" a
> -Original Message-
> From: Aslak Hellesøy [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 21, 2003 12:33 PM
> To: Maven Developers List
> Subject: Re: private jar dependencies
>
>
>
> >
> > We're doing this in the http://www.nanocontainer.o
We're doing this in the http://www.nanocontainer.org/ project. Have a
look at:
Oops, this example is from xdoclet2 and not nanocontainer. Oh well.
http://tinyurl.com/ew5l (look at the end of the 1st property)
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/xdoclet/xdoclet2/lib/
(this is our own
dependencies are available on
ibiblio (some are not open source, etc.) Also it makes
sense for us to keep these jars in CVS, to make sure they
don't get lost, and just because "it works".
What I would like is to specify some "private" jar
dependencies that are stored in a lib dir. I
l dependencies are available on
> ibiblio (some are not open source, etc.) Also it makes
> sense for us to keep these jars in CVS, to make sure they
> don't get lost, and just because "it works".
>
> What I would like is to specify some "private" jar
> dependenci
sense for us to keep these jars in CVS, to make sure they
don't get lost, and just because "it works".
What I would like is to specify some "private" jar
dependencies that are stored in a lib dir. Is there a quick
hack that would allow me to do this? If it is, perhaps
document
17 matches
Mail list logo
