[JBoss JIRA] (JBIDE-20149) Standard indentation functionality doesn't work
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20149?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-20149:
----------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.Beta2)
> Standard indentation functionality doesn't work
> -----------------------------------------------
>
> Key: JBIDE-20149
> URL: https://issues.jboss.org/browse/JBIDE-20149
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.3.0.Beta1
> Environment: Eclipse Mars, Windows, Java 8, 64 bit
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Fix For: 4.3.0.CR1
>
>
> When nothing is selected, the tab key works, but shift-tab doesn't do anything (should unindent). Nor tab nor shift-tab does anything when selecting multiple lines (to indent/unindent a whole block of text).
> FTL (and HTML) needs to be indented to remain readable. Thus the plain text editor of Eclipse (where indentation commands works as expected) still is often more usable for editing templates than the FTL editor.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3453) Launch after installation results in 'not responding'
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3453?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3453:
--------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta2)
> Launch after installation results in 'not responding'
> -----------------------------------------------------
>
> Key: JBDS-3453
> URL: https://issues.jboss.org/browse/JBDS-3453
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Environment: Fedora 20, 64-bit
> installer run with OpenJDK 1.7.0_79
> devstudio run with OpenJDK 1.8.0_45
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 9.0.0.CR1
>
> Attachments: .log, jstacks
>
>
> When I try to launch JBDS from the installer, which I run with Java 7, after choosing a workspace (using a clean workspace btw.) the 'loading' splash disappears shortly after it shows up (and the progress bar is still somewhere around the beginning).
> Then a blank JBDS window appears and about 10 - 20 seconds later a 'Not Responding' dialog appears followed by the rest of JBDS right away.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3450:
--------------------------------
Fix Version/s: 9.0.0.CR1
(was: 9.0.0.Beta2)
> installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3450
> URL: https://issues.jboss.org/browse/JBDS-3450
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 9.0.0.CR1
>
> Attachments: jbds-installer_step4-jvm-selection.png
>
>
> {quote}
> (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min
> (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS.
> (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK)
> (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine
> (2015-06-02 16:39:02) joshuaw: was found after searching the following locations:
> (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java
> (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java?
> (2015-06-02 16:39:40) joshuaw: let me check
> 16:40
> (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it
> (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :(
> (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist?
> (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file
> (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update?
> (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist
> (2015-06-02 16:42:32) nickboldt: aha
> (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8*
> (2015-06-02 16:42:48) nickboldt: pwd
> (2015-06-02 16:42:52) nickboldt: put that in your ini file
> (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file
> (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk
> (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39
> (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39
> (2015-06-02 16:46:33) joshuaw: stupid minor minor version update
> (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ?
> (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file
> (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion
> (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini
> (2015-06-02 17:55:27) nickboldt: -vm
> (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> (2015-06-02 17:55:36) maxandersen: thats bad
> (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :(
> (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ?
> {quote}
> It's possible the installer is using the CURRENT value of alternatives path for JDK...
> {code}
> $➔ alternatives --display java
> java - status is manual.
> link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071
> {code}
> So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3463) Headless installer should at least warn when running on Java 7
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3463?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3463:
--------------------------------
Sprint: Sprint #7 July 2015 (was: Sprint #6 July 2015)
> Headless installer should at least warn when running on Java 7
> --------------------------------------------------------------
>
> Key: JBDS-3463
> URL: https://issues.jboss.org/browse/JBDS-3463
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 9.0.0.CR1
>
> Attachments: InstallConfigRecord.xml
>
>
> While the GUI installer won't let you complete the installation without choosing Java 8 or higher, the headless installer doesn't care.
> If you give it a config with path to Java 7, it will install everything and set Java 7 as -vm in jbdevstudio.ini. I think it should behave consistently with the GUI or at least warn that the Java I'm installing with is not supported anymore.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19590:
----------------------------------
Sprint: Sprint #7 July 2015 (was: Sprint #6 July 2015)
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.CR1
>
> Attachments: hibernate-psf-import.mp4, oomph-installer-hibernate-codebase.png
>
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3453) Launch after installation results in 'not responding'
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3453?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3453:
--------------------------------
Sprint: Sprint #7 July 2015 (was: Sprint #6 July 2015)
> Launch after installation results in 'not responding'
> -----------------------------------------------------
>
> Key: JBDS-3453
> URL: https://issues.jboss.org/browse/JBDS-3453
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Environment: Fedora 20, 64-bit
> installer run with OpenJDK 1.7.0_79
> devstudio run with OpenJDK 1.8.0_45
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 9.0.0.Beta2
>
> Attachments: .log, jstacks
>
>
> When I try to launch JBDS from the installer, which I run with Java 7, after choosing a workspace (using a clean workspace btw.) the 'loading' splash disappears shortly after it shows up (and the progress bar is still somewhere around the beginning).
> Then a blank JBDS window appears and about 10 - 20 seconds later a 'Not Responding' dialog appears followed by the rest of JBDS right away.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3450:
--------------------------------
Sprint: Sprint #7 July 2015 (was: Sprint #6 July 2015)
> installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3450
> URL: https://issues.jboss.org/browse/JBDS-3450
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 9.0.0.Beta2
>
> Attachments: jbds-installer_step4-jvm-selection.png
>
>
> {quote}
> (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min
> (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS.
> (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK)
> (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine
> (2015-06-02 16:39:02) joshuaw: was found after searching the following locations:
> (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java
> (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java?
> (2015-06-02 16:39:40) joshuaw: let me check
> 16:40
> (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it
> (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :(
> (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist?
> (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file
> (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update?
> (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist
> (2015-06-02 16:42:32) nickboldt: aha
> (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8*
> (2015-06-02 16:42:48) nickboldt: pwd
> (2015-06-02 16:42:52) nickboldt: put that in your ini file
> (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file
> (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk
> (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39
> (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39
> (2015-06-02 16:46:33) joshuaw: stupid minor minor version update
> (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ?
> (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file
> (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion
> (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini
> (2015-06-02 17:55:27) nickboldt: -vm
> (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> (2015-06-02 17:55:36) maxandersen: thats bad
> (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :(
> (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ?
> {quote}
> It's possible the installer is using the CURRENT value of alternatives path for JDK...
> {code}
> $➔ alternatives --display java
> java - status is manual.
> link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java
> /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071
> {code}
> So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-20149) Standard indentation functionality doesn't work
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20149?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-20149:
----------------------------------
Sprint: Sprint #7 July 2015 (was: Sprint #6 July 2015)
> Standard indentation functionality doesn't work
> -----------------------------------------------
>
> Key: JBIDE-20149
> URL: https://issues.jboss.org/browse/JBIDE-20149
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.3.0.Beta1
> Environment: Eclipse Mars, Windows, Java 8, 64 bit
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Fix For: 4.3.0.Beta2
>
>
> When nothing is selected, the tab key works, but shift-tab doesn't do anything (should unindent). Nor tab nor shift-tab does anything when selecting multiple lines (to indent/unindent a whole block of text).
> FTL (and HTML) needs to be indented to remain readable. Thus the plain text editor of Eclipse (where indentation commands works as expected) still is often more usable for editing templates than the FTL editor.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-17281) parent/pom.xml build/plugins should reference plugins defined build/pluginManagement
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17281?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17281:
----------------------------------
Sprint: Sprint #7 July 2015 (was: Sprint #6 July 2015)
> parent/pom.xml build/plugins should reference plugins defined build/pluginManagement
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-17281
> URL: https://issues.jboss.org/browse/JBIDE-17281
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Optional
> Fix For: 4.3.0.CR1
>
>
> The Idea is to move all what we have in build/plugins to build/pluginManagement and leave only plugins with groupId and artifactid in build/plugins. It would let to do further clean up and reduce clutter in jbosstools modules like:
> - remove <version>${tychoVersion}</version>
> - move jacoco plugin to tests/pom.xml
> - move update site manipulations to site/pom.xml
> - move ant task runner configuration to parent/pom.xml#pluginManagement node for easy reuse
> - etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months