Apr 9th, 2012, 08:35 AM
Problem with Grails plugin dto 0.2.4 - please help
I am using Grails 2.0.1, I installed dto 0.2.4 plugin to convert domain classes and it installed successfully. But when I clean / run-app then it is showing following error. Please help here.
"Error executing script RunApp: Cannot find plugin descriptor in plugin directory 'C:\Documents and Settings\sdhurjet\.grails\2.0.1\projects\cmlui\plu gins\dto-0.2.4'. (Use --stacktrace to see the full trace)"
Apr 9th, 2012, 08:38 AM
Hi, forgot to mention , it got created all DTOs corresponding to domain classes successfully. But when I clean/run it is giving problems.
Apr 9th, 2012, 11:02 AM
Can you try executing clean/run-app on the command line (outside of STS) to see if it is a problem with the tooling or a general Grails problem? I just created a simple project, installed dto (0.2.4) and did a clean/run-app and it was OK - however this was on a Mac (not windows).
If it works on the command line but still fails in STS, please raise a jira on our issuetracker: https://issuetracker.springsource.com/browse/STS
Apr 9th, 2012, 12:46 PM
Same result when ran clean/run-app outside of STS.
I tried by installing the plugin again inside STS though it's installed earlier(I did not uninstall), please find the logs below.
| Loading Grails 2.0.1
| Configuring classpath
Cannot find plugin descriptor for path 'C:\Documents and Settings\sdhurjet\.grails\2.0.1\projects\cmlui\plu gins\dto-0.2.4'.
| Configuring classpath.
| Environment set to development.....
| Installing zip dto-0.2.4.zip.....
| Installed plugin dto-0.2.4
| Resolving plugin JAR dependencies.....
| Plugin installed.
Apr 9th, 2012, 01:51 PM
So if it is happening outside of STS as well, sounds like a grails issue. Can you try deleting your grails cache and retrying? So delete the C:\Documents and Settings\sdhurjet\.grails folder). I'll ask the grails guys about the message.
Apr 12th, 2012, 10:47 AM
It got woked for me. I just started everything fresh including STS, then it works.
I have one doubt, while code check-in into source control, do we explicitly need to check in all the DTOs and other plugin created stuff or is there any thing like keeping the plugin information will automatically install everything when run the project.
For example I saw some of the plug-in entries in the BuildConfig.groovy file like below
// Uncomment these (or add new ones) to enable additional resources capabilities
Do we have any thing like this. please let me know asap.
Apr 12th, 2012, 12:38 PM
If you don't commit the generated DTOs I imagine you will just have to run the generate command again to reproduce them. However, you don't need to try and commit the dto plugin itself. Just having the dependency expressed (BuildConfig.groovy/application.properties) should ensure it is around when you need it (the first attempt to interact with the project should grab it). When I played with it the dto plugin reference was in the applications.properties file.
Apr 14th, 2012, 11:59 AM
It is working, by putting the DTO plugin info in BuildConfig.Groovy.