Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find build.xml file in parent directory tree (Trac #864) #551

Closed
phing-issues-importer opened this issue Oct 9, 2016 · 5 comments
Closed

Comments

@phing-issues-importer
Copy link

phing-issues-importer commented Oct 9, 2016

It should be possible to run phing in a subdirectory of a project, when the
build.xml file is in the root dir of the project.

This would keep people from constantly switching directories just to run phing, and allow to run phing tasks on different working directories (current subdirectory).

To prevent security problems and BC breaks, project files should have a new attribute in their xml that declares them to be subdirectory-capable. Only then phing would work from a subdirectory.

Migrated from https://www.phing.info/trac/ticket/864

{
    "status": "new", 
    "changetime": "2016-10-07T08:28:55", 
    "description": "It should be possible to run {{{phing}}} in a subdirectory of a project, when the \n{{{build.xml}}} file is in the root dir of the project.\n\nThis would keep people from constantly switching directories just to run phing, and allow to run phing tasks on different working directories (current subdirectory).\n\nTo prevent security problems and BC breaks, project files should have a new attribute in their xml that declares them to be subdirectory-capable. Only then phing would work from a subdirectory.", 
    "reporter": "cweiske", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1475828935569836", 
    "component": "phing-core", 
    "summary": "Find build.xml file in parent directory tree", 
    "priority": "tbd", 
    "keywords": "", 
    "version": "2.4.9", 
    "time": "2012-03-07T09:20:02", 
    "milestone": "4.0", 
    "owner": "mrook", 
    "type": "enhancement"
}
@phing-issues-importer
Copy link
Author

phing-issues-importer commented Oct 9, 2016

Trac update at 20130816T01:18:17: anonymous commented:

I wrote a simple wrapper shell function that does this https://gist.github.com/kimpepper/6245571

@phing-issues-importer
Copy link
Author

phing-issues-importer commented Oct 9, 2016

Trac update at 20150826T09:49:08: mrook changed milestone from "Icebox" to "3.0"

@phing-issues-importer
Copy link
Author

phing-issues-importer commented Oct 9, 2016

Trac update at 20161007T08:28:55:

  • mrook commented:

Milestone renamed

  • mrook changed milestone from "3.0" to "4.0"

@siad007
Copy link
Member

siad007 commented Nov 4, 2016

Couldn't this be done with the find option?

$ phing -find build.xml

@mrook mrook removed their assignment Nov 17, 2016
@mrook mrook modified the milestones: 3.0, 4.0 Feb 4, 2017
@mrook
Copy link
Member

mrook commented Feb 5, 2017

@siad007 yep, you're totally right. phing -find covers this case.

@mrook mrook closed this as completed Feb 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants