Project

General

Profile

Bug #2313

Metacat Skins: Skins should not be installed by default

Added by Saurabh Garg almost 14 years ago. Updated about 6 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
metacat
Target version:
Start date:
12/08/2005
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2313

Description

Not all skins should be installed when metacat is installed. Hence it should be
configurable in build.properties which skins should be installed. And bu
default, only default skin should be installed.

Also skins like esa should not be part of the shipped release.


Related issues

Is duplicate of Metacat - Bug #3751: Move skins to external directoryResolved01/14/2009

History

#1 Updated by Saurabh Garg about 13 years ago

Moving this target to 1.7

#2 Updated by Saurabh Garg about 13 years ago

Moving this bug to 1.7.

#3 Updated by Michael Daigle about 10 years ago

All skins will still ship with release, since all releases are the same. However, available skins should be configurable. As well, customized skins should be pulled in when appropriate.

#4 Updated by Michael Daigle about 10 years ago

  • Bug 3751 has been marked as a duplicate of this bug. ***

#5 Updated by Michael Daigle about 10 years ago

Note, in order to facilitate custom skins. Skins should be stored in external directory. There should be some discussion on how differences should be resolved between installed skins and corresponding customized versions.

#6 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 2313

#7 Updated by ben leinfelder over 6 years ago

  • Target version changed from Unspecified to 2.1.0
  • Assignee changed from Michael Daigle to Chris Jones

Should be considered as part of the Metacat-UI project.

#8 Updated by ben leinfelder about 6 years ago

  • Target version changed from 2.1.0 to 2.x.y

Also available in: Atom PDF