[
https://issues.apache.org/jira/browse/NIFI-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996016#comment-15996016
]
James Wing commented on NIFI-3795:
----------------------------------
I believe the following will work:
{code}
mvn clean install -DskipTests -PgenerateArchives
{code}
The error is referring to the dir, tar, and zip formats for the output
assemblies. These are now toggled by profiles in the nifi-assembly POM, and I
think we're fighting over which profiles are active.
* In a routine build from a git repo, {{mvn clean install}} uses the
"activeByDefault" generateArchives profile to output dir, tar.gz, and zip
assemblies.
* If the {{-Pdir-only}} flag is added, the dir-only profile is activated, and
the explicit activation of another profile causes generateArchives to not be
active.
* If the build is performed outside a git repo, the build-info-no-git profile
is activated, and again generateArchives is then deactivated as a result. This
leaves the maven-assembly-plugin with no declared output formats for a source
build.
I believe this situation is the cumulative result of NIFI-2115 for detailed
version info and NIFI-3434 for the dir-only flag. I'm not yet sure what a
better arrangement of profiles might look like, but hopefully adding
{{-PgenerateArchives}} is not unacceptable for the moment.
> nifi-assembly fails with "no formats specified" error
> -----------------------------------------------------
>
> Key: NIFI-3795
> URL: https://issues.apache.org/jira/browse/NIFI-3795
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Bryan Bende
> Priority: Blocker
> Fix For: 1.2.0
>
>
> After staging the 1.2.0 RC1 artifacts, I then downloaded the source zip from
> the Nexus staging repo, unzipped it and ran "mvn clean install -DskipTests"
> to verify that it would build. I encountered the below error:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.5.2:single (make shared
> resource) on project nifi-assembly: No formats specified in the execution
> parameters or the assembly descriptor. -> [Help 1]
> After some debugging it was determined that one difference between this build
> and the previous build that staged the artifacts, is that this build was not
> within a git repo where as the other one was.
> After running git init, adding all files, and making a commit, then the build
> passed. Still unclear as to why being in a git repo matters here, although
> every NAR now tries to use the git info from the buildnumber plugin to filter
> into the MANIFEST files.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
