Solved

No lib folder and no class-path in manifest when compiling a NetBeans project on a machine which just has Ant

Posted on 2008-09-29
2
934 Views
Last Modified: 2013-12-14
I am writing a Java application using NetBeans. As part of an automated build process, I need to be able to build the projects on a machine that does not have NetBeans installed. It has Ant, however.

For now, I am just creating a new Java Desktop Application, which uses Swing.

When I compile using NetBeans (or using Ant on the machine where NetBeans is installed), the manifest.mf file in the jar contains a class-path entry which is not present when installing on the other machine. Also, a lib folder is created with the two utility jars required for Swing.

There is a difference in the steps that Ant performs on each machine.

On NetBeans machine, -do-jar-with-libraries is executed.
On server, -do-jar-with-mainclass is executed.

This appears to be why the extra steps aren't being performed, so how do I get Ant to perform the correct steps?

I don't want to modify any files in the project, but I have had to create a .properties file outside the project anyway to specify libs.swing-app-framework.classpath and libs.CopyLibs.classpath, so if there is something simple I can add to this file that would solve the problem, that would be great.

Something to do with mkdist.available?

TIA!
0
Comment
Question by:scuzzie
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 6

Expert Comment

by:wwnosal
ID: 22599235
Try to include attached snippet somewhere in -do-jar-with-mainclass target before jar is actually created.
<manifest>
  <attribute name="Main-Class" value="${main.class}"/>
  <attribute name="Class-Path" value="${jar.classpath}"/>
</manifest>

Open in new window

0
 
LVL 1

Accepted Solution

by:
scuzzie earned 0 total points
ID: 22601006
It seems that once I had specified libs.CopyLibs.classpath in an additional build.properties file, this was enough to switch conditions and cause the correct path to run.

I just had to specify the path on the ant command-line:
ant -propertyfile ../build.properties jar

worked for me.
0

Featured Post

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

By the end of 1980s, object oriented programming using languages like C++, Simula69 and ObjectPascal gained momentum. It looked like programmers finally found the perfect language. C++ successfully combined the object oriented principles of Simula w…
Introduction This article is the second of three articles that explain why and how the Experts Exchange QA Team does test automation for our web site. This article covers the basic installation and configuration of the test automation tools used by…
Viewers will learn about basic arrays, how to declare them, and how to use them. Introduction and definition: Declare an array and cover the syntax of declaring them: Initialize every index in the created array: Example/Features of a basic arr…
This tutorial explains how to use the VisualVM tool for the Java platform application. This video goes into detail on the Threads, Sampler, and Profiler tabs.
Suggested Courses

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question