Showcase WAR classifiers cleanup

[lfryc]

Currently we ship with following classified WARs, which distinguish target container:

- jee6 (Java EE 6 compatible)

- tomcat6

These names starts to be out-of-date, since tomcat6 WAR are being deployed on Tomcat7 and jee6 won't run on all of the Java EE 6 compatible containers.

Reason for incompability of jee6 is introduction of new APIs (JMS, JPA, CDI) and implementation requirement that demo should run out of the box.

I propose clean this up and introduce classifiers as follows:

- tomcat - Tomcat 6 and Tomcat 7 compatible (no differences currently)

- jbas6

- jbas7

- (glassfish3)

[bleathem]

Whatever happened to "write once, run anywhere?"

Your proposed renames sound good to me, although I've heard elsewhere that it's not worth supporting JBoss AS 6 anymore, as it is completely obviated by AS7.

[lfryc]

Brian Leathem wrote:

Whatever happened to "write once, run anywhere?"

Showcase as I have modified it in scope of RFPL-1465 is able to configure messaging provider, so you don't need any management operations when deploying to clean container distribution.

On AS6 and AS7 both contains HornetQ, but both of them are managed in different way - AS7 is not managable through JXM anymore (it will be probably exposed only in read-only mode [#jboss-as7]), that's why we need to have DMR client instead.

And furthemore, in Glassfish, management API is (probably) completely different.

[lfryc]

One more change which is related to this is fact that Showcase uses two principles to generate different classifiers (container profiles):

- maven-war-plugin executions in release profile

- container profiles (default (tomcat), jee6, jboss-as7)

Both of them are adequate but only release profile generated WARs are tested through CI builds.

I'm thinking about removing WAR generation from release profile and use repeated build with various container profiles.

The only issue is if Maven deploy plugin and Maven consumers on other side can handle that [1].

[1] https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-UniqueSnapshotVersionsandClassifiers

[lfryc]

Brian Leathem wrote:

..., I've heard elsewhere that it's not worth supporting JBoss AS 6 anymore, as it is completely obviated by AS7.

Yes, I think so, but we haven't run AS7 in CI yet (though guys are working on that heavily) so in my opinion we can't drop AS6 immediately without replacement.