On 19/11/2007, dennisl@apache.org <dennisl@apache.org> wrote:
> Author: dennisl
> Date: Mon Nov 19 09:10:07 2007
> New Revision: 596370
>
> URL: http://svn.apache.org/viewvc?rev=596370&view=rev
> Log:
> Use the correct value for the X-Compile-Target-JDK manifestEntry.
>
> Modified:
> commons/proper/commons-parent/trunk/pom.xml
>
> Modified: commons/proper/commons-parent/trunk/pom.xml
> URL: http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?rev=596370&r1=596369&r2=596370&view=diff
> ==============================================================================
> --- commons/proper/commons-parent/trunk/pom.xml (original)
> +++ commons/proper/commons-parent/trunk/pom.xml Mon Nov 19 09:10:07 2007
> @@ -172,7 +172,7 @@
> <Implementation-Vendor>${project.organization.name}</Implementation-Vendor>
> <Implementation-Vendor-Id>org.apache</Implementation-Vendor-Id>
> <X-Compile-Source-JDK>${maven.compile.source}</X-Compile-Source-JDK>
> - <X-Compile-Target-JDK>${maven.compile.source}</X-Compile-Target-JDK>
> + <X-Compile-Target-JDK>${maven.compile.target}</X-Compile-Target-JDK>
Have any formal releases been affected by this bug?
I.e. where compile.target != source.target
If so, what should be done?
> </manifestEntries>
> </archive>
> </configuration>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
|