Now, since Birt 3.7 has an easier way to use the runtime (just deploy the jars), why is there no maven repository?
Birt contains over 50 dependencies, it\'s ridiculous.<
It looks like someone took the burden:
http://mvnrepository.com/artifact/org.ow2.orchestra.eclipse.birt
You can find another workaround here: http://hartmann-schneevoigt.com/2012/04/04/eclipse-birt-3-7-2-with-maven/
Basically, in this solution / workaround the birt
artifacts were uploaded to a local artifact proxy using maven-eclipse-plugin
and then used as normal maven dependencies, as you would do in general.
All necessary pom snippets and commands are provided, so this should be a short task.
Below maven dependency worked for me perfectly.
<repositories>
<repository>
<id>sonatype-nexus-releases</id>
<name>Sonatype Nexus Releases</name>
<url>https://oss.sonatype.org/content/repositories/releases/</url>
</repository>
</repositories>
http://wiki.eclipse.org/Maven_Tools_4_Eclipse might help.
There is this: maven.eclipse.org The official maven repository from eclipse, it even uses dependencies from maven central.
Now it narrows down to: Why is BIRT 3.7 not in eclipse 3.7?
Please note that the artifacts present in Maven Central (http://mvnrepository.com/artifact/org.ow2.orchestra.eclipse.birt) are incomplete: for example, they are missing the PDF emitter.
That means you cannot produce PDF, a serious drawback for a reporting engine, IMO.