The 2.3.3 source is now available.

Fixed for 2.4.5 and was backported to 2.4.4.

The source release for 2.4.4 is now available.

If you have the appropriate license, you can download the source release here:
http://www.atlassian.com/software/confluence/ConfluenceSourceDownloads.jspa

Refer to the documentation of the source release here:
http://confluence.atlassian.com/display/DOC/Customise+Confluence+Source+Code

Please update http://confluence.atlassian.com/display/DOC/Customise+Confluence+Source+Code when patched

This also a major show-stopper in my organization, too (license for 500 users).

For our Confluence 2.2.x installation I developed a build system which patches the Confluence source release with some custom patches, configures confluence-init.properties, copies over some custom and 3rd-party plugins to be included in WEB-INF/lib of Confluence webapp and finally creates a deployable war with maven1 target war:war. It worked (well still works for 2.2, of course) great.

Now there's pressure to upgrade to Confluence 2.4. I want to do similar build setup with Confluence 2.4. I can build the confluence jar with the new Maven2 setup ok (mvn -Dmaven.test.skip jar:jar), tested with 2.4.2. I've also converted the build system of our custom plugins to use atlassian-pdk for Maven2 (it works nicely, thanks, though it looks like you haven't integrated updating of the Maven2 repository automatically with your Confluence release process as the repository looks like to be out of date, currently of official 2.4 releases the latest in repository is 2.4.2 though 2.4.4 is the latest released version but I guess a new issue should be created for this discussion) instead of using custom ant build.xml hack that we've been using. However, building the war (mvn -Dmaven.test.skip war:war) fails due to the fact that handling of webapp resources is somehow broken.

PLEASE fix the source release ASAP so that running a simple Maven2 target (war:war, package, what ever) in freshly untarred confluence-$VERSION-source/confluence produces effectively the same confluence-$VERSION.war that can be created with the confluence-$VERSION/build.sh script of the official binary release. Thanks.

Users who are waiting for this issue to be resolved so that they can compile their custom plugin on Confluence 2.3 have a workaround available:

1. If you haven't got the standalone version of Confluence, please download it.
2. Unpack the standalone
3. Now copy your plugin source to the 'plugins' folder in the standalone directory (try to make sure that your plugin is structured similarly to the other plugins)
4. Build your plugin by running:

> ant build -Dlibrary=<name of your plugin>

davidsoul your support specialist thinks that this is the same reason why we cannot compile our plugin under 2.3 or 2.4 if this is so this is a show stopper for us. We have a commercial license with more than 2700 users. Our user need the features in 2.3 and we cannot go there because we have a plugin that MUST be recompiled under 2.3.

I see that this issue is 13 days old. THIS MUST BE FIXED ASAP. If your customers cannot upgrade their plugin along with your software then your software upgrade is useless and so is their annual license.