cowwoc wrote:
>
>
> Jörg Schaible-3 wrote:
>>
>> The point is that it is platform dependent - the platform your developer
>> is
>> using. A profile should not be used to define dependencies - at least if
>> those should be transitively inherited. It simply does not work in the
>> way
>> mos
Jörg Schaible-3 wrote:
>
> The point is that it is platform dependent - the platform your developer
> is
> using. A profile should not be used to define dependencies - at least if
> those should be transitively inherited. It simply does not work in the way
> most people assume. It is not inhe
Hi Gili,
cowwoc wrote:
>
>
> Jörg Schaible-3 wrote:
>>
>> cowwoc wrote:
>>
>>>
>>> Hi Zac,
>>>
>>> I added:
>>>
>>>
>>> win32-x86
>>>
>>
>> You can define this property in your settings.xmll in the appropriate
>> profile.
>>
>> - Jörg
>>
>
> Jörg,
>
> Isn't one of the main selling p
Jörg Schaible-3 wrote:
>
> cowwoc wrote:
>
>>
>> Hi Zac,
>>
>> I added:
>>
>>
>> win32-x86
>>
>
> You can define this property in your settings.xmll in the appropriate
> profile.
>
> - Jörg
>
Jörg,
Isn't one of the main selling points of Maven the ability to include
transitive depend
cowwoc wrote:
>
> Hi Zac,
>
> I added:
>
>
> win32-x86
>
You can define this property in your settings.xmll in the appropriate
profile.
- Jörg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional c
Hi Zac,
I added:
win32-x86
to project C but Maven still complains:
Failed to execute goal on project C: Could not resolve dependencies for
project com.foo:C:jar:1.0-SNAPSHOT: Failure to find
org.eclipse.swt:swt:jar:${swt.classifier}:3.6
I posted a reply to this on stackoverflow, since that's where you
included more details. The bottom line was that the properties are
*not* defined in A or B, only in *profiles* in A and B. And there's
the rub: those profiles do not apply when building C, and the property
is not defined anywhere i
On 2/7/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:
Hi Tommy,
Tommy Knowlton wrote on Thursday, February 08, 2007 3:30 AM:
> On 2/7/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:
>> Tommy Knowlton wrote on Tuesday, February 06, 2007 11:19 PM:
>>
>>> Is this a bug in the code that resolves ${proje
Hi Tommy,
Tommy Knowlton wrote on Thursday, February 08, 2007 3:30 AM:
> On 2/7/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:
>> Tommy Knowlton wrote on Tuesday, February 06, 2007 11:19 PM:
>>
>>> Is this a bug in the code that resolves ${project} references?
>>
>> No, this is a feature (that fa
On 2/7/07, Jörg Schaible <[EMAIL PROTECTED]> wrote:
Tommy Knowlton wrote on Tuesday, February 06, 2007 11:19 PM:
> Is this a bug in the code that resolves ${project} references?
No, this is a feature (that fails miserably when the directory in your
repository does not match the artifactId ...
Tommy Knowlton wrote on Tuesday, February 06, 2007 11:19 PM:
> Hello,
>
> I've got a parent POM that declares e.g.,
>
>
> ...
> http://javabuild2.mycompany.com/${project.artifactId}
>
>
> (in other words, top-level configuration that varies by the project
> that has declared this parent)
> You may want to use transitive parents. By this I mean have B depend
> on A, C depend on B, etc. This way, when C is dependent on B, C is
> also dependent on A. Thanks.
This message (including any attachments) contains confidential information
intended for a specific individual and purpose
Good day to you, jp4,
Maven2 does not have multiple pom inheritance.
You may want to try and use profile.xml and build.xml. I am not sure if they
can be used as workarounds to "2nd" and "3rd parents" though, but that's the
only thing I can think of right now.
Cheers,
Franz
jp4 wrote:
>
> I
Don't know if this helps any but here is how I worked around the links not
working issue -- its ugly:
maven-antrun-plugin
pre-site
I had a similar issue: I set up to the url tag :
http://yoururl in my pom parent.
(I don't know why but you cannot use relative url)
Yann
Breddy wrote:
Group,
I have a POM that inherits from another using a relative path that looks
something like ../parent-pom-dir/pom.xml. All POM inheritance
Thanks Fabrice ;)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: mardi 22 novembre 2005 14:03
To: Maven Users List
Subject: RE: POM inheritance
Damien,
have a look at
http://maven.apache.org/guides/introduction/introduction
Damien,
have a look at
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
HTH
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - [EMAIL PROTECTED]
No, but we should have.
(most things are)
- Brett
On 10/24/05, Jorg Heymans <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Is there a document describing what exactly is transferred from the
> parent pom to the child when doing things like :
>
>
> apache-cocoon
> cocoon
> 2.2-SNAPSHOT
>
On 5/20/05, Walter Vandeweyer <[EMAIL PROTECTED]> wrote:
> I did find out that is very comfortable to use POM inheritance, by writing a
> central Project.xml, and having all the others extending from it, like :
>
> ${basedir}/../project.xml
>
> However there is a problem when building versioned
On Mon, 2004-03-08 at 13:42, John Casey wrote:
> This has been my experience. I'm not sure it's being addressed for
> future releases, but I think it's safe to say that cleaner inheritance
> won't be implemented in maven until post-1.0...
Arbitrary levels of inheritance works well and is tested in
This has been my experience. I'm not sure it's being addressed for
future releases, but I think it's safe to say that cleaner inheritance
won't be implemented in maven until post-1.0...
-john
On Mon, 2004-03-08 at 12:14, JÃrn Gebhardt wrote:
> Hi,
> is it possible that the project inheritance wor
21 matches
Mail list logo
