[JBoss JIRA] (JBIDE-17032) Ability to configure jQuery / jQuery Mobile versions injected by Palette
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17032?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-17032:
----------------------------------------
Should we hardcode the default versions (2.0.3 and 1.4.2) or just use the latest versions which match the pattern 2.0.* and 1.4.*? When/if 2.0.4 & 1.4.3 are released and added by user to the preferences what should we use by default?
I think it's better to use the latest versions which match the patterns of supported versions for JQM 1.4 and 1.3 until users select some other version (we will remember his choice for the project). What do you think?
> Ability to configure jQuery / jQuery Mobile versions injected by Palette
> ------------------------------------------------------------------------
>
> Key: JBIDE-17032
> URL: https://issues.jboss.org/browse/JBIDE-17032
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta2
>
> Attachments: 2014-04-25 17.02.bmml, 2014-04-25 17.02.bmml, 2014-04-25 17.02.png, css.gif, js.png, lib.png, NextPage.bmml, NextPage.bmml, NextPage.bmml, NextPage.png, Preferences.bmml, Preferences.png, SeparateDialog.bmml, SeparateDialog.png
>
>
> Currently the following versions are injected for JQM 1.4:
> {code}
> <script src="http://code.jquery.com/jquery-1.10.2.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.4.2/jquery.mobile-1.4.2.min.js"></script>
> {code}
> And for JQM 1.3:
> {code}
> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.3.2/jquery.mobile-1.3.2.min.js"></script>
> {code}
> It would be good if we have a place where users can configure what versions of JQ and JQM they want to inject.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBDS-3026) Provide better default JRE path in univeral installer on Mac OS X
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3026?page=com.atlassian.jira.plugin.... ]
Denis Golovin closed JBDS-3026.
-------------------------------
Fix Version/s: 8.0.0.Beta2
Resolution: Duplicate Issue
Please see linked issue
> Provide better default JRE path in univeral installer on Mac OS X
> -----------------------------------------------------------------
>
> Key: JBDS-3026
> URL: https://issues.jboss.org/browse/JBDS-3026
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta1
> Reporter: Michelle Murray
> Fix For: 8.0.0.Beta2
>
>
> Max OS X, universal installer, step 4 - choose JVM
> When installer is launched from command line, the Default JVM path is correct - /Library/Java/JavaVirtualMachines/jdk1.7.0_55.jdk/Contents/Home
> ^ great :D
> When installer is launched by double-clicking .jar file, the Default JVM path is not right - /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
> ^ can we provide a better default value when installer is launched by this method?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-17032) Ability to configure jQuery / jQuery Mobile versions injected by Palette
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17032?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-17032:
-----------------------------------------
I'll re-emphasize one bit of info - the versions of jQueyr and jQuery Mobile that we'd want to support out of the box are:
jQueryMobile:
* 1.4.2
jQuery:
* 1.10.2
* 2.0.3
In WFk 2.6, the quickstarts now use jQuery 2.0.3 and jQuery Mobile 1.4.2.
For JBDS, I'm not sure jQuery 2.0.3 would be a good default over 1.10.2, given most of the JBDS user base is on Windows, and MSIE 6-8 support maybe expected from the selected version of jQuery. I'd prefer to have inputs from [~akazakov] and [~maxandersen] on which would be suitable.
And the proposed designs do look like what we'd want to continue to build on in the future.
> Ability to configure jQuery / jQuery Mobile versions injected by Palette
> ------------------------------------------------------------------------
>
> Key: JBIDE-17032
> URL: https://issues.jboss.org/browse/JBIDE-17032
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta2
>
> Attachments: 2014-04-25 17.02.bmml, 2014-04-25 17.02.bmml, 2014-04-25 17.02.png, css.gif, js.png, lib.png, NextPage.bmml, NextPage.bmml, NextPage.bmml, NextPage.png, Preferences.bmml, Preferences.png, SeparateDialog.bmml, SeparateDialog.png
>
>
> Currently the following versions are injected for JQM 1.4:
> {code}
> <script src="http://code.jquery.com/jquery-1.10.2.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.4.2/jquery.mobile-1.4.2.min.js"></script>
> {code}
> And for JQM 1.3:
> {code}
> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.3.2/jquery.mobile-1.3.2.min.js"></script>
> {code}
> It would be good if we have a place where users can configure what versions of JQ and JQM they want to inject.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBDS-2793) Align JDF and WFK quickstarts/examples/tutorials with a project layout that works with eclipse tooling
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBDS-2793?page=com.atlassian.jira.plugin.... ]
Gorkem Ercan updated JBDS-2793:
-------------------------------
Attachment: directoryStructure.tiff
directory structure used by the Eclipse tooling. Basically same structure as Cordova-cli except for the platforms folder. If platforms folder exists Eclipse tooling will just ignore them. Everything under www is merged with merges/${platform} for the platform builds. Everything else is ignored. We puth the config.xml under www folder by default but we will play nicely if it is at the root level like CLI does on later releases.
> Align JDF and WFK quickstarts/examples/tutorials with a project layout that works with eclipse tooling
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2793
> URL: https://issues.jboss.org/browse/JBDS-2793
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: aerogear-hybrid
> Reporter: Max Rydahl Andersen
> Assignee: Gorkem Ercan
> Fix For: 8.0.0.Beta2
>
> Attachments: directoryStructure.tiff
>
>
> wfk/jdf has or will get quickstarts/tutorials that works with cordova.
> Needs to sync up with them on what we support/dont support.
> Current suggestion is that the cordova app should be *separate* from the webapp, not "mixed" in.
> With a structure like:
> TicketMonster/
> www/config.xml
> plugins
> .project
> platforms
> ios
> android
> it can build both with cordova-cli and the eclipse tools (eclipse will ignore platforms directory)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBDS-2793) Align JDF and WFK quickstarts/examples/tutorials with a project layout that works with eclipse tooling
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBDS-2793?page=com.atlassian.jira.plugin.... ]
Gorkem Ercan edited comment on JBDS-2793 at 5/5/14 12:16 PM:
-------------------------------------------------------------
directory structure used by the Eclipse tooling. Basically same structure as Cordova-cli except for the platforms folder. If platforms folder exists Eclipse tooling will just ignore them. Everything under www is merged with merges/${platform} for the platform builds. Everything else is ignored. We put the config.xml under www folder by default but we will play nicely if it is at the root level like CLI does on later releases.
was (Author: gercan):
directory structure used by the Eclipse tooling. Basically same structure as Cordova-cli except for the platforms folder. If platforms folder exists Eclipse tooling will just ignore them. Everything under www is merged with merges/${platform} for the platform builds. Everything else is ignored. We puth the config.xml under www folder by default but we will play nicely if it is at the root level like CLI does on later releases.
> Align JDF and WFK quickstarts/examples/tutorials with a project layout that works with eclipse tooling
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2793
> URL: https://issues.jboss.org/browse/JBDS-2793
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: aerogear-hybrid
> Reporter: Max Rydahl Andersen
> Assignee: Gorkem Ercan
> Fix For: 8.0.0.Beta2
>
> Attachments: directoryStructure.tiff
>
>
> wfk/jdf has or will get quickstarts/tutorials that works with cordova.
> Needs to sync up with them on what we support/dont support.
> Current suggestion is that the cordova app should be *separate* from the webapp, not "mixed" in.
> With a structure like:
> TicketMonster/
> www/config.xml
> plugins
> .project
> platforms
> ios
> android
> it can build both with cordova-cli and the eclipse tools (eclipse will ignore platforms directory)
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-9479) Enhance custom classpath containers for additional support such as as7's modules tag
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9479?page=com.atlassian.jira.plugin... ]
Rob Stryker updated JBIDE-9479:
-------------------------------
Attachment: JBIDE-9479a.png
JBIDE-9479b.png
JBIDE-9479c.png
Screenshots
> Enhance custom classpath containers for additional support such as as7's modules tag
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-9479
> URL: https://issues.jboss.org/browse/JBIDE-9479
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 3.3.0.M3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.Beta2
>
> Attachments: JBIDE-9479a.png, JBIDE-9479b.png, JBIDE-9479c.png
>
>
> Enhance /JBIDE-1354 to allow for additional types of filesets.
> 1) Maintain backwards compatibility in terms of reading legacy files stores and functioning properly
> 2) If user makes a change, save in new persistance format
> 3) Add core elements for a 'module id' based classpath provider, only for jboss servers that have jboss-modules as a base
> 4) Expand UI to allow creation of a classpath element by using a module id instead of a basedir/includes/excludes pattern
> Out of scope for this issue: Core/UI for a per-facet customized response.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBDS-3025) Installer duplicates last folder in path causing errors (Mac OS X)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3025?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3025:
-------------------------------------
Cannot replicate that on 10.8.5. I'll check the code if there is a way to workaround it for Mavericks.
> Installer duplicates last folder in path causing errors (Mac OS X)
> ------------------------------------------------------------------
>
> Key: JBDS-3025
> URL: https://issues.jboss.org/browse/JBDS-3025
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta1
> Reporter: Michelle Murray
> Fix For: 8.0.0.Beta2
>
> Attachments: Installer_jrelocationerror.png
>
>
> Mac OS X Mavericks
> Universal installer, step 4 - choose JVM:
> * Click 'Specific Java JVM'
> * Click Browse to locate JDK or JRE
> * Navigate to find folder and click ok in file browser > the last folder is added twice to the displayed path
> In most cases this path now doesn't exist and causes error messages to this extent.
> !Installer_jrelocationerror.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (JBIDE-9479) Enhance custom classpath containers for additional support such as as7's modules tag
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9479?page=com.atlassian.jira.plugin... ]
Rob Stryker commented on JBIDE-9479:
------------------------------------
I'll add some screenshots. Just so you know, though, I believe I have not over-loaded terms at all. Fileset is still used in the legacy case only, and, I *think*, I have successfully renamed appropriate methods, signatures, and comments, to use IRuntimePathProvider[] wherever required.
Some classes that did require refactoring were implementations of IRuntimePathProvider and are filesets, while the new implementation is not.
It's possible I missed some signatures, though, so I'll double-check to find them.
> Enhance custom classpath containers for additional support such as as7's modules tag
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-9479
> URL: https://issues.jboss.org/browse/JBIDE-9479
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 3.3.0.M3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.Beta2
>
>
> Enhance /JBIDE-1354 to allow for additional types of filesets.
> 1) Maintain backwards compatibility in terms of reading legacy files stores and functioning properly
> 2) If user makes a change, save in new persistance format
> 3) Add core elements for a 'module id' based classpath provider, only for jboss servers that have jboss-modules as a base
> 4) Expand UI to allow creation of a classpath element by using a module id instead of a basedir/includes/excludes pattern
> Out of scope for this issue: Core/UI for a per-facet customized response.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months