Hi Joe,
I've put in a feature request [1] so the OAE builder could do this for us.
Afaik, right now you have 2 options:
1) Modifying the settings.rb file (or add it) in the OAE-Builder directory
ui = {"path" => "../3akai-ux", "repository" =>
"git://github.com/sakaiproject/3akai-ux.git", "branch" => "1.5.0",
"localbranch" => "1.5.0"}
and do:
cd OAE-Builder
rake
(---- If something goes wrong - try `cd 3akai-ux` and `git checkout -b 1.5.0
origin/1.5.0` ---- not sure whether you'll need it)
rake run
(wait until the server has started completely)
rake setup
2) Do it manually
cd OAE-Builder
rake clean
cd ../nakamura
git fetch origin
git checkout origin/master # Nakamura doesn't currently has a 1.5.0 branch yet
mvn clean install -Dmaven.test.skip
cd ../3akai-ux
git fetch origin
git checkout origin/1.5.0
cd ../OAE-Builder
rake run
(wait until the server has started completely)
rake setup #adding dummy users and dummy data + setting up FSResource.
As you can see these are quite a lot of commands and I assume that you did
`rake clone` without any modifications.
- Christian
[1] https://jira.sakaiproject.org/browse/OAEBLDR-22
On May 8, 2012, at 9:32 AM, Humbert, Joseph A wrote:
> Hi All,
>
> I have been verifying all the Accessibility issues using the OAE-Builder and
> OAE-tools. Is there an easy way to use those tools to verify fixes against
> the 1.5.0 branch instead of master?
>
> Joe Humbert, Assistive Technology and Web Accessibility Specialist
> UITS Adaptive Technology and Accessibility Centers
> Indiana University, Indianapolis and Bloomington
> 535 W Michigan St. IT214 E
> Indianapolis, IN 46202
> Office Phone: (317) 274-4378
> Cell Phone: (317) 644-6824
> [email protected]
> http://iuadapts.Indiana.edu/
>
> _______________________________________________
> oae-dev mailing list
> [email protected]
> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
_______________________________________________
oae-dev mailing list
[email protected]
http://collab.sakaiproject.org/mailman/listinfo/oae-dev
