Hi,
Shouldn't that be generated automaitcally by ear plugin?
org.apache.maven.plugins
maven-ear-plugin
Foo
Foo EAR
5
Hi,
I'm using Maven 3.0.3 with WebSphere 6.1. In my
src/main/webapp/META-INF/application.xml file, I have
;
myco
myco-app-
For what it's worth, I agree with you both (version strings should be
controlled via the -ahem- version control system), but I am willing to
allow Maven (more to the point, the maven-release-plugin) to take care
of the version strings for me.
However, if you don't want to, you can still do it your
On 25 May 2011 23:43, David McCabe wrote:
> > -Original Message-
> > From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
> > Sent: Wednesday, 25 May 2011 4:54 PM
> > To: users@maven.apache.org
> > Subject: Re: How to compile twice
> >
> > On 25/05/2011 10:58 AM, David McCabe wrote:
Any time you all get tired of insulting each other's intelligence we
can all try to find a solution.
It's a simple fact, Maven was, indeed, designed to build Java. It was
not designed to build C++ or any other native code language. The core
model of what gets built is one output per module.
Featu
> -Original Message-
> From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
> Sent: Wednesday, 25 May 2011 4:54 PM
> To: users@maven.apache.org
> Subject: Re: How to compile twice
>
> On 25/05/2011 10:58 AM, David McCabe wrote:
> > In that case, how does one handle a single module bui
I've used both M2 and M3 builds for Spring-based apps and done many
component scans. I've never heard of the well-known issue nor had
problems with doing so.
I agree with Wayne it is a Spring question at this point, unless you
can demonstrate how, as Wayne says, the M2 vs M3 build difference
caus
> Just to Make a scenary: I am Having a well known problem about Spring can't
> do a Component Scan aganinst a jar generated by Maven 2.
>
> Apparently this happens because the generated Jar does not add its Directory
> Entries.
If you can take the Maven-generated Jar file and modify it such that
2011/5/25 Ron Wheeler
> On 25/05/2011 10:58 AM, David McCabe wrote:
>
>> In that case, how does one handle a single module build that produces
>> multiple artefacts? Is this 'not the Maven way'? What about multi-platform
>> builds? What about multiple output types (header files, DLLs, import
>> l
-Original Message-
From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
>
>This is the Maven way.
Ok I will use my copy of "Maven: The Definitive Guide" to light my next BBQ.
You convinced me, I am back to the orthodoxy. Nested Modules.
Thanks
Claves
The information contained in th
On 25/05/2011 10:58 AM, David McCabe wrote:
In that case, how does one handle a single module build that produces
multiple artefacts? Is this 'not the Maven way'? What about multi-platform
builds? What about multiple output types (header files, DLLs, import
libraries and JNI JARs)?
I'm getting v
-Original Message-
From: Antonio Petrelli [mailto:antonio.petre...@gmail.com]
>
>Not much, Maven is very angry about it :-D Anyway, did you try, at least, to
>see if you can do a multimodule build?
We had multi-module builds but it turned out to be a bit messy.
Now, we switched to profile
That is a different case, but you still face issues... but for side
artifacts like JNI libs etc, I would be less worried
The case in question is producing just jars
On 25 May 2011 15:58, David McCabe wrote:
> In that case, how does one handle a single module build that produces
> multiple artef
2011/5/25 Claves Do Amaral
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> >
> >STOP FIGHTING MAVEN
>
> :)
>
> I will take the risky way, like Prometheus, and pay the consequences of my
> hubris. I hope that Maven will have mercy on me.
>
Not much
How do you think the code review for this change will go? Left or right side?
;-)
http://www.gridshore.nl/wp-content/uploads/code-quality-measurement.jpg
> -Original Message-
> From: Claves Do Amaral [mailto:claves.doama...@iggroup.com]
> Sent: Wednesday, May 25, 2011 10:53 AM
> To: Mav
In that case, how does one handle a single module build that produces
multiple artefacts? Is this 'not the Maven way'? What about multi-platform
builds? What about multiple output types (header files, DLLs, import
libraries and JNI JARs)?
I'm getting very confused by this, because the 'Maven way'
-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of
Anders Hammar
>It will not. I can tell you that for sure. The person that ends du maintaining
>your build setup will curse your name forever!
I will comment it very well...
What about usin
It will not. I can tell you that for sure. The person that ends du
maintaining your build setup will curse your name forever!
/Anders (mobile)
Den 25 maj 2011 16.44 skrev "Claves Do Amaral" :
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
>>
>>STOP F
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
>
>STOP FIGHTING MAVEN
:)
I will take the risky way, like Prometheus, and pay the consequences of my
hubris. I hope that Maven will have mercy on me.
The information contained in this email is strictly
STOP FIGHTING MAVEN
Multi-module is your only man anything else is torture
On 25 May 2011 15:26, Claves Do Amaral wrote:
> -Original Message-
> From: Jörg Schaible [mailto:joerg.schai...@scalaris.com]
>
>>It seems that the plugin will add the target directories automatically to the
-Original Message-
From: Laird Nelson [mailto:ljnel...@gmail.com]
>
>How about:
>
>
> ../../generated-sources-jacorb/**
> ../../generated-sources-sunorb/**
>
I have downloaded the Plexus compiler source code (which is what ultimately
maven-compiler-plugin 2.3.2 uses) and it looks that t
On Wed, May 25, 2011 at 10:26 AM, Claves Do Amaral <
claves.doama...@iggroup.com> wrote:
>
>
>
> ${project.build.directory}/generated-sources-sunorb/idl/**/*.java
>
>
> Does not have any effect since the excludes start from the source root,
> i.e. it's a filter that is applied to the subtree
>
-Original Message-
From: Jörg Schaible [mailto:joerg.schai...@scalaris.com]
>It seems that the plugin will add the target directories automatically to the
>list of sources directory for the compiler. You need now two separate
I see that the sources are added to the compileSourceRoots by
I haven't reproduced the problem on a separate project yet.
I have used m2eclipse and got 2 different results:
On the Dependecy Hierarchy the dependency appears as compile but on the
Dependency Graph it appears as provided. But I still couldn't see what is
pulling this dependency as compiled.
Wh
Sure enough. I have a structure where the deploy URL is built as a
sort of little template with a property set in children,
On Tue, May 24, 2011 at 4:17 PM, Dennis Lundberg wrote:
> I'm guessing that you have run into this:
>
> http://jira.codehaus.org/browse/MSITE-585
>
> On 2011-05-24 21:17, Be
I've sorted this. If Dennis likes my patches from last night, I'll add
one more with some documentation to save other people from this
experience.
On Tue, May 24, 2011 at 6:06 PM, Benson Margulies wrote:
> In my POM, I have (to begin with):
>
>
> JIRA
> http://jira.basistech.net:8
I believe the problem is that you're not doing the assemblying within the
reactor, i.e. you don't have the assembly-plugin bound to the lifecycle but
execute that plugin directly. If you're only executing "mvn package" the
artifacts will not be installed to the local repo.
So create a binding for
Hi Ron,
Thanks for your advices! I grouped all the repos in a single group so the
developers just have to point to a single group repo for development and
release. But I am considering to split that in several group repos to make
it cleaner :-)
Anyway I opened an issue for my problem, I believe t
I have the pom too.
Are you tryin to say that maven is not able to pick up the pom, if yes, what
is the way i can resolve this?
I have the pom , infact yesterday I could run mvn package successfully but
today it shows this error, so I thought it is not able to connect to the
local repo.
Please sug
Hello,
Looked into an issue I've encountered with assembly not using
snapshots correctly. I believe it's due to Maven 3.0.3 restricting
libraries to "configured" repositories only, but not sure why the
assembly plugin doesn't have the repository in question "configured" for
use.
I've
30 matches
Mail list logo
