Authentication-results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
Delivered-to: email@hidden
Delivered-to: email@hidden
Thread-index: AcpbjUzFDcjh3XSzMEOZBLTKeBFeLQ==
Thread-topic: Package information in manifest, without JAR?
User-agent: Microsoft-Entourage/12.20.0.090605
Hi
The first point that I responding to is: ³However, during development, it's
not practical to package all classes
into a JAR file for every test-run (waste of time)².
Maven does that for every build, so there is no extra effort for you to do
that.
If you want to put something into the manifest, then create a manifest file
in your src/main/resources.
Still, since you use Maven already, you probably know all this anyway. So I
guess I don't really understand what your question really is.
Maybe what you need to do is create two modules. One that creates the jar
file, and another that runs tests that use the jar file and so can test its
contents?
Regards
Nathan
On 31/10/2009 19:07, "Harald Kuhr" <email@hidden> wrote:
> Hi Nathan,
>
> I'm quite familiar with Maven. I have a completely mavenized build, and use
> Maven (maven-jar-plugin) to create the manifest for my JARs. But I don't
> understand how Maven will help me here...
>
> Do you have some more specific information on how Maven can help me in this
> case?
>
>
> Thanks,
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden