Re: Non-unique Snapshot Deployments is not in Maven 3

[Brian Fox <br...@infinity.nu>]

This use case currently isn't covered, you're right and it's really
the only reason anymore to use non unique snapshots. Bringing this
over to @dev to figure out what to do.

On Mon, Nov 16, 2009 at 3:41 PM, Paul Benedict <pb...@apache.org> wrote:
> I did read the link. I thought Jason was saying Maven's metadata isn't
> "complete" -- that the classifier isn't included in the repository's
> description of the snapshot deployment.
>
> Paul
>
> On Mon, Nov 16, 2009 at 2:38 PM, Dan Tran <da...@gmail.com> wrote:
>> I dont have a solution,  Jason however did propose an alternative
>> metadata handling ( see the discussion link )
>>
>> 0D
>>
>> On Mon, Nov 16, 2009 at 12:28 PM, Paul Benedict <pb...@apache.org> wrote:
>>> So are you asking for the classifier to be part of the snapshot metadata?
>>>
>>> On Mon, Nov 16, 2009 at 1:57 PM, Dan Tran <da...@gmail.com> wrote:
>>>> of course, we must use classifier per platform.
>>>>
>>>> see this link for other fundamental issues when not using non-unique snapshot
>>>>
>>>> http://old.nabble.com/Multi-Platform-snapshots-td25295999.html
>>>>
>>>> -Dan
>>>>
>>>> On Mon, Nov 16, 2009 at 11:53 AM, Paul Benedict <pb...@apache.org> wrote:
>>>>> If you are creating artifacts for different environments, you can use
>>>>> custom classifiers. I have done this. This will add a suffix to your
>>>>> artifacts.
>>>>>
>>>>> Paul
>>>>>
>>>>> On Mon, Nov 16, 2009 at 1:50 PM, Dan Tran <da...@gmail.com> wrote:
>>>>>> How about an alternative solution to replace that feature?
>>>>>>
>>>>>> -D
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Nov 15, 2009 at 11:26 AM, Dan Tran <da...@gmail.com> wrote:
>>>>>>> Hi
>>>>>>>
>>>>>>> According to
>>>>>>>
>>>>>>> http://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-NonuniqueSnapshotDeployments
>>>>>>>
>>>>>>> "The setting <uniqueVersion>false</uniqueVersion> for a distribution
>>>>>>> repository has no effect in version 3.x, snapshot artifacts will
>>>>>>> always be deployed using a timestamped version."
>>>>>>>
>>>>>>> This is a huge lost to those projects with multiple profile to build
>>>>>>> per platform specific.  see
>>>>>>> http://old.nabble.com/Multi-Platform-snapshots-td25295999.html for
>>>>>>> details
>>>>>>>
>>>>>>> For my case, we might be able to go forward with maven 3 ......
>>>>>>>
>>>>>>> Can the dev team put it back?
>>>>>>>
>>>>>>> -Dan
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org