Post

1 follower Follow
0
Avatar

Dependencies for xldeploy-maven-plugin-6.0.1 can not be downloaded

Hi,

I have a problem downloading the `remote-booter-2017.3.0` from the xebia maven repo. I am pretty sure this worked in the past.

Repo config

<pluginRepositories>
<pluginRepository>
<id>xebialabs-maven2</id>
<url>https://dist.xebialabs.com/public/maven2/</url>
</pluginRepository>
</pluginRepositories>

Plugin use:

<plugin>
<groupId>com.xebialabs.xldeploy</groupId>
<artifactId>xldeploy-maven-plugin</artifactId>
<version>6.0.1</version>
<extensions>true</extensions>

<configuration/>
</plugin

Build log:

[INFO] Scanning for projects...
Downloading from xxx: https://xxx/repository/maven-public/com/xebialabs/xldeploy/xldeploy-maven-plugin/6.0.1/xldeploy-maven-plugin-6.0.1.pom
Downloading from xebialabs-maven2: https://dist.xebialabs.com/public/maven2/com/xebialabs/xldeploy/xldeploy-maven-plugin/6.0.1/xldeploy-maven-plugin-6.0.1.pom
Downloaded from xebialabs-maven2: https://dist.xebialabs.com/public/maven2/com/xebialabs/xldeploy/xldeploy-maven-plugin/6.0.1/xldeploy-maven-plugin-6.0.1.pom (19 kB at 96 kB/s)
[...]
Downloading from xxx: https://xxx/repository/maven-public/com/xebialabs/deployit/engine/remote-booter/2017.3.0/remote-booter-2017.3.0.pom
Downloading from xebialabs-maven2: https://dist.xebialabs.com/public/maven2/com/xebialabs/deployit/engine/remote-booter/2017.3.0/remote-booter-2017.3.0.pom
Downloading from central: https://repo.maven.apache.org/maven2/com/xebialabs/deployit/engine/remote-booter/2017.3.0/remote-booter-2017.3.0.pom
Downloading from xebialabs-alphas: https://nexus.xebialabs.com/nexus/content/repositories/alphas/com/xebialabs/deployit/engine/remote-booter/2017.3.0/remote-booter-2017.3.0.pom
Downloading from xebialabs-snapshots: https://nexus.xebialabs.com/nexus/content/repositories/snapshots/com/xebialabs/deployit/engine/remote-booter/2017.3.0/remote-booter-2017.3.0.pom
Downloading from xebialabs-releases: https://nexus.xebialabs.com/nexus/content/repositories/releases/com/xebialabs/deployit/engine/remote-booter/2017.3.0/remote-booter-2017.3.0.pom
Downloading from knopflerfish: http://www.knopflerfish.org/maven2/com/xebialabs/deployit/engine/remote-booter/2017.3.0/remote-booter-2017.3.0.pom
[...]
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Unresolveable build extension: Plugin com.xebialabs.xldeploy:xldeploy-maven-plugin:6.0.1 or one of its dependencies could not be resolved: Failed to collect dependencies at com.xebialabs.xldeploy:xldeploy-maven-plugin:jar:6.0.1 -> com.xebialabs.deployit.engine:remote-booter:jar:2017.3.0 @
[ERROR] Unknown packaging: dar @ xxx:[unknown-version], /xxx/pom.xml, line 14, column 14
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project xxx (/xxx/pom.xml) has 2 errors
[ERROR] Unresolveable build extension: Plugin com.xebialabs.xldeploy:xldeploy-maven-plugin:6.0.1 or one of its dependencies could not be resolved: Failed to collect dependencies at com.xebialabs.xldeploy:xldeploy-maven-plugin:jar:6.0.1 -> com.xebialabs.deployit.engine:remote-booter:jar:2017.3.0: Failed to read artifact descriptor for com.xebialabs.deployit.engine:remote-booter:jar:2017.3.0: Could not transfer artifact com.xebialabs.deployit.engine:remote-booter:pom:2017.3.0 from/to xebialabs-alphas (https://nexus.xebialabs.com/nexus/content/repositories/alphas): Not authorized , ReasonPhrase:Unauthorized. -> [Help 2]

So the build fails with an unauthorised message. Which I can imagine because maven tries to pull from your internal repositories.

I checked the public maven repo and found this at URL https://dist.xebialabs.com/public/maven2/com/xebialabs/deployit/

Index of /public/maven2/com/xebialabs/deployit

[ICO] Name Last modified Size Description

[PARENTDIR] Parent Directory   -  
[DIR] appserver-api/ 2018-10-02 12:02 -  
[DIR] engine-api/ 2018-10-02 12:03 -  
[DIR] engine-spi/ 2018-10-02 12:03 -  
[DIR] maven-deployit-plugin/ 2018-01-09 15:55 -  
[   ] maven-metadata.xml 2016-03-01 10:53 238  
[   ] maven-metadata.xml.md5 2016-03-01 10:53 32  
[   ] maven-metadata.xml.sha1 2016-03-01 10:53 40  
[DIR] udm-plugin-api/ 2018-10-02 12:03 -  

 

So. Maybe something changed recently at your side (at october 2nd) with this build error as result? Or did I make some stupid mistake?

 

Thanks

Steef

 

 

Steef de Bruijn

Please sign in to leave a comment.

1 comment