Generated project have wrong package when using org.acme.something

[ia3andy]

Describe the bug
Holy guacamole, the package is acting weird when generating an app with org.acme.something as package name (only affecting spring-web and resteasy).. which is pretty bad since it's the first getting started example: https://quarkus.io/guides/getting-started

mvn io.quarkus:quarkus-maven-plugin:1.10.2.Final:create \
    -DprojectGroupId=org.acme \
    -DprojectArtifactId=getting-started \
    -DclassName="org.acme.getting.started.GreetingResource" \
    -Dpath="/hello"
cd getting-started

The output is:

.
├── README.md
├── mvnw
├── mvnw.cmd
├── pom.xml
└── src
    ├── main
    │   ├── docker
    │   │   ├── Dockerfile.fast-jar
    │   │   ├── Dockerfile.jvm
    │   │   └── Dockerfile.native
    │   ├── java
    │   │   └── org
    │   │       └── acme
    │   │           └── getting
    │   │               └── started
    │   │                   └── getting
    │   │                       └── started
    │   │                           └── GreetingResource.java
    │   └── resources
    │       ├── META-INF
    │       │   └── resources
    │       │       └── index.html
    │       └── application.properties
    └── test
        └── java
            └── org
                └── acme
                    └── getting
                        └── started
                            └── getting
                                └── started
                                    ├── GreetingResourceTest.java
                                    └── NativeGreetingResourceIT.java

The problem is because org.acme is being replaced twice when using resteasy and spring-web.

[ghost]

/cc @geoand

[ia3andy]

By luck, the bug is consistent, and the project does work.. so the "only" problem is the wrong package name and dir..