[JBoss JIRA] (JBIDE-18535) Opening of wizards from forge cheatsheet does not result in "attached cheatsheet"
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18535?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-18535:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Opening of wizards from forge cheatsheet does not result in "attached cheatsheet"
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-18535
> URL: https://issues.jboss.org/browse/JBIDE-18535
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge, project-examples
> Reporter: Max Rydahl Andersen
> Assignee: Koen Aers
> Fix For: 4.5.x
>
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> I'm not sure what is the cause of this but I just noticed that when I launch a forge wizard from the forge cheat sheets the cheat sheet is "stuck" in the overall perspective.
> But when I open a wizard in the Java Development/Create a Hello World Application the cheatsheet behaves as expected and is attached to the wizard (see screenshot)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22910) NullPointerException in JSFProjectsTree.getProjectsRoot
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22910?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22910:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> NullPointerException in JSFProjectsTree.getProjectsRoot
> -------------------------------------------------------
>
> Key: JBIDE-22910
> URL: https://issues.jboss.org/browse/JBIDE-22910
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.5.x
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.jsf.model.pv.JSFProjectsTree.getProjectsRoot(JSFProjectsTree.java:45)
> at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldHelper.getBeanList(JSFRenameFieldHelper.java:48)
> at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:68)
> at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:310)
> at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper$Operation.run(RefactoringExecutionHelper.java:97)
> at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:729)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5409)
> at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:106)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {noformat}
> Bundles:
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 |
> | org.eclipse.jdt.core | 3.11.0.xx-201604081629-e45 | 3.12.0.v20160516-2131 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.12.0.v20160525-1829 |
> | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
> | org.eclipse.ltk.core.refactoring | 3.6.201.v20150819-1034 | 3.7.0.v20160419-0705 |
> | org.eclipse.ltk.ui.refactoring | 3.7.200.v20140625-1835 | 3.7.200.v20140625-1835 |
> | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.0.Final-v20160610-0126-B1 |
> Operating Systems:
> | Linux | 3.10.0.14 | 4.5.7.fc24 |
> | MacOSX | 10.11.4 | 10.11.6 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571a3a3fe4b0e9dd9c...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22694) Environment Var Wizard: Improve deletion of environment variables
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22694?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22694:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Environment Var Wizard: Improve deletion of environment variables
> -----------------------------------------------------------------
>
> Key: JBIDE-22694
> URL: https://issues.jboss.org/browse/JBIDE-22694
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Marián Labuda
> Labels: env_var_wizard, openshift_v3
> Fix For: 4.5.x
>
>
> Deletion of environment variable does not match user expectation. If I delete an environment variable which has been added in earlier opened and closed Env. Var wizard, this variable has prefix [deleted]. I don't think this is good practice, we should be consistent across all wizards and dialog, so once user select an env var in table and push Delete button, value should be removed from the table. No labelling should be done here, the table should reflect real current state of environment variable (what it is gonna look like once I hit Finish button).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-16996) Text "cordova.default" cannot be used as application id
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16996?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-16996:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Text "cordova.default" cannot be used as application id
> -------------------------------------------------------
>
> Key: JBIDE-16996
> URL: https://issues.jboss.org/browse/JBIDE-16996
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1-v20140402-0037-B82
> Reporter: Vlado Pakan
> Priority: Minor
> Fix For: 4.5.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> 1. Create Hybrid Mobile project with ID="cordova.default"
> 2. Export project as Native Mobile Project for android
> ERROR:
> {noformat}
> [javac] /home/vpakan/jbdevstudio800Beta1a/studio/configuration/org.eclipse.osgi/947/data/proj_gen/cordova-def/android/src/cordova/default/cordova_def.java:20: error: <identifier> expected
> [javac] package cordova.default;
> {noformat}
> 3. Run Project on Android Device/Simulator
> ERROR: the same as above
> I don't know if it's bug or some restriction for application name. If it's just restriction we should not allow user to specify such a ID or at least display warning that user is using wrong ID and will not be able to export/run project with this ID.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-16582) Cordova Engine deleting from file system is not handled properly
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16582?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-16582:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Cordova Engine deleting from file system is not handled properly
> ----------------------------------------------------------------
>
> Key: JBIDE-16582
> URL: https://issues.jboss.org/browse/JBIDE-16582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Alpha2
> Environment: JBT 4.2.0.Alpha2-v20140212-1651-B82
> Reporter: Vlado Pakan
> Priority: Minor
> Fix For: 4.5.x
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> 1. Create Hybrid Mobile project and download at least 2 Cordova engines.
> 2. Delete one downloaded engine from <user_home>/.cordova/...
> 3. Open Project properties and try to change Cordova Engine for project
> ERROR: Library for the Active Hybrid Mobile Engine for Android is incomplete. No framework directory is present.
> This error is displayed even when deleted Cordova engine is not selected.
> Only currently available engines should be displayed in Preferences dialog.
> The same error occurs when trying to create another Hybrid Mobile project.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-13003) No support for inheritance in JAX-RS API scan
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13003?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-13003:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> No support for inheritance in JAX-RS API scan
> ---------------------------------------------
>
> Key: JBIDE-13003
> URL: https://issues.jboss.org/browse/JBIDE-13003
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.0.0.Alpha1, 4.0.0.Alpha2
> Reporter: Ron Ratovsky
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.5.x
>
>
> Assume:
> class BaseRest {
> @POST
> public Response save(Object o) {
> ....
> }
> }
> @Path("/url")
> class RealRest extends BaseRest {}
> The JAX-RS tools won't add a "POST /url" entry to the JAX-RS calls overview.
> While not tested (due to another bug) - they may also apply to definitions of @PathParam's in the parent class.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-11259) BrowserSim: broken layout on Linux
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11259?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-11259:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> BrowserSim: broken layout on Linux
> ----------------------------------
>
> Key: JBIDE-11259
> URL: https://issues.jboss.org/browse/JBIDE-11259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 3.3.0.Beta1
> Reporter: Yahor Radtsevich
> Assignee: Ilya Buziuk
> Fix For: 4.5.x
>
> Attachments: BrowserSim_BrokenRender.png, screenshot-1.png
>
>
> *Steps to reproduce:*
> # Run BrowserSim on Linux (I used Ubuntu Linux 11.10 x86_64)
> # Check 'Use Skins' if it is not checked.
> # Select 'Samsung Galaxy Tab 10.1' skin
> # Click 'Turn Left' several times.
> *Actual result:*
> From time to time the layout of the window is broken:
> !screenshot-1.png|thumbnail!
> *Update:*
> Video created by [~rhopp]: http://youtu.be/HKN7hnLQOz8
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-22384) Application Wizard: Skip revalidating of a connection if it is already established
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22384?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22384:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Application Wizard: Skip revalidating of a connection if it is already established
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-22384
> URL: https://issues.jboss.org/browse/JBIDE-22384
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Labels: application_wizard, openshift_v3
> Fix For: 4.5.x
>
>
> When launching a New OpenShift Application wizard via shell menu File - New - OpenShift Application or via Red Hat Central, at first I am obliged to select an existing connection (or create a new one) and then proceed to New OpenShift Application wizard. At the moment, if I select an existing, already established connection (it is possible to work with it in OpenShift Explorer view, password/token has been filled in and is valid), it is still revalidated, what take some time (not too much but seems to be annoying for me every time opening the wizard). Also the connection is every time refreshed in OpenShift Explorer view once revalidation is finished. It would be nice if already established connections would not be revalidated again.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months