[ 
https://issues.apache.org/jira/browse/MSHADE-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MSHADE-153.
---------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period 
of time. If you think this issue still applies, retest your problem with the 
most recent version of Maven and the affected component, reopen and post your 
results.

> Relocating all classes packages preappends that pattern to date strings
> -----------------------------------------------------------------------
>
>                 Key: MSHADE-153
>                 URL: https://issues.apache.org/jira/browse/MSHADE-153
>             Project: Maven Shade Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0
>         Environment: Intelij- IDEA
>            Reporter: sam schumer
>            Priority: Major
>
> When relocating all all classes for a given project, I ran into issues with 
> date stings. The relocations were formatted in the pom as:
> <relocation>
>    <!--<pattern></pattern>-->
>    <shadedPattern>apitests.</shadedPattern>
> <relocation>
> The original idea for relocating everything in this way was to avoid 
> non-compatible versions when this project is imported, and it worked once I 
> excluded all java files from relocation. 
> However it seems that shade was pre-appending the strings "apitest." to 
> strings inside class files that had nothing to do with the location of 
> classes. Specifically when formatting a 
> "com.fasterxml.jackson.databind.util.StdDateFormat" which should have been 
> "yyyy-MM-dd'T'HH:mm:ss.SSSZ" it threw an illegal argument exception when 
> trying to parse the date string "apitests.yyyy-MM-dd'T'HH:mm:ss.SSSZ" It 
> would appear that shade pre-appended "apitests." to multiple strings which 
> follow a very similar format to strings which like locations of files. 
> Edit: submitted before I was read edit completes the issue
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to