Looks like the problem can also be prevented by adding an additional reference to GWT and moving it to the top of your "order and export".
This at least ensures the POM, under version control, does not need to be modified (with potential for erroneous check-ins).
With kind regards,
Eclipse users:
I had to remove GWT from Maven's dependencies and add a reference manually so that it could be moved to the top of the build classpath "order and export" section.
AFAIK, this is a well known problem running Guvnor from Eclipse due to incompatibilities of the version of JDT.
These JIRAs contain reference to the problem. I don't think a fix was ever found.
The problem manifests itself with "java.lang.NoSuchFieldError: warningThreshold" errors when GWT attempts to compile Guvnor (either when the URL is first accessed or explicitly selected).
With lind regards,
MikeOn 14 February 2011 13:25, Geoffrey De Smet <ge0ffrey.spam@gmail.com> wrote:
The split-off of guvnor is done, the repository is ready to be used.
See below how to get started.
But before you get started, please check these settings:
For detailed instructions on how to configure this fast correctly, see the README.txt file, currently still at:
- Do not include @author tags in new files
- For motivation see: https://issues.jboss.org/browse/JBRULES-2869
- All author tags have been stripped (done during split-up)
- Line endings are unix (\n)
- All files now have unix line endings (done during split-up)
- Do not use tab characters (\t)
- All flies now use spaces instead of tabs (done during split-up)
- Encoding for all files (except property files) is UTF-8
- Not changes during split-up
https://github.com/droolsjbpm/droolsjbpm/blob/master/README.txt#L118
How to get started
============
// Close eclipse/intellij
cd ~/projects
// Move the old repostory out of the way
mv droolsjbpm monolitic-droolsjbpm
// Make a directory to hold all the new repositories
mkdir droolsjbpm
cd droolsjbpm
git clone git@github.com:droolsjbpm/guvnor.git guvnor
git clone git@github.com:droolsjbpm/droolsjbpm-tools.git droolsjbpm-tools
// As the split-up continues, you'll be able to add more repo's
// Make a new workspace in Eclipse/IntelliJ
// Add each of the new repo's as maven projects to that new workspace
Temporary workaround during the next week
============================
Because the split-up is still ongoing (not everything split up yet + the hudson jobs don't deploy snapshot yet),
you 'll need to do this to get it to work, because the repo's still depend on the old parent pom for now:
cd ~/projects
// go the old repo and get it up to date
cd monolitic-droolsjbpm
git pull --rebase
// Just build and install the parent pom
mvn clean install -N
cd ..
cd droolsjbpm
cd guvnor
mvn clean install -DskipTests
cd ..
cd droolsjbpm-tools
mvn clean install -DskipTests
Status of split-up
===========
Guvnor and droolsjbpm-tools are unfrozen and mostly ready.
Integration is starting now, might take till tomorrow.
Drools will be started Wednesday.
droolsjbpm-knowledge and droolsjbpm-parent will be started later this week
drools-planner has to be redone.
droolsjbpm-dist will be started after those.
General cleanup and improvements can run into next week.
-- With kind regards, Geoffrey De Smet_______________________________________________
rules-dev mailing list
rules-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev