[
https://issues.apache.org/jira/browse/GERONIMO-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466804
]
Paul McMahan commented on GERONIMO-2728:
I agree with #1 above, and also agree with #2 in principle if there is a
substantial number of modules that should be built, bundled, and undergo
release management separately from the assemblies in server/trunk. Right off
hand I don't know of any modules that fall into that category besides directory
and ldap-realm, and I wonder if some might argue that those modules should
remain in the jee5 assemblies.
If there are in fact a substantial number of modules to warrant creating a new
area in svn then I believe that new area should be called something other than
"geronimo/plugins". perhaps geronimo/opt ? IMO "plugin" is packaging
terminology and not indicative of whether or not a module belongs in
server/trunk.
That's not to say that modules moved out of server/trunk won't be offered as
plugins, I think in practically every case they should be because doing so
makes them easier to add to a running server. But there are some modules that
are offered as plugins that should stay in trunk - tomcat, jetty, admin
console, ca-helper, openjpa... and perhaps more in the 2.0 time frame.
> Exception while removing directory module from the console
> --
>
> Key: GERONIMO-2728
> URL: https://issues.apache.org/jira/browse/GERONIMO-2728
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment, security
>Affects Versions: 2.0-M2, 2.0-beta1, 2.0-beta2, 2.0
> Environment: rev # 495595
>Reporter: Hernan Cunico
> Attachments: log.txt
>
>
> removing *directory* module form the console's *Installed System Modules*
> portlet throws an exception while removing dependencies. attaching log
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
