[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-14544.
-----------------------------------------
Fix Version/s: 4.1.1.Beta1
(was: 4.1.x)
(was: 4.2.x)
Resolution: Done
The original issue about requirement on names was fixed - moving separate issue concerning android requirement versioon to another jira.
> 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
> Labels: respin-a
> Fix For: 4.1.1.Beta1
>
> Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png
>
> 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, 5 months
[JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-13869 at 11/6/13 11:11 AM:
------------------------------------------------------------------
[~jpeterka] [~vpakan] [~psrna] [~rhopp] [~rawagner]... Guys, this change is for you. Can you please review the PR and give a try on your favourite use-case?
You'll need to:
* Fetch code from PR
* "mvn install" parent pom
* Use a version of JBDS that matches the stream of the test module (JBDS 8.0.0.Alpha1 for master, JBDS 7.1.0.Beta1 for 4.1.1 branch).
* and run the command as described above. You can also run it on an Eclipse instance (instead of JBDS), but you'll need to override the "tycho.surefire.profileName" property to match the right profile.
was (Author: mickael_istria):
[~jpeterka] [~vpakan] [~psrna] [~rhopp] [~rawagner]... Guys, this change is for you. Can you please review the PR and give a try on your favourite use-case?
You'll need to:
* Fetch code from PR
* "mvn install" parent pom
* Use a version of JBDS that matches the stream of the test module (JBDS 8.0.0.Alpha1 for master, JBDS 7.1.0.Beta1 for 4.1.1 branch).
and run the command as described above. You can also run it on an Eclipse instance (instead of JBDS), but you'll need to override the "tycho.surefire.profileName" property to match the right profile.
> Find a way to run testsuite against existing builds but with different TP without requiring publishing
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13869
> URL: https://issues.jboss.org/browse/JBIDE-13869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
>
> Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again.
> Possible options:
> 1) Create new testsuite that depends on all other testsuites and run them in surefire test.
> 2) use something else than surefire to run the already built testsuites.
--
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, 5 months
[JBoss JIRA] (JBIDE-15864) Add dialog displaying errors when Plugins are added to Hybrid Mobile Project
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15864?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-15864:
-------------------------------------
When error happens no information is displayed user and no plugins are added to configuration and project. But users doesn't know what happened.
Example: When user specify incorrect repo URL no plugins are added but user don't know why
> Add dialog displaying errors when Plugins are added to Hybrid Mobile Project
> ----------------------------------------------------------------------------
>
> Key: JBIDE-15864
> URL: https://issues.jboss.org/browse/JBIDE-15864
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Vlado Pakan
> Fix For: 4.1.1.CR1
>
>
> Sometimes when adding Plugins to Hybrid Mobile project via Cordova Configuration Editor some errors are happening and added Plugins are different than Plugins selected to be added. This is very confusing for user. Would be nice to have some dialog explaining errors which happened while adding Plugins so user know what has happened
--
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, 5 months
[JBoss JIRA] (JBDS-2690) Internal problem when spring project from jboss central is used
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBDS-2690?page=com.atlassian.jira.plugin.... ]
Joshua Wilson commented on JBDS-2690:
-------------------------------------
Jiri, after working through this error with Nick, he found that it has to do with a java/jdt difference.
The solution is to provide the required libs in the pom. If you want to test this, the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts/tree...] have this applied. I have also updated the source for the [Spring Archetype|https://github.com/jboss-eap/wfk-archetypes/tree/1.0.3.Final] that is listed on Jboss Central in JBDS.
I am trying very hard to keep the Spring Quickstarts up to date and error free (as much as is possible), please use these to test with. Please also let me know if you find any other errors with Spring based projects.
The solution was to add the following to the pom:
{code}
<dependency>
<groupId>org.jboss.spec.javax.servlet</groupId>
<artifactId>jboss-servlet-api_3.0_spec</artifactId>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.servlet.jsp</groupId>
<artifactId>jboss-jsp-api_2.2_spec</artifactId>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.servlet.jstl</groupId>
<artifactId>jboss-jstl-api_1.2_spec</artifactId>
</dependency>
{code}
This assumes that these libs are listed in the BOM that the project references.
> Internal problem when spring project from jboss central is used
> ---------------------------------------------------------------
>
> Key: JBDS-2690
> URL: https://issues.jboss.org/browse/JBDS-2690
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-dependencies, upstream
> Affects Versions: 7.0.0.CR1
> Environment: JBDS 7.0.0.CR1a, L64
> Reporter: Jiri Peterka
> Assignee: Nick Boldt
> Fix For: 7.1.x, 8.0.x
>
>
> I have this error when Spring 3.2 or Spring 3.3 is installed:
> {code}
> java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2521)
> at java.lang.Class.getDeclaredMethods(Class.java:1845)
> at org.springframework.core.type.StandardAnnotationMetadata.hasAnnotatedMethods(StandardAnnotationMetadata.java:159)
> at org.springframework.context.annotation.ConfigurationClassUtils.isLiteConfigurationCandidate(ConfigurationClassUtils.java:106)
> at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:87)
> at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:257)
> at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:73)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:748)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:741)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcess(BeansConfig.java:625)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.access$8(BeansConfig.java:584)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:450)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:1)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 23 more
> {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, 5 months
[JBoss JIRA] (JBDS-2738) Support OpenShift 2.0 features
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2738?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen closed JBDS-2738.
-------------------------------------
Resolution: Partially Completed
The features wanted for beta1 is done. The remaining will be done separately.
> Support OpenShift 2.0 features
> ------------------------------
>
> Key: JBDS-2738
> URL: https://issues.jboss.org/browse/JBDS-2738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 7.1.0.Beta1
>
>
> OpenShift 2.0 is coming, needs to investigate when that happens and what it implies for eclipse (and eventually Forge) tooling.
> This functionallity would need to be added without breaking how we work with current openshift online and openshift enterprise which has 1.x api's.
> Opening this issue to track issues related to this (please create subtasks)
--
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, 5 months
[JBoss JIRA] (JBDS-2784) Support EAP 6.2
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2784?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-2784.
---------------------------------------
Resolution: Done
This is done by using EAP 6.1+ server adapter.
> Support EAP 6.2
> ---------------
>
> Key: JBDS-2784
> URL: https://issues.jboss.org/browse/JBDS-2784
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: 7.1.0.Beta1
>
>
> EAP 6.2 comes out around our release.
> Should we try and support this in 7.1 even though we won't have the last final build ?
> For now it is possible to use EAP 6.1 to run EAP 6.2
--
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, 5 months
[JBoss JIRA] (JBDS-2784) Support EAP 6.2
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2784?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2784:
--------------------------------------
CDW devel_ack: + (was: ?)
Status: New (was: New)
> Support EAP 6.2
> ---------------
>
> Key: JBDS-2784
> URL: https://issues.jboss.org/browse/JBDS-2784
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: 7.1.0.Beta1
>
>
> EAP 6.2 comes out around our release.
> Should we try and support this in 7.1 even though we won't have the last final build ?
> For now it is possible to use EAP 6.1 to run EAP 6.2
--
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, 5 months