(I have updated my super pom accordingly, thanks, Ive not re-run the release since, but I can do if you think this is the root cause of the problem)
My reactor output is as follows: [INFO] Reactor build order: [INFO] Main ß Main super pom [INFO] commons [INFO] sql_runner [INFO] db_data_extractor [INFO] backup [INFO] text_processing [INFO] db_field_categoriser [INFO] db_field_cleaner [INFO] downloader_commons [INFO] downloader_client [INFO] downloader_server [INFO] flat_file_patent_parsing [INFO] file_comparator [INFO] validation_tool [INFO] max_value_finder [INFO] xml_file_patent_parsing [INFO] record_counter [INFO] Jar Signer ß my custom maven signing plugin (used in research_client module) [INFO] linked_file_downloader [INFO] web_based_app_delivery ß a new war project [INFO] research_commons [INFO] research_client ß uses obfuscation, my jar signing and jnlp webstart plugins [INFO] research_discrepancy_tool [INFO] workflow_server ß depended upon module [INFO] workflow_client ß module that fails (depends on workflow_server) >From looking at the output, it seems as though several passes over the build are performed, on the earlier passes the compile, jar and install steps are performed, so I get the following messages for other modules: [INFO] [INFO] Installing C:\temp\trunk\linked_file_downloader\target\linked_file_downloader-2.3.30-pa ckage-release.zip to C:\Documents and Settings\jbowkett\.m2\repository\com\..\downloader\linkedfile\linked_file_do wnloader\2.3.30\linked_file_downloader-2.3.30-package-release.zip The build falls over when building the workflow_client module (as it requires the workflow_server module). The workflow_server was built directly before, but I dont get the install message for this module, even though it has been built and a package prepared for it. Why is the build repeated, and moreover, why is the workflow_server excluded from that first round which includes the install:install step? Thanks for your help on this, -James On 26/02/2009, at 2:09 AM, James Bowkett wrote: > I have tried adding <preparationGoals>clean install > deploy</preparationGoals> you should only need "clean install" here, firstly deploy runs install as well so this doubles up, and secondly you don't want to deploy on preparation, just on perform. > > I have recently done quite a lot of new development between the last > release > and this one....some of which comprising a custom maven plugin, the > webstart > jnlp plugin, and the proguard obfuscator plugin This sounds related - the explanation of your problem makes it sounds like one of the required modules is not in the build process. Does it get listed in the reactor when the build kicks off? - Brett
