You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Thomas Jungblut (Created) (JIRA)" <ji...@apache.org> on 2012/01/20 12:28:40 UTC
[jira] [Created] (HAMA-491) Add Maven Release Target
Add Maven Release Target
------------------------
Key: HAMA-491
URL: https://issues.apache.org/jira/browse/HAMA-491
Project: Hama
Issue Type: New Feature
Components: build
Affects Versions: 0.3.0
Reporter: Thomas Jungblut
Priority: Blocker
Fix For: 0.4.0
We need to add a release target to maven:
* "binary" release without sources, packed into a tar.gz archive
* sources release without precompiled jars, as well packed into a tar.gz archive
Pluspoints: Automagically pgp armoring of the created archive.
You can pretty much just copy and paste the 0.3.0 release and just update the jars (core, example, add YARN and graph). Maybe there must be a depedency update done in the lib folder.
One feature that must be included in 0.4.0 is HAMA-470, you have to make sure that the file is in the correct place.
How to test:
A user just has to set the hdfs address in the site config and is able to start the cluster without problems (run some examples etc).
All packaging stuff can be done with the maven assembly plugin: http://maven.apache.org/plugins/maven-assembly-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HAMA-491) Add Maven Release Target
Posted by "Edward J. Yoon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward J. Yoon updated HAMA-491:
--------------------------------
Attachment: patch_v02.txt
attach again.
> Add Maven Release Target
> ------------------------
>
> Key: HAMA-491
> URL: https://issues.apache.org/jira/browse/HAMA-491
> Project: Hama
> Issue Type: New Feature
> Components: build
> Affects Versions: 0.3.0
> Reporter: Thomas Jungblut
> Priority: Blocker
> Labels: newbie
> Fix For: 0.4.0
>
> Attachments: patch.txt, patch_v02.txt
>
>
> We need to add a release target to maven:
> * "binary" release without sources, packed into a tar.gz archive
> * sources release without precompiled jars, as well packed into a tar.gz archive
> Pluspoints: Automagically pgp armoring of the created archive.
> You can pretty much just copy and paste the 0.3.0 release and just update the jars (core, example, add YARN and graph). Maybe there must be a depedency update done in the lib folder.
> One feature that must be included in 0.4.0 is HAMA-470, you have to make sure that the file is in the correct place.
> How to test:
> A user just has to set the hdfs address in the site config and is able to start the cluster without problems (run some examples etc).
> All packaging stuff can be done with the maven assembly plugin: http://maven.apache.org/plugins/maven-assembly-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HAMA-491) Add Maven Release Target
Posted by "Edward J. Yoon (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward J. Yoon reassigned HAMA-491:
-----------------------------------
Assignee: Edward J. Yoon
> Add Maven Release Target
> ------------------------
>
> Key: HAMA-491
> URL: https://issues.apache.org/jira/browse/HAMA-491
> Project: Hama
> Issue Type: New Feature
> Components: build
> Affects Versions: 0.3.0
> Reporter: Thomas Jungblut
> Assignee: Edward J. Yoon
> Priority: Blocker
> Labels: newbie
> Fix For: 0.4.0
>
> Attachments: patch.txt, patch_v02.txt
>
>
> We need to add a release target to maven:
> * "binary" release without sources, packed into a tar.gz archive
> * sources release without precompiled jars, as well packed into a tar.gz archive
> Pluspoints: Automagically pgp armoring of the created archive.
> You can pretty much just copy and paste the 0.3.0 release and just update the jars (core, example, add YARN and graph). Maybe there must be a depedency update done in the lib folder.
> One feature that must be included in 0.4.0 is HAMA-470, you have to make sure that the file is in the correct place.
> How to test:
> A user just has to set the hdfs address in the site config and is able to start the cluster without problems (run some examples etc).
> All packaging stuff can be done with the maven assembly plugin: http://maven.apache.org/plugins/maven-assembly-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HAMA-491) Add Maven Release Target
Posted by "Edward J. Yoon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward J. Yoon updated HAMA-491:
--------------------------------
Attachment: patch.txt
This patch adds dist module to generate release tarball.
> Add Maven Release Target
> ------------------------
>
> Key: HAMA-491
> URL: https://issues.apache.org/jira/browse/HAMA-491
> Project: Hama
> Issue Type: New Feature
> Components: build
> Affects Versions: 0.3.0
> Reporter: Thomas Jungblut
> Priority: Blocker
> Labels: newbie
> Fix For: 0.4.0
>
> Attachments: patch.txt
>
>
> We need to add a release target to maven:
> * "binary" release without sources, packed into a tar.gz archive
> * sources release without precompiled jars, as well packed into a tar.gz archive
> Pluspoints: Automagically pgp armoring of the created archive.
> You can pretty much just copy and paste the 0.3.0 release and just update the jars (core, example, add YARN and graph). Maybe there must be a depedency update done in the lib folder.
> One feature that must be included in 0.4.0 is HAMA-470, you have to make sure that the file is in the correct place.
> How to test:
> A user just has to set the hdfs address in the site config and is able to start the cluster without problems (run some examples etc).
> All packaging stuff can be done with the maven assembly plugin: http://maven.apache.org/plugins/maven-assembly-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HAMA-491) Add Maven Release Target
Posted by "Edward J. Yoon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196059#comment-13196059 ]
Edward J. Yoon commented on HAMA-491:
-------------------------------------
Regarding yarn module, I'd like to release separately because of dependency problems.
Maybe like this?
* hama-0.4-incubating.tar.gz
* hama-0.4-yarn-incubating.tar.gz
> Add Maven Release Target
> ------------------------
>
> Key: HAMA-491
> URL: https://issues.apache.org/jira/browse/HAMA-491
> Project: Hama
> Issue Type: New Feature
> Components: build
> Affects Versions: 0.3.0
> Reporter: Thomas Jungblut
> Priority: Blocker
> Labels: newbie
> Fix For: 0.4.0
>
> Attachments: patch.txt
>
>
> We need to add a release target to maven:
> * "binary" release without sources, packed into a tar.gz archive
> * sources release without precompiled jars, as well packed into a tar.gz archive
> Pluspoints: Automagically pgp armoring of the created archive.
> You can pretty much just copy and paste the 0.3.0 release and just update the jars (core, example, add YARN and graph). Maybe there must be a depedency update done in the lib folder.
> One feature that must be included in 0.4.0 is HAMA-470, you have to make sure that the file is in the correct place.
> How to test:
> A user just has to set the hdfs address in the site config and is able to start the cluster without problems (run some examples etc).
> All packaging stuff can be done with the maven assembly plugin: http://maven.apache.org/plugins/maven-assembly-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HAMA-491) Add Maven Release Target
Posted by "Edward J. Yoon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196653#comment-13196653 ]
Edward J. Yoon commented on HAMA-491:
-------------------------------------
Seems work fine. I just commit this.
Please let me know if there are strange unusual things.
> Add Maven Release Target
> ------------------------
>
> Key: HAMA-491
> URL: https://issues.apache.org/jira/browse/HAMA-491
> Project: Hama
> Issue Type: New Feature
> Components: build
> Affects Versions: 0.3.0
> Reporter: Thomas Jungblut
> Assignee: Edward J. Yoon
> Priority: Blocker
> Labels: newbie
> Fix For: 0.4.0
>
> Attachments: patch.txt, patch_v02.txt
>
>
> We need to add a release target to maven:
> * "binary" release without sources, packed into a tar.gz archive
> * sources release without precompiled jars, as well packed into a tar.gz archive
> Pluspoints: Automagically pgp armoring of the created archive.
> You can pretty much just copy and paste the 0.3.0 release and just update the jars (core, example, add YARN and graph). Maybe there must be a depedency update done in the lib folder.
> One feature that must be included in 0.4.0 is HAMA-470, you have to make sure that the file is in the correct place.
> How to test:
> A user just has to set the hdfs address in the site config and is able to start the cluster without problems (run some examples etc).
> All packaging stuff can be done with the maven assembly plugin: http://maven.apache.org/plugins/maven-assembly-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HAMA-491) Add Maven Release Target
Posted by "Thomas Jungblut (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196061#comment-13196061 ]
Thomas Jungblut commented on HAMA-491:
--------------------------------------
+1
> Add Maven Release Target
> ------------------------
>
> Key: HAMA-491
> URL: https://issues.apache.org/jira/browse/HAMA-491
> Project: Hama
> Issue Type: New Feature
> Components: build
> Affects Versions: 0.3.0
> Reporter: Thomas Jungblut
> Priority: Blocker
> Labels: newbie
> Fix For: 0.4.0
>
> Attachments: patch.txt
>
>
> We need to add a release target to maven:
> * "binary" release without sources, packed into a tar.gz archive
> * sources release without precompiled jars, as well packed into a tar.gz archive
> Pluspoints: Automagically pgp armoring of the created archive.
> You can pretty much just copy and paste the 0.3.0 release and just update the jars (core, example, add YARN and graph). Maybe there must be a depedency update done in the lib folder.
> One feature that must be included in 0.4.0 is HAMA-470, you have to make sure that the file is in the correct place.
> How to test:
> A user just has to set the hdfs address in the site config and is able to start the cluster without problems (run some examples etc).
> All packaging stuff can be done with the maven assembly plugin: http://maven.apache.org/plugins/maven-assembly-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HAMA-491) Add Maven Release Target
Posted by "Edward J. Yoon (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HAMA-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward J. Yoon resolved HAMA-491.
---------------------------------
Resolution: Fixed
Fixed.
> Add Maven Release Target
> ------------------------
>
> Key: HAMA-491
> URL: https://issues.apache.org/jira/browse/HAMA-491
> Project: Hama
> Issue Type: New Feature
> Components: build
> Affects Versions: 0.3.0
> Reporter: Thomas Jungblut
> Assignee: Edward J. Yoon
> Priority: Blocker
> Labels: newbie
> Fix For: 0.4.0
>
> Attachments: patch.txt, patch_v02.txt
>
>
> We need to add a release target to maven:
> * "binary" release without sources, packed into a tar.gz archive
> * sources release without precompiled jars, as well packed into a tar.gz archive
> Pluspoints: Automagically pgp armoring of the created archive.
> You can pretty much just copy and paste the 0.3.0 release and just update the jars (core, example, add YARN and graph). Maybe there must be a depedency update done in the lib folder.
> One feature that must be included in 0.4.0 is HAMA-470, you have to make sure that the file is in the correct place.
> How to test:
> A user just has to set the hdfs address in the site config and is able to start the cluster without problems (run some examples etc).
> All packaging stuff can be done with the maven assembly plugin: http://maven.apache.org/plugins/maven-assembly-plugin/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira