[jira] [Created] (RATIS-241) Links on home page (download area) to checksum/gpg key are mistaken
Karl Heinz Marbaise created RATIS-241: - Summary: Links on home page (download area) to checksum/gpg key are mistaken Key: RATIS-241 URL: https://issues.apache.org/jira/browse/RATIS-241 Project: Ratis Issue Type: Improvement Affects Versions: 0.1.0-alpha Reporter: Karl Heinz Marbaise The link `checksum` links to https://dist.apache.org/repos/dist/release/incubator/ratis/0.1.0-alpha/apache-ratis-incubating-0.1.0-alpha-src.tar.gz.asc which is the GPG signature file and the link `signature` links to https://dist.apache.org/repos/dist/release/incubator/ratis/0.1.0-alpha/apache-ratis-incubating-0.1.0-alpha-src.tar.gz.mds which contains the checksums ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (RATIS-56) Update project version to 0.1.0-alpha
[
https://issues.apache.org/jira/browse/RATIS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955244#comment-15955244
]
Karl Heinz Marbaise edited comment on RATIS-56 at 5/3/17 5:44 AM:
--
Is there a good reason why not using either
[maven-release-plugin|http://maven.apache.org/maven-release/maven-release-plugin/]
which updates the pom versions accordingly or use the
[versions-maven-plugin|http://www.mojohaus.org/versions-maven-plugin/] which
can do the same for that purpose..? For example via versions-maven-plugin:
{code}
mvn versions:set -DnewVersion=0.1.0-alpha
{code}
was (Author: khmarbaise):
Is there a good reason why not using either
[maven-release-plugin|http://maven.apache.org/maven-release/maven-release-plugin/]
which updates the pom versions accordingly or use the
[versions-maven-plugin|http://www.mojohaus.org/versions-maven-plugin/] which
can do the same for that purpose..? For example via versions-maven-plugin:
{code}
mvn versons:set -DnewVersion=0.1.0-alpha
{code}
> Update project version to 0.1.0-alpha
> -
>
> Key: RATIS-56
> URL: https://issues.apache.org/jira/browse/RATIS-56
> Project: Ratis
> Issue Type: Sub-task
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
> Fix For: 0.1.0-alpha
>
> Attachments: r56_20170330.patch, r56_20170402.patch
>
>
> We may use the following command to update the project version from
> 0.1-SNAPSHOT to 0.1.0-alpha.
> {code}
> find . -name pom.xml | xargs sed -i.old "s/0.1-SNAPSHOT/0.1.0-alpha/g"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (RATIS-73) Update apache-rat-plugin to version 0.12
Karl Heinz Marbaise created RATIS-73: Summary: Update apache-rat-plugin to version 0.12 Key: RATIS-73 URL: https://issues.apache.org/jira/browse/RATIS-73 Project: Ratis Issue Type: Improvement Affects Versions: 0.1.0-alpha Reporter: Karl Heinz Marbaise Priority: Trivial Fix For: 0.1.0-alpha Upgrading the apache-rat-plugin to 0.12 and remove the rest of the configuration cause it's the default. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (RATIS-67) BUILDING.md file is not correct
[
https://issues.apache.org/jira/browse/RATIS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed RATIS-67.
Resolution: Invalid
Assignee: Karl Heinz Marbaise
Fix Version/s: (was: 0.1.0-alpha)
I missed that I had configured some routes in my local Nexus which were
blocking the download of the hadoop parts...
> BUILDING.md file is not correct
> ---
>
> Key: RATIS-67
> URL: https://issues.apache.org/jira/browse/RATIS-67
> Project: Ratis
> Issue Type: Bug
>Affects Versions: 0.1.0-alpha
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
>
> The {{BUILDING.md}} file claims to build RATIS for the first time via:
> {code}
> mvn package -DskipTests
> {code}
> which simply fails with the following output:
> {code}
> [ERROR] Failed to execute goal on project ratis-hadoop-shaded: Could not
> resolve dependencies for project
> org.apache.ratis:ratis-hadoop-shaded:jar:0.1-SNAPSHOT: Failure to find
> org.apache.hadoop:hadoop-common:jar:3.0.0-alpha1 in
> http://localhost:8081/nexus/content/groups/public was cached in the local
> repository, resolution will not be reattempted until the update interval of
> nexus has elapsed or updates are forced -> [Help 1]
> {code}
> This looks like those dependencies are used instead of being dependencies
> defined by {{true
[jira] [Updated] (RATIS-71) Removed usage of version properties usages for maven-plugins
[
https://issues.apache.org/jira/browse/RATIS-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated RATIS-71:
-
Attachment: 0001-RATIS-71-Removed-usage-of-version-properties-usages-.patch
> Removed usage of version properties usages for maven-plugins
>
>
> Key: RATIS-71
> URL: https://issues.apache.org/jira/browse/RATIS-71
> Project: Ratis
> Issue Type: Improvement
>Affects Versions: 0.1.0-alpha
>Reporter: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 0.1.0-alpha
>
> Attachments:
> 0001-RATIS-71-Removed-usage-of-version-properties-usages-.patch
>
>
> Currently there several plugins usages which look like this:
> {code:xml}
> org.apache.maven.plugins
> maven-shade-plugin
> ${maven-shade-plugin.version}
> {code}
> which is superfluous cause the versions are already defined via the
> pluginManagement in parent.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (RATIS-71) Removed usage of version properties usages for maven-plugins
Karl Heinz Marbaise created RATIS-71:
Summary: Removed usage of version properties usages for
maven-plugins
Key: RATIS-71
URL: https://issues.apache.org/jira/browse/RATIS-71
Project: Ratis
Issue Type: Improvement
Affects Versions: 0.1.0-alpha
Reporter: Karl Heinz Marbaise
Priority: Trivial
Fix For: 0.1.0-alpha
Currently there several plugins usages which look like this:
{code:xml}
org.apache.maven.plugins
maven-shade-plugin
${maven-shade-plugin.version}
{code}
which is superfluous cause the versions are already defined via the
pluginManagement in parent.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RATIS-68) Simplify parent entries
[
https://issues.apache.org/jira/browse/RATIS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated RATIS-68:
-
Description:
Every child pom has in it's parent:
{code:xml}
4.0.0
ratis
org.apache.ratis
0.1-SNAPSHOT
..
..
0.1-SNAPSHOT
{code} where the entry for {{relativePath}} is simply not needed, cause it the
default in Maven.
Furthermore each child defines the version which is also not needed cause it's
inherited from the parent. This can be simplified.
I have attached an appropriate patch to fix the issue.
was:
Every child pom has in it's parent:
{code:xml}
4.0.0
ratis
org.apache.ratis
0.1-SNAPSHOT
..
..
0.1-SNAPSHOT
{code} where the entry for {{relativePath}} is simply not needed, cause it the
default in Maven.
Furthermore each child defines the version which is also not needed cause it's
inherited from the parent. This can be simplified.
> Simplify parent entries
> ---
>
> Key: RATIS-68
> URL: https://issues.apache.org/jira/browse/RATIS-68
> Project: Ratis
> Issue Type: Improvement
>Affects Versions: 0.1.0-alpha
>Reporter: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 0.1.0-alpha
>
> Attachments: 0001-RATIS-68-Simplify-parent-entries.patch
>
>
> Every child pom has in it's parent:
> {code:xml}
> 4.0.0
>
> ratis
> org.apache.ratis
> 0.1-SNAPSHOT
> ..
>
> ..
> 0.1-SNAPSHOT
> {code} where the entry for {{relativePath}} is simply not needed, cause it
> the default in Maven.
> Furthermore each child defines the version which is also not needed cause
> it's inherited from the parent. This can be simplified.
> I have attached an appropriate patch to fix the issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RATIS-68) Simplify parent entries
[
https://issues.apache.org/jira/browse/RATIS-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated RATIS-68:
-
Attachment: 0001-RATIS-68-Simplify-parent-entries.patch
> Simplify parent entries
> ---
>
> Key: RATIS-68
> URL: https://issues.apache.org/jira/browse/RATIS-68
> Project: Ratis
> Issue Type: Improvement
>Affects Versions: 0.1.0-alpha
>Reporter: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 0.1.0-alpha
>
> Attachments: 0001-RATIS-68-Simplify-parent-entries.patch
>
>
> Every child pom has in it's parent:
> {code:xml}
> 4.0.0
>
> ratis
> org.apache.ratis
> 0.1-SNAPSHOT
> ..
>
> ..
> 0.1-SNAPSHOT
> {code} where the entry for {{relativePath}} is simply not needed, cause it
> the default in Maven.
> Furthermore each child defines the version which is also not needed cause
> it's inherited from the parent. This can be simplified.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RATIS-66) Do you need make-maven-plugin ?
[
https://issues.apache.org/jira/browse/RATIS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated RATIS-66:
-
Attachment: 0001-RATIS-66-make-maven-plugin-removed-cause-it-not-real.patch
> Do you need make-maven-plugin ?
> ---
>
> Key: RATIS-66
> URL: https://issues.apache.org/jira/browse/RATIS-66
> Project: Ratis
> Issue Type: Improvement
>Affects Versions: 0.1.0-alpha
>Reporter: Karl Heinz Marbaise
>Priority: Trivial
> Fix For: 0.1.0-alpha
>
> Attachments:
> 0001-RATIS-66-make-maven-plugin-removed-cause-it-not-real.patch
>
>
> I have taken a look into your pom file and seen that you have defined
> {{make-maven-plugin}} which is a plugin from 2009 ? Are you really have need
> for this? Furthermore I have taken a look at MojoHaus (former codehaus) there
> does not exist any references of this plugin which means it is not supported
> nor developer in any kind?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (RATIS-56) Update project version to 0.1.0-alpha
[
https://issues.apache.org/jira/browse/RATIS-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955244#comment-15955244
]
Karl Heinz Marbaise commented on RATIS-56:
--
Is there a good reason why not using either
[maven-release-plugin|http://maven.apache.org/maven-release/maven-release-plugin/]
which updates the pom versions accordingly or use the
[versions-maven-plugin|http://www.mojohaus.org/versions-maven-plugin/] which
can do the same for that purpose..? For example via versions-maven-plugin:
{code}
mvn versons:set -DnewVersion=0.1.0-alpha
{code}
> Update project version to 0.1.0-alpha
> -
>
> Key: RATIS-56
> URL: https://issues.apache.org/jira/browse/RATIS-56
> Project: Ratis
> Issue Type: Sub-task
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Tsz Wo Nicholas Sze
> Attachments: r56_20170330.patch, r56_20170402.patch
>
>
> We may use the following command to update the project version from
> 0.1-SNAPSHOT to 0.1.0-alpha.
> {code}
> find . -name pom.xml | xargs sed -i.old "s/0.1-SNAPSHOT/0.1.0-alpha/g"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
