maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Kick" <gk5...@gmail.com>
Subject Re: Source Archives: Source Plugin vs. Assembly Plugin
Date Sun, 14 Jan 2007 10:05:37 GMT
Dennis,

I definitely agree.  The sources plugin has been successfully used as
the mechanism for creating and deploying source jars to the the
repository.  The reason that I brought it up was that any number of
artifacts can be deployed to a repository (
http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#deploy
) and it seems to be unnecessary to have to manage multiple plugins.

I would understand if there was some added functionality that was
provided by the source plugin, but the goals and parameters both seem
to be a subset.  As far as it being "write protected," wouldn't a
predefined descriptor standardize the process to the same degree?

In the end, I certainly have nothing against the source plugin and the
jar goal of the javadoc plugin because I use them both frequently.  It
would just simplify my POMs and probably promote source and jar
publishing if adding these artifacts was an additional line in the
assembly plugin configuration instead of running each plugin manually
or individually attaching them to the lifecycle.

Now obviously, I could just go ahead and do it, but I brought it up
because assembly's faq refers users to the javadoc plugin for that
artifact and has a different suffix and packaging for sources.  So,
again I'll ask if there is a particular reason that this hasn't been
consolidated or is it just because the assembly plugin seems to have
matured a bit later?

On 1/13/07, Dennis Lundberg <dennisl@apache.org> wrote:
> Hi Gregory
>
> Although I haven't spent a lot of time using either of these plugins, it
> is my understanding that the source-plugin is there to enable you to
> publish the sources for your product in the repository. Look at it as a
> write-protected assembly which is tailored to match the exact needs of
> sources jars that are to be published in the repository.
>
> Gregory Kick wrote:
> > Franz,
> >
> > The difference that I see between the sources and javadoc plugins and
> > jar, war, etc. is that plugins like the jar plugin actually define the
> > lifecycle for that particular packaging.  Since source and javadoc
> > jars are "auxiliary" artifacts, it seems as though it would make more
> > sense to consolidate that functionality in order to minimize effort
> > across the plugins.  Also, it seems like it would be much more
> > convenient to look look at the descriptorRefs tag and see __every__
> > artifact that was being generated (aside from the default, "main"
> > artifact).
> >
> > Aside from it already being implemented, was there a specific reason
> > for sources and javadoc to create their own jars?
> >
> > On 1/12/07, franz see <franz.see@gmail.com> wrote:
> >>
> >> Good day to you, Gregory,
> >>
> >> I think it is simply for ease of use. Intead of configuring the assembly
> >> plugin, you can simply do mvn sources:jar. Same goes for the other
> >> packaing
> >> goals ( jar:jar, javadoc:jar, ejb:ejb, ejb3:ejb3, war:war, ear:ear,
> >> etc ).
> >> Usually, you don't have to use the assembly plugin because the other
> >> packaging goals are much easier to use. But if those goals are not enough
> >> for your needs, then go for the assembly plugin.
> >>
> >> As for the difference between -sources and -src, I am not sure myself :-)
> >>
> >> Cheers,
> >> Franz
> >>
> >>
> >> Gregory Kick-2 wrote:
> >> >
> >> > After looking through the documentation for each of these plugins, I
> >> > am left with a few questions:
> >> >
> >> > - Isn't the functionality of the source plugin just a subset of the
> >> > assembly plugin (i.e. couldn't I just use the assembly plugin to do
> >> > the same thing and only have to worry about one plugin)?
> >> >
> >> > - Is there a reason that the assembly plugin uses -src for its
> >> > archives while the sources plugin uses -sources?
> >> >
> >> > - Should the Source Plugin be deprecated for a pre-defined assembly
> >> > descriptor with the same behavior?
> >> >
> >> > --
> >> > Gregory Kick
> >> > gk5885@gmail.com
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> > For additional commands, e-mail: users-help@maven.apache.org
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Source-Archives%3A-Source-Plugin-vs.-Assembly-Plugin-tf2963424s177.html#a8292765
> >>
> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
Gregory Kick
gk5885@gmail.com

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


Mime
View raw message