[JBoss JIRA] (JBIDE-18174) cdi.ui tests failure
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18174?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-18174:
-----------------------------------------
The problem is that JSFNature couldn't be created on a test project:
{code}
!ENTRY org.jboss.tools.jst.web.ui 4 0 2014-09-03 19:47:57.183
!MESSAGE Missing project nature extension for org.jboss.tools.jsf.jsfnature.
!STACK 1
org.eclipse.core.internal.resources.ResourceException: Missing project nature extension for org.jboss.tools.jsf.jsfnature.
at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:216)
at org.eclipse.core.internal.resources.Project.getNature(Project.java:448)
at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.XmlELCompletionProposalComputer.isELCAToBeShown(XmlELCompletionProposalComputer.java:558)
at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.XmlELCompletionProposalComputer.addAttributeValueELProposals(XmlELCompletionProposalComputer.java:172)
at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.XmlELCompletionProposalComputer.addAttributeValueProposals(XmlELCompletionProposalComputer.java:158)
at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeAttributeValueProposals(AbstractXMLCompletionProposalComputer.java:594)
at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeCompletionProposals(AbstractXMLCompletionProposalComputer.java:399)
at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.AbstractXmlCompletionProposalComputer.computeCompletionProposals(AbstractXmlCompletionProposalComputer.java:741)
at org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCompletionProposalComputer.computeCompletionProposals(AbstractXMLCompletionProposalComputer.java:169)
at org.jboss.tools.jst.web.ui.internal.editor.contentassist.computers.AbstractXmlCompletionProposalComputer.computeCompletionProposals(AbstractXmlCompletionProposalComputer.java:89)
at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:284)
at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:290)
at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.collectProposals(StructuredContentAssistProcessor.java:484)
at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.computeCompletionProposals(StructuredContentAssistProcessor.java:255)
at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:127)
at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1861)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:573)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:570)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:505)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:499)
at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1687)
at org.jboss.tools.common.base.test.contentassist.CATestUtil.prepareCAInvokation(CATestUtil.java:108)
at org.jboss.tools.common.base.test.contentassist.CATestUtil.collectProposals(CATestUtil.java:113)
at org.jboss.tools.common.base.test.contentassist.AbstractContentAssistantTestCase.checkProposals(AbstractContentAssistantTestCase.java:129)
at org.jboss.tools.common.base.test.contentassist.AbstractContentAssistantTestCase.checkProposals(AbstractContentAssistantTestCase.java:108)
at org.jboss.tools.cdi.ui.test.CATest.testEL(CATest.java:49)
{code}
> cdi.ui tests failure
> --------------------
>
> Key: JBIDE-18174
> URL: https://issues.jboss.org/browse/JBIDE-18174
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR2
>
>
> {code}
> Failed tests: testCAELProposalFilteringInXHTML(org.jboss.tools.cdi.ui.test.CAELProposalFilteringTest): Content Assistant returned no proposals
> testCAELProposalFilteringInJSP(org.jboss.tools.cdi.ui.test.CAELProposalFilteringTest): Content Assistant returned no proposals
> testEL(org.jboss.tools.cdi.ui.test.CATest): Content Assistant returned no proposals
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-10067) Connection wizard: Provide capability to signup to openshift in openshift client
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10067?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-10067.
------------------------------------
Assignee: Andre Dietisheim
Fix Version/s: 4.2.0.CR1
(was: LATER)
Resolution: Done
> Connection wizard: Provide capability to signup to openshift in openshift client
> --------------------------------------------------------------------------------
>
> Key: JBIDE-10067
> URL: https://issues.jboss.org/browse/JBIDE-10067
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.M4
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard
> Fix For: 4.2.0.CR1
>
>
> We currently dont offer the possibility to signup to the OpenShift Express PaaS. We only offer a link to the signup page on OpenShift. The REST service now offers this capability and it's now up to us to include this into our client.
> There are implementation details to discuss with the OpenShift Express team, since they currently offer this capability only with a shared secret (see Appcelerator and mails discussing this topic). As opensource project it's not possible for us to require a shared secret we have to hide from the public.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18148) problem with Hibernate package-info.java TypeDefs
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18148?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-18148:
-----------------------------------
As you can see in the screenshot, your attached example imports perfectly normally in my JBT. There was an error related to a missing console configuration but after creating that one everything became ok. Which version of JBT are you using? Can you try with the recent candidate CR1 build: http://download.jboss.org/jbosstools/updates/staging/luna/jbosstools-4.2.... ? Btw, this requires the Luna JEE bundle (http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/...).
> problem with Hibernate package-info.java TypeDefs
> -------------------------------------------------
>
> Key: JBIDE-18148
> URL: https://issues.jboss.org/browse/JBIDE-18148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Environment: OSX 10.9.4
> Reporter: Jeffrey Simpson
> Assignee: Koen Aers
> Fix For: 4.2.0.CR1
>
> Attachments: eclipseErrors.log, TypeDefError.png, TypeDefError.zip
>
>
> I just tried out JBoss Developer Studio 8.0.0.Beta3 and it reports all of my Hibernate types that are defined in a package-info as not being found. I get "Type "common-big-decimal" could not be found" where I use it to define an attribute on an entity.
> Here is my Package-info.java
>
> @org.hibernate.annotations.TypeDefs (
>
> {
> @org.hibernate.annotations.TypeDef(name="yfu_boolean", typeClass=org.yfu.util.hibernate.TrueFalseBooleanUserType.class),
> @org.hibernate.annotations.TypeDef(name="integer_date", typeClass=org.yfu.util.hibernate.IntegerDateUserType.class),
> @org.hibernate.annotations.TypeDef(name="integer_local_date", typeClass=org.yfu.util.hibernate.IntegerLocalDateUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_big_decimal", typeClass=org.yfu.util.hibernate.NullableBigDecimalUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_long", typeClass=org.yfu.util.hibernate.NullableLongUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_integer", typeClass=org.yfu.util.hibernate.NullableIntegerUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_string", typeClass=org.yfu.util.hibernate.NullableStringUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_tf_boolean", typeClass=org.yfu.util.hibernate.NullableTFBooleanUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_yn_boolean", typeClass=org.yfu.util.hibernate.NullableYNBoolenaUserType.class),
> @org.hibernate.annotations.TypeDef(name="yfu_boolean_integer", typeClass=org.yfu.util.hibernate.YFUBooleanIntegerUserType.class),
>
> }
> )
> package org.yfu.util.hibernate;
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-10067) Connection wizard: Provide capability to signup to openshift in openshift client
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10067?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-10067:
------------------------------------------
closing since there was no discussion about it for +2y
> Connection wizard: Provide capability to signup to openshift in openshift client
> --------------------------------------------------------------------------------
>
> Key: JBIDE-10067
> URL: https://issues.jboss.org/browse/JBIDE-10067
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.M4
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard
> Fix For: LATER
>
>
> We currently dont offer the possibility to signup to the OpenShift Express PaaS. We only offer a link to the signup page on OpenShift. The REST service now offers this capability and it's now up to us to include this into our client.
> There are implementation details to discuss with the OpenShift Express team, since they currently offer this capability only with a shared secret (see Appcelerator and mails discussing this topic). As opensource project it's not possible for us to require a shared secret we have to hide from the public.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16885) Embed wizard: Can provide "Code Anything" without url, should not be able to
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16885?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16885:
-------------------------------------
Assignee: (was: Andre Dietisheim)
> Embed wizard: Can provide "Code Anything" without url, should not be able to
> ----------------------------------------------------------------------------
>
> Key: JBIDE-16885
> URL: https://issues.jboss.org/browse/JBIDE-16885
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta1
> Reporter: Marián Labuda
> Labels: embed_wizard
> Fix For: 4.2.1.Final
>
> Attachments: wrong_button_accessibility.png, wrong_button_accessibility.png, wrong_button_accessibility2.png, wrong_button_accessibility2.png
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> In the wizard to edit the embeddable cartridges there is "Code Anything" cartridge which requires URL of cartridge. If user just selects and does not check this cartridge, it is not possible to hit the OK button (see attached screen wrong_button_accessibility).
> Also if user check this cartridge but select another one without providing URL to the Code anything cartridge, it is possible to hit the OK button (it should not be - see attached screenshot wrong_button_accessibility2.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16720) Server Adapter: Allow easier access to openshift operations from jboss servers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16720:
-------------------------------------
Fix Version/s: 4.2.1.Final
(was: 4.3.x)
> Server Adapter: Allow easier access to openshift operations from jboss servers
> ------------------------------------------------------------------------------
>
> Key: JBIDE-16720
> URL: https://issues.jboss.org/browse/JBIDE-16720
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.1.1.Final
> Reporter: Mark Drilling
> Labels: server_adapter
> Fix For: 4.2.1.Final
>
>
> We currently have a couple issues with connecting to an OpenShift Data Virtualization instance from the tooling. I'm aware that issues are being addressed for future release, others I'm not sure. This is intended to help guide your development to accommodate this use case.
> Our expected usage with Data Virtualization is a bit different than some others. With DV we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV instance as a remote server. We typically would not deploy using git push.
> Currently, we connect to an OpenShift DV instance like this:
> 1) Deploy DV cartridge via OpenShift web console.
> 2) Port forward from command line using rhc port-forward
> 3) Set up EAP server instance in the tooling, mark as externally managed and start it. From there we can connect to the DV instance and continue with modeling and deployments in Teiid Designer perspective
> The issues we observed:
> 1) Creation of the OpenShift 'server' forces a git repo to be copied locally. We'd like to simply create the 'OpenShift server' without cloning the repo.
> 2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is now (or will soon) allow downloadable carts to be registered, so this problem should be solved as the cart will show up in the cartridge list.
> Our current method of connecting is ok for now, but a simpler usage of the OpenShift server adapter would allow us to more easily manage the instance (e.g. port-forward without going to the command line, viewing logs, etc.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months