| 1 |
On 05/23/2011 07:52 PM, Kasun Gajasinghe wrote: |
| 2 |
|
| 3 |
>> |
| 4 |
>> maven-bin 2.x support continues to work through the binary package? |
| 5 |
> |
| 6 |
> Yes, we can keep supporting maven-bin 2.x for maven users. Though the |
| 7 |
> packagers of projects based on maven won't be able to use the support |
| 8 |
> for maven 2.x if we start with 3.x.This project's focus is more |
| 9 |
> towards packagers, right? I think Serkan or people who are more |
| 10 |
> familiar with this can give an exact answer. |
| 11 |
> |
| 12 |
|
| 13 |
So are you discussing which version of Maven to build from source or |
| 14 |
which version to target ebuild infrastructure for? Those two don't |
| 15 |
necessarily need to be the same and your topic implied the former but |
| 16 |
the above talks about the latter. The ebuild infrastructure for Maven |
| 17 |
based projects should work just the same regardless of whether the maven |
| 18 |
package itself is built from source or not. Our target is of course to |
| 19 |
get rid of all binary packages but I consider this thread about asking |
| 20 |
about priorities. For ebuild infrastructure targeting 2.x is fine if the |
| 21 |
large majority of projects that will start using the work are using 2.x. |
| 22 |
Otherwise I think my earlier logic still applies. |
| 23 |
|
| 24 |
Regards, |
| 25 |
Petteri |
Archives