You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@maven.apache.org by bo...@werken.com on 2003/02/08 00:56:45 UTC

[maven-bug] New comment: (MAVEN-258) Decouple Project reading from the File object

The following comment has been added to this issue:

     Author: Ben Walding
    Created: Fri, 7 Feb 2003 5:56 PM
       Body:
Deserialisation only fails if it uses <extends>

eg. 95% of commons!
---------------------------------------------------------------------
View the issue:

  http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-258


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-258
    Summary: Decouple Project reading from the File object
       Type: Improvement

     Status: Assigned
   Priority: Trivial

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: maven
  Component: core

   Assignee: Jason van Zyl
   Reporter: Ben Walding

    Created: Fri, 7 Feb 2003 5:54 PM
    Updated: Fri, 7 Feb 2003 5:54 PM

Description:
At the moment MavenUtils has a couple getProject(File, *) methods.

Unfortunately, things like Overlord / anything that is downloading the POM via a URL don't have File references to work with. And as such, deserializing the POM fails.

I propose we either
1) Start using URLs
2) Add a resolver to resolve lookups.

I prefer 2 as it means that I can download a project, save it to disk, have the getProject(File) work, and if it needs a parent POM, the resolver is called.  At which point I can download that POM and return a ref to it.

Some classes that I use are visible at
http://projects.walding.com:8000/viewcvs/DataForge/dataforge-engine/src/java/com/walding/dataforge/resolvers/

I will relicense these (and any deps) under ASL if they are used in Maven in any form.

(That whole library will be come ASL compatible shortly in any event).



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.werken.com/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira