[ https://issues.apache.org/jira/browse/STREAMS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Blackmon resolved STREAMS-359. ------------------------------------ Resolution: Fixed Resolved. Root cause resolved as well. > copy streams-master pom into streams-project as CI workaround > ------------------------------------------------------------- > > Key: STREAMS-359 > URL: https://issues.apache.org/jira/browse/STREAMS-359 > Project: Streams > Issue Type: Task > Reporter: Steve Blackmon > Assignee: Steve Blackmon > Priority: Blocker > > I've been trying for months to get someone to fix the problem messing > up our Jenkins/Travis setup without success. BUILDS-88 is the related > open issue. > Details: > a) streams has a master pom which contains most of the standard > dependency and plugin management details. > b) incubator-streams and incubator-streams-examples both depend on > incubator-streams-master, greatly reducing duplication between their > poms. > c) however this means that neither incubator-streams and > incubator-streams-examples can build their SNAPSHOTs without resolving > the incubator-streams-master SNAPSHOT > d) something wrong in the jenkins/repository.a.o setup is refusing > deployment of SNAPSHOT artifacts. > e) thus every push and every PR to incubator-streams and > incubator-streams-examples appears broken > As beneficial as a having a master pom is, being able to keep a > functioning CI system and perform releases is more important. > Copy incubator-streams-master/pom.xml into incubator-streams/pom.xml and > incubator-streams-examples/pom.xml so CI starts working again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)