[JBoss JIRA] (JBIDE-16257) Cordova Plug-in Discovery wizard should have option to show already installed plug-ins as disabled
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16257?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-16257:
---------------------------------
Labels: new_and_noteworthy (was: )
> Cordova Plug-in Discovery wizard should have option to show already installed plug-ins as disabled
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16257
> URL: https://issues.jboss.org/browse/JBIDE-16257
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Assignee: Gorkem Ercan
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta1
>
>
> In JBoss Central Software/Updates tab, can select 'show installed' check box and already installed components are shown as disabled (greyed out).
> A similar feature should be added to Cordova plug-in Discovery wizard. As at the moment if you have installed a plug-in and then search for it in discovery wizard, the wizard shows nothing to inform you why is isn't listed - user has to make an assumption that it's because they have already installed it rather than say typed the wrong text in the search field.
--
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
[JBoss JIRA] (JBIDE-15327) CDI Test failure
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15327?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-15327.
------------------------------------
closing
> CDI Test failure
> ----------------
>
> Key: JBIDE-15327
> URL: https://issues.jboss.org/browse/JBIDE-15327
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Alpha1
>
>
> Some times I see the following error when running cdi.core.tests:
> {code}
> Contains: Errors running builder 'JBoss Knowledge Base Builder' on project 'missingBeansXmlChildProject'.
> java.lang.IllegalArgumentException: ImageRegistry key already in use: -1314270185
> at org.eclipse.jface.resource.ImageRegistry.put(ImageRegistry.java:284)
> at org.jboss.tools.common.model.icons.impl.XModelObjectIcon.getEclipseImage0(XModelObjectIcon.java:100)
> at org.jboss.tools.common.model.undo.XChangeSetUndo.<init>(XChangeSetUndo.java:29)
> at org.jboss.tools.common.model.undo.XChangeUndo.<init>(XChangeUndo.java:18)
> at org.jboss.tools.common.model.impl.XModelImpl.changeObjectAttribute(XModelImpl.java:356)
> at org.jboss.tools.common.model.impl.XModelImpl.changeObjectAttribute(XModelImpl.java:277)
> at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.mergeAttributes(AbstractExtendedXMLFileImpl.java:407)
> at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.merge(AbstractExtendedXMLFileImpl.java:390)
> at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.mergeAll(AbstractExtendedXMLFileImpl.java:290)
> at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.edit(AbstractExtendedXMLFileImpl.java:261)
> at org.jboss.tools.common.model.filesystems.impl.AbstractExtendedXMLFileImpl.edit(AbstractExtendedXMLFileImpl.java:210)
> at org.jboss.tools.common.model.loaders.impl.SimpleWebFileLoader.update(SimpleWebFileLoader.java:149)
> at org.jboss.tools.common.model.filesystems.impl.FolderImpl.reload(FolderImpl.java:696)
> at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateLoaded(FolderImpl.java:607)
> at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateNew(FolderImpl.java:729)
> at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:418)
> at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateLoaded(FolderImpl.java:592)
> at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:415)
> at org.jboss.tools.common.model.util.EclipseResourceUtil.findResourceInFileSystem(EclipseResourceUtil.java:569)
> at org.jboss.tools.common.model.util.EclipseResourceUtil.getObjectByResource(EclipseResourceUtil.java:144)
> at org.jboss.tools.jst.web.kb.internal.scanner.XMLScanner.isLikelyComponentSource(XMLScanner.java:82)
> at org.jboss.tools.jst.web.kb.internal.KbResourceVisitor.visit(KbResourceVisitor.java:98)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder$SampleDeltaVisitor.visit(KbBuilder.java:69)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.incrementalBuild(KbBuilder.java:151)
> at org.jboss.tools.jst.web.kb.internal.KbBuilder.build(KbBuilder.java:114)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:394)
> at org.eclipse.core.internal.resources.Project$1.run(Project.java:618)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597)
> at org.eclipse.core.internal.resources.Project.build(Project.java:114)
> at org.jboss.tools.common.base.test.validation.TestUtil.validate(TestUtil.java:61)
> at org.jboss.tools.cdi.core.test.tck.validation.MissingBeansXmlValidationTest.testCreatingBeansXml(MissingBeansXmlValidationTest.java:64)
> 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:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:23)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.extensions.TestSetup.run(TestSetup.java:27)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> 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:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
> {code}
--
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
[JBoss JIRA] (JBIDE-15638) New CDI Bean wizard should require a scope for CDI 1.1 project with beans.xml in annotated mode
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15638?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-15638:
------------------------------------------
Previously I tried with AS 7.1 (which does not have JEE7 support) by changing CDI 1.0 configuration to 1.1 (using Modify configuration) - in this case, error isn't displayed when I try to create new Bean.
If I try with Wildfly, choosing CDI 1.1 configuration, then error is displayed.
> New CDI Bean wizard should require a scope for CDI 1.1 project with beans.xml in annotated mode
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-15638
> URL: https://issues.jboss.org/browse/JBIDE-15638
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdi
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Alpha1
>
>
> 1. Create a CDI 1.1 Web project
> 2. File->New->Bean->
> 3. Enter any name of the bean
> 4. There should be an error message in the wizard saying Bean scope should be set in archives with bean discovery mode 'annotated'
--
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
[JBoss JIRA] (JBIDE-11919) Forge Console in JBDS/Tools - Screen "Garbage"
by Larry Wilson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11919?page=com.atlassian.jira.plugi... ]
Larry Wilson commented on JBIDE-11919:
--------------------------------------
Lincoln - I do believe this is related to executing in the JBDS environment. I've run my script 3 times this morning without an error (that's unusual in the JBDS environment). Native is a *lot* faster. I hunch that there's an issue between executing a forge command, auto-refreshing the JBDS environment, and running the next forge command before the refresh has completed. Apparently a timing/synchonization issue.
Koen, I don't see a way to attach a file. Besides, I'd have to get an OK to upload the entire thing. Here's a sample (first part of the script) of what we're doing:
set ACCEPT_DEFAULTS true;
new-project --named tcs2 --topLevelPackage com.tcs --type war --projectFolder tcs2
forge install-plugin angularjs
persistence setup --named Tcs --provider HIBERNATE --container JBOSS_EAP6 --jndiDataSource java:jboss/TcsDS
validation setup
entity --named TimeZone --package ~.model;
field string --named code --length 100;
constraint NotNull --onProperty code;
field string --named description --length 100;
constraint NotNull --onProperty description;
field string --named lastUpdateBy --length 50;
field temporal --type TIMESTAMP --named lastUpdateDate;
entity --named PhoneType --package ~.model;
field string --named description;
constraint NotNull --onProperty description;
field string --named lastUpdateBy --length 50;
field temporal --type TIMESTAMP --named lastUpdateDate;
entity --named AttributeType --package ~.model;
field string --named description;
constraint NotNull --onProperty description;
field string --named lastUpdateBy --length 50;
field temporal --type TIMESTAMP --named lastUpdateDate;
entity --named ProductCode --package ~.model;
field string --named description;
constraint NotNull --onProperty description;
field string --named lastUpdateBy --length 50;
field temporal --type TIMESTAMP --named lastUpdateDate;
entity --named Country --package ~.model;
field string --named code --length 2;
constraint NotNull --onProperty code;
constraint Size --min 2 --max 2 --onProperty code;
field string --named description;
constraint NotNull --onProperty description;
field string --named lastUpdateBy --length 50;
field temporal --type TIMESTAMP --named lastUpdateDate;
entity --named State --package ~.model;
field string --named code --length 4;
constraint NotNull --onProperty code;
constraint Size --onProperty code --min 2 --max 4;
field string --named description;
constraint NotNull --onProperty description;
field string --named lastUpdateBy --length 50;
field temporal --type TIMESTAMP --named lastUpdateDate;
Hope this helps.
> Forge Console in JBDS/Tools - Screen "Garbage"
> ----------------------------------------------
>
> Key: JBIDE-11919
> URL: https://issues.jboss.org/browse/JBIDE-11919
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 3.3.0.Beta3
> Environment: 3.3.Beta3 or JBDS5 Beta3
> Reporter: Burr Sutter
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 3.3.0.CR1
>
> Attachments: forgedemo.fsh, Screen Shot 2012-05-21 at 11.00.35 AM.png, Screen Shot 2012-05-21 at 11.05.15 AM.png, Screen Shot 2012-05-21 at 11.18.41 AM.png
>
>
> _____
> | ___|__ _ __ __ _ ___
> EC: echo echo CRN: /Users/burr/gettingstarted/workspaceToolsBeta2v3 CRT: DirectoryResource CPN: PAR: [Ljava.lang.String;@1371098d org.jboss.forge.shell.util.PipeOutImpl@622a11f3 EC: echo echo CRN: /Users/burr/gettingstarted/workspaceToolsBeta2v3 CRT: DirectoryResource CPN: PAR: [Ljava.lang.String;@38009ade org.jboss.forge.shell.util.PipeOutImpl@2fb7818b EC: echo echo CRN: /Users/burr/gettingstarted/workspaceToolsBeta2v3 CRT: DirectoryResource CPN: PAR: [Ljava.lang.String;@421dc8c8 org.jboss.forge.shell.util.PipeOutImpl@3004ed34
--
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