Hi Brett
Thank's a lot. So it was not the end. With a little help of my friends, we progress ;-)
These links help me a lot. I don't understand how I missed them before.
Brett Porter wrote:
Yes it is no info on where are maven CVS, which plugins are required etc. (and which release) and where are them CVS.
http://maven.apache.org/reference/plugins/optional/cvs-usage.html http://maven.apache.org/cvs-usage.html
The documentation is out of date - you'll need all the plugins.
When you want to run jellySwt demo. We must use maven demo.
Then (but if you are on a win32 machine) it cry this :
no swt-win32-2128 in java.library.path
In fact win32 is hardcoded in project.xml. (I follow to you a complete detailed explanation of problem)
You'll need to take that up with commons-user as you have done. I don't know anything about SWT.
I imagine it should be forking the test, and setting java.library.path at that point.
Swt is graphical lbray competitor of swing and coming from eclipse project.
It is very popular and very nice, but it's drwback is that it use native graphical libraries.
Do you plan to solve the problem ?I told you how to get around this in my email yesterday.
For the bootstrap JARs, its not a problem. Specify the system properties.
For test-SNAPSHOT.war, I have no idea what your problem is - I still have no idea how you got that far without the plugins CVS source.
You are right, now that Iknow the good door, I have to start the process from the begining in the good way.
It seems tome that the problem in jellySwt is that nothing has been done in project.xml to manage native, win32 is just hardcoded nothing about other arch.
My problem with Maven is that I cannot succeed to run jellySwt demo on a linux machine (Looking in archive I found that others people has the problem on windows2000 but they just stop to use it, having no answers).
I cannot run it because swt use natives and it seems that natives are not managed very well in Maven 1.0. I wanted to look if latest Maven was better.
No, no changes in lastest Maven in this regard. Maven can handle natives to some extent, but I don't know the specific problem with the JellySWT project.
It is probably not a maven issue but a jellySwt issue.
But I don't now how maven solve the problem :
We need to have in repository, not only jar required by project but also corresponding (same release level) native dll or .so etc.
Then put it in a place know by OS (LD_LIBRARY_PATH for Linux for example). May be maven can help to manage this ?
By now in jellySwt, native are not in ibiblio and this is an issue.
because my swt natives does not correspond to swt jar present in my maven repository which is use by jellySwt project.xml.
I have asked to common-users jelly but no answers.
Thank's for your help.
Andre Legendre
- Brett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
