[JBoss JIRA] (JBDS-3115) Include Ionic Palette
by Denis Golovin (JIRA)
Denis Golovin created JBDS-3115:
-----------------------------------
Summary: Include Ionic Palette
Key: JBDS-3115
URL: https://issues.jboss.org/browse/JBDS-3115
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: p2-product
Affects Versions: 8.0.0.CR1
Reporter: Denis Golovin
Assignee: Denis Golovin
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (JBIDE-17498) Can't run default hybrid project on device
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17498?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-17498:
--------------------------------
Attachment: BUILD SUCCESSFUL.png
> Can't run default hybrid project on device
> ------------------------------------------
>
> Key: JBIDE-17498
> URL: https://issues.jboss.org/browse/JBIDE-17498
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: windows
> Reporter: Ilya Buziuk
> Assignee: Gorkem Ercan
> Fix For: 4.2.0.CR1
>
> Attachments: BUILD SUCCESSFUL.png, Launching.png
>
>
> After choosing *Run As.. -> Run on Android Device* getting exception:
> {code}
> !ENTRY org.eclipse.ant.launching 4 0 2014-06-02 13:03:42.618
> !MESSAGE Ant Build Failed
> !STACK 1
> org.eclipse.core.runtime.CoreException: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:448)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:380)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
> ... 12 more
> !SUBENTRY 1 org.eclipse.ant.core 4 1 2014-06-02 13:03:42.618
> !MESSAGE E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> !STACK 0
> E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.jboss.tools.aerogear.hybrid.android.core 4 0 2014-06-02 13:03:42.620
> !MESSAGE Build failed... Build artifact does not exist
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (JBIDE-17498) Can't run default hybrid project on device
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17498?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-17498:
--------------------------------
Attachment: Launching.png
Now I have 'Build Successful' log !BUILD SUCCESSFUL.png|thumbnail!
However the process of Launching stucks on 48 % !Launching.png|thumbnail!
Any ideas why this might happen?
> Can't run default hybrid project on device
> ------------------------------------------
>
> Key: JBIDE-17498
> URL: https://issues.jboss.org/browse/JBIDE-17498
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: windows
> Reporter: Ilya Buziuk
> Assignee: Gorkem Ercan
> Fix For: 4.2.0.CR1
>
> Attachments: BUILD SUCCESSFUL.png, Launching.png
>
>
> After choosing *Run As.. -> Run on Android Device* getting exception:
> {code}
> !ENTRY org.eclipse.ant.launching 4 0 2014-06-02 13:03:42.618
> !MESSAGE Ant Build Failed
> !STACK 1
> org.eclipse.core.runtime.CoreException: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:448)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:380)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
> ... 12 more
> !SUBENTRY 1 org.eclipse.ant.core 4 1 2014-06-02 13:03:42.618
> !MESSAGE E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> !STACK 0
> E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.jboss.tools.aerogear.hybrid.android.core 4 0 2014-06-02 13:03:42.620
> !MESSAGE Build failed... Build artifact does not exist
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (JBIDE-17498) Can't run default hybrid project on device
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17498?page=com.atlassian.jira.plugi... ]
Ilya Buziuk edited comment on JBIDE-17498 at 7/31/14 12:49 PM:
---------------------------------------------------------------
Now I have 'Build Successful' log !BUILD SUCCESSFUL.png|thumbnail!
However the process of Launching stucks on 48 % !Launching.png|thumbnail!
Any ideas why this might happen?
was (Author: ibuziuk):
Now I have 'Build Successful' log !BUILD SUCCESSFUL.png|thumbnail!
However the process of Launching stucks on 48 % !Launching.png|thumbnail!
Any ideas why this might happen?
> Can't run default hybrid project on device
> ------------------------------------------
>
> Key: JBIDE-17498
> URL: https://issues.jboss.org/browse/JBIDE-17498
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: windows
> Reporter: Ilya Buziuk
> Assignee: Gorkem Ercan
> Fix For: 4.2.0.CR1
>
> Attachments: BUILD SUCCESSFUL.png, Launching.png
>
>
> After choosing *Run As.. -> Run on Android Device* getting exception:
> {code}
> !ENTRY org.eclipse.ant.launching 4 0 2014-06-02 13:03:42.618
> !MESSAGE Ant Build Failed
> !STACK 1
> org.eclipse.core.runtime.CoreException: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:448)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:380)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
> ... 12 more
> !SUBENTRY 1 org.eclipse.ant.core 4 1 2014-06-02 13:03:42.618
> !MESSAGE E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> !STACK 0
> E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.jboss.tools.aerogear.hybrid.android.core 4 0 2014-06-02 13:03:42.620
> !MESSAGE Build failed... Build artifact does not exist
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (JBIDE-18010) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18010?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-18010:
----------------------------------
Assignee: Nick Boldt
> For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18010
> URL: https://issues.jboss.org/browse/JBIDE-18010
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1: Please perform the following *2* tasks:
> 1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
> Be sure to also include *translated* files, where they exist.
> *java files*
> {code:title=*.java}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> *html files*
> {code:title=about.html}
> © 2014 Red Hat, Inc. All rights reserved
> {code}
> *properties files*
> {code:title=about.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
> {code}
> {code:title=about_fr.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
> {code}
> {code:title=feature.properties}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> {code:title=Messages.properties}
> # Copyright (c) 2014 Red Hat, Inc. and others.
> {code}
> *xsd files*
> {code:title=jboss-as-naming_1_3.xsd}
> Copyright 2014, Red Hat, Inc., and individual contributors
> {code}
> 2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
> Be sure to also include *translated* files, where they exist.
> *This step is particularly important for new plugins and features that have been added recently.*
> Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
> {code}BundleName = JMX Resources Bundle
> BundleProvider = JBoss by Red Hat{code}
> or
> {code}Bundle-Name.0 = JBossTools Archives Core Plugin
> Bundle-Vendor.0 = JBoss by Red Hat{code}
> Then in your MANIFEST.MF files, you will reference these variables like this.
> *Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
> {code}Bundle-Localization: plugin
> Bundle-Name: %BundleName
> Bundle-Vendor: %BundleProvider{code}
> or
> {code}Bundle-Localization: plugin
> Bundle-Name: %Bundle-Name.0
> Bundle-Vendor: %Bundle-Vendor.0{code}
> For features, check that your *feature.properties* file contains good values too:
> {code}featureName=JMX Console
> featureProvider=JBoss by Red Hat{code}
> or
> {code}featureName=JBoss Archives Tools
> providerName=JBoss by Red Hat{code}
> Then in your feature.xml files, you will reference these variables like this:
> {code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
> or
> {code}<feature label="%featureName" provider-name="%providerName" ...>{code}
> 3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
> 4. If you do not require QE to review your changes, please *Close* this JIRA when done.
> 5. If you have any questions, please contact [~nickboldt].
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3114
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (JBIDE-18027) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [LiveReload]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18027:
----------------------------------
Summary: For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [LiveReload]
Key: JBIDE-18027
URL: https://issues.jboss.org/browse/JBIDE-18027
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: livereload
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.CR1 [LiveReload]: Please perform the following *2* tasks:
1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
Be sure to also include *translated* files, where they exist.
*java files*
{code:title=*.java}
Copyright (c) 2010-2014 Red Hat, Inc. and others.
{code}
*html files*
{code:title=about.html}
© 2014 Red Hat, Inc. All rights reserved
{code}
*properties files*
{code:title=about.properties}
Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
{code}
{code:title=about_fr.properties}
Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
{code}
{code:title=feature.properties}
Copyright (c) 2010-2014 Red Hat, Inc. and others.
{code}
{code:title=Messages.properties}
# Copyright (c) 2014 Red Hat, Inc. and others.
{code}
*xsd files*
{code:title=jboss-as-naming_1_3.xsd}
Copyright 2014, Red Hat, Inc., and individual contributors
{code}
2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
Be sure to also include *translated* files, where they exist.
*This step is particularly important for new plugins and features that have been added recently.*
Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
{code}BundleName = JMX Resources Bundle
BundleProvider = JBoss by Red Hat{code}
or
{code}Bundle-Name.0 = JBossTools Archives Core Plugin
Bundle-Vendor.0 = JBoss by Red Hat{code}
Then in your MANIFEST.MF files, you will reference these variables like this.
*Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
{code}Bundle-Localization: plugin
Bundle-Name: %BundleName
Bundle-Vendor: %BundleProvider{code}
or
{code}Bundle-Localization: plugin
Bundle-Name: %Bundle-Name.0
Bundle-Vendor: %Bundle-Vendor.0{code}
For features, check that your *feature.properties* file contains good values too:
{code}featureName=JMX Console
featureProvider=JBoss by Red Hat{code}
or
{code}featureName=JBoss Archives Tools
providerName=JBoss by Red Hat{code}
Then in your feature.xml files, you will reference these variables like this:
{code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
or
{code}<feature label="%featureName" provider-name="%providerName" ...>{code}
3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
4. If you do not require QE to review your changes, please *Close* this JIRA when done.
5. If you have any questions, please contact [~nickboldt].
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (JBIDE-18023) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Arquillian]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18023:
----------------------------------
Summary: For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Arquillian]
Key: JBIDE-18023
URL: https://issues.jboss.org/browse/JBIDE-18023
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: testing-tools
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.CR1 [Arquillian]: Please perform the following *2* tasks:
1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
Be sure to also include *translated* files, where they exist.
*java files*
{code:title=*.java}
Copyright (c) 2010-2014 Red Hat, Inc. and others.
{code}
*html files*
{code:title=about.html}
© 2014 Red Hat, Inc. All rights reserved
{code}
*properties files*
{code:title=about.properties}
Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
{code}
{code:title=about_fr.properties}
Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
{code}
{code:title=feature.properties}
Copyright (c) 2010-2014 Red Hat, Inc. and others.
{code}
{code:title=Messages.properties}
# Copyright (c) 2014 Red Hat, Inc. and others.
{code}
*xsd files*
{code:title=jboss-as-naming_1_3.xsd}
Copyright 2014, Red Hat, Inc., and individual contributors
{code}
2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
Be sure to also include *translated* files, where they exist.
*This step is particularly important for new plugins and features that have been added recently.*
Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
{code}BundleName = JMX Resources Bundle
BundleProvider = JBoss by Red Hat{code}
or
{code}Bundle-Name.0 = JBossTools Archives Core Plugin
Bundle-Vendor.0 = JBoss by Red Hat{code}
Then in your MANIFEST.MF files, you will reference these variables like this.
*Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
{code}Bundle-Localization: plugin
Bundle-Name: %BundleName
Bundle-Vendor: %BundleProvider{code}
or
{code}Bundle-Localization: plugin
Bundle-Name: %Bundle-Name.0
Bundle-Vendor: %Bundle-Vendor.0{code}
For features, check that your *feature.properties* file contains good values too:
{code}featureName=JMX Console
featureProvider=JBoss by Red Hat{code}
or
{code}featureName=JBoss Archives Tools
providerName=JBoss by Red Hat{code}
Then in your feature.xml files, you will reference these variables like this:
{code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
or
{code}<feature label="%featureName" provider-name="%providerName" ...>{code}
3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
4. If you do not require QE to review your changes, please *Close* this JIRA when done.
5. If you have any questions, please contact [~nickboldt].
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (JBIDE-18024) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Central]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18024:
----------------------------------
Summary: For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Central]
Key: JBIDE-18024
URL: https://issues.jboss.org/browse/JBIDE-18024
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: central, maven, project-examples
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.CR1 [Central]: Please perform the following *2* tasks:
1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
Be sure to also include *translated* files, where they exist.
*java files*
{code:title=*.java}
Copyright (c) 2010-2014 Red Hat, Inc. and others.
{code}
*html files*
{code:title=about.html}
© 2014 Red Hat, Inc. All rights reserved
{code}
*properties files*
{code:title=about.properties}
Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
{code}
{code:title=about_fr.properties}
Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
{code}
{code:title=feature.properties}
Copyright (c) 2010-2014 Red Hat, Inc. and others.
{code}
{code:title=Messages.properties}
# Copyright (c) 2014 Red Hat, Inc. and others.
{code}
*xsd files*
{code:title=jboss-as-naming_1_3.xsd}
Copyright 2014, Red Hat, Inc., and individual contributors
{code}
2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
Be sure to also include *translated* files, where they exist.
*This step is particularly important for new plugins and features that have been added recently.*
Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
{code}BundleName = JMX Resources Bundle
BundleProvider = JBoss by Red Hat{code}
or
{code}Bundle-Name.0 = JBossTools Archives Core Plugin
Bundle-Vendor.0 = JBoss by Red Hat{code}
Then in your MANIFEST.MF files, you will reference these variables like this.
*Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
{code}Bundle-Localization: plugin
Bundle-Name: %BundleName
Bundle-Vendor: %BundleProvider{code}
or
{code}Bundle-Localization: plugin
Bundle-Name: %Bundle-Name.0
Bundle-Vendor: %Bundle-Vendor.0{code}
For features, check that your *feature.properties* file contains good values too:
{code}featureName=JMX Console
featureProvider=JBoss by Red Hat{code}
or
{code}featureName=JBoss Archives Tools
providerName=JBoss by Red Hat{code}
Then in your feature.xml files, you will reference these variables like this:
{code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
or
{code}<feature label="%featureName" provider-name="%providerName" ...>{code}
3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
4. If you do not require QE to review your changes, please *Close* this JIRA when done.
5. If you have any questions, please contact [~nickboldt].
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (JBIDE-18025) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Portlet]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-18025:
----------------------------------
Summary: For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Portlet]
Key: JBIDE-18025
URL: https://issues.jboss.org/browse/JBIDE-18025
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: portal-gatein
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.CR1 [Portlet]: Please perform the following *2* tasks:
1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
Be sure to also include *translated* files, where they exist.
*java files*
{code:title=*.java}
Copyright (c) 2010-2014 Red Hat, Inc. and others.
{code}
*html files*
{code:title=about.html}
© 2014 Red Hat, Inc. All rights reserved
{code}
*properties files*
{code:title=about.properties}
Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
{code}
{code:title=about_fr.properties}
Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
{code}
{code:title=feature.properties}
Copyright (c) 2010-2014 Red Hat, Inc. and others.
{code}
{code:title=Messages.properties}
# Copyright (c) 2014 Red Hat, Inc. and others.
{code}
*xsd files*
{code:title=jboss-as-naming_1_3.xsd}
Copyright 2014, Red Hat, Inc., and individual contributors
{code}
2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
Be sure to also include *translated* files, where they exist.
*This step is particularly important for new plugins and features that have been added recently.*
Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
{code}BundleName = JMX Resources Bundle
BundleProvider = JBoss by Red Hat{code}
or
{code}Bundle-Name.0 = JBossTools Archives Core Plugin
Bundle-Vendor.0 = JBoss by Red Hat{code}
Then in your MANIFEST.MF files, you will reference these variables like this.
*Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
{code}Bundle-Localization: plugin
Bundle-Name: %BundleName
Bundle-Vendor: %BundleProvider{code}
or
{code}Bundle-Localization: plugin
Bundle-Name: %Bundle-Name.0
Bundle-Vendor: %Bundle-Vendor.0{code}
For features, check that your *feature.properties* file contains good values too:
{code}featureName=JMX Console
featureProvider=JBoss by Red Hat{code}
or
{code}featureName=JBoss Archives Tools
providerName=JBoss by Red Hat{code}
Then in your feature.xml files, you will reference these variables like this:
{code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
or
{code}<feature label="%featureName" provider-name="%providerName" ...>{code}
3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
4. If you do not require QE to review your changes, please *Close* this JIRA when done.
5. If you have any questions, please contact [~nickboldt].
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Portlet task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months