Re: RMI in a normal J2SE app
Geoffrey,
You need to call the ant rmic task. I simply added the following to
maven.xml, so the rmic is performed after each java compile.
postGoal name=java:compile
ant:rmic
base=${maven.build.dest}
includes=com/xxx/yyy/Classname.class
/
/postGoal
HTH,
Al.
Digital Union UK
[EMAIL PROTECTED]
www.digitalunion.com
t: +44 (0) 1483 889482 m:+44 (0) 7713 631367 f: +44 (0) 1483 889450
The information in this email and in any attachment(s) is confidential. If
you are not the named addressee(s) or if you receive this email in error
then any distribution, copying or use of this communication or the
information in it is strictly prohibited.
While attachments are virus checked, Digital Union UK Limited does not
accept any liability in respect of any virus which is not detected.
Geoffrey [EMAIL PROTECTED]
Sent by: news [EMAIL PROTECTED]
03/04/2004 13:52
Please respond to
Maven Users List [EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
Subject
RMI in a normal J2SE app
Hi all,
Specs: Maven rc2, Sun SDK 1.4.2 (and IntelliJ 4)
How do I configure project.xml to automatically rmic my RMI classes?
Which target do I call?
Which target do I call to run my application?
Thanks for any and all help,
Geoffrey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
where to find reference for build.properties ?
Hi, I browsed the Maven Homepage but couldn't find a doc with complete reference for build.properties. Where can I find it? Regards Marc
Re: where to find reference for build.properties ?
Hi! Do you mean project.properties?? I don't think that there is complete reference.. Everybody can make new plugin to maven, and it would be quite hard to maintain that kind reference. Try googlen like maven site plugin properties. Artsi On Mon, 2004-04-05 at 12:34, Marc Lustig wrote: Hi, I browsed the Maven Homepage but couldn't find a doc with complete reference for build.properties. Where can I find it? Regards Marc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using Maven on a very large integration project - how far can Maven go?
Michael, I think your overall approch is on target. One of the things I have found easier when deploying to containers is to have Tomcat as part of CVS.. It gives you a lot more control over what the Tomcat environment looks like, isn't too large, and reduces variables. Also, as far as the merging of jars, anything you can do in Ant, you can do in Maven, as Maven supports all ant tasks. Here is an article that gives a simple example of calling the echo/ task from Ant in Maven: http://www.onjava.com/pub/a/onjava/2004/03/17/maven.html. Eric Pugh -Original Message- From: Michael Mattox [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 1:04 AM To: Maven Users List Subject: Using Maven on a very large integration project - how far can Maven go? I've used ANT on several projects in the past, and have had my eye on Maven for a year now. I am now working on a large project that is mostly integration. That is to say we are working with a few software editors (a webmail application and a chat application) to integrate them into our customers portal architecture. Each software editor is modifying their applications to support new requirements, and we're writing a relatively small amount of code to integrate them. For example, the webmail application has an API which uses HTTP to return XML data. We're writing a protocol adapter to exposure their API as a web service. We're also writing some protocol adapters that will be deployed on their servers. So far, I've set up a multi-project build for our source code. I created a common project, and then mail chat directories. Under each I have several projects for each application. I've found a lot of resources on doing this and it was relatively easy to set up and it's working great. From the top level I can do the multi-project build. My problem is I'm not sure how to proceed with the integration part using Maven. I have a couple needs: 1 - I need to deploy to the integration team our entire source code tree, along with the deliveries from our partners (the companies that make mail chat). The integration team is willing to install Maven, and they also use ANT. So my current thinking is to structure the tree like this: - extern (for deliveries from our partners) - mail - a standalone application - a webapp - chat - static HTML - a web app - a standalone application - our source tree - mail - a JAR to be deployed to the mail standalone app - a JAR to be deployed to the mail webapp - chat - a JAR to be deployed to the chat standalone app - a JAR to be deployed to the chat webapp - an EJB to be deployed to another server Does Maven have functionality to take the applications from our partners (in extern) and combine them with our JARS? Like copying all this to another top level directory, maybe install? I know I can do it with ANT, but I'm curious if Maven offers an added value here. 2 - The mail chat apps use WebSphere Tomcat, and databases Oracle MySQL. I'm currently working on install procedures. Using Tomcat for an example, should I put tomcat under the extern/chat tree? Or should integration install their own tomcat and then copy the files from the chat project to the appropriate tomcat directories? The integration team wants to do it like this, where they reassemble the parts themselves (using my maven project). That way they know what they have (official Tomcat release, etc.). On the other hand, the mail chat companies want to deliver a complete package that is tested and they know it works. For example, what if the mail application uses a modified Tomcat? In that case we'd have to use their Tomcat instead of installing a new one. This complicates the packaging a bit. Thank you for taking the time to read this long mail, and if you have any ideas please let me know. I've heard from a few people that Maven works great for simple JAR projects but it falls apart for complicated projects like this. I want to prove them wrong! In the worst case I can have Maven call ANT tasks. My goal is that the integration team gets our code from CVS and types a single command to build, test, and package our project. I think it's an aggressive goal but I'm certainly going to try. Michael - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
how to specify maven.repo.remote on a remote drive (win)
Hi, I am trying to build a maven-project that was created on Linux on a win-box. Specifically I'm running into trouble with this entry maven.repo.remote=file:/s/repository/maven/ On my win machine s is the remote drive. I tried to access it using various notations like maven.repo.remote=file:s:/repository/maven/ or maven.repo.remote=file:///s/repository/maven/ and also with backslash. But Maven doesn't appear to acquire the jars from the remote machine. Idea? Marc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using Maven on a very large integration project - how far can Maven go?
I think your overall approch is on target. One of the things I have found easier when deploying to containers is to have Tomcat as part of CVS.. It gives you a lot more control over what the Tomcat environment looks like, isn't too large, and reduces variables. I agree in principle. The problem is it's not practical to put WebSphere or Oracle in CVS. So what I was thinking was to divide the containers into two categories: - versioned in CVS - for unstable, lightweight containers only. For example tomcat. - an install procedure using official releases. This would be for Oracle, MySQL, WebSphere. Tomcat can fall into either category, and I prefer the second. But I'm open to suggestions. Also, as far as the merging of jars, anything you can do in Ant, you can do in Maven, as Maven supports all ant tasks. Here is an article that gives a simple example of calling the echo/ task from Ant in Maven: http://www.onjava.com/pub/a/onjava/2004/03/17/maven.html. This is a worst case, call the ANT target. But with Maven's Jelly scripts I wasn't sure if it'd be better to do something with ANT or Jelly. Thanks, Michael -- This E-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return E-mail. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using Maven on a very large integration project - how far can Maven go?
-Original Message- From: Michael MATTOX [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 11:59 AM To: [EMAIL PROTECTED]; Maven Users List Subject: RE: Using Maven on a very large integration project - how far can Maven go? I think your overall approch is on target. One of the things I have found easier when deploying to containers is to have Tomcat as part of CVS.. It gives you a lot more control over what the Tomcat environment looks like, isn't too large, and reduces variables. I agree in principle. The problem is it's not practical to put WebSphere or Oracle in CVS. So what I was thinking was to divide the containers into two categories: - versioned in CVS - for unstable, lightweight containers only. For example tomcat. - an install procedure using official releases. This would be for Oracle, MySQL, WebSphere. Tomcat can fall into either category, and I prefer the second. But I'm open to suggestions. Also, as far as the merging of jars, anything you can do in Ant, you can do in Maven, as Maven supports all ant tasks. Here is an article that gives a simple example of calling the echo/ task from Ant in Maven: http://www.onjava.com/pub/a/onjava/2004/03/17/maven.html. This is a worst case, call the ANT target. But with Maven's Jelly scripts I wasn't sure if it'd be better to do something with ANT or Jelly. I am using quite different technique. I keep Tomcat and such as zips in my maven repository. For example in case of Tomcat I have removed most of the files and I keep only those files which are really needed to run it in a zip file in local repository. Then I have POM fragments like: dependencies dependency groupIdfoo/groupId artifactIdfoo-webapp/artifactId version1.0/version typewar/type /dependency dependency groupIdfoo/groupId artifactIdfoo-configuration-for-node-X/artifactId version1.0/version typezip/type /dependency dependency groupIdtomcat/groupId artifactIdtomcat/artifactId version4.1.27/version typezip/type /dependency dependency groupIdtomcat/groupId artifactIdtomact-admin/artifactId version4.1.27/version typewar/type /dependency /dependencies and plugins which are creating application which are a merger of tomcat zip/wars (possibly many wars)/zip with configuration settings. As the result I get another zip (ready to use application) which is zipped and installed in my local repository. Using this technique I am for example easily enable to use different version of tomcat (just need to edit my POM to change it) or have many configuration (for many customers) of the same application. But I am _always_ using local repository for keeping and exchaing artifacts between projects. Even artifacts like tomcat (zip) or configuration files. I have created maven zip plugin which puts to zip archive all the files declared as resources in POM and which is also able to merge many zips into one. I am also using my own version of war plugin in which I can declare dependencies on other wars and just replace some configuration files. So I have one base war file and couple of its mutations for various environments: for testing (e.g. against different databases), for various production environment (in my case we use the same wars with different configuration setting for different customers). Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Splitting project into multiple projects
Hello, I'd like to split a project into several sub-projects (basically a kernel and different implementations for it, which depend on the kernel). The project itself is already using Maven. What I'd like to know is what is the best way to organize this: - Correct build order - Deploying JARs - Common checkstyle rules - Organization of testcases (some tests are generic because they only require the interfaces but can only be invoked if the implementation is available) Thanks in advance, Boris Böhlen -- Dipl.-Inform. Boris Boehlen [EMAIL PROTECTED] RWTH Aachen University Department of Computer Science III phone: +49 (2 41) 80 21 312 Ahornstrasse 55, 52074 Aachen fax: +49 (2 41) 80 22 218 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using Maven on a very large integration project - how far can Maven go?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 3:10 PM To: Maven Users List Subject: Re: Using Maven on a very large integration project - how far can Maven go? That is really cool. Very useful. Are you going to push through the zip plugin and war plugin changes? I haven't been thinking about that but if somebody will find it useful I can certainly do that. I should not have any problems with creating zip plugin. It's bit more difficult with war plugin but doable. The idea is that when war plugins finds any dependency of type war it should un-war it (unzip :) and use files which were stored there as sources for building new war file. I have it working but it's rather a quick hack then release quality. But I can try to improve it if somebody will be interested. Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Maven on a very large integration project - how far can Maven go?
Maczka Michal wrote: I haven't been thinking about that but if somebody will find it useful I can certainly do that. I should not have any problems with creating zip plugin. It's bit more difficult with war plugin but doable. The idea is that when war plugins finds any dependency of type war it should un-war it (unzip :) and use files which were stored there as sources for building new war file. I have it working but it's rather a quick hack then release quality. But I can try to improve it if somebody will be interested. Hmmm, maybe something like this: if war plugin finds 'war' dependency then un-war it and merge content of dependency war into created war. At least web.xml files should be merged together, probably more descriptor files too - but this may be done as postGoals. Michal Tomek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to implement a nightly build system in maven
I am a maven beginner. We use maven to build and manage our project. Right now we want to build a nightly build system that will automatically build, deploy, run all the tests of the project at least once a day. Can anyone give me some ideas for it? I use CruiseControl for this (http://cruisecontrol.sourceforge.net/). It has acceptable Maven support. My only real problem with this is that I want the daily build to happen whether it needs to or not, and the CruiseControl philosophy seems to be that things should only be built when code has change. I sort of hacked around this by configuring the list of files CruiseControl looks at to see if any changes happened to look at the CruiseControl's own log file, which changes when the check for changes starts, thus guaranteeing that the build's always happen. A typical CruiseControl script for us looks like this (note that we use Perforce for source control; the CVS config is slightly different). This script compiles a project called dispatcher. Note that the goal lists contain a lot of goals from a custom plugin, but you can put whatever goals you want: cruisecontrol !-- *** dispatcher *** -- project name=dispatcher !-- Events that get executed all of the time when a build is started, before the actual build begins -- bootstrappers currentbuildstatusbootstrapper file=logs/current-dispatcher.txt/ p4bootstrapper path=//depot/dispatcher/main/project.xml p4port=p4depot.tagaudit.com:1666 p4user=p4daemon p4client=linux-cruise/ p4bootstrapper path=//depot/dispatcher/main/project.properties p4port=p4depot.tagaudit.com:1666 p4user=p4daemon p4client=linux-cruise/ p4bootstrapper path=//depot/dispatcher/main/maven.xml p4port=p4.domain.com:1666 p4user=p4daemon p4client=linux-cruise/ /bootstrappers !-- A set of data to look at to see if there have been changes and, therefore, a new build is required. -- modificationset quietperiod=0 !-- Use the always changing log to force a build -- filesystem folder=cruisecontrol.log/ p4 port=p4.domain.com:1666 user=p4daemon client=linux-cruise view=//depot/dispatcher/main/.../ /modificationset !-- The build process. Interval is in seconds. -- schedule interval=300 maven time=2300 mavenscript=/opt/maven/bin/maven projectfile=/home/build/cruise/checkout/dispatcher/main/project.xml goal=tag:bad-build-icon tag:checkout tag:clean|tag:build|tag:site tag:good-build-icon/ /schedule !-- Output -- publishers currentbuildstatuspublisher file=logs/current-dispatcher.txt/ email buildresultsurl=http://build.tagaudit.com:8080/cruisecontrol/buildresults/d ispatcher/ defaultsuffix=@tagaudit.com mailhost=mail reportsuccess=always returnaddress=lward subjectprefix=[BUILD] always address=lward/ failure address=lward/ success address=lward/ /email /publishers /project /cruisecontrol - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to implement a nightly build system in maven
On Mon, 2004-04-05 at 10:15, Lester Ward wrote: My only real problem with this is that I want the daily build to happen whether it needs to or not Out of curiosity, why? What's the point of tying up CPU cycles when you know the build products are going to be the same? -- Craig S. Cottingham [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: How to implement a nightly build system in maven
Hello, As a beginner as well I have tried to use Anthill OS, though it lacks support for calling Maven goals directly (in the Open Source version). Instead I have written a little build script that executes Maven in an Ant exec task. Has anyone else utilised Anthill with Maven before? Someone found a more elegant way perhaps? Regards, Christian Nill I am a maven beginner. We use maven to build and manage our project. Right now we want to build a nightly build system that will automatically build, deploy, run all the tests of the project at least once a day. Can anyone give me some ideas for it? Are there any examples available which I can have a look? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Newbe: Maven vs AntHill
I am new to Maven. Can anyone tell me how Maven compares to AntHill OS and/or AntHill Pro? Thanks, David Robison -- David R Robison Open Roads Consulting, Inc. 708 S. Battlefield Blvd., Chesapeake, VA 23322 phone: (757) 546-3401 e-mail: [EMAIL PROTECTED] web: http://openroadsconsulting.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to implement a nightly build system in maven
Even in the pro version you need to wrap the maven call with an ant target since anthill pro doesn't look for the various maven return codes it only looks for 1 or a 0 based on success or failure. I am using the java task instead of the exec task. -Scott -Original Message- From: CNI [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 12:17 PM To: Maven Users List Subject: AW: How to implement a nightly build system in maven Hello, As a beginner as well I have tried to use Anthill OS, though it lacks support for calling Maven goals directly (in the Open Source version). Instead I have written a little build script that executes Maven in an Ant exec task. Has anyone else utilised Anthill with Maven before? Someone found a more elegant way perhaps? Regards, Christian Nill I am a maven beginner. We use maven to build and manage our project. Right now we want to build a nightly build system that will automatically build, deploy, run all the tests of the project at least once a day. Can anyone give me some ideas for it? Are there any examples available which I can have a look? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: How to implement a nightly build system in maven
http://gump.apache.org/ Have you looked at gump? CNI wrote: Hello, As a beginner as well I have tried to use Anthill OS, though it lacks support for calling Maven goals directly (in the Open Source version). Instead I have written a little build script that executes Maven in an Ant exec task. Has anyone else utilised Anthill with Maven before? Someone found a more elegant way perhaps? Regards, Christian Nill I am a maven beginner. We use maven to build and manage our project. Right now we want to build a nightly build system that will automatically build, deploy, run all the tests of the project at least once a day. Can anyone give me some ideas for it? Are there any examples available which I can have a look? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: How to implement a nightly build system in maven
Alright, that answers the question wheter it would be worth purchasing the Pro-version ;-) Does using the java task actually give you more control over Maven than just plainly using the exec task? What do you use the various return codes for (I am also currently only looking for 0 or !0)? I seriously hope these questions aren't just too naiv... Christian -Ursprüngliche Nachricht- Von: Nelson, Scott (MAN-Corporate) [mailto:[EMAIL PROTECTED] Gesendet: Montag, 5. April 2004 18:42 An: 'Maven Users List' Betreff: RE: How to implement a nightly build system in maven Even in the pro version you need to wrap the maven call with an ant target since anthill pro doesn't look for the various maven return codes it only looks for 1 or a 0 based on success or failure. I am using the java task instead of the exec task. -Scott -Original Message- From: CNI [mailto:[EMAIL PROTECTED] Sent: Monday, April 05, 2004 12:17 PM To: Maven Users List Subject: AW: How to implement a nightly build system in maven Hello, As a beginner as well I have tried to use Anthill OS, though it lacks support for calling Maven goals directly (in the Open Source version). Instead I have written a little build script that executes Maven in an Ant exec task. Has anyone else utilised Anthill with Maven before? Someone found a more elegant way perhaps? Regards, Christian Nill I am a maven beginner. We use maven to build and manage our project. Right now we want to build a nightly build system that will automatically build, deploy, run all the tests of the project at least once a day. Can anyone give me some ideas for it? Are there any examples available which I can have a look? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbe: Maven vs AntHill
David R Robison wrote: I am new to Maven. Can anyone tell me how Maven compares to AntHill OS and/or AntHill Pro? Thanks, David Robison No relationship other than one can schedule Maven based builds using Anthill. Maven is a build tool that extends the capabilities of Ant in new and interesting ways. Anthill is build scheduling tool. One uses Anthill to fetch changed sources from a source repository and initiate builds. Anthill OS can be tricked into running Maven based builds by using a simple Ant script that launches Maven. Anthill Pro can, I believe, invoke Maven directly. I am using Anthill OS to run my Maven based builds. -- Erik Husby Team Lead for Software Quality Automation Broad Institute Rm. 2192 320 Charles St Cambridge, MA 02141-2023 mobile: 781.354.6669, office: 617.258.9227, [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbe: Maven vs AntHill
Can Maven fetch changed sources from a source repository during a build? David Erik Husby wrote: David R Robison wrote: I am new to Maven. Can anyone tell me how Maven compares to AntHill OS and/or AntHill Pro? Thanks, David Robison No relationship other than one can schedule Maven based builds using Anthill. Maven is a build tool that extends the capabilities of Ant in new and interesting ways. Anthill is build scheduling tool. One uses Anthill to fetch changed sources from a source repository and initiate builds. Anthill OS can be tricked into running Maven based builds by using a simple Ant script that launches Maven. Anthill Pro can, I believe, invoke Maven directly. I am using Anthill OS to run my Maven based builds. -- David R Robison Open Roads Consulting, Inc. 708 S. Battlefield Blvd., Chesapeake, VA 23322 phone: (757) 546-3401 e-mail: [EMAIL PROTECTED] web: http://openroadsconsulting.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Newbe: Maven vs AntHill
scm:update-project will fetch changed source from CVS. So I would imagine you could put that into a build. We use Cruise Control here and we get maven do do all the heavy lifting. CC fetches one file (project.xml) and checks the repository for changes; if it finds them maven updates the project and builds it. -Original Message- From: David R Robison [mailto:[EMAIL PROTECTED] Sent: 05 April 2004 18:05 To: Maven Users List Subject: Re: Newbe: Maven vs AntHill Can Maven fetch changed sources from a source repository during a build? David Erik Husby wrote: David R Robison wrote: I am new to Maven. Can anyone tell me how Maven compares to AntHill OS and/or AntHill Pro? Thanks, David Robison No relationship other than one can schedule Maven based builds using Anthill. Maven is a build tool that extends the capabilities of Ant in new and interesting ways. Anthill is build scheduling tool. One uses Anthill to fetch changed sources from a source repository and initiate builds. Anthill OS can be tricked into running Maven based builds by using a simple Ant script that launches Maven. Anthill Pro can, I believe, invoke Maven directly. I am using Anthill OS to run my Maven based builds. -- David R Robison Open Roads Consulting, Inc. 708 S. Battlefield Blvd., Chesapeake, VA 23322 phone: (757) 546-3401 e-mail: [EMAIL PROTECTED] web: http://openroadsconsulting.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dependencies and the local repository
Forgive me for asking what must be a very basic question. I've searched the
Maven site and scoured the archives for this list and haven't found an
answer.
I have a simple java project defined in an Ant file. The dependencies for
my current project are in jars in the ${basedir}/lib directory. I've
configured Ant to include in the classpath whatever jars it finds in that
lib directory.
I'm trying to duplicate this functionality with Maven, and I've hit a
roadblock. I have jars that don't conform to Maven's idea of a standard
name. An example would be the mail.jar from Sun's site. I use it. I tried
a dependency entry in my project.xml as follows:
dependency
groupIdmail/groupID
artifactIdmail/artifactId
version1.3/version
jarmail.jar/jar
/dependency
I tried putting the jar in ${HOME}/.maven/repository/jars, but it wasn't
found. Then I tried to follow the format in the repository and made a
directory structure as follows:
$HOME/.maven/repository/mail/jars/mail.jar
That appears to work, but is that what Maven expects me to do for each jar
file? This seems like a lot of work for jars that will never be downloaded
from a remote repository anyway.
This all brings me to the fact that I don't grasp the remote repository
concept. Is there 1 remote repository and it's global to the world? I went
to http://www.imbiblio.org/maven and looked at the repository there. It
seems small if it's supposed to be the global parking spot for Maven
projects world-wide.
Please forgive my misunderstanding,
Maury
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Dependencies and the local repository
That appears to work, but is that what Maven expects me to do for each jar file? The mail.jar (and a few others) are sort of special cases, as I understand it, because Sun does not license them for redistribution. You have to download it specifically from Sun and no one else is allowed to post it. Therefore, the mail jar cannot be made available in the standard Maven repository. Is this stupid of Sun? Yes. Is this annoying for Maven users? Yes. For this and a number of other reasons, our company created our own Maven repository on our company intranet. This allows us to control the repository ourselves and, since it is not public, put any jars we like on it (including commercial stuff). Not least, we can post our own internal jars for use by other projects within the company. Basically, this means that every project needs to override maven.repo.remote in its properties file, but that's pretty much as hard as it gets. The setup is pretty much just setting up an Apache box somewhere and throwing stuff into a directory. (We actually build the repository with a script from our source control system, but this is probably overkill for most companies.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbe: Maven vs AntHill
David R Robison [EMAIL PROTECTED] wrote: Can Maven fetch changed sources from a source repository during a build? David You could definitely make Maven do this. However, if you are wanting to use Maven with Anthill, you wouldn't want to do that. The way Anthill works is to pull everything out of the repository that you are going to build (either the tip of HEAD or branch, or a given tag), and then run the build on that. If you are using Anthill, you wouldn't want your build scripts to have anything to do with pulling stuff out of the repository - let Anthill do that for you before it invokes the build. Hope this helps, Chad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Dependencies and the local repository
-Original Message- From: Lester Ward [mailto:[EMAIL PROTECTED] For this and a number of other reasons, our company created our own Maven repository on our company intranet. This allows us to control the repository ourselves and, since it is not public, put any jars we like on it (including commercial stuff). Not least, we can post our own internal jars for use by other projects within the company. Thanks, Lester. I've got some learning to do, but this points me in the right direction. Maury - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
multiproject:site (plugin v1.2) fails to create a directory
Maven 1.0-RC2 (multiproject plugin v1.2) The multiproject:site goals was failing with following error: creation was not successful for an unknown reason After much looking around, I found the problem. One of the project.xml files was a missing id tag in a project XML. After adding the id tag to the project.xml, the goal succeeded! Paul Spencer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
