Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a create-extension Maven mojo #3191

Merged
merged 1 commit into from
Jul 24, 2019
Merged

Conversation

ppalaga
Copy link
Contributor

@ppalaga ppalaga commented Jul 11, 2019

No description provided.

@ppalaga
Copy link
Contributor Author

ppalaga commented Jul 11, 2019

cc @emmanuelbernard

@ppalaga ppalaga force-pushed the i2113 branch 4 times, most recently from 48c0c82 to 1995478 Compare July 12, 2019 07:18
@ppalaga
Copy link
Contributor Author

ppalaga commented Jul 12, 2019

Force pushed 1995478 with shorter file paths to make Windows happy.

This branch demonstrates how I'd like to use the mojo in camel-quarkus. (A similar setup can be done for the main Quarkus repo too.)

mvn io.quarkus:quarkus-maven-plugin:999-SNAPSHOT:create-extension -N -Dquarkus.artifactIdBase=log

@Dufgui
Copy link
Contributor

Dufgui commented Jul 13, 2019

Very interesting feature. Thanks a lot. A really small return (maybe I am wrong):
you code most of the part inside the mojo itself and not put anything in devtools common. But it can be interesting to put in common the template part if someone code the graddle part. And you write directly inside the filesystem. And in this way you cannot write in a zip for exemple. You can reuse/extends ZipProjectWriter and FileProjectWriter no ? What do you think about it ?

@ppalaga
Copy link
Contributor Author

ppalaga commented Jul 13, 2019

you code most of the part inside the mojo itself and not put anything in devtools common. But it can be interesting to put in common the template part if someone code the graddle part.

Sorry, I am primarily addressing my own need and this is unfortunately of the scope. Somebody who finds this important is welcome to do that.

And you write directly inside the filesystem. And in this way you cannot write in a zip for exemple. You can reuse/extends ZipProjectWriter and FileProjectWriter no ? What do you think about it ?

The current proposal is just solving the task of creating extension modules in existing source trees. How would a zip file be useful in that scenario?

@Dufgui
Copy link
Contributor

Dufgui commented Jul 14, 2019

For the put in common ok. It s just a proposal to facility the gradle part.

I start to work on a web project generator. So I think it’s interesting to do the same on extension. But I am on hold and wait some return to progress again. So it’s up to you for the zip part.

@ppalaga
Copy link
Contributor Author

ppalaga commented Jul 15, 2019

web project generator. So I think it’s interesting to do the same on extension.

I see, but I guess zipping and being used from an online generator would only make sense for the standalone scenario, that I left unimplemented https://github.com/quarkusio/quarkus/pull/3191/files#diff-e41033b79bb31b53ffe8ec1f25646b7bR476

@aloubyansky
Copy link
Member

BTW, it'd be also great to mention this in the guide. And as it's a noteworthy feature, I believe, @gsmet will appreciate a brief summary of it he could include in the release notes.
Thanks @ppalaga!

@ppalaga
Copy link
Contributor Author

ppalaga commented Jul 15, 2019

3442267:

  • Rebased on current master
  • Addressed some @aloubyansky 's comments

Still open from my PoV:

  • How to handle the version of maven-compiler-plugin? - If document - where? If version - do we want a separate Mojo param?
  • No problem with mentioning the new mojo in the guide, I vote for creating a followup issue and assigning to me.

@aloubyansky
Copy link
Member

@ppalaga there were test failures, could you review those please? Thanks.

@ppalaga
Copy link
Contributor Author

ppalaga commented Jul 19, 2019

0ab6267 should fix the test failures

@ppalaga
Copy link
Contributor Author

ppalaga commented Jul 19, 2019

The CI is passing now

@ppalaga
Copy link
Contributor Author

ppalaga commented Jul 23, 2019

About 52ad079:

All issues are solved from my PoV.

@ppalaga ppalaga force-pushed the i2113 branch 4 times, most recently from 05209c0 to 6666bd5 Compare July 23, 2019 13:29
@ppalaga
Copy link
Contributor Author

ppalaga commented Jul 23, 2019

f957cc8 should fix the windows build

@ppalaga
Copy link
Contributor Author

ppalaga commented Jul 24, 2019

Is this good to merge now, @aloubyansky ?

@aloubyansky
Copy link
Member

Looks great, thanks a lot @ppalaga !

@aloubyansky aloubyansky added this to the 0.20.0 milestone Jul 24, 2019
@aloubyansky aloubyansky merged commit 1d9806f into quarkusio:master Jul 24, 2019
@gsmet gsmet changed the title Fix #2113 create-extension Maven mojo Add a create-extension Maven mojo Jul 31, 2019
@gsmet
Copy link
Member

gsmet commented Jul 31, 2019

I removed the noteworthy-feature label for now because we don't have any documentation about this feature.

We need to have a paragraph in the extension guide explaining how this works.

@ppalaga
Copy link
Contributor Author

ppalaga commented Jul 31, 2019

@gsmet could you please assing #3386 to me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants