Open GoogleCodeExporter opened 9 years ago
Until resolved you can build and install your own copies of the jars to your
local maven repository, as outlined in this blog post...
http://mattmccomb.wordpress.com/2010/10/24/how-to-use-windowlicker-as-a-maven-de
pendency/
Original comment by mattmcc...@gmail.com
on 25 Oct 2010 at 6:34
Is there any news on this?
Original comment by carsten....@gmail.com
on 30 Oct 2011 at 7:09
One option is to upload to Sonatype OSS repo (which gets sync to maven central)
as a 3rd party jar (see
https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Th
e+Central+Repository).
I can try to do that if the authors are fine with it.
Original comment by vte...@gmail.com
on 20 Dec 2011 at 2:52
You can close the issue. I uploaded binaries as third-party jars on maven
central.
groupId: com.googlecode.windowlicker
artifactIds: windowlicker-core, windowlicker-swing, windowlicker-web
Maven build is at https://github.com/testinfected/windowlicker-maven-integration
Original comment by vte...@gmail.com
on 10 Apr 2012 at 1:06
Original issue reported on code.google.com by
michael....@gmail.com
on 26 Jan 2010 at 11:09