[ http://jira.codehaus.org/browse/MSUREFIRE-94?page=comments#action_64014 ]
Milos Kleint commented on MSUREFIRE-94: --------------------------------------- well, I haven't checked the netbeans sources but doubt this has anything to with netbeans. Smells more like ant issue. While netbeans module can separate concerns with classloaders to prevent clashes, in similar manner as maven does, I'm afraid the system properties bypass these mechanisms. I agree that rollbacking to the state before is probably the only workable solution. There still will be a time slot with "wrong" property values, but the probability of anything failing is significantly reduced. > settting System property "basedir" is evil. > ------------------------------------------- > > Key: MSUREFIRE-94 > URL: http://jira.codehaus.org/browse/MSUREFIRE-94 > Project: Maven 2.x Surefire Plugin > Type: Bug > Environment: maven 2.1-snapshot embedder, latest surefire plugin, Netbeans > IDE. > Reporter: Milos Kleint > Priority: Blocker > Fix For: 2.2 > > > when running in embedded environment, the surefire plugin seems to influence > the embedding application by setting system properties, like "basedir". plus > some custom additional per project. > In netbeans, this causes all ant-based projects to stop working after > building a m2 project once. See MEVENIDE-412. > The proper way of setting the environment variables is either not to set them > at all (when building 2 projects at the same time, we can get strange results > as the 2 builds both write the same props but different values) or to reset > them back to whatever the value was previosly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
