I was only referring to Jenkins as to look at how a war file could be used both as a "normal" war file being installed in a web container as well as a jar file (with a war extension) to be used as a standalone application. Look at it purely from a Java perspective and not how Maven might be abused to accomplish it. When you know what you want to end up with, then we can help you accomplish that with Maven.
/Anders On Tue, Sep 30, 2014 at 8:03 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Of course one of my long term goals is to teach KK how to use Maven... He > keeps going to maven expecting a fight... And lo he gets one. > > I keep trying to unwind his battles but every time I unwind one he's > started two more... > > In short, do not use the way Jenkins abuses maven as a way to learn how to > use maven... > > (Aside: KK's lack of full grök of maven explains *why* the jenkins maven > (aka evil) job type is so evil) > > On Tuesday, 30 September 2014, Les Hartzman <lhartz...@gmail.com> wrote: > > > Thanks Anders. I'll take a look at Jenkins. Sounds like an interesting > > learning experience. > > > > Les > > > > On Tue, Sep 30, 2014 at 2:33 AM, Anders Hammar <and...@hammar.net > > <javascript:;>> wrote: > > > > > It is possible. > > > One way is to use a generic packaging plugin like the > > > maven-assembly-plugin. If that doesn't fit your desires, or you want a > > > "nicer solution", writting your own plugin is a different way. For > > example, > > > have a look at the Android Maven Plugin which creates android archives. > > > > > > That being said, the web app you're talking about should be a standard > > war > > > projekt (which uses the maven-war-plugin to produce the war archive). > The > > > desktop app could possibly be a standard jar project. So I don't think > > you > > > need any special packaging plugins, but your question is rather how to > > > handle these two flavors of your application. Something that you should > > try > > > to solve, as it will significantly simplify things, is to have only one > > > package/archive. Have a look at how, for example, the Jenkins projekt > has > > > solved this. They produce a war file that is possible to deploy to a > web > > > container (web app) as well as start from command line (application). > > When > > > looking at that topic you're in pure Java land and shouldn't worry > about > > > Maven. > > > If you need different config files it could be tricky to solve this way > > > though. > > > > > > /Anders > > > > > > On Mon, Sep 29, 2014 at 7:17 PM, Les Hartzman <lhartz...@gmail.com > > <javascript:;>> wrote: > > > > > > > Hi, > > > > > > > > I'm a fairly basic maven user and would like to know if it is > possible > > to > > > > have maven support multiple type of packaging or if I need to look > at a > > > > different mechanism. > > > > > > > > What I want to do is to build a JavaFX application that depending on > > how > > > it > > > > is packaged is either a desktop app or a web app. > > > > > > > > There would potentially be some different configuration files that > > would > > > > pertain to the different packaging options. > > > > > > > > Can I use maven in this way or does someone know of another means of > > > > accomplishing the same thing? > > > > > > > > Thanks. > > > > > > > > Les > > > > > > > > > > > > -- > Sent from my phone >
