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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
> >>>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>>
> >>>
> >>> ---
> >>> 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: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >
> > ---
> > 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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to