[JBoss JIRA] (JBIDE-13799) Source Lookup enhancements
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13799?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-13799:
---------------------------------------
{quote}
i.e. this should be separate PR:
AS 7.2/EAP 6.1 are now recognized correctly
the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2
the fix for the ConcurrentModificationException exception
{quote}
They are minor fixes. I have included them in one jira because the remaining features described here, don't work correctly without them.
{quote}
And what does
"included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container" mean ? Doesn't the source container now have knowledge that the AS container should have instead ?
{quote}
There are the "Include pattern"/"Exclude pattern" fields on the Source Lookup preferences page. You can enter a regular expression to filter the included/excluded libraries. That isn't related to a JBoss AS server except that the default values are set to exclude the jsf 1.2 and hibernate3 libraries for it (the container includes only the jsf 2.1 and hibernate4 libraries).
That is a feature users have required.
Please take a look at the screencast.
{quote}
And this:
"JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search)"
sounds really interesting - but isn't this a separate jira/feature ? What kind of external container is used here ?
{quote}
There is a separate container added to the ".JBoss Servers" project that is hidden and contains JBoss libraries. They are the same as the libraries included in the Source Lookup. This way, the classes from a JBoss AS server can be searched using the standard Java Search engine.
This has also been required by a user.
{quote}
"JBoss Java Project Source Container"
This one is also separate feature afacis - the name is not very informative of what it do, nor why this is needed and how it work - i.e. why is the default Maven source container not enough?
{quote}
I suppose you are talking about the JBoss Maven source container. It contains libraries from a JBoss server. The JBoss Java Project Source Container contains libraries from the project's classpath.
To be clarify, you could take a look at the screencast.
If you still think it is important to separate these bugs/features, I will do it.
However, they are related to each other and will probably have to be applied at the same time.
> Source Lookup enhancements
> --------------------------
>
> Key: JBIDE-13799
> URL: https://issues.jboss.org/browse/JBIDE-13799
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
>
> The PR includes the following enhancements:
> - AS 7.2/EAP 6.1 are now recognized correctly
> - the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2
> - the fix for the ConcurrentModificationException exception
> - included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container
> - JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search)
> - JBoss Java Project Source Container
> See http://screencast.com/t/39LHqYx5m
> Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2.
> Note:
> You have to have some deployment on the servers in order the WeldBootstrap class to be created.
> You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason.
> The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13834) install-grinder tests fail due to missing deps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13834?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13834 at 3/21/13 11:54 AM:
--------------------------------------------------------------
To better link central discovery site production w/ automated testing of that site, I've linked these jobs so that install always follows a rebuild of discovery:
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.discovery_... produces discovery plugins, directory.xml files, and composite site
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... installs from JBT and JBDS Central sites
was (Author: nickboldt):
To better link central discovery site production w/ automated testing of that site, we might want to consider linking or merging these two jobs:
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.discovery_... produces discovery plugins, directory.xml files, and composite site
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... installs from JBT and JBDS Central sites
> install-grinder tests fail due to missing deps
> ----------------------------------------------
>
> Key: JBIDE-13834
> URL: https://issues.jboss.org/browse/JBIDE-13834
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-install-grinder.install-tests.matrix_master/90/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fbuilds%2Fstaging%2Fdevstudio-7.0_trunk.updatesite%2Fproduct%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fbuilds%2Fstaging%2Fdevstudio-7.0_trunk.updatesite%2Fproduct%2Fdevstudio-directory.xml,eclipseBundleVersion=kepler.M5,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/console}
> Contains: Only one of the following can be installed at once:
> Contains: Overlay support for Eclipse WTP (Incubation) 0.17.0.20130212-1819 (org.eclipse.m2e.wtp.overlay 0.17.0.20130212-1819)
> Contains: Overlay support for Eclipse WTP (Incubation) 0.17.0.20130205-1928 (org.eclipse.m2e.wtp.overlay 0.17.0.20130205-1928)
> Contains: Overlay support for Eclipse WTP (Incubation) 0.17.0.20121219-1146 (org.eclipse.m2e.wtp.overlay 0.17.0.20121219-1146)
> Contains: Cannot satisfy dependency:
> Contains: From: Maven Integration (Selected) 7.0.0.Alpha1-v20130206-0326-B3219 (com.jboss.jbds.m2e.feature.feature.group 7.0.0.Alpha1-v20130206-0326-B3219)
> Contains: To: org.eclipse.m2e.wtp.feature.feature.group [0.17.0.20130205-1928]
> Contains: Cannot satisfy dependency:
> Contains: From: m2e-wtp - Maven Integration for WTP (Incubation) 0.17.0.20130205-1928 (org.eclipse.m2e.wtp.feature.feature.group 0.17.0.20130205-1928)
> Contains: To: org.eclipse.m2e.wtp.overlay [0.17.0.20130205-1928]
> Contains: Cannot satisfy dependency:
> Contains: From: m2e-wtp - Maven Integration for WTP (Incubation) 0.17.0.20130212-1819 (org.eclipse.m2e.wtp.feature.feature.group 0.17.0.20130212-1819)
> Contains: To: org.eclipse.m2e.wtp.overlay [0.17.0.20130212-1819]
> {code}
> Should clone this job so we have a stable branch version available too, pulling from these locations:
> * http://download.jboss.org/jbosstools/discovery/nightly/core/4.1.kepler/
> * http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/4.1.kepler/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13835) Improve publish script (split? Move to maven?)
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-13835:
--------------------------------------
Summary: Improve publish script (split? Move to maven?)
Key: JBIDE-13835
URL: https://issues.jboss.org/browse/JBIDE-13835
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Reporter: Mickael Istria
Fix For: 4.1.0.Alpha2
Publish script deals with a lot of different and not-always-related things. It makes it difficult to maintain it. We should think about some improvements such as
* different conventions from different stream
* components vs aggregate
* devstudio vs jbosstools.
Or,
* Make publishing part of a "mvn deploy" step.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13834) install-grinder tests fail due to missing deps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13834?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13834:
------------------------------------
To better link central discovery site production w/ automated testing of that site, we might want to consider linking or merging these two jobs:
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.discovery_... produces discovery plugins, directory.xml files, and composite site
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... installs from JBT and JBDS Central sites
> install-grinder tests fail due to missing deps
> ----------------------------------------------
>
> Key: JBIDE-13834
> URL: https://issues.jboss.org/browse/JBIDE-13834
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, updatesite
> Affects Versions: 4.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-install-grinder.install-tests.matrix_master/90/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fbuilds%2Fstaging%2Fdevstudio-7.0_trunk.updatesite%2Fproduct%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fbuilds%2Fstaging%2Fdevstudio-7.0_trunk.updatesite%2Fproduct%2Fdevstudio-directory.xml,eclipseBundleVersion=kepler.M5,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/console}
> Contains: Only one of the following can be installed at once:
> Contains: Overlay support for Eclipse WTP (Incubation) 0.17.0.20130212-1819 (org.eclipse.m2e.wtp.overlay 0.17.0.20130212-1819)
> Contains: Overlay support for Eclipse WTP (Incubation) 0.17.0.20130205-1928 (org.eclipse.m2e.wtp.overlay 0.17.0.20130205-1928)
> Contains: Overlay support for Eclipse WTP (Incubation) 0.17.0.20121219-1146 (org.eclipse.m2e.wtp.overlay 0.17.0.20121219-1146)
> Contains: Cannot satisfy dependency:
> Contains: From: Maven Integration (Selected) 7.0.0.Alpha1-v20130206-0326-B3219 (com.jboss.jbds.m2e.feature.feature.group 7.0.0.Alpha1-v20130206-0326-B3219)
> Contains: To: org.eclipse.m2e.wtp.feature.feature.group [0.17.0.20130205-1928]
> Contains: Cannot satisfy dependency:
> Contains: From: m2e-wtp - Maven Integration for WTP (Incubation) 0.17.0.20130205-1928 (org.eclipse.m2e.wtp.feature.feature.group 0.17.0.20130205-1928)
> Contains: To: org.eclipse.m2e.wtp.overlay [0.17.0.20130205-1928]
> Contains: Cannot satisfy dependency:
> Contains: From: m2e-wtp - Maven Integration for WTP (Incubation) 0.17.0.20130212-1819 (org.eclipse.m2e.wtp.feature.feature.group 0.17.0.20130212-1819)
> Contains: To: org.eclipse.m2e.wtp.overlay [0.17.0.20130212-1819]
> {code}
> Should clone this job so we have a stable branch version available too, pulling from these locations:
> * http://download.jboss.org/jbosstools/discovery/nightly/core/4.1.kepler/
> * http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/4.1.kepler/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13824) update install-grinder jobs to use short workspace & INSTALL_PLAN instead of groovy environment variable hack
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13824?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13824 at 3/21/13 11:16 AM:
--------------------------------------------------------------
I've tweaked both jobs mentioned above, so we should be good here.
Spinning:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=9
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=88
was (Author: nickboldt):
I've tweaked both jobs mentioned above, so we should be good here.
> update install-grinder jobs to use short workspace & INSTALL_PLAN instead of groovy environment variable hack
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13824
> URL: https://issues.jboss.org/browse/JBIDE-13824
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, testing-tools
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.upgrade-tests.matrix/7/console}
> Started by user nboldt(a)REDHAT.COM
> [EnvInject] - Loading node environment variables.
> [EnvInject] - Preparing an environment for the build.
> [EnvInject] - Keeping Jenkins system variables.
> [EnvInject] - Keeping Jenkins build variables.
> [EnvInject] - Adding build parameters as variables.
> [EnvInject] - Evaluation the following Groovy script content:
> // Horrible hack to set PRODUCT !
> import hudson.model.*
> def thr = Thread.currentThread()
> def build = thr?.executable
> def resolver = build.buildVariableResolver
> def url = resolver.resolve("INSTALL_URL")
> String product = url.contains("devstudio") ? "devstudio" : "jbosstools"
> String proto = url.contains("devstudio.jboss.com") ? "https" : "http"
> [PRODUCT: product, PROTO: proto]
> [EnvInject] - [ERROR] - SEVERE ERROR occurs: No such property: executable for class: hudson.model.OneOffExecutor
> Notifying upstream projects of job completion
> Finished: FAILURE
> {code}
> Similar problem (which I worked around by removing the check on url and just hardcoding the values of product and proto):
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests.matrix/77/console}
> Started by user nboldt(a)REDHAT.COM
> [EnvInject] - Loading node environment variables.
> [EnvInject] - Preparing an environment for the build.
> [EnvInject] - Keeping Jenkins system variables.
> [EnvInject] - Keeping Jenkins build variables.
> [EnvInject] - Adding build parameters as variables.
> [EnvInject] - Evaluation the following Groovy script content:
> // Horrible hack to set PRODUCT !
> import hudson.model.*
> def thr = Thread.currentThread()
> def build = thr?.getCurrentExecutable()
> def resolver = build.buildVariableResolver
> def url = resolver.resolve("INSTALL_URL")
> String product = url.contains("devstudio") ? "devstudio" : "jbosstools"
> String proto = url.contains("devstudio.jboss.com") ? "https" : "http"
> [PRODUCT: product, PROTO: proto]
> [EnvInject] - [ERROR] - SEVERE ERROR occurs: Cannot invoke method contains() on null object
> Notifying upstream projects of job completion
> Finished: FAILURE{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13834) install-grinder tests fail due to missing deps
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13834:
----------------------------------
Summary: install-grinder tests fail due to missing deps
Key: JBIDE-13834
URL: https://issues.jboss.org/browse/JBIDE-13834
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, updatesite
Affects Versions: 4.1.0.Alpha2
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.1.0.Alpha2
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-install-grinder.install-tests.matrix_master/90/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fbuilds%2Fstaging%2Fdevstudio-7.0_trunk.updatesite%2Fproduct%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fbuilds%2Fstaging%2Fdevstudio-7.0_trunk.updatesite%2Fproduct%2Fdevstudio-directory.xml,eclipseBundleVersion=kepler.M5,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/console}
Contains: Only one of the following can be installed at once:
Contains: Overlay support for Eclipse WTP (Incubation) 0.17.0.20130212-1819 (org.eclipse.m2e.wtp.overlay 0.17.0.20130212-1819)
Contains: Overlay support for Eclipse WTP (Incubation) 0.17.0.20130205-1928 (org.eclipse.m2e.wtp.overlay 0.17.0.20130205-1928)
Contains: Overlay support for Eclipse WTP (Incubation) 0.17.0.20121219-1146 (org.eclipse.m2e.wtp.overlay 0.17.0.20121219-1146)
Contains: Cannot satisfy dependency:
Contains: From: Maven Integration (Selected) 7.0.0.Alpha1-v20130206-0326-B3219 (com.jboss.jbds.m2e.feature.feature.group 7.0.0.Alpha1-v20130206-0326-B3219)
Contains: To: org.eclipse.m2e.wtp.feature.feature.group [0.17.0.20130205-1928]
Contains: Cannot satisfy dependency:
Contains: From: m2e-wtp - Maven Integration for WTP (Incubation) 0.17.0.20130205-1928 (org.eclipse.m2e.wtp.feature.feature.group 0.17.0.20130205-1928)
Contains: To: org.eclipse.m2e.wtp.overlay [0.17.0.20130205-1928]
Contains: Cannot satisfy dependency:
Contains: From: m2e-wtp - Maven Integration for WTP (Incubation) 0.17.0.20130212-1819 (org.eclipse.m2e.wtp.feature.feature.group 0.17.0.20130212-1819)
Contains: To: org.eclipse.m2e.wtp.overlay [0.17.0.20130212-1819]
{code}
Should clone this job so we have a stable branch version available too, pulling from these locations:
* http://download.jboss.org/jbosstools/discovery/nightly/core/4.1.kepler/
* http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/4.1.kepler/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13824) update install-grinder jobs to use short workspace & INSTALL_PLAN instead of groovy environment variable hack
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13824?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13824:
------------------------------------
I've tweaked both jobs mentioned above, so we should be good here.
> update install-grinder jobs to use short workspace & INSTALL_PLAN instead of groovy environment variable hack
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13824
> URL: https://issues.jboss.org/browse/JBIDE-13824
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, testing-tools
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.upgrade-tests.matrix/7/console}
> Started by user nboldt(a)REDHAT.COM
> [EnvInject] - Loading node environment variables.
> [EnvInject] - Preparing an environment for the build.
> [EnvInject] - Keeping Jenkins system variables.
> [EnvInject] - Keeping Jenkins build variables.
> [EnvInject] - Adding build parameters as variables.
> [EnvInject] - Evaluation the following Groovy script content:
> // Horrible hack to set PRODUCT !
> import hudson.model.*
> def thr = Thread.currentThread()
> def build = thr?.executable
> def resolver = build.buildVariableResolver
> def url = resolver.resolve("INSTALL_URL")
> String product = url.contains("devstudio") ? "devstudio" : "jbosstools"
> String proto = url.contains("devstudio.jboss.com") ? "https" : "http"
> [PRODUCT: product, PROTO: proto]
> [EnvInject] - [ERROR] - SEVERE ERROR occurs: No such property: executable for class: hudson.model.OneOffExecutor
> Notifying upstream projects of job completion
> Finished: FAILURE
> {code}
> Similar problem (which I worked around by removing the check on url and just hardcoding the values of product and proto):
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests.matrix/77/console}
> Started by user nboldt(a)REDHAT.COM
> [EnvInject] - Loading node environment variables.
> [EnvInject] - Preparing an environment for the build.
> [EnvInject] - Keeping Jenkins system variables.
> [EnvInject] - Keeping Jenkins build variables.
> [EnvInject] - Adding build parameters as variables.
> [EnvInject] - Evaluation the following Groovy script content:
> // Horrible hack to set PRODUCT !
> import hudson.model.*
> def thr = Thread.currentThread()
> def build = thr?.getCurrentExecutable()
> def resolver = build.buildVariableResolver
> def url = resolver.resolve("INSTALL_URL")
> String product = url.contains("devstudio") ? "devstudio" : "jbosstools"
> String proto = url.contains("devstudio.jboss.com") ? "https" : "http"
> [PRODUCT: product, PROTO: proto]
> [EnvInject] - [ERROR] - SEVERE ERROR occurs: Cannot invoke method contains() on null object
> Notifying upstream projects of job completion
> Finished: FAILURE{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years