Re: problem using archetype create-from-project to process files under resources folders.
check the sources of the generic nbm archetype at codehaus. http://svn.codehaus.org/mojo/trunk/mojo/mojo-archetypes/nbm-archetype/ Milos On Thu, Oct 1, 2009 at 5:03 PM, Djohannot david.johan...@heig-vd.ch wrote: Hi all, I have exactly the same problem. I use the Netbeans platform and the layer.xml, Bundle.properties, etc are in resources folder, and the archetype:generate-from-project keep the original folder hierarchy. dou you have found a way to tell Maven to modif the resources folders too? regards, David J. Trent Rosenbaum-2 wrote: Hi there, I am having a problem with the 'main/resources' and the 'test/resources' folders when trying to generate an archetype from an example project. Both folders are preserving the original folder structures from the project used to generate the archetype. The 'main/java' and the 'test/java' are modified to allow them to be placed into a new package structure when the archetype is used for future projects. Are the folders 'main/resources' and 'test/resources' meant to work in this way? I would expect the 'resources' folders within the archetype to generate the new files in the same manner as the java folders. I have a situation where junit test classes are locating Spring configuration files in the same package. I have the test class under the 'test/java' folder and the configuration files under 'test/resources'. When I run the 'maven-archetype-plugin' over the example project, (a project that builds and tests as expected) I get the java classes modified to except new project values, but the configuration files under resources folders are left under the old package/folder structure. After generation of the new project the build fails because the tests cannot locate the appropriate configuration files. Is it expected that I should modify the generated archetype files by hand to place the configuration files in the correct location? I have been using archetypes of a while, but have never noticed this before because I always placed my configuration files at the route of 'main/resources' and 'test/resources'. What are the plans for the archetype plugin going forward? I get a sense that things on the archetype front have gone quiet? Are there any other options and what is everyone else doing? Any feedback would be a great help. Many thanks Trent -- View this message in context: http://www.nabble.com/problem-using-archetype-create-from-project-to-process-files-under--resources-folders.-tp24772317p25696921.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: problem using archetype create-from-project to process files under resources folders.
Hi all, I have exactly the same problem. I use the Netbeans platform and the layer.xml, Bundle.properties, etc are in resources folder, and the archetype:generate-from-project keep the original folder hierarchy. dou you have found a way to tell Maven to modif the resources folders too? regards, David J. Trent Rosenbaum-2 wrote: Hi there, I am having a problem with the 'main/resources' and the 'test/resources' folders when trying to generate an archetype from an example project. Both folders are preserving the original folder structures from the project used to generate the archetype. The 'main/java' and the 'test/java' are modified to allow them to be placed into a new package structure when the archetype is used for future projects. Are the folders 'main/resources' and 'test/resources' meant to work in this way? I would expect the 'resources' folders within the archetype to generate the new files in the same manner as the java folders. I have a situation where junit test classes are locating Spring configuration files in the same package. I have the test class under the 'test/java' folder and the configuration files under 'test/resources'. When I run the 'maven-archetype-plugin' over the example project, (a project that builds and tests as expected) I get the java classes modified to except new project values, but the configuration files under resources folders are left under the old package/folder structure. After generation of the new project the build fails because the tests cannot locate the appropriate configuration files. Is it expected that I should modify the generated archetype files by hand to place the configuration files in the correct location? I have been using archetypes of a while, but have never noticed this before because I always placed my configuration files at the route of 'main/resources' and 'test/resources'. What are the plans for the archetype plugin going forward? I get a sense that things on the archetype front have gone quiet? Are there any other options and what is everyone else doing? Any feedback would be a great help. Many thanks Trent -- View this message in context: http://www.nabble.com/problem-using-archetype-create-from-project-to-process-files-under--resources-folders.-tp24772317p25696921.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
problem using archetype create-from-project to process files under resources folders.
Hi there, I am having a problem with the 'main/resources' and the 'test/resources' folders when trying to generate an archetype from an example project. Both folders are preserving the original folder structures from the project used to generate the archetype. The 'main/java' and the 'test/java' are modified to allow them to be placed into a new package structure when the archetype is used for future projects. Are the folders 'main/resources' and 'test/resources' meant to work in this way? I would expect the 'resources' folders within the archetype to generate the new files in the same manner as the java folders. I have a situation where junit test classes are locating Spring configuration files in the same package. I have the test class under the 'test/java' folder and the configuration files under 'test/resources'. When I run the 'maven-archetype-plugin' over the example project, (a project that builds and tests as expected) I get the java classes modified to except new project values, but the configuration files under resources folders are left under the old package/folder structure. After generation of the new project the build fails because the tests cannot locate the appropriate configuration files. Is it expected that I should modify the generated archetype files by hand to place the configuration files in the correct location? I have been using archetypes of a while, but have never noticed this before because I always placed my configuration files at the route of 'main/resources' and 'test/resources'. What are the plans for the archetype plugin going forward? I get a sense that things on the archetype front have gone quiet? Are there any other options and what is everyone else doing? Any feedback would be a great help. Many thanks Trent
