Hi all, Stian reported several issues with Maven POM files related to third-party dependencies. We are definitely going to fix those issues and fully support Maven-based builds.
Still, some dependencies like AsyncWeb and Simple are not available (yet?) in public repositories. It seems that users could workaround the current limitations by managing a local repository where they would manually upload the missing JAR files with matching POM files and version tags. We could even provide those POM files in the distribution if that would help. Also, we understand the need for a better integration with Maven builds, especially to provide a way to download Restlet modules and dependencies directly from Maven instead of relying on the Restlet distribution (Zip/Installer). Instead of relying on a public Maven repository such as Ibiblio, we would prefer to host our own Maven repository at "maven.noelios.com" and control its freshness and service quality. We haven't fully decided about the type of access to this repository: 1) fully free 2) restricted to support plans subscribers [1] 3) a combination of both with different update schedules depending on the type of access (e.g. immediate availability of update versions for subscribers, availability after a given delay for others). It is of course tempting to freely provide this service, but we also need a viable economic model if we want to continue investing in Restlets R&D as strongly in the future. We also have some hosting costs to support all those services. As I said, we haven't fully decided yet so it's time to express your opinion. Thierry has already started the work on the repository which will of course run on Restlets :) He is struggling a bit to find reliable reference information on the repository layouts. For example, should we support the "legacy" layout from Maven 1 or should be directly move to the better one introduced by Maven 2. Does anyone has good pointers? Best regards, Jerome [1] http://www.noelios.com/services/
