| 1 |
On Wed, May 25, 2011 at 5:09 PM, Jörg Schaible <joerg.schaible@×××.de> wrote: |
| 2 |
> Hi Robert, |
| 3 |
|
| 4 |
Hi Jörg |
| 5 |
|
| 6 |
> Robert Burrell Donkin wrote: |
| 7 |
|
| 8 |
<snip> |
| 9 |
|
| 10 |
>> maven seems to be moving towards requiring specific core versions for |
| 11 |
>> builds. some projects i develop require maven 2, some maven 3. i |
| 12 |
>> manage this situation with a set of custom scripts and installations |
| 13 |
>> independent of gentoo. i expect other developers now work in a similar |
| 14 |
>> way. (same goes for jdks.) the gentoo java stuff just gets in my way |
| 15 |
>> now for development. |
| 16 |
> |
| 17 |
> Why? I have emerged maven:1.0, maven:1.1, maven:2.0, maven:2.2 and |
| 18 |
> maven:3.0. I've selected my default version with eselect. However, I can use |
| 19 |
> any of those versions at the same time: |
| 20 |
> |
| 21 |
> /usr/bin $ ls -lGgo m*v*n* |
| 22 |
> lrwxrwxrwx 1 34 Jan 22 14:07 maven-1.0 -> /usr/share/maven- |
| 23 |
> bin-1.0/bin/maven |
| 24 |
> lrwxrwxrwx 1 34 Jan 22 14:07 maven-1.1 -> /usr/share/maven- |
| 25 |
> bin-1.1/bin/maven |
| 26 |
> lrwxrwxrwx 1 7 Jul 19 2010 mvn -> mvn-3.0 |
| 27 |
> lrwxrwxrwx 1 32 Apr 30 2010 mvn-2.0 -> /usr/share/maven-bin-2.0/bin/mvn |
| 28 |
> lrwxrwxrwx 1 32 Apr 30 2010 mvn-2.2 -> /usr/share/maven-bin-2.2/bin/mvn |
| 29 |
> lrwxrwxrwx 1 32 Mar 10 18:17 mvn-3.0 -> /usr/share/maven-bin-3.0/bin/mvn |
| 30 |
> |
| 31 |
> All that eselect effectively does is to switch the unversioned link. You may |
| 32 |
> call any of those scripts (well, you should not have set MAVEN_HOME at all, |
| 33 |
> the Maven start script will do this for you anyway). |
| 34 |
|
| 35 |
eselect edits the symlinks. this switches the maven version for the |
| 36 |
entire system. i want to be able to switch maven (and ant and java) |
| 37 |
versions for just a terminal. is there some way to make this work with |
| 38 |
eselect? |
| 39 |
|
| 40 |
- robert |
Archives