Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "John B. Matthews" Newsgroups: comp.lang.java.programmer Subject: Re: How Do I Publish My Working Project (corresponding dot jar doesn't work on other's PCs) Date: Fri, 07 Sep 2012 21:28:32 -0400 Organization: The Wasteland Lines: 38 Message-ID: References: <08dcc4bb-ac13-4992-b576-1d4f51a28d2e@googlegroups.com> NNTP-Posting-Host: LQJtZWzu+iKlBROuDg+IUg.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: MT-NewsWatcher/3.5.3b3 (Intel Mac OS X) X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:18600 In article , Lew wrote: > > Check the contents of your dist/ directory, and the project jar. If > > it doesn't include these features then it's not a proper Java > > "application" jar. That may mean that you didn't create it > > correctly, or NetBeans has cocked up (technical term) the project > > properties (this does happen). If this does happen the simplest > > alternative is to create a new Java Application project and copy > > all your sources into it. Fixing it manually requires dexterous > > manipulation of, IIRC, project.properties and build-impl.xml. > > Creating a new project is simpler, quicker, and less likely to bite > > you back in the future. > > You don't need to futz with NB-specific files if you edit manifests > yourself, and also you should build from "build.xml", not > IDE-specific artifacts. I like the flexibility NetBeans affords in this area: For convenience, I can use the stock, NB-generated build.xml, even from the command line, and hook into it as needed: Alternatively, I can add a small number of targets to my custom build.xml, and NB will happily adopt it in a free-form project: For example: -- John B. Matthews trashgod at gmail dot com