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.
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.
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.
- Brett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
