Hi,
in the meantime INFRA has helped here.
Thanks a lot to INFRA Team...
Kind regards
Karl Heinz Marbaise
On 7/6/15 9:08 PM, Karl Heinz Marbaise wrote:
Hi,
does someone has a clue why i'm not allowed to push to this repository:
https://git-wip-us.apache.org/repos/asf/maven-integration-test
Hi,
does someone has a clue why i'm not allowed to push to this repository:
https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: dev-unsubscr...@maven
On 07/02/2009, at 2:43 AM, John Casey wrote:
Can we implement modello's identity/identifier element in maven.mdo
rather than hand-coding the identity methods?
getKey() here is a method, since the identifier is a composite
(groupId + ":" + artifactId). I added a test to make sure the curren
On 07/02/2009, at 7:12 PM, Torben S. Giesselmann wrote:
John Casey wrote:
Is there a reason we haven't banned multiple plugin entries in a
single POM? I thought we talked about this ages ago...frankly, I'm
a little shocked that we never got it in code...
Yes, I was surprised too - I appli
It might be worth adding a warning if a second plugin entry is
detected, as that will begin to create an awareness of this non-
recommended practice.
Christian.
On 7-Feb-09, at 06:12 , Torben S. Giesselmann wrote:
John Casey wrote:
Is there a reason we haven't banned multiple plugin entries
John Casey wrote:
Is there a reason we haven't banned multiple plugin entries in a single
POM? I thought we talked about this ages ago...frankly, I'm a little
shocked that we never got it in code...
I would recommend such a change for 2.1, not 2.0.x, since that would
probably break a lot of e
Can we implement modello's identity/identifier element in maven.mdo
rather than hand-coding the identity methods?
-john
br...@apache.org wrote:
Modified:
maven/components/branches/maven-2.0.x/maven-model/src/main/mdo/maven.mdo
URL:
http://svn.apache.org/viewvc/maven/components/branches/maven
branches/maven-2.0.x/apache-maven/ (props changed)
maven/components/branches/maven-2.0.x/apache-maven/src/test/ (props
changed)
maven/components/branches/maven-2.0.x/maven-integration-tests/ (props
changed)
maven/components/branches/maven-2.0.x/maven-model/src/test/ (
t.
>
> Hudson is running on Redhat linux, but I'm running on Windows and I got
> almost the exact same errors.
>
>
> -Original Message-
> From: Nigel Magnay [mailto:[EMAIL PROTECTED]
>
> Sent: Tuesday, March 18, 2008 7:52 AM
> To: Maven Developers List
>
Nigel Magnay [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 7:52 AM
To: Maven Developers List
Subject: Maven Integration Tests
Help...
I started to run the integration tests to work out why my patch breaks
them, and have moved on to trying to work out why my integration tests
work on some
On 19/03/2008, at 9:04 AM, Brian E. Fox wrote:
Make sure you have installed the latest core integration test folder.
I'll redeploy everything, but it's possible it is out of date. The
Hudson at ci.sonatype.org is building the Its locally everytime it
changes.
That's what I did... I haven't l
TED]
Sent: Tuesday, March 18, 2008 10:29 AM
To: Maven Developers List
Subject: Re: Maven Integration Tests
Ok - I'll compare to what I get.
It still worries me that you've got failures when
https://ci.sonatype.org/job/Maven-2.0.x-ITs/ is showing a clean bill
of health since Mar 17, 2008 3:32:
Ok - I'll compare to what I get.
It still worries me that you've got failures when
https://ci.sonatype.org/job/Maven-2.0.x-ITs/ is showing a clean bill
of health since Mar 17, 2008 3:32:29 PM..
On Tue, Mar 18, 2008 at 2:24 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
> These are the failures I'm g
These are the failures I'm getting today with 2.0.9-SNAPSHOT:
testitMNG2861
(org.apache.maven.integrationtests.MavenITmng2861RelocationsAndRanges)
testitMNG2744
(org
.apache.maven.integrationtests.MavenITmng2744checksumVerificationTest)
- Brett
On 18/03/2008, at 10:51 PM, Nigel Magn
On 18/03/2008, at 10:51 PM, Nigel Magnay wrote:
[1] Added bonus : 12 hours ago, these worked for me on the same
machine...
[2] Looking in the IT test directories, this looks like there's a
"${maven.repo.local}" directory being created which is why things are
getting confused.
This looks rel
Help...
I started to run the integration tests to work out why my patch breaks
them, and have moved on to trying to work out why my integration tests
work on some of my machines, but not others, to a bit of confusion. My
patch is in r638310
r638310 of 2.0.x,
(https://ci.sonatype.org/job/Maven-2.0
Hello,
I am trying to run and understand maven-it suite. It runs OK but
everything is put in my home dir repo instead of in the environment
defined LOCAL_REPO. I this normal ? There is a simple workaround:
create settings.xml in the script with correct settings.
Regards,
--
OQube < software engin
On 25/10/2006, at 7:28 AM, [EMAIL PROTECTED] wrote:
+
+org.apache.maven
+maven-parent
+1
+../pom/maven/pom.xml
+
Isn't this an old parent?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comm
18 matches
Mail list logo
