Bug 1076259

Summary: Cannot manage WildFly 8.0 through eclipse
Product: [Fedora] Fedora Reporter: Filipe Rosset <rosset.filipe>
Component: eclipse-webtoolsAssignee: Gerard Ryan <fedora>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: akurtako, andjrobins, fedora, jerboaa, krzysztof.daniel, mgoldman, msimacek, overholt, rgrunber, swagiaal, vladimir.kostadinov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 03:10:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Installed eclipse packages
none
error1
none
wildfly_errors none

Description Filipe Rosset 2014-03-13 23:49:51 UTC
Created attachment 874175 [details]
Installed eclipse packages

Description of problem:
I want to manage a WildFly 8.0 final through eclipse, but no luck.

Version-Release number of selected component (if applicable):
Versions were upload in eclipse_version.txt

How reproducible:
Always.

Steps to Reproduce:
0. Install packages listed in eclipse_version.txt
1. Download WildFly 8.0 .tar.gz and extract in any folder
2. Configure a new server connection (please see error1, error2 and error3 file)
3. 

Actual results:
Error

Expected results:
Start wildfly

Comment 1 Filipe Rosset 2014-03-13 23:51:04 UTC
Created attachment 874176 [details]
error1

Comment 2 Filipe Rosset 2014-03-13 23:52:24 UTC
Created attachment 874177 [details]
wildfly_errors

Comment 3 Filipe Rosset 2014-03-13 23:54:04 UTC
Error screenshots are uploaded here: https://bugzilla.redhat.com/attachment.cgi?id=874177

Comment 4 Filipe Rosset 2014-03-27 03:21:41 UTC
Hi guys, you'd a chance to look into this issue? In this case I was trying to manage a standalone wildfly installation (from .tar.gz file), but I believe it's also reproducible with a system-side widfly installation (by RPM repos).

Comment 5 Marek Goldmann 2014-03-27 09:26:24 UTC
Version installed in the RPM form is not meant to be managed by Eclipse at all. This server is for running applications and not for the development purposes per se.

If you want to use this version, please take a look at the wildfly-cp.sh located in the /user/share/wildfly/bin folder. This script copies only required part of WildFly to make it bootable from a different directory so you can manage and deploy apps as a regular user (or maintain it in Eclipse, in your case).

If this will not work for you - this is a bug and should be reported in new ticket.

Comment 6 Fedora Admin XMLRPC Client 2014-07-09 19:46:33 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Fedora End Of Life 2015-11-04 15:16:53 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2015-12-02 03:10:17 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.