Maven 2.x One Plugin

Goal one:convert ignores extend tag in project.xml

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.2
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    Maven version: 2.0.9
    Java version: 1.6.0_05
    OS name: "mac os x" version: "10.5.2" arch: "x86_64" Family: "mac"
  • Number of attachments :
    0

Description

I tried to convert a Maven 1 project.xml (v3 pom) to a Maven 2 pom.xml (v4 pom). In project.xml, I use <extend> to inherit some values from a "project_base.xml" file. The goal one:convert seems to ignore the base file, so no configuration values from that base file are present in the generated pom.xml file.

Activity

Hide
Dennis Lundberg added a comment -

To me this is the desired behavior. Each project.xml is converted separately into a pom.xml file. That way you can maintain the separation of configuration found in your existing inheritance structure.

Show
Dennis Lundberg added a comment - To me this is the desired behavior. Each project.xml is converted separately into a pom.xml file. That way you can maintain the separation of configuration found in your existing inheritance structure.
Hide
Martin Burger added a comment -

So, some "merge" option / switch would be useful. Then you could select your preferred behavior.

Show
Martin Burger added a comment - So, some "merge" option / switch would be useful. Then you could select your preferred behavior.
Hide
Dennis Lundberg added a comment -

Right, if you wanted to move away from the inheritance all together it would be a nice feature.

Changing from "bug" to "improvement".

Show
Dennis Lundberg added a comment - Right, if you wanted to move away from the inheritance all together it would be a nice feature. Changing from "bug" to "improvement".

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated: