For the maven users out there, would be nice if the jar and the os-specific libraries were also published to ibiblio.org/maven2.
Or, alternatively, publish using the maven2 convention such that /maven2/net/contentobjects/jnotify/0.91/jnotify-0.91.jar directory/file is visible somewhere, along with jnotify.dll and libjnotify.so
I am not a maven user. if you want to do this you have my blessing.
(note that I intend to make a bugfix release for win32 soon.
Hi
I want to publish JNotify to Maven central repo and need licensing clarification.
The Java part licenses are LGPL 2.1 and EPL 1.0. What is the license (licenses) of native parts?
Can I add native libraries to 'jnotify-0.94.jar' and publish it with LGPL 2.1 and EPL 1.0 licenses or should I publish native libraries in seperate jar (or separate jar for every OS)? With what licenses?
Hi,
Both the Java and the native parts are released under the same dual license (LGPL and EPL).
Feel free to pack them however you like.
Hi
Sorry for delay
I've created temporary GitHub repo https://github.com/gslowikowski/jnotify-mavenization-tmp as a place to show you, how it will be published. We can discuss various aspects (e.g. groupId) and I will modify files there. When we agree that everything is as it should be, I will publish files to Maven central.
Is it OK for you?
looks fine.
please rename groupId to net.contentobjects.jnotify.
and I really don't know why fucking sf ar enot sending me notifications on this discussion.
https://github.com/gslowikowski/jnotify-mavenization-tmp changed.
There is one more step required before publishing. Maven team has to give me rights to publish your project (actually publish anything under the groupId "net.contentobjects.jnotify). As a project owner add comment here https://issues.sonatype.org/browse/OSSRH-24402 that you approve me as a person responsible for publishing.
Published.
Maven dependency: