I think the use case is where you need to give a client lib to 3rd parties
not using maven, otherwise the dependency issue will kill you unless you
are doing this from an api-only module
On Saturday, 5 January 2013, Stanimir Stamenkov wrote:
> Sat, 5 Jan 2013 23:52:50 +0100, /Anders Hammar/:
>
>
Sat, 5 Jan 2013 23:52:50 +0100, /Anders Hammar/:
I always argue for having the API (e.g. ejb client) as a separate module
and then the impl (e.g. the ejb) as a separate module.
That's what we're using after all, but I've recently discovered this
ejb-client option and started wondering if ther
Totally agree ++
On Sat, January 5, 2013 2:52 pm, Anders Hammar wrote:
> I always argue for having the API (e.g. ejb client) as a separate module
> and then the impl (e.g. the ejb) as a separate module.
>
> /Anders
>
>
> On Sat, Jan 5, 2013 at 11:45 PM, Manfred Moser
> wrote:
>
>> On Sat, January
I always argue for having the API (e.g. ejb client) as a separate module
and then the impl (e.g. the ejb) as a separate module.
/Anders
On Sat, Jan 5, 2013 at 11:45 PM, Manfred Moser wrote:
> On Sat, January 5, 2013 2:43 pm, Stanimir Stamenkov wrote:
> > Sat, 5 Jan 2013 14:38:38 -0800, /Manfre
On Sat, January 5, 2013 2:43 pm, Stanimir Stamenkov wrote:
> Sat, 5 Jan 2013 14:38:38 -0800, /Manfred Moser/:
>
>> If the dependencies are not applicable for this artifact (e.g. the pom
>> is
>> not valid for it because it is generated against Maven convention) then
>> it
>> should not be an artifa
Sat, 5 Jan 2013 14:38:38 -0800, /Manfred Moser/:
If the dependencies are not applicable for this artifact (e.g. the pom is
not valid for it because it is generated against Maven convention) then it
should not be an artifact in the same coordinates but rather be a
different module with different
If the dependencies are not applicable for this artifact (e.g. the pom is
not valid for it because it is generated against Maven convention) then it
should not be an artifact in the same coordinates but rather be a
different module with different GAV coordinates
On Sat, January 5, 2013 2:34 pm, St
Is it true attached artifacts, that is artifacts with a non-empty
classifier, "inherit" their dependencies from the main artifact?
Stated otherwise - is it possible to specify different set of
dependencies for an attached artifact such that when included in
another project, that different set o
