Skip to content

* Use path.resolve for frameworkPath #244

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

Merged
merged 1 commit into from
Feb 26, 2015
Merged

Conversation

Fatme
Copy link
Contributor

@Fatme Fatme commented Feb 25, 2015

  • Don't delete frameworkPath directory

@ns-bot
Copy link

ns-bot commented Feb 25, 2015

Test FAILed.

@ErjanGavalji
Copy link
Contributor

test this please

@ns-bot
Copy link

ns-bot commented Feb 25, 2015

Test FAILed.

@ErjanGavalji
Copy link
Contributor

test this please

@ns-bot
Copy link

ns-bot commented Feb 25, 2015

Test PASSed.

@rosen-vladimirov
Copy link
Contributor

👍 after green build

* Don't delete frameworkPath directory
@Fatme Fatme force-pushed the fatme/fix-frameworkPath-option branch from a94b9df to 8fce1b1 Compare February 25, 2015 16:25
@ns-bot
Copy link

ns-bot commented Feb 25, 2015

Test PASSed.

@ErjanGavalji
Copy link
Contributor

👍

Fatme pushed a commit that referenced this pull request Feb 26, 2015
@Fatme Fatme merged commit fe952b5 into release Feb 26, 2015
@Fatme Fatme deleted the fatme/fix-frameworkPath-option branch February 26, 2015 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants