Ok, after more trial and effort, this pom.xml might be working....are there any obvious problems with it?
<project xmlns=*"http://maven.apache.org/POM/4.0.0"* xmlns:xsi=*"http://www.w3.org/2001/XMLSchema-instance"* xsi:schemaLocation=*"http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"*> <modelVersion>4.0.0</modelVersion> <groupId>BBj</groupId> <artifactId>BBj</artifactId> <version>19.10-SNAPSHOT</version> <packaging>gwt-app</packaging> <dependencyManagement> <dependencies> <dependency> <groupId>com.google.gwt</groupId> <artifactId>gwt</artifactId> <version>2.8.2</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId>com.google.gwt</groupId> <artifactId>gwt-user</artifactId> </dependency> <dependency> <groupId>com.google.gwt</groupId> <artifactId>gwt-dev</artifactId> <exclusions> <exclusion> <groupId>xml-apis</groupId> <artifactId>xml-apis</artifactId> </exclusion> <exclusion> <groupId>net.sourceforge.htmlunit</groupId> <artifactId>htmlunit</artifactId> </exclusion> </exclusions> </dependency> </dependencies> <build> <sourceDirectory>src</sourceDirectory> <resources> <resource> <directory>src</directory> <excludes> <exclude>**/*.java</exclude> </excludes> </resource> <resource> <directory>.apt_generated</directory> <excludes> <exclude>**/*.java</exclude> </excludes> </resource> </resources> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>3.8.0</version> <configuration> <release>11</release> </configuration> </plugin> <plugin> <groupId>net.ltgt.gwt.maven</groupId> <artifactId>gwt-maven-plugin</artifactId> <version>1.0-rc-10</version> <extensions>true</extensions> <configuration> <moduleName>com.basis.bbj.web.gwt.GWTWebClient</moduleName> <outputDirectory>war/WEB-INF/classes</outputDirectory> </configuration> </plugin> </plugins> </build> </project> On Friday, August 2, 2019 at 9:50:58 AM UTC-7, Jim Douglas wrote: > > Ok, StackOverflow showed me > <https://stackoverflow.com/questions/2449461/convert-existing-eclipse-project-to-maven-project/10122316> > > how to convert an existing Eclipse project to a Maven Project, then based > on your steps <https://tbroyer.github.io/gwt-maven-plugin/usage.html> 1 > and 3 I copied those chunks into the generated pom.xml (I couldn't make any > sense of step 2, so I skipped it). After hunting down and (I think) > resolving some module conflicts, that gave me this pom.xml: > > <project xmlns=*"http://maven.apache.org/POM/4.0.0 > <http://maven.apache.org/POM/4.0.0>"* > > xmlns:xsi=*"http://www.w3.org/2001/XMLSchema-instance > <http://www.w3.org/2001/XMLSchema-instance>"* > > xsi:schemaLocation=*"http://maven.apache.org/POM/4.0.0 > <http://maven.apache.org/POM/4.0.0> > http://maven.apache.org/xsd/maven-4.0.0.xsd > <http://maven.apache.org/xsd/maven-4.0.0.xsd>"*> > > <modelVersion>4.0.0</modelVersion> > > <groupId>BBj</groupId> > > <artifactId>BBj</artifactId> > > <version>19.10-SNAPSHOT</version> > > <dependencyManagement> > > <dependencies> > > <dependency> > > <groupId>com.google.gwt</groupId> > > <artifactId>gwt</artifactId> > > <version>2.8.2</version> > > <type>pom</type> > > <scope>import</scope> > > </dependency> > > </dependencies> > > </dependencyManagement> > > <dependencies> > > <dependency> > > <groupId>com.google.gwt</groupId> > > <artifactId>gwt-user</artifactId> > > </dependency> > > <dependency> > > <groupId>com.google.gwt</groupId> > > <artifactId>gwt-dev</artifactId> > > <exclusions> > > <exclusion> > > <groupId>xml-apis</groupId> > > <artifactId>xml-apis</artifactId> > > </exclusion> > > <exclusion> > > <groupId>net.sourceforge.htmlunit</groupId> > > <artifactId>htmlunit</artifactId> > > </exclusion> > > </exclusions> > > </dependency> > > </dependencies> > > <build> > > <sourceDirectory>src</sourceDirectory> > > <resources> > > <resource> > > <directory>src</directory> > > <excludes> > > <exclude>**/*.java</exclude> > > </excludes> > > </resource> > > <resource> > > <directory>.apt_generated</directory> > > <excludes> > > <exclude>**/*.java</exclude> > > </excludes> > > </resource> > > </resources> > > <plugins> > > <plugin> > > <artifactId>maven-compiler-plugin</artifactId> > > <version>3.8.0</version> > > <configuration> > > <release>11</release> > > </configuration> > > </plugin> > > <plugin> > > <groupId>net.ltgt.gwt.maven</groupId> > > <artifactId>gwt-maven-plugin</artifactId> > > <version>1.0-rc-10</version> > > <extensions>true</extensions> > > <configuration> > > <moduleName>com.basis.bbj.web.gwt.GWTWebClient</moduleName> > > <webappDirectory>/BBj/war/WEB-INF/classes</webappDirectory> > > </configuration> > > </plugin> > > </plugins> > > </build> > > </project> > > What is this Eclipse error message trying to tell me? > > Description Resource Path Location Type > The output directory for the project should be set to > /BBj/war/WEB-INF/classes BBj Unknown GWT Web App Problem > > > On Thursday, August 1, 2019 at 4:34:05 AM UTC-7, Thomas Broyer wrote: >> >> >> >> On Wednesday, July 31, 2019 at 8:02:53 PM UTC+2, Jim Douglas wrote: >>> >>> We have a large and complex Eclipse project that uses the GWT SDK for >>> the GWT client stuff, and doesn't use Maven in any way at all. How would we >>> go about evolving that away from the GWT SDK? I know effectively nothing >>> about Maven. Is there some sort of instruction list somewhere to convert an >>> existing project, as opposed to creating a new project from scratch? >>> >> >> Are you saying that you have *zero* build tool‽ not even Ant? (because >> Ant, with Ivy, can resolve dependencies from Maven repositories too; I have >> no idea how to do it myself, but there are, or have been, people here using >> Ivy who could possibly help) >> >> >>> I'm staring at this, and I don't know what to make of it: >>> >>> https://tbroyer.github.io/gwt-maven-plugin/index.html >>> >>> It seems to assume I already know what Maven is, I already have a Maven >>> project, I understand all of this obscure terminology, and I know how to >>> edit various configuration files... >>> >> >> It does assume you already know Maven, yes. >> >> >>> and I'm just trying to find a page that says "How to install this thing." >>> >> >> That's not how things work; "this thing" is a plugin for Maven, one of >> many plugins any Maven project will use during a build. >> And you don't "install" it, once you have Maven installed, you only need >> to describe your dependencies (and plugins) in an XML file (pom.xml) and >> Maven will download things for you. >> >> But you don't need to move your whole build to using Maven only to use >> dependencies from a Maven repository. You could for example use Coursier >> <https://get-coursier.io/> (or Maven or Ivy or Gradle or SBT) to >> retrieve all the JARs, and continue using your current setup for the rest. >> >> >>> >>> On Wednesday, July 24, 2019 at 8:40:21 AM UTC-7, Thomas Broyer wrote: >>>> >>>> >>>> >>>> On Wednesday, July 24, 2019 at 5:14:42 PM UTC+2, Jim Douglas wrote: >>>>> >>>>> > Sure. Use a build tool of your choice and use the maven >>>>> dependencies. >>>>> >>>>> I don't know what that means. As far as I've ever known, developing a >>>>> GWT application in Eclipse implies installing the GWT Plugin for Eclipse >>>>> and picking a GWT SDK. >>>>> >>>>> http://www.gwtproject.org/usingeclipse.html >>>>> >>>> >>>> Nope. >>>> Install the GWT Eclipse Plugin ( >>>> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html; >>>> >>>> note that the SDKs are optional). >>>> Create ( >>>> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/maven/Maven.html) >>>> >>>> or import ( >>>> https://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/workspace/Importing.html) >>>> >>>> a Maven project using GWT. >>>> You're all set; the plugin will use the GWT dependencies from the Maven >>>> project. >>>> >>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/37da2f0f-4443-410f-877a-54c74b9d409e%40googlegroups.com.
