| Summary: | [patch] Adding a managed dependency adds a blank dependency instead | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | benson margulies <bimargulies> | ||||
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cbridgha, fbricon, igor, jmmunoz, shr31223, stephen.k.cooper | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
benson margulies
Reproducible always when artifact is managed. Expected behaviour: - Ok button should be disabled if dependency version is not managed - If I click on the top entry when managed, then it should insert the groupId and artifactId, and enable the ok button Created attachment 228890 [details]
Proposed patch
The issue reported here does not only affects addition of entries to the Dependency and Dependency Management lists since in both cases the Add button launches the MavenRepositorySearchDialog.
The patch do the next:
- Adds a method to validate the Group Id and Artifact Id fields
- Add two new error messages to report that the corresponding field has no value:
+ "Artifact Id cannot be empty"
+ "Group Id cannot be empty"
- Disables OK button until user enters a value in the fields or the fields are filled automatically when user selects an artifact from the list.
Hi, Any chance to have a review of this defect? Reviewed and applied the patch. Thank you. |