Mule

WSSecurity not released in 1.4.1

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.4.1
  • Fix Version/s: 1.4.2
  • Component/s: Build: Distributions
  • Labels:
    None
  • User impact:
    High
  • Similar Issues:
    MULE-1900 WSSecurity Module and WSS4J.Jar missing from 1.4.1 Release
    MULE-2917 Drop WSSecurity from 2.x
    MULE-2288 Maven archetype is not working for creating new connectors.
    MULE-1177 Upgrade commons-net to 1.4.1
    MULE-2000 Update i18n docs for 1.4.1+
    MULE-2100 Update slf4j to 1.4.1
    MULE-2506 Fix Tests in WS Security
    MULE-1952 When using 1.4.1, the sbin executables aren't found
    MULE-4847 Release 3.0-M3
    MULE-1710 Publish updated Mule 1.4.1 DTDs at http://mule.mulesource.org/dtds/mule-configuration.dtd

Issue Links

Duplicate
 

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Perepelytsya added a comment - 07/Jun/07 06:22 PM

Dirk, mule-module-wssecurity now ends up in $MULE_HOME/lib/opt, should be in /lib/mule/

The assembly verifier already checks it's in the build.

Show
Andrew Perepelytsya added a comment - 07/Jun/07 06:22 PM Dirk, mule-module-wssecurity now ends up in $MULE_HOME/lib/opt, should be in /lib/mule/ The assembly verifier already checks it's in the build.
Hide
Permalink
Dirk Olmes added a comment - 13/Jun/07 09:41 AM

fixed with MULE-1820

Show
Dirk Olmes added a comment - 13/Jun/07 09:41 AM fixed with MULE-1820

People

Vote (0)
Watch (0)

Dates

  • Created:
    07/Jun/07 06:19 PM
    Updated:
    13/Jun/07 09:41 AM
    Resolved:
    13/Jun/07 09:41 AM
Atlassian JIRA (v4.2#587) | Report a problem
Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.