« Return to Thread: Releases In the Trash!?
Re: Releases In the Trash!?
by MALICE
::
Rate this Message:
I'm not using the same version as they are. For instance my colleague has
been developing the maven-eclipse-plugin and we would deploy our internal
versions as "2.3-CFC-<date>". Then when his changes were merged into the
new release, we would update our POMs to use 2.4 instead of
2.3-CFC-<date>.
So, there would be no conflicts and no SNAPSHOT dependencies...
Roland
> You shouldn't use the same version as they would to avoid potential
> conflicts, thus you would want to maintain your internal release in case
> you
> need to rebuild a tag. I have some thoughts on that here:
> http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/
>
>
> On Tue, Jun 2, 2009 at 5:54 PM, Roland Asmann <Roland.Asmann@...>
> wrote:
>
>> Just wondering here... Could this be used as a feature? In my company
>> this
>> would be great behavior on our 'fix' repository... Here we upload
>> libraries and/or plugins that had some bugs and we fixed ourselves.
>> Until
>> they are released by the respective owners, we use them, after official
>> release, we should delete them. However, if they are automatically
>> deleted
>> when not requested, we can be sure they are deleted if we forget!
>>
>> Just my thoughts on this. If it is left in, it should of course be
>> documented and be used with caution...
>>
>>
>> > We confirmed that it is the evict task and apparently has been broken
>> for
>> > a
>> > while. See my other thread for the url.
>> >
>> > On Tue, Jun 2, 2009 at 11:56 AM, Stephen Duncan Jr
>> > <stephen.duncan@...
>> >> wrote:
>> >
>> >> I'm more paranoid than that; for now I have all tasks disabled. :)
>> >>
>> >> It was set to All Repositories, because I want it set to all
>> >> proxy-repos,
>> >> but there's no multi-select, and I certainly didn't want to schedule
>> >> each
>> >> proxy-repo individually...
>> >>
>> >> On Tue, Jun 2, 2009 at 2:49 PM, Brian Fox <brianf@...>
>> wrote:
>> >>
>> >>> We think the purge unused artifacts task might be the culprit but
>> the
>> >>> code
>> >>> in question hasn't changed in over a year. We're still evaluating
>> it,
>> >>> but
>> >>> make sure you have selected only proxy repos in the task config
>> until
>> >>> we
>> >>> confirm.
>> >>>
>> >>>
>> >>
>> >> --
>> >> Stephen Duncan Jr
>> >> www.stephenduncanjr.com
>> >>
>> >
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: nexus-user-unsubscribe@...
>> For additional commands, e-mail: nexus-user-help@...
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...
been developing the maven-eclipse-plugin and we would deploy our internal
versions as "2.3-CFC-<date>". Then when his changes were merged into the
new release, we would update our POMs to use 2.4 instead of
2.3-CFC-<date>.
So, there would be no conflicts and no SNAPSHOT dependencies...
Roland
> You shouldn't use the same version as they would to avoid potential
> conflicts, thus you would want to maintain your internal release in case
> you
> need to rebuild a tag. I have some thoughts on that here:
> http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/
>
>
> On Tue, Jun 2, 2009 at 5:54 PM, Roland Asmann <Roland.Asmann@...>
> wrote:
>
>> Just wondering here... Could this be used as a feature? In my company
>> this
>> would be great behavior on our 'fix' repository... Here we upload
>> libraries and/or plugins that had some bugs and we fixed ourselves.
>> Until
>> they are released by the respective owners, we use them, after official
>> release, we should delete them. However, if they are automatically
>> deleted
>> when not requested, we can be sure they are deleted if we forget!
>>
>> Just my thoughts on this. If it is left in, it should of course be
>> documented and be used with caution...
>>
>>
>> > We confirmed that it is the evict task and apparently has been broken
>> for
>> > a
>> > while. See my other thread for the url.
>> >
>> > On Tue, Jun 2, 2009 at 11:56 AM, Stephen Duncan Jr
>> > <stephen.duncan@...
>> >> wrote:
>> >
>> >> I'm more paranoid than that; for now I have all tasks disabled. :)
>> >>
>> >> It was set to All Repositories, because I want it set to all
>> >> proxy-repos,
>> >> but there's no multi-select, and I certainly didn't want to schedule
>> >> each
>> >> proxy-repo individually...
>> >>
>> >> On Tue, Jun 2, 2009 at 2:49 PM, Brian Fox <brianf@...>
>> wrote:
>> >>
>> >>> We think the purge unused artifacts task might be the culprit but
>> the
>> >>> code
>> >>> in question hasn't changed in over a year. We're still evaluating
>> it,
>> >>> but
>> >>> make sure you have selected only proxy repos in the task config
>> until
>> >>> we
>> >>> confirm.
>> >>>
>> >>>
>> >>
>> >> --
>> >> Stephen Duncan Jr
>> >> www.stephenduncanjr.com
>> >>
>> >
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: nexus-user-unsubscribe@...
>> For additional commands, e-mail: nexus-user-help@...
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...
« Return to Thread: Releases In the Trash!?
| Free embeddable forum powered by Nabble | Forum Help |
