Ate Douma wrote: > Carsten Ziegeler wrote: >> Ate Douma wrote >>> Yes, I think I can get it to work with a custom assembly. >>> I'm on route to office right now and will be there shortly. >>> If you can give me an hour or so, I can try it out and commit a >>> solution. > Done! > > It took a little more time and some dirty "hacking" than I expected > because the assembly-plugin always merges multiple descriptor > configurations. So, adding just our custom assembly still also produced > the -project archives as you already found out. > > I "fixed" this by configuring a *non-existing* predefined assembly > instead which *does* override the "project" configuration. > To make this build however we also need to configure > ignoreMissingDescriptor=true. > All this really is a dirty hack of course. Great :) I just tested it on my machine and it works here (of course) as well. Many thanks Ate!
> We will have to update the portals-pom to either not configure any > predefined assembly and/or wait for the next assembly-plugin release > which hopefully will fix these deficiencies. Yepp, one or the other. You could remove it from our parent pom and do a new release so you're not affected for the Jetspeed release. > Anyway, I ran mvn release:prepare -DdryRun and all went fine, so AFAIK > Pluto now finally is ready for release. > > GO :) Yuppie!! :) Thanks again, Ate! I'll not try my luck with Nexus... Regards Carsten -- Carsten Ziegeler [email protected]
