+1
On 8 Jan 07, at 4:29 PM 8 Jan 07, Stephane Nicoll wrote:
Hi,
I'd like to release the ear plugin which contains a backward
compatibility issue in 2.3 [1]. The issue has been fixed and the
reporter has validated his builds successfully.
Revision 492264
Snapshot available
http://people.apach
On 11 Jan 07, at 12:37 AM 11 Jan 07, Ralph Goers wrote:
Well, if you absolutely positively promise to release 2.0.6 when
MNG-1577 is applied ;-) . Seriously, it has been rather
frustrating as I can't even use Maven 2 without that fix.
I'm sure if you and Mike work together then I can hel
Well, if you absolutely positively promise to release 2.0.6 when
MNG-1577 is applied ;-) . Seriously, it has been rather frustrating as
I can't even use Maven 2 without that fix.
Ralph
Jason van Zyl wrote:
Hi,
I want to call a vote for 2.0.5. All the issues that are going to get
done are d
Can we put the webapp stuff that's currently in the site plugin in
another plugin so that when you simply want to generate your site you
don't drag down Jetty and all its dependencies? It really is
something unexpected and isn't something most would associate with
just generating a site. Th
On 10 Jan 07, at 10:41 PM 10 Jan 07, Brett Porter wrote:
If the artifact was created with an artifact factory, isn't there
already a getHandler() method on the artifact itself?
In what there is currently yes, but I'm not going to using it because
the artifact is data and should not carry
If the artifact was created with an artifact factory, isn't there
already a getHandler() method on the artifact itself?
On 11/01/2007, at 2:39 PM, [EMAIL PROTECTED] wrote:
Author: jvanzyl
Date: Wed Jan 10 19:39:22 2007
New Revision: 495101
URL: http://svn.apache.org/viewvc?view=rev&rev=49510
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (29 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-1317SweetXML 0.2 bundles ready for repository
http://jira.codehaus.org/browse/MAVENUPLOAD-1317
MAVENUPLOAD-1316upload vraptor 2.3.1
h
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (40 issues)
Subscriber: mavendevlist
Key Summary
MEV-479 Invalid POI POM
http://jira.codehaus.org/browse/MEV-479
MEV-483 Still invalid deps in 3.2.1, 3.2.2, 3.2.3, 3.2.4
http://jira.c
im looking into it, but i cant seen to install the modules locally -
im getting a weird random access denied error...
On 1/10/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
Yes. A global patch would be better instead of separate patches.
I tried your 2 patches and updated locally jpox-* to 1.1
Forwarding to dev list
-- Forwarded message --
From: Ben Alex <[EMAIL PROTECTED]>
Date: Jan 10, 2007 1:28 PM
Subject: Changing property during execution of particular mojo
To: [EMAIL PROTECTED]
Cc: Stewart Alan <[EMAIL PROTECTED]>
Hi Carlos
Just related to MCOMPILER-48, the plu
Yes, I have a script to automate installing the latest build (though
would need changes if continuum_ci was turned off).
1.1 is running very well thanks to some sleuthing by Wendy and quick
fixes from Emmanuel.
My biggest concern is the scalability of polling. It currently takes
about 30
On 10 Jan 07, at 6:07 PM 10 Jan 07, Brian E. Fox wrote:
Sounds like a plan to me. To clarify, are you targeting all maven core
only releases for this machine, or all maven related releases (ie
plugins, shared etc)? I think it makes sense to consolidate as many as
possible to the same machine, i
good luck ;-)
did you update the 2.1 snapshot ?
Arnaud
On 1/11/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Folks,
I'd like to turn off continuum_ci.sh and instead only use Continuum
itself to do CI for Continuum. Any objections?
- Brett
Sounds like a plan to me. To clarify, are you targeting all maven core
only releases for this machine, or all maven related releases (ie
plugins, shared etc)? I think it makes sense to consolidate as many as
possible to the same machine, it's how we operate our corporate builds
anyway. It will have
Folks,
I'd like to turn off continuum_ci.sh and instead only use Continuum
itself to do CI for Continuum. Any objections?
- Brett
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
Agreed to the plan - thanks for getting this moving.
(Presuming this is not an actual vote though)
- Brett
On 11/01/2007, at 9:20 AM, Jason van Zyl wrote:
Hi,
I want to call a vote for 2.0.5. All the issues that are going to
get done are done. We'll release and move on.
I would like to s
I haven't called the vote yet, just wanted to settle on picking a
machine to dispatch it from.
It's coming, it's coming :-)
jason.
On 10 Jan 07, at 5:20 PM 10 Jan 07, Jason van Zyl wrote:
Hi,
I want to call a vote for 2.0.5. All the issues that are going to
get done are done. We'll rele
On 09/01/2007, at 11:18 PM, Vincent Siveton wrote:
Hi,
In the same way of Brett's thread [1], WDYT to move all
/maven/*/*-site to /maven/site/*?
I've considered this before, but I agree with Trygve that we don't
want this in particular. The problem is that when you want to do
something wi
+1
I'm all for more frequent releases. I believe the 2.0.5 snapshot
works ok with our build. Ship it!
On 1/10/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
I want to call a vote for 2.0.5. All the issues that are going to get
done are done. We'll release and move on.
I would like to star
Hi,
I want to call a vote for 2.0.5. All the issues that are going to get
done are done. We'll release and move on.
I would like to start building all releases from a standard machine
with the same JDK. I would like to propose the maven.org machine
which is monitored 24/7 running Linux. I
hehe so this is why releases were failing at my end!
Rahul
Kenney Westerhof wrote:
Prasad Kashyap wrote:
I suspect this to be the cause of my woes :-)
[INFO] [INFO] Surefire report directory:
C:\Apache\geronimo\trunk\testsuite\deployment-testsuite\deployment-tests\target\surefire-repor
Thanx Kenney. Problem solved.
Cheers
Prasad
On 1/10/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Prasad Kashyap wrote:
> I suspect this to be the cause of my woes :-)
>
> [INFO] [INFO] Surefire report directory:
>
C:\Apache\geronimo\trunk\testsuite\deployment-testsuite\deployment-tests\ta
Prasad Kashyap wrote:
I suspect this to be the cause of my woes :-)
[INFO] [INFO] Surefire report directory:
C:\Apache\geronimo\trunk\testsuite\deployment-testsuite\deployment-tests\target\surefire-reports
[INFO] java.lang.NoClassDefFoundError:
org/apache/maven/surefire/booter/SurefireBoote
Trygve Laugstøl wrote:
Vincent Siveton wrote:
Hi,
2007/1/10, Jason van Zyl <[EMAIL PROTECTED]>:
On 9 Jan 07, at 7:18 AM 9 Jan 07, Vincent Siveton wrote:
> Hi,
>
> In the same way of Brett's thread [1], WDYT to move all
> /maven/*/*-site to /maven/site/*?
>
> Actually, archiva, jxr and doxi
I suspect this to be the cause of my woes :-)
[INFO] [INFO] Surefire report directory:
C:\Apache\geronimo\trunk\testsuite\deployment-testsuite\deployment-tests\target\surefire-reports
[INFO] java.lang.NoClassDefFoundError:
org/apache/maven/surefire/booter/SurefireBooter
[INFO] Exception in thread
[X] +1 for the full proposal - collapse all groups (implies a vote for
the next option if vote doesn't pass)
I think that anybody that got a committer status in any of the maven
subproject should at least be considered enough smart to understand by
himself if he has enough knowledge and confidenc
atm the group name can be pretty much anything since its not making
the project groups automatically anymore, you have to make it manually
and then just load in the project...so I would just make a couple of
project groups, one for each...it will render out under the current UI
better anyway
the
Yes. A global patch would be better instead of separate patches.
I tried your 2 patches and updated locally jpox-* to 1.1.3 in continuum parent
pom. With them, all tests works fine, but continuum doesn't start.
Emmanuel
Marcelo Fukushima a écrit :
Hello dear devs.
After everyone's help, ive n
+1 for the partial proposal, retaining subproject access restrictions.
On 1/10/07, Jesse McConnell <[EMAIL PROTECTED]> wrote:
[X] +1 for the partial proposal - retain subproject access restrictions
On 1/9/07, John Tolentino <[EMAIL PROTECTED]> wrote:
> > Brett Porter wrote:
> > [ ] +1 for the
[X] +1 for the partial proposal - retain subproject access restrictions
On 1/9/07, John Tolentino <[EMAIL PROTECTED]> wrote:
> Brett Porter wrote:
> [ ] +1 for the full proposal - collapse all groups (implies a vote for
> the next option if vote doesn't pass)
> [X] +1 for the partial proposal -
Vincent Siveton wrote:
Hi,
2007/1/10, Jason van Zyl <[EMAIL PROTECTED]>:
On 9 Jan 07, at 7:18 AM 9 Jan 07, Vincent Siveton wrote:
> Hi,
>
> In the same way of Brett's thread [1], WDYT to move all
> /maven/*/*-site to /maven/site/*?
>
> Actually, archiva, jxr and doxia have no standard layout
On 10 Jan 07, at 11:29 AM 10 Jan 07, Vincent Siveton wrote:
Hi,
2007/1/10, Jason van Zyl <[EMAIL PROTECTED]>:
On 9 Jan 07, at 7:18 AM 9 Jan 07, Vincent Siveton wrote:
> Hi,
>
> In the same way of Brett's thread [1], WDYT to move all
> /maven/*/*-site to /maven/site/*?
>
> Actually, archiva,
Hi,
2007/1/10, Jason van Zyl <[EMAIL PROTECTED]>:
On 9 Jan 07, at 7:18 AM 9 Jan 07, Vincent Siveton wrote:
> Hi,
>
> In the same way of Brett's thread [1], WDYT to move all
> /maven/*/*-site to /maven/site/*?
>
> Actually, archiva, jxr and doxia have no standard layout for site and
> problems
On 9 Jan 07, at 7:18 AM 9 Jan 07, Vincent Siveton wrote:
Hi,
In the same way of Brett's thread [1], WDYT to move all
/maven/*/*-site to /maven/site/*?
Actually, archiva, jxr and doxia have no standard layout for site and
problems of deployment can appear (throw a glance to [2] about doxia
sit
On 10 Jan 07, at 8:18 AM 10 Jan 07, Richard van der Hoff wrote:
Jason van Zyl wrote:
We're going to be releasing a new version (looking like tomorrow)
so you can take a look at the roadmap after that.
Wasn't there a release made like last week? What's changed this time?
[I'd like to put in
Jason van Zyl wrote:
We're going to be releasing a new version (looking like tomorrow) so you
can take a look at the roadmap after that.
Wasn't there a release made like last week? What's changed this time?
[I'd like to put in a bid for MECLIPSE-151's patch to be applied].
Richard
--
Richard
Vincent Siveton wrote:
Hi,
In the same way of Brett's thread [1], WDYT to move all
/maven/*/*-site to /maven/site/*?
Actually, archiva, jxr and doxia have no standard layout for site and
problems of deployment can appear (throw a glance to [2] about doxia
site). We could consolidate them instea
38 matches
Mail list logo
