Thanks for the suggestion - that worked, although it isn't ideal. I'm
looking at this with Jakarta Commons in mind, where (possibly) many
components would inherit from a main pom.xml. Using this approach a
component could override the "maven-compiler-plugin" configuration and
then what was being output to the manifest would not be the values the
compiler actually used. Is there no way of getting a reference to the
compiler plugin and accesssing its configuration values?
Niall
On 2/14/06, dan tran <[EMAIL PROTECTED]> wrote:
> Create a property set
>
> <properties>
> <source>1.3</source>
> <target>1.3</target>
> </properties>
>
> Look up the Pom descriptor to where to place it.
>
> Then you can use ${source} and ${target} both plugin configurations
>
> -D
>
> On 2/13/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> >
> > I'm trying to reference a plugin configuration attribute in another
> > plugin's configuration in maven2. Can anyone point me in the right
> > direction?
> >
> > Specifically I want to output two config attributes (source & target
> > JVM) from the "compile" in the jar's manifest file, so I have the
> > following:
> >
> > <plugin>
> > <artifactId>maven-compiler-plugin</artifactId>
> > <configuration>
> > <source>1.3</source>
> > <target>1.3</target>
> > </configuration>
> > </plugin>
> >
> > <plugin>
> > <artifactId>maven-jar-plugin</artifactId>
> > <configuration>
> > <archive>
> > <manifestEntries>
> > <Source-JDK>${maven.compile.source}</Source-JDK>
> > <Target-JDK>${maven.compile.target}</Target-JDK>
> > </manifestEntries>
> > </archive>
> > </configuration>
> > </plugin>
> >
> > I have used property values ${maven.compile.target} in maven1 - is
> > there anyway I can reference the source/target configuration values
> > for "maven-compiler-plugin" in the "maven-jar-plugin" confiuration
> > items?
> >
> > Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
