[JBoss JIRA] (JBIDE-18117) Unable to remove the JAX-RS facet on a Dynamic Web Project version 3.1
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18117?page=com.atlassian.jira.plugi... ]
Xavier Coulon resolved JBIDE-18117.
-----------------------------------
Resolution: Done
Marking this issue as resolved since the patch was committed (see comment from Sept. 11th) and Luna SR1 was released.
> Unable to remove the JAX-RS facet on a Dynamic Web Project version 3.1
> ----------------------------------------------------------------------
>
> Key: JBIDE-18117
> URL: https://issues.jboss.org/browse/JBIDE-18117
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream, webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.CR2
>
>
> A bug in Eclipse WTP causes the following exception:
> {code}
> java.lang.ClassCastException: org.eclipse.jst.javaee.web.internal.impl.WebAppImpl cannot be cast to org.eclipse.jst.j2ee.webapplication.WebApp
> at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSFacetUninstallDelegate.uninstallJAXRSReferencesFromWebApp(JAXRSFacetUninstallDelegate.java:116)
> at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSFacetUninstallDelegate.execute(JAXRSFacetUninstallDelegate.java:85)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$5.run(FacetedProject.java:1099)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1109)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:2020)
> at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$4.run(FacetsPropertyPage.java:232)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$5.run(FacetsPropertyPage.java:246)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> {code}
> the problem comes from an evaluation that checks for dynamic project facet version 2.5 or 3.0 but not higher, in {{JAXRSJEEUtils#isWebApp25or40(Object)}}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18383) forge command rely on english description label to lookup commands - fragile!
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18383?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18383:
-------------------------------------
+1 for using command ids. This will need a rebuild of the cheatsheet accordingly
> forge command rely on english description label to lookup commands - fragile!
> -----------------------------------------------------------------------------
>
> Key: JBIDE-18383
> URL: https://issues.jboss.org/browse/JBIDE-18383
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: Max Rydahl Andersen
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> it seems this is the way forge commands are looked up:
> org.jboss.tools.forge.ui.runForgeCommand(org.jboss.tools.forge.ui.runForgeCommand.commandName=REST: Generate Endpoints From Entities)"
> meaning if description changes the cheatsheet breaks.
> should this not us a unique id or at least the cli command name so we have *one* API to obey to ?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18409) OpenShift Adapter: Add choice to show application in external device/browser
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18409?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18409:
------------------------------------------
[~jpviragine] can you please explain what is "External Device"? I'm not aware of such an option in our server adapters, but I most likely miss that somehow.
> OpenShift Adapter: Add choice to show application in external device/browser
> ----------------------------------------------------------------------------
>
> Key: JBIDE-18409
> URL: https://issues.jboss.org/browse/JBIDE-18409
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Joao Viragine
> Assignee: Max Rydahl Andersen
> Labels: server_adapter
> Fix For: 4.3.x
>
>
> It would be nice if we had the option: Show In/Web Browser on External Device for OpenShift Server as we have for JBoss EAP Server. (Servers/(Application)/Show In/Add Web Browser on External Device)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-16225) Let the user select the version of the arquillian container adapter
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16225?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16225:
----------------------------------------
Fix Version/s: 4.2.1.Final
4.3.0.Alpha1
(was: 4.2.0.CR2)
> Let the user select the version of the arquillian container adapter
> ---------------------------------------------------------------------
>
> Key: JBIDE-16225
> URL: https://issues.jboss.org/browse/JBIDE-16225
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: testing-tools
> Affects Versions: 4.1.1.CR1
> Reporter: Xavier Coulon
> Assignee: Snjezana Peco
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> The Arquillian wizard provides users with a list of containers (eg: JBOSS_AS_REMOTE_7.X) that can be used but it misses the version selection (eg: 7.1.1.Final, 7.2.0.Final, etc.).
> I think it's important to let the user choose the version of the 'driver' she needs to use, because it needs to match against the actual version of the container.
> for example, using org.jboss.as:jboss-as-arquillian-container-remote:7.2.0.Final against JBoss AS 7.1.1 will not work.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-16695) Add marker/quick fix if test contains non static deployment method
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16695?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16695:
----------------------------------------
Fix Version/s: 4.3.0.Alpha1
(was: 4.2.0.CR2)
> Add marker/quick fix if test contains non static deployment method
> ------------------------------------------------------------------
>
> Key: JBIDE-16695
> URL: https://issues.jboss.org/browse/JBIDE-16695
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.Final
> Reporter: Rich DiCroce
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Alpha1
>
>
> In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive:
> {code}
> @Deployment
> public static WebArchive createDeployment() {
> ...code to create deployment here...
> }
> {code}
> As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17696:
----------------------------------------
Fix Version/s: 4.2.1.Final
4.3.0.Alpha1
(was: 4.2.0.CR2)
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Assignee: Denis Golovin
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months