Netbeans packages as source files

Hi,
I noticed that the Composer in NetBeans 6.9 creates (copies) new sources files in the project when some special components are used (like DataSource).
For example if a JDBC data source component is added, several files .fx are added in the project under the package "org.netbeans.javafx.datasrc".
Even if source files are instructive and interesting, I was expecting to have a dedicated components library and not sources file to be compiled.
They just increase compilation time and final jar dimension (compared to a library released with the JVM).
Can someone explain me the benefits of this choice ?
Grazie,
Gualtiero

You wrote:
c:\jarfiles> jar cfm jarfilename.jar c:\com\packages\
import com.packages.classfilename;What do you notice? The "root" of your JAR is at class level, you forgot to include the directory structure com/packages. So these class files can never be found.
Move your classes to c:\anemptydir\com\packages\ and run
jar cfm jarfilename.jar c:\anemptydir
(Be aware that the m option also requires you to name a manifest file.)
Now gimme some dukes.

Similar Messages

Compiling a package from source files

I am trying to install a package from source files. The installation instructions for this package say that I should just download the scripts to one directory, enter the correct paths in the Makefile (which comes with the package) and run "make".
The problem is that while the g++ compiler is there on my computer
(there is a binary called g++ located at
/Developer/usr/bin/g++
I am not sure if that is the real compiler. Or where the c header files are, for instance, I can't find math.h, or stdio.h or any of the other standard files.
Any help will be greatly appreciated. I am very new to command lines, so please explain as you would to a five year old.
To help with specifics, I edited the Makefile so that the first part looks like:
#MATLABDIR ?= /usr/local/matlab
# for Mac
MATLABDIR ?= /Applications/MATLAB_R2008b.app
CXX ?= g++
#CXX = g++-4.1
CFLAGS = -Wall -Wconversion -O3 -fPIC -I$(MATLABDIR)/extern/include
Thanks a ton for the help

Your compiler program is gcc. (/usr/bin/gcc).
http://gcc.gnu.org/
in terminal type (at the prompt):
gcc --version
(press return)
should output the following:
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5646) (dot 1)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
If it does, your compiler is alive and kicking and ready for action, if not, reinstall developer tools
package from your SL install DVD.
The usual ritual for compiling is to drag the directory containing the source code to your desktop,
then, in terminal, change terminal path to the source directory using the change directory command
"cd".
example; say I have a program called cdrtools 2.0.1 and the source is in a folder I dragged to my
desktop called cdrtools_2.0.1:
In terminal i would type:
cd /Users/kj/Desktop/cdrtools_2.0.1
Follow the instructions that come with the package. Typically they will tell you to:
./configure
( Many packages have a configure script which will query your system and configure themselves
appropriately. Not supported by all software).
make
( Compile the software. Some require a file name to build such as make foo. make reads a file
normally called Makefile for what commands to run).
make install
( Install the software. Typically packages will put themselves in /usr/local. Run as root).
That is the usual ritual, but you must follow the instructions that come with the software, as they
may vary.
Read documentation!
Look for files called: INSTALL, README, SETUP, or similar.
For more information see the following:
http://luv.asn.au/overheads/compile.html
Now beware that some source code written before Snow Leopard was released may not compile
properly on SL, because of SL's 64Bit gcc extensions. If the source has not been updated to run
under the Snow Leopard compiler, then the compilation may fail.
IF the program fails to compile, or fails to run after compiling, then most likely, then the source
may need updating.
good luck, and don't pull all your hair out at once. Save some for later.
The guys in the 'NIX forum can help you with all the grizzly details as you go on your quest.
http://discussions.apple.com/forum.jspa?forumID=735
Good luck,
Kj ♘

Problem compiling source file in package

Hi, I have 5 source files which I have just packaged together and put in the same sub-directory, the problem is that when I try to compile the file with the main method I get the error message:"cannot read" then the name of the source file. I am compiling from the command line and setting the classpath as I compile with the statement:
c:\j2sdk1.4.1\bin>javac -classpath c:\directory\package directory source file.java
I'm not sure what I am doing wrong and the source files all compiled fine before I added the package statement to the files. Please any help would really be appreciated.

It sounds like the java file your are trying to compile is not in the directory you are compiling from.
Is this basically what you are doing?:
Say the package name is mypackage.
Assume we are O.K. with keeping source and class files together.
Create a directory named 'mypackage' somewhere...C:\mypackage\.
Put all the .java files in it (these .java files indicate that they are a member of the 'mypackage' package).
At a command prompt, cd to the directory containing the 'mypackage' directory...'cd C:\'
Compile the source files: C:\j2sdk1.4.1\bin\javac mypackage\*.java
run the main class: C:\j2sdk1.4.1\bin\java mypackage.TheMainClass
Basically, this says keep the files where you want them and point to javac, instead of moving everything under java/bin. btw it will save a lot of typing if you add java/bin to your PATH.
Hope this helps.

[SOLVED] How to download package source files ? they become HTML

Hi. dumb one I'm afraid. I don't want to install ABS.
OK, so I'm not talking about AUR here, rather simply going to:
http://www.archlinux.org/packages/
Over on the right under, Package Actions
Source Files / View Changes
I click Source Files, i right click on the list of files amd get html downloaded and not the source files.
I like to build things myself on ocassion.
how to get files without using ABS!?
thank you!
Last edited by yvonney (2012-03-19 16:09:19)

You don't have to check out the whole abs tree:
* https://wiki.archlinux.org/index.php/Dw … s_with_ABS
* https://wiki.archlinux.org/index.php/Ar … d_ABS_tree
[karol@black ~]$ sudo abs community/dwm
==> Starting ABS sync...
receiving file list ... done
community/
community/dwm/
community/dwm/PKGBUILD
community/dwm/config.h
community/dwm/dwm.desktop
community/dwm/dwm.install
sent 172 bytes received 7885 bytes 2302.00 bytes/sec
total size is 7523 speedup is 0.93
[karol@black ~]$ du -sh /var/abs/
40K /var/abs/
The installed size of abs package is 120,00 KiB (on my 32-bit Arch).
The files it pulls (e.g. for dwm) are the same you can get manually, so abs is as minimal as it gets.
You call 'under 5 gigs' ultra-minimal. My full (and IMHO a bit bloated) system is about 3 GB.
Last edited by karol (2012-03-19 13:45:55)

[SOLVED]What to do when AUR provides source files, but no 'configure'?

Not sure if this is better posted here in "Newbie Corner" or in the "AUR" forum.... but I suppose it's a newbie-type question.
There's a package I've installed from AUR on another Arch system and the install process went smoothly then. New box; everything else is working fine and dandy, but need help with a package found in AUR.
The package installs source files -- no binaries available -- and there's no 'configure' file. There's a 'configure.in' file that gets parsed by 'autoconf', but there are errors, and no 'configure' gets created.
The PDF documentation from the author implies there's a 'configure' already prepared (the author writes the standard "Enter these commands: ./configure && make install"), and located in the src directory.
Is this an issue for the Arch package maintainer, or for the upstream author? And might I be pointed to a suitable resource to continue my own investigation?
Thanks!
Last edited by fionn (2013-10-06 19:49:25)

skottish wrote:
fionn wrote:
Trilby wrote:You *might* be looking for `makepkg -o` which is what gets the actual source code for the package.
Oh, Cr*p. This means I need to do it all over again and burn another CD.
I have a tinfoil-hat wearing conspiracy-theory nut of a brother-in-law who wants a new system, compiled from sources, "without Government Interference". He wants an "air-gap" (not networked) box to prevent NSA boogeymen from monkeying around with our Precious Bodily Fluids or some damned thing like that. Why is it always a brother-in-law who goes off the deep end? Why can't I have one who's a lawyer or doctor or something useful?
You know, you may gently want to look into the idea that you're taking advice from a hat wearing bird. I'm not suggesting anything, but it is something that you may want to consider.
On the upside, it does look to be an aluminum-free chapeau...

Deleting Updates source files

I am in the process of changing the Software update groups and Deployment packages. I am removing all the old Groups and packages, however I noticed that despite deleting the group and the package, the source files are still on the HDD. Is
there a process I need to go through to delete these? Since the Group and packages have been deleted, can I just delete the folder? I want to Create a new Deployment package, and re-download the updates, but I don't want to have the update residing
on the HDD in two places.

(Package) source files will not be deleted automatically - so you have to remove them manually (or scripted).
Torsten Meringer | http://www.mssccmfaq.de

How can I share a *.java source file across multiple projects in NetBeans?

I'm sure this simple and a pretty common operation but how can I share a *.java source file across multiple projects in NetBeans? Right now I keep cut, coping and pasting the same source file between multiple projects to re-use the same code. But I could I make this source file a library file or something like that so that I could access it from any project. I assume this would be a generic operation but I mentioned NetBeans for clarity. Thanks.

fiebigc wrote:
I know I mentioned NetBeans but I'm most interested in the generic method for creating a library of source files that I can call into whatever program I am developing. I've done such a thing in C using header files and such but I'm trying to get a direction on how this is accomplished in Java. I'm sorry if I could edit the title I would. If anyone wants to be specific about NetBeans I welcome that too.
Edited by: fiebigc on Jun 20, 2008 5:57 PM
>I know I mentioned NetBeans but I'm most interested in the generic method for creating a library of source files that I can call into whatever program I am developing. I've done such a thing in C using header files and such but I'm trying to get a direction on how this is accomplished in Java. I'm sorry if I could edit the title I would. If anyone wants to be specific about NetBeans I welcome that too.
Edited by: fiebigc on Jun 20, 2008 5:57 PM
Create a class library.
Write your code, compile it to .class files, put those class files in a .jar file and include the jar file in the classpath whenever you want to compile a project against it.

Compiling a seperate source file package

Hey everyone,
I've been trying to compile a package project for a university assignment for ages now but it just won't work. The assignment is purely about compiling the project in a certain way. The question says:
Create a sub-directory called 'src' which is a child of your main application directory and copy all the source files into this directory.
Which means that it wants this sort of structure:
./program name
./program name/src
./program name/classes
The problem is - no matter what i try it never compiles successfully. What would you suggest i try to compile it?

./program name
./program name/src
./program name/classesI always get an itchy feeling when I see spaces in
pathnames ...
kind regards,
JosSorry, the program name does not have spaces in.
I've also got it working now. Thanks for your reply!

Software Update Packages - the Package Source files are gone

I am running SCCM 2012 SP1. Something or someone deleted all my deployment package source files and folders for my software updates. Once I noticed they were gone, I was expecting there to be a simple way to have SCCM reload them from WSUS, since they should
still be there. However, I see no obvious way to do this in the GUI or from PowerShell. Is there a repair command for deployment packages that have lost their files?

Indeed, I just tested it in my environment and the real download won't start as long as it thinks that the updates are already downloaded.
The easiest way download them again is (if they are not all member of the same Software Update Group) temporarily add them to a SUP, delete them all from the deployment package and start the download again for all the updates in the (temporary) SUP.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Package with *many* source files, Stepmix songs for Stepmania

Hi, I would like to create a package for the Stepmix songs for Stepmania (http://www.stepmania.com/wiki/Download_StepMix_1_Songs and 6 other pages).
The problem is that there are many songs (about 500) and that there is no way to download them all at once.
I can see three solutions to this problem :
- Write a PKGBUILD with all the songs as source files, but the AUR page (and the PKGBUILD) will look terrifying and I'm not even sure that the website and/or makepkg accept PKGBUILDs with hundreds of source files
- Write an ugly script in the PKGBUILD grep'ing the Downloads pages to find every link which look like a download link and download them
- Write this ugly script only once to make a tgz containing all the songs, then store this on my website and tell the PKGBUILD to fetch the songs from here, but I'm not sure that the licence of the songs allow me to do that (a priori the copyright holders have only allowed to distribute the songs on the Stepmania website)
What do you think?
Fractal

Stepmania is a rythm game where you have to step on arrows in rythm with the music. To be able to play you must have songs : audio files *and* appropriate simfiles describing the arrows in sync with the music (and those files must be placed in /opt/stepmania or Stepmania will not see them).
The problem is that Stepmania doesn't include songs, once Stepmania is installed you cannot play because you still have to find songs and this is not that easy to find cool songs to play with.
That's why I think it would be very convenient to have an AUR package downloading some songs.
And yes, there are songs better than the others, but this is difficult to know which are better without trying them, so I guess that most users will want to have them all.
Fractal

[SOLVED] Creating src package when the source files must d/l manually

There's a program which requires to input some data before the GPL source can be downloaded.
http://www.csse.uwa.edu.au/cnet/download.html
When I put `source=('cnet-3.3.1.tgz')` in the PKGBUILD and put the archive in PKGBIULD's dir - it compiles and installs just fine.
However when creating a source file with `mkaurball` it puts the whole archive in the .src.tar.gz.
What do I do?
Last edited by axper (2014-06-28 12:11:58)

You should file a bug against pkgbuild-introspection , looks like mkaurball needs an extra check for archives in source array.
You could use makepkg --source for now, and upload the file that creates.
An alternative may be to edit the .src.tar.gz mkaurball created and delete the cnet*.tgz manually .
Not sure is editing .AURINFO is also needed .

Netbeans Package error

A project im working with in netbeans is showing the following error;
"Incorrect Package" (With the option to change package declaration to "X" ) Where X is the name of another project (from which the current project was created (importing existing sources))
It doesnt stop it from copiling or running, but I dont know what it means so i cant fix it, any ideas?
Thanks
J

Without really seeing your code and how the source files are structured in your file system, I'd have to guess that one or more of your source files' package statement conflicts with the directory hierarchy it is stored in. The directory hierarchy should match the package hierarchy. So for example, if a source file indicates it belongs in package a.b.c, then it should live in a directory ending in \a\b\c

Netbeans Package project setup

Using the good advice I have been given over the last few days from this forum I have setup the following directory structure :
<Root>
|
Amini
|
| | |
nb_projects packages_src packages_class
| |
com com
| |
bilbo bilbo
I want to preserve all my own package source and class files in the structure above but and have all my netbeans projects in nb_projects
If I start a new project in netbeans how can I make it store all the source files in the correct directory. For instance, if I make a "tax" package I want to develop it in a project folder in nb_projects but have the source files and class files put in c:\amini\packages_src\com\bilbo\tax ... etc
The new project wizard attempts this by asking Project loaction and Project folder but it creates another "src" folder under the tax folder which means that my package structure is compromised !!!
Really appreciate some help here. Thanks.

right-click the "Source Package" node in the project. Select "Properties". Click the add folder and name it. This will automatically include the new packages in the build.

Error 1308.Source file not found with 9.4.2 Admin Install point

I'm including as much information in this post as possible to help narrow down my problem, so if it's too wordy I appologize.
I've created an Admin install point for Acrobat 9 patching it up to Acrobat 9.4.2 using the following commands in a batch file:
D:
cd \Adobe\Acrobat\AcrobatPro9
md \Adobe\Acrobat\AcrobatPro9AIP
start /wait msiexec /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP /Liv D:\Adobe\Acrobat\AcrobatPro9AIP\install900.log /qn
cd \Adobe\Acrobat\AcrobatPro9AIP
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcroProStdUpd910_T1T2_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install910.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd912_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install912.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd920_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install920.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd930_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install930.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd932_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install932.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd933_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install933.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd940_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install940.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd941_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install941.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd942_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install942.log /qn
I rename the folder "AcrobatPro9AIP" to reflect the current version (e.g. "Acrobat9.4.2"), copy the folder to my DFS, create an MST with the Customization Wizard, and then deploy with Group Policy.
Before I deploy I always run a few test installations on two Windows XP 32-bit machines, and two Windows 7 64-bit workstations. I've been using this method to build my install point for the last 5 Adobe patches without a problem, but suddenly with version 9.4.2 my test workstations pop up with the following error during the installation via the standard installation method "msiexec /i acropro.msi TRANSFORMS=acropro.mst":
I built my installation package for acrobat9.4.1, 9.4.0 and 9.3.3 exactly the same way and the installations did not have this error. The file in question "Adobe.Acrobat.Dependencies.manifest" does not exist in my 9.4.1, or 9.4.0 package folders, nor does it exist in the 9.4.2 folder. Any suggestions?

I am having the same problem, all the relevant info was already covered in the "thewaker" post above.   I too have made a script to make a Admin install with patches up to 9.4.2. The script worked for 9.3.3 but when I remade the AdobeAIP for 9.4.2, I too got this error when installing it, even manually. (Error 1308.Source file not found. Adobe.Acrobat.Dependencies.manifest ) Running on Windows 7 32bit.
Here is my Script.
C:
cd\AcroBatPro9
md \AcrobatPro9AIP
start /wait msiexec /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP /Liv c:\AcrobatPro9AIP\install900.log /qn
cd \AcrobatPro9AIP
start /wait msiexec /p c:\AcrobatPro9\AcroProStdUpd910_T1T2_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install910.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd912_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install912.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd920_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install920.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd930_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install930.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd932_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install932.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd933_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install933.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd940_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install940.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd942_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install942.log /qn
I did notice though that the "thewaker" has added AcrobatUpd941_all_incr.msp to his script, which is a security update. Which may be "a" problem, but I don’t think this is related to the problem we are having.
Administrative deployment
Administration Installation Point (AIP) deployments must not apply a quarterly update AIP in which a security update was the most recently applied update. Because a quarterly update includes the changes implemented in all recent security updates, the quarterly update forcibly bypasses those updates entirely. To deploy a quarterly update from an AIP, create a AIP which includes only quarterly updates as follows:
    Acceptable:      Acrobat 9.0.0 -> 9.1.0 (Quarterly) -> 9.1.2 (Quarterly) -> 9.2.0 (Quarterly) -> 9.3.0 (Quarterly) -> 9.3.2 (Quarterly) -> 9.3.3 (Quarterly) -> 9.4.0 (Quarterly) -> 9.4.1 (Security)
    Acceptable:      Acrobat 9.0.0 -> 9.1.0 (Quarterly) -> 9.1.2 (Quarterly) -> 9.2.0 (Quarterly) -> 9.3.0 (Quarterly) -> 9.3.2 (Quarterly) -> 9.3.3 (Quarterly) -> 9.4.0 (Quarterly) -> 9.4.2 (Quarterly)
    Unacceptable: Acrobat 9.0.0 -> 9.1.0 (Quarterly) -> 9.1.2 (Quarterly) -> 9.2.0 (Quarterly) -> 9.3.0 (Quarterly) -> 9.3.2 (Quarterly) -> 9.3.3 (Quarterly) -> 9.4.0 (Quarterly) -> 9.4.1 (Security) -> 9.4.2 (Quarterly)
Anyway.. Any help with this would be helpful as I would like to deploy it soon.
Thanks.

Getting all the members (variables, methods AND method bodies) of a java source file

For a project I want to programmatically get access to the members of java source file (member variables, methods etc) as well as to the source code of those members. My question is what is the best method for this? So far I have found the following methods:
Use AST's provided by the Java Source API and Java Tree API, as discussed in the following posts:
http://today.java.net/pub/a/today/2008/04/10/source-code-analysis-using-java-6-compiler-apis.html
http://weblogs.java.net/blog/timboudreau/archive/2008/02/see_java_code_t.html
http://netbeans.dzone.com/announcements/new-class-visualization-module
This has the disadvantage that the classes actually have to be compilable. When I look at the Netbeans Navigator view however, it provides me with a nicely formatted UI list, regardless of the "compilable" state of the class.
Thus I started looking at how to do this... The answer appears to be through the use of tools such as JavaCC: https://javacc.dev.java.net/
ANTLR: http://www.antlr.org/
which are lexers and parsers of source code. However, since the Navigator panel already does this, couldn't I use part of this code to get me the list of variables and methods in a source file? Does the Navigator API help in this regard?
Another route seems to be through tools such as
BeautyJ: http://beautyj.berlios.de/
which run on top of JavaCC if I am correct, and which has the ability to provide a clean view on your java code (or an XML view). However, BeautyJ does not seem to be too actively developed, and is only j2se1.4 compatible.
I hope someone can shed a light on the best way to go about what I want to achieve. Somebody already doing this?
(I crossposted on the Netbeans forums too, hope this is OK...)

I'm currently developing a LaTeX editor(MDI) and I do the same thing, but I don't know what exactly do you need.

Netbeans packages as source files

Similar Messages

Maybe you are looking for