mercredi 20 août 2014

Maven error when deploying to FTP server on CentOS VPS (Could not transfer artifact : Unable to create directory com)


Vote count:

0




When I try to deploy my jar to an external repo, I receive this error.



[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.062s
[INFO] Finished at: Wed Aug 20 16:50:30 CDT 2014
[INFO] Final Memory: 10M/244M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project core: Failed to deploy artifacts: Could not transfer artifact com.merikmc:core:jar:1.0 from/to merik-ftp (ftp://merikmc.com/): Unable to create directory com -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project core: Failed to deploy artifacts: Could not transfer artifact com.merikmc:core:jar:1.0 from/to merik-ftp (ftp://merikmc.com/): Unable to create directory com
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
at org.codehaus.classworlds.Launcher.main(Launcher.java:46)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)


Here is my pom.xml:



<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://ift.tt/IH78KX" xmlns:xsi="http://ift.tt/ra1lAU" xsi:schemaLocation="http://ift.tt/IH78KX http://ift.tt/HBk9RF">

<modelVersion>4.0.0</modelVersion>
<groupId>com.merikmc</groupId>
<artifactId>core</artifactId>
<version>1.0</version>
<description>Core plugin for MErikMC</description>

<repositories>
<repository>
<id>snapshot-repo</id>
<url>http://ift.tt/1kwsBJ2;
</repository>
<repository>
<id>json-simple-repo</id>
<url>http://ift.tt/1waj7tS;
</repository>
</repositories>

<dependencies>
<dependency>
<groupId>net.md-5</groupId>
<artifactId>bungeecord-api</artifactId>
<version>1.7-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>com.googlecode.json-simple</groupId>
<artifactId>json-simple</artifactId>
<version>1.1.1</version>
</dependency>
<dependency>
<groupId>net.cubescape</groupId>
<artifactId>Yamler</artifactId>
<version>1.0</version>
<scope>system</scope>
<systemPath>${project.basedir}/lib/Yamler-1.0.jar</systemPath>
</dependency>
</dependencies>

<build>
<sourceDirectory>src/main/java</sourceDirectory>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ftp</artifactId>
<version>1.0-alpha-6</version>
</extension>
</extensions>
<resources>
<resource>
<targetPath>.</targetPath>
<filtering>true</filtering>
<directory>${basedir}/src/main/resources/</directory>
<includes>
<include>plugin.yml</include>
</includes>
</resource>
</resources>
<finalName>MErikCore</finalName>
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
</configuration>
</plugin>
</plugins>
</build>

<distributionManagement>
<repository>
<id>merik-ftp</id>
<url>http://ift.tt/1mncOcH;
</repository>
</distributionManagement>

</project>


I have configured my server in settings.xml only containing the tags id, username, and password.


The user that I connect to for FTP access is called repo and it is granted all permissions (such like root)


I have also changed the folder i'm uploading to to 777 so I can publicly execute, read, and write to it.


If I sign in using a FTP application like FileZilla, I can go into the folder and create the directory com manually if I wanted to.


I have used these same exact settings previously for another project but I was uploading elsewhere so I do believe it is a problem with the FTP server itself.



asked 1 min ago







Maven error when deploying to FTP server on CentOS VPS (Could not transfer artifact : Unable to create directory com)

Aucun commentaire:

Enregistrer un commentaire