[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3360:
-------------------------------------
Minor correction: It turns out RHEL actually keeps older artifacts in the repo, so if you really wanted to, you could install an older version of something and avoid updating the rest of your packages. But you would need to specify a version when installing the package. By default, you always get the latest with the latest deps.
> Align bits offered in JBoss Central with installed version of JBDS
> ------------------------------------------------------------------
>
> Key: JBDS-3360
> URL: https://issues.jboss.org/browse/JBDS-3360
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, updatesite
> Affects Versions: 8.0.2.GA
> Reporter: Martin Malina
> Fix For: 8.1.0.CR1
>
>
> The problem in JBDS-3359 shows a broader issue.
> (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.)
> Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites:
> https://devstudio.redhat.com/updates/8.0/
> Initially this update site contained JBDS 8.0.0 core + 8.0.0 central.
> But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users:
> 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits
> 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits)
> Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also.
> I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBDS-3360) Align bits offered in JBoss Central with installed version of JBDS
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3360?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3360:
-------------------------------------
My idea was that until you move from JBDS 8.0.0 to 8.0.2 (for example), you should be able to stay in the past with all the functionality - including installation of extra features from Central.
But Max is right that this probably doesn't work like that in RHEL either - yum always offers the latest in the stream.
So I suppose this will be rejected.
Unless somebody wants to push the other thing:
{quote}
Something that could be considered though is that we don't remove 8.0.0 content from the updatesites, but instead put both 8.0.0, 8.0.1 and 8.0.2 content so users at least manually can do updates.
{quote}
> Align bits offered in JBoss Central with installed version of JBDS
> ------------------------------------------------------------------
>
> Key: JBDS-3360
> URL: https://issues.jboss.org/browse/JBDS-3360
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, updatesite
> Affects Versions: 8.0.2.GA
> Reporter: Martin Malina
> Fix For: 8.1.0.CR1
>
>
> The problem in JBDS-3359 shows a broader issue.
> (That one is about issues when clicking on an example in Central in JBDS 8.0.0 when 8.0.2 has already been released and central points to it.)
> Currently when you install JBDS 8.0.0, it will contain this update site in Preferences -> Available Software Sites:
> https://devstudio.redhat.com/updates/8.0/
> Initially this update site contained JBDS 8.0.0 core + 8.0.0 central.
> But once we released JBDS 8.0.1, the update site was updated with 8.0.1 and this update was offered to users in Eclipse. And we started to have two groups of users:
> 1. Those who stayed on JBDS 8.0.0, but their Central already pointed to 8.0.1 bits
> 2. Those who update to JBDS 8.0.1 (and their Central also pointed to 8.0.1 bits)
> Wouldn't it make more sense if central used the same version that is currently installed? I.e. if a user stays with JBDS 8.0.0, the bits offered in Central are 8.0.0 also.
> I'm not sure if this is doable or makes sense at all, so I'm looking forward to feedback :)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (JBTIS-402) Cannot install Teiid Designer from JBDS-IS 7.1.0.CR1
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-402?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky reassigned JBTIS-402:
---------------------------------------
Assignee: Paul Leacu
> Cannot install Teiid Designer from JBDS-IS 7.1.0.CR1
> ----------------------------------------------------
>
> Key: JBTIS-402
> URL: https://issues.jboss.org/browse/JBTIS-402
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 7.1.0.CR1
> Environment: JBDS 7.1.1.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
>
> Cannot install Teiid Designer from JBDS-IS 7.1.0.CR1, the following error occurs
> Cannot complete the install because one or more required items could not be found.
> Software being installed: Teiid Runtime Clients 8.6.1.CR1-v20150219-1612-B790 (org.teiid.designer.teiid.client.feature.feature.group 8.6.1.CR1-v20150219-1612-B790)
> Missing requirement: Teiid DataTools Connectivity 8.6.1.CR1-v20150219-1612-B790 (org.teiid.datatools.connectivity.feature.feature.group 8.6.1.CR1-v20150219-1612-B790) requires '[rg.eclipse.datatools.sqltools.sqleditor [1.0.2,2.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: Teiid Runtime Clients 8.6.1.CR1-v20150219-1612-B790 (org.teiid.designer.teiid.client.feature.feature.group 8.6.1.CR1-v20150219-1612-B790)
> To: org.teiid.datatools.connectivity.feature.feature.group [8.6.1.CR1-v20150219-1612-B790]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TOOLSDOC-560) We should add an illustration of the RESTFUL output
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-560?page=com.atlassian.jira.plug... ]
Marián Labuda commented on TOOLSDOC-560:
----------------------------------------
We use Web Service Tester view to show web services responses. Maybe it would be nice to incorporate it in the guide WDYT?
> We should add an illustration of the RESTFUL output
> ---------------------------------------------------
>
> Key: TOOLSDOC-560
> URL: https://issues.jboss.org/browse/TOOLSDOC-560
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Affects Versions: 4.2.0.Final
> Environment: Build Name: 22960, Start Developing-8.0
> Build Date: 22-10-2014 11:29:36
> Topic ID: 13785-717269 [Latest]
> Reporter: Len DiMaggio
> Assignee: Michelle Murray
> Priority: Minor
> Fix For: 4.2.3.Beta1
>
>
> Title: Add a RESTful Web Service
> Describe the issue:
> The final step in this section reads:
> Open a new Web Browser and in the address bar of the Web Browser enter http://localhost:8080/ticket-monster/rest/events. This shows the output of the new RESTful endpoint.
> Suggestions for improvement:
> We should add test explaining to the reader that the output should look like this:
> [{"id":2,"version":1,"name":"Rock concert of the decade","description":"Get ready to rock...","major":true,"picture":null},{"id":1,"version":1,"name":"Shane's Sock Puppets","description":"This critically acclaimed masterpiece...","major":true,"picture":null}]
> Additional information:
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TOOLSDOC-561) We should mention that the internal web browser will save the RESTFUL output to a file and not display it
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-561?page=com.atlassian.jira.plug... ]
Marián Labuda commented on TOOLSDOC-561:
----------------------------------------
Why are you using creating a JAX-RS web services from class altough we have JAX-RS web service wizard to create endpoints? It would minimalize addition of further data/metadata into class.
> We should mention that the internal web browser will save the RESTFUL output to a file and not display it
> ---------------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-561
> URL: https://issues.jboss.org/browse/TOOLSDOC-561
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Affects Versions: 4.2.0.Final
> Environment: Build Name: 22960, Start Developing-8.0
> Build Date: 22-10-2014 11:29:36
> Topic ID: 13785-717269 [Latest]
> Reporter: Len DiMaggio
> Assignee: Michelle Murray
> Priority: Minor
> Fix For: 4.2.3.Beta1
>
>
> Title: Add a RESTful Web Service
> Describe the issue:
> The final step in this section reads:
> Open a new Web Browser and in the address bar of the Web Browser enter http://localhost:8080/ticket-monster/rest/events. This shows the output of the new RESTful endpoint.
> Suggestions for improvement:
> We should mention that the internal web browser will save the RESTFUL output to a file and not display it
> Additional information:
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month