[JBoss JIRA] (JBIDE-22943) FileNotFoundException below DocTypeUtil.getContentInitFile (thrown in FileInputStream.open0)
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22943?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22943:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> FileNotFoundException below DocTypeUtil.getContentInitFile (thrown in FileInputStream.open0)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-22943
> URL: https://issues.jboss.org/browse/JBIDE-22943
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: file:\C:\Users\Administrator\eclipse\jee-mars\eclipse\links\eclipse\plugins\org.jboss.tools.vpe_3.7.1.Final-v20160331-0327-B91.jar!\ve\init.html (文件名、目录名或卷标语法不正确。)
> {noformat}
> java.io.FileNotFoundException: file:\C:\Users\Administrator\eclipse\jee-mars\eclipse\links\eclipse\plugins\org.jboss.tools.vpe_3.7.1.Final-v20160331-0327-B91.jar!\ve\init.html (文件名、目录名或卷标语法不正确。)
> at java.io.FileInputStream.open0(null:-2)
> at java.io.FileInputStream.open(null:-1)
> at java.io.FileInputStream.<init>(null:-1)
> at java.io.FileReader.<init>(null:-1)
> at org.jboss.tools.vpe.editor.util.DocTypeUtil.getContentInitFile(DocTypeUtil.java:354)
> at org.jboss.tools.vpe.editor.util.DocTypeUtil.prepareInitFile(DocTypeUtil.java:339)
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.setInitialContent(MozillaEditor.java:630)
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:610)
> at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:813)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:283)
> at org.eclipse.ui.part.MultiPageEditorPart$2.widgetSelected(MultiPageEditorPart.java:295)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> {noformat}
> Bundles:
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.7.1.Final-v20160331-0256-B96 |
> | org.jboss.tools.vpe | 3.7.1.Final-v20160331-0327-B91 | 3.7.1.Final-v20160331-0327-B91 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/574e7369e4b06056d2...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-19329) Start Forge2 runtime when workbench starts
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19329?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-19329:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Start Forge2 runtime when workbench starts
> ------------------------------------------
>
> Key: JBIDE-19329
> URL: https://issues.jboss.org/browse/JBIDE-19329
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: forge
> Affects Versions: 4.3.0.Alpha1
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Fix For: 4.5.x
>
>
> With removal of Forge1 some of the preferences related to Forge1 are gone. For example, Start Forge when workbench starts, or start in Debug mode.
> Some of them make sense and come handy also for Forge2.
> It would be good to bring back the start option for F2.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22948) NullPointerException in VpvEditorController.init
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22948?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22948:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> NullPointerException in VpvEditorController.init
> ------------------------------------------------
>
> Key: JBIDE-22948
> URL: https://issues.jboss.org/browse/JBIDE-22948
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.vpe.preview.editor.VpvEditorController.init(VpvEditorController.java:88)
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart$13.load(VpvEditorPart.java:615)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.createPartControl(VpvEditor.java:430)
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart.createVisualEditor(VpvEditorPart.java:620)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:283)
> at org.eclipse.ui.part.MultiPageEditorPart$2.widgetSelected(MultiPageEditorPart.java:295)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> {noformat}
> Bundles:
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.7.1.Final-v20160331-0256-B96 |
> | org.jboss.tools.vpe.preview.editor | 3.7.1.Final-v20160331-0327-B91 | 3.7.1.Final-v20160331-0327-B91 |
> Operating Systems:
> | Windows | 6.3.0 | 6.3.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/574c33cee4b06056d2...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-20177) migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20177?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-20177:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20177
> URL: https://issues.jboss.org/browse/JBIDE-20177
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.x
>
>
> If we can migrate this logic into the mojo...
> {code}
> if [[ ${skipRevisionCheckWhenPublishing} == "true" ]] || [[ $(. ${WORKSPACE}/sources/util/checkLatestPublishedSHA.sh -s ${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo -t http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...) == "true" ]]; then
> {code}
> ... we'll be able to remove this step in all jobs:
> {code}
> <hudson.tasks.Maven>
> <targets>-U -e org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack</targets>
> <mavenName>maven-3.2.5</mavenName>
> <properties>artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Beta2-SNAPSHOT:zip
> outputDirectory=${WORKSPACE}/sources
> trimVersion=true
> mdep.stripClassifier=true
> mdep.stripVersion=true</properties>
> <usePrivateRepository>false</usePrivateRepository>
> <settings class="jenkins.mvn.DefaultSettingsProvider"/>
> <globalSettings class="jenkins.mvn.DefaultGlobalSettingsProvider"/>
> </hudson.tasks.Maven>
> {code}
> ... and instead, just pass in those vars to maven:
> {code}
> -DskipRevisionCheckWhenPublishing=${skipRevisionCheckWhenPublishing}
> -DcheckLatestPublishedSHA_SOURCE_PATH=${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo
> -DcheckLatestPublishedSHA_TARGET_PATH=http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-build-sites.aggregate.${projectName}-site_${jbosstools_site_stream}/latest/all/repo/
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22353) TimeoutException in JettyServerRunner.start
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22353?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22353:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> TimeoutException in JettyServerRunner.start
> -------------------------------------------
>
> Key: JBIDE-22353
> URL: https://issues.jboss.org/browse/JBIDE-22353
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Xavier Coulon
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Failed to create or start LiveReload proxy for server wildfly at OpenShift 3 (10.1.2.2)
> {noformat}
> java.util.concurrent.TimeoutException: Failed to start Proxy Server (50347 -> 80) within expected time (reason: timeout)
> at org.jboss.tools.livereload.core.internal.server.jetty.JettyServerRunner.start(JettyServerRunner.java:72)
> at org.jboss.tools.livereload.core.internal.server.wst.LiveReloadServerBehaviour.startProxy(LiveReloadServerBehaviour.java:344)
> at org.jboss.tools.livereload.core.internal.server.wst.LiveReloadServerBehaviour.inform(LiveReloadServerBehaviour.java:304)
> at org.jboss.tools.livereload.core.internal.service.EventService.publish(EventService.java:58)
> at org.jboss.tools.livereload.core.internal.service.ServerLifeCycleListener.serverChanged(ServerLifeCycleListener.java:120)
> at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
> at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:745)
> at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:653)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setServerStarted(ControllableServerBehavior.java:201)
> at org.jboss.tools.openshift.core.server.OpenShiftServerBehaviour.setServerStarted(OpenShiftServerBehaviour.java:38)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.checkServerState(OpenShiftLaunchController.java:143)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:113)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160209-0147 | 3.8.0.v20160209-0147 |
> | org.eclipse.debug.core | 3.10.100.v20160203-1134 | 3.10.100.v20160203-1134 |
> | org.eclipse.wst.server.core | 1.8.100.v201603031514 | 1.8.100.v201603031514 |
> | org.jboss.ide.eclipse.as.wtp.core | 3.2.0.Alpha1-v20160505-0626-B966 | 3.2.0.Alpha1-v20160505-0626-B966 |
> | org.jboss.tools.livereload.core | 1.4.0.Alpha1-v20160401-2041-B449 | 1.4.0.Alpha1-v20160401-2041-B449 |
> | org.jboss.tools.openshift.core | 3.2.0.qualifier | 3.2.0.qualifier |
> Operating Systems:
> | MacOSX | 10.10.5 | 10.10.5 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/572cf573e4b0a54983...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-21755) Properties: "Eager-er" loading of the project properties
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-21755:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Properties: "Eager-er" loading of the project properties
> --------------------------------------------------------
>
> Key: JBIDE-21755
> URL: https://issues.jboss.org/browse/JBIDE-21755
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Labels: openshift_v3, properties
> Fix For: 4.5.x
>
>
> Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months