[
https://issues.apache.org/jira/browse/DAFFODIL-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-2849.
-----------------------------------
Verified the specified commit (commit fd7005995850cb72af9a58e4eb1d38b30db183a8)
is included in the latest pull from the daffodil repository.
Verified, via review, changes identified in the commit comment were
implemented.
Reviewed the RPM, tgz and zip and verified the .jar filename now include the
_2.12 as specified.
Rolled the back to a prefix commit and verified that the .jar filenames in the
RPM, tgz and zip did not include the _2.12.
> Daffodil jars in RPM/tar/zip do not have the same name as those published to
> maven
> ----------------------------------------------------------------------------------
>
> Key: DAFFODIL-2849
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2849
> Project: Daffodil
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Steve Lawrence
> Priority: Major
> Fix For: 3.7.0
>
>
> When sbt native packager is used to create an RPM, tar, or zip release files,
> the daffodil jars do not have the "_2.12" in the name. This usually isn't a
> big deal because we package these files along with the scala library, so we
> know they are compatible.
> However, this can make it a bit more difficult to verify the published maven
> artifacts are the same as those in the helper binaries since they have
> different names. I have also heard of instances where the files in the RPM
> are used to create a mini local maven repository, which requires changing pom
> dependencies because the _2.12 is missing.
> The sbt native packager plugin is used to creae the RPM, tar, and zip
> files--we should see if it can be configured so that it will include the
> _2.12 version in the jar names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
