Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add pom.xml for publishing to sonatype / maven central #70

Merged
merged 2 commits into from
Jun 15, 2014

Conversation

magro
Copy link
Collaborator

@magro magro commented Jun 14, 2014

Should close issue #1

This version is deployed to sonatype and synced to maven central:
http://repo1.maven.org/maven2/com/esotericsoftware/kryonet/

Currently tests failing when running mvn install:

Tests in error:
  testRMI(com.esotericsoftware.kryonet.rmi.RmiSendObjectTest): Address already in use

The full output of mvn install is available here:
https://dl.dropboxusercontent.com/u/1439289/mvn-install.log.zip

To be able to build the jar mvn install was run with -Dmaven.test.skip=true.

magro added 2 commits June 15, 2014 00:06
…Software#1

This version is deployed to sonatype and synced to maven central:
http://repo1.maven.org/maven2/com/esotericsoftware/kryonet/

Currently tests failing when running `mvn install`:

    Tests in error:
      testRMI(com.esotericsoftware.kryonet.rmi.RmiSendObjectTest): Address already in use

The full output of `mvn install` is available here:
https://dl.dropboxusercontent.com/u/1439289/mvn-install.log.zip

To be able to build the jar `mvn install` was run with `-Dmaven.test.skip=true`.
NathanSweet added a commit that referenced this pull request Jun 15, 2014
Add pom.xml for publishing to sonatype / maven central
@NathanSweet NathanSweet merged commit 83ff508 into EsotericSoftware:master Jun 15, 2014
@NathanSweet
Copy link
Member

Thanks! You rock! :) I'll give you commit access to KryoNet and JsonBeans tomorrow.

@magro
Copy link
Collaborator Author

magro commented Jun 15, 2014

Thanks! :-) What do you think about the test failure?

@NathanSweet
Copy link
Member

Not sure, likely a problem closing a socket in a previous test. I'm guessing it doesn't fail every time?

@magro
Copy link
Collaborator Author

magro commented Jun 15, 2014

I tried it 3 times or so, and it always failed.
Am 15.06.2014 17:56 schrieb "Nathan Sweet" notifications@github.com:

Not sure, likely a problem closing a socket in a previous test. I'm
guessing it doesn't fail every time?


Reply to this email directly or view it on GitHub
#70 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants