[JBoss JIRA] (JBIDE-24841) Remove findbugs plugin from Central
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24841?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24841:
---------------------------------------
[~nickboldt], personally I would go with just removing FindBugs, nor replacing it with anything. I guess the final decision is on [~rpdavis] though.
> Remove findbugs plugin from Central
> -----------------------------------
>
> Key: JBIDE-24841
> URL: https://issues.jboss.org/browse/JBIDE-24841
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update, target-platform, updatesite, upstream
> Affects Versions: 4.5.0.Final
> Reporter: Martin Malina
> Assignee: Jeff MAURY
> Fix For: 4.5.1.AM2
>
>
> I suggest we remove FindBugs connector from Central. It seems it hasn't been developed for some time now. The version we have in central is:
> edu.umd.cs.findbugs.plugin.eclipse_3.0.1.20150306-5afe4d1
> And if you look at the project's update site, that's still the latest release there is:
> http://findbugs.cs.umd.edu/eclipse/
> Furthermore, it kind of broke for me now. I never tested it extensively. But I would create a project and then right-click -> Find Bugs -> Find Bugs. This would open a window showing progress as the project is searched for bugs. When I tried it now, no window appears. For a few seconds something shows up in the status bar. But I can't see the results anywhere.
> Since this is Central, we could do this right away - affecting devstudio 11 / jbosstools 4.5.0. But I guess we need PM approval first.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24801) Remove no-cache header for xml schema files
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24801?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24801:
---------------------------------------
OK, fair enough.
> Remove no-cache header for xml schema files
> -------------------------------------------
>
> Key: JBIDE-24801
> URL: https://issues.jboss.org/browse/JBIDE-24801
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, upstream
> Affects Versions: 4.5.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM2
>
>
> This is a followup of JBIDE-20610 . In the past we were trying to figure out how to make validation in Eclipse faster. The problem is that xml schema files return no-cache header and so Eclipse needs to fetch them over and over again.
> We tried to solve this on Eclipse side - allow ignoring of the no-cache http header. But why not try to solve this properly on the server side at least where we have control over it? I think there is no reason why request to urls like http://jboss.org/j2ee/dtd/service-ref_4_0.dtd should return no-cache.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24883) Python on windows slaves
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24883?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-24883:
------------------------------------
Python 2.7 is now installed on win10, win81 and win7.
However the provisioning script does not work out of the box on win7. Fix for this will be targeted in the next sprint.
> Python on windows slaves
> -------------------------
>
> Key: JBIDE-24883
> URL: https://issues.jboss.org/browse/JBIDE-24883
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Labels: central-ci
> Fix For: 4.5.1.AM2
>
>
> python installation needs to be scripted in mwqa-cloud-slaves to be installed automatically when provisioning from openstack.
> Purpose: facilitate running cross-platform scripts (eg., for JDK detection & discovery). Will allow Nick to start porting .sh script to .py so they can be used on all OSes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24883) Python on windows slaves
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24883?page=com.atlassian.jira.plugi... ]
Pavol Srna resolved JBIDE-24883.
--------------------------------
Resolution: Done
> Python on windows slaves
> -------------------------
>
> Key: JBIDE-24883
> URL: https://issues.jboss.org/browse/JBIDE-24883
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Labels: central-ci
> Fix For: 4.5.1.AM2
>
>
> python installation needs to be scripted in mwqa-cloud-slaves to be installed automatically when provisioning from openstack.
> Purpose: facilitate running cross-platform scripts (eg., for JDK detection & discovery). Will allow Nick to start porting .sh script to .py so they can be used on all OSes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24968) VersionProviderTest.testFallBackEmbeddedValues is failing
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24968?page=com.atlassian.jira.plugi... ]
Jeff MAURY edited comment on JBIDE-24968 at 9/7/17 2:24 AM:
------------------------------------------------------------
> Thanks to Rob and Jeff for nagging me until -I- *we* dug into this
was (Author: rob.stryker):
> Thanks to Rob for nagging me until -I- *we* dug into this
> VersionProviderTest.testFallBackEmbeddedValues is failing
> ---------------------------------------------------------
>
> Key: JBIDE-24968
> URL: https://issues.jboss.org/browse/JBIDE-24968
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.5.1.AM1
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.1.AM2
>
>
> the test if failing since the beginning of August.
> It seems that the test was not played before, see [JBIDE-19081] so maybe it is that it has never worked
> {noformat}
> Error Message
> ide-config.properties can't be loaded from the org.jboss.tools.foundation.core plugin
> Stacktrace
> java.lang.RuntimeException: ide-config.properties can't be loaded from the org.jboss.tools.foundation.core plugin
> at java.util.Properties$LineReader.readLine(Properties.java:434)
> at java.util.Properties.load0(Properties.java:353)
> at java.util.Properties.load(Properties.java:341)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getProperties(VersionPropertiesProvider.java:293)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.loadDefaultProperties(VersionPropertiesProvider.java:204)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:158)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:217)
> at org.jboss.tools.foundation.core.properties.internal.VersionProviderTest.testFallBackEmbeddedValues(VersionProviderTest.java:207)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24991) Improve server port offset detection by inspecting configured system properties
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24991?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24991:
-------------------------------
Component/s: server
> Improve server port offset detection by inspecting configured system properties
> -------------------------------------------------------------------------------
>
> Key: JBIDE-24991
> URL: https://issues.jboss.org/browse/JBIDE-24991
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.5.0.Final
> Environment: JBDS11, WF10
> Reporter: Vsevolod Golovanov
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> The default Wildfly standalone.xml config has port offset configured like this:
> {code}
> <socket-binding-group ... port-offset="${jboss.socket.binding.port-offset:0}">
> {code}
> With the way our configuration process is set up we don't change that. Instead we add a system property to the same config file:
> {code}
> <system-properties>
> <property name="jboss.socket.binding.port-offset" value="10"/>
> </system-properties>
> {code}
> The problem is JBoss Tools doesn't detect this currently. It could be improved to inspect the port-offset attribute and find the corresponding system property value.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months