[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19536:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.3.x)
(was: 4.4.0.Alpha1)
> Infinite job loop when creating project
> ---------------------------------------
>
> Key: JBIDE-19536
> URL: https://issues.jboss.org/browse/JBIDE-19536
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Rastislav Wagner
> Priority: Critical
> Fix For: 4.4.x
>
> Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump, workspace_jbds9_endless_building_loop.rar
>
>
> Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974
> I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20387:
-----------------------------------
Story Points: 1 (was: 3)
> Use column number when navigating to errors, and more
> -----------------------------------------------------
>
> Key: JBIDE-20387
> URL: https://issues.jboss.org/browse/JBIDE-20387
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Affects Versions: 4.3.0.Beta2
> Reporter: Daniel Dekany
> Assignee: Alexey Kazakov
> Fix For: 4.4.0.Alpha1
>
>
> The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}):
> * {{getColumnNumber()}}, {{getEndColumnNumber()}}
> * {{getEndLineNumber()}}
> * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20387:
--------------------------------------
Assignee: Alexey Kazakov (was: Denis Golovin)
> Use column number when navigating to errors, and more
> -----------------------------------------------------
>
> Key: JBIDE-20387
> URL: https://issues.jboss.org/browse/JBIDE-20387
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Affects Versions: 4.3.0.Beta2
> Reporter: Daniel Dekany
> Assignee: Alexey Kazakov
> Fix For: 4.4.0.Alpha1
>
>
> The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}):
> * {{getColumnNumber()}}, {{getEndColumnNumber()}}
> * {{getEndLineNumber()}}
> * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21234) release webtools site for Eclipse 4.4 Neon to so WTP 3.8 discovery upstream can find it
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21234?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21234:
------------------------------------
Just need to verify this works and that the version of JBT found is the Neon one. Seems to be working fine.
{code}
./plugins/org.jboss.ide.eclipse.as.jmx.integration_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.rse.ui_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.classpath.ui_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.ui.mbeans_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.rse.core_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.wtp.core_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.management.core_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.core_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.tools.runtime.core_3.2.0.Alpha1-v20160421-1235-B915.jar
./plugins/org.jboss.tools.runtime.ui_3.2.0.Alpha1-v20160421-1235-B915.jar
./plugins/org.jboss.tools.as.catalog_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.management.wildfly9_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.management.as7_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.doc.user_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.classpath.core_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.archives.webtools_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.ui_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.wtp.ui_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.tools.as.runtimes.integration_3.2.0.Alpha1-v20160421-0826-B947.jar
./plugins/org.jboss.ide.eclipse.as.dmr_3.2.0.Alpha1-v20160421-0826-B947.jar
./features/org.jboss.ide.eclipse.as.feature_3.2.0.Alpha1-v20160421-0826-B947
./features/org.jboss.ide.eclipse.as.server.rse.integration.feature_3.2.0.Alpha1-v20160421-0826-B947
./features/org.jboss.ide.eclipse.as.archives.integration.feature_3.2.0.Alpha1-v20160421-0826-B947
./features/org.jboss.tools.runtime.core.feature_3.2.0.Alpha1-v20160421-1235-B915
./features/org.jboss.ide.eclipse.as.jmx.integration.feature_3.2.0.Alpha1-v20160421-0826-B947
./features/org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.2.0.Alpha1-v20160421-0826-B947
{code}
> release webtools site for Eclipse 4.4 Neon to so WTP 3.8 discovery upstream can find it
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-21234
> URL: https://issues.jboss.org/browse/JBIDE-21234
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, updatesite, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> Need a semi-working placeholder (even if it's a weak first alpha or copy of JBT 4.4.0's site) so that WTP can resolve a valid site for server adapters.
> Content that needs to be copied is here:
> http://download.jboss.org/jbosstools/neon/snapshots/updates/
> Eventually we'll have a first Alpha and the symlink can be updated to point here:
> http://download.jboss.org/jbosstools/mars/development/updates/
> Once we release 4.4.0.Final, we can then update the symlink to point here:
> http://download.jboss.org/jbosstools/mars/stable/updates/
> Upstream issue:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=484041
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20387:
-----------------------------------
Sprint: devex #6 April 2016
> Use column number when navigating to errors, and more
> -----------------------------------------------------
>
> Key: JBIDE-20387
> URL: https://issues.jboss.org/browse/JBIDE-20387
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Affects Versions: 4.3.0.Beta2
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Fix For: 4.4.0.Alpha1
>
>
> The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}):
> * {{getColumnNumber()}}, {{getEndColumnNumber()}}
> * {{getEndLineNumber()}}
> * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months