I found a few spelling errors in the doc jiras I filed for 2.7. Do you want
to re-spin to get that fixed, or should I file a new jira to take care of
that in the next release?
/Anders
On Thu, Dec 23, 2010 at 00:39, Kristian Rosenvold wrote:
> Hi,
>
> We solved 10 issues:
>
> http://jira.codehaus
+1 from me - solves my mockito issue fine!
--
Mark Derricutt
Sent with Sparrow
On Thursday, 23 December 2010 at 12:39 PM, Kristian Rosenvold wrote:
> Hi,
>
> We solved 10 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=17014
>
> There are still a couple o
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=17014
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+up
On 2010-12-22 22:09, Ralph Goers wrote:
>
> On Dec 22, 2010, at 12:58 PM, Dennis Lundberg wrote:
>
>> On 2010-12-22 20:31, Ralph Goers wrote:
>>> My thought was to
>>> a) enhance the release plugin to invoked the changes plugin and then commit
>>> the release notes before tagging and then remove
On Dec 22, 2010, at 12:58 PM, Dennis Lundberg wrote:
> On 2010-12-22 20:31, Ralph Goers wrote:
>> My thought was to
>> a) enhance the release plugin to invoked the changes plugin and then commit
>> the release notes before tagging and then remove then after
>> b) enhance the changes plugin to ha
On 2010-12-22 20:31, Ralph Goers wrote:
> My thought was to
> a) enhance the release plugin to invoked the changes plugin and then commit
> the release notes before tagging and then remove then after
> b) enhance the changes plugin to have goals to commit and delete the release
> notes.
> or c) c
I'd favour b or c. Don't add complexity to m-release-p
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 22 Dec 2010 19:32, "Ralph Goers" wrote:
> My thought was to
> a) enha
Maven 2.2 and up require Java 5. The only reason to support Java 1.4 is for bug
fixes for 2.0.x. I would suggest that at this point those are only necessary
for really critical errors.
Ralph
On Dec 22, 2010, at 1:30 AM, Stephane Nicoll wrote:
> Shouldn't we switch that in a coherent manner? I
My thought was to
a) enhance the release plugin to invoked the changes plugin and then commit the
release notes before tagging and then remove then after
b) enhance the changes plugin to have goals to commit and delete the release
notes.
or c) create a new plugin to do this.
I'm already able to
Thanks for the blazing-fast help, Olivier.
Regarding the Java 5 language updates I referred to in my original post, I
created http://jira.codehaus.org/browse/MINVOKER-114 MINVOKER-114 .
--
View this message in context:
http://maven.40175.n5.nabble.com/feedback-on-maven-invoker-plugin-patches-t
but in my case (invoker plugin) is in jira and already committed :-).
2010/12/22 Stephane Nicoll :
> Shouldn't we switch that in a coherent manner? I am afraid that if
> each plugin changes at their own pace, users will get confused about
> which ones are still compatible with Java 1.4.
>
> How ab
Hello,
It looks some changes in the modello plugin has introduced issue for
element with mixed content (in our case generated schema
).
Which was the modello type : Content.
This one is deprecated now.
Output :
[WARNING] 'Content' type is deprecated: use 'String' type and add
xml.content='true' t
Thanks for working on this. Today is my last day before Christmas vacation
so I might not be able to test the staged version when the time comes. Happy
voting, and hopefully we'll be able to upgrade in 2011 :)
--
- Jan Fredrik Wedén
On Wed, Dec 22, 2010 at 10:23, Kristian Rosenvold <
kristian.ro
Shouldn't we switch that in a coherent manner? I am afraid that if
each plugin changes at their own pace, users will get confused about
which ones are still compatible with Java 1.4.
How about releasing each plugin with what's in Jira currently and
switch to java 5 for the next major version?
S.
Hello,
changes.xml for changes plugin is included ?
Can we play with this to include a generated text release notes ?
Could me more easy (I remember stuff in m1 which updated the changes.xml).
--
Olivier
2010/12/22 Ralph Goers :
> Apache Commons has a policy (which is in alignment with
> http:/
Hi Folks,
Regarding the Dennis vote for changes plugin move to java5.
Do we need such votes for all changes of this type ?
Here I think about invoker plugin, I have moved recently but only with
a jira entry [1]
WDYT ?
Thanks,
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/ol
Mockito problem should be fixed, issue see
http://jira.codehaus.org/browse/SUREFIRE-673
There is a published 2.7.1-SNAPSHOT that you can use to re-test,
attach feedback to issue.
2.7.1 is fairly close, I'll just pack in one more session of fixing
low-hanging issues from the backlog. Vote will sta
Done and applied.
Thanks !
--
Olivier
2010/12/21 Olivier Lamy :
> Hello,
> I will have a look.
>
> 2010/12/21 lukewpatterson :
>>
>> Hi,
>>
>> I created two issues for maven-invoker-plugin:
>>
>> "duplicate script classpath entries are not filtered out, can cause
>> ClassCastException" - http://
18 matches
Mail list logo
