All geek questions in one place

Maven workspace permission not available for local Tomcat testing

I have a mavenized project with dependencies on 4 other mavenized projects my team is working on. We have workspace permission.

If I publish Tomcat, banks will not be available for 4 projects, so I see all kinds of NoClassDefFoundError exceptions. I do not see any problems with testing or packaging JUnit. (I run the package target, and the resulting war file includes the SNAPSHOT banks that I expect.)

I see a lot of people who advocate using workspace permissions, but if we need to test on Tomcat, should we disable this? Or what else can I lose?

We use Eclipse Helios, the m2eclipse plugin, Maven 3.0.3. I even installed m2extras to find out if this helped, but I did not see any difference.

thank

+3
source share
2 answers

You can tweak this setting (we work with the same tool binding and tuning here) if you can live with some manual updates after you use m2eclipse targets for assembly.

The problem is that not all external changes using m2eclipse are built in workspace projects, correctly synchronized with your deployed web application in tomcat.

So, if you experience NoClassDefFoundError exceptions after creating via m2eclipse, the following should help (not all of this is necessary every time):

  • / maven
  • (F5) maven
  • - ( )

, , .

0
  • .
  • .settings .project .
  • .
  • maven .
0

Source: https://habr.com/ru/post/1785246/

More articles:


All Articles