November 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3238) Early Access update site is active by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3238?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3238: ------------------------------ Description: When opening JBDS on a clean new workspace, the early access update site is enabled by default. Check Preferences > Install/Updates > Available Software sites or Install New Software > select https://devstudio.redhat.com/earlyaccess/8.0/ The early access update site should only be active if Early Access is enabled in JBoss Central was: When opening JBDS on a clean new workspace, the early access update site is enabled by default. Check Preferences > Install/Updates > Available Software sites or Install New Software > select https://devstudio.redhat.com/earlyaccess/8.0/ > Early Access update site is active by default > --------------------------------------------- > > Key: JBDS-3238 > URL: https://issues.jboss.org/browse/JBDS-3238 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Environment: JBDS Version: 8.0.0.GA > Build id: GA-v20141020-1042-B317 > Build date: 20141020-1042 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > > When opening JBDS on a clean new workspace, the early access update site is enabled by default. > Check Preferences > Install/Updates > Available Software sites > or Install New Software > select https://devstudio.redhat.com/earlyaccess/8.0/ > The early access update site should only be active if Early Access is enabled in JBoss Central -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3238) Early Access update site is active by default

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3238?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3238: ----------------------------- CDW docs_ack: ? CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? CDW release: ? > Early Access update site is active by default > --------------------------------------------- > > Key: JBDS-3238 > URL: https://issues.jboss.org/browse/JBDS-3238 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Environment: JBDS Version: 8.0.0.GA > Build id: GA-v20141020-1042-B317 > Build date: 20141020-1042 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > > When opening JBDS on a clean new workspace, the early access update site is enabled by default. > Check Preferences > Install/Updates > Available Software sites > or Install New Software > select https://devstudio.redhat.com/earlyaccess/8.0/ -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3238) Early Access update site is active by default

by Fred Bricon (JIRA)

Fred Bricon created JBDS-3238: --------------------------------- Summary: Early Access update site is active by default Key: JBDS-3238 URL: https://issues.jboss.org/browse/JBDS-3238 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: central Environment: JBDS Version: 8.0.0.GA Build id: GA-v20141020-1042-B317 Build date: 20141020-1042 Reporter: Fred Bricon Assignee: Mickael Istria Priority: Blocker When opening JBDS on a clean new workspace, the early access update site is enabled by default. Check Preferences > Install/Updates > Available Software sites or Install New Software > select https://devstudio.redhat.com/earlyaccess/8.0/ -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16385) Add 'Export Archive' to Arquillian Cruiser view

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16385?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16385: ---------------------------------- Fix Version/s: (was: 4.2.1.Final) > Add 'Export Archive' to Arquillian Cruiser view > ----------------------------------------------- > > Key: JBIDE-16385 > URL: https://issues.jboss.org/browse/JBIDE-16385 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.0.Alpha1 > > > Allow to export the Archive for further investigation / standalone deploy from the Arquillian Cruiser view. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3163: ---------------------------------- Ah, but we DO today. http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... In future we'd have nightly installers on www.qa and nightly update sites on ds.rh.com. Would skip only ONE step in the release process, but it would certainly save some time. > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.1.GA, 9.0.0.Alpha1 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18823) Invalid generated code in JAX-RS Endpoint

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18823?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-18823: ---------------------------------- Labels: rest (was: ) > Invalid generated code in JAX-RS Endpoint > ----------------------------------------- > > Key: JBIDE-18823 > URL: https://issues.jboss.org/browse/JBIDE-18823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > > The generated code in the 'create' method contains something like this: > {code} > return Response.created( > UriBuilder.fromResource(Session.class) > .path(String.valueOf(session.getId())).build()).build(); > {code} > but the {{Session.class}} should be {{SessionEndpoint.class}} since it must be the resource class annotated with {{@Path}} > Also, after discussion with [~maxandersen], here the plan to fix this issue: > - if the {{create}} method generation is selected and the target entity is selected and contains a 'getId()' method, then generate the following method body: > {code} > //TODO: process the given pojo > // here we use Pojo#getId(), assuming it provides the end-user with the identifier to retrieve the created Pojo resource > Response.created(UriBuilder.fromResource(PojoEndpoint.class).path(String.valueOf(pojo.getId())).build()) > .build(); > {code} > - if the {{create}} method generation is selected and the target entity is selected and *does not contain* a 'getId()' method, then generate the following method body: > {code} > //TODO: process the given pojo > // you may want to do something like this > // return Response.created(UriBuilder.fromResource(PojoEndpoint.class).path(String.valueOf(pojo.getId())).build(); > // assuming that Pojo#getId() or a similar method would provide the end-user with the identifier to retrieve the created Pojo resource > Response.created(null).build(); > {code} > If no target entity is provided, there is no way to generate the method skeletons. > The goal if this change is to make sure we generate code that compiles (that was not the case if the target entity class did not have a {{getId()}} method) and that returns a sensitive Response object (hence, we don't return {{null}}). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18823) Invalid generated code in JAX-RS Endpoint

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18823?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-18823: ---------------------------------- Labels: (was: rest) > Invalid generated code in JAX-RS Endpoint > ----------------------------------------- > > Key: JBIDE-18823 > URL: https://issues.jboss.org/browse/JBIDE-18823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > > The generated code in the 'create' method contains something like this: > {code} > return Response.created( > UriBuilder.fromResource(Session.class) > .path(String.valueOf(session.getId())).build()).build(); > {code} > but the {{Session.class}} should be {{SessionEndpoint.class}} since it must be the resource class annotated with {{@Path}} > Also, after discussion with [~maxandersen], here the plan to fix this issue: > - if the {{create}} method generation is selected and the target entity is selected and contains a 'getId()' method, then generate the following method body: > {code} > //TODO: process the given pojo > // here we use Pojo#getId(), assuming it provides the end-user with the identifier to retrieve the created Pojo resource > Response.created(UriBuilder.fromResource(PojoEndpoint.class).path(String.valueOf(pojo.getId())).build()) > .build(); > {code} > - if the {{create}} method generation is selected and the target entity is selected and *does not contain* a 'getId()' method, then generate the following method body: > {code} > //TODO: process the given pojo > // you may want to do something like this > // return Response.created(UriBuilder.fromResource(PojoEndpoint.class).path(String.valueOf(pojo.getId())).build(); > // assuming that Pojo#getId() or a similar method would provide the end-user with the identifier to retrieve the created Pojo resource > Response.created(null).build(); > {code} > If no target entity is provided, there is no way to generate the method skeletons. > The goal if this change is to make sure we generate code that compiles (that was not the case if the target entity class did not have a {{getId()}} method) and that returns a sensitive Response object (hence, we don't return {{null}}). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3163: ------------------------------------------- or we just dont push installers onto devstudio.redhat.com only the updatesites ? We don't publish the updatesites and installers together anyway do we ? > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.1.GA, 9.0.0.Alpha1 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3191: ------------------------------------------- No, the suggestion is: Alice installs JBDS 8.0.0.Beta3 it will default include /updates/8.0 as updatesite since declared in .product file and this updatesite will be empty. No magic needed in p2.inf/feature.xml or .product. during startup we lookup in ide.properties based on the version you are running and apply settings defined in here. i.e. we could have property to define development sites and a flag for wether they should be on or on. We could even ask the user during startup if he wants to get updates to development content or not..and vice versa, if he ends up upgrading to a GA and we can see he still have the list of sites from the development property installed we can ask if he wants to continue receiving these updates or not - if not, we clear out the development sites from his list of updatesites. Meaning * GA users will not see or be affecting of any of this. (only those actually running development versions will see it) * it does not matter what updatesite you got content from * none of this affects the build time settings. > Improve the way we switch between development and GA > ---------------------------------------------------- > > Key: JBDS-3191 > URL: https://issues.jboss.org/browse/JBDS-3191 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Fix For: 8.0.1.GA > > > JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream. > We need to improve that. > Changes are necessary in: > * features/com.jboss.devstudio.core/feature/p2.inf > * site/associate.properties > * results/pom.xml > As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there. > Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA. > The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties). > CC [~nickboldt] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-363) Additional user documentation needed to explain/clarify install options

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-363?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-363: ---------------------------------- Hey [~mmurray] - this is a generic Eclipse install behavior. Can you find the correct doc to update? Thanks! --paull > Additional user documentation needed to explain/clarify install options > ----------------------------------------------------------------------- > > Key: JBTIS-363 > URL: https://issues.jboss.org/browse/JBTIS-363 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.Beta1 > Reporter: Len DiMaggio > Assignee: Michelle Murray > Fix For: 8.0.0.Beta1 > > > If a user selects to install a subset of the individual components in a package grouping as displayed in JBoss Central - for example, if the user opts to install only the Fuse related items from the "JBoss Integration and SOA Development" group - then JBoss Central will continue to mark that group as not installed. > This behavior is correct, but may cause confusion for users if they expect that installing one component from a group will mark that group as being installed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

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 November 2014