[JBoss JIRA] (JBIDE-23872) Tools clear war deployed files
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23872?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23872:
-------------------------------
Fix Version/s: 4.5.0.AM1
> Tools clear war deployed files
> ------------------------------
>
> Key: JBIDE-23872
> URL: https://issues.jboss.org/browse/JBIDE-23872
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.2.Final
> Environment: Windows 7 64
> JDK 8
> Eclipse Neon 1
> JBoss Tools 4.4
> WildFly 10.1
> Reporter: Claudio Weiler
> Priority: Minor
> Fix For: 4.5.0.AM1
>
>
> After an Eclipse start war deployed files are deleted and not republished.
> I have created a system lock to one of the html resources to try to dig more infos, but the exception shown refers to another resource:
> "Error renaming D:\Aplic\wildfly-10.1.0\standalone\tmp\tmp7250132485298982117.MF to D:\Aplic\wildfly-10.1.0\standalone\deployments\testing-ear.ear\META-INF\MANIFEST.MF."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBTIS-1032) Drools - Fix failing smoke tests
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1032?page=com.atlassian.jira.plugin... ]
Tomas David commented on JBTIS-1032:
------------------------------------
I reproduced this issue but I am not able to find a cause of the problem.
The issue appears only when you run test via command line with bundle eclipse.
I found out that there is weird version of drools eclipse plugin (7.0.0.201701021409) although there should be (6.5.0.CR1).
Are there any related changes in plugin installation?
> Drools - Fix failing smoke tests
> --------------------------------
>
> Key: JBTIS-1032
> URL: https://issues.jboss.org/browse/JBTIS-1032
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: drools/ jBPM, QE
> Affects Versions: 4.4.0.Final
> Reporter: Andrej Podhradsky
> Assignee: Tomas David
> Attachments: archive.zip
>
>
> Please see the attached zip file which contains all reports and screenshots
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4263) Problems after install from Red Hat Central into rh-eclipse46-devstudio
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4263:
------------------------------------
Problem with JBoss Data Virtualization Developement (Teiid) moved to subtask (JBDS-4273).
> Problems after install from Red Hat Central into rh-eclipse46-devstudio
> -----------------------------------------------------------------------
>
> Key: JBDS-4263
> URL: https://issues.jboss.org/browse/JBDS-4263
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.3.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 10.3.0.GA
>
> Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> The installation of software from Red Hat Central causes errors in the log. Some functionality may be broken. We have to test installation of all the stuff from the central and fix the problems.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4175.
------------------------------
Closing, with future work in JBDS-4263.
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.3.0.AM2
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, devstudio-is-major-feature-groups-to-test.png, install-all-the-categorized-features.png, install-integration-stack-441cr1.png, install-springide383-correctly.png, install-springide383-create-mvc-project-done.png, install-springide383-create-mvc-project.png, integration-stack-install-everything-some-deps-are-old-neon.1-versions.png, integration-stack-install-everything-some-deps-are-old-neon.1-versions_option2.png, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, slf4j-error.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, springide382.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4263) Problems after install from Red Hat Central into rh-eclipse46-devstudio
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4263:
-------------------------------
Description: The installation of software from Red Hat Central causes errors in the log. Some functionality may be broken. We have to test installation of all the stuff from the central and fix the problems. (was: [~lvalach] said: {quote}
Hi Nick,
I tested installation of stuff from central as you described. I am not finished yet, but here is what I found.
-install latest integration stack bits from IS
-JBoss Fule Development - OK
-JBoss Business P. and Rules D. - OK
-JBoss Integration and SOA D. - OK
-JBoss Data Virtualization D. (IS early acess)
-there is problem with slf4j
-IS contains Teiid 11.0.1.CR1-v20170117-222 which should be fixed
-there are error like this:
{code}
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences".
!STACK 0
java.lang.LinkageError: loader constraint violation: when resolving method
"org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader
(instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class,
org/slf4j/LoggerFactory, and the class loader
(instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class,
org/slf4j/impl/StaticLoggerBinder, have different
Class objects for the type org/slf4j/ILoggerFactory
used in the signature{code}
-install everything from Central (including PMD and Findbugs, and early access stuff. NOTE: newer versions of the Integration Stack connectors should already be installed from the step above)
-I installed everything using Central-Software/update, *no remediation action* was needed.
-Eclipse started but with many errors. So I have to find out which feature causes the problem.{quote}
[~nickboldt] said:
{quote}
loader constraint violation == two different versions of slf4j in the installed plugins
check in :~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 vs. in /opt/rh/
Problem appears to be in *org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory*. {quote}
[~lvalach] said:
{quote}
{code}
cd ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
find . -iname *slf4j*
./configuration/org.eclipse.osgi/1293/0/.cp/lib/slf4j-api-1.6.1.jar
{code}
The output for /opt/rh/ is quite long but I can say that it contains slf4j.api_1.7.4.jar
{quote}
So, we may have a conflict between slf4j and slf4j-api, which both use the same bundle names, but expose packages differently.
Unclear which IS project is causing this problem as I thought we'd fixed both SY and TD already.
* https://issues.jboss.org/browse/SWITCHYARD-2976
* https://issues.jboss.org/browse/TEIIDDES-2999)
> Problems after install from Red Hat Central into rh-eclipse46-devstudio
> -----------------------------------------------------------------------
>
> Key: JBDS-4263
> URL: https://issues.jboss.org/browse/JBDS-4263
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.3.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 10.3.0.GA
>
> Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> The installation of software from Red Hat Central causes errors in the log. Some functionality may be broken. We have to test installation of all the stuff from the central and fix the problems.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4263) Problems after install from Red Hat Central into rh-eclipse46-devstudio
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4263:
-------------------------------
Summary: Problems after install from Red Hat Central into rh-eclipse46-devstudio (was: possible use constraint violation from slf4j / slf4j-api)
> Problems after install from Red Hat Central into rh-eclipse46-devstudio
> -----------------------------------------------------------------------
>
> Key: JBDS-4263
> URL: https://issues.jboss.org/browse/JBDS-4263
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.3.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 10.3.0.GA
>
> Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> [~lvalach] said: {quote}
> Hi Nick,
> I tested installation of stuff from central as you described. I am not finished yet, but here is what I found.
> -install latest integration stack bits from IS
> -JBoss Fule Development - OK
> -JBoss Business P. and Rules D. - OK
> -JBoss Integration and SOA D. - OK
> -JBoss Data Virtualization D. (IS early acess)
> -there is problem with slf4j
> -IS contains Teiid 11.0.1.CR1-v20170117-222 which should be fixed
> -there are error like this:
> {code}
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: when resolving method
> "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader
> (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class,
> org/slf4j/LoggerFactory, and the class loader
> (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class,
> org/slf4j/impl/StaticLoggerBinder, have different
> Class objects for the type org/slf4j/ILoggerFactory
> used in the signature{code}
> -install everything from Central (including PMD and Findbugs, and early access stuff. NOTE: newer versions of the Integration Stack connectors should already be installed from the step above)
> -I installed everything using Central-Software/update, *no remediation action* was needed.
> -Eclipse started but with many errors. So I have to find out which feature causes the problem.{quote}
> [~nickboldt] said:
> {quote}
> loader constraint violation == two different versions of slf4j in the installed plugins
> check in :~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 vs. in /opt/rh/
> Problem appears to be in *org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory*. {quote}
> [~lvalach] said:
> {quote}
> {code}
> cd ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
> find . -iname *slf4j*
> ./configuration/org.eclipse.osgi/1293/0/.cp/lib/slf4j-api-1.6.1.jar
> {code}
> The output for /opt/rh/ is quite long but I can say that it contains slf4j.api_1.7.4.jar
> {quote}
> So, we may have a conflict between slf4j and slf4j-api, which both use the same bundle names, but expose packages differently.
> Unclear which IS project is causing this problem as I thought we'd fixed both SY and TD already.
> * https://issues.jboss.org/browse/SWITCHYARD-2976
> * https://issues.jboss.org/browse/TEIIDDES-2999
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-4273) Problem installing Teidd form IS discovery site - possible use constraint violation from slf4j / slf4j-api
by Lukáš Valach (JIRA)
Lukáš Valach created JBDS-4273:
----------------------------------
Summary: Problem installing Teidd form IS discovery site - possible use constraint violation from slf4j / slf4j-api
Key: JBDS-4273
URL: https://issues.jboss.org/browse/JBDS-4273
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Sub-task
Components: build, rpm
Affects Versions: 10.3.0.GA
Environment: RHEL7, RHSCL 2.4 Alpha 1.1, rh-eclipse46-devstudio.x86_64 10.3-0.20170206.0203.el7
Integration Stack Discovery site: http://download.jboss.org/jbosstools/neon/integration/updates/integration...
Reporter: Lukáš Valach
Assignee: Lukáš Valach
Fix For: 10.3.0.GA
Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
[~lvalach] said: {quote}
Hi Nick,
I tested installation of stuff from central as you described. I am not finished yet, but here is what I found.
-install latest integration stack bits from IS
-JBoss Fule Development - OK
-JBoss Business P. and Rules D. - OK
-JBoss Integration and SOA D. - OK
-JBoss Data Virtualization D. (IS early acess)
-there is problem with slf4j
-IS contains Teiid 11.0.1.CR1-v20170117-222 which should be fixed
-there are error like this:
{code}
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences".
!STACK 0
java.lang.LinkageError: loader constraint violation: when resolving method
"org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader
(instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class,
org/slf4j/LoggerFactory, and the class loader
(instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class,
org/slf4j/impl/StaticLoggerBinder, have different
Class objects for the type org/slf4j/ILoggerFactory
used in the signature{code}
-install everything from Central (including PMD and Findbugs, and early access stuff. NOTE: newer versions of the Integration Stack connectors should already be installed from the step above)
-I installed everything using Central-Software/update, *no remediation action* was needed.
-Eclipse started but with many errors. So I have to find out which feature causes the problem.{quote}
[~nickboldt] said:
{quote}
loader constraint violation == two different versions of slf4j in the installed plugins
check in :~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 vs. in /opt/rh/
Problem appears to be in *org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory*. {quote}
[~lvalach] said:
{quote}
{code}
cd ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64
find . -iname *slf4j*
./configuration/org.eclipse.osgi/1293/0/.cp/lib/slf4j-api-1.6.1.jar
{code}
The output for /opt/rh/ is quite long but I can say that it contains slf4j.api_1.7.4.jar
{quote}
[~nickboldt] said:
{quote}
So, we may have a conflict between slf4j and slf4j-api, which both use the same bundle names, but expose packages differently.
Unclear which IS project is causing this problem as I thought we'd fixed both SY and TD already.
* https://issues.jboss.org/browse/SWITCHYARD-2976
* https://issues.jboss.org/browse/TEIIDDES-2999
{quote}
[~lvalach] said:
{quote}
I tried to install Jboss Data Virtualization Developement from [IS discovery site|http://download.jboss.org/jbosstools/neon/integration/updates/integr...] again.
Whole log:
[^rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt]
Slf4j files in ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/
[^home_eclipse.txt]
Slf4j files in /opt/rh/
[^opt_rh.txt]
The problem is caused by Teiid Designer and Teiid Designer Runtime.
Teiid DataTools Connectivity and Teiid Runtime Clients don't cause problem.
IS repository contains SwitchYard 2.3.0.CR1-v20170120-1347-B20 which works properly.
{quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23862) Server adapter: if "oc" in preferences is set to path with a " " syncing fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23862?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23862:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have "oc" available at a path that contains a " " (ex. /Users/adietish/Download/oc binaries/oc)
# ASSERT: have an OpenShift server adapter
# EXEC: start the adapter
Result:
Publishing fails, reporting that the "oc" binary could not be found
was:
# ASSERT: make sure that you have "oc" available at a path that contains a " " (ex. /Users/adietish/Download/oc binaries/oc)
# ASSERT: have an OpenShift server adapter
# EXEC: start the adapter
Result:
Publishing fails, reporting that the "oc" binary could not be found
> Server adapter: if "oc" in preferences is set to path with a " " syncing fails
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23862
> URL: https://issues.jboss.org/browse/JBIDE-23862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.4.3.Final
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23881) Properties: Builds are missing the cathegories and properties that exist in all other tab items
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23881:
------------------------------------------
I found a simple change that fixes this and included it into the PR for JBIDE-23841
> Properties: Builds are missing the cathegories and properties that exist in all other tab items
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23881
> URL: https://issues.jboss.org/browse/JBIDE-23881
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Andre Dietisheim
> Labels: openshift_v3, properties
> Fix For: 4.4.4.AM1
>
> Attachments: build-config-properties.png, build-properites.png
>
>
> The "Builds" tab contains a list of builds that exist on the server. Selecting them unveil the properties of the selected build.
> The same is valid for all other tabs like "Build Configs" , "Deployments", etc. But these other items all have cathegories like "Annotations", "Basic", "Labels", etc.
> !build-config-properties.png!
> "Builds" dont have these:
> !build-properites.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month