[JBoss JIRA] (JBIDE-10155) JavaScript content assist issue with jQuery, but likely more
by Jay Balunas (Created) (JIRA)
JavaScript content assist issue with jQuery, but likely more
------------------------------------------------------------
Key: JBIDE-10155
URL: https://issues.jboss.org/browse/JBIDE-10155
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.3.0.M4
Reporter: Jay Balunas
Content assist with JavaScript with jQuery not working, or respecting namespaces. Most JavaScript content assist was fine.
{code:JavaScript}
<script type="text/javascript">
$(document).ready(function() {
//Fetches the initial member table
updateMemberTable();
//Register a event listener on the sumbit action
$('#reg').submit(function(event) {
event.preventDefault();
var formValues = $(this).serialize();
registerMember(formValues);
});
});
</script>
{code}
Any call to "$('foo')." does not show any content assist. Using "jquery('foo'." instead of $ partially worked, but still not 100%. Not all the expected values are there. This makes me think there is two issues.
To see the problem import the project I attached and try out desktop.html, or app.js.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBIDE-12520) Add Test of CDIProjectAsYouType
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-12520:
---------------------------------------------
Summary: Add Test of CDIProjectAsYouType
Key: JBIDE-12520
URL: https://issues.jboss.org/browse/JBIDE-12520
Project: Tools (JBoss Tools)
Issue Type: Task
Affects Versions: 3.3.0.Final
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.0.0.Alpha1
This test should modify text in open editor, create instance of CDIProjectAsYouType for the modified resource and query it. This will help find model problems instead of guessing if model is to blame when validation or code assistant tests fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBIDE-12490) Improve type resolution performance
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-12490:
---------------------------------------------
Summary: Improve type resolution performance
Key: JBIDE-12490
URL: https://issues.jboss.org/browse/JBIDE-12490
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Affects Versions: 3.3.0.Final
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.0.0.M1
Method IType.resolveType(String typeName) is rather slow - it takes about 5ms for a class with ~20 imports and ~3 super types. For a middle size project with ~500 classes and ~100 type references per class it will take about 4 minutes to resolve all of them. We should try to do our best to resolve type in a simplified way and invoke IType.resolveType only when it fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBIDE-12514) Do not have jobs blocked by upstream
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-12514:
--------------------------------------
Summary: Do not have jobs blocked by upstream
Key: JBIDE-12514
URL: https://issues.jboss.org/browse/JBIDE-12514
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Nick Boldt
Currently, when a component is building, all components relying on it are blocked and have to wait for this one to finish before running. If another of their deps is waiting and builds before, it waits over and over again.
We should disable this lock so builds can perform in parallel. It may cause some failure because of sync from times to times, but we'll probably save hours of wait for feedback.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBIDE-12512) Fix cascading builds related to runtime pushdown
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-12512:
-----------------------------------
Summary: Fix cascading builds related to runtime pushdown
Key: JBIDE-12512
URL: https://issues.jboss.org/browse/JBIDE-12512
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 4.0.0.Alpha1
Reporter: Rob Stryker
Assignee: Mickael Istria
Fix For: 4.0.0.Alpha1
The Runtime component has been pushed down from the top of the stack to the bottom.
For runtime-soa, there should be no changes, as it depended on runtime already.
1) ASTools must now be kicked if runtime changes
2) Seam must now be kicked if runtime changes
Other builds that already got kicked should remain kicked. I assume project examples is one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBIDE-12513) Update runtimes plugin versions
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-12513:
-----------------------------------
Summary: Update runtimes plugin versions
Key: JBIDE-12513
URL: https://issues.jboss.org/browse/JBIDE-12513
Project: Tools (JBoss Tools)
Issue Type: Task
Components: runtime detection
Affects Versions: 4.0.0.Alpha1
Reporter: Rob Stryker
Assignee: Snjezana Peco
Fix For: 4.0.0.Alpha1
With a pushdown and the coming large api changes, we should increment to a new major version runtime detection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months