mthmulders edited a comment on pull request #177:
URL: https://github.com/apache/maven-site/pull/177#issuecomment-657255635
Your pull request has been merged. Thanks again for your contribution!
This is an automated message f
mthmulders commented on pull request #177:
URL: https://github.com/apache/maven-site/pull/177#issuecomment-657255635
Your pull request has been merged into master. Thanks again for your
contribution!
This is an automated mes
mthmulders closed pull request #177:
URL: https://github.com/apache/maven-site/pull/177
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
dpd73 commented on a change in pull request #177:
URL: https://github.com/apache/maven-site/pull/177#discussion_r453312612
##
File path: content/apt/guides/getting-started/index.apt
##
@@ -370,40 +378,47 @@ mvn install
Upon executing this command you should see the following
mthmulders removed a comment on pull request #177:
URL: https://github.com/apache/maven-site/pull/177#issuecomment-657210544
Thanks for updating this guide! Overall it looks good to me, I have left one
small remark.
This is
mthmulders commented on a change in pull request #177:
URL: https://github.com/apache/maven-site/pull/177#discussion_r453305679
##
File path: content/apt/guides/getting-started/index.apt
##
@@ -370,40 +378,47 @@ mvn install
Upon executing this command you should see the follo
mthmulders commented on pull request #177:
URL: https://github.com/apache/maven-site/pull/177#issuecomment-657210544
Thanks for updating this guide! Overall it looks good to me, I have left one
small remark.
This is an autom
dpd73 opened a new pull request #177:
URL: https://github.com/apache/maven-site/pull/177
https://issues.apache.org/jira/browse/MNGSITE-416
This is an automated message from the Apache Git Service.
To respond to the message, p
psed: 2,257.786 sec
> - in RunnerClass.CucumberRunnerTest
> Results: Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>
> 2. I keep getting a BUILD failure..and I believe the reason is that it says
> could Could not parse build number: ${${build.number}}. when it is about to
> g
Hi,
Remove the blank line at the beginning of the file. The processing
instruction Hello Team,
>
> I'm following the instructions on
>
> https://wiki.jasig.org/display/CASUM/Best+Practice+-+Setting+Up+CAS+Locally+using+the+Maven2+WAR+Overlay+Method
>
> I'm using the pom.xml file that is described
I think you did something wrong while pastiong from the web page.
According to the error, it seems your pom didn't start with wrote:
> Hello Team,
>
> I'm following the instructions on
>
> https://wiki.jasig.org/display/CASUM/Best+Practice+-+Setting+Up+CAS+Locally+using+the+Maven2+WAR+Overlay+Met
Hello Team,
I'm following the instructions on
https://wiki.jasig.org/display/CASUM/Best+Practice+-+Setting+Up+CAS+Locally+using+the+Maven2+WAR+Overlay+Method
I'm using the pom.xml file that is described on the upper page.
the problem is that I'm stuck at the step "Build it" where we build the Ca
This is because maven-remote-resources-plugin:1.1 requires Java 1.5, and
this Builder is using Java 1.4.
On 2010-02-10 12:37, contin...@vmbuild.apache.org wrote:
> Online report :
> http://vmbuild.apache.org/continuum/buildResult.action?buildId=282248&projectId=1251
>
> Build statistics:
> Sta
The problem dissapear after upgrading to IBM SDK SR10.
2009/11/6 Patrick Schneider :
> Did you get this figured out? I've seen the MalformedInputException before
> on Windows machines when the default character endcoding is being used.
>
> Are you configuring the resource plugin at all, or relyi
Did you get this figured out? I've seen the MalformedInputException before
on Windows machines when the default character endcoding is being used.
Are you configuring the resource plugin at all, or relying on defaults? You
might try specifying UTF-8 explicitly in there.
On Tue, Nov 3, 2009 at 8
Henri Gomez wrote:
What's the JIRA for this problem (and fix in r832389) ?
I'd like to verify if this bug could affect some of ours projects
There is no JIRA because it's not a bug in Maven itself. As visible from
the mentioned SVN revision, the failure to build Maven was due to a
corrupt re
FYI:
After upgrading our IBM SDK 1.5 to SR10 (build pxi32dev-20090707
(SR10 ), maven-3 from trunk build with maven 2.2.1.
SDK is now :
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build
pxi32dev-20090707 (SR10 ))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32
Hi Benjamin,
What's the JIRA for this problem (and fix in r832389) ?
I'd like to verify if this bug could affect some of ours projects
Regards
2009/11/3 Benjamin Bentmann :
> Henri Gomez wrote:
>
>> Caused by: org.apache.maven.shared.filtering.MavenFilteringException
>> at
>> org.apache.m
> Henri Gomez wrote:
>
>> Caused by: org.apache.maven.shared.filtering.MavenFilteringException
>> at
>> org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:130)
>> at
>> org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterRe
Henri Gomez wrote:
Caused by: org.apache.maven.shared.filtering.MavenFilteringException
at
org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:130)
at
org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources(Defa
A note on this one.
Build works with an IBM SDK 6.
2009/11/3 Henri Gomez :
> Hi to all,
>
> I just added a job on our Hudson server to build Maven 3.0 from the trunk.
> The job use maven 2.2.1 and a custom repository (to avoid collisions
> with our others projects).
> Goals are clean install and
Hi to all,
I just added a job on our Hudson server to build Maven 3.0 from the trunk.
The job use maven 2.2.1 and a custom repository (to avoid collisions
with our others projects).
Goals are clean install and MAVEN_OPTS is set to -Xmx512m
No problem when I use a Sun JVM Java 5.
But if I select
Thanks.
--
Olivier
2008/10/3 Brett Porter <[EMAIL PROTECTED]>:
> Yep, sorry, I got side tracked after trying this the other day. I'll change
> it now.
>
> On 03/10/2008, at 7:08 PM, Olivier Lamy wrote:
>
>> is-it possible to use an other ml ?
>>
>> 2008/10/3 [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
Yep, sorry, I got side tracked after trying this the other day. I'll
change it now.
On 03/10/2008, at 7:08 PM, Olivier Lamy wrote:
is-it possible to use an other ml ?
2008/10/3 [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buil
is-it possible to use an other ml ?
2008/10/3 [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> Online report :
> http://vmbuild.apache.org/continuum/buildResult.action?buildId=118181&projectId=1247
>
> Build statistics:
> State: Failed
> Previous State: Failed
> Started at: Fri 3 Oct 2008 01:11:58 -070
These were caused by my upgrade to Modello 1.0-alpha-19. I was just a
little to quick, because the artifacts hadn't made it central yet. They
are there now, so the next build should be OK.
[EMAIL PROTECTED] wrote:
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=1
On 01/07/2008, at 10:36 AM, Shane Isbell wrote:
On a clean build and repo, I can't get past maven-project:
MavenProjectDynamismTest, 4 failures. If I remove that, I run into
runtime
errors on all the ITs dealing with a missing method in the
interpolator.
Yes, see the report by Henri, and
On a clean build and repo, I can't get past maven-project:
MavenProjectDynamismTest, 4 failures. If I remove that, I run into runtime
errors on all the ITs dealing with a missing method in the interpolator.
Shane
On Mon, Jun 30, 2008 at 5:07 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> On 01/
On 01/07/2008, at 3:08 AM, John Casey wrote:
Pretty sure this is fixed. It's building on my localhost and hudson
now...not sure about continuum (yet)
It did tick over successfully shortly after your mail.
However, it's back to failing on it0081 / it0065 again. It seems I am
not crazy then
Pretty sure this is fixed. It's building on my localhost and hudson
now...not sure about continuum (yet)
Brett Porter wrote:
John,
Can you check this one out - I was first getting it on my local
machines and so tried it here. I can't check it in Hudson due to other
build errors that are uniq
John,
Can you check this one out - I was first getting it on my local
machines and so tried it here. I can't check it in Hudson due to other
build errors that are unique to there.
It looks related to the interpolation changes. If I use the built
maven on that project, I get this error:
d I am attaching a patch, in case
anyone else runs into it and needs the fix.
Cheers,
Deepak
-Original Message-
From: Deepak Bhole [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 15, 2008 5:34 PM
To: Brian E. Fox
Cc: Maven Developers List
Subject: Re: Maven 2.0.9 build failure
* Brian
> Cc: Maven Developers List
> Subject: Re: Maven 2.0.9 build failure
>
> * Brian E. Fox <[EMAIL PROTECTED]> [2008-04-15 17:21]:
> > Not many people are using the bootstrap on 2.0.x. Just grab 2.0.8 (or
> > 2.0.9) and build it as a normal maven project.
> >
> &
:[EMAIL PROTECTED]
Sent: Tuesday, April 15, 2008 5:34 PM
To: Brian E. Fox
Cc: Maven Developers List
Subject: Re: Maven 2.0.9 build failure
* Brian E. Fox <[EMAIL PROTECTED]> [2008-04-15 17:21]:
Not many people are using the bootstrap on 2.0.x. Just grab 2.0.8 (or
2.0.9) and build it as a normal
Subject: Re: Maven 2.0.9 build failure
* Brian E. Fox <[EMAIL PROTECTED]> [2008-04-15 17:21]:
> Not many people are using the bootstrap on 2.0.x. Just grab 2.0.8 (or
> 2.0.9) and build it as a normal maven project.
>
>
Thanks, that worked. Are there plans to make bootstrap wo
package in Fedora, and from a packaging
perspective, bootstrapping is a valuable option...
Deepak
> -Original Message-
> From: Deepak Bhole [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 15, 2008 5:15 PM
> To: dev@maven.apache.org
> Subject: Maven 2.0.9 build failure
>
Not many people are using the bootstrap on 2.0.x. Just grab 2.0.8 (or
2.0.9) and build it as a normal maven project.
-Original Message-
From: Deepak Bhole [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 15, 2008 5:15 PM
To: dev@maven.apache.org
Subject: Maven 2.0.9 build failure
Hi,
I
Hi,
I checked out the 2.0.9 tag from here:
http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.9
rm -rf'd ~/.m2, set M2_HOME to $PWD/build/apache-maven-2.0.9, and
ran ./bootstrap.sh. However, the build keeps failing:
--- BEGIN ---
Building project in /tmp/maven2-build/maven2/apach
778.477 sec <<< FAILURE!
Results :
Tests in error:
testDependencyManagementForOverConstrainedRanges
(org
.apache
.maven
.integrationtests
.MavenITmng3396DependencyManagementForOverConstrainedRanges)
Tests run: 125, Failures: 0, Errors: 1, Skipped
ange (2.0.8,))
>
> 0115CustomArtifactHandlerAndCustomLifecycle(testit0115).. Ok
> 0119PluginPrefixOrder(testit0119).. Ok
> mng3099SettingsProfilesWithNoPOM(testitMNG3099).. Skipping (version 2.0.7
> not in range (2.0.8,))
> mng3331ModulePathNormalization(test
; [INFO] Uploading project information for maven-deploy-test 1.0-SNAPSHOT
> > > [INFO] Retrieving previous metadata from deploy-test
> > > [INFO] Uploading repository metadata for: 'snapshot
> org.apache.maven.test:maven-deploy-test:1.0-SNAPSHOT'
> > > [I
revious build number from deploy-test
> > [INFO] Retrieving previous metadata from deploy-test
> > [INFO] Uploading repository metadata for: 'artifact
> org.apache.maven.test:attached-artifact-test-0'
> > [INFO] Retrieving previous metadata from deploy-test
>
tinuum/checkouts/13/target/ssh-user-home
> Testing .ssh dir:
> /export/home/build/data/continuum/checkouts/13/target/ssh-user-home/.ssh
> Tests run: 7, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 1.62 sec <<<
> FAILURE!
> Running org.apache.maven.plugin.deploy.Deplo
On Feb 11, 2008 7:19 AM, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> We don't use jpox 1.1.9 but 1.1.7
That explains it. :) Archiva switched to jpox 1.1.9, and we were
discussing it here-- I have local changes.
Well, heads up that it may be a problem if we upgrade!
--
Wendy
We don't use jpox 1.1.9 but 1.1.7
Emmanuel
On Feb 10, 2008 7:47 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> I'm having trouble building the trunk of Continuum. It's complaining
> about:
>
> Missing:
> --
> 1) bcel:bcel:jar:5.2
> ...
> Path to dependency:
>1) org.apache.maven.c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Kulp wrote:
> On Thursday 13 December 2007, Brett Porter wrote:
>> is PMD JDK 5 only now?
>
> Yes. But they are working on getting a retrotranslated version submitted
> to central the the plugin can use.
>
> Dan
Hi,
Now that my upload req
> >>> **
> >>>** [INFO] Scanning for projects...
> >>> [INFO]
> >>> --
> >>>-- ---- [INFO] Buil
resources.
[INFO] Copying 4 resources
[INFO] [compiler:compile]
[INFO] Compiling 9 source files to
/export/home/build/data/continuum/ checkouts/27/target/classes
[INFO]
---------
for language: java
> > [INFO] Extractor for language: java found 4 mojo descriptors.
> > [INFO] Applying extractor for language: bsh
> > [INFO] Extractor for language: bsh found 0 mojo descriptors.
> > [INFO] [resources:resources]
> > [INFO] Using default encoding to copy filtered reso
resources.
[INFO] Copying 4 resources
[INFO] [compiler:compile]
[INFO] Compiling 9 source files to /export/home/build/data/continuum/
checkouts/27/target/classes
[INFO]
---------
e elapsed:
0.181 sec <<< FAILURE!
Results :
Tests in error:
testDeleteDontFollowSymlinks
(org.apache.maven.shared.model.fileset.util.FileSetUtilsTest)
Tests run: 4, Failures: 0, Errors: 1, Skipped: 0
[INFO
torAccessorImpl.newInstance(
> NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance (
> DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
> at
&
/home/build/data/continuum/checkouts/9/target/surefire-reports
> >
> > -------
> > T E S T S
> > ---
> > Running org.apache.maven.plugin.clean.CleanMojoTest
> > [info] Deleting directory
> /export/home/build/data/continuum/checkouts
um/checkouts/9/target/testDirectoryStructure/buildOutputDirectory
> [info] Deleting directory
> /export/home/build/data/continuum/checkouts/9/target/testDirectoryStructure/buildTestDirectory
> [info] Deleting directory
> /export/home/build/data/continuum/checkouts/9/target/test
On 11/11/2007, at 6:25 AM, [EMAIL PROTECTED] wrote:
Tests in error: testit0039
(org.apache.maven.integrationtests.MavenIT0039Test)
Anyone else seeing this breaking? I get it here as well, but the
error is just that the it0039 directory isn't found - I haven't
looked into it yet.
http:/
5:56:00 AM
To: [EMAIL PROTECTED]
Subject: [continuum] BUILD FAILURE: Maven Artifact
Reply-To: dev@maven.apache.org
Reply-To: "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]>
List-Id:
Message-Id:
<[EMAIL PROTECTED]>
Online report : http://maven.zones.apache.org/continuum/
buildResult
d resources.
[INFO] Copying 1 resource
[INFO] [compiler:compile]
[INFO] Compiling 119 source files to /export/home/build/data/
continuum/checkouts/442/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
-
ource
[INFO] [compiler:compile]
[INFO] Compiling 119 source files to /export/home/build/data/
continuum/checkouts/442/target/classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
--
19 source files to /export/home/build/data/
continuum/checkouts/442/target/classes
[INFO]
------
--
[ERROR] BUILD FAILURE
[INFO]
--
--
[INFO] Compilation failure
Failure execut
On 03/11/2007, at 5:25 PM, Jason van Zyl wrote:
The core IT plugins all get installed as 2.1-SNAPSHOT (when or who
changed that), but that test is looking for 1.0-SNAPSHOT. I always
install all the plugins as part of running the ITs, and I've not
had that problem. That plugin is looking fo
On 2 Nov 07, at 7:56 PM 2 Nov 07, Brett Porter wrote:
Hey John,
On 03/11/2007, at 11:56 AM, [EMAIL PROTECTED] wrote:
Tests in error:
testit0046(org.apache.maven.integrationtests.MavenIT0046Test)
Looks like your changes fixed the two IT problems, but this seems to
be a new one? I get th
Hey John,
On 03/11/2007, at 11:56 AM, [EMAIL PROTECTED] wrote:
Tests in error: testit0046
(org.apache.maven.integrationtests.MavenIT0046Test)
Looks like your changes fixed the two IT problems, but this seems to
be a new one? I get the same result locally - it's not able to find
one of th
/113/target/surefire-reports
---
T E S T S
---
Running org.apache.maven.continuum.store.ContinuumStoreTest
[INFO]
--
--
[ERROR] BUILD FAILURE
[INFO
stReport(org.apache.maven.report.projectinfo.TeamListReportTest)
> testReport(org.apache.maven.report.projectinfo.ProjectIndexPageReportTest)
> testReport(org.apache.maven.report.projectinfo.ProjectSummaryReportTest)
> testReport(org.apache.maven.report.projectinfo.IssueTrackingReportTest)
> testReport
On 25/09/2007, at 6:14 AM, Dennis Lundberg wrote:
It turned out I had some local changes that I had forgotten to
commit. After committing those Continuum seems happy. Can you try
again locally, just to make sure?
That did the trick - thanks!
- Brett
---
It turned out I had some local changes that I had forgotten to commit.
After committing those Continuum seems happy. Can you try again locally,
just to make sure?
Brett Porter wrote:
I get this locally too - anyone else seen it?
- Brett
On 24/09/2007, at 11:55 PM, [EMAIL PROTECTED] wrote:
O
I get this locally too - anyone else seen it?
- Brett
On 24/09/2007, at 11:55 PM, [EMAIL PROTECTED] wrote:
Online report : http://maven.zones.apache.org/continuum/
buildResult.action?buildId=24366&projectId=32
Build statistics:
State: Failed
Previous State: Failed
Started at: Mon 24 Sep 2
s: 0, Errors: 0, Skipped: 0, Time elapsed: 4.126
sec
Results :
Tests in error:
testSibling
(org.apache.maven.plugin.dependency.its.DependencyPluginTest)
testResolve
(org.apache.maven.plugin.dependency.its.DependencyPluginTest)
Tests run: 236, Failures: 0, Errors: 2, Skipped: 0
[INFO]
--
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, September 24, 2007 4:32 AM
To: [EMAIL PROTECTED]
Subject: [continuum] BUILD FAILURE: Maven Dependency Plugin
Online report :
http://maven.zones.apache.org/continuum/buildResult.action?buildId=24268
&proje
> this...
>
> Begin forwarded message:
>
> > From: "[EMAIL PROTECTED]"
> > <[EMAIL PROTECTED]>
> > Date: 9 September 2007 9:30:28 AM
> > To: [EMAIL PROTECTED]
> > Subject: [continuum] BUILD FAILURE: Maven Dependency Tree
> > Re
PROTECTED]>
Date: 9 September 2007 9:30:28 AM
To: [EMAIL PROTECTED]
Subject: [continuum] BUILD FAILURE: Maven Dependency Tree
Reply-To: dev@maven.apache.org
Reply-To: "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]>
List-Id:
Message-Id:
<[EMAIL PROTECTED]>
Online repor
On 08/09/2007, at 12:25 AM, Jason van Zyl wrote:
On 7 Sep 07, at 2:19 AM 7 Sep 07, Brett Porter wrote:
I guess you're out for the night now... anyway, until we get the
direct nag happening I'll just pass it on :)
I just checked again, no changes for me locally, bootstrapped again
and
[INFO] [compiler:compile]
[INFO] Compiling 24 source files to /export/home/build/data/
continuum/checkouts/486/target/classes
[INFO]
---------
---
[ERROR] BUILD FAILURE
[INFO]
6/target
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] [compiler:compile]
[INFO] Compiling 24 source files to /export/home/build/data/
continuum/checkouts/486/target/classes
[INFO]
------
ault encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] [compiler:compile]
[INFO] Compiling 24 source files to /export/home/build/data/
continuum/checkouts/486/target/classes
[INFO]
---------
[resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] [compiler:compile]
[INFO] Compiling 24 source files to /export/home/build/data/
continuum/checkouts/486/target/classes
[INFO]
----------
dealing
with heavy sets of changes. Removing modules or moving classes
between modules seems to throw it for a loop.
- Brett
Begin forwarded message:
From: "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]>
Date: 7 September 2007 4:48:51 AM
To: [EMAIL PROTECTED]
Subject: [continuu
On 07/09/2007, at 2:00 PM, Jason van Zyl wrote:
On 6 Sep 07, at 12:17 PM 6 Sep 07, Brett Porter wrote:
Jason - you're aware of this?
Builds fine in Hudson and on my machine, you sure this isn't a
Continuum error?
This morning - no, it failed on my machine as well when I
bootstrapped
Jason - you're aware of this?
- Brett
Begin forwarded message:
From: "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]>
Date: 7 September 2007 4:48:51 AM
To: [EMAIL PROTECTED]
Subject: [continuum] BUILD FAILURE: Maven Project Builder
Reply-To: dev@maven.apache.org
Reply-
installed surefire-2.3.1-SNAPSHOT, which I hadn't done previously,
and now
I'm having the build failure.
Thanks for your help, Dennis.
Hervé
Le dimanche 26 août 2007, Dennis Lundberg a écrit :
I think I solved this, at least it works locally for me now. It seems to
be the same kind of
Thanks Dennis.
So is this the same as SUREFIRE-347? If it's a different regression,
it be good to file it.
- Brett
On 27/08/2007, at 7:32 AM, Hervé BOUTEMY wrote:
Yes, that's it!
I installed surefire-2.3.1-SNAPSHOT, which I hadn't done
previously, and now
I'm havi
Yes, that's it!
I installed surefire-2.3.1-SNAPSHOT, which I hadn't done previously, and now
I'm having the build failure.
Thanks for your help, Dennis.
Hervé
Le dimanche 26 août 2007, Dennis Lundberg a écrit :
> I think I solved this, at least it works locally for me now. It
please add some karma for me (dennisl) in
[EMAIL PROTECTED] It would be nice to be able to run the builds
manually.
Hervé BOUTEMY wrote:
I looked at this build failure and found misc problem when investigating:
1. I can't reproduce the problem on my machine:
same Maven version, sam
I get the same failures on Windows XP with Maven 2.0.6/2.0.7 and Sun JDK
1.4.2_13/1.5.0_11.
Hervé BOUTEMY wrote:
I looked at this build failure and found misc problem when investigating:
1. I can't reproduce the problem on my machine:
same Maven version, same JDK version, no SNA
I looked at this build failure and found misc problem when investigating:
1. I can't reproduce the problem on my machine:
same Maven version, same JDK version, no SNAPSHOT dependency, but I get no
surefire failure
Do I miss something in my configuration? Does somebody reproduce the proble
updates from central
> [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
> [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0
> -
> this realm = plexus.core
> Number of imports: 0
>
Hi,
I'm developing a plugin for Maven and I'll need it to execute only if
the build has failed (or maybe if it succeeded). So I'd like to know
if there's a way to do this conditional execution.
Thanks,
--
Ruben Gutierrez
-
To
on-ssh-external:1.0-
>> beta-3-SNAPSHOT: checking for updates from apache.snapshots
>> [INFO] snapshot org.apache.maven.wagon:wagon-ssh:1.0-beta-3-
>> SNAPSHOT: checking for updates from codehaus.snapshots
>> [INFO] snapshot org.apache.maven.wagon:wagon-ssh:1.0-beta-3-
>> SNAPSHOT: checking for updates from
-external:1.0-
>> beta-3-SNAPSHOT: checking for updates from codehaus.snapshots
>> [INFO] snapshot org.apache.maven.wagon:wagon-ssh-external:1.0-
>> beta-3-SNAPSHOT: checking for updates from apache.snapshots
>> [INFO] snapshot org.apache
s-container-default/1.0-alpha-16-SNAPSHOT/
plexus-container-default-1.0-alpha-16-20070122.203121-16.jar
205K downloaded
[INFO] [compiler:compile]
[INFO] Compiling 16 source files to /export/home/continuum/
continuum_data/working-directory/185/target/classes
[INFO]
-
[INFO] Compiling 16 source files to
/export/home/continuum/continuum_data/working-directory/185/target/classes
[INFO] --------
[ERROR] BUILD FAILURE
[INFO]
I think this is because the other CI builds are nuking the local
repository. I'll need to make continuum use a different one.
- Brett
On 11/01/2007, at 8:28 AM, [EMAIL PROTECTED] wrote:
Online report : http://maven.zones.apache.org/continuum/
buildResult.action?buildId=612&projectId=32&proje
On 12/14/06, Rahul Thakur <[EMAIL PROTECTED]> wrote:
did you find what was causing it? :-)
Not yet.
I think the problem is in ProjectTool.manglePomForTesting
but I need to do more investigating.
I am looking into why internal_plugins dont work and this is higher
priority for me at the momen
did you find what was causing it? :-)
Barrie Treloar wrote:
On 12/13/06, Rahul Thakur <[EMAIL PROTECTED]> wrote:
If i remember correct from what I saw in the m-e-p sources last week,
maven-eclipse-plugin-test is created by the Plugin unit tests and then
installed to a *test* repo local to the
On 12/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
"Barrie Treloar" <[EMAIL PROTECTED]> schrieb am 13.12.2006 01:47:02:
> Running mvn in debug mode so I can attach eclipse to the running
instance.
How do you do that?
Copy your mvn script to something like mvn-debug.{bat|.sh}
Then find
"Barrie Treloar" <[EMAIL PROTECTED]> schrieb am 13.12.2006 01:47:02:
> Running mvn in debug mode so I can attach eclipse to the running
instance.
How do you do that?
Regards,
--
Aaron Digulla
-
To unsubscribe, e-mail: [EMAIL
On 12/13/06, Rahul Thakur <[EMAIL PROTECTED]> wrote:
If i remember correct from what I saw in the m-e-p sources last week,
maven-eclipse-plugin-test is created by the Plugin unit tests and then
installed to a *test* repo local to the Eclipse project.
Not sure why is your build seeing the -test v
If i remember correct from what I saw in the m-e-p sources last week,
maven-eclipse-plugin-test is created by the Plugin unit tests and then
installed to a *test* repo local to the Eclipse project.
Not sure why is your build seeing the -test version. Do you have
maven-eclipse-plugin sources ch
Manually hacking the jar to set the version correctly resolves the problem.
Now to find out why the jar is being created incorrectly...
Running mvn package will incorrectly create a "test" version for the
real version jar.
I just noticed that there are two jars in here:
* maven-eclipse-plugin
!/META-INF/maven/plugin.xml
Internal release from subversion revision r485327.
Applied patches:
* http://jira.codehaus.org/browse/MECLIPSE-206
* parent version now 4 instead of 4-SNAPSHOT
org.apache.maven.plugins
maven-eclipse-plugin
test
[del]
My pom version is:
2.3-INTE
1 - 100 of 247 matches
Mail list logo
