clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Minto van der Sluis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLEREZZA-779) Jenkins build failure due to wink snapshot and obsolete jaxrs.testutils
Date Tue, 07 May 2013 12:21:16 GMT

     [ https://issues.apache.org/jira/browse/CLEREZZA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Minto van der Sluis updated CLEREZZA-779:
-----------------------------------------

    Description: 
Jenkins build fails due to: 
[WARNING] The POM for org.apache.wink:wink-osgi:jar:1.3.0-SNAPSHOT is missing, no dependency
information available

and

[WARNING] The POM for org.apache.clerezza:jaxrs.testutils:jar:0.10-incubating-20121111.020652-15
is invalid, transitive dependencies (if any) will not be available, enable debug logging for
more details

  was:Jenkins build fails due to: [WARNING] The POM for org.apache.wink:wink-osgi:jar:1.3.0-SNAPSHOT
is missing, no dependency information available

        Summary: Jenkins build failure due to wink snapshot and obsolete jaxrs.testutils 
(was: Upgrade wink dependency to latest release (1.3.0-SNAPSHOT --> 1.3.0))
    
> Jenkins build failure due to wink snapshot and obsolete jaxrs.testutils
> -----------------------------------------------------------------------
>
>                 Key: CLEREZZA-779
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-779
>             Project: Clerezza
>          Issue Type: Dependency upgrade
>            Reporter: Minto van der Sluis
>            Assignee: Minto van der Sluis
>
> Jenkins build fails due to: 
> [WARNING] The POM for org.apache.wink:wink-osgi:jar:1.3.0-SNAPSHOT is missing, no dependency
information available
> and
> [WARNING] The POM for org.apache.clerezza:jaxrs.testutils:jar:0.10-incubating-20121111.020652-15
is invalid, transitive dependencies (if any) will not be available, enable debug logging for
more details

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message