[JBoss JIRA] (ERT-408) Properties do not show information about selected image/container in respective tab [EBZ#500638]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-408?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston resolved ERT-408.
-------------------------------
Fix Version/s: Neon.1 (4.6)
Assignee: Xavier Coulon
Resolution: Done
> Properties do not show information about selected image/container in respective tab [EBZ#500638]
> ------------------------------------------------------------------------------------------------
>
> Key: ERT-408
> URL: https://issues.jboss.org/browse/ERT-408
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: Docker, bzira
> Fix For: Neon.1 (4.6)
>
>
> Properties view is empty if an image or a container is selected in Docker Images or Docker Containers tab. This was working in previous versions.
> When an image or a container is selected in Docker Explorer, properties view shows correct information.
> Eclipse version:
> Neon Release (4.6.0)
> Build id: 20160613-1800
> Docker Tooling:
> 2.1.0.201608292220
> Docker version:
> Docker version 1.12.1, build 23cf638
> (from upstream repository)
> Tested on Fedora 24
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-3866?page=com.atlassian.jira.plugin.... ]
Rob Stryker updated JBDS-3866:
------------------------------
Sprint: devex #123 November 2016
> vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-3866
> URL: https://issues.jboss.org/browse/JBDS-3866
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> (previous installs of CDK and dependencies)
> Reporter: Robert Terzi
> Assignee: Rob Stryker
> Fix For: 10.2.0.GA
>
>
> vagrant up through the CDK server tooling failed because of an rsync problem. The tooling lost track of the state of the vagrant box. The vagrant box couldn't be stopped from inside of Eclipse.
> The vagrant up failed because of an error with rsync. Something was confused about the user's home directory. It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist.
> The CDK server was shown as 'Started, Sychronized'.
> The error message appeared in the server console tab. However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either.
> Synchronized seems misleading here, since no files had been sync'd yet.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-3866?page=com.atlassian.jira.plugin.... ]
Rob Stryker reassigned JBDS-3866:
---------------------------------
Assignee: Rob Stryker
> vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-3866
> URL: https://issues.jboss.org/browse/JBDS-3866
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> (previous installs of CDK and dependencies)
> Reporter: Robert Terzi
> Assignee: Rob Stryker
> Fix For: 10.2.0.GA
>
>
> vagrant up through the CDK server tooling failed because of an rsync problem. The tooling lost track of the state of the vagrant box. The vagrant box couldn't be stopped from inside of Eclipse.
> The vagrant up failed because of an error with rsync. Something was confused about the user's home directory. It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist.
> The CDK server was shown as 'Started, Sychronized'.
> The error message appeared in the server console tab. However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either.
> Synchronized seems misleading here, since no files had been sync'd yet.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-3866?page=com.atlassian.jira.plugin.... ]
Rob Stryker updated JBDS-3866:
------------------------------
Fix Version/s: 10.2.0.GA
(was: 10.x)
> vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-3866
> URL: https://issues.jboss.org/browse/JBDS-3866
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> (previous installs of CDK and dependencies)
> Reporter: Robert Terzi
> Assignee: Rob Stryker
> Fix For: 10.2.0.GA
>
>
> vagrant up through the CDK server tooling failed because of an rsync problem. The tooling lost track of the state of the vagrant box. The vagrant box couldn't be stopped from inside of Eclipse.
> The vagrant up failed because of an error with rsync. Something was confused about the user's home directory. It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist.
> The CDK server was shown as 'Started, Sychronized'.
> The error message appeared in the server console tab. However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either.
> Synchronized seems misleading here, since no files had been sync'd yet.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBTIS-982) org.sonatype.tycho.m2e plug-in missing from integration stack
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-982?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBTIS-982:
-----------------------------------------
[~lhein] Do you think maybe that the dependency isn't dragging it in during an installation? I simply grabbed the Fuse tooling from the integration stack, so it would have grabbed whatever dependencies were set up there
> org.sonatype.tycho.m2e plug-in missing from integration stack
> -------------------------------------------------------------
>
> Key: JBTIS-982
> URL: https://issues.jboss.org/browse/JBTIS-982
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE
> Affects Versions: 10.0.0.Alpha1
> Reporter: Brian Fitzpatrick
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 10.0.0.CR1
>
>
> Based on FUSETOOLS-2170, we have discovered that the org.sonatype.tycho.m2e plug-in is missing from the Integration Stack.
> Can we add it back? It disappeared sometime after September 9.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-13851) Add source lookup classes to Java Search
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13851?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-13851:
-------------------------------------
[~snjeza] is this a good enough improvement to rebase it and get some screenshots up on how it works? I've marked it as later since it was marked 4.2.x. I'm not really sure how it was intended to work anyway.
> Add source lookup classes to Java Search
> ----------------------------------------
>
> Key: JBIDE-13851
> URL: https://issues.jboss.org/browse/JBIDE-13851
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Fix For: LATER
>
>
> This feature would be implemented in a similar way to adding PDE plugins to the Java Search.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4133) org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4133 at 11/8/16 4:12 PM:
-----------------------------------------------------------
You PR restricts the user to using lucene [3.5.0,4.0.0) [1]
[1] https://github.com/jbosstools/jbosstools-webservices/pull/256/files#diff-...
How's that going to work when only Lucene 5.4.1 is installed?
Which version of lucene do you have installed and active in your Eclipse's osgi console? Mine has this:
{code}ss lucene
id State Bundle
103 RESOLVED org.apache.lucene.analysis_3.5.0.v20120725-1805
104 RESOLVED org.apache.lucene.analyzers-common_5.4.1
105 RESOLVED org.apache.lucene.analyzers-smartcn_5.4.1
106 RESOLVED org.apache.lucene.core_5.4.1
107 RESOLVED org.apache.lucene.core_3.5.0.v20120725-1805
108 RESOLVED org.apache.lucene.queries_5.4.1
109 RESOLVED org.apache.lucene.queryparser_5.4.1
110 RESOLVED org.apache.lucene.sandbox_5.4.1
{code}
was (Author: nickboldt):
You PR restricts the user to using lucene [3.5.0,4.0.0) [1]
[1] https://github.com/jbosstools/jbosstools-webservices/pull/256/files#diff-...
How's that going to work when only Lucene 5.4.1 is installed?
> org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4133
> URL: https://issues.jboss.org/browse/JBDS-4133
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, target-platform, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 10.2.0.GA
>
> Attachments: image-2016-11-08-19-07-53-492.png, lucene3.5corevs.5.4.1analyzers-common.png, lucene3.5corevs.5.4.1queryparser.png, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt, TEST-org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.xml
>
>
> I'm getting this problem after running the HTML5 quickstart. I've installed this [1] version of the rpm.
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-10-26 16:22:07.578
> !MESSAGE An internal error occurred during: "JAX-RS Metamodel build...".
> !STACK 0
> java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.<init>(JaxrsMetamodel.java:163)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.create(JaxrsMetamodel.java:278)
> at org.jboss.tools.ws.jaxrs.core.metamodel.domain.JaxrsMetamodelLocator.get(JaxrsMetamodelLocator.java:120)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.apache.lucene.analysis.standard.StandardAnalyzer cannot be found by org.jboss.tools.ws.jaxrs.core_1.9.2.v20161011-1002
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 5 more
> {code}
> [1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4133) org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4133:
----------------------------------
You PR restricts the user to using lucene [3.5.0,4.0.0) [1]
[1] https://github.com/jbosstools/jbosstools-webservices/pull/256/files#diff-...
How's that going to work when only Lucene 5.4.1 is installed?
> org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4133
> URL: https://issues.jboss.org/browse/JBDS-4133
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, target-platform, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 10.2.0.GA
>
> Attachments: image-2016-11-08-19-07-53-492.png, lucene3.5corevs.5.4.1analyzers-common.png, lucene3.5corevs.5.4.1queryparser.png, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt, TEST-org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.xml
>
>
> I'm getting this problem after running the HTML5 quickstart. I've installed this [1] version of the rpm.
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-10-26 16:22:07.578
> !MESSAGE An internal error occurred during: "JAX-RS Metamodel build...".
> !STACK 0
> java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.<init>(JaxrsMetamodel.java:163)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.create(JaxrsMetamodel.java:278)
> at org.jboss.tools.ws.jaxrs.core.metamodel.domain.JaxrsMetamodelLocator.get(JaxrsMetamodelLocator.java:120)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.apache.lucene.analysis.standard.StandardAnalyzer cannot be found by org.jboss.tools.ws.jaxrs.core_1.9.2.v20161011-1002
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 5 more
> {code}
> [1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months