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.

Sign up for GitHub

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

Jump to bottom

Create a Gradle Plugin #29

Open
kdabir opened this issue Aug 8, 2020 · 0 comments
Open

Create a Gradle Plugin #29

kdabir opened this issue Aug 8, 2020 · 0 comments
Assignees
@kdabir

Comments

@kdabir
Copy link
Member

kdabir commented Aug 8, 2020

for ease of use in consuming projects
@kdabir kdabir self-assigned this Aug 8, 2020
kdabir added a commit that referenced this issue Aug 8, 2020
@kdabir
[#29] spike out a gradle plugin within the project. need to upgrade g…
c027062 
…radle
kdabir added a commit that referenced this issue Aug 8, 2020
@kdabir
[#29] required publish to maven repo
73cf2b8
kdabir added a commit that referenced this issue Aug 8, 2020
@kdabir
[#29] subprojects need that too
0b6d125
kdabir added a commit that referenced this issue Aug 8, 2020
@kdabir
[#29] with maven-publish, need to specify publication as well.. learn…
6577a7f 
…t the hard way
kdabir added a commit that referenced this issue Aug 8, 2020
@kdabir
[#29] do not publish/configure plugin project like another projects
504509e
kdabir added a commit that referenced this issue Aug 8, 2020
@kdabir
[#29] use own's verison to resolve dependency version
0343757 
we can't reference project directly hence we have to use group and artifact id
to resolve the dependencies in maven repos
kdabir added a commit that referenced this issue Aug 8, 2020
@kdabir
[#29] correct group for the plugin
62a3a48
kdabir added a commit that referenced this issue Aug 9, 2020
@kdabir
[#29] read the version from processed resources
ab816d1 
this way the version is actually the version from the plugin's project
and not the version of the project to which the plugin is being applied
ashwini-desai pushed a commit to ashwini-desai/apifi that referenced this issue Sep 18, 2020
@kdabir @ashwini-desai
[medly#29] spike out a gradle plugin within the project. need to upgr…
840f911 
…ade gradle
ashwini-desai pushed a commit to ashwini-desai/apifi that referenced this issue Sep 18, 2020
@kdabir @ashwini-desai
[medly#29] required publish to maven repo
cb36ebe
ashwini-desai pushed a commit to ashwini-desai/apifi that referenced this issue Sep 18, 2020
@kdabir @ashwini-desai
[medly#29] subprojects need that too
85f610a
ashwini-desai pushed a commit to ashwini-desai/apifi that referenced this issue Sep 18, 2020
@kdabir @ashwini-desai
[medly#29] with maven-publish, need to specify publication as well.. …
b1b9645 
…learnt the hard way
ashwini-desai pushed a commit to ashwini-desai/apifi that referenced this issue Sep 18, 2020
@kdabir @ashwini-desai
[medly#29] do not publish/configure plugin project like another projects
0649d2f
ashwini-desai pushed a commit to ashwini-desai/apifi that referenced this issue Sep 18, 2020
@kdabir @ashwini-desai
[medly#29] use own's verison to resolve dependency version
d3dd0b9 
we can't reference project directly hence we have to use group and artifact id
to resolve the dependencies in maven repos
ashwini-desai pushed a commit to ashwini-desai/apifi that referenced this issue Sep 18, 2020
@kdabir @ashwini-desai
[medly#29] correct group for the plugin
bc32591
ashwini-desai pushed a commit to ashwini-desai/apifi that referenced this issue Sep 18, 2020
@kdabir @ashwini-desai
[medly#29] read the version from processed resources
74da25a 
this way the version is actually the version from the plugin's project
and not the version of the project to which the plugin is being applied
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kdabir kdabir

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kdabir