[JBoss JIRA] (ERT-420) Open or ping failure for connection causes exception to be logged [EBZ#501522]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-420:
---------------------------------------
Summary: Open or ping failure for connection causes exception to be logged [EBZ#501522]
Key: ERT-420
URL: https://issues.jboss.org/browse/ERT-420
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon.2 (4.6)
An open or ping failure for a closed/invalid connection causes an exception trace to be logged. This will cause an AERI bug filed and offers little information to an end-user. It is better to give an information message that the open or ping failed for the particular connection. The connection is shown as greyed and invalid.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4023) set up docker/jenkins instance on wonka to do CI builds of RPM
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4023?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4023:
----------------------------------
I was given access to the existing jenkins docker image that runs on :80 on wonka, but it doesn't have rpmbuild or mock installed, so ... that's a non-starter. Back to building my own. :(
> set up docker/jenkins instance on wonka to do CI builds of RPM
> --------------------------------------------------------------
>
> Key: JBDS-4023
> URL: https://issues.jboss.org/browse/JBDS-4023
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: build, rpm
> Affects Versions: 10.1.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM1
>
>
> To enable building the RPM via CI builds, in response to new devstudio builds, need a Jenkins server on which we can run rpmbuild and mock.
> I have root access to wonka and it has TONS of space, so that seems a viable place to host this until we can get eng-ops to support Fedora24 or RHEL7 w/ EPEL.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23175) Validation of RetentionPolicy
by Lukáš Valach (JIRA)
Lukáš Valach created JBIDE-23175:
------------------------------------
Summary: Validation of RetentionPolicy
Key: JBIDE-23175
URL: https://issues.jboss.org/browse/JBIDE-23175
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi-extensions
Affects Versions: 4.4.1.Final
Reporter: Lukáš Valach
The DeltaSpike sometimes requires to create new annotation. There are "parameter binding annotation" and "security binding annotation" in security module ([doc|https://deltaspike.apache.org/documentation/security.html]). If the anotation haven't this repention policy,then the annotation doesn't works ([explanation|http://stackoverflow.com/questions/3107970/how-do-different-r...]).
This is a valid annotation
{code:java}
@Retention(value = RetentionPolicy.RUNTIME)
@Target({ElementType.TYPE, ElementType.METHOD})
@Documented
@SecurityBindingType
public @interface CustomSecurityBinding {
}
{code}
and this doesn't work
{code:java}
//@Retention(value = RetentionPolicy.RUNTIME)
@Target({ElementType.TYPE, ElementType.METHOD})
@Documented
@SecurityBindingType
public @interface CustomSecurityBinding {
}
{code}
I am not sure if that can be or should be validated.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23155) tests: sonar should report test coverage
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23155?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23155 at 9/15/16 11:19 AM:
--------------------------------------------------------------------
To have sonar reporting test coverage one has to include cobertura or jacoco in the build. Sonar will then pick up the report that was generated as long as required properties are configured correctly.
To add jacoco to our build the following has to be added to pom:
{code:title=http://www.eclemma.org/jacoco/trunk/doc/examples/build/pom.xml}
<build>
<plugins>
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>0.7.8-SNAPSHOT</version>
<executions>
<execution>
<id>default-prepare-agent</id>
<goals>
<goal>prepare-agent</goal>
</goals>
</execution>
<execution>
<id>default-report</id>
<phase>prepare-package</phase>
<goals>
<goal>report</goal>
</goals>
</execution>
<execution>
<id>default-check</id>
<goals>
<goal>check</goal>
</goals>
<configuration>
<rules>
<!-- implementation is needed only for Maven 2 -->
<rule implementation="org.jacoco.maven.RuleConfiguration">
<element>BUNDLE</element>
<limits>
<!-- implementation is needed only for Maven 2 -->
<limit implementation="org.jacoco.report.check.Limit">
<counter>COMPLEXITY</counter>
<value>COVEREDRATIO</value>
<minimum>0.60</minimum>
</limit>
</limits>
</rule>
</rules>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
{code}
docs for integrating jacoco are here: http://docs.sonarqube.org/display/PLUG/Usage+of+JaCoCo+with+Java+Plugin
was (Author: adietish):
To have sonar reporting test coverage one has to include cobertura or jacoco in the build. Sonar will then pick up the report that was generated as long as required properties are configured correctly.
To add jacoco to our build the following has to be added to pom:
{code:title=http://www.eclemma.org/jacoco/trunk/doc/examples/build/pom.xml}
<build>
<plugins>
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>0.7.8-SNAPSHOT</version>
<executions>
<execution>
<id>default-prepare-agent</id>
<goals>
<goal>prepare-agent</goal>
</goals>
</execution>
<execution>
<id>default-report</id>
<phase>prepare-package</phase>
<goals>
<goal>report</goal>
</goals>
</execution>
<execution>
<id>default-check</id>
<goals>
<goal>check</goal>
</goals>
<configuration>
<rules>
<!-- implementation is needed only for Maven 2 -->
<rule implementation="org.jacoco.maven.RuleConfiguration">
<element>BUNDLE</element>
<limits>
<!-- implementation is needed only for Maven 2 -->
<limit implementation="org.jacoco.report.check.Limit">
<counter>COMPLEXITY</counter>
<value>COVEREDRATIO</value>
<minimum>0.60</minimum>
</limit>
</limits>
</rule>
</rules>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
{code}
> tests: sonar should report test coverage
> ----------------------------------------
>
> Key: JBIDE-23155
> URL: https://issues.jboss.org/browse/JBIDE-23155
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Andre Dietisheim
> Fix For: 4.4.x
>
>
> I'd be great if our sonar instance at sonarqube.com would report test coverage.
> Docs are here: http://docs.sonarqube.org/display/PLUG/Code+Coverage+by+Unit+Tests+for+Ja...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23155) tests: sonar should report test coverage
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23155?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23155 at 9/15/16 11:18 AM:
--------------------------------------------------------------------
To have sonar reporting test coverage one has to include cobertura or jacoco in the build. Sonar will then pick up the report that was generated as long as required properties are configured correctly.
To add jacoco to our build the following has to be added to pom:
{code:title=http://www.eclemma.org/jacoco/trunk/doc/examples/build/pom.xml}
<build>
<plugins>
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>0.7.8-SNAPSHOT</version>
<executions>
<execution>
<id>default-prepare-agent</id>
<goals>
<goal>prepare-agent</goal>
</goals>
</execution>
<execution>
<id>default-report</id>
<phase>prepare-package</phase>
<goals>
<goal>report</goal>
</goals>
</execution>
<execution>
<id>default-check</id>
<goals>
<goal>check</goal>
</goals>
<configuration>
<rules>
<!-- implementation is needed only for Maven 2 -->
<rule implementation="org.jacoco.maven.RuleConfiguration">
<element>BUNDLE</element>
<limits>
<!-- implementation is needed only for Maven 2 -->
<limit implementation="org.jacoco.report.check.Limit">
<counter>COMPLEXITY</counter>
<value>COVEREDRATIO</value>
<minimum>0.60</minimum>
</limit>
</limits>
</rule>
</rules>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
{code}
was (Author: adietish):
To have sonar reporting test coverage one has to include cobertura or jacoco in the build. Sonar will then pick up the report that was generated as long as required properties are configured correctly.
To add jacoco to our build the following has to be added to pom:
{code:title=http://www.eclemma.org/jacoco/trunk/doc/examples/build/pom.xml}
<build>
<plugins>
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>0.7.8-SNAPSHOT</version>
<executions>
<execution>
<id>default-prepare-agent</id>
<goals>
<goal>prepare-agent</goal>
</goals>
</execution>
<execution>
<id>default-report</id>
<phase>prepare-package</phase>
<goals>
<goal>report</goal>
</goals>
</execution>
<execution>
<id>default-check</id>
<goals>
<goal>check</goal>
</goals>
<configuration>
<rules>
<!-- implementation is needed only for Maven 2 -->
<rule implementation="org.jacoco.maven.RuleConfiguration">
<element>BUNDLE</element>
<limits>
<!-- implementation is needed only for Maven 2 -->
<limit implementation="org.jacoco.report.check.Limit">
<counter>COMPLEXITY</counter>
<value>COVEREDRATIO</value>
<minimum>0.60</minimum>
</limit>
</limits>
</rule>
</rules>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
{code}
> tests: sonar should report test coverage
> ----------------------------------------
>
> Key: JBIDE-23155
> URL: https://issues.jboss.org/browse/JBIDE-23155
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Andre Dietisheim
> Fix For: 4.4.x
>
>
> I'd be great if our sonar instance at sonarqube.com would report test coverage.
> Docs are here: http://docs.sonarqube.org/display/PLUG/Code+Coverage+by+Unit+Tests+for+Ja...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23155) tests: sonar should report test coverage
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23155?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23155:
------------------------------------------
To have sonar reporting test coverage one has to include cobertura or jacoco in the build. Sonar will then pick up the report that was generated as long as required properties are configured correctly.
To add jacoco to our build the following has to be added to pom:
{code:title=http://www.eclemma.org/jacoco/trunk/doc/examples/build/pom.xml}
<build>
<plugins>
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>0.7.8-SNAPSHOT</version>
<executions>
<execution>
<id>default-prepare-agent</id>
<goals>
<goal>prepare-agent</goal>
</goals>
</execution>
<execution>
<id>default-report</id>
<phase>prepare-package</phase>
<goals>
<goal>report</goal>
</goals>
</execution>
<execution>
<id>default-check</id>
<goals>
<goal>check</goal>
</goals>
<configuration>
<rules>
<!-- implementation is needed only for Maven 2 -->
<rule implementation="org.jacoco.maven.RuleConfiguration">
<element>BUNDLE</element>
<limits>
<!-- implementation is needed only for Maven 2 -->
<limit implementation="org.jacoco.report.check.Limit">
<counter>COMPLEXITY</counter>
<value>COVEREDRATIO</value>
<minimum>0.60</minimum>
</limit>
</limits>
</rule>
</rules>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
{code}
> tests: sonar should report test coverage
> ----------------------------------------
>
> Key: JBIDE-23155
> URL: https://issues.jboss.org/browse/JBIDE-23155
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Andre Dietisheim
> Fix For: 4.4.x
>
>
> I'd be great if our sonar instance at sonarqube.com would report test coverage.
> Docs are here: http://docs.sonarqube.org/display/PLUG/Code+Coverage+by+Unit+Tests+for+Ja...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23039:
-------------------------------------
> VAGRANT_DETECTED_OS
Hi [~hardy.ferentschik]:
VAGRANT_DETECTED_OS is unrelated to the cdt's instantiation and creation of a PTY. In fact, eclipse crashes before I even get to run anything, just when doing a PTY constructor. So it's unrelated.
> Need an interactive terminal that fits specific requirements
> ------------------------------------------------------------
>
> Key: JBIDE-23039
> URL: https://issues.jboss.org/browse/JBIDE-23039
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.4.1.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
> Attachments: vagranttty.png
>
>
> CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for.
> 1) I must be able to get a Process or IProcess object when a command is run
> 2) I must be able to get an event or know when the process terminates
> 3) The terminal or console must be interactive and allow user input when prompted.
> 4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins.
> These three requirements thus far seem impossible to solve. Solutions that have been attempted are:
> 1) Creating a java Process by myself via Runtime.exec. The interactive prompts never arrive and there is no API for Process to know when it is waiting for input.
> 2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed:
> a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input
> b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen
> 3) Launching / Opening a tm.terminal view. This solution fails requirements 1 and 2. We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed.
> Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant.
> Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream?
> No other obvious solutions have presented themselves in the past year.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23016:
---------------------------------------
[~hardy.ferentschik], actually even if you're already logged in as an admin user on Windows, you still have to accept the admin permissions for the process. I would call this transparent as this is done by the OS and Eclipse do not have to support it in any way. But in my experience it is not true that as an admin there is no interaction needed - you won't need to enter your credentials, but you will still be prompted to accept this.
{quote}
BTW, does anybody know how to get back to the state where landrush needs to make these changes which require admin permissions? I mean how to recreate the first time use of landrush.
OS X - Remove the file created in /etc/resolver/
Linux - Remove generated file in /etc/dnsmasq.d and revert /etc/resolv.conf
{quote}
And what about Windows?
> When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23016
> URL: https://issues.jboss.org/browse/JBIDE-23016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.2.AM1
>
>
> The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
> This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
> When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months