[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-15714:
------------------------------------------------
{quote}#2 I don't follow what this problem is ? why would we need to refresh the browser when we already are connecting to the browser used in the visual editor ?{quote}
Source tab also need to have content assist option, so we need it to be connected with browser.
> Dynamic content assist for AngularJS expressions in html files
> --------------------------------------------------------------
>
> Key: JBIDE-15714
> URL: https://issues.jboss.org/browse/JBIDE-15714
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: Diagram.gliffy, vpe.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15714:
---------------------------------------------
#1 can't we just put a placeholder saying "content assist loading...try again" or similar and if I choose it we just do the content assist again ?
#2 I don't follow what this problem is ? why would we need to refresh the browser when we already are connecting to the browser used in the visual editor ?
> Dynamic content assist for AngularJS expressions in html files
> --------------------------------------------------------------
>
> Key: JBIDE-15714
> URL: https://issues.jboss.org/browse/JBIDE-15714
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: Diagram.gliffy, vpe.png
>
>
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19568) central check for updates fails silently when provisioning errors
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-19568:
-------------------------------------------
Summary: central check for updates fails silently when provisioning errors
Key: JBIDE-19568
URL: https://issues.jboss.org/browse/JBIDE-19568
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Reporter: Max Rydahl Andersen
while trying to check JBIDE-18559 I clicked "checked for updates" in central and got nothing, not even a dialog.
In error log it was reporting this:
org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/Users/max/code/jbdevstudio/linuxtools-docker/org.eclipse.linuxtools.docker.core/target/.
at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116)
at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:284)
at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:191)
at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:378)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117)
at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102)
at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83)
at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
would have expected we told the user about this error.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-12161) Deploy application to JBoss AS 7 in domain mode
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12161?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-12161:
---------------------------------------------
Okey - please then open a JBDS feature request jira and provide details etc. and we'll need to get this raised to the right PM's to prioritize and get into play.
Since honestly, we have not seen much request nor usecases where domain mode is *required* and it adds alot of complexity compared to all the other deployment approaches thus it been kept out of the priority list.
> Deploy application to JBoss AS 7 in domain mode
> -----------------------------------------------
>
> Key: JBIDE-12161
> URL: https://issues.jboss.org/browse/JBIDE-12161
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 3.3.0.CR1
> Environment: Any.
> Reporter: Humberto Ferreira da Luz Jr.
> Assignee: Rob Stryker
> Labels: f2f2012
> Fix For: 4.2.x
>
>
> I think JBoss Tools should be able to deploy an application to JBoss AS 7 in domain mode.
> We would choose an specific server group (or any) and the application would be automatically deployed (I guess JBoss AS CLI could be directly used by JBoss Tools instead of ftp, ssh...).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Rastislav Wagner updated JBIDE-19536:
-------------------------------------
Attachment: cdi_jstack
I used bot tests to reproduce, that's why you will see them in attached stack trace.
Workspace isnt blocked. I can create other projects/add classes..however if I add something what needs CDI validation to blocked project it never gets validated.
> 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: cdi
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha2
>
> Attachments: cdi_jstack
>
>
> 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.3.11#6341)
11 years