You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2007/06/01 06:50:34 UTC

Re: [jira] Closed: (MNG-2121) mvn launch script should use jpackage.org config if available

Jason,

There was hardly consensus on this issue.

More generally, maybe it'd be better to leave it open and unscheduled  
and let user votes drive it?

- Brett

On 01/06/2007, at 2:23 PM, Jason van Zyl (JIRA) wrote:

>
>      [ http://jira.codehaus.org/browse/MNG-2121? 
> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jason van Zyl closed MNG-2121.
> ------------------------------
>
>     Resolution: Won't Fix
>
> Not supporting jpackage. Redhat specific and we're not interested  
> in fracturing our installs.
>
>> mvn launch script should use jpackage.org config if available
>> -------------------------------------------------------------
>>
>>                 Key: MNG-2121
>>                 URL: http://jira.codehaus.org/browse/MNG-2121
>>             Project: Maven 2
>>          Issue Type: Improvement
>>          Components: Command Line
>>    Affects Versions: 2.0.2
>>         Environment: GNU/Linux
>>            Reporter: Chris Hubick
>>            Priority: Minor
>>             Fix For: 2.2.x
>>
>>         Attachments: maven_jpp.patch
>>
>>
>> I am attempting to install and use Maven for the first time... so  
>> excuse me if I'm off base here :)
>> It is my understanding that a single global classpath (and JVM) is  
>> generally deprecated, so I trivially modified my version of the  
>> command line 'mvn' script to automatically utilize my existing  
>> jpackage.org configuration (patch attached).
>> Also, the installation instructions at http://maven.apache.org/ 
>> download.html say to unpack it to /usr/local/maven-2.0.2/, yet the  
>> mvn script looks for the existance of /opt/m2/ when attempting to  
>> automatically set $M2_HOME.  I symlinked /usr/local/maven to /usr/ 
>> local/maven-2.0.2, and also trivially patched my mvn script to  
>> look for /usr/local/maven/ when setting $M2_HOME.  Instead of  
>> adding $M2_HOME/bin to my global path, I just symlinked /usr/local/ 
>> bin/mvn -> /usr/local/maven/bin/mvn.  In this way, I have a  
>> working Maven (I hope) without having to modify any global  
>> configuration on my machine - meaning the install should be side  
>> effect free.  I can also upgrade to a new release without having  
>> to modify any configuration.
>
> -- 
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the  
> administrators: http://jira.codehaus.org/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/ 
> software/jira
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: [jira] Closed: (MNG-2121) mvn launch script should use jpackage.org config if available

Posted by Jason van Zyl <ja...@maven.org>.
On 1 Jun 07, at 12:50 AM 1 Jun 07, Brett Porter wrote:

> Jason,
>
> There was hardly consensus on this issue.
>

There were definitely more users who were in the "who cares" camp.  
And I will always be -1 for adding anything that is location specific  
based on platform/distribution. We have enough problems with  
behaviors of different platform/distributions a la the shell script  
hacks. If we give an inch every distribution will insist on having  
it's platform/distribution specifics baked into everything we have.  
Let the distributions support it. I will never lend support to  
something I think will fracture usage patterns.

> More generally, maybe it'd be better to leave it open and  
> unscheduled and let user votes drive it?
>

I've sifted through almost all the issues and there is no drive for it.

> - Brett
>
> On 01/06/2007, at 2:23 PM, Jason van Zyl (JIRA) wrote:
>
>>
>>      [ http://jira.codehaus.org/browse/MNG-2121? 
>> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Jason van Zyl closed MNG-2121.
>> ------------------------------
>>
>>     Resolution: Won't Fix
>>
>> Not supporting jpackage. Redhat specific and we're not interested  
>> in fracturing our installs.
>>
>>> mvn launch script should use jpackage.org config if available
>>> -------------------------------------------------------------
>>>
>>>                 Key: MNG-2121
>>>                 URL: http://jira.codehaus.org/browse/MNG-2121
>>>             Project: Maven 2
>>>          Issue Type: Improvement
>>>          Components: Command Line
>>>    Affects Versions: 2.0.2
>>>         Environment: GNU/Linux
>>>            Reporter: Chris Hubick
>>>            Priority: Minor
>>>             Fix For: 2.2.x
>>>
>>>         Attachments: maven_jpp.patch
>>>
>>>
>>> I am attempting to install and use Maven for the first time... so  
>>> excuse me if I'm off base here :)
>>> It is my understanding that a single global classpath (and JVM)  
>>> is generally deprecated, so I trivially modified my version of  
>>> the command line 'mvn' script to automatically utilize my  
>>> existing jpackage.org configuration (patch attached).
>>> Also, the installation instructions at http://maven.apache.org/ 
>>> download.html say to unpack it to /usr/local/maven-2.0.2/, yet  
>>> the mvn script looks for the existance of /opt/m2/ when  
>>> attempting to automatically set $M2_HOME.  I symlinked /usr/local/ 
>>> maven to /usr/local/maven-2.0.2, and also trivially patched my  
>>> mvn script to look for /usr/local/maven/ when setting $M2_HOME.   
>>> Instead of adding $M2_HOME/bin to my global path, I just  
>>> symlinked /usr/local/bin/mvn -> /usr/local/maven/bin/mvn.  In  
>>> this way, I have a working Maven (I hope) without having to  
>>> modify any global configuration on my machine - meaning the  
>>> install should be side effect free.  I can also upgrade to a new  
>>> release without having to modify any configuration.
>>
>> -- 
>> This message is automatically generated by JIRA.
>> -
>> If you think it was sent incorrectly contact one of the  
>> administrators: http://jira.codehaus.org/secure/Administrators.jspa
>> -
>> For more information on JIRA, see: http://www.atlassian.com/ 
>> software/jira
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org