harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George Harley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-245) clean-layout target in build-java.xml keeps wiping security provider jar
Date Fri, 24 Mar 2006 11:54:19 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-245?page=comments#action_12371717 ] 

George Harley commented on HARMONY-245:

HARMONY-208 sounds great. However, at the moment the clean-layout target doesn't take into
account that a developer may have other stuff in jre/lib/ext (a customised version of the
BC provider jar ? Perhaps another kind of provider jar altogether ?). It's a pain to have
to copy such resources back in after every build. I think that HARMONY-208 and HARMONY-245
are both relevant without any obsolescence.

Best regards, 

> clean-layout target in build-java.xml keeps wiping security provider jar
> ------------------------------------------------------------------------
>          Key: HARMONY-245
>          URL: http://issues.apache.org/jira/browse/HARMONY-245
>      Project: Harmony
>         Type: Improvement
>   Components: Misc
>  Environment: All
>     Reporter: George Harley
>     Priority: Minor
>  Attachments: harmony-245.txt
> A full build of Harmony always deletes the contents of ${target.output}/jre/lib/ext which
can be really irritating if it already contains an (unsigned) Bouncy Castle provider jar previously
copied in. Solution is to add another exclusion entry to the delete task of the clean-layout
> Best regards, 
> George

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