February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16617) New Hybrid Mobile dialog shows error before anything is entered

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16617?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-16617: ---------------------------------- Attachment: hybrid-dialog-1.png hybrid-dialog-2.png > New Hybrid Mobile dialog shows error before anything is entered > --------------------------------------------------------------- > > Key: JBIDE-16617 > URL: https://issues.jboss.org/browse/JBIDE-16617 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Alpha2 > Environment: JBDS 8.0.0.Alpha2b B71 > Reporter: Martin Malina > Fix For: 4.2.0.Beta1 > > Attachments: hybrid-dialog-1.png, hybrid-dialog-2.png > > > When you create a new hybrid mobile project (File -> New -> Hybrid Mobile...), on the first page of the dialog, you're shown an error at the top even though you haven't done anything yet. > This is ugly and violates http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards Guideline 5.3. > Also, consider polishing the next page, too. If I don't have an engine installed, I get the error Please select a Hybrid Mobile Engine. This is not very nice, but I'm not sure how to improve it - perhaps if there are no engines installed, have a different message? And if you have at least one engine, select the first one by default, so that we avoid unnecessary errors? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16617) New Hybrid Mobile dialog shows error before anything is entered

by Martin Malina (JIRA)

Martin Malina created JBIDE-16617: ------------------------------------- Summary: New Hybrid Mobile dialog shows error before anything is entered Key: JBIDE-16617 URL: https://issues.jboss.org/browse/JBIDE-16617 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.2.0.Alpha2 Environment: JBDS 8.0.0.Alpha2b B71 Reporter: Martin Malina Fix For: 4.2.0.Beta1 Attachments: hybrid-dialog-1.png, hybrid-dialog-2.png When you create a new hybrid mobile project (File -> New -> Hybrid Mobile...), on the first page of the dialog, you're shown an error at the top even though you haven't done anything yet. This is ugly and violates http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards Guideline 5.3. Also, consider polishing the next page, too. If I don't have an engine installed, I get the error Please select a Hybrid Mobile Engine. This is not very nice, but I'm not sure how to improve it - perhaps if there are no engines installed, have a different message? And if you have at least one engine, select the first one by default, so that we avoid unnecessary errors? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15601) Implement ANSI commands for Aesh integration

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15601?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-15601. ------------------------------ > Implement ANSI commands for Aesh integration > -------------------------------------------- > > Key: JBIDE-15601 > URL: https://issues.jboss.org/browse/JBIDE-15601 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.2.0.Alpha2 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16616) New Maven Project dialog, "Finish" in no more enabled after archetypes are retrieved

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-16616: --------------------------------------- Summary: New Maven Project dialog, "Finish" in no more enabled after archetypes are retrieved Key: JBIDE-16616 URL: https://issues.jboss.org/browse/JBIDE-16616 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.2.0.Alpha2 Reporter: Radoslav Rábara Fix For: 4.2.0.Beta1 When you are on the last page of dialog New Maven Project and the job "Retrieving archetypes:" is still running then the button Finish will be enabled only until the job is running. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16616) New Maven Project dialog, "Finish" in no more enabled after archetypes are retrieved

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16616?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-16616: ------------------------------------ Description: When you are on the last page of dialog New Maven Project and the job "Retrieving archetypes:" is still running then the button Finish will be enabled only until the job is running. This bug is reproducible only once after the dialog New Maven Project is opened. When you want to reproduce it more times in the single instance of JBDS than you need to restart the JBDS. was:When you are on the last page of dialog New Maven Project and the job "Retrieving archetypes:" is still running then the button Finish will be enabled only until the job is running. > New Maven Project dialog, "Finish" in no more enabled after archetypes are retrieved > ------------------------------------------------------------------------------------ > > Key: JBIDE-16616 > URL: https://issues.jboss.org/browse/JBIDE-16616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.2.0.Alpha2 > Reporter: Radoslav Rábara > Fix For: 4.2.0.Beta1 > > > When you are on the last page of dialog New Maven Project and the job "Retrieving archetypes:" is still running then the button Finish will be enabled only until the job is running. > This bug is reproducible only once after the dialog New Maven Project is opened. When you want to reproduce it more times in the single instance of JBDS than you need to restart the JBDS. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16302) Make jobs suffix = stream (eg 4.2.luna instead of 42)

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16302?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-16302. ------------------------------ > Make jobs suffix = stream (eg 4.2.luna instead of 42) > ----------------------------------------------------- > > Key: JBIDE-16302 > URL: https://issues.jboss.org/browse/JBIDE-16302 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > In order to reduce the amount of conventions and allow better factorization, we should get rid of the current convention (jobname_42) on job/nightly-build/staging names and replace it by the same convention as _composite_ and aggregate site (4.2.luna). > For example: > * jbosstools-central_42 => jbosstools-central_4.2.luna > * as a consequence download.jboss.org/jbosstools/builds/staging/jbosstools-central_42/ => download.jboss.org/jbosstools/builds/staging/jbosstools-central_4.2.luna/ > And > * devstudio.product_80 => devstudio.product_8.0.luna -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16543) Missing requirement Google Eclipse 4.2 Platform Plugin when installing from central

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16543?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-16543. ------------------------------ Verified in JBT 4.2.0.Alpha2b build. > Missing requirement Google Eclipse 4.2 Platform Plugin when installing from central > ------------------------------------------------------------------------------------ > > Key: JBIDE-16543 > URL: https://issues.jboss.org/browse/JBIDE-16543 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.2.0.Alpha2 > Reporter: Pavol Srna > Assignee: Nick Boldt > Labels: respin-a > Fix For: 4.2.0.Alpha2 > > Attachments: com.goog-installed.png, JBDE16543-nightly-fixed.png, JBIDE16543-remediation-option.png, maven.gwt-in-central.png, maven.gwt-installed.png, screen-missing-dep-central.png > > > Cannot complete the install because one or more required items could not be found. > Software being installed: Google Plugin for Eclipse 4.3 3.4.2.v201310081834-rel-r43 (com.google.gdt.eclipse.suite.e43.feature.feature.group 3.4.2.v201310081834-rel-r43) > Missing requirement: Google Eclipse 4.2 Platform Plugin 3.4.2.v201310081834-rel-r43 (com.google.gdt.eclipse.platform.e42 3.4.2.v201310081834-rel-r43) requires 'bundle org.eclipse.core.runtime [3.8.0,3.10.0)' but it could not be found > Cannot satisfy dependency: > From: Google Plugin for Eclipse 4.3 3.4.2.v201310081834-rel-r43 (com.google.gdt.eclipse.suite.e43.feature.feature.group 3.4.2.v201310081834-rel-r43) > To: com.google.gdt.eclipse.platform.e42 [3.4.2.v201310081834-rel-r43] -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2918) No repository found for JBDS 8 development

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-2918?page=com.atlassian.jira.plugin.... ] Pavol Srna closed JBDS-2918. ---------------------------- Empty repository site exists and no more errors are seen. Closing. > No repository found for JBDS 8 development > ------------------------------------------ > > Key: JBDS-2918 > URL: https://issues.jboss.org/browse/JBDS-2918 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 8.0.0.Alpha2 > Reporter: Martin Malina > Assignee: Mickael Istria > Fix For: 8.0.0.Alpha2 > > > JBDS gives me this error: > No repository found at https://devstudio.jboss.com/updates/8.0-development/ > {quote} > [mmalina] mistria: is this expacted because we haven't pushed any JBDS 8 bits to be public yet, or is this a bug? > [maxandersen] mmalina: its kinda expected for now yes. we could/should put an empty site there imo though. open a bug for that. > {quote} > So can we create an empty repo for now? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Pavol Srna closed JBDS-2669. ---------------------------- Verified in JBDs 8.0.0.Alpha2b build. > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > Attachments: build1667.png, update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2880) com.jboss.jbds.product.EclipseGenerator application failure in installer

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-2880?page=com.atlassian.jira.plugin.... ] Pavol Srna closed JBDS-2880. ---------------------------- > com.jboss.jbds.product.EclipseGenerator application failure in installer > ------------------------------------------------------------------------ > > Key: JBDS-2880 > URL: https://issues.jboss.org/browse/JBDS-2880 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 8.0.0.Alpha2 > > > {code}!SESSION 2014-01-16 16:34:55.784 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.7.0_51 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -application com.jboss.jbds.product.EclipseGenerator > Command-line arguments: -application com.jboss.jbds.product.EclipseGenerator -clean > !ENTRY org.eclipse.osgi 4 0 2014-01-16 16:34:57.716 > !MESSAGE Application error > !STACK 1 > java.lang.RuntimeException: Application "com.jboss.jbds.product.EclipseGenerator" could not be found in the registry. The applications available are: com.jboss.jbds.p2.director, org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.garbagecollector.application, org.eclipse.equinox.p2.publisher.InstallPublisher, org.eclipse.equinox.p2.publisher.EclipseGenerator, org.eclipse.equinox.p2.publisher.ProductPublisher, org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher, org.eclipse.equinox.p2.repository.repo2runnable, org.eclipse.equinox.p2.repository.metadataverifier, org.eclipse.equinox.p2.artifact.repository.mirrorApplication, org.eclipse.equinox.p2.metadata.repository.mirrorApplication. > at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:248) > at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > 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:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426){code} > Installer could not run this application becasue it is trying to start it inside p2 director, just installed product should be used instead. -- 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, 2 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 February 2014