maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmed El-Madhoun (JIRA)" <j...@codehaus.org>
Subject [jira] (MASSEMBLY-343) add symbolic links managment
Date Sun, 16 Sep 2012 20:10:21 GMT

    [ https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308651#comment-308651
] 

Ahmed El-Madhoun commented on MASSEMBLY-343:
--------------------------------------------

Hi Zuhayr,

I was able to get the proper revisions of the maven plugins and plexus components (as listed
above), however, I am having trouble building the assembly plugin.  All code patches fine,
except that I run into this issue:

[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR : 
[INFO] -------------------------------------------------------------
[ERROR] /home/aelmadho/ASSEMBLY/maven/plugins/maven-assembly-plugin-2.2.1/target/generated-sources/modello/org/apache/maven/plugin/assembly/model/io/xpp3/AssemblyXpp3Writer.java:[291,119]
error: unclosed string literal
[ERROR] /home/aelmadho/ASSEMBLY/maven/plugins/maven-assembly-plugin-2.2.1/target/generated-sources/modello/org/apache/maven/plugin/assembly/model/io/xpp3/AssemblyXpp3Writer.java:[292,10]
error: unclosed string lite

The file in context (AssemblyXpp3Writer) looks like this at line 291-292:

       if ( ( dependencySet.getOutputFileNameMapping() != null ) && !dependencySet.getOutputFileNameMapping().equals(
"${artifact.artifactId} ${artifact.version}${dashClassifier?}.${artifact.extension}
          " ) )
        {
            serializer.startTag( NAMESPACE, "outputFileNameMapping" ).text( dependencySet.getOutputFileNameMapping()
).endTag( NAMESPACE, "outputFileNameMapping" );
        }


There seems to be a "\n" character at the end of the logical comparison that the parser fails.
 I am not very familiar with Xpp3, I need to do some more reading there, but I was hoping
to try and generate maven artifacts including symlinks using the solution you have proposed.

Any idea on how I can proceed?

Thanks a bunch.

                
> add symbolic links managment
> ----------------------------
>
>                 Key: MASSEMBLY-343
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-343
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Wish
>    Affects Versions: 2.2-beta-2
>         Environment: linux, ubuntu 
>            Reporter: Godet Gilles
>         Attachments: MASSEMBLY-343_maven-assembly-plugin.patch
>
>
> i need to buid archives ( tar for example ) with symbolic links
> the plugin build an archive with a file containing the destination of the link, not the
link itself
> => the plugin need an option to know if deferencement of links is needed 
> this is just like -h option of tar
>   -h, --dereference
>               don't dump symlinks; dump the files they point to
> actually, if you do an archive of /lib, for example, many file will be in double with
différent names. extract of archive will not be the exactly the same as the source of the
archive. => this is a test !

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message