You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Marshall Schor <ms...@schor.com> on 2018/10/02 14:27:49 UTC
Re: doing the changes to add checksums for maven artifacts
Hi Richard,
In your comment you say: I have filed another commit doing that under <jira
uima-5856>
Are you doing the commit, or did you mean to say "comment"?
It's probably best if I continue hacking this code, rather than trying to
coordinate. In looking at the apache-wide pom, I can see it too is making the
assumption that the artifacts finalName is the maven conventional one. I can
easily override this I think, which is how I plan to do this.
-Marshall
On 10/2/2018 7:20 AM, Richard Eckart de Castilho wrote:
> I have filed another commit doing that under
> https://issues.apache.org/jira/browse/UIMA-5856.
>
> ----
>
> Trying to build uima v2, I'm seeing messages such as these during the build:
>
> ----
> [INFO] --- maven-javadoc-plugin:3.0.1:jar (attach-javadocs) @ uimaj-test-util ---
> [WARNING] Are you sure about the <javadocVersion/> parameter? It seems to be 1.8.0
> ----
>
> But I have no idea where they come from. I already tested locally upgrading to
> the maven-javadoc-plugin 3.0.1 (https://issues.apache.org/jira/browse/MJAVADOC-512)
> but even with that version, I get the warning. I also have no idea where the
> 1.8.0 value would be coming from - "mvn help:effective-pom" says that the
> "javadocVersion" parameter value is "1.7". Might be still a but in
> maven-javadoc-plugin 3.0.1.
>
> ----
>
> While we are at it: Maven keeps telling me that we shouldn't use the stanza
>
> <prerequisites>
> <!-- 2.2.0 is broken when deploying - checksums invalid -->
> <!-- 2.2.1 doesn't work -->
> <maven>3.3.9</maven>
> </prerequisites>
>
> in the parent pom, because that stanza is only relevant for Maven plugin modules.
> If we want to generally enforce the use of a specific Maven version, we should be
> using the enforcer plugin instead.
>
> Is there any reason we have that stanza in the UIMA parent pom?
>
> Cheers,
>
> -- Richard
Re: doing the changes to add checksums for maven artifacts
Posted by Richard Eckart de Castilho <re...@apache.org>.
On 2. Oct 2018, at 16:27, Marshall Schor <ms...@schor.com> wrote:
>
> In your comment you say: I have filed another commit doing that under <jira
> uima-5856>
>
> Are you doing the commit, or did you mean to say "comment"?
I did the commit:
URL: https://svn.apache.org/repos/asf/uima/build/trunk/parent-pom/pom.xml
Commit: rev 1842612
Added this section:
<plugin>
<groupId>net.nicoulaj.maven.plugins</groupId>
<artifactId>checksum-maven-plugin</artifactId>
<version>1.8</version>
<!-- Cannot use 1.7 used by ASF parent pom because of https://github.com/nicoulaj/checksum-maven-plugin/issues/62 -->
<executions>
<execution>
<id>artifacts-checksum</id>
<goals>
<goal>artifacts</goal>
</goals>
</execution>
</executions>
<configuration>
<algorithms>
<algorithm>SHA-512</algorithm>
</algorithms>
<appendFilename>true</appendFilename>
<attachChecksums>true</attachChecksums>
</configuration>
</plugin>
-- Richard