Re: Building Maven Under JDK 24

On 3/19/25 23:34, Mark Derricutt wrote: > On 20 Mar 2025 at 10:04:24 AM, Romain Manni-Bucau > wrote: > >> did you try upgrading asm in plugin deps? >> > Nope - but a cursory glance shows asm 9.7.1 being used, which is the > current version. i ended up bumping asm as direct dependency in most pro

Re: Building Maven Under JDK 24

On 20 Mar 2025 at 9:43:02 PM, Guillaume Nodet wrote: > And raise a PR. I suppose we should add jdk24 to the list of JDK we're > building against: > Looks like an upstream ticket has already been raised to add the new ASM to Sisu: https://github.com/eclipse-sisu/sisu-project/issues/174 I’ve

Re: Building Maven Under JDK 24

And raise a PR. I suppose we should add jdk24 to the list of JDK we're building against: https://github.com/apache/maven/blob/master/.github/workflows/maven.yml#L86 Le jeu. 20 mars 2025 à 08:18, Romain Manni-Bucau a écrit : > Or just upgrade asm in plugin dependencies ;) > > Romain Manni-Bucau

Re: Building Maven Under JDK 24

Or just upgrade asm in plugin dependencies ;) Romain Manni-Bucau @rmannibucau | .NET Blog | Blog | Old Blog | Github | LinkedIn

Re: Building Maven Under JDK 24

On 20 Mar 2025 at 7:12:40 PM, Romain Manni-Bucau wrote: > Looks like the error says the opposite, did you check the plugin asm > version and not maven one? > > > Looks like the build is using 0.9.0.M3 of the issue-maven-plugin, which includes and embeded version of asm 9.6: https://github.com/e

Re: Building Maven Under JDK 24

Looks like the error says the opposite, did you check the plugin asm version and not maven one? Romain Manni-Bucau @rmannibucau | .NET Blog | Blog | Old Blog | Github <

Re: Building Maven Under JDK 24

On 20 Mar 2025 at 10:04:24 AM, Romain Manni-Bucau wrote: > did you try upgrading asm in plugin deps? > Nope - but a cursory glance shows asm 9.7.1 being used, which is the current version. -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree

Re: Building Maven Under JDK 24

Hi, did you try upgrading asm in plugin deps? Romain Manni-Bucau @rmannibucau | .NET Blog | Blog | Old Blog | Github | LinkedIn

Building Maven Under JDK 24

Whilst Maven 4 is targeting Java 17, I see the build doesn’t seem to work under Java 24: [INFO] --- sisu:0.9.0.M3:main-index (index-project) @ maven-model-builder --- [INFO] [INFO] Reactor Summary for Apache Maven 4.0.0-rc-4-

Re: Building Maven from scratch

Hi Karl Heinz, On Wed, 24 Aug 2016 19:54:07 +0200 Karl Heinz Marbaise wrote: > First we call Maven Core this: > > https://git-wip-us.apache.org/repos/asf/maven.git > > which is Maven itself and in the end can be downloaded from > http://maven.apache.org/download.html and what you call usuall

Re: Building Maven from scratch

till Maven 3.3.9 starting with Maven 3.4.0 you need Maven 3.3.9 to build Maven 3.4.0...Details [1]. That is fine. I really thought it would be worse: Building maven 2 with 1, 3 with 2, or worse. But it seams I have to go back some way. Where should I start? Is there some manual? What exactly is

Re: Building Maven from scratch

n 3.3.9 starting with Maven 3.4.0 > you need Maven 3.3.9 to build Maven 3.4.0...Details [1]. That is fine. I really thought it would be worse: Building maven 2 with 1, 3 with 2, or worse. But it seams I have to go back some way. Where should I start? Is there some manual? What exactly is maven

Re: Building Maven from scratch

Hi Björn, On 23/08/16 08:25, Björn Höfling wrote: I want to build maven without haven _ANY_ maven/plugin binary. How can I do that? First you can do that only till Maven 3.3.9 starting with Maven 3.4.0 you need Maven 3.3.9 to build Maven 3.4.0...Details [1]. The question is why do you want

Re: Building Maven from scratch

I doubt this is possible. We used to support building Maven core with Ant, but IIRC a fairly recent discussion resulted in a decision to stop supporting that. So you need Maven installed to build Maven core. More info here: http://maven.apache.org/guides/development/guide-building-maven.html

Re: Building Maven from scratch

Out of curiosity, what is your usecase? -- Regards, Igor On Tue, Aug 23, 2016, at 02:25 AM, Björn Höfling wrote: > I want to build maven without haven _ANY_ maven/plugin binary. How can > I do that? > > I found out that there is a build.xml and it start building a first > version of Maven. But

Building Maven from scratch

I want to build maven without haven _ANY_ maven/plugin binary. How can I do that? I found out that there is a build.xml and it start building a first version of Maven. But then it needs plugins to go further. I found the plugins source here: https://maven.apache.org/plugins/ But these have only p

Re: Building maven-scm

On Fri, Sep 12, 2014 at 4:51 PM, Karl Heinz Marbaise wrote: > Hi Benson, > > On 9/12/14 10:36 PM, Benson Margulies wrote: > >> On my mac, using maven 3.0.4, the master of maven-scm gets a bazillion >> unit >> test failures on "Maven SCM Subversion Provider - SVN Executable Impl.". >> >> Is there

Re: Building maven-scm

Hi Benson, On 9/12/14 10:36 PM, Benson Margulies wrote: On my mac, using maven 3.0.4, the master of maven-scm gets a bazillion unit test failures on "Maven SCM Subversion Provider - SVN Executable Impl.". Is there something I need to know? Which version of SVN command line client do you have

Building maven-scm

On my mac, using maven 3.0.4, the master of maven-scm gets a bazillion unit test failures on "Maven SCM Subversion Provider - SVN Executable Impl.". Is there something I need to know? Am I likelier to be cheerful on Linux?

Re: Building Maven Fluido Skin site dies with incorrect artifact resolution

Am 2013-12-10 01:56, schrieb Hervé BOUTEMY: on my machine, build with Maven 3.1.1 works actually old 2.4 m-pir-p is used, which doesn't use Aether, so it works both for Maven 3.0.x and 3.1.x To test a skin, I suppose this old version is sufficient do you have issues? Yes, I do. Maven 3.1.1 an

Re: Building Maven Fluido Skin site dies with incorrect artifact resolution

on my machine, build with Maven 3.1.1 works actually old 2.4 m-pir-p is used, which doesn't use Aether, so it works both for Maven 3.0.x and 3.1.x To test a skin, I suppose this old version is sufficient do you have issues? Regards, Hervé Le mardi 10 décembre 2013 01:12:43 Michael-O a écrit :

Re: Building Maven Fluido Skin site dies with incorrect artifact resolution

Am 2013-12-10 00:54, schrieb Hervé BOUTEMY: AFAIK, this is due to the fact that the skin uses itself, which is a good thing to show the effective result for people wanting to use it, but it costs this little problem: the most recent version is the version actually built, not what is in local repo

Re: Building Maven Fluido Skin site dies with incorrect artifact resolution

AFAIK, this is due to the fact that the skin uses itself, which is a good thing to show the effective result for people wanting to use it, but it costs this little problem: the most recent version is the version actually built, not what is in local repo (at least when working with SNAPSHOT) so

Re: Building Maven Fluido Skin site dies with incorrect artifact resolution

Am 2013-12-09 22:23, schrieb Robert Scholte: Have you tried to run it with an extra 'clean'? I've seen this a few times and IIRC the clean helped. No avail. Still the same error. If I leave out the profile reporting it suddenly works. Op Mon, 09 Dec 2013 20:47:20 +0100 schreef Michael-O <19

Re: Building Maven Fluido Skin site dies with incorrect artifact resolution

Have you tried to run it with an extra 'clean'? I've seen this a few times and IIRC the clean helped. Robert Op Mon, 09 Dec 2013 20:47:20 +0100 schreef Michael-O <1983-01...@gmx.net>: Hi, during release preps of 1.3.1 I am constantly failing to build the with Maven 3.1.1. I do "mvn -Prep

Building Maven Fluido Skin site dies with incorrect artifact resolution

Hi, during release preps of 1.3.1 I am constantly failing to build the with Maven 3.1.1. I do "mvn -Preporting site" and it dies with [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project maven-fluido-skin: Error during site generation:

Re: Problems building Maven from 2.2.x branch with integration tests

Dennis Lundberg wrote: So I checked out the 2.2.x branch tried to build it prior to maing any changes, by running: mvn install -Prun-its ... Tests run: 663, Failures: 6, Errors: 370, Skipped: 0 The last CI build on Hudson for the 2.2.x branch yielded only 1 failure, hard to tell what's going

Problems building Maven from 2.2.x branch with integration tests

Hi I'm looking into releasing Wagon and Brett suggested that I try the new version in a Maven build to make sure everything is building fine. So I checked out the 2.2.x branch tried to build it prior to maing any changes, by running: mvn install -Prun-its All is fine until it gets to "Building

Re: Error while building maven-2.2.x from SVN repository

gt; > (...) > [INFO] > ---- > [INFO] Building Maven Artifact > [INFO]task-segment: [install] > [INFO] > > [WARNING] Skipping jpp reposit

Error while building maven-2.2.x from SVN repository

Hi, When I try to build maven-2.2.x from SVN repository, it fails with the following error. Am I doing something wrong? (...) [INFO] [INFO] Building Maven Artifact [INFO]task-segment: [install] [INFO

Re: Building Maven 3.0 from trunk

The build use the plugin buildnumber-maven-plugin (which use native svn with cli) In order to get the svn rev when you use : mvn -v. -- Olivier 2009/10/29 Henri Gomez : >> If you have a missing SVN command, that may mean you do not have an >> SVN client installed. You should have one installed on

Re: Building Maven 3.0 from trunk

2009/10/29 Henri Gomez : >> If you have a missing SVN command, that may mean you do not have an >> SVN client installed. You should have one installed on your path so >> when you type "svn --version" (that's two dashes), you'll know what >> version you have. > > yep, I know that, svn command is ins

Re: Building Maven 3.0 from trunk

> If you have a missing SVN command, that may mean you do not have an > SVN client installed. You should have one installed on your path so > when you type "svn --version" (that's two dashes), you'll know what > version you have. yep, I know that, svn command is installed on my OS/X but not on my

Re: Building Maven 3.0 from trunk

If you have a missing SVN command, that may mean you do not have an SVN client installed. You should have one installed on your path so when you type "svn --version" (that's two dashes), you'll know what version you have. Download a binary here: http://subversion.tigris.org/ Paul On Thu, Oct 29,

Building Maven 3.0 from trunk

Hi to all, After build Maven 3 from trunk (https://svn.apache.org/repos/asf/maven/maven-3/trunk/) with ant, I tried to build it with maven 2.2.1 but the build failed about a missing svn command. - To unsubscribe, e-mail: dev-unsu

Re: Building maven 3.0.x

tp://www.mail-archive.com/[EMAIL PROTECTED]/maillist.html Thanks! -- Abel Muiño - http://www.linkedin.com/in/amuino Abel Muiño Vizcaino - http://ramblingabout.wordpress.com http://ramblingabout.wordpress.com -- View this message in context: http://www.nabble.com/Building-maven-3.0.x-tp20914299p20

Building maven 3.0.x

ext: http://www.nabble.com/Building-maven-3.0.x-tp20914299p20914299.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: problems building maven

emiddio-verizon wrote: Reason: Cannot find parent: org.apache.maven:maven-parent for project: You will need to configure Maven to use the Apache snapshot repository: http://maven.apache.org/guides/development/guide-testing-development-plugins.html : The filename or extension is too long. Y

problems building maven

re: http://maven.apache.org/guides/development/guide-building-m2.html please help me get maven to build i am using windows xp; i have maven 2.0.9 installed; i have successfully fully built apache axis2, which uses maven and mercurial. i have ant1.7.0 installed; the maven build instructions

RE: Building Maven

bject: Building Maven Hi, I'm brand new to this subject, but I was trying to build maven the bootstrap way, like described here http://maven.apache.org/guides/development/guide-building-m2.html but I always run into a: HOWEVER, since you did not specify a repository path, maven will use: /home

Building Maven

Hi, I'm brand new to this subject, but I was trying to build maven the bootstrap way, like described here http://maven.apache.org/guides/development/guide-building-m2.html but I always run into a: HOWEVER, since you did not specify a repository path, maven will use: /home/fnk64/.m2/reposito

Issue in building Maven 2.x

Hi Maven Developers: I am trying to download and build Maven code from the following svn URL (given on the Web): svn co https://svn.apache.org/repos/asf/maven/components/trunk maven-components However, I found an issue in building Maven: In building the code, I got the following message is from

RE: Question on building Maven 2.0.x

I figured it out - I went back to v 1.4 of shade. -Original Message- From: Clark, Gil W. [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 18, 2007 8:53 AM To: Maven Developers List Subject: RE: Question on building Maven 2.0.x Sorry to be naïve but is the shade work going to replace

RE: Question on building Maven 2.0.x

Sorry to be naïve but is the shade work going to replace the way the uber jar was used? Thanks -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 18, 2007 8:23 AM To: Maven Developers List Subject: Re: Question on building Maven 2.0.x On 18 Apr

Re: Question on building Maven 2.0.x

On 18 Apr 07, at 10:55 AM 18 Apr 07, Clark, Gil W. wrote: A couple weeks back I was successfully building Maven 2.0.x. The last stage of the build is to run mvn assembly:assembly in the maven-core directory. The resultant zip, gz, etc. contained the uberjar called maven-2.0.x-uber.jar

Question on building Maven 2.0.x

A couple weeks back I was successfully building Maven 2.0.x. The last stage of the build is to run mvn assembly:assembly in the maven-core directory. The resultant zip, gz, etc. contained the uberjar called maven-2.0.x-uber.jar which goes in the lib directory. Unzip it somewhere

Re: [build]Fails to get file when building maven.

Thank you. It works.:) On 11/4/06, Dan Tran <[EMAIL PROTECTED]> wrote: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.4/README.txt may help ;-) On 11/3/06, Leo Li <[EMAIL PROTECTED]> wrote: > > Hi, all > I encountered a problem when building mav

Re: [build]Fails to get file when building maven.

http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.4/README.txt may help ;-) On 11/3/06, Leo Li <[EMAIL PROTECTED]> wrote: Hi, all I encountered a problem when building maven 2.0.4. After checking out source code from http://svn.apache.org/repos/asf/maven/component

[build]Fails to get file when building maven.

Hi, all I encountered a problem when building maven 2.0.4. After checking out source code from http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.4, I use "mvn compile" to build it, but found errors when downloading files. For example, one of them is: [WARNING]

Re: Typo in Guide to Building Maven 2.0

should be fixed.. Thanks for pointing this out! -- Kenney Mike George wrote: Typo "maven-core" should be "maven-cli" Page: http://maven.apache.org/guides/development/guide-building-m2.html Section: Building Maven with Maven Installed [[ currently ]] This will build, test an

Typo in Guide to Building Maven 2.0

Typo "maven-core" should be "maven-cli" Page: http://maven.apache.org/guides/development/guide-building-m2.html Section: Building Maven with Maven Installed [[ currently ]] This will build, test and install all libraries in the local repository. Next, if you want t

Re: trouble in building maven

This question is not appropriate for the Maven Dev list and I doubt you'll receive a response. Please send it to Maven Users, or even better, directly to the Agila Users/Dev list as this is really "their" problem. Wayne On 9/27/06, charles magnes <[EMAIL PROTECTED]> wrote: Hello, Could anybody

trouble in building maven

Hello, Could anybody help me about some troubles I encountered when I tried to run: 'maven buildall' on an Ubuntu os. I received the following message: ** [EMAIL PROTECTED]:~/agila/trunk/modules/bpel$ maven buildall __ __ | \/

Re: Building Maven

Someone else has reported this... I'd need to goodle to see what bad file descriptor usualy results from. On 07/09/2006, at 3:35 AM, Jack J. Woehr wrote: On Aug 24, 2006, at 3:46 PM, Brett Porter wrote: Check your M2_HOME env var and PATH was set correctly, and that the installation dire

Re: Building Maven

On Aug 24, 2006, at 3:46 PM, Brett Porter wrote: Check your M2_HOME env var and PATH was set correctly, and that the installation directory was correctly populated. If you are on unix as you appear to be, "bash -x mvn -v" would show the exact command it tried to run and might give a clue a

Re: Now what? (Re: Trouble building Maven 2 trunk)

Mark Lundquist wrote: So, what next? How do I invoke the Maven I have just built? I tried ./maven-cli/src/bin/mvn ...and got Exception in thread "main" java.lang.NoClassDefFoundError: org/codehaus/classworlds/Launcher So I guess that wasn't the right thing to do :-) help? —ml— Most of t

Now what? (Re: Trouble building Maven 2 trunk)

So, what next? How do I invoke the Maven I have just built? I tried ./maven-cli/src/bin/mvn ...and got Exception in thread "main" java.lang.NoClassDefFoundError: org/codehaus/classworlds/Launcher So I guess that wasn't the right thing to do :-) help? —ml—

Re: Trouble building Maven 2 trunk

Dennis Lundberg wrote: Mark, I see that you are using Planet Mirror as you central repo. They recently made some changes which makes it impossible to download certain files. Please use another mirror, until their problems have been fixed. OK... I commented out the Planet Mirror section in

Re: Trouble building Maven 2 trunk

Mark, I see that you are using Planet Mirror as you central repo. They recently made some changes which makes it impossible to download certain files. Please use another mirror, until their problems have been fixed. -- Dennis Lundberg Mark Lundquist wrote: Brett Porter wrote: Sorry, I'm no

Re: Trouble building Maven 2 trunk

Brett Porter wrote: Sorry, I'm not quite sure what's happened to you here. The POM should have a parent of version 4, and that should in turn have a parent org:apache:apache, version 3. When I remove them from my local repo it successfully downloads them again. You might want to run wit

Re: Trouble building Maven 2 trunk

up w/ "svn up". Still no go. So then I changed it back to 4-SNAPSHOT and tried again with -Papache... no love there either, so I reverted back to HEAD (4). So here's what it it does now: + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level

Re: Trouble building Maven 2 trunk

ied again with -Papache... no love there either, so I reverted back to HEAD (4). So here's what it it does now: + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/Users/ml/.m2/plugin-registry.xml' [DEBUG] Building Maven glob

Re: Trouble building Maven 2 trunk

gs.xml out of the way, so it should be defaults for everything... any ideas? Am I doing something wrong? thx, Mark -- + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/Users/ ml/.m2/plugin-registry.xml' [DEBUG] Bu

Re: Trouble building Maven 2 trunk

g... any ideas? Am I doing something wrong? thx, Mark -- + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/Users/ml/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/usr/local/

Trouble building Maven 2 trunk

urned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/Users/ml/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/usr/local/maven-2.0.4/conf/plugin-registry.xml' [INFO] Scanning for projects.

Re: Building Maven

On Aug 24, 2006, at 3:46 PM, Brett Porter wrote: Check your M2_HOME env var and PATH was set correctly, and that the installation directory was correctly populated. If you are on unix as you appear to be, "bash -x mvn -v" would show the exact command it tried to run and might give a clue a

Re: Building Maven

html At the end, I find a "mvn" executable, so I return to the top of the source tree and try the "building Maven when you already have Maven installed" proceedure and I get: $ mvn install Exception in thread "main" java.lang.NoClassDefFoundError: org/ codeha

Building Maven

ot; executable, so I return to the top of the source tree and try the "building Maven when you already have Maven installed" proceedure and I get: $ mvn install Exception in thread "main" java.lang.NoClassDefFoundError: org/ codehaus/classworlds/Launcher --- Jack J

Re: building maven with maven

it means from the components root On 12/08/2006 10:07 PM, berndq wrote: Hi, looking at http://maven.apache.org/guides/development/guide-building-m2.html ist says you can svn co https://svn.apache.org/repos/asf/maven/trunks maven and then mvn install from root, but there is no pom in ro

building maven with maven

Hi, looking at http://maven.apache.org/guides/development/guide-building-m2.html ist says you can svn co https://svn.apache.org/repos/asf/maven/trunks maven and then mvn install from root, but there is no pom in root? Is there some information missing? thanks Bernd

[jira] Updated: (MNG-1297) Continuum build throws LifecycleExecutionException while building Maven PLUGIN Plugin

[ http://jira.codehaus.org/browse/MNG-1297?page=all ] Jason van Zyl updated MNG-1297: --- Fix Version: (was: 2.0.3) 2.0.4 > Continuum build throws LifecycleExecutionException while building Maven > PLUGIN

[jira] Updated: (MNG-1297) Continuum build throws LifecycleExecutionException while building Maven PLUGIN Plugin

[ http://jira.codehaus.org/browse/MNG-1297?page=all ] John Casey updated MNG-1297: Fix Version: (was: 2.0.1) 2.0.2 > Continuum build throws LifecycleExecutionException while building Maven > PLUGIN

[jira] Closed: (MPSIMIAN-13) Building MAven throuigh bootstrapping fails

[ http://jira.codehaus.org/browse/MPSIMIAN-13?page=all ] Arnaud Heritier closed MPSIMIAN-13: --- No more error with 1.1 beta 3 > Building MAven throuigh bootstrapping fails > --- > > Key:

[jira] Updated: (MNG-1297) Continuum build throws LifecycleExecutionException while building Maven PLUGIN Plugin

time which succeeds. IT is a bug that only affects building of the plugin-plugin (because it is using itself). > Continuum build throws LifecycleExecutionException while building Maven > PL

[jira] Created: (MNG-1297) Continuum build throws LifecycleExecutionException while building Maven PLUGIN Plugin

Continuum build throws LifecycleExecutionException while building Maven PLUGIN Plugin -- Key: MNG-1297 URL: http://jira.codehaus.org/browse/MNG-1297 Project: Maven 2 Type: Bug

[jira] Resolved: (MPSIMIAN-13) Building MAven throuigh bootstrapping fails

[ http://jira.codehaus.org/browse/MPSIMIAN-13?page=all ] David Eric Pugh resolved MPSIMIAN-13: - Assign To: David Eric Pugh Resolution: Incomplete Please reopen this bug if things fail with Maven 1.1 beta 2. > Building MAven throu

[jira] Closed: (MNG-537) building maven 2.0 webpage is not clear

[ http://jira.codehaus.org/browse/MNG-537?page=all ] Emmanuel Venisse closed MNG-537: Resolution: Fixed Applied. Thanks. > building maven 2.0 webpage is not clear > --- > > Key: MNG-537 &g

[jira] Updated: (MNG-537) building maven 2.0 webpage is not clear

\t" + dist ); System.err.println(); System.err.println( "If you really mean to install Maven to this location, please delete the directory first" ); System.exit( 1 ); } } See attachment: patch

[jira] Commented: (MNG-537) building maven 2.0 webpage is not clear

strap? - M2_HOME directory doens't exist - M2_HOME directory contains an valid installation of m2 (ie %M2_HOME%\bin\m2.bat exist) Can you provide a patch for point 4? > building maven 2.0 webpage is not clear > --- > > Key: MNG-53

[jira] Updated: (MNG-537) building maven 2.0 webpage is not clear

[ http://jira.codehaus.org/browse/MNG-537?page=all ] Loïc Lefèvre updated MNG-537: - Attachment: MNG-537.txt Patch for points 1, 2 and 3. > building maven 2.0 webpage is not clear > --- > >

[jira] Created: (MNG-537) building maven 2.0 webpage is not clear

building maven 2.0 webpage is not clear --- Key: MNG-537 URL: http://jira.codehaus.org/browse/MNG-537 Project: Maven 2 Type: Improvement Components: documentation Versions: 2.0-alpha-3 Reporter: Loïc Lefèvre

About the Building Maven 2.0 webpage

d-part-for-a-maven2-dummy-like-me! -8<---- "... Building Maven Once you have checked out the code, change into the maven-components directory that was created. You may want to setup a different environment to install Maven to other than your normal installation of

Re: Building maven-scm-1.5-branch

I'll reply on scm-dev. Please, don't crosspost. Thanks, Brett On Wed, 5 Jan 2005 13:44:04 -0500, Poppe, Troy <[EMAIL PROTECTED]> wrote: > > I'm trying to get started on a VSS provider for Maven SCM, but I'm having some > trouble getting some of the base project stuff to compile. And I'm terribl

Building maven-scm-1.5-branch

I'm trying to get started on a VSS provider for Maven SCM, but I'm having some trouble getting some of the base project stuff to compile. And I'm terribly lost at this point. Specifically when I try to execute any goal in maven-scm-1.5-branch, it's failing to resolve three dependencies: Attem

[jira] Updated: (MAVEN-1488) Building MAven throuigh bootstrapping fails

: - Key: MAVEN-1488 Summary: Building MAven throuigh bootstrapping fails Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components

[jira] Updated: (MAVEN-1488) Building MAven throuigh bootstrapping fails

: - Key: MAVEN-1488 Summary: Building MAven throuigh bootstrapping fails Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: installer Fix Fors: 1.1

[jira] Commented: (MAVEN-1488) Building MAven throuigh bootstrapping fails

: - Key: MAVEN-1488 Summary: Building MAven throuigh bootstrapping fails Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project

[jira] Commented: (MAVEN-1488) Building MAven throuigh bootstrapping fails

the issue: - Key: MAVEN-1488 Summary: Building MAven throuigh bootstrapping fails Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown

[jira] Created: (MAVEN-1488) Building MAven throuigh bootstrapping fails

: MAVEN-1488 Summary: Building MAven throuigh bootstrapping fails Type: Bug Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven Components: installer Versions: 1.1

[jira] Closed: (MAVEN-1355) Add instructions on building maven with maven

! - View the issue: http://jira.codehaus.org/browse/MAVEN-1355 Here is an overview of the issue: - Key: MAVEN-1355 Summary: Add instructions on building maven with maven Type: Improvement Status: Closed

[jira] Updated: (MAVEN-1355) Add instructions on building maven with maven

: - Key: MAVEN-1355 Summary: Add instructions on building maven with maven Type: Improvement Status: Unassigned Priority: Major Original Estimate: 10 minutes Time Spent: Unknown Remaining: 10 minutes Project: maven Components: documentation Fix Fors

[jira] Updated: (MAVEN-1355) Add instructions on building maven with maven

: - Key: MAVEN-1355 Summary: Add instructions on building maven with maven Type: Improvement Status: Unassigned Priority: Major Original Estimate: 10 minutes Time Spent: Unknown Remaining: 10 minutes Project: maven Components: documentation

[jira] Created: (MAVEN-1355) Add instructions on building maven with maven

: MAVEN-1355 Summary: Add instructions on building maven with maven Type: Improvement Status: Unassigned Priority: Major Original Estimate: 10 minutes Time Spent: Unknown Remaining: 10 minutes Project: maven Components: documentation Assignee

Re: Why not a building maven with maven doc?

On Fri, 2004-06-18 at 14:10, Miguel Griffa wrote: > Jerome Lacoste wrote: > > >On Thu, 2004-06-17 at 20:51, Miguel Griffa wrote: > > > > > >>Is there any reson (besides resources to write it) that there's no info > >>on building maven with maven?

Re: Why not a building maven with maven doc?

Jerome Lacoste wrote: On Thu, 2004-06-17 at 20:51, Miguel Griffa wrote: Is there any reson (besides resources to write it) that there's no info on building maven with maven? you need to have a working version of maven to build maven. What I don't get is: what's wrong wit

Re: Why not a building maven with maven doc?

On Thu, 2004-06-17 at 20:51, Miguel Griffa wrote: > Is there any reson (besides resources to write it) that there's no info > on building maven with maven? you need to have a working version of maven to build maven. Hence the bootstrap mecanism. Indeed maven is built with maven, b

Why not a building maven with maven doc?

Is there any reson (besides resources to write it) that there's no info on building maven with maven? I find it an interesting paradox that all the info on building maven points to ant... Is it because latest releases cannot build maven? I've updating maven CVS from some time, and

Re: Building Maven from 1.0 branch fails...

ssing a dependency in the linkcheck project. I'll try adding it to see if it works. -Vincent -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: 13 June 2004 13:01 To: 'Maven Developers List' Cc: 'Brett Porter' Subject: Building Maven from 1.

RE: Building Maven from 1.0 branch fails...

t; From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: 13 June 2004 13:01 > To: 'Maven Developers List' > Cc: 'Brett Porter' > Subject: Building Maven from 1.0 branch fails... > > I think it's due to the change brought recently by Brett with the jar >

RE: Building Maven from 1.0 branch fails...

List' > Cc : 'Brett Porter' > Objet : Building Maven from 1.0 branch fails... > > I think it's due to the change brought recently by Brett with the jar > override for maven.jar. That would work *only* if you already have a > maven installed. > > Thus when y

  1   2   >