September 2015 - jbosstools-issues

[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 updated JBDS-3531: ----------------------------- Description: 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. 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 - suspect something is missing, or else the OS detection is faulty. {code} > 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 > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > 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, 9 months

1
0
0 / 0

[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 updated JBDS-3531: ----------------------------- Component/s: installer > 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 > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3531) versionwatch install not working with JBDS 10 - os detection fails

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3531: -------------------------------- Summary: 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 Affects Versions: 10.0.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt 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 - suspect something is missing, or else the OS detection is faulty. {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-508: ---------------------------------- Here's my proposal for the most pressing issue - removal of unwanted early access URLs in the Eclipse Luna install update site list (without rebuilding anything): 1. Update http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... composites to contain the following children: {code} <children size='3'> <child location='http://download.jboss.org/jbosstools/updates/stable/luna/'/> <child location='http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...'/> <child location='http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.7.Fi...'/> </children> {code} 2. Create http://download.jboss.org/jbosstools/discovery/stable/integration-stack/e... - composites to contain: {code} <children size='3'> <child location='http://download.jboss.org/jbosstools/updates/stable/luna/'/> <child location='http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac...'/> <child location='http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.7.Fi...'/> </children> {code} - modify the plugin.xml in the EA discovery jar to establish the following as the siteUrl: {code} siteUrl="${jboss.discovery.earlyaccess.site.integration-stack.url}" {code} 3. The current jbosstools-directory.xml http://download.jboss.org/jbosstools/updates/stable/luna/jbosstools-direc... appears as follows: {code} <directory xmlns="http://www.eclipse.org/mylyn/discovery/directory/"> <entry url="plugins/org.jboss.tools.central.discovery.earlyaccess_4.2.3.Final-v20150327-0914-B526.jar" permitCategories="true"/> <entry url="plugins/org.jboss.tools.central.discovery_4.2.3.Final-v20150409-0637-B528.jar" permitCategories="true"/> <entry permitCategories="true" url="plugins/org.jboss.tools.central.discovery.integration-stack_4.2.3.Final-v20150824-1515-B22.jar"/> <entry permitCategories="true" url="plugins/org.jboss.tools.central.discovery.integration-stack.earlyaccess_4.2.3.Final-v20150824-1515-B22.jar"/> </directory> {code} I'll copy the updated IS EA jar into the parent plugins directory. 4. Create a composite site http://download.jboss.org/jbosstools/discovery/stable/integration-stack/e... which references http://download.jboss.org/jbosstools/discovery/stable/integration-stack/e... 5. Modify ide-config.properties to set the jboss.discovery.earlyaccess.site.integration-stack.url property: {code} jboss.discovery.earlyaccess.site.integration-stack.url|jbosstools|4.2.4=h... jboss.discovery.earlyaccess.site.integration-stack.url|jbosstools|4.2=htt... {code} That should do it for JBT. I'd like to complete everything there and then proceed to do similar things to devstudio. It works locally for me. > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20735) Docker New and Noteworthy for 4.3.0.CR1

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20735?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-20735: --------------------------------------- thanks ;-) > Docker New and Noteworthy for 4.3.0.CR1 > --------------------------------------- > > Key: JBIDE-20735 > URL: https://issues.jboss.org/browse/JBIDE-20735 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Docker is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Docker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19719) EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19719?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19719. ------------------------------ Verified in JBDS 9.0.0.CR1a build. > EasyImport of MobileHybrid project with Android SDK not configured results in errors - written to .log, but not communicated to the user via the UI > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19719 > URL: https://issues.jboss.org/browse/JBIDE-19719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Fix For: 4.3.0.Beta2 > > Attachments: jbosstools-diagnostics-20150427143128.zip, jbosstools-diagnostics-20150428105107.zip > > > This issue is related to JBIDE-19716 > Multiple errors are raised when a mobile hybrid project created in Central in JBoss Tools 4.3.0.alpha2 is exported and then imported from a directory using easy import. > See attached .zip for the error file (logs, etc..) > The error message logged is: > eclipse.core.runtime.CoreException: Android SDK location is not defined -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20735) Docker New and Noteworthy for 4.3.0.CR1

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20735?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20735. --------------------------------- I verified the N&N here: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.CR1.html#d... > Docker New and Noteworthy for 4.3.0.CR1 > --------------------------------------- > > Key: JBIDE-20735 > URL: https://issues.jboss.org/browse/JBIDE-20735 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Docker is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Docker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20735) Docker New and Noteworthy for 4.3.0.CR1

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20735?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20735: --------------------------------------- And applied a small fix for a typo here ;) https://github.com/jbosstools/jbosstools-website/commit/0dd6cd4f0a0286e70... > Docker New and Noteworthy for 4.3.0.CR1 > --------------------------------------- > > Key: JBIDE-20735 > URL: https://issues.jboss.org/browse/JBIDE-20735 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.0.CR1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Docker is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Docker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20537) wildfly-ejb-multi-server-app-one-ejb quickstart content incomplete

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20537?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20537: --------------------------------------- [~rob.stryker] where can I verify this? Is the quickstart also available from Central, or do I simply get it from github? > wildfly-ejb-multi-server-app-one-ejb quickstart content incomplete > ------------------------------------------------------------------ > > Key: JBIDE-20537 > URL: https://issues.jboss.org/browse/JBIDE-20537 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Labels: xml_validation_quickstart_content, xml_validation_quickstarts_wildfly > Fix For: 4.3.0.CR1 > > > Even after fixing https://issues.jboss.org/browse/JBIDE-20536 to import some namespaces using exact schema locations on the web, wildfly-ejb-multi-server-app-one-ejb fails to validate. > The file jboss-ejb3.xml has the following content (trimmed for brevity): > {code} > <jboss:ejb-jar (cut out xml:ns stuff) version="3.1" impl-version="2.0"> > <enterprise-beans> > </enterprise-beans> > <assembly-descriptor> > </assembly-descriptor> > </jboss:ejb-jar> > {code} > Unfortunately, empty enterprise-beans tags are invalid according to the xsd against which this is validated. Error message as follows: > {code} > cvc-complex-type.2.4.b: The content of element 'enterprise-beans' is not complete. One of '{"http:// > java.sun.com/xml/ns/javaee":session, "http://java.sun.com/xml/ns/javaee":entity, "http:// > java.sun.com/xml/ns/javaee":message-driven}' is expected. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20533) Bean-validation quickstart fails to validate in jbt

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20533?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20533: --------------------------------------- [~rob.stryker], how can I verify this? Do I need to get the quickstart from github and then import? Or can I do that via Central? In Central, I found only two versions of bean-validation project - one for EAP 6.4 and one for EAP 6.3. > Bean-validation quickstart fails to validate in jbt > --------------------------------------------------- > > Key: JBIDE-20533 > URL: https://issues.jboss.org/browse/JBIDE-20533 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: xml_validation_quickstart_content, xml_validation_quickstarts_wildfly > Fix For: 4.3.0.CR1 > > > bean-validation quickstart fails to validate in arquillian.xml. > The arquillian_1_0.xsd file includes the following: > {code} > <element name="container"> > <complexType> > <choice minOccurs="1" maxOccurs="unbounded"> > <element ref="tns:configuration" minOccurs="0" maxOccurs="1" /> >  > <element ref="tns:protocol" minOccurs="0" maxOccurs="unbounded" /> > </choice> > <attribute name="qualifier" type="string" use="required" /> > <attribute name="default" type="boolean" use="optional" default="false" /> > <attribute name="mode" use="optional" default="suite"> > <simpleType> > <restriction base="string"> > <enumeration value="suite" /> > <enumeration value="class" /> > <enumeration value="manual" /> > <enumeration value="custom" /> > </restriction> > </simpleType> > </attribute> > </complexType> > <unique name="unique-protocol-within-container"> > <annotation> > <documentation> > @type must be unique between all > protocols in a container. > </documentation> > </annotation> > <selector xpath="tns:protocol" /> > <field xpath="@type" /> > </unique> > </element> > {code} > The arquillian.xml included in the example includes the following: > {code} > <container qualifier="jboss" default="true"> >  >  > <property name="jbossHome">C:/tools/wildfly-9.0.0.Final</property> >  > </container> > {code} > Validation error is that "property" is not a valid sub-element, which is true based on the xsd file. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2015