We are having the same problem in Clerezza, one of the dependencies that isn't in the central repo is sesame 2 [1]. I think we have the following options:
- not include the sesame backend in the default distribution (users who need it would have to compile it their selves of download it from elsewhere) - repackage the whole of sesame underneath org.apache.clerezza and distribute own artifacts (and recursively for all dependencies of sesame not in central, tedious) Cheers, reto 1. http://sourceforge.net/mailarchive/forum.php?thread_name=4B71ABD4.4080904%40apache.org&forum_name=sesame-general On Sat, Mar 20, 2010 at 9:45 PM, Brian Fox <bri...@infinity.nu> wrote: > At the Central repository we are restricting the inclusion of external > repositories because this generally creates a mess. This is being > enforced on new artifacts coming in so I would recommend you do not > add them or your artifacts themselves will end up blocked. A better > choice is to encourage the missing dependency projects to get their > stuff into Central, or find some compatible libraries that are. > > On Mon, Mar 8, 2010 at 11:50 AM, Gurkan Erdogdu > <cgurkanerdo...@gmail.com> wrote: > > Hi; > > > > Is there any rule/policy for using third-party maven repositories in our > > project poms? Recently, we have required to list some repositories in > > settings.xml (for example: jboss) to our codebase built correctly. But > when > > Apache-Hudson runs to built daily, it throws errors because of not > finding > > required repositories. Is it OK to list those repositories in our poms? > > > > I have just found > > > http://maven.apache.org/guides/mini/guide-central-repository-upload.htmldocumentation > > FAQ and common mistakes section. > > > > Thanks; > > > > --Gurkan > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
