On Friday 14 March 2008, Jason Dillon wrote: > Any reason why after running shade that the project.basedir becomes > project.build.directory ? >
I wonder if this has something to do with the dependency reduced pom creation. The reduced pom is created in the target dir (so it gets cleaned properly). The ptr to the file for the pom in the reactor is replaced with a ptr to that pom so that it gets installed/deployed instead of the original. (and so it get's properly gpg signed) If project.basedir is lazily calculated based on the dir of the pom file, this may be the source of the issue. Could the shade set the "project.basedir" property sepcifically on the project and have it picked up instead of calculated? That might work. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
