Please push this to maven central about config

[havocp]

Reading about how to do this (https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide I guess?) is sort of giving me a headache, but I'll ask around about the best approach and try to get to it at some point. Maybe there's some way to sync all of repo.typesafe.com automatically.

[brianm]

I think a sync to central makes sense in your case. I'll ping you via another channel with someone to pester.

[brianm]

Would be be horribly offended if I pushed a version of this into oss.sonatype.org under a different group id? I ported the build to maven and set it up to push into oss.s.o

https://github.com/brianm/config/

there are two code changes to get it to compile cleanly in that repo: the first is to change the search path in TestUtils and the second is to disable a test which relied on the test-lib/directory.

[havocp]

Nope, I wouldn't be offended, happy you have a solution that isn't blocking on me ;-) Do change the group ID, so I'll have the option to push it to maven central myself later, as you mentioned. We can keep this issue open for that task.

If you want to send a pull request to mention your build in the README.md under "Binary Releases" that might make sense

Also, if you ever change the actual code (especially API or file format or other semantics) you'd probably have to rename the Java package, not just the group ID, in case people loaded both libs into the same class loader. But hopefully any changes like that could be merged into the main version.

Thanks!

[brianm]

Okay went ahead and pushed org.skife.com.typesafe.config:typesafe-config:0.2.1 to os.s.o. Once it propagates to central I'll send a pull request with the info.

Thank you!

[havocp]

I've gone through the hoops and an "official" release should be syncing shortly at com.typesafe:config:0.4.0
So you are off the hook! Thanks a lot for helping me out in the interim.