cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-3102) Update Apache CXF's main pom.xml file
Date Fri, 29 Oct 2010 21:04:20 GMT

    [ https://issues.apache.org/jira/browse/CXF-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926456#action_12926456
] 

Daniel Kulp commented on CXF-3102:
----------------------------------


I personally would prefer not to have the re-ordering done, or at least not for the <properties>
element.  I MUCH perfer that to be at the top.  (define properties before using them type
thing)  The rest of the reordering I'm pretty indifferent about.

As Benson said, we have issues with the Apache parent, so no-parent is appropriate.

I'd prefer not to have the empty contributor thing.   For the developers, this is something
we need to think about.   At some point in the not-to-distant future, that will be required
to have it synced to central.  Thus, we'll need SOMETHING there.  Thus, we either have to
"pollute" the pom with all of our details or we just add a single "The Apache CXF Team" developer
to the pom.   Thoughts?  (I prefer the single developer thing)

Thus, I'm OK with 2 and 4 on the list, OK with adding a developers element for 3, semi-OK
with 1 except for the properties element, and I'm not sure if 5 is even relevant as I think
it was already pretty cleanly formatted.




> Update Apache CXF's main pom.xml file
> -------------------------------------
>
>                 Key: CXF-3102
>                 URL: https://issues.apache.org/jira/browse/CXF-3102
>             Project: CXF
>          Issue Type: Improvement
>          Components: Build system
>    Affects Versions: 2.3.0
>            Reporter: Robert Liguori
>            Priority: Minor
>         Attachments: pom.xml, pom_diff.txt
>
>
> Familiarizing myself with Apache's CXF's build process, I made a few refinements to the
main pom.xml file (note: testing is needed on these changes).
> Below are descriptions of the changes, the updated pom.xml from the CXF 2.3.0 project
and a diff file between the old and new pom.xml files are attached.
> The refinements:
> 1) Reorganized elements relative to Maven project descriptor reference: http://maven.apache.org/ref/2.2.1/maven-model/maven.html
> 2) Added "description" element.  Note: This description should be expanded by someone
more versed in CXF's main features.
> 3) Added empty elements where there is no present content.
> 4) Made the following versioning changes:
> Updated maven-project-info-reports-plugin from 2.1.1 to 2.2.  
> Referenece: http://maven.apache.org/plugins/maven-project-info-reports-plugin/jira-report.html
> Updated maven-javadoc-plugin from 2.6 to 2.7.  
> Reference: http://maven.apache.org/plugins/maven-javadoc-plugin/jira-report.html
> Updated maven-release-plugin from 2.0 to 2.1. 
> Reference: http://maven.apache.org/plugins/maven-release-plugin/usage.html
> 5) Performed formatting using NetBeans default XML formatting settings.
> 6) Question: Shouldn't there be a parent element?  I made no changes here, but think
that there should be.
> Note: If you open up the attached pom.xml file in Firefox, you will not see the applied
spacing (but it's there).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message