Re: [tycho-user] Bundling JREs with my Product

[Massimo Rabbi <massimo.rabbi@xxxxxxxxx>]

Hi Jan,
I'm using the parent feature with child ones as suggested in the
mentioned article (2nd approach).
My goal is to avoid any kind of problems when updating. I hope this
can bypass the problem you are talking about.
In the article they refer at it when talking about the "rootfiles"
solution (1st approach).

Let's hope I'm not wasting time :-)

Best regards,
Massimo.

2013/7/11 Sievers, Jan <jan.sievers@xxxxxxx>:
> as a side note, I can imagine you will probably have a hard time updating the JDK while it's currently running.
> So I'm not sure if updating the JDK is a scenario which can be supported at all using p2
> (unless you use one installation to update another one which is generally not the case for IDE/RCP scenarios).
>
> Regards,
> Jan
>
> -----Original Message-----
> From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Massimo Rabbi
> Sent: Donnerstag, 11. Juli 2013 17:54
> To: Tycho user list
> Subject: Re: [tycho-user] Bundling JREs with my Product
>
> Hi Simon,
> thanks for the suggestion. I will try to give a look at it.
> What I was able to achieve right now is more or less the same.
> I used in my product pom.xml the maven-antrun-plugin in order to
> perform the chmod operation during the package phase.
> From the first test it seems to be enough, for example in Linux,
> setting permissions to 755 to the jre/bin folder content.
>
> I will try to achieve the same stuff using the touchpoint.
>
> Best regards,
> Massimo.
>
> 2013/7/11 Simon Goodall <simon@xxxxxxxxxxxxxxxxxx>:
>> Hi,
>>
>> I've only tried this when building my features on windows. If packaging the
>> jre on Linux does not retain the file permissions then you could look at
>> adding calls to the chmod touchpoint [1] in your p2.inf to set the correct
>> permissions for each required file.
>>
>> [1]
>> http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_actions_touchpoints.html
>>
>> Regards,
>>
>> Simon
>>
>>
>> On 11 July 2013 09:13, Massimo Rabbi <massimo.rabbi@xxxxxxxxx> wrote:
>>>
>>> Hi all,
>>> I've tried the approach mentioned in the blog article, posted some
>>> mails ago. This one:
>>>
>>> http://codeiseasy.wordpress.com/2012/07/31/including-a-jre-in-a-tycho-build/
>>> Therefore I've created the main feature including the optional ones
>>> specific for every operating system configuration (macosx 64bit, linux
>>> 32/64bit and windows 32/64bit). I've used the solution with p2.inf
>>> file, hoping this will allow to update smoothly the JRE in the future.
>>> In my build.properties I've included the jre folder (already
>>> exploded). And my final product eclipse.ini will have the vm
>>> installation specified with the -vm flag pointing to the correct
>>> feature subfolder.
>>>
>>> The problem is that in the final produced product the jre folder
>>> inside the dedicated feature does not have the original permissions.
>>> This is not a problem for Windows but for Linux and Mac OS X, not
>>> having executable flags for the files contained in the bin subfolders
>>> lead to not recognize the JRE installation as valid.
>>> By the way I'm building on Mac OS X 10.7.4, but I also tried in Linux
>>> Mint 15 Oliva.
>>>
>>> Did anyone experienced a similar problem?
>>> Doug the solution you use with generate-resource phase, does it keep
>>> the permissions?
>>>
>>> Thanks in advance,
>>> Best regards,
>>> Massimo.
>>>
>>> 2013/6/18 Doug Schaefer <dschaefer@xxxxxxx>:
>>> > This is maven, so, yes, this is being done as part of our product build
>>> > and
>>> > we redistribute all of it. We just pre-download the JRE and put it on a
>>> > local server so we don't lose it. My pom for the feature downloads and
>>> > extracts the JRE from there as part of the generate-resource phase.
>>> >
>>> > Mind you, we don't change JREs very often. If you're trying to keep up
>>> > with
>>> > the latest JREs then I'm not sure Oracle's interface will allow that.
>>> >
>>> > Doug.
>>> >
>>> > From: Simon Goodall <simon@xxxxxxxxxxxxxxxxxx>
>>> > Reply-To: Tycho user list <tycho-user@xxxxxxxxxxx>
>>> > Date: Tuesday, 18 June, 2013 10:58 AM
>>> > To: Tycho user list <tycho-user@xxxxxxxxxxx>
>>> > Subject: Re: [tycho-user] Bundling JREs with my Product
>>> >
>>> > Hi,
>>> >
>>> > In the past Oracle's licensing terms (as I understood them) forbid
>>> > automatic
>>> > downloads of the JRE/JDK or redistribution in a more convenient format.
>>> > However you can include it as part of your application. I am not sure if
>>> > things have changed since I last looked. The latest hudson version still
>>> > has
>>> > the automatic jdk install disabled with a note to the same Hudson-9016
>>> > bug
>>> > referenced in the blog post. The Jenkins build server does have this
>>> > support
>>> > enabled - essentially it programmatically navigates the oracle website
>>> > using
>>> > your oracle developer network credentials.
>>> >
>>> > Simon
>>> >
>>> >
>>> > On 18 June 2013 15:30, Laurent PETIT <laurent.petit@xxxxxxxxx> wrote:
>>> >>
>>> >> 2013/6/18 Doug Schaefer <dschaefer@xxxxxxx>:
>>> >> > Or Google it. I'm using the following I found through a search:
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> > http://codeiseasy.wordpress.com/2012/07/31/including-a-jre-in-a-tycho-build
>>> >> > /
>>> >> >
>>> >> > Doug.
>>> >>
>>> >>
>>> >> Hello Doug,
>>> >>
>>> >> I have come across this July 2012 link.
>>> >> If you think it's the panacea, good for you, but for me it's far from
>>> >> ideal, and that's why I'm asking for an update on the best way of
>>> >> doing things currently, e.g. a year later.
>>> >>
>>> >> Especially, this last bit annoys me a lot, and I'd like to know if
>>> >> there's a better way:
>>> >>
>>> >> "The only piece left is to obtain the JRE itself. Unfortunately the
>>> >> Oracle JRE's cannot be downloaded direct from Orcale automatically
>>> >> (see e.g. here) so they must be manually downloaded, installed and the
>>> >> the jre directory copied across for each version and platform you need
>>> >> to support."
>>> >>
>>> >> Seems like repetitive / tedious / error prone work that could be
>>> >> avoided if there's a central place to put each new public revision of
>>> >> say open jdk 7.
>>> >> A maven repo ?
>>> >> A p2 repository ?
>>> >> Already done ? Where ?
>>> >>
>>> >> That's why, among other things, I ask here on the ml, to humans, and
>>> >> not just the google bot.
>>> >>
>>> >> Cheers,
>>> >>
>>> >> --
>>> >> Laurent
>>> >> _______________________________________________
>>> >> tycho-user mailing list
>>> >> tycho-user@xxxxxxxxxxx
>>> >> https://dev.eclipse.org/mailman/listinfo/tycho-user
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > tycho-user mailing list
>>> > tycho-user@xxxxxxxxxxx
>>> > https://dev.eclipse.org/mailman/listinfo/tycho-user
>>> >
>>> _______________________________________________
>>> tycho-user mailing list
>>> tycho-user@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>>
>>
>>
>> _______________________________________________
>> tycho-user mailing list
>> tycho-user@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>>
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user