Archiva and Maven 2.0.9, refreshing defect POM/folder

[Michael Hüttermann <mi...@huettermann.net>]

Hello,

I use Maven 2.0.9 and Archiva 1.1.1.
In my environment the central proxy repository Archiva has a defect entry
for \internal\org\apache\maven\maven\2.0.9. After some manual and
suboptimal work there only dummy data garbage is existing in that folder. 
Actually after installing Archiva the folder was not existing at all.

OK, now I have issues with that defect entries for 2.0.9, and I removed
the whole folder \internal\org\apache\maven\maven\2.0.9 from disc. If I
trigger a "mvn install" or if I browse Archiva via web interface, I still
get and see the old and corrupt 2.0.9 version.

Now after deleting the folder I updated the database (admin:
database > update database now) and scanned my repository (admin:
repositories > scan repository now). That is obviously not enough.
Although the repository under
/archiva/repository/internal/org/apache/maven/maven does not contain the
2.0.9 folder any more, browsing Archiva still shows the corrupt folder:
/archiva/browse/org.apache.maven/maven/2.0.9 .. and even worse running
"mvn clean install" still accesses the defect 2.0.9 version.

So the question is, how can I fully and correctly refresh Archiva that it
will deliver the right 2.0.9 version for me? The correct version I see
under http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.9/ ?


Thank you for your time!!!

Best regards
Michael

Re: Archiva and Maven 2.0.9, refreshing defect POM/folder

[Marc Lustig <ml...@marclustig.com>]

Michael Hüttermann wrote:
> 
> I followed this how-to, but unfortunately the defect foldler is still
> there. :-| Pressing all those buttons does not provide a fantastic user
> experience I have to say. Archiva does not provide feedback what it did
> and if the scanning etc. was completed successfully.
> 
> 

try digging in the log-files, I think audit.log
-- 
View this message in context: http://www.nabble.com/Archiva-and-Maven-2.0.9%2C-refreshing-defect-POM-folder-tp21806694p21827197.html
Sent from the archiva-users mailing list archive at Nabble.com.

Re: Archiva and Maven 2.0.9, refreshing defect POM/folder

[Michael Hüttermann <mi...@huettermann.net>]

Hi Marc,

thanks for your explanation.

> from our experience I can tell you that removing corrupt artifacts from
> the
> managed repos is a common practise. Make sure to delete the entire folder
> (not just single files).

yes, I think so too .. it is a common task.

> It appears there a number of scenarios causing corrupt data either in the
> fs
> or in the Archiva db.
> If you have done this and run a repo scan, the artifact gets also removed
> from the Archiva db.
> Make sure you have enables the corresponding consumers under "Repository
> Scanning".

I followed this how-to, but unfortunately the defect foldler is still
there. :-| Pressing all those buttons does not provide a fantastic user
experience I have to say. Archiva does not provide feedback what it did
and if the scanning etc. was completed successfully.

What I did now is re-deploying the artifact/POM again manually. It works now.

Thanks.

Best regards
Michael

Re: Archiva and Maven 2.0.9, refreshing defect POM/folder

[Marc Lustig <ml...@marclustig.com>]

hi Michael,

from our experience I can tell you that removing corrupt artifacts from the
managed repos is a common practise. Make sure to delete the entire folder
(not just single files).
It appears there a number of scenarios causing corrupt data either in the fs
or in the Archiva db.
If you have done this and run a repo scan, the artifact gets also removed
from the Archiva db.
Make sure you have enables the corresponding consumers under "Repository
Scanning".
hth
M.



Michael Hüttermann wrote:
> 
> Hello,
> 
> I use Maven 2.0.9 and Archiva 1.1.1.
> In my environment the central proxy repository Archiva has a defect entry
> for \internal\org\apache\maven\maven\2.0.9. After some manual and
> suboptimal work there only dummy data garbage is existing in that folder. 
> Actually after installing Archiva the folder was not existing at all.
> 
> OK, now I have issues with that defect entries for 2.0.9, and I removed
> the whole folder \internal\org\apache\maven\maven\2.0.9 from disc. If I
> trigger a "mvn install" or if I browse Archiva via web interface, I still
> get and see the old and corrupt 2.0.9 version.
> 
> Now after deleting the folder I updated the database (admin:
> database > update database now) and scanned my repository (admin:
> repositories > scan repository now). That is obviously not enough.
> Although the repository under
> /archiva/repository/internal/org/apache/maven/maven does not contain the
> 2.0.9 folder any more, browsing Archiva still shows the corrupt folder:
> /archiva/browse/org.apache.maven/maven/2.0.9 .. and even worse running
> "mvn clean install" still accesses the defect 2.0.9 version.
> 
> So the question is, how can I fully and correctly refresh Archiva that it
> will deliver the right 2.0.9 version for me? The correct version I see
> under http://repo1.maven.org/maven2/org/apache/maven/maven/2.0.9/ ?
> 
> 
> Thank you for your time!!!
> 
> Best regards
> Michael
> 
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Archiva-and-Maven-2.0.9%2C-refreshing-defect-POM-folder-tp21806694p21812291.html
Sent from the archiva-users mailing list archive at Nabble.com.