On 3/1/07, Thierry Lach [EMAIL PROTECTED] wrote:
Using current sources patched for JBoss, I can't access the configuration
page. As the administrator, when I try to go there, I get the message
Authorization Error You are not authorized to access this page. Please
contact your administrator to
+1
Stéphane
On 3/1/07, Jason van Zyl [EMAIL PROTECTED] wrote:
+1
On 1 Mar 07, at 12:22 PM 1 Mar 07, Carlos Sanchez wrote:
anything pending to do in the apache pom? there are some mistakes in
the version 3 like organization name that propagates to all apache
projects.
--
I could give
sounds great, +1
Stéphane
On 3/2/07, Jason van Zyl [EMAIL PROTECTED] wrote:
Hi,
The impetus for this is wanting to release the surefire plugin that
has a tiny bug in it. We are versioning our Maven release
major.minor.micro so why don't we do the same with our plugin and
treat everything
Hi all,
I asked on the user list whether I was doing this correctly, but got no
response - in the mean time this is looking like a bug.
I have a jar file, attached to the lifecycle being the compiling of some
C++ code into target/build, which works fine.
I need to embed the C++ library
Thierry Lach-2 wrote:
Using current sources patched for JBoss, I can't access the configuration
page. As the administrator, when I try to go there, I get the message
Authorization Error You are not authorized to access this page. Please
contact your administrator to be granted the
Hi,
I can't bootstrap.
Maven-project doesn't build for me due to test errors.
Other people seem to be building just fine.
I've tracked the problem down to environment issues - the order
in which the tests are run is important.
The errors are in t02.ProjectInheritanceTest and others,
+1
On 2 Mar 2007, at 02:20, Jason van Zyl wrote:
Hi,
The impetus for this is wanting to release the surefire plugin that
has a tiny bug in it. We are versioning our Maven release
major.minor.micro so why don't we do the same with our plugin and
treat everything like we're going to do
+1
On 1 Mar 2007, at 17:22, Carlos Sanchez wrote:
anything pending to do in the apache pom? there are some mistakes in
the version 3 like organization name that propagates to all apache
projects.
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
+1, as long as it's done like this:
- use major.minor on trunk
- major.[minor+1] is either api breaking or has new features
- bugfixes should be major.minor.micro, from a maintenance branch for
major.minor.
so -0 on bugfix versions in the poms on trunk.
-- Kenney
Jason van Zyl wrote:
Hi,
ping :-)
On 2/18/07, Niall Pemberton [EMAIL PROTECTED] wrote:
On 2/18/07, Jason van Zyl [EMAIL PROTECTED] wrote:
On 18 Feb 07, at 9:32 AM 18 Feb 07, Niall Pemberton wrote:
On 2/15/07, Stephane Nicoll [EMAIL PROTECTED] wrote:
Yes. I need to check with Jason because it seems he's found a
+1
- Joakim
Jason van Zyl wrote:
Hi,
The impetus for this is wanting to release the surefire plugin that
has a tiny bug in it. We are versioning our Maven release
major.minor.micro so why don't we do the same with our plugin and
treat everything like we're going to do small incremental
On 2 Mar 07, at 12:07 AM 2 Mar 07, Ralph Goers wrote:
Patrick Mike took this over. To be honest, I really don't know
what they are doing. I think they are confused over your desire to
have this be just the way it works in 2.1. That means the
override tag won't be there in 2.1.
On 2 Mar 07, at 7:28 AM 2 Mar 07, Niall Pemberton wrote:
ping :-)
I just released a snapshot, do you think you could give it a whirl
quickly?
Jason.
On 2/18/07, Niall Pemberton [EMAIL PROTECTED] wrote:
On 2/18/07, Jason van Zyl [EMAIL PROTECTED] wrote:
On 18 Feb 07, at 9:32 AM 18
I believe the patch is very very similar for the branch but the
sandbox code was for the trunk code as of a few weeks ago. Patrick is
out on vacation this week and back on Monday. I know we found two
bugs in the patch while using it internally over the last month that
are not fixed in the
On 2 Mar 07, at 8:27 AM 2 Mar 07, Mike Perham wrote:
I believe the patch is very very similar for the branch but the
sandbox code was for the trunk code as of a few weeks ago. Patrick is
out on vacation this week and back on Monday. I know we found two
bugs in the patch while using it
On 3/2/07, Jason van Zyl [EMAIL PROTECTED] wrote:
On 2 Mar 07, at 7:28 AM 2 Mar 07, Niall Pemberton wrote:
ping :-)
I just released a snapshot, do you think you could give it a whirl
quickly?
I ran mvn source:jar for commons validator with the new snapshot and
everything was fine (with a
Brian E. Fox wrote:
How close is the dependency analyzer shared piece from coming out of the
sandbox and being released?
It's Mark's code, but from my PoV it simply works. So it should no problem
to release some kind of alpha version, indicating that Mark is going to add
more stuff.
- Jörg
Would it be better the other way around? Branch for wagon-1.x, have
trunk be wagon-2.x?
- Brett
On 03/03/2007, at 4:24 AM, [EMAIL PROTECTED] wrote:
Author: joakime
Date: Fri Mar 2 12:24:33 2007
New Revision: 513930
URL: http://svn.apache.org/viewvc?view=revrev=513930
Log:
Due to issues
Hi All,
Due to our source structure, I have to svn checkout/update many separate
folders to do build. Thus continuum checkout/update an ant scripts and that
ant script will checkout different folders and do the build. My problem is
continuum is skipping the builds since there is no change in the
Hi
I'd like to release JXR 1.1. All issues scheduled for that version has
been solved. Before I start a vote I thought I'd ask if someone needs
any of the remaining unscheduled issues [1] solved in version 1.1. None
of the remaining bugs seem very dangerous.
[1]
Is the patch on -16 any good? That's the only one I'd move to fix.
-14 can probably be closed - it's either a findbugs problem, or a
duplicate of -11.
The rest are feature requests, so I'd leave them for the future.
How about moving the plugin into the same source tree and releasing a
On 2 Mar 07, at 5:29 PM 2 Mar 07, Brett Porter wrote:
Would it be better the other way around? Branch for wagon-1.x, have
trunk be wagon-2.x?
Doesn't matter now, I fixed it.
Jason.
- Brett
On 03/03/2007, at 4:24 AM, [EMAIL PROTECTED] wrote:
Author: joakime
Date: Fri Mar 2 12:24:33
22 matches
Mail list logo
