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, I've had a couple of hardware
>
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 related maven-filtering patc
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 :
> H
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 have registered for
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...)
Kristi
+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:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=
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 Andreas,
>
> See Robert's cha
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]
>
> [IN
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 folks,
>
> Hervé is quite
Is there any way we can do this to avoid manual steps in the release
process ?
K
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
> > leaks in the code that was
hade-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 samedi 21 novembre 2015 15:13:15 K
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 point
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 :)
Having worked with 1.8 since long b
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
al #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 second case it is
> referenci
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 byt
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) {
System.out.println(
ases (warn before remove).
>
> Because the only issue I fear is this hack makes the shade plugin have support
> for other plugins leaks: it's probably not easy to know how much plugins have
> leaks...
>
> Regards,
>
> Hervé
>
> Le samedi 21 novembre 2015 10:16:51 Kar
s issues is caused by long Windows paths.
> INFRA made shorter file names and issue disappeared.
> Reported issue with Git 2.6.2 installation requirements and Git variable
> "core.longPaths=true" setup, see
> https://issues.apache.org/jira/browse/INFRA-10724.
>
> On Fr
ven-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.
>
> --
> Regards,
> Igor
>
ase 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
>> :
>>
>> > While working on MSHADE-171, I figured
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 META-I
+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&version=12333074
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-
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 quick and dirty chec
; stderr: warning: failed to remove surefire-integration-tests/target/
>
> It looks like we have some files in test which leak. Therefore I asked
> Gavin [1] to find out those files which are held by a process.
> [1] https://issues.apache.org/jira/browse/INFRA-10650
>
>
>
>
>
5-10-22 21:05 GMT+02:00
Subject: Re: to delete windows build ?
To: Andreas Gudian
Kopi: Kristian Rosenvold
>>Could it be the ancient shadefire-version that causes hanging processes in
>>our integration tests on those windows nodes?
I do not know since I could not reproduce this iss
+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 a écrit :
>> Hi,
>>
>>
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 Marbaise wrote:
>>
>> H
+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 are no pending issues I ca
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 <
> kristian.rosenv...@gmail.
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 :
> I created ht
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 :
> 2015-10-08 16:55 GMT+02:00 Tibor Digana :
>> @Kristian
>> Can we switch to other mail thread "surefire 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 matters, since it's really a go/
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 important is to see which proc
+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:
>
> https://issues.apache.org/jira/browse/MASSEMBLY-782?jql=project%20%3D%20MASSEMBLY%20AND%20status%20%
t;
>> 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:
>>
>>> Looking at
Just for building
2015-10-08 9:24 GMT+02:00 Anders Hammar :
> 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 at 9:06 AM, Kris
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, Tibor Digana wrote:
>
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 :
> Yesterday I clarified an iss
d 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
>> >>
>> >&g
+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?
> Nowadays the Maven support for
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 wh
:14, Kristian Rosenvold
> wrote:
>
>> FYI; I am setting up a full copy of asf svn (just 65GB) and will be trying
>> some imports once this is ready
>>
>
> How did this go?
-
To unsubscribe, e-mail:
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
> wrote:
>
>> Hi,
>>
>> Hervés arguments count
+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&version=12329010
>>
>> Changes since the last release:
>>
>> http://svn.apa
+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&version=12332813
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20
gt; 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
ux, 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+s40175n5844990...@n5.
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)
I
+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:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=
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" reques
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 pl
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 project
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" :
> after investigation (everything is described in details in MASSEMBLY-777),
> these exclusions were necessary when using File based filtering, cr
> 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" >
>>> mvn clean verify -Prun-its -Dinvoker.mavenHome
ght 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 :
>>
>> Op Tue, 14 Jul 2015 20:46:50 +0200 schreef Kristian Rosenvold <
>&
14. jul. 2015 21.04 skrev "Robert Scholte" 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 :)
ot a code change, so I 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 :
> Op Tue, 14 Jul 2015 20:46:50 +0200 schreef Krist
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.
Kristi
2015-07-14 20:06 GMT+02:00 Robert Scholte :
> 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 before your shared
Fyi: This seems to be the cause of our current grief on jenkins builds.
Kristian
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 :
> Maybe related
> https:/
Welcome !
K
2015-06-23 8:16 GMT+02:00 Hervé BOUTEMY :
> 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:
> >
+1
21. jun. 2015 21.14 skrev "Tibor Digana" :
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12331401
>
> There is still one issue left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resol
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) :
>
> [
> https://issues.apache.org/jira/browse/MINVOKER-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comme
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 :
> Under some unknown conditions the build fails on tests maven-shared-utils
> with command mvn
+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 :
> I would report a bug in 0.9 assign it to me and continue the vote.
> I believe you had such issue, but I trust the command mvn r
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 :
> Hi Tibor,
>
> i have a strange thing...
>
As long as each class is either sonatype-aether or eclipse-aether, it does
not really need reflection ?
K
Cool. I suppose not much other stuff uses that anyway :)
K
2015-06-13 22:22 GMT+02:00 Robert Scholte :
> 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 Rosenv
/constructors 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 Rosen
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 creat
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 :
> 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 that you can
> release the ear
The sections should be preserved though, so that's definitely a bug.
K
2015-06-07 19:17 GMT+02:00 Robert Scholte :
> 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 3.1.1
> 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 :
> 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, without anythi
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
suppor
rg/apache/maven/artifact/resolver/ArtifactResolver.html#49
>
>
> Op Sun, 07 Jun 2015 14:45:24 +0200 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
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
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 dis
+1
2015-06-01 7:06 GMT+02:00 Kristian Rosenvold :
> I'll re-publish the site tonight (vote stays open).
>
> Kristian
>
>
> 2015-05-31 21:42 GMT+02:00 Karl Heinz Marbaise :
>
>> Hi Kristian,
>>
>> checked SHA1 Ok.
>>
>> Checked wi
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
> We have the time to figure it out, communicate a plan, understand it and
> then implement 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,
someone has to do :)
Kristian
2015-06-01 17:12 GMT+02:00 Jason van Zyl :
> 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 &l
yl :
> 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 clo
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
:
> No, the maven-plugins repo i
vely figure it out. I really don’t see 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 prob
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 th
generated site has a little problem:
>
> 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 (
or you here?
>
> Regards
> Mirko
> --
> 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.
>
Hi,
We solved 3
issues:https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332381&styleName=Text&projectId=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
JIRA:https
hink putting components that have their
> > own 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
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
Known for its immensely agreeable traffic levels, this is the new google
group for plexus :)
https://groups.google.com/forum/#!forum/codehaus-plexus
Kristian
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 :
> I would love that... if I can avoid relearning more SVN I am all for it ;-)
>
> manfred
>
> Stephen Connolly wrote on 29.05.2015 07:56:
>
> > +1 for
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
+1
13. mai 2015 8.55 a.m. skrev "Hervé BOUTEMY" :
> 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 told he wants
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 :
> Maven committers,
>
> Jetbrains has graciously provided a project wide license for Apache
+1
9. mai 2015 09.15 skrev "Karl Heinz Marbaise" :
> 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
>> Mave
+1
6. mai 2015 6.57 p.m. skrev "Karl Heinz Marbaise" :
> 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:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1231
1 - 100 of 1154 matches
Mail list logo
