March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4167) Provide progression when installing "Supplemental Runtimes"

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4167?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4167: -------------------------------- Fix Version/s: 10.4.0.AM2 (was: 10.4.0.AM1) > Provide progression when installing "Supplemental Runtimes" > ----------------------------------------------------------- > > Key: JBDS-4167 > URL: https://issues.jboss.org/browse/JBDS-4167 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer > Affects Versions: 10.2.0.AM3 > Reporter: Aurélien Pupier > Fix For: 10.4.0.AM2 > > Attachments: image-2016-11-08-09-38-19-198.png > > > it stays several seconds (perhaps several minutes) in this state: > !image-2016-11-08-09-38-19-198.png|thumbnail! > wondering if it is frozen or not -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3645) Installation of JBoss Developer Studio to a network drive fails

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3645?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3645: -------------------------------- Fix Version/s: 10.4.0.AM2 (was: 10.4.0.AM1) > Installation of JBoss Developer Studio to a network drive fails > ---------------------------------------------------------------- > > Key: JBDS-3645 > URL: https://issues.jboss.org/browse/JBDS-3645 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 8.1.0.GA > Environment: * Windows Server 2012 > Reporter: Takayuki Konishi > Assignee: Denis Golovin > Fix For: 10.4.0.AM2 > > > A customer is trying to install 64 bit jboss developer studio 8.1 using java 1.8 64 bit on a network drive (32 bit) from their local 64 bit machine. > Installation failed with the error, see the attached error message: > {code} > !SESSION 2016-02-16 16:05:32.385 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.8.0_65 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -roaming -r jar:file:///E:/downloads/jboss-devstudio-8.1.0.GA-installer-standalone.jar!/ -d E:\tools\eclipse\studio -p jbds -i com.jboss.devstudio.core.package,org.testng.eclipse.feature.group,org.eclipse.wst.jsdt.feature.patch.feature.group -profileProperties org.eclipse.update.install.features=true > Command-line arguments: -roaming -r jar:file:///E:/downloads/jboss-devstudio-8.1.0.GA-installer-standalone.jar!/ -d E:\tools\eclipse\studio -p jbds -i com.jboss.devstudio.core.package,org.testng.eclipse.feature.group,org.eclipse.wst.jsdt.feature.patch.feature.group -profileProperties org.eclipse.update.install.features=true > !ENTRY org.eclipse.equinox.p2.engine 4 4 2016-02-16 16:27:12.468 > !MESSAGE An error occurred while installing the items > !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2016-02-16 16:27:12.468 > !MESSAGE session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.rse.subsystems.shells.telnet 1.2.300.201403100950, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). > !SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2016-02-16 16:27:12.468 > !MESSAGE The artifact file for osgi.bundle,org.eclipse.rse.subsystems.shells.telnet,1.2.300.201403100950 was not found. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3730) Headless standalone installer can be run with xml config that contains eap bundle

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3730?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3730: -------------------------------- Fix Version/s: 10.4.0.AM2 (was: 10.4.0.AM1) > Headless standalone installer can be run with xml config that contains eap bundle > --------------------------------------------------------------------------------- > > Key: JBDS-3730 > URL: https://issues.jboss.org/browse/JBDS-3730 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.4.0.AM2 > > > One can run the headless standalone installer with a config xml file which contains the instructions to install eap as well. This results in the following: > {noformat}[ Starting automated installation ] > [INFO] Selected JVM Information > [INFO] Location : /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.72-1.b15.fc22.x86_64 > [INFO] Vendor : Oracle Corporation > [INFO] Version : 1.8.0_72 > [INFO] Arch : 64-bit > [ Starting to unpack ] > [ Processing package: P2 Director Application (1/4) ] > [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 (2/4) ] > [ Processing package: Red Hat JBoss Developer Studio 9.1.0.CR1 Metadata Generation (3/4) ] > [ Processing package: JBoss Enterprise Application Platform (4/4) ] > [ WARNING: Error executing > /bin/chmod a+x /home/jrichter/Downloads/temp/runtimes/jboss-eap/bin/init.d/jboss-as-standalone.sh ] > [ ERROR: The installation was not completed ] > [ Unpacking finished ] > com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) > com.izforge.izpack.installer.InstallerException: Unpack failed (xml line 19) > at com.izforge.izpack.panels.InstallPanelAutomationHelper.runAutomated(Unknown Source) > 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! ]{noformat} > The resulting installation is still perfectly functional, but no icons/shortcuts are created. It might be nicer if the installer was able to identify if it can install all the bundles in the config file and at least warn when starting up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2355) JEE web project example generates warnings

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2355?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2355: -------------------------------- Fix Version/s: 10.4.0.AM2 (was: 10.4.0.AM1) > JEE web project example generates warnings > ------------------------------------------ > > Key: JBDS-2355 > URL: https://issues.jboss.org/browse/JBDS-2355 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 6.0.0.Alpha2 > Environment: Version: 6.0.0.Alpha2 > Build id: Alpha2-v20121004-2330-B40 > Build date: 20121004-2330 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Labels: examplewarnings > Fix For: 10.4.0.AM2 > > > The JEE web project example generates these warnings: > The import java.util.logging.Logger is never used > MemberController.java > /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller > line 3 > No connection specified for project. No database-specific validation will be performed. > jboss-javaee6-webapp > Unnecessary @SuppressWarnings("unused") Resources.java > /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/util > line 26 > The import javax.persistence.EntityManager is never used > MemberController.java > /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller > line 14 > The import javax.enterprise.event.Event is never used > MemberController.java > /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller > line 7 > The import javax.ejb.Stateful is never used > MemberController.java > /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller > line 6 > The import org.jboss.tools.examples.controller.MemberController is never used > MemberRegistrationTest.java > /jboss-javaee6-webapp/src/test/java/org/jboss/tools/examples/test -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4105: -------------------------------- Fix Version/s: 10.4.0.AM2 (was: 10.4.0.AM1) > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: 10.4.0.AM2 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24114) [parent pom] do not skip baseline comparison check when -DskipTests=true

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24114?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24114: ------------------------------------ I'll let this stew for a few days so more people can see my post and react. > [parent pom] do not skip baseline comparison check when -DskipTests=true > ------------------------------------------------------------------------ > > Key: JBIDE-24114 > URL: https://issues.jboss.org/browse/JBIDE-24114 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.4.AM1, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > Currently, when you build with -DskipTests, the baseline checks are also skipped. This means that if you make a change to a file in a plugin, and build it locally to see if anything breaks, but forget to bump the version of the plugin and its containing feature, you won't see the baseline check failure until it's built in Jenkins and someone like me complains about it to you directly. > This happened recently in the 4.4.x branch for changes to openshift and base. > So I propose this change in parent pom for 4.4.x and master branches: > {code} > - <skipBaselineComparison>${skipTestsOrITests}</skipBaselineComparison> > + <skipBaselineComparison>false</skipBaselineComparison> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23494) Tests: Should provide unit-tests for WatchManager

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23494?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23494: ------------------------------------- Labels: test (was: ) > Tests: Should provide unit-tests for WatchManager > ------------------------------------------------- > > Key: JBIDE-23494 > URL: https://issues.jboss.org/browse/JBIDE-23494 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: test > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > WatchManager proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23494) Tests: Should provide unit-tests for WatchManager

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23494?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23494: ------------------------------------- Fix Version/s: 4.4.4.AM2 > Tests: Should provide unit-tests for WatchManager > ------------------------------------------------- > > Key: JBIDE-23494 > URL: https://issues.jboss.org/browse/JBIDE-23494 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Critical > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > WatchManager proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it. I'll jira -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23494) Tests: Should provide unit-tests for WatchManager

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23494?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23494: ------------------------------------- Description: WatchManager proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it. (was: WatchManager proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it. I'll jira) > Tests: Should provide unit-tests for WatchManager > ------------------------------------------------- > > Key: JBIDE-23494 > URL: https://issues.jboss.org/browse/JBIDE-23494 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Critical > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > WatchManager proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23494) Tests: Should provide unit-tests for WatchManager

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23494?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23494: ------------------------------------------ merged to master and cherry-picked into jbosstools-4.4.x > Tests: Should provide unit-tests for WatchManager > ------------------------------------------------- > > Key: JBIDE-23494 > URL: https://issues.jboss.org/browse/JBIDE-23494 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Critical > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > WatchManager proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it. I'll jira -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 March 2017