Bug 530639 - tomcat-parent POM needs a new home
Summary: tomcat-parent POM needs a new home
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: tomcat5
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Devrim Gündüz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 538868
TreeView+ depends on / blocked
 
Reported: 2009-10-23 21:40 UTC by Jerry James
Modified: 2010-12-04 03:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 03:43:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jerry James 2009-10-23 21:40:10 UTC
Description of problem:
These packages:

  tomcat5-jasper
  tomcat5-jsp-2.0-api
  tomcat5-servlet-2.4-api

install the following POMs:

  JPP-jasper5-compiler.pom
  JPP-jasper5-runtime.pom
  JPP-tomcat5-jsp-2.0-api.pom
  JPP-tomcat5-servlet-2.4-api.pom

all of which refer to a tomcat-parent POM.  However the tomcat-parent POM is not supplied by any of the dependencies of these packages, resulting in a build failure when I try to use the servlet POM.  It looks like the tomcat-parent POM is in the tomcat5 package, which doesn't seem like a good idea, due to the number of dependencies it drags in.  Can we move the tomcat-parent POM somewhere else, maybe a tomcat5-parent-pom subpackage that depends only on commons-logging?  Then the packages mentioned above would Require this new subpackage to make the POMs work out right.

Version-Release number of selected component (if applicable):
tomcat5-5.5.27-7.4.fc12.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Try to build a maven-using project that refers to the servlet 2.4 API without having tomcat5 installed.
  
Actual results:
The build fails due to being unable to resolve the tomcat-parent name.

Expected results:
The build succeeds.

Additional info:

Comment 1 Bug Zapper 2009-11-16 14:08:44 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2010-11-04 09:11:42 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2010-12-04 03:43:52 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.