+ <profiles>\r
+ <profile>\r
+ <!-- Tomcat 7 profile, includes JSF 2.0 and Weld -->\r
+ <id>default</id>\r
+ <activation>\r
+ <activeByDefault>true</activeByDefault>\r
+ </activation>\r
+ <properties>\r
+ <env />\r
+ </properties>\r
+ <dependencies>\r
+ </dependencies>\r
+ <build>\r
+ <resources>\r
+ <resource>\r
+ <targetPath>META-INF</targetPath>\r
+ <directory>src/main/resources/tomcat</directory>\r
+ <includes>\r
+ <include>beans.xml</include>\r
+ </includes>\r
+ </resource>\r
+ </resources>\r
+ </build>\r
+ </profile>\r
+ <profile>\r
+ <!-- J2EE Application Server profile (Glassfish, JBoss) -->\r
+ <!-- beans.xml contains information of which configuration \r
+ scheme to inject. Optimally this would be decided at \r
+ the .war/application level, not at (this) jar/library\r
+ level, but for now this is necessary when using Glassfish\r
+ or JBoss -->\r
+ <id>as</id>\r
+ <properties>\r
+ <env>as</env>\r
+ </properties>\r
+ <dependencies>\r
+ </dependencies>\r
+ <build>\r
+ <resources>\r
+ <resource>\r
+ <targetPath>META-INF</targetPath>\r
+ <directory>src/main/resources/as</directory>\r
+ <includes>\r
+ <include>beans.xml</include>\r
+ </includes>\r
+ </resource>\r
+ </resources>\r
+ </build> \r
+ </profile>\r
+ </profiles>\r