<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> <parent> <groupId>org.sonatype.oss</groupId> <artifactId>oss-parent</artifactId> <version>9</version> </parent> <groupId>com.perforce.p4maven</groupId> <artifactId>p4maven</artifactId> <version>2014.6.16-SNAPSHOT</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 Bundles for Perforce</description> <licenses> <license> <name>Perforce</name> <url>LICENSE.txt</url> <distribution>repo</distribution> <comments>BSD with Perforce Copyright</comments> </license> </licenses> <distributionManagement> <site> <id>p4maven.site</id> <name>P4Maven Site</name> <url>${site.deploy.url}</url> </site> <!-- remove this when sonatype account is activated --> <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></tag> </scm> <developers> <developer> <id>dantran</id> <name>Dan Tran</name> <email>dantran@gmail.com</email> <organization>apache.org</organization> <organizationUrl>http://www.apache.org</organizationUrl> <roles> <role>Java Developer</role> </roles> <timezone>-8</timezone> </developer> <developer> <id>perforce</id> <name>Perforce Support</name> <email>support@perforce.com</email> <organization>Perforce</organization> <organizationUrl>http://www.perfoce.com</organizationUrl> <roles> <role>Java Developer</role> </roles> <timezone>-8</timezone> </developer> </developers> <modules> <module>p4maven-provider</module> <module>p4maven-mojo</module> </modules> <properties> <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://${user.home}/.m2/p4maven/repository</releases.url> <site.deploy.url>file://${user.home}/.m2/p4maven/site</site.deploy.url> <maven.scm.test.version>1.10-SNAPSHOT</maven.scm.test.version> <metadata.package /> </properties> <dependencyManagement> <dependencies> <dependency> <groupId>com.perforce.p4maven</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>${maven.scm.test.version}</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.5</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> <defaultGoal>install</defaultGoal> <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>${metadata.package}.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> </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 at the end of release:prepare is needed so that release:perform can pick up the next snapshot --> <completionGoals>install</completionGoals> <releaseProfiles>run-its-at-release,run-tck,deploy-site-jar</releaseProfiles> </configuration> <dependencies> <!-- eat our own food by using the latest snapshot to cut own own release --> <dependency> <groupId>com.perforce.p4maven</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.p4maven</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> <profile> <!-- since perforce does not have a site, deploy site-jar to maven repo. See maven-release-plugin's config for details --> <id>deploy-site-jar</id> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-site-plugin</artifactId> <executions> <execution> <id>site-jar</id> <goals> <goal>jar</goal> </goals> </execution> </executions> </plugin> </plugins> </build> </profile> </profiles> </project>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 9585 | Joel Brown |
Populate //guest/joel_brown/cases/88163/p4maven/... from //guest/dantran/p4maven/.... |
||
//guest/dantran/p4maven/pom.xml | |||||
#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 |