This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | "Misconfigured maven project" when property exists in system-scoped dependency's systemPath | ||
---|---|---|---|
Product: | projects | Reporter: | karbonized |
Component: | Maven | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | juhrik, malary, theanuradha |
Priority: | P2 | ||
Version: | 7.0 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
karbonized
2010-10-20 13:31:42 UTC
Probably related to bug #154507, though that deals with environment variables. (In reply to comment #0) > the project can be built successfully (and obviously maven is happy with this) Don't be too sure. At least in the case of Maven plugins, you cannot run a plugin whose POM included a system-scope dependency of relative path, even when the plugin could be built from source just fine: other Maven processes (perhaps on someone else's machine) will read the *.pom from the local repo, see an unevaluated property or invalid relative path, and choke. Not sure if this problem applies to other usages of a built artifact. I would recommend trying ${java.home}/../lib/tools.jar (perhaps controlled by a profile) rather than relying on a path in settings.xml, at least until there is some resolution to <http://jira.codehaus.org/browse/MNG-1867>. Reproducible, but so far I have no clue where this is supposed to be fixed. MavenEmbedder does call MavenExecutionRequest.setUserSettingsFile with the expected value. *** Bug 154507 has been marked as a duplicate of this bug. *** core-main #ee31298e328a *** Bug 191309 has been marked as a duplicate of this bug. *** |