+1
did run it the last 2 days on many of my projects without any issues.
LieGrue,
strub
- Original Message -
> From: Brian Fox
> To: Maven Developers List
> Cc:
> Sent: Tuesday, 4 June 2013, 18:13
> Subject: Re: [VOTE] Apache 3.1.0-alpha-1 (Take 4)
>
> +1
>
> On Sat, Jun 1, 2013
+1
LieGrue,
strub
- Original Message -
> From: Andreas Gudian
> To: Maven Developers List
> Cc:
> Sent: Friday, 7 June 2013, 8:29
> Subject: [VOTE] Release Maven Surefire Plugin version 2.15
>
> Hi,
>
> This is my first release, so please check carefully what I may have missed
> :
I found that most people use
false and
true
Which renders most of the stuff useless in GIT.
LieGrue,
strub
- Original Message -
> From: Fred Cooke
> To: Maven Developers List
> Cc:
> Sent: Saturday, 10 August 2013, 15:19
> Subject: Re: What is the correct Git SCM URL for a branc
+1, that's what we also use in DeltaSpike and dozen other projects.
pushChanges=false + localCheckout=true for the win!
LieGrue,
strub
- Original Message -
> From: Arnaud Héritier
> To: Maven Developers List
> Cc:
> Sent: Saturday, 14 September 2013, 19:45
> Subject: Re: Leaving Ma
e the tag if they want during the
> release. I can't keep it on my machine until the vote passes.
>
> On Sep 14, 2013, at 2:20 PM, Mark Struberg wrote:
>
>> +1, that's what we also use in DeltaSpike and dozen other projects.
>> pushChanges=fal
wrote:
>
>> We need a slight modification of this strategy because the changes need to
>> be pushed somewhere so that people can examine the tag if they want during
>> the release. I can't keep it on my machine until the vote passes.
>>
>> On Sep 14, 2013, at
e VOTE has
succeeded.
LieGrue,
strub
>
> From: Fred Cooke
>To: Maven Developers List ; Mark Struberg
>
>Sent: Saturday, 14 September 2013, 21:43
>Subject: Re: Leaving Maven Core POMs at major.minor-SNAPSHOT
>
>
>
>I believe the str
se bugs against a non-exist any version!
>>
>> On Saturday, 14 September 2013, Jason van Zyl wrote:
>>
>> > We need a slight modification of this strategy because the changes
> need
>> to
>> > be pushed somewhere so that people can examine the tag if th
+1
LieGrue,
strub
- Original Message -
> From: Stephen Connolly
> To: Maven Developers List
> Cc:
> Sent: Saturday, 5 October 2013, 9:35
> Subject: Re: Maven Core moving to 1.6
>
> +1
>
>
> On Saturday, 5 October 2013, Jason van Zyl wrote:
>
>> Given the vote we had about relea
+1
LieGrue,
strub
> On Monday, 3 February 2014, 11:21, Stephen Connolly
> wrote:
> > +1
>
> spot checks to confirm that Robert beat me to my standard tests: pass
>
>
>
> On 2 February 2014 11:11, Robert Scholte wrote:
>
>> +1
>>
>> rat: only approved licenses
>> sha1: correct
>>
+1
LieGrue,
strub
On Thursday, 13 February 2014, 18:42, Andreas Gudian
wrote:
+1
>
>:-)
>
>Am Donnerstag, 13. Februar 2014 schrieb Hervé BOUTEMY :
>
>> +1
>>
>> Regards,
>>
>> Hervé
>>
>> Le jeudi 13 février 2014 15:14:03 Stephen Connolly a écrit :
>> > We have not made a release of Maven
+1 (binding)
src looks good, did a small local test release on a simple project which did
run fine.
txs and LieGrue,
strub
On Sunday, 23 February 2014, 15:50, Benson Margulies
wrote:
Hi,
>
>maven-release is a component that provides the maven-release-manager
>and the maven-release-plugi
+1
and thanks for pushing this, Dennis!
LieGrue,
strub
> On Saturday, 8 March 2014, 23:50, Dennis Lundberg wrote:
> > Hi,
>
> We solved 15 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127&styleName=Html&version=19723
>
> There are still a couple of issues left i
+1
LieGrue,
strub
> On Thursday, 6 March 2014, 22:19, Hervé BOUTEMY wrote:
> > Hi,
>
> Changes since the last release:
> http://svn.apache.org/viewvc/maven/pom/tags/apache-14/pom.xml?r1=HEAD&r2=1434717&diff_format=h
>
> Staging repo:
> https://repository.apache.org/content/repositories/o
+1
LieGrue,
strub
> On Saturday, 8 March 2014, 17:13, Hervé BOUTEMY wrote:
> > +1
>
> Regards,
>
> Hervé
>
> Le jeudi 6 mars 2014 22:08:10 Robert Scholte a écrit :
>> Hi,
>>
>> We solved 5 issues:
>>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=187
>> 29
+1 (binding)
LieGrue,
strub
On Wednesday, 12 March 2014, 22:53, Andreas Gudian
wrote:
Hi,
>
>long ago since we released the last Surefire version. It's about time we
>change that ;-).
>
>We solved 16 issues:
>https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=19536
+1
LieGrue,
strub
> On Thursday, 1 May 2014, 10:22, Kristian Rosenvold
> wrote:
> > +1
>
>
>
> 2014-05-01 6:48 GMT+02:00 Olivier Lamy :
>
>> my +1
>>
>>
>> On 29 April 2014 15:24, Olivier Lamy wrote:
>> > Hi,
>> > I'd like to release Apache Maven Shade Plugin 2.3.
>> > The main
Hi!
Building with Java8 breaks buiding JavaDocs many existing maven projects.
And thus most times also breaks releasing them.
The reason is that they enabled all warnings and errors now by default.
This means that we get tons of oddly broken builds because it also breaks for
missing @param, etc
ld could have failed due to the changes of the javadoc executable.
>Add to that message the xdoclint options to get the original behavior.
>
>regarding the parent, we probably also want to add -reference ( as
>suggested by one of the Oracle developers )
>
>thanks,
>Robert
>
k Derricutt wrote:
>> > On 4 Jul 2014, at 9:33, Robert Scholte wrote:
>> >> If I'm correct, following have joined at least 2 times or are Maven PMC
>> >> 22:00-23:00 (CEST) Robert Scholte, Hervé Boutemy, Karl-Heinz Marbaise,
>> >> Mark Struberg
>
Hi folks!
Looking at massembler right now I stumbled across a parentPom section
maven-plugins
org.apache.maven.plugins
33
../../pom/maven/maven-plugins/pom.xml
This was perfectly fine when we had all in SVN under one big project.
But nowadays - having all in GIT - I'd we should remove
Hi!
Feeling a bit rusty, so I thought I better ask for a 2nd opinion.
To me it looks like the following code block is really obsolete and did not
make anything useful ever since
https://github.com/apache/maven-assembly-plugin/blob/master/src/main/java/org/apache/maven/plugins/assembly/archive/t
rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>
>
> Le jeu. 19 déc. 2019 à 14:39, Mark Struberg a
&
+1
LieGrue,
strub
> Am 16.12.2019 um 19:37 schrieb Hervé BOUTEMY :
>
> Hi,
>
> We solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924&version=12346480&styleName=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1545/
>
t;>
>>>> Robert
>>>> On 21-12-2019 12:33:53, Hervé BOUTEMY wrote:
>>>> disagree
>>>>
>>>> We have the repo configuration which brings a location for every Git
>>>> repository:
>>>> https://maven.apache.org/scm.htm
But the main purpose is not to have multiple frameworks run with it. That's the
main difference to surefire.
The maven-checkstyle-plugin is rather pretty much hardcoded to a specific
checkstyle version. While you _could_ technically exchange the checkstyle
dependency it is not really intended.
Hi lords and ladies!
I try to get my head around the ticket MASSEMBLY-775.
It is related to MASSEMBLY-746 and MASSEMBLY-665.
The problem is basically that a reference to /somedirectory is
interpreted as absolute path on *nix and as relative path on Win*.
And sometimes we have code of the form
hould be interpreted as an absolute
> path, and AFAIK the warning is there already for ages so I don't mind
> changing the behavior.
>
> thanks,
> Robert
> On 1-1-2020 23:26:00, Mark Struberg wrote:
> Hi lords and ladies!
>
> I try to get my head around the ticke
+1
LieGrue,
strub
> Am 05.01.2020 um 18:45 schrieb Hervé BOUTEMY :
>
> Hi,
>
> We solved N issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12343925&styleName=Text
>
> https://github.com/apache/maven-apache-parent/compare/apache-21...apache-22
>
> S
I'll try to give it a look over the weekend.
LieGrue,
strub
> Am 16.01.2020 um 23:31 schrieb Falko Modler :
>
> Hi Karl Heinz,
>
> thanks for this clarification.
>
> So now there is only one last ticket left for 3.2.2 and the PR for it
> looks good to be merged:
> https://github.com/apache/ma
+1
Thanks Hervé, was on my list for the next weeks as well ;)
LieGrue,
strub
> Am 09.02.2020 um 10:24 schrieb Hervé BOUTEMY :
>
> Hi,
>
> We solved 28 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=1230&styleName=Text
>
> Staging repo:
> http
Don't we configure those patterns mostly directly in the poms?
Ditching our own DirectoryScanner would likely require a huge amount of
existing projects to rewrite their config when they update some plugins.
Don't think this is really worth it. Plus the Java7 directoryScanner is not
really faste
+1 for dropping. Also already had problems with it.
LieGrue,
strub
> Am 01.12.2020 um 17:50 schrieb Romain Manni-Bucau :
>
> Up,
>
> Encountered a few bugs related to this regression, wonder how we want to
> tackle it.
> My 2cts would be to drop cdi-api and replace the single used
> annotation
+1
LieGrue,strub
On Sunday, 24 January 2021, 00:02:35 CET, Sylwester Lachiewicz
wrote:
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223&version=12347024&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apa
@Inject
private Logger??? logger;
That would imo depend on the package of the Logger in the import. There could
be producers for both our internal maven logging api and SLF4J.
LieGrue,strub
On Friday, 22 January 2021, 19:19:47 CET, Slawomir Jaranowski
wrote:
It is not only a
+1Technically from a pure ClassLoader point our very own makes more sense.We
can probably think about Lambda to resolve the String lazily.Insofar the SLF4J
api is outdated as well.
And of course internally we might still route to slf4j. But we should not
expose those classes to the plugins if n
Hiho!
I will attend and arrive monday morning. Sigfried Göschl will also be in
Budapest.
LieGrue,
strub
> On Wednesday, 5 November 2014, 9:32, Tamas Cservenak
> wrote:
> > Don’t worry about the details. All the kidnapped people will get what they
> deserve ;)
>
> Thanks,
> ~t~
>
>
> On
+1
really like the new logo (or better any of those owls).
LieGrue,
strub
> On Tuesday, 25 November 2014, 12:02, Arnaud Héritier
> wrote:
> > +1
>
> thx
>
>
> On Tue, Nov 25, 2014 at 11:57 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>> +1
>>
>> On 25 November
Hi!
Today I had a discussion with Robert about how we can solve a problem I had
over at Apache OpenWebBeans:
https://issues.apache.org/jira/browse/OWB-952
As a short summary: the classes provided in rt.jar of Java8 are slightly
different than the ones from Java7 and 6. Similar big differences
Hi!
> This lets you selectively forbid certain methods
The problem is that the methods used are perfectly fine. The API methods used
in our program do exist even in Java6. But they get coerced to different
methods when compiling with Java8. And those new methods do not exist in Java7
and ol
+1 if they like to use Mavens infrastructure then they also need to play
according to those rules.
Anyone likes to talk with the Ivy guys? They have to fix this.
Another question is what we do with those existing poms in maven.central? Do we
convert them? What about sha1, md5 and asc in that c
;>the like.)
>>- Have a factory class, with code like the following:
>>
>>private static final IRTUser instance = newRTUser();
>>
>>private static IRTUser newInstance() {
>> try {
>>return new JDK18RTUser();
>> } catch (Throwable t0)
Hi Paul!
Txs, this is definitely one possible direction in which we could aim.
LieGrue,
strub
> On Saturday, 29 November 2014, 11:18, Paul Moloney
> wrote:
> > Hi
>
> I had written this rule for the enforcer plugin which actually checks the
> label of jdk version in toolchains against out
works fine over here.
rat fine as well.
+1
LieGrue,
strub
> On Thursday, 8 January 2015, 21:21, Karl Heinz Marbaise
> wrote:
> > Hi,
>
> We solved 12 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150&version=20681
>
> There are still a couple of issues left in
Hi Martin!
The maven-compiler plugin already does this. But once a single change is
detected then we need to recompile the _whole_ module because of the reasons
explained by Igor.
Pro of JDT: you can e.g. also see if there were only 'internal' changes and
thus the other dependencies don't need
Hi!
I'm quite confused by the sheer amount of libs we already have in our lib
folder. For maven-3.2.1 this is
133957 7. Mai 2013 aether-api-0.9.0.M2.jar
12637 14. Feb 2014 aether-api.license
34117 7. Mai 2013 aether-connector-wagon-0.9.0.M2.jar
12637 14. Feb 2014 aether-connector-wagon.license
1
+1
LieGrue,
strb
> Am 19.04.2015 um 14:28 schrieb Robert Scholte :
>
> Hi,
>
> We solved 13 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824&version=12331215
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=p
maybe I missed some change, but I cannot run mvnDebug anymore. It nicely says
that I start in debug mode, but doesn’t open a debug port and neither doesn’t
wait for me to attach.
Anything I missed, or is this really a regression?
txs and LieGrue,
strub
> Am 22.04.2015 um 14:22 schrieb Jason
rue,
strub
> Am 24.04.2015 um 14:08 schrieb Jason van Zyl :
>
> Working fine here. The scripts haven't changed since the end of February.
>
> Anyone else confirm an issue with remote debugging?
>
> On Apr 24, 2015, at 3:24 AM, Mark Struberg wrote:
>
>> maybe I
that's where we changed the scripts.
>
> I'm using your exact MAVEN_OPTS and it's working here to startup and debug in
> Eclipse.
>
> On Apr 24, 2015, at 8:20 AM, Mark Struberg wrote:
>
>> Re-tested with 3.3.2 and it doesn’t work there neither on my box.
+1 sounds like a plan.
LieGrue,
strub
> Am 24.04.2015 um 18:55 schrieb Andreas Gudian :
>
> In the windows script, I introduced a new variable for the debug settings -
> perhaps we can do the same for the shell scripts.
>
> Am Freitag, 24. April 2015 schrieb Francisco Collao Gárate :
>
>> Yep
+1
The problem I have with mvnDebug on OSX cmd line seems to be there in older
3.3.x versions already. So 3.3.3 is at least better than 3.3.2. We should
really fix this in the next version. But otherwise the release looks good.
LieGrue,
strub
> Am 25.04.2015 um 23:45 schrieb Mark Derricutt :
set MAVEN_SKIP_RC=1 when invoking mvn
>> with the combined MAVEN_OPT setting. This should stop it getting reset in
>> the mvn script and allow the debug settings to pass through.
>>>
>>> On Apr 26, 2015, at 2:12 AM, Mark Struberg >> (mailto:strub...@yahoo.de)> w
+1
only did simple checks (work) and checked source. looks good so far
LieGrue,
strub
> Am 27.04.2015 um 16:52 schrieb Kristian Rosenvold
> :
>
> +1
> 27. apr. 2015 16.01 skrev "Stephen Connolly" <
> stephen.alan.conno...@gmail.com>:
>
>> +1 (you beat me to my vote on core, but you can have
indeed, then it passed twice ;)
LieGrue,
strub
> Am 27.04.2015 um 17:01 schrieb Jason van Zyl :
>
> You have checked Maven 3.3.3 so really you have already checked Wagon 2.9 :-)
>
> On Apr 27, 2015, at 10:59 AM, Mark Struberg wrote:
>
>> +1
>>
>> only
+1
tested with 2 projects without issues.
LieGrue,
strub
> Am 24.04.2015 um 21:08 schrieb Karl Heinz Marbaise :
>
> Hi,
>
> We solved 10 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&version=12329009
>
> Staging repo:
> https://repository.apache.org/cont
nope, go on you even have 4 already:
Kristian, Jason, you, me
http://people.apache.org/committers-by-project.html#maven-pmc
LieGrue,
strub
> Am 27.04.2015 um 20:37 schrieb Karl Heinz Marbaise :
>
> Hi,
>
> here is my +1.
>
> need two more binding VOTES...
>
> Kind regards
> Karl Heinz Marb
+1 on Manfred, even thought he is already^^
LieGrue,
strub
PS: usually committer votes are held on the private lists…:wq
> Am 13.05.2015 um 17:13 schrieb Stephane Nicoll :
>
> +1
>
> S.
>
> On Wed, May 13, 2015 at 8:55 AM, Hervé BOUTEMY
> wrote:
>
>> Hi,
>>
>> I'd like to introduce Manfred
+1
LieGrue,
strub
> Am 08.06.2015 um 12:32 schrieb Jason van Zyl :
>
> +1
>
>> On Jun 7, 2015, at 6:15 AM, Karl Heinz Marbaise wrote:
>>
>> Hi,
>>
>> We solved 14 issues:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12331393
>>
>> There are still a c
Hi folks!
Having dozen sub repos in GIT is still a PITA.
Also git-submodules is still sub-optimal and at best a smallish helper.
For me personally there is one major decision point if it comes to deciding
whether to hav one big repo or multiple smaller ones: the deliverable.
Is there exactly o
> I like this idea of avoiding force pushing, but I'm not git expert to know
> exactly if this gives exactly the intended result = start clean and not
> have noise when doing bisects or git blame
It's clean for our own repo but might probably screw up cloned repos as they
cannot just git-pull an
+1
LieGrue,
strub
- Original Message -
> From: Stephen Connolly
> To: Maven Developers List
> Cc:
> Sent: Friday, March 16, 2012 1:10 PM
> Subject: Re: [VOTE] Apache Maven Shade Plugin 1.6
>
> +1
>
> -Stephen
>
> On 15 March 2012 09:56, Olivier Lamy wrote:
>> Hello,
>> I'd like
+1
yess, markdown 4twin!
txs Dennis!
LieGrue,
strub
- Original Message -
> From: Olivier Lamy
> To: Maven Developers List
> Cc:
> Sent: Thursday, April 12, 2012 10:19 AM
> Subject: Re: [VOTE] Release Maven Doxia version 1.3
>
> +1
>
> 2012/4/10 Dennis Lundberg :
>> Hi,
>>
>> W
rat fine, deps fine, pgp fine, artifacts look ok. Source Release [1] also ok
+1
LieGrue,
strub
[1]
https://repository.apache.org/content/repositories/maven-112/org/apache/maven/scm/maven-scm/1.7/maven-scm-1.7-source-release.zip
- Original Message -
> From: Hervé BOUTEMY
> To: Mave
did use it on a few big projects without hitting a problem. Artifacts look
good,
+1
LieGrue,
strub
- Original Message -
> From: Stephane Nicoll
> To: Maven Developers List
> Cc:
> Sent: Sunday, April 29, 2012 10:03 PM
> Subject: Re: [VOTE] Apache Maven Compiler Plugin 2.4
>
> +1
we can get a release out of the door soon.
LieGrue,
strub
- Original Message -
> From: Robert Scholte
> To: Maven Dev ; Mark Struberg
> Cc:
> Sent: Sunday, April 29, 2012 11:11 PM
> Subject: Re: [RELEASE] sparse release:perform with DSCM and
> -DlocalCheckout=true
please look at the openjpa-maven-plugin [1].
Check the following classes: OpenJpaEnhancerMojo.java,
OpenJpaTestEnhancerMojo.java and AbstractOpenJpaMojo.java
Here are the important parts:
/** * List of all class path elements that will be searched for the *
persistence-enabled classes and reso
n Mon, 30 Apr 2012 12:19:25 +0100 (BST)
> Mark Struberg wrote:
>
>> please look at the openjpa-maven-plugin [1].
>> Check the following classes: OpenJpaEnhancerMojo.java,
> OpenJpaTestEnhancerMojo.java and AbstractOpenJpaMojo.java
>>
>> Here are the important pa
+1 (binding)
Just a small note:
Please always also link to the source-release as this is what the ASF primarily
ships. All other artifacts are only nice to have goodies (in the legal aspect).
https://repository.apache.org/content/repositories/maven-053/org/apache/maven/release/maven-release/2.
activation is king ;)
The reason why it got removed is obvious: you needed to know exactly what goes
into it. Without that info you sometimes could not even compile your project.
What you can try nowadays is to create profiles (maybe in your parent pom) and
have them activated via a system pro
Sorry to hear that you have no fun hacking here anymore.
But just to share some thoughts about the groovy-maven stuff. I can certainly
see that there was lots of bad timing around on both sides in those days. But
the argument for _not_ checking this in to maven 1:1 was mainly because this
featu
I only have those profiles in my projects. The only profile I have in my
settings.xml is for enabling staging repos.
Do you have a sample so we get an idea what you try to solve?
LieGrue,
strub
- Original Message -
> From: Jochen Wiedmann
> To: Maven Developers List ; Mark St
@java.lang.Deprecated misses not only the description text but also a 'since'
field.
It would be really important to know since when a method is deprecated...
LieGrue,
strub
- Original Message -
> From: Olivier Lamy
> To: Maven Developers List
> Cc:
> Sent: Thursday, May 10, 2012 9
for the next time.
>>
>> -Robert
>>
>>
>> Op Fri, 11 May 2012 00:17:30 +0200 schreef Robert Scholte
>> :
>>
>>> Hi,
>>>
>>> The vote has passed with the following result :
>>>
>>> +1 (binding): Olivier L
+1
LieGrue,
strub
- Original Message -
> From: Lukas Theussl
> To: Maven Developers List
> Cc:
> Sent: Friday, May 11, 2012 11:56 AM
> Subject: Re: [VOTE] Release maven-changes-plugin 2.7.1
>
>
> +1
>
> -Lukas
>
>
> Benson Margulies wrote:
>> Hi,
>>
>> We solved 1 issues: MCH
Hi!
Sorry that I didn't have more time yesterday night, so I missed the most
important question:
Is the @Component annotation meant to be used on the component itself (for
defining the factory rule, like @ApplicationScoped) or is it used on the
InjectionPoint like @Inject?
Or is it like a @Qu
> Nothing is done at maven execution time (as we will need some core
> changes for that) and IMHO this could slow execution.
This depends on whether we do a full ClassPath scan or still have some parts in
the XML.
With e.g. CDI it would also be possible to use the existing plugin.xml and
provid
+1
LieGrue,
strub
- Original Message -
> From: Anders Hammar
> To: Maven Developers List
> Cc:
> Sent: Tuesday, May 22, 2012 11:22 AM
> Subject: Re: [VOTE] Apache Maven Invoker Plugin 1.6 (take 3)
>
> +1 (non-binding)
>
> Thanks Olivier!
>
> /Anders
>
> On Mon, May 21, 2012 at 4:
JSR-330 knows the @Qualifier meta annotation. (@Named is a @Qualifier itself)
Thus it would be perfectly possible to create a @Role Qualifier:
@Qualifier
public @interface @Role {
value();
hint() default "";
}
Note: the role is usually the Interface, thus we do not need it in most cases
as
+1
LieGrue,
strub
- Original Message -
> From: Olivier Lamy
> To: Maven Developers List
> Cc:
> Sent: Thursday, May 31, 2012 11:37 AM
> Subject: [VOTE] Release Maven Compiler plugin 2.5.1
>
> Hi,
> I'd like to release Maven Compiler plugin 2.5.1 to fix a backward
> compatibility iss
gimme a few minutes, reviewing...
LieGrue,
strub
- Original Message -
> From: Benson Margulies
> To: Maven Developers List
> Cc:
> Sent: Thursday, May 31, 2012 12:45 PM
> Subject: maven-shade-1.7
>
> I need two more votes ...
>
>
+1
source looks good, test with 1 of my projects was fine, gpg and hashes are ok.
License and Notice files do fit, deps are IP clean.
LieGrue,
strub
- Original Message -
> From: Benson Margulies
> To: Maven Developers List
> Cc:
> Sent: Monday, May 28, 2012 2:33 PM
> Subject: [VOT
And there are plenty in SCM and release ;)
Of course, it got much better already as Robert and Olivier (and a few others)
did some great work on it in the last few months.
LieGrue,
strub
- Original Message -
> From: Stephen Connolly
> To: Maven Developers List
> Cc:
> Sent: Thursda
+1
LieGrue,
strub
- Original Message -
> From: Kristian Rosenvold
> To: Maven Developers List
> Cc:
> Sent: Sunday, July 29, 2012 10:45 PM
> Subject: [VOTE] Release Maven Surefire Plugin version 2.12.1
>
> Hi,
>
> This is a bugfix release.
>
> We solved a few issues:
>
> Bug
>
>
quick local site build works fine.
+1
LieGrue,
strub
- Original Message -
> From: Hervé BOUTEMY
> To: Maven Developers List
> Cc:
> Sent: Thursday, August 2, 2012 8:38 PM
> Subject: Re: [VOTE] Release Maven Stylus Skin version 1.5
>
> PING
>
> Le lundi 30 juillet 2012 23:00:22 Her
looked at the diffs and they do look fine.
+1
LieGrue,
strub
- Original Message -
> From: Olivier Lamy
> To: Maven Developers List
> Cc:
> Sent: Friday, August 10, 2012 3:52 PM
> Subject: [VOTE] Release Maven Parent pom 22, Maven Plugins Parent pom 23,
> Maven Shared Components 18
+1
LieGrue,
strub
- Original Message -
> From: Stephen Connolly
> To: Maven Developers List
> Cc:
> Sent: Monday, August 13, 2012 9:47 AM
> Subject: Re: [VOTE] Maven Shared Filtering 1.1 - Maven Script Interpreter 1.1
> - Maven Invoker Plugin 1.7
>
> +1
>
> On 10 August 2012 05:56
Hi folks!
After a short discussion with Kristian, I've created a small app with 2 modules
which shows a few problems with mavens incremental build logic.
And since incremental builds do not work well, people use
$> mvn _clean_ install
all the time.
We could speed up the development effort heav
leA
>
> does? So your idea is to find the list of changed modules and then build
> that
> list with -amd?
>
> thanks
> david jencks
>
> On Aug 25, 2012, at 1:32 PM, Mark Struberg wrote:
>
>> Hi folks!
>>
>> After a short discussion
how do we maintain the plexus-compiler-utils stuff? This contains some
weirdo bugs which should get fixed...
- Original Message -
> From: Olivier Lamy
> To: Maven Developers List ; Mark Struberg
>
> Cc:
> Sent: Monday, August 27, 2012 9:13 AM
> Subject: Re: improving
+1
key looks fine, source builds fine, reports ok in my project.
LieGrue,
strub
- Original Message -
> From: Stephen Connolly
> To: Maven Developers List
> Cc:
> Sent: Monday, August 27, 2012 9:53 AM
> Subject: Re: [VOTE] Release Maven Project Info Reports Plugin version 2.5.1
>
>
su changed the 'container' field from plexus original:
> protected to 'private')
>>
>> PPS: how do we maintain the plexus-compiler-utils stuff? This contains some
> weirdo bugs which should get fixed...
>>
>>
>>
>> - Original Me
the following: compiling a bit too much is
> better than
>> >> missing some files which need compilation. Because the later is
> exactly
>> the
>> >> reason why noone uses mvn compile but always do a mvn clean
> compile
>> nowadays. If
>> &g
s List ; Mark Struberg
>
> Cc:
> Sent: Monday, August 27, 2012 12:24 PM
> Subject: Re: improving incremental builds
>
>> +0 for auto detecting changed scenarios. If someone changes a profile or
> the whole pom, then I'd expect he invokes a clean manually. We have
be that we compile too much. Thats still
better than a full mvn clean install :)
LieGrue,
strub
- Original Message -
> From: Benson Margulies
> To: Maven Developers List ; Mark Struberg
>
> Cc:
> Sent: Monday, August 27, 2012 5:07 PM
> Subject: Re: improving
>Cc: Mark Struberg
>Sent: Monday, August 27, 2012 8:11 PM
>Subject: Re: improving incremental builds
>
>
>On 27 August 2012 19:10, Stephen Connolly
>wrote:
>
>On 27 August 2012 18:09, Benson Margulies wrote:
>>
>>On Mon, Aug 27, 2012 at 12:07 PM, Mark Str
>
> From: Stephen Connolly
>To: Maven Developers List ; Mark Struberg
>
>Sent: Monday, August 27, 2012 9:53 PM
>Subject: Re: improving incremental builds
>
>
>The issue (for benson) is when the shade plugin modifies after the class file
from trunk
- Original Message -
> From: Mark Struberg
> To: Maven Developers List
> Cc:
> Sent: Monday, August 27, 2012 10:04 PM
> Subject: Re: improving incremental builds
>
>t he shade plugin would just need to store a local status file with the md5 of
> the
new MavenCLI parameters:
$> mvn -i test
"-i" for 'build Incrementally'
resp xor
$> mvn -ni test
"-ni" for 'build Non-Incrementally'
Not sure what the default should be though...
From the backward compat point probably -ni
LieGrue,
strub
- O
; To: Maven Developers List ; Mark Struberg
>
> Cc:
> Sent: Monday, August 27, 2012 11:13 PM
> Subject: Re: improving incremental builds
>
> Mark, I don't see how this helps. If the jar plugin hasn't rebuilt the
> jar, the shade plugin can't rebuild the jar, ev
1 - 100 of 583 matches
Mail list logo
