You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Gianmarco De Francisci Morales (JIRA)" <ji...@apache.org> on 2012/07/18 17:26:35 UTC

[jira] [Created] (GIRAPH-264) bin/giraph should not maven on the machine running graph

Gianmarco De Francisci Morales created GIRAPH-264:
-----------------------------------------------------

             Summary: bin/giraph should not maven on the machine running graph
                 Key: GIRAPH-264
                 URL: https://issues.apache.org/jira/browse/GIRAPH-264
             Project: Giraph
          Issue Type: Improvement
    Affects Versions: 0.2.0
            Reporter: Gianmarco De Francisci Morales
            Priority: Trivial


Maven is for building the project, but it is used also in bin/giraph to run it.
{code}
	CLASSPATH2=`mvn dependency:build-classpath | grep -v "[INFO]"`
{code}

I understand that it is useful for building the classpath given the dependencies, but this creates a dependency on Maven on the Giraph runtime.
I don't think it is desirable.
Working around it should be easy.

--
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] (GIRAPH-264) bin/giraph should not require maven on the machine running graph

Posted by "Gianmarco De Francisci Morales (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GIRAPH-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gianmarco De Francisci Morales updated GIRAPH-264:
--------------------------------------------------

    Summary: bin/giraph should not require maven on the machine running graph  (was: bin/giraph should not maven on the machine running graph)
    
> bin/giraph should not require maven on the machine running graph
> ----------------------------------------------------------------
>
>                 Key: GIRAPH-264
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-264
>             Project: Giraph
>          Issue Type: Improvement
>    Affects Versions: 0.2.0
>            Reporter: Gianmarco De Francisci Morales
>            Priority: Trivial
>
> Maven is for building the project, but it is used also in bin/giraph to run it.
> {code}
> 	CLASSPATH2=`mvn dependency:build-classpath | grep -v "[INFO]"`
> {code}
> I understand that it is useful for building the classpath given the dependencies, but this creates a dependency on Maven on the Giraph runtime.
> I don't think it is desirable.
> Working around it should be easy.

--
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] (GIRAPH-264) bin/giraph should not require maven on the machine running graph

Posted by "Eli Reisman (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GIRAPH-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419715#comment-13419715 ] 

Eli Reisman commented on GIRAPH-264:
------------------------------------

It looks like that if..then path is only taken if its a dev environment, otherwise -cp is obtained from the user's lib/ of jars in $GIRAPH_HOME (see lines 69-81)

                
> bin/giraph should not require maven on the machine running graph
> ----------------------------------------------------------------
>
>                 Key: GIRAPH-264
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-264
>             Project: Giraph
>          Issue Type: Improvement
>    Affects Versions: 0.2.0
>            Reporter: Gianmarco De Francisci Morales
>            Priority: Trivial
>
> Maven is for building the project, but it is used also in bin/giraph to run it.
> {code}
> 	CLASSPATH2=`mvn dependency:build-classpath | grep -v "[INFO]"`
> {code}
> I understand that it is useful for building the classpath given the dependencies, but this creates a dependency on Maven on the Giraph runtime.
> I don't think it is desirable.
> Working around it should be easy.

--
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