dding 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 (artifact not available).
>
> Best regar
ot work, please elaborate.
>
> Best regards,
>
> Ansgar
> Am 26.04.2012 20:36 schrieb "Ryan Wexler" :
>
> > 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
> &g
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
I am deploying artifacts with configuration files as well. I have
different config files for each production server, so I am creating a
different artifact for each production server with the proper config files.
I create a generic war and then overlay it, adding the config files for
each producti
I am not sure I understand the problem exactly. But one option you could
look at is separating the two tasks.
You could first use the maven dependency plugin to unpack the parent war.
${project.build.directory}/
true
I recently dealt with this exact challenge.
In the "child" war project that you are overlaying the parent with, you
need to configure the webResource section and turn filtering on like so:
In this example I will filter on any xml file in the WEB-INF folder.
org.apache.maven.plug
resource filtering to the directory.
On Tue, Apr 3, 2012 at 4:11 PM, Ryan Wexler wrote:
> I tried the unpack-dependencies but that didn't make a difference, still
> doesn't work as described.
>
>
> On Tue, Apr 3, 2012 at 3:34 PM, Ryan Wexler wrote:
>
>> That blog
I tried the unpack-dependencies but that didn't make a difference, still
doesn't work as described.
On Tue, Apr 3, 2012 at 3:34 PM, Ryan Wexler wrote:
> That blog post seemed very self explanatory, but it didn't work.
>
> What I am getting from the blog is that if
That blog post seemed very self explanatory, but it didn't work.
What I am getting from the blog is that if you bind a plugin to the
"generate-resources" phase, then you can filter on the resulting files in
project build directory.
I did this, but no luck. The only difference between what I am d
I have a project that creates a generic package which is then used in
several other nearly identical sibling projects. These projects pull this
"client-generic" package in as a dependency and create an almost identical
package other than the difference in these configuration files. This
looks li
shade plugin adds the main class to the manifest perfectly, but I don't
see how I can add the classpath reference?
> Why do you need to play with the manifest?
> Are you building something so unusual that Maven has not been used to do
> this before?
>
> Ron
>
> Unfortunatel
reference all the dependencies in
the classpath with the prefix 'lib'.
On Mar 8, 2012 9:21 AM, "Ron Wheeler"
wrote:
> Sound interesting but what are you trying to make in the end?
>
> What is the 30,000 ft view of the problem?
>
> Ron
>
> On 08/03/2012 12:03
On Thu, Mar 8, 2012 at 8:36 AM, Wayne Fay wrote:
> > I would also like to add the classpath and set a classpathprefix like you
> > can do using the normal maven jar.
> >true
> >lib/
> >
> > Is there a way to do this with the shade plugin?
>
> Generally, the thinking with Shade is that you
I am using the ManifestResourceTransformer of the maven shade plugin to
create an executable jar from an existing jar.
I would also like to add the classpath and set a classpathprefix like you
can do using the normal maven jar.
true
lib/
Is there a way to do this with the shade plugin?
t
Interesting.
What was the advantage you found to a custom plugin versus just executing
through Antrun?
On Wed, Mar 7, 2012 at 3:51 PM, Dan Tran wrote:
> I have experience on both IA ant and build executable. Ended up to
> write a maven plugin ( ia-maven-plugin) and just invoke the
> build/build.
On Fri, Mar 2, 2012 at 7:19 AM, Wayne Fay wrote:
> > 1)I keep getting this error in reference to the generic-war project:
> >'packaging' with value 'war' is invalid. Aggregator projects
> > require 'pom' as packaging.
> > I tried to changing it to pom but that doesn't seem right. Is an
>
I am trying to create different WAR builds using profiles for my different
production sites. Each site requires different configuration files. I
think I am confused on how to use build profiles.
My plan was this:
1)Create a base configuration for the war plugin that includes my basic
configurati
17 matches
Mail list logo
