 |
 |
Hi, An addendum to previous message... If you did ‘mvn post-clean’ once then all subsequent ‘mvn install’ commands should work fine on that package. So I think the best suggestion here is that instead of executing the ‘clean’ goal use ‘post-clean’ instead because that executes ‘clean’ also. Long term though this isn’t the greatest solution because ‘post-clean’ is not the proper goal to find to here. But all other solutions I have found online for the ‘lifecycle’ error have their own complications unfortunately. —Jeremy On Mar 27, 2014, at 1:11 PM, McCormick, Jeremy I. <[log in to unmask]> wrote: > Hi, > > I’m working on a fix up for this annoying “lifecycle not covered by plugin execution” error reported by Eclipse which causes all my projects to be marked as having errors. I know others have seen this too. > > Pardon me while I bore you with Maven talk... > > I committed the simple fix, which has introduced another issue, albeit a minor and solvable one. > > The problem is that Eclipse doesn’t want to bind the antrun plugin to the generate-test-resources phase but it will accept post-clean. (No idea why this is.) > > So I found a solution which suggested binding the antrun plugin to post-clean, which is a very easy fix for this problem, but this introduces another issue. > > If you don’t execute post-clean before a fresh build then some of the modules will fail (namely a test case in tracking) because they depend on post-clean being executed to setup a directory for them where output test files go. > > The easiest solution is always executing ‘post-clean install’ which I have made the default when you type ‘mvn’ without any arguments now in the parent. > > If you are doing manually something like ‘mvn install’, then do ‘mvn post-clean install’ instead to make sure this error is avoided. > > This also has the somewhat undesirable side effect that every build is executing clean which means it is compiling all the source files in the module, but this doesn’t seem too bad to me. The modules (now that they are all small!) compile very quickly from scratch. > > Anyways, I will look at a better solution for this which preserves incremental builds (will probably be more complicated), but in the meantime the annoying “lifecycle” error in Eclipse should disappear. > > —Jeremy > ######################################################################## > Use REPLY-ALL to reply to list > > To unsubscribe from the HPS-SOFTWARE list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the HPS-SOFTWARE list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1