You should add a <build> … <resources> <resource> <directory>src/main</directory> <filtering>true</filtering> <includes> <include>**/*.js</include> </includes> </resource> </resources> … in your pom.xml
The bug seems to be still present in the maven-archetype-plugin v3.0.1 . For those who do not want to downgrade the maven-resource-plugin. I managed to establish a more or less ugly workaround. First you rename the archetype-resources/.gitignore to __gitignore__ then inside the archetype-metadata.xml add <requiredProperties> <requiredProperty key=”gitignore”> <defaultValue>.gitignore</defaultValue> </requiredProperty> </requiredProperties> <fileSets> <fileSet> <directory></directory> <includes> <include>__gitignore__</include> … Read more
mvn archetype:generate command is used to create a project from an existing template. There are several archetype’s defined by many developers and project groups. When you run the command, maven does following things: Downloads maven-archetype-plugin’s latest version. Lists all archetype’s that can be used to create a project from. If you defined an archetype while … Read more
To be honest, I don’t really see the point of building a list of all catalogs. It looks more “natural” to me to pick a project first and then add the catalog if required. This is why there is IMO more value in a list of archetypes. You’ll need their name anyway, even if you … Read more
There is an archetype for webapp: mvn archetype:generate -DgroupId=com.acme \ -DartifactId=my-webapp \ -Dversion=1.0-SNAPSHOT \ -DarchetypeArtifactId=maven-archetype-webapp \ -DinteractiveMode=false This will generate the following structure: $ tree my-webapp/ my-webapp/ ├── pom.xml └── src └── main ├── resources └── webapp ├── index.jsp └── WEB-INF └── web.xml Where the web.xml is a Servlet 2.3 web.xml: $ cat my-webapp/src/main/webapp/WEB-INF/web.xml <!DOCTYPE … Read more
You can use STS (spring tool suite) a new spring MVC template project creates a working application using spring 3. Or you can using Spring Roo to give a working foundation to your project.
Use build init plugin: ~$ mkdir newproj ~$ cd newproj ~/newproj$ gradle init –type java-library At the moment java-library, scala-library, groovy-library, java-application, pom and basic supported. The feature is incubating, thus it can be changed in future releases, so keep an eye on docs.
Simply create a java directory under main (i.e. src/main/java) and right-click on your project and select Maven > Update Project Configuration.
I use two archetypes. It depends on what kind of application you will create. If you want a web application, use maven-archetype-webapp, or if you want a simple application use maven-archetype-quickstart. They are useful because you will be able to expand them with no problem.
You haven’t set the encoding default property like this: <project> … <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> </properties> … </project> This approach is better than defining encoding manually for every plugin, cause all plugins having default values for encoding for example the maven-resources-plugin: encoding: The character encoding scheme to be applied when filtering resources. Type: java.lang.String Required: No User … Read more