July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3105) Show type of cartridge in create application wizard for custom cartridges

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3105?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-3105: -------------------------------- Issue Type: Enhancement (was: Feature Request) > Show type of cartridge in create application wizard for custom cartridges > ------------------------------------------------------------------------- > > Key: JBDS-3105 > URL: https://issues.jboss.org/browse/JBDS-3105 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: uxtest > > During the application creation process, if the user chooses a custom cartridge we should display the name of the cartridge from the .yml file in following wizard steps rather than "code anything". > Reproducable steps: > - New OpenShift application wizard > - Code Anything Downloadable Cartridge. Paste in yml file (example used: http://www.accursoft.com/cartridges/snap.yml) > - ISSUE: Next screen shows Cartridge type: "code anything". EXPECTED: cartridge type from yml file. https://www.evernote.com/shard/s230/sh/6e600e31-5527-4159-856a-3c8fdf2463... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17960) "The specified JRE installation does not exist"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17960?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17960: ------------------------------------- hi Karl: Can you verify for me that you do mean the affected version is 3.0.0.GA ? There are no further maintenance releases planned for that release train. We're currently working on 3.2.0, and I don't believe we even have any releases planned for 3.1.x anymore. If you mean 3.2.0 or 3.1.x, please let me know. Otherwise I might have to close this issue as wont-fix. > "The specified JRE installation does not exist" > ----------------------------------------------- > > Key: JBIDE-17960 > URL: https://issues.jboss.org/browse/JBIDE-17960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.0.0.GA > Reporter: Karl Pietrzak > Priority: Minor > Attachments: jbossastools-bad.jre.swf > > > h3. What > If you get a ""The specified JRE installation does not exist" error, JBoss Tools puts the entry in the Servers section as "Starting...", which is inaccurate. > h3. Screencast > !jbossastools-bad.jre.swf! > If the above embedded SWF doesn't work for you, you can watch it at http://screencast.com/t/bytN53lp -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3108) Add ability to "always accept" the hostkey of the SSH connection for cloning git repos

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3108?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-3108: ---------------------------------------- We had this blind acceptance before we added the key dialog which shows you the key and asks you to accept/refute it. IMHO to blindly accept keys is never a good idea. [~maxandersen] dare to comment? > Add ability to "always accept" the hostkey of the SSH connection for cloning git repos > -------------------------------------------------------------------------------------- > > Key: JBDS-3108 > URL: https://issues.jboss.org/browse/JBDS-3108 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Labels: uxtest > > Each time JBDS does a git clone, it gives me a warning about the hostkey of the SSH connection. As a developer, I will always accept this. I'd like the ability to click an "always accept" checkbox so I don't have to see this pop-up every time. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3108) Add ability to "always accept" the hostkey of the SSH connection for cloning git repos

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3108?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-3108: ----------------------------------- Assignee: Max Rydahl Andersen > Add ability to "always accept" the hostkey of the SSH connection for cloning git repos > -------------------------------------------------------------------------------------- > > Key: JBDS-3108 > URL: https://issues.jboss.org/browse/JBDS-3108 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 8.0.0.Beta2 > Reporter: Catherine Robson > Assignee: Max Rydahl Andersen > Labels: uxtest > > Each time JBDS does a git clone, it gives me a warning about the hostkey of the SSH connection. As a developer, I will always accept this. I'd like the ability to click an "always accept" checkbox so I don't have to see this pop-up every time. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17965) Update stacks url (jdf is now jboss developer)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17965?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-17965: -------------------------------- Fix Version/s: 4.2.0.CR1 > Update stacks url (jdf is now jboss developer) > ---------------------------------------------- > > Key: JBIDE-17965 > URL: https://issues.jboss.org/browse/JBIDE-17965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > I'm not sure exactly which component is right here. > stacks.yaml is now on this location: > https://github.com/jboss-developer/jboss-stacks/blob/1.0.0.Final/stacks.yaml > It's no longer jdf, but jboss-developer. The old url still works through redirects, but it's probably a good idea to use the new one. > Reject this JIRA if this has already been done. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17523) Filter runtime downloads to hide unsupported runtime types

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17523?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17523. --------------------------------- I crafted a local stacks.yaml with an altered runtime type for WildFly 8.0.0 definition: wtp-runtime-type: org.jboss.ide.eclipse.as.runtime.wildfly.82 With this, going through Preferences -> Runtime Detection -> Download didn't show WildFly 8.0, only 8.1. Going through New Server, the filtering also still works correctly - selecting a WildFly server, only 8.1 was shown. So it works as expected. Verified in JBDS 8.0.0.Beta3c B194. Closing. > Filter runtime downloads to hide unsupported runtime types > ---------------------------------------------------------- > > Key: JBIDE-17523 > URL: https://issues.jboss.org/browse/JBIDE-17523 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > This concern arose while testing the new WildFly 8.1 runtime added to stacks.yaml (JDF-727). This itself is ok, but Rob pointed out another concern: > If a new runtime requires a new runtime type in the future and we add this to stacks.yaml, older versions of JBDS/JBT will not recognize this runtime type, but will still gladly offer it to you for download through Preferences -> Runtime Detection -> Download. When you choose the path of Server -> New, the runtimes offered for download are restricted to the given server type, so we're safe there. > So this is what we should do: > The list of runtimes offered for download should always be restricted to only those runtimes that are defined in the given JBDS/JBT. > E.g. if EAP 7 needs an eap7 runtime type in stacks.yaml, but this type is not available in JBDS 8, JBDS 8 should not offer EAP 7 for download. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17801) JAX-RS validation: Bogus warning for parameter whose type is an enumeration

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17801?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-17801: --------------------------------------- [~clovisseragiotto ], The validation message refers to the section 3.2 of the JAX-RS 2.0 spec because there should be a Message#fromString(String) or a Message#valueOf(String) method that was not found, but it is implicit in the case of Enumerations, which is clearly something I forgot when coding the validator :( {quote} Valid parameter types for each of the above annotations are listed in the corresponding Javadoc, however in general (excluding @Context) the following types are supported: 1. Types for which a ParamConverter is available via a registered ParamConverterProvider. See Javadoc for these classes for more information. 2. Primitive types. 3. Types that have a constructor that accepts a single String argument. 4. Types that have a static method named valueOf or fromString with a single String argument that return an instance of the type. If both methods are present then valueOf MUST be used unless the type is an enum in which case fromString MUST be used(1). 5. List<T>, Set<T>, or SortedSet<T>, where T satisfies 3 or 4 above. (1) Due to limitations of the built-in valueOf method that is part of all Java enumerations, a fromString method is often defined by the enum writers. Consequently, the fromString method is preferred when available. {quote} I'll fix that today. Thanks for reporting that bug ! And please, feel free to report any other problem you can find, or missing features you'd like to see in the tooling! > JAX-RS validation: Bogus warning for parameter whose type is an enumeration > --------------------------------------------------------------------------- > > Key: JBIDE-17801 > URL: https://issues.jboss.org/browse/JBIDE-17801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Clovis Seragiotto > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > The JAX-RS validation wrongly complains about the type of the parameter when it is an enumeration defined in the same class of the resource. > "The type 'Resources.InstanceType' is not valid for this parameter. See JAX-RS 2.0 Specification (section 3.2) for more information." > (the error message just telling that something is invalid doesn't help too much either when you are trying to understand how the validation is reasoning) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17965) Update stacks url (jdf is now jboss developer)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17965?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17965: ---------------------------------- Assignee: Rob Stryker > Update stacks url (jdf is now jboss developer) > ---------------------------------------------- > > Key: JBIDE-17965 > URL: https://issues.jboss.org/browse/JBIDE-17965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > > I'm not sure exactly which component is right here. > stacks.yaml is now on this location: > https://github.com/jboss-developer/jboss-stacks/blob/1.0.0.Final/stacks.yaml > It's no longer jdf, but jboss-developer. The old url still works through redirects, but it's probably a good idea to use the new one. > Reject this JIRA if this has already been done. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17965) Update stacks url (jdf is now jboss developer)

by Martin Malina (JIRA)

Martin Malina created JBIDE-17965: ------------------------------------- Summary: Update stacks url (jdf is now jboss developer) Key: JBIDE-17965 URL: https://issues.jboss.org/browse/JBIDE-17965 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central, server Affects Versions: 4.2.0.Beta3 Reporter: Martin Malina I'm not sure exactly which component is right here. stacks.yaml is now on this location: https://github.com/jboss-developer/jboss-stacks/blob/1.0.0.Final/stacks.yaml It's no longer jdf, but jboss-developer. The old url still works through redirects, but it's probably a good idea to use the new one. Reject this JIRA if this has already been done. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17964) add keywords for JBoss Tools and Developer studio marketplace entry

by Lars Heinemann (JIRA)

Lars Heinemann created JBIDE-17964: -------------------------------------- Summary: add keywords for JBoss Tools and Developer studio marketplace entry Key: JBIDE-17964 URL: https://issues.jboss.org/browse/JBIDE-17964 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: marketplace Affects Versions: 4.2.0.CR1 Reporter: Lars Heinemann Fix For: 4.2.0.CR1 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, 9 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