-1 non binding - I had that null version issue earlier. Now home and will
try to reproduce it with a currently nightly.
--
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree
2011/3/1 Tamás Cservenák
> +1
> On Feb 28, 2011 6:59 PM, "Benjamin Bentmann"
+1
On Feb 28, 2011 6:59 PM, "Benjamin Bentmann"
wrote:
> Hi,
>
> Thanks to those who tested the RC, I think we can move on to the real
> thing now.
>
> We solved 29 issues since 3.0.2:
>
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=17061
>
> There are still a couple of
There are two useful fixes since 1.1, and only one outstanding bug.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Yep - now that I have my release out ( well, deployment awaiting ) I'll
switch back and grab a log.
--
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree
On Tue, Mar 1, 2011 at 11:41 AM, Benjamin Bentmann <
benjamin.bentm...@udo.edu> wrote:
> A test case
Mark Derricutt wrote:
I note today's nightly breaks in the release plugin with a "null" version
reference in upstream artifacts which seems like a regression to a problem I
had back before 3.0 first came out.
A test case or even the actual log would be highly appreciated.
Is there a release
I note today's nightly breaks in the release plugin with a "null" version
reference in upstream artifacts which seems like a regression to a problem I
had back before 3.0 first came out.
Is there a release branch or are releases being made from trunk?
For reference, I'm downloading:
wget --no-ch
+1 (non-binding).
2011/2/28 Benjamin Bentmann
> Hi,
>
> Thanks to those who tested the RC, I think we can move on to the real thing
> now.
>
> We solved 29 issues since 3.0.2:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=17061
>
> There are still a couple of issue
Jesse Glick wrote:
Cleaner would have been to introduce ArtifactRepositoryLayout3 (?) with
the getId() method; then a simple instanceof check would suffice.
No, I want any plugin moving forward to compile against mvn 3.x libs to
get a compile error and eventually implement the method themselv
On 02/28/2011 07:09 AM, Benjamin Bentmann wrote:
Fixed in trunk by now.
Rev 1075309, which seems to be included in 3.0.3 final. Suggestion for
tightening up RepositoryUtils.getLayout a bit:
1. Call repo.getLayout() outside the try block, since that is not expected to
give an error. It is use
Hi,
Thanks to those who tested the RC, I think we can move on to the real
thing now.
We solved 29 issues since 3.0.2:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=17061
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.
According to my plans, Surefire 2.8 is 1-2 weeks from now, keeping a
nice 6 week schedule ;)
There are a few bugs in the "reporting" part of surefire Jira that I
somehow don't want to start touching as long as we're on
a fairly old version of doxia.
So it's just the "business as usual" stuff - i
I'll have look but it might not be trivial... is there any special
reason why you want to upgrade now?
-Lukas
Kristian Rosenvold wrote:
There seem to be a few compatibility breaks and maybe some incorrect
usage within the surefire-report-plugin that is making it hard to
upgrade.
I was wond
Brett Porter wrote:
Same problem building Archiva trunk (in archiva-jetty) if you want a test
project to look at.
Thanks, that did the trick. Fixed in trunk by now.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.
13 matches
Mail list logo
