You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by bo...@werken.com on 2002/12/04 21:00:00 UTC
[maven-bug] Resolved: (MAVEN-135) Incorrect Environment detection in build-bootstrap.xml
Message:
The following issue has been resolved as FIXED.
Resolver: Peter Lynch
Date: Wed, 4 Dec 2002 1:59 PM
I have rewrote the maven.bat script and also I use Cygwin and the 'maven' nix script daily and things appear to be working fine on my Win 2k server system. Therefore time to close this.
---------------------------------------------------------------------
View the issue:
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-135
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-135
Summary: Incorrect Environment detection in build-bootstrap.xml
Type: Bug
Status: Resolved
Priority: Major
Resolution: FIXED
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Component: core
Fix For: 1.0-beta-8
Versions:
1.0-beta-6
Assignee: Jason van Zyl
Reporter: Berin Loritsch
Created: Mon, 7 Oct 2002 4:16 PM
Updated: Wed, 4 Dec 2002 1:59 PM
Environment: Windows 2000/Cygwin
Description:
Building Maven with Cygwin no longer works because of some "OS detection" which does not work properly. Below is the output of
the build and the cuplrit code:
[echo]
[echo] +------------------------------------------------------------------+
[echo] | |
[echo] | B U I L D I N G M A V E N W I T H I T S E L F |
[echo] | |
[echo] +------------------------------------------------------------------+
[echo]
[exec] FIND: /I: No such file or directory
[exec] FIND: /C: No such file or directory
[exec] ERROR: File (C:\maven) MAVEN_HOME not found.
[exec] Please, set the MAVEN_HOME variable in your environment to match the
[exec] location of the Maven installation
clean-maven-home:
[delete] Deleting directory c:\Program Files\maven\bin
[mkdir] Created dir: c:\Program Files\maven\bin
[delete] Deleting directory c:\Program Files\maven\lib
[mkdir] Created dir: c:\Program Files\maven\lib
[delete] Deleting directory c:\Program Files\maven\plugins
[mkdir] Created dir: c:\Program Files\maven\plugins
-----------------------------------------------------
BTW: MAVEN_HOME is set to:
C:\Program Files\maven
It barfs on the space. The code that causes this to happen is:
<exec executable="${maven.home}/bin/${maven.script}" failonerror="true">
<arg line="${maven.bootstrap.online}"/>
<arg line="clean"/>
<arg line="java:jar"/>
</exec>
${maven.script} is set incorrectly to the ".bat" version and not
the ".sh" The condition is incorrectly set:
<!-- make sure we run the correct maven script per os -->
<condition property="maven.script" value="maven.bat">
<and>
<os family="windows" />
<equals arg1="${maven.script}" arg2="$${maven.script}" />
</and>
</condition>
<condition property="maven.script" value="maven">
<equals arg1="${maven.script}" arg2="$${maven.script}" />
</condition>
It is this issue that is causing things to blow up with Cygwin.
You can accurately determine if you are running under a Cygwin
environment by looking at the "TERM" environment variable. If
${TERM}=='cygwin' then you are running Windows under a Cygwin
environment.
Furthermore, there is a problem with spaces in the path name.
Things really choke up if there is a space in the filename (at
least in the shell scripts).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.werken.com/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira