[windup-dev] Forge module deps?

[Lincoln Baxter, III]

Sure, I'll take a look at this. I was in the middle of working on the POMs
but I had to stop due to the other refactoring work (I didn't want to get
in the way and cause lots of merge conflicts)

In the mean time, please read these two sections of the forge docs:

https://github.com/forge/core#re-use-functionality-from-other-addons
https://github.com/forge/core#what-scope-should-my-addon-dependencies-be

They should explain how dependencies should be added.

~Lincoln



On Mon, Jun 23, 2014 at 7:21 AM, Ondrej Zizka <ozizka at redhat.com> wrote:

> Hi Lincoln,
>
> could you please go through the dependencies and check if everything is ok,
> and explain what are the correct ways to set up the deps?
>
> E.g., there are some forge-addon deps, but not declared as provided.
> Also, what to do if some other module only depends on an API? Should it
> depend on the whole module?
> Isn't it wrong to add the implementation to classpath too?
> If it is, should API  be a standalone module?
> If not, is there a way to limit the exported classes? AS uses
> module.xml, can that be used in Forge too?
>
> Not the top priority thing, but I'd like to have this clear, can spare
> me of some CL troubles in the future.
>
> Thanks,
> Ondra
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>



-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140625/4f21c346/attachment.html