-
Type:
Bug
-
Status: Open
-
Resolution: Unresolved
-
Affects Version/s: Master
-
Fix Version/s: None
-
Component/s: Dev Tools > Gradle Plugins, Dev Tools > Plugins SDK, Testing > Plugins
-
Labels:None
Step to reproduce:
- Prepare a build-able portal source
- Make sure to remove com.liferay.exportimport.test.util.jar from both osgi/test and osgi/modules
- Go under export-import/export-import-test-util, and run gradlew deploy
- Notice in osgi/test, there is com.liferay.exportimport.test.util.jar generated, but not in osgi/modules
- Go under export-import/export-import-test, and run gradlew testIntegration --tests com.liferay.exportimport.test.DummyFolderExportImportTest
- Notice it will fail because unresolved module of export-import-test-util, and console will report export-import-test-util is installed after few seconds
- run gradlew testIntegration --tests com.liferay.exportimport.test.DummyFolderExportImportTest again
- Notice it will pass all tests
- In the class file of DummyFolderPortletDataHandler, replace the last statement of return null; with throw new IllegalArgumentException(), in method of doImportData()
- Repeat step 3
- Notice in osgi/test, a new jar of com.liferay.exportimport.test.util.jar is generated, but the one in osgi/modules is still the old one.
- Repeat step 4
#Notice all tests still pass
The build.gradle file in export-import/export-import-test-util says, the jar will be deployed to osgi/test
Ideally, one of these should happen:
- Portal picks up test-util jar from osgi/test
- The gradlew deploy should also make a copy to osgi/modules
- gradlew IntegrationTest should copy test-util jar from osgi/test to osgi/modules everytime if there is a diffrence.