Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.0-beta-2
-
Fix Version/s: 1.1
-
Component/s: None
-
Labels:None
-
Environment:Windows XP SP2 and Solaris - Default install run via plexus. JDK1.6.0_03.
-
Number of attachments :
Description
1. Take an existing POM in the repository and modify its contents (I changed the description).
2. In administration console select Repositories.
3. Click "Scan Repository Now" for test repository where POM was changed.
4. Database > Update Database Now.
5. Browse to POM location.
The index information has not been updated, the changes are not reflected in the browse > info section for the POM. Step 1 can be replaced with the modification of the POM outside of the repository, followed by the redeployment of the POM ad associated jar to the repository.
Issue Links
| This issue relates to: | ||||
| MRM-622 | database not being updated with project model information |
|
|
|
I view this as a low priority - we generally avoid allowing updates to poms in the repository as Maven doesn't expect it. I hope this is an infrequent thing, and that the workaround of rebuilding the database is ok