You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@maven.org> on 2007/08/12 20:47:01 UTC
Maven Artifact
I have separated out maven-artifact into its own module here:
https://svn.apache.org/repos/asf/maven/maven-artifact
I will attempt to use it in trunk mid week, and right now I have
change the groupId to org.apache.maven.artifact.
Do we need to change the name of the artifactId to prevent confusion?
The groupId should prevent any dependency clashes, but the name being
the same may cause some confusion. I was also going to drop the
version back to 1.0.0-SNAPSHOT (start using major, minor, micro).
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by Jason van Zyl <ja...@maven.org>.
I have whimsical wifi here so I got cut off while trying to flip
things around last night. I'll have a real connection shortly.
On 17 Aug 07, at 2:02 AM 17 Aug 07, John Casey wrote:
> If we do that, let's not forget to update the externals reference
> in /trunks!
>
> Thanks,
>
> -john
>
> On Aug 16, 2007, at 6:32 PM, Brett Porter wrote:
>
>> Can we move maven-artifact from:
>>
>> http://svn.apache.org/repos/asf/maven/maven-artifact/
>>
>> to
>>
>> http://svn.apache.org/repos/asf/maven/artifact/trunk
>>
>> so we can have trunk/tags/branches?
>>
>> Also, can you add the <scm> element to the new location? Then I'll
>> add it back to Continuum.
>>
>> I'd do it myself, but I don't want to disturb your checkout.
>>
>> Thanks,
>> Brett
>>
>> On 16/08/2007, at 2:25 AM, Jason van Zyl wrote:
>>
>>>
>>> On 15 Aug 07, at 3:30 PM 15 Aug 07, Carlos Sanchez wrote:
>>>
>>>> Maven artifact is still in
>>>> https://svn.apache.org/repos/asf/maven/components/trunk/maven-
>>>> artifact
>>>>
>>>> does it need to be deleted and change the references?
>>>>
>>>> I also have some changes made in trunk, should I merge to the
>>>> new location?
>>>>
>>>
>>> Just put them in the new location. I left it there until I test
>>> it. But don't worry about what's in the 2.1.x.
>>>
>>>> On 8/15/07, Jason van Zyl <ja...@maven.org> wrote:
>>>>>
>>>>> On 15 Aug 07, at 1:36 AM 15 Aug 07, Brett Porter wrote:
>>>>>
>>>>>> Yes, that's what I meant by supercede. Nobody would use the
>>>>>> downloader any more.
>>>>>>
>>>>>
>>>>> Yes, I understood that part. The part I wasn't clear about is that
>>>>> Jan's facade makes it far easier for someone to use the
>>>>> functionality
>>>>> of the artifact resolution mechanism. Her facade does all the
>>>>> nasty
>>>>> work of using the resolver, artifact factory, and anything else to
>>>>> grab a set of dependencies for the runtime scope for example. It
>>>>> could be expanded to shield people from the complexity of the
>>>>> existing API. Jan's facade does this quite nicely. It would be the
>>>>> starting point of making something easier for any external
>>>>> client to
>>>>> use.
>>>>>
>>>>>> On 15/08/2007, at 7:12 AM, Jason van Zyl wrote:
>>>>>>
>>>>>>>
>>>>>>> On 13 Aug 07, at 4:43 AM 13 Aug 07, Brett Porter wrote:
>>>>>>>
>>>>>>>> All looks good. My preference is to keep going with 2.1-
>>>>>>>> SNAPSHOT
>>>>>>>> as the version (I've found in the past going backwards was
>>>>>>>> found
>>>>>>>> to be confusing), but I'm not that worried either way.
>>>>>>>>
>>>>>>>> I assume Jan's facade would supercede maven-downloader, so that
>>>>>>>> should be deprecated?
>>>>>>>>
>>>>>>>
>>>>>>> No, it would replace using the resolver directly. So it could
>>>>>>> easily replace the downloader but give people access to what
>>>>>>> they
>>>>>>> need 95% of the time without suffering the current API.
>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Brett
>>>>>>>>
>>>>>>>> On 13/08/2007, at 12:38 PM, Brian E. Fox wrote:
>>>>>>>>
>>>>>>>>> There will be confusion no matter what we do and the current
>>>>>>>>> name is the
>>>>>>>>> most specific, might as well leave it. Dropping back to
>>>>>>>>> 1.0.0 is
>>>>>>>>> good
>>>>>>>>> since it's really a new thing. It will add to the group to
>>>>>>>>> help
>>>>>>>>> distinguish that its new.
>>>>>>>>> +1 to leaving the artifactId
>>>>>>>>> +1 to the 1.0.0 version.
>>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Jason van Zyl [mailto:jason@maven.org]
>>>>>>>>> Sent: Sunday, August 12, 2007 2:47 PM
>>>>>>>>> To: Maven Developers List
>>>>>>>>> Subject: Maven Artifact
>>>>>>>>>
>>>>>>>>> I have separated out maven-artifact into its own module here:
>>>>>>>>>
>>>>>>>>> https://svn.apache.org/repos/asf/maven/maven-artifact
>>>>>>>>>
>>>>>>>>> I will attempt to use it in trunk mid week, and right now I
>>>>>>>>> have
>>>>>>>>> change the groupId to org.apache.maven.artifact.
>>>>>>>>>
>>>>>>>>> Do we need to change the name of the artifactId to prevent
>>>>>>>>> confusion?
>>>>>>>>> The groupId should prevent any dependency clashes, but the
>>>>>>>>> name
>>>>>>>>> being
>>>>>>>>> the same may cause some confusion. I was also going to drop
>>>>>>>>> the
>>>>>>>>> version back to 1.0.0-SNAPSHOT (start using major, minor,
>>>>>>>>> micro).
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Jason
>>>>>>>>>
>>>>>>>>> ----------------------------------------------------------
>>>>>>>>> Jason van Zyl
>>>>>>>>> Founder and PMC Chair, Apache Maven
>>>>>>>>> jason at sonatype dot com
>>>>>>>>> ----------------------------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --------------------------------------------------------------
>>>>>>>>> -----
>>>>>>>>> --
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --------------------------------------------------------------
>>>>>>>>> -----
>>>>>>>>> --
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------
>>>>>>>> -----
>>>>>>>> -
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jason
>>>>>>>
>>>>>>> ----------------------------------------------------------
>>>>>>> Jason van Zyl
>>>>>>> Founder and PMC Chair, Apache Maven
>>>>>>> jason at sonatype dot com
>>>>>>> ----------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ----------------------------------------------------------------
>>>>>>> -----
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> ----
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder and PMC Chair, Apache Maven
>>>>> jason at sonatype dot com
>>>>> ----------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> I could give you my word as a Spaniard.
>>>> No good. I've known too many Spaniards.
>>>> -- The Princess Bride
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder and PMC Chair, Apache Maven
>>> jason at sonatype dot com
>>> ----------------------------------------------------------
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---
> John Casey
> Committer and PMC Member, Apache Maven
> mail: jdcasey at commonjava dot org
> blog: http://www.ejlife.net/blogs/john
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by John Casey <jd...@commonjava.org>.
If we do that, let's not forget to update the externals reference in /
trunks!
Thanks,
-john
On Aug 16, 2007, at 6:32 PM, Brett Porter wrote:
> Can we move maven-artifact from:
>
> http://svn.apache.org/repos/asf/maven/maven-artifact/
>
> to
>
> http://svn.apache.org/repos/asf/maven/artifact/trunk
>
> so we can have trunk/tags/branches?
>
> Also, can you add the <scm> element to the new location? Then I'll
> add it back to Continuum.
>
> I'd do it myself, but I don't want to disturb your checkout.
>
> Thanks,
> Brett
>
> On 16/08/2007, at 2:25 AM, Jason van Zyl wrote:
>
>>
>> On 15 Aug 07, at 3:30 PM 15 Aug 07, Carlos Sanchez wrote:
>>
>>> Maven artifact is still in
>>> https://svn.apache.org/repos/asf/maven/components/trunk/maven-
>>> artifact
>>>
>>> does it need to be deleted and change the references?
>>>
>>> I also have some changes made in trunk, should I merge to the new
>>> location?
>>>
>>
>> Just put them in the new location. I left it there until I test
>> it. But don't worry about what's in the 2.1.x.
>>
>>> On 8/15/07, Jason van Zyl <ja...@maven.org> wrote:
>>>>
>>>> On 15 Aug 07, at 1:36 AM 15 Aug 07, Brett Porter wrote:
>>>>
>>>>> Yes, that's what I meant by supercede. Nobody would use the
>>>>> downloader any more.
>>>>>
>>>>
>>>> Yes, I understood that part. The part I wasn't clear about is that
>>>> Jan's facade makes it far easier for someone to use the
>>>> functionality
>>>> of the artifact resolution mechanism. Her facade does all the nasty
>>>> work of using the resolver, artifact factory, and anything else to
>>>> grab a set of dependencies for the runtime scope for example. It
>>>> could be expanded to shield people from the complexity of the
>>>> existing API. Jan's facade does this quite nicely. It would be the
>>>> starting point of making something easier for any external
>>>> client to
>>>> use.
>>>>
>>>>> On 15/08/2007, at 7:12 AM, Jason van Zyl wrote:
>>>>>
>>>>>>
>>>>>> On 13 Aug 07, at 4:43 AM 13 Aug 07, Brett Porter wrote:
>>>>>>
>>>>>>> All looks good. My preference is to keep going with 2.1-SNAPSHOT
>>>>>>> as the version (I've found in the past going backwards was found
>>>>>>> to be confusing), but I'm not that worried either way.
>>>>>>>
>>>>>>> I assume Jan's facade would supercede maven-downloader, so that
>>>>>>> should be deprecated?
>>>>>>>
>>>>>>
>>>>>> No, it would replace using the resolver directly. So it could
>>>>>> easily replace the downloader but give people access to what they
>>>>>> need 95% of the time without suffering the current API.
>>>>>>
>>>>>>> Cheers,
>>>>>>> Brett
>>>>>>>
>>>>>>> On 13/08/2007, at 12:38 PM, Brian E. Fox wrote:
>>>>>>>
>>>>>>>> There will be confusion no matter what we do and the current
>>>>>>>> name is the
>>>>>>>> most specific, might as well leave it. Dropping back to
>>>>>>>> 1.0.0 is
>>>>>>>> good
>>>>>>>> since it's really a new thing. It will add to the group to help
>>>>>>>> distinguish that its new.
>>>>>>>> +1 to leaving the artifactId
>>>>>>>> +1 to the 1.0.0 version.
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Jason van Zyl [mailto:jason@maven.org]
>>>>>>>> Sent: Sunday, August 12, 2007 2:47 PM
>>>>>>>> To: Maven Developers List
>>>>>>>> Subject: Maven Artifact
>>>>>>>>
>>>>>>>> I have separated out maven-artifact into its own module here:
>>>>>>>>
>>>>>>>> https://svn.apache.org/repos/asf/maven/maven-artifact
>>>>>>>>
>>>>>>>> I will attempt to use it in trunk mid week, and right now I
>>>>>>>> have
>>>>>>>> change the groupId to org.apache.maven.artifact.
>>>>>>>>
>>>>>>>> Do we need to change the name of the artifactId to prevent
>>>>>>>> confusion?
>>>>>>>> The groupId should prevent any dependency clashes, but the name
>>>>>>>> being
>>>>>>>> the same may cause some confusion. I was also going to drop the
>>>>>>>> version back to 1.0.0-SNAPSHOT (start using major, minor,
>>>>>>>> micro).
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Jason
>>>>>>>>
>>>>>>>> ----------------------------------------------------------
>>>>>>>> Jason van Zyl
>>>>>>>> Founder and PMC Chair, Apache Maven
>>>>>>>> jason at sonatype dot com
>>>>>>>> ----------------------------------------------------------
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------
>>>>>>>> ----
>>>>>>>> --
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------
>>>>>>>> ----
>>>>>>>> --
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>> ----------------------------------------------------------------
>>>>>>> ----
>>>>>>> -
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Jason
>>>>>>
>>>>>> ----------------------------------------------------------
>>>>>> Jason van Zyl
>>>>>> Founder and PMC Chair, Apache Maven
>>>>>> jason at sonatype dot com
>>>>>> ----------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> ----
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder and PMC Chair, Apache Maven
>>>> jason at sonatype dot com
>>>> ----------------------------------------------------------
>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> I could give you my word as a Spaniard.
>>> No good. I've known too many Spaniards.
>>> -- The Princess Bride
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder and PMC Chair, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
Re: Maven Artifact
Posted by Brett Porter <br...@apache.org>.
Can we move maven-artifact from:
http://svn.apache.org/repos/asf/maven/maven-artifact/
to
http://svn.apache.org/repos/asf/maven/artifact/trunk
so we can have trunk/tags/branches?
Also, can you add the <scm> element to the new location? Then I'll
add it back to Continuum.
I'd do it myself, but I don't want to disturb your checkout.
Thanks,
Brett
On 16/08/2007, at 2:25 AM, Jason van Zyl wrote:
>
> On 15 Aug 07, at 3:30 PM 15 Aug 07, Carlos Sanchez wrote:
>
>> Maven artifact is still in
>> https://svn.apache.org/repos/asf/maven/components/trunk/maven-
>> artifact
>>
>> does it need to be deleted and change the references?
>>
>> I also have some changes made in trunk, should I merge to the new
>> location?
>>
>
> Just put them in the new location. I left it there until I test it.
> But don't worry about what's in the 2.1.x.
>
>> On 8/15/07, Jason van Zyl <ja...@maven.org> wrote:
>>>
>>> On 15 Aug 07, at 1:36 AM 15 Aug 07, Brett Porter wrote:
>>>
>>>> Yes, that's what I meant by supercede. Nobody would use the
>>>> downloader any more.
>>>>
>>>
>>> Yes, I understood that part. The part I wasn't clear about is that
>>> Jan's facade makes it far easier for someone to use the
>>> functionality
>>> of the artifact resolution mechanism. Her facade does all the nasty
>>> work of using the resolver, artifact factory, and anything else to
>>> grab a set of dependencies for the runtime scope for example. It
>>> could be expanded to shield people from the complexity of the
>>> existing API. Jan's facade does this quite nicely. It would be the
>>> starting point of making something easier for any external client to
>>> use.
>>>
>>>> On 15/08/2007, at 7:12 AM, Jason van Zyl wrote:
>>>>
>>>>>
>>>>> On 13 Aug 07, at 4:43 AM 13 Aug 07, Brett Porter wrote:
>>>>>
>>>>>> All looks good. My preference is to keep going with 2.1-SNAPSHOT
>>>>>> as the version (I've found in the past going backwards was found
>>>>>> to be confusing), but I'm not that worried either way.
>>>>>>
>>>>>> I assume Jan's facade would supercede maven-downloader, so that
>>>>>> should be deprecated?
>>>>>>
>>>>>
>>>>> No, it would replace using the resolver directly. So it could
>>>>> easily replace the downloader but give people access to what they
>>>>> need 95% of the time without suffering the current API.
>>>>>
>>>>>> Cheers,
>>>>>> Brett
>>>>>>
>>>>>> On 13/08/2007, at 12:38 PM, Brian E. Fox wrote:
>>>>>>
>>>>>>> There will be confusion no matter what we do and the current
>>>>>>> name is the
>>>>>>> most specific, might as well leave it. Dropping back to 1.0.0 is
>>>>>>> good
>>>>>>> since it's really a new thing. It will add to the group to help
>>>>>>> distinguish that its new.
>>>>>>> +1 to leaving the artifactId
>>>>>>> +1 to the 1.0.0 version.
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Jason van Zyl [mailto:jason@maven.org]
>>>>>>> Sent: Sunday, August 12, 2007 2:47 PM
>>>>>>> To: Maven Developers List
>>>>>>> Subject: Maven Artifact
>>>>>>>
>>>>>>> I have separated out maven-artifact into its own module here:
>>>>>>>
>>>>>>> https://svn.apache.org/repos/asf/maven/maven-artifact
>>>>>>>
>>>>>>> I will attempt to use it in trunk mid week, and right now I have
>>>>>>> change the groupId to org.apache.maven.artifact.
>>>>>>>
>>>>>>> Do we need to change the name of the artifactId to prevent
>>>>>>> confusion?
>>>>>>> The groupId should prevent any dependency clashes, but the name
>>>>>>> being
>>>>>>> the same may cause some confusion. I was also going to drop the
>>>>>>> version back to 1.0.0-SNAPSHOT (start using major, minor,
>>>>>>> micro).
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jason
>>>>>>>
>>>>>>> ----------------------------------------------------------
>>>>>>> Jason van Zyl
>>>>>>> Founder and PMC Chair, Apache Maven
>>>>>>> jason at sonatype dot com
>>>>>>> ----------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ----------------------------------------------------------------
>>>>>>> ---
>>>>>>> --
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>> ----------------------------------------------------------------
>>>>>>> ---
>>>>>>> --
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> ---
>>>>>> -
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder and PMC Chair, Apache Maven
>>>>> jason at sonatype dot com
>>>>> ----------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder and PMC Chair, Apache Maven
>>> jason at sonatype dot com
>>> ----------------------------------------------------------
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>>
>> --
>> I could give you my word as a Spaniard.
>> No good. I've known too many Spaniards.
>> -- The Princess Bride
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by Jason van Zyl <ja...@maven.org>.
On 15 Aug 07, at 3:30 PM 15 Aug 07, Carlos Sanchez wrote:
> Maven artifact is still in
> https://svn.apache.org/repos/asf/maven/components/trunk/maven-artifact
>
> does it need to be deleted and change the references?
>
> I also have some changes made in trunk, should I merge to the new
> location?
>
Just put them in the new location. I left it there until I test it.
But don't worry about what's in the 2.1.x.
> On 8/15/07, Jason van Zyl <ja...@maven.org> wrote:
>>
>> On 15 Aug 07, at 1:36 AM 15 Aug 07, Brett Porter wrote:
>>
>>> Yes, that's what I meant by supercede. Nobody would use the
>>> downloader any more.
>>>
>>
>> Yes, I understood that part. The part I wasn't clear about is that
>> Jan's facade makes it far easier for someone to use the functionality
>> of the artifact resolution mechanism. Her facade does all the nasty
>> work of using the resolver, artifact factory, and anything else to
>> grab a set of dependencies for the runtime scope for example. It
>> could be expanded to shield people from the complexity of the
>> existing API. Jan's facade does this quite nicely. It would be the
>> starting point of making something easier for any external client to
>> use.
>>
>>> On 15/08/2007, at 7:12 AM, Jason van Zyl wrote:
>>>
>>>>
>>>> On 13 Aug 07, at 4:43 AM 13 Aug 07, Brett Porter wrote:
>>>>
>>>>> All looks good. My preference is to keep going with 2.1-SNAPSHOT
>>>>> as the version (I've found in the past going backwards was found
>>>>> to be confusing), but I'm not that worried either way.
>>>>>
>>>>> I assume Jan's facade would supercede maven-downloader, so that
>>>>> should be deprecated?
>>>>>
>>>>
>>>> No, it would replace using the resolver directly. So it could
>>>> easily replace the downloader but give people access to what they
>>>> need 95% of the time without suffering the current API.
>>>>
>>>>> Cheers,
>>>>> Brett
>>>>>
>>>>> On 13/08/2007, at 12:38 PM, Brian E. Fox wrote:
>>>>>
>>>>>> There will be confusion no matter what we do and the current
>>>>>> name is the
>>>>>> most specific, might as well leave it. Dropping back to 1.0.0 is
>>>>>> good
>>>>>> since it's really a new thing. It will add to the group to help
>>>>>> distinguish that its new.
>>>>>> +1 to leaving the artifactId
>>>>>> +1 to the 1.0.0 version.
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Jason van Zyl [mailto:jason@maven.org]
>>>>>> Sent: Sunday, August 12, 2007 2:47 PM
>>>>>> To: Maven Developers List
>>>>>> Subject: Maven Artifact
>>>>>>
>>>>>> I have separated out maven-artifact into its own module here:
>>>>>>
>>>>>> https://svn.apache.org/repos/asf/maven/maven-artifact
>>>>>>
>>>>>> I will attempt to use it in trunk mid week, and right now I have
>>>>>> change the groupId to org.apache.maven.artifact.
>>>>>>
>>>>>> Do we need to change the name of the artifactId to prevent
>>>>>> confusion?
>>>>>> The groupId should prevent any dependency clashes, but the name
>>>>>> being
>>>>>> the same may cause some confusion. I was also going to drop the
>>>>>> version back to 1.0.0-SNAPSHOT (start using major, minor, micro).
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Jason
>>>>>>
>>>>>> ----------------------------------------------------------
>>>>>> Jason van Zyl
>>>>>> Founder and PMC Chair, Apache Maven
>>>>>> jason at sonatype dot com
>>>>>> ----------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> --
>>>>>> --
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------------------
>>>>>> --
>>>>>> --
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> --
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder and PMC Chair, Apache Maven
>>>> jason at sonatype dot com
>>>> ----------------------------------------------------------
>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder and PMC Chair, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by Carlos Sanchez <ca...@apache.org>.
Maven artifact is still in
https://svn.apache.org/repos/asf/maven/components/trunk/maven-artifact
does it need to be deleted and change the references?
I also have some changes made in trunk, should I merge to the new location?
On 8/15/07, Jason van Zyl <ja...@maven.org> wrote:
>
> On 15 Aug 07, at 1:36 AM 15 Aug 07, Brett Porter wrote:
>
> > Yes, that's what I meant by supercede. Nobody would use the
> > downloader any more.
> >
>
> Yes, I understood that part. The part I wasn't clear about is that
> Jan's facade makes it far easier for someone to use the functionality
> of the artifact resolution mechanism. Her facade does all the nasty
> work of using the resolver, artifact factory, and anything else to
> grab a set of dependencies for the runtime scope for example. It
> could be expanded to shield people from the complexity of the
> existing API. Jan's facade does this quite nicely. It would be the
> starting point of making something easier for any external client to
> use.
>
> > On 15/08/2007, at 7:12 AM, Jason van Zyl wrote:
> >
> >>
> >> On 13 Aug 07, at 4:43 AM 13 Aug 07, Brett Porter wrote:
> >>
> >>> All looks good. My preference is to keep going with 2.1-SNAPSHOT
> >>> as the version (I've found in the past going backwards was found
> >>> to be confusing), but I'm not that worried either way.
> >>>
> >>> I assume Jan's facade would supercede maven-downloader, so that
> >>> should be deprecated?
> >>>
> >>
> >> No, it would replace using the resolver directly. So it could
> >> easily replace the downloader but give people access to what they
> >> need 95% of the time without suffering the current API.
> >>
> >>> Cheers,
> >>> Brett
> >>>
> >>> On 13/08/2007, at 12:38 PM, Brian E. Fox wrote:
> >>>
> >>>> There will be confusion no matter what we do and the current
> >>>> name is the
> >>>> most specific, might as well leave it. Dropping back to 1.0.0 is
> >>>> good
> >>>> since it's really a new thing. It will add to the group to help
> >>>> distinguish that its new.
> >>>> +1 to leaving the artifactId
> >>>> +1 to the 1.0.0 version.
> >>>>
> >>>> -----Original Message-----
> >>>> From: Jason van Zyl [mailto:jason@maven.org]
> >>>> Sent: Sunday, August 12, 2007 2:47 PM
> >>>> To: Maven Developers List
> >>>> Subject: Maven Artifact
> >>>>
> >>>> I have separated out maven-artifact into its own module here:
> >>>>
> >>>> https://svn.apache.org/repos/asf/maven/maven-artifact
> >>>>
> >>>> I will attempt to use it in trunk mid week, and right now I have
> >>>> change the groupId to org.apache.maven.artifact.
> >>>>
> >>>> Do we need to change the name of the artifactId to prevent
> >>>> confusion?
> >>>> The groupId should prevent any dependency clashes, but the name
> >>>> being
> >>>> the same may cause some confusion. I was also going to drop the
> >>>> version back to 1.0.0-SNAPSHOT (start using major, minor, micro).
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Jason
> >>>>
> >>>> ----------------------------------------------------------
> >>>> Jason van Zyl
> >>>> Founder and PMC Chair, Apache Maven
> >>>> jason at sonatype dot com
> >>>> ----------------------------------------------------------
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> --
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> --
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>> --------------------------------------------------------------------
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder and PMC Chair, Apache Maven
> >> jason at sonatype dot com
> >> ----------------------------------------------------------
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by Jason van Zyl <ja...@maven.org>.
On 15 Aug 07, at 1:36 AM 15 Aug 07, Brett Porter wrote:
> Yes, that's what I meant by supercede. Nobody would use the
> downloader any more.
>
Yes, I understood that part. The part I wasn't clear about is that
Jan's facade makes it far easier for someone to use the functionality
of the artifact resolution mechanism. Her facade does all the nasty
work of using the resolver, artifact factory, and anything else to
grab a set of dependencies for the runtime scope for example. It
could be expanded to shield people from the complexity of the
existing API. Jan's facade does this quite nicely. It would be the
starting point of making something easier for any external client to
use.
> On 15/08/2007, at 7:12 AM, Jason van Zyl wrote:
>
>>
>> On 13 Aug 07, at 4:43 AM 13 Aug 07, Brett Porter wrote:
>>
>>> All looks good. My preference is to keep going with 2.1-SNAPSHOT
>>> as the version (I've found in the past going backwards was found
>>> to be confusing), but I'm not that worried either way.
>>>
>>> I assume Jan's facade would supercede maven-downloader, so that
>>> should be deprecated?
>>>
>>
>> No, it would replace using the resolver directly. So it could
>> easily replace the downloader but give people access to what they
>> need 95% of the time without suffering the current API.
>>
>>> Cheers,
>>> Brett
>>>
>>> On 13/08/2007, at 12:38 PM, Brian E. Fox wrote:
>>>
>>>> There will be confusion no matter what we do and the current
>>>> name is the
>>>> most specific, might as well leave it. Dropping back to 1.0.0 is
>>>> good
>>>> since it's really a new thing. It will add to the group to help
>>>> distinguish that its new.
>>>> +1 to leaving the artifactId
>>>> +1 to the 1.0.0 version.
>>>>
>>>> -----Original Message-----
>>>> From: Jason van Zyl [mailto:jason@maven.org]
>>>> Sent: Sunday, August 12, 2007 2:47 PM
>>>> To: Maven Developers List
>>>> Subject: Maven Artifact
>>>>
>>>> I have separated out maven-artifact into its own module here:
>>>>
>>>> https://svn.apache.org/repos/asf/maven/maven-artifact
>>>>
>>>> I will attempt to use it in trunk mid week, and right now I have
>>>> change the groupId to org.apache.maven.artifact.
>>>>
>>>> Do we need to change the name of the artifactId to prevent
>>>> confusion?
>>>> The groupId should prevent any dependency clashes, but the name
>>>> being
>>>> the same may cause some confusion. I was also going to drop the
>>>> version back to 1.0.0-SNAPSHOT (start using major, minor, micro).
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder and PMC Chair, Apache Maven
>>>> jason at sonatype dot com
>>>> ----------------------------------------------------------
>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder and PMC Chair, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by Brett Porter <br...@apache.org>.
Yes, that's what I meant by supercede. Nobody would use the
downloader any more.
On 15/08/2007, at 7:12 AM, Jason van Zyl wrote:
>
> On 13 Aug 07, at 4:43 AM 13 Aug 07, Brett Porter wrote:
>
>> All looks good. My preference is to keep going with 2.1-SNAPSHOT
>> as the version (I've found in the past going backwards was found
>> to be confusing), but I'm not that worried either way.
>>
>> I assume Jan's facade would supercede maven-downloader, so that
>> should be deprecated?
>>
>
> No, it would replace using the resolver directly. So it could
> easily replace the downloader but give people access to what they
> need 95% of the time without suffering the current API.
>
>> Cheers,
>> Brett
>>
>> On 13/08/2007, at 12:38 PM, Brian E. Fox wrote:
>>
>>> There will be confusion no matter what we do and the current name
>>> is the
>>> most specific, might as well leave it. Dropping back to 1.0.0 is
>>> good
>>> since it's really a new thing. It will add to the group to help
>>> distinguish that its new.
>>> +1 to leaving the artifactId
>>> +1 to the 1.0.0 version.
>>>
>>> -----Original Message-----
>>> From: Jason van Zyl [mailto:jason@maven.org]
>>> Sent: Sunday, August 12, 2007 2:47 PM
>>> To: Maven Developers List
>>> Subject: Maven Artifact
>>>
>>> I have separated out maven-artifact into its own module here:
>>>
>>> https://svn.apache.org/repos/asf/maven/maven-artifact
>>>
>>> I will attempt to use it in trunk mid week, and right now I have
>>> change the groupId to org.apache.maven.artifact.
>>>
>>> Do we need to change the name of the artifactId to prevent
>>> confusion?
>>> The groupId should prevent any dependency clashes, but the name
>>> being
>>> the same may cause some confusion. I was also going to drop the
>>> version back to 1.0.0-SNAPSHOT (start using major, minor, micro).
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder and PMC Chair, Apache Maven
>>> jason at sonatype dot com
>>> ----------------------------------------------------------
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by Jason van Zyl <ja...@maven.org>.
On 13 Aug 07, at 4:43 AM 13 Aug 07, Brett Porter wrote:
> All looks good. My preference is to keep going with 2.1-SNAPSHOT as
> the version (I've found in the past going backwards was found to be
> confusing), but I'm not that worried either way.
>
> I assume Jan's facade would supercede maven-downloader, so that
> should be deprecated?
>
No, it would replace using the resolver directly. So it could easily
replace the downloader but give people access to what they need 95%
of the time without suffering the current API.
> Cheers,
> Brett
>
> On 13/08/2007, at 12:38 PM, Brian E. Fox wrote:
>
>> There will be confusion no matter what we do and the current name
>> is the
>> most specific, might as well leave it. Dropping back to 1.0.0 is good
>> since it's really a new thing. It will add to the group to help
>> distinguish that its new.
>> +1 to leaving the artifactId
>> +1 to the 1.0.0 version.
>>
>> -----Original Message-----
>> From: Jason van Zyl [mailto:jason@maven.org]
>> Sent: Sunday, August 12, 2007 2:47 PM
>> To: Maven Developers List
>> Subject: Maven Artifact
>>
>> I have separated out maven-artifact into its own module here:
>>
>> https://svn.apache.org/repos/asf/maven/maven-artifact
>>
>> I will attempt to use it in trunk mid week, and right now I have
>> change the groupId to org.apache.maven.artifact.
>>
>> Do we need to change the name of the artifactId to prevent confusion?
>> The groupId should prevent any dependency clashes, but the name being
>> the same may cause some confusion. I was also going to drop the
>> version back to 1.0.0-SNAPSHOT (start using major, minor, micro).
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder and PMC Chair, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by Brett Porter <br...@apache.org>.
All looks good. My preference is to keep going with 2.1-SNAPSHOT as
the version (I've found in the past going backwards was found to be
confusing), but I'm not that worried either way.
I assume Jan's facade would supercede maven-downloader, so that
should be deprecated?
Cheers,
Brett
On 13/08/2007, at 12:38 PM, Brian E. Fox wrote:
> There will be confusion no matter what we do and the current name
> is the
> most specific, might as well leave it. Dropping back to 1.0.0 is good
> since it's really a new thing. It will add to the group to help
> distinguish that its new.
> +1 to leaving the artifactId
> +1 to the 1.0.0 version.
>
> -----Original Message-----
> From: Jason van Zyl [mailto:jason@maven.org]
> Sent: Sunday, August 12, 2007 2:47 PM
> To: Maven Developers List
> Subject: Maven Artifact
>
> I have separated out maven-artifact into its own module here:
>
> https://svn.apache.org/repos/asf/maven/maven-artifact
>
> I will attempt to use it in trunk mid week, and right now I have
> change the groupId to org.apache.maven.artifact.
>
> Do we need to change the name of the artifactId to prevent confusion?
> The groupId should prevent any dependency clashes, but the name being
> the same may cause some confusion. I was also going to drop the
> version back to 1.0.0-SNAPSHOT (start using major, minor, micro).
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Maven Artifact
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
There will be confusion no matter what we do and the current name is the
most specific, might as well leave it. Dropping back to 1.0.0 is good
since it's really a new thing. It will add to the group to help
distinguish that its new.
+1 to leaving the artifactId
+1 to the 1.0.0 version.
-----Original Message-----
From: Jason van Zyl [mailto:jason@maven.org]
Sent: Sunday, August 12, 2007 2:47 PM
To: Maven Developers List
Subject: Maven Artifact
I have separated out maven-artifact into its own module here:
https://svn.apache.org/repos/asf/maven/maven-artifact
I will attempt to use it in trunk mid week, and right now I have
change the groupId to org.apache.maven.artifact.
Do we need to change the name of the artifactId to prevent confusion?
The groupId should prevent any dependency clashes, but the name being
the same may cause some confusion. I was also going to drop the
version back to 1.0.0-SNAPSHOT (start using major, minor, micro).
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by Jason van Zyl <ja...@maven.org>.
On 12 Aug 07, at 11:45 PM 12 Aug 07, Jason Dillon wrote:
> On Aug 12, 2007, at 11:47 AM, Jason van Zyl wrote:
>> I have separated out maven-artifact into its own module here:
>>
>> https://svn.apache.org/repos/asf/maven/maven-artifact
>
> Cool! Will this hopefully get a simplified API for handling
> resolution of transitive dependencies too?
>
The first thing I will add is Jan's facade which is simple and decent
for most external use cases. It's tucked away in the Jetty plugin but
I have her permission to put it in the codebase so I'll do that soon.
>
>> I will attempt to use it in trunk mid week, and right now I have
>> change the groupId to org.apache.maven.artifact.
>>
>> Do we need to change the name of the artifactId to prevent
>> confusion? The groupId should prevent any dependency clashes, but
>> the name being the same may cause some confusion.
>
> Personally I don't think so... I think the groupId change is
> sufficient.
>
>
>> I was also going to drop the version back to 1.0.0-SNAPSHOT (start
>> using major, minor, micro).
>
> +1
>
> --jason
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by Jason Dillon <ja...@planet57.com>.
On Aug 12, 2007, at 11:47 AM, Jason van Zyl wrote:
> I have separated out maven-artifact into its own module here:
>
> https://svn.apache.org/repos/asf/maven/maven-artifact
Cool! Will this hopefully get a simplified API for handling
resolution of transitive dependencies too?
> I will attempt to use it in trunk mid week, and right now I have
> change the groupId to org.apache.maven.artifact.
>
> Do we need to change the name of the artifactId to prevent
> confusion? The groupId should prevent any dependency clashes, but
> the name being the same may cause some confusion.
Personally I don't think so... I think the groupId change is sufficient.
> I was also going to drop the version back to 1.0.0-SNAPSHOT (start
> using major, minor, micro).
+1
--jason
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by Milos Kleint <mk...@gmail.com>.
lately I've read this:
http://ancientprogramming.blogspot.com/2007/08/badly-packaged-project-will-break.html
can we get into the same packaging/classloading issues? what happens
to the plugins?
I haven't checked the changes yet, just recalled the maven artifact
when reading the blog post..
Milos
On 8/13/07, Jason van Zyl <ja...@maven.org> wrote:
>
> On 13 Aug 07, at 8:03 PM 13 Aug 07, John Casey wrote:
>
> > But I thought the whole point of the major version number was to
> > track the progression of the project as a concept...that is, a set
> > of logically evolving specifications and behaviors. The whole point
> > here is that Maven's artifact behavior is not new. In fact, we're
> > starting the third major iteration of this work. I think it makes
> > much more sense to capture that fact.
> >
> > In the end, it's not critical one way or the other, but I think
> > it's pointless to have a major version number as such if we're not
> > going to use it.
> >
>
> We've never had an independent release. We'll release 3.0, and folks
> will probably ask where 1 and 2 went. I ultimately don't care, 1.0-S
> was most consistent to me.
>
> > -john
> >
> > On Aug 12, 2007, at 8:03 PM, Jason van Zyl wrote:
> >
> >>
> >> On 13 Aug 07, at 1:02 AM 13 Aug 07, John Casey wrote:
> >>
> >>> I think the move is a good idea, especially since it means
> >>> formally decoupling the release cycles. Just one question: why
> >>> drop the version? If this is a total rewrite of the code, then
> >>> isn't a 3.0 more in order than going all the way back to 1.0? The
> >>> behaviors and specs for artifacts are still relatively well
> >>> defined, and won't change that significantly, after all.
> >>>
> >>
> >> I just always default something "new" to 1.0-S. The artifact
> >> interfaces probably won't change much, but I see the guts changing
> >> quite a bit.
> >>
> >>> -john
> >>>
> >>> On Aug 12, 2007, at 2:47 PM, Jason van Zyl wrote:
> >>>
> >>>> I have separated out maven-artifact into its own module here:
> >>>>
> >>>> https://svn.apache.org/repos/asf/maven/maven-artifact
> >>>>
> >>>> I will attempt to use it in trunk mid week, and right now I have
> >>>> change the groupId to org.apache.maven.artifact.
> >>>>
> >>>> Do we need to change the name of the artifactId to prevent
> >>>> confusion? The groupId should prevent any dependency clashes,
> >>>> but the name being the same may cause some confusion. I was also
> >>>> going to drop the version back to 1.0.0-SNAPSHOT (start using
> >>>> major, minor, micro).
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Jason
> >>>>
> >>>> ----------------------------------------------------------
> >>>> Jason van Zyl
> >>>> Founder and PMC Chair, Apache Maven
> >>>> jason at sonatype dot com
> >>>> ----------------------------------------------------------
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> --
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>
> >>> ---
> >>> John Casey
> >>> Committer and PMC Member, Apache Maven
> >>> mail: jdcasey at commonjava dot org
> >>> blog: http://www.ejlife.net/blogs/john
> >>>
> >>>
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder and PMC Chair, Apache Maven
> >> jason at sonatype dot com
> >> ----------------------------------------------------------
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >
> > ---
> > John Casey
> > Committer and PMC Member, Apache Maven
> > mail: jdcasey at commonjava dot org
> > blog: http://www.ejlife.net/blogs/john
> >
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by Carlos Sanchez <ca...@apache.org>.
I'm with you, I think a 3.0 would make more sense ;)
specially if it keeps evolving from 1.0.0 and gets to 2.0, 2.0.1...,
then it'd be really confusing
On 8/14/07, John Casey <jd...@commonjava.org> wrote:
> Whatever works, it just seemed like a confusing move to me...but
> then, I am often confused by things that others just "get". :-)
>
> -j
>
> On Aug 13, 2007, at 4:52 PM, Jason van Zyl wrote:
>
> >
> > On 13 Aug 07, at 8:03 PM 13 Aug 07, John Casey wrote:
> >
> >> But I thought the whole point of the major version number was to
> >> track the progression of the project as a concept...that is, a set
> >> of logically evolving specifications and behaviors. The whole
> >> point here is that Maven's artifact behavior is not new. In fact,
> >> we're starting the third major iteration of this work. I think it
> >> makes much more sense to capture that fact.
> >>
> >> In the end, it's not critical one way or the other, but I think
> >> it's pointless to have a major version number as such if we're not
> >> going to use it.
> >>
> >
> > We've never had an independent release. We'll release 3.0, and
> > folks will probably ask where 1 and 2 went. I ultimately don't
> > care, 1.0-S was most consistent to me.
> >
> >> -john
> >>
> >> On Aug 12, 2007, at 8:03 PM, Jason van Zyl wrote:
> >>
> >>>
> >>> On 13 Aug 07, at 1:02 AM 13 Aug 07, John Casey wrote:
> >>>
> >>>> I think the move is a good idea, especially since it means
> >>>> formally decoupling the release cycles. Just one question: why
> >>>> drop the version? If this is a total rewrite of the code, then
> >>>> isn't a 3.0 more in order than going all the way back to 1.0?
> >>>> The behaviors and specs for artifacts are still relatively well
> >>>> defined, and won't change that significantly, after all.
> >>>>
> >>>
> >>> I just always default something "new" to 1.0-S. The artifact
> >>> interfaces probably won't change much, but I see the guts
> >>> changing quite a bit.
> >>>
> >>>> -john
> >>>>
> >>>> On Aug 12, 2007, at 2:47 PM, Jason van Zyl wrote:
> >>>>
> >>>>> I have separated out maven-artifact into its own module here:
> >>>>>
> >>>>> https://svn.apache.org/repos/asf/maven/maven-artifact
> >>>>>
> >>>>> I will attempt to use it in trunk mid week, and right now I
> >>>>> have change the groupId to org.apache.maven.artifact.
> >>>>>
> >>>>> Do we need to change the name of the artifactId to prevent
> >>>>> confusion? The groupId should prevent any dependency clashes,
> >>>>> but the name being the same may cause some confusion. I was
> >>>>> also going to drop the version back to 1.0.0-SNAPSHOT (start
> >>>>> using major, minor, micro).
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> Jason
> >>>>>
> >>>>> ----------------------------------------------------------
> >>>>> Jason van Zyl
> >>>>> Founder and PMC Chair, Apache Maven
> >>>>> jason at sonatype dot com
> >>>>> ----------------------------------------------------------
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> ------------------------------------------------------------------
> >>>>> ---
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>
> >>>>
> >>>> ---
> >>>> John Casey
> >>>> Committer and PMC Member, Apache Maven
> >>>> mail: jdcasey at commonjava dot org
> >>>> blog: http://www.ejlife.net/blogs/john
> >>>>
> >>>>
> >>>
> >>> Thanks,
> >>>
> >>> Jason
> >>>
> >>> ----------------------------------------------------------
> >>> Jason van Zyl
> >>> Founder and PMC Chair, Apache Maven
> >>> jason at sonatype dot com
> >>> ----------------------------------------------------------
> >>>
> >>>
> >>>
> >>>
> >>> --------------------------------------------------------------------
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>
> >> ---
> >> John Casey
> >> Committer and PMC Member, Apache Maven
> >> mail: jdcasey at commonjava dot org
> >> blog: http://www.ejlife.net/blogs/john
> >>
> >>
> >
> > Thanks,
> >
> > Jason
> >
> > ----------------------------------------------------------
> > Jason van Zyl
> > Founder and PMC Chair, Apache Maven
> > jason at sonatype dot com
> > ----------------------------------------------------------
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> ---
> John Casey
> Committer and PMC Member, Apache Maven
> mail: jdcasey at commonjava dot org
> blog: http://www.ejlife.net/blogs/john
>
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by John Casey <jd...@commonjava.org>.
Whatever works, it just seemed like a confusing move to me...but
then, I am often confused by things that others just "get". :-)
-j
On Aug 13, 2007, at 4:52 PM, Jason van Zyl wrote:
>
> On 13 Aug 07, at 8:03 PM 13 Aug 07, John Casey wrote:
>
>> But I thought the whole point of the major version number was to
>> track the progression of the project as a concept...that is, a set
>> of logically evolving specifications and behaviors. The whole
>> point here is that Maven's artifact behavior is not new. In fact,
>> we're starting the third major iteration of this work. I think it
>> makes much more sense to capture that fact.
>>
>> In the end, it's not critical one way or the other, but I think
>> it's pointless to have a major version number as such if we're not
>> going to use it.
>>
>
> We've never had an independent release. We'll release 3.0, and
> folks will probably ask where 1 and 2 went. I ultimately don't
> care, 1.0-S was most consistent to me.
>
>> -john
>>
>> On Aug 12, 2007, at 8:03 PM, Jason van Zyl wrote:
>>
>>>
>>> On 13 Aug 07, at 1:02 AM 13 Aug 07, John Casey wrote:
>>>
>>>> I think the move is a good idea, especially since it means
>>>> formally decoupling the release cycles. Just one question: why
>>>> drop the version? If this is a total rewrite of the code, then
>>>> isn't a 3.0 more in order than going all the way back to 1.0?
>>>> The behaviors and specs for artifacts are still relatively well
>>>> defined, and won't change that significantly, after all.
>>>>
>>>
>>> I just always default something "new" to 1.0-S. The artifact
>>> interfaces probably won't change much, but I see the guts
>>> changing quite a bit.
>>>
>>>> -john
>>>>
>>>> On Aug 12, 2007, at 2:47 PM, Jason van Zyl wrote:
>>>>
>>>>> I have separated out maven-artifact into its own module here:
>>>>>
>>>>> https://svn.apache.org/repos/asf/maven/maven-artifact
>>>>>
>>>>> I will attempt to use it in trunk mid week, and right now I
>>>>> have change the groupId to org.apache.maven.artifact.
>>>>>
>>>>> Do we need to change the name of the artifactId to prevent
>>>>> confusion? The groupId should prevent any dependency clashes,
>>>>> but the name being the same may cause some confusion. I was
>>>>> also going to drop the version back to 1.0.0-SNAPSHOT (start
>>>>> using major, minor, micro).
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder and PMC Chair, Apache Maven
>>>>> jason at sonatype dot com
>>>>> ----------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> ---
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>
>>>> ---
>>>> John Casey
>>>> Committer and PMC Member, Apache Maven
>>>> mail: jdcasey at commonjava dot org
>>>> blog: http://www.ejlife.net/blogs/john
>>>>
>>>>
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder and PMC Chair, Apache Maven
>>> jason at sonatype dot com
>>> ----------------------------------------------------------
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> ---
>> John Casey
>> Committer and PMC Member, Apache Maven
>> mail: jdcasey at commonjava dot org
>> blog: http://www.ejlife.net/blogs/john
>>
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
Re: Maven Artifact
Posted by Jason van Zyl <ja...@maven.org>.
On 13 Aug 07, at 8:03 PM 13 Aug 07, John Casey wrote:
> But I thought the whole point of the major version number was to
> track the progression of the project as a concept...that is, a set
> of logically evolving specifications and behaviors. The whole point
> here is that Maven's artifact behavior is not new. In fact, we're
> starting the third major iteration of this work. I think it makes
> much more sense to capture that fact.
>
> In the end, it's not critical one way or the other, but I think
> it's pointless to have a major version number as such if we're not
> going to use it.
>
We've never had an independent release. We'll release 3.0, and folks
will probably ask where 1 and 2 went. I ultimately don't care, 1.0-S
was most consistent to me.
> -john
>
> On Aug 12, 2007, at 8:03 PM, Jason van Zyl wrote:
>
>>
>> On 13 Aug 07, at 1:02 AM 13 Aug 07, John Casey wrote:
>>
>>> I think the move is a good idea, especially since it means
>>> formally decoupling the release cycles. Just one question: why
>>> drop the version? If this is a total rewrite of the code, then
>>> isn't a 3.0 more in order than going all the way back to 1.0? The
>>> behaviors and specs for artifacts are still relatively well
>>> defined, and won't change that significantly, after all.
>>>
>>
>> I just always default something "new" to 1.0-S. The artifact
>> interfaces probably won't change much, but I see the guts changing
>> quite a bit.
>>
>>> -john
>>>
>>> On Aug 12, 2007, at 2:47 PM, Jason van Zyl wrote:
>>>
>>>> I have separated out maven-artifact into its own module here:
>>>>
>>>> https://svn.apache.org/repos/asf/maven/maven-artifact
>>>>
>>>> I will attempt to use it in trunk mid week, and right now I have
>>>> change the groupId to org.apache.maven.artifact.
>>>>
>>>> Do we need to change the name of the artifactId to prevent
>>>> confusion? The groupId should prevent any dependency clashes,
>>>> but the name being the same may cause some confusion. I was also
>>>> going to drop the version back to 1.0.0-SNAPSHOT (start using
>>>> major, minor, micro).
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder and PMC Chair, Apache Maven
>>>> jason at sonatype dot com
>>>> ----------------------------------------------------------
>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>
>>> ---
>>> John Casey
>>> Committer and PMC Member, Apache Maven
>>> mail: jdcasey at commonjava dot org
>>> blog: http://www.ejlife.net/blogs/john
>>>
>>>
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder and PMC Chair, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---
> John Casey
> Committer and PMC Member, Apache Maven
> mail: jdcasey at commonjava dot org
> blog: http://www.ejlife.net/blogs/john
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by John Casey <jd...@commonjava.org>.
But I thought the whole point of the major version number was to
track the progression of the project as a concept...that is, a set of
logically evolving specifications and behaviors. The whole point here
is that Maven's artifact behavior is not new. In fact, we're starting
the third major iteration of this work. I think it makes much more
sense to capture that fact.
In the end, it's not critical one way or the other, but I think it's
pointless to have a major version number as such if we're not going
to use it.
-john
On Aug 12, 2007, at 8:03 PM, Jason van Zyl wrote:
>
> On 13 Aug 07, at 1:02 AM 13 Aug 07, John Casey wrote:
>
>> I think the move is a good idea, especially since it means
>> formally decoupling the release cycles. Just one question: why
>> drop the version? If this is a total rewrite of the code, then
>> isn't a 3.0 more in order than going all the way back to 1.0? The
>> behaviors and specs for artifacts are still relatively well
>> defined, and won't change that significantly, after all.
>>
>
> I just always default something "new" to 1.0-S. The artifact
> interfaces probably won't change much, but I see the guts changing
> quite a bit.
>
>> -john
>>
>> On Aug 12, 2007, at 2:47 PM, Jason van Zyl wrote:
>>
>>> I have separated out maven-artifact into its own module here:
>>>
>>> https://svn.apache.org/repos/asf/maven/maven-artifact
>>>
>>> I will attempt to use it in trunk mid week, and right now I have
>>> change the groupId to org.apache.maven.artifact.
>>>
>>> Do we need to change the name of the artifactId to prevent
>>> confusion? The groupId should prevent any dependency clashes, but
>>> the name being the same may cause some confusion. I was also
>>> going to drop the version back to 1.0.0-SNAPSHOT (start using
>>> major, minor, micro).
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder and PMC Chair, Apache Maven
>>> jason at sonatype dot com
>>> ----------------------------------------------------------
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> -
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> ---
>> John Casey
>> Committer and PMC Member, Apache Maven
>> mail: jdcasey at commonjava dot org
>> blog: http://www.ejlife.net/blogs/john
>>
>>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
Re: Maven Artifact
Posted by Jason van Zyl <ja...@maven.org>.
On 13 Aug 07, at 1:02 AM 13 Aug 07, John Casey wrote:
> I think the move is a good idea, especially since it means formally
> decoupling the release cycles. Just one question: why drop the
> version? If this is a total rewrite of the code, then isn't a 3.0
> more in order than going all the way back to 1.0? The behaviors and
> specs for artifacts are still relatively well defined, and won't
> change that significantly, after all.
>
I just always default something "new" to 1.0-S. The artifact
interfaces probably won't change much, but I see the guts changing
quite a bit.
> -john
>
> On Aug 12, 2007, at 2:47 PM, Jason van Zyl wrote:
>
>> I have separated out maven-artifact into its own module here:
>>
>> https://svn.apache.org/repos/asf/maven/maven-artifact
>>
>> I will attempt to use it in trunk mid week, and right now I have
>> change the groupId to org.apache.maven.artifact.
>>
>> Do we need to change the name of the artifactId to prevent
>> confusion? The groupId should prevent any dependency clashes, but
>> the name being the same may cause some confusion. I was also going
>> to drop the version back to 1.0.0-SNAPSHOT (start using major,
>> minor, micro).
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder and PMC Chair, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---
> John Casey
> Committer and PMC Member, Apache Maven
> mail: jdcasey at commonjava dot org
> blog: http://www.ejlife.net/blogs/john
>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven Artifact
Posted by John Casey <jd...@commonjava.org>.
I think the move is a good idea, especially since it means formally
decoupling the release cycles. Just one question: why drop the
version? If this is a total rewrite of the code, then isn't a 3.0
more in order than going all the way back to 1.0? The behaviors and
specs for artifacts are still relatively well defined, and won't
change that significantly, after all.
-john
On Aug 12, 2007, at 2:47 PM, Jason van Zyl wrote:
> I have separated out maven-artifact into its own module here:
>
> https://svn.apache.org/repos/asf/maven/maven-artifact
>
> I will attempt to use it in trunk mid week, and right now I have
> change the groupId to org.apache.maven.artifact.
>
> Do we need to change the name of the artifactId to prevent
> confusion? The groupId should prevent any dependency clashes, but
> the name being the same may cause some confusion. I was also going
> to drop the version back to 1.0.0-SNAPSHOT (start using major,
> minor, micro).
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder and PMC Chair, Apache Maven
> jason at sonatype dot com
> ----------------------------------------------------------
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john