+1 to make the system aware of Maven/Gradle re/sources structure. I have felt the need myself many times. Creating first resource (until the src/main/resources or src/test/resources directories exist) is painful and errorprone. MoveToResources action would help with that.
When converting Ant projects to Maven, many resources are at wrong location - again MoveToResources would be cheap way to fix that. Clearly the current UI has been designed for Ant based projects without any source/resource separation. The best way to improve the UX would be to fix the wizards to place their files at the right location to begin with. That may however be very long term effort, so meanwhile MoveToResources would be a cheap way to simplify the operation for power users. -jt so 2. 1. 2021 v 0:45 odesÃlatel Ernie Rael <[email protected]> napsal: > The recent thread in netbeans-users > > Netbeans/Maven Resource Bundle problem (classpath?) > > http://mail-archives.apache.org/mod_mbox/netbeans-users/202101.mbox/%3C30f4e17a-2fd2-df88-d08d-a1c0ddb5f8f2%40weldingengineering.com%3E > > suggests that the internationalization wizard doesn't know about maven > project directory layout. > > Got me wondering if there should be an action on a file in a maven project > > MoveToResources > > for files under the source tree. Working with multiple selection best. > > This could be useful for situations where old/legacy parts of the system > don't understand maven projects. Also useful when converting an ant > project to maven. > > -ernie > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
