reconstructing oracle connect string from userenv details

select sys_context('userenv','IP_ADDRESS') || '=' || sys_context('userenv','instance_name')  || '.' || sys_context('userenv','db_domain') from dual;

990 mvn versions:set -DnewVersion=1.0.0 997 next_version=1.0.0 999 svn copy . https://conexus.com:9443/subversion/sefs_common/fxs-deploy/tags/${next_version} $svn_opts -m "Tagged by SEFS shared-library. [artf1376420] Release ${next_version}"

email all users that have exceeded their /home/ size quota with oneliner in du, perl

du -skh /home/* 2> /dev/null | sort -h | perl -pe 'if (/^\d{3}M/){ ($sz,$who) = $_=~ m!(\S+)\s\/home\/[a-z]{1,2}(75\d+)$!mxi;if ($who) {open(MAIL, "|/usr/sbin/sendmail -t");print MAIL "To: $who\@company.com\nFrom: mightymouse\@company.com\nSubject: homedir size exceeds: $sz; please remove items from your /home/ directory on uwb00078\n\nhomedir current size exceeds $sz > 99.9M; please remove items from your /home/ directory on uwb00078!";close(MAIL);print "$who $sz\n"}} $_=undef'

Syntax for Maven / Eclipse Lifecycle mapping

New syntax for specifying lifecycle mapping metadata

A new syntax has been introduced to simplify lifecycle mapping metadata for plugin executions, using processing instructions within plugin/executions/execution nodes.

Supported syntax:

• <?m2e ignore?> this execution will be ignored;
• <?m2e execute?> this execution will be executed once on project import;
• <?m2e execute onConfiguration?> this execution will be executed on every Project Configuration update;
• <?m2e execute onIncremental?> this execution will be executed on every incremental build;
• <?m2e execute onConfiguration,onIncremental?> this execution will be executed on every Project Configuration update and every incremental build;
• <?m2e configurator configuratorId?> this execution will be delegated to the matching m2e configurator.

Each instruction can be placed in the <execution> node, this way it applies on this exact execution or on any execution of the same plugin with the same executionId in child pom. It can also be placed in a <plugin> node, this way it acts the same as a dedicated <pluginManagement> section which lists all goals of this plugin.

Please be aware there are currently no Quick Fixes available to automatically inject these new instructions when a “Plugin Execution Not Covered” error marker is found.