sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [sling-whiteboard] rombert edited a comment on pull request #51: SAML2 Service Provider Pull Request
Date Mon, 04 May 2020 13:57:10 GMT

rombert edited a comment on pull request #51:

   @cmrockwell - what I get is
   ```$ mvn -U clean verify 
   [WARNING] SystemTray is not supported, skipping notifications...
   [INFO] Scanning for projects...
   [INFO] ------------< >------------
   [INFO] Building SAML2 Service Provider 0.1.0-SNAPSHOT
   [INFO] --------------------------------[ jar ]---------------------------------
   Downloading from shibboleth:
   Downloading from central:
   [WARNING] The POM for is missing,
no dependency information available
   Downloading from shibboleth:
   Downloading from central:
   [INFO] ------------------------------------------------------------------------
   [INFO] ------------------------------------------------------------------------
   [INFO] Total time:  1.351 s
   [INFO] Finished at: 2020-05-04T15:52:37+02:00
   [INFO] ------------------------------------------------------------------------
   [ERROR] Failed to execute goal on project Could not resolve
dependencies for project
Could not find artifact in shibboleth
( -> [Help 1]
   [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] For more information about the errors and possible solutions, please read the following
   [ERROR] [Help 1]
   I have no settings.xml. I am running with 
   ```$ mvn -v
   Apache Maven 3.6.3 (SUSE 3.6.3-2.1)
   Maven home: /usr/share/maven
   Java version: 11.0.7, vendor: Oracle Corporation, runtime: /usr/lib64/jvm/java-11-openjdk-11
   Default locale: en_US, platform encoding: UTF-8
   OS name: "linux", version: "5.6.6-1-default", arch: "amd64", family: "unix"
   At any rate, we'll have to solve the issue of external artifacts at some points, we should
not have any custom repositories set.
   I've merged this in now, let's focus on getting the build passing so we can start validating
the functionality.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

View raw message