[STREAMS-359] copy streams-master pom into streams-project as CI workaround

• Type: Task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 0.3
• Assignee: Steve Blackmon
• Reporter: Steve Blackmon
• Created: 28/Aug/15 20:26
• Updated: 04/Oct/16 15:36
• Resolved: 02/Mar/16 16:47

Description

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.