Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 996880

Summary: Project screen: Source not working
Product: [Retired] JBoss BRMS Platform 6 Reporter: Zuzana Krejčová <zkrejcov>
Component: Business CentralAssignee: Toni Rikkola <trikkola>
Status: CLOSED CURRENTRELEASE QA Contact: Zuzana Krejčová <zkrejcov>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: lpetrovi
Target Milestone: ER4   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:19:27 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:
Bug Depends On:    
Bug Blocks: 983516    
Attachments:
Description Flags
no source none

Description Zuzana Krejčová 2013-08-14 08:39:31 UTC
Created attachment 786445 [details]
no source

Description of problem:
In the Project screen, you are offered the option to view the Project Setting source (pom.xml I expect) and the Knowledge Base Settings source (I'd expect kmodule.xml). Neither of the two are working. The screen shows the same thing as before.

In the screenshot, you can see I opened the GAV option and then tried switching to the source. No source showed up.


Version-Release number of selected component (if applicable):
kie-wb 6.0 CR1

Comment 1 Toni Rikkola 2013-09-05 12:55:50 UTC
The reason why Source was an option in the Project Editor is that we needed a way to be able to edit the source file. Now that I have thought about this. It feels risky to allow hard editing the file to everybody who can open the Project Editor.

So what I did was. I removed the Source options for both pom.xml and kmodule.xml. Now if you want to hard edit them, this can be done clicking the pom.xml or kmodule.xml file in admin perspective or using the technical view in the Project Explorer.

This also removes the duplicate editors we had for these two files and the confusion that they have caused. Since opening the pom.xml for example used to open a stripped down read only view of the Project Editor. We have had few people asking where the other editing options or the ability to save went.

Comment 5 Zuzana Krejčová 2013-10-21 09:15:55 UTC
Verified in ER4: the Source view is gone form the Project Screen, functionality available as per comment 1.