jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 1
  • MAVEN-1393

Add the possibility to use parent pom present in repo

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Resolution: Duplicate
  • Affects Version/s: None
  • Fix Version/s: 1.0.1
  • Component/s: None
  • Labels:
    None

Description

For the extend tag, we can support http protocol, or another syntax like this <extend>${repo}/aGroupId/poms/anArtifactId-version.pom</extend>. Personally, I prefer the second solution.

With this features, users can share default pom parameter between all their projects, and it prepare the introduction of pom V4.

Issue Links

relates to

Improvement - An improvement or enhancement to an existing feature or task. MAVEN-1390 POM example <extends> doco is non-portable

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Trygve Laugstol added a comment - 23/Jul/04 9:18 AM

I don't think we should change the behaviour of maven that much. We could enforce the idea that John Casey came up with when uploading artifacts so that the <extend> element it changes to the form that was suggested.

Show
Trygve Laugstol added a comment - 23/Jul/04 9:18 AM I don't think we should change the behaviour of maven that much. We could enforce the idea that John Casey came up with when uploading artifacts so that the <extend> element it changes to the form that was suggested.
Hide
Permalink
Brett Porter added a comment - 23/Jul/04 10:47 AM

yep, John's JIRA issue has enough info.

Show
Brett Porter added a comment - 23/Jul/04 10:47 AM yep, John's JIRA issue has enough info.
Hide
Permalink
Manfred Mayer added a comment - 17/Nov/05 6:21 AM

I also think this would be a nice feature extension for Maven 1.1.
I created a patch for the current 1.1-beta3-SNAPSHOT, which parses the string in <extend>${maven.repo.local}/aGroupId/poms/anArtifactId-version.pom</extend>
and tries to download "aGroupId/poms/anArtifactId-version.pom" with the common artifact-download-mechanism from the specified remote repositories to the local repository. It works fine. It also supports the SNAPSHOT mechanism.
IMHO this change is not very invasive.

Show
Manfred Mayer added a comment - 17/Nov/05 6:21 AM I also think this would be a nice feature extension for Maven 1.1. I created a patch for the current 1.1-beta3-SNAPSHOT, which parses the string in <extend>${maven.repo.local}/aGroupId/poms/anArtifactId-version.pom</extend> and tries to download "aGroupId/poms/anArtifactId-version.pom" with the common artifact-download-mechanism from the specified remote repositories to the local repository. It works fine. It also supports the SNAPSHOT mechanism. IMHO this change is not very invasive.

People

  • Assignee:
    Unassigned
    Reporter:
    Emmanuel Venisse
Vote (0)
Watch (1)

Dates

  • Created:
    23/Jul/04 4:00 AM
    Updated:
    08/Mar/06 10:47 PM
    Resolved:
    23/Jul/04 10:47 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.