Re: Speeding up Maven

Just make sure you're not running low on entropy on your linux box, all sorts of weird slowdowns happen then. https://major.io/2007/07/01/check-available-entropy-in-linux/ Kristian 2018-04-16 11:28 GMT+02:00 Mark Raynsford : > With absolutely impeccable timing,

Re: Questions about how to contribute to Plexus

I will take a look at your interpolation pr's this weekend unless someone picks it up before. Kristian 2016-09-01 0:46 GMT+02:00 Gabriel Belingueres : > Hi Robert: > > Regarding Plexus components, I created a couple of pull requests on > plexus-interpolator (and some

Re: [SUREFIRE] Surefire provider for JUnit 5?

Hi, Benedikt :) JUnit 5 provider is cool, yes please :) Providers have different language levels (the different modules have different language levels), and I am sure we can build with jdk8. jdk8 still supports the target 1.6, right ? Kristian 2016-08-27 11:23 GMT+02:00 Benedikt Ritter

Re: Contributing to Apache Maven

Just to be clear about this; only actual committers on the project are allowed to assign an issue to themselves. If you want to fix an issue you will just need to attach a patch to the jira or a pull request. Kristian 2016-06-30 12:30 GMT+02:00 Stian Soiland-Reyes : > If you

Re: Maven Memory Consumption

I somehow assume the original patch that caused this behaviour was created due to memory leaks in embedded mode. Do de have any way to handle both ? (I'm wondering if we have any scope that is bound to the current embedsed execution) (I'm all i favour of this change no matter what...)

Re: migrating Surefire to 3.0-RC1

I would recommend that you instead update the existing wiki page that we use to gather "tips" about migrating plugins: https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies Kristian 2016-01-08 1:18 GMT+01:00 Tibor Digana : > Hi

Re: [VOTE] Release Apache Maven Shade Plugin version 2.4.3

+1 2016-01-07 18:59 GMT+01:00 Tibor Digana : > `+1 > > On Wed, Jan 6, 2016 at 10:05 PM, Tibor Digana-2 [via Maven] < > ml-node+s40175n5858080...@n5.nabble.com> wrote: > > > Hi, > > > > We solved 4 issues: > > > > >

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19.1 - TAKE 2

Verify does not work with surefire. K 31. des. 2015 15.52 skrev "Karl Heinz Marbaise" : > Hi Tibor, > > i have tried to test with Maven 3.0.5 via mvn -Prun-its clean verify and > got the following message: > > [INFO] >

Automating upload(commit) to "dist" area ?

Is there any way we can do this to avoid manual steps in the release process ? K

Re: Retiring Maven Skins

Yes! +2 2015-12-24 11:03 GMT+01:00 : > yes, that's a good cleanup > > Regards, > > Hervé > > - Mail original - > De: "Michael Osipov" <1983-01...@gmx.net> > À: dev@maven.apache.org > Envoyé: Mercredi 23 Décembre 2015 21:30:28 > Objet: Retiring Maven Skins > > Hi

Re: to delete windows build ?

gt; > Regards, > > Hervé > > Le vendredi 18 décembre 2015 07:53:19 Kristian Rosenvold a écrit : > > As long as shade is not released and updated it will probably come back. > > > > I actually checked all the plugins for file leaks and there were no other > > le

Re: to delete windows build ?

tweak seems about internal m-shade-p leaks: in such > > conditions, > > now that leaks are fixed, yes, let's just remove the code (or fix the > > plugin if > > another leak is found later) > > > > Regards, > > > > Hervé > > > > Le sa

Re: [DISCUSS] Java version requirement for Mavan 3.4.x

The new module can/may require jdk8. It may even be possible to build the provider with an older jdk - it depends on what they do in JUnit 8; most of the lambda stuff can be used from older versions - but if they expose jdk8 types on public api's there's not much alternative. From a practical

Re: [DISCUSS] Java version requirement for Mavan 3.4.x

2015-12-02 9:38 GMT+01:00 Stephen Connolly : > If we look at our JVM company history, IIRC > > 2.0 = Java 1.4 > 2.1 = Java 1.4 > 2.2 = Java 1.5 > 3.0 = Java 1.5 > 3.1 = Java 1.6 > 3.2 = Java 1.6 > 3.3 = Java 1.7 > > It looks like 3.4 will be 1.7 and 3.5 1.8 :)

Re: [DISCUSS] Java version requirement for Mavan 3.4.x

Technically, JDK8 is entirely undramatic for maven; I'm having a hard time understanding why it should trigger any api changes or any other "4.0" reasons. I cannot make heads or tails of the supposed versioning policy, the language is too convoluted for me or I'm just not smart enough. If we are

Re: Why can't dependency plugin "see" statics /and staticimports

t; > 24: invokevirtual #10 // Method > java/io/PrintStream.println:(Ljava/lang/String;)V > > 27: return > > } > > > So what I see there is that in the first case javac has inlined the > constant and converted it to a string... in the secon

Re: Why can't dependency plugin "see" statics /and staticimports

Let me be more precise here; the dependency:analyze seems to miss a whole group of references to static fields. Both static imports and references to fields. In my code sample, I can do the following: javap -v bar/BarMain.class Classfile bar/BarMain.class Last modified 25.nov.2015; size 583

Why can't dependency plugin "see" statics /and staticimports

I poked around in the depdenedncy analyzer code to see if I could make it "see" the following code: Module 1: public class Test2 { public static final int AZAZ = 42; } Module 2: import foo.Test2; public class BarMain { public static void main(String[] args) {

Re: to delete windows build ?

; No.. >> >> > Kristian >> > >> > 5. nov. 2015 5.29 p.m. skrev "Tibor Digana" <tibor.dig...@googlemail.com>: >> >> This issues is caused by long Windows paths. >> >> INFRA made shorter file names and issue disappe

Re: to delete windows build ?

NFRA-10724. > > On Fri, Oct 23, 2015 at 6:22 AM, Kristian Rosenvold < > kristian.rosenv...@gmail.com> wrote: > > > (Tibor; I'm taking this to the mailing list) > > > > > > It would appear that we are leaking file handles/resources when being > > kill

Re: Shade plugin from directories instead of jars in multimodule builds ?

-- > [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ > mshade171-base --- > > > Although jar:jar sets project artifact file to packaged jar, the second > compiler:compile compile invocation sets it back to target/classes > folder. > > -- > Rega

Shade plugin from directories instead of jars in multimodule builds ?

While working on MSHADE-171, I figured I'd take a stab at making shade work from the "target" folder instead of just the assembled finished jar. I implemented this, and it works kinda-ok, but then I realized that I'm not producing the same output as I would from "package", since there is no

Re: Shade plugin from directories instead of jars in multimodule builds ?

t" run at all. What phase is the plugin bound to in your project? > > -- > Regards, > Igor > > On Sat, Nov 14, 2015, at 06:45 AM, Robert Scholte wrote: >> Op Sat, 14 Nov 2015 11:53:41 +0100 schreef Kristian Rosenvold >> <kristian.rosenv...@gmail.com>: >>

Re: [VOTE] Maven 3.3.9

+1 2015-11-10 18:16 GMT+01:00 Jason van Zyl : > Hi, > > Time to release Maven 3.3.9! > > Here is a link to the issues resolved: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12333074 > > Staging repo: >

Re: [VOTE] Maven 3.3.8

Amazing flute section ! ROFL :) K 2015-11-02 23:46 GMT+01:00 Jason van Zyl : > One more time > > https://www.youtube.com/watch?v=ry4ngf766N0 > > > On Nov 2, 2015, at 7:26 AM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > > > Well I was asked to remove the

Fwd: to delete windows build ?

com> Date: 2015-10-22 21:05 GMT+02:00 Subject: Re: to delete windows build ? To: Andreas Gudian <andreas.gud...@gmail.com> Kopi: Kristian Rosenvold <kristian.rosenv...@gmail.com> >>Could it be the ancient shadefire-version that causes hanging processes in >>our integratio

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19 (Take 2)

+1 2015-10-18 10:48 GMT+02:00 Hervé BOUTEMY : > +1 > (I don't know how I checked this release with its checksum but voted on the > wrong thread... but for sure, I'm voting on the second take only :) ) > > Regards, > > Hervé > > Le jeudi 15 octobre 2015 03:48:00 Tibor Digana

Re: Maven Core Branch Cleanup

Anyone wishing to retain these branches can just go ahead and fork the girhub repo, they' 2015-10-12 20:20 GMT+02:00 Jason van Zyl : > You can nuke all my branches. They are either integrated, irrelevant, or easy > to recreate. > >> On Oct 12, 2015, at 2:11 PM, Karl Heinz

Re: [VOTE] Release Apache Maven maven-plugin parent-pom version 28

+1 11. okt. 2015 2.56 a.m. skrev "Benson Margulies" : > Hi, > > 2 changes in JIRA. Many other commits. > > > ** Bug > * [MPOM-88] - yyy-LATEST deployment URL breaks site parent reference > menu > * [MPOM-89] - Unbalanced versions of Maven Invoker Plugin > > There

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19

oot cause. The only problem was with unterminated JVM using > non-daemon Threads in tests. > I will cancel the Vote, delete the staging repo and tag. I will test the > plugin in another real project and I will make improvements. > > On Thu, Oct 8, 2015 at 8:44 PM, Kristian Rosenvold <

Re: Maven and JDK requirements in Surefire

Just for building 2015-10-08 9:24 GMT+02:00 Anders Hammar <and...@hammar.net>: > Ok, just to build or to use as well? > > 'prerequisites' is for usage. maven-enforcer-plugin with > requireMavenVersion=[3.0.5,) is for building. > > /Anders > > On Thu, Oct 8, 2015

Re: Maven and JDK requirements in Surefire

Surefire requires 3.0.5 to build, due to bugs in earlier versions. Kristian 2015-10-08 9:04 GMT+02:00 Anders Hammar : > Why 3.0.5? > > We've had this discussion (in general for plugins) before and IIRC we > decided on 3.0. > > /Anders > > On Thu, Oct 8, 2015 at 8:43 AM,

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19

te: >> >> I keep it open, because the CI pass. >> We next time should discuss stacktrace investigations in a separate >> thread. >> >> On Thu, Oct 8, 2015 at 7:11 AM, Kristian Rosenvold < >> kristian.rosenv...@gmail.com> wrote: >> >>

Re: [VOTE] Release Apache Maven Assembly Plugin version 2.6

+1 2015-10-06 15:41 GMT+02:00 Benson Margulies : > Hi, > > We solved 1 issues: > > ** New Feature > * [MASSEMBLY-780] - Snappy supported > > There are still a couple of issues left in JIRA: > >

Re: surefire 2.19 hangs

This was on linux. I'll try to diagnose later tonight K 8. okt. 2015 5.32 p.m. skrev "Arnaud Héritier" : > When I was using windows I remember that unlocked was my friend : > http://www.emptyloop.com/unlocker/ > Maybe there are others tools nowadays … > The most

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19

2015-10-08 16:55 GMT+02:00 Tibor Digana : > @Kristian > Can we switch to other mail thread "surefire 2.19 hangs". I dont necessarily think this is a good idea. We are discussing a candidate for a release, and I believe this is the appropriate place to discuss these

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19

process ? We'll continue in the jira. I'm definitely -1 on this release until we can sort this out. Kristian 2015-10-08 18:54 GMT+02:00 Kristian Rosenvold <kristian.rosenv...@gmail.com>: > 2015-10-08 16:55 GMT+02:00 Tibor Digana <tibordig...@apache.org>: >> @Kristian >>

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19

I identified the commit that caused the breakage, cb97ba70cb9ebe685f8f2a06e87b538795b5dd9b. I dont have further time to find the bug right now, but I suspect this should be enough to find the problem. Kristian 2015-10-08 19:09 GMT+02:00 Kristian Rosenvold <kristian.rosenv...@gmail.com>

Re: [VOTE] Release Apache Maven Surefire Plugin version 2.19

Looking at the change it applies only to a single IT for a specific type of environment setting; are you keeping this vote open or respinning ? (Personally I think it's ok to keep it open if I understand it right) Kristian 2015-10-07 22:35 GMT+02:00 Tibor Digana :

Re: [VOTE] Retire Maven Eclipse Plugin / Donation to Mojohaus

+1 retire it 4. okt. 2015 11.19 a.m. skrev "Robert Scholte" : > Hi, > > during the latest upgrade of the plugin-parent I faced several issues with > the maven-eclipse-plugin. > It will take quite some time to fix these issues, but is it worth > maintaining it here? >

Re: Releasing the assembly plugin

e >> >> deprecated code. For that reason I ask in general: please do a >> >> pre-announcement when going for a plugin 3.0 release, so we can have a >> good >> >> and critical look at it. >> >> >> >> thanks, >> >> Robert

Re: Releasing the assembly plugin

Personally I'd release 3.0.0 and stuff whatever nit-picky requirements are not met. Revert any changes that depends on code that is not yet ready for release. I think ultimately the large list of requirements is a nice way to just halt all progress. It'll be at least a jdk 1.6 release no matter

Re: Full migration to Git

com>: > On 3 June 2015 at 18:14, Kristian Rosenvold <kristian.rosenv...@gmail.com> > wrote: > >> FYI; I am setting up a full copy of asf svn (just 65GB) and will be trying >> some imports once thi

Re: FOSDEM 2016

Jan 30-31 is in the prime skiing season. No can do :) Kristian 2015-09-27 22:25 GMT+02:00 Arnaud Héritier : > I think that Jenkins will be here too, thus I hope to have the opportunity > to come > > On Sun, Sep 27, 2015 at 7:13 PM, Robert Scholte >

Re: [VOTE] Release Apache Maven Parent POM version 27

+1 2015-09-21 13:21 GMT+02:00 Olivier Lamy : > +1 > > On 21 September 2015 at 07:06, Hervé BOUTEMY wrote: > >> Hi, >> >> We solved 13 issues: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12329010 >> >> Changes since the

Re: [VOTE] Release Apache Maven Shared Utils version 0.9 - TAKE 2

+1 2015-09-17 22:12 GMT+02:00 Tibor Digana : > Hi, > > We solved 4 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12332813 > > There are still a couple of issues left in JIRA: >

Re: [VOTE] Release Apache Maven Shared Utils version 0.9

. > I will install Linux, but now I have to spend the time on surefire release > till the EO September. > > [1] mvn release:prepare -DdryRun=true > [2] mvn release:prepare -DskipTests > > > > On Wed, Sep 16, 2015 at 9:11 AM, Kristian Rosenvold-4 [via Maven] < > ml-node+

Re: [VOTE] Release Apache Maven Shared Utils version 0.9

Tibor; Which operating system did you use when running the release ? I'm probably a bit slow since I'm the last person in the universe to realize this: Symlinks cannot really be checked into git/svn if we are to support releases from windows. (If the release is run on macos/linux it will be ok)

Re: [VOTE] Release Apache Maven Shared Utils version 0.9

e troubles with making the release. >>> I will install Linux, but now I have to spend the time on surefire >>> release >>> till the EO September. >>> >>> [1] mvn release:prepare -DdryRun=true >>> [2] mvn release:prepare -DskipTests &

Re: [VOTE] Release Apache Maven Shared Utils version 0.9

+1 Note that I also added https://issues.apache.org/jira/browse/MSHARED-436 as fixed to the release, increasing the issues to 4. Kristian 2015-09-15 23:22 GMT+02:00 Tibor Digana : > Hi, > > We solved 3 issues: >

Read timeout from repository ?

We are discussing (in https://issues.apache.org/jira/browse/MNG-5869) what appears to be a situation where an intermediate proxy sends an incorrect content-length and the download seems to wait indefinitely for the complete payload to await. Is there no timeout configured for a default get request

Interleaving forks/tests

I've been thinking about the way surefire forks JVMs for all the scenarios where it forks a new JVM per testcase; right now we basically start one JVM, load the surefire provider and run the test. Then we shut down the JVM. Repeat until done. Since we have a 2-way comms channel between the main

Re: [VOTE] Maven 3.3.5

You still do not have any publicly available project to reproduce this ? Every time you complain about this I have compared 3.0.5 and 3.3.3, and every time I get the same result; 3.3.3 might have about 10% more allocated objects overall when compared to 3.0.5. There is something about your

Re: Intend to release maven-assembly-plugin 3.0.0

I also only have 4 failing ITs to fix wrt removing the deprecated goals. One heck of a job though... K 18. jul. 2015 1.33 a.m. skrev Hervé BOUTEMY herve.bout...@free.fr: after investigation (everything is described in details in MASSEMBLY-777), these exclusions were necessary when using File

Re: Intend to release maven-assembly-plugin 3.0.0

:) Now it is clear for everybody. Robert Op Wed, 15 Jul 2015 08:43:59 +0200 schreef Kristian Rosenvold kristian.rosenv...@zenior.no: 14. jul. 2015 21.04 skrev Robert Scholte rfscho...@apache.org mvn clean verify -Prun-its -Dinvoker.mavenHome=d:\apache-maven-3.0 fails on my machine

Re: Intend to release maven-assembly-plugin 3.0.0

14. jul. 2015 21.04 skrev Robert Scholte rfscho...@apache.org mvn clean verify -Prun-its -Dinvoker.mavenHome=d:\apache-maven-3.0 fails on my machine We are 3.0.3/4/5 minimum, which I believe is in accordance with our discussions. Cant remember exactly which versjon though :)

Re: Intend to release maven-assembly-plugin 3.0.0

:50 +0200 schreef Kristian Rosenvold kristian.rosenv...@gmail.com: 2015-07-14 20:06 GMT+02:00 Robert Scholte rfscho...@apache.org: Hi Benson, this is not the 3.0 version of a plugin I had in mind. For instance, it isn't compatible with all Maven3 versions and there's still a lot

Re: Intend to release maven-assembly-plugin 3.0.0

cant veto it. But it's as silly as it gets. I thought o.a.m.plugins was /supposed/ to be there, at least that's what I renamed everything to ? Kristian 2015-07-14 21:03 GMT+02:00 Robert Scholte rfscho...@apache.org: Op Tue, 14 Jul 2015 20:46:50 +0200 schreef Kristian Rosenvold

Re: Intend to release maven-assembly-plugin 3.0.0

2015-07-14 20:06 GMT+02:00 Robert Scholte rfscho...@apache.org: Hi Benson, this is not the 3.0 version of a plugin I had in mind. For instance, it isn't compatible with all Maven3 versions and there's still a lot of cleanup to do[1] It's compatible with all 3.x versions, but I did this

Re: Intend to release maven-assembly-plugin 3.0.0

I have already updated this requirements to maven 3.x and moved the version to 3.0.0. If you for some reason think Benson requires to jump through some special hoops for legacy support on this I'd find that largely amusing, given the versioning strategy we have been discussing wrt 3.x move.

Apache infrastructure and java6; https://issues.apache.org/jira/browse/BUILDS-85

Fyi: This seems to be the cause of our current grief on jenkins builds. Kristian

Re: JAR/WAR file wasting memory if building with Maven

Note that the memory leak was fixed in 2.10.3 in https://github.com/codehaus-plexus/plexus-archiver/issues/6 . Issues #5 which Igor mentioned may or may not be the same problem. (Btw 3.x has not yet received this fix...) K 2015-07-02 23:25 GMT+02:00 Igor Fedorenko i...@ifedorenko.com:

Re: svn commit: r1686969 - /maven/pom/trunk/maven/pom.xml

Welcome ! K 2015-06-23 8:16 GMT+02:00 Hervé BOUTEMY herve.bout...@free.fr: Welcome Manfred! Regards, Hervé Le mardi 23 juin 2015 05:30:37 mmo...@apache.org a écrit : Author: mmoser Date: Tue Jun 23 05:30:37 2015 New Revision: 1686969 URL: http://svn.apache.org/r1686969 Log:

Re: [VOTE] Release Apache Maven Verifier Component version 1.6

+1 21. jun. 2015 21.14 skrev Tibor Digana tibordig...@apache.org: Hi, We solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922version=12331401 There is still one issue left in JIRA:

Re: [jira] [Commented] (MINVOKER-187) Cloned IT project must be writable

I am a bit surprised the proposed fix does the trick; I thought perforce checked out *every file* read only ? Kristian 2015-06-19 17:22 GMT+02:00 Karl Heinz Marbaise (JIRA) j...@apache.org: [

Re: [VOTE] Release Apache Maven Shared Utils version 0.8

+1 This has probably been released a couple of times already in this state, so my 2NOK is just to make an issue. Kristian 2015-06-17 13:29 GMT+02:00 Tibor Digana tibordig...@apache.org: I would report a bug in 0.9 assign it to me and continue the vote. I believe you had such issue, but I

Re: [VOTE] Release Apache Maven Shared Utils version 0.8

It's because the symlinks dont get packaged properly as a symlink inside source-jar. This is probably because an old version of maven-assembly-plugin has been used when building the source-jar Kristian 2015-06-17 10:09 GMT+02:00 Karl Heinz Marbaise khmarba...@gmx.de: Hi Tibor, i have a

Re: Broken build on maven-shared-utils

I fixed the root cause by upgrading assembly-plugin to 2.5.5 in r1686055, which includes proper symlinks in the zip. Did you make an issue for this ? Kristian 2015-06-17 15:10 GMT+02:00 Tibor Digana tibordig...@apache.org: Under some unknown conditions the build fails on tests

Does maven-artifact-transfer really need to use reflection ?

As long as each class is either sonatype-aether or eclipse-aether, it does not really need reflection ? K

Re: svn commit: r1685226 - in /maven/plugins/trunk/maven-assembly-plugin/src: main/java/org/apache/maven/plugin/assembly/artifact/ test/java/org/apache/maven/plugin/assembly/archive/phase/ test/java/o

I looked at maven-artifact-transfer and the code seems to be focused on install/deploy. The description tag in the project also says An API to either install or deploy artifacts with Maven3 It would appear we should either change the description of the project (to include download) or create a

Re: svn commit: r1685226 - in /maven/plugins/trunk/maven-assembly-plugin/src: main/java/org/apache/maven/plugin/assembly/artifact/ test/java/org/apache/maven/plugin/assembly/archive/phase/ test/java/o

etc. First intention was indeed install/deploy, but then I discovered I had to do more. So let's change the description and let this become that main aether-neutral project. Robert Op Sat, 13 Jun 2015 20:55:51 +0200 schreef Kristian Rosenvold kristian.rosenv...@gmail.com: I looked

Re: svn commit: r1685226 - in /maven/plugins/trunk/maven-assembly-plugin/src: main/java/org/apache/maven/plugin/assembly/artifact/ test/java/org/apache/maven/plugin/assembly/archive/phase/ test/java/o

Cool. I suppose not much other stuff uses that anyway :) K 2015-06-13 22:22 GMT+02:00 Robert Scholte rfscho...@apache.org: Hervé already worked on the graph-stuff. It's part of the shared maven-dependency-tree. Robert Op Sat, 13 Jun 2015 22:02:44 +0200 schreef Kristian Rosenvold

Re: Unable to Update to DOXIA 1.6 (latest)

I generally try to avoid more than 2, but hey - time to break records ! Kristian 2015-06-10 13:02 GMT+02:00 Stephen Connolly stephen.alan.conno...@gmail.com : The only issue is if there is a problem in one of the projects then you may need to respin all four... if you frame your vote email so

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

S; if you cannot add a class-path element to the manifest then ? You're wrong. Kristian 2015-06-07 19:09 GMT+02:00 Karl Heinz Marbaise khmarba...@gmx.de: Hi Igor, On 6/7/15 6:57 PM, Igor Fedorenko wrote: If I provide custom jar manifest, I expect the manifest to be used as-is,

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

The jar specification says explicitly that Attributes which are not understood are ignored.; I interpret this to mean it's ok for every man and his dog to add values. Which I think means that you should expect your *values* to win, not necessarily your particular file - there's an implicit support

Re: MANIFEST Handling in maven-jar-plugin / maven-archiver / plexus-archiver

The sections should be preserved though, so that's definitely a bug. K 2015-06-07 19:17 GMT+02:00 Robert Scholte rfscho...@apache.org: The following attributes are very handsome to be able to reproduce a build based on sources Built-By: kama Build-Jdk: 1.7.0_21 Created-By: Apache Maven

Re: 3.0 versions in branches ?

schreef Kristian Rosenvold kristian.rosenv...@gmail.com: Do we really need to keep the 3.0 versions in branches ? Can't we just make a branch if we need to fix something in the 2.x range ? Kristian - To unsubscribe, e-mail

3.0 versions in branches ?

Do we really need to keep the 3.0 versions in branches ? Can't we just make a branch if we need to fix something in the 2.x range ? Kristian

[ANN] Apache Maven Assembly Plugin 2.5.5 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Assembly Plugin, version 2.5.5 The Assembly Plugin for Maven is primarily intended to allow users to aggregate the project output along with its dependencies, modules, site documentation, and other files into a single

[RESULT][VOTE] Release Apache Maven Assembly Plugin version 2.5.5

Hi, The vote has passed with the following result: +1 (binding): Jason, Karl, Kristian +1 (non binding): none. I will promote the artifacts to the central repo and continue the release

Re: [VOTE] Release Apache Maven Assembly Plugin version 2.5.5

+1 2015-06-01 7:06 GMT+02:00 Kristian Rosenvold kristian.rosenv...@gmail.com: I'll re-publish the site tonight (vote stays open). Kristian 2015-05-31 21:42 GMT+02:00 Karl Heinz Marbaise khmarba...@gmx.de: Hi Kristian, checked SHA1 Ok. Checked with Maven 2.2.1, 3.0.5, 3.2.5, 3.3.3

Re: Full migration to Git

it. Personally, I can't ever see a retrospective cleanup happening. We have the time and opportunity to do it right, why would we not take it? -Chris On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The real problem here is maven-shared and maven-plugins, which

Re: Full migration to Git

The real problem here is maven-shared and maven-plugins, which need to be rewritten quite heavily. The existing git mirrors may be used as a starting point for filtering operations, but I suspect retaining history is going to be quite a lot of work when splitting the repos. We should not defer

Re: Full migration to Git

it being an issue given how much Git knowledge we have between us all and the Mojo migration to Github. On Jun 1, 2015, at 8:13 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The real problem here is maven-shared and maven-plugins, which need to be rewritten quite heavily

Re: Full migration to Git

...@takari.io: Ok, let’s look around I’m sure folks have gone from monorepo setups to individual project setups. I doubt we’re the first to attempt this. On Jun 1, 2015, at 10:28 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: git clone https://github.com/apache/maven-plugins.git

Re: Full migration to Git

git clone https://github.com/apache/maven-plugins.git cd maven-plugins ls -al git checkout maven-shade-plugin-2.2 ls -al The root gets rewritten on the tags. Not nice. Mojo did not have this issue. Kristian 2015-06-01 16:27 GMT+02:00 Kristian Rosenvold kristian.rosenv...@gmail.com

Re: Full migration to Git

to do :) Kristian 2015-06-01 17:12 GMT+02:00 Jason van Zyl ja...@takari.io: I wasn’t but that’s good. If you wanted to run the clone again is that an issue? We just figure out the best way and then do it to all of them. On Jun 1, 2015, at 10:48 AM, Kristian Rosenvold kristian.rosenv

Re: Releasing entire maven-shared as a single release ?

-- Sent from my mobile Am 31.05.2015 10:38 schrieb Kristian Rosenvold kristian.rosenv...@gmail.com: Oh well, I suppose what I /really/ want to fix is making combined releases work. K 2015-05-31 10:05 GMT+02:00 Mirko Friedenhagen mfriedenha...@gmail.com: +1 for Jason's procedure

[VOTE] Release Apache Maven Assembly Plugin version 2.5.5

Hi, We solved 3 issues:https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332381styleName=TextprojectId=12317220 This release fixes a somewhat nasty regression in 2.5.4 when creating jar files. Still 2.2.1 jdk 1.5 compatible. There are still a couple of issues left in

Re: [VOTE] Release Apache Maven Assembly Plugin version 2.5.5

: http://maven.apache.org/plugins-archives/maven-assembly-plugin-LATEST/ The list of xsd's is a little bit screwed upbut this will not prevent to continue with the release. Created an appropriate issue for it...MASSEMBLY-770 (Fixed.) On 5/31/15 6:36 PM, Kristian Rosenvold wrote: Hi

Re: Releasing entire maven-shared as a single release ?

unique lifecycle into their its own repository is more the direction we need to go in. Grouping everything together and releasing them together I believe runs counter to having a good separation of concerns in general. On May 30, 2015, at 11:03 AM, Kristian Rosenvold kristian.rosenv

Releasing entire maven-shared as a single release ?

I've been wondering if we should just give every component in maven-shared the same version number and always release all of the modules at the same time ? (this would influence an upcoming git migration) Kristian

Re: Full migration to Git

I really dont even know how to use svn any more, so it's just irritating. All git is the way to go. K 2015-05-29 19:08 GMT+02:00 Manfred Moser manf...@mosabuam.com: I would love that... if I can avoid relearning more SVN I am all for it ;-) manfred Stephen Connolly wrote on 29.05.2015

codehaus-plexus google group

Known for its immensely agreeable traffic levels, this is the new google group for plexus :) https://groups.google.com/forum/#!forum/codehaus-plexus Kristian

Re: logging during multithreaded builds

I know it's not directly related, but any general purpose algorithm that captures to memory buffers needs an overflow to disk mechanism - every time a ByteArrayOutputStream is used for this, some guy with a *huge* output from his build gets an OOM. It's nice you're looking into this issue. As for

Re: [VOTE] Add Manfred Moser as committer

+1 13. mai 2015 8.55 a.m. skrev Hervé BOUTEMY herve.bout...@free.fr: Hi, I'd like to introduce Manfred Moser as committer for the Apache Maven project. He's working on Android Maven plugin for years, has great discussions both on users and dev MLs, has a great attitude. And he's just

Re: IDEA licenses for Maven committers

It would appear there's a limit to the number of licenses: This invitation for *IntelliJ IDEA* by *Jason van Zyl* cannot be accepted. No assets left. Kristian 2015-05-12 13:20 GMT+02:00 Jason van Zyl ja...@takari.io: Maven committers, Jetbrains has graciously provided a project wide

Re: [VOTE] Maven Site upgrade to maven-fluido-skin 1.4

+1 9. mai 2015 09.15 skrev Karl Heinz Marbaise khmarba...@gmx.de: Hi, here is my +1.. at least one more binding VOTEs... Kind regards Karl Heinz Marbaise On 5/7/15 7:59 PM, Karl Heinz Marbaise wrote: Hi, i would like to update our main page http://maven.apache.org/ to the new Maven

Re: [VOTE] Release Apache Maven Fluido Skin Version 1.4 (Take 2)

+1 6. mai 2015 6.57 p.m. skrev Karl Heinz Marbaise khmarba...@gmx.de: Hi, i need two more binding VOTEs... Kind regards Karl Heinz Marbaise On 5/3/15 8:57 PM, Karl Heinz Marbaise wrote: Hi, We solved 10 issues:

Migrating to maven 3 deps

Do we have any wiki page describing the migration steps that would be recommended to move a plugin from 2.2.1 deps to 3.x deps ? I'm thinking *both* in terms of avoiding deprecations and other troubles that may arise ? Kristian

  1   2   3   4   5   6   7   8   9   10   >