[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Marcel Bruch commented on JBDS-3566:
------------------------------------
See JBDS-3600 for additional information. It seems there is some information about how to use the AERI server extension point is missing.
I have also no information where the above referred discovery file comes from. Looking at its contents ("submitUrl" : "https://dev.eclipse.org/recommenders/community/confess/0.6/reports/") it looks like an leftover of an incomplete early experiment.
Is there a wiki page where we can collect all required information about how to integrate AERI into the various JBoss Tools editions?
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Attachments: aeri-in-jbds91.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3600) include AERI in JBDS 10
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBDS-3600?page=com.atlassian.jira.plugin.... ]
Marcel Bruch commented on JBDS-3600:
------------------------------------
Nick,
Since you already made it work in another setup, I assume you know how servers are contributed to AERI. Is that correct? If not, please let me know. I'll happily provide the missing information.
Having said this, I've two questions:
1. Which plugin contributes the error reporting extension point contribution? If no server shows up in the configure dialog I assume there is no plugin that contributes the extension.
2.Where does "-Dorg.eclipse.recommenders.stacktraces.rcp.serverUrl" come from? This property should not / cannot be used anymore for two reasons: 1. It does not make sense with the extension point definition we use. All required information to configure an additional error reporting server is located in the plugin.xml. Thus, there is no need to specify the server urls via a system property. 2. That system property was used *until* a year ago when AERI was located under the Recommenders project. The namespace changed with its move to EPP in March last year. So this property is never read anymore.
To make it work:
Please point me to the plugin.xml that contributes a server extension similar to [1].
Thanks.
[1] https://git.eclipse.org/c/epp/org.eclipse.epp.logging.git/tree/examples/a...
> include AERI in JBDS 10
> -----------------------
>
> Key: JBDS-3600
> URL: https://issues.jboss.org/browse/JBDS-3600
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: aeri-in-jbds10.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21835) Server adapter: incremental deployment is broken
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21835?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21835:
--------------------------------
Description:
Running OS 3.1.1 from https://github.com/redhat-developer-tooling/openshift-vagrant/tree/master...
Deploy an eap basic app on openshift,
import the kitchensink code in the workspace
wait for the application to deploy and run on openshift
Issue #1
- when creating a server adapter from the OpenShift Explorer menu "Server Adapter...", on the eap service, the server has no module. The project is treated as a magic project.
- After making a change to the index page and saving, the page is incrementally pushed to the openshift server, and then the ROOT.war restart. It's not supposed to
Issue #2
- create a new server adapter from the Servers view. Add the kitchensink project as a module to the last page of the wizard
- jbosstools-kitchensink.war is deployed to the remote server. Both ROOT.war and jbosstools-kitchensink.war start, access to the / context root fails. It's been superseded by jbosstools-kitchensink
- local change is not pushed immediately to the server. module restart happens before the change is effective.
(Fred indicates this issue was not replicatable on most recent test)
was:
Running OS 3.1.1 from https://github.com/redhat-developer-tooling/openshift-vagrant/tree/master...
Deploy an eap basic app on openshift,
import the kitchensink code in the workspace
wait for the application to deploy and run on openshift
- when creating a server adapter from the OpenShift Explorer menu "Server Adapter...", on the eap service, the server has no module. The project is treated as a magic project.
- After making a change to the index page and saving, the page is incrementally pushed to the openshift server, and then the ROOT.war restart. It's not supposed to
- create a new server adapter from the Servers view. Add the kitchensink project as a module to the last page of the wizard
- jbosstools-kitchensink.war is deployed to the remote server. Both ROOT.war and jbosstools-kitchensink.war start, access to the / context root fails. It's been superseded by jbosstools-kitchensink
- local change is not pushed immediately to the server. module restart happens before the change is effective.
> Server adapter: incremental deployment is broken
> ------------------------------------------------
>
> Key: JBIDE-21835
> URL: https://issues.jboss.org/browse/JBIDE-21835
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Running OS 3.1.1 from https://github.com/redhat-developer-tooling/openshift-vagrant/tree/master...
> Deploy an eap basic app on openshift,
> import the kitchensink code in the workspace
> wait for the application to deploy and run on openshift
> Issue #1
> - when creating a server adapter from the OpenShift Explorer menu "Server Adapter...", on the eap service, the server has no module. The project is treated as a magic project.
> - After making a change to the index page and saving, the page is incrementally pushed to the openshift server, and then the ROOT.war restart. It's not supposed to
> Issue #2
> - create a new server adapter from the Servers view. Add the kitchensink project as a module to the last page of the wizard
> - jbosstools-kitchensink.war is deployed to the remote server. Both ROOT.war and jbosstools-kitchensink.war start, access to the / context root fails. It's been superseded by jbosstools-kitchensink
> - local change is not pushed immediately to the server. module restart happens before the change is effective.
> (Fred indicates this issue was not replicatable on most recent test)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3375) JBDS target platform zip contains both packed and unpacked artifacts
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3375?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3375.
----------------------------
Resolution: Rejected
Rejected.
> JBDS target platform zip contains both packed and unpacked artifacts
> --------------------------------------------------------------------
>
> Key: JBDS-3375
> URL: https://issues.jboss.org/browse/JBDS-3375
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Components: build, target-platform, updatesite
> Affects Versions: 9.0.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 9.x
>
>
> I've got two approaches now for including the JBDS target platform into the JBDS update site.
> a) mirror the TP site - size on disk is 328M and the increase in size to JBDS update site is about 200M
> b) wget the TP zip and unpack - size on disk after unzipping is 458M
> So... not sure which approach is more efficient given the zip is a single file to download, but it's 130M (more than 1/3rd) larger.
> If we can remove the packed (or unpacked) artifacts from the zip, we'd certainly win.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3600) include AERI in JBDS 10
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3600?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3600 at 3/11/16 6:06 PM:
-----------------------------------------------------------
I can't make Aeri work in JBDS 10.0.0.Alpha1.
I've created a dummy aeri-discovery site here:
https://devstudio.jboss.com/10.0/aeri-discovery/
I've tried installation of jboss-devstudio-10.0.0.Alpha1-v20160311-1742-B4952-installer-standalone.jar against a fresh workspace, then launching it thus:
{code}./jbdevstudio -Dorg.eclipse.recommenders.stacktraces.rcp.serverUrl=https://devstudio.jboss.com/10.0/aeri-discovery{code}
Also tried adding the -D flag directly into the jbdevstudio.ini file. In both cases, I get this when I go to Window > Prefs > General > Error Reporting > Servers...
!aeri-in-jbds10.png!
But I can't get the AERI reporting to fire when I cause problem in p2, as suggested above.
And, unlike in JBDS 9.1.0.CR1, there's not even a JBoss Tools aeri tracker (see https://issues.jboss.org/browse/JBDS-3566?focusedCommentId=13175673&page=... )
was (Author: nickboldt):
I can't make Aeri work in JBDS 10.0.0.Alpha1.
I've created a dummy aeri-discovery site here:
https://devstudio.jboss.com/10.0/aeri-discovery/
I've tried installation of jboss-devstudio-10.0.0.Alpha1-v20160311-1742-B4952-installer-standalone.jar against a fresh workspace, then launching it thus:
{code}./jbdevstudio -Dorg.eclipse.recommenders.stacktraces.rcp.serverUrl=https://devstudio.jboss.com/10.0/aeri-discovery{code}
Also tried adding the -D flag directly into the jbdevstudio.ini file. In both cases, I get this when I go to Window > Prefs > General > Error Reporting > Servers...
!aeri-in-jbds10.png!
But I can't get the AERI reporting to fire when I cause problem in p2, as suggested above.
> include AERI in JBDS 10
> -----------------------
>
> Key: JBDS-3600
> URL: https://issues.jboss.org/browse/JBDS-3600
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: aeri-in-jbds10.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3600) include AERI in JBDS 10
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3600?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3600:
-----------------------------
Attachment: aeri-in-jbds10.png
I can't make Aeri work in JBDS 10.0.0.Alpha1.
I've created a dummy aeri-discovery site here:
https://devstudio.jboss.com/10.0/aeri-discovery/
I've tried installation of jboss-devstudio-10.0.0.Alpha1-v20160311-1742-B4952-installer-standalone.jar against a fresh workspace, then launching it thus:
{code}./jbdevstudio -Dorg.eclipse.recommenders.stacktraces.rcp.serverUrl=https://devstudio.jboss.com/10.0/aeri-discovery{code}
Also tried adding the -D flag directly into the jbdevstudio.ini file. In both cases, I get this when I go to Window > Prefs > General > Error Reporting > Servers...
!aeri-in-jbds10.png!
But I can't get the AERI reporting to fire when I cause problem in p2, as suggested above.
> include AERI in JBDS 10
> -----------------------
>
> Key: JBDS-3600
> URL: https://issues.jboss.org/browse/JBDS-3600
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: aeri-in-jbds10.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3566:
----------------------------------
Note that in JBDS 10, the problem is even worse... the JBoss Tools Project isn't even shown in the above dialog. See JBDS-3600 for details.
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Attachments: aeri-in-jbds91.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month