This repository has been archived by the owner on Oct 16, 2020. It is now read-only.
Blinky: Maven Profiles: Selectively run Statik and Diagnostics #36
Assignees
Comments
VijayKrishna
added a commit
that referenced
this issue
Nov 13, 2016
Ref. Issue #36 Summary: - Keeping the following modules as the default: core, util, trace-manager, tacoco; let's call it the default set * This default set can be run using the regular command: `mvn compile test package install` - Introducing **three** additional profiles in blinky's POM.xml (i.e. the parent project pom) for the following: * statik -- this adds statik to the default set. * diagnostics -- this adds diagnostics to the default set. * full -- this adds statik and diagnostics to the default set. - Following are the changes to the maven commands to invoke any of the three profiles: * statik: `mvn -P statik compile test package install` * diagnostics: `mvn -P diagnostics compile test package install` * full: `mvn -P full compile test package install`
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
core,util,trace-manager,tacoco; let's call it the default setPOM.xml(i.e. the parent project pom) for the following:statikanddiagnosticsto the default set.Following are the changes to the maven commands to invoke any of the three profiles:
mvn -P statik compile test package installmvn -P diagnostics compile test package installmvn -P full compile test package installThe text was updated successfully, but these errors were encountered: