Off the top of my head, I could imagine 2 other approaches: 1. set up 2 separate project trees - one that produces the debug output, and another that depends on the source of the first (use dependency:unpack), and merely produces the non-debug output
2. if tooling exists to strip debug information, set up a second tree of projects, each one depending on the primary artifact and running the "strip debug" tool Best of luck keeping the versions in sync etc. Wayne On Thu, Mar 27, 2014 at 2:22 PM, Mark Eggers <its_toas...@yahoo.com> wrote: > Recently I received a requirement much like that covered in the following > thread: > > Releasing artifacts with and without debug info (December 04, 2013) > > I'm new to Maven, but I more or less followed the idea: > > 1. create a profile > 2. in the profile, specify the plugins > 3. in each plugin, specify multiple execution blocks > a. one block is configured to generate debug info > b. another block is configured to omit debug info > c. add classifiers to the JAR or WAR plugin as needed > 4. deploy plugin > a. add a configuration section > b. add a files section > c. list additional artifacts to be attached (?!) > > Is this the gist of Dimitar Gospodinov's reply at the end of the thread? > > It seems both hackish and verbose. > > However, I'm not sure of any other way to provide both fully optimized > (compressed CSS, Javascript) and non-optimized WAR and JAR artifacts. > > Any time I'm doing something like this, I feel that I'm not doing it the > "Maven way". > > Other approaches? > > /mde/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
