Hi,
here my +1.
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=11132version=20436
Hey Karl,
This is the list of concurrency issues in Maven.
http://jira.codehaus.org/browse/MNG-5705?jql=project%20%3D%20MNG%20AND%20status%20%3D%20Open%20AND%20text%20~%20%22parallel%22
The funny thing with such of these issues is that they may not appear in
another environments and new may
An excellent operation is CAS (Compare and Swap/Set). This would mean that
POJO would have getters which return unmodifiableCollection, and new CAS
operations, for instance for the project dependencies.
The new method would be then:
public boolean casDependencies(CollectionArtifact original,
Hi,
The vote has passed with the following result:
+1 (binding): Jason, Karl Heinz, Kristian, Hervé
+1 (non binding): Igor
I will promote the artifacts to the central repo.
Thank you Karl Heinz for giving this vote little extra push it needed.
--
Regards,
Igor
On 2014-12-17 20:40, Igor
Can somebody with PMC powers copy the source release to the Apache
Distribution Area? Thank you in advance.
--
Regards,
Igor
On 2014-12-30 8:55, Igor Fedorenko wrote:
Hi,
The vote has passed with the following result:
+1 (binding): Jason, Karl Heinz, Kristian, Hervé
+1 (non binding): Igor
I
Hi Igor,
On 12/30/14 3:17 PM, Igor Fedorenko wrote:
Can somebody with PMC powers copy the source release to the Apache
Distribution Area? Thank you in advance.
Done so.
Also added to board report.
Kind regards
Karl Heinz Marbaise
--
Regards,
Igor
On 2014-12-30 8:55, Igor Fedorenko wrote:
Hi,
This commit gives me compilation errors, e.g.
[ERROR]
/E:/java-workspace/apache-maven-plugin-tools/plugin-tools/maven-plugin-plugin/src/main/java/org/apache/maven/plugin/plugin/PluginReport.java:[77,6]
On Sun, Dec 28, 2014 at 9:04 PM, Robert Scholte rfscho...@apache.org
wrote:
Op Sun, 28 Dec 2014 19:37:47 +0100 schreef Kristian Rosenvold
kristian.rosenv...@gmail.com:
I'll sumarize what appears to be our consensus so far.
Update to jdk 6.0 at will, but please be sure that we're not
In my experience, there are significant API issues between 3.0 and
3.1. My particular obsession is with the plugin testing harness.
I've had several experiences of the following forn:
1: go to fix a problem in a plugin.
2: try to create an appropriately focussed test
3: try to set up the testing
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven/pull/34
Improved visibility of collections and variables across multiple threads
Upon our discussion with Karl in
Github user Tibor17 commented on the pull request:
https://github.com/apache/maven/pull/34#issuecomment-68410326
I wante to have final field o `MavenProject#dependencyArtifacts`, but in
that case two tests would fail due to
`DefaultProjectDependenciesResolver#process()` iterates over
+1
Regards,
Hervé
Le dimanche 28 décembre 2014 15:30:09 Karl Heinz Marbaise a écrit :
Hi,
We solved 19 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132version=204
36
http://jira.codehaus.org/issues/?jql=project%20%3D%20MEAR%20AND%20status%20%
personnally, I use invoker: no compatibility problems
Regards,
Hervé
Le mardi 30 décembre 2014 17:45:36 Benson Margulies a écrit :
In my experience, there are significant API issues between 3.0 and
3.1. My particular obsession is with the plugin testing harness.
I've had several
uh, which JDK version?
Regards,
Hervé
Le mardi 30 décembre 2014 22:40:17 Robert Scholte a écrit :
Hi,
This commit gives me compilation errors, e.g.
[ERROR]
/E:/java-workspace/apache-maven-plugin-tools/plugin-tools/maven-plugin-plugi
On Tue, Dec 30, 2014 at 6:36 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
personnally, I use invoker: no compatibility problems
I try to make unit tests when I can make unit tests. it's a religion,
or a disease. I agree that falling back to the invoker is the
fallback.
Regards,
Hervé
Le
Github user hboutemy commented on the pull request:
https://github.com/apache/maven/pull/34#issuecomment-68425530
The worst is that open implementation can change the status of objects by
any plugin: yes, the API wasn't meant to be defensive when it was created, we
could simply tell
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/34#issuecomment-68426777
Much of the shitiness stems from leaving things in such a way that nothing
was broken between Maven 2.x and 3.x. There are many weird interactions but the
overriding goal
I'm not convinced by the maven-builder-support artifact id
because Maven is a build tool, so I would expect builder support about Maven
builds (about parallel build strategies, and so on), not descriptors
rename to maven-desc-builder-support?
or even maven-desc-builder?
any better idea?
18 matches
Mail list logo
