Hi,
I am creating an RPM package using rpm-maven-plugin.
During the generation of the SPEC file, I would want to have the
"BUILDREQUIRES" tag also to be printed in the SPEC file. Is it
possible? If so how?
Naren
-
To unsub
You are most welcome - and the blog is super cool - I wish I had seen it
a long time ago.
Cheers, Eric
On 2012-03-14 5:33 PM, Daivish Shah wrote:
Thanks all for quick responses !!!
Special Thanks to Eric Kolotyluk and Manfred Moser.
Blog is super cool. Thanks for posting it.
*
*
*
*
On Wed,
Thanks all for quick responses !!!
Special Thanks to Eric Kolotyluk and Manfred Moser.
Blog is super cool. Thanks for posting it.
*
*
*
*
On Wed, Mar 14, 2012 at 2:51 PM, Amir Gheibi wrote:
> Got it. Thanks.
>
> -Original Message-
> From: Eric Kolotyluk [mailto:eric.koloty...@gmail.com]
I have seen customizations of war files done mainly through the assembly
plugin. You *can* specify a wildcard inclusion of dependencies based on
classifier with assembly.
-Original Message-
From: Maven User [mailto:maven.2.u...@gmail.com]
Sent: Wednesday, March 14, 2012 5:10 PM
To: Mav
Hi all -
Is there a way to wildcard the overlaying of various dependencies?
I'd like to take all the artifacts of a given and stick them
at the root of the war.
Currently, we're doing a dependency:unpack of them, then including them as
the base web dir.
In the end, I guess it works, but I was
Got it. Thanks.
-Original Message-
From: Eric Kolotyluk [mailto:eric.koloty...@gmail.com]
Sent: March-14-12 2:57 PM
To: Amir Gheibi
Cc: Maven Users List
Subject: Re: Which is the BEST Approach to define Global POM.XML
Amir, my Project POM has more modules inside (platform.Java & platform.
Amir, my Project POM has more modules inside (platform.Java &
platform.NET), and they in turn are packaging type "POM" because there
are more modules in those, that typically are types like "JAR" so my
structure looks like
Corporate POM
+-- Project POM 1
+--+-- Platform POM 1.1
+--+--+-- Artif
I did a blog post about this ages ago..
http://www.mosabuam.com/2009/10/company-super-pom-a-maven-practice
Keep in mind that this is a few years old so the versions and such are
out of date.. but the concept still applies.
manfred
http://simpligility.com
On 12-03-14 02:34 PM, Amir Gheibi wro
On Thu, Mar 15, 2012 at 8:04 AM, Amir Gheibi wrote:
> Hi Eric,
>
> I was wondering why your project POM's packaging type is "POM". If I
> understand correctly, with "POM" packaging type you'd only get 3 default
> goals bound to their phases (I read it here:
> http://maven.apache.org/guides/intr
Hi Eric,
I was wondering why your project POM's packaging type is "POM". If I understand
correctly, with "POM" packaging type you'd only get 3 default goals bound to
their phases (I read it here:
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Built-in_Lifecycle_B
What I do is have a top-level POM like (see below), and then I have my
top level project POMs reference that (see further below). This may not
be the best example, as I am still in the process of building the
infrastructure, but
1. I put the Parent POM in its own place in source control and I
Thanks everyone - and yes, overriding the default execution id works!
On Wed, Mar 14, 2012 at 2:14 PM, Laird Nelson wrote:
> On Wed, Mar 14, 2012 at 2:08 PM, Maven User
> wrote:
>
> > I'm doing this:
> > .
> >
> >org.apache.maven.plugins
> >mave
I am looking to set the location of the key file to be used based on the OS the
user is executing within a distributable settings.xml file. This would be for
a company-wide change, not just a per-project basis. Unfortunately, All I get
is:
[WARNING] repository metadata for: 'org.apache.maven.
On Wed, Mar 14, 2012 at 2:08 PM, Maven User wrote:
> I'm doing this:
> .
>
>org.apache.maven.plugins
>maven-war-plugin
>
>
>war
>
Set the id to default-war and see if that does the trick.
I _think_ I solved this - but I can't tell if I'm leveraging what may seem
like a bug lol.
I used this:
default-war <--
package
Try changing the execution id to 'default-war'.
> -Original Message-
> From: Maven User [mailto:maven.2.u...@gmail.com]
> Sent: Wednesday, March 14, 2012 12:08 PM
> To: Maven Users List
> Subject: Skip default execution?
>
> Hi all -
>
> I _swore_ you could do this, but maybe I've overlo
Hi all -
I _swore_ you could do this, but maybe I've overlooked something...
I have a project that has a packaging type of "war". BUT - we have two
ways we'd like to build - a compressed war (if releaseable) or an exploded
directory (if it's a developer build).
I'm doing this:
.
> 1) Annotating a release requires a code change and a rebuild.
This can be annoying. I know there has been some discussion about a
possible "turn this snapshot into a release without actually
rebuilding anything, just changing metadata" plugin on this list but
don't believe anyone has built it ye
Thanks Seth,
Branching a code base is one of the major work flows where the current
version design creates a mess.
Other examples include
1) Annotating a release requires a code change and a rebuild. Forcing a
QA check on the binary forcing the implementation of a release candidate
process
19 matches
Mail list logo
