> However, Maven does come with its issues and a certain level of complexity.
> The management of dependencies can become difficult as well (for example when
> you rely on artifact not available in public Maven repositories or without
> Internet connectivity).
Some additional informations about these two points:
- For artifacts not available from public Maven repository, Maven can
use alternate repositories. If dependencies are only available from
Restlet Maven repository or from the Maven repository of Sun (see the
file modules/pom.xml on the last ZIP file I submit):
...
<repositories>
<repository>
<id>maven-restlet</id>
<name>Public online Restlet repository</name>
<url>http://maven.restlet.org</url>
</repository>
<repository>
<id>sun-java-net</id>
<name>Public Sun repository on Java.net</name>
<url>http://download.java.net/maven/2</url>
</repository>
</repositories>
...
- For off-line purpose:
By default, Maven uses a local cache (also to decrease Internet download
bandwidth).
And, all dependencies can be retrieve with the command
mvn dependency:copy-dependencies
Very useful to create a distribution package!
With the "Maven Site", We can have a dependency graph of each project:
Example with JAX-RS module:
http://jycronier.free.fr/tmp/restlet-maven-site/org.restlet.ext.jaxrs/dependencies.html
(see section "Project Dependency Graph")
> I have targeted it for Restlet 2.0 to give it time to mature. Let's continue
> the debate!
Totally agree!!! :) I will have a look on Buckminster
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=994650
