[JBoss JIRA] (JBIDE-18623) Examples are not working in offline mode
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18623?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-18623:
------------------------------------------
I'm able to reproduce while following [~rhopp] steps.
[~fbricon] make sure that you run JBDS while disconnected from the internet (step 4.)
> Examples are not working in offline mode
> ----------------------------------------
>
> Key: JBIDE-18623
> URL: https://issues.jboss.org/browse/JBIDE-18623
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.2.0.CR2
> Environment: JBT 4.2.0.CR2a, JBDS 8.0.0.CR2a
> Reporter: Radim Hopp
> Assignee: Fred Bricon
>
> After executing offline groovy script and configuring JBT/JBDS to use generated examples and maven repository, project examples are not shown in JBoss Central.
> Warning is logged, when user tries to refresh "Start from sample" section (this one is from JBDS):
> {noformat}Invalid URL: http://download.jboss.org/jbosstools/examples/project-examples-jbds80.Bet...
> Groovy script has errors generating few examples (JBIDE-18582), but I think this is not relevant to this issue. What can be relevant is PR from JBIDE-18589 - switching descriptors from Beta3 to GA.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18623) Examples are not working in offline mode
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18623?page=com.atlassian.jira.plugi... ]
Radim Hopp edited comment on JBIDE-18623 at 10/15/14 7:49 AM:
--------------------------------------------------------------
I was also asked to provide exact steps to reproduce this issue:
Prereq: groovy ver>=2.1.x, redhat enterprise maven repo defined in settings.xml
1. Go to Preferences -> JBoss Tools-> Project Examples ->Offline support
2. Execute groovy command in terminal (outside eclipse) (this takes a long time) - it should generate "offline/" directory
3. Edit your maven settings.xml to use local repository "offline/.m2/repository"
4. disconnect from internet (on linux systems should be this command enough: `sudo unshare -n \-\- sh -c 'ifconfig lo up;su <USERNAME> -c xterm' ` this shoud open new xterm with access only to localhost
5. Start JBDS/JBT, go to Preferences -> JBoss Tools-> Project Examples ->Offline support
6. Check "Enable offline mode for project examples" and in Offline directory textfield fill "offline/.jbosstools/cache"
7. "OK"
8. All project examples should be working now even without internet access
was (Author: rhopp):
I was also asked to provide exact steps to reproduce this issue:
Prereq: groovy ver>=2.1.x, redhat enterprise maven repo defined in settings.xml
1. Go to Preferences -> JBoss Tools-> Project Examples ->Offline support
2. Execute groovy command in terminal (outside eclipse) (this takes a long time) - it should generate "offline/" directory
3. Edit your maven settings.xml to use local repository "offline/.m2/repository"
4. disconnect from internet (on linux systems should be this command enough: `sudo unshare -n -- sh -c 'ifconfig lo up;su <USERNAME> -c xterm' ` this shoud open new xterm with access only to localhost
5. Start JBDS/JBT, go to Preferences -> JBoss Tools-> Project Examples ->Offline support
6. Check "Enable offline mode for project examples" and in Offline directory textfield fill "offline/.jbosstools/cache"
7. "OK"
8. All project examples should be working now even without internet access
> Examples are not working in offline mode
> ----------------------------------------
>
> Key: JBIDE-18623
> URL: https://issues.jboss.org/browse/JBIDE-18623
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.2.0.CR2
> Environment: JBT 4.2.0.CR2a, JBDS 8.0.0.CR2a
> Reporter: Radim Hopp
> Assignee: Fred Bricon
>
> After executing offline groovy script and configuring JBT/JBDS to use generated examples and maven repository, project examples are not shown in JBoss Central.
> Warning is logged, when user tries to refresh "Start from sample" section (this one is from JBDS):
> {noformat}Invalid URL: http://download.jboss.org/jbosstools/examples/project-examples-jbds80.Bet...
> Groovy script has errors generating few examples (JBIDE-18582), but I think this is not relevant to this issue. What can be relevant is PR from JBIDE-18589 - switching descriptors from Beta3 to GA.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-17956) Add progress bar to Add Arquillian profiles dialog
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17956?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova updated JBIDE-17956:
------------------------------------
Attachment: progressbar-cr2a.ogv
> Add progress bar to Add Arquillian profiles dialog
> --------------------------------------------------
>
> Key: JBIDE-17956
> URL: https://issues.jboss.org/browse/JBIDE-17956
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: testing-tools
> Affects Versions: 4.2.0.Beta3
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Priority: Minor
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
> Attachments: progressbar-1.ogv, progressbar-2.ogv, progressbar-cr2a.ogv
>
>
> In Add Arquillian profiles dialog, when I select all profiles and press OK, it takes quite a long time to finish the task. There should be a progress bar in this case.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18111) Arquillian warnings are not cleared properly
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18111?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-18111.
-----------------------------------
Verified JBT 4.2.0.CR2a
> Arquillian warnings are not cleared properly
> --------------------------------------------
>
> Key: JBIDE-18111
> URL: https://issues.jboss.org/browse/JBIDE-18111
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.Beta3
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> When I create an arquillian test without test method and deployment method, I get 2 warnings - that is correct. However, when I mark class as abstract, these warnings should disappear, but they do not. I need to clean the project (causing to rebuild the project) to make those warnings disappear.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18265) NullPointerException in ArquillianBuilder when creating test class with the name Test
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18265?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova closed JBIDE-18265.
-----------------------------------
Verified JBT 4.2.0.CR2a
> NullPointerException in ArquillianBuilder when creating test class with the name Test
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18265
> URL: https://issues.jboss.org/browse/JBIDE-18265
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.CR1
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Priority: Critical
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
>
> When I try to create an Arquillan test class with the name Test, it is created, however, the Arquillian builder fails with NP.
> {code}
> java.lang.NullPointerException
> at org.eclipse.jdt.core.dom.MethodBinding.filterTypeAnnotations(MethodBinding.java:205)
> at org.eclipse.jdt.core.dom.MethodBinding.getAnnotations(MethodBinding.java:104)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.isDeploymentMethod(ArquillianSearchEngine.java:862)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.getDeploymentMethods(ArquillianSearchEngine.java:849)
> at org.jboss.tools.arquillian.core.internal.util.ArquillianSearchEngine.hasDeploymentMethod(ArquillianSearchEngine.java:599)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:255)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:210)
> at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:109)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> This is because the test method is generated with the @Test annotation without fully qualified name.
> {code}
> @Test
> public void test() {
> fail("Not yet implemented");
> }
> {code}
> In JUnit, when I tried to create test class with the name Test, the @Test annotation was generated with fullly qualified name
> {code}
> @Test
> @org.junit.Test
> public void test() {
> fail("Not yet implemented");
> }
> {code}
> However, when I checked that I want do generate tearDown method, JUnit created the annotation withou fully qualified name too.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-3183) Usage website does not contain ws tester reporting
by Radim Hopp (JIRA)
Radim Hopp created JBDS-3183:
--------------------------------
Summary: Usage website does not contain ws tester reporting
Key: JBDS-3183
URL: https://issues.jboss.org/browse/JBDS-3183
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: usage, website
Affects Versions: 8.0.0.CR2
Reporter: Radim Hopp
Assignee: Radim Hopp
Priority: Minor
Usage website is missing info about Web Service Tester usage reporting.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18521) On RHEL7, Browsersim cannot use the SWT Browser (GTK2) as the browser engine
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18521?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18521:
------------------------------------------------
{quote}We did get the fix in about making gtk3 the default option for rhel if users are not running java8,right ? {quote}
We set GTK3 as a default option on RHEL7, regardless of java version. Maybe you remember about JBIDE-18522, but I'm not sure this issue is not machine specific, cause I could not reproduce on another RHEL7 computer. Will retest everything with [~ldimaggio] once again later(cause documentation is highest priority for me now).
> On RHEL7, Browsersim cannot use the SWT Browser (GTK2) as the browser engine
> ----------------------------------------------------------------------------
>
> Key: JBIDE-18521
> URL: https://issues.jboss.org/browse/JBIDE-18521
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.CR2
> Environment: RHEL7
> Java 1.7
> Java 1.8
> Reporter: Len DiMaggio
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.1.Final, 4.3.x
>
> Attachments: screenshot_JBIDE-18521.png
>
>
> Steps to reproduce:
> * Configure Browsersim to use either Oracle 1.7 or 1.8 JDK on RHEL7
> * Open Browsersim
> * Right-click to open the Browsersim context menu
> * Observe the "please install webkitgtk to to use SWT.WebKit.engine" error
> (See attached screenshot)
> The webkitgtk package does not exist for RHEL7 - webkitgtk3 is installed in RHEL7 OOTB.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months