Thanks! I did try to do that for several days until I was able to get some
help from the retrotranslator developers.
It seemed that there were enough dependencies on other sandbox items that I
just couldn't get this approach to work. So the developer said I needed to
include a pointer to the snapshot plugin repository. Which I am very eager
to take out when and if retrotranslator is taken out of the sandbox.
Am I needing to trace all the transitive sandbox dependencies and install
them as well? It seems that plugins get pulled from a different repository
by default, since they do seem to get their own POM entry.
Given the way things work, I probably won't ever point to the snapshot
plugin repository ever again! I wasn't comfortable with it when the
developer recommended it, and now I know why it's not terribly functional
unless you don't plan to do a release.
Harold
dan tran wrote:
>
> a release of retrotranslator plugin is imminent it has all the votes to
> be
> released last week.
> Now it is up the owner to put time in.
>
> In the mean while, you can cut a release of this plugin yourself , by
> deploying it
> to your yr internal remote repo using a unique version of your own.
>
> I usually append the current svn revision number to the version so that I
> can refer back.
> (ie 1.0-alpha-1-2422 )
>
> Strongly suggest that you get used to this, since expecting an immediate
> release of public
> plugin is quite impossible.
>
> -D
>
>
>
>
> On 9/28/06, shinsato <[EMAIL PROTECTED]> wrote:
>>
>>
>> We're using the retrotranslator plugin, which unfortunately isn't
>> released
>> yet. It's still in the sandbox. Which breaks the release plugin (which
>> we
>> discover the day before we have to get our first ever maven executed
>> release
>> out).
>>
>> Is there any way around this at all? I'm a bit new to maven2 still, and
>> when I tried to do an internal release of retrotranslator, it was an
>> exercise in frustration.
>>
>> Hopefully someone knows some possible way around this. If not, does
>> anyone
>> have an idea how to get such a release accomplished. There were snapshot
>> dependencies as well. Is this going to require releasing every
>> transitive
>> dependency too? Please say there's a short cut around this...
>>
>> Thanks in advance,
>> Harold Shinsato
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Any-way-to-release-with-snapshot-dependency--tf2354831.html#a6558929
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Any-way-to-release-with-snapshot-dependency--tf2354831.html#a6567307
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
