[JBoss JIRA] (JBTIS-422) Lots of errors when we try to install JBDS-IS 8.0.1.GA from central
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-422?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-422:
------------------------------------
Attachment: error_log.txt
> Lots of errors when we try to install JBDS-IS 8.0.1.GA from central
> -------------------------------------------------------------------
>
> Key: JBTIS-422
> URL: https://issues.jboss.org/browse/JBTIS-422
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.1.GA
> Reporter: Andrej Podhradsky
> Attachments: error_log.txt
>
>
> Specify the integration stack discovery artifact:
> {code}
> ./jbdevstudio -vmargs \
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA/devstudio-integration-stack-directory.xml \
> -Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-development/ \
> -Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/earlyaccess/8.0-development/ \
> -Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyaccess.properties \
> -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA
> {code}
> then select Software/Update in JBoss Central and open Error Log
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBTIS-422) Lots of errors when we try to install JBDS-IS 8.0.1.GA from central
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-422:
---------------------------------------
Summary: Lots of errors when we try to install JBDS-IS 8.0.1.GA from central
Key: JBTIS-422
URL: https://issues.jboss.org/browse/JBTIS-422
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 8.0.1.GA
Reporter: Andrej Podhradsky
Specify the integration stack discovery artifact:
{code}
./jbdevstudio -vmargs \
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA/devstudio-integration-stack-directory.xml \
-Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-development/ \
-Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/earlyaccess/8.0-development/ \
-Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyaccess.properties \
-Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA
{code}
then select Software/Update in JBoss Central and open Error Log
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-19410 at 4/9/15 4:39 AM:
----------------------------------------------------------------
{quote}Mickael, considering your last change related to wrapping updateTitle(heading) inside display.asyncExec() you never ran the actual code, did you? {quote}
I have to admit I didn't try the last patch before pushing ;) But I just gave it a try now, and it's working fine on my machine. What did you find wrong? I'm just changing the asyncExec by a syncExec because async in an (async) job is too much async.
The root cause of this failure are explained in previous comments (mainly #2 and #8). This is a corner-case of using PDE Launch Configuration without p2 enabled, such issue doesn't exist in real package and the change is actually just some "powder" to hide the fact that dev-mode doesn't support p2 by default. Since this doesn't happen in "real-life", I don't think we need more effort regarding messages.
If you want to fully try the Central functionality in dev-mode, you have to tweak your PDE Launch Configuration to enable p2, as explained in comment #2.
was (Author: mickael_istria):
{quote}Mickael, considering your last change related to wrapping updateTitle(heading) inside display.asyncExec() you never ran the actual code, did you? {quote}
I have to admit I didn't try the last patch ;) But I just gave it a try now, and it's working fine on my machine. What did you find wrong? I'm just changing the asyncExec by a syncExec because async in an (async) job is too much async.
The root cause of this failure are explained in previous comments (mainly #2 and #8). This is a corner-case of using PDE Launch Configuration without p2 enabled, such issue doesn't exist in real package and the change is actually just some "powder" to hide the fact that dev-mode doesn't support p2 by default. Since this doesn't happen in "real-life", I don't think we need more effort regarding messages.
If you want to fully try the Central functionality in dev-mode, you have to tweak your PDE Launch Configuration to enable p2, as explained in comment #2.
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19410:
----------------------------------------
{quote}Mickael, considering your last change related to wrapping updateTitle(heading) inside display.asyncExec() you never ran the actual code, did you? {quote}
I have to admit I didn't try the last patch ;) But I just gave it a try now, and it's working fine on my machine. What did you find wrong? I'm just changing the asyncExec by a syncExec because async in an (async) job is too much async.
The root cause of this failure are explained in previous comments (mainly #2 and #8). This is a corner-case of using PDE Launch Configuration without p2 enabled, such issue doesn't exist in real package and the change is actually just some "powder" to hide the fact that dev-mode doesn't support p2 by default. Since this doesn't happen in "real-life", I don't think we need more effort regarding messages.
If you want to fully try the Central functionality in dev-mode, you have to tweak your PDE Launch Configuration to enable p2, as explained in comment #2.
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
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:
---------------------------------------------
I would say if the user has disabled refresh then I would be fine saying he won't get uptodate content assist.
Thus i'm still not really following what the problem is besides that on the very first content assist the browser might not be fully initialized ?
> 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-19425) Error when loading projects in Central with Java 9
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19425?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19425:
---------------------------------------
Hmm, that seems strange.
The truth is that there is no rt.jar in the jdk.
But maybe it has been reorganized and is somewhere else now? And Eclipse is not yet fully ready? But I don't really know where it could be.
Like in the case of javafx (JBIDE-19050).
> Error when loading projects in Central with Java 9
> --------------------------------------------------
>
> Key: JBIDE-19425
> URL: https://issues.jboss.org/browse/JBIDE-19425
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Labels: Java9
> Fix For: 4.3.x
>
>
> Today I wanted to try out the latest build of Oracle JDK 1.9 beta and discovered a problem with central.
> When I started JBDS, I immediately got an error window pop up:
> {code}
> Refreshing JBoss Tutorials... has encountered a problem.
> An internal error occurred during: "Refreshing JBoss Tutorials...".
> javax/xml/bind/JAXBException
> {code}
> This is in the workspace log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2015-03-10 17:12:52.346
> !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...".
> !STACK 0
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.fetchCategories(ProjectExampleUtil.java:389)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:266)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:257)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:52)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.0.Alpha1-v20150213-0945-B3
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 5 more
> {code}
> I used JBDS 9.0.0.Alpha1 installed on OS X 10.10 Yosemite with Oracle JDK 1.9:
> {code}
> nattura:9.0.0 rasp$ java -version
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b53)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b53, mixed mode)
> {code}
> The consequence of this is that the "Start from scratch" section in Central is not loaded and shows "No entries found".
> Note: When I installed the same JBDS with Java 8, there was no error.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-624) JBDS-IS 8.0.1: Update Install Document
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-624?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-624:
-------------------------------
Description:
1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But:
a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites. Update: Four installation instructions are provided in the Install Guide at the moment. The first two are for installing JBDS, the latter two are for JBDS-IS. The latter two should have a prerequisite step that tells you to install JBDS and links to the relevant topics (the first two ways to install).
b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS
was:
1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But:
a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites
b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS
> JBDS-IS 8.0.1: Update Install Document
> ---------------------------------------
>
> Key: TOOLSDOC-624
> URL: https://issues.jboss.org/browse/TOOLSDOC-624
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Reporter: Misha Ali
> Assignee: Misha Ali
>
> 1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But:
> a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites. Update: Four installation instructions are provided in the Install Guide at the moment. The first two are for installing JBDS, the latter two are for JBDS-IS. The latter two should have a prerequisite step that tells you to install JBDS and links to the relevant topics (the first two ways to install).
> b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TOOLSDOC-624) JBDS-IS 8.0.1: Update Install Document
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-624?page=com.atlassian.jira.plug... ]
Misha Ali reassigned TOOLSDOC-624:
----------------------------------
Assignee: Supriya Bharadwaj (was: Misha Ali)
> JBDS-IS 8.0.1: Update Install Document
> ---------------------------------------
>
> Key: TOOLSDOC-624
> URL: https://issues.jboss.org/browse/TOOLSDOC-624
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Reporter: Misha Ali
> Assignee: Supriya Bharadwaj
>
> 1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But:
> a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites. Update: Four installation instructions are provided in the Install Guide at the moment. The first two are for installing JBDS, the latter two are for JBDS-IS. The latter two should have a prerequisite step that tells you to install JBDS and links to the relevant topics (the first two ways to install).
> b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19569?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19569:
---------------------------------------
[~kmarmaliykov], so at least that seems to be a bug then? That you can click a button in the visual preview and it will take you to the next page (where the link leads).
> Unable to switch pages shown in visual preview when editing mobile html5
> ------------------------------------------------------------------------
>
> Key: JBIDE-19569
> URL: https://issues.jboss.org/browse/JBIDE-19569
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
> Assignee: Konstantin Marmalyukov
>
> I'm not sure if my use case is valid or not.
> But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one.
> So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview.
> Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button?
> But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :)
> [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen reassigned JBDS-3384:
-----------------------------------------
Assignee: Rob Stryker (was: Max Rydahl Andersen)
> Investigate how the terminal changes in Mars will/should affect us
> -------------------------------------------------------------------
>
> Key: JBDS-3384
> URL: https://issues.jboss.org/browse/JBDS-3384
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: build, forge, openshift
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
>
> Terminal (console) support in eclipse mars is changing and we should
> make sure we adjust for it.
> Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html
> Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now.
> This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new.
> As we find what it entails we should link those issues to this jira.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19389) Cannot set timeout configuration to connect JDV server on Teiid designer
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19389?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19389:
-------------------------------------
Hi [~blafond], I'm not sure what's going on here. We already have the property IAS7ManagementDetails.PROPERTY_TIMEOUT,
Are you guys not sure how to use it or customize it? Or is it not functioning as intended?
It seems right now you all are using:
String resultString = JBoss7ManagerUtil.getService(parentServer).execute(new AS7ManagementDetails(parentServer), requestString);
You're not customizing the timeout at all. I'd suggest instead of simply instantiating the AS7ManagementDetails, you do something like this below:
private AS7ManagementDetails createTimeoutDetails(IServer server, int timeout) {
HashMap<String, Object> props = new HashMap<String, Object>();
props.put(IAS7ManagementDetails.PROPERTY_TIMEOUT, new Integer(timeout));
return new AS7ManagementDetails(server, props);
}
> Cannot set timeout configuration to connect JDV server on Teiid designer
> ------------------------------------------------------------------------
>
> Key: JBIDE-19389
> URL: https://issues.jboss.org/browse/JBIDE-19389
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Eiichi Nagai
> Assignee: Rob Stryker
>
> Describe the issue:
> The teiid-designer cannot connect to remote JDV server by timeout exceptions. However, the teiid-designer cannnot set timeout for it.
> {noformat}
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:336)
> at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:66)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:192)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:181)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:82)
> at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:153)
> at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
> at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742)
> at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setServerStarted(ControllableServerBehavior.java:201)
> at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:127)
> at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.preLaunchCheck(StandardRSEStartLaunchDelegate.java:72)
> at org.jboss.ide.eclipse.as.rse.core.subsystems.RSECommandLineLaunchController.preLaunchCheck(RSECommandLineLaunchController.java:103)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:325)
> ... 23 more
> Caused by: java.net.ConnectException: JBAS012144: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:144)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 25 more
> {noformat}
> Additional information:
> We want to set a property of "IAS7ManagementDetails.PROPERTY_TIMEOUT" via teiid-designer.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19389) Cannot set timeout configuration to connect JDV server on Teiid designer
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19389?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19389:
-------------------------------------
Sorry for the slow response but I've been on PTO.
> Cannot set timeout configuration to connect JDV server on Teiid designer
> ------------------------------------------------------------------------
>
> Key: JBIDE-19389
> URL: https://issues.jboss.org/browse/JBIDE-19389
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Eiichi Nagai
> Assignee: Rob Stryker
>
> Describe the issue:
> The teiid-designer cannot connect to remote JDV server by timeout exceptions. However, the teiid-designer cannnot set timeout for it.
> {noformat}
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:336)
> at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:66)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:192)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:181)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:82)
> at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:153)
> at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
> at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742)
> at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setServerStarted(ControllableServerBehavior.java:201)
> at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:127)
> at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.preLaunchCheck(StandardRSEStartLaunchDelegate.java:72)
> at org.jboss.ide.eclipse.as.rse.core.subsystems.RSECommandLineLaunchController.preLaunchCheck(RSECommandLineLaunchController.java:103)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:325)
> ... 23 more
> Caused by: java.net.ConnectException: JBAS012144: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:144)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 25 more
> {noformat}
> Additional information:
> We want to set a property of "IAS7ManagementDetails.PROPERTY_TIMEOUT" via teiid-designer.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19389) Cannot set timeout configuration to connect JDV server on Teiid designer
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19389?page=com.atlassian.jira.plugi... ]
Rob Stryker edited comment on JBIDE-19389 at 4/8/15 10:39 PM:
--------------------------------------------------------------
Hi [~blafond], I'm not sure what's going on here. We already have the property IAS7ManagementDetails.PROPERTY_TIMEOUT,
Are you guys not sure how to use it or customize it? Or is it not functioning as intended?
It seems right now you all are using:
String resultString = JBoss7ManagerUtil.getService(parentServer).execute(new AS7ManagementDetails(parentServer), requestString);
You're not customizing the timeout at all. I'd suggest instead of simply instantiating the AS7ManagementDetails, you do something like this below:
{code}
private AS7ManagementDetails createTimeoutDetails(IServer server, int timeout) {
HashMap<String, Object> props = new HashMap<String, Object>();
props.put(IAS7ManagementDetails.PROPERTY_TIMEOUT, new Integer(timeout));
return new AS7ManagementDetails(server, props);
}
{code}
was (Author: rob.stryker):
Hi [~blafond], I'm not sure what's going on here. We already have the property IAS7ManagementDetails.PROPERTY_TIMEOUT,
Are you guys not sure how to use it or customize it? Or is it not functioning as intended?
It seems right now you all are using:
String resultString = JBoss7ManagerUtil.getService(parentServer).execute(new AS7ManagementDetails(parentServer), requestString);
You're not customizing the timeout at all. I'd suggest instead of simply instantiating the AS7ManagementDetails, you do something like this below:
private AS7ManagementDetails createTimeoutDetails(IServer server, int timeout) {
HashMap<String, Object> props = new HashMap<String, Object>();
props.put(IAS7ManagementDetails.PROPERTY_TIMEOUT, new Integer(timeout));
return new AS7ManagementDetails(server, props);
}
> Cannot set timeout configuration to connect JDV server on Teiid designer
> ------------------------------------------------------------------------
>
> Key: JBIDE-19389
> URL: https://issues.jboss.org/browse/JBIDE-19389
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Eiichi Nagai
> Assignee: Rob Stryker
>
> Describe the issue:
> The teiid-designer cannot connect to remote JDV server by timeout exceptions. However, the teiid-designer cannnot set timeout for it.
> {noformat}
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:336)
> at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:66)
> at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:192)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:181)
> at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:82)
> at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:153)
> at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
> at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742)
> at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setServerStarted(ControllableServerBehavior.java:201)
> at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:127)
> at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.preLaunchCheck(StandardRSEStartLaunchDelegate.java:72)
> at org.jboss.ide.eclipse.as.rse.core.subsystems.RSECommandLineLaunchController.preLaunchCheck(RSECommandLineLaunchController.java:103)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:325)
> ... 23 more
> Caused by: java.net.ConnectException: JBAS012144: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:144)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 25 more
> {noformat}
> Additional information:
> We want to set a property of "IAS7ManagementDetails.PROPERTY_TIMEOUT" via teiid-designer.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-19453.
---------------------------------
Fix Version/s: 4.3.0.Alpha2
Resolution: Done
Well, it took all day, probably way more time than I should have justified on this bug. The actual solution I chose was to simply code the composite better to have a preferred width of 200 but to be able to scale based on its container.
The solution I spent all day TRYING to get working was to get the scrollbars in the ScrolledPageBook to show up. The reason that was failing was two-fold:
1) Any time I changed the style bits to H_SCROLL | V_SCROLL, the form toolkit would change the composite to grey (which looked fine in new server wizard but horrible in editor), and...
2) A bug upstream in ScrolledPageBook where the horizontal scrollbars refused to function properly. In short, the scrollbar would 'show', but, it always thought the control inside the scrollable composite was not larger than its container. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=464223 for more information.
Either way, the committed solution was much simpler and made more sense, so I learned a lot about properly coding FormLayout for preferred sizes.
> Remote host information does not fit in the server editor
> ---------------------------------------------------------
>
> Key: JBIDE-19453
> URL: https://issues.jboss.org/browse/JBIDE-19453
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
> Attachments: remote-runtime-does-not-fit.png
>
>
> Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it.
> !remote-runtime-does-not-fit.png!
> The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Description:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
Example:
During the search for references for class "SearchableBatchlet" like:
{code}
package batch;
import javax.batch.api.BatchProperty;
import javax.batch.api.Batchlet;
import javax.inject.Inject;
import javax.inject.Named;
@Named
public class SearchableBatchlet implements Batchlet {
@Inject @BatchProperty(name="secondName") String otherName;
@Override
public String process() throws Exception {
return null;
}
@Override
public void stop() throws Exception {
}
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableBatchletReferences.png!
2. Should be able to find references in job.xml files for Batch Artifact Property IField
Example:
During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
!FieldReference.png!
3. Should be able to find references in job.xml files for Exception Class IType
Example:
During the search for references for class "SearchableException" like:
{code}
package batch;
public class SearchableException extends Exception{
private static final long serialVersionUID = 1L;
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableExceptionReferences.png!
*Rename Participant*
1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named
Example:
During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring:
!BatchArtifactRename.png!
2. Should be able to add changes in Exception Class Rename for references in job.xml files.
Example:
During rename of class "SearchableException" changes for job.xml references should be added in Refactoring:
!ExceptionRename.png!
was:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
Example:
During the search for references for class "SearchableBatchlet" like:
{code}
package batch;
import javax.batch.api.BatchProperty;
import javax.batch.api.Batchlet;
import javax.inject.Inject;
import javax.inject.Named;
@Named
public class SearchableBatchlet implements Batchlet {
@Inject @BatchProperty(name="secondName") String otherName;
@Override
public String process() throws Exception {
return null;
}
@Override
public void stop() throws Exception {
}
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableBatchletReferences.png!
2. Should be able to find references in job.xml files for Batch Artifact Property IField
Example:
During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
!FieldReference.png!
3. Should be able to find references in job.xml files for Exception Class IType
Example:
During the search for references for class "SearchableException" like:
{code}
package batch;
public class SearchableException extends Exception{
private static final long serialVersionUID = 1L;
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableExceptionReferences.png!
*Rename Participant*
1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
Example:
During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring:
!BatchArtifactRename.png!
2. Should be able to add changes in Exception Class Rename for references in job.xml files.
Example:
During rename of class "SearchableException" changes for job.xml references should be added in Refactoring:
!ExceptionRename.png!
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> Example:
> During the search for references for class "SearchableException" like:
> {code}
> package batch;
> public class SearchableException extends Exception{
> private static final long serialVersionUID = 1L;
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableExceptionReferences.png!
> *Rename Participant*
> 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
> Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named
> Example:
> During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring:
> !BatchArtifactRename.png!
> 2. Should be able to add changes in Exception Class Rename for references in job.xml files.
> Example:
> During rename of class "SearchableException" changes for job.xml references should be added in Refactoring:
> !ExceptionRename.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Description:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
Example:
During the search for references for class "SearchableBatchlet" like:
{code}
package batch;
import javax.batch.api.BatchProperty;
import javax.batch.api.Batchlet;
import javax.inject.Inject;
import javax.inject.Named;
@Named
public class SearchableBatchlet implements Batchlet {
@Inject @BatchProperty(name="secondName") String otherName;
@Override
public String process() throws Exception {
return null;
}
@Override
public void stop() throws Exception {
}
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableBatchletReferences.png!
2. Should be able to find references in job.xml files for Batch Artifact Property IField
Example:
During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
!FieldReference.png!
3. Should be able to find references in job.xml files for Exception Class IType
Example:
During the search for references for class "SearchableException" like:
{code}
package batch;
public class SearchableException extends Exception{
private static final long serialVersionUID = 1L;
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableExceptionReferences.png!
*Rename Participant*
1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
Example:
During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring:
!BatchArtifactRename.png!
2. Should be able to add changes in Exception Class Rename for references in job.xml files.
Example:
During rename of class "SearchableException" changes for job.xml references should be added in Refactoring:
!ExceptionRename.png!
was:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
Example:
During the search for references for class "SearchableBatchlet" like:
{code}
package batch;
import javax.batch.api.BatchProperty;
import javax.batch.api.Batchlet;
import javax.inject.Inject;
import javax.inject.Named;
@Named
public class SearchableBatchlet implements Batchlet {
@Inject @BatchProperty(name="secondName") String otherName;
@Override
public String process() throws Exception {
return null;
}
@Override
public void stop() throws Exception {
}
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableBatchletReferences.png!
2. Should be able to find references in job.xml files for Batch Artifact Property IField
Example:
During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
!FieldReference.png!
3. Should be able to find references in job.xml files for Exception Class IType
Example:
During the search for references for class "SearchableException" like:
{code}
package batch;
public class SearchableException extends Exception{
private static final long serialVersionUID = 1L;
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableExceptionReferences.png!
*Rename Participant*
1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
Example:
During rename of class "SearchableBatchlet" changes for job.xml references should be created:
!BatchArtifactRename.png!
2. Should be able to add changes in Exception Class Rename for references in job.xml files.
Example:
During rename of class "SearchableException" changes for job.xml references should be created:
!ExceptionRename.png!
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> Example:
> During the search for references for class "SearchableException" like:
> {code}
> package batch;
> public class SearchableException extends Exception{
> private static final long serialVersionUID = 1L;
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableExceptionReferences.png!
> *Rename Participant*
> 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
> Example:
> During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring:
> !BatchArtifactRename.png!
> 2. Should be able to add changes in Exception Class Rename for references in job.xml files.
> Example:
> During rename of class "SearchableException" changes for job.xml references should be added in Refactoring:
> !ExceptionRename.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Description:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
Example:
During the search for references for class "SearchableBatchlet" like:
{code}
package batch;
import javax.batch.api.BatchProperty;
import javax.batch.api.Batchlet;
import javax.inject.Inject;
import javax.inject.Named;
@Named
public class SearchableBatchlet implements Batchlet {
@Inject @BatchProperty(name="secondName") String otherName;
@Override
public String process() throws Exception {
return null;
}
@Override
public void stop() throws Exception {
}
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableBatchletReferences.png!
2. Should be able to find references in job.xml files for Batch Artifact Property IField
Example:
During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
!FieldReference.png!
3. Should be able to find references in job.xml files for Exception Class IType
Example:
During the search for references for class "SearchableException" like:
{code}
package batch;
public class SearchableException extends Exception{
private static final long serialVersionUID = 1L;
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableExceptionReferences.png!
*Rename Participant*
1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
Example:
During rename of class "SearchableBatchlet" changes for job.xml references should be created:
!BatchArtifactRename.png!
2. Should be able to add changes in Exception Class Rename for references in job.xml files.
Example:
During rename of class "SearchableException" changes for job.xml references should be created:
!ExceptionRename.png!
was:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
Example:
During the search for references for class "SearchableBatchlet" like:
{code}
package batch;
import javax.batch.api.BatchProperty;
import javax.batch.api.Batchlet;
import javax.inject.Inject;
import javax.inject.Named;
@Named
public class SearchableBatchlet implements Batchlet {
@Inject @BatchProperty(name="secondName") String otherName;
@Override
public String process() throws Exception {
return null;
}
@Override
public void stop() throws Exception {
}
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableBatchletReferences.png!
2. Should be able to find references in job.xml files for Batch Artifact Property IField
Example:
During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
!FieldReference.png!
3. Should be able to find references in job.xml files for Exception Class IType
Example:
During the search for references for class "SearchableException" like:
{code}
package batch;
public class SearchableException extends Exception{
private static final long serialVersionUID = 1L;
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableExceptionReferences.png!
*Rename Participant*
1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> Example:
> During the search for references for class "SearchableException" like:
> {code}
> package batch;
> public class SearchableException extends Exception{
> private static final long serialVersionUID = 1L;
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableExceptionReferences.png!
> *Rename Participant*
> 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files.
> Example:
> During rename of class "SearchableBatchlet" changes for job.xml references should be created:
> !BatchArtifactRename.png!
> 2. Should be able to add changes in Exception Class Rename for references in job.xml files.
> Example:
> During rename of class "SearchableException" changes for job.xml references should be created:
> !ExceptionRename.png!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Attachment: BatchArtifactRename.png
ExceptionRename.png
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> Example:
> During the search for references for class "SearchableException" like:
> {code}
> package batch;
> public class SearchableException extends Exception{
> private static final long serialVersionUID = 1L;
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableExceptionReferences.png!
> *Rename Participant*
> 1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Description:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
Example:
During the search for references for class "SearchableBatchlet" like:
{code}
package batch;
import javax.batch.api.BatchProperty;
import javax.batch.api.Batchlet;
import javax.inject.Inject;
import javax.inject.Named;
@Named
public class SearchableBatchlet implements Batchlet {
@Inject @BatchProperty(name="secondName") String otherName;
@Override
public String process() throws Exception {
return null;
}
@Override
public void stop() throws Exception {
}
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableBatchletReferences.png!
2. Should be able to find references in job.xml files for Batch Artifact Property IField
Example:
During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
!FieldReference.png!
3. Should be able to find references in job.xml files for Exception Class IType
Example:
During the search for references for class "SearchableException" like:
{code}
package batch;
public class SearchableException extends Exception{
private static final long serialVersionUID = 1L;
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableExceptionReferences.png!
*Rename Participant*
1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
was:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
Example:
During the search for references for class "SearchableBatchlet" like:
{code}
package batch;
import javax.batch.api.BatchProperty;
import javax.batch.api.Batchlet;
import javax.inject.Inject;
import javax.inject.Named;
@Named
public class SearchableBatchlet implements Batchlet {
@Inject @BatchProperty(name="secondName") String otherName;
@Override
public String process() throws Exception {
return null;
}
@Override
public void stop() throws Exception {
}
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableBatchletReferences.png!
2. Should be able to find references in job.xml files for Batch Artifact Property IField
Example:
During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
!FieldReference.png!
3. Should be able to find references in job.xml files for Exception Class IType
*Rename Participant*
1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: FieldReference.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> Example:
> During the search for references for class "SearchableException" like:
> {code}
> package batch;
> public class SearchableException extends Exception{
> private static final long serialVersionUID = 1L;
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableExceptionReferences.png!
> *Rename Participant*
> 1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Attachment: SearchableExceptionReferences.png
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: FieldReference.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> *Rename Participant*
> 1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Attachment: FieldReference.png
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: FieldReference.png, SearchableBatchletReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> *Rename Participant*
> 1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Description:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
Example:
During the search for references for class "SearchableBatchlet" like:
{code}
package batch;
import javax.batch.api.BatchProperty;
import javax.batch.api.Batchlet;
import javax.inject.Inject;
import javax.inject.Named;
@Named
public class SearchableBatchlet implements Batchlet {
@Inject @BatchProperty(name="secondName") String otherName;
@Override
public String process() throws Exception {
return null;
}
@Override
public void stop() throws Exception {
}
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableBatchletReferences.png!
2. Should be able to find references in job.xml files for Batch Artifact Property IField
Example:
During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
!FieldReference.png!
3. Should be able to find references in job.xml files for Exception Class IType
*Rename Participant*
1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
was:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
Example:
During the search for references for class "SearchableBatchlet" like:
{code}
package batch;
import javax.batch.api.BatchProperty;
import javax.batch.api.Batchlet;
import javax.inject.Inject;
import javax.inject.Named;
@Named
public class SearchableBatchlet implements Batchlet {
@Inject @BatchProperty(name="secondName") String otherName;
@Override
public String process() throws Exception {
return null;
}
@Override
public void stop() throws Exception {
}
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableBatchletReferences.png!
2. Should be able to find references in job.xml files for Batch Artifact Property IField
3. Should be able to find references in job.xml files for Exception Class IType
*Rename Participant*
1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: SearchableBatchletReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> Example:
> During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this:
> !FieldReference.png!
> 3. Should be able to find references in job.xml files for Exception Class IType
> *Rename Participant*
> 1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Attachment: SearchableBatchletReferences.png
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: SearchableBatchletReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> 3. Should be able to find references in job.xml files for Exception Class IType
> *Rename Participant*
> 1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Attachment: (was: SearchableBatchletReferences.png)
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> 3. Should be able to find references in job.xml files for Exception Class IType
> *Rename Participant*
> 1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Attachment: SearchableBatchletReferences.png
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
> Attachments: SearchableBatchletReferences.png
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> 3. Should be able to find references in job.xml files for Exception Class IType
> *Rename Participant*
> 1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Description:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
Example:
During the search for references for class "SearchableBatchlet" like:
{code}
package batch;
import javax.batch.api.BatchProperty;
import javax.batch.api.Batchlet;
import javax.inject.Inject;
import javax.inject.Named;
@Named
public class SearchableBatchlet implements Batchlet {
@Inject @BatchProperty(name="secondName") String otherName;
@Override
public String process() throws Exception {
return null;
}
@Override
public void stop() throws Exception {
}
}
{code}
In the search result should be added references in jbob.xml files like this:
!SearchableBatchletReferences.png!
2. Should be able to find references in job.xml files for Batch Artifact Property IField
3. Should be able to find references in job.xml files for Exception Class IType
*Rename Participant*
1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
was:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
2. Should be able to find references in job.xml files for Batch Artifact Property IField
3. Should be able to find references in job.xml files for Exception Class IType
*Rename Participant*
1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> Example:
> During the search for references for class "SearchableBatchlet" like:
> {code}
> package batch;
> import javax.batch.api.BatchProperty;
> import javax.batch.api.Batchlet;
> import javax.inject.Inject;
> import javax.inject.Named;
> @Named
> public class SearchableBatchlet implements Batchlet {
>
> @Inject @BatchProperty(name="secondName") String otherName;
> @Override
> public String process() throws Exception {
> return null;
> }
> @Override
> public void stop() throws Exception {
> }
> }
> {code}
> In the search result should be added references in jbob.xml files like this:
> !SearchableBatchletReferences.png!
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> 3. Should be able to find references in job.xml files for Exception Class IType
> *Rename Participant*
> 1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Description:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
2. Should be able to find references in job.xml files for Batch Artifact Property IField
3. Should be able to find references in job.xml files for Exception Class IType
*Rename Participant*
1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
was:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
2. Should be able to find references in job.xml files for Batch Artifact Property
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> 2. Should be able to find references in job.xml files for Batch Artifact Property IField
> 3. Should be able to find references in job.xml files for Exception Class IType
> *Rename Participant*
> 1. Should be able to add changes in JDT Java Class Rename Refactoring for references in job.xml files.
--
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 Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-15714:
------------------------------------------------
{quote}The browser we are connecting to is the browser used in the preview tab is it not ?{quote}
Exactly, from preview tab, not from Visual/Source tab(user can disable refresh there, so we cannot use this browser)
{quote}and why would source tab now have content assist ? thats what this is all about.{quote}
There is no difference between source editor from source and visual/source parts. They both should use browser from Preview tab.
> 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-19507) Search and rename participants for Batch Artifacts
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-19507:
----------------------------------
Description:
*Search Participant*
1. Should be able to find references in job.xml files for Batch Artifact Class IType
2. Should be able to find references in job.xml files for Batch Artifact Property
> Search and rename participants for Batch Artifacts
> --------------------------------------------------
>
> Key: JBIDE-19507
> URL: https://issues.jboss.org/browse/JBIDE-19507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: batch
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha2
>
>
> *Search Participant*
> 1. Should be able to find references in job.xml files for Batch Artifact Class IType
> 2. Should be able to find references in job.xml files for Batch Artifact Property
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19568) Disable the "Check for update" button while a check for update is in progress
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19568:
--------------------------------
Summary: Disable the "Check for update" button while a check for update is in progress (was: Disable the "Check for update" button while an check for update is in progress)
> Disable the "Check for update" button while a check for update is in progress
> -----------------------------------------------------------------------------
>
> Key: JBIDE-19568
> URL: https://issues.jboss.org/browse/JBIDE-19568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
>
> 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-19568) Disable the "Check for update" button while an check for update is in progress
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-19568:
-----------------------------------
Assignee: Mickael Istria
> Disable the "Check for update" button while an check for update is in progress
> ------------------------------------------------------------------------------
>
> Key: JBIDE-19568
> URL: https://issues.jboss.org/browse/JBIDE-19568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
>
> 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-19568) Disable the "Check for update" button while an check for update is in progress
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19568:
--------------------------------
Summary: Disable the "Check for update" button while an check for update is in progress (was: central check for updates fails silently when provisioning errors)
> Disable the "Check for update" button while an check for update is in progress
> ------------------------------------------------------------------------------
>
> 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-19410) earlyaccess still not failing gracefully
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19410:
---------------------------------------
{quote}I hope you are just kidding.
Currently Im forced to disable central manually or live with slow startup and a modal dialog every time I start eclipse in Dev mode.
This did not happen in previous versions of central,
Thus this is a regression.
Please fix that or explain why we cannot just fix it with a simple if statement to check if p2 is actually available in this install. Thank you.{quote}
In previous central it was failing with NPE w/o any message or explanation see https://github.com/mickaelistria/jbosstools-central/commit/d9e82bb6ef425e....
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19190:
---------------------------------------------
not sure why this is assigned to me since nothing except #0 is related to me.
lets move it as its own repo. it does not seem to fit anywhere else and its supposed to be completely independent anyway.
Can you fix the rest ?
> migrate VersionWatch to jbosstools-* repo
> -----------------------------------------
>
> Key: JBIDE-19190
> URL: https://issues.jboss.org/browse/JBIDE-19190
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Jiri Peterka
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly.
> 1. remove all refs to QA Jenkins file paths to make this more generic
> 2. migrate those internal file paths into jenkins config.xml files
> 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here:
> http://download.jboss.org/jbosstools/updates/scripted-installation/
> https://devstudio.redhat.com/download/scripted-install/
> 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report
--
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)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19568:
---------------------------------------------
so I did not notice the oomph part here - that is interesting and worrying if oomph is hooking into things.
But back to the original issue - after about 5 minutes a dialog showed up showing what was being suggested for update.
Is there a way the button could be disabled until the first check has finsihed or tell the user an update is already running ?
> 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-19568) central check for updates fails silently when provisioning errors
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19568:
----------------------------------------
Component/s: (was: upstream)
> 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-19410) earlyaccess still not failing gracefully
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19410:
---------------------------------------
{quote}By the line numbers exception is for code from jbosstools-4.2.x branch.
InstallationChecker.java#L101 fails because iusForFamily is null. Proposed PR doesn't deal with NPE. It will still reported the same way.{quote}
that is not right. I mixed it up with JBIDE-18542.
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18542) NPE during "Check installation for Early Access"
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18542?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-18542:
---------------------------------------
Easiest manual way to replicate just assign null in code and run it. Question remains why sometimes null value was returned? Was it fixed?
> NPE during "Check installation for Early Access"
> ------------------------------------------------
>
> Key: JBIDE-18542
> URL: https://issues.jboss.org/browse/JBIDE-18542
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR2
> Reporter: Rob Cernich
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.2.x, 4.3.0.Alpha2
>
>
> I got the following exception upon restart after updating to CR2 from the following site: http://download.jboss.org/jbosstools/updates/staging/luna/
> {noformat}
> java.lang.NullPointerException
> at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:99)
> at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79)
> at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72)
> at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:574)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19410:
----------------------------------
Comment: was deleted
(was: easiest manual way to replicate just assign null in code and run it. Question remains why sometimes null value returned?)
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18542) NPE during "Check installation for Early Access"
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18542?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-18542:
---------------------------------------
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:4477)
at org.eclipse.swt.SWT.error(SWT.java:4392)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3793)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3431)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
Caused by: java.lang.NullPointerException
at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:106)
at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:97)
at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:90)
at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText.updateTitle(JBossCentralEditor.java:654)
at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText.access$0(JBossCentralEditor.java:641)
at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3$1.run(JBossCentralEditor.java:584)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
... 24 more
> NPE during "Check installation for Early Access"
> ------------------------------------------------
>
> Key: JBIDE-18542
> URL: https://issues.jboss.org/browse/JBIDE-18542
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR2
> Reporter: Rob Cernich
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.2.x, 4.3.0.Alpha2
>
>
> I got the following exception upon restart after updating to CR2 from the following site: http://download.jboss.org/jbosstools/updates/staging/luna/
> {noformat}
> java.lang.NullPointerException
> at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:99)
> at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79)
> at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72)
> at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:574)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-19410:
----------------------------------
Comment: was deleted
(was: Proposed PR has the same problem Max mentioned:
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:4477)
at org.eclipse.swt.SWT.error(SWT.java:4392)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3793)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3431)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
Caused by: java.lang.NullPointerException
at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:106)
at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:97)
at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:90)
at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText.updateTitle(JBossCentralEditor.java:654)
at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText.access$0(JBossCentralEditor.java:641)
at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3$1.run(JBossCentralEditor.java:584)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
... 24 more)
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19410:
---------------------------------------
easiest manual way to replicate just assign null in code and run it. Question remains why sometimes null value returned?
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19410:
---------------------------------------
Proposed PR has the same problem Max mentioned:
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:4477)
at org.eclipse.swt.SWT.error(SWT.java:4392)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3793)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3431)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:648)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:592)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
Caused by: java.lang.NullPointerException
at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:106)
at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:97)
at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:90)
at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText.updateTitle(JBossCentralEditor.java:654)
at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText.access$0(JBossCentralEditor.java:641)
at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3$1.run(JBossCentralEditor.java:584)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
... 24 more
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
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 Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15714:
----------------------------------------
In order to provide this content assist we need to:
1. Initialize the browser
2. Refresh the browser if anything is changed on the page but before we execute our JS to get proposals.
Both tasks are asynchronous and take some time.
#1 can be solved by initializing the browser when the editor (even the source tab) is being opened (I don't like it) OR as Max suggested we could put a placeholder/message for the very first time when the Angular content assist in invoked (I like this idea better).
#2 can be solved if we enable the refreshing mechanism when the angular content assist is invoked the very first time for the page/editor. As soon as it's enabled we will refresh the browser after every change in the source.
So, we wouldn't see angular proposals only the first time the content assist is invoked.
> 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-19410) earlyaccess still not failing gracefully
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19410:
---------------------------------------
In current PR error messages are "Location was not provisioned by p2" and "Unable to acquire the profile registry service."
Should we translate it from Eclipse p2 language to something user friendly?
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19448) Performance problems with angular-phonecat project
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19448?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-19448.
------------------------------------
Resolution: Done
> Performance problems with angular-phonecat project
> --------------------------------------------------
>
> Key: JBIDE-19448
> URL: https://issues.jboss.org/browse/JBIDE-19448
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.2.3.Final
> Environment: Tern.java + AngularJS-Eclipse installed
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.3.0.Alpha2
>
> Attachments: IncludePath.png
>
>
> On angular-phonecat project with the dependencies added by 'npm install' (as well as some other projects where dependencies are taken by bower with 'bower install') there is performance problem occurs.
> 'npm install' and 'bower install' command could add more than 1000 JavaScripts into the project's Include Path, so this could lead into a problem with Eclipse's performance.
> The workaround for the issue is to exclude some directories from JSDT Include Path like 'node_modules/' (in case of 'npm install' is used), 'bower_components/' (in case of 'bower install' is used) as well as other service directories containing JavaScripts that aren't used in JS application:
> !IncludePath.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18505) 4 Test Failures in JSFAsYouTypeInJavaValidationTes for jsf component
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18505?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18505:
-----------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.Alpha2)
> 4 Test Failures in JSFAsYouTypeInJavaValidationTes for jsf component
> --------------------------------------------------------------------
>
> Key: JBIDE-18505
> URL: https://issues.jboss.org/browse/JBIDE-18505
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: jsf
> Affects Versions: 4.2.0.CR2
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Labels: testfailure
> Fix For: 4.3.x
>
>
> *4 Test Failure(s) in JBIDE 4.2.0.CR2 for jsf component:*
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4....
> Also failing in master branch for the past 21 builds:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> # [org.jboss.tools.jsf.ui.test.validation.java.JSFAsYouTypeInJavaValidationT...] (failing for 8 builds)
> # [org.jboss.tools.jsf.ui.test.validation.java.JSFAsYouTypeInJavaValidationT...] (failing for 8 builds)
> # [org.jboss.tools.jsf.ui.test.validation.JSFAsYouTypeValidationTest|https:/...] (failing for 8 builds)
> # [org.jboss.tools.jsf.ui.test.validation.JSFAsYouTypeValidationTest|https:/...] (failing for 8 builds)
> [Search for Test Failure JIRAs in JBIDE 4.2.0.CR2 for jsf component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.jsf.ui.test.validation.java.JSFAsYouTypeInJavaValidationTest : testAsYouTypeMarkerAnnotationsRemovalInJavaValidation{color} (failing for 8 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.2.luna/60/testReport/org.jboss.tools.jsf.ui.test.validation.java/JSFAsYouTypeInJavaValidationTest/testAsYouTypeMarkerAnnotationsRemovalInJavaValidation}
> <case>
> <age>8</age>
> <className>org.jboss.tools.jsf.ui.test.validation.java.JSFAsYouTypeInJavaValidationTest</className>
> <duration>19.277</duration>
> <errorDetails>Resource Marker not found for type: org.jboss.tools.jst.web.kb.elproblem, message: [EL syntax error: Expecting expression.] at line: 38</errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: Resource Marker not found for type: org.jboss.tools.jst.web.kb.elproblem, message: [EL syntax error: Expecting expression.] at line: 38
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertFalse(Assert.java:39)
> at junit.framework.TestCase.assertFalse(TestCase.java:210)
> at org.jboss.tools.common.base.test.validation.java.BaseAsYouTypeInJavaValidationTest.assertResourceMarkerIsCreated(BaseAsYouTypeInJavaValidationTest.java:111)
> at org.jboss.tools.common.base.test.validation.AbstractAsYouTypeValidationTest.doAsYouTypeValidationMarkerAnnotationsRemovalTest(AbstractAsYouTypeValidationTest.java:271)
> at org.jboss.tools.jsf.ui.test.validation.java.JSFAsYouTypeInJavaValidationTest.testAsYouTypeMarkerAnnotationsRemovalInJavaValidation(JSFAsYouTypeInJavaValidationTest.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:23)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.extensions.TestSetup.run(TestSetup.java:27)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:87)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:115)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> </errorStackTrace>
> <failedSince>53</failedSince>
> <name>testAsYouTypeMarkerAnnotationsRemovalInJavaValidation</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
> * {color:red}org.jboss.tools.jsf.ui.test.validation.java.JSFAsYouTypeInJavaValidationTest : testAsYouTypeInJavaValidation{color} (failing for 8 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.2.luna/60/testReport/org.jboss.tools.jsf.ui.test.validation.java/JSFAsYouTypeInJavaValidationTest/testAsYouTypeInJavaValidation}
> <case>
> <age>8</age>
> <className>org.jboss.tools.jsf.ui.test.validation.java.JSFAsYouTypeInJavaValidationTest</className>
> <duration>22.068</duration>
> <errorDetails>No Problem Annotation found!</errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: No Problem Annotation found!
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.TestCase.assertNotNull(TestCase.java:426)
> at org.jboss.tools.common.base.test.validation.AbstractAsYouTypeValidationTest.doAsYouTypeValidationTest(AbstractAsYouTypeValidationTest.java:185)
> at org.jboss.tools.jsf.ui.test.validation.java.JSFAsYouTypeInJavaValidationTest.testAsYouTypeInJavaValidation(JSFAsYouTypeInJavaValidationTest.java:95)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:23)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.extensions.TestSetup.run(TestSetup.java:27)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:87)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:115)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> </errorStackTrace>
> <failedSince>53</failedSince>
> <name>testAsYouTypeInJavaValidation</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> <stdout>Didn't find the following annotation: Text: EL syntax error: Expecting expression.; Position:1073(start), 1077(end).Document Text: [#{[}";
> }
> }
> Found annotations: [
> Text: EL syntax error: Expecting ']'., Position: offset: 1077, length: 0, Document Text: [";
> }
> }
> ]
> Text: EL syntax error: Expecting ']'., Position: offset: 1076, length: 1, Document Text: [}";
> }
> }
> ]
> Text: 41 changed lines , Position: offset: 0, length: 1085, Document Text: [/*******************************************************************************
> * Copyright (c) 2010 Red Hat, Inc.
> * Distributed under license by Red Hat, Inc. All rights reserved.
> * This program is made available under the terms of the
> * Eclipse Public License v1.0 which accompanies this distribution,
> * and is available at http://www.eclipse.org/legal/epl-v10.html
> *
> * Contributors:
> * Red Hat, Inc. - initial API and implementation
> ******************************************************************************/
> package demo;
> import javax.faces.bean.ManagedBean;
> import javax.faces.bean.SessionScoped;
> /**
> * Created by JBoss Tools
> */
> @ManagedBean(name="user")
> @SessionScoped
> public class User {
> private String name;
> public User() {
> }
> // >>> JBIDE-13995: Do not change the order of setName() and getName() methods
> public void setName(String name) {
> this.name = name;
> }
> public String getName() {
> return name;
> }
> // <<< JBIDE-13995: Do not change the order of setName() and getName() methods
> public String sayHello() {
> return "greeting #{[}";
> }
> }
> ]
> ]
> </stdout>
> </case>
> {code}
> * {color:red}org.jboss.tools.jsf.ui.test.validation.JSFAsYouTypeValidationTest : testAsYouTypeMarkerAnnotationsRemovalValidation{color} (failing for 8 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.2.luna/60/testReport/org.jboss.tools.jsf.ui.test.validation/JSFAsYouTypeValidationTest/testAsYouTypeMarkerAnnotationsRemovalValidation}
> <case>
> <age>8</age>
> <className>org.jboss.tools.jsf.ui.test.validation.JSFAsYouTypeValidationTest</className>
> <duration>40.553</duration>
> <errorDetails>Resource Marker not found for type: org.jboss.tools.jst.web.kb.elproblem, message: [EL syntax error: Expecting expression.] at line: 11</errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: Resource Marker not found for type: org.jboss.tools.jst.web.kb.elproblem, message: [EL syntax error: Expecting expression.] at line: 11
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertFalse(Assert.java:39)
> at junit.framework.TestCase.assertFalse(TestCase.java:210)
> at org.jboss.tools.jst.jsp.test.validation.BaseAsYouTypeValidationTest.assertResourceMarkerIsCreated(BaseAsYouTypeValidationTest.java:114)
> at org.jboss.tools.common.base.test.validation.AbstractAsYouTypeValidationTest.doAsYouTypeValidationMarkerAnnotationsRemovalTest(AbstractAsYouTypeValidationTest.java:271)
> at org.jboss.tools.jsf.ui.test.validation.JSFAsYouTypeValidationTest.testAsYouTypeMarkerAnnotationsRemovalValidation(JSFAsYouTypeValidationTest.java:81)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:23)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.extensions.TestSetup.run(TestSetup.java:27)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:87)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:115)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> </errorStackTrace>
> <failedSince>53</failedSince>
> <name>testAsYouTypeMarkerAnnotationsRemovalValidation</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
> * {color:red}org.jboss.tools.jsf.ui.test.validation.JSFAsYouTypeValidationTest : testAsYouTypeValidation{color} (failing for 8 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.2.luna/60/testReport/org.jboss.tools.jsf.ui.test.validation/JSFAsYouTypeValidationTest/testAsYouTypeValidation}
> <case>
> <age>8</age>
> <className>org.jboss.tools.jsf.ui.test.validation.JSFAsYouTypeValidationTest</className>
> <duration>35.234</duration>
> <errorDetails>No Problem Annotation found!</errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: No Problem Annotation found!
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.Assert.assertNotNull(Assert.java:256)
> at junit.framework.TestCase.assertNotNull(TestCase.java:426)
> at org.jboss.tools.common.base.test.validation.AbstractAsYouTypeValidationTest.doAsYouTypeValidationTest(AbstractAsYouTypeValidationTest.java:185)
> at org.jboss.tools.jsf.ui.test.validation.JSFAsYouTypeValidationTest.testAsYouTypeValidation(JSFAsYouTypeValidationTest.java:121)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:23)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.extensions.TestSetup.run(TestSetup.java:27)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:87)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:115)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> </errorStackTrace>
> <failedSince>53</failedSince>
> <name>testAsYouTypeValidation</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> <stdout>Didn't find the following annotation: Text: EL syntax error: Expecting expression.; Position:509(start), 513(end).Document Text: [#{[}!
> <h:o
> Found annotations: [
> Text: EL syntax error: Expecting ']'., Position: offset: 512, length: 1, Document Text: [}!
> <h:o]
> Text: 10 changed lines , Position: offset: 0, length: 505, Document Text: [<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core">
> <ui:composition template="/templates/common.xhtml">
> <ui:define name="pageTitle">Greeting to User</ui:define>
> <ui:define name="pageHeader">Greeting Page</ui:define>
> <ui:define name="body">
> #{[}!
> ]
> Text: 1 changed line , Position: offset: 505, length: 10, Document Text: [ #{[}!
> <h:out]
> Text: 5 changed lines , Position: offset: 515, length: 85, Document Text: [ <h:outputText value="#{user.name}" />
> </ui:define>
> </ui:composition>
> </html>
> ]
> ]
> </stdout>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18113) Wrong 'dirty regions' values passed to the 'as-you-type' validator
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18113?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18113:
-----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Wrong 'dirty regions' values passed to the 'as-you-type' validator
> ------------------------------------------------------------------
>
> Key: JBIDE-18113
> URL: https://issues.jboss.org/browse/JBIDE-18113
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Victor Rubezhny
> Fix For: 4.3.0.Beta1
>
>
> The as-you-type validator received an array of dirty regions that can be wrong when the region contains a String.
> Steps to reproduce:
> - grab the latest changes in jbosstools-webservices repo
> - start a runtime workbench
> - create a new dynamic web project targeting Wildfly 8.x (the example below uses JAX-RS 2.0 APIs)
> - add support for JAX-RS
> - create a class with the following content:
> {code}
> package jaxrs;
> import java.io.IOException;
> import javax.ws.rs.GET;
> import javax.ws.rs.Path;
> import javax.ws.rs.PathParam;
> import javax.ws.rs.container.ContainerRequestContext;
> import javax.ws.rs.container.ContainerResponseContext;
> import javax.ws.rs.container.ContainerResponseFilter;
> import javax.ws.rs.core.Response;
> import javax.ws.rs.ext.Provider;
> @Path("/")
> public class RestService {
>
> @GET
> @Path("/{ide}")
> public Response get(@PathParam("ide") String id) {
> System.out.println("Just passed in method");
> return Response.ok().build();
> }
>
> @Provider
> public static class AuthorizedResponseFilter implements ContainerResponseFilter {
> @Override
> public void filter(ContainerRequestContext arg0,
> ContainerResponseContext arg1) throws IOException {
> System.out.println("Just passed in filter");
> }
> }
> }
> {code}
> - In your development workspace, open {{org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator}} and put a breakpoint on line 441
> - Back in the runtime workspace, remove the @Provider annotation and see the value for 'dirtyRegion'. In my last test, this one alone looked good (offset=559)
> - DO NOT SAVE THE FILE
> - remove the @Path("/") annotation on the RestService type, this time you should have *4* dirty regions, with unexpected values (ie, pointing at other locations in the document).
> As [~akazakov] commented in a private mail:
> {quote}
> JaxrsMetamodelValidator implements IJavaElementValidator and IStringValidator.
> When you remove @Provider then you get the region with offset of the removed JavaElement because you validator implements IJavaElementValidator.
> This interface tells our validation manager that the validator is interested in validating of changes in java elements.
> When you remove @Path("/") you also remove a string ("/") and since your validator implements IStringValidator this validator is notified and you got a list of the regions of all the strings of the file: 4 regions in your case.
> The problem is that you also should have been notified about removed java element because this annotation is not just a String. It's also a java element. That looks like a bug for me.
> So if you remove any code with a string inside then you will get a list of strings of the file (but only if you implements IStringValidator).
> If you don't implement IStringValidator and remove any java element which contains a string you won't be notified at all. This is a bug.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-17727) CSS content assist for class attribute in custom HTML tags
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17727?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17727:
-----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> CSS content assist for class attribute in custom HTML tags
> ----------------------------------------------------------
>
> Key: JBIDE-17727
> URL: https://issues.jboss.org/browse/JBIDE-17727
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Fix For: 4.3.0.Beta1
>
>
> Right now, content assist for CSS classes works only for standart HTML tags. But some frameworks use custom html tags (AngularJS and its extensions like ionic framework for example). It would be useful if our CSS content assist also worked for such tags.
> For example:
> {code}
> <ion-tabs class="tabs-positive tabs-icon-only">
> <ion-tab title="Home" icon-on="ion-ios7-filing" icon-off="ion-ios7-filing-outline">
> </ion-tab>
> </ion-tabs>
> {code}
> Currently the content assis works only if you change <ion-tabs> to <div> or any other standart HTML tags.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19410:
---------------------------------------
Mickael, considering your last change related to wrapping updateTitle(heading) inside display.asyncExec() you never ran the actual code, did you? :)
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19410:
----------------------------------------
[~dgolovin] I disagree. Try to reproduce the error as described about (start Central in debug mode without support for p2), reproduce the error, then apply the patch and try again. You'll see it's actually fixing what needs to be fixed, and that at that time, it's the profile that is null.
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18542) NPE during "Check installation for Early Access"
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18542?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-18542:
---------------------------------------
Nope, the same NPE is going to happen.
> NPE during "Check installation for Early Access"
> ------------------------------------------------
>
> Key: JBIDE-18542
> URL: https://issues.jboss.org/browse/JBIDE-18542
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR2
> Reporter: Rob Cernich
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.2.x, 4.3.0.Alpha2
>
>
> I got the following exception upon restart after updating to CR2 from the following site: http://download.jboss.org/jbosstools/updates/staging/luna/
> {noformat}
> java.lang.NullPointerException
> at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:99)
> at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79)
> at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72)
> at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:574)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19410:
---------------------------------------
By the line numbers exception is for code from jbosstools-4.2.x branch.
[InstallationChecker.java#L101|https://github.com/jbosstools/jbosstools-ce...] fails because iusForFamily is null. Proposed PR doesn't deal with NPE. It will still reported the same way.
> earlyaccess still not failing gracefully
> ----------------------------------------
>
> Key: JBIDE-19410
> URL: https://issues.jboss.org/browse/JBIDE-19410
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE)
> start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently.
> but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19570) Arquillian icon is missing in JBDS 8.1.0 Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19570?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19570:
----------------------------------------
[~ldimaggio] This is actually a pure JBoss Tools issue, everything is OK with JBDS. Please be careful when an issue is related to a remote site or catalog, there are big differences and almost no inheritance between JBT and JBDS, so make sure you report the issue to the right project.
> Arquillian icon is missing in JBDS 8.1.0 Central
> ------------------------------------------------
>
> Key: JBIDE-19570
> URL: https://issues.jboss.org/browse/JBIDE-19570
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: discovery
> Affects Versions: 4.2.3.Final
> Reporter: Len DiMaggio
> Assignee: Mickael Istria
> Attachments: JBDS_810_GA.png
>
>
> See attached screenshot
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19570) Arquillian icon is missing in JBDS 8.1.0 Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19570?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19570:
-----------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio))
Key: JBIDE-19570 (was: JBDS-3392)
Workflow: GIT Pull Request workflow (was: CDW v1)
Status: Open (was: New)
Affects Version/s: 4.2.3.Final
(was: 8.1.0.GA)
Component/s: discovery
(was: central)
Docs QE Status: (was: NEW)
> Arquillian icon is missing in JBDS 8.1.0 Central
> ------------------------------------------------
>
> Key: JBIDE-19570
> URL: https://issues.jboss.org/browse/JBIDE-19570
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: discovery
> Affects Versions: 4.2.3.Final
> Reporter: Len DiMaggio
> Assignee: Mickael Istria
> Attachments: JBDS_810_GA.png
>
>
> See attached screenshot
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-19536:
-----------------------------------------------
Why this thread hangs? -
"ReaderThread" #43 prio=6 os_prio=0 tid=0x00007f8be0072000 nid=0x3ef6 runnable [0x00007f8bdb6fd000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
- locked <0x00000000c486c5b8> (a java.io.InputStreamReader)
at java.io.InputStreamReader.read(InputStreamReader.java:184)
at java.io.BufferedReader.fill(BufferedReader.java:161)
at java.io.BufferedReader.readLine(BufferedReader.java:324)
- locked <0x00000000c486c5b8> (a java.io.InputStreamReader)
at java.io.BufferedReader.readLine(BufferedReader.java:389)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner$ReaderThread.run(RemoteTestRunner.java:135)
I cannot see anything more criminal in the attached stack traces.
> 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
[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19569?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-19569:
------------------------------------------------
{quote}OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview.{quote}
you should not be able to navigate, sounds not very good. Refreshing page should help to get to start page.
> Unable to switch pages shown in visual preview when editing mobile html5
> ------------------------------------------------------------------------
>
> Key: JBIDE-19569
> URL: https://issues.jboss.org/browse/JBIDE-19569
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
> Assignee: Konstantin Marmalyukov
>
> I'm not sure if my use case is valid or not.
> But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one.
> So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview.
> Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button?
> But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :)
> [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19569?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-19569:
------------------------------------------------
Navigation on visual preview is disabled by design. It was done to provide visual-to-source navigation(you click on the button - source editor scrolls to this button code). If you want to browse through your page - you can use preview tab, where navigation is not disabled. It is not very good in one-page-app usecase, but it is better than nothing.
> Unable to switch pages shown in visual preview when editing mobile html5
> ------------------------------------------------------------------------
>
> Key: JBIDE-19569
> URL: https://issues.jboss.org/browse/JBIDE-19569
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
> Assignee: Konstantin Marmalyukov
>
> I'm not sure if my use case is valid or not.
> But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one.
> So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview.
> Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button?
> But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :)
> [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19569?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-19569:
-------------------------------------------
Component/s: visual-page-editor-core
(was: jsp/jsf/xml/html source editing)
> Unable to switch pages shown in visual preview when editing mobile html5
> ------------------------------------------------------------------------
>
> Key: JBIDE-19569
> URL: https://issues.jboss.org/browse/JBIDE-19569
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
>
> I'm not sure if my use case is valid or not.
> But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one.
> So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview.
> Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button?
> But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :)
> [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19569?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov reassigned JBIDE-19569:
----------------------------------------------
Assignee: Konstantin Marmalyukov
> Unable to switch pages shown in visual preview when editing mobile html5
> ------------------------------------------------------------------------
>
> Key: JBIDE-19569
> URL: https://issues.jboss.org/browse/JBIDE-19569
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
> Assignee: Konstantin Marmalyukov
>
> I'm not sure if my use case is valid or not.
> But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one.
> So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview.
> Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button?
> But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :)
> [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBTIS-421) Cannot install JBoss Integration and SOA Development from non-earlyaccess site
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-421?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-421.
------------------------------
Fix Version/s: 8.0.1.GA
Resolution: Done
Removed com.jboss.devstudio.integration-stack.soa.feature from the GA site category.xml. This is a hidden feature needed only for Eclipse Marketplace which only applies to fully released features.
https://github.com/jbosstools/jbosstools-integration-stack/commit/9aeced9...
> Cannot install JBoss Integration and SOA Development from non-earlyaccess site
> ------------------------------------------------------------------------------
>
> Key: JBTIS-421
> URL: https://issues.jboss.org/browse/JBTIS-421
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.1.CR1
> Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.1.CR1 (without earlyaccess
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 8.0.1.GA
>
> Attachments: Screenshot_20150403103207.png, Screenshot_20150403103215.png
>
>
> Cannot install JBoss Integration and SOA Development from non-earlyaccess site, namely if you try to install com.jboss.devstudio.integration-stack.soa.feature.
> Note that this is not a common use case since you have to uncheck 'Group items by category' during installation.
> The problem is that this feature includes fuse and switchyard features which are available only on early access.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (LOCUS-23) New version of Saxon-HE required in locus
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/LOCUS-23?page=com.atlassian.jira.plugin.s... ]
Max Rydahl Andersen commented on LOCUS-23:
------------------------------------------
[~phantomjinx] do you have a related TEIID or JBTIS issue to know when this is needed by ?
> New version of Saxon-HE required in locus
> -----------------------------------------
>
> Key: LOCUS-23
> URL: https://issues.jboss.org/browse/LOCUS-23
> Project: JBoss Tools Locus
> Issue Type: Feature Request
> Affects Versions: 1.1.0
> Reporter: Paul Richardson
> Fix For: 1.2.0
>
>
> The Teiid Server project has updated their dependencies, including increasing the Saxon-HE version to 9.1.5-6j.
> Since Teiid Designer takes a cut of the Teiid Server's client, it is necessary to update the Saxon-HE dependency in the former in order to remain in sync. Designer gets it Saxon library from the Locus repository.
--
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 Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-19568:
-------------------------------------
This looks like an Ooomph issue to me. Nothing in the stacktrace indicates we have anything to catch in our code.
> 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, upstream
> 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-19568) central check for updates fails silently when provisioning errors
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19568:
--------------------------------
Component/s: upstream
> 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, upstream
> 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-19569) Unable to switch pages shown in visual preview when editing mobile html5
by Martin Malina (JIRA)
Martin Malina created JBIDE-19569:
-------------------------------------
Summary: Unable to switch pages shown in visual preview when editing mobile html5
Key: JBIDE-19569
URL: https://issues.jboss.org/browse/JBIDE-19569
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.2.3.Final
Reporter: Martin Malina
I'm not sure if my use case is valid or not.
But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one.
So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview.
Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button?
But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :)
[1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18542) NPE during "Check installation for Early Access"
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18542?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18542:
----------------------------------------
I have hope that fix for JBIDE-19410 improves status here, but since it's not determistic, one cannot know...
> NPE during "Check installation for Early Access"
> ------------------------------------------------
>
> Key: JBIDE-18542
> URL: https://issues.jboss.org/browse/JBIDE-18542
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR2
> Reporter: Rob Cernich
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.2.x, 4.3.0.Alpha2
>
>
> I got the following exception upon restart after updating to CR2 from the following site: http://download.jboss.org/jbosstools/updates/staging/luna/
> {noformat}
> java.lang.NullPointerException
> at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:99)
> at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79)
> at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72)
> at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:574)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19419) NPE in InstallationChecker
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19419?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19419:
----------------------------------------
Hey [~ilx], thanks for reporting.
Can you please comment (in JBIDE-18542) whether you know deterministic steps to reproduce?
> NPE in InstallationChecker
> --------------------------
>
> Key: JBIDE-19419
> URL: https://issues.jboss.org/browse/JBIDE-19419
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.3.Beta1
> Reporter: Ivica Loncar
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.central.installation.InstallationChecker.getUnits(InstallationChecker.java:99)
> at org.jboss.tools.central.installation.InstallationChecker.getEarlyAccessUnits(InstallationChecker.java:79)
> at org.jboss.tools.central.installation.InstallationChecker.hasEarlyAccess(InstallationChecker.java:72)
> at org.jboss.tools.central.editors.JBossCentralEditor$HeaderText$3.run(JBossCentralEditor.java:571)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> {code}
> eclipse.buildId=4.4.2.M20150204-1700
> java.version=1.8.0
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> {code}
--
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 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