Maven provides the functionality to include resources not in
ibiblio.org. I am not arguing about that. All that I want to do can be
done with Maven maven.repo.remote, but as I mentioned, this has
potential limitations. My suggestion is just to review whether this
mechanism is the best that can
Which licensing policy of ibiblio are you referring to?
AFAIK, there is none other than legality.
You can get this simple build process you want by putting jar
overrides in project.properties and supplying the jars that aren't
allowed on ibiblio with your project.
On Sun, 6 Jun 2004 10:34:54
My argument is that at first sight the element suggests that the
URL address is used for downloading resources. As I wrote, the current
manner to fetch dependencies not stored in ibiblio is to overload
maven.repo.remote. This is sufficient for the purposes of accessing
libraries needed for use
From my perspective as a maven user...
On Monday, May 31, 2004, at 02:50 PM, Sancho Neves-Graca wrote:
For resources not found in ibilio, the element can be used to
display an address where the resource can be fetched. However, this is
not really in accordance with one of the objectives of maven
For resources not found in ibilio, the element can be used to
display an address where the resource can be fetched. However, this is
not really in accordance with one of the objectives of maven, mainly to
provide a build system independent of the local environment. I dread
the idea of writing
