|summary:||Fixing the distribution assembly issue that Shingwai was facing, which is that the most of the modules were placed directly under|
|date:||2008-03-04 22:28:09 UTC (9 years)|
|message:||Fixing the distribution assembly issue that Shingwai was facing,
which is that the most of the modules were placed directly under
modules/ and not under modules/web, where they were supposed to.
It turns out that the org.glassfish.core:security module was declaring
a provided dependency to webtier, and because the security module was
not in the webtier, this was causing the build to consider almost all
the modules to be shared.
The key here is that the dependency from security to webtier is
in the "provided" scope. I don't think we ever collectively decided
what it means for an HK2 module to depend on another one with the
provided scope, but this appears to be used as an indication of
soft dependency, so I'm taking advantages of this by treating
such dependency in the distribution assembly process little differently.
By cutting the provided scope dependency in the retention computation,
the build now considers webtier to be a part of the webtier-all module
and not shared, so we achieve the desired effect of moving most modules
under modules/web again.