Hi Folks, I was just looking throught the DefaultRepositoryBrowsing class trying to identify the path from the UI to the project model information. But I actually got confused on why Archiva first searches the pom file associated with the file and use the version in it to get the final project model. Do you guys have any idea on why Archiva does that? Why couldn't it just look for the project model information using the already known group id, artifact id and version?
Kind regards, Felipe Roos http://www.linkedin.com/in/feliperoos Achar desculpas para os nossos defeitos não nos torna melhores Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com
