Carlos Sanchez wrote:

>Hi,
>
>I'd like to know what should be done with missing and wrong poms in
>the Maven 2 repo. For instance I'm trying to build a project and many
>poms are missing and some others are incorrect (referenced with a
>wrong name). 
>
Missing POMs should only exist if the Maven 1.x POM could not be parsed.
Report it in JIRA under MEV. The source needs to be fixed - not just the
copy in repository-staging.

>Also poms for non redistributable apps should be added to
>establish name convention.
>  
>
Definitely - and make sure they are on the docs page for m1
(http://maven.apache.org/reference/standard-sun-jar-names.html).

>Seems that the best solution could be add the maven 1 pom when
>possible and in other cases, like specifying scope of the jars, the
>maven 2 repo poms should be changed in
>/home/projects/maven/repository-staging/to-ibiblio/maven2.
>  
>
You can specify the scope in an m1 pom using
<properties><scope>...</scope></properties>. The repoconverter will
honour it (though m1 will not, obviously).

>BTW it'd be nice if when a pom or jar can't be downloaded I could see
>from where it's referenced.
>  
>
Yes it would be nice :)

Cheers,
Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to