[
https://issues.apache.org/jira/browse/UIMA-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641921#comment-16641921
]
Marshall Schor commented on UIMA-5876:
--------------------------------------
I'm looking for a way forward to have us able to run releases with the 2
patched plugins, until these patches are accepted / released by their PMCs.
Some thoughts:
1) create 2 patched JAR artifacts, and include them in the uima-wide parent-pom
build, so that when this is deployed (SNAPSHOT or release), the download into
users local .m2 includes these Jars
2) make a dependency with a scope "system" and specifying a systemPath to the
jar in the local .m2, using ${settings.localRepository} as the starting root,
followed by /org/apache/uima/parent-pom/${version}/jar-name.jar,
* jar-name = checksum-maven-plugin-1.8-uima-patch.jar
* jar-name = maven-gpg-plugin-1.6-uima-patch.jar
and hope this dependency "overrides" the main artifact jar.
3) for reference, we could put the patches into some subdirectories of the
parent-pom, so they would be recorded in svn, and the jars could be rebuilt (by
checking out the source - tag and applying the patch).
This seems like a big hack, so if anyone knows an easier better way to proceed,
please add your idea :)
> update uima-wide parent-pom
> ---------------------------
>
> Key: UIMA-5876
> URL: https://issues.apache.org/jira/browse/UIMA-5876
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Affects Versions: parent-pom-11
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: parent-pom-12
>
>
> Additional updates beyond UIMA-5856. Remove redundant/outdated versioning
> now provided by current apache-wide parent-pom (21). add common configuration
> for api change report.
> Attempts to use the checksum-maven-plugin reveal that it doesn't work
> correctly, see [https://github.com/nicoulaj/checksum-maven-plugin/issues/63]
> ). Design a work-around that uses Ant scripts, and insure it works both for
> maven-deploy targets (e.g. .m2) and for normal apache distribution targets
> (e.g. project/target ).
> Due to bug in the current implementation of the maven-gpg-plugin ( MGPG-66 ),
> the gpg plugin needs to be run before doing the .sha512 checksumming
> (otherwise the checksums also get signed).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
