I know, but I cannot change the real world, this is how it gets supplied
to me, I can probably over time get them (those that create it) to
change it for me, but not now..
Wayne Fay skrev:
Different files (contents) with the same name is just a recipe for disaster.
Wayne
On 11/13/07,
quick recap..
Hi there, first some history :-)
I'm currently using maven 1.0.3 (yes, I know it is old, but it works for
me) and we are currently switching from cvs to subversion. Along with
this switch from cvs to subversion we are also going to try to switch
from our old maven to maven 2
I'd really (really really) try not to mess with the maven versioning - it's
a recipe for having to custom write loads of stuff, and it really is pretty
fundamental to the operation of maven. Without it, I'm not sure there's much
reason to change if it's currently working...
That said... Is there
I'm not sure what you mean by messing with maven versioning
since what I basicly want is to have different local repositories for
different projects without having to create a settings.xml for each
project..
that would take care of our immediate problem and in time we could start
using maven
Sure, but by doing that you're effectively trying to dodge the bullet of
having correct versions for artifacts, which isn't really what m2 is
designed to do.
It's quite common to have 'unversioned' 3rd party jars. Best solution is to
version them yourself, and deploy them somewhere locally -
Sounds like you might want to look into classifiers -- then your
artifacts would use classifierwebsite1/classifier and the naming
of the files etc would indicate which website the code was for, but it
would all go into the same Maven2 repo.
Wayne
On 11/13/07, Nigel Magnay [EMAIL PROTECTED]
of course, that is what is going to happen IN TIME, but right now it is
not the only sollution to this right now is to create different users
for each webapplication, that way the users settings.xml can be different..
is there some parameter I can add to the mvn command line to force it to
read a
how does that solve the problem where I got 3:rd party jar files name
for example project.jar which contains different versions depending on
my website?
Wayne Fay skrev:
Sounds like you might want to look into classifiers -- then your
artifacts would use classifierwebsite1/classifier and the
Try mvn -h. There's a parameter you should look at, -s.
Wayne
On 11/13/07, Christian Andersson [EMAIL PROTECTED] wrote:
of course, that is what is going to happen IN TIME, but right now it is
not the only sollution to this right now is to create different users
for each webapplication, that
Different files (contents) with the same name is just a recipe for disaster.
Wayne
On 11/13/07, Christian Andersson [EMAIL PROTECTED] wrote:
how does that solve the problem where I got 3:rd party jar files name
for example project.jar which contains different versions depending on
my website?
10 matches
Mail list logo