Bug 1014704

Summary: Project dependencies: Version ID, Artifact ID
Product: [Retired] JBoss BRMS Platform 6 Reporter: Zuzana Krejčová <zkrejcov>
Component: Business CentralAssignee: Toni Rikkola <trikkola>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: low Docs Contact:
Priority: low    
Version: 6.0.0CC: etirelli, lpetrovi, manstis
Target Milestone: DR2   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:47:13 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Zuzana Krejčová 2013-10-02 14:52:14 UTC 
Description of problem:
The dependencies table in the Project Screen has header with Group ID, Artifact ID (alright so far) and Version ID.

Maven artifacts have version, not version ID. Even if we do not think of these things as Maven related information, version ID still makes no sense.

It should read simply Version.

Similarly with Artifact ID - Maven uses the term artifact. 

And also, in the Deployments perspective, the header uses Group ID, Artifact and Version, indicating that the dependencies section of the Project Screen is a simple copy&paste mistake.

1. Please, keep things consistent and,
2. please, don't use 'Version ID'.
Comment 1 manstis 2014-06-11 10:19:23 UTC 
Maven Conventions are Group ID, Artifact ID and Version. See http://maven.apache.org/guides/mini/guide-naming-conventions.html