Failure to maven-deploy Kauri (to non-default repository?)

[bruno]

When I try to deploy Kauri to alternative repository, as is described here for Lily:

​http://docs.outerthought.org/lily-docs-trunk/422-lily/418-lily.html

I run into an, at first sight, strange error about a failure of building the deploy plugin configuration at the kauri-tutorial-myblog project.

Further investigation learns that kauri-tutorial-myblog is a child-module of the Kauri Maven project, but that the reverse relation is not set: kauri-tutorial-myblog does not have a <parent>.

So while kauri-tutorial-myblog will be included in the build, it does not inherit configuration from the parent, leading to the problem I encountered (I wonder if it does not give the same problem for a normal Kauri deploy, as in the recent release?).

Excluding kauri-tutorial-myblog from the modules allowed me to work around the problem.

[mpo]

good catch!

Don't know about how things went during 04-rc release (maybe Freya can chime in)
The steps we follow are described here: ​http://docs.outerthought.org/kauri-docs-0_4/g2/128-kauri.html

They don't mention an explicit mvn deploy, but I do believe the mvn release will include a deploy. In any case the 04-rc jars seem to be present on ​http://kauriproject.org/maven/maven2/deploy/org/kauriproject
(No entry for the tutorial however)

As for what to do about it I'm still thinking:

• the myblog should IMHO not inherit from the kauri parent, since this should show as good as possible what end-user projects should look like.
• on the contrary: listing it as a module (mvn terminology, not kauri!) for the mvn-multi-module build is of course handy not to forget it during build
• surely we want the samples to be available in the distro as well, so having them included in the build somewhere does make sense. (Note their presence in the distro should be source, not the mvn build artifact IMHO)
• However, during deploy I really think all contents of the [svn]/samples/ should be excluded, no? (I see no reason why we should put those artifacts on the repo, or am I missing something?)

Dunno if mvn has subtle settings to allow for this, but IMHO this is what we should try to achieve, no?

(And not to forget: if needed adapt the release building instructions accordingly)

[bruno]

Yes, the ability to skip these modules would be perfect.

Found this:
​http://maven.apache.org/plugins/maven-deploy-plugin/faq.html

Quote:

I don't want to deploy one of the artifacts in my multi-module build. Can I skip deployment?

    Yes, you can skip deployment of individual modules by configuring the Deploy Plugin as follows:

                 <plugin>
                   <artifactId>maven-deploy-plugin</artifactId>
                   <version>X.Y</version>
                   <configuration>
                     <skip>true</skip>
                  </configuration>
                </plugin>

[mpo]

lovely,

except that even if skip=true the deploy-target-repo should be declared in the pom:

  <distributionManagement>
    <repository>
      <id>fake</id>
      <url>but needed to skip deploy anyway</url>
    </repository>
  </distributionManagement>

anyways, commit underway...

[mpo]

(In [1696]) fixes #359 which rightfully states that we don't need to deploy the artifacts in the samples