July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17078) JAX-RS Problems doesn't appears after the JAX-RS Support is activated

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17078?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-17078: --------------------------------------- [~akazakov], thanks for your response (and sorry for this late reply :-/ ) So, to summarize what you suggested: - I should ensure that the WST validator is also added (or already there) when the JAX-RS nature is added, - I should trigger a project build if the WST validation was already present when the JAX-RS nature was added (and only in that case) ? When you trigger such a build, do you do it just after adding the CDI nature ? thanks > JAX-RS Problems doesn't appears after the JAX-RS Support is activated > --------------------------------------------------------------------- > > Key: JBIDE-17078 > URL: https://issues.jboss.org/browse/JBIDE-17078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, webservices > Affects Versions: 4.2.0.Beta1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > > JAX-RS validation runs when there is a change in the project with JAX-RS Support. However, it doesn't run right after the JAX-RS Support is enabled. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17746) NPE while editing @PathParam in BeanParam class

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17746?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-17746: --------------------------------------- [~rrabara], I could not reproduce it on my machine after the last changes/fixes I made. Can you verify it's fixed with the next build ? Thanks > NPE while editing @PathParam in BeanParam class > ----------------------------------------------- > > Key: JBIDE-17746 > URL: https://issues.jboss.org/browse/JBIDE-17746 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140702-0157-B560 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17746) NPE while editing @PathParam in BeanParam class

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17746?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-17746: ---------------------------------- Sprint: Sprint to Beta3 Release > NPE while editing @PathParam in BeanParam class > ----------------------------------------------- > > Key: JBIDE-17746 > URL: https://issues.jboss.org/browse/JBIDE-17746 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140702-0157-B560 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17747) Unable to complete the JAX-RS Resource Creation Wizard

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17747?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-17747: --------------------------------------- This only happens if the project already contains a java-based Application with the default name/package, in which case the "Name:" field is not filled. > Unable to complete the JAX-RS Resource Creation Wizard > ------------------------------------------------------ > > Key: JBIDE-17747 > URL: https://issues.jboss.org/browse/JBIDE-17747 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > > when selecting an existing class to create a new JAX-RS Resource from it, using the default values, the 'Finish' button remains disabled, but no error message is shown on the dialog window. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3079) Offline Central installation misses some JBT bundles

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3079?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3079: ----------------------------- Description: Removed items include: org.jboss.tools.vpe.cordovasim.feature (and source) org.jboss.tools.maven.jbosspackaging.feature (and source) org.jboss.tools.common.mylyn.feature (and source) Problem w/ removing these is that the JBDS Central plugin.xml requirs all three of them in these connectors: JBoss Hybrid Mobile Tools + CordovaSim JBoss Tools Maven Packaging Configurator Mylyn support for reporting JBoss JIRAs and Red Hat Bugzillas So if we remove them, then those connectors can't be installed in JBDS. Possible workarounds: a) do nothing and accept that for offline installs, you need the update site (not the installer) + central zip; also accept that the installer != update site b) put these 3 features in the installer so that the installer contents == the update site contents (except for sources) [I did this in JBDS-3071 but [~dgolovin] reverted it] c) move these 3 features into the JBDS TP; this is bad because it creates an ugly dependency chain: JBDS -> JBDS TP -> JBT -> JBT TP... every time JBT rebuilds, we need to update the version of org.jboss.tools.* in the JBDS TP d) move these 3 features into the Central TP; this is bad in that as in (c) we would have to keep updating the Central TP each time there's a new JBT release... but we already have this problem because of Arquillian being included in the EA TP. Since (b) was rejected, clearly the solution is (d). Or do nothing and annoy offline users with (a). :D was: Since the installer jar doesn't contain some JBT IUs any more (cf JBDS-3071), installing some feature from Central will fail with missing dependencies when running offline. We should add tp JBDS Central the necessary JBT bundles. > Offline Central installation misses some JBT bundles > ---------------------------------------------------- > > Key: JBDS-3079 > URL: https://issues.jboss.org/browse/JBDS-3079 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: discovery > Affects Versions: 8.0.0.Beta2 > Reporter: Mickael Istria > Priority: Minor > Fix For: 8.0.0.Beta3 > > > Removed items include: > org.jboss.tools.vpe.cordovasim.feature (and source) > org.jboss.tools.maven.jbosspackaging.feature (and source) > org.jboss.tools.common.mylyn.feature (and source) > Problem w/ removing these is that the JBDS Central plugin.xml requirs all three of them in these connectors: > JBoss Hybrid Mobile Tools + CordovaSim > JBoss Tools Maven Packaging Configurator > Mylyn support for reporting JBoss JIRAs and Red Hat Bugzillas > So if we remove them, then those connectors can't be installed in JBDS. > Possible workarounds: > a) do nothing and accept that for offline installs, you need the update site (not the installer) + central zip; also accept that the installer != update site > b) put these 3 features in the installer so that the installer contents == the update site contents (except for sources) [I did this in JBDS-3071 but [~dgolovin] reverted it] > c) move these 3 features into the JBDS TP; this is bad because it creates an ugly dependency chain: JBDS -> JBDS TP -> JBT -> JBT TP... every time JBT rebuilds, we need to update the version of org.jboss.tools.* in the JBDS TP > d) move these 3 features into the Central TP; this is bad in that as in (c) we would have to keep updating the Central TP each time there's a new JBT release... but we already have this problem because of Arquillian being included in the EA TP. > Since (b) was rejected, clearly the solution is (d). Or do nothing and annoy offline users with (a). :D -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3079) Offline Central installation misses some JBT bundles

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3079?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3079: ----------------------------- Comment: was deleted (was: This issue is caused by changes in JBDS-3071.) > Offline Central installation misses some JBT bundles > ---------------------------------------------------- > > Key: JBDS-3079 > URL: https://issues.jboss.org/browse/JBDS-3079 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: discovery > Affects Versions: 8.0.0.Beta2 > Reporter: Mickael Istria > Priority: Minor > Fix For: 8.0.0.Beta3 > > > Removed items include: > org.jboss.tools.vpe.cordovasim.feature (and source) > org.jboss.tools.maven.jbosspackaging.feature (and source) > org.jboss.tools.common.mylyn.feature (and source) > Problem w/ removing these is that the JBDS Central plugin.xml requirs all three of them in these connectors: > JBoss Hybrid Mobile Tools + CordovaSim > JBoss Tools Maven Packaging Configurator > Mylyn support for reporting JBoss JIRAs and Red Hat Bugzillas > So if we remove them, then those connectors can't be installed in JBDS. > Possible workarounds: > a) do nothing and accept that for offline installs, you need the update site (not the installer) + central zip; also accept that the installer != update site > b) put these 3 features in the installer so that the installer contents == the update site contents (except for sources) [I did this in JBDS-3071 but [~dgolovin] reverted it] > c) move these 3 features into the JBDS TP; this is bad because it creates an ugly dependency chain: JBDS -> JBDS TP -> JBT -> JBT TP... every time JBT rebuilds, we need to update the version of org.jboss.tools.* in the JBDS TP > d) move these 3 features into the Central TP; this is bad in that as in (c) we would have to keep updating the Central TP each time there's a new JBT release... but we already have this problem because of Arquillian being included in the EA TP. > Since (b) was rejected, clearly the solution is (d). Or do nothing and annoy offline users with (a). :D -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3079) Offline Central installation misses some JBT bundles

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3079?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3079: ---------------------------------- This issue is caused by changes in JBDS-3071. > Offline Central installation misses some JBT bundles > ---------------------------------------------------- > > Key: JBDS-3079 > URL: https://issues.jboss.org/browse/JBDS-3079 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: discovery > Affects Versions: 8.0.0.Beta2 > Reporter: Mickael Istria > Priority: Minor > Fix For: 8.0.0.Beta3 > > > Since the installer jar doesn't contain some JBT IUs any more (cf JBDS-3071), installing some feature from Central will fail with missing dependencies when running offline. > We should add tp JBDS Central the necessary JBT bundles. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3079) Offline Central installation misses some JBT bundles

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3079?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3079: ----------------------------- Fix Version/s: 8.0.0.Beta3 (was: 8.0.0.CR1) > Offline Central installation misses some JBT bundles > ---------------------------------------------------- > > Key: JBDS-3079 > URL: https://issues.jboss.org/browse/JBDS-3079 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: discovery > Affects Versions: 8.0.0.Beta2 > Reporter: Mickael Istria > Priority: Minor > Fix For: 8.0.0.Beta3 > > > Since the installer jar doesn't contain some JBT IUs any more (cf JBDS-3071), installing some feature from Central will fail with missing dependencies when running offline. > We should add tp JBDS Central the necessary JBT bundles. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17747) Unable to complete the JAX-RS Resource Creation Wizard

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-17747: ------------------------------------- Summary: Unable to complete the JAX-RS Resource Creation Wizard Key: JBIDE-17747 URL: https://issues.jboss.org/browse/JBIDE-17747 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.2.0.Beta3 Reporter: Xavier Coulon when selecting an existing class to create a new JAX-RS Resource from it, using the default values, the 'Finish' button remains disabled, but no error message is shown on the dialog window. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17587) CordovaSim configuration is stored directly in home directory

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17587?page=com.atlassian.jira.plugi... ] Ilya Buziuk resolved JBIDE-17587. --------------------------------- Resolution: Done > CordovaSim configuration is stored directly in home directory > ------------------------------------------------------------- > > Key: JBIDE-17587 > URL: https://issues.jboss.org/browse/JBIDE-17587 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Environment: JBDS 8.0.0.Beta2 respin b > RHEL7 > Reporter: Karel Piwko > Assignee: Ilya Buziuk > Fix For: 4.2.0.Beta3 > > > First, I believe this configuration should be in a configuration (.dot) directory by default - related to JBIDE-13189. > Secondly, I'm not sure whether configuration should not be specific per workspace. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014