Bug 1014704 - Project dependencies: Version ID, Artifact ID
Summary: Project dependencies: Version ID, Artifact ID
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: DR2
: 6.1.0
Assignee: Toni Rikkola
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-02 14:52 UTC by Zuzana Krejčová
Modified: 2020-03-27 19:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:47:13 UTC
Type: Enhancement
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.