[jbosstools-dev] Packaging JBoss Tools for Fedora (issue & potential patches)

[Gerard Ryan]

On Wed, Aug 22, 2012 at 12:48:09PM +0200, Max Rydahl Andersen wrote:
>>>> The customizations that Gerard is referring to in this case are of the Linux environment itself, not specific to JBoss Tools (or even Eclipse). We are setting up the user's home directory so that they can start coding as soon as the boot finishes. This includes things like customizing terminal settings, adding git awareness to the bash prompt, setting the Eclipse workspace directory and default perspective and things of that sort.
>>> cool - but what needs to change concerning eclipse workspace directory and default perspective?
>>
>> We pre-selected the workspace directory ($HOME/workspace) so that the user is not prompted when running the LiveCD. We've put settings in that directory, so if they pick another location they don't get those settings, so we want them to get the full experience.
>
>> We set the default perspective to the JBoss perspective (instead of Resource) to highlight the area with the main features (and the configured server).
>
>hmm - didn't see any of that when running the builds from http://ryan.lt/fedora-java-remix/ which I downloaded yesterday ?
>
>no predefined server nor JBoss perspective ?
>
Thanks for pointing that out Max, it was a bug that sliiped in
unnoticed late on before I uploaded those. A couple of files were
failing to br created because the directories they would be in didn't
yet exist. New builds are up now that fix that, sorry for the
inconvenience!

>>>> This script creates a skinny standalone instance of JBoss AS that only has the configuration files and uses JBOSS_BASE_DIR to point to the real installation. This is the proper way (IMO) to properly handle permissions on an operating system that properly handles permissions :)
>>> Please open JBIDE jiras for stuff we don't handle properly - just fixing it in fedora java remix is not a good long term solution.
>> Agreed. What we've done so far has been a proof of concept to understand the requirements for whatever feature request we would file. I think what I wrote above is sufficient for a JIRA report and I will file it as such...
>>
>> Voila! https://issues.jboss.org/browse/JBIDE-12452
>
>Thanks!
>
>>>> when they start Eclipse the first time, they should have a JBoss AS server already ready to go (that's one of the key goals of this spin).
>>> Yes, please open jiras so we can now what you actually need - adding yet another autosetup is IMO backwards. (fine for this gsoc java respin as a proof of concept, but for me being able to have the autodetect pick up such installation no matter how you got jboss tools is much more interesting)
>>>
>>> Could you open a jira and optimally point to the source for whatever configuration you do externally to the existing autodetection and server adapter setup ?
>>>
>>>> Btw, you can grab a spin ISO, pop it into a virtual machine (like VirtualBox) and try it out:
>>>>
>>>> http://ryan.lt/fedora-java-remix/
>>> thanks, i'll try it out.
>>
>> Please do. And please pass it on.
>>
>
>done: https://community.jboss.org/en/tools/blog/2012/08/22/summer-time-with-new-release-soa-tools-and-a-bit-of-juno-and-fedora-news
>
>/max

-- 
Gerard Ryan :: gerard at ryan.lt :: http://blog.grdryn.me :: @grdryn
PGP Fingerprint: AA11 A666 C98E B6D8 231C 11ED 6EDC 7E4A 62BC 4A15