The first error doesn't look familiar, but seems to be Windows-specific (I use IntelliJ on Mac, not Windows, so can't really help much there)
The test issues also don't seem especially familiar - my only suggestion would be to try doing a full maven build and reloading the maven dependencies - it kind of looks like it is getting the wrong version of some dependencies. Torben On Mon, Nov 26, 2018 at 8:26 AM Thomas <[email protected]> wrote: > Thank you for your response. I didn't think to try adding the profile to > the Maven command. That seems to work. But having the profile selected in > intellij does not. Or at least I can't get that far. > > I have had to do a few strange things to get to this point. One, I had > to set bash on my path because the build fails without it when I use mvn or > the intellij build option. Is there some sort of switch I should be using > to turn this off? Otherwise, I get the below error. > > Using the intellij build dialog it complains about many missing symbols. > They appear to be about test class symbols. I put the errors below past > the bash errors. > > Thanks, > Thomas > > ++++++++++ > Bash error > ++++++++++ > [INFO] --- git-commit-id-plugin:2.1.15:revision (default) @ gs-web-app --- > [ERROR] Caught exception in FS.readPipe() > java.io.IOException: Cannot run program "bash" (in directory > "C:\Users\thomas.harper.ctr"): CreateProcess error=2, The system cannot > find the file specified > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) > at java.lang.Runtime.exec(Runtime.java:620) > at org.eclipse.jgit.util.FS.readPipe(FS.java:431) > at org.eclipse.jgit.util.FS_Win32.discoverGitPrefix(FS_Win32.java:113) > at org.eclipse.jgit.util.FS.gitPrefix(FS.java:517) > at > org.eclipse.jgit.util.SystemReader$Default.openSystemConfig(SystemReader.java:92) > at > org.eclipse.jgit.internal.storage.file.FileRepository.<init>(FileRepository.java:171) > at > org.eclipse.jgit.storage.file.FileRepositoryBuilder.build(FileRepositoryBuilder.java:92) > at > pl.project13.maven.git.JGitProvider.getGitRepository(JGitProvider.java:265) > at pl.project13.maven.git.JGitProvider.init(JGitProvider.java:79) > at > pl.project13.maven.git.GitDataProvider.loadGitData(GitDataProvider.java:91) > at > pl.project13.maven.git.GitCommitIdMojo.loadGitDataWithJGit(GitCommitIdMojo.java:585) > at > pl.project13.maven.git.GitCommitIdMojo.loadGitData(GitCommitIdMojo.java:558) > at pl.project13.maven.git.GitCommitIdMojo.execute(GitCommitIdMojo.java:376) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > at org.codehaus.classworlds.Launcher.main(Launcher.java:47) > Caused by: java.io.IOException: CreateProcess error=2, The system cannot > find the file specified > at java.lang.ProcessImpl.create(Native Method) > at java.lang.ProcessImpl.<init>(ProcessImpl.java:386) > at java.lang.ProcessImpl.start(ProcessImpl.java:137) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > ... 36 more > > ++++++++++++++++ > Missing test symbols > ++++++++++++++++ > > C:\Users\thomas.harper.ctr\source\geoserver\src\web\security\core\src\test\java\org\geoserver\security\web\AbstractSecurityWicketTestSupport.java > Error:(42, 35) java: cannot find symbol > symbol: class AbstractUserGroupServiceTest > location: package org.geoserver.security.impl > Error:(56, 34) java: cannot find symbol > symbol: class XMLRoleServiceTest > location: package org.geoserver.security.xml > Error:(57, 34) java: cannot find symbol > symbol: class XMLUserGroupServiceTest > location: package org.geoserver.security.xml > Error:(77, 15) java: cannot find symbol > symbol: class AbstractUserGroupServiceTest > location: class > org.geoserver.security.web.AbstractSecurityWicketTestSupport > Error:(127, 31) java: cannot find symbol > symbol: class AbstractUserGroupServiceTest > location: class > org.geoserver.security.web.AbstractSecurityWicketTestSupport > Error:(144, 24) java: cannot find symbol > symbol: class XMLUserGroupServiceTest > location: class > org.geoserver.security.web.AbstractSecurityWicketTestSupport > Error:(144, 55) java: cannot find symbol > symbol: class XMLRoleServiceTest > location: class > org.geoserver.security.web.AbstractSecurityWicketTestSupport > > On Fri, Nov 23, 2018 at 4:24 PM Torben Barsballe < > [email protected]> wrote: > >> That should work, the configuration which includes oauth2 in the webapp >> is indeed controlled by that profile (here >> <https://github.com/geoserver/geoserver/blob/master/src/web/app/pom.xml#L1434-L1448> >> ). >> >> Two suggestions: >> >> - If you are running from maven, also include that profile when >> executing the run command, for example: "mvn jetty:run -Poauth2-github >> " >> - If you are running from IntelliJ, ensure the oauth2-github profile >> is selected in the "Maven Projects" window. >> >> Torben >> >> On Wed, Nov 21, 2018 at 4:57 PM Thomas <[email protected]> wrote: >> >>> I'm exploring building a geoserver extension that runs with my project's >>> oauth2 server. In that direction, I'm trying to get one of the original >>> oauth2 community extensions built and working. >>> >>> I'm building geoserver from within Intellij IDEA on a windows machine. >>> I have chosen the profile oauth2-github in the maven projects dialog and >>> built it using the execute maven goal using "clean install -DskipTests >>> -Poauth2-github" It seems to build fine but I don't see any indication the >>> extension is built. >>> >>> To start geoserver I use "jetty:run" and it starts up without issue. >>> However, when going into the web console -> authentication -> add new >>> authentication filters, the choices don't include any oauth2 filters. >>> >>> Is there any other sort of step I should be taking or log I should look >>> at to help me resolve this? >>> >>> ~Thomas >>> >>> >>> _______________________________________________ >>> Geoserver-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>> >>
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
