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
>
> > 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.
14 matches
Mail list logo
