Activate enterprise cluster and disable modules with incompatible licenses

[matthiasblaesing]

PR #1098 activates the enterprise cluster. There are however modules,
that have dependencies on incompatible license (wildfly + jboss LGPL,
weblogic 9 commercial, wsit OASIS license). PR #1101 removes some,
but skips wildfly (it is indicated, that red hat might be willing to relax
licensing for the DTDs/XSDs).

In the current state however the module does not qualify and thus is
disabled.

The enterprise cluster also includes some libraries, that need either
adjustment to use common dependencies or adjustments in the build
system to tollerate duplicate libraries.

This PR merges the work from #1098, #1101 and adds the described
pieces. In combination this should let the travis builds succeed.

Please do not squash this, I'll merge myself, when reviewed.

Closes: #1098
Closes: #1101

[matthiasblaesing]

I'm looking into the build failures.

[matthiasblaesing]

The travis build is green now. There were remaining dependencies that referenced the disabled modules and metro.model needs to be removed to, as it depends on wsit. I did not go through the EE modules though.

[geertjanw]

Makes sense. I vote to merge and then to take it from there, now that everything is green.

[lkishalmi]

Looks good to me.

[matthiasblaesing]

Thank you both for checking - lets see how the fallout will look.

[geertjanw]

I've unzipped the latest build that includes the enterprise cluster. Something isn't working quite right with the enablement, i.e., when clicking Next in 'Java Web' or 'Java EE' in the New Project dialog, to enable the feature, the 'Finding Feature' dialog appears and messages of 'Not all requested modules can be installed' appears, starting with org.netbeans.modules.web.primefaces.

[matthiasblaesing]

Yes I see, it can be reproduced locally to. However, manually enabling JavaEE in the plugin manager correctly enabled the feature and then the error is gone. It would be great if some one with a bit more experience in the black magic of automatic feature enablement (is that ergonomics?) could have a look.

[matthiasblaesing]

Update: please clear the userdir. I ran ant tryme after I removed nbbuild/testuserdir/. After that I'm correctly asked do "Download and activate" the feature.

[geertjanw]

I can still reproduce it, though I started by downloading the ZIP from the artifacts on Jenkins, then ran with a fresh user directory, and can still see the same problem.

[geertjanw]

Definitely was a network issue of some kind, VPN, etc.