Maven pom has invalid parent

• Key: FILEUPLOAD-118
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Blocker
• Assignee: Unassigned
• Reporter: Dain Sundstrom

Description

The correct parent for commons seems to be artifactId=commons-parent, but the pom has artifactId=commons. This prevents building with m2.

Comments

[Henri Yandell]

Yup, can't say I understand why it's commons-parent and not commons. All of the components within Commons with pom.xml's that refer to the parent pom say 'commons'. I'm +1 to changing it back.

'commons-parent/' is also not in the svn:externals for trunks-proper.

There are also pom.xml's that do not reference the parent (scxml, logging).

[Henri Yandell]

ping. The notification for fileupload was turned off, so I've turned it back on and am making sure this issue hits the list.

[Jochen Wiedmann]

The change to commons-parent was discussed in

http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=116012264831061&w=2

The main reason for using "commons-parent" and not "commons" is that the module is now located at

http://svn.apache.org/repos/asf/jakarta/commons/proper/commons-parent/

and no longer at

http://svn.apache.org/repos/asf/jakarta/commons/trunks-proper/

[Henri Yandell]

All commons children poms should now point to commons-parent.