You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running nGrinder test in the intellij, the dependency to the ngrinder-groovy should be compile scope. It's because intellij excludes the dependencies in the classpath when running JUnit test by default. However puttting ngrinder-groovy dependency to the compile scope, test under ngrinder context might be failed. There we need to put the maven profile to activate the dependency only in the intelliJ context . I've already provided the description in the following url, http://www.cubrid.org/wiki_ngrinder/entry/import-groovy-maven-project-in-intellij
However it might be better to provide these profiles in the default maven template by default.
<profiles>
<!-- Following dependency is mandatory -->
<profile>
<id>default</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<dependencies>
<dependency>
<groupId>org.ngrinder</groupId>
<artifactId>ngrinder-groovy</artifactId>
<version>${ngrinder.version}</version>
<scope>provided</scope>
</dependency>
</dependencies>
</profile>
<!-- Use intellij profile when running tests in the intellij -->
<profile>
<id>intellij</id>
<dependencies>
<dependency>
<groupId>org.ngrinder</groupId>
<artifactId>ngrinder-groovy</artifactId>
<version>${ngrinder.version}</version>
<scope>compile</scope>
</dependency>
</dependencies>
</profile>
</profiles>
The text was updated successfully, but these errors were encountered:
- FileContents를 생성할 때 사용하는 동작은 유지하지만, 객체를 사용할 때 최상위 디렉토리는 변경이 가능하도록 수정
- FileDistributionHandler에서 특정 폴더 하위로 파일들을 전송할 수 있도록 수정
- FileStoreSupport에선 clearCacheMessage를 무시하여 새로운 파일이 전송되어도 기존파일은 유지.
When running nGrinder test in the intellij, the dependency to the ngrinder-groovy should be compile scope. It's because intellij excludes the dependencies in the classpath when running JUnit test by default. However puttting ngrinder-groovy dependency to the compile scope, test under ngrinder context might be failed. There we need to put the maven profile to activate the dependency only in the intelliJ context . I've already provided the description in the following url,
http://www.cubrid.org/wiki_ngrinder/entry/import-groovy-maven-project-in-intellij
However it might be better to provide these profiles in the default maven template by default.
The text was updated successfully, but these errors were encountered: