maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@codehaus.org
Subject [jira] Updated: (MAVEN-1081) maven.mode.online=true not specified in 1.0 CVS build
Date Mon, 15 Dec 2003 04:27:22 GMT
The following issue has been updated:

    Updater: Brett Porter (mailto:brett@codehaus.org)
       Date: Sun, 14 Dec 2003 10:26 PM
    Changes:
             timeoriginalestimate changed from 60
             timeestimate changed from 1 minute
             Fix Version changed to 1.0-rc2
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1081&page=history

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1081


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1081
    Summary: maven.mode.online=true not specified in 1.0 CVS build
       Type: Bug

     Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
 Components: 
             core
   Fix Fors:
             1.0-rc2
   Versions:
             1.0-rc2

   Assignee: Brett Porter
   Reporter: John Casey

    Created: Sat, 13 Dec 2003 10:31 PM
    Updated: Sun, 14 Dec 2003 10:26 PM
Environment: linux; clean filesystem (no previous maven builds), with maven CVS MAVEN-1_0-BRANCH
checked out.

Description:
when trying to build maven on a new filesystem - with no previous version installed - the
build process fails in the very beginnings of the plugins build step, due to missing commons-jelly-tags-velocity
and velocity artifacts. This is not immediately apparent, however. Instead, the build process
bombs out with an UnsatisfiedDependencyException, citing the above dependencies as missing
the download URL...

After some investigation, I discovered that maven.mode.online didn't appear to have a default
value. I'm not sure whether this should be specified or whether the default value in the code
itself should be true. If this is the intended behavior (if the user needs to specify this
in the build.properties), then feedback is essential during the build process.

I will attach a patch which specifies maven.mode.online=true in the defaults.properties file,
since this is a little easier than hard-coding the true default into the code. It is also
consistent with other property specifications.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message