Howard, sounds grear. I'll do that for the quick shot.
> "The version element can just have an arbitray value > like ???. You can later append this file into project.xml." What exactly does that mean? I can just put '???' to version, 'xyz' to id and the jar name to be looked up will be 'xyz.jar' not 'xyz-???.jar', right? Mariano On Wed, 2002-10-09 at 18:23, Howard Lin wrote: > Assuming you have a lib directory containing all the dependent jars, you can write a >shell script or Perl script to > 1) loop through all jar file and > 2) create dependencies tags and output to a file. You can use the jar file name as >the value for id and jar element. The version element can just have an arbitray value > like ???. You can later append this file into project.xml. > 3) mkdir on the $MAVEN_HOME/repositary/<jar_file_name>/jars and copy jar file there. > > Howard Lin > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, October 09, 2002 11:55 AM > > To: Turbine Maven Users List > > Subject: Re: project.xml how to specify needed jars? > > > > > > Hi, > > > > sorry if I sounded like I don't like the ideas behind it. I > > do appreciate > > the way dependencies are specified and used. I'll absolutly > > give it a shot on > > the next project, but currently we have almost 2000 classes, > > more than 50 > > jar files and the project is already a product. Hence we > > cannot just change > > something anymore and throw our ant build process away to toy > > around. Btw. We > > are not even the build anymore. It is done by another > > departement (the QA > > people) since we moved to production. > > > > Anyway. My point is, that I don't have a week to get maven > > up and running > > to show to my boss what it would do, but a day. And I > > understood that a day > > is not enough. It would alone take a day to take all out jar > > files and to > > rename them, put them in a new directory structure etc. etc. > > > > I'll try to find a hack to put a classpath together by hand > > and to bring > > it in somehow or will go back to my boss and ask for toy time ... > > > > Mariano > > > > > On Wed, 2002-10-09 at 16:43, [EMAIL PROTECTED] wrote: > > > > Hi Peter, > > > > > > > > thanks very much for caring. > > > > > > > > > you can use maven with quite a lot of layouts, just specify your > > > > > dependencies (so it will not look into your lib/ > > folder, you have to > > > > > move or download your jars to the local repository) and > > specify the > > > > > source folder. > > > > That sounds interesting. If I do not specify the > > dependencies it looks > > > > below lib and includes all jars found there? In which lib > > does it look? > > > B > > > elow > > > > repository or project base directory? Would it care for nested > > > directorie > > > s? > > > > > > > > What do you mean by "quite a lot of layouts ... when using > > > dependencies > > > "? > > > > As far as I understood your mail by specifying > > dependencies I will limit > > > the > > > > possible file layout to <jarname>/jars/<version><jarname.jar> or > > > similar. > > > > This sounds like a great approach for a new project, but > > in the current > > > p > > > roject > > > > we are using the conventional approach dividing our 60 > > jar files into > > > > subdirectories below lib named something like, > > development, client, > > > serve > > > r, common > > > > etc. > > > What you do is to specify all the dependencies in the > > project.xml. Then, > > > you compile everything (someone please fill in here on > > maybe different > > > project.xml files per project), still with all .jars in one central > > > (local) repository. then, for the runtime environment to > > work, you make > > > a special goal in the maven.xml using the <copy-dep> goal > > that copies > > > every dependency into a specified dir (here, your lib dir). > > > One drawback, you have to explicitly state which deps shouldn't be > > > copied > > > <copy-deps excludes="id1, id2, id3..." toDir="PATH_TO_LIB"> > > > (maybe this is not quite right syntax, I get it better > > looking it up :) > > > > > > So, if you are using only one project.xml, you will have to > > have several > > > such tags, excluding different things. I think there is an include > > > attribute too, but does that exclude everything else? Look > > in the docs. > > > > > > I find maven really great in managing my projects, but then > > they aren't > > > so big, but it works probably great for that, too - the > > main part is to > > > set up the deps in the project.xml and to customize the > > build process > > > using the maven.xml. That is a pain first time, but after > > that you will > > > love it! > > > Then, using your own remote repository beside the default, you just > > > check out the project and build it. The needed deps are > > downloaded and > > > don't bloat your vcs down. And building, testing etc. is > > consistent for > > > everyone. > > > And don't forget - the big part of documentation (xdoc, > > javadoc, source > > > xdoc, checkstyle, activity etc) you get. > > > > > > /peter > > > > > > > > > > > Cheers, > > > > Mariano > > > > > > > > > > > > > On Wed, 2002-10-09 at 16:15, [EMAIL PROTECTED] wrote: > > > > > > Hi, > > > > > > > > > > > > I looked through the documentation, but haven't > > found the answer > > > to > > > my > > > > > > question. > > > > > > > > > > > > My question is how can I specify jar files needed > > at build time? I > > > > > looked > > > > > > at the jars tag element inside the build element and > > found that the > > > j > > > ar > > > > > > element seems to be what I was looking for. The > > schema says it is of > > > > > type String > > > > > > and I just specified an absolute path to a jar file > > there, but with > > > > > absolutely > > > > > > no effect to the compilation. > > > > > > > > > > > the name of the .jar file is actually derived from the id of the > > > > > dependency tag and the version (betteer to use version > > than the <jar> > > > > > tag). Then, it is looked for in your local repository, > > if it is not > > > > > there, in the remote repository (default www.ibiblio.org/maven - > > > browse > > > > > there to find the newest jars, if you are using some of them). > > > > > so > > > > > <dependency> > > > > > <id>log4j</id> > > > > > <version>1.2.6</version> > > > > > </dependency> > > > > > Would resolve to : log4j-1.2.6.jar. That is looked for in: > > > > > $MAVEN_HOME/repository/log4j/jars/log4j-1.2.6.jar, and > > if that not > > > > > exists, maven will attempt to download it from > > > > > http://www.ibiblio.org/maven/log4j/jars/log4j-1.2.6.jar. > > > > > > Is there any sample project.xml file? I read on the > > website that > > > th > > > e > > > > > > turbine projects are build with maven so I downloaded > > a couple of > > > the > > > m > > > > > (torque and > > > > > > turbine and something else I forgot), but haven't found a > > > project.xml > > > > > file > > > > > > in there. > > > > > Checking out the whole project from cvs, you should see the > > > project.xml > > > > > file in the top folder. > > > > > > > > > > > > Is there any other place to look for documentation > > besides the > > > gett > > > ing > > > > > > started and users guide (where I didn't find an answer to my > > > question > > > )? > > > > > > > > > > > > It is quite possible that I am missing the whole point about > > > maven. > > > Is > > > > > it > > > > > > targeted at new projects starting from the scratch to > > adhere special > > > > > rules on > > > > > > how the file system is layed out and the jars are stored? > > > > > > > > > > > you can use maven with quite a lot of layouts, just specify your > > > > > dependencies (so it will not look into your lib/ > > folder, you have to > > > > > move or download your jars to the local repository) and > > specify the > > > > > source folder. > > > > > > > > > > > > > > > > Would it be possible to just use the rendering mechanism of > > > jdepend > > > > > > without converting the whole project to maven?` > > > > > > > > > > > > Cheers, > > > > > > Mariano > > > > > > > > > > > > > > > > > > -- > > > > > > To unsubscribe, e-mail: > > > > > <mailto:[EMAIL PROTECTED]> > > > > > > For additional commands, e-mail: > > > > > <mailto:[EMAIL PROTECTED]> > > > > > /peter > > > > > > > > > > _____________________________________________________ > > > > > Gratis e-mail resten av livet p� www.yahoo.se/mail > > > > > Busenkelt! > > > > > > > > > > -- > > > > > To unsubscribe, e-mail: > > > > > <mailto:[EMAIL PROTECTED]> > > > > > For additional commands, e-mail: > > > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: > > > <mailto:turbine-maven-user-unsubscribe@jakarta. > > > apache.org> > > > > For additional commands, e-mail: > > > <mailto:turbine-maven-user-help@jakarta. > > > apache.org> > > > > > > > > > _____________________________________________________ > > > Gratis e-mail resten av livet p� www.yahoo.se/mail > > > Busenkelt! > > > > > > -- > > > To unsubscribe, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
