[
http://jira.codehaus.org/browse/MSHADE-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135392#action_135392
]
Daniel Kulp commented on MSHADE-23:
-----------------------------------
Well, it's partially my fault. In one of the alphas, I moved the dependency
reduced pom into the target directory to make sure it got properly cleaned.
That's what caused this. However, I wanted the reduced pom left there so I
can see it.
The fix is going to be to do that, but then copy it into the basedir, set the
file to delete on exit, and set the project file to that file. Thus, the
reduced pom will still be left in target (for me), but the "runtime" will use
the version in basedir so the paths don't get screwed up. The delete on exit
will make sure the reduced pom is not left in the basedir to keep that
directory clean.
> ${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
