[JBoss JIRA] (JBIDE-18952) Project Import is not possible when 'www' is an Eclipse linked folder
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18952?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18952:
-----------------------------------
Fix Version/s: 4.2.3.Beta1
(was: 4.2.3.Final)
> Project Import is not possible when 'www' is an Eclipse linked folder
> ---------------------------------------------------------------------
>
> Key: JBIDE-18952
> URL: https://issues.jboss.org/browse/JBIDE-18952
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Final
> Reporter: Vineet Reynolds
> Assignee: Gorkem Ercan
> Fix For: 4.2.3.Beta1
>
>
> Related to JBIDE-18711 and WFK2-822, project import is not possible when the 'www' directory is in an Eclipse linked folder. No projects are shown in the 'Cordova Project Import' dialog. It seems like Eclipse linked folders are not resolved in the project import dialog.
> Converting the 'www' directory back to a symbolic link or a real directory ensures that import succeeds.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18878) Eclipse livelock(?) at startup with hibernate builder in stacktrace
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18878?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-18878:
----------------------------------------
Yes it's reported as fixed in SR2 R4_2_maintenance.
> Eclipse livelock(?) at startup with hibernate builder in stacktrace
> -------------------------------------------------------------------
>
> Key: JBIDE-18878
> URL: https://issues.jboss.org/browse/JBIDE-18878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Assignee: Snjezana Peco
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
> Attachments: jstack-output.txt
>
>
> See attached [^jstack-output.txt]
> Console out is:
> {code}sh ./jbt420final.sh
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
> org.eclipse.m2e.logback.configuration: Logback config file: /home/eskimo/workspace/420cr2-test1/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.5.0.20140606-0033.xml
> org.eclipse.m2e.logback.configuration: Initializing logback
> java.lang.ClassCastException: org.eclipse.osgi.internal.framework.EquinoxConfiguration$1 cannot be cast to java.lang.String
> at org.eclipse.m2e.logback.configuration.LogHelper.logJavaProperties(LogHelper.java:26)
> at org.eclipse.m2e.logback.configuration.LogPlugin.loadConfiguration(LogPlugin.java:189)
> at org.eclipse.m2e.logback.configuration.LogPlugin.configureLogback(LogPlugin.java:144)
> at org.eclipse.m2e.logback.configuration.LogPlugin.access$2(LogPlugin.java:107)
> at org.eclipse.m2e.logback.configuration.LogPlugin$1.run(LogPlugin.java:62)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Dec 05, 2014 3:41:58 PM org.hibernate.eclipse.HibernatePlugin start
> INFO: HibernatePlugin Started{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18878) Eclipse livelock(?) at startup with hibernate builder in stacktrace
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18878?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18878:
-----------------------------------
Fix Version/s: 4.2.3.Beta1
(was: 4.2.3.Final)
> Eclipse livelock(?) at startup with hibernate builder in stacktrace
> -------------------------------------------------------------------
>
> Key: JBIDE-18878
> URL: https://issues.jboss.org/browse/JBIDE-18878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Assignee: Snjezana Peco
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
> Attachments: jstack-output.txt
>
>
> See attached [^jstack-output.txt]
> Console out is:
> {code}sh ./jbt420final.sh
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
> org.eclipse.m2e.logback.configuration: Logback config file: /home/eskimo/workspace/420cr2-test1/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.5.0.20140606-0033.xml
> org.eclipse.m2e.logback.configuration: Initializing logback
> java.lang.ClassCastException: org.eclipse.osgi.internal.framework.EquinoxConfiguration$1 cannot be cast to java.lang.String
> at org.eclipse.m2e.logback.configuration.LogHelper.logJavaProperties(LogHelper.java:26)
> at org.eclipse.m2e.logback.configuration.LogPlugin.loadConfiguration(LogPlugin.java:189)
> at org.eclipse.m2e.logback.configuration.LogPlugin.configureLogback(LogPlugin.java:144)
> at org.eclipse.m2e.logback.configuration.LogPlugin.access$2(LogPlugin.java:107)
> at org.eclipse.m2e.logback.configuration.LogPlugin$1.run(LogPlugin.java:62)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Dec 05, 2014 3:41:58 PM org.hibernate.eclipse.HibernatePlugin start
> INFO: HibernatePlugin Started{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18914) Spring cleaning for /targetplatforms/ folder
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18914?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18914:
-----------------------------------
Fix Version/s: (was: 4.2.3.Final)
> Spring cleaning for /targetplatforms/ folder
> --------------------------------------------
>
> Key: JBIDE-18914
> URL: https://issues.jboss.org/browse/JBIDE-18914
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, updatesite
> Affects Versions: 4.2.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0].
> [0] http://download.jboss.org/jbosstools/targetplatforms/
> Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]:
> {code}
> [DIR] 3.62.0.Final-SNAPSHOT/
> [DIR] 3.72.0.Final-SNAPSHOT/
> [DIR] 4.20.5.Final-SNAPSHOT/
> [DIR] 4.20.6.Final-SNAPSHOT/
> [DIR] 4.21.3.Final-SNAPSHOT/
> [DIR] 4.21.4.Final-SNAPSHOT/
> [DIR] 4.22.0.Final-SNAPSHOT/
> [DIR] 4.22.1.Final-SNAPSHOT/
> [DIR] 4.22.2.Final-SNAPSHOT/
> {code}
> Then we can purge all the 4.\{3?,4?}.\*.\*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1].
> [1] http://download.jboss.org/jbosstools/static/targetplatforms/
> I believe we can also purge things like 4.40.0.Beta* from here [2]:
> [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar...
> But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18177:
-----------------------------------
Fix Version/s: 4.2.3.Beta1
(was: 4.2.3.Final)
> Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18177
> URL: https://issues.jboss.org/browse/JBIDE-18177
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Labels: f2f2014, new_and_noteworthy
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
> Attachments: 2014-12-10 15.03.bmml, 2014-12-10 15.03.png, restart.jpg
>
>
> Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner)
> if he says okey - we set a flag somewhere to not start xulrunner.
> user restart - user is happy.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months