|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I forked yui2 into my own repo (for starters): https://github.com/tfennelly/yui2
I'm trying to find out how they actually built the full release assembly as this is the easiest path to making sure we are getting the right changes over in Jenkins. the yui2 codebase does not have it's own top level build script. Instead, it relies on a a separate "YUI Builder" project, which typically needs to be checked out separately to a folder parallel to the yui code. I actually checked this into a "builder" folder in my fork.
The problem I'm trying to get to the bottom of is the fact that this Builder just builds a single component (e.g. "buttons"). I'm trying to find out where the higher level release scripts are located - they do an aggregated build + apply copyright, version info etc. I was trying to hack this but it just results in a ton of diffs. Most of the diffs are OK (missing copyrights etc) but I'd like to get rid of them by building it properly if I can. Then I can see the real differences.