[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2719 at 11/6/13 2:03 PM:
-----------------------------------------------------------
[~jowilson] [~fbricon] So we need to add org.springframework.ide.eclipse.ajdt.feature to our SpringIDE 3.4 mirror, the Central TP, and the SpringIDE connector in JBoss Central? Anything else missing?
To clarify versions, JBDS 7.x currently includes *SpringIDE 3.3* in its Central connector. But I'm hoping to upgrade that to *SpringIDE 3.4* for 7.1.0.CR1, if we can sort out all the missing deps / requirements & establish that version 3.4 contains the same or fewer problems than 3.3.
was (Author: nickboldt):
[~jowilson] [~fbricon] So we need to add org.springframework.ide.eclipse.ajdt.feature to our SpringIDE 3.4 mirror, the Central TP, and the SpringIDE connector in JBoss Central? Anything else missing?
To clarify versions, JBDS 7.x currently includes *SpringIDE 3.3* in its Central connector. But I'm hoping to upgrade that to SpringIDE 3.4 for 7.1.0.CR1, if we can sort out all the missing deps / requirements & establish that version 3.4 contains the same or fewer problems than 3.3.
> Multiple Spring AOP problems when travel example is imported
> ------------------------------------------------------------
>
> Key: JBDS-2719
> URL: https://issues.jboss.org/browse/JBDS-2719
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.0.0.GA
> Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central
> Reporter: Jiri Peterka
> Assignee: Rodney Russ
> Fix For: 7.1.0.Beta1
>
>
> There are Multiple Spring AOP Errors after travel example is imported:
> {code}
> Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException
> {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-2719) Multiple Spring AOP problems when travel example is imported
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-2719:
--------------------------------
Assignee: Nick Boldt (was: Rodney Russ)
> Multiple Spring AOP problems when travel example is imported
> ------------------------------------------------------------
>
> Key: JBDS-2719
> URL: https://issues.jboss.org/browse/JBDS-2719
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.0.0.GA
> Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central
> Reporter: Jiri Peterka
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1
>
>
> There are Multiple Spring AOP Errors after travel example is imported:
> {code}
> Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException
> {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-15869) Test failure in org.jboss.tools.cdi.text.ext.test
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15869?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15869:
----------------------------------------
Adding more time to the test plugin won't help with "no more handles" error. Avoiding bad slaves seems to be a better idea.
> Test failure in org.jboss.tools.cdi.text.ext.test
> -------------------------------------------------
>
> Key: JBIDE-15869
> URL: https://issues.jboss.org/browse/JBIDE-15869
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdi
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/120/console}
> 13:39:46 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.text.ext.test: An unexpected error occured (return code 13). See log for details. -> [Help 1]
> 13:39:46 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.text.ext.test: An unexpected error occured (return code 13). See log for details.
> {code}
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/ws/sources/cdi/tests/org.jboss.tools.cdi.text.ext.test/target/work/data/.metadata/.log}
> !ENTRY org.eclipse.osgi 4 0 2013-11-05 11:42:47.049
> !MESSAGE Application error
> !STACK 1
> org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]{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-2719) Multiple Spring AOP problems when travel example is imported
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2719 at 11/6/13 2:03 PM:
-----------------------------------------------------------
[~jowilson] [~fbricon] So we need to add org.springframework.ide.eclipse.ajdt.feature to our SpringIDE 3.4 mirror, the Central TP, and the SpringIDE connector in JBoss Central? Anything else missing?
To clarify versions, JBDS 7.x currently includes *SpringIDE 3.3* in its Central connector. But I'm hoping to upgrade that to SpringIDE 3.4 for 7.1.0.CR1, if we can sort out all the missing deps / requirements & establish that version 3.4 contains the same or fewer problems than 3.3.
was (Author: nickboldt):
[~jowilson] [~fbricon] So we need to add org.springframework.ide.eclipse.ajdt.feature to our SpringIDE 3.4 mirror, the Central TP, and the SpringIDE connector in JBoss Central? Anything else missing?
> Multiple Spring AOP problems when travel example is imported
> ------------------------------------------------------------
>
> Key: JBDS-2719
> URL: https://issues.jboss.org/browse/JBDS-2719
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.0.0.GA
> Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central
> Reporter: Jiri Peterka
> Assignee: Rodney Russ
> Fix For: 7.1.0.Beta1
>
>
> There are Multiple Spring AOP Errors after travel example is imported:
> {code}
> Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException
> {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-2719) Multiple Spring AOP problems when travel example is imported
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2719:
----------------------------------
[~jowilson] [~fbricon] So we need to add org.springframework.ide.eclipse.ajdt.feature to our SpringIDE 3.4 mirror, the Central TP, and the SpringIDE connector in JBoss Central? Anything else missing?
> Multiple Spring AOP problems when travel example is imported
> ------------------------------------------------------------
>
> Key: JBDS-2719
> URL: https://issues.jboss.org/browse/JBDS-2719
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.0.0.GA
> Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central
> Reporter: Jiri Peterka
> Assignee: Rodney Russ
> Fix For: 7.1.0.Beta1
>
>
> There are Multiple Spring AOP Errors after travel example is imported:
> {code}
> Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException
> {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-15869) Test failure in org.jboss.tools.cdi.text.ext.test
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15869?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15869:
------------------------------------
[~akazakov] What about adding more time to the test plugin timeout? More memory to the job's config? Or just avoiding bad slaves?
Looks like we have good success on vmg39, but dev84 and dev110 are less effective.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
They're all RHEL6 boxes. Wonder how the dev slaves are configured differently from the vmg ones. Can't see anything obvious - looks like the same system props and more or less the same labels are used. Maybe [~vjuranek] knows?
> Test failure in org.jboss.tools.cdi.text.ext.test
> -------------------------------------------------
>
> Key: JBIDE-15869
> URL: https://issues.jboss.org/browse/JBIDE-15869
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdi
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/120/console}
> 13:39:46 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.text.ext.test: An unexpected error occured (return code 13). See log for details. -> [Help 1]
> 13:39:46 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.text.ext.test: An unexpected error occured (return code 13). See log for details.
> {code}
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/ws/sources/cdi/tests/org.jboss.tools.cdi.text.ext.test/target/work/data/.metadata/.log}
> !ENTRY org.eclipse.osgi 4 0 2013-11-05 11:42:47.049
> !MESSAGE Application error
> !STACK 1
> org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]{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-15869) Test failure in org.jboss.tools.cdi.text.ext.test
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15869?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-15869 at 11/6/13 1:52 PM:
-------------------------------------------------------------
[~akazakov] What about adding more time to the test plugin timeout? More memory to the job's config? Or just avoiding bad slaves?
Looks like we have good success on vmg39, but dev84 and dev110 are less effective.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
They're all RHEL6 boxes. Wonder how the dev slaves are configured differently from the vmg ones. Can't see anything obvious - looks like the same system props and more or less the same labels are used.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/vmg39-rhel6-x86...
vs.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev84-rhel6-x86...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev110-rhel6-x8...
Maybe [~vjuranek] knows?
was (Author: nickboldt):
[~akazakov] What about adding more time to the test plugin timeout? More memory to the job's config? Or just avoiding bad slaves?
Looks like we have good success on vmg39, but dev84 and dev110 are less effective.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
They're all RHEL6 boxes. Wonder how the dev slaves are configured differently from the vmg ones. Can't see anything obvious - looks like the same system props and more or less the same labels are used. Maybe [~vjuranek] knows?
> Test failure in org.jboss.tools.cdi.text.ext.test
> -------------------------------------------------
>
> Key: JBIDE-15869
> URL: https://issues.jboss.org/browse/JBIDE-15869
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdi
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/120/console}
> 13:39:46 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.text.ext.test: An unexpected error occured (return code 13). See log for details. -> [Help 1]
> 13:39:46 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.text.ext.test: An unexpected error occured (return code 13). See log for details.
> {code}
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/ws/sources/cdi/tests/org.jboss.tools.cdi.text.ext.test/target/work/data/.metadata/.log}
> !ENTRY org.eclipse.osgi 4 0 2013-11-05 11:42:47.049
> !MESSAGE Application error
> !STACK 1
> org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]{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-15877) In Run Configurations, Android label should be more descriptive
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15877?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-15877:
-----------------------------------
Fix Version/s: 4.2.0.Alpha1
> In Run Configurations, Android label should be more descriptive
> ---------------------------------------------------------------
>
> Key: JBIDE-15877
> URL: https://issues.jboss.org/browse/JBIDE-15877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Michelle Murray
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Alpha1
>
> Attachments: HybridMobile_runconfig_icons.png
>
>
> In Run Configurations, labels are "Android", "CordovaSim" and "iOS Simulator".
> The "Android" label should be renamed to emphasis Android what? How about "Android Simulator/Device"? - since I assume run configs will work with simulator and device. Otherwise just "Android Simulator"?
> !HybridMobile_runconfig_icons.png!
--
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-15877) In Run Configurations, Android label should be more descriptive
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15877?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15877:
----------------------------------------
OK. We have a separate issue for missing icons - JBIDE-15876
> In Run Configurations, Android label should be more descriptive
> ---------------------------------------------------------------
>
> Key: JBIDE-15877
> URL: https://issues.jboss.org/browse/JBIDE-15877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Michelle Murray
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Alpha1
>
> Attachments: HybridMobile_runconfig_icons.png
>
>
> In Run Configurations, labels are "Android", "CordovaSim" and "iOS Simulator".
> The "Android" label should be renamed to emphasis Android what? How about "Android Simulator/Device"? - since I assume run configs will work with simulator and device. Otherwise just "Android Simulator"?
> !HybridMobile_runconfig_icons.png!
--
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