Define artifacts resulting from an application build

[hugithordarson]

To make the plugin play nice with other plugins, having it define a primary artifact might be a capital idea

[paulhoadley]

This one is interesting. For reference, wolifecycle will produce:

Juno.woapplication.tar.gz
Juno.wowebserverresources.tar.gz

and both of those get shipped to your Maven repo on deploy. We're going to need to replicate something similar, aren't we—with or without the WSR part, though you've just shipped the performSplit option! (It might be a conversation for another ticket, but is "split install" a deployment anachronism? I mean, we currently use it, but as discussed elsewhere, there's no real need to when you're running appserver and webserver on the same box. I suppose the residual use case is where you're not.)

In any case, we need some way to ship the WOA bundle, don't we?

[hugithordarson]

Yeah, this one probably needs solving, for exactly the reasons you mention. In fact I think the whole artifact thing needs a little cleanup. I've always used rsync to deploy the woa folder so I hadn't really hit this.