| 1 |
> Dne 31.1.2011 02:14, Vlastimil Babka napsal(a): |
| 2 |
> > On 01/19/2011 04:03 PM, "Miroslav Šulc (fordfrog)" wrote: |
| 3 |
> >> hi, |
| 4 |
> >> |
| 5 |
> >> i was looking at the issues when some classes cannot be found via |
| 6 |
> >> DEPENDS, like http://bugs.gentoo.org/show_bug.cgi?id=298689. the problem |
| 7 |
> >> is that DEPENDS for ant tasks does not contain dependency on ant-core. |
| 8 |
> >> this patch below could fix it (at least it fixed the issue for me and |
| 9 |
> >> testing some junit ant tasks while emerging packages with |
| 10 |
> > |
| 11 |
> >> FEATURES="test" worked too): |
| 12 |
> > This could work for ant-tasks themselves, but not for everything else |
| 13 |
> > that has ant-core dependency, such as when a package provides some ant |
| 14 |
> > task. In that case, the depending classes are needed only when invoked |
| 15 |
> > from within ant, in which case they are already on classpath. |
| 16 |
> > Registering as dependency would make ant put on classpath in all cases |
| 17 |
> > the package is used. |
| 18 |
> > The bottom line is, there should be a way to exclude stuff (such as ant |
| 19 |
> > classes) in java-dep-check. |
| 20 |
> |
| 21 |
> well, imo there is a question when to exclude and when not, talking |
| 22 |
> generally, not just about ant classes. |
| 23 |
> |
| 24 |
|
| 25 |
I actually thought that functionality had been implemented a long time ago, |
| 26 |
but obviously my memory is failing me.... |
| 27 |
|
| 28 |
Another example is servlet-api. |
Archives