Good point, it's probably a bad idea to add a pom that contains any dependencies
or other information that would affect the build of a project using the
dependency. Although I think it would be safe to add information like project
url, description, and license if those are available since those wo
Possibly if we introduce a pom that has the exact internal model maven
generates when it can't find one. This could cause some issues for
people who have their own versions of those poms.
On Mon, May 3, 2010 at 2:05 PM, Paul Gier wrote:
> Jason van Zyl wrote:
>> On May 3, 2010, at 12:10 PM, Benja
Jason van Zyl wrote:
> On May 3, 2010, at 12:10 PM, Benjamin Bentmann wrote:
>
>> Hi,
>>
>> somehow related to my previous question about the checksums, what are our
>> chances to automatically detect and fix bad maven-metadata.xml's deployed to
>> Central like seen in [0]?
>>
>
> While the con
On May 3, 2010, at 12:10 PM, Benjamin Bentmann wrote:
> Hi,
>
> somehow related to my previous question about the checksums, what are our
> chances to automatically detect and fix bad maven-metadata.xml's deployed to
> Central like seen in [0]?
>
While the content of the POMs is not somethin
Hi,
somehow related to my previous question about the checksums, what are
our chances to automatically detect and fix bad maven-metadata.xml's
deployed to Central like seen in [0]?
Benjamin
[0] http://jira.codehaus.org/browse/MEV-658
---
