OK, since I'm new to Maven (and Mevenide-Eclipse) here is what my setup is. I would appreciate help in Maven-izing this.
Current state of affairs is in Eclipse I have the following Java (Eclipse) projects (renamed): Common Webapp Framework EJB App1 App2 App3 Etc. The Common project contains a lib and reference directory. The Common/lib contains 3rd party jars e.g. from Sun, Apache, etc., and Common/reference contains jars that I have built from the other projects like Framework, EJB, etc. This is all version controlled (with Subversion) so that when I create a branch I don't need to check out the source code for every project, just the Common project containing the jars for reference. Assuming there is one Eclipse project for one Maven artifact, how do I setup multiproject configuration? When I'm working in a branch, I don't necessarily have or need all of the projects in my workspace, just a select few. Can my project override whatever is in the remote repository? Assuming that my Common project is now obsoleted by Maven's remote repository, where do I reference the jars that I need while I'm in my IDE? The Help documentation for Mevenide says that it does not currently support Eclipse project dependencies. How do I do that by hand? Mevenide has an auto-build feature. Does that replace Eclipse's default internal build system as I edit and save source files that would normally trigger a compile? For the Eclipse project, do I specify Eclipse project dependencies, or configure the dependencies in project.xml and rely on Mevenide's auto-build feature? We have web applications that have customized JSP's, image files, application configuration, etc. for each of our many customers. The Web application jar itself is compiled from a single source, but to create a distribution or WAR file I need to specify the location of where to get these customized files. Does that imply that I need a custom project.properties file for each webapp to deploy? Or can they all be configured in the one file and I can specify on the maven command line which customer I am deploying for? Thanks in advance for any help. - Simon -----Original Message----- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Friday, June 17, 2005 11:40 AM To: Maven Users List; Guillaume Lederrey Subject: Re: Remote repository version control Hi Simon, maven encourges not to store binary artifact to version control system, but to be placed in your remote repository (make sure to back it up regularly). Let's maven manages the artifacts for you. If you insist on using artifacts in your VCS, look up maven.jar.override settings. So that you can ask maven to skip the remote lookup but only at your local propriety place. -D On 6/17/05, Guillaume Lederrey <[EMAIL PROTECTED]> wrote: > On 6/17/05, Simon McClenahan <[EMAIL PROTECTED]> wrote: > > I am specifying a remote repository because the jar files I need are > > stored in my version control system, where I have checked them out into > > my local filesystem. I would have like to specify a relative path to the > > remote repository, but I don't think that's possible with a URL scheme. > > I have not attempted to setup a multiproject configuration in Maven yet, > > but what would be the best practice for version control of artifacts in > > a remote repository that is referenced locally? Maybe this is the > > complicated way of doing it. Should I be creating a remote repository to > > upload to on a shared resource (e.g. network drive) instead and not be > > concerned about version control? > > I would say that the cleanest way is to create a repository on a > shared resource. If you really want to include your dependencies in > your versionning tool, it probably makes sense only if they are > included with your project. So in this case, put them in your project > tree and copy them at the right place with a "maven.xml" goal. -------------------------- NOTE: This message and any included attachments are from HealthCom Partners, LLC and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
