Re: gwt-maven-springboot-archetype updated ...

Ok, got it, was thinking, we were talking about the generated project ... Yep correct, usually, running the verify goal, will compare the generated sources with the ones stored under test resources. There is no test were the generated project gets started/tested, if it works. The generated project from the verify goal can be found here: 'modular-springboot-webapp/target/test-classes/projects/basic-webapp/project/basic-webapp'

inside the web-app directory you can do a `mvn clean install` and test the project. 

Craig Mitchell schrieb am Dienstag, 21. Mai 2024 um 08:13:47 UTC+2:

Sorry, I think I wasn't clear.  Yes, I can make changes to the gwt-maven-springboot-archetype project, and do a mvn compile on it to make sure there are no syntax errors with my changes.

The problem is, if I want to test to make sure my modified version of gwt-maven-springboot-archetype actually generates a new project correctly (Ie: Run mvn archetype:generate ...), this doesn't work unless I do a mvn install. as maven doesn't see the HEAD-SNAPSHOT version, as (I'm guessing a bit here, I'm not a maven expert), I think maven only looks in its repositories (local and remote), and there isn't any HEAD-SNAPSHOT version, as it's not installed.  Thus, I get the "The desired archetype does not exist (com:modular-springboot-webapp:HEAD-SNAPSHOT)" error.

fyi:  At no point are there any GWT compilations.  That comes later when I compile the project that was generated.

On Monday 20 May 2024 at 11:07:45 pm UTC+10 Frank Hossfeld wrote:

Thanks for you PR. Your PR is merged and a new release is done. New version should be available soon.

doing a `mvn clean compile` is usually enough to generate all necessary sources and run the project. It's much faster cause it avoids a GWT compile during build. In case you need a war, run `mvn clean verify`- not sure, if install is really needed. So, for develpment, `mvn clean compile`  Is all you need to do. And it save a lot of time especially when the project gets more classes.

Craig Mitchell schrieb am Montag, 20. Mai 2024 um 05:00:07 UTC+2:

Just tried a mvn install, and it seems to have worked.

So I think the instructions https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation :

cd gwt-maven-springboot-archetype && mvn clean compile

should be:

cd gwt-maven-springboot-archetype && mvn clean install

And my PR looks good.  🙂

On Monday 20 May 2024 at 12:40:45 pm UTC+10 Craig Mitchell wrote:

Hi Frank.  Unfortunately, that didn't work.  I raised an issue:  https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/15

I've also submitted a fix:  https://github.com/NaluKit/gwt-maven-springboot-archetype/pull/16

However, I couldn't test my fix with the generation.  The instructions here:  https://github.com/NaluKit/gwt-maven-springboot-archetype?tab=readme-ov-file#local-generation say to test, you do:

cd gwt-maven-springboot-archetype && mvn clean compile

And then I should be able to do:

mvn archetype:generate -DarchetypeGroupId=com.github.nalukit.archetype -DarchetypeVersion=HEAD-SNAPSHOT -DarchetypeArtifactId=modular-springboot-webapp

But that fails with:

The desired archetype does not exist (com:modular-springboot-webapp:HEAD-SNAPSHOT)

I suspect I'm supposed to do a mvn install?  Or mvn deploy?  Something that makes HEAD-SNAPSHOT available?

On Sunday 19 May 2024 at 2:17:17 am UTC+10 Frank Hossfeld wrote:

I'll added some additional code to avoid adding the launcherDir as document root in production mode. 
New version should be soon available.

Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 16:00:47 UTC+2:

The issue seems to be the launcherDir directory doesn't exist.  I've raised a an issue with the full stack trace:  https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/13

On Saturday 18 May 2024 at 11:06:28 pm UTC+10 Frank Hossfeld wrote:

please can you post the error message: Thanks

Craig Mitchell schrieb am Samstag, 18. Mai 2024 um 13:11:40 UTC+2:

I spoke to soon.  Adding the EmbeddedServletContainerConfig fixes the serialization policy when running locally, but if you do a build and try to run.  Ie:  mvn clean package and then java -jar myserver/myapp.war, it crashes.

I'll investigate.  Any ideas/help most welcome.

On Saturday 18 May 2024 at 8:42:09 pm UTC+10 Craig Mitchell wrote:

> New version available ... This one fixes the serializationPolicyFilePath issue ... 

Awesome, thanks!  I've closed https://github.com/NaluKit/gwt-maven-springboot-archetype/issues/7  👍

On Thursday 16 May 2024 at 4:38:52 am UTC+10 Frank Hossfeld wrote:

Bott -> Boot ...  (spelling correction .... arrrgh)

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/ff0117ce-1446-4b77-a69c-322bf1e26cfen%40googlegroups.com.