On 23 Apr 2007, at 18:10, Jerome Louvel wrote:
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.
If you do start your own repository, and there's nothing in the
licence of say Asyncweb or Simple preventing you from doing so, you
can include those artefacts in that repository as well. Ideally
adding the repository for Restlet and the dependency for the chosen
Restlet artefacts should then be able to pull down automatically the
rest.
1) fully free
If you go for #1 I can contribute with at least 2 mirror sites which
should have enough bandwidth available.
A commercial maven repository for a so-called open source project
don't sound quite right for me - what would prevent me from making a
competing "free" maven repository that would more easily get support
and possibly later merged with ibiblio? And if so - what is then the
point of the commercial repository except to encourage forking..?
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?
For me, Maven 2, definitively. I don't see a point in a maven 1
repository, as Vincent points out, typical Restlet users are not
using Maven 1.
Maven 2 has lots of functionality built-in (OK, it's all plugins) for
deploying to repositories, for instance using scp towards an Apache-
hosted (or Restlet-directory hosted, I Guess) directory.
The Maven book "Better builds with Maven" - available for free from
http://www.mergere.com/common/reg.jsp?form_source=m-
m2book&form_landing=DefaultPage - should have some references. You
don't have to move the whole build process to Maven to do the deploy,
although of course in the long run it could be worthwhile to do that
as well.
--
Stian Soiland, myGrid team
School of Computer Science
The University of Manchester
http://www.cs.man.ac.uk/~ssoiland/
