You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Reto Bachmann-Gmür <re...@apache.org> on 2012/01/29 01:09:35 UTC
missing dependency and non-central maven repository
Hello
I'm failing to compile stanbol due to a missing dependency
org.drools:drools-compiler:jar:5.1.1 required in
org.apache.stanbol.data.bundlelist.
Also I see that the list of maven repositories other than maven central is
quite long, 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.
cheers,
Reto
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:2.1:resolve-plugins
(resolve-plugins) on project org.apache.stanbol.data.bundlelist: Nested:
Could not find artifact org.drools:drools-compiler:jar:5.1.1 in apache (
http://repository.apache.org/snapshots/)
[ERROR]
[ERROR] Try downloading the file manually from the project website.
[ERROR]
[ERROR] Then, install it using the command:
[ERROR] mvn install:install-file -DgroupId=org.drools
-DartifactId=drools-compiler -Dversion=5.1.1 -Dpackaging=jar
-Dfile=/path/to/file
[ERROR]
[ERROR] Alternatively, if you host your own repository you can deploy the
file there:
[ERROR] mvn deploy:deploy-file -DgroupId=org.drools
-DartifactId=drools-compiler -Dversion=5.1.1 -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR]
[ERROR]
[ERROR] org.drools:drools-compiler:jar:5.1.1
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] apache (http://repository.apache.org/snapshots/, releases=true,
snapshots=true),
[ERROR] java.net (http://download.java.net/maven/2, releases=true,
snapshots=true),
[ERROR] repository-codehaus (http://repository.codehaus.org, releases=true,
snapshots=true),
[ERROR] nuxeo-vendor-release (
https://maven.nuxeo.org/nexus/content/repositories/vendor-releases,
releases=true, snapshots=true),
[ERROR] clojars.org (http://clojars.org/repo, releases=true,
snapshots=true),
[ERROR] com.springsource.repository.bundles.external (
http://repository.springsource.com/maven/bundles/external, releases=true,
snapshots=true),
[ERROR] kiwi-project_SNAPSHOTS (
http://devel.kiwi-project.eu:8080/nexus/content/repositories/snapshots/,
releases=true, snapshots=true),
[ERROR] kiwi-project (
http://devel.kiwi-project.eu:8080/nexus/content/repositories/releases/,
releases=true, snapshots=true),
[ERROR] apache.snapshots (http://repository.apache.org/snapshots,
releases=false, snapshots=true),
[ERROR] central (http://repo1.maven.org/maven2, releases=true,
snapshots=false)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :org.apache.stanbol.data.bundlelist
Re: missing dependency and non-central maven repository
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi Fabian, all
Because it is related to this Thread ..
regarding the LDPath dependencies:
The two LDPath artifacts (api and core) are currently SNAPSHOT and
hosted on a private maven server. I already agreed with Sebastian
that we will make a release soon and also upload this dependencies to
maven central.
best
Rupert
On Tue, Feb 7, 2012 at 5:53 PM, Reto Bachmann-Gmür <re...@apache.org> wrote:
> I found a document on how to add third party artifacts to maven central:
>
> https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
>
> Reto
>
> On Mon, Jan 30, 2012 at 9:22 AM, Reto Bachmann-Gmür <re...@apache.org> wrote:
>
>> 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 <
>> christ.fabian@googlemail.com> wrote:
>>
>>> Hi,
>>>
>>> Am 29. Januar 2012 01:09 schrieb Reto Bachmann-Gmür <re...@apache.org>:
>>> > 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
>>>
>>
>>
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: missing dependency and non-central maven repository
Posted by Reto Bachmann-Gmür <re...@apache.org>.
I found a document on how to add third party artifacts to maven central:
https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
Reto
On Mon, Jan 30, 2012 at 9:22 AM, Reto Bachmann-Gmür <re...@apache.org> wrote:
> 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 <
> christ.fabian@googlemail.com> wrote:
>
>> Hi,
>>
>> Am 29. Januar 2012 01:09 schrieb Reto Bachmann-Gmür <re...@apache.org>:
>> > 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
>>
>
>
Re: missing dependency and non-central maven repository
Posted by Reto Bachmann-Gmür <re...@apache.org>.
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 <christ.fabian@googlemail.com
> wrote:
> Hi,
>
> Am 29. Januar 2012 01:09 schrieb Reto Bachmann-Gmür <re...@apache.org>:
> > 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
>
Re: missing dependency and non-central maven repository
Posted by Fabian Christ <ch...@googlemail.com>.
Hi,
Am 29. Januar 2012 01:09 schrieb Reto Bachmann-Gmür <re...@apache.org>:
> 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