I verified that owlapi is actually present and accounted for
  in the duraspace thirdparty repository;  going back over the maven 
error log, I encountered these warnings:

Downloading: 
https://m2.duraspace.org/content/repositories/releases/owlapi/owlapi/3.0.0/owlapi-3.0.0.jar
[WARNING] Unable to get resource 'owlapi:owlapi:jar:3.0.0' from 
repository duraspace-releases 
(https://m2.duraspace.org/content/repositories/releases): Error 
transferring file: sun.security.validator.ValidatorException: PKIX path 
building failed: 
sun.security.provider.certpath.SunCertPathBuilderException: unable to 
find valid certification path to requested target
Downloading: 
https://m2.duraspace.org/content/repositories/thirdparty/owlapi/owlapi/3.0.0/owlapi-3.0.0.jar
[WARNING] Unable to get resource 'owlapi:owlapi:jar:3.0.0' from 
repository duraspace-thirdparty 
(https://m2.duraspace.org/content/repositories/thirdparty): Error 
transferring file: sun.security.validator.ValidatorException: PKIX path 
building failed: 
sun.security.provider.certpath.SunCertPathBuilderException: unable to 
find valid certification path to requested target

It looks like https://m2.duraspace.org/ uses a valid GoDaddy 
certificate.  Should I manually add the certificate to my java keystore, 
or is there a friendlier way to get access to this repository?

thanks,

-- Scott

thanks,

Scott Prater wrote:
> I attempted to compile fedora-3.4 from trunk, but ran into unresolved 
> dependency when running "mvn clean install -P fedora-installer":
> 
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> 
> Missing:
> ----------
> 1) owlapi:owlapi:jar:3.0.0
> 
>    Try downloading the file manually from the project website.
> 
>    Then, install it using the command:
>        mvn install:install-file -DgroupId=owlapi -DartifactId=owlapi 
> -Dversion=3.0.0 -Dpackaging=jar -Dfile=/path/to/file
> 
>    Alternatively, if you host your own repository you can deploy the 
> file there:
>        mvn deploy:deploy-file -DgroupId=owlapi -DartifactId=owlapi 
> -Dversion=3.0.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] 
> -DrepositoryId=[id]
> 
>    Path to dependency:
>          1) org.fcrepo:fcrepo-server:jar:3.4-SNAPSHOT
>          2) owlapi:owlapi:jar:3.0.0
> 
> ----------
> 1 required artifact is missing.
> 
> for artifact:
>    org.fcrepo:fcrepo-server:jar:3.4-SNAPSHOT
> 
> from the specified remote repositories:
>    duraspace-releases 
> (https://m2.duraspace.org/content/repositories/releases),
>    duraspace-thirdparty 
> (https://m2.duraspace.org/content/repositories/thirdparty),
>    central (http://repo1.maven.org/maven2),
>    apache-incubating 
> (http://people.apache.org/repo/m2-incubating-repository/),
>    java.net (https://maven-repository.dev.java.net/nonav/repository),
>    aduna (http://repo.aduna-software.org/maven2/releases/),
>    maven2-repository.dev.java.net (http://download.java.net/maven/2/),
>    duraspace-snapshots 
> (https://m2.duraspace.org/content/repositories/snapshots),
>    jboss (http://repository.jboss.com/maven2/)
> 
> Does the owlapi artifact need to be added to the 
> https://m2.duraspace.org/content/repositories/thirdparty repository?
> 
> thanks,
> 
> -- Scott
> 
> Steve Bayliss wrote:
>> Fedora source code is now in code freeze ready for final testing of the
>> Fedora 3.4 release.  If all goes to plan we aim to release Fedora 3.4 at the
>> end of this week.
>>  
>> No further commits to trunk should be made without coordinating with me
>> first so that we can ensure we have full test coverage for the version of
>> code we intend to release.
>>  
>> Many thanks to those who have volunteered to test this release, you may go
>> ahead and get the latest copy of Fedora source code from trunk.
>>  
>> If anyone else is interested in testing this release please do let me know,
>> or just go ahead and get a copy of the source code from Subversion.
>>  
>> Regards
>> Stephen Bayliss
>> Fedora 3.4 Release Manager
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by 
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev 
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Fedora-commons-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
> 
> 


-- 
Scott Prater
Library, Instructional, and Research Applications (LIRA)
Division of Information Technology (DoIT)
University of Wisconsin - Madison
[email protected]

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Fedora-commons-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers

Reply via email to