[JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs
by Mikhail Kalkov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugi... ]
Mikhail Kalkov commented on JBIDE-22878:
----------------------------------------
By the way, with this test-ear project and Developer Studio 8.1.0.GA I reliably get JBIDE-18697 reproduced. So, I don't think it was really fixed in 4.2.1.
> EAR deployed from DevStudio to EAP contains errorneously named ejbs
> -------------------------------------------------------------------
>
> Key: JBIDE-22878
> URL: https://issues.jboss.org/browse/JBIDE-22878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Final, 4.4.0.Final
> Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime.
> Reporter: Mikhail Kalkov
> Attachments: screendump.png, test-projects.zip
>
>
> I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar.
> When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot.
> This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml and remember to revert this change before committing!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22879) JavaEE jars files are built with another java version than used for compilation
by Mikhail Kalkov (JIRA)
Mikhail Kalkov created JBIDE-22879:
--------------------------------------
Summary: JavaEE jars files are built with another java version than used for compilation
Key: JBIDE-22879
URL: https://issues.jboss.org/browse/JBIDE-22879
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.0.Final, 4.2.3.Final
Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime.
Reporter: Mikhail Kalkov
Attachments: test-projects.zip
I have installed system-wide JRE 8 in order to run all java applications with it. At the same time, out target platform is still based on Java 7 and that's why I've also downloaded JDK 7 and set JAVA_HOME path to it.
When I build test-ejb project from attached zip file on command line, maven both compiles and packages it with JDK 7 obtained from JAVA_HOME. When I build the same project with JBoss Developer Studio which was configured via Window > Preferences > Java > Installed JREs to use JDK 7 by default, class files get version 51 (java 7) but Build-Jdk stanza in MANIFEST.MF is set to 1.8.0_102 instead of 1.7. I've also observed that test-ear project is also packaged with Java 8 instead of Java 7.
This is not a big issue but is a bit worrying since for example jar tool from JDK 8 may contains bugfixes not present in JDK 7. This also makes me think that other tools may be fetched from wrong JDK version. Finally, I'm not even sure whether this is a JBoss Tools, Eclipse WTP or Eclipse M2E issue but it is clearly present in the latest stock version of JBoss Developer Studio.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs
by Mikhail Kalkov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugi... ]
Mikhail Kalkov updated JBIDE-22878:
-----------------------------------
Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime. (was: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedde Maven installation and JBoss EAP 6.4 target runtime.)
> EAR deployed from DevStudio to EAP contains errorneously named ejbs
> -------------------------------------------------------------------
>
> Key: JBIDE-22878
> URL: https://issues.jboss.org/browse/JBIDE-22878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Final, 4.4.0.Final
> Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target runtime.
> Reporter: Mikhail Kalkov
> Attachments: screendump.png, test-projects.zip
>
>
> I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar.
> When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot.
> This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml and remember to revert this change before committing!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs
by Mikhail Kalkov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugi... ]
Mikhail Kalkov updated JBIDE-22878:
-----------------------------------
Description:
I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar.
When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot.
This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml and remember to revert this change before committing!
was:
I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar.
When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot.
> EAR deployed from DevStudio to EAP contains errorneously named ejbs
> -------------------------------------------------------------------
>
> Key: JBIDE-22878
> URL: https://issues.jboss.org/browse/JBIDE-22878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Final, 4.4.0.Final
> Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedde Maven installation and JBoss EAP 6.4 target runtime.
> Reporter: Mikhail Kalkov
> Attachments: screendump.png, test-projects.zip
>
>
> I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar.
> When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot.
> This problem makes it extremely difficult to debug issues that arise only with zipped ear deployments. The only workaround is to comment out bundleFileName lines in test-ear pom.xml and remember to revert this change before committing!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs
by Mikhail Kalkov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22878?page=com.atlassian.jira.plugi... ]
Mikhail Kalkov updated JBIDE-22878:
-----------------------------------
Steps to Reproduce:
* Download JBoss Developer Studio 10.0.0.GA
* Add JBoss EAP 6.4 runtime to the studio.
* Unzip attached test-project.zip into workspace
* In Studio, use import existing projects wizard to import test-ejb and test-ear projects into workspace
* Double-click the server in Servers view, select "Deployment" tab and check "Deploy projects as compressed archives"
* Add test-ear to the server, right-click on the server and select "Clean".
* Now navigate to the deployments directory and inspect test-ear.ear contents. Compare this file to to test-ear.ear obtained from command-line maven build or via Export EAR Eclipse wizard.
Attachment: test-projects.zip
Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedde Maven installation and JBoss EAP 6.4 target runtime. (was: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with JBoss EAP 6.4 target runtime.)
> EAR deployed from DevStudio to EAP contains errorneously named ejbs
> -------------------------------------------------------------------
>
> Key: JBIDE-22878
> URL: https://issues.jboss.org/browse/JBIDE-22878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.3.Final, 4.4.0.Final
> Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with embedde Maven installation and JBoss EAP 6.4 target runtime.
> Reporter: Mikhail Kalkov
> Attachments: screendump.png, test-projects.zip
>
>
> I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar.
> When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22878) EAR deployed from DevStudio to EAP contains errorneously named ejbs
by Mikhail Kalkov (JIRA)
Mikhail Kalkov created JBIDE-22878:
--------------------------------------
Summary: EAR deployed from DevStudio to EAP contains errorneously named ejbs
Key: JBIDE-22878
URL: https://issues.jboss.org/browse/JBIDE-22878
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.0.Final, 4.2.3.Final
Environment: I've observed this problem on a Win7 64 bit machine with Oracle JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA when used in conjunction with JBoss EAP 6.4 target runtime.
Reporter: Mikhail Kalkov
Attachments: screendump.png
I've created a maven-based EAR project that contains serveral ejb modules some of which come from workspace whereas others are downloaded from binary artifact repository. All modules have bundleFileName specified as module-name.jar in order to override the default module-name-version.jar.
When I right-click on an EAR project and choose Export..., a correct EAR file is built, which looks exactly the same as when I build it from command line. However, when I add this project to an EAP 6.4 server, and check "Deploy projects as compressed archives" option, an EAR with erroneously named ejbs is deployed. the bundleFileName option is namely ignored for EJBs that come from binary artifact repository. See attached screenshot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22848) Application Wizard: NPE is thrown when closing the wizard and Create OpenShift Project shell
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22848?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22848:
---------------------------------------
[~adietish] well, "only" concern is duration of tests. At the moment there are almost no places where sometimes like this is implemented (active error check). Usually, when a wizard/shell is closed and something unexpected occurs, test fails on clean up, if there was an error dialog. And then I find out that something is wrong and its easily traceable. If an error is silent (only in error log), its not processed. We are going to implement a new feature in RedDeer - log collector after each test https://github.com/jboss-reddeer/reddeer/issues/1436 I would wait for it.
> Application Wizard: NPE is thrown when closing the wizard and Create OpenShift Project shell
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-22848
> URL: https://issues.jboss.org/browse/JBIDE-22848
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.1.AM3
>
>
> There is a prompt to create a new project, if there is no project under an OpenShift 3 connection and New OpenShift Application wizard is opened. If I close popped up shell Create OpenShift Project, also New App wizard is closed and following NPE is shown. This is happening only when opening the wizard through context menu in OpenShift Explorer. Wizards opened via central/shell menu leave New App wizard opened upon cancellation/closing of Create OpenShift Project shell.
> {code}
> org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:64)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:454)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:482)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.setConnection(NewApplicationWizard.java:292)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizard.init(NewApplicationWizard.java:98)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:281)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> ... 37 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22294) Build Configuration: Git Source section is cropped on OSX
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22294?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22294.
---------------------------------
I just checked again with devstudio 10.1.0.AM3 B5682 and I can confirm that it still works the same as reported by me previously - default window size is big enough, so it will be fine in most case, i.e. "good enough". Closing.
> Build Configuration: Git Source section is cropped on OSX
> ---------------------------------------------------------
>
> Key: JBIDE-22294
> URL: https://issues.jboss.org/browse/JBIDE-22294
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.4.1.AM3
>
>
> After creating a new openshift application, selecting a builder image, then on the next page:
> !http://content.screencast.com/users/fbricon/folders/Jing/media/5e21b5d7-9cb1-43cf-bfe9-05c1ef6e0dad/00000404.png|width=800!
> Context directory field / label are cropped.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22877) Update RedDeer in TP for JBT 4.4.1.AM3
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22877?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-22877:
----------------------------------
Description:
Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP.
You can simply take the latest from http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master/ . Let me know if it's better for you if I copy it somewhere else using the rsync job or if this is sufficient.
Please make sure to copy the RedDeer UI feature as well as it seems to have been missing last time: JBIDE-22857 (I'm not sure how that happened.)
Once this is done, it should be available on the current TP within a day?
was:
Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bit in our TP.
You can simply take the latest from http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master/ . Let me know if it's better for you if I copy it somewhere else using the rsync job or if this is sufficient.
Please make sure to copy the RedDeer UI feature as well as it seems to have been missing last time: JBIDE-22857 (I'm not sure how that happened.)
Once this is done, it should be available on the current TP within a day?
> Update RedDeer in TP for JBT 4.4.1.AM3
> --------------------------------------
>
> Key: JBIDE-22877
> URL: https://issues.jboss.org/browse/JBIDE-22877
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.4.1.AM3
>
>
> Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP.
> You can simply take the latest from http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master/ . Let me know if it's better for you if I copy it somewhere else using the rsync job or if this is sufficient.
> Please make sure to copy the RedDeer UI feature as well as it seems to have been missing last time: JBIDE-22857 (I'm not sure how that happened.)
> Once this is done, it should be available on the current TP within a day?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months