[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-14544:
--------------------------------------
I am having trouble reproducing this on my system. This may be a related to Linux or may be related to android tools. I have however made some improvements that can help discover the problem. The builds that includes the changes will be published on the nightly site(give it a few hours before it propogates) http://download.jboss.org/jbosstools/builds/staging/jbosstools-aerogear_m.... Can you please update the plugins from the nightly update site and check out the problem. We should at least see somewhat useful logging that can help me track the problem.
> Cannot run Cordova project on Android Emulator/Device
> -----------------------------------------------------
>
> Key: JBIDE-14544
> URL: https://issues.jboss.org/browse/JBIDE-14544
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Fedora 17 32bit
> Android 4.1.2
> Reporter: Stefan Bunciak
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.1.0.Beta1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> {code}
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> at java.io.File.createNewFile(File.java:883)
> at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99)
> at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {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, 10 months
[JBoss JIRA] (JBIDE-13237) Use "suggested-value" from faces-config.xml for JSF attribute suggestion
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13237?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13237:
-----------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> Use "suggested-value" from faces-config.xml for JSF attribute suggestion
> ------------------------------------------------------------------------
>
> Key: JBIDE-13237
> URL: https://issues.jboss.org/browse/JBIDE-13237
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JSF
> Reporter: Paul Dijou
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
>
> After reading [this wiki entry|https://community.jboss.org/wiki/NewKBPlug-inAndCodeAssistInJBossTo...], it looks like one property of the faces-config.xml isn't used so far, it's the *"suggested-value"* (see http://horstmann.com/corejsf/faces-config.html#suggested-value ). Its description is quite small and I couldn't find any real documentation about it. But we can read: "This value is advisory only and is intended for tools", and JBoss Tools is... a tool, right? :-)
> So it would be great that JBoss Tools check the presence of such a "suggested-value" inside faces-config.xml and population an "enumeration" proposal type for the corresponding attribute.
> Since "suggested-value" is a string, it cannot support natively a list of suggestions, so, right now, RichFaces is using "," as a separator. Which mean having:
> {code}
> <property-name>severity</property-name>
> <property-class>java.lang.String</property-class>
> <suggested-value>success,info,warning,important,inverse</suggested-value>
> {code}
> Should be equivalent to:
> {code}
> <attribute name="severity">
> <proposal type="enumeration">
> <param value="success" />
> <param value="info" />
> <param value="warning" />
> <param value="important" />
> <param value="inverse" />
> </proposal>
> </attribute>
> {code}
> What do you think?
--
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, 10 months
[JBoss JIRA] (JBIDE-13419) Support invocation handler binding extension of Deltaspike
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13419?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13419:
-----------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> Support invocation handler binding extension of Deltaspike
> ----------------------------------------------------------
>
> Key: JBIDE-13419
> URL: https://issues.jboss.org/browse/JBIDE-13419
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: CDI extensions
> Affects Versions: 4.0.0.Final
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
>
> Objects:
> 1. Binding Annotations - annotation type with @InvocationHandlerBinding.
> 2. Partial Beans - abstract classes and interfaces annotated with a binding annotation.
> 3. Invocation Handlers - classes inplementing InvocationHandler and annotated with a binding annotation.
> Validation rules:
> 1. Class annotated with a binding annotation should be either abstract, or interface, or implement InvocationHandler.
> Error text: "Binding annotation %annotationName% can be applied only to abstract classes, interfaces, and classes implementing InvocationHandler."
> 2. There should be no more than one invocation handler for each binding annotation.
> Error text: "Multiple handlers are found for binding annotation %annotationName%."
> 3. Invocation handler class should be normal-scoped.
> Error text: "Invocation handler class should be a normal-scoped bean."
> 4. Each partial bean should be bound to an invocation handler.
> Error text: "Partial bean %className% should have an invocation handler for binding annotation %annotationName%."
> 5. Deltaspike implementation of the extension reads the first binding annotation on a class and ignores the next ones. Hence, they should be marked with a warning:
> "Binding annotation %annotationName% is ignored because class is already annotated with binding annotation %firstAnnotationName%."
--
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, 10 months
[JBoss JIRA] (JBIDE-13630) EL code completion/validation is not working with JSF resource bundles from dependent project
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13630?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13630:
-----------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> EL code completion/validation is not working with JSF resource bundles from dependent project
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-13630
> URL: https://issues.jboss.org/browse/JBIDE-13630
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF
> Affects Versions: 4.1.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.x
>
>
> 1. Create a JSF 1.2 project: JSFProject
> 2. Create a java project: JavaProject
> 3. Add the resource bundle to the JavaProject/src/demo/labels.properties
> 4. Add some properties to this resource bundle
> 5. Add the following reference to the faces.config:
> {code}
> <resource-bundle>
> <base-name>demo.labels</base-name>
> <var>labels</var>
> </resource-bundle>
> {code}
> 6. Add JavaProject to the classpath of JSFProject
> 7. Open any xhtml file in JSFProject
> 8. Try Ctrl+Space on {code}#{labels.|}{code}
> 9. {color:red}FAILURE:{color} There is no any property available via code assist.
> 10. Move the labels.properties to JSFProject source folder.
> 11. {color:red}FAILURE:{color} Code completion for labels is still not working.
> 12. Edit and save labels.properties (in JSFProject)
> 13. Code completion is working.
--
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, 10 months