The IRC channel is #sakai on the freenode network, you can join using a web 
client at http://webchat.freenode.net/?channels=sakai and you can view the 
complete logs at http://sakai.iriscouch.com/irc/_design/viewer/index.html

03:32 <GitHub191> [nakamura] zathomas pushed 2 new commits to master: 
http://git.io/03qYfw
03:37 <GitHub159> [nakamura] zathomas pushed 2 new commits to master: 
http://git.io/ezk8tQ
03:37 <GitHub159> [nakamura/master] KERN-3044 Store paths in the cache without 
escaping them. - Carl Hall
03:37 <GitHub159> [nakamura/master] Merge pull request #932 from 
thecarlhall/kern-3044 - Zach A. Thomas
05:35 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5556 Fixing content permissions 
notification to separate each user - Dean Angerer
05:35 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5556 Cleaning up content 
permissions notification with - Dean Angerer
10:28 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5434 check username contains valid 
characters - James Sloane
10:36 <SakaiGithub> [3akai-ux] bp323 pushed 1 new commit to 1.5.0: 
http://git.io/JnKJTA
10:54 <SakaiGithub> [3akai-ux] bp323 pushed 1 new commit to 1.5.0: 
http://git.io/OxBDzQ
10:54 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5483 changed heading sizes - James 
Sloane
11:22 <SakaiGithub> [3akai-ux] bp323 pushed 2 new commits to master: 
http://git.io/gH5l_A
11:22 <SakaiGithub> [3akai-ux/master] Merge pull request #2280 from 
jsloane/SAKIII-5947 - Bert Pareyn
11:30 <SakaiGithub> [3akai-ux] bp323 pushed 2 new commits to master: 
http://git.io/xQUsyA
11:30 <SakaiGithub> [3akai-ux/master] SAKIII-5895 scroll to top of content when 
page changes - jsloane
11:30 <SakaiGithub> [3akai-ux/master] Merge pull request #2283 from 
jsloane/SAKIII-5895 - Bert Pareyn
11:33 <SakaiGithub> [3akai-ux] bp323 pushed 4 new commits to 1.5.0: 
http://git.io/gJEvAA
11:33 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5947 removed unused notification - 
jsloane
11:33 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5895 scroll to top of content when 
page changes - jsloane
11:33 <SakaiGithub> [3akai-ux/1.5.0] Merge remote-tracking branch 
'james/SAKIII-5947' into 1.5.0 - Bert Pareyn
13:37 <SakaiGithub> [OAE-Builder] stuartf pushed 3 new commits to master: 
http://git.io/dIXbvQ
13:37 <SakaiGithub> [OAE-Builder/master] OAEBLDR-27 Add count and offset 
environment vars for creating users and - Carl Hall
13:37 <SakaiGithub> [OAE-Builder/master] Merge pull request #54 from 
thecarlhall/oaebldr-27 - D. Stuart Freeman
13:37 <SakaiGithub> [OAE-Builder/master] OAEBLDR-27 Change count & offset to 
OAEBLDR_COUNT & OAEBLDR_OFFSET for better uniqueness. - Carl Hall
13:49 <MrVisser> ping froese
13:53 <froese> pong mrvisser
13:54 <MrVisser> hey froese. I'm going to start loading data into the perf 
testing environment. I've done part of a load, then realized that the solr 
server utilization is like, 0, which doesn't make sense to me.
13:54 <froese> are the indexes growing?
13:55 <MrVisser> froese, where are they stored?
13:55 <froese> one sec
13:58 <froese> looks like the last index was written on july 23rd
13:59 <MrVisser> froese: should have been written today. the configuration 
looks like it's pointing to "remote".. hmm
14:00 <MrVisser> name is "remote; URL is: 
http://OAE-SOLR-426995740.us-west-1.elb.amazonaws.com:8080/solr
14:01 <froese> that looks right
14:01 <froese> id have to look through the logs and see whats going on
14:01 <froese> can't do it right this second
14:03 <MrVisser> froese: no problem. I'll continue troubleshooting, will be 
good for me to learn this stuff any way.
14:04 <froese> :-) look for the logs where the Solr stuff comes up
14:04 <froese> a
14:04 <froese> and check the SolrServerImpl to make sure it has the right 
remote client wired in
14:04 <MrVisser> froese: everywhere I look for solr logs seems to turn up 
empty.. will keep searching.
14:04 <froese> there's also solr.log
14:06 <froese> Has everyone seen the new LinkedIn design?
14:06 <froese> we've been robbed!
14:07 <SakaiGithub> [3akai-ux] bp323 pushed 2 new commits to 1.5.0: 
http://git.io/qeVaGA
14:07 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5998 set default permission on 
dropped content - jsloane
14:07 <SakaiGithub> [3akai-ux/1.5.0] Merge pull request #2364 from 
jsloane/SAKIII-5998 - Bert Pareyn
14:14 <SakaiGithub> [3akai-ux] bp323 pushed 2 new commits to 1.5.0: 
http://git.io/NUgxeQ
14:14 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5695 set the copyright year on the 
acknowledgements page - jsloane
14:14 <SakaiGithub> [3akai-ux/1.5.0] Merge pull request #2370 from 
jsloane/SAKIII-5695 - Bert Pareyn
14:25 <SakaiGithub> [3akai-ux] bp323 pushed 2 new commits to 1.5.0: 
http://git.io/sD401Q
14:25 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5784 made infinite scroll an 
aria-live region and added an alt attribute to the loading img - jsloane
14:25 <SakaiGithub> [3akai-ux/1.5.0] Merge pull request #2366 from 
jsloane/SAKIII-5784 - Bert Pareyn
14:33 <SakaiGithub> [3akai-ux] bp323 pushed 1 new commit to 1.5.0: 
http://git.io/A0ByGg
14:33 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5728 Select area too wide when 
choosing too what you want to share content from your library - Celine Quoy
14:36 <SakaiGithub> [3akai-ux] bp323 pushed 1 new commit to 1.5.0: 
http://git.io/wjVRVA
14:36 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5733 Within Profile when adding a 
new publication the submit button should be called Add and not update - Celine 
Quoy
14:38 <GitHub45> [nakamura] zathomas pushed 1 new commit to master: 
http://git.io/MOeHpA
14:38 <GitHub45> [nakamura/master] KERN-2953 add org.json bundle to the main 
build profile - Zach A. Thomas
14:41 <zacht> ha! good riddance KERN-2953
14:42 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5983 - Remove .infinity selectors 
from search pages - Nicolaas Matthijs
14:50 <SakaiGithub> [3akai-ux] bp323 pushed 2 new commits to 1.5.0: 
http://git.io/h_DxRw
14:50 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5736 fix button width - jsloane
14:50 <SakaiGithub> [3akai-ux/1.5.0] Merge pull request #2367 from 
jsloane/SAKIII-5736 - Bert Pareyn
15:42 <MrVisser> should I have a calliflower invite?
15:43 <zacht> mrvisser I think you should. Remind me what timezone you're in…
15:43 <zacht> mrvisser it's 4pm EDT
15:44 <ctweney> zacht:  can you clarify what's intended in the Trello card 
"Document (ad hoc) data model for pooled content"?
15:44 <zacht> ctweney Yeah. It means the equivalent of an ER diagram.
15:45 <zacht> ctweney Here are the properties. Here is what we consider to be 
keys.
15:45 <MrVisser> zacht that is my timezone
15:45 <zacht> ctweney e.g., what is the relationship between docs and pages?
15:45 <ctweney> so, it's documenting what we have today? or what ought to be?
15:46 <zacht> ctweney I supposed it's "ought to be", but the current functions 
of the system are like de facto contract.
15:47 <ctweney> ok
15:47 <zacht> ctweney The main purpose of that is to help OmniTI (I suppose it 
helps us too) see what our usage patterns are.
15:47 <ctweney> another question zacht: do sakaidocs get their own (separate) 
service API or are they still just a fancy form of pooled content?
15:48 <zacht> ctweney There is a lot of overlap. Maybe one service derives from 
the other? That's a good topic to discuss with the UX team.
15:49 <ctweney> ok
15:50 <SakaiGithub> [3akai-ux] bp323 pushed 2 new commits to 1.5.0: 
http://git.io/kpqczA
15:50 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5611 Adding default search option 
to sort by Relevance - Dean Angerer
15:50 <SakaiGithub> [3akai-ux/1.5.0] Merge pull request #2374 from 
apex13/SAKIII-5611b - Bert Pareyn
16:07 <MrVisser> froese: what are the pass phrases to those certs on 
oae-performance?
16:08 <zacht> Current limitation: I don't know how to have it record more than 
one bundle at a time. :-(
16:10 <froese> the certs on the machine shouldn't have passphrases
16:10 <froese> nor the keys
16:11 <MrVisser> froese, ok, I think I'm stepping a bit on the stuff that 
anthony was doing.
16:14 <SakaiGithub> [3akai-ux] bp323 pushed 1 new commit to 1.5.0: 
http://git.io/NTWjrw
16:14 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-5566 fix contact button in IE9 and 
added error notification - James Sloane
16:29 <zacht>  ctweney You should use this cobertura hack to get stats on 
files/impl
16:31 <ctweney> cool zacht, where's the hack?
16:31 <zacht> ctweney I need to write it up. There are some limitations I want 
to overcome.
16:32 <ctweney> ah
16:32 <ctweney> looks promising from your screenshot though
16:33 <zacht> ctweney the main limitation currently is the necessity to embed 
the cobertura dependency in my bundle.
16:34 <zacht> ctweney assuming we only want to do this every now and then, it's 
still worth it to put together a special bundle for it.
16:36 <GitHub30> [nakamura] thecarlhall pushed 2 new commits to master: 
http://git.io/cXp6TQ
16:36 <GitHub30> [nakamura/master] KERN-3056 Include the module 
bundles/org.json in pom.xml - Branden Visser
16:36 <GitHub30> [nakamura/master] Merge remote-tracking branch 
'mrvisser@github/kern-3056' - Carl Hall
16:41 <MrVisser> froese: I restarted the appserver on oae-app0 and now 
oae-performance relentlessly gives 502 proxy error. 
oae-appservers-365563856.us-west-1.elb.amazonaws.com:8080 seems to respond fine 
though. Apache logs aren't giving me any useful information :( Do the balancer 
members need to be refreshed somehow after an outage?
16:42 <froese> maybe the reconnect threshold is too high?
16:42 <froese> restart apache
16:42 <MrVisser> froese: I did
16:42 <froese> maybe we need to wait for the amazon elb to recognize them
16:42 <MrVisser> froese: after I reverted the cert/key stuff back to the 
original stuff.
16:43 <froese> what about OAE-AppServers-365563856.us-west-1.elb.amazonaws.com
16:43 <MrVisser> froese: when I go to 
oae-appservers-365563856.us-west-1.elb.amazonaws.com:8080, it seems to go 
through OK..
16:43 <froese> oh sorry yes you said that earlier
16:43 <froese> hrm
16:43 <MrVisser> server protection service bounces me out, but that's expected.
16:44 <froese> the logs are in 
/var/www/vhosts/oae-performance.sakaiproject.org:443/logs
16:44 <froese> [Thu Jul 26 09:39:15 2012] [error] [client 76.10.128.124] 
(20014)Internal error: proxy: error reading status line from remote server 
oae-appservers-365563856.us-west-1.elb.amazonaws.com:8080
16:49 <denbuzze> ping stuartf - I've seen your PR's 
https://github.com/sakaiproject/3akai-ux/pull/2376, 
https://github.com/sakaiproject/3akai-ux/pull/2377 and nakamura: 
https://github.com/sakaiproject/nakamura/pull/936 - should we 1) merge in the 
1.4.1 PR into master 2) Create a 1.4.1 branch out of that and 3) merge the 
1.5.0 PR into master? /cc ctweney
16:51 <ctweney> stuartf and denbuzze I'm also wondering, if 3akai-ux has a 
1.4.1, shouldn't nakamura also have a 1.4.1 commit?
16:51 <denbuzze> ctweney: I was thinking the same thing - /cc zacht any 
thoughts on this?
16:52 <zacht> denbuzze ctweney I'm not opposed to putting out nakamura 1.4.1, 
but we've never talked about what would go in it. :-)
16:53 <zacht> ctweney Do you mean just creating a 1.4.1 tag from the branch as 
it is?
16:53 <denbuzze> zacht ctweney: for us it will be the complete reformatting 
(whitespaces etc) of our code
16:53 <zacht> scorched earth!
16:54 <zacht> Does that mean I can remove tab characters everywhere?
16:54 <ctweney> zacht:  no, stuartf created a separate commit that bumps 
3akai-ux to 1.4.1
16:55 <stuartf> denbuzze: yes, that sounds correct
16:55 <zacht> ctweney Unless I'm mistaken, the 1.4.0 nakamura branch (should 
actually be called 1.4.x) is currently sitting at 1.4.1-SNAPSHOT. So we would 
just follow the usual (scripted) procedure to move those up, commit, tag, and 
move them again to 1.4.2-SNAPSHOT.
16:57 <ctweney> you're right zacht, nakamura 1.4.0 (the branch) is at 
1.4.1-SNAPSHOT
16:57 <ctweney> zacht:  we don't need to release 1.4.1 yet to my knowledge
16:57 <ctweney> just have it in the branch
16:57 <ctweney> I think that's what stuartf is doing in 3akai, am I right?
16:57 <GitHub55> [nakamura/master] KERN-3001 Initial commit of Perf4J 
integration into Nakamura - Branden Visser
16:57 <GitHub55> [nakamura] thecarlhall pushed 4 new commits to master: 
http://git.io/dVBQBQ
16:57 <GitHub55> [nakamura/master] KERN-3001 Fixing spacing issue in events 
pom.xml - Branden Visser
16:57 <GitHub55> [nakamura/master] KERN-3001 Remove unnecessary embedding of 
slf4j-api -- what was I thinking? - Branden Visser
16:58 <zacht> thecarlhall!
16:58 <thecarlhall> zacht!
16:58 <thecarlhall> !!
16:58 <denbuzze> zacht: the thing is, it's targeting the master branch - 
https://github.com/sakaiproject/3akai-ux/pull/2376
16:58 <thecarlhall> mrvisser, is there a way to get stats using perf4j that 
aren't time boxed? e.g. all cache hits ever
16:59 <MrVisser> thecarlhall: you can crunch the raw stats log file
16:59 <stuartf> denbuzze: another possibility would be just merge the 1.5.0 PR, 
because it has both commits in it, then checkout HEAD^ and branch 1.4.x from 
there
16:59 <thecarlhall> mrvisser, I see. What about adding a graph for that? New 
appender + some graph code?
17:00 <thecarlhall> mrvisser, or just some graph code only?
17:01 <MrVisser> thecarlhall: the graph appender configurations I think have 
configurations for time-boxes that you might be able to set high, but they 
might only spit out information in that interval as well, which makes it not 
very helpful.
17:01 <MrVisser> afaik such a think does not exist right now
17:03 <MrVisser> thecarlhall: 
http://perf4j.codehaus.org/devguide.html#Using_the_log4j_Appenders_to_Generate_Real-Time_Performance_Information
  TimeSlice property might do the trick.
17:04 <ctweney> denbuzze:  I have to run out for physical therapy in about 15 
min. Should I merge the nakamura 1.5.0 version bump or hold on to it?
17:04 <denbuzze> ctweney: I would go ahead with it
17:04 <ctweney> okee dokee
17:04 <denbuzze> ctweney: I'll follow stuartf 's suggestion
17:04 <ctweney> sounds good
17:05 <GitHub45> [nakamura] ctweney pushed 3 new commits to master: 
http://git.io/MH5tsw
17:05 <GitHub45> [nakamura/master] change 1.4.0-SNAPSHOT to 1.5.0-SNAPSHOT - D. 
Stuart Freeman
17:05 <GitHub45> [nakamura/master] update version in tools/version - D. Stuart 
Freeman
17:05 <GitHub45> [nakamura/master] Merge pull request #936 from 
stuartf/bump-version - Chris Tweney
17:08 <SakaiGithub> [3akai-ux] christianv pushed 2 new commits to master: 
http://git.io/ZvoJVw
17:08 <SakaiGithub> [3akai-ux/master] SAKIII-6063 bump 1.4.0 to 1.4.1 - D. 
Stuart Freeman
17:08 <SakaiGithub> [3akai-ux/master] SAKIII-6047 change version 1.4.1 to 1.5.0 
- D. Stuart Freeman
17:24 <SakaiGithub> [3akai-ux] christianv pushed 2 new commits to master: 
http://git.io/-YYOEg
17:24 <SakaiGithub> [3akai-ux/master] SAKIII-6064 add Sakai Maven snapshot and 
release repo definitions to <distributionManagement> - Anthony Whyte
17:24 <SakaiGithub> [3akai-ux/master] Merge remote-tracking branch 
'arwhyte/SAKIII-6064' - Christian Vuerings
17:25 <SakaiGithub> [3akai-ux] christianv pushed 1 new commit to 1.4.1: 
http://git.io/UUqz8Q
17:25 <SakaiGithub> [3akai-ux/1.4.1] Merge remote-tracking branch 
'arwhyte/SAKIII-6064' into 1.4.1 - Christian Vuerings
17:26 <SakaiGithub> [3akai-ux] christianv pushed 1 new commit to 1.5.0: 
http://git.io/hvQ1lg
17:26 <SakaiGithub> [3akai-ux/1.5.0] Merge remote-tracking branch 
'arwhyte/SAKIII-6064' into 1.5.0 - Christian Vuerings
17:38 <MrVisser> froese: it appears *both* app servers *must* be available for 
the proxy to work.
17:38 <MrVisser> I had app1 down, but app0 was up.
17:38 <froese> there has to be some ELB setting
17:44 <thecarlhall> ctweney, you should contribute to the "HTTP Caching in 
Java"   https://devcenter.heroku.com/articles/open-topics
18:00 <SakaiGithub> [3akai-ux] bp323 pushed 2 new commits to 1.5.0: 
http://git.io/JRWqlg
18:00 <SakaiGithub> [3akai-ux/1.5.0] Merge pull request #2375 from 
apex13/SAKIII-5824b - Bert Pareyn
18:09 <MrVisser> ping kentfitz, quick question about server configuration
18:09 <kentfitz> mrvisser: what's up
18:09 <MrVisser> I have manually placed a config file: 
./sling/config/org/sakaiproject/nakamura/lite/storage/jdbc/JDBCStorageClientPool.config
18:10 <MrVisser> but the values are not being picked up into the server after 
it has been restarted. Do you know why that might be?
18:11 <kentfitz> mrvisser: Hmmmm, we'd see that with the mysql config file for 
JDBCStorageClientPool if nakamura wasn't compiled with the correct values in 
list.xml, but that's not an issue for postgres. What are you trying to 
configure it for?
18:12 <MrVisser> kentfitz: trying to configure it to postgres
18:13 <MrVisser> kentfitz: but it always shows derby information when I press 
the configuration icon in the admin console.
18:13 <kentfitz> mrvisser: Thanks, that was my next question, how are you 
determining it's not picking it up.
18:13 <kentfitz> mrvisser: Let me look at a setup, one moment
18:14 <MrVisser> thanks kentfitz
18:14 <MrVisser> kentfitz: also, when I "Reset" the config, it blanks out.
18:15 <kentfitz> mrvisser: Can I see your .config file?
18:15 <MrVisser> 
service.pid="org.sakaiproject.nakamura.lite.storage.jdbc.JDBCStorageClientPool"
18:15 <MrVisser> jdbc-driver="org.postgresql.Driver"
18:15 <MrVisser> 
jdbc-url="jdbc:postgresql://OAE-Postgres-566174176.us-west-1.elb.amazonaws.com/nakamura?charSet\=UTF-8&tcpKeepAlive=true"
18:15 <MrVisser> password="ironchef"
18:15 <MrVisser> username="nakamura"
18:15 <MrVisser> that is the contents
18:18 <SakaiGithub> [3akai-ux/master] Merge remote-tracking branch 
'arwhyte/SAKIII-6065' - Christian Vuerings
18:18 <SakaiGithub> [3akai-ux] christianv pushed 1 new commit to 1.4.0: 
https://github.com/sakaiproject/3akai-ux/commit/56b327ca425f273cf8b7b662d869f6648f7fc581
18:18 <SakaiGithub> [3akai-ux/1.4.0] Merge remote-tracking branch 
'arwhyte/SAKIII-6065' into 1.4.0 - Christian Vuerings
18:20 <kentfitz> mrvisser: Hmmm, I admit I was still using a config file as 
specified for 1.3.0. It has a bit more in it. 
https://oae-community.sakaiproject.org/content#p=kXyf3CaWaa/Configuring%20Nakamura%20for%20Postgres
18:23 <SakaiGithub> [3akai-ux] christianv pushed 1 new commit to 1.4.0: 
http://git.io/ZuVcrQ
18:23 <SakaiGithub> [3akai-ux/1.4.0] NOJIRA - the 1.4.0 branch should be using 
1.4.0-snapshot - Christian Vuerings
18:23 <thecarlhall> hey raydavis, for solr-82, should escaping also be added to 
json search nodes?
18:24 <raydavis> thecarlhall, yes, that is an IMMENSE commit on my SOLR-75 
upgrade branch.
18:24 <thecarlhall> raydavis, gotcha
18:24 <raydavis> So I won't be closing SOLR-82 right away.
18:26 <raydavis> thecarlhall if you want to monitor progress: 
https://github.com/raydavis/nakamura/commits/SOLR-75/
18:27 <raydavis> I'm hoping to get through the last of the integration test 
failures soon & get a big review next week. I anticipate uncaught bugs (mostly 
from forward-slash) so it would be good to get it in early in the release 
cycle. Also, the merge conflicts are killer.
18:27 <SakaiGithub> [3akai-ux] christianv pushed 2 new commits to 1.4.1: 
http://git.io/kqFLpw
18:27 <SakaiGithub> [3akai-ux/1.4.1] Merge remote-tracking branch 
'arwhyte/SAKIII-6065' into 1.4.1 - Christian Vuerings
18:27 <SakaiGithub> [3akai-ux/1.4.1] NOJIRA - 1.4.1 branch should be using 
1.4.1-SNAPSHOT - Christian Vuerings
18:29 <arwhyte> zacht ping
18:29 <zacht> arwhyte hi.
18:30 <arwhyte> cell re: 1.4.0 tags
18:30 <SakaiGithub> [3akai-ux] christianv pushed 1 new commit to 1.5.0: 
http://git.io/3M_sjw
18:30 <SakaiGithub> [3akai-ux/1.5.0] SAKIII-6065 - add wagon-ssh extension to 
<build> - Christian Vuerings
18:31 <zacht> arwhyte For some reason, my phone didn't ring. It says I have a 
voicemail from you, though.
18:54 <MrVisser> froese: I no longer have any clue what is going on :( It 
doesn't seem like oae-performance is hitting either app0 or app1, though it is 
getting a response. Nothing is going through either machine's logs. if I do 
curl requests for localhost:8080/ on those specific machines, I am getting log 
entries on the respective machines, though.
18:59 <MrVisser> froese: scratch that, looks like things are going through app1.
19:01 <lancespeelmon> mrvisser: I am getting a compile error on per4j - not 
sure if it is just me
19:02 <MrVisser> lancespeelmon: hmm. is it failing on perf4j-enhanced library?
19:02 <MrVisser> saying that the artifact is not available?
19:02 <lancespeelmon> let me check one thing
19:02 <lancespeelmon> [ERROR]   The project 
org.sakaiproject.nakamura:org.sakaiproject.nakamura.perf4j:1.4.0-SNAPSHOT 
(/Develop/k2/nakamura/bundles/perf4j/pom.xml) has 4 errors
19:02 <lancespeelmon> [ERROR]     'dependencies.dependency.version' for 
commons-jexl:commons-jexl:jar is missing. @ line 85, column 17
19:02 <lancespeelmon> [ERROR]     'dependencies.dependency.version' for 
org.sakaiproject.nakamura:perf4j-enhanced:jar is missing. @ line 89, column 17
19:02 <lancespeelmon> [ERROR]     'dependencies.dependency.version' for 
org.aspectj:aspectjrt:jar is missing. @ line 93, column 17
19:02 <lancespeelmon> [ERROR]     'dependencies.dependency.version' for 
log4j:log4j:jar is missing. @ line 101, column 17
19:03 <lancespeelmon> Apache Maven 3.0.4
19:03 <MrVisser> lancespeelmon: are you building from the base?
19:03 <raydavis> Nakamura master currently has build errors.
19:03 <lancespeelmon> yes just trying mvn clean
19:03 <lancespeelmon> ok
19:03 <raydavis> Looks like bad parents in org.json & pref4j
19:04 <MrVisser> lancespeelmon: that suggests to me that the base pom only 
needs to be refreshed first
19:04 <raydavis> zacht ^^ conflicting merges?
19:04 <MrVisser> lancespeelmon: meaning, need to do an install
19:04 <MrVisser> raydavis: the org.json thing should be fixed as of this morning
19:05 <MrVisser> or maybe noonish
19:05 <zacht> raydavis looking into it now.
19:05 <raydavis> zacht, mrvisser, definitly a matter of those two POMs not 
being updated to 1.5.0-SNAPSHOT.
19:06 <SakaiGithub> [3akai-ux] bp323 pushed 2 new commits to master: 
http://git.io/rU5l3Q
19:06 <SakaiGithub> [3akai-ux/master] SAKIII-5838 validate password change 
fields on focus out - jsloane
19:06 <SakaiGithub> [3akai-ux/master] Merge pull request #2304 from 
jsloane/SAKIII-5838 - Bert Pareyn
19:14 <lancespeelmon> should be 1.3.7-SNAPSHOT
19:14 <raydavis> Hoo boy. thecarlhall, my revised pull request might be delayed 
a bit while Nakamura master gets sorted out.
19:24 <thecarlhall> raydavis, why's that? your work is in a branch
19:26 <SakaiGithub> [3akai-ux] zathomas created 1.4.0-release (+2 new commits): 
http://git.io/gYiSeQ
19:26 <SakaiGithub> [3akai-ux/1.4.0-release] release_pre_process: Moving config 
files from 1.4.0-SNAPSHOT to 1.4.0 - Zach A. Thomas
19:26 <SakaiGithub> [3akai-ux/1.4.0-release] [maven-release-plugin] prepare 
release 1.4.0 - Zach A. Thomas
19:37 <zacht> we'll be back in business in a couple more minutes.
19:38 <lancespeelmon> zacht: I have been watching merges in 1.4.0 branch - 
should I also worry about 1.4.0-release branch?
19:38 <MrVisser> raydavis: was wondering if I can pick your brain on a quick 
remote solr issue.
19:39 <zacht> lancespeelmon, no, I'm going to bring that stuff back to 1.4.0 
within a day.
19:41 <thecarlhall> lancespeelmon, looks like this will be of interest to you 
if zacht hasn't already brought it in
19:41 <thecarlhall> https://github.com/sakaiproject/nakamura/pull/938
19:41 <thecarlhall> kern-3058
19:46 <raydavis> mrvisser, hey, just making some lunch. What's up (or down)?
19:47 <MrVisser> well, I'm trying to configure OAE to use one. the 
SolrServerServiceImpl is configured to use "remote", and the RemoteSolrClient 
exists, with its client-name set to "remote". But regardless, the server still 
uses embedded. Am I missing some area to check that you know of?
19:51 <raydavis> Checking, mrvisser...
19:52 <raydavis> mrvisser, see: 
https://github.com/ets-berkeley-edu/myberkeley/tree/dev/solrserver/src/main/resources/sling/config/org/sakaiproject/nakamura/solr
19:54 <raydavis> I don't see more than that needed.
19:57 <raydavis> mrvisser, is the Solr server running? I assume you probably 
saw Carl's documentation for what's needed to run it in OAE 1.4.0, but just in 
case...
19:58 <MrVisser> raydavis: this is using 1.3.0 for now. hmm
19:58 <MrVisser> raydavis: I guess I'll just have to troubleshoot further. 
thanks for your help!
19:58 <GitHub94> [nakamura/master] NOJIRA no version number left behind. - Zach 
A. Thomas
19:58 <GitHub94> [nakamura] zathomas pushed 1 new commit to master: 
http://git.io/Gv2-rQ
19:59 <raydavis> Shouldn't be an issue, then. Sorry, mrvisser, point me at logs 
if/when you have 'em.
20:25 <stuartf> 
https://trello.com/board/trg-planning-board/4ff362b06acac58850c4d19f
20:26 <lancespeelmon> any idea how to fix this?
20:26 <lancespeelmon> [ERROR] Failed to execute goal on project 
org.sakaiproject.nakamura.memory: Could not resolve dependencies for project 
org.sakaiproject.nakamura:org.sakaiproject.nakamura.memory:bundle:1.5.0-SNAPSHOT:
 Failure to find org.sakaiproject.nakamura:perf4j-enhanced:jar:0.9.16 in 
http://repo1.maven.org/maven2/ was cached in the local repository, resolution 
will not be reattempted until the update interval of maven repo has elapsed or 
updates are forced -> [Help 
20:26 <lancespeelmon> sorry just asking if someone has crossed this bridge 
already
20:27 <raydavis> lancespeelmon, I believe that was the fix mrvisser referred to 
as a-comin'.
20:28 <lancespeelmon> ta
20:59 <SakaiGithub> [3akai-ux] bp323 pushed 2 new commits to 1.5.0: 
http://git.io/q63LEg
20:59 <SakaiGithub> [3akai-ux/1.5.0] Merge remote-tracking branch 
'james/SAKIII-5838' into 1.5.0 - Bert Pareyn
22:12 <GitHub170> [nakamura/master] KERN-2983 SOLR-82 Support long Solr 
queries; escape forward-slash in queries - Ray Davis
22:12 <GitHub170> [nakamura/master] Merge pull request #935 from 
raydavis/KERN-2983 - Carl Hall
22:30 <GitHub159> [nakamura] zathomas pushed 2 new commits to 1.4.0-release: 
http://git.io/JfX2hQ
22:30 <GitHub159> [nakamura/1.4.0-release] KERN-3058 uncomment Sakai Maven 
snapshot and release repos in <distributionManagement> - Anthony Whyte
22:30 <GitHub159> [nakamura/1.4.0-release] Merge pull request #940 from 
arwhyte/KERN-3058 - Zach A. Thomas
23:17 <zacht> ping ctweney stuartf thecarlhall
23:18 <zacht> ^^ You might all be interested in the Cobertura-fu I achieved 
today: http://screencast.com/t/yQmXbI1G
23:18 <thecarlhall> woot!
23:19 <zacht> You'll notice that my presentation ends rather abruptly. I ran up 
against Jing's hard five-minute limit. :-)

_______________________________________________
oae-dev mailing list
[email protected]
http://collab.sakaiproject.org/mailman/listinfo/oae-dev

Reply via email to