Modify ↓

Ticket #86 (closed defect: duplicate)

Opened 5 years ago

Last modified 3 years ago

Class names are not pear standard compliant and are very generic

Reported by: bmonkman@… Owned by: hans
Priority: minor Milestone: TBD
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

comment:1 Changed 5 years ago 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.

comment:2 Changed 5 years ago by hans

  • Milestone set to 3.0

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

comment:3 Changed 4 years ago by hans

  • Status changed from new to closed
  • Resolution set to duplicate

Is being fixed by namespace support, see #188.

View ↑

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

Attachments ↑
 
Note: See TracTickets for help on using tickets.