| Would the project build with maven alone, if it depends on another
| eclipse project?
Yes, because it's doesn't depends on a stand alone eclipse project it's
a subproject. (eclipse doesn't support subprojects so you must import
each subproject to a project in the workspace and set the dependencies
between them) For example, I'm working in a project called delfos and
the project layout is like this:
delfos
project.xml
qa
project.xml
src
client
project.xml
src
web
project.xml
commons
project.xml
In eclipse I use maven:reactor and the eclipse plugin to create the
.project and .classpath, and import the following subprojects to the
eclipse workspace:
delfos-commons
delfos-qa
delfos-client
delfos-web
The problem is that I didn't found a way to tell Maven that a dependency
is another project instead of a JAR file. (searching in the maven-users
mail list I found that a workaround to this is install the JARs in the
local repository and treat the dependencies like normal JAR files... but
this uncomfortable when you work in a IDE).
I would be nice to have something like this:
<dependencies>
<project>
<id>delfos-commons</id>
</project>
<jar>
<id>commons-lang</id>
<version>1.0</version>
<url>http://jakarta.apache.org/commons/</url>
</jar>
<xsl-stylesheet>
<id>docbook-xsl</id>
<version>4.1.2</version>
</xsl-stylesheet>
</dependencies>
So each plug-in can work with the appropriate dependencies (for example
maven:reactor can handle project dependencies, a docbook processing
plug-in can use the appropriate XSL for transformations, etc). I don't
know if this approach is better than the "dependency properties"
mentioned in the Matt's mail. Because, at the end each dependency is
always tied to the plug-in interpretation.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
