September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15476) Allow users to provide downloadble cartidges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15476?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15476: ------------------------------------- Attachment: add-downloadable-cartridge.png > Allow users to provide downloadble cartidges > -------------------------------------------- > > Key: JBIDE-15476 > URL: https://issues.jboss.org/browse/JBIDE-15476 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.1.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Alpha2 > > Attachments: add-downloadable-cartridge.png > > > OpenShift allows lately to provide your very own cartridge by giving it a git-url where the cartridge source may get cloned from. In the Web-UI this looks as follows: > !add-downloadable-cartridge.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15476) Allow users to provide downloadble cartidges

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-15476: ---------------------------------------- Summary: Allow users to provide downloadble cartidges Key: JBIDE-15476 URL: https://issues.jboss.org/browse/JBIDE-15476 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.1.1.Alpha2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.1.Alpha2 Attachments: add-downloadable-cartridge.png OpenShift allows lately to provide your very own cartridge by giving it a git-url where the cartridge source may get cloned from. In the Web-UI this looks as follows: !add-downloadable-cartridge.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15392: --------------------------------------------- never mind....now I get it. You need the api to work as if you had a real server, but you only have a directory ? If sourcelookup have to mess with "new File(homePath, "server/default").getAbsolutePath();" that leaks alot of knowledge into sourcelookup which just isn't necessary. Wouldn't it be the simplest to be able to create a class that provides all these default settings for the server type based on result from the beanloaders ? And seriously - why can't sourcelookup just know about the runtime and if it does not know about it simply just return all jars ? then all this custom knowledge in sourcelookup goes away ? > Add api in server needed for source lookup > ------------------------------------------ > > Key: JBIDE-15392 > URL: https://issues.jboss.org/browse/JBIDE-15392 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes. > We need to define a stable api that can be used here. > lets outline what api is actually needed and then subjiras for the specifics. > For me it looks like server lookup needs a few things: > 0. know exact version of server > 1. know the file structure of a certain server > 2. get dir or directories that contain jar that is the "runtime" > My guess is that #2 might just be sufficient for source code lookup. > Any comments ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15472) Improve visibility for developers when test failures persist for multiple builds (Jenkins emails are ignored)

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15472?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15472: --------------------------------------- Here are my 2c: - would a new issue be opened for each build failure ? I'd be concerned with the number of issues that would be created, then.. - there's a Jenkins widget that can be installed on user's personal JIRA dashboard. It links to the public jenkins instance (not the private one, sadly) - would the script that generates the issue also closes it if the build becomes stable again ? because otherwise, it would become a real mess to manage in JIRA - it could be usefull if it was triggered after a certain amount of build failures or a certain "quite" time after the last build failure. Like a reminder. Said another way, it should be possible to "stay under the radar" of this script. We sometimes get build failures (nexus/network/disk issues) that don't repeat if we kick another job just after. So there should not be an issue creation for that. IMO, the issue description should just provide links to the tests with failure/errors so that we can quickly get to the problem. No real need to put the whole stacktrace in the description. Those were my 2c ;-) > Improve visibility for developers when test failures persist for multiple builds (Jenkins emails are ignored) > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15472 > URL: https://issues.jboss.org/browse/JBIDE-15472 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > > First iteration: https://issues.jboss.org/browse/JBIDE-15470, as generated by this: https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTestF... > [~maxandersen] said: > {quote} i would put the details in attachment i think. its a bit overloaded otherwise I think, > btw. is this something you will run when you find a failed buid or did you say you would detect when hit a certain amont of fail you generate it ? > if auto generated shuold take care to not keep opening new jiras again andagain ;) > maybe add a "watermark" to detect stil open test failure jiras > {quote} > Idea here is to run this tool as needed when I notice that builds which are supposed to be frozen and stable are showing test failures persisting for multiple builds. Could also run against master jobs, but less critical. > Not sure what you mean by a watermark, or how that would be implemented. Please elaborate. > As this is purely a workflow optimization, it does NOT affect docs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15392: --------------------------------------------- why do you need a "usedefaultconfiguration" if you can just pass it an actual runtime ? Which usecase exist where you don't know the runtime ? and if you only know a directory why make it pretend it knows the exact configuration ? > Add api in server needed for source lookup > ------------------------------------------ > > Key: JBIDE-15392 > URL: https://issues.jboss.org/browse/JBIDE-15392 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes. > We need to define a stable api that can be used here. > lets outline what api is actually needed and then subjiras for the specifics. > For me it looks like server lookup needs a few things: > 0. know exact version of server > 1. know the file structure of a certain server > 2. get dir or directories that contain jar that is the "runtime" > My guess is that #2 might just be sufficient for source code lookup. > Any comments ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15472) Improve visibility for developers when test failures persist for multiple builds (Jenkins emails are ignored)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15472?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15472: --------------------------------------------- If this is just for running when needed then it is less of an issue but would be nice to avoid cluttering more jiras in for same test issues. My "watermark" idea was so instead of keep adding new jiras the script could check if there are still unresolved issues for the same test scenario, and instead of adding new jira just add comment to the jira about it continue to fail/be an issue. Something like, when creating an issue add unique part to the jira title, i.e. "job/jbosstools-server_41 repeated test failures" where "job/jbosstools-server_41" identifies the job and "job/" makes it fairly unlikely a human would enter similar issue. Then when running this script you simply search for unresolved issues "job/jbosstools-server_41" in the title and if there is one add a comment instead of keep adding same jira content. > Improve visibility for developers when test failures persist for multiple builds (Jenkins emails are ignored) > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15472 > URL: https://issues.jboss.org/browse/JBIDE-15472 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > > First iteration: https://issues.jboss.org/browse/JBIDE-15470, as generated by this: https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTestF... > [~maxandersen] said: > {quote} i would put the details in attachment i think. its a bit overloaded otherwise I think, > btw. is this something you will run when you find a failed buid or did you say you would detect when hit a certain amont of fail you generate it ? > if auto generated shuold take care to not keep opening new jiras again andagain ;) > maybe add a "watermark" to detect stil open test failure jiras > {quote} > Idea here is to run this tool as needed when I notice that builds which are supposed to be frozen and stable are showing test failures persisting for multiple builds. Could also run against master jobs, but less critical. > Not sure what you mean by a watermark, or how that would be implemented. Please elaborate. > As this is purely a workflow optimization, it does NOT affect docs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15475) Provide a "Link with Editor" button on the JUnit Test View

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15475: ------------------------------------- Summary: Provide a "Link with Editor" button on the JUnit Test View Key: JBIDE-15475 URL: https://issues.jboss.org/browse/JBIDE-15475 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: upstream Affects Versions: 4.1.0.Final Reporter: Xavier Coulon Assignee: Xavier Coulon Submitted a patch for https://bugs.eclipse.org/bugs/show_bug.cgi?id=372588 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15474) "Further Configuration" for JAX-RS Facet should be optional

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15474: ------------------------------------- Summary: "Further Configuration" for JAX-RS Facet should be optional Key: JBIDE-15474 URL: https://issues.jboss.org/browse/JBIDE-15474 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: upstream, webservices Affects Versions: 4.1.0.Final Reporter: Xavier Coulon Assignee: Xavier Coulon - library configuration should be optional, since users may work with Maven - web.xml configuration (servlet mapping) should be optional as well, since it has not been required since JavaEE6. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15473) JAX-RS 2.0 Facet should not require Java7

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15473: ------------------------------------- Summary: JAX-RS 2.0 Facet should not require Java7 Key: JBIDE-15473 URL: https://issues.jboss.org/browse/JBIDE-15473 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: upstream, webservices Affects Versions: 4.1.0.Final Reporter: Xavier Coulon Assignee: Xavier Coulon JAX-RS 2.0 Facet (in WTP) requires a Java7 project, but the JAX-RS spec mentions that it should run on Java6 projects. Opened Bugzilla at Eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=416704 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15362) Page is just simply rendered in VPE editor

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15362?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-15362: ------------------------------------- Issue Type: Feature Request (was: Bug) > Page is just simply rendered in VPE editor > ------------------------------------------ > > Key: JBIDE-15362 > URL: https://issues.jboss.org/browse/JBIDE-15362 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.1.0.Final > Reporter: Jiri Peterka > Assignee: Yahor Radtsevich > Fix For: 4.1.x > > Attachments: login-real-page.png, login-vpe-page.png, screenshot-PR161.png, standard-vpe-page.png > > > Not sure if this is not supported or if it's a bug. Thing is that page is not rendered with style but only very simple. See real output and output in VPE editor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 September 2013