[JBoss JIRA] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3598:
----------------------------------
With Len's +1, I've pushed this to 4.3.x, and a similar change to master.
> Error while building Jboss developer studio 9.1.0 Beta 2 from source
> --------------------------------------------------------------------
>
> Key: JBDS-3598
> URL: https://issues.jboss.org/browse/JBDS-3598
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.1.0.Beta2
> Environment: RHEL 7.1 PPC64le and Ubuntu x86_64
> Maven - 3.3.9
> JDK - 1.8
> Reporter: Deepali Chourasia
> Assignee: Nick Boldt
> Labels: respin-c
> Fix For: 9.1.0.GA
>
> Attachments: Jboss_devstudio_9.1.0_Beta2_buildlog.txt
>
>
> I have downloaded jboss-devstudio-9.1.0.Beta2-src.zip and am building it from source.
> The build fails with the following error:
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-3598.
------------------------------
Resolution: Done
> Error while building Jboss developer studio 9.1.0 Beta 2 from source
> --------------------------------------------------------------------
>
> Key: JBDS-3598
> URL: https://issues.jboss.org/browse/JBDS-3598
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.1.0.Beta2
> Environment: RHEL 7.1 PPC64le and Ubuntu x86_64
> Maven - 3.3.9
> JDK - 1.8
> Reporter: Deepali Chourasia
> Assignee: Nick Boldt
> Labels: respin-c
> Fix For: 9.1.0.GA
>
> Attachments: Jboss_devstudio_9.1.0_Beta2_buildlog.txt
>
>
> I have downloaded jboss-devstudio-9.1.0.Beta2-src.zip and am building it from source.
> The build fails with the following error:
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3598) Error while building Jboss developer studio 9.1.0 Beta 2 from source
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3598?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3598:
----------------------------------
PR to adjust the source zip doc again.
https://github.com/jbdevstudio/jbdevstudio-product/pull/373
> Error while building Jboss developer studio 9.1.0 Beta 2 from source
> --------------------------------------------------------------------
>
> Key: JBDS-3598
> URL: https://issues.jboss.org/browse/JBDS-3598
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.1.0.Beta2
> Environment: RHEL 7.1 PPC64le and Ubuntu x86_64
> Maven - 3.3.9
> JDK - 1.8
> Reporter: Deepali Chourasia
> Assignee: Nick Boldt
> Labels: respin-c
> Fix For: 9.1.0.GA
>
> Attachments: Jboss_devstudio_9.1.0_Beta2_buildlog.txt
>
>
> I have downloaded jboss-devstudio-9.1.0.Beta2-src.zip and am building it from source.
> The build fails with the following error:
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin (default-package-plugin) on project com.jboss.devstudio.core: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-package-plugin of goal org.eclipse.tycho:tycho-packaging-plugin:0.24.0:package-plugin failed: One of setGitDir or setWorkTree must be called.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21857:
-------------------------------------
I've replicated this exact same behavior on oracle jdk 1.8.0_31, so seems pretty consistant here.
The real problem is, I can't think of any way to ensure that the given class is "reached" via some execution path on the server. There's no real way to know (at the hcr level) when or how the class is used and how it might be reached to force a reload on the server.
Again, hitting the gc repeadetly has no effect (even after a module republish) unless i've somehow gotten the server to load the new class. Republishing the old module doesn't seem to do anything until the code path is reached.
In fact, here's another path that fails in a unique way:
1) Change method signature,
2) "Continue" when hcr dialog comes up (ie ignore the error)
3) In server view, UNPUBLISH the module
4) wait a bit, hit the GC in jmx ui a few times
5) in editor, try to make a non-breaking change to the file (change a string)
6) Note hcr dialog re-appears.
In this case, the hcr dialog comes up again, even though the file we're changing is part of a module that is no longer published on the server. Even if I reload the webpage (and get a 404 of course) and then hit the GC 5 more times, and THEN make a non-breaking change to the file again, the HCR dialog will continue to show up.
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21857:
-------------------------------------
After a lot of testing, there's only a few ways I can replicate this patch actually successfully working. Tested on linux using java-1.8.0-openjdk-1.8.0.65-3.b17.fc21.x86_64, I get the following results:
1) I can make internal method changes all day long and there's no error
2) If I change a signature, and redeploy the application, then:
a) No matter how many times I garbage collect, or how much time I wait, further changes will always continue to show the hcr-error dialog
UNLESS, b) I refresh the page that actually uses the class, wait about 3-5 seconds, and then garbage collect 2x via JMX UI.
So basically, even though I've republished the module, and even though the server should have theoretically gotten rid of all old references, it seems to me that somehow it's still holding on to the old class until someone actually comes in and refreshes the page.
[~tmader], any ideas on this? Is this something you can verify?
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20937) Create resource(s) from json
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20937:
-------------------------------------
I'll put my comments from JBIDE-22146 here:
There should be a Create Resource menu at the Connection and Project levels in the openshift explorer. A wizard would need to provide something like:
- selected project (with link to project management)
- input field + browse workspace / filesystem (similar to local template mgmt)
The input field should also accept URLs (which we should also add to the template mgt BTW)
There might be some options from the oc create command to expose to the UI (I haven't checked).
It looks like this new wizard has a lot in common with the local template tab of the new app wizard, so there's probably room for some refactoring here.
[~jeffmaury], you can ask [~jcantrill] or me if you have any questions
> Create resource(s) from json
> ----------------------------
>
> Key: JBIDE-20937
> URL: https://issues.jboss.org/browse/JBIDE-20937
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR2
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png
>
>
> It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json"
> Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json).
> This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3793) On Windows 10 (4K Display), installer dialogs are too small and cannot be resized
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3793?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3793:
---------------------------------
Summary: On Windows 10 (4K Display), installer dialogs are too small and cannot be resized (was: On Windows 10, installer dialogs are too small and cannot be resized)
> On Windows 10 (4K Display), installer dialogs are too small and cannot be resized
> ---------------------------------------------------------------------------------
>
> Key: JBDS-3793
> URL: https://issues.jboss.org/browse/JBDS-3793
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Version: 9.1.0.GA
> Build id: GA-v20160410-1849-B495
> Build date: 20160410-1849
> Windows 10
> 4K Display
> Reporter: Len DiMaggio
> Attachments: installer.png
>
>
> See the attached screenshot - This issue has been raised before regarding the default size used for the JBDS IDE display - the issues that are specific to the JBDS installer is that the small sized dialogs obscure user-editable fields and and that the dialogs cannot be resized.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years