maven-profiles

Maven allows to activate certain build profiles based on the operating system family it runs on, for example: <profile> <activation> <os><family>Windows</family></os> </activation> </profile> There is a number of question around this: what are allowed values for os.family then? Are they case sensitive? Does Linux come across as Unix ? Or unix ? And so on. Where can I find information about allowed values – or, at least, where does Maven take these values from? Environment variables? The values are defined in the plexus-utils project, in Os.java . You can see in isOs that the match is case

I am in reference to " Maven: The Complete Reference " and especially the section regarding profiles which documents the use of a <properties... tag within the <profile... tag here: see here <profile> <id>development</id> <activation> <activeByDefault>true</activeByDefault> <property> <name>environment.type</name> <value>dev</value> </property> </activation> <properties> <database.driverClassName>com.mysql.jdbc.Driver</database.driverClassName> <database.url> jdbc:mysql://localhost:3306/app_dev </database.url> <database.user>development_user</database.user> <database.password>development

I am trying to run maven goal: validation and keep getting: [WARNING] The requested profile "pom.xml" could not be activated because it does not exist. In my org.eclipse.m2e.core.prefs: activeProfiles=pom.xml eclipse.preferences.version=1 resolveWorkspaceProjects=true version=1 What did I do wrong? Right click on your project Go to "Run as" Go to "Run configurations... " When the screen opens, please delete the word "pom.xml" from the "Profiles:" line and then click "Run". The project will now run. Your activeProfiles is set to pom.xml . But your Maven profile should be defined inside your pom

I have two profiles for different environments in pom.xml , I have to run mvn -PTest1 install and mvn -PTest2 install command to get these profiles in use. Can we integrate two separate maven commands in a single one (like mvn clean install )? Here is my Pom entry <profiles> <profile> <id>Test1</id> <activation> <activeByDefault>true</activeByDefault> <jdk>1.5</jdk> <os> <name>Windows XP</name> <family>Windows</family> <arch>x86</arch> <version>5.1.2600</version> </os> <property> <name>sparrow-type</name> <value>African</value> </property> </activation> <dependencies> <dependency> <groupId>

I have a Java webapp project that I develop in Eclipse (more precisely MyEclipse 10) and build using Maven 3. I have the following layout (including only the files relevant to my problem : project root |-- src | |-- main | | |-- java | | |-- resources | | | |-- log4j.xml | | | +-- struts.properties | | |-- webapp | | | |-- META-INF | | | | +--context.xml | | |-- config | | | |-- test | | | | |--log4j.xml | | | | |--struts.properties | | | | +--context.xml | | | +-- prod | | | | |--log4j.xml | | | | |--struts.properties | | | | +--context.xml | +--test +--pom.xml As you can see, I included a

I have the following profiles in my parent pom <profile> <id>P1</id> <activation> <activeByDefault>true</activeByDefault> </activation> </profile> <profile> <id>P2</id> <activation> <file> <exists>${project.basedir}/src/main/whatever</exists> </file> </activation> </profile> Why P1 is active in child POM and P2 isn't? The directory ${project.basedir}/src/main/whatever , does not exist in the parent project, but exists in the child one. linski Profile P2 is not activated because the path under its exists tag does not resolve to an existing path even though the directory ${project.basedir}/src

I wish to find out whether Never use <activeByDefault > is a maven best practice? The advice here around this seems pretty sound, but do you think it's absolute or if there are some cases in which it would not apply ? Am posting a snapshot of the content on that page for posterity: 来源： https://stackoverflow.com/questions/16167206/does-using-activebydefault-go-against-maven-best-practices