Understand your Mac and iPhone more deeply by tracing the evolution of Mac OS X from prelease to Swift. John Siracusa delivers the details.
You've got two main options:
jobs.scheduleTemporaryJob({ | |
jobName: 'SimpleAuthorModificationJob', | |
runAs: 'system', | |
cronExpression: '0 0/1 * 1/1 * ? *', | |
script: function(){ | |
batchExecuter.processFolderRecursively({ | |
'root': repository.getCompanyHome(), | |
onNode: function(node) { | |
if (node.isDocument) { | |
node.properties['cm:author'] = 'Alfresco'; |
var MIN_MISS_PERCENTAGE = 10; | |
var fields = [ "CacheType", ".Bean", "ObjectCount", "CacheHits", "CacheMisses", "CacheMissPercentage" ]; | |
var padding30 = Array(30).join(' '), padding12 = Array(12).join(' '), padding20 = Array(20).join(' '); | |
var platformMBeanServer = Packages.java.lang.management.ManagementFactory.getPlatformMBeanServer(); | |
function printInColumns(values) { | |
var beanName = values[1]; |
user name: liferay passwod : liferay
Commands:
Setting keyboard:
setxkbmap en_US
During Liferay DEVCON 2015 some interesting topics spurred out of the new Liferay Theme build process.
This document, and the expected following discussion, is here to understand how we can guarantee for web front-end engineers a friendly development environment and a de-facto standards adherent runtime.
At Liferay DEVCON 2015 a [new way to build Liferay Themes][ltt] has been announced. It is built around [gulp][gulp] tasks and offers the concept of Themelets, composable features distributable through [npm][npm]. Themelets are then merged in your own theme at build time.
I'm definitely not looking for work. However to provide some helpful guidance for hiring like-minded engineers, I would only consider working for a company if it met these requirements:
<#-- dump.ftl | |
-- | |
-- Generates tree representations of data model items. | |
-- | |
-- Usage: | |
-- <#import "dump.ftl" as dumper> | |
-- | |
-- <#assign foo = something.in["your"].data[0].model /> | |
-- | |
-- <@dumper.dump foo /> |
var node = search.findNode(<nodeRefOfADocumentOrFolder>); | |
var modified = node.properties.modified; | |
policies.disableForNode(node); | |
node.setName("C10"); | |
node.save(); | |
node.reset(); | |
policies.enableForNode(node); | |
var modifiedAfter = node.properties.modified; |
// get the global group | |
Group globalGroup = GroupLocalServiceUtil.getCompanyGroup(companyId); | |
//get the guest group | |
Group guestGroup = GroupLocalServiceUtil.getGroup(companyId, GroupConstants.GUEST); |
#!/usr/bin/ruby | |
# | |
# This script fixes /usr/local only. | |
# | |
# 6th January 2010: | |
# Modified the script to just fix, rather than install. - rpavlik | |
# | |
# 30th March 2010: | |
# Added a check to make sure user is in the staff group. This was a problem | |
# for me, and I think it was due to me migrating my account over several |