2.1.5 Release

Dear All,

2.1.5
    - <http://jogamp.org/deployment/v2.1.5/>
    - Our Maven Repo
    - Mark will soon update Maven Central

The test applets:
   <http://jogamp.org/deployment/v2.1.5/jogl-test-applets.html>


Overview of notable fixed bugs compared to 2.1.4:
 <https://jogamp.org/wiki/index.php/SW_Tracking_Report_Objectives_for_the_release_2.1.5>


Thank you all !


Cheers, Sven

Pushed to central.

Suspect that https://jogamp.org/bugzilla/show_bug.cgi?id=991 is definitely fixed, as it took about two hours to upload instead of the usual one...

I have a very strange problem compiling using 2.1.5, not sure if it just my machine or what is going on.
I'm using maven + jdk build 1.8.0-ea-b121. I changed my POM files to depend on jogl 2.1.5 instead of 2.1.4 and now javac can't find any jogl classes.
I see that the JAR files for 2.1.5 are downloaded, I can even run jar -tf jogl-all.jar and see all the classes but javac will not see them. Switching back to 2.1.4 and everything works fine.

My question is, can this be related to some JAR-signing or some security that Oracle has screwed with in later JDKs?

This is an incredibly stupid mistake on my part. I've no idea how, but somehow the compiled jar files have been replaced with the source jar files (so you get a jar file full of .java source files instead of compiled class files).

I'm looking into how to revert this now (we may be able to replace the artifacts on central).

https://jogamp.org/bugzilla/show_bug.cgi?id=999

Am working on this now.

It seems it really isn't possible to replace artifacts on the central repository, but correct artifacts will be deployed to the jogamp repository, and I'll see what I can do about getting fresher artifacts onto the central repos (possibly under a name like 2.1.5b).

Apologies to anyone affected (that includes me)!

On 03/11/2014 08:16 PM, io7m [via jogamp] wrote:
> This is an incredibly stupid mistake on my part. I've no idea how, but somehow
> the compiled jar files have been replaced with the source jar files (so you
> get a jar file full of .java source files instead of compiled class files).

No reason to be harsh to yourself,
only the working person can make mistakes.

Our Jenkins headline:
  "An expert is a man who has made all the mistakes which can be made,
   in a narrow field.", Niels Bohr

:)

>
> I'm looking into how to revert this now (we may be able to replace the
> artifacts on central).

Awesome - thank you Mark!

~Sven

PS: I had to reboot jogamp.org a few time just now, due
    to a mistake on my behalf and a 'zfs send' kernel hang
    on the zfsonlinux's team behalf :)

io7m wrote

This is an incredibly stupid mistake on my part. I've no idea how, but somehow the compiled jar files have been replaced with the source jar files (so you get a jar file full of .java source files instead of compiled class files).

I'm looking into how to revert this now (we may be able to replace the artifacts on central).

LOL I unpacked the JAR-files, linked them in Netbeans, ran jar -tf and still didn't spot the mistake so yeah.. You are not alone

And yes, I don't think you can overwrite a released version, there is a ton of caching in maven-land once you release a version, better just to release 2.1.5.1 or something and just get on with life :)

Ok... If people here would be so kind, please try version 2.1.5-01 from the jogamp test repository.

If everything works for you (it appeared to work for my test program here), then I'll upload 2.1.5-01 to central.

2.1.5-01 worked fine, no problems.

Deployed to central as 2.1.5-01. Should be up in a few hours!