I hear you, I just really wanted to avoid that because this is definitely
not an artifact.
On Thu, Apr 26, 2012 at 12:26 PM, Ansgar Konermann <
ansgar.konerm...@googlemail.com> wrote:
> From my experience: that's a hard problem. I ended up making the resource
> an artifact, adding a "provided"-sc
>From my experience: that's a hard problem. I ended up making the resource
an artifact, adding a "provided"-scoped dependency and switched off
deployment using m-deploy-p's skip config parameter.
Works, but is so ugly.
Not sure if the provided dependency would be allowed in Maven Central
though (
Well this item isn't an artifact and I don't want to make one out of it.
I tried another approach which was to declare the resource w/o the basedir
reference in my parent pom:
\src\main\MySpecialResource
Then I referenced it like so with the ${project.parent.basedir} preceding
the resource pro
Common approach: put your special resource in a jar module. Let the modules
which should have access to the resource define a dependency to that jar.
If this approach does not work, please elaborate.
Best regards,
Ansgar
Am 26.04.2012 20:36 schrieb "Ryan Wexler" :
> I have a large library resou
I have a large library resource that is used during my build that is
accessed from many of my modules. I have put that resource in the top
level parent basedir /src/main/MySpecialResource.
I want all the modules in my project to have access to the location of this
resource. So I created a proper
