You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Henning Schmiedehausen (JIRA)" <de...@velocity.apache.org> on 2007/01/11 18:28:28 UTC
[jira] Reopened: (VELOCITY-502) Skip jar verification unless
"force.jar.loading" is true
[ https://issues.apache.org/jira/browse/VELOCITY-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Schmiedehausen reopened VELOCITY-502:
---------------------------------------------
Assignee: Henning Schmiedehausen (was: Claude Brisson)
> Skip jar verification unless "force.jar.loading" is true
> --------------------------------------------------------
>
> Key: VELOCITY-502
> URL: https://issues.apache.org/jira/browse/VELOCITY-502
> Project: Velocity
> Issue Type: Improvement
> Components: Build
> Affects Versions: 1.5 beta2
> Environment: all
> Reporter: Claude Brisson
> Assigned To: Henning Schmiedehausen
> Priority: Minor
> Fix For: 1.5
>
> Attachments: jar-downloading.patch
>
>
> When the www.iblibo.org/maven repository is down (as it seems right now, at least from here), or when you want to work form an unconnected place (yes, it still exists...), build fails because ant wants to check every jar timestamp.
> The attached patch modifies this behaviour: if a jar file is already present, the repository is not hit at all (why would we have to check any timestamp anyway since version numbers are present inside filenames?!).
> The new force.jar.loading property forces reloading of jar files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org