Opened 13 years ago
Closed 13 years ago
#8518 closed bug (fixed)
Dont delete qunit and sizzle on clean target
| Reported by: | AzaToth | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | 1.next |
| Component: | build | Version: | 1.5.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
sizzle and qunit shouldn't be deleted on make clean
Change History (3)
comment:1 Changed 13 years ago by
| Component: | unfiled → build |
|---|---|
| Priority: | undecided → low |
| Status: | new → open |
comment:3 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | open → closed |
This is addressed with the fix for #8536.
Note: See
TracTickets for help on using
tickets.
Sizzle and QUnit are deleted on clean target in order to clear the way for pulling the most current versions of each. I agree this isn't the best way to handle their inclusion. Preferably, these should be submodules