> The real issue is that there is few libraries in java that are GPL
> compatible. Even essentials like xml parsers don't really have a showing,
> nor can you use standard extentions - thus most "GPL" java projects ignore
> this and violate the GPL ;) The exception being the GNU projects which are
> relatively clean.
Up until recently, I have sort of ignored the license issues and just used
whatever I could get my greedy hands on. I'm sure at sometime I may have
technically violated a license out of confusion and laziness. Now that I'm
working on my own free open source project, picking a license has become an
issue. My project uses several ASL projects and one LGPL. I also want to use
the Mckoi DB, but it is GPL. At this point, I believe I can release my code
under both GPL and modified BSD and if a user needs to use my project code
for propriety use, they can swap out the Mckoi DB for something else and
everything is cool. I admit to being license illiterate and my opinion about
them so far has been limited to... the shorter the better.
On a side note, I have a prototype of my project and it is very hardwired
right now. I think my project may need to be re-developed using a component
based framework, since I want the ability to swap and configure components
at runtime, plus the components need to be context aware. I'm thinking
Avalon may be a good fit, but I'm still pretty clueless about some parts of
it, so I'm digging into the docs and code at this moment. I may have to ask
a few questions...
Thanks
-david
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
