Note that there are some explanatory texts on larger screens.

plurals
  1. POResolving snapshot versions of Grails plugins (deployed using the maven-publisher plugin)
    text
    copied!<p>Good day,</p> <p>I'm trying to integrate our company's Grails plugins into our Maven repositories (our repositories are named 'snapshots' and 'releases').</p> <p>To do that, I installed the maven-publisher plugin in all of our plugins, and I'm deploying them using the "grails maven-deploy" command. This works well.</p> <p>However, if I deploy a SNAPSHOT version of a plugin (say, version 1.0.0-SNAPSHOT), it gets properly deployed in our repository, but I can't install it in our applications (using version "latest.integration").</p> <p>I'm using Grails 1.3.7.</p> <p>First of all, when deployed, the actual artifact name has a timestamp added to it ("blablabla-1.0.0-20110421.122823-1.zip"). However, the version is still 1.0.0-SNAPSHOT. I'm guessing that it's Maven that does that transformation.</p> <p>However, Ivy doesn't seem to understand the transformation, or to handle SNAPSHOT versions. I get errors like:</p> <pre><code>==== http://myRepo/repository/snapshots: tried -- artifact myOrg#blablabla;latest.integration!blablabla.zip: http://myRepo/repository/snapshots/myOrg/blablabla/[revision]/blablabla-[revision].zip </code></pre> <p>Initial research has revealed that I could create a resolver pattern, but that seems a little bit complicated for something that should work out of the box, and my initial tests were not conclusive anyway (I tried a few patterns, none of which worked).</p> <p>I should note that deploying my plugins locally using the "maven-install" command works, because the script create an artifact with the proper version (blablabla-1.0.0-SNAPSHOT.zip) alongside the one with timestamps.</p> <p>Does anybody have a solution?</p> <p>Thanks!</p> <p>Guillaume.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload