Btw, some things the eclipse team could do to make packagers' lives easier
and increase the chances for an eclipse version that meets debian's high
freedom/quality standards:
* Test your code with openjdk.
* Assist with building eclipse in a headless manner from the command-line.
(this practically means test your code with eclipse-build and help fix the bugs)
2-3 redhat people trying to fix bugs in the ant scripts of more than 50 people
doesn't really scale, especially if said 50 people continuously add new bugs :)
There are other issues like proper policy for eclipse and plugins (placement
within FHS) etc but debian people can deal with those and the build issue
is currently the thorniest
Btw, some things the eclipse team could do to make packagers' lives easier
and increase the chances for an eclipse version that meets debian's high
freedom/quality standards:
* Test your code with openjdk.
* Assist with building eclipse in a headless manner from the command-line.
(this practically means test your code with eclipse-build and help fix the bugs)
2-3 redhat people trying to fix bugs in the ant scripts of more than 50 people
doesn't really scale, especially if said 50 people continuously add new bugs :)
There are other issues like proper policy for eclipse and plugins (placement
within FHS) etc but debian people can deal with those and the build issue
is currently the thorniest