- 27 11月, 2015 1 次提交
-
-
由 Thomas Eizinger 提交于
-
- 14 5月, 2015 1 次提交
-
-
由 Brendan Forster 提交于
-
- 03 4月, 2015 1 次提交
-
-
由 Tushar Kapila 提交于
Else sub projects (main dir has sub dirs with own pom files - sub modules) targets are not ignored.
-
- 30 3月, 2015 1 次提交
-
-
由 Jean-Christophe GAY 提交于
This extension is an alternative scheduler to build multi-module Maven projects. It stores and updates timing for every build run in .mvn/timing.properties. http://takari.io/book/30-team-maven.html#takari-smart-builder
-
- 03 3月, 2015 1 次提交
-
-
由 Mike Duigou 提交于
The popular build plugin org.codehaus.mojo:buildnumber-maven-plugin stores the build number it managers in a file named buildNumber.properties.
-
- 18 2月, 2015 1 次提交
-
-
由 Darren Yin 提交于
-
- 31 3月, 2014 1 次提交
-
-
由 Namik Nuhanovic 提交于
'mvn versions:use-latest-versions' generates 'pom.xml.versionsBackup' file, because '-DgenerateBackupPoms=true' is default; see http://mojo.codehaus.org/versions-maven-plugin/use-latest-versions-mojo.html#generateBackupPoms
-
- 16 11月, 2013 1 次提交
-
-
由 Oliver Schrenk 提交于
Maven Release Plugin provides a standard mechanism to release project artifacts. During the various phases of the execution the plugin create various files, especially if you do a dry run that allows you to see the changes that the plugin will perform on your pom files mvn release:prepare -D dryRun=true It will create - `release.properties` - copy of the properties to be used - `pom.xml.releaseBackup` - the pom.xml prior to any changes - `pom.xml.tag` - the pom.xml as it will look when tagged - `pom.xml.next` - the pom.xml as it will look for the next iteration
-
- 15 3月, 2013 1 次提交
-
-
由 zafarella-Linux 提交于
-
- 09 11月, 2010 1 次提交
-
-
由 Martin Desrosiers 提交于
-