[m2] repository hell

[Xavier Toth <tx...@gmail.com>]

There seem to be a number of issues here are several:
a.) different poms with dependencies on the same jar but using different
groupId/artifactId (ex. jetty/jetty and jetty/org.mortbay.jetty) causing
multiple copies to be downloaded and stored

b.) poms using syntax like ${commons_beanutils_version} which isn't valid
(as far as I know)

I wish there was something I could do to help fix these problem maybe if
there were a way to know the maintainer of parts of the repository so they
could be contacted and told of specific issues?

Re: [m2] repository hell

[Wendy Smoak <ws...@gmail.com>]

On 11/1/05, Xavier Toth <tx...@gmail.com> wrote:
>
> I see this a problem also in that the users like myself aren't necessarily
> qualified to provide a fix for someone elses pom. I still think the
> contributor/maintainer needs to be known and notified since they would
> have
> the knowledge of how to resolve the issue.


Many of the projects with pom problems are not themselves using m2, so the
volunteers there may know even less than you do about how to fix the
problem. A polite inquiry on the developers list can't hurt, though. :)

It's important that everyone do what they can to help. Just opening a ticket
and posting what you think is the correct pom will go a long way-- if you
don't get it exactly right, others will comment on the ticket and eventually
the right solution will be arrived at.

For example, someone (Matt?) opened a ticket for the MyFaces pom with a
couple of changes. I didn't have time to write the complete fixed version,
but I posted a link to the MyFaces Wiki that lists all the dependencies.
Someone else came along and posted a more complete pom.

--
Wendy

Re: [m2] repository hell

[Xavier Toth <tx...@gmail.com>]

I see this a problem also in that the users like myself aren't necessarily
qualified to provide a fix for someone elses pom. I still think the
contributor/maintainer needs to be known and notified since they would have
the knowledge of how to resolve the issue.

On 11/1/05, John Casey <jd...@commonjava.org> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Basically, the best way to address this (at least so far) is to file a
> MEV issue with the fixes for that POM.
>
> http://jira.codehaus.org/browse/MEV
>
> It's going to take awhile to get the repository completely cleaned up,
> particularly since it's metadata demands are higher than with m1.
>
> HTH,
>
> john
>
> Xavier Toth wrote:
> | There seem to be a number of issues here are several:
> | a.) different poms with dependencies on the same jar but using different
> | groupId/artifactId (ex. jetty/jetty and jetty/org.mortbay.jetty) causing
> | multiple copies to be downloaded and stored
> |
> | b.) poms using syntax like ${commons_beanutils_version} which isn't
> valid
> | (as far as I know)
> |
> | I wish there was something I could do to help fix these problem maybe if
> | there were a way to know the maintainer of parts of the repository so
> they
> | could be contacted and told of specific issues?
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (GNU/Linux)
>
> iD8DBQFDZ5t+K3h2CZwO/4URArC2AJ4lwBQscs1ui7DdruF9nDfs6cif2wCgqNSO
> xj3ND0HhxLq9ijqUqR/vrkU=
> =jONB
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Re: [m2] repository hell

[John Casey <jd...@commonjava.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Basically, the best way to address this (at least so far) is to file a
MEV issue with the fixes for that POM.

http://jira.codehaus.org/browse/MEV

It's going to take awhile to get the repository completely cleaned up,
particularly since it's metadata demands are higher than with m1.

HTH,

john

Xavier Toth wrote:
| There seem to be a number of issues here are several:
| a.) different poms with dependencies on the same jar but using different
| groupId/artifactId (ex. jetty/jetty and jetty/org.mortbay.jetty) causing
| multiple copies to be downloaded and stored
|
| b.) poms using syntax like ${commons_beanutils_version} which isn't valid
| (as far as I know)
|
| I wish there was something I could do to help fix these problem maybe if
| there were a way to know the maintainer of parts of the repository so they
| could be contacted and told of specific issues?
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDZ5t+K3h2CZwO/4URArC2AJ4lwBQscs1ui7DdruF9nDfs6cif2wCgqNSO
xj3ND0HhxLq9ijqUqR/vrkU=
=jONB
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org