Bill Shannon wrote:
> Sreenivas Munnangi wrote:
>> Hi,
>>
>> The issue of workspace, specifically organizing admin source code
>> corresponding to v3 modularization has been discussed among admin
>> team members and arrived at the final structure. Following link
>> provides details.
>>
>> http://wiki.glassfish.java.net/Wiki.jsp?page=V3AdminWorkspaceStructure
>>
>> Pl. let us know if you have any suggestions.
>
> Is each module in your list a separate HK2 module?
> Or do the submodules correspond to HK2 modules?
In the following, admin is a HK2 module with pacakages
org.glassfish.web.admin.cli, org.glassfish.web.admin.amx,
org.glassfish.web.admin.amx.impl, etc.
/v3
/v3/web
/v3/web/<core modules>
/v3/web/admin
/v3/web/admin/src/main/java/org/glassfish/web/admin/cli
/v3/web/admin/src/main/java/org/glassfish/web/admin/amx
/v3/web/admin/src/main/java/org/glassfish/web/admin/amx/impl
/v3/web/admin/src/main/java/org/glassfish/web/admin/monitor
/v3/web/admin/src/main/java/org/glassfish/web/admin/plugin/impl
/v3/web/admin/src/main/java/org/glassfish/web/admin/common
>
> How do the modules relate to Maven projects?
> Which
> modules are sub-projects and what is the parent project?
For distribution/packaging purposes, web is the parent project with
admin being the sub-project. So whenever web is built, admin is also
built as part of it.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>