I think rasoners/hermit shows a possible work-around by adding the jars to
svn and the following to the pom:
<repository>
<releases>
<updatePolicy>always</updatePolicy>
</releases>
<snapshots>
<updatePolicy>always</updatePolicy>
</snapshots>
<id>reasoners-hermit-embedded</id>
<url>file://localhost/${project.basedir}/src/main/resources/maven/repo</url>
</repository>
I think this approach should be combined with embedding the dependencies in
the bundle as otherwise there are still the dependencies at runtime that
can't be resolved without adding sources other than maven central.
It is easy for a project owner to add jars to maven central, but I don't
think thirs-party jars can easily be added. So wherever possible we should
get the project we depend on to add their dependencies to maven central (I
didn't manage to convince aduna/sesame so the sesame backend will not be
part of the clerezza release).
Cheers,
Reto
On Sun, Jan 29, 2012 at 1:15 AM, Fabian Christ <[email protected]
> wrote:
> Hi,
>
> Am 29. Januar 2012 01:09 schrieb Reto Bachmann-Gmür <[email protected]>:
> > we cannot release modules that have dependencies that are not
> > in maven central, to keep maven central self contained no third-party
> > repository dependency are allowed.
>
> @Stanbol Mentors: Is this an official Apache policy?
>
> If this is the case, do you know how to solve such problems? Can we
> upload artifacts to Maven central somehow?
>
> Best,
> - Fabian
>
