Ticket #86 (closed defect: duplicate)

Opened 1 year ago

Last modified 6 months ago

Class names are not pear standard compliant and are very generic

Reported by: bmonkman@navarik.com Assigned to: hans
Priority: minor Milestone: 3.0
Component: phing-core Version: devel
Keywords: class name Cc:

Description

The class names used by Phing are overly generic and should be changed to follow the pear standard for naming conventions. When building a pear package of phing, it spits out warnings, suggesting that the class names start with "phing".

Attachments

Change History

06/14/07 15:59:44 changed by mrook

  • version changed from 2.3.0beta1 to devel.

Moving this to the "devel" milestone as it's not something to be done lightly.

07/29/07 21:36:07 changed by hans

  • milestone set to 3.0.

This will be addressed by use of namespaces in Phing 3.

11/15/07 13:14:57 changed by hans

  • status changed from new to closed.
  • resolution set to duplicate.

Is being fixed by namespace support, see #188.

Add/Change #86 (Class names are not pear standard compliant and are very generic)




Action