[
http://jira.codehaus.org/browse/MSHADE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135394#action_135394
]
Benjamin Bentmann commented on MSHADE-23:
-----------------------------------------
A possible short-term solution might be to have the Shade Plugin write the
modified POM always next to the original POM instead of {{target}}. This way,
the base directory would at least stay the same.
bq. I guess the sad truth is that the shade plugin is playing with undocumented
features
If you have a look at
[{{MavenProject}}|http://maven.apache.org/ref/current/maven-project/apidocs/org/apache/maven/project/MavenProject.html],
it's fair to say that quite every non-trivial plugin is using undocumented
features... That somehow frightens me and I hope the day will arive when the
core guys realize that a complex beast like Maven needs a thorough API as its
foundation.
> ${basedir} is wrong after running shade plugin
> ----------------------------------------------
>
> Key: MSHADE-23
> URL: http://jira.codehaus.org/browse/MSHADE-23
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Environment: Maven version: 2.0.8
> Java version: 1.5.0_06
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Andreas Schouten
> Assignee: Daniel Kulp
>
> After the shade plugin has run, the ${basedir} points to target.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
