Github user hboutemy commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-77975130
another issue found regarding slf4j, this time with cobertura plugin,
during instrumentation http://jira.codehaus.org/browse/MNG-5783 created, with
the difference in {{Pop
+1
On 9 March 2015 at 22:56, Benson Margulies wrote:
> Hi,
>
> This is a vote to release Archetype 2.3, intended as the last version
> of Archetype built to support Maven 2.2.x.
>
> We solved some issues:
>
> Release Notes - Maven Archetype - Version 2.3
>
>
> ** Bug
> * [ARCHETYPE-345] - ar
+1
Regards,
Hervé
Le lundi 9 mars 2015 07:56:16 Benson Margulies a écrit :
> Hi,
>
> This is a vote to release Archetype 2.3, intended as the last version
> of Archetype built to support Maven 2.2.x.
>
> We solved some issues:
>
> Release Notes - Maven Archetype - Version 2.3
>
>
> ** Bug
>
AFAIK we have switched deploying directly to ossrh for long time now :-)
On 10 March 2015 at 06:01, Dennis Lundberg wrote:
> Hi,
>
> What is the intended binary repo for plexus, after the move to the
> codehaus-plexus organization on github?
>
> I requested permissions to deploy to ossrh, which
I'm making good progress but I'm hitting issues with the unittests (see
below).
I've tried several combinations of plugin-testing-harness version and
Maven version, but no result yet.
Anyone seen this issue before?
If would be nice if surefire could at least report what it is trying to
call
Hi,
What is the intended binary repo for plexus, after the move to the
codehaus-plexus organization on github?
I requested permissions to deploy to ossrh, which is what it says in the
parent. They wanted confirmation that we are switching from
nexus.codehaus.org to ossrh. Are we?
--
Dennis Lundb
Hi,
What is the intended binary repo for plexus, after the move to the
codehaus-plexus organization on github?
I requested permissions to deploy to ossrh, which is what it says in the
parent. They wanted confirmation that we are switching from
nexus.codehaus.org to ossrh. Are we?
--
Dennis Lundb
Yes, I'll leave it until Wednesday to see if anyone has any issues running
master and then I'll stage the release.
On Mar 8, 2015, at 6:42 PM, Hervé BOUTEMY wrote:
> notice that this would be a de-facto Maven versionning pattern:
> 2.0 (Java 1.4)/2.1(Java 1.4+changes)/2.2(Java 5)
> 3.0 (Java 5)
Hi,
The vote has passed with the following result:
+1 (binding): Olivier Lamy, Hervé Boutemy, Karl Heinz Marbaise
+1 (non binding): none
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
-
To
Hi,
The vote has passed with the following result:
+1 (binding): Olivier Lamy, Hervé Boutemy, Karl Heinz Marbaise
+1 (non binding): none
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
-
To
Hi Benson,
Checked SHA1,
Tested with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.5 via mvn -Prun-its clean verify
now without any issue...
So +1 from me
Kind regards
Karl Heinz Marbaise
On 3/9/15 12:56 PM, Benson Margulies wrote:
Hi,
This is a vote to release Archetype 2.3, intended as the last version
Hi,
This is a vote to release Archetype 2.3, intended as the last version
of Archetype built to support Maven 2.2.x.
We solved some issues:
Release Notes - Maven Archetype - Version 2.3
** Bug
* [ARCHETYPE-345] - archetype:create-from-project do not process
and sections into EAR's pom.xm
What's the rush?
Releases are cheap and easy, so I find the argument to upgrade now due to one
less release is somewhat lacking.
Sent from my iPad
> On 9 Mar 2015, at 2:22 am, Dennis Lundberg wrote:
>
> Hi Igor,
>
> In my opinion the switch to Java 7 as a prerequisite is a non-risky
> thing
13 matches
Mail list logo
