geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher James Blythe (JIRA)" <>
Subject [jira] Commented: (DAYTRADER-20) Daytrader ear includes lots of kitchen sinks
Date Wed, 10 Jan 2007 15:03:27 GMT


Christopher James Blythe commented on DAYTRADER-20:

Hmmm..... I haven't noted this at all when building from the 1.2 branch. The only jar/war
files that are packaged inside the ear are the ones that should be there...

Did you make any changes to the 1.2 branch to fix this? Can this issue be closed?

Archive:  daytrader-ear-1.2-SNAPSHOT.ear
    testing: META-INF/                OK
    testing: META-INF/MANIFEST.MF     OK
    testing: dt-ejb.jar               OK
    testing: streamer.jar             OK
    testing: wsappclient.jar          OK
    testing: web.war                  OK
    testing: META-INF/LICENSE.txt     OK
    testing: META-INF/application.xml   OK
    testing: META-INF/NOTICE.txt      OK
    testing: META-INF/maven/          OK
    testing: META-INF/maven/org.apache.geronimo.daytrader/   OK
    testing: META-INF/maven/org.apache.geronimo.daytrader/daytrader-ear/   OK
    testing: META-INF/maven/org.apache.geronimo.daytrader/daytrader-ear/pom.xml   OK
    testing: META-INF/maven/org.apache.geronimo.daytrader/daytrader-ear/   OK

> Daytrader ear includes lots of kitchen sinks
> --------------------------------------------
>                 Key: DAYTRADER-20
>                 URL:
>             Project: DayTrader
>          Issue Type: Bug
>          Components: buildsystem
>    Affects Versions: 1.2
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: 1.2
> Currently the ear includes about 10-15 dependent jars it shouldn't.  The m2 dependency
scopes need to be adjusted to fix this.
> I'll fix this in trunk (2.0), also an issue in 1.2 branch

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message