+1
/Anders
On Sun, May 29, 2016 at 12:07 AM, Karl Heinz Marbaise
wrote:
> Hi,
>
> We have solved 5 issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20fixVersion%20%3D%20maven-filtering-3.1.1
>
> There are still a couple of issues left in
+1
Found a new link error on the character encoding example page but that can
be fixed in a later release. I'll file a ticket.
Also, which I didn't notice during vote take 1, there is additonal logging
now on which files were copied (and also a weird row about delta) which
should IMO only be
+1
/Anders (mobile)
On May 15, 2016 23:24, "Michael Osipov" wrote:
> Hi,
>
> this component hasn't been touched for years effectively and we rely now
> on Maven for Maven (dog food). Additionally, Ant build support has already
> been removed from Maven. This relic shouldn't
+0, non-binding
I found a few minor issues with the plugin site that I filed tickets for,
to be fixed later.
However, I was thinking if we should seize the opportunity to remove some
user properties here as we did for the 3.0.0 release of the jar plugin.
Typically the resources plugin is always
Right, there is no IT in m-jar-plugun to check this. The tests are in the
library/component that handles this.
/Anders (mobile)
On May 7, 2016 23:06, "Robert Scholte" wrote:
> I'm using Win10
>
> The funny thing:
> Manifest-Version: 1.0
> Implementation-Vendor: The Apache
It works for me. Do you by any chance have an old staged 3.0.0 of the
plugin in your local repo?
/Anders (mobile)
On May 7, 2016 20:35, "Robert Scholte" wrote:
> https://issues.apache.org/jira/browse/MJAR-218
> is this really fixed?
>
> I still see a versionless Apache
+1, non-binding
/Anders
On Wed, May 4, 2016 at 8:16 PM, Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 21 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12334171
>
> There are still a couple of issues left in JIRA:
>
>
+1
/Anders (mobile)
On May 6, 2016 22:00, "Karl Heinz Marbaise" wrote:
> Hi to all,
>
> I would like to suggest to keep the version number of the plugins and
> shared components to the following format (and may be also things we are
> using like plexus?):
>
>
+1
/Anders
On Wed, Apr 27, 2016 at 7:57 PM, Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 1 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12335563
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1264
>
>
>
On Wed, Apr 27, 2016 at 3:17 PM, Anders Hammar <and...@hammar.net> wrote:
> Fixed. Now we need a 3.0.2 release of maven-archiver.
>
MJAR-218 created to track this.
/Anders
>
> /Anders
>
> On Wed, Apr 27, 2016 at 2:53 PM, Anders Hammar <and...@hammar.net> wrote:
Fixed. Now we need a 3.0.2 release of maven-archiver.
/Anders
On Wed, Apr 27, 2016 at 2:53 PM, Anders Hammar <and...@hammar.net> wrote:
> MSHARED-296 is something else. I'm talking about the manifest file. Se
> MSHARED-513 for more info. I'll fix it.
>
> /Anders
>
> On W
MSHARED-296 is something else. I'm talking about the manifest file. Se
MSHARED-513 for more info. I'll fix it.
/Anders
On Wed, Apr 27, 2016 at 2:30 PM, Michael Osipov <1983-01...@gmx.net> wrote:
>
> > -1
> > There seems to be a regression where the Created-By line in the manifest
> > now
Hi Anders,
> On 4/27/16 1:24 PM, Anders Hammar wrote:
>
>> -1
>> There seems to be a regression where the Created-By line in the manifest
>> now doesn't specify the Maven version but just "Apache Maven". I'll try to
>> figure out how this has happene
-1
There seems to be a regression where the Created-By line in the manifest
now doesn't specify the Maven version but just "Apache Maven". I'll try to
figure out how this has happened.
/Anders
On Wed, Apr 27, 2016 at 9:04 AM, Mirko Friedenhagen wrote:
> +1 from me,
+1
v3.0.0 is an excellent opportunity to do this I think!
/Anders
On Wed, Apr 20, 2016 at 9:48 AM, Robert Scholte
wrote:
> https://issues.apache.org/jira/browse/MJAR-183 should also be good to do
> now.
> that is: *copy* the lifecycle from core to the plugin.
> IIRC it
On Tue, Apr 19, 2016 at 9:27 PM, Robert Scholte
wrote:
> Hi,
>
> Not sure if this is the right moment, but I'd like to make finalName
> readonly for all packaging plugins.
> The reason: for some new features I probably need to know the name of the
> generated (main)
?
[1]
http://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/examples/create-test-jar.html
/Anders
On Tue, Apr 19, 2016 at 8:40 PM, Karl Heinz Marbaise <khmarba...@gmx.de>
wrote:
> Hi Anders,
>
> On 4/18/16 10:31 AM, Anders Hammar wrote:
>
>> I'm -1 as I think w
I'm -1 as I think we should handle MJAR-209 [1] in v3.0.0. Sorry for not
pushing that earlier, but I didn't know a release was imminent.
[1] https://issues.apache.org/jira/browse/MJAR-209
/Anders
On Sun, Apr 17, 2016 at 12:49 PM, Karl Heinz Marbaise
wrote:
> Hi,
>
> We
(MojoExecutor.java:216)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
>
> WDYT ?
>
> Kind regards
> Karl Heinz
>
>
>
> On 4/4/16 9:13 PM, Anders Hammar wrot
ram is no more supported (deprecated typically means it still works).
We will surely run into more cases like this (for example MEAR-228).
/Anders
>
>
>
>
>> /Anders
>>
>>
>> -- Forwarded message --
>> From: Anders Hammar (JIRA) <j...@apache.or
an exception could
simplify for the users. WDYT?
/Anders
-- Forwarded message --
From: Anders Hammar (JIRA) <j...@apache.org>
Date: Mon, Apr 4, 2016 at 8:50 PM
Subject: [jira] [Commented] (MJAR-210) Remove useDefaultManifestFile
parameter
To: iss...@maven.apache.org
[
Thanks for reporting! I filed a jira issue for this:
https://issues.apache.org/jira/browse/MNG-5989
/Anders
On Fri, Mar 4, 2016 at 11:19 PM, Bhowmik, Bindul
wrote:
> Hello,
>
> I ran across a few links on the documentation which should probably be
> updated. The pages
+1
Tested with Maven 3.2.5 and IBM JDK 7.1 on Windows 7.
/Anders
On Sat, Feb 6, 2016 at 8:25 PM, Andreas Gudian
wrote:
> Hi,
>
> We solved 3 issues (well, two of them deal with the same error):
>
>
Could someone with enough karma mark version 3.3.0 of the MPLUGINTESTING
JIRA project [1] as released?
I believe it was released on 2014-12-30 [2].
[1]
https://issues.apache.org/jira/browse/MPLUGINTESTING/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel
[2]
The github repo for maven-plugin-testing [1] seems to be a mirror of the
wrong git repo at Apache for the maven-plugin-testing. It's currently
mirroring [2] but it should be mirroring [3].
How do we change that?
[1] https://github.com/apache/maven-plugin-testing
[2]
>
> Then I think we are missing *user* extensions, that would be added in
> ${maven.home}/bin/m2.conf the same way as installation extensions, but
> pointing to ~/.m2/ext/*.jar
>
What would the benefit be of configuring this on installation level but
keep the jar in user space? How would that
My take is that if we bump version to 4.x we have to include some more
(major) features other than just a requirement of Java 8 as it doesn't
provide any real benefit for the user, which I'm sure they would expect
from a new major version.
If we would like to align Maven version with pom model
I've similar issues with the analyze. There are unused imports in the
source code (lazy devs) which aren't seen by the analyzer. Haven't looked
into the byte code, but guess it's the same issue as here.
/Anders
On Thu, Nov 26, 2015 at 9:25 AM, Kristian Rosenvold <
kristian.rosenv...@gmail.com>
That's how Maven core releases were done in the early v3.0.x days.
Personally I think it worked very good.
/Anders (mobile)
On Nov 15, 2015 15:40, "Benson Margulies" wrote:
> Given the number of 'burned' releases recently, I thought people might
> be interested in hearing
+1, tested with IBM JDK 7.1 on Windows 7
/Anders
On Thu, Nov 12, 2015 at 10:29 AM, Tibor Digana
wrote:
> +1: applied in private project and works just fine
>
> On Tue, Nov 10, 2015 at 6:16 PM, Jason van Zyl wrote:
>
> > Hi,
> >
> > Time to release
I second Robert comment here on not having everything configurable from
command line. It's not always good as the build will not be reproducible.
/Anders
On Mon, Nov 9, 2015 at 5:57 PM, Robert Scholte wrote:
> Hi Karl-Heinz,
>
> properties for arrays? How would that work?
Just to clarify, it's Oracle's JDK 1.7 that is EOL. IBM still supports
their Java 6 and 7 level JDKs.
Moving to a 1.7 default is still ok I think. However, if we think that most
people will still need to configure 1.8 (or 1.9 soon) I don't see the point
of doing this as it does introduce a level
You're right, this is the problem. What would need to be done is the
version to be fixed for the release version (tag).
/Anders (mobile)
Den 26 okt 2015 15:55 skrev "Benson Margulies" :
> Folks,
>
> I would appreciate some assistance in thinking through the
> implications
Takari has an incremental build API:
http://takari.io/2014/03/25/incremental-build.html
/Anders
On Mon, Oct 19, 2015 at 8:14 PM, Karl Heinz Marbaise
wrote:
> Hi,
>
> i would like to know if there exist an alternative for the above api ?
>
>
> Kind regards
> Karl Heinz
+1 non-binding
Tested with Maven 3.0.4 and IBM JDK 1.7 on a number of non-public projects.
/Anders
On Mon, Oct 19, 2015 at 1:19 PM, Jason van Zyl wrote:
> +1
>
> > On Oct 19, 2015, at 3:25 AM, Karl Heinz Marbaise
> wrote:
> >
> > Hi,
> >
> > We solved 7
do I have to manually put central in as a
> pluginRepository if I'm just trying to add one?
>
>
> On Fri, Oct 16, 2015 at 9:19 AM, Anders Hammar <and...@hammar.net> wrote:
> > It looks like a specific staging repo is accessed (look at the URL in the
> > end). As the parent ha
It looks like a specific staging repo is accessed (look at the URL in the
end). As the parent has been released it is no longer available there.
/Anders (mobile)
Den 16 okt 2015 15:01 skrev "Benson Margulies" :
> Maven-plugins 28 is released, of course; what's up? It
of JDK and fixes required from Users group.
>
>
>
> On Thu, Oct 8, 2015 at 9:04 AM, Anders Hammar <and...@hammar.net> wrote:
>
> > Why 3.0.5?
> >
> > We've had this discussion (in general for plugins) before and IIRC we
> > decided on 3.0.
> >
&
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:
> Do you agree to specify these build requirements in surefire POM?
>
>
> 3.0.5
>
>
> Updating
e to bugs in earlier versions.
>
> Kristian
>
>
>
>
> 2015-10-08 9:04 GMT+02:00 Anders Hammar <and...@hammar.net>:
> > Why 3.0.5?
> >
> > We've had this discussion (in general for plugins) before and IIRC we
> > decided on 3.0.
> >
> >
et of the trunk
> in there, possibly up to and including the current end of the trunk?
>
> On Mon, Oct 5, 2015 at 3:03 PM, Anders Hammar <and...@hammar.net> wrote:
> > I agree with Robert; it would be great to do lots of cleanup (remove
> > deprecated goals for starters) in a 3.0 ver
I believe there is a ticket that was closed in one of the big
close-all-old-tickets efforts. Someone then commented on that ticket that
it was still a problem in a newer Maven version and I asked him to create a
new ticket. Not sure if he did so or not.
/Anders (mobile)
Den 6 okt 2015 13:48 skrev
That ticket is not about the root cause I think.
/Anders (mobile)
Den 6 okt 2015 15:36 skrev "Michael Osipov" <1983-01...@gmx.net>:
>
>
> > Gesendet: Dienstag, 06. Oktober 2015 um 13:48 Uhr
> > Von: "Benson Margulies"
> > An: "Maven Developers List"
I agree with Robert; it would be great to do lots of cleanup (remove
deprecated goals for starters) in a 3.0 version. So doing a v2.6 now would
keep that option open.
/Anders
On Mon, Oct 5, 2015 at 8:23 PM, Robert Scholte wrote:
> IIRC for maven-assembly-plugin most of
+1 to retire.
/Anders
On Sun, Oct 4, 2015 at 5:48 PM, Tamás Cservenák wrote:
> +1 retire it
>
> On Sun, Oct 4, 2015, 17:01 Arnaud Héritier wrote:
>
> > +1 to retire it from Apache and to give it to MojoHaus where
> contributions
> > are easier if some
Joining this discussion...
Based on my experience when I joined, Maven core and maven plugins are
different beasts. Sure, if you understand the inner parts of Maven core it
is easier to understand plugins, but core also depends on many different
libraries which handle different aspects of the
Yes! Didn't we already decide on this? Or was it Java 7 even?
/Anders
On Wed, Sep 9, 2015 at 8:25 AM, Hervé BOUTEMY wrote:
> Hi,
>
> I'm preparing to make a release of Maven Parnet POM once MPIR 2.8.1 is out
> (since MPIR-300 is required).
>
> This release will require
I'd say yes. If someone dislikes your changes, they're free to step up and
do another change.
/Anders
On Tue, Jun 23, 2015 at 7:50 AM, Manfred Moser manf...@simpligility.com
wrote:
Hi!
I would like to start my cleanup of the Maven site with fixing
I agree with Jason, it would be better to keep this outside of core (the
core distro).
/Anders
On Thu, May 28, 2015 at 5:21 AM, Jason van Zyl ja...@takari.io wrote:
I honestly don't think an optional feature relying on an optional
dependency belongs in the core itself.
On May 27, 2015, at
+1
/Anders
On Wed, May 13, 2015 at 8:55 AM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
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
As I'm being mentioned here I'd like to clarify:
I'm able to build with an IBM JDK 1.6 (included with WAS 8.0.0.10) on
Windows 7. Some of the unit tests and int tests fail though, very likely
due to the fact that I'm currently behind a corp firewall/proxy.
Chris is on Windows XP I believe, and
Ok, the consensus is to move forward to Java7. I updated the POM and we're
in no rush so give it a whirl and we can think about releasing next week if
the world doesn't blow up.
Please create a JIRA ticket for this to make things clear in the release
notes.
/Anders
On Mar 5, 2015, at
I think this is what we decided on - support latest and one prior released
JDK version.
IF we do, we need to update the README file in the distro as well as the
system requirements page online.
/Anders
On Thu, Mar 5, 2015 at 1:19 PM, Igor Fedorenko i...@ifedorenko.com wrote:
With maven core
What I'd like to stress here is that we're talking about Maven core, not
our plugins. We've had a separate discussion/thread for the plugins and for
those we've decided to go with a Java 6 requirement.
As plugins were mentioned in this thread as well I want to make sure there
is no
that no one out there cares for Windows 98/ME
anyway
;-).
Am Donnerstag, 26. Februar 2015 schrieb Anders Hammar :
On Thu, Feb 26, 2015 at 8:16 AM, Stephen Connolly
stephen.alan.conno...@gmail.com javascript:; wrote:
On Thursday, February 26, 2015, Anders Hammar
and...@hammar.net
Just a heads up that the Codehaus services are coming to an end, see [1].
As there already was an discussion about moving our JIRA projects, we now
have a deadline for that, in May if I read the info correctly.
[1] http://www.codehaus.org/
/Anders
One thing we could do to make stuff easier around these .bat scripts is to
drop support for this 4NT shell and Windows versions that are not based on
NT (i.e. Windows 9x / ME).
Well, as Maven 3.2+ requires a minimum of JDK 1.6 there is no reason to
support anything that JDK 1.6 doesn't run
On Thu, Feb 26, 2015 at 8:16 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On Thursday, February 26, 2015, Anders Hammar and...@hammar.net wrote:
One thing we could do to make stuff easier around these .bat scripts is
to
drop support for this 4NT shell and Windows
A question was raised the otehr day if this shouldn't rather be v3.3.0, as
it seems to be new functionality rather than bug fixes. Your call though.
/Anders
On Tue, Feb 24, 2015 at 3:02 PM, Jason van Zyl ja...@takari.io wrote:
Ok, so it's been over 3 weeks :-) I have two branches I'm going to
I don't understand why http://jira.codehaus.org/browse/MNG-5767 was
integrated without a windows support ? For me it is everything or nothing.
I agree. All features of Maven should be available on all supported
platforms. And Windows is one of them [1].
[1]
Robert,
Wrt to the goal names, do we want the test-xxx syntax instead of
testXxx (used in m-compiler-p and m-resources-p)? test-xxx is used in
some other core plugins as well.
/Anders
On Sat, Feb 14, 2015 at 4:32 PM, Robert Scholte rfscho...@apache.org
wrote:
Hi,
during FOSDEM 2015 a few
Ouch that's an old one :-)
Yes I was interested to have a 2.3 release but we failed to find the
motivation/time to close 431
Yes, I hardly even remember this one. The code seems to be fixed except the
unit test. I'd say we should go for the easiest way so that we could close
this ticket.
be cleaned up.
/Anders
On Wed, Feb 4, 2015 at 3:43 PM, Anders Hammar and...@hammar.net wrote:
I'll have a look.
/Anders (mobile)
Den 4 feb 2015 14:03 skrev Benson Margulies bimargul...@gmail.com:
Gents, are you willing to do it and I'll just be RM?
On Wed, Feb 4, 2015 at 6:33 AM, Arnaud
I'll have a look.
/Anders (mobile)
Den 4 feb 2015 14:03 skrev Benson Margulies bimargul...@gmail.com:
Gents, are you willing to do it and I'll just be RM?
On Wed, Feb 4, 2015 at 6:33 AM, Arnaud Héritier aherit...@gmail.com
wrote:
+1
On Wed, Feb 4, 2015 at 10:18 AM, Anders Hammar
Sounds good to me. I especially like the Maven 3.0 (not 3.0.5) requirement.
/Anders
On Mon, Feb 2, 2015 at 12:42 PM, Karl Heinz Marbaise khmarba...@gmx.de
wrote:
Hi,
after some discussions at FOSDEM with Hervé, Kristian and Robert in
Brussels i will summarize some ideas we would like to
I strongly second that the maven-eclipse-plugin be retired. For us working
in Eclipse, the m2e integration is the way to go. Also, there has not been
any active work on that plugin for many years and I think we should clearly
indicate to the community that there is very little hope anyone would
Did we really decide/settle on that?
Having a four digit version will not play well with most (all?) tools that
list Maven artifacts. Just an ui issue, but still.
/Anders (mobile)
Den 31 jan 2015 12:18 skrev Jason van Zyl ja...@takari.io:
I'm not releasing an RC build. I will do more what I
Start in JavacCompiler.performCompile(). Depending on JDK version the
actual compilation is then done by that class or JavaxToolsCompiler.
/Anders
On Thu, Jan 29, 2015 at 9:48 AM, Anders Hammar and...@hammar.net wrote:
org.codehaus.plexus:plexus-compiler-javac
assuming you're using javac
org.codehaus.plexus:plexus-compiler-javac
assuming you're using javac.
https://github.com/sonatype/plexus-compiler/tree/master/plexus-compilers/plexus-compiler-javac/src/main/java/org/codehaus/plexus/compiler/javac
/Anders
On Wed, Jan 28, 2015 at 11:12 PM, Benson Margulies bimargul...@gmail.com
I would still suggest to make sure its documented somewhere. I find it
incredibly useful to just change M2_HOME to simply switch Maven versions.
+1, very useful but I guess it doesn't require the name M2_HOME.
/Anders
manfred
Mirko Friedenhagen wrote on 26.01.2015 21:40:
Dan, go
+1 non-binding
/Anders
On Sun, Jan 25, 2015 at 11:52 AM, Robert Scholte rfscho...@apache.org
wrote:
+1
Op Sat, 24 Jan 2015 16:22:26 +0100 schreef Karl Heinz Marbaise
khmarba...@gmx.de:
Hi,
We solved 9 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?
Tested with my internal projects.
Tested the source package with maven 2.2.1, 3.1.1, and 3.2.5 with java 6
under windows
maven 2.2.1 fails at
[ERROR] The following builds failed:
[ERROR] * analyze-multimodule-project\pom.xml
Yes, I saw that on Jenkins as well. I've just briefly
I've committed a fix for this. As I suspected it was not a plugin code
problem but something in the IT wrt Maven 2.2.1's faulty reactor.
Although thoroughly tested locally, let us wait for Jenkins to verify this.
A m2 build job is in the build queue.
/Anders
On Thu, Jan 22, 2015 at 7:15 PM,
Heinz Marbaise
On 1/18/15 3:04 PM, Karl Heinz Marbaise wrote:
Hi,
On 1/18/15 2:42 PM, Anders Hammar wrote:
MDEP-466 [1] is the regression I was talking about. The issue has been
fixed in source but it requires a new release of
maven-dependency-analyzer.
Ok...Than i will start VOTE for maven
An svn patch is the preferred way for a plugin hosted in svn.
http://maven.apache.org/guides/development/guide-maven-development.html
/Anders
On Tue, Jan 20, 2015 at 4:12 PM, twilliamso...@oreillyauto.com wrote:
This may or may not be a stupid question, but it's new territory for me
so I
Create an account on Xircles [1] and then file a JIRA ticket [2] with your
patch. Please include integration tests or similar to verify the new
functionality.
[1] https://xircles.codehaus.org/
[2] http://jira.codehaus.org/browse/MPMD
/Anders
On Mon, Jan 19, 2015 at 2:15 AM,
MDEP-466 [1] is the regression I was talking about. The issue has been
fixed in source but it requires a new release of maven-dependency-analyzer.
[1] https://jira.codehaus.org/browse/MDEP-466
/Anders
On Sun, Jan 18, 2015 at 10:22 AM, Anders Hammar and...@hammar.net wrote:
There's
There's a regression in the last release that would be great to have fixed
as well. I'm not by a computer right now though to dig up the jira.
/Anders (mobile)
Den 17 jan 2015 09:41 skrev Karl Heinz Marbaise khmarba...@gmx.de:
Hi,
On 1/17/15 6:16 AM, Henning Schmiedehausen wrote:
Hi,
any
+1 (non-binding)
Verified with m-dependency-p ITs.
/Anders
On Sun, Jan 18, 2015 at 3:34 PM, Karl Heinz Marbaise khmarba...@gmx.de
wrote:
Hi,
We solved 3 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?
projectId=11761version=20721
There are still a couple of issues left in
I've always been thinking we'd pick such stuff up from somewhere.
For surefire I've always figured test scope.
Wouldn't it be better to get it from the classpath of the mojo execution?
i.e. it should be added as a dep to the plugin declaration.
/Anders
A more general solution
would
In my f*g company we have surefire plugin and all plugins in top parent POM
with configuration stuff and dependencies. This way I cannot customize my
project because i don't have rights to change top parent POM.
I cannot say this module has this extension, this and this another because
the
Do you foresee any issues with use all available CPU cores when used on a
shared resource like CI server?
When writing guidelines for my customers' devs I'm always very firm on that
build jobs are not allowed to fork (or similar) freely and thereby
occupy more than their share of the resources on
TL;DR we should let the OS be responsible for applying resource limits, we
should use every resource we are given to the full in order to reduce the
build time as that shortens the feedback loop and makes developers mire
productive
I guess I agree. Guidelines doesn't work anyways as the
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
Awesome!
I know there are plugins over at Codehaus Mojo that uses tools.jar.
/Anders
On Thu, Dec 18, 2014 at 10:58 PM, Robert Scholte rfscho...@apache.org
wrote:
Hi all,
small update: I've fixed MANIMALSNIFFER-49
I've built Maven from trunk using the latest SNAPSHOT of the
B
/Anders
On Mon, Dec 15, 2014 at 11:39 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
After the run-off round, we are left with two names standing.
This second vote will be a straight and simple majority wins.
The vote will be open for at least 72 hours (with the potential
both types. But then I always advocate that one maven project
should only create one artifact...hmm.
/Anders
On Thu, Dec 11, 2014 at 8:55 AM, Paul Benedict pbened...@apache.org wrote:
Anders, like make a maven-zip-plugin project?
On Dec 11, 2014 1:50 AM, Anders Hammar and...@hammar.net wrote
K, B
/Anders
On Tue, Dec 9, 2014 at 11:52 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
This is a run-off vote to select the top two options for our new mascot's
name.
The entries with the highest number of votes will be selected for the final
round. If there is only one
I don't think that the zip package type should be part of Maven core, but
we could provide some plugin which provides for it as a custom packaging
type. Possibly this could be part of the assembly plugin.
/Anders
On Thu, Dec 11, 2014 at 7:33 AM, Paul Benedict pbened...@apache.org wrote:
Well
I think we should retire it. There hasn't been a release for almost three
years and there has just been very little code activity since then.
Retiring it would give the community a clear (and honest) indication that
we will not fix any issues in it.
/Anders
On Sun, Dec 7, 2014 at 1:05 AM, Barrie
I recently took a look at the release-profile in Maven's super POM.
It uses the jar goal of the maven-source-plugin to create the source
JAR. Wouldn't it be better to use the jar-no-fork goal for that?
sounds definitively like a good idea...to change that...
I have created an appropriate
I've been in the same position as you. My solution back then was to work on
Maven (and also some plugins) on my private MBP connecting to Internet
through other channels (an open guest network).
I don't know if the mrm-maven-plugin could solve some of this. It does for
plugin ITs, but is not used
+1
/Anders
On Tue, Nov 25, 2014 at 11:57 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
For anyone who has been living under a rock, here is the background
Background
=
I think everyone can agree that the site needs a reorganisation and a
rewrite. Users cannot find
I ran into something similar in the maven-war-project. Checking I see that
similar hard-coded values exist there:
On Mon, Nov 24, 2014 at 9:03 AM, Karl Heinz Marbaise khmarba...@gmx.de
wrote:
Hi,
so after diving more into this issue i found that the original
MavenProject is working different
Hmm, Googel decided to send my mail before I finished...
I ran into something similar in the maven-war-project. Checking I see that
similar hard-coded values exist there:
Here's the link:
I showed the latest pic for a fellow developer (who hasn't seen the earlier
ones) and he said he thinks it looks like the bird's been shot. So the
shotgun owl is probably the nickname we will have to live with. :-)
But I want to stress that I think it's great work you're doing!
/Anders
On Thu,
the emphasis on the feather outlines and use the inner body
for the inner colour... note that we need to switch away from red as a
central red section just looks like blood)
On 20 November 2014 09:57, Anders Hammar and...@hammar.net wrote:
I showed the latest pic for a fellow developer (who hasn't
This I am basically trying to explain them as well. They are newbies and
the
funny thing is that they are ignoring us. My proposal was to serve a
contact
of Maven PMC experts so that they would pay for new environment, build
process, POM structures, and CI systems setup but again with no
I've been working with/on a plugin for talking to github, and I'm
staring at some fairly complex code for processing proxy information
from settings.xml, and some slightly less complex code for obtaining
and decrypting credentials from servers.
Is there a shared component in which I put
...@gmail.com
wrote:
Well, see https://github.com/benson-basis/github-release-note-maven-plugin
for the code I have. Is this the sort of thing you're talking about?
On Mon, Nov 10, 2014 at 2:57 PM, Anders Hammar and...@hammar.net wrote:
I've been working with/on a plugin for talking
101 - 200 of 568 matches
Mail list logo