Closed
Bug 108223
Opened 23 years ago
Closed 23 years ago
Default Plug-in should not be in the CVS repository
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: bnesse, Assigned: bnesse)
Details
The binary for the Default Plugin is currently checked into the CVS repository. As we now create it as part of the normal build process I don't see any reason for this. As I recall, this was added shortly before the release of either 6.0 or 6.01 as a stopgap measure to get the Default Plug-in released without affecting the tree. Now it just causes the Default Plug-in to appear as a lurker anytime the tree is pulled and built.
Comment 1•23 years ago
|
||
I fixed the target names in DefaultPlugin.mcp, and CVS removed the Default Plugin binary. So this is fixed.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•