[
https://issues.apache.org/jira/browse/AXIS2-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-4290.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.6
> Repository updatePolicies are inverted
> --------------------------------------
>
> Key: AXIS2-4290
> URL: https://issues.apache.org/jira/browse/AXIS2-4290
> Project: Axis2
> Issue Type: Bug
> Components: samples, build,site
> Affects Versions: nightly
> Reporter: Jason Fager
> Assignee: Andreas Veithen
> Fix For: 1.6
>
>
> In axis2 parent's pom.xml, in the repositories section, the updatePolicies
> for releases/snapshots is reversed from what one would expect.
> One would expect releases to be pegged at never (or at least less frequent)
> update policy, while snapshots would be always (or at least more frequent).
> This is because a release should be considered a static thing, and there
> should be no reason to update it once it's in a user's local repository,
> while snaps could be updated frequently.
> Maybe repositories shouldn't be kept in the pom at all. The end user can
> always configure repos on their own machine; if there are concerns that a
> user wouldn't be able to download their needed deps from their already
> configured locations, instructions on how to update their settings could be
> provided. This would allow the user to decide their own update policies and
> would reduce the clutter of the pom file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
