This content has been marked as final.
Show 4 replies
-
1. Re: Need explanation for forge addon folder structure
alwad Feb 27, 2015 4:38 AM (in response to mani_mylavarapu)Hello Mani,
AFAIK, you can run the install command from any directory as long as you specify the project root of your addon.
I presume the main point is because this is where the pom is.
Cheers,
Jérôme
-
2. Re: Need explanation for forge addon folder structure
mani_mylavarapu Feb 27, 2015 6:13 AM (in response to alwad)Hi Jerome,
Thank you!But i would also be interested to know why forge addon structure is like this.
-
3. Re: Re: Need explanation for forge addon folder structure
gastaldi Feb 27, 2015 8:17 AM (in response to mani_mylavarapu)1 of 1 people found this helpfulHello Mani,
Here is an explanation of each module and their relationship:
- addon: The addon project. This module should depend on api (and spi if available) in compile time and impl in runtime. The artifact produced by this project should be a JAR with the classifier forge-addon
- api: any artifact that is supposed to be exposed by your addon.
- impl: this is where the implementation of your API lies and they should never be accessed externally.
- spi (when feasible): Use a SPI when you want other addons to provide extensions for your addon.
- tests: This is where the integration tests are kept.
-
4. Re: Re: Need explanation for forge addon folder structure
mani_mylavarapu Mar 1, 2015 2:48 AM (in response to gastaldi)Thank you for clarifying.I always had this doubt!!