[jira] Updated: (MASSEMBLY-426) Inconsistant inheritance
[ http://jira.codehaus.org/browse/MASSEMBLY-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MASSEMBLY-426: -- Fix Version/s: (was: 2.2) > Inconsistant inheritance > > > Key: MASSEMBLY-426 > URL: http://jira.codehaus.org/browse/MASSEMBLY-426 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-4 > Environment: mvn 2.0.9 jdk1.5 >Reporter: fabrice >Assignee: John Casey > Attachments: basedir.zip > > > Hi > A concret example is easy to understand : > My superPom contains : > > > ... > > > maven-assembly-plugin > > > > com.almerys.assemblies > > > My-jar-assembly-descriptor > > > 1.0.0.0.3 > > > > > make-assembly > package > > > single > > > > > > > And a child project overwritte the plugin conf to specify the assembly.xml > that is placed in My-jar-assembly-descriptor. But In this way I can specify > another assembly.xml that the default (in My-jar-assembly-descriptor) > > maven-assembly-plugin > > > > > assembly.xml > > > > > I have the error bellow : > Reason: Error reading assemblies: Error locating assembly descriptor file: > D:\workspace7.5\BatchAGLBPS\assembly.xml > Ok but if in my child I add for exemple the version (anyone it does not > matter) it works ! assembly plugin find the assembly.xml in my-jar-descriptor > ! > 2.2-beta-2 for instance > I do not understand is a bug ? > Fabrice > When I do a help:effective-pom I have my maven that say it uses 2.2-beta-1 in > the pluginManagment section and 2.2-beta-2 in the child... -- 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
[jira] Updated: (MASSEMBLY-426) Inconsistant inheritance
[
http://jira.codehaus.org/browse/MASSEMBLY-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MASSEMBLY-426:
Attachment: basedir.zip
bq. I think ${basedir} references the base directory of the topmost project,
while ${project.basedir} references the base directory for the project
currently being built.
In case we talk about POM interpolation, {{basedir}} and {{project.basedir}}
are synonyms, both resolve to the directory of the current (child) project, see
the attached example.
> Inconsistant inheritance
>
>
> Key: MASSEMBLY-426
> URL: http://jira.codehaus.org/browse/MASSEMBLY-426
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-4
> Environment: mvn 2.0.9 jdk1.5
>Reporter: fabrice
> Fix For: 2.2-beta-5
>
> Attachments: basedir.zip
>
>
> Hi
> A concret example is easy to understand :
> My superPom contains :
>
>
> ...
>
>
> maven-assembly-plugin
>
>
>
> com.almerys.assemblies
>
>
> My-jar-assembly-descriptor
>
>
> 1.0.0.0.3
>
>
>
>
> make-assembly
> package
>
>
> single
>
>
>
>
>
>
> And a child project overwritte the plugin conf to specify the assembly.xml
> that is placed in My-jar-assembly-descriptor. But In this way I can specify
> another assembly.xml that the default (in My-jar-assembly-descriptor)
>
> maven-assembly-plugin
>
>
>
>
> assembly.xml
>
>
>
>
> I have the error bellow :
> Reason: Error reading assemblies: Error locating assembly descriptor file:
> D:\workspace7.5\BatchAGLBPS\assembly.xml
> Ok but if in my child I add for exemple the version (anyone it does not
> matter) it works ! assembly plugin find the assembly.xml in my-jar-descriptor
> !
> 2.2-beta-2 for instance
> I do not understand is a bug ?
> Fabrice
> When I do a help:effective-pom I have my maven that say it uses 2.2-beta-1 in
> the pluginManagment section and 2.2-beta-2 in the child...
--
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
[jira] Updated: (MASSEMBLY-426) Inconsistant inheritance
[ http://jira.codehaus.org/browse/MASSEMBLY-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MASSEMBLY-426: - Fix Version/s: 2.2-beta-5 set to review this for the next release. > Inconsistant inheritance > > > Key: MASSEMBLY-426 > URL: http://jira.codehaus.org/browse/MASSEMBLY-426 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-4 > Environment: mvn 2.0.9 jdk1.5 >Reporter: fabrice > Fix For: 2.2-beta-5 > > > Hi > A concret example is easy to understand : > My superPom contains : > > > ... > > > maven-assembly-plugin > > > > com.almerys.assemblies > > > My-jar-assembly-descriptor > > > 1.0.0.0.3 > > > > > make-assembly > package > > > single > > > > > > > And a child project overwritte the plugin conf to specify the assembly.xml > that is placed in My-jar-assembly-descriptor. But In this way I can specify > another assembly.xml that the default (in My-jar-assembly-descriptor) > > maven-assembly-plugin > > > > > assembly.xml > > > > > I have the error bellow : > Reason: Error reading assemblies: Error locating assembly descriptor file: > D:\workspace7.5\BatchAGLBPS\assembly.xml > Ok but if in my child I add for exemple the version (anyone it does not > matter) it works ! assembly plugin find the assembly.xml in my-jar-descriptor > ! > 2.2-beta-2 for instance > I do not understand is a bug ? > Fabrice > When I do a help:effective-pom I have my maven that say it uses 2.2-beta-1 in > the pluginManagment section and 2.2-beta-2 in the child... -- 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
