[webbeans-issues] [JBoss JIRA] Commented: (WBRI-219) Use SNAPSHOT policy never for all SNAPSHOT dependencies

Pete Muir (JIRA) jira-events at lists.jboss.org
Mon Apr 6 09:35:21 EDT 2009


    [ https://jira.jboss.org/jira/browse/WBRI-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460732#action_12460732 ] 

Pete Muir commented on WBRI-219:
--------------------------------

Ondre, I have created this JIRA issue as I can't actually get into Hudson atm ;-)

> Use SNAPSHOT policy never for all SNAPSHOT dependencies
> -------------------------------------------------------
>
>                 Key: WBRI-219
>                 URL: https://jira.jboss.org/jira/browse/WBRI-219
>             Project: Web Beans
>          Issue Type: Bug
>         Environment: generic
>            Reporter: Sahoo Sahoo
>            Assignee: Pete Muir
>            Priority: Minor
>             Fix For: 1.0.0.PREVIEW
>
>
> Current pom.xmls in webbeans/ri/trunk have quite a few SNAPSHOT dependency. e.g., jsr299-tck-impl. Imagine a developer doing this:
> day 1: svn up, mvn clean install // This refreshed maven-repo-local with a new copy of jsr299-tck-impl
> day 2: mvn install // This again brings a newer copy of jsr299-tck-impl. 
> Who guarantees that the latest copy of jsr299-tck-impl is compatible with svn rev corresponding to previous day? Nobody.
> So, I suggest the SNAPSHOT update policy be set to NEVER so that user can run mvn -U when they refresh the workspace.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the weld-issues mailing list