The ee bundle's README.txt includes the following, which has a few suspicious lines, detailed below.

This package contains:

   Apache Tomcat 6.0.32
   magnolia-core 4.5-beta4
   magnolia-crx 1.1
   magnolia-enterprise-webapp 4.5-beta4
   magnolia-gui 4.5-beta4
   magnolia-jndi 1.0.1
   magnolia-ldap 1.4.1
   magnolia-ldap-bundle 1.4.1
   magnolia-ldap-tester 1.4.1
   Magnolia Backup Module Project 1.1.2
   magnolia-module-cas 1.0
   magnolia-module-groovy 1.2-beta4
   Magnolia Newsletter Module - Base 1.0.1
   Magnolia Newsletter Module - Simple Bundle 1.0.1
   Magnolia Newsletter Module - Campaign Monitor integration 1.0.1
   Magnolia Newsletter Module - STK integration 1.0.1
   Magnolia Synchronization Module 1.0
   magnolia-module-webdav 1.0.1
   magnolia-rendering 4.5-beta4
   magnolia-templating 4.5-beta4
   magnolia-templating-samples 4.5-beta4
   Magnolia Tools Project 1.1.2
   Magnolia Tools Project 1.1.2

This list, afaicr, is built from the project's direct dependencies. (so in this case I'd expect Tomcat, ee-webapp, and add-ons)

Here are some issues:

1. Inclusion of -core, -gui, -rendering, -templating: in the past, since these were transitive deps from the webapp, they were not included in the list. Note that not all "main project" artifacts are in the list, which is really what makes it wrong. Either none should be included (we only like ee-webapp), or all.
2. LDAP - magnolia-ldap is the main jar, -tester is a separate tool, and -bundle bundles both of these. How come both are listed ?
3. Newsletter - same thing - how come both the bundle and its components are both listed ?
4. Tools - twice ? I suspect this is because two different artifacts (i.e with a different groupId:artifactId) have the same <name>, which is a mistake.

Additionally, it'd be nice if we started having "nice names" for our projects, consistently, so that such lists are readable and consistent.