Hi Brett,
I updated my workspace today and tried to build Archiva, and I get an error
during JPOX enhancement, in the archiva-model module
(UnsupportedClassVersionError, see at the end of the mail for the log). If I
use the last revision of the Archiva's root POM (that is, with compiler set
to
I don't agree to postpone m1 support for 1.0.X. It's one of the feature
which create the difference with others proxy repo tools... It's the feature
which help to install archiva in corporate contexts...
Arnaud
On 20/06/07, Joakim Erdfelt [EMAIL PROTECTED] wrote:
Fabrice,
Excellent news! :-)
m1 is just postponed to a release after 1.0-alpha-2, and before 1.0-final
It's not out, it's not forgotten. :-)
The 1.0.x fix version is just a holding area for 1.0 related jiras.
Things that are post-1.0 are in the Future fix version right now.
When I get back from my various trips these
On 6/19/07, Fabrice Bellingard [EMAIL PROTECTED] wrote:
which proxy related bugs do you think of? I've tested Archiva proxying for
some days, and it works pretty good for me. I mean, if we'd have to release
alpha-2, I wouldn't say no. :-)
That's good to know. I see 14 closed issues in
No problems here, or on the solaris zone. You ran with clean as well?
I'd suggest upgrading your JDK if it really is _01 - that's pretty
old :)
- Brett
On 20/06/2007, at 8:42 PM, Fabrice Bellingard wrote:
Hi Brett,
I updated my workspace today and tried to build Archiva, and I get
an
The only one I'd change is the maximum. I don't really understand the
usefulness of that and it's hit me a couple of times.
- Brett
On 18/06/2007, at 8:12 PM, Joakim Erdfelt wrote:
There has been some controversy on the closing of MRM-229 and MRM-225,
I feel that they should remain closed.
On 6/20/07, Brett Porter [EMAIL PROTECTED] wrote:
The only one I'd change is the maximum. I don't really understand the
usefulness of that and it's hit me a couple of times.
Same here. Jesse already said he'd change it in Redback, so Archiva
will pick up the change at some point.
--
Wendy
Hi,
I had a look at the ContinuumService Interface of the XML RPC API in the
current sources. At the moment the service lacks a method where i can
retrieve all projects or project groups without specifying a parameter
(in 1.0.3 this was possible). There are only methods where i have to
pass in
Idon't know when we'll can work on it, your patch will be welcome.
Emmanuel
Jan Lisse a écrit :
Hi,
I had a look at the ContinuumService Interface of the XML RPC API in the
current sources. At the moment the service lacks a method where i can
retrieve all projects or project groups without
Hi,
I'm having a problem deleting projects that I've been using for a
while. New Projects I can delete without problem:
When I try to delete an old project I get the error below:
This seems to be the JIRA issue:
http://jira.codehaus.org/browse/CONTINUUM-1301
The instructions to manually
Le mercredi 20 juin 2007, Brian E. Fox a écrit :
I discovered http://jira.codehaus.org/browse/MNG-2961 while working on
mdep a while back.
same for me while working on http://jira.codehaus.org/browse/MANTTASKS-18
It should be an easy fix but I'm pondering what the
least intrusive fix is.
Will http://jira.codehaus.org/browse/MNG-2305 (not able to access HTTPS
repositories via proxy/firewall) be resolved?
Cheers
Franz
Jason van Zyl schrieb:
Just a reminder for anyone lurking who wants issues addressed in 2.0.8
to vote for issues in JIRA.
Thanks,
Jason
On 19/06/07, Jason van Zyl [EMAIL PROTECTED] wrote:
If you do mvn install in the parent IT directory all the plugins
and artifacts required will be installed and the ITs will pass.
I'm sure we're crossing wires here:
[EMAIL PROTECTED] core-integration-testing]$ mvn install
...
[EMAIL
Hi Joakim,
On 19/06/07, Joakim Erdfelt [EMAIL PROTECTED] wrote:
I want to see maven 2.1 fixed in regards to project model resolution.
The current mess in maven/components is completely unusable within
archiva. If that occurs, then the rest of the dependency graph
resolution bits will fall into
Also see
https://svn.apache.org/repos/asf/maven/surefire/trunk/maven-surefire-plugin/src/main/java/org/apache/maven/plugin/surefire/SurefirePlugin.java
line 494.
I tried to fix this a while back but it's a big mess and has a lot of unwanted
side effects.
Accessors shouldn't change a property,
I agree.
I likewise share concerns about the performance of this. My
preference would be for the policy to be better separated, but still
applied during the resolution process. In my mind this had always
been the place for 'conflict resolvers' to enforce policy during the
process.
Thanks for the summary mail, Mark. I agree that's the general plan. A
couple of comments...
On 20/06/2007, at 2:48 AM, Mark Hobson wrote:
other than that let's just choose one of the libraries and deprecate
the other one to avoid splitting the work
archiva-dependency-graph appears to be
I'd like to contribute a plug-in that wraps installjammer,
www.installjammer.com. We use it to create GUI installers as part of
the build process. Should I just submit a Jira issue and attach the
code? I'm sure that this has been asked many times before, but I didn't
see any way to search the
On 20 Jun 07, at 6:37 AM 20 Jun 07, Donovan, Aaron wrote:
I'd like to contribute a plug-in that wraps installjammer,
www.installjammer.com. We use it to create GUI installers as part of
the build process. Should I just submit a Jira issue and attach the
code? I'm sure that this has been
Hi there,
I've having problems with DefaultArtifactCollector events when scopes
are being updated. The scenario in question is as follows:
p - a
a - c:test, b
b - c:compile
This resolves as follows:
1) c:test's scope is broadened to compile
2) p - a - c:test is disabled in
On 20/06/2007, at 3:27 AM, Joakim Erdfelt wrote:
+1
How can I not vote +1? After all, according to the META-INF/
MANIFEST.MF in the maven-core-2.0.7-uber.jar I built it.
Niggle: It still feels wrong to have the maven-core-2.0.7-uber.jar
have a LICENSE.txt in it's root that says it's a
Can you change the logger to detect this and not re-report? This will
make -X output obscenely long (as if it wasn't already :)
- Brett
On 20/06/2007, at 2:53 AM, [EMAIL PROTECTED] wrote:
Author: markh
Date: Tue Jun 19 09:53:10 2007
New Revision: 548797
URL:
Be sure that this doesn't break forward compatibility too.
That approach would not allow for proper mirroring, authentication
propagation, network proxy usage, and short-circuits the whole wagon
manager approach of wagon 2.x
Direct usage of the wagon, not through the wagon manager, means a
Hi team,
It's with pleasure that I want to launch the vote to release the final
version of maven 1.1.
We published, one month ago, a first release candidate for maven 1.1 and
we had few issues opened (certainly because this release is perfect, and not
because we lost our last users ;-) ).
+1
Woo hoo!
On 20 Jun 07, at 10:46 AM 20 Jun 07, Arnaud HERITIER wrote:
Hi team,
It's with pleasure that I want to launch the vote to release the
final
version of maven 1.1.
We published, one month ago, a first release candidate for maven
1.1 and
we had few issues opened (certainly
+1
On 6/20/07, Arnaud HERITIER [EMAIL PROTECTED] wrote:
Hi team,
It's with pleasure that I want to launch the vote to release the final
version of maven 1.1.
We published, one month ago, a first release candidate for maven 1.1 and
we had few issues opened (certainly because this release
On 20 Jun 07, at 10:13 AM 20 Jun 07, Joakim Erdfelt wrote:
Be sure that this doesn't break forward compatibility too.
That approach would not allow for proper mirroring, authentication
propagation, network proxy usage, and short-circuits the whole
wagon manager approach of wagon 2.x
+1: Jason, Brett, Stephane, Joakim, Arnaud, Jesse, Brian (non-
binding: Eric, Jo, Jochen, Christian)
+0: nada
-1: nada
I'll push this out as soon as I can today.
Jason.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
On 20 Jun 07, at 11:47 AM 20 Jun 07, Joakim Erdfelt wrote:
Jason van Zyl wrote:
On 20 Jun 07, at 10:13 AM 20 Jun 07, Joakim Erdfelt wrote:
Be sure that this doesn't break forward compatibility too.
That approach would not allow for proper mirroring,
authentication propagation, network
+1 Good job!
Stéphane
On 6/20/07, Arnaud HERITIER [EMAIL PROTECTED] wrote:
Hi team,
It's with pleasure that I want to launch the vote to release the final
version of maven 1.1.
We published, one month ago, a first release candidate for maven 1.1 and
we had few issues opened (certainly
Jason van Zyl wrote:
On 20 Jun 07, at 10:13 AM 20 Jun 07, Joakim Erdfelt wrote:
Be sure that this doesn't break forward compatibility too.
That approach would not allow for proper mirroring, authentication
propagation, network proxy usage, and short-circuits the whole wagon
manager
It's been about 5 months since we last released eclipse. There are
plenty of issues already fixed:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13001styleName
=HtmlprojectId=11133Create=Create
There are currently 24 remaining open. Any objections to cutting a
release as is and
go for it
On 6/20/07, Brian E. Fox [EMAIL PROTECTED] wrote:
It's been about 5 months since we last released eclipse. There are
plenty of issues already fixed:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13001styleName
=HtmlprojectId=11133Create=Create
There are currently 24
It's also worth considering contributing it to installjammer itself.
On 20/06/2007, at 11:55 PM, Jason van Zyl wrote:
On 20 Jun 07, at 6:37 AM 20 Jun 07, Donovan, Aaron wrote:
I'd like to contribute a plug-in that wraps installjammer,
www.installjammer.com. We use it to create GUI
It is in my todo list but up until now I focused on maven 1.
I have several co-workers who reported to me that they are unable to run
tests in this plugin.
I'll study this problem with them tomorrow.
I have also some patchs to apply concerning rad6 and myeclipse but it can be
included in the next
+1
On 20 Jun 07, at 1:01 PM 20 Jun 07, Brian E. Fox wrote:
It's been about 5 months since we last released eclipse. There are
plenty of issues already fixed:
http://jira.codehaus.org/secure/ReleaseNote.jspa?
version=13001styleName
=HtmlprojectId=11133Create=Create
There are currently 24
IT doesn't quite sound right - I would have expected it still select
nearest and apply the alternate scope from my recollection. But IIRC
behaviour was changed ~2.0.4 in relation to scopes, for some
particular reason and perhaps this is it: Carlos?
Second part sounds like a simple
On 18/06/2007, at 10:41 AM, Jason van Zyl wrote:
On 17 Jun 07, at 5:25 PM 17 Jun 07, Brett Porter wrote:
On 17/06/2007, at 8:43 AM, Jason van Zyl (JIRA) wrote:
[ http://jira.codehaus.org/browse/MNG-2943?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason
+1
I don't have a lot of projects, so I tested by building the source
distro with the binary one :)
Great job all - I really appreciate the efforts you put in to finish
this.
- Brett
On 21/06/2007, at 3:46 AM, Arnaud HERITIER wrote:
Hi team,
It's with pleasure that I want to launch
Le mercredi 20 juin 2007, Kenney Westerhof a écrit :
Also see
https://svn.apache.org/repos/asf/maven/surefire/trunk/maven-surefire-plugin
/src/main/java/org/apache/maven/plugin/surefire/SurefirePlugin.java
line 494.
I tried to fix this a while back but it's a big mess and has a lot of
40 matches
Mail list logo
