[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3981:
------------------------------
Attachment: .log
I gave it a spin on my RHEL 7.2 VM - added the rh-eclipse46 repo, downloaded the devstudio rpm and yum installed the rpm.
Everything installs nicely, but eclipse won't start. Log is attached. Eclipse alone without the devstudio part worked for me btw.
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-23015) Creating a route should have a default port
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ]
Jeff MAURY edited comment on JBIDE-23015 at 8/31/16 2:18 AM:
-------------------------------------------------------------
It does not seem to have a route directed to a specific port. So I suggest that the service should be defined to a single port (by deleting other ports). [~fbricon] [~jcantrill] WDYT ?
was (Author: jeffmaury):
It does not seem to have a route directed to a specific port. So I suggest that the service should be defined to a single port (by deleting other ports). @fbricon @jcantrill WDYT ?
> Creating a route should have a default port
> -------------------------------------------
>
> Key: JBIDE-23015
> URL: https://issues.jboss.org/browse/JBIDE-23015
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Fix For: 4.4.1.Final
>
>
> When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail.
> There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others.
> The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation)
> To reproduce:
> - git clone https://github.com/redhat-helloworld-msa/aloha
> - mvn package
> - build docker image from Dockerfile, to CDK docker connection
> - deploy docker image to openshift
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-23015) Creating a route should have a default port
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23015?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23015:
------------------------------------
It does not seem to have a route directed to a specific port. So I suggest that the service should be defined to a single port (by deleting other ports). @fbricon @jcantrill WDYT ?
> Creating a route should have a default port
> -------------------------------------------
>
> Key: JBIDE-23015
> URL: https://issues.jboss.org/browse/JBIDE-23015
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Fix For: 4.4.1.Final
>
>
> When deploying a docker image, in the Services and Routing settings, when "Add route" is checked, if there are multiple ports exposed, then openshift will round-robin the route to any of the ports. So if you have 3 exposed ports, 1 of them is for the web app, then 2/3 of the http connections to the service will fail.
> There should be a new column, in the ports table, with 1 checkbox checkable at the time: checking 1 box will uncheck the others.
> The lowest port should be selected by default (that's what the oc client does apparently, but deserve confirmation)
> To reproduce:
> - git clone https://github.com/redhat-helloworld-msa/aloha
> - mvn package
> - build docker image from Dockerfile, to CDK docker connection
> - deploy docker image to openshift
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-23052) IllegalStateException in SProperties.get
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23052?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-23052:
-----------------------------------------------
I have reproduced the issue in debugger at Eclipse closing. We do not rely on Java deleting files marked to be deleted on exit. Eclipse may crush, its process may be manually killed, then temp files remain on disk. We clean our temp files in ModelPlugin.stop(). It is the phase of life-cycle when nothing valid should be expected of core (e.g. JDT throws JavaModelException, resources do not exist, etc.). Validation/build processes should be terminated as soon as possible, as they make closing Eclipse longer without any good reason. So, I suggest checking before logging the illegal state error if the core plugins got already inactive and in this case throw some CoreDisposedException to be caught and ignored by builders, validators and other processes that cannot be any good with the stopped core.
> IllegalStateException in SProperties.get
> ----------------------------------------
>
> Key: JBIDE-23052
> URL: https://issues.jboss.org/browse/JBIDE-23052
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.4.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Cannot read C:\Desarrollo\workspaceSTS\.metadata\.plugins\org.jboss.tools.common.model\tmp\efs_8421649034830489156.sp.txt for object
> entity:FacesConfig12
> id=
> xmlns=http://java.sun.com/xml/ns/javaee
> xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
> xmlns:xi=http://www.w3.org/2001/XInclude
> xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd
> version=1.2
> isIncorrect=no
> incorrectBody=
> encoding=UTF-8
> {noformat}
> java.lang.IllegalStateException: Cannot read C:\Desarrollo\workspaceSTS\.metadata\.plugins\org.jboss.tools.common.model\tmp\efs_8421649034830489156.sp.txt for object
> entity:FacesConfig12
> id=
> xmlns=http://java.sun.com/xml/ns/javaee
> xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
> xmlns:xi=http://www.w3.org/2001/XInclude
> xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd
> version=1.2
> isIncorrect=no
> incorrectBody=
> encoding=UTF-8
> at org.jboss.tools.common.model.impl.SProperties.get(XModelObjectImpl.java:692)
> at org.jboss.tools.common.model.impl.XModelObjectImpl.get(XModelObjectImpl.java:145)
> at org.jboss.tools.common.model.filesystems.impl.FileAnyImpl.get(FileAnyImpl.java:176)
> at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.get(AbstractExtendedXMLFileImpl.java:71)
> at org.jboss.tools.jst.web.model.AbstractWebFileImpl.getAsText(AbstractWebFileImpl.java:54)
> at org.jboss.tools.common.model.util.PositionHolder.update(PositionHolder.java:60)
> at org.jboss.tools.jst.web.model.project.ext.store.XMLValueInfo.getPositionHolder(XMLValueInfo.java:59)
> at org.jboss.tools.jst.web.model.project.ext.store.XMLValueInfo.getLength(XMLValueInfo.java:41)
> at org.jboss.tools.common.validation.ValidationErrorManager.addError(ValidationErrorManager.java:174)
> at org.jboss.tools.jst.web.validation.Check.fireMessage(Check.java:49)
> at org.jboss.tools.jst.web.validation.CheckClass.fireNotExist(CheckClass.java:192)
> at org.jboss.tools.jst.web.validation.CheckClass.check(CheckClass.java:96)
> at org.jboss.tools.jsf.web.validation.FacesConfigValidator.validateObject(FacesConfigValidator.java:284)
> at org.jboss.tools.jsf.web.validation.FacesConfigValidator.validateObject(FacesConfigValidator.java:289)
> at org.jboss.tools.jsf.web.validation.FacesConfigValidator.validateObject(FacesConfigValidator.java:289)
> at org.jboss.tools.jsf.web.validation.FacesConfigValidator.validateFile(FacesConfigValidator.java:276)
> at org.jboss.tools.jsf.web.validation.FacesConfigValidator.validate(FacesConfigValidator.java:265)
> at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:140)
> at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)
> at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
> 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.core.resources | 3.10.0.v20150423-0755 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.0.v20150405-1723 | 3.12.0.v20160606-1342 |
> | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.6.0.v20160319-0612 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 |
> | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
> | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 |
> | org.eclipse.ltk.core.refactoring | 3.6.200.v20140826-0859 | 3.7.0.v20160419-0705 |
> | org.eclipse.ltk.ui.refactoring | 3.7.200.v20140625-1835 | 3.8.0.v20160518-1817 |
> | org.eclipse.search | 3.10.0.v20150318-0856 | 3.10.0.v20150318-0856 |
> | org.eclipse.swt | 3.104.0.v20150528-0211 | 3.105.0.v20160603-0902 |
> | org.eclipse.team.svn.core | 3.0.4.I20160131-1700 | 3.0.4.I20160131-1700 |
> | org.eclipse.team.svn.ui | 3.0.4.I20160131-1700 | 3.0.4.I20160131-1700 |
> | org.eclipse.team.ui | 3.7.200.v20150203-1452 | 3.7.200.v20150203-1452 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.eclipse.ui.editors | 3.9.0.v20150213-1939 | 3.9.0.v20150213-1939 |
> | org.eclipse.ui.ide | 3.11.0.v20150825-2158 | 3.11.0.v20150825-2158 |
> | org.eclipse.ui.navigator | 3.6.0.v20150422-0725 | 3.6.100.v20160518-1929 |
> | org.eclipse.ui.navigator.resources | 3.5.1.v20160128-1644 | 3.5.100.v20160518-1929 |
> | org.eclipse.wst.jsdt.core | 2.0.0.v201605251700 | 2.0.0.v201605251700 |
> | org.eclipse.wst.server.ui | 1.5.202.v201602111638 | 1.5.202.v201602111638 |
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.tools.batch.core | 1.8.0.Final-v20160610-0126-B1 | 1.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.common | 3.7.0.Final-v20150924-2213-B38 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.model | 3.7.0.Final-v20150924-2213-B38 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.model.ui | 3.7.0.Final-v20150924-2213-B38 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.hibernate.ui | 5.0.1.Final-v20160331-1852-B88 | 5.1.0.Final-v20160609-2146-B2 |
> | org.jboss.tools.hibernate.xml | 5.0.1.Final-v20160331-1852-B88 | 5.0.1.Final-v20160331-1852-B88 |
> | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.jsf.ui | 3.7.1.Final-v20160330-2256-B84 | 3.7.1.Final-v20160330-2256-B84 |
> | org.jboss.tools.jst.web | 3.7.1.Final-v20160331-0256-B96 | 3.8.0.Final-v20160609-2146-B2 |
> | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.0.Final-v20160609-2146-B2 |
> | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.8.0.Final-v20160609-2146-B2 |
> | org.jboss.tools.seam.core | 3.8.0.Final-v20160610-0126-B1 | 3.8.0.Final-v20160610-0126-B1 |
> Operating Systems:
> | Linux | 3.2.0 | 4.6.3.fc24 |
> | MacOSX | 10.11.4 | 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/57193d5de4b0cd449c...] 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)
7 years, 10 months
[JBoss JIRA] (JBIDE-22912) Deploy Docker Wizard: Inappropriate project combo size
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22912?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-22912:
-------------------------------------
Assignee: Snjezana Peco
> Deploy Docker Wizard: Inappropriate project combo size
> ------------------------------------------------------
>
> Key: JBIDE-22912
> URL: https://issues.jboss.org/browse/JBIDE-22912
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Environment: Fedora 24, GTK 3
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Priority: Minor
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: deploy-to-docker-wizard-fc23.png, project_combo.png
>
>
> In Deploy Docker Image wizard opened from context menu of a docker image is project combo stretched to left size and it does not look good.
> !project_combo.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months