beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-2344) Re-rename fat jar in archetypes
Date Tue, 23 May 2017 00:52:04 GMT


ASF GitHub Bot commented on BEAM-2344:

GitHub user jasonkuster opened a pull request:

    [BEAM-2344] Re-rename fat jar

    Signed-off-by: Jason Kuster <>
    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [x] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [x] Make sure tests pass via `mvn clean verify`.
     - [x] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

You can merge this pull request into a Git repository by running:

    $ git pull jar-name

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3204
commit 94cdd31e1e9a386dfcc7964aecf14ffc1c4f5850
Author: Jason Kuster <>
Date:   2017-05-23T00:46:49Z

    Re-rename fat jar so that install doesn't install the bundled jar as the default jar.
    Signed-off-by: Jason Kuster <>


> Re-rename fat jar in archetypes
> -------------------------------
>                 Key: BEAM-2344
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>            Reporter: Jason Kuster
>            Assignee: Jason Kuster
>             Fix For: 2.1.0
> Currently fat jar in archetypes will overwrite the standard jar, and will thus be installed
as that module's artifact during the install phase. Re-rename it such that it is not.

This message was sent by Atlassian JIRA

View raw message