Skip to content

Commit

Permalink
Make comments actionable
Browse files Browse the repository at this point in the history
  • Loading branch information
pmuir committed Nov 22, 2011
1 parent 0dd5327 commit 60a94f1
Show file tree
Hide file tree
Showing 2 changed files with 19 additions and 12 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -21,26 +21,28 @@
<!-- You can reference property in pom.xml or filtered resources (must
enable third-party plugin if using Maven < 2.1) -->
<maven.build.timestamp.format>yyyyMMdd'T'HHmmss</maven.build.timestamp.format>
<!-- Specify the JBoss AS directory to be the JBOSS_HOME environment
variable -->
<jboss.home>${env.JBOSS_HOME}</jboss.home>
<!-- Define the version of JBoss' Java EE 6 APIs we want to import.
Any dependencies from org.jboss.spec will have their version defined by this
BOM -->
#if ($enterprise == "true" || $enterprise == "y" || $enterprise == "yes" )
<!-- Certified version of the JBoss EAP components we want to use -->
<javaee6.web.spec.version>3.0.0.Beta1-redhat-1</javaee6.web.spec.version>
<!-- Alternatively, you can use version 2.0.0.Beta1 which is based on community built dependencies.
You can actually use this stack with any version of JBoss AS that implements the Java EE 6 web profile
<!-- Alternatively, comment out the above line, and un-comment the line below to
use version 2.0.0.Beta1 which is based on community built dependencies.
You can actually use this stack with any version of JBoss AS that implements
the Java EE 6 web profile -->
<!--
<javaee6.web.spec.version>2.0.0.Final</javaee6.web.spec.version>
-->
#else
<javaee6.web.spec.version>2.0.0.Final</javaee6.web.spec.version>
<!-- Alternatively, you can use version 3.0.0.Beta1-redhat-1 which is a release certified
to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6 maven repository.
<!-- Alternatively, comment out the above line, and un-comment the line below to
use version 3.0.0.Beta1-redhat-1 which is a release certified
to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6 maven repository. -->
<!--
<javaee6.web.spec.version>3.0.0.Beta1-redhat-1</javaee6.web.spec.version>
-->
#end
#end
</properties>

<dependencyManagement>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -26,14 +26,19 @@ $symbol_escape = '\' )
#if ($enterprise == "true" || $enterprise == "y" || $enterprise == "yes" )
<!-- Certified version of the JBoss EAP components we want to use -->
<javaee6.web.spec.version>3.0.0.Beta1-redhat-1</javaee6.web.spec.version>
<!-- Alternatively, you can use version 2.0.0.Beta1 which is based on community built dependencies.
You can actually use this stack with any version of JBoss AS that implements the Java EE 6 web profile
<!-- Alternatively, comment out the above line, and un-comment the line below to
use version 2.0.0.Beta1 which is based on community built dependencies.
You can actually use this stack with any version of JBoss AS that implements
the Java EE 6 web profile -->
<!--
<javaee6.web.spec.version>2.0.0.Final</javaee6.web.spec.version>
-->
#else
<javaee6.web.spec.version>2.0.0.Final</javaee6.web.spec.version>
<!-- Alternatively, you can use version 3.0.0.Beta1-redhat-1 which is a release certified
to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6 maven repository.
<!-- Alternatively, comment out the above line, and un-comment the line below to
use version 3.0.0.Beta1-redhat-1 which is a release certified
to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6 maven repository. -->
<!--
<javaee6.web.spec.version>3.0.0.Beta1-redhat-1</javaee6.web.spec.version>
-->
#end
Expand Down

0 comments on commit 60a94f1

Please sign in to comment.