On Fri, Aug 3, 2012 at 3:28 PM, Barrie Treloar <[email protected]> wrote:
> On Fri, Aug 3, 2012 at 2:49 PM, Chris Graham <[email protected]> wrote: > > Why make it so hard? > > Why cann't you filter the resources and/or package them via the assembly > plugin. > > > > Remember that plugins still run during the release process, so why not > use them? > > Because these are not things you can filter. > They are Eclipse Manifest files, Feature files, etc and Eclipse needs > to be able to read them. > > I'm missing something here. The above statement means that Eclipse needs to be able to read them *whilst* maven is building the package. Isn't Tyco for build eclipse modules? So read the end result, yes, but *whilst* building??? > > I don't see why you need extensions here (but then, I've just come back > from my first loooooong lunch in ages!) > > Because I wanted to be able to click the "Perform Maven Release" in > Jenkins and have everything taken care of. > > Otherwise I need to run a couple of things on the command line, and > then manually tag and deploy. > I can't use the release plugin because the pom and Eclipse files need > to be kept in sync, and if I upgrade them to release versions outside > of the release plugin then the release fails because there are no > snapshots to transform. > > Admittedly this is a bunch of trivial steps I need to do to get this > to work, but I am trying to automate and dumb down the steps. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
