Yes, pom is deprecated but stills works in 3.0-beta-1 I believe.
/Anders
On Fri, Jul 9, 2010 at 09:40, Robin Wenglewski <ro...@wenglewski.de> wrote:
> Hi guys,
>
> I am experiencing problems when using the maven-assembly-plugin. In
> the main pom.xml i got
>
> <plugins>
> <plugin>
> <artifactId>maven-assembly-plugin</artifactId>
> ...
> <configuration>
> <descriptors>
> <descriptor>src/main/assembly/bin.xml</descriptor>
>
> <descriptor>src/main/assembly/common.xml</descriptor>
> </descriptors>
> </configuration>
> </plugin>
> </plugins>
>
> In the bin.xml I have different output directories, all looking like that:
>
> <fileSet>
> <directory>src/main/bin/bin</directory>
>
> <outputDirectory>test-${project.version}/bin</outputDirectory>
> <fileMode>0755</fileMode>
> </fileSet>
>
> This compiles well under Ubuntu 10.04. However, under mac the
> ${project.version} does not get substituted. When I substitute the
> ${project. through ${pom. everywhere, everything works fine. My setup
> is
>
> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0_20
> Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x" version: "10.6.4" arch: "x86_64" Family: "mac"
>
> From the page
> http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
> I got, that pom is deprecated and project is the one to use. Which is
> it now? Will sustituting $pom everywhere break in future versions?
>
> Thanks,
> Robin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
