July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17849) CSS Hyperlinks aren't working on non-WTP projects

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17849?page=com.atlassian.jira.plugi... ] Victor Rubezhny reassigned JBIDE-17849: --------------------------------------- Assignee: Victor Rubezhny > CSS Hyperlinks aren't working on non-WTP projects > ------------------------------------------------- > > Key: JBIDE-17849 > URL: https://issues.jboss.org/browse/JBIDE-17849 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta3 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.2.0.CR1 > > > CSS Hyperlinks aren't working for the project that are not the WTP ones (when a project has no Module Core Nature ("org.eclipse.wst.common.modulecore.ModuleCoreNature")). > For such projects we cannot find according CSS file. This is a limitation in o.j.t.jst.web.kb.PageContextFactory.getFileFromProject(String, IFile). > See JBIDE-17676 on how to get an example of non-working Hyperlinks on CSS classes -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17716) An error "TypeParameter cannot be cast to IType" occurs when quick fix is used

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17716?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-17716: --------------------------------------- No need to export huge project. It can be replicated on posted steps to reproduce, but test class should be template: {code} package jaxrs; import java.util.ArrayList; import java.util.List; import javax.ejb.Stateless; import javax.ws.rs.GET; import javax.ws.rs.Path; import javax.ws.rs.Produces; import javax.ws.rs.core.MediaType; @Stateless @Path("/path") public class Converter<T> { @GET @Produces(MediaType.APPLICATION_JSON) public List<T> getConverter() { return new ArrayList<T>(); } } {code} Example above throws the same exception. problem is in <T> processing, it fails because it cannot be converted to actual type. > An error "TypeParameter cannot be cast to IType" occurs when quick fix is used > ------------------------------------------------------------------------------ > > Key: JBIDE-17716 > URL: https://issues.jboss.org/browse/JBIDE-17716 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Radoslav Rábara > Labels: respin-a > Fix For: 4.2.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17849) CSS Hyperlinks aren't working on non-WTP projects

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17849?page=com.atlassian.jira.plugi... ] Victor Rubezhny updated JBIDE-17849: ------------------------------------ Description: CSS Hyperlinks aren't working for the project that are not the WTP ones (when a project has no Module Core Nature ("org.eclipse.wst.common.modulecore.ModuleCoreNature")). For such projects we cannot find according CSS file. This is a limitation in o.j.t.jst.web.kb.PageContextFactory.getFileFromProject(String, IFile). See JBIDE-17676 on how to get an example of non-working Hyperlinks on CSS classes was: CSS Hyperlinks aren't working for the project that are not the WTP ones (when a project has no Module Core Nature ("org.eclipse.wst.common.modulecore.ModuleCoreNature")). For such projects we cannot find according CSS file. This is a limitation in o.j.t.jst.web.kb.PageContextFactory.getFileFromProject(String, IFile). > CSS Hyperlinks aren't working on non-WTP projects > ------------------------------------------------- > > Key: JBIDE-17849 > URL: https://issues.jboss.org/browse/JBIDE-17849 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta3 > Reporter: Victor Rubezhny > Fix For: 4.2.0.CR1 > > > CSS Hyperlinks aren't working for the project that are not the WTP ones (when a project has no Module Core Nature ("org.eclipse.wst.common.modulecore.ModuleCoreNature")). > For such projects we cannot find according CSS file. This is a limitation in o.j.t.jst.web.kb.PageContextFactory.getFileFromProject(String, IFile). > See JBIDE-17676 on how to get an example of non-working Hyperlinks on CSS classes -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17849) CSS Hyperlinks aren't working on non-WTP projects

by Victor Rubezhny (JIRA)

Victor Rubezhny created JBIDE-17849: --------------------------------------- Summary: CSS Hyperlinks aren't working on non-WTP projects Key: JBIDE-17849 URL: https://issues.jboss.org/browse/JBIDE-17849 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Affects Versions: 4.2.0.Beta3 Reporter: Victor Rubezhny CSS Hyperlinks aren't working for the project that are not the WTP ones (when a project has no Module Core Nature ("org.eclipse.wst.common.modulecore.ModuleCoreNature")). For such projects we cannot find according CSS file. This is a limitation in o.j.t.jst.web.kb.PageContextFactory.getFileFromProject(String, IFile). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17849) CSS Hyperlinks aren't working on non-WTP projects

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17849?page=com.atlassian.jira.plugi... ] Victor Rubezhny updated JBIDE-17849: ------------------------------------ Fix Version/s: 4.2.0.CR1 > CSS Hyperlinks aren't working on non-WTP projects > ------------------------------------------------- > > Key: JBIDE-17849 > URL: https://issues.jboss.org/browse/JBIDE-17849 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta3 > Reporter: Victor Rubezhny > Fix For: 4.2.0.CR1 > > > CSS Hyperlinks aren't working for the project that are not the WTP ones (when a project has no Module Core Nature ("org.eclipse.wst.common.modulecore.ModuleCoreNature")). > For such projects we cannot find according CSS file. This is a limitation in o.j.t.jst.web.kb.PageContextFactory.getFileFromProject(String, IFile). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17847) Bad UI workflow when changing the profile of a server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17847?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17847: ------------------------------------- I'm aware of the dialog (wtp does that automatically when it notices a server has saved). Apparently what's happening is I try to save the changes to the server, and then close the editor and re-open it. WTP is somehow noticing the change before I have a chance to close the editor, and is throwing up the dialog. To note, I am not able to replicate it, but I can understand how it's happening. Not quite sure how to fix it though. I suppose I can have my performFinish fire a job to save, then close the editor. At least then the dialog won't be hidden if it manages to come up. > Bad UI workflow when changing the profile of a server > ----------------------------------------------------- > > Key: JBIDE-17847 > URL: https://issues.jboss.org/browse/JBIDE-17847 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta3 B172 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.2.0.Beta3 > > > When I try to change the profile of a server (e.g. WildFly) between file operations and management, I get stuck in the dialog and nothing happens. It turns out that there is a pop up asking me if I want to reload the server editor, but it opens behind this other dialog, so I don't know it's there. > Shouldn't the profile dialog close when you click Finish? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17831) Application wizard: dirty project should not be selectable as existing project (validate before starting to merge openshift app into existing proj and fail)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17831?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17831: ------------------------------------- Summary: Application wizard: dirty project should not be selectable as existing project (validate before starting to merge openshift app into existing proj and fail) (was: Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes) > Application wizard: dirty project should not be selectable as existing project (validate before starting to merge openshift app into existing proj and fail) > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-17831 > URL: https://issues.jboss.org/browse/JBIDE-17831 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Optional > Labels: application_wizard, respin-a > Fix For: 4.2.0.Beta3 > > Attachments: import-failed-uncommitted-changes.png, uncommitted-changes.png > > > EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) > EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). > EXEC: Choose basic cartridge and click Next button (ex. EAP 6). > EXEC: Fill in name on the next wizard page and click Next. > EXEC: Choose Use existing project and select the existing git based project. > EXEC: Finish the wizard. > *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge). > !import-failed-uncommitted-changes.png! > This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17848) Application wizard: dirty project should not be selectable as existing project (validate before starting to merge openshift app into existing proj and fail)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17848?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17848: ------------------------------------- Summary: Application wizard: dirty project should not be selectable as existing project (validate before starting to merge openshift app into existing proj and fail) (was: Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes) > Application wizard: dirty project should not be selectable as existing project (validate before starting to merge openshift app into existing proj and fail) > ------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-17848 > URL: https://issues.jboss.org/browse/JBIDE-17848 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Optional > Labels: application_wizard > Fix For: 4.2.0.CR1 > > Attachments: import-failed-uncommitted-changes.png, uncommitted-changes.png > > > EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) > EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). > EXEC: Choose basic cartridge and click Next button (ex. EAP 6). > EXEC: Fill in name on the next wizard page and click Next. > EXEC: Choose Use existing project and select the existing git based project. > EXEC: Finish the wizard. > *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge). > !import-failed-uncommitted-changes.png! > This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17848) Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17848?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-17848: ------------------------------------------ merged and pushed to upstream/master > Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-17848 > URL: https://issues.jboss.org/browse/JBIDE-17848 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Optional > Labels: application_wizard > Fix For: 4.2.0.CR1 > > Attachments: import-failed-uncommitted-changes.png, uncommitted-changes.png > > > EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) > EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). > EXEC: Choose basic cartridge and click Next button (ex. EAP 6). > EXEC: Fill in name on the next wizard page and click Next. > EXEC: Choose Use existing project and select the existing git based project. > EXEC: Finish the wizard. > *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge). > !import-failed-uncommitted-changes.png! > This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17848) Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17848?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-17848. -------------------------------------- Resolution: Done > Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-17848 > URL: https://issues.jboss.org/browse/JBIDE-17848 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Optional > Labels: application_wizard > Fix For: 4.2.0.CR1 > > Attachments: import-failed-uncommitted-changes.png, uncommitted-changes.png > > > EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git) > EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application). > EXEC: Choose basic cartridge and click Next button (ex. EAP 6). > EXEC: Fill in name on the next wizard page and click Next. > EXEC: Choose Use existing project and select the existing git based project. > EXEC: Finish the wizard. > *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge). > !import-failed-uncommitted-changes.png! > This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 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 July 2014