> Seriously, just get over it and run a repository manager.
Ok, will do :)
Thanks for your help guys!
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
2009/4/21 Kogel, Jonck-van-der :
>
>>> Sounds right; system scoped stuff are supposed to be provided by the
>>> JVM etc. so they shouldn't be any need for the manifest to point them
> out.
>
>>Also to expand a bit; if you intent to bundle those jars with your app
> use the default (compile) scope a
Graham Leggett wrote:
> The core reason is that it's virtually guaranteed that someone else, on
> a different machine, will want to build you code, and if the jars are on
> a shared repository (public or private, maven does care), then this is
> trivial and automatic.
you == your
does == doesn't
Kogel, Jonck-van-der wrote:
> Ok, allow me to rephrase :) I'm struggling with some proprietary (IBM,
> Oracle, etc..) jars that I need to get added to my manifest class path.
> I don't want to do that manually obviously. When I add the proprietary
> jars to my pom and set their scope to default l
>> Sounds right; system scoped stuff are supposed to be provided by the
>> JVM etc. so they shouldn't be any need for the manifest to point them
out.
>Also to expand a bit; if you intent to bundle those jars with your app
use the default (compile) scope and if
>you expect something like a servl
Manos Batsis wrote:
Kogel, Jonck-van-der wrote:
I'm trying to get Maven to correctly set my class path entry in the Jar
manifest file. It's all working as it should except for my system scoped
jars, these get excluded from the manifests class path for some reason.
Sounds right; system scoped s
Kogel, Jonck-van-der wrote:
I'm trying to get Maven to correctly set my class path entry in the Jar
manifest file. It's all working as it should except for my system scoped
jars, these get excluded from the manifests class path for some reason.
Sounds right; system scoped stuff are supposed to
Hi,
I'm trying to get Maven to correctly set my class path entry in the Jar
manifest file. It's all working as it should except for my system scoped
jars, these get excluded from the manifests class path for some reason.
I have several system scoped dependencies as such:
com.ibm.db2
db2jcc
1.