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
mvn compile errors #31
Comments
hey lob! :-) Workaroundin the file |
hi hoijui, thanx a huge bunch for your msg. i just ended up loading the folder into eclipse and compiling it there. actually i have been just importing the source files for my own compiles and everything worked out like a charm. just got into osc and am puzzled by how good this system is. kicking myself why i haven't used it earlier. thanks again, robert |
ahhh good! :-)
yeah... i never, really actually used OSC in practise. i made an
out-interface for a real time strategy game engine, where i exported
statistics in rela time over OSC, which then could be used to generate
live music dependent on what would be going on on the battlefield.
there was a music artist interested in using it, he said, but he never
did anythign, and i am not talented in music to do anything myself.
what do you use it for? music or robotics or something else?
btw, i just released a SNAPSHOT of soon-to-come version 0.5.
(it is from the development branch, which is often rebased)
PS: i am swiss-german. living in berlin
2017-03-27 22:32 GMT+02:00, Robert Huber <notifications@github.com>:
… hi hoijui, thanx a huge bunch for your msg. i just ended up loading the
folder into eclipse and compiling it there. actually i have been just
importing the source files for my own compiles and everything worked out
like a charm. just got into osc and am puzzled by how good this system is.
kicking myself why i haven't used it earlier. thanks again, robert
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#31 (comment)
|
hallo freut mich ungemein, bin Oesterreicher und lebe in den USA :-) I really appreciate your library, saved my bacon. i was using it to play sound in PureData for a series of site-specific acousmatic compositions and I was controlling it from a java-based videotracking application. it would have been very difficult to do this dynamic soundscape without your library. i had never used OSC before (or had even heard of it), but I can see its power and i will use it for many future projects from sensor logging to controlling robotic interfaces. the library is very elegant, beautifully abstracted and i managed to get it working even without much knowledge of the protocol. my favorite object is OSCPortOut - was my friend on first sight. only thing that took me a while was realizing that the 'address' in osc message was not referring to a hostname ... smooth sailing after. Vielen Dank noch einmal. |
:D
ahh wow.. danke fuer die blumen! :-)
obwohl die lib urspruenglich nicht von mir designed wurde, hab ich da
schon viel geaendert, und mittlerweile sicher viel mehr daran gemacht
als der urspruengliche author.
und das ist eine gute info bezueglich der OSC address...
das ist versaendlich, dass man das eher so interpretiert. meinst du es
haette was gebracht, wenn ddas im class doc beschrieben waehre? oder
haettest du da eh nicht nachgelesen?
werd ich so oder so noch machen jetzt.
na dann... viel erfolg und spass mit deinen werken!
2017-03-29 8:56 GMT+02:00, Robert Huber <notifications@github.com>:
… hallo freut mich ungemein, bin Oesterreicher und lebe in den USA :-) I
really appreciate your library, saved my bacon. i was using it to play sound
in PureData for a series of site-specific acousmatic compositions that I was
controlling from a java-based videotracking application. it would have been
very difficult to do this dynamic soundscape without your library. i had
never used OSC before (or had even heard about it), but I can see the power
and will use it for many new projects from sensor logging to controlling
robotic interfaces. the library is very elegant, beautifully abstracted and
i managed to get it working even without much knowledge of the protocol. my
favorite object is OSCPortOut - was my friend on first sight. only thing
that took me a while was realizing that the 'address' in osc message was not
referring to a hostname ... smooth sailing after. Vielen Dank noch einmal.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#31 (comment)
|
i began working through it via the examples/tutorial. a comment there in
the line for OSCMessage construction would have been the path to the
correct read for me. thanks again.
|
ahh... where did you find that? i would not know where that is.. ;-) |
i found several |
i see... |
Your workaround removes the one error, but there are test failure.
|
what works for me: get latest repo status:
then:
and finally:
this works for me with Java 8 on linux, including the unit tests. |
confirming it works like a charm on mac osx as well. thanks for doing this. a few minor heads-ups like |
ook, nice! :-) |
I just got bit by the same thing as in the original post, running Java 8 on the
The issue here is that we have a class OSCMessageEvent that is supposed to be Serializable (by way of extending java.util.EventObject), however it has a This StackOverflow question is relevant here. I'm not quite sure how best to handle this. It feels like we just need to implement Serializable for OSCMessage, like we've done for other classes. I'm about to submit a PR that merges |
BTW, I found that changing this line: private final OSCMessage message; to private final transient OSCMessage message; also fixes the bug and allows |
ouhh yeah the OSCMessage should probably be serializable! |
That makes sense. Do you know what, exactly about the |
I think that is only possible with two different code-bases, or at least two different artifacts (like javaosc-0.5.0-java6and7 and javaosc-0.5.0-java8+, because the class-file format has changed in Java 8. If I remember right, that is the fundamental issue. Common practice to deal with this is to just change to the newer versions of Java at a new release... sometime. I find it a bit strange, because one never knows with which Java version a library is compiled.. that is not something that Maven has mechanisms for, for example. |
Ah, that all makes sense. If your goal is to release some unreleased code and have it be available for Java 6-7, then I think it makes sense to release JavaOSC 0.5.0 as the last release that supports Java 6-7, then immediately release JavaOSC 0.6.0 as the first release that requires Java 8+. FWIW, Java 7 reached EOL back in January 2015, so I don't think there is a compelling reason to continue to support it. Everybody should be using Java 8+ at this point, for critical security updates, etc. |
wow... makes me feel old! ;-) |
the |
hi all, am running into some problems with the basic mvn install ...
osx 10.11.6 and
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
and finally
any suggestions greatly welcome
The text was updated successfully, but these errors were encountered: