> the bone. Does anyone have a suggestion? BTW, I can run a Maven build > manually on the build server on top of the source pulled over by TFS, and > the manual build works fine. Also, the jar that is read-only is created by > the Maven build. (And it is read-only when built with TFS and not read-only > when built manually.)
Then I would blame TFS for the problem, not Maven. I would pursue TFS support options. Also consider "stupid Windows reasons" for this problem. We see a lot of issues related to files being locked by anti-virus software etc on this list. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
