[gatein-issues] [JBoss JIRA] (GTNPORTAL-3315) Portal setup improvements
Trong Tran (JIRA)
jira-events at lists.jboss.org
Tue Dec 3 00:12:05 EST 2013
[ https://issues.jboss.org/browse/GTNPORTAL-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trong Tran updated GTNPORTAL-3315:
----------------------------------
Description:
The Portal Setup feature was introduced since Gatein 3.6, it is always active by default.
Today there is a need that it could be able to disable the feature somehow. We also identify there are following needed improvements, potential bug fixes should be done in current implementation:
- Ability to Enable/Disable the feature
- Make it work more as an extension, to not forced adding things to core portal
- Get rid of cloning SetupOrganizationDatabaseInitializer from OrganizationDatabaseInitializer
- Removing repository/workspace name hard-coding in PortalSetupService
was:
The Portal Setup feature was introduced since Gatein 3.6, it is always active by default.
Today there is a need that we could be able to disable the feature somehow. We also identify there are following needed improvements, potential bug fixes should be done in current implementation:
- Ability to Enable/Disable the feature
- Make it work more as an extension, to not forced adding things to core portal
- Get rid of cloning SetupOrganizationDatabaseInitializer from OrganizationDatabaseInitializer
- Removing repository/workspace name hard-coding in PortalSetupService
> Portal setup improvements
> --------------------------
>
> Key: GTNPORTAL-3315
> URL: https://issues.jboss.org/browse/GTNPORTAL-3315
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Final
> Reporter: Trong Tran
> Fix For: 3.7.0.Final
>
>
> The Portal Setup feature was introduced since Gatein 3.6, it is always active by default.
> Today there is a need that it could be able to disable the feature somehow. We also identify there are following needed improvements, potential bug fixes should be done in current implementation:
> - Ability to Enable/Disable the feature
> - Make it work more as an extension, to not forced adding things to core portal
> - Get rid of cloning SetupOrganizationDatabaseInitializer from OrganizationDatabaseInitializer
> - Removing repository/workspace name hard-coding in PortalSetupService
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the gatein-issues
mailing list