- Windows: fsutil file createnew 4g.win 4294967296
- Linux: fallocate -l 4G ./4g.img
'분류 전체보기'에 해당되는 글 71건
- 2023.09.12 Create a big file in a second
- 2023.05.31 DBeaver checkstyle
- 2023.05.23 DBeaver a new Database Connector Development Process
- 2022.09.21 Windows 10, 11 탐색기 오른쪽 마우스 클릭 (Context) 메뉴 예전 방식으로 보기
- 2020.10.08 mkcscope.sh
- 2020.09.09 Get the path of executed script file resides
- 2020.05.13 log4j with JUnit at Eclipse
- 2020.03.25 Unable to input "@" at HP UX
- 2019.11.11 현재 수행중인 메서드 이름 가져오기
- 2019.06.24 Add Jenkins build number at About dialog
java -jar checkstyle-10.8.1-all.jar -c dbeaver-checkstyle-config.xml ${your_java_code_file_list}
Starting audit...
Audit done.
- Create a new ticket (https://github.com/dbeaver/dbeaver/wiki/Contribute-your-code)
- Create a ticket on our issue tracker before creating a PR: https://github.com/dbeaver/dbeaver/issues
- Create a fork of the dbeaver/dbeaver repository, create a new branch, commit your changes, and then create a pull request in the upstream repository.
- Set up your own development environment
- https://dbeaver.com/docs/wiki/Develop-in-Eclipse/#running-and-debugging-in-eclipse
- Refer to DBeaver wiki for development: https://dbeaver.com/docs/wiki/
- Implement your own DB plugin
- org.jkiss.dbeaver.ext.yourDBPlugin, org.jkiss.dbeaver.ext.yourDBPlugin.ui
- Don't forget to put license header into source code file: https://github.com/ALTIBASE/dbeaver/blob/devel/docs/license_header.txt
- Build package with your own DB plugin: https://github.com/orgs/dbeaver/discussions/13200
- dbeaver/plugins/pom.xml (22.1 version)
- <modules>... <module>org.jkiss.dbeaver.ext.yourDBPlugin</module>...</modules>
- <profiles>... <module>org.jkiss.dbeaver.ext.yourDBPlugin.ui</module>... </profiles>
- dbeaver/features/org.jkiss.dbeaver.db.feature/features.xml
- <plugin id="org.jkiss.dbeaver.ext.yourDBPlugin"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
- <plugin id="org.jkiss.dbeaver.ext.yourDBPlugin"
- (23.1) dbeaver/features/org.jkiss.dbeaver.db.ui.feature/features.xml
- <plugin id="org.jkiss.dbeaver.ext.yourDBPlugin.ui"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
- <plugin id="org.jkiss.dbeaver.ext.yourDBPlugin.ui"
- mvn clean package at dbeaver
- Package directory: dbeaver\product\community\target\products\
org.jkiss.dbeaver.core.product\win32\win32\x86_64\dbeaver - Confirm your own plugin comes with the package in the plugins directory.
- Execute a new dbeaver.exe to ensure everything works fine.
- Package directory: dbeaver\product\community\target\products\
- dbeaver/plugins/pom.xml (22.1 version)
- org.jkiss.dbeaver.ext.yourDBPlugin, org.jkiss.dbeaver.ext.yourDBPlugin.ui
- Creating your own PR
변경 전 | 변경 후 |
'더 많은 옵션 표시 Shift + F10' 없애기: 예전처럼 컨텍스트 메뉴를 다 보기 위해 되돌리기
1. 시작버튼의 오른쪽 마우스 클릭해서 Windows 터미널 (관리자)
2. 아래 명령을 윈도우 터미널에 붙여넣고 엔터
reg.exe add "HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32" /f /ve
3. 윈도우 탐색기를 재시작하거나 리부팅
위 작업을 Windows 10, 11 기본 모양으로 다시 되돌리기
1. 시작버튼의 오른쪽 마우스 클릭해서 Windows 터미널 (관리자)
2. 아래 명령을 윈도우 터미널에 붙여넣고 엔터
reg.exe delete "HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}" /f
3. 윈도우 탐색기를 재시작하거나 리부팅
#!/bin/bash
cd ${DEV_HOME}
ctags -R .
rm -rf ${DEV_HOME}/cscope.files
find `pwd` -name "*.h" -o -name "*.c" -o -name "*.cpp" -o -name "*.java" -o -name "*.msg" > ${ALTIDEV_HOME}/cscope.files
cscope -b -i cscope.files
Linux
#!/bin/sh
BASEDIR=$(dirname "$0")
echo "$BASEDIR"
Windows
%~dp0: the full path of the directory in which the batch script resides.
You can specify the location of myLib.jar regardless of where the batch file is executed.
set JAVA_CMD="%JAVA_HOME%\bin\java" -XX:MaxPermSize=512m -Xms1g -Xmx4g -Duser.language=en
%JAVA_CMD% -jar %~dp0\myLib.jar %*
1. Put the following log4j.properties file at root directory at the Eclipse JUnit project
####################################
# Categories & Levels
####################################
#For develop
log4j.rootCategory=DEBUG, ConApp, FileApp
####################################
# Appender
####################################
# ConApp is set to be a ConsoleAppender
log4j.appender.ConApp=org.apache.log4j.ConsoleAppender
log4j.appender.ConApp.layout=org.apache.log4j.PatternLayout
log4j.appender.ConApp.layout.ConversionPattern=%d [%t] %-5p %l - %m%n
# FileApp is to create log-file using FileAppender
log4j.appender.FileApp=org.apache.log4j.FileAppender
log4j.appender.FileApp.File=./test.log
log4j.appender.FileApp.ImmediateFlush=true
log4j.appender.FileApp.Append=false
log4j.appender.FileApp.layout=org.apache.log4j.PatternLayout
log4j.appender.FileApp.layout.ConversionPattern=%d [%t] %-5p %l - %m%n
2. Add static initializer to JUnit test class
private static Logger gLogger = Logger.getLogger(TestClass.class);
static
{
PropertyConfigurator.configure("log4j.properties");
}
Run a JUnit test, then log4j log will be shown at console and file.
https://www.unix.com/hp-ux/256104-after-using-line-breaks-particular-user-shell.html
// set to default values
stty sane
// change terminal control characters
stty erase "^h" intr "^c" kill "^u" susp "^z" eof "^d"
// see all values
stty -a
protected String getCurrentMethodName()
{
return new Exception().getStackTrace()[1].getMethodName();
}
cat plugin_directory/plugin.properties
aboutText=blah blah\n\n\
Build Number:
cat build.xml
...
<target name="before-pde-build">
<echo file="${buildDirectory}/plugins/plug_in_name/plugin.properties" message=${env.BUILD_NUMBER}" append="true"/>
</target>