3:39 p.m.
Should support auto download of new container for Arquillian
------------------------------------------------------------
Key: JBIDE-6369
URL: https://jira.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: testing
Reporter: Aslak Knutsen
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:48 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6369) Should support auto download of new container for Tools
[
https://jira.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen updated JBIDE-6369:
---------------------------------------
Summary: Should support auto download of new container for Tools (was: Should
support auto download of new container for Arquillian)
Fix Version/s: 3.2.x
Priority: Blocker (was: Major)
changed description since this aren't specific to arquillian IMO; being able to do the
exact same thing from within eclipse to get various AS, EAP, Tomcat installations would be
beneficial.
Not sure what we can do beyond having a set of URL's with distro locations +
mechanical instructions on how to get it and install it (this actually sounds very much
like a good job for P2...?) and then associate that to an identifier (i.e. Maven GAV)
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://jira.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: testing
Reporter: Aslak Knutsen
Priority: Blocker
Fix For: 3.2.x
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:32 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6369) Should support auto download of new container for Tools
[
https://jira.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin.s...
]
Denis Golovin updated JBIDE-6369:
---------------------------------
Fix Version/s: 3.3.x
(was: 3.2.x)
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://jira.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: testing
Reporter: Aslak Knutsen
Priority: Blocker
Fix For: 3.3.x
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:20 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Dan Allen updated JBIDE-6369:
-----------------------------
Attachment: new-glassfish.png
I'm looking for something similar to what the GlassFish Tools Bundle provides. When
you add a new server, it asks for an installation path. If that path doesn't exist,
you have the option of downloading it automatically, as shown in the attached
screenshots.
IMO, this is the best way to get JBoss AS in the hands of the developers. They start in
the IDE, where they should start, and they never have to worry about the jboss.org/jbossas
download page, sourceforge, or any unzipping messiness. Just point and shoot.
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: testing
Reporter: Aslak Knutsen
Priority: Blocker
Fix For: 3.3.x
Attachments: new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:22 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Dan Allen updated JBIDE-6369:
-----------------------------
Attachment: downloading-glassfish.png
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: testing
Reporter: Aslak Knutsen
Priority: Blocker
Fix For: 3.3.x
Attachments: downloading-glassfish.png, new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:01 a.m.
New subject: [JBoss JIRA] (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-6369:
--------------------------------------------
snjezana - could you update this issue with info on what you have done so far on this ?
Past M4 we should see how we can move the extension point to something that others can
depend on so the server UI can get the download/install functionallity too
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime detection
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M4
Attachments: downloading-glassfish.png, new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:01 a.m.
New subject: [JBoss JIRA] (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-6369:
---------------------------------------
Assignee: Snjezana Peco
Fix Version/s: 3.3.0.M4
(was: 3.3.x)
Priority: Critical (was: Blocker)
Component/s: runtime detection
(was: testing)
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime detection
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M4
Attachments: downloading-glassfish.png, new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:22 a.m.
New subject: [JBoss JIRA] (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-6369:
--------------------------------------
Downloading runtimes has been implemented using the
org.jboss.tools.runtime.core.downloadJBossRuntimes ext. point.
It is defined in the org.jboss.tools.runtime.core plugin. This plugin depends on the
org.jboss.tools.runtime plugin.
The UI is placed in the org.jboss.tools.runtime.ui plugin and depends on the
project-examples plugin (it uses the download method from this plugin).
The following is an example of the use of this ext. point:
<extension
point="org.jboss.tools.runtime.core.downloadJBossRuntimes">
<runtime
id="org.jboss.tools.runtime.core.as.702"
name="JBoss AS 7.0.2 Everything (NOT Java EE6 Certified)"
version="7.0.2.Final"
size="75MB"
url="http://download.jboss.org/jbossas/7.0/jboss-as-7.0.2.Final/jbos...
</extension>
See
https://issues.jboss.org/browse/JBIDE-9368?focusedCommentId=12635034&....
We could easily move this ext. point, the UI code and the download method to the common or
to any other component.
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime detection
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M4
Attachments: downloading-glassfish.png, new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 a.m.
New subject: [JBoss JIRA] (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-6369:
--------------------------------------------
yes thats the idea.
we really should not call it "downloadJBossRuntimes", should just be
downloadruntimes or something non jboss specific since there isn't really anything
jboss specific about this functionallity.
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime detection
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M4
Attachments: downloading-glassfish.png, new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:13 a.m.
New subject: [JBoss JIRA] (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-6369:
--------------------------------------
The extension point name has been changed from
org.jboss.tools.runtime.core.downloadJBossRuntimes to
org.jboss.tools.runtime.core.downloadruntimes.
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime detection
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M4
Attachments: downloading-glassfish.png, new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:15 a.m.
New subject: [JBoss JIRA] (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Snjezana Peco edited comment on JBIDE-6369 at 10/17/11 10:14 AM:
-----------------------------------------------------------------
Downloading runtimes has been implemented using the
org.jboss.tools.runtime.core.downloadJBossRuntimes ext. point.
It is defined in the org.jboss.tools.runtime.core plugin. This plugin depends on the
org.jboss.tools.runtime plugin.
The UI is placed in the org.jboss.tools.runtime.ui plugin and depends on the
project-examples plugin (it uses the download method from this plugin).
The following is an example of the use of this ext. point:
<extension
point="org.jboss.tools.runtime.core.downloadruntimes">
<runtime
id="org.jboss.tools.runtime.core.as.702"
name="JBoss AS 7.0.2 Everything (NOT Java EE6 Certified)"
version="7.0.2.Final"
size="75MB"
url="http://download.jboss.org/jbossas/7.0/jboss-as-7.0.2.Final/jbos...
</extension>
See
https://issues.jboss.org/browse/JBIDE-9368?focusedCommentId=12635034&....
We could easily move this ext. point, the UI code and the download method to the common or
to any other component.
was (Author: snjeza):
Downloading runtimes has been implemented using the
org.jboss.tools.runtime.core.downloadJBossRuntimes ext. point.
It is defined in the org.jboss.tools.runtime.core plugin. This plugin depends on the
org.jboss.tools.runtime plugin.
The UI is placed in the org.jboss.tools.runtime.ui plugin and depends on the
project-examples plugin (it uses the download method from this plugin).
The following is an example of the use of this ext. point:
<extension
point="org.jboss.tools.runtime.core.downloadJBossRuntimes">
<runtime
id="org.jboss.tools.runtime.core.as.702"
name="JBoss AS 7.0.2 Everything (NOT Java EE6 Certified)"
version="7.0.2.Final"
size="75MB"
url="http://download.jboss.org/jbossas/7.0/jboss-as-7.0.2.Final/jbos...
</extension>
See
https://issues.jboss.org/browse/JBIDE-9368?focusedCommentId=12635034&....
We could easily move this ext. point, the UI code and the download method to the common or
to any other component.
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime detection
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M4
Attachments: downloading-glassfish.png, new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:12 p.m.
New subject: [JBoss JIRA] (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Snjezana Peco updated JBIDE-6369:
---------------------------------
Fix Version/s: 3.3.0.Beta1
(was: 3.3.0.M4)
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime detection
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.Beta1
Attachments: downloading-glassfish.png, new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:56 a.m.
New subject: [JBoss JIRA] (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-6369:
--------------------------------------------
snjezana - isn't the basics of this done for M4 ? should be resovled and anything left
added in for Beta1 ?
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime detection
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.Beta1
Attachments: downloading-glassfish.png, new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:53 a.m.
New subject: [JBoss JIRA] (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-6369:
--------------------------------------
We only need to move the org.jboss.tools.runtime.core.downloadruntimes ext. point to some
other plugin (common probably).
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime detection
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.Beta1
Attachments: downloading-glassfish.png, new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:59 p.m.
New subject: [JBoss JIRA] (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Snjezana Peco resolved JBIDE-6369.
----------------------------------
Resolution: Done
Since the org.jboss.tools.runtime.core.downloadruntimes ext. point creates runtimes, it
depends on the runtime plugin.
We can't add the runtime plugin dependency to the common plugin so that this ext.
point should remain in the runtime plugin.
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime detection
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M5
Attachments: downloading-glassfish.png, new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:11 a.m.
New subject: [JBoss JIRA] (JBIDE-6369) Should support auto download of new container for Tools
[
https://issues.jboss.org/browse/JBIDE-6369?page=com.atlassian.jira.plugin...
]
Jiri Peterka closed JBIDE-6369.
-------------------------------
Nice feature, verified in JBDS 5.0.0.M5a,H62, L64
Should support auto download of new container for Tools
-------------------------------------------------------
Key: JBIDE-6369
URL: https://issues.jboss.org/browse/JBIDE-6369
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime detection
Reporter: Aslak Knutsen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 3.3.0.M5
Attachments: downloading-glassfish.png, new-glassfish.png
This can be done using maven, but Tools needs some way to know which containers exists as
they can be located in multiple repos and not necessarily a part of Arquillian project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5066
days inactive
5641
days old
jbosstools-issues@lists.jboss.org
15 comments
11 participants
participants (11)
-
Aslak Knutsen (JIRA) -
Dan Allen (JIRA)
-
Denis Golovin (JIRA)
-
Jiri Peterka (Closed) (JIRA)
-
Max Rydahl Andersen (Commented) (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Max Rydahl Andersen (Updated) (JIRA)
-
Snjezana Peco (Commented) (JIRA)
-
Snjezana Peco (Issue Comment Edited) (JIRA)
-
Snjezana Peco (Resolved) (JIRA)
-
Snjezana Peco (Updated) (JIRA)