Henning P. Schmiedehausen wrote:
>What would be needed to cut an RC? I've seen that you've cut bundles
>for an 1.1-rc. Is there a specific script / maven goal to collect all
>the plugins for a release and cut these bundles?
>
>
maven maven:build-plugin-profile (rewrites plugin-profile.xml with
l
Brett Porter <[EMAIL PROTECTED]> writes:
>The main blocker I'd see to this is the SCM plugin not being backwards
>compatible with 1.4 (which needs to be fixed anyway).
What would be needed to cut an RC? I've seen that you've cut bundles
for an 1.1-rc. Is there a specific script / maven goal to co
Vincent Massol wrote:
>The problem is that several new versions of plugins rely on Maven 1.1's core
>so I don't think it would work. We don't really have a mechanism set up to
>ensure m1 plugins continue to work with all versions.
>
>
erm, you sure? What were you thinking of specifically?
To my
We could upgrade only some plugins but it may be easier to do it if we have a
continous integration to test them with m1.0/m1.1 and
jdk 1.3/1.4/1.5.
The problem is that there aren't tests for all of them :-(
Arnaud
> >
> > It all depends on when 1.1 is expected to become final. And how
> > l
> -Original Message-
> From: Martijn Dashorst [mailto:[EMAIL PROTECTED]
> Sent: jeudi 8 septembre 2005 10:29
> To: Maven Developers List
> Subject: Re: Maven 1.0 branch
>
> It all depends on when 1.1 is expected to become final. And how long/much
> effort i
ite slow on minor
> revisions it would not be picked up before 1.1 was out anyway.
>
> I'm interested to hear what others think.
>
> - Brett
>
> Henning P. Schmiedehausen wrote:
>
> >Hi,
> >
> >due to some questions related to plugin changes on an
ed to hear what others think.
- Brett
Henning P. Schmiedehausen wrote:
>Hi,
>
>due to some questions related to plugin changes on another mailing
>list, I wondered what changes have been done to the maven-1.0 branch
>(http://svn.apache.org/repos/asf/maven/maven-1/core/branches/MAV
Hi,
due to some questions related to plugin changes on another mailing
list, I wondered what changes have been done to the maven-1.0 branch
(http://svn.apache.org/repos/asf/maven/maven-1/core/branches/MAVEN-1_0-BRANCH)
post the maven-1.0.2 release
(http://svn.apache.org/repos/asf/maven/maven-1
Here is an overview of the issue:
-
Key: MAVEN-1347
Summary: 1.0 Branch issues message about missing deploy plugin
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: Unknown
Brett Porter wrote on Friday, September 17, 2004 9:29 AM:
> It has worked for me very recently - are you sure your
> plugins checkout is untainted? Try a clean checkout? Anything
> dodgy in ~/.maven/cache?
Clean checkout did the trick. Sorry for bothering ...
- Jörg
It has worked for me very recently - are you sure your plugins checkout is
untainted? Try a clean checkout? Anything dodgy in ~/.maven/cache?
- Brett
Quoting Jörg Schaible <[EMAIL PROTECTED]>:
> Hi folks,
>
> it seems that currently it is not possible to bootstrap the 1.
Hi folks,
it seems that currently it is not possible to bootstrap the 1.0 branch. After builing
the plugins, the process fails:
=== %< ===
[echo] |
[echo] | BUILDING MAVEN WITH ITSELF...
[echo] |
[echo]
[exec] __ __
[exec] | \/ |__ _Apach
:
-
Key: MAVEN-1347
Summary: 1.0 Branch issues message about missing deploy plugin
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.0.1
Assignee:
Reporter
Fixed in CVS. and now load the plugin if necessary.
I'll add a test on the way in for :set and then post some more info - looks like
we can ditch those stupid dependency handles though.
The fix is something like the last straw the PluginManager camel's back can
take, but it's still holding :)
P
Bizarre... I'll take a look tonight.
Quoting Dion Gillard <[EMAIL PROTECTED]>:
> On Mon, 5 Jul 2004 14:54:38 +1000, Dion Gillard <[EMAIL PROTECTED]>
> wrote:
> > I'll try adding a prereq of dist:build-setup
>
> Same sort of failure:
>
> Tag library requested that is not present: 'dist' in plugi
On Mon, 5 Jul 2004 14:54:38 +1000, Dion Gillard <[EMAIL PROTECTED]> wrote:
> I'll try adding a prereq of dist:build-setup
Same sort of failure:
Tag library requested that is not present: 'dist' in plugin:
'maven-nsis-plugin-1.1-SNAPSHOT'
INTERNAL ERROR
Reference made to goal 'dist:build-setup' wh
On Mon, 5 Jul 2004 11:18:26 +1000, Brett Porter <[EMAIL PROTECTED]> wrote:
> Quoting Dion Gillard <[EMAIL PROTECTED]>:
>
> > I'm having problems with maven:get in the latest builds of the 1.0 branch.
> >
> > In the NSIS plugin I have this:
> >
Quoting Dion Gillard <[EMAIL PROTECTED]>:
> Given Jason's comments last week, I'm trying not to put preGoals in plugins.
Yep, that's a good thing. I probably meant prereq though - if there is a goal
(like the :init stuff) you can prereq on that'll work (eg war:load was used for
this), but the tag
On Mon, 5 Jul 2004 11:18:26 +1000, Brett Porter <[EMAIL PROTECTED]> wrote:
> Quoting Dion Gillard <[EMAIL PROTECTED]>:
>
> This stuff has always been flaky. It depends on the plugin already being loaded.
> The "documented" fashion of doing so is a taglib dependency handle (see
> eclipse's use of
Quoting Dion Gillard <[EMAIL PROTECTED]>:
> I'm having problems with maven:get in the latest builds of the 1.0 branch.
>
> In the NSIS plugin I have this:
>
> plugin="maven-dist-plugin" property="maven.dist.bin.assembly.dir"/>
>
> And
I'm having problems with maven:get in the latest builds of the 1.0 branch.
In the NSIS plugin I have this:
And it comes back blank.
Thinking it was the variable, I tried:
Still no luck.
Also, running maven dist by itself works ok, but putting it as a
pre-req for a plugin goal
: MAVEN-1347
Summary: 1.0 Branch issues message about missing deploy plugin
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Assignee:
Reporter: dion gillard
Created: Tue, 29 Jun
>
> > I didn't found when you committed this change.
>
> dIon beat me to it - I only just got home.
Sorry,
I talked about the first time when you committed the bug. ;-)
I try to follow the CVS mails ;-)
>
> > Why need we to produce a RC4 ?
>
> Because the artifact and httputils code changed
> I didn't found when you committed this change.
dIon beat me to it - I only just got home.
> Why need we to produce a RC4 ?
Because the artifact and httputils code changed significantly - there's a risk
of problems. There are also still bugs in javadoc, and multiproject.
Cheers,
Brett
---
n 2004 01:08
> À : Maven Developers List
> Objet : Re: [Maven 1.0 branch] Problem with the bootstrap
>
>
> That was awful dumb of me :)
>
> I'll fix this up tonight when I cut the release for RC4.
>
> Cheers,
> Brett
>
> Quoting Arnaud HERITIER <[EMAIL PROTECTE
Done. Thanks.
On Sun, 27 Jun 2004 23:40:55 +0200, Arnaud HERITIER
<[EMAIL PROTECTED]> wrote:
>
> Hello guys,
>
> I'm coming back after two weeks of inactivity and I can't build maven with
> the bootstrap.
> The problem comes from the build-bootstrap ant file.
>
> The ge
That was awful dumb of me :)
I'll fix this up tonight when I cut the release for RC4.
Cheers,
Brett
Quoting Arnaud HERITIER <[EMAIL PROTECTED]>:
> Hello guys,
>
> I'm coming back after two weeks of inactivity and I can't build maven with
> the bootstrap.
> The problem comes from th
Hello guys,
I'm coming back after two weeks of inactivity and I can't build maven with the
bootstrap.
The problem comes from the build-bootstrap ant file.
The get commands used to retrieve commons-logging and http-client jars use
${maven.get.jars.baseUrl} as source.
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.
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
>
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
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 you build Maven (ant -f build-bootstrap.xml) it fails in the
linkcheck plugin:
Testsuite: org.apache.maven.linkcheck.LinkCheckTest
the issue:
-
Key: MAVEN-1257
Summary: Specify in site documentation that HEAD does not compile now and 1.0
branch should be used
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Original
:
-
Key: MAVEN-1257
Summary: Specify in site documentation that HEAD does not compile now and 1.0
branch should be used
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: 15 minutes
Time Spent: Unknown
Remaining: 15 minutes
Project: maven
The following issue has been updated:
Updater: Miguel Griffa (mailto:[EMAIL PROTECTED])
Date: Mon, 3 May 2004 6:10 PM
Comment:
A patch that adds info about current compilation state in HEAD and 1.0 branch in
building instructions
Changes:
Attachment changed to
Have fixed, will commit soon. I don't know how this came about...
> -Original Message-
> From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 15 April 2004 8:52 PM
> To: Maven Developers List
> Subject: 1.0 branch fails to bootstrap
>
>
> Hi,
Hi, for the past few days I was unable to bootstrap 1.0 branch.
Here's the mysterious-looking exception message.
If this does not help, I may try bootstraping off fresh checkout & empty
local repository
[echo] |
[echo] | INSTALLING THE PLUGINS...
[echo] |
[echo]
overview of the issue:
-
Key: MPCHECKSTYLE-19
Summary: plugin:test fails under 1.0 branch
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
:
-
Key: MPCHECKSTYLE-19
Summary: plugin:test fails under 1.0 branch
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-checkstyle-plugin
Fix Fors:
2.3
Versions
On Mon, 2004-02-16 at 18:20, Jason van Zyl wrote:
> Yo,
>
> Anyone else getting this:
>
> [exec] BUILD FAILED
> [exec] com.werken.werkz.UnattainableGoalException: Unable to obtain
> goal [plugin] --
> file:/home/jvanzyl/maven/plugins/java/plugin.jelly:36:48:
> srcdir attribute must be
Hmmm. That's different :)
No, I don't get that from a clean checkout. Did something screw up earlier
in the bootstrap?
- Brett
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 17 February 2004 10:20 AM
> To: Maven Develope
Yo,
Anyone else getting this:
[exec] BUILD FAILED
[exec] com.werken.werkz.UnattainableGoalException: Unable to obtain
goal [plugin] --
file:/home/jvanzyl/maven/plugins/java/plugin.jelly:36:48:
srcdir attribute must be set!
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://maven.apache.
per which
is the little automated upload tool that's in the works.
> Cheers,
> Brett
>
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, 11 February 2004 3:58 PM
> > To: Maven Developers List
> > Subject:
Ok, let me roll in my last set of changes and we'll get to it by the end of
the week.
Cheers,
Brett
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 11 February 2004 3:58 PM
> To: Maven Developers List
> Subject: RE: HEAD and 1
On Tue, 2004-02-10 at 17:00, Brett Porter wrote:
> Yeah, I missed something the other day, and haven't had a spare second to
> fix it.
>
> In this version the parser isn't used, nor are the marshaller/unmarshaller,
> so they can just be removed from your local copy.
>
> I've actually mostly repai
fast
under all situations as RC1, then I'm ready to cut a release (any plugins
left to do?)
- Brett
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 11 February 2004 5:35 AM
> To: Maven Developers List
> Subject: HEAD and 1.0 Branch
&
Brett,
You midstream on some stuff? I can't compile either HEAD or the 1.0, I
won't wander in if you're doing stuff.
1.0 branch:
symbol : constructor PluginScriptParser
(org.apache.maven.plugin.PluginCacheManager,java.lang.String)
[javac]
OK, it seems that jar are deleted on ibiblio. I don't know why.
I upload it now.
Emmanuel
- Original Message -
From: "Jörg Schaible" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Thursday, January 22, 2004 2:59 PM
Subject
Emmanuel Venisse wrote on Thursday, January 22, 2004 2:34 PM:
> I build all days Maven 1.0 branch, and it build correctly. I
> think you have a problem with your checkout. You can do a
> fresh checkout of maven branch and plugin.
If you have a local copy somewhere of the missing bati
le [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 22 janvier 2004 13:42
À : Maven Developers List
Objet : RE: 1.0-branch fails because of pdf-plugin
Heritier Arnaud wrote on Thursday, January 22, 2004 12:42 PM:
> Hello,
>
> I participated for several days to the development of the new
> rel
I build all days Maven 1.0 branch, and it build correctly. I think you have
a problem with your checkout. You can do a fresh checkout of maven branch
and plugin.
Emmanuel
- Original Message -
From: "Jörg Schaible" <[EMAIL PROTECTED]>
To: "Maven Developers List"
lmost complete) in
>> the HEAD branch. Can you send me the logs. I will try to download the
>> 1.0 branch to test it.
>>
>> Arnaud
>
> Well, the plugin is HEAD ... just Maven is 1.0-BRANCH.
>
> Logs later.
Hi,
coming back with logs, but it seems that it mis
o download the 1.0 branch to test it.
>
> Arnaud
Well, the plugin is HEAD ... just Maven is 1.0-BRANCH.
Logs later.
Regards,
Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hello,
I participated for several days to the development of the new release of the PDF
plugin.
The new PDF plugin is ok (and almost complete) in the HEAD branch.
Can you send me the logs.
I will try to download the 1.0 branch to test it.
Arnaud
-Message d'origine-
De :
Hello Emmanuel,
I realize that there have been some changes to the pdf-plugin lately, but I wanna just
report as heads-up that you cannot build the 1.0-branch since two days, because of
exceptions building this plugin. Are those changes now supposed to be complete (and I
should create a JIRA
Brett Porter wrote on Tuesday, January 13, 2004 10:54 PM:
> If it's not in JIRA, then it won't get fixed. Please add both
> issues, and run with maven -e so the full stack trace appears.
Done. Next time I'll read your mail more carefully [maven -e]
;-)
Cheers,
Jörg
What's the actual exception from maven -e?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jörg Schaible <[EMAIL PROTECTED]> wrote on 14/01/2004
02:51:13 AM:
> Hi gang,
>
> there seem to be more issues with the Maven-1.0 bran
Maven Developers List
> Subject: plugin:download fails also with 1.0-branch
>
>
> Hi gang,
>
> there seem to be more issues with the Maven-1.0 branch:
>
> == snip =
>
> $ maven plugin:download -DgroupId=xdoclet
> -DartifactId=maven-xdoc
Hi gang,
there seem to be more issues with the Maven-1.0 branch:
== snip =
$ maven plugin:download -DgroupId=xdoclet -DartifactId=maven-xdoclet-plugin
-Dversion=1.2
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||
Hello,
currently site gneration fails for Maven 1.0 branch using the tasklist-report-plugin:
snip ===
maven-tasklist-plugin:report:
[echo] Generating tasklist ...
BUILD FAILED
java.lang.IncompatibleClassChangeError
Total time: 22 seconds
Finished at: Tue Jan 13 16:24:26 CET
Brett Porter wrote on Tuesday, December 16, 2003 10:57 PM:
>> The log shows that Maven retrieved the TableLayout without any
>> problems
> from ibiblio, but continues with an attempt to download the
> same file from the
>> local repository. I do not think this is intended.
>
> This is an existing
> The log shows that Maven retrieved the TableLayout without any problems
from ibiblio, but continues with an attempt to download the same file from
the
> local repository. I do not think this is intended.
This is an existing bug, not one introduced on the branch - you'll find it
in JIRA. Patches
> although it is possible now to build Maven in the 1.0 branch,
> I have proplems with this version. As reported before, Maven
> still claims beeing offline and reports warnings, but is also
> not able to retrieve the SNAPSHOT artifacts (tested with Jelly-SOAP):
Fixed, not commi
Jörg Schaible wrote on Tuesday, December 16, 2003 11:07 AM:
> although it is possible now to build Maven in the 1.0 branch,
> I have proplems with this version. As reported before, Maven
> still claims beeing offline and reports warnings, but is also
> not able to retrieve the SNAPSH
Hi Brett,
Brett Porter wrote on Friday, December 12, 2003 12:36 AM:
> These are all warnings. I will clean them up by RC2.
although it is possible now to build Maven in the 1.0 branch, I have proplems with
this version. As reported before, Maven still claims beeing offline and reports
warni
In the maven's 1.0 CVS branch, maven.mode.online is missing from both
the defaults.properties and the driver.properties...this leads to the
eventuality that one cannot build maven onto a clean filesystem without
creating a ~/build.properties containing maven.mode.online=true.
Is this the correct s
These are all warnings. I will clean them up by RC2.
- Brett
> -Original Message-
> From: Jörg Schaible [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 11 December 2003 7:24 PM
> To: Maven Developers List
> Subject: RE: Bootstrapping 1.0-branch
>
>
> Hi Brett,
&g
oks much better today. I've build the 1.0-branch quite successfull. The only
remaining issue are the tag libs, that cannot be found during the build:
= snip =
[exec] Tag library requested that is not present: 'deploy'
[exec] Tag library requested that is
s/file/fine/
:)
> -Original Message-
> From: Brett Porter
> Sent: Thursday, 11 December 2003 11:44 AM
> To: 'Maven Developers List'
> Subject: RE: Bootstrapping 1.0-branch
>
>
> I just bootrapped a clean build after committing some fixes
> an
Brett
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 11 December 2003 11:48 AM
> To: Maven Developers List
> Subject: RE: Bootstrapping 1.0-branch
>
>
> Not yet, as it is a bigger problem that I first thought. :-(
>
> I'm h
Not yet, as it is a bigger problem that I first thought. :-(
I'm hoping to get it resolved soon, but don't hold your breath today.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jörg Schaible <[EMAIL PROTECTED]> wrote on 10/12/2003
11:31:30 PM:
> [EMAI
I noticed this too - I think its fixed. More to follow.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 10 December 2003 11:04 PM
> To: Maven Developers List
> Subject: RE: Bootstrapping 1.0-branch
>
>
> It now breaks
[EMAIL PROTECTED] wrote on Wednesday, December 10, 2003 1:04 PM:
> This is caused by an empty maven.xml file.
>
> Not sure why, but I'm removing the offending file now.
Did you commit the deletion into the branch? CVS did not report any change.
Regards,
Jörg
It now breaks on a valid maven.xml in the faq plugin :-(
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jörg Schaible <[EMAIL PROTECTED]> wrote on 10/12/2003
07:36:26 PM:
> Hi,
>
> repeated the task below right now, but it is getting worse with today's
This is caused by an empty maven.xml file.
Not sure why, but I'm removing the offending file now.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jörg Schaible <[EMAIL PROTECTED]> wrote on 10/12/2003
07:36:26 PM:
> Hi,
>
> repeated the task below right
Hi,
repeated the task below right now, but it is getting worse with today's version in
CVS, since building the plugins during bootstrap failes in ashkelon. It seems one of
the changes yesterday from Brett or dIon has side-effects.
Regards,
Jörg
Jörg Schaible wrote on Monday, December 08, 2003
[EMAIL PROTECTED] wrote on Monday, December 08, 2003 3:59 PM:
> Did you exclude checkstyle, as Brett suggested previously?
Yes, but no difference. Results are the same as reported.
>> [EMAIL PROTECTED] wrote on Monday, December 08, 2003 2:29 PM:
>>> In the 1.0 branch, th
Did you exclude checkstyle, as Brett suggested previously?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jörg Schaible <[EMAIL PROTECTED]> wrote on 09/12/2003
12:53:01 AM:
> [EMAIL PROTECTED] wrote on Monday, December 08, 2003 2:29 PM:
>
otstrap doesn't use
this
> functionality?
>
> Emmanuel
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: "Maven Developers List" <[EMAIL PROTECTED]>
> Sent: Monday, December 08, 2003 2:29 PM
> Subject: Re: Bootstrapping 1.0-
ll do not have a working Maven from CVS in the 1.0-branch.
Regards,
Jörg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
onday, December 08, 2003 3:04 PM
Subject: Re: Bootstrapping 1.0-branch
> try this for obtain an online bootstrap :
> %ANT_HOME%\bin\ant -Dmaven.bootstrap.online= -f build-bootstrap.xml
>
> Emmanuel
>
> - Original Message -
> From: "Jörg Schaible" <[EMAIL PR
Original Message -
> From: "Jörg Schaible" <[EMAIL PROTECTED]>
> To: "Maven Developers List" <[EMAIL PROTECTED]>
> Sent: Monday, December 08, 2003 2:53 PM
> Subject: RE: Bootstrapping 1.0-branch
>
>
> [EMAIL PROTECTED] wrote on Monday, Decembe
ber 08, 2003 2:53 PM
Subject: RE: Bootstrapping 1.0-branch
[EMAIL PROTECTED] wrote on Monday, December 08, 2003 2:29 PM:
> In the 1.0 branch, the bootstrap is run offline.
>
> All necessary jars must be downloaded before running bootstrap.
Well, since I did not had any clue, what jars are
[EMAIL PROTECTED] wrote on Monday, December 08, 2003 2:29 PM:
> In the 1.0 branch, the bootstrap is run offline.
>
> All necessary jars must be downloaded before running bootstrap.
Well, since I did not had any clue, what jars are really needed, I bootstrapped once
being online. While
ctionality?
Emmanuel
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Monday, December 08, 2003 2:29 PM
Subject: Re: Bootstrapping 1.0-branch
In the 1.0 branch, the bootstrap is run offline.
All necessary jars m
In the 1.0 branch, the bootstrap is run offline.
All necessary jars must be downloaded before running bootstrap.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jörg Schaible <[EMAIL PROTECTED]> wrote on 08/12/2003
11:33:56 PM:
&
. Reinstall a appserver instance
restart Restart a appserver instance
start .. Start a appserver instance
stop ... Stop a appserver instance
[artifact] ( NO DEFAULT G
Brett Porter wrote:
I hadn't seen that bootstrapping recently, but it starts working again if
checkstyle is removed. That is one of the notes in the .txt file.
That leaves the current list of plugins not working at all at simian and
checkstyle.
I'm pretty clueless about this one myself. Time to dig
g into the
classloaders.
- Brett
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Monday, 8 December 2003 2:02 AM
> To: [EMAIL PROTECTED]
> Subject: [1.0 branch] current status
>
>
> I've gotten 1.0 to load plugins, and end up
I've gotten 1.0 to load plugins, and end up with an
IncompatibleClassChangeError whenever driver.jelly is loaded.
e.g.:
C:\source\maven>maven -e site
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-rc2-SNAPSHOT
You are work
90 matches
Mail list logo
