10:42 a.m.
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL: https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: updatesite
Affects Versions: 5.0.0.M2
Reporter: Libor Zoubek
Priority: Blocker
Fix For: 5.0.0.M2
Right now JBDS 5 refers to
* https://devstudio.jboss.com/updates/4.0/
* https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update references
in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:44 a.m.
New subject: [JBoss JIRA] Assigned: (JBDS-1707) JBDS 5 refers to 4.0 updatesites
[
https://issues.jboss.org/browse/JBDS-1707?page=com.atlassian.jira.plugin....
]
Libor Zoubek reassigned JBDS-1707:
----------------------------------
Assignee: Denis Golovin
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL: https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: updatesite
Affects Versions: 5.0.0.M2
Reporter: Libor Zoubek
Assignee: Denis Golovin
Priority: Blocker
Fix For: 5.0.0.M2
Right now JBDS 5 refers to
* https://devstudio.jboss.com/updates/4.0/
* https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update
references in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:44 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1707) JBDS 5 refers to 4.0 updatesites
[
https://issues.jboss.org/browse/JBDS-1707?page=com.atlassian.jira.plugin....
]
Libor Zoubek updated JBDS-1707:
-------------------------------
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201106290641R-H21-M2.jar
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL: https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: updatesite
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201106290641R-H21-M2.jar
Reporter: Libor Zoubek
Assignee: Denis Golovin
Priority: Blocker
Fix For: 5.0.0.M2
Right now JBDS 5 refers to
* https://devstudio.jboss.com/updates/4.0/
* https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update
references in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:45 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1707) JBDS 5 refers to 4.0 updatesites
[
https://issues.jboss.org/browse/JBDS-1707?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen updated JBDS-1707:
--------------------------------------
Fix Version/s: 5.0.0.M3
(was: 5.0.0.M2)
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL: https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: updatesite
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201106290641R-H21-M2.jar
Reporter: Libor Zoubek
Assignee: Denis Golovin
Priority: Blocker
Fix For: 5.0.0.M3
Right now JBDS 5 refers to
* https://devstudio.jboss.com/updates/4.0/
* https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update
references in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:16 p.m.
New subject: [JBoss JIRA] Assigned: (JBDS-1707) JBDS 5 refers to 4.0 updatesites
[
https://issues.jboss.org/browse/JBDS-1707?page=com.atlassian.jira.plugin....
]
Nick Boldt reassigned JBDS-1707:
--------------------------------
Assignee: Nick Boldt (was: Denis Golovin)
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL: https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: updatesite
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201106290641R-H21-M2.jar
Reporter: Libor Zoubek
Assignee: Nick Boldt
Priority: Blocker
Fix For: 5.0.0.M3
Right now JBDS 5 refers to
* https://devstudio.jboss.com/updates/4.0/
* https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update
references in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9 a.m.
New subject: [JBoss JIRA] Resolved: (JBDS-1707) JBDS 5 refers to 4.0 updatesites
[
https://issues.jboss.org/browse/JBDS-1707?page=com.atlassian.jira.plugin....
]
Nick Boldt resolved JBDS-1707.
------------------------------
Resolution: Done
The following sites now exist as empty placeholders (until we have 5.0.0.GA released,
they'll stay empty):
http://devstudio.jboss.com/updates/5.0/
http://devstudio.jboss.com/updates/5.0/extras/
http://devstudio.jboss.com/updates/5.0/techpreview/
http://devstudio.jboss.com/updates/5.0/soa-tooling/
And I've updated these to point at the correct sites:
./product/features/com.jboss.jbds.product.feature/feature.xml
./product-soa/features/com.jboss.jbds.product.soa.feature/feature.xml
./extras/features/com.jboss.jbds.product.extra.feature/feature.xml
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL: https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: updatesite
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201106290641R-H21-M2.jar
Reporter: Libor Zoubek
Assignee: Nick Boldt
Priority: Blocker
Fix For: 5.0.0.M3
Right now JBDS 5 refers to
* https://devstudio.jboss.com/updates/4.0/
* https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update
references in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:50 a.m.
New subject: [JBoss JIRA] Reopened: (JBDS-1707) JBDS 5 refers to 4.0 updatesites
[
https://issues.jboss.org/browse/JBDS-1707?page=com.atlassian.jira.plugin....
]
Libor Zoubek reopened JBDS-1707:
--------------------------------
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL: https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201106290641R-H21-M2.jar
Reporter: Libor Zoubek
Assignee: Nick Boldt
Priority: Blocker
Fix For: 5.0.0.M3
Right now JBDS 5 refers to
* https://devstudio.jboss.com/updates/4.0/
* https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update
references in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:50 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1707) JBDS 5 refers to 4.0 updatesites
[
https://issues.jboss.org/browse/JBDS-1707?page=com.atlassian.jira.plugin....
]
Libor Zoubek commented on JBDS-1707:
------------------------------------
I've just checked 5.0.0.M3.H24 and I am missing soa-tooling and techpreview among
predefined updatesites. I am not sure if this is a bug, because
http://devstudio.jboss.com/updates/5.0 could be composite site having soa and techpreview
as children. Reopening anyway for sure
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL: https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201106290641R-H21-M2.jar
Reporter: Libor Zoubek
Assignee: Nick Boldt
Priority: Blocker
Fix For: 5.0.0.M3
Right now JBDS 5 refers to
* https://devstudio.jboss.com/updates/4.0/
* https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update
references in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:32 a.m.
New subject: [JBoss JIRA] Assigned: (JBDS-1707) JBDS 5 refers to 4.0 updatesites
[
https://issues.jboss.org/browse/JBDS-1707?page=com.atlassian.jira.plugin....
]
Nick Boldt reassigned JBDS-1707:
--------------------------------
Assignee: Max Rydahl Andersen (was: Nick Boldt)
Tech Preview and SOA Tooling are *OPTIONAL* sites, not to be preloaded in JBDS AFAIK.
Bouncing to Max to confirm we don't want SOA Tooling site preloaded in JBDS 5.0.0.M4.
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL: https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201106290641R-H21-M2.jar
Reporter: Libor Zoubek
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 5.0.0.M3
Right now JBDS 5 refers to
* https://devstudio.jboss.com/updates/4.0/
* https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update
references in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:37 p.m.
New subject: [JBoss JIRA] Assigned: (JBDS-1707) JBDS 5 refers to 4.0 updatesites
[
https://issues.jboss.org/browse/JBDS-1707?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen reassigned JBDS-1707:
-----------------------------------------
Assignee: Nick Boldt (was: Max Rydahl Andersen)
yes, for now JBDS 5 milestones are not intended to be preloaded with access to SOA.
The current thinking is that once SOA plugins gets available the idea is to make them
aggregated into the core site so there is no default notion of a separated site for the
user - but for now that site exists externally and are not merged in.
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL: https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201106290641R-H21-M2.jar
Reporter: Libor Zoubek
Assignee: Nick Boldt
Priority: Blocker
Fix For: 5.0.0.M3
Right now JBDS 5 refers to
* https://devstudio.jboss.com/updates/4.0/
* https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update
references in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:39 p.m.
New subject: [JBoss JIRA] Resolved: (JBDS-1707) JBDS 5 refers to 4.0 updatesites
[
https://issues.jboss.org/browse/JBDS-1707?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen resolved JBDS-1707.
---------------------------------------
Resolution: Done
resolving as fixed.
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL: https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201106290641R-H21-M2.jar
Reporter: Libor Zoubek
Assignee: Nick Boldt
Priority: Blocker
Fix For: 5.0.0.M3
Right now JBDS 5 refers to
* https://devstudio.jboss.com/updates/4.0/
* https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update
references in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:29 a.m.
New subject: [JBoss JIRA] Closed: (JBDS-1707) JBDS 5 refers to 4.0 updatesites
[
https://issues.jboss.org/browse/JBDS-1707?page=com.atlassian.jira.plugin....
]
Libor Zoubek closed JBDS-1707.
------------------------------
JBDS 5 refers to 4.0 updatesites
--------------------------------
Key: JBDS-1707
URL: https://issues.jboss.org/browse/JBDS-1707
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: updatesite
Affects Versions: 5.0.0.M2
Environment: jbdevstudio-product-linux-gtk-5.0.0.v201106290641R-H21-M2.jar
Reporter: Libor Zoubek
Assignee: Nick Boldt
Priority: Blocker
Fix For: 5.0.0.M3
Right now JBDS 5 refers to
* https://devstudio.jboss.com/updates/4.0/
* https://devstudio.jboss.com/updates/4.0/extras/
Which is wrong, since users won't be albe to install 5.0 extras or SOA
We need to create 5.0 updatesites (5.0,5.0/extras,5.0/soa-tooling) + add/update
references in JBDS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5324
days inactive
5389
days old
jbosstools-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Libor Zoubek (JIRA) -
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)