[JBoss JIRA] (JBIDE-20600) document how to use Deploy to OpenShift (Docker integration)
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20600?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20600:
--------------------------------
Summary: document how to use Deploy to OpenShift (Docker integration) (was: document how to use Deploy to OpenShift)
> document how to use Deploy to OpenShift (Docker integration)
> ------------------------------------------------------------
>
> Key: JBIDE-20600
> URL: https://issues.jboss.org/browse/JBIDE-20600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.0.Final
>
>
> Trying to use the Deploy to OpenShift dialog I found a few issues and i'm a bit stuck figuring out how it works.
> What I did was trying to just take jboss/wildfly:latest and deploy to openshift.
> First off, the first page of Deploy to openshift wont let me create a connection or project so I have as a user to have done that *before* starting the dialog.
> Once I have done that the dialog is asking for a lot of questions but very little hints about what they are.
> One example is "Add Route" on services ports page - that page can have multiple services so which does "Add Route" refer to and should it not need to know which port needed to use ?
> But worst issue is that once all that is filled out then I do not seem to be able to get any logs or info on why wildfly is not started.
> neither in webconsole nor in eclipse views.
> Should there not be access to some console logs or similar to things created by a project ?
> anyway - long description to point out we need some docs on how to actually use this if we cannot fix the UI before GA.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20600) document how to use Deploy to OpenShift
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20600?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20600:
-------------------------------------
What is really missing are step by step instructions to Deploy a Docker Image to OpenShift (that what the title of this ticket references)
[~jcantrill] could you write an how-to page in https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
Then it should be linked from https://github.com/jbosstools/jbosstools-website/blob/master/documentatio... and https://github.com/jbosstools/jbosstools-website/blob/master/documentatio...
> document how to use Deploy to OpenShift
> ---------------------------------------
>
> Key: JBIDE-20600
> URL: https://issues.jboss.org/browse/JBIDE-20600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.3.0.Final
>
>
> Trying to use the Deploy to OpenShift dialog I found a few issues and i'm a bit stuck figuring out how it works.
> What I did was trying to just take jboss/wildfly:latest and deploy to openshift.
> First off, the first page of Deploy to openshift wont let me create a connection or project so I have as a user to have done that *before* starting the dialog.
> Once I have done that the dialog is asking for a lot of questions but very little hints about what they are.
> One example is "Add Route" on services ports page - that page can have multiple services so which does "Add Route" refer to and should it not need to know which port needed to use ?
> But worst issue is that once all that is filled out then I do not seem to be able to get any logs or info on why wildfly is not started.
> neither in webconsole nor in eclipse views.
> Should there not be access to some console logs or similar to things created by a project ?
> anyway - long description to point out we need some docs on how to actually use this if we cannot fix the UI before GA.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-20737) On Linux, non-root user us not able to use auto-detect to access running Docker instance
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugi... ]
Len DiMaggio reassigned JBIDE-20737:
------------------------------------
Assignee: Misha Ali (was: Len DiMaggio)
> On Linux, non-root user us not able to use auto-detect to access running Docker instance
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-20737
> URL: https://issues.jboss.org/browse/JBIDE-20737
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker
> Affects Versions: 4.3.0.CR1
> Environment: RHEL 7
> OpenJDK 1.8
> Version: 9.0.0.CR1
> Build id: CR1-v20150912-1100-B100
> Build date: 20150912-1100
> CR1 includes:
> com.spotify.docker.client_3.1.1.jar
> org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar
> org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar
> org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar
> Reporter: Len DiMaggio
> Assignee: Misha Ali
> Fix For: 4.3.1.Final
>
> Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png
>
>
> On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock)
> A non-root user is not able to connect. No warning or error is written to the UI/dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBDS-3531) versionwatch thinks JBDS 10 is older than JBDS 9 (1 < 9 instead of 10 > 9)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3531?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3531:
-----------------------------
Description:
In http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers... we see versionwatch complaining that the version of com.jboss.devstudio.core.feature went DOWN from 10.0.0 to 9.0.0.
Obviously we need to fix the version diffing engine so it sees more than the first digit of the version, and therefore sees 10 > 9, rather than 1 < 9.
was:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
{code}
/qa/tools/opt/amd64/jdk1.8.0_last/bin/java -DTRACE=true -DSTREAM_NAME=10.0 -jar /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_master/latest/all/jboss-devstudio-10.0.0.Alpha1-v20150918-1953-B3976-installer-standalone.jar /home/hudson/static_build_env/jbds/versionwatch/installations/jbds-10.0.0.Alpha1.install.xml
10:48:07 TRACE enabled.
10:48:07 checking if os constraints [Os family unix name null version null arch null jre null ] match current OS
10:48:07 matched current OS.
10:48:07 checking if os constraints [Os family windows name null version null arch null jre null ] match current OS
10:48:07 checking if os constraints [Os family null name null version null arch x86 jre null ] match current OS
10:48:07 no match with current OS!
10:48:08 Custom langpack for eng available.
10:48:08 Initializing RulesEngine
10:48:08 RulesEngine.init()
10:48:08 Initializing builtin conditions for packs.
10:48:08 Pack.getCondition(): null for pack jbds-installer
10:48:08 Pack.getCondition(): null for pack jbds.update
10:48:08 Pack.getCondition(): null for pack jbds.generate
10:48:08 Pack.getCondition(): null for pack jbosseap
10:48:08 [ Starting automated installation ]
10:48:08 java.lang.NullPointerException
10:48:08 java.lang.NullPointerException
10:48:08 at com.jboss.devstudio.core.installer.PathInputPanelAutomationHelper.runAutomated(PathInputPanelAutomationHelper.java:48)
10:48:08 at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432)
10:48:08 at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388)
10:48:08 at com.izforge.izpack.installer.Installer.main(Unknown Source)
10:48:08 [ Automated installation FAILED! ]
{code}
Tested locally on dev01:
{code} /qa/tools/opt/jdk1.8.0_last/bin/java -DTRACE=true -DSTREAM_NAME=10.0 -jar jboss-devstudio-10.0.0.Alpha1-v20150918-1953-B3976-installer-standalone.jar /tmp/jbds-10.0.0.Alpha1.install.xml
TRACE enabled.
checking if os constraints [Os family unix name null version null arch null jre null ] match current OS
matched current OS.
checking if os constraints [Os family windows name null version null arch null jre null ] match current OS
checking if os constraints [Os family null name null version null arch x86 jre null ] match current OS
no match with current OS!
Custom langpack for eng available.
Initializing RulesEngine
RulesEngine.init()
Initializing builtin conditions for packs.
Pack.getCondition(): null for pack jbds-installer
Pack.getCondition(): null for pack jbds.update
Pack.getCondition(): null for pack jbds.generate
Pack.getCondition(): null for pack jbosseap
[ Starting automated installation ]
java.lang.NullPointerException
java.lang.NullPointerException
at com.jboss.devstudio.core.installer.PathInputPanelAutomationHelper.runAutomated(PathInputPanelAutomationHelper.java:48)
at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432)
at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388)
at com.izforge.izpack.installer.Installer.main(Unknown Source)
[ Automated installation FAILED! ]
{code}
So, we might have to tweak the XML file - [^jbds-10.0.0.Alpha1.install.xml] as I suspect something is missing, or else maybe the OS detection is faulty.
> versionwatch thinks JBDS 10 is older than JBDS 9 (1 < 9 instead of 10 > 9)
> --------------------------------------------------------------------------
>
> Key: JBDS-3531
> URL: https://issues.jboss.org/browse/JBDS-3531
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.0.0.Alpha1
>
> Attachments: jbds-10.0.0.Alpha1.install.xml
>
>
> In http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers... we see versionwatch complaining that the version of com.jboss.devstudio.core.feature went DOWN from 10.0.0 to 9.0.0.
> Obviously we need to fix the version diffing engine so it sees more than the first digit of the version, and therefore sees 10 > 9, rather than 1 < 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBDS-3531) versionwatch install not working with JBDS 10 - os detection fails
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3531?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3531:
----------------------------------
You're correct -- I thought I'd already rebuilt w/ my namespace fix, but turns out I hadn't. Respun and it's happy.
However, versionwatch sees "10.0" as older than "9.0" so we need to fix that. :D
http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
I'll rename this JIRA.
> versionwatch install not working with JBDS 10 - os detection fails
> ------------------------------------------------------------------
>
> Key: JBDS-3531
> URL: https://issues.jboss.org/browse/JBDS-3531
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.0.0.Alpha1
>
> Attachments: jbds-10.0.0.Alpha1.install.xml
>
>
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> /qa/tools/opt/amd64/jdk1.8.0_last/bin/java -DTRACE=true -DSTREAM_NAME=10.0 -jar /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_master/latest/all/jboss-devstudio-10.0.0.Alpha1-v20150918-1953-B3976-installer-standalone.jar /home/hudson/static_build_env/jbds/versionwatch/installations/jbds-10.0.0.Alpha1.install.xml
> 10:48:07 TRACE enabled.
> 10:48:07 checking if os constraints [Os family unix name null version null arch null jre null ] match current OS
> 10:48:07 matched current OS.
> 10:48:07 checking if os constraints [Os family windows name null version null arch null jre null ] match current OS
> 10:48:07 checking if os constraints [Os family null name null version null arch x86 jre null ] match current OS
> 10:48:07 no match with current OS!
> 10:48:08 Custom langpack for eng available.
> 10:48:08 Initializing RulesEngine
> 10:48:08 RulesEngine.init()
> 10:48:08 Initializing builtin conditions for packs.
> 10:48:08 Pack.getCondition(): null for pack jbds-installer
> 10:48:08 Pack.getCondition(): null for pack jbds.update
> 10:48:08 Pack.getCondition(): null for pack jbds.generate
> 10:48:08 Pack.getCondition(): null for pack jbosseap
> 10:48:08 [ Starting automated installation ]
> 10:48:08 java.lang.NullPointerException
> 10:48:08 java.lang.NullPointerException
> 10:48:08 at com.jboss.devstudio.core.installer.PathInputPanelAutomationHelper.runAutomated(PathInputPanelAutomationHelper.java:48)
> 10:48:08 at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432)
> 10:48:08 at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388)
> 10:48:08 at com.izforge.izpack.installer.Installer.main(Unknown Source)
> 10:48:08 [ Automated installation FAILED! ]
> {code}
> Tested locally on dev01:
> {code} /qa/tools/opt/jdk1.8.0_last/bin/java -DTRACE=true -DSTREAM_NAME=10.0 -jar jboss-devstudio-10.0.0.Alpha1-v20150918-1953-B3976-installer-standalone.jar /tmp/jbds-10.0.0.Alpha1.install.xml
> TRACE enabled.
> checking if os constraints [Os family unix name null version null arch null jre null ] match current OS
> matched current OS.
> checking if os constraints [Os family windows name null version null arch null jre null ] match current OS
> checking if os constraints [Os family null name null version null arch x86 jre null ] match current OS
> no match with current OS!
> Custom langpack for eng available.
> Initializing RulesEngine
> RulesEngine.init()
> Initializing builtin conditions for packs.
> Pack.getCondition(): null for pack jbds-installer
> Pack.getCondition(): null for pack jbds.update
> Pack.getCondition(): null for pack jbds.generate
> Pack.getCondition(): null for pack jbosseap
> [ Starting automated installation ]
> java.lang.NullPointerException
> java.lang.NullPointerException
> at com.jboss.devstudio.core.installer.PathInputPanelAutomationHelper.runAutomated(PathInputPanelAutomationHelper.java:48)
> at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432)
> at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388)
> at com.izforge.izpack.installer.Installer.main(Unknown Source)
> [ Automated installation FAILED! ]
> {code}
> So, we might have to tweak the XML file - [^jbds-10.0.0.Alpha1.install.xml] as I suspect something is missing, or else maybe the OS detection is faulty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBDS-3531) versionwatch thinks JBDS 10 is older than JBDS 9 (1 < 9 instead of 10 > 9)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3531?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3531:
-----------------------------
Summary: versionwatch thinks JBDS 10 is older than JBDS 9 (1 < 9 instead of 10 > 9) (was: versionwatch install not working with JBDS 10 - os detection fails)
> versionwatch thinks JBDS 10 is older than JBDS 9 (1 < 9 instead of 10 > 9)
> --------------------------------------------------------------------------
>
> Key: JBDS-3531
> URL: https://issues.jboss.org/browse/JBDS-3531
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.0.0.Alpha1
>
> Attachments: jbds-10.0.0.Alpha1.install.xml
>
>
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> /qa/tools/opt/amd64/jdk1.8.0_last/bin/java -DTRACE=true -DSTREAM_NAME=10.0 -jar /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_master/latest/all/jboss-devstudio-10.0.0.Alpha1-v20150918-1953-B3976-installer-standalone.jar /home/hudson/static_build_env/jbds/versionwatch/installations/jbds-10.0.0.Alpha1.install.xml
> 10:48:07 TRACE enabled.
> 10:48:07 checking if os constraints [Os family unix name null version null arch null jre null ] match current OS
> 10:48:07 matched current OS.
> 10:48:07 checking if os constraints [Os family windows name null version null arch null jre null ] match current OS
> 10:48:07 checking if os constraints [Os family null name null version null arch x86 jre null ] match current OS
> 10:48:07 no match with current OS!
> 10:48:08 Custom langpack for eng available.
> 10:48:08 Initializing RulesEngine
> 10:48:08 RulesEngine.init()
> 10:48:08 Initializing builtin conditions for packs.
> 10:48:08 Pack.getCondition(): null for pack jbds-installer
> 10:48:08 Pack.getCondition(): null for pack jbds.update
> 10:48:08 Pack.getCondition(): null for pack jbds.generate
> 10:48:08 Pack.getCondition(): null for pack jbosseap
> 10:48:08 [ Starting automated installation ]
> 10:48:08 java.lang.NullPointerException
> 10:48:08 java.lang.NullPointerException
> 10:48:08 at com.jboss.devstudio.core.installer.PathInputPanelAutomationHelper.runAutomated(PathInputPanelAutomationHelper.java:48)
> 10:48:08 at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432)
> 10:48:08 at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388)
> 10:48:08 at com.izforge.izpack.installer.Installer.main(Unknown Source)
> 10:48:08 [ Automated installation FAILED! ]
> {code}
> Tested locally on dev01:
> {code} /qa/tools/opt/jdk1.8.0_last/bin/java -DTRACE=true -DSTREAM_NAME=10.0 -jar jboss-devstudio-10.0.0.Alpha1-v20150918-1953-B3976-installer-standalone.jar /tmp/jbds-10.0.0.Alpha1.install.xml
> TRACE enabled.
> checking if os constraints [Os family unix name null version null arch null jre null ] match current OS
> matched current OS.
> checking if os constraints [Os family windows name null version null arch null jre null ] match current OS
> checking if os constraints [Os family null name null version null arch x86 jre null ] match current OS
> no match with current OS!
> Custom langpack for eng available.
> Initializing RulesEngine
> RulesEngine.init()
> Initializing builtin conditions for packs.
> Pack.getCondition(): null for pack jbds-installer
> Pack.getCondition(): null for pack jbds.update
> Pack.getCondition(): null for pack jbds.generate
> Pack.getCondition(): null for pack jbosseap
> [ Starting automated installation ]
> java.lang.NullPointerException
> java.lang.NullPointerException
> at com.jboss.devstudio.core.installer.PathInputPanelAutomationHelper.runAutomated(PathInputPanelAutomationHelper.java:48)
> at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432)
> at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388)
> at com.izforge.izpack.installer.Installer.main(Unknown Source)
> [ Automated installation FAILED! ]
> {code}
> So, we might have to tweak the XML file - [^jbds-10.0.0.Alpha1.install.xml] as I suspect something is missing, or else maybe the OS detection is faulty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBDS-3531) versionwatch install not working with JBDS 10 - os detection fails
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3531?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3531:
-------------------------------------
installer is fine, it is jenkins build generates automation xml file with wrong namespace.
> versionwatch install not working with JBDS 10 - os detection fails
> ------------------------------------------------------------------
>
> Key: JBDS-3531
> URL: https://issues.jboss.org/browse/JBDS-3531
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.0.0.Alpha1
>
> Attachments: jbds-10.0.0.Alpha1.install.xml
>
>
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> /qa/tools/opt/amd64/jdk1.8.0_last/bin/java -DTRACE=true -DSTREAM_NAME=10.0 -jar /qa/services/http/binaries/RHDS/10.0/snapshots/builds/devstudio.product_master/latest/all/jboss-devstudio-10.0.0.Alpha1-v20150918-1953-B3976-installer-standalone.jar /home/hudson/static_build_env/jbds/versionwatch/installations/jbds-10.0.0.Alpha1.install.xml
> 10:48:07 TRACE enabled.
> 10:48:07 checking if os constraints [Os family unix name null version null arch null jre null ] match current OS
> 10:48:07 matched current OS.
> 10:48:07 checking if os constraints [Os family windows name null version null arch null jre null ] match current OS
> 10:48:07 checking if os constraints [Os family null name null version null arch x86 jre null ] match current OS
> 10:48:07 no match with current OS!
> 10:48:08 Custom langpack for eng available.
> 10:48:08 Initializing RulesEngine
> 10:48:08 RulesEngine.init()
> 10:48:08 Initializing builtin conditions for packs.
> 10:48:08 Pack.getCondition(): null for pack jbds-installer
> 10:48:08 Pack.getCondition(): null for pack jbds.update
> 10:48:08 Pack.getCondition(): null for pack jbds.generate
> 10:48:08 Pack.getCondition(): null for pack jbosseap
> 10:48:08 [ Starting automated installation ]
> 10:48:08 java.lang.NullPointerException
> 10:48:08 java.lang.NullPointerException
> 10:48:08 at com.jboss.devstudio.core.installer.PathInputPanelAutomationHelper.runAutomated(PathInputPanelAutomationHelper.java:48)
> 10:48:08 at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432)
> 10:48:08 at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388)
> 10:48:08 at com.izforge.izpack.installer.Installer.main(Unknown Source)
> 10:48:08 [ Automated installation FAILED! ]
> {code}
> Tested locally on dev01:
> {code} /qa/tools/opt/jdk1.8.0_last/bin/java -DTRACE=true -DSTREAM_NAME=10.0 -jar jboss-devstudio-10.0.0.Alpha1-v20150918-1953-B3976-installer-standalone.jar /tmp/jbds-10.0.0.Alpha1.install.xml
> TRACE enabled.
> checking if os constraints [Os family unix name null version null arch null jre null ] match current OS
> matched current OS.
> checking if os constraints [Os family windows name null version null arch null jre null ] match current OS
> checking if os constraints [Os family null name null version null arch x86 jre null ] match current OS
> no match with current OS!
> Custom langpack for eng available.
> Initializing RulesEngine
> RulesEngine.init()
> Initializing builtin conditions for packs.
> Pack.getCondition(): null for pack jbds-installer
> Pack.getCondition(): null for pack jbds.update
> Pack.getCondition(): null for pack jbds.generate
> Pack.getCondition(): null for pack jbosseap
> [ Starting automated installation ]
> java.lang.NullPointerException
> java.lang.NullPointerException
> at com.jboss.devstudio.core.installer.PathInputPanelAutomationHelper.runAutomated(PathInputPanelAutomationHelper.java:48)
> at com.izforge.izpack.installer.AutomatedInstaller.installPanel(AutomatedInstaller.java:432)
> at com.izforge.izpack.installer.AutomatedInstaller.doInstall(AutomatedInstaller.java:388)
> at com.izforge.izpack.installer.Installer.main(Unknown Source)
> [ Automated installation FAILED! ]
> {code}
> So, we might have to tweak the XML file - [^jbds-10.0.0.Alpha1.install.xml] as I suspect something is missing, or else maybe the OS detection is faulty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months
[JBoss JIRA] (JBIDE-19536) Infinite job loop when creating project
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19536?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19536:
-----------------------------------
Priority: Critical (was: Major)
> Infinite job loop when creating project
> ---------------------------------------
>
> Key: JBIDE-19536
> URL: https://issues.jboss.org/browse/JBIDE-19536
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rastislav Wagner
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.3.1.Final, 4.4.0.Alpha1
>
> Attachments: building.png, cdi_jstack, jstack.out, threaddump-1440009974151.tdump, threaddump-1440009999047.tdump, threaddump-1440010035476.tdump, workspace_jbds9_endless_building_loop.rar
>
>
> Sometimes i end up in infinite job loop after creating a CDI project. There's no description of what jobs are running, not exception in log. In progress view I can see only "Building workspace (sleeping)" -see on video https://vimeo.com/123634974
> I was able to reproduce on CDI projects (1.0,1.2) but not on any other (Dynamic Web..)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 6 months