[
https://issues.apache.org/jira/browse/NIFI-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996916#comment-15996916
]
James Wing commented on NIFI-3795:
----------------------------------
[~trixpan] I'm not sure we **need** to do anything. Because of the changes to
the build profiles, {{mvn clean install}} no longer works for a source build
the way it used to. Was that ever a hard requirement? {{mvn clean install
-PgenerateArchives}} will work. The change is unexpected, and perhaps a bit
awkward, but it doesn't seem impossible. Hopefully Brian's solution will make
it an irrelevant issue.
> 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
> Assignee: James Wing
> 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)
