I have a multiproject setup with a parent pom that consolidates common
properties for subprojects in the ...
section (below modules). I found that none of the subprojects inherit
these props so Im curious to know what I am doing wrong. How does one
set properties in a parent pom and have them inh
I'm having a problem with my subprojects in maven.
Top level multiproject has the following in maven.properties
maven.repo.local=../maven-rep
This value gets inherited by the sub projects, but comes through with the
same value rather than the desired ../../maven-rep.
Is there a better way to
On Tue, 2006-03-14 at 03:09 -0500, Evan Bollig wrote:
> I have a multiproject setup with a parent pom that consolidates common
> properties for subprojects in the ...
> section (below modules). I found that none of the subprojects inherit
> these props so Im curious to know what I am doing wrong.
> -Original Message-
> From: Kevin Pearcey [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 21, 2004 11:05 AM
> To: 'Maven Users List'
> Subject: Inherited properties (RC3)
>
>
> I'm having a problem with my subprojects in maven.
>
>
> > I'm having a problem with my subprojects in maven.
> >
> > Top level multiproject has the following in maven.properties
> >
> > maven.repo.local=../maven-rep
> >
> > This value gets inherited by the sub projects, but comes
> > through with the
> > same value rather than the desired ../../m
Always prepend ${basedir}
For example ${basedir}/../maven-rep
wkr,
Geoffrey
"Kevin Pearcey" <[EMAIL PROTECTED]> schreef in bericht
news:[EMAIL PROTECTED]
> I'm having a problem with my subprojects in maven.
>
> Top level multiproject has the following in maven.properties
>
> maven.repo.local=..
,
pomextend.lastIndexOf('/'))}
Harald
-Opprinnelig melding-
Fra: Geoffrey [mailto:[EMAIL PROTECTED]
Sendt: 21. mai 2004 11:40
Til: [EMAIL PROTECTED]
Emne: Re: Inherited properties (RC3)
Always prepend ${basedir}
For example ${basedir}/../maven-rep
wkr,
Geoffrey
"Kevin P
> -Original Message-
> From: Kevin Pearcey [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 21, 2004 11:36 AM
> To: 'Maven Users List'
> Subject: RE: Inherited properties (RC3)
>
>
> > > I'm having a problem with my subprojects in maven
> Always prepend ${basedir}
> For example ${basedir}/../maven-rep
>
> wkr,
> Geoffrey
Nope, doesn't make any difference. Path is still evaluated from the sub
projects location rather then where the project.properties file was found
(ie inherited from).
Kevin
---
structure my projects, and it works very well for these reasons.
Ryan
> -Original Message-
> From: Kevin Pearcey [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 21, 2004 10:45 AM
> To: 'Maven Users List'
> Subject: RE: Inherited properties (RC3)
>
>
> &
subproject.
> -Original Message-
> From: Kevin Pearcey [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 21, 2004 10:45 AM
> To: 'Maven Users List'
> Subject: RE: Inherited properties (RC3)
>
>
> > Always prepend ${basedir}
> > For example ${basedir}/../maven-r
Hi,
I'm using rc3 and I have some projects (model, webapp, doc, ...) that
inherit a project called "common" where some properties are set in a
project.properties file.
I run multiproject from the "doc" subproject (this calls all projects except
doc, including the superproject "common") and some o
I have a multilevel project inheritance structure. Where project C inherits from
project B
inherits from project A, etc. I have some properties set up at the top level in
project.properties for things like checkstyle.xml and liscense.txt. If I run
site:generate from
the bottom level project, it
Hi,
There is a known issue with multiproject and inherited properties.
Check http://jira.codehaus.org/browse/MPMULTIPROJECT-32
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
> -Original Message-
> From: Webb Morris [mailto:[EMAIL PROTECTED]
Hello,
I'm trying to upgrade to maven 1.1-beta2.
My project uses commons-attributes and it's maven plugin
When I run a "maven war:install" on my web sub-project, attributes
classes are generated by plugin.
When I run a "multiproject:install", everything SEEMS good, but
attributes classes are
I've observed some unexpected behavior when a declaration in a
parent pom uses a property that is overridden in a child pom.
While waiting for parameterized mixins I'd love to know to what
degree property overriding can actually simulate parameterization.
Is this a FAQ? Were should I search for
Hi Nicolas,
Why do you talk about inherited properties ?
can it be related to http://jira.codehaus.org/browse/MAVEN-1691 ?
Arnaud
On 1/31/06, Nicolas De Loof <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I'm trying to upgrade to maven 1.1-beta2.
> My project uses c
es the attributes classes
(jar) maven jar:install generates the attributes classes
(head) maven multiproject:install generates the attributes classes ONLY
for jar project.
Arnaud HERITIER a écrit :
Hi Nicolas,
Why do you talk about inherited properties ?
can it be related to http://jira.codeh
:
Hi Nicolas,
Why do you talk about inherited properties ?
can it be related to http://jira.codehaus.org/browse/MAVEN-1691 ?
Arnaud
On 1/31/06, Nicolas De Loof <[EMAIL PROTECTED]> wrote:
Hello,
I'm trying to upgrade to maven 1.1-beta2.
My project uses commons-attributes and it
:
Hi Nicolas,
Why do you talk about inherited properties ?
can it be related to http://jira.codehaus.org/browse/MAVEN-1691 ?
Arnaud
On 1/31/06, Nicolas De Loof <[EMAIL PROTECTED]> wrote:
Hello,
I'm trying to upgrade to maven 1.1-beta2.
My project uses commons-attributes and it
the attributes classes
> > (jar) maven jar:install generates the attributes classes
> > (head) maven multiproject:install generates the attributes classes
> > ONLY for jar project.
> >
> > Arnaud HERITIER a écrit :
> >
> >> Hi Nicolas,
> >>
> >
without having to experiment, what the effect
of the given declarations is.
Also: if overriding inherited properties is a supported concept,
it would be cool if maven would follow the lead of good OO programming
languages: let the user specify whether a property definition is intended
to create a fr
> Also: if overriding inherited properties is a supported concept,
> it would be cool if maven would follow the lead of good OO programming
> languages: let the user specify whether a property definition is intended
> to create a fresh property vs. override an inherited one (think @Ove
Hello everyone,
I have been a Maven user for a few months now. I haven't tried to do anything
out of the ordinary. So far our setup is basic, a parent-pom and 7 sub-
projects.
We've recently realized the need to add buildNumbers (from Subversion) to our
builds. Unfortunately, this does us ve
hi,
is there a way to define properties for specific plugins? i have two
problems related to properties that maven profiles doesn't seem to
solve.
- properties defined in the pom.xml are not assured to be carried
over to the plugin. i have already defined properties in the pom.xml
(e.g. curre
Hi,
in one of my parent poms, i have a property like this:
${project.basedir}/../../target/it-repository
This property is then inherited to various child modules which live at
different depths in the inheritance tree.
As far as I understand the maven property inheritance mechanism,
${projec
hi,
the build-phase specific properties is solved (at least) for the
test phase since surefire allows the user to set properties to be
passed to junit tests
(http://maven.apache.org/plugins/maven-surefire-plugin/howto.html).
maybe the same could be implemented for the assembly plugin. :)
c
Sory for this stupid subjet : I was thinking this comes from a
properties failure...
created [http://jira.codehaus.org/browse/MAVEN-1741] for this with a
minimalist test-case
Hello,
I'm trying to upgrade to maven 1.1-beta2.
My project uses commons-attributes and it's maven plugin
When I
28 matches
Mail list logo
