You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2018/07/13 17:28:00 UTC

[jira] [Resolved] (BEAM-3590) Can't activate release profile from a module directory

     [ https://issues.apache.org/jira/browse/BEAM-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré resolved BEAM-3590.
----------------------------------------
       Resolution: Won't Fix
    Fix Version/s: Not applicable

As we now use Gradle, this issue is not valid anymore.

> Can't activate release profile from a module directory
> ------------------------------------------------------
>
>                 Key: BEAM-3590
>                 URL: https://issues.apache.org/jira/browse/BEAM-3590
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>    Affects Versions: 2.3.0
>            Reporter: Ismaël Mejía
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: Not applicable
>
>
> To run and test a specific module, e.g. JmsIO a common pattern is to go to the
> directory and do:
> {quote}cd sdks/java/io/jms
> mvn clean verify -Prelease
> {quote}
> This worked before but breaks since the recent changes in the release profile.
> The detailed exception
> {quote}[INFO] --- maven-assembly-plugin:3.1.0:single (source-release-assembly) @ beam-sdks-java-io-jms ---
> [INFO] Reading assembly descriptor: assembly.xml
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 12.221 s
> [INFO] Finished at: 2018-01-31T22:03:27+01:00
> [INFO] Final Memory: 71M/1457M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (source-release-assembly) on project beam-sdks-java-io-jms: Error reading assemblies: Error locating assembly descriptor: assembly.xml
> [ERROR]
> [ERROR] [1] [INFO] Searching for file location: /home/ismael/upstream/beam/sdks/java/io/jms/assembly.xml
> [ERROR]
> [ERROR] [2] [INFO] File: /home/ismael/upstream/beam/sdks/java/io/jms/assembly.xml does not exist.
> [ERROR]
> [ERROR] [3] [INFO] File: /home/ismael/upstream/beam/sdks/java/io/jms/assembly.xml does not exist.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {quote}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)