[ https://issues.apache.org/jira/browse/MRQL-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leonidas Fegaras updated MRQL-14: --------------------------------- Attachment: MRQL-14.patch Actually, I have already done this. This is how I pushed the snapshots to Nexus. The attached patch renames the version to 0.9.0-incubating-SNAPSHOT and split the dist module into two modules: src-dist and bin-dist so that the two tarballs are deployed under a different name. > Add the "-SNAPSHOT" suffix > -------------------------- > > Key: MRQL-14 > URL: https://issues.apache.org/jira/browse/MRQL-14 > Project: MRQL > Issue Type: Sub-task > Reporter: Edward J. Yoon > Attachments: MRQL-14.patch > > > {code} > $ mvn release:prepare > ... > [INFO] MRQL .............................................. FAILURE [15.365s] > [INFO] gen ............................................... SKIPPED > [INFO] mrql-mr ........................................... SKIPPED > [INFO] mrql-bsp .......................................... SKIPPED > [INFO] mrql-spark ........................................ SKIPPED > [INFO] mrql-dist ......................................... SKIPPED > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 33.922s > [INFO] Finished at: Thu Sep 05 08:30:35 KST 2013 > [INFO] Final Memory: 16M/242M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on > project MRQL: You don't have a SNAPSHOT project in the reactor projects list. > -> [Help 1] > {code} > To fix above error, we need to add '-SNAPSHOT' suffix like: > {code} > <groupId>org.apache.mrql</groupId> > <artifactId>MRQL</artifactId> > <version>0.9.0-SNAPSHOT</version> > <packaging>pom</packaging> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira