You need to use profiles here is a pom. Xml example.
You need to use profiles, here is a pom. Xml example: 4.0.0 com. Mycompany FooBar 1.0 jar Foo maven-assembly-plugin foo/id> package single Bar maven-assembly-plugin Bar package single And you would invoke maven like this: mvn package -P Foo // Only Foo mvn package -P Bar // Only Bar mvn package -P Foo,Bar // All (Foo and Bar).
My Maven is a bit rusty but I think you can do this a couple of ways: 1) Use profiles. Specify a profile on the command line with "maven -PprofileName". 2) Put your executions in separate phases/goals and run only the ones you want.
If you don't want "bar" to run, then don't bind it to a lifecycle phase. Plugin executions only run when they are bound to a phase and that phase executes as part of a build. As TheCoolah suggested, profiles are one way of managing when executions are bound to lifecycle phases and when not.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.