<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.perforce</groupId> <artifactId>p4maven</artifactId> <version>2014.6.4</version> <packaging>pom</packaging> <name>p4maven parent</name> <url>http://www.perforce.com</url> <organization> <name>Perforce Software</name> <url>http://www.perforce.com</url> </organization> <description> Maven Bundle for Perforce. </description> <distributionManagement> <snapshotRepository> <id>snapshots</id> <name>Snapshots</name> <url>${snapshots.url}</url> </snapshotRepository> <repository> <id>releases</id> <name>Releases</name> <url>${releases.url}</url> </repository> </distributionManagement> <scm> <connection>scm:p4:workshop.perforce.com:1666://guest/dantran/p4maven</connection> <developerConnection>scm:p4:workshop.perforce.com:1666://guest/dantran/p4maven</developerConnection> <url>https://swarm.workshop.perforce.com/files/guest/dantran/p4maven</url> <tag>p4maven-2014.6.4</tag> </scm> <modules> <module>com.perforce.maven</module> <module>com.perforce.maven.mojo</module> </modules> <properties> <build.changelist>0</build.changelist> <build.type>DEV</build.type> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <project.build.java.target>1.5</project.build.java.target> <maven.scm.version>1.9</maven.scm.version> <releases.url>file://tmp/p4maven</releases.url> </properties> <dependencyManagement> <dependencies> <dependency> <groupId>com.perforce</groupId> <artifactId>p4maven-provider</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.apache.maven.scm</groupId> <artifactId>maven-scm-api</artifactId> <version>${maven.scm.version}</version> </dependency> <dependency> <groupId>org.apache.maven.scm</groupId> <artifactId>maven-scm-test</artifactId> <version>1.9</version> </dependency> <dependency> <groupId>org.apache.maven.scm</groupId> <artifactId>maven-scm-manager-plexus</artifactId> <version>${maven.scm.version}</version> </dependency> <dependency> <groupId>org.codehaus.plexus</groupId> <artifactId>plexus-utils</artifactId> <version>3.0.15</version> </dependency> <dependency> <groupId>com.perforce</groupId> <artifactId>p4java</artifactId> <version>2013.2.788582</version> </dependency> <dependency> <groupId>commons-io</groupId> <artifactId>commons-io</artifactId> <version>2.4</version> </dependency> <dependency> <groupId>org.sonatype.plexus</groupId> <artifactId>plexus-sec-dispatcher</artifactId> <version>1.3</version> </dependency> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.11</version> </dependency> <dependency> <groupId>org.apache.maven.release</groupId> <artifactId>maven-release-manager</artifactId> <!-- this is minimum version so that we can pickup ScmTranslator interface --> <version>2.0</version> <exclusions> <exclusion> <!-- Dan's Comcast blocks this --> <groupId>org.apache.maven.scm</groupId> <artifactId>maven-scm-provider-cvsexe</artifactId> </exclusion> </exclusions> </dependency> </dependencies> </dependencyManagement> <build> <pluginManagement> <plugins> <!-- Apache plugins in alphabetical order --> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-antrun-plugin</artifactId> <version>1.7</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-assembly-plugin</artifactId> <version>2.4</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-checkstyle-plugin</artifactId> <version>2.12.1</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-clean-plugin</artifactId> <version>2.5</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.1</version> <configuration> <encoding>${project.build.sourceEncoding}</encoding> <source>${project.build.java.target}</source> <target>${project.build.java.target}</target> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.8</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-deploy-plugin</artifactId> <version>2.8.1</version> <configuration> <updateReleaseInfo>true</updateReleaseInfo> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-enforcer-plugin</artifactId> <version>1.3.1</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-install-plugin</artifactId> <version>2.5.1</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-invoker-plugin</artifactId> <version>1.8</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <version>2.4</version> <configuration> <archive> <addMavenDescriptor>true</addMavenDescriptor> <manifest> <addDefaultImplementationEntries>true</addDefaultImplementationEntries> <mainClass>com.perforce.maven.scm.provider.Metadata</mainClass> </manifest> <manifestEntries> <Manifest-Version>1.0</Manifest-Version> <!-- Bundle headers --> <Bundle-Name>${project.name}</Bundle-Name> <Bundle-ManifestVersion>2</Bundle-ManifestVersion> <Bundle-SymbolicName>${project.groupId}.${project.artifactId}</Bundle-SymbolicName> <Bundle-Vendor>${project.organization.name}</Bundle-Vendor> <Bundle-Version>${project.version}</Bundle-Version> <!-- Build headers --> <Build-Type>${build.type}</Build-Type> <Build-Changelist>${build.changelist}</Build-Changelist> </manifestEntries> </archive> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-javadoc-plugin</artifactId> <version>2.9.1</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-plugin-plugin</artifactId> <version>3.3</version> <configuration> <skipErrorNoDescriptorsFound>true</skipErrorNoDescriptorsFound> </configuration> <executions> <!-- generate help mojo source first --> <execution> <id>help-goal</id> <phase>generate-sources</phase> <goals> <goal>helpmojo</goal> </goals> </execution> <execution> <id>mojo-descriptor</id> <phase>process-classes</phase> <goals> <goal>descriptor</goal> </goals> </execution> </executions> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-pmd-plugin</artifactId> <version>3.1</version> </plugin> <plugin> <groupId>org.codehaus.plexus</groupId> <artifactId>plexus-maven-plugin</artifactId> <version>1.3.8</version> </plugin> <!-- display source,javadoc, and site deployment during release --> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-release-plugin</artifactId> <version>2.5</version> <configuration> <preparationGoals>clean</preparationGoals> <autoVersionSubmodules>true</autoVersionSubmodules> <useReleaseProfile>false</useReleaseProfile> <goals>deploy</goals> <arguments>-Pp4maven-release -Dp4maven-release</arguments> <!-- install goal is needed so that release:perform can pick up the next p4maven snapshot --> <completionGoals>install</completionGoals> </configuration> <dependencies> <!-- eat our own dog food, but one step release is not possible --> <!-- mvn -B release:prepare -Dmaven.scm.perforce.clientspec.name=the.current.p4.client.that.host.this.source.tree --> <!-- mvn -B release:perform --> <dependency> <groupId>com.perforce</groupId> <artifactId>p4maven-provider</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.apache.maven.release</groupId> <artifactId>maven-release-manager</artifactId> <version>2.5</version> <exclusions> <exclusion> <groupId>org.apache.maven.scm</groupId> <artifactId>maven-scm-provider-cvsexe</artifactId> </exclusion> </exclusions> </dependency> </dependencies> </plugin> <!-- for testing only --> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-scm-plugin</artifactId> <version>1.9</version> <dependencies> <dependency> <groupId>com.perforce</groupId> <artifactId>p4maven-provider</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.apache.maven.scm</groupId> <artifactId>maven-scm-providers-standard</artifactId> <version>1.9</version> <type>pom</type> <exclusions> <exclusion> <groupId>org.apache.maven.scm</groupId> <artifactId>maven-scm-provider-cvsexe</artifactId> </exclusion> </exclusions> </dependency> </dependencies> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-resources-plugin</artifactId> <version>2.6</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-site-plugin</artifactId> <version>3.3</version> <dependencies> <dependency><!-- add support for ssh/scp site deploy --> <groupId>org.apache.maven.wagon</groupId> <artifactId>wagon-ssh</artifactId> <version>2.6</version> </dependency> </dependencies> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-source-plugin</artifactId> <version>2.2.1</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.17</version> <configuration> <redirectTestOutputToFile>${surefire.redirectTestOutputToFile}</redirectTestOutputToFile> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-failsafe-plugin</artifactId> <version>2.17</version> </plugin> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <versionRange>[2.0.0,)</versionRange> <goals> <goal>copy</goal> <goal>unpack</goal> <goal>copy-dependencies</goal> </goals> </pluginExecutionFilter> <action> <ignore /> </action> </pluginExecution> <pluginExecution> <pluginExecutionFilter> <groupId>org.codehaus.plexus</groupId> <artifactId>plexus-maven-plugin</artifactId> <versionRange>[1.0,)</versionRange> <goals> <goal>descriptor</goal> </goals> </pluginExecutionFilter> <action> <ignore /> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> </plugin> </plugins> </pluginManagement> </build> <profiles> <profile> <id>p4maven-release</id> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-assembly-plugin</artifactId> <dependencies> <dependency> <groupId>org.apache.apache.resources</groupId> <artifactId>apache-source-release-assembly-descriptor</artifactId> <version>1.0.3</version> </dependency> </dependencies> <executions> <execution> <id>attach-source-release-distro</id> <phase>package</phase> <goals> <goal>single</goal> </goals> <configuration> <runOnlyAtExecutionRoot>true</runOnlyAtExecutionRoot> <descriptorRefs> <descriptorRef>source-release</descriptorRef> </descriptorRefs> <tarLongFileFormat>gnu</tarLongFileFormat> </configuration> </execution> </executions> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-source-plugin</artifactId> <executions> <execution> <id>attach-sources</id> <goals> <goal>jar-no-fork</goal> </goals> </execution> </executions> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-javadoc-plugin</artifactId> <executions> <execution> <id>attach-javadocs</id> <goals> <goal>jar</goal> </goals> </execution> </executions> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-gpg-plugin</artifactId> <version>1.5</version> <executions> <execution> <id>sign-artifacts</id> <phase>verify</phase> <goals> <goal>sign</goal> </goals> </execution> </executions> </plugin> </plugins> </build> </profile> </profiles> </project>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#191 | 14824 | dantran |
* add p4mojo:remove-current-workspace * Update maven-invoker-plugin for maven 3.3.x+ support |
||
#190 | 14128 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#189 | 14127 | dantran | [maven-release-plugin] prepare release p4maven-1.0.6 | ||
#188 | 14103 | dantran | Ugrade p4java, externalize p4mojo | ||
#187 | 13667 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#186 | 13666 | dantran | [maven-release-plugin] prepare release p4maven-1.0.5 | ||
#185 | 12887 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#184 | 12886 | dantran | [maven-release-plugin] prepare release p4maven-1.0.4 | ||
#183 | 12871 | dantran |
- Description in ChangeLog command gets truncated - Downgrade invoker maven plugin to 1.9 since due to regression (MINVOKER-187) which is fixed in 3.0 ( not GAed yet). The also means we can't build p4maven with maven 3.3+ |
||
#182 | 12381 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#181 | 12380 | dantran | [maven-release-plugin] prepare release p4maven-1.0.3 | ||
#180 | 12379 | dantran | lock plexus-utils at 3.0.15 to get release:prepare to work where plexus fails to exec maven process with exit code 103 | ||
#179 | 12378 | dantran | revert back to plexus-utils-3.0.20 since release fail with latest | ||
#178 | 12376 | dantran | upgrade plexus-utils since the 3.22 has a huge revert | ||
#177 | 12263 | dantran | upgrade plugins | ||
#176 | 11618 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#175 | 11617 | dantran | [maven-release-plugin] prepare release p4maven-1.0.2 | ||
#174 | 11424 | dantran |
- P4Java logs are no under debug mode to reduce verbosity. To enable, pass in -X into mvn command - Info command now supports tag - Add p4java into export extension - Use BSD for license name - Update doc |
||
#173 | 11406 | dantran | Remote Maven site, place important user and dev doc at root level instead | ||
#172 | 11346 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#171 | 11345 | dantran | [maven-release-plugin] prepare release p4maven-1.0.1 | ||
#170 | 11344 | dantran |
target java 6 and maven 3.1+. Should have done this at 1.0.0 |
||
#169 | 11292 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#168 | 11291 | dantran | [maven-release-plugin] prepare release p4maven-1.0.0 | ||
#167 | 11290 | dantran | use user settings.xml during IT so that it would pass during release due to my local nexus | ||
#166 | 11289 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#165 | 11288 | dantran | [maven-release-plugin] prepare release p4maven-1.0.0 | ||
#164 | 11287 | dantran | more pom cleanup | ||
#163 | 11286 | dantran | update plugins, and dev doc | ||
#162 | 11285 | dantran | Enable sonatype release | ||
#161 | 11284 | dantran |
- upgrade plugins - cleanup plugin-plugin config - add option to configure p4maven-mojo as plugin extension so that all manager singletons can be shared with other plugins ( ie scm, release, build-helper, etc ) |
||
#160 | 10681 | dantran | update dep versions | ||
#159 | 10680 | dantran | set version 1.0.0-SNAPSHOT for version semantics | ||
#158 | 10679 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#157 | 10678 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.10 | ||
#156 | 10677 | dantran | rollback bad release, should not use java8 to release it | ||
#155 | 10676 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.10 | ||
#154 | 10674 | dantran | corrected copyright year and use URL for license text | ||
#153 | 10673 | dantran | format pom.xml according to tidy:pom automation | ||
#152 | 10415 | dantran | no need to validate scm during release:prepare, better to do on teh same command line as release:prepare | ||
#151 | 10414 | dantran | up the version after a good tag | ||
#150 | 10224 | dantran | [maven-release-plugin] rollback the release of p4maven-2014.0.9 | ||
#149 | 10223 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#148 | 10222 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.9 | ||
#147 | 10221 | dantran | update scm-plugin and site-plugin | ||
#146 | 10220 | dantran | [maven-release-plugin] rollback the release of p4maven-2014.0.9 | ||
#145 | 10219 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#144 | 10218 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.9 | ||
#143 | 10217 | dantran | upgrade scm-plugin, revert bad release | ||
#142 | 10145 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#141 | 10144 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.8 | ||
#140 | 10143 | dantran | add a maven goal to validate the scm element to makesure it is valid before release:prepare. | ||
#139 | 10142 | dantran | add a maven goal to validate the scm element to makesure it is valid before release:prepare. | ||
#138 | 10053 | dantran | revert bad internal release | ||
#137 | 10051 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#136 | 10050 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.9 | ||
#135 | 10049 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#134 | 10048 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.8 | ||
#133 | 10046 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#132 | 10045 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.7 | ||
#131 | 10042 | dantran | revert bad internal release | ||
#130 | 10041 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.7 | ||
#129 | 10040 | dantran | revert bad internal release | ||
#128 | 10039 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.7 | ||
#127 | 10038 | dantran | revert bad internal release | ||
#126 | 10037 | dantran | revert bad internal release | ||
#125 | 10036 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.7 | ||
#124 | 9848 | dantran | fixup email | ||
#123 | 9847 | dantran | upgrade assembly plugin | ||
#122 | 9846 | dantran |
no need to configure jacoco. Let's jenkins do this job |
||
#121 | 9784 | dantran | plexus-utils update | ||
#120 | 9767 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#119 | 9766 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.6 | ||
#118 | 9765 | dantran | pickup maven-scm-1.9.1 | ||
#117 | 9725 | dantran | minor update to test with p4jenkins | ||
#116 | 9708 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#115 | 9707 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.5 | ||
#114 | 9706 | dantran | - add apache snapshot repo for maven-scm-test-1.10-SNAPSHOT | ||
#113 | 9681 | dantran | add site report | ||
#112 | 9664 | dantran | add jacolo code coverage | ||
#111 | 9662 | dantran | fix typos + match diff command with the one at apache-maven using @now | ||
#110 | 9635 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#109 | 9634 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.4 | ||
#108 | 9633 | dantran | revert bad release | ||
#107 | 9632 | dantran |
- use groupId:artifactId:version to test release automation - Implment p4maven-settings.xml's p4Port field |
||
#106 | 9630 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#105 | 9629 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.3 | ||
#104 | 9624 | dantran | remove unused files | ||
#103 | 9623 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#102 | 9622 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.2 | ||
#101 | 9620 | dantran | remove cvsexe exclusions | ||
#100 | 9619 | dantran | move invoker config for IT profiles to parent | ||
#99 | 9597 | dantran |
- minor cleanup - doc update |
||
#98 | 9592 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#97 | 9591 | dantran | [maven-release-plugin] prepare release p4maven-2014.0.1 | ||
#96 | 9590 | dantran |
- add option to fail tag when it already exist - add P4ScmUrl parser test - cleanup |
||
#95 | 9578 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#94 | 9577 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.15 | ||
#93 | 9576 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#92 | 9574 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#91 | 9573 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.13 | ||
#90 | 9572 | dantran | Introduce run-its-at-release profile so that we can run release automation IT test at release time | ||
#89 | 9569 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#88 | 9568 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.12 | ||
#87 | 9567 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#86 | 9564 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#85 | 9563 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.10 | ||
#84 | 9561 | dantran |
- it/release now can be used to test after release:perform - only deploy site during release:perform - more dev and user doc |
||
#83 | 9552 | dantran | discover main class during build | ||
#82 | 9551 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#81 | 9550 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.9 | ||
#80 | 9548 | dantran |
- pickup P4PORT form env and system properties to support multi site using proxy - add development doc - check for error after each action |
||
#79 | 9543 | dantran | cleanup, pickup scm-test 1.10-snapshot again | ||
#78 | 9542 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#77 | 9541 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.8 | ||
#76 | 9540 | dantran | disable running IT during release since we scm-test 1.10 is not release yet | ||
#75 | 9530 | dantran | should have committed | ||
#74 | 9518 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#73 | 9517 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.7 | ||
#72 | 9516 | dantran | back to scm-test-1.9 to prep for next release | ||
#71 | 9514 | dantran |
- Remove support to pick up p4port and its credential from ENV and System properties. These setttings has no use since Maven requires user to provide the required URL which has both p4port and credential. Also user can always fall back to settings.xml to store credential - Rewrite URL parser and also support password as part of URL - TCK test now has default URL and its credential is store under settings.xml - User can also issue her how scmTckUrl system properties ( to be doc as part of maven site) |
||
#70 | 9513 | dantran | add provider doc, deploy site:jar, support external charset config | ||
#69 | 9512 | dantran | add defaultGoal, doc how to generate initial data, exclude template it | ||
#68 | 9498 | dantran |
- Setup Maven site for documetation - Implement ~/m2/p4maven-settings.xml to store external config overridable by system properties. All global settings now can be retrieved va P4Utils |
||
#67 | 9491 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#66 | 9490 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.6 | ||
#65 | 9489 | dantran | back to scm-test 1.9 to prep for another release | ||
#64 | 9486 | dantran | Simplify update command and rely on AbstractUpdateCommand to gather the ChangeSet | ||
#63 | 9479 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#62 | 9478 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.5 | ||
#61 | 9477 | dantran | add logger, prepare the next release | ||
#60 | 9471 | dantran |
- cleanup diff command - simplify branch command and full compliant with maven-scm-test - add checkout with branch - add repo's path as client manager lookup key in addition to p4port and rootdir so that we can handle mutiple clients on the same rootdir |
||
#59 | 9468 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#58 | 9467 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.4 | ||
#57 | 9466 | dantran | additional client discovery work to prevent false positive | ||
#56 | 9455 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#55 | 9454 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.3 | ||
#54 | 9453 | dantran | go back to scm-test 1.9 for another release cut | ||
#53 | 9446 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#52 | 9445 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.2 | ||
#51 | 9443 | dantran | use maven-scm-test 1.9 so that we can cut test a release | ||
#50 | 9241 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#49 | 9240 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#48 | 9239 | dantran | back to 2014.6.1-SNAPSHOT, add missing file | ||
#47 | 9238 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#46 | 9237 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#45 | 9236 | dantran | back to 2014.6.1-SNAPSHOT | ||
#44 | 9235 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#43 | 9225 | dantran | have release:prepare to build the next snaphot to be pickup by relelase:perform | ||
#42 | 9224 | dantran | add IT validation, simplify release/scm exclusion and doc why I exclude cvsexe scm provider | ||
#41 | 9223 | dantran | back to 2014.6.1-SNAPSHOT, doc the release steps | ||
#40 | 9222 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#39 | 9221 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.4 | ||
#38 | 9220 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#37 | 9219 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.3 | ||
#36 | 9218 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#35 | 9217 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.2 | ||
#34 | 9216 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#33 | 9215 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#32 | 9214 | dantran | back to 2014.6.1-SNAPSHOT to try another trial release:prepare. | ||
#31 | 9213 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#30 | 9212 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.5 | ||
#29 | 9211 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#28 | 9210 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.4 | ||
#27 | 9209 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#26 | 9208 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.3 | ||
#25 | 9207 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#24 | 9206 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.2 | ||
#23 | 9205 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#22 | 9204 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#21 | 9203 | dantran |
back to 2014.6.1-SNAPSHOT to try another trial release:prepare. Default releases.url to a local disk for testing purpose |
||
#20 | 9202 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#19 | 9201 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#18 | 9200 | dantran | back to 2014.6.1-SNAPSHOT to try another trial release:prepare | ||
#17 | 9199 | dantran | Implement ScmTranlator for P4 provider so that release plugin can correctly push the tag/label id into <SCM> element | ||
#16 | 9198 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#15 | 9197 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#14 | 9196 | dantran | artifact signing at release time | ||
#13 | 9195 | dantran |
dont use random tag during test, it is hard to remove after many get generated. unit test credential move to ~/.p4maven/test.properties |
||
#12 | 9194 | dantran | rework in p4maven-release profile to include source distribution | ||
#11 | 9193 | dantran | add IT | ||
#10 | 9191 | dantran |
jobs,shelve, and unshelve should run as aggregate, there is no need to tranverse. Ensure extracting credential from settings.xml working |
||
#9 | 9190 | dantran | Migrate to java annotation, add loading credential from settings.xml if not given | ||
#8 | 9188 | dantran |
setup release plugin to pickup 2014.6.1. This mean we need to manually deploy 2014.6.1 first before official release plugin can work |
||
#7 | 9187 | dantran | version is now 2015.6.1-SNAPSHOT | ||
#6 | 9185 | dantran |
more comment on tagging with latesgt changelist. Add <SCM> to parent pom |
||
#5 | 9183 | dantran | refactor P4TagCommand for code readability and introduce tagging using changelist when the ScmFileSet input is empty | ||
#4 | 9178 | dantran | One more round of pom cleanup with the introduction of dependencyManagement at parent pom | ||
#3 | 9171 | dantran |
- Lock down all plugin version at top level parent for reproduciblity - Promote all common plugin configuration to the top level pom - Remove all assembly profile, to be reimplement in its own sub module call perforce-p4maven |
||
#2 | 9168 | dantran | Artifact ids renamed to be more conventional like Maven | ||
#1 | 9167 | dantran |
Populate //guest/dantran/p4maven/... from //guest/perforce_software/p4maven/main/.... |
||
//guest/perforce_software/p4maven/main/pom.xml | |||||
#1 | 8496 | Matt Attaway | Move P4Ant and P4Maven into their proper homes | ||
//public/perforce/p4maven/main/pom.xml | |||||
#1 | 8270 | Matt Attaway | Initial add of P4Maven source code |