Bug 1107987
| Summary: | Can't create new maven settings.xml during installation | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Denno <dennis.noordzij> |
| Component: | Installer | Assignee: | Thomas Hauser <thauser> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Len DiMaggio <ldimaggi> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | atangrin, dennis.noordzij, dlesage, felias, fnguyen, jstastny, vhalbert |
| Target Milestone: | ER2 | Keywords: | QA-Closed |
| Target Release: | 6.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Windows | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Users could not create a new Maven path during installation. This was due to the installer being unclear as it required the name of the file, not just the path to it. To solve this problem, the installer will now append a default 'settings.xml' filename onto the user provided value if the value given is a directory that exists.
|
Story Points: | --- |
| Clone Of: | 1053627 | Environment: |
DV6 CR2
|
| Last Closed: | 2016-02-10 08:53:14 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: | |||
|
Description
Denno
2014-06-11 08:48:04 UTC
Hello Denno, I believe that you need to enter the new file name also, so C:\Localdata\JBoss\maven\settings.xml should be created if you give it that path. This points to a problem with the explanatory text that we should fix. The installer will now append a default 'settings.xml' filename onto the user provided value if the value given is a directory that exists. There are a few possibilities now for a given value Suppose the user provides this location: /home/user/folder1/folder2 1) folder1 and folder2 exist and are directories: - settings.xml created at /home/user/folder1/folder2/settings.xml 2) folder1 doesn't exist: - settings.xml created at /home/user/folder1/folder2 (the filename folder2 is taken to be the desired name for the file.) 3) folder2 exists and is a file: - if the file is a valid maven settings.xml file: required changes are added - if not: the user is warned A link is also displayed to the user so they can view the schema. |