wolverine my wrote:
Hi!
I created a JAR with the following Ant task:
The HelloWorld.jar contains two manifest files:
...
META-INF/MANIFEST.MF
HelloWorld.mf
Both manifest files are the same except that the MANIFEST.MF contains
two extra lines:
Ant-Version: Apache Ant 1.7.0
Created-By
Hi!
I created a JAR with the following Ant task:
The HelloWorld.jar contains two manifest files:
...
META-INF/MANIFEST.MF
HelloWorld.mf
Both manifest files are the same except that the MANIFEST.MF contains
two extra lines:
Ant-Version: Apache Ant 1.7.0
Created-By: 1.5.0_11-b03 (Sun
Thank you very much Conor. We just have passed over
the problem making Maven to build up the manifest
following instructions defined in POMs. So we
completely ignore old manifest files from single
projects in order to follow artifact dependencies
defined in POMs.
Thank you once again
Jo
Giovanni,
>
> Just tried, but it doesn't work completely. The
> resulting manifest is compilant but some dependencies
> in class-path are missing.
>
It should work. The process Stefan outlines ultimately uses the merge()
method you identified below, so if you were to use that directly you
would
nto one. I can't find the way to merge up
> all
> > manifest files from many projects into a single
> one.
>
> There is no built-in one.
>
> What probably would work is to create jar files for
> each of your
> manifests (putting the manifests in as
> META-IN
On Thu, 2 Feb 2006, Giovanni Mesturini <[EMAIL PROTECTED]> wrote:
> I'm going to set up a temporary-maven-compilant
> project, taking source code from many different src
> dirs into one. I can't find the way to merge up all
> manifest files from many projects into a si
Hi all,
I'm going to set up a temporary-maven-compilant
project, taking source code from many different src
dirs into one. I can't find the way to merge up all
manifest files from many projects into a single one.
Any suggestion?
I've also considered the possibility to use a
(u
On Wed, 23 Jul 2003, Vikas Phonsa <[EMAIL PROTECTED]> wrote:
> How can have ant to automatically update the Manifest File every
> time I do a build so that the Manifest file would have the current
> time stamp as the Version Number/Tag of the jars to be created.
Use the task, something like
> Can you send me an example (or raise a bug and attach it). I'll
> investigate. The manifest handling is done with the JDK's
> Jar/Manifest classes
Will do - I'll open a bug, and attach an example, hopefully by Monday.
Kyle