Re: Atomic jars in Maven Central - Gradle build system.
Posted by Sven Gothel on Jul 11, 2013; 2:55am
URL: https://forum.jogamp.org/Atomic-jars-in-Maven-Central-Gradle-build-system-tp4029555p4029560.html
On 07/11/2013 01:12 AM, Jesus Zazueta [via jogamp] wrote:
> Well I certainly didn't think JGL could serve as a good starting point for
> tutorials/examples lol. :P
>
> I have to admit that even though I got a good bunch of examples ready, the
> code is still in diapers.
>
> However, what I can do is to (as you guys suggest) switch to NEWT and do some
> code cleanup. I still intend to use the NEWT-SWT classes since my main project
> involves mixing in SWT widgets, but that's still a bit far down the road :P.
>
> I'll also try to reference JOGAMP's Maven repository in my Gradle build instead.
>
> And finally, I'll setup a small project page in case you guys might want to
> reference this project on the jogamp.org site. I'll keep you posted. ;)That would be awesome - thank you!
>
> Sven, a couple questions:
>
> 1) Can I find JOGL's atomic jars in JOGAMP's Maven repo as well? I tried
> looking in Maven central but the only artifact I could find was 'jogl-all'.
> Ideally, a Maven repo (either central or JOGAMP's) should also allow to select
> the atomic artifacts as well. Take a look at this Gist, where I split the jars
> in jogamp-all-platforms.7z (./jar/atomic) and basically uploaded gluegen and
> the bare minimal JOGL's jars for running on Linux/Windows.
This is a question for our Maven Man: Mark !
<http://jogamp.org/wiki/index.php/Maintainer_and_Contacts#Mark_Raynsford>
If you join our IRC channel .. you can chat w/ him, he is 'rmk0' AFAIK.
I myself .. just use his great scripts etc to provide the maven artifacts.
>
> https://gist.github.com/jjzazuet/5971006
>
> Which resulted in my custom repo structure.
>
> https://github.com/jjzazuet/mvn-repo/tree/master/repo/org/jogamp
>
> Would it be too cumbersome to make JOGL's build syste produce such artifacts?
> I understand it may be alot of cherry picking, but as Xerxes stated, this
> could eventually benefit people doing development for mobile platforms.I don't know.
I also don't know why you prefer using the atomics .. i.e.
in a real world deployment over the network it is surely slower
than using on of our all jar files.
The latter exist for mobile, desktop, with- and without AWT.
>
> And
>
> 2) I previously mentioned the idea of using Gradle for the JOGAMP projects.
> Not a trivial undertaking, I know, but I also think it might benefit a
> codebase this big. Do you guys think it might be useful?
I don't even know what this is :)
However, if you like to maintain such thing, you are surely more than welcome.
We can discuss this after SIGGRAPH .. let's say in August?
Maybe create an enhancement bug report in our bugzilla,
then remind me in August.
Thank you!
~Sven
>
> Thanks again for your time and help!
>
URL: https://forum.jogamp.org/Atomic-jars-in-Maven-Central-Gradle-build-system-tp4029555p4029560.html
On 07/11/2013 01:12 AM, Jesus Zazueta [via jogamp] wrote:
> Well I certainly didn't think JGL could serve as a good starting point for
> tutorials/examples lol. :P
>
> I have to admit that even though I got a good bunch of examples ready, the
> code is still in diapers.
>
> However, what I can do is to (as you guys suggest) switch to NEWT and do some
> code cleanup. I still intend to use the NEWT-SWT classes since my main project
> involves mixing in SWT widgets, but that's still a bit far down the road :P.
>
> I'll also try to reference JOGAMP's Maven repository in my Gradle build instead.
>
> And finally, I'll setup a small project page in case you guys might want to
> reference this project on the jogamp.org site. I'll keep you posted. ;)
>
> Sven, a couple questions:
>
> 1) Can I find JOGL's atomic jars in JOGAMP's Maven repo as well? I tried
> looking in Maven central but the only artifact I could find was 'jogl-all'.
> Ideally, a Maven repo (either central or JOGAMP's) should also allow to select
> the atomic artifacts as well. Take a look at this Gist, where I split the jars
> in jogamp-all-platforms.7z (./jar/atomic) and basically uploaded gluegen and
> the bare minimal JOGL's jars for running on Linux/Windows.
This is a question for our Maven Man: Mark !
<http://jogamp.org/wiki/index.php/Maintainer_and_Contacts#Mark_Raynsford>
If you join our IRC channel .. you can chat w/ him, he is 'rmk0' AFAIK.
I myself .. just use his great scripts etc to provide the maven artifacts.
>
> https://gist.github.com/jjzazuet/5971006
>
> Which resulted in my custom repo structure.
>
> https://github.com/jjzazuet/mvn-repo/tree/master/repo/org/jogamp
>
> Would it be too cumbersome to make JOGL's build syste produce such artifacts?
> I understand it may be alot of cherry picking, but as Xerxes stated, this
> could eventually benefit people doing development for mobile platforms.
I also don't know why you prefer using the atomics .. i.e.
in a real world deployment over the network it is surely slower
than using on of our all jar files.
The latter exist for mobile, desktop, with- and without AWT.
>
> And
>
> 2) I previously mentioned the idea of using Gradle for the JOGAMP projects.
> Not a trivial undertaking, I know, but I also think it might benefit a
> codebase this big. Do you guys think it might be useful?
I don't even know what this is :)
However, if you like to maintain such thing, you are surely more than welcome.
We can discuss this after SIGGRAPH .. let's say in August?
Maybe create an enhancement bug report in our bugzilla,
then remind me in August.
Thank you!
~Sven
>
> Thanks again for your time and help!
>
signature.asc (911 bytes) | Free forum by Nabble | Edit this page |