Thread: using open source project in our application

That almost definitely depends on the project. I'd send the developers an email just to make sure.

This thread has been cross posted here:

http://www.java-forums.org/web-frameworks/48786-using-open-source-project-our-application.html

Although cross posting is allowed, for everyone's benefit, please read:

Java Programming Forums Cross Posting Rules

The Problems With Cross Posting

Originally Posted by the light

regarding cross posting:
we do this just to get as much opinions as we can from various resources :-)

Read the link I posted about the problems with cross-posting. It's very rude because it wastes our time. There are thousands of questions on these forums, so it's a waste of time to answer a question that has already been answered, or to repeat an answer you've already received. Simply linking your crossposts to each other fixes that problem, because at the very least, we can see what other people have already told you. Being rude and treating our time as meaningless is one way to convince people NOT to help you.

Originally Posted by the light

anyways,
i would be thankful if u make me clear about my query.

I already gave you an answer, and you've already made it clear you don't care about my time. So unless you have something more specific to ask (with relevant links to any crossposts of the same question), I'm done here.

5. You may charge a reasonable copying fee for any distribution of this
Package. You may charge any fee you choose for support of this Package.
You may not charge a fee for this Package itself. However,
you may distribute this Package in aggregate with other (possibly
commercial) programs as part of a larger (possibly commercial) software
distribution provided that you do not advertise this Package as a
product of your own.

6. The scripts and library files supplied as input to or produced as
output from the programs of this Package do not automatically fall
under the copyright of this Package, but belong to whomever generated
them, and may be sold commercially, and may be aggregated with this
Package.


7. C or perl subroutines supplied by you and linked into this Package
shall not be considered part of this Package.

So it depends on what you're planning on doing:

If you're going to modify their project (or Package), you must provide the changes made to the package in a public domain. However, it sounds like you're allowed to use their package in a proprietary program under it's current license. If you're just using the package to create a file or something for your project, that artwork is yours and you can do whatever you want with it.

Basically, it sounds like the terms of the license are similar the LGPL license, but if you want to make sure ask an attorney.