Add artifact base target to nexus configuration 65/4965/1
authorAndrew Grimberg <agrimberg@linuxfoundation.org>
Wed, 24 May 2017 00:02:27 +0000 (17:02 -0700)
committerAndrew Grimberg <agrimberg@linuxfoundation.org>
Wed, 24 May 2017 00:02:27 +0000 (17:02 -0700)
commiteb919f27fc7a9e983f3d9537acb160090ffb5627
tree234e64a3a7fd428b9cd81afa62b2670f0a49eaf6
parentc3bf292e964551563b4675a1b39a27d26da66703
Add artifact base target to nexus configuration

Projects should be able to push to $groupId.$artifactId.$extension as
well well as anything under that path. Not allowing this means that our
projects always are having to define a broken pom that may look like:

<groupId>org.example.artifactId</groupId>
<artifactId>artifactId</artifactId>

Which means they always end up deploying a base artifact at
$groupId.$artifactId.$artifactId in many cases.

Change-Id: I11a2bcebfe07d39251d85f92ab783c1a2ed5288c
Signed-off-by: Andrew Grimberg <agrimberg@linuxfoundation.org>
lftools/nexus/cmd.py