[JBoss JIRA] (JBTIS-296) New BPEL Process wizard should display a warning when user selects a target other than bpelContent folder
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-296?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-296.
-----------------------------------
Hi Bob, you are right. I tested BPEL project creation wizard, where you are allowed to select any content folder.
Note that the BPEL process creation wizard checks the location according to the one specified during project creation (and this is good).
Verified with JBDS-IS 7.0.2.GA / JBTIS 4.1.5.Final
> New BPEL Process wizard should display a warning when user selects a target other than bpelContent folder
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-296
> URL: https://issues.jboss.org/browse/JBTIS-296
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BPEL
> Affects Versions: 4.1.5.Final
> Reporter: Robert (Bob) Brodt
> Assignee: Robert (Bob) Brodt
> Priority: Minor
> Attachments: JBIDE-9044.patch
>
>
> Although the user should be allowed to create a new BPEL process anywhere in the workspace (for e.g. a non-deployable BPEL process file intended to be used for documentation only), the New BPEL Process wizard should display a warning message if the target folder is not bpelContent.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBDS-2847) Java EE 7 Tech Preview
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.... ]
Xavier Coulon commented on JBDS-2847:
-------------------------------------
hello [~mmalina],
You should be able to start working on this issue right now.
Please note that the javaee7 samples on github use Groovy for some tests with Spock (as declared in the parent pom.xml), so you may have issues with Eclipse out-of-the-box. You have two options:
- install the Groovy/JDT plugin
- comment out the maven-compiler-plugin that uses the groovy-eclipse-compiler, so you don't need to install anything on your JBDS
[~maxandersen] also asked that we should test against Wildfly 8.1 using Java 8 (as mentionned in JBDS-2919).
> Java EE 7 Tech Preview
> ----------------------
>
> Key: JBDS-2847
> URL: https://issues.jboss.org/browse/JBDS-2847
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.CR1
>
>
> Successfully/cleanly import the Java EE 7 Samples that have been migrated/ported to Wildfly
> https://github.com/javaee-samples/javaee7-samples
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBTIS-293) Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBTIS-293?page=com.atlassian.jira.plugin.... ]
Lars Heinemann commented on JBTIS-293:
--------------------------------------
Currently reworking Fuse Tooling. Camel-Tooling-Util and the fabric8.io stuff will be mostly dropped and if not they will be embedded in the bundle where needed instead. That could fix the issue. We need to check when I am done with the reorg.
> Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
> -----------------------------------------------------------------------------------------------------
>
> Key: JBTIS-293
> URL: https://issues.jboss.org/browse/JBTIS-293
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Fuse IDE
> Affects Versions: 4.2.0.Alpha1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> If I run eclipse/jbdevstudio -clean (purging the OSGi cache) I don't get this error.
> SESSION 2014-07-30 09:22:59.386 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_60-ea
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.fusesource.ide.branding 4 0 2014-07-30 09:23:05.987
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.branding [975]
> Unresolved requirement: Require-Bundle: org.fusesource.ide.camel.model
> -> Bundle-SymbolicName: org.fusesource.ide.camel.model; bundle-version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"
> org.fusesource.ide.camel.model [977]
> No resolution report for the bundle. Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"] because it is exposed to package 'javax.xml.bind.annotation.adapters' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
> Chain 1:
> org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
> require: (osgi.wiring.bundle=org.eclipse.core.runtime)
> |
> provide: osgi.wiring.bundle: org.eclipse.core.runtime
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140606-1445"; singleton:="true"]
> Chain 2:
> org.fusesource.ide.branding [osgi.identity; osgi.identity="org.fusesource.ide.branding"; type="osgi.bundle"; version:Version="7.3.0.v20140729-2156-H292-MASTER"; singleton:="true"]
> import: (osgi.wiring.package=org.fusesource.camel.tooling.util)
> |
> export: osgi.wiring.package=org.fusesource.camel.tooling.util; uses:=org.apache.camel.model
> io.fabric8.camel-tooling-util [osgi.identity; osgi.identity="io.fabric8.camel-tooling-util"; type="osgi.bundle"; version:Version="1.0.0.redhat-379"]
> import: (&(osgi.wiring.package=org.apache.camel.model)(&(version>=2.12.0)(!(version>=3.0.0))))
> |
> export: osgi.wiring.package=org.apache.camel.model; uses:=javax.xml.bind.annotation.adapters
> org.apache.camel.camel-core [osgi.identity; osgi.identity="org.apache.camel.camel-core"; type="osgi.bundle"; version:Version="2.12.0.redhat-610379"]
> import: (osgi.wiring.package=javax.xml.bind.annotation.adapters)
> |
> export: osgi.wiring.package: javax.xml.bind.annotation.adapters
> javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBDS-3058) Workaround to JBDS-3054 causes the blank/white welcome screen bug to return
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3058?page=com.atlassian.jira.plugin.... ]
Len DiMaggio resolved JBDS-3058.
--------------------------------
Fix Version/s: 8.0.0.Beta3
Resolution: Done
> Workaround to JBDS-3054 causes the blank/white welcome screen bug to return
> ---------------------------------------------------------------------------
>
> Key: JBDS-3058
> URL: https://issues.jboss.org/browse/JBDS-3058
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: welcome
> Affects Versions: 8.0.0.Beta2
> Environment: JBDS 8.0.beta2.respin-a
> RHEL 6.5
> OpenJDK 1.7
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Fix For: 8.0.0.Beta3
>
> Attachments: workaround_bug.png
>
>
> If the workaround defined in JBDS-3054 is used (-Dorg.jboss.tools.vpe.loadxulrunner=false), then the welcome screen becomes blank. See attached screenshot.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17498) Can't run default hybrid project on device
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17498?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-17498:
--------------------------------------
[~ibuziuk] On device adb acts as a mediator so it is not affected. adb has its own problems and sometimes it never returns any result or does not connect, which keeps our tools waiting.
> 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)
11 years, 8 months