[JBoss JIRA] (JBIDE-22880) List of modules filtered by "deployed" is always empty on the ServerEditor Deployment tab
by Mikhail Kalkov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22880?page=com.atlassian.jira.plugi... ]
Mikhail Kalkov commented on JBIDE-22880:
----------------------------------------
[~mmalina] Thanks for a link! I'm on a sick leave right now but will test this as soon as I'm back at work.
> List of modules filtered by "deployed" is always empty on the ServerEditor Deployment tab
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22880
> URL: https://issues.jboss.org/browse/JBIDE-22880
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Final, 4.4.0.Final
> Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime.
> Reporter: Mikhail Kalkov
> Assignee: Rob Stryker
> Fix For: 4.4.1.Final
>
> Attachments: test-projects.zip
>
>
> It is impossible to select "filter by" dropdown or press "Refresh Table" on the deployment tab of ServerEditor in JBoss Developer Studio when anything is deployed. I think it should be possible to change filter configuration but do not edit the table itself. Otherwise, both "Refresh" button and some of filter options becomes useless. See Steps to Reproduce for more details.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22879) JavaEE jars files are built with another java version than used for compilation
by Mikhail Kalkov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22879?page=com.atlassian.jira.plugi... ]
Mikhail Kalkov commented on JBIDE-22879:
----------------------------------------
{quote}It's worth noting, however, that this bug is almost entirely cosmetic.{quote}
I agree as long as the class files are compiled with correct classpath, which seems to be the case. Thanks for looking into it!
> JavaEE jars files are built with another java version than used for compilation
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22879
> URL: https://issues.jboss.org/browse/JBIDE-22879
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Final, 4.4.0.Final
> Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime.
> Reporter: Mikhail Kalkov
> Assignee: Rob Stryker
> Fix For: LATER
>
> Attachments: test-projects.zip
>
>
> I have installed system-wide JRE 8 in order to run all java applications with it. At the same time, out target platform is still based on Java 7 and that's why I've also downloaded JDK 7 and set JAVA_HOME path to it.
> When I build test-ejb project from attached zip file on command line, maven both compiles and packages it with JDK 7 obtained from JAVA_HOME. When I build the same project with JBoss Developer Studio which was configured via Window > Preferences > Java > Installed JREs to use JDK 7 by default, class files get version 51 (java 7) but Build-Jdk stanza in MANIFEST.MF is set to 1.8.0_102 instead of 1.7. I've also observed that test-ear project is also packaged with Java 8 instead of Java 7.
> This is not a big issue but is a bit worrying since for example jar tool from JDK 8 may contains bugfixes not present in JDK 7. This also makes me think that other tools may be fetched from wrong JDK version. Finally, I'm not even sure whether this is a JBoss Tools, Eclipse WTP or Eclipse M2E issue but it is clearly present in the latest stock version of JBoss Developer Studio.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22896) JavaModelException below JdtUtils.findDeclaringNode (thrown in JavaElement.newNotPresentException)
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22896?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-22896:
----------------------------------
Fix Version/s: 4.4.2.AM1
> JavaModelException below JdtUtils.findDeclaringNode (thrown in JavaElement.newNotPresentException)
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22896
> URL: https://issues.jboss.org/browse/JBIDE-22896
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Xavier Coulon
> Fix For: 4.4.2.AM1
>
>
> The following problem was reported via the automated error reporting:
> Message: Failed to build or refresh the JAX-RS metamodel
> {noformat}
> org.eclipse.jdt.core.JavaModelException: submt(HttpServletRequest, int) [in PublicWS [in [Working copy] PublicWS.java [in be.fromprison.ws.endpoints [in src/main/java [in from-prison]]]]] does not exist
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:556)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:590)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
> at org.eclipse.jdt.internal.core.SourceRefElement.getSourceRange(SourceRefElement.java:218)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.findDeclaringNode(JdtUtils.java:494)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveAllAnnotations(JdtUtils.java:373)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsResourceMethod$Builder.buildInResource(JaxrsResourceMethod.java:153)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:211)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createElements(JaxrsElementFactory.java:65)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:420)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processJavaElementChange(JaxrsMetamodel.java:392)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:73)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.jdt.core | 3.11.0.xx-201604081629-e45 | 3.12.0.v_OTDT_r250_201606070956 |
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.ws.jaxrs.core | 1.8.1.Final-v20160331-0952-B76 | 1.9.1.v20160608-0648 |
> | org.jboss.tools.ws.jaxrs.ui | 1.8.1.Final-v20160331-0952-B76 | 1.9.0.Final-v20160610-0003-B1 |
> Operating Systems:
> | Linux | 3.10.0.13 | 4.6.3.fc24 |
> | MacOSX | 10.11.3 | 10.11.6 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571dd2b8e4b08bd809...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBTIS-866) SwitchYardEditorImplementationsTest sometimes fails
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-866:
---------------------------------------
Summary: SwitchYardEditorImplementationsTest sometimes fails
Key: JBTIS-866
URL: https://issues.jboss.org/browse/JBTIS-866
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: QE, switchyard
Affects Versions: 4.3.1.Final
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Attachments: stacktrace.txt, sy_camel.png
The problem occurs while adding an existing a camel route.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3890) Devstudio installation takes a long, long time
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3890?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3890:
-----------------------------------
The issue seems to have magically fixed itself, I can no longer replicate it. I guess you can go ahead and resolve it as out of date or something like that.
> Devstudio installation takes a long, long time
> ----------------------------------------------
>
> Key: JBDS-3890
> URL: https://issues.jboss.org/browse/JBDS-3890
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.0.0.Alpha1
> Environment: Fedora 22 x64
> OpenJDK 1.8.0_91
> jboss-devstudio-10.0.0.Alpha1-v20160517-0518-B5370-installer-standalone.jar
> Reporter: Jan Richter
> Priority: Critical
> Fix For: 10.x
>
> Attachments: install.png, res.png
>
>
> Some actual data here:
> - Alpha1 (staged) build took 2:05 to install on my machine
> - Alpha1 nightly (B5370) took 5:15 to install
> Around the minute mark the installation just freezes in this state:
> !install.png|thumbnail!
> Meanwhile the trace says:
> {noformat}
> Committing the provisioning operation.
> Operation completed in 275702 ms.
> {noformat}
> That is quite a long time it spent doing that operation.
> Some jstack info can be found here:
> http://pastebin.test.redhat.com/374700
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBTIS-865) Prepare a logic for performance tests
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-865:
---------------------------------------
Summary: Prepare a logic for performance tests
Key: JBTIS-865
URL: https://issues.jboss.org/browse/JBTIS-865
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: QE
Affects Versions: 4.3.1.Final
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Prepare a logic for performance tests. We need to store results and use them for comparison.
Let's start with a performance test for update a maven project.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months