July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17890) Command 'cd #/projectname' not implemented in Forge2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17890?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-17890. ------------------------------------- Resolution: Done Implemented > Command 'cd #/projectname' not implemented in Forge2 > ---------------------------------------------------- > > Key: JBIDE-17890 > URL: https://issues.jboss.org/browse/JBIDE-17890 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Pavol Srna > Assignee: George Gastaldi > Fix For: 4.2.0.CR1 > > > I'm missing 'cd #' command in Forge2. > Would it be possible to make the forge "cd" command aware of the eclipse workspace the same way as it is in Forge1? Especially being able to "cd #/projectname" where projectname is *NOT* inside the physical workspace directory. > Remember our recommendation to users is *NOT* to put their projects inside eclipse workspaces thus having just 'cd #' is not really that useful on its own. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17890) Command 'cd #/projectname' not implemented in Forge2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17890?page=com.atlassian.jira.plugi... ] George Gastaldi reassigned JBIDE-17890: --------------------------------------- Assignee: George Gastaldi (was: Lincoln Baxter III) > Command 'cd #/projectname' not implemented in Forge2 > ---------------------------------------------------- > > Key: JBIDE-17890 > URL: https://issues.jboss.org/browse/JBIDE-17890 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Pavol Srna > Assignee: George Gastaldi > Fix For: 4.2.0.CR1 > > > I'm missing 'cd #' command in Forge2. > Would it be possible to make the forge "cd" command aware of the eclipse workspace the same way as it is in Forge1? Especially being able to "cd #/projectname" where projectname is *NOT* inside the physical workspace directory. > Remember our recommendation to users is *NOT* to put their projects inside eclipse workspaces thus having just 'cd #' is not really that useful on its own. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17977) configure markers missing in server adapter context menu

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-17977: ------------------------------------------- Summary: configure markers missing in server adapter context menu Key: JBIDE-17977 URL: https://issues.jboss.org/browse/JBIDE-17977 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen configure markers available from the project context menu should also be accessible from server context menu. seem to have been missed when we aligned the context markers. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17976) Problem markers are not removed on related Parameter Aggregators

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-17976: ------------------------------------- Summary: Problem markers are not removed on related Parameter Aggregators Key: JBIDE-17976 URL: https://issues.jboss.org/browse/JBIDE-17976 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webservices Affects Versions: 4.2.0.Beta3 Reporter: Xavier Coulon Let's have those 2 classes: {code} @Path("/rest") public class RestService { @POST @Path("{id}") public void post(@BeanParam BeanClass bean) { } } {code} and {code} public class BeanClass { @PathParam("id") private Integer id; } {code} if the users changes {{@Path("{id}")}} to {{@Path("{i}")}} in the {{RestService}}, a problem marker will be set on {{@PathParam("id") }} in {{BeanClass}}, which is fine. If the user changes {{@Path("{i}")}} back to {{@Path("{id}")}}, the problem marker is not removed :( -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17976) Problem markers are not removed on related Parameter Aggregators

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17976?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-17976: ---------------------------------- Fix Version/s: 4.2.0.CR1 > Problem markers are not removed on related Parameter Aggregators > ---------------------------------------------------------------- > > Key: JBIDE-17976 > URL: https://issues.jboss.org/browse/JBIDE-17976 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Fix For: 4.2.0.CR1 > > > Let's have those 2 classes: > {code} > @Path("/rest") > public class RestService { > @POST > @Path("{id}") > public void post(@BeanParam BeanClass bean) { > > } > } > {code} > and > {code} > public class BeanClass { > > @PathParam("id") > private Integer id; > > } > {code} > if the users changes {{@Path("{id}")}} to {{@Path("{i}")}} in the {{RestService}}, a problem marker will be set on {{@PathParam("id") }} in {{BeanClass}}, which is fine. > If the user changes {{@Path("{i}")}} back to {{@Path("{id}")}}, the problem marker is not removed :( -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17976) Problem markers are not removed on related Parameter Aggregators

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17976?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-17976: ------------------------------------- Assignee: Xavier Coulon > Problem markers are not removed on related Parameter Aggregators > ---------------------------------------------------------------- > > Key: JBIDE-17976 > URL: https://issues.jboss.org/browse/JBIDE-17976 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > Let's have those 2 classes: > {code} > @Path("/rest") > public class RestService { > @POST > @Path("{id}") > public void post(@BeanParam BeanClass bean) { > > } > } > {code} > and > {code} > public class BeanClass { > > @PathParam("id") > private Integer id; > > } > {code} > if the users changes {{@Path("{id}")}} to {{@Path("{i}")}} in the {{RestService}}, a problem marker will be set on {{@PathParam("id") }} in {{BeanClass}}, which is fine. > If the user changes {{@Path("{i}")}} back to {{@Path("{id}")}}, the problem marker is not removed :( -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17890) Command 'cd #/projectname' not implemented in Forge2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17890?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-17890: ------------------------------------ Issue Type: Feature Request (was: Enhancement) > Command 'cd #/projectname' not implemented in Forge2 > ---------------------------------------------------- > > Key: JBIDE-17890 > URL: https://issues.jboss.org/browse/JBIDE-17890 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Pavol Srna > Assignee: Lincoln Baxter III > Fix For: 4.2.0.CR1 > > > I'm missing 'cd #' command in Forge2. > Would it be possible to make the forge "cd" command aware of the eclipse workspace the same way as it is in Forge1? Especially being able to "cd #/projectname" where projectname is *NOT* inside the physical workspace directory. > Remember our recommendation to users is *NOT* to put their projects inside eclipse workspaces thus having just 'cd #' is not really that useful on its own. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17964) add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17964?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17964: ------------------------------------ Would it not simply be the list of features contained here, when you browse it in Eclipse or with the p2-browser? https://devstudio.jboss.com/updates/7.0/integration-stack/ > add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric > ------------------------------------------------------------------------------------------ > > Key: JBIDE-17964 > URL: https://issues.jboss.org/browse/JBIDE-17964 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 4.1.2.Final > Reporter: Lars Heinemann > Assignee: Nick Boldt > Fix For: 4.1.2.Final > > > Currently when people search the marketplace for Fuse, Fabric, Fabric8 or Camel they don't find JBoss products. We should add those keywords to JBT and JBDS. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17536) JBoss Tools Core Nightly update site fails to install if a new build is published during install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17536?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17536: ------------------------------------ How? With *SCIENCE!* :D It's a SYMLINK (not a composite) to http://download.jboss.org/jbosstools/builds/nightly/core/master/ which contains all the latest builds for that stream, and an auto-generated pair of composite*.xml files pointing into their update site folders (*/all/repo/). > JBoss Tools Core Nightly update site fails to install if a new build is published during install > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17536 > URL: https://issues.jboss.org/browse/JBIDE-17536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > When you install JBT nightly from http://download.jboss.org/jbosstools/updates/nightly/core/master/ into Eclipse and during the build, a new nightly build replaces the old one, you can get a failure like this: > {code}http://download.jboss.org/jbosstools/updates/nightly/core/master/features/org.jboss.tools.wtp.runtimes.tomcat.feature_1.1.0.Beta3-v20140603-0027-B526.jar cannot be found{code} > This is because during your install, the old jars were replaced with the new jars, i.e. different filenames. > I'm not sure if it's something we really need to fix, it's open for discussion. But it happened to me yesterday and it wasn't the first time, so I'm throwing it on the table. > Nick offered this alternative: > install from a specific build folder instead of the "latest nightly" > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > But obviously that's just a workaround, not a real solution. > One way this could be achieved is this: plugins/ and features/ would contain jars from both the latest and previous builds. This way if you start installing (latest=build N) and in the middle of your installation there is a new build (N+1), there would still be jars for both N and N+1 builds. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17000) Show in -> Forge Console option disappeared

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17000?page=com.atlassian.jira.plugi... ] George Gastaldi reassigned JBIDE-17000: --------------------------------------- Assignee: George Gastaldi (was: Koen Aers) > Show in -> Forge Console option disappeared > ------------------------------------------- > > Key: JBIDE-17000 > URL: https://issues.jboss.org/browse/JBIDE-17000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta1 > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.2.0.CR1 > > > Show in -> Forge Console option disappeared -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 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 July 2014