Re: The resource is a duplicate of .link_to_grails_plugins grails-app i18n messages.properties and was not copied to the output folder

[zfleet]

Hello, 

if you want to remove the duplicate file warning in your project, 

you have to go to your project properties (right click on your project, properties), then go to "java build path" and on the "source" tab.

Next you have to remove i18n folder from  your plugins source folder.

The project need to be rebuild, and warnings will vanish.

If you want a better grails IDE integration you can try intelliJ IDEA.

Le vendredi 8 juin 2012 15:36:03 UTC+2, Paul Lin a écrit :

Please forgive my my ignorance but I've been using Grails for some time now and I still feel like a newbie all the time.  I see this warning message in the "Markers" tab a lot but I think Grails thinks the files are duplicates only by the file name and not by the contents of the file, which makes this warning message not only useless but also misleading.  

Actually the fact that there are multiple messages.properties files with the same path should be a given anyway because every plugin should probably have those (along with all their translations if any).  So what should we expect Grails to do when that happens?  The ideal way would potentially be to have a big messages.properties file that can combine all these other messasges.properties, as an outcome of the build.  But maybe that is too much to ask from Grails.  Should I file a JIRA for this or would I be wasting my time?

In any case, if there are no good solutions to do this "right", does anyone know how to remove this warning permanently?  It gets annoying seeing a warning sign on my project all the time.  I would try to fix this by going into Configure Build Path and remove these i18n folders from the source but they almost always come back after some refresh (e.g. Grails Dependencies) or project clean.

[Paul Lin]

Thanks zfleet.  Not sure why I didn't get a notification when you replied.  I'm currently trying out IDEA.  

Just curious, on the Grails main site at grails.org, it shows that SpringSource / VMWare is "behind" grails.  So why is it that someone else has a better IDE than they do?