10:23 a.m.
Separate specific runtime detection plugins from base core
-----------------------------------------------------------
Key: JBIDE-9026
URL: https://issues.jboss.org/browse/JBIDE-9026
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtimes
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
JBoss Runtime detection should not assume all plugins are available especially with drools
and jbpm plugins being separated out for SOA pack.
Copied from JBIDE-8456:
2. org.jboss.tools.runtime
It contains a plugin that implements the JBoss AS, Drools, Seam and jBPM detectors and
depends on AS, Drools, jBPM, Seam and JBoss Runtime Detection Core.
The problem was because JBDS installer detection wasn't separating AS runtime within
EAP, EPP, SOA-P ... from Seam, Drools, jBPM runtimes. I have inherited that code.
Because of that, all these detectors are included in the org.jboss.tools.runtime plugin.
If we want to separate those dependencies, we need to do the following:
separate the Drools, Seam, jBPM detectors from the AS/EAP/EPP/SOA-P detector
move runtime detectors to separated features (the AS, Drools, jBPM, Seam, ESB feature
or some new features)
change the JBDS installer detection code according to these changes
As to optional dependencies, P2 treats them as hard dependencies. If IU exists, P2 will
install it no matter if it is optional or not. Currently only the drools dependency is
optional.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:43 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9026) Separate specific runtime detection plugins from base core
[
https://issues.jboss.org/browse/JBIDE-9026?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-9026:
--------------------------------------
Do we need to create new features as:
- JBoss AS Runtime detector
- JBoss Seam Runtime detector
...
or we need to add detectors to corresponding features (AS, Seam, Drools, jBPM ...)?
Since Drools, Seam, jBPM will be independent on AS/EAP/EPP/SOA-P, the user won't be
able to see if any of those runtimes is included in EAP/EPP/SOA-P. The TreeTable viewer
introduced by JBIDE-8128 has to be removed and all the runtimes will be shown separately.
Is that OK?
Separate specific runtime detection plugins from base core
-----------------------------------------------------------
Key: JBIDE-9026
URL: https://issues.jboss.org/browse/JBIDE-9026
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtimes
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
JBoss Runtime detection should not assume all plugins are available especially with
drools and jbpm plugins being separated out for SOA pack.
Copied from JBIDE-8456:
2. org.jboss.tools.runtime
It contains a plugin that implements the JBoss AS, Drools, Seam and jBPM detectors and
depends on AS, Drools, jBPM, Seam and JBoss Runtime Detection Core.
The problem was because JBDS installer detection wasn't separating AS runtime within
EAP, EPP, SOA-P ... from Seam, Drools, jBPM runtimes. I have inherited that code.
Because of that, all these detectors are included in the org.jboss.tools.runtime plugin.
If we want to separate those dependencies, we need to do the following:
separate the Drools, Seam, jBPM detectors from the AS/EAP/EPP/SOA-P detector
move runtime detectors to separated features (the AS, Drools, jBPM, Seam, ESB feature
or some new features)
change the JBDS installer detection code according to these changes
As to optional dependencies, P2 treats them as hard dependencies. If IU exists, P2 will
install it no matter if it is optional or not. Currently only the drools dependency is
optional.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:14 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9026) Separate specific runtime detection plugins from base core
[
https://issues.jboss.org/browse/JBIDE-9026?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9026:
--------------------------------------------
doesnt the detectors say from within what detectors they should be used to find possible
subparts?
Separate specific runtime detection plugins from base core
-----------------------------------------------------------
Key: JBIDE-9026
URL: https://issues.jboss.org/browse/JBIDE-9026
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtimes
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
JBoss Runtime detection should not assume all plugins are available especially with
drools and jbpm plugins being separated out for SOA pack.
Copied from JBIDE-8456:
2. org.jboss.tools.runtime
It contains a plugin that implements the JBoss AS, Drools, Seam and jBPM detectors and
depends on AS, Drools, jBPM, Seam and JBoss Runtime Detection Core.
The problem was because JBDS installer detection wasn't separating AS runtime within
EAP, EPP, SOA-P ... from Seam, Drools, jBPM runtimes. I have inherited that code.
Because of that, all these detectors are included in the org.jboss.tools.runtime plugin.
If we want to separate those dependencies, we need to do the following:
separate the Drools, Seam, jBPM detectors from the AS/EAP/EPP/SOA-P detector
move runtime detectors to separated features (the AS, Drools, jBPM, Seam, ESB feature
or some new features)
change the JBDS installer detection code according to these changes
As to optional dependencies, P2 treats them as hard dependencies. If IU exists, P2 will
install it no matter if it is optional or not. Currently only the drools dependency is
optional.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:36 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9026) Separate specific runtime detection plugins from base core
[
https://issues.jboss.org/browse/JBIDE-9026?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-9026:
--------------------------------------
doesnt the detectors say from within what detectors they should be
used to find possible subparts?
Will try to implement.
Do I need to create new features or I need to add the detectors to the existing features?
Separate specific runtime detection plugins from base core
-----------------------------------------------------------
Key: JBIDE-9026
URL: https://issues.jboss.org/browse/JBIDE-9026
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtimes
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
JBoss Runtime detection should not assume all plugins are available especially with
drools and jbpm plugins being separated out for SOA pack.
Copied from JBIDE-8456:
2. org.jboss.tools.runtime
It contains a plugin that implements the JBoss AS, Drools, Seam and jBPM detectors and
depends on AS, Drools, jBPM, Seam and JBoss Runtime Detection Core.
The problem was because JBDS installer detection wasn't separating AS runtime within
EAP, EPP, SOA-P ... from Seam, Drools, jBPM runtimes. I have inherited that code.
Because of that, all these detectors are included in the org.jboss.tools.runtime plugin.
If we want to separate those dependencies, we need to do the following:
separate the Drools, Seam, jBPM detectors from the AS/EAP/EPP/SOA-P detector
move runtime detectors to separated features (the AS, Drools, jBPM, Seam, ESB feature
or some new features)
change the JBDS installer detection code according to these changes
As to optional dependencies, P2 treats them as hard dependencies. If IU exists, P2 will
install it no matter if it is optional or not. Currently only the drools dependency is
optional.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:09 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9026) Separate specific runtime detection plugins from base core
[
https://issues.jboss.org/browse/JBIDE-9026?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9026:
--------------------------------------------
Not sure where the split need to be - but if the SOA tools will want to release later on
the soa bits needs at least to be in their own feature (might even have to move to a
separate module). And in all cases we need to be sure we got an API in place we can commit
to being stable and maintain going forward.
Separate specific runtime detection plugins from base core
-----------------------------------------------------------
Key: JBIDE-9026
URL: https://issues.jboss.org/browse/JBIDE-9026
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtimes
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
JBoss Runtime detection should not assume all plugins are available especially with
drools and jbpm plugins being separated out for SOA pack.
Copied from JBIDE-8456:
2. org.jboss.tools.runtime
It contains a plugin that implements the JBoss AS, Drools, Seam and jBPM detectors and
depends on AS, Drools, jBPM, Seam and JBoss Runtime Detection Core.
The problem was because JBDS installer detection wasn't separating AS runtime within
EAP, EPP, SOA-P ... from Seam, Drools, jBPM runtimes. I have inherited that code.
Because of that, all these detectors are included in the org.jboss.tools.runtime plugin.
If we want to separate those dependencies, we need to do the following:
separate the Drools, Seam, jBPM detectors from the AS/EAP/EPP/SOA-P detector
move runtime detectors to separated features (the AS, Drools, jBPM, Seam, ESB feature
or some new features)
change the JBDS installer detection code according to these changes
As to optional dependencies, P2 treats them as hard dependencies. If IU exists, P2 will
install it no matter if it is optional or not. Currently only the drools dependency is
optional.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:38 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9026) Separate specific runtime detection plugins from base core
[
https://issues.jboss.org/browse/JBIDE-9026?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-9026:
--------------------------------------
For now, I will create new features within the runtime component. Agree ?
Separate specific runtime detection plugins from base core
-----------------------------------------------------------
Key: JBIDE-9026
URL: https://issues.jboss.org/browse/JBIDE-9026
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtimes
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
JBoss Runtime detection should not assume all plugins are available especially with
drools and jbpm plugins being separated out for SOA pack.
Copied from JBIDE-8456:
2. org.jboss.tools.runtime
It contains a plugin that implements the JBoss AS, Drools, Seam and jBPM detectors and
depends on AS, Drools, jBPM, Seam and JBoss Runtime Detection Core.
The problem was because JBDS installer detection wasn't separating AS runtime within
EAP, EPP, SOA-P ... from Seam, Drools, jBPM runtimes. I have inherited that code.
Because of that, all these detectors are included in the org.jboss.tools.runtime plugin.
If we want to separate those dependencies, we need to do the following:
separate the Drools, Seam, jBPM detectors from the AS/EAP/EPP/SOA-P detector
move runtime detectors to separated features (the AS, Drools, jBPM, Seam, ESB feature
or some new features)
change the JBDS installer detection code according to these changes
As to optional dependencies, P2 treats them as hard dependencies. If IU exists, P2 will
install it no matter if it is optional or not. Currently only the drools dependency is
optional.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:15 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9026) Separate specific runtime detection plugins from base core
[
https://issues.jboss.org/browse/JBIDE-9026?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9026:
--------------------------------------------
agree
Separate specific runtime detection plugins from base core
-----------------------------------------------------------
Key: JBIDE-9026
URL: https://issues.jboss.org/browse/JBIDE-9026
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtimes
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
JBoss Runtime detection should not assume all plugins are available especially with
drools and jbpm plugins being separated out for SOA pack.
Copied from JBIDE-8456:
2. org.jboss.tools.runtime
It contains a plugin that implements the JBoss AS, Drools, Seam and jBPM detectors and
depends on AS, Drools, jBPM, Seam and JBoss Runtime Detection Core.
The problem was because JBDS installer detection wasn't separating AS runtime within
EAP, EPP, SOA-P ... from Seam, Drools, jBPM runtimes. I have inherited that code.
Because of that, all these detectors are included in the org.jboss.tools.runtime plugin.
If we want to separate those dependencies, we need to do the following:
separate the Drools, Seam, jBPM detectors from the AS/EAP/EPP/SOA-P detector
move runtime detectors to separated features (the AS, Drools, jBPM, Seam, ESB feature
or some new features)
change the JBDS installer detection code according to these changes
As to optional dependencies, P2 treats them as hard dependencies. If IU exists, P2 will
install it no matter if it is optional or not. Currently only the drools dependency is
optional.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:01 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9026) Separate specific runtime detection plugins from base core
[
https://issues.jboss.org/browse/JBIDE-9026?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-9026:
---------------------------------------
Fix Version/s: 3.3.0.M2
Setting fix version.
Separate specific runtime detection plugins from base core
-----------------------------------------------------------
Key: JBIDE-9026
URL: https://issues.jboss.org/browse/JBIDE-9026
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtimes
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 3.3.0.M2
JBoss Runtime detection should not assume all plugins are available especially with
drools and jbpm plugins being separated out for SOA pack.
Copied from JBIDE-8456:
2. org.jboss.tools.runtime
It contains a plugin that implements the JBoss AS, Drools, Seam and jBPM detectors and
depends on AS, Drools, jBPM, Seam and JBoss Runtime Detection Core.
The problem was because JBDS installer detection wasn't separating AS runtime within
EAP, EPP, SOA-P ... from Seam, Drools, jBPM runtimes. I have inherited that code.
Because of that, all these detectors are included in the org.jboss.tools.runtime plugin.
If we want to separate those dependencies, we need to do the following:
separate the Drools, Seam, jBPM detectors from the AS/EAP/EPP/SOA-P detector
move runtime detectors to separated features (the AS, Drools, jBPM, Seam, ESB feature
or some new features)
change the JBDS installer detection code according to these changes
As to optional dependencies, P2 treats them as hard dependencies. If IU exists, P2 will
install it no matter if it is optional or not. Currently only the drools dependency is
optional.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:26 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9026) Separate specific runtime detection plugins from base core
[
https://issues.jboss.org/browse/JBIDE-9026?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-9026:
--------------------------------------
Now, the runtime component contains 6 features:
1) o.j.t.runtime.core.feature
The feature contains the Runtime Detection model and UI. It doesn't have the JBT/SOA
dependencies.
2) o.j.t.runtime feature
The feature contains the org.eclipse.ui.startup ext.point which activates the runtime
detection when starting Eclipse.
It depends on the o.j.t.runtime.core.feature.
3) o.j.t.runtime.as.detector.feature
The feature contains the JBoss AS detector. It depends on the o.j.t.runtime.core and as
plugin.
4) o.j.t.runtime.seam.detector.feature
The feature contains the JBoss Seam detector. It depends on the o.j.t.runtime.core and
seam plugin.
5) o.j.t.runtime.drools.detector.feature
The feature contains the Drools detector. It depends on the o.j.t.runtime.core and drools
plugin.
6) o.j.t.runtime.jbpm.detector.feature
The feature contains the jBPM detector. It depends on the o.j.t.runtime.core and jbpm
plugin.
We can separate o.j.t.runtime.drools.detector.feature and
o.j.t.runtime.jbpm.detector.feature to a new component (soadetectors) that would depend on
o.j.t.runtime.core, drools and jbpm.
Separate specific runtime detection plugins from base core
-----------------------------------------------------------
Key: JBIDE-9026
URL: https://issues.jboss.org/browse/JBIDE-9026
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtimes
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 3.3.0.M2
JBoss Runtime detection should not assume all plugins are available especially with
drools and jbpm plugins being separated out for SOA pack.
Copied from JBIDE-8456:
2. org.jboss.tools.runtime
It contains a plugin that implements the JBoss AS, Drools, Seam and jBPM detectors and
depends on AS, Drools, jBPM, Seam and JBoss Runtime Detection Core.
The problem was because JBDS installer detection wasn't separating AS runtime within
EAP, EPP, SOA-P ... from Seam, Drools, jBPM runtimes. I have inherited that code.
Because of that, all these detectors are included in the org.jboss.tools.runtime plugin.
If we want to separate those dependencies, we need to do the following:
separate the Drools, Seam, jBPM detectors from the AS/EAP/EPP/SOA-P detector
move runtime detectors to separated features (the AS, Drools, jBPM, Seam, ESB feature
or some new features)
change the JBDS installer detection code according to these changes
As to optional dependencies, P2 treats them as hard dependencies. If IU exists, P2 will
install it no matter if it is optional or not. Currently only the drools dependency is
optional.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:09 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-9026) Separate specific runtime detection plugins from base core
[
https://issues.jboss.org/browse/JBIDE-9026?page=com.atlassian.jira.plugin...
]
Snjezana Peco resolved JBIDE-9026.
----------------------------------
Resolution: Done
Separate specific runtime detection plugins from base core
-----------------------------------------------------------
Key: JBIDE-9026
URL: https://issues.jboss.org/browse/JBIDE-9026
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtimes
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 3.3.0.M2
JBoss Runtime detection should not assume all plugins are available especially with
drools and jbpm plugins being separated out for SOA pack.
Copied from JBIDE-8456:
2. org.jboss.tools.runtime
It contains a plugin that implements the JBoss AS, Drools, Seam and jBPM detectors and
depends on AS, Drools, jBPM, Seam and JBoss Runtime Detection Core.
The problem was because JBDS installer detection wasn't separating AS runtime within
EAP, EPP, SOA-P ... from Seam, Drools, jBPM runtimes. I have inherited that code.
Because of that, all these detectors are included in the org.jboss.tools.runtime plugin.
If we want to separate those dependencies, we need to do the following:
separate the Drools, Seam, jBPM detectors from the AS/EAP/EPP/SOA-P detector
move runtime detectors to separated features (the AS, Drools, jBPM, Seam, ESB feature
or some new features)
change the JBDS installer detection code according to these changes
As to optional dependencies, P2 treats them as hard dependencies. If IU exists, P2 will
install it no matter if it is optional or not. Currently only the drools dependency is
optional.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-9026) Separate specific runtime detection plugins from base core
[
https://issues.jboss.org/browse/JBIDE-9026?page=com.atlassian.jira.plugin...
]
Libor Zoubek closed JBIDE-9026.
-------------------------------
Separate specific runtime detection plugins from base core
-----------------------------------------------------------
Key: JBIDE-9026
URL: https://issues.jboss.org/browse/JBIDE-9026
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtimes
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 3.3.0.M2
JBoss Runtime detection should not assume all plugins are available especially with
drools and jbpm plugins being separated out for SOA pack.
Copied from JBIDE-8456:
2. org.jboss.tools.runtime
It contains a plugin that implements the JBoss AS, Drools, Seam and jBPM detectors and
depends on AS, Drools, jBPM, Seam and JBoss Runtime Detection Core.
The problem was because JBDS installer detection wasn't separating AS runtime within
EAP, EPP, SOA-P ... from Seam, Drools, jBPM runtimes. I have inherited that code.
Because of that, all these detectors are included in the org.jboss.tools.runtime plugin.
If we want to separate those dependencies, we need to do the following:
separate the Drools, Seam, jBPM detectors from the AS/EAP/EPP/SOA-P detector
move runtime detectors to separated features (the AS, Drools, jBPM, Seam, ESB feature
or some new features)
change the JBDS installer detection code according to these changes
As to optional dependencies, P2 treats them as hard dependencies. If IU exists, P2 will
install it no matter if it is optional or not. Currently only the drools dependency is
optional.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5408
days inactive
5434
days old
jbosstools-issues@lists.jboss.org
10 comments
3 participants
participants (3)
-
Libor Zoubek (JIRA) -
Max Rydahl Andersen (JIRA)
-
Snjezana Peco (JIRA)