Maven Shared Components

DefaultMavenFileFilter.getDefaultFilterWrappers loads filters from the current directory instead of using basedir

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: maven-filtering-1.0-beta-3, maven-filtering-1.0-beta-4
  • Fix Version/s: None
  • Component/s: maven-filtering
  • Labels:
    None
  • Number of attachments :
    0

Description

If a POM is a sub module and has filtered configured other than with the build section (through the configuration part of the WAR plugin for example), then the call to this method will fail if Maven is run from the parent POM because the filters are loaded without any regard to absolute/relative paths and projet basedir.
Please note that the Maven project is available to these methods but not used for this purpose.

Issue Links

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. MWAR-157 webResources paths NOT resolved relative to pom.xml but relative to 'current directory'

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dennis Lundberg added a comment -

Can you supply a sample project that shows the problem?

Show
Dennis Lundberg added a comment - Can you supply a sample project that shows the problem?
Hide
Permalink
Dennis Lundberg added a comment -

Ah sorry, found one in the linked issue in MWAR.

Show
Dennis Lundberg added a comment - Ah sorry, found one in the linked issue in MWAR.

People

  • Assignee:
    Unassigned
    Reporter:
    Jeff MAURY
Vote (0)
Watch (1)

Dates

  • Created:
    Updated: