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

Move package building logic into separate tool #4108

Closed
devversion opened this issue Apr 15, 2017 · 2 comments
Closed

Move package building logic into separate tool #4108

devversion opened this issue Apr 15, 2017 · 2 comments
Assignees
Labels
area: dev-infra Issue related to internal project infrastructure

Comments

@devversion
Copy link
Member

The build logic should not live in tools/gulp anymore. It could be exposed as a separate tool that will be shared between the different libraries.

@devversion devversion added the area: dev-infra Issue related to internal project infrastructure label Apr 15, 2017
@devversion devversion self-assigned this Apr 15, 2017
devversion added a commit to devversion/material2 that referenced this issue Apr 21, 2017
* No longer creates the whole set of gulp tasks just to build a single package.
* Makes the package building & releasing more consistent. No extra `build:release` just for the `lib` package.

References angular#4108
devversion added a commit to devversion/material2 that referenced this issue Apr 21, 2017
* No longer creates the whole set of gulp tasks just to build a single package.
* Makes the package building & releasing more consistent. No extra `build:release` just for the `lib` package.

References angular#4108
mmalerba pushed a commit that referenced this issue Apr 25, 2017
* build: use shared logic to build packages

* No longer creates the whole set of gulp tasks just to build a single package.
* Makes the package building & releasing more consistent. No extra `build:release` just for the `lib` package.

References #4108

* Address feedback
@devversion
Copy link
Member Author

As a reference: #4719

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: dev-infra Issue related to internal project infrastructure
Projects
None yet
Development

No branches or pull requests

1 participant