+1
This is awesome news - real repository manager at last !! When can we
start using it?
Jason van Zyl wrote:
Hi,
This release worked out better and the release profile is working now
and everything is signed. This release is being staged with Nexus that
we've installed in a new zone. So B
I support only ranges. The + notation is just shorthand, but why allow
2 ways to do the same thing?
Paul
On Wed, Feb 4, 2009 at 10:41 PM, Brian E. Fox wrote:
> Yep. In the context of the enforcer this was most natural, since you
> would normally say "enforcer jdk is at least 1.5" etc.
>
> -O
Hi,
This release worked out better and the release profile is working now
and everything is signed. This release is being staged with Nexus that
we've installed in a new zone. So Brian and I are guinea pigging the
whole setup. We deployed with a self-signed SSL cert and we've asked
for a
Yep. In the context of the enforcer this was most natural, since you
would normally say "enforcer jdk is at least 1.5" etc.
-Original Message-
From: Brett Porter [mailto:br...@apache.org]
Sent: Wednesday, February 04, 2009 11:28 PM
To: Maven Developers List
Subject: Re: JDK ranges
Ah, I
Ah, I misread it. I thought 1.4 was [1.4,1.5) in the enforcer (Which
is how it works in the profiles).
- Brett
On 05/02/2009, at 3:15 PM, Brian E. Fox wrote:
Just a clarification, the enforcer impl treats "1.4" as 1.4+ or more
literally [1.4,). This slightly overrides the version range inter
Just a clarification, the enforcer impl treats "1.4" as 1.4+ or more
literally [1.4,). This slightly overrides the version range internally
because in that case "1.4" = (,) with a recommended version of 1.4.
-Original Message-
From: Brett Porter [mailto:br...@apache.org]
Sent: Wednesday
I am not sure if anyone can help me, but I wasn't able to find an admin email
on jira.
I changed companies and thus my email changed. I thought I had changed it in
jira, but I guess I didn't. Then, yesterday I tried to login, but it wasn't
working so I reset my password and of course I never
The previous regressions have been fixed.
Here's the list of issues fixed in 2.0.10:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName
=Html&projectId=10500&Create=Create
Staged at (self-signed cert for now)
https://repository.zones.apache.org/content/groups/stag
Actually, I found this page: http://docs.codehaus.org/display/MAVEN/Maven+3.0.x
I cannot tell you how happy I am to hear about the rewriting of the artifact
handling. It is the main part of maven that I think has major architectural
issues. I very glad to see that Maven developers have realize
Is there a timeline for a release and there anywhere I can find documentation
on the new features/improvements/changes in said release?
regards,
Jason
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional co
Hi Dennis,
Clirr plugin doesnt support ${reactorProjects} or aggregate so it is a
normal behaviour IMHO (and javadoc plugin 2.5 is correct).
As a workaround, you could create a reporting-aggregate similar to [1].
Cheers
Vincent
[1]
https://svn.apache.org/repos/asf/maven/components/branches/ma
Hi guys
The "just adding a Clirr report" turned out to be a little more than that...
When I run 'mvn -Preporting site:stage' on either doxia trunk or
doxia-1.0.x branch I get the following errors. They happen when the
javadoc plugin is creating its aggregated report. I have tried
everything I can
c +1
a 0
b -1
Sent from my [rhymes with myPod] ;-)
On 4 Feb 2009, at 23:25, Brett Porter wrote:
Hi,
First of all, kudos to Benjamin for knocking out my latest issues IT
while I slept (I hear he is actually capable of knocking them out in
his sleep :)
Due to an interesting change histor
Hi,
First of all, kudos to Benjamin for knocking out my latest issues IT
while I slept (I hear he is actually capable of knocking them out in
his sleep :)
Due to an interesting change history (closed for 2.0.x, which I
assumed to be the latest release 2.0.7, but was actually trunk), I
m
Likewise.
These are the type of bugs that really make maven look bad. I have been
promoting maven for well over 5 years now and I am currently converting a new
company to maven and we encountered this bug. It really has turned everyone
off on Maven and it is making it an uphill battle to conv
Brett, It should be ok now, the links are stabilized to making the deep
linking easier. Tim, any concerns with deep linking?
-Original Message-
From: Brett Porter [mailto:br...@apache.org]
Sent: Wednesday, February 04, 2009 5:55 AM
To: Maven Developers List
Subject: deep linking to other
Hi Jason,
2009/2/4 Jason van Zyl :
> What happened to doxia 1.0?
Doxia 1.0 should work as usually for Maven 2.0.x.
2.1.M3 should include 1.1
Cheers,
Vincent
> On 4-Feb-09, at 5:39 AM, Vincent Siveton wrote:
>
>> Hi guys,
>>
>> The good news is that using the shade plugin, I was able to run a t
Hi Petar,
I opened an issue in Jira : http://jira.codehaus.org/browse/MSHARED-92
I've also enclosed unit tests inside the patch.
Regards,
Jerome
2009/2/3 Petar Tahchiev
> Hi Jerome,
>
> looks obvious to me.
>
> Can you open an issue in the JIRA with the patch attached?
>
> 2009/2/2 jerome cr
Hi guys,
The good news is that using the shade plugin, I was able to run a the
latest Doxia plugin (using Doxia 1.1) with mvn 2.0.9 and 2.1.0.M2 and
site-plugin 2.0-beta-7.
The bad news, I don't know what are the potential side effects.
You could do similar things for the pdf plugin [1]. Let's ju
In an effort to get some more information available from the Maven
docs, if not in the docs, I added a link for "more information" to the
bottom of a new article. In this case, to chapter 6 of The Definitive
Guide.
a) any issues with doing this?
b) Definitive Guide authors: any issues with
20 matches
Mail list logo
