Hi,
unfortunately i got the following if i try to build the release via:
mvn -Prun-its clean verify
[INFO] -
[INFO] Build Summary:
[INFO] Passed: 18, Failed: 6, Errors: 0, Skipped: 2
[INFO] -
[ERRO
Hi Kristian,
There had to be some kind of issue with collection if Karl made IdentityMap
synchronized.
Whatever collections are too open. As an example, this is not right and it
is not right in multithreading either:
request.setArtifactDependencies( project.getDependencyArtifacts() );
//common in
Hi,
We solved 13 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11139&styleName=Html&version=20381
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11139&status=1
Staging repo:
https://repository.apache.org/co
The Apache Maven team is pleased to announce the release of the
Apache Maven EAR Plugin, version 2.10
This plugin generates Java EE Enterprise Archive (EAR) file. It can also
generate the deployment descriptor file (e.g. application.xml).
http://maven.apache.org/plugins/maven-ear-plugin/
You sh
Hi,
The vote has passed with the following result:
+1 (binding): Hervé Boutemy, Stephane Nicoll, Robert Scholte, Karl Heinz
Marbaise
+1 (non binding): none.
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
---
We try to move the code forwards, but old code bases are
"interesting"; you have to make sure you keep track of your goals.
What I am trying to say is that when I think of rouge threads writing
in unsynchronized data; I immediately get flashbacks of the gunman in
pulp fiction (Samuel L Jackson I b
1. problem reproduced: in a global plugin-tools build, there is no compilation
issue but if I build only maven-plugin-plugin the compilation failure happens
strange: I wouldn't expect the reactor build to have any impact on build
classpath
2. problem explained:
when I changed the annotations ext
than with what Maven version?
In fact, in the past, I didn't declare plugin annotations as "provided" since
I thought they were necessary at runtime, since they have CLASS
RetentionPolicy.
But later, marking the artifact as provided just worked, even if I didn't
unserstand why: then we finally
ok, fair
Regards,
Hervé
Le mercredi 31 décembre 2014 11:25:05 Robert Scholte a écrit :
> I can imagine the confusion between "build" and "builder"
> If you talk about parallel build strategies, I'd say it would be something
> for build-support.
>
> Build*er* support can/should be used by model-
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven/pull/34#issuecomment-68440499
@jvanzyl
That's clear we must not break current users.
You kow my problem is, as always when i design any API, how much open the
interfaces should be.
Here I tr
+1
Op Wed, 31 Dec 2014 13:02:47 +0100 schreef Karl Heinz Marbaise
:
Hi,
just one VOTE is missing ;-)...
Kind regards
Karl Heinz Marbaise
On 12/28/14 3:30 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 19 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132&version=20436
I clearly overlooked this one, sorry.
+1
On Wed, Dec 31, 2014 at 1:02 PM, Karl Heinz Marbaise
wrote:
> Hi,
>
> just one VOTE is missing ;-)...
>
> Kind regards
> Karl Heinz Marbaise
> On 12/28/14 3:30 PM, Karl Heinz Marbaise wrote:
>
>> Hi,
>>
>> We solved 19 issues:
>> http://jira.codehaus.org
Hi,
just one VOTE is missing ;-)...
Kind regards
Karl Heinz Marbaise
On 12/28/14 3:30 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 19 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132&version=20436
http://jira.codehaus.org/issues/?jql=project%20%3D%20MEAR%20AND%20statu
Don't worry Kristian, you did great job in parallel Maven exec, honestly I
don't say opposite!
As the CPUs speed up and disks as well, we really need parallal executions
in Maven core.
The thing how the discussion started in emails is that i wrote some local
changes and opened PR
https://github.com
I can imagine the confusion between "build" and "builder"
If you talk about parallel build strategies, I'd say it would be something
for build-support.
Build*er* support can/should be used by model-builder, settings-builder
and toolchains-builder (still wondering if it is worth it to extract
I've tried it with:
Java version: 1.6.0_25, vendor: Sun Microsystems Inc.
Java version: 1.7.0_55, vendor: Oracle Corporation
in both cases the error output starts with:
package org.apache.maven.plugins.annotations does not exist
thanks,
Robert
Op Wed, 31 Dec 2014 00:38:50 +0100 schreef Hervé BO
I'll take a look once I get down from the mountains. What little time
I'm not skiing I'm hacking on commons-compress right now. Remember
that the general multi-threaded contract of maven is simple and clear;
unless clearly stated a mojo is not allowed to call back on the maven
core model objects on
17 matches
Mail list logo
