[JBoss JIRA] (JBIDE-19796) Forge editor changes are not applied after changing font preferences
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19796?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-19796:
-----------------------------------
AFAICS the "Forge Console Font" from the "Forge" category is a remainder of the F1 support and currently not used in the F2 related console. The font used in the F2 console is called "Aesh Console Font" and taken from the "Aesh" category. I have done some work so that changing the preferences for this font (or the main Console Font) are now immediately reflected in the F2 console.
The old "Forge Console Font" should either be removed or else used properly in the F2TextViewer. Using it properly will need some additional refactoring though and I'm not sure if it's worth doing this effort because we want to change the Forge console implementation to use the new shell included in Eclipse anyway. So I have commented out this contribution for now. I'm going to resolve this issue as 'Done' but feel free to reopen it if the fix is not sufficient.
> Forge editor changes are not applied after changing font preferences
> --------------------------------------------------------------------
>
> Key: JBIDE-19796
> URL: https://issues.jboss.org/browse/JBIDE-19796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.3.0.Alpha2
> Reporter: George Gastaldi
> Assignee: Koen Aers
> Fix For: 4.3.x
>
>
> 1. Start the Forge console
> 2. Go to Eclipse Settings -> General -> Appearance -> Colors and Fonts
> 3. Choose the _Forge Console Font_ under the Forge category
> 4. Apply changes
> 5. Forge console editor should have been changed to match your settings, but it does not.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18772:
----------------------------------------
{quote}But isn't what you did in https://github.com/jbosstools/jbosstools-integration-tests/pull/990 basically copying the whole profile?{quote}
Yes, and in later commits, I changed it to re-use what is defined in the parent pom. The change only *adds* an additional deploy steps compared to what is in the parent pom, but still consume the deploy-to-jboss.org profile from parent.
{quote}Integration tests inherit the parent pom, whereas RedDeer doesn't. Does RedDeer need anything more than what you did for integration tests?{quote}
Yes, I believe RedDeer has to copy the deploy-to-jboss.org profile that is in parent pom.
> Include publish steps in pom files
> ----------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
> Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19554) Show actual error for target-platform validation error in maven build
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19554?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19554:
----------------------------------------
Resolved upstream: https://git.eclipse.org/r/49345
That will be in Tycho 0.24 or so (not soon).
> Show actual error for target-platform validation error in maven build
> ----------------------------------------------------------------------
>
> Key: JBIDE-19554
> URL: https://issues.jboss.org/browse/JBIDE-19554
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, upstream
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
>
> Currently error is printed out only with -X maven option. To findout what is the problem build have be executed twice in case of error:
> 1. Normal maven call - you see the message
> {code}[INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4....
> [INFO] Failed, see Error log below
> [ERROR] Validation found errors in 1 .target files:
> Could not resolve content of jbdevstudio-unified.target{code}
> 2. Run with -X and you get the error details
> {code}Could not resolve content of jbdevstudio-unified.target
> org.eclipse.tycho.core.ee.shared.BuildFailureException: Failed to resolve target definition /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target: Could not find "org.eclipse.jetty.http/8.1.14.v20131031" in the repositories of the current location
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:99)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.resolveFromArguments(TargetDefinitionResolverService.java:70)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.getTargetDefinitionContent(TargetDefinitionResolverService.java:60)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.resolveTargetDefinitions(TargetPlatformFactoryImpl.java:213)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:153)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:126)
> at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveMetadata(P2ResolverImpl.java:130)
> at org.eclipse.tycho.extras.tpvalidator.TPValidationMojo.validateTarget(TPValidationMojo.java:135)
> at org.eclipse.tycho.extras.tpvalidator.TPValidationMojo.execute(TPValidationMojo.java:83)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 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:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 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.eclipse.tycho.p2.target.facade.TargetDefinitionResolutionException: Could not find "org.eclipse.jetty.http/8.1.14.v20131031" in the repositories of the current location
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver$LoadedIULocation.findUnitInThisLocation(TargetDefinitionResolver.java:313)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver$LoadedIULocation.getRootIUs(TargetDefinitionResolver.java:303)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver$ResolverRun.addLocation(TargetDefinitionResolver.java:155)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContentWithExceptions(TargetDefinitionResolver.java:121)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:94)
> ... 29 more
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 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:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 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.MojoExecutionException: Validation found errors in 1 .target files:
> Could not resolve content of jbdevstudio-unified.target
> org.eclipse.tycho.core.ee.shared.BuildFailureException: Failed to resolve target definition /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target: Could not find "org.eclipse.jetty.http/8.1.14.v20131031" in the repositories of the current location
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:99)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.resolveFromArguments(TargetDefinitionResolverService.java:70)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.getTargetDefinitionContent(TargetDefinitionResolverService.java:60)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.resolveTargetDefinitions(TargetPlatformFactoryImpl.java:213)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:153)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:126)
> at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveMetadata(P2ResolverImpl.java:130)
> at org.eclipse.tycho.extras.tpvalidator.TPValidationMojo.validateTarget(TPValidationMojo.java:135)
> at org.eclipse.tycho.extras.tpvalidator.TPValidationMojo.execute(TPValidationMojo.java:83)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> 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:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 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.eclipse.tycho.p2.target.facade.TargetDefinitionResolutionException: Could not find "org.eclipse.jetty.http/8.1.14.v20131031" in the repositories of the current location
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver$LoadedIULocation.findUnitInThisLocation(TargetDefinitionResolver.java:313)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver$LoadedIULocation.getRootIUs(TargetDefinitionResolver.java:303)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver$ResolverRun.addLocation(TargetDefinitionResolver.java:155)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContentWithExceptions(TargetDefinitionResolver.java:121)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:94)
> ... 29 more
> at org.eclipse.tycho.extras.tpvalidator.TPValidationMojo.execute(TPValidationMojo.java:95)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19907) Default options to start a Docker container
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19907?page=com.atlassian.jira.plugi... ]
Xavier Coulon closed JBIDE-19907.
---------------------------------
Assignee: Xavier Coulon
Release Notes Text: Won't fix since the "Run Image" wizard was fully rewritten and merged just after you reported this bug.
Resolution: Out of Date
> Default options to start a Docker container
> -------------------------------------------
>
> Key: JBIDE-19907
> URL: https://issues.jboss.org/browse/JBIDE-19907
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: docker
> Reporter: Arun Gupta
> Assignee: Xavier Coulon
>
> Starting a Docker container from Docker Images tab does not have stdin, stdout, stderr attached. Also, TTY is not assigned.
> These mimic "-it" options on CLI and are commonly used for interactively running a container. This should be the default in this tooling as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19906) Disabled Finish button for Create Container
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19906?page=com.atlassian.jira.plugi... ]
Xavier Coulon closed JBIDE-19906.
---------------------------------
Assignee: Xavier Coulon
Release Notes Text: Won't fix since the "Run Image" wizard was fully rewritten and merged just after you reported this bug.
Resolution: Won't Fix
> Disabled Finish button for Create Container
> -------------------------------------------
>
> Key: JBIDE-19906
> URL: https://issues.jboss.org/browse/JBIDE-19906
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker
> Reporter: Arun Gupta
> Assignee: Xavier Coulon
> Attachments: Screen Shot 2015-06-02 at 10.46.11 PM.png
>
>
> Using JBDS 9.0 nightly + Docker Tooling plugins.
> In Docker Images view, select jboss/wildfly:latest image, click on "Create Container" shows the wizard but the Finish button is disabled.
> This is because Memory, Memory Swap, Cpu Shares are initialized as 0. Finish button is enabled after 0 value is removed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19898) Error displayed on initial connection to an OpenShift Server for a new eclipse session
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19898?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-19898:
---------------------------------------
[~adietish] I believe this is related to JBIDE-19905. Recall that basic auth results in a token being aquired by a user. If we are not saving that token or the token is invalid then you will be asked to get a new token, which is what you are seeing here.
> Error displayed on initial connection to an OpenShift Server for a new eclipse session
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-19898
> URL: https://issues.jboss.org/browse/JBIDE-19898
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
> Attachments: existing-connection-1.png, existing-connection-2.png
>
>
> # Create a connection to a v3 instance of openshift
> # Restart Eclipse
> # Open the OpenShift explorer view
> # Expand the previously created connection
> # Notice an error like: "system:anonymous..."
> Is this related to token's not being saved? It should either go through the sequence to establish a new token or connect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ]
Brian Stansberry edited comment on JBIDE-19641 at 6/3/15 8:48 AM:
------------------------------------------------------------------
Just an FYI, I mentioned on the mail thread that the code path for the CLI and what JBIDE is using is the same once it reaches the point where the bits are being pushed to the server (which is where things are stuck.) But it turns out that's not the case; the management op the CLI uses is different.
The CLI actually reads the entire file into memory, Base64 encodes it and sends it to server as a param to the management op. That's really not ideal, as the memory requirements on the client and the server can be really high.
The ServerDeploymentManager stuff JBIDE is using results in sending the bytes out of band to the server. That's a better approach but there may be a problem there.
But to say more I'll need to try out the versions your using.
was (Author: brian.stansberry):
Just an FYI, I mentioned on the mail thread that the code path for the CLI and what JBIDE is using is the same once it reaches the point where the bits are being pushed to the server (which is where things are stuck.) But it turns out that's not the case; the management op the CLI uses is different.
> Big war deployment via management API gets stuck
> ------------------------------------------------
>
> Key: JBIDE-19641
> URL: https://issues.jboss.org/browse/JBIDE-19641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
> Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log
>
>
> When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through.
> This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months