December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23641) Jboss AS Eclipse plugin freezes STS on Mac OS Sierra

by fede pia (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23641?page=com.atlassian.jira.plugi... ] fede pia edited comment on JBIDE-23641 at 12/14/16 11:01 AM: ------------------------------------------------------------- [~mmalina], I could solve this by installing an older version of the full JBoss Web bundle: {noformat} JBossAS Tools 3.0.3.Final-v20150325-0035-B129 org.jboss.ide.eclipse.as.feature.feature.group JBoss by Red Hat {noformat} However, I can't risk to bork my environment for the moment again since have multiple projects going on. was (Author: fedepia): [~mmalina], I could solve this by installing an older version of the full JBoss Web bundle: {noformat} JBossAS Tools 3.0.3.Final-v20150325-0035-B129 org.jboss.ide.eclipse.as.feature.feature.group JBoss by Red Hat {noformat} However, I can't risk to bork my environment for the moment again since have multiple projects going on. > Jboss AS Eclipse plugin freezes STS on Mac OS Sierra > ---------------------------------------------------- > > Key: JBIDE-23641 > URL: https://issues.jboss.org/browse/JBIDE-23641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.3.AM1 > > Attachments: eclipse.log > > > When installing Jboss Tool 4.4.2 (only Jboss AS plugin) in Spring Tool Suite in a Mac, the Eclipse hangs up and needs to be killed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20300) As a user I would like to hot deploy my application to shorten the development cycle

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20300?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20300: ---------------------------------------- Assignee: Andre Dietisheim > As a user I would like to hot deploy my application to shorten the development cycle > ------------------------------------------------------------------------------------ > > Key: JBIDE-20300 > URL: https://issues.jboss.org/browse/JBIDE-20300 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Fix For: 4.4.2.Final > > > As a developer, it would be nice to compile locally and sync the changes with an existing deployment of my application to shorten my code/test/deploy cycle. I'm not sure how feasible this is in v3. > * There may be a way to copy changed files to a running pod, but these changes would be lost if the pod is bounced unless there is persistent storage > * Where do the files get copied to? How do find this information out? An agreed location based on an annotation? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23641) Jboss AS Eclipse plugin freezes STS on Mac OS Sierra

by fede pia (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23641?page=com.atlassian.jira.plugi... ] fede pia commented on JBIDE-23641: ---------------------------------- [~mmalina], I could solve this by installing an older version of the full JBoss Web bundle: {{ JBossAS Tools 3.0.3.Final-v20150325-0035-B129 org.jboss.ide.eclipse.as.feature.feature.group JBoss by Red Hat}} However, I can't risk to bork my environment for the moment again since have multiple projects going on. > Jboss AS Eclipse plugin freezes STS on Mac OS Sierra > ---------------------------------------------------- > > Key: JBIDE-23641 > URL: https://issues.jboss.org/browse/JBIDE-23641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.3.AM1 > > Attachments: eclipse.log > > > When installing Jboss Tool 4.4.2 (only Jboss AS plugin) in Spring Tool Suite in a Mac, the Eclipse hangs up and needs to be killed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20346) Jts quickstart (EAP 6.4) contains XML validation errors

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20346?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20346: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.x) > Jts quickstart (EAP 6.4) contains XML validation errors > ------------------------------------------------------- > > Key: JBIDE-20346 > URL: https://issues.jboss.org/browse/JBIDE-20346 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.0.Beta2 > Environment: JBDS 9.0.0.Beta2 > Reporter: Radim Hopp > Fix For: 4.4.3.AM1 > > > jts quickstart contains XML validation errors after import: > {noformat} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected. jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 30 XML Problem > {noformat} > {noformat} > Referenced file contains errors (jar:file:/home/rhopp/eclipse/jbdevstudio-9.0.0.Beta2/studio/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150716-2030-B26.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 1 XML Problem > {noformat} > The same error was once reported in JBIDE-17871, but that jira was closed as duplicate (of JBIDE-12990), but this error is not in the original (JBIDE-12990) issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20300) As a user I would like to hot deploy my application to shorten the development cycle

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20300?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-20300. ------------------------------ Resolution: Done > As a user I would like to hot deploy my application to shorten the development cycle > ------------------------------------------------------------------------------------ > > Key: JBIDE-20300 > URL: https://issues.jboss.org/browse/JBIDE-20300 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Fix For: 4.4.x > > > As a developer, it would be nice to compile locally and sync the changes with an existing deployment of my application to shorten my code/test/deploy cycle. I'm not sure how feasible this is in v3. > * There may be a way to copy changed files to a running pod, but these changes would be lost if the pod is bounced unless there is persistent storage > * Where do the files get copied to? How do find this information out? An agreed location based on an annotation? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20262) Explorer: Manually trigger builds from the connection or project level

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20262?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20262: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Explorer: Manually trigger builds from the connection or project level > ---------------------------------------------------------------------- > > Key: JBIDE-20262 > URL: https://issues.jboss.org/browse/JBIDE-20262 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Labels: explorer, help_wanted, openshift_v3 > Fix For: 4.5.0.AM1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Add selection dialog to allow you to choose a build config from which to start a build by right-clicking on a connection or project. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20125) Import wizard, application wizard: use easy import, not our custom facility

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20125?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20125: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Import wizard, application wizard: use easy import, not our custom facility > --------------------------------------------------------------------------- > > Key: JBIDE-20125 > URL: https://issues.jboss.org/browse/JBIDE-20125 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.5.0.AM1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The current impl of the import wizard in v2 and v3 is using a custom import logic where it launches m2e for repositories that have a pom.xml and "General project" for all the others. In JBDS-3285 [~mickael_istria] contributed a new Easy import facility for Eclipse that we should use instead of our own minimalistic, custom made approach -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20153) Docker server adapter

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20153?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20153: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Docker server adapter > --------------------- > > Key: JBIDE-20153 > URL: https://issues.jboss.org/browse/JBIDE-20153 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.0.AM1 > > > I've been wondering for a time what would be the best way to integrate docker with our server adapters. > I initially first thought it should be an additional profile to the existing local or remote profiles - but I think that option actually ends up being too limiting. To start - the server inside the docker then is assumed to always be a wildfly server; and I think for docker that is too limiting. > Watching Eclipse Che demo at EclipseCon I realized their approach for "Runners" actually fits perfectly. > What they do is that they don't actually have any insight into what servers they are running - they simply just have an associated DockerFile for a "runner" which they build and then run before launching. > Once launched they then know where the server port is, where the possible debug port is, where files are mounted etc. > So this Docker Server Adapter can be made to run *any* kind of application. > WildFly, Tomcat, Python, even plain java apps. > And actually it is not just a DockerFile that is associated with the run but a templated dockerfile. A file where certain variables will be replaced; like: > {code} > VOLUME /deployments > ADD $app$ /deployments > {code} > will add the packaged app (i.e. wonka.war) into the /deployments folder and /deployments is mounted. > And actually the /deployments can then be updated incrementally if wanted to. > Even greater is that if we could support the same syntax and semantics of the templating we can simply reuse the templates defined by Che at https://github.com/codenvy/dockerfiles/ > You can see more complete info on what codenvy/che does http://docs.codenvy.com/user/builders-and-runners/#custom-machines > This would cover all the usecases I can currently think of with launching docker from eclipse - but not be tied to any specific server type. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20060) Connection wizard: cannot store v2 connections to default host, they always get stored as non-default

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20060?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20060: ------------------------------- Fix Version/s: LATER (was: 4.4.x) > Connection wizard: cannot store v2 connections to default host, they always get stored as non-default > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-20060 > URL: https://issues.jboss.org/browse/JBIDE-20060 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Fix For: LATER > > Attachments: default-host.png, non-default-host.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20063) locked up machine with "Loading descriptor" ...

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20063?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20063: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.x) > locked up machine with "Loading descriptor" ... > ----------------------------------------------- > > Key: JBIDE-20063 > URL: https://issues.jboss.org/browse/JBIDE-20063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.4.3.AM1 > > > when loaded javaee7-samples I ended up with frozen eclipse showing this: > https://www.dropbox.com/s/ttx9ppieads5m7n/Screenshot%202015-06-13%2001.31... > its so frozen I cannot even get a stacktrace from jps. > I tried looking for "Loading descriptor" in common and batch but no luck so maybe it is not in batch this is happening but something is definitely locking up ;/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2016