You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Siegfried Goeschl <si...@it20one.at> on 2008/04/08 12:34:36 UTC
Looking at commons-parent-9.pom
Hi folks,
I'm currently looking at moving Fulcrum to M2 and would like to use the
grunge work you did on commons-parent - looking at it I have a few
questions/improvements ...
1) Legal Stuff
=========================================================================
the ASL is missing in the parent pom
2) Improvement of IDE project generation
=========================================================================
in my pom I configure IDEA and Eclipse to download the sources when
creating the project files - this makes stepping through used libraries
much easier
<plugin>
<!-- generate the IntelliJ project files -->
<artifactId>maven-idea-plugin</artifactId>
<configuration>
<downloadSources>true</downloadSources>
</configuration>
</plugin>
<plugin>
<!-- generate the Eclipse project files -->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<downloadSources>true</downloadSources>
<downloadJavadocs>false</downloadJavadocs>
</configuration>
</plugin>
3) Creating sources jar
=========================================================================
in my projects I always create the sources jar not only for release
candidates and releases - this allows to quickly make a SNAPSHOT install
in your local repo including the sources - having said that you can
always do a manual invocation but it would reduce the complexity of the
parent pom
4) Reporting
=========================================================================
I have a few standard reporting plugins which could be an useful
addition - maven-changes-plugin, maven-pmd-plugin, taglist-maven-plugin
(codehaus)
5) commons-build-plugin
=========================================================================
What is it exactly doing?
Thanks in advance
Siegfried Goeschl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@turbine.apache.org
For additional commands, e-mail: dev-help@turbine.apache.org
Re: Looking at commons-parent-9.pom
Posted by Niall Pemberton <ni...@gmail.com>.
On Tue, Apr 8, 2008 at 11:34 AM, Siegfried Goeschl
<si...@it20one.at> wrote:
> Hi folks,
>
> I'm currently looking at moving Fulcrum to M2 and would like to use the
> grunge work you did on commons-parent - looking at it I have a few
> questions/improvements ...
>
> 1) Legal Stuff
> =========================================================================
> the ASL is missing in the parent pom
Yes it got stripped out by the release plugin when I did the version 9
release, its been put back in in trunk
> 2) Improvement of IDE project generation
> =========================================================================
>
> in my pom I configure IDEA and Eclipse to download the sources when
> creating the project files - this makes stepping through used libraries much
> easier
>
> <plugin>
> <!-- generate the IntelliJ project files -->
> <artifactId>maven-idea-plugin</artifactId>
> <configuration>
> <downloadSources>true</downloadSources>
> </configuration>
> </plugin> <plugin>
> <!-- generate the Eclipse project files -->
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-eclipse-plugin</artifactId>
> <configuration>
> <downloadSources>true</downloadSources>
> <downloadJavadocs>false</downloadJavadocs>
> </configuration>
> </plugin>
>
>
> 3) Creating sources jar
> =========================================================================
>
> in my projects I always create the sources jar not only for release
> candidates and releases - this allows to quickly make a SNAPSHOT install in
> your local repo including the sources - having said that you can always do a
> manual invocation but it would reduce the complexity of the parent pom
You can use the "rc" profile to do this - just
mvn -Prc install
>
> 4) Reporting
> =========================================================================
>
> I have a few standard reporting plugins which could be an useful addition -
> maven-changes-plugin, maven-pmd-plugin, taglist-maven-plugin (codehaus)
For the changes plugin, doesn't this require individual component
configuration? If so, then not sure it would do any good configuring
in the parent.
> 5) commons-build-plugin
> =========================================================================
>
> What is it exactly doing?
Just generating custom download and issue tracking pages for commons - see
http://commons.apache.org/commons-build-plugin/
Niall
> Thanks in advance
>
> Siegfried Goeschl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Looking at commons-parent-9.pom
Posted by Jochen Wiedmann <jo...@gmail.com>.
On Tue, Apr 8, 2008 at 12:34 PM, Siegfried Goeschl
<si...@it20one.at> wrote:
> 1) Legal Stuff
> =========================================================================
> the ASL is missing in the parent pom
That's most possibly a deployment problem. I do not remember the exact
syntax, but it seems that comments are lost unless they are placed in
a specific location, like right after the root element or something
like that.
> 3) Creating sources jar
> =========================================================================
>
> in my projects I always create the sources jar not only for release
> candidates and releases - this allows to quickly make a SNAPSHOT install in
> your local repo including the sources - having said that you can always do a
> manual invocation but it would reduce the complexity of the parent pom
I'd personally be in favour for that, but I doubt that you'll get the
majority here.
> 4) Reporting
> =========================================================================
>
> I have a few standard reporting plugins which could be an useful addition -
> maven-changes-plugin, maven-pmd-plugin, taglist-maven-plugin (codehaus)
As I see it, it goes the other way round: Parent is the minimum,
others may add. I do not know whether removing reports from the parent
works. If that is not the case, then I'd discourage adding more
reports.
> 5) commons-build-plugin
> =========================================================================
>
> What is it exactly doing?
Legal stuff, like adding the NOTICE and LICENSE files, AFAIK.
Jochen
--
Look, that's why there's rules, understand? So that you think before
you break 'em.
-- (Terry Pratchett, Thief of Time)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org