If you are using Eclipse, this is allready supported by the maven-eclipse-plugin : project dependencies are set as workspace project dependencies in place of jars, so that you can code and test under eclipse with no jar to install.
I also use the sysdeo-tomcat-maven-plugin from mojo to avoid creation of a war to test webapp under Tomcat. Nicolas. 2008/5/16 BenDave <[EMAIL PROTECTED]>: > > Hi, > > I am working on 2 projects, one is Dependant on the other. The usual way of > dealing with this is to add a dependency to a jar file located in the > repository. This works fine but the source project (on which the target > project depends) is constantly evolving, as we are doing some iterative > development. The source and target project are modified at the same time. > Consequently i don't want to work off a jar file of the source project, > because generating jar files and deploying them to the repository takes too > long (only 20 seconds but it adds up when this is done dozens / hundreds of > times per day ). > I do not want to merge these two projects into one as the source is a > common > project and is being used by other projects too, I need these two projects > to be distinct. > > So the solution is to indicate to maven a source folder which the target > project depends on rather than a JAR file. > > Can this be achieved ? > > Thanks, > > -- > View this message in context: > http://www.nabble.com/Maven-2-Dependency-on-java-source-folder-rather-than-jar-file-tp17276237p17276237.html > Sent from the Maven - Users mailing list archive at Nabble.com. >
