[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22362:
-------------------------------
Fix Version/s: 4.4.3.Final
(was: 4.4.3.AM2)
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
> Attachments: enabling-dev-mode-has-encountered-an-error.png
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23783) Server adapter editor: Project settings composite is badly layouted
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23783?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23783:
-------------------------------------
Attachment: resized-project-settings-composite.png
> Server adapter editor: Project settings composite is badly layouted
> -------------------------------------------------------------------
>
> Key: JBIDE-23783
> URL: https://issues.jboss.org/browse/JBIDE-23783
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.3.AM2
>
> Attachments: corrected-project-settings-composite.png, project-settings-composite.png, resized-project-settings-composite.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a server adapter defined
> # EXEC: open up the editor for your server adapter
> Result:
> The project settings composite is badly layouted, especially the right border boundaries are not even:
> !project-settings-composite.png!
> # EXEC: maximise the editor
> Result:
> The "Eclipse Project:" combo does not fill all the available space. At times you also see this combo jumping in horizontal size. At times it's even smearing across redraws, there are leftovers of prior sizes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23783) Server adapter editor: Project settings composite is badly layouted
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23783?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23783:
-------------------------------------
Description:
steps to reproduce:
# ASSERT: make sure that you have a server adapter defined
# EXEC: open up the editor for your server adapter
Result:
The project settings composite is badly layouted, especially the right border boundaries are not even:
!project-settings-composite.png!
# EXEC: maximise the editor
Result:
The "Eclipse Project:" combo does not fill all the available space. At times you also see this combo jumping in horizontal size. At times it's even smearing across redraws, there are leftovers of prior sizes.
was:
steps to reproduce:
# ASSERT: make sure that you have a server adapter defined
# EXEC: open up the editor for your server adapter
Result:
The project settings composite is badly layouted, especially the right border boundaries are not even:
!project-settings-composite.png!
> Server adapter editor: Project settings composite is badly layouted
> -------------------------------------------------------------------
>
> Key: JBIDE-23783
> URL: https://issues.jboss.org/browse/JBIDE-23783
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.3.AM2
>
> Attachments: corrected-project-settings-composite.png, project-settings-composite.png, resized-project-settings-composite.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a server adapter defined
> # EXEC: open up the editor for your server adapter
> Result:
> The project settings composite is badly layouted, especially the right border boundaries are not even:
> !project-settings-composite.png!
> # EXEC: maximise the editor
> Result:
> The "Eclipse Project:" combo does not fill all the available space. At times you also see this combo jumping in horizontal size. At times it's even smearing across redraws, there are leftovers of prior sizes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23766) ZipException in CDICoreBuilder when indexing some Camel artifacts
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23766?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23766:
-------------------------------
Fix Version/s: 4.4.3.Final
(was: 4.4.3.AM2)
> ZipException in CDICoreBuilder when indexing some Camel artifacts
> -----------------------------------------------------------------
>
> Key: JBIDE-23766
> URL: https://issues.jboss.org/browse/JBIDE-23766
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.4.2.Final
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Fix For: 4.4.3.Final
>
> Attachments: FT_FISprojectBldFail_011917.rtf, FT_blankBlueprintProj.log, FuseToolingInstalledSW.png, blankBlueprintPomError.png, devstudio10.0ISinstalledFTplugins.png, newFuseFISProjectCreateLog.hang, newFuseProjectCreateLog2.hang, settings.xml
>
>
> it would be nice to provide more information in log such as teh classes in inspection by CDI Core Builder
> {noformat}
> !ENTRY org.jboss.tools.common.core 4 0 2017-01-17 11:17:20.815
> !MESSAGE invalid LOC header (bad signature)
> !STACK 0
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(Native Method)
> at java.util.zip.ZipFile.access$1400(ZipFile.java:60)
> at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:419)
> at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:286)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at java.io.DataInputStream.readFully(DataInputStream.java:195)
> at java.io.DataInputStream.readFully(DataInputStream.java:169)
> at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:433)
> at org.jboss.jandex.Indexer.index(Indexer.java:689)
> at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56)
> at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> 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:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4070) DevStudio / external OpenShift fails deployment
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4070?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4070:
-----------------------------
Fix Version/s: 10.3.0.GA
(was: 10.3.0.AM2)
> DevStudio / external OpenShift fails deployment
> -----------------------------------------------
>
> Key: JBDS-4070
> URL: https://issues.jboss.org/browse/JBDS-4070
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 10.1.0.GA
> Environment: DevStudio as used with an external OpenShift
> Reporter: Rick Wagner
> Assignee: Jeff MAURY
> Labels: openshift_v3
> Fix For: 10.3.0.GA
>
> Attachments: OSDeployRecreate.docx, eap-app-server-adapter-publish.png, eap-app-server-adapter-settings.png, kitchensink-ear-deployed-succcessfully.png, kitchensink-ear-projects.png, new-openshift-server-adapter.png
>
>
> If DevStudio (with Server Adapter configured for external OpenShift) is used to deploy an application developed in DevStudio, errors result.
> The reporting user shows indications additional 'deploy' directories are being synthesized as the binary target location. The log reports:
> 15:59:41,588 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0010: Scan found incompletely copied file content for deployment /opt/eap/standalone/deployments/deploy/deploy/deploy/deploy/deploy/deploy/activemq-rar.rar.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-20346) Jts quickstart (EAP 6.4) contains XML validation errors
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20346?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20346:
-------------------------------
Fix Version/s: 4.4.3.Final
(was: 4.4.3.AM2)
> Jts quickstart (EAP 6.4) contains XML validation errors
> -------------------------------------------------------
>
> Key: JBIDE-20346
> URL: https://issues.jboss.org/browse/JBIDE-20346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.0.Beta2
> Environment: JBDS 9.0.0.Beta2
> Reporter: Radim Hopp
> Fix For: 4.4.3.Final
>
>
> jts quickstart contains XML validation errors after import:
> {noformat}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected. jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 30 XML Problem
> {noformat}
> {noformat}
> Referenced file contains errors (jar:file:/home/rhopp/eclipse/jbdevstudio-9.0.0.Beta2/studio/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150716-2030-B26.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 1 XML Problem
> {noformat}
> The same error was once reported in JBIDE-17871, but that jira was closed as duplicate (of JBIDE-12990), but this error is not in the original (JBIDE-12990) issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months