Please publish Defense4All artifacts so they can be included in Simultaneous Release Vehicles


Ed Warnicke (eaw) <eaw@...>
 

Guys,
Right now there are no artifacts for groupid org.opendaylight.defense4all in nexus.opendaylight.org,
which means I can't include them in the Release Vehicle (what we will actually be releasing)  builds I'm doing in the integration project.
Looking at your pom.xml files, this appears to be because they are using groupId controlapps and not org.opendaylight.defense4all
and thus your Jenkin's Merge Job will not have appropriate rights to deploy them to Nexus.  If you could please correct this, and 
make sure that your merge job is properly pushing artifacts to Nexus:


I would be happy to include you in the Virtualization Edition :)

Ed


Ed Warnicke (eaw) <eaw@...>
 

Resending to defense4-all as original was bounced because I wasn't subscribed.

Ed

On Oct 1, 2013, at 3:57 PM, Ed Warnicke (eaw) <eaw@...> wrote:

Guys,
Right now there are no artifacts for groupid org.opendaylight.defense4all in nexus.opendaylight.org,
which means I can't include them in the Release Vehicle (what we will actually be releasing)  builds I'm doing in the integration project.
Looking at your pom.xml files, this appears to be because they are using groupId controlapps and not org.opendaylight.defense4all
and thus your Jenkin's Merge Job will not have appropriate rights to deploy them to Nexus.  If you could please correct this, and 
make sure that your merge job is properly pushing artifacts to Nexus:


I would be happy to include you in the Virtualization Edition :)

Ed