Maven assembly plugin : includeBaseDirectory not correctly used
Hi,
It's the first time I post a bug on a maven plugin. If that's the wrong
way, please let me know where to do it. I found the issue tracker but I'm
unable to create new issue.
My problem:
I use the assembly plugin, with the tag in the
assembly.xml file. If I put a variable (${mine.includeBaseDirectory}) in
the tag, it's not taken into account.
But if I use true or false, that fine.
I have created a small project that shows the problem. It's attached.
*To reproduce:*
- unzip the attachment
- cd maven-assembly-bug/
- mvn clean install assembly:single
The file maven-assembly-bug-1.0.0-SNAPSHOT.tar.gz doesn't contain the
baseDir, while the variable used is set to true
If you change the value in assembly.xml to true or false (instead of using
the variable), that's worting fine.
Any idea?
Thanks a lot.
--
Jean-Eric Cuendet
Le Pré des Buis 1
CH - 1315 La Sarraz
Blog: http://jesc.ch
<http://jesc.ch>LinkedIn: http://www.linkedin.com/profile/view?id=1456133
<http://jesc.ch>FB: http://www.facebook.com/profile.php?id=12135244701
Mobile: +41 76 222 3343
maven-assembly-bug.tar.gz
Description: GNU Zip compressed data
[jira] (MASSEMBLY-743) not correct
Jean-Eric Cuendet created MASSEMBLY-743:
---
Summary: not correct
Key: MASSEMBLY-743
URL: https://jira.codehaus.org/browse/MASSEMBLY-743
Project: Maven Assembly Plugin
Issue Type: Bug
Affects Versions: 2.5.2
Reporter: Jean-Eric Cuendet
Attachments: maven-assembly-bug.tar.gz
I use the assembly plugin, with the tag in the
assembly.xml file. If I put a variable (${mine.includeBaseDirectory}) in the
tag, it's not taken into account.
But if I use true or false, that fine.
I have created a small project that shows the problem. It's attached.
To reproduce:
- unzip the attachment
- cd maven-assembly-bug/
- mvn clean install assembly:single
The file maven-assembly-bug-1.0.0-SNAPSHOT.tar.gz doesn't contain the baseDir,
while the variable used in the tag is set to true
If you change the value in assembly.xml to true or false (instead of using the
variable), that's worting fine.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-743) not correct
[
https://jira.codehaus.org/browse/MASSEMBLY-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358714#comment-358714
]
Jean-Eric Cuendet commented on MASSEMBLY-743:
-
After analysis, the value set between the tag,
${min.includeBaseDirectory} is converted in Boolean while reading the assembly
descriptor. Since it's not a valid boolean value, it's transformed to the
default value : false
The resolution of variables into values is done after the assembly descriptor
reading. And at that moment the variable is lost.
To correct, there is 2 way:
1. In the Assembly class, have 2 values, one as String containing the variable,
another Boolean value containing the resolved value
2. Resolve the variables to values while reading the assembly descriptor.
Which one do you prefer?
I can try to correct that one and post a patche if you give some guidance.
> not correct
> --
>
> Key: MASSEMBLY-743
> URL: https://jira.codehaus.org/browse/MASSEMBLY-743
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Jean-Eric Cuendet
>Assignee: Kristian Rosenvold
> Fix For: 2.5.3
>
> Attachments: maven-assembly-bug.tar.gz
>
>
> I use the assembly plugin, with the tag in the
> assembly.xml file. If I put a variable (${mine.includeBaseDirectory}) in the
> tag, it's not taken into account.
> But if I use true or false, that fine.
> I have created a small project that shows the problem. It's attached.
> To reproduce:
> - unzip the attachment
> - cd maven-assembly-bug/
> - mvn clean install assembly:single
> The file maven-assembly-bug-1.0.0-SNAPSHOT.tar.gz doesn't contain the
> baseDir, while the variable used in the tag is set to
> true
> If you change the value in assembly.xml to true or false (instead of using
> the variable), that's worting fine.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MASSEMBLY-743) not correct
[
https://jira.codehaus.org/browse/MASSEMBLY-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359073#comment-359073
]
Jean-Eric Cuendet commented on MASSEMBLY-743:
-
Thanks a lot!
When will it be released on Maven central?
> not correct
> --
>
> Key: MASSEMBLY-743
> URL: https://jira.codehaus.org/browse/MASSEMBLY-743
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.5.2
> Reporter: Jean-Eric Cuendet
>Assignee: Kristian Rosenvold
> Fix For: 2.5.3
>
> Attachments: maven-assembly-bug.tar.gz
>
>
> I use the assembly plugin, with the tag in the
> assembly.xml file. If I put a variable (${mine.includeBaseDirectory}) in the
> tag, it's not taken into account.
> But if I use true or false, that fine.
> I have created a small project that shows the problem. It's attached.
> To reproduce:
> - unzip the attachment
> - cd maven-assembly-bug/
> - mvn clean install assembly:single
> The file maven-assembly-bug-1.0.0-SNAPSHOT.tar.gz doesn't contain the
> baseDir, while the variable used in the tag is set to
> true
> If you change the value in assembly.xml to true or false (instead of using
> the variable), that's worting fine.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] Created: (MNG-4692) Maven choose the wrong transitive dependency
Maven choose the wrong transitive dependency Key: MNG-4692 URL: http://jira.codehaus.org/browse/MNG-4692 Project: Maven 2 & 3 Issue Type: Bug Components: Inheritance and Interpolation Affects Versions: 2.2.1 Environment: Ubuntu Linux, JVM 1.6.0_18 OpenJdk Reporter: Jean-Eric Cuendet Attachments: bugmaven.tar.gz I have a dependency used by 2 sub-projects (spring-core) but with 2 different versions (2.5.5 and 2.5.6.SEC01) My project which uses theses 2 sub-projects gets spring-core 2.5.5 instead of the more recent 2.5.6.SEC01 I attach a test project which illustrates this case. To reproduce: 1. untar proj.tar.gz 2. Run ./build.sh 3. Have a look at the xxx-tree.log generated files The dep for apireg is 2.5.5 -> OK The dep for rcpers-core is 2.5.6.SEC01 -> OK The dep for adam-services is 2.5.5 -> NOK (Should be 2.5.6.SEC01 since it depends on rcpers-core) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
