September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15160) support comparing bundle folders as well as bundle jars when comparing MD5 sums

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15160?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15160: ------------------------------------ While you're applying PRs, this trivial update needs some love too: https://github.com/jbdevstudio/jbdevstudio-qa/pull/5 > support comparing bundle folders as well as bundle jars when comparing MD5 sums > ------------------------------------------------------------------------------- > > Key: JBIDE-15160 > URL: https://issues.jboss.org/browse/JBIDE-15160 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Affects Versions: 4.1.0.CR1 > Reporter: Nick Boldt > Assignee: Pavol Srna > Priority: Critical > Fix For: 4.1.1.Alpha2 > > > Currently, versionwatch can only compare md5s for jars. Adding support for zipping folders to jars and then comparing those should be fairly simple to add. > We could also compare MD5s for plugins' manifest.mf files as well as the jars themselves. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2741) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2741: ---------------------------------- * https://raw.github.com/jbosstools/jbosstools-build-ci/master/util/cleanup... (see clean() and regenCompositeMetadata() methods) * https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub... and https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pro... will need to be fine-tuned too. > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2741 > URL: https://issues.jboss.org/browse/JBDS-2741 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15437) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15437?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-15437. ------------------------------ Assignee: Nick Boldt Resolution: Done With subtasks done, this is done too. > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch > -------------------------------------------- > > Key: JBIDE-15437 > URL: https://issues.jboss.org/browse/JBIDE-15437 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; > 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; > 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; > 4. Close (not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-2755 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15460) bumping plugin version with tycho 0.18.1 fails with NPE

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15460?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-15460. ------------------------------------ nothing for QE to verify, thus closing > bumping plugin version with tycho 0.18.1 fails with NPE > ------------------------------------------------------- > > Key: JBIDE-15460 > URL: https://issues.jboss.org/browse/JBIDE-15460 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > > Try to bump the version of the plugins: > {code} > mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=2.5.1-SNAPSHOT > {code} > it ends in tycho failing with an NPE: > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version (default-cli) on project openshift: Execution default-cli of goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version failed. NullPointerException -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version (default-cli) on project openshift: Execution default-cli of goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version failed. > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal org.eclipse.tycho:tycho-versions-plugin:0.18.1:set-version failed. > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > Caused by: java.lang.NullPointerException > at org.eclipse.tycho.versions.pom.GAV.getGroupId(GAV.java:23) > at org.eclipse.tycho.versions.manipulation.PomManipulator.isGavEquals(PomManipulator.java:154) > at org.eclipse.tycho.versions.manipulation.PomManipulator.changePlugins(PomManipulator.java:129) > at org.eclipse.tycho.versions.manipulation.PomManipulator.changeBuild(PomManipulator.java:117) > at org.eclipse.tycho.versions.manipulation.PomManipulator.applyChange(PomManipulator.java:83) > at org.eclipse.tycho.versions.engine.VersionsEngine.applyChange(VersionsEngine.java:165) > at org.eclipse.tycho.versions.engine.VersionsEngine.apply(VersionsEngine.java:142) > at org.eclipse.tycho.versions.SetMojo.execute(SetMojo.java:78) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > ... 20 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15462) bump openshift plugins to 2.6.0

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15462?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15462: ------------------------------------------ pushed upstream > bump openshift plugins to 2.6.0 > ------------------------------- > > Key: JBIDE-15462 > URL: https://issues.jboss.org/browse/JBIDE-15462 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > > We have to bump the plugins from 2.5.0 -> 2.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2663) Installer cannot find unpack200.exe due to spaces in JDK path on Windows 8

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2663?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2663: -------------------------------------- Fix Version/s: 7.1.0.Alpha2 (was: 7.1.0.Alpha1) > Installer cannot find unpack200.exe due to spaces in JDK path on Windows 8 > -------------------------------------------------------------------------- > > Key: JBDS-2663 > URL: https://issues.jboss.org/browse/JBDS-2663 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, upstream > Affects Versions: 7.0.0.Beta2 > Environment: Windows 8, Oracle JRE 1.6 x86_64/x86 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 7.1.0.Alpha2 > > > {code}C:\Users\alena\Downloads>java -jar jbdevstudio-product-universal-7.0.0.Beta2-B26 > 1.jar > java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The > system cannot find the file specified > at java.lang.ProcessBuilder.start(Unknown Source) > at java.lang.Runtime.exec(Unknown Source) > at java.lang.Runtime.exec(Unknown Source) > at java.lang.Runtime.exec(Unknown Source) > at com.izforge.izpack.util.LibraryRemover.initJavaExec(Unknown Source) > at com.izforge.izpack.util.LibraryRemover.<init>(Unknown Source) > at com.izforge.izpack.util.LibraryRemover.invoke(Unknown Source) > at com.izforge.izpack.util.Librarian.cleanUp(Unknown Source) > at com.izforge.izpack.util.Housekeeper.shutDown(Unknown Source) > at com.izforge.izpack.installer.InstallerFrame.exit(InstallerFrame.java: > 1161) > at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP > erformed(InstallerFrame.java:1562) > at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) > at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) > at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) > at javax.swing.DefaultButtonModel.setPressed(Unknown Source) > at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour > ce) > at java.awt.Component.processMouseEvent(Unknown Source) > at javax.swing.JComponent.processMouseEvent(Unknown Source) > at java.awt.Component.processEvent(Unknown Source) > at java.awt.Container.processEvent(Unknown Source) > at java.awt.Component.dispatchEventImpl(Unknown Source) > at java.awt.Container.dispatchEventImpl(Unknown Source) > at java.awt.Component.dispatchEvent(Unknown Source) > at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) > at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) > at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) > at java.awt.Container.dispatchEventImpl(Unknown Source) > at java.awt.Window.dispatchEventImpl(Unknown Source) > at java.awt.Component.dispatchEvent(Unknown Source) > at java.awt.EventQueue.dispatchEventImpl(Unknown Source) > at java.awt.EventQueue.access$400(Unknown Source) > at java.awt.EventQueue$2.run(Unknown Source) > at java.awt.EventQueue$2.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown > Source) > at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown > Source) > at java.awt.EventQueue$3.run(Unknown Source) > at java.awt.EventQueue$3.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown > Source) > at java.awt.EventQueue.dispatchEvent(Unknown Source) > at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) > at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) > at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) > at java.awt.EventDispatchThread.pumpEvents(Unknown Source) > at java.awt.EventDispatchThread.pumpEvents(Unknown Source) > at java.awt.EventDispatchThread.run(Unknown Source) > Caused by: java.io.IOException: CreateProcess error=2, The system cannot find th > e file specified > at java.lang.ProcessImpl.create(Native Method) > at java.lang.ProcessImpl.<init>(Unknown Source) > at java.lang.ProcessImpl.start(Unknown Source) > ... 47 more{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2716) NoClassDefFoundError: javax/servlet/http/HttpServletRequest after importing getting-started WFK Spring example

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2716?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2716: -------------------------------------- Fix Version/s: 7.1.0.Alpha2 (was: 7.1.0.Alpha1) > NoClassDefFoundError: javax/servlet/http/HttpServletRequest after importing getting-started WFK Spring example > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2716 > URL: https://issues.jboss.org/browse/JBDS-2716 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-dependencies > Affects Versions: 7.0.0.GA > Environment: JBDS 7.0.0.GA, L64 > Reporter: Jiri Peterka > Fix For: 7.1.0.Alpha2 > > Attachments: spring-internal-error.png > > > IDE reports error after importing getting-started spring wfk 2.3 demo project. Expecting this error is more general, not only this project specific. > {code} > java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) > at java.lang.Class.getDeclaredMethods(Class.java:1793) > at org.springframework.core.type.StandardAnnotationMetadata.hasAnnotatedMethods(StandardAnnotationMetadata.java:130) > at org.springframework.context.annotation.ConfigurationClassUtils.isLiteConfigurationCandidate(ConfigurationClassUtils.java:109) > at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:87) > at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:259) > at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:86) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:749) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:742) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcess(BeansConfig.java:626) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.access$8(BeansConfig.java:585) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:451) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:1) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:247) > ... 23 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2457) Mirror stable content on Akamai

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2457?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2457: ---------------------------------- Not yet. Waiting for [~jpallich] to talk to [~dfj] to confirm this is allowed. > Mirror stable content on Akamai > ------------------------------- > > Key: JBDS-2457 > URL: https://issues.jboss.org/browse/JBDS-2457 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Mickael Istria > Assignee: Mickael Istria > > In order to improve installation time (for both end-users and internal build/test usage), we should use Akamai on the stable folders if devstudio downloas site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2741) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2741: ----------------------------- CDW devel_ack: ? CDW pm_ack: + (was: ?) CDW qa_ack: ? > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2741 > URL: https://issues.jboss.org/browse/JBDS-2741 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2712) Typo in installer: Ok > OK

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2712?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2712: -------------------------------------- Fix Version/s: 7.1.0.Alpha2 (was: 7.1.0.Alpha1) > Typo in installer: Ok > OK > -------------------------- > > Key: JBDS-2712 > URL: https://issues.jboss.org/browse/JBDS-2712 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Michelle Murray > Assignee: Denis Golovin > Fix For: 7.1.0.Alpha2 > > Attachments: Installer_Ok1.png, Installer_Ok2.png > > > In step 5 of the installer (Select Platforms and Servers), two child windows have 'Ok', which should be 'OK'. > 1. At step 5, click Add. > 2. Click Browse. > 3. Select location and click *Ok*. > 4. Click *Ok* to close the Add Location window. > Screen captures attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 2013