Fair enough, I've put https://issues.apache.org/jira/browse/INFRA-5312
on hold until we also release
wagon + scm to verify that it goes smoothly. Although it may seem like
it, we're not in that big of a rush ;)
Kristian
2012/9/24 Dennis Lundberg :
> Hi Kristian
>
> I hate to be the one hitting t
+1(non-binding) Now toolchain is working with this release. Thanks.
rgds, Markku
On 09/24/2012 09:30 PM, Kristian Rosenvold wrote:
Hi,
We solved 6 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18757&styleName=Html&projectId=10541
2.12.4 is a minimal bugfix release and is i
Sent from my iPhone
On 25/09/2012, at 12:21 PM, Jesse Farinacci wrote:
> Greetings,
>
> On Mon, Sep 24, 2012 at 8:57 PM, Chris Graham wrote:
>> +1
>>
>> On 25/09/2012, at 6:06 AM, Dennis Lundberg wrote:
>>> I hate to be the one hitting the brakes on everything Git, but...
>>> ...I really t
Nothing conflicted at all.
I was sims agreeing with what Dennis said.
To paraphrase: let's make sure we've worked all the kinks out first before we
move everything else over.
Isn't that prudent?
-Chris
Sent from my iPhone
On 25/09/2012, at 12:21 PM, Jesse Farinacci wrote:
> Greetings,
>
Greetings,
On Mon, Sep 24, 2012 at 8:57 PM, Chris Graham wrote:
> +1
>
> On 25/09/2012, at 6:06 AM, Dennis Lundberg wrote:
>> I hate to be the one hitting the brakes on everything Git, but...
>> ...I really think we shouldn't move our release component to Git until
>> we have ironed out any poss
+1
Sent from my iPhone
On 25/09/2012, at 6:06 AM, Dennis Lundberg wrote:
> Hi Kristian
>
> I hate to be the one hitting the brakes on everything Git, but...
>
> ...I really think we shouldn't move our release component to Git until
> we have ironed out any possible problems related to doing M
Hello,
I am working on integration toolchains configuration files into Jenkins.
In order to be compatible with distributed Jenkins, I need to be able to
dynamically compute the path of the JDKs configured in the toolchains
configuration file.
Do you know if there is an integration point in Maven f
Hi Kristian
I hate to be the one hitting the brakes on everything Git, but...
...I really think we shouldn't move our release component to Git until
we have ironed out any possible problems related to doing Maven releases
in Git.
On 2012-09-24 10:24, Kristian Rosenvold wrote:
> Just filed https:
+1 (non-binding) I tested this release using JDK 1.6.0_32-b05-420 as
well as jdk1.7.0_07 with a small multi-module project, surefire as
well as building the site including a cobertura report look good.
Regards Mirko
On Mon, Sep 24, 2012 at 8:30 PM, Kristian Rosenvold
wrote:
> Hi,
>
> We solved
Hi,
We solved 6 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=18757&styleName=Html&projectId=10541
2.12.4 is a minimal bugfix release and is intended to be the new
parent-pom version. It's also our first git-based release.
There are still lots of issues left in JIRA:
http://
I'd like to release maven plugin testing 1.3 (maven 2.x) and 2.1 (maven 3.x)
The main intent of this release is to modernize dependencies, so we
can build on post 1.5 jdks for dependant projects.
This includes especially upgrading to easymock 2.5.2, dependencies
updating to this version should
ad
On Mon, Sep 24, 2012 at 8:53 AM, Stephen Connolly
wrote:
> On 24 September 2012 12:58, Benson Margulies wrote:
>
>> Folks,
>>
>> Much electronic ink was spilt on the subject of POM5. One of the pools
>> of ink was created by my attempt, some months ago, to move the design
>> along.
>>
>> I wish s
Just filed https://issues.apache.org/jira/browse/INFRA-5312
Kristian
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
If that is the only reason for the release and it can be fixed in an earlier
release, then I see no reason not too.
This is also in line with the general
Maven ethos of not forcing people to upgrade.
-Chris
Sent from my iPhone
On 24/09/2012, at 6:44 AM, Kristian Rosenvold
wrote:
> At the mo
+1
-Lukas
Dennis Lundberg wrote:
> Hi,
>
> This is the first release of the Doxia Tools parent after the
> restructuring of these components. It now works in the same way as the
> parents for Plugins and Shared Components.
>
> Doxia Integration Tools moved from Shared Components to Doxia Tool
+1
--
Olivier
Le 23 sept. 2012 15:42, "Dennis Lundberg" a écrit :
> Hi,
>
> This is the first release of the Doxia Tools parent after the
> restructuring of these components. It now works in the same way as the
> parents for Plugins and Shared Components.
>
> Doxia Integration Tools moved from S
16 matches
Mail list logo