yrift / jwebsocket

Automatically exported from code.google.com/p/jwebsocket
0 stars 0 forks source link

typo / wrong case in jWebSocketFactory pom.xml #31

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Maven build with 0.9.5 sources 
mvn clean install
fails on my system (linux + openjdk 6 + mvn 2.2.1) due to a typo in pom.xml of 
jWebSocketFactory module:

===============================================================================
[INFO] Unable to find resource 'org.jwebsocket:jWebSocketPlugIns:jar:0.9.5' in 
repository central (http://repo1.maven.org/maven2)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.jwebsocket:jWebSocketPlugIns:jar:0.9.5

  Try downloading the file manually from the project website.

  Then, install it using the command: 
      mvn install:install-file -DgroupId=org.jwebsocket -DartifactId=jWebSocketPlugIns -Dversion=0.9.5 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there: 
      mvn deploy:deploy-file -DgroupId=org.jwebsocket -DartifactId=jWebSocketPlugIns -Dversion=0.9.5 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
    1) org.jwebsocket:jWebSocketFactory:jar:0.9.5
    2) org.jwebsocket:jWebSocketPlugIns:jar:0.9.5

===============================================================================

SOLUTION:

fix typo in line 44 of pom.xml:
from:
<artifactId>jWebSocketPlugIns</artifactId>
to:
<artifactId>jWebSocketPlugins</artifactId>

Original issue reported on code.google.com by gimpelmo...@gmail.com on 28 Jul 2010 at 9:43

GoogleCodeExporter commented 8 years ago

Original comment by mailtopu...@gmail.com on 4 Aug 2010 at 7:18

GoogleCodeExporter commented 8 years ago
This should be done due to our module consolidation. The factory module now is 
part of the the server module, which makes this bug obsolete.

Original comment by fivefeetfurther@gmail.com on 5 Aug 2010 at 9:25