On Fri, Oct 16, 2009 at 9:18 PM, Peter Janes
wrote:
> On 16/10/09 11:45 AM, Stephen Connolly wrote:
>>
>> 2009/10/16 Peter Janes
>>
>>> On 15/10/09 05:45 AM, Stephen Connolly wrote:
>>>
These are very dangerous versions to suggest use of.
>>>
>>> ...but there *are* use cases for them.
>>
>> W
2009/10/16 Peter Janes
> On 16/10/09 11:45 AM, Stephen Connolly wrote:
>
>> 2009/10/16 Peter Janes
>>
>> On 15/10/09 05:45 AM, Stephen Connolly wrote:
>>>
>>> These are very dangerous versions to suggest use of.
>>>
>>> ...but there *are* use cases for them.
>>>
>>
>> When your use case re
On 16/10/09 11:45 AM, Stephen Connolly wrote:
2009/10/16 Peter Janes
On 15/10/09 05:45 AM, Stephen Connolly wrote:
These are very dangerous versions to suggest use of.
...but there *are* use cases for them.
When your use case results in a completely unpredictable build... no thank
you.
F
2009/10/16 Benjamin Bentmann
> Stephen Connolly wrote:
>
> maven-deploy-plugin updates the metadata whenever there is a deploy...
>> e.g.
>>
>> it sets the /metadata/versioning/latest to the version that is has just
>> deployed. and if the version is not a SNAPSHOT, it sets the
>> /metadata/ver
2009/10/16 Peter Janes
> On 16/10/09 11:45 AM, Stephen Connolly wrote:
>
>> 2009/10/16 Peter Janes
>>
>> On 15/10/09 05:45 AM, Stephen Connolly wrote:
>>>
>>> These are very dangerous versions to suggest use of.
>>>
>>> ...but there *are* use cases for them.
>>>
>>
>> When your use case re
Stephen Connolly wrote:
2009/10/16 Peter Janes
On 15/10/09 05:45 AM, Stephen Connolly wrote:
These are very dangerous versions to suggest use of.
...but there *are* use cases for them.
When your use case results in a completely unpredictable build... no thank
you.
For dependencies, use
2009/10/16 Peter Janes
> On 16/10/09 11:47 AM, Stephen Connolly wrote:
>
>> 2009/10/16 Peter Janes
>>
>> However, I'm not aware of any released version of Maven or any plugin
>>> that
>>> actually treats dependencies this way; Mercury, tested through
>>> versions-maven-plugin, doesn't appear to
On 16/10/09 11:45 AM, Stephen Connolly wrote:
2009/10/16 Peter Janes
On 15/10/09 05:45 AM, Stephen Connolly wrote:
These are very dangerous versions to suggest use of.
...but there *are* use cases for them.
When your use case results in a completely unpredictable build... no thank
you.
F
On 16/10/09 11:47 AM, Stephen Connolly wrote:
2009/10/16 Peter Janes
However, I'm not aware of any released version of Maven or any plugin that
actually treats dependencies this way; Mercury, tested through
versions-maven-plugin, doesn't appear to either. (But I'd love to be proven
wrong!)
Stephen Connolly wrote:
maven-deploy-plugin updates the metadata whenever there is a deploy...
e.g.
it sets the /metadata/versioning/latest to the version that is has just
deployed. and if the version is not a SNAPSHOT, it sets the
/metadata/versioning/release as well.
Actually, it's a littl
2009/10/16 Stephen Connolly
> 2009/10/16 Peter Janes
>
>> However, I'm not aware of any released version of Maven or any plugin
>> that actually treats dependencies this way; Mercury, tested through
>> versions-maven-plugin, doesn't appear to either. (But I'd love to be proven
>> wrong!)
>>
>
2009/10/16 Peter Janes
> However, I'm not aware of any released version of Maven or any plugin that
> actually treats dependencies this way; Mercury, tested through
> versions-maven-plugin, doesn't appear to either. (But I'd love to be proven
> wrong!)
>
versions-maven-plugin does not use merc
2009/10/16 Peter Janes
> On 15/10/09 05:45 AM, Stephen Connolly wrote:
>
>> These are very dangerous versions to suggest use of.
>>
>
> ...but there *are* use cases for them.
When your use case results in a completely unpredictable build... no thank
you.
For dependencies, use version ranges.
On 15/10/09 05:45 AM, Stephen Connolly wrote:
These are very dangerous versions to suggest use of.
...but there *are* use cases for them.
These are deprecated and are only "special" versions when considering
plugins... and they do not behave as you think they behave.
For what it's worth, th
t reliable (at least should be, but never tried that behaviour of
> the release-plugin myself, anyone?)
>
> LieGrue,
> strub
>
>
>
> - Original Message
> > From: gerhard presser
> > To: dev@maven.apache.org
> > Sent: Thu, October 15, 2009 8:59:3
; --
> View this message in context:
> http://www.nabble.com/fetching-latest-release-of-an-artifact-tp25903867p25903867.html
> Sent from the Maven Developers mailing list archive at Nabble.com.
>
>
> -
> To unsubs
gerhard presser wrote:
because of that i want to fetch the last release of my artifact.
how can i do that. i'm playing around with ArtifactResolver,
ArtifactMetadataSource etc.
is this the right way?
Yes, [0] and [1] could provide further hints on using those components.
IIRC, the artifact re
never tried that behaviour of
the release-plugin myself, anyone?)
LieGrue,
strub
- Original Message
> From: gerhard presser
> To: dev@maven.apache.org
> Sent: Thu, October 15, 2009 8:59:32 AM
> Subject: fetching latest release of an artifact
>
>
> hi all!
> i&
View this message in context:
http://www.nabble.com/fetching-latest-release-of-an-artifact-tp25903867p25903867.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: de
19 matches
Mail list logo
