You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Milos Kleint (JIRA)" <ji...@codehaus.org> on 2006/04/23 09:24:18 UTC

[jira] Created: (MSUREFIRE-94) settting System property "basedir" is evil.

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


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


[jira] Closed: (MSUREFIRE-94) settting System property "basedir" is evil.

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MSUREFIRE-94?page=all ]
     
Brett Porter closed MSUREFIRE-94:
---------------------------------

     Assign To: Brett Porter
    Resolution: Fixed

> 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
>     Assignee: Brett Porter
>     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


[jira] Commented: (MSUREFIRE-94) settting System property "basedir" is evil.

Posted by "Milos Kleint (JIRA)" <ji...@codehaus.org>.
    [ 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


[jira] Updated: (SUREFIRE-70) settting System property "basedir" is evil.

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/SUREFIRE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated SUREFIRE-70:
---------------------------------

    Fix Version/s: 2.0 (2.2 plugin)

> settting System property "basedir" is evil.
> -------------------------------------------
>
>                 Key: SUREFIRE-70
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-70
>             Project: Maven Surefire
>          Issue Type: Bug
>         Environment: maven 2.1-snapshot embedder, latest surefire plugin, Netbeans IDE.
>            Reporter: Milos Kleint
>         Assigned To: Brett Porter
>            Priority: Blocker
>             Fix For: 2.0 (2.2 plugin)
>
>
> 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

        

[jira] Updated: (MSUREFIRE-94) settting System property "basedir" is evil.

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MSUREFIRE-94?page=all ]

Brett Porter updated MSUREFIRE-94:
----------------------------------

    Fix Version: 2.2

we can't kill it as tests rely on it, but it should be reset afterwards. I'd also consider a bugrep for ant/netbeans on this one - should modules really be able to affect ant-based projects in such a significant way just by setting a simple system property?

> 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