<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>com.perforce.p4maven</groupId> <artifactId>p4maven</artifactId> <version>2014.6.16-SNAPSHOT</version> </parent> <artifactId>p4maven-provider</artifactId> <name>Perforce Maven SCM Provider</name> <description>Maven SCM Provider implementation for Perforce using P4Java.</description> <dependencies> <dependency> <groupId>org.apache.maven.scm</groupId> <artifactId>maven-scm-api</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>com.perforce</groupId> <artifactId>p4java</artifactId> </dependency> <dependency> <groupId>commons-io</groupId> <artifactId>commons-io</artifactId> </dependency> <dependency> <groupId>org.apache.maven.release</groupId> <artifactId>maven-release-manager</artifactId> <scope>provided</scope> <optional>true</optional> </dependency> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>org.sonatype.plexus</groupId> <artifactId>plexus-sec-dispatcher</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>org.apache.maven.scm</groupId> <artifactId>maven-scm-test</artifactId> <scope>test</scope> </dependency> </dependencies> <properties> <skipTests>true</skipTests> <metadata.package>com.perforce.maven.scm.provider</metadata.package> <!-- these are passed into IT --> <!-- should in the profile, but there are 2 profiles, so place it here --> <scmItDepotUrl>scm:p4:localhost:1666://scmtck</scmItDepotUrl> <scmItUrl>${scmItDepotUrl}/p4maven-tck</scmItUrl> <maven.scm.plugin.it.version>1.9</maven.scm.plugin.it.version> </properties> <build> <pluginManagement> <plugins> <plugin> <!-- this shared by 2 profiles --> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-invoker-plugin</artifactId> <configuration> <debug>false</debug> <postBuildHookScript>verify</postBuildHookScript> <!-- use current local repo for speed --> <!-- localRepositoryPath>${project.build.directory}/local-repo</localRepositoryPath --> <settingsFile>${user.home}/.m2/settings.xml</settingsFile> <cloneProjectsTo>${project.build.directory}/it</cloneProjectsTo> </configuration> <executions> <execution> <id>integration-test</id> <goals> <goal>install</goal> <goal>run</goal> </goals> </execution> </executions> </plugin> </plugins> </pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <configuration> <skipTests>${skipTests}</skipTests> </configuration> </plugin> <plugin> <groupId>org.codehaus.plexus</groupId> <artifactId>plexus-maven-plugin</artifactId> <executions> <execution> <id>create-component-descriptor</id> <phase>generate-resources</phase> <goals> <goal>descriptor</goal> </goals> </execution> </executions> </plugin> <plugin> <groupId>org.codehaus.modello</groupId> <artifactId>modello-maven-plugin</artifactId> <version>1.6</version> <executions> <execution> <goals> <goal>java</goal> <goal>xpp3-reader</goal> <goal>xpp3-writer</goal> <goal>xsd</goal> </goals> </execution> </executions> <configuration> <version>1.0.0</version> <useJava5>true</useJava5> <models> <model>src/main/mdo/p4maven-settings.mdo</model> </models> </configuration> </plugin> </plugins> </build> <profiles> <profile> <id>run-tck</id> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <configuration> <skipTests>false</skipTests> </configuration> </plugin> </plugins> </build> </profile> <profile> <id>run-its</id> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-invoker-plugin</artifactId> <configuration> <pomExcludes> <!-- only use this to populate test data for brand new test depot --> <pomExclude>initial-data/pom.xml</pomExclude> <pomExclude>release/pom.xml</pomExclude> </pomExcludes> </configuration> </plugin> </plugins> </build> </profile> <profile> <id>run-its-at-release</id> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-invoker-plugin</artifactId> <configuration> <pomExcludes> <!-- only use this to populate test data for brand new test depot --> <pomExclude>initial-data/pom.xml</pomExclude> </pomExcludes> </configuration> </plugin> </plugins> </build> </profile> </profiles> </project>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 9586 | Joel Brown | test submit for case | ||
//guest/joel_brown/cases/88163/p4maven/p4maven-provider/pom.xml | |||||
#1 | 9585 | Joel Brown |
Populate //guest/joel_brown/cases/88163/p4maven/... from //guest/dantran/p4maven/.... |
||
//guest/dantran/p4maven/p4maven-provider/pom.xml | |||||
#24 | 9578 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#23 | 9577 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.15 | ||
#22 | 9576 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#21 | 9574 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#20 | 9573 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.13 | ||
#19 | 9572 | dantran | Introduce run-its-at-release profile so that we can run release automation IT test at release time | ||
#18 | 9569 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#17 | 9568 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.12 | ||
#16 | 9567 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#15 | 9566 | dantran |
- pickup charset from external config - Use repo's path during branch, if is not value use the basedir. This means it assumes maven user likely to name artifactId and module the same - Less verbose on server info |
||
#14 | 9564 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#13 | 9563 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.10 | ||
#12 | 9552 | dantran | discover main class during build | ||
#11 | 9551 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#10 | 9550 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.9 | ||
#9 | 9542 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#8 | 9541 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.8 | ||
#7 | 9540 | dantran | disable running IT during release since we scm-test 1.10 is not release yet | ||
#6 | 9539 | dantran |
add release automation IT. make test branching random name |
||
#5 | 9538 | dantran |
rename it/template to it/initial-data. It is much more meaningful |
||
#4 | 9531 | dantran | run tck and IT tests during at release time | ||
#3 | 9524 | dantran | switch default tck's depot from //depot to //scmtck to be very specific since user may have a //depot in production | ||
#2 | 9521 | dantran | folders rename to match with its artfiactId | ||
#1 | 9519 | dantran | folder rename to match with its artifactId | ||
//guest/dantran/p4maven/com.perforce.maven/pom.xml | |||||
#73 | 9518 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#72 | 9517 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.7 | ||
#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 | 9510 | dantran | add missing pom for release template for IT | ||
#67 | 9509 | dantran | adjust TCK's new data location which under src/it/template | ||
#66 | 9502 | dantran | prepare for template IT which will be used to create intial project for TCK and IT testing | ||
#65 | 9500 | dantran | switch IT to use local P4D | ||
#64 | 9499 | dantran |
Discover latest revision expected by scm:update goal Check for error under IFileSpec during client discovery |
||
#63 | 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 |
||
#62 | 9491 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#61 | 9490 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.6 | ||
#60 | 9479 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#59 | 9478 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.5 | ||
#58 | 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 |
||
#57 | 9468 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#56 | 9467 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.4 | ||
#55 | 9466 | dantran | additional client discovery work to prevent false positive | ||
#54 | 9455 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#53 | 9454 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.3 | ||
#52 | 9452 | dantran |
current client is now correctly discoverable. Use absolute path at ChangeLog command |
||
#51 | 9451 | dantran | Discover current client | ||
#50 | 9446 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#49 | 9445 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.2 | ||
#48 | 9423 | dantran | get all test to use the same setup, handle checkout with tag, need to revisit how we handle ScmVersion | ||
#47 | 9266 | dantran |
fixed up P4EditCommand to comply ScmFileSpec where the internal filelist is always relative to its basedir. When Creating P4 FileSpec, must convert the relative path to absolute path otherwise p4 would use it currently directory to calculate the path. Will need to apply the same principal to all commands |
||
#46 | 9259 | dantran |
hookup with maven-scm-test. Pickup user/password from system properties |
||
#45 | 9241 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#44 | 9240 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#43 | 9239 | dantran | back to 2014.6.1-SNAPSHOT, add missing file | ||
#42 | 9238 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#41 | 9237 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#40 | 9236 | dantran | back to 2014.6.1-SNAPSHOT | ||
#39 | 9235 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#38 | 9224 | dantran | add IT validation, simplify release/scm exclusion and doc why I exclude cvsexe scm provider | ||
#37 | 9223 | dantran | back to 2014.6.1-SNAPSHOT, doc the release steps | ||
#36 | 9222 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#35 | 9221 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.4 | ||
#34 | 9220 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#33 | 9219 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.3 | ||
#32 | 9218 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#31 | 9217 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.2 | ||
#30 | 9216 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#29 | 9215 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#28 | 9214 | dantran | back to 2014.6.1-SNAPSHOT to try another trial release:prepare. | ||
#27 | 9213 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#26 | 9212 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.5 | ||
#25 | 9211 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#24 | 9210 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.4 | ||
#23 | 9209 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#22 | 9208 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.3 | ||
#21 | 9207 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#20 | 9206 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.2 | ||
#19 | 9205 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#18 | 9204 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#17 | 9203 | dantran |
back to 2014.6.1-SNAPSHOT to try another trial release:prepare. Default releases.url to a local disk for testing purpose |
||
#16 | 9202 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#15 | 9201 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#14 | 9200 | dantran | back to 2014.6.1-SNAPSHOT to try another trial release:prepare | ||
#13 | 9199 | dantran | Implement ScmTranlator for P4 provider so that release plugin can correctly push the tag/label id into <SCM> element | ||
#12 | 9198 | dantran | [maven-release-plugin] prepare for next development iteration | ||
#11 | 9197 | dantran | [maven-release-plugin] prepare release p4maven-2014.6.1 | ||
#10 | 9192 | dantran | add IT | ||
#9 | 9190 | dantran | Migrate to java annotation, add loading credential from settings.xml if not given | ||
#8 | 9187 | dantran | version is now 2015.6.1-SNAPSHOT | ||
#7 | 9186 | dantran | Add TagCommand unit test and setup integration test | ||
#6 | 9183 | dantran | refactor P4TagCommand for code readability and introduce tagging using changelist when the ScmFileSet input is empty | ||
#5 | 9178 | dantran | One more round of pom cleanup with the introduction of dependencyManagement at parent pom | ||
#4 | 9177 | dantran |
Compatible with maven-scm-api-1.5+. The current 1.4 is too old |
||
#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/com.perforce.maven/pom.xml | |||||
#2 | 9014 | Matt Attaway |
Add SSL support to P4Maven (committed on behalf of Dan Tran) USer visible change |
||
#1 | 8496 | Matt Attaway | Move P4Ant and P4Maven into their proper homes | ||
//public/perforce/p4maven/main/com.perforce.maven/pom.xml | |||||
#1 | 8270 | Matt Attaway | Initial add of P4Maven source code |