Do you agree to specify these build requirements in surefire POM?
3.0.5
Updating README.txt in GitHub.
Adding configuration of maven-enforcer-plugin with requireMavenVersion=[3.0.5,)
and removing in every POM:
${mavenVersion}
Configuring maven-plugin-plugin:
2.
Thanks for the quick answer :)
You can contact INFRA on hipchat http://infra.chat/ to get test environment
for plugin :)
On Thu, Oct 8, 2015 at 12:32 PM, wrote:
> Hello,
>
> I think we have a plugin based on Eclipse sign infrastructure code in my
> company, I will check how custom it is an how t
On Wed, Oct 7, 2015 at 8:04 PM, Gary Gregory wrote:
> Does m2e still want to pollute POMs withcryptic entries?
There are alternative storage possibilities, but that
doesn't fix the inherited difficulties. Just mákes the
SCM purists happy (and forces other users to live with the same
trouble that
Hello,
I think we have a plugin based on Eclipse sign infrastructure code in my
company, I will check how custom it is an how the licensing looks like.
[Sometimes I think a JCE/PkCS11 based solution (using ordinary jar signer) has
(besides the missing mandatory archiving) its merits. This does
Hello All,
More than a year ago INFRA announce availability of code signing at Apache:
https://blogs.apache.org/infra/entry/code_signing_service_now_available
but still there is no maven plugin for doing that :(
I never wrote maven plugins and need more time to write "Hello world" level
plugins b
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 the change it applies only to a single IT for a specific
> type of environment se
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
I believe MNG-5727 is a different issue. Here you have unused invalid
element. I don't have strong opinion if such
elements should cause build failure or ignored.
--
Regards,
Igor
On Wed, Oct 7, 2015, at 05:24 PM, Michael Osipov wrote:
> Hi folks,
>
> I am currently trying to fix MDEP-506 [1].
Some goals can run outside of maven project. Very likely apache one will be
first.
-D
On Wednesday, October 7, 2015, Robert Scholte wrote:
> It should be the first one specified in pluginManagement
>
> Robert
>
> Op Wed, 07 Oct 2015 23:38:10 +0200 schreef Dan Tran :
>
> Just wonder
>>
>> after
-- Forwarded message --
From: Tony Kurc
Date: Wed, Oct 7, 2015 at 9:49 PM
Subject: Re: [proposal/discuss] Add a committer tier
To: priv...@nifi.apache.org
What language goes into project 'bylaws' for nifi. I pasted some
samples, I prefer httpd's.
sample from hadoop [1]:
Commit
Thanks for the pointers, this approach worked well, setting the
maven.test.additionalClasspath property from the VALIDATE stage. The
value is split by surefire, so I modify it it exists.
For archival purposes, I did it as:
@Mojo(name = "dataInit", defaultPhase = LifecyclePhase.VALIDATE)
public
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12331490&styleName=Text&projectId=12317922&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C8959a4aa0ef1e581a93c2903df89c21523603417%7Clin
There are still a couple of issues left in JIRA:
https://issues.apache.o
It should be the first one specified in pluginManagement
Robert
Op Wed, 07 Oct 2015 23:38:10 +0200 schreef Dan Tran :
Just wonder
after the migration
which plugin would (apache, codehaus)
mvn eclipse:
picks up?
Thanks
-Dan
On Wed, Oct 7, 2015 at 12:22 PM, Robert Scholte
wrote:
Just wonder
after the migration
which plugin would (apache, codehaus)
mvn eclipse:
picks up?
Thanks
-Dan
On Wed, Oct 7, 2015 at 12:22 PM, Robert Scholte
wrote:
> Hi,
>
> as one might already have read: the Apache Maven team has decided to stop
> the maintenance of the maven-eclipse
Hi folks,
I am currently trying to fix MDEP-506 [1].
The core problem is that a POM has a dep in dep mngt without version and
that dependency is never referenced. Unfortunately, that build succeeds
though the POM is invalid.
I have done some digging and found
DefaultModelBuilder#importDepen
Hi,
currently i'm trying to understand how to create unit/integration tests
for the ModelMerger / MavenModelMerger part..which does things like
merging the configuration of plugins...
I have found a Test:
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob_plain;f=maven-model-builder/
Hi Benson,
to be honest you have decided to be the Release Manager...that means you
have to decide it...
Neither Hervé, nor me...
It's simply your turn ;-)...
Kind regards
Karl Heinz Marbaise
On 10/7/15 10:48 PM, Benson Margulies wrote:
Looks like you, Karl, and Hervé are the actors here;
Looks like you, Karl, and Hervé are the actors here; I can be a monkey
and stage a release but only if you all think it's ready.
On Wed, Oct 7, 2015 at 4:27 PM, Robert Scholte wrote:
> if you are talking about
> https://builds.apache.org/job/maven-plugins/org.apache.maven.plugins$maven-dependenc
Yesterday I clarified an issue with Karl-Heinz.
It was a specific environment issue appeared when using .mavenrc script
(maybe without using global java_home).
Hacking :-) in two ways see [1]:
1. Java code changed only in integration tests. Loading MANIFEST via
JarFile instead of ClassLoader's re
if you are talking about
https://builds.apache.org/job/maven-plugins/org.apache.maven.plugins$maven-dependency-plugin/4730/
this happens every now and than. Some time comparison which fails.
Based on the svn log it seems like most of the 3.0 things have been done,
especially with the replace
I've committed the code for MDEP-509 in maven-dependency-tree.
I'm sorry to seem a broken record, but is anyone working actively
towards the 3.0 of this and the dependency plugin? to be clear, I'm
not urgent, I'd just like to be helpful.
---
Hi,
as one might already have read: the Apache Maven team has decided to stop
the maintenance of the maven-eclipse-plugin. Even though M2Eclipse does a
great job, some still prefer or need to use the maven-eclipse-plugin.
For this reason the plugin is donated to Mojohaus.
I've done a check
What a release! 50 issues solved? Tibor, you're the man! Kudos for all the
work you've put into this one (again).
I've just built it from the source including all integration tests (JDK 7
only, sorry). In just 41 minutes, the build showed full success. I've
executed the test that Karl-Heinz wrote
Op Wed, 07 Oct 2015 19:45:03 +0200 schreef Andreas Gudian
:
I was the last one doing a release there, primarily fixing some issues
that
blocked it from being much of use for Java 8 projects that share the
.project / .classpath files in SCM. I still stand by the reasoning that I
had the last
Am 2015-10-07 um 19:45 schrieb Andreas Gudian:
I was the last one doing a release there, primarily fixing some issues that
blocked it from being much of use for Java 8 projects that share the
.project / .classpath files in SCM.
That is higly discouraged these days. Those should be autogenerated
Hi,
The vote has passed with the following result:
+1 (binding): Barrie Treloar, Arnaud Héritier, Tamás Cservenák, Dennis
Lundberg, Hervé BOUTEMY, Olivier Lamy, Karl Heinz Marbaise, Kristian
Rosenvold, Jason van Zyl, Robert Scholte
+1 (non binding): Tibor Digana, Anders Hammar, Michael Osipo
Darn, I use eclipse:eclipse all the time. Every time I've used the m2e
plugin in the past, it's driven me to cussing and madness.
Does m2e still want to pollute POMs withcryptic entries?
Gary
On Wed, Oct 7, 2015 at 10:45 AM, Andreas Gudian
wrote:
> I was the last one doing a release there, pri
+1
Op Sun, 04 Oct 2015 11:18:55 +0200 schreef 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
I was the last one doing a release there, primarily fixing some issues that
blocked it from being much of use for Java 8 projects that share the
.project / .classpath files in SCM. I still stand by the reasoning that I
had the last time, of why there is still the need for it - despite the
great len
ok it is in the parent.
thanks
> On 07 Oct 2015, at 19:22, Karl Heinz Marbaise wrote:
>
> Hi Arnaud,
>
> the maven.compiler.target/maven.compiler.source is defined in maven core..
>
> 1.7
> 1.7
>
> Furthermore the parent defines
>
>
>
>${maven.compiler.target}
>
>
>
>
> http://
Hi Arnaud,
the maven.compiler.target/maven.compiler.source is defined in maven core..
1.7
1.7
Furthermore the parent defines
${maven.compiler.target}
http://svn.apache.org/viewvc/maven/pom/tags/maven-parent-26/pom.xml?view=markup
On 10/7/15 6:46 PM, Arnaud Héritier wrote:
I’m
I’m surprised we didn’t yet have configured the enforcer plugin to validate the
JDK version to use to build ?
Or maybe it is done in our parent from the value of maven.compiler.target ?
> On 07 Oct 2015, at 17:30, khmarba...@apache.org wrote:
>
> Repository: maven
> Updated Branches:
> refs/hea
Bootstrap is the ant bootstrap
You just define M2_HOME and launch ant in the maven core directory to build and
deploy your local maven distro
cheers
> On 07 Oct 2015, at 15:43, Karl Heinz Marbaise wrote:
>
> Hi Jason,
>
> On 10/7/15 3:38 PM, Jason van Zyl wrote:
>> That it’s used in all pro
ok I will do some tests in that direction to see if I can find a solution.
Clearly I would like to be able to break maven logging by just adding an
extension jar including a simple logger.properties. If it is the case we need
to fix it.
But have a way with a distinct/specific file to do it may be
Hi Jason,
On 10/7/15 3:38 PM, Jason van Zyl wrote:
That it’s used in all projects not just selective ones so it’s directly
> inherited by all. As to not have to declare in each POM.
The inheritance was what i expected (apart from that i don't like this
kind of dependency definition in a pom
That it’s used in all projects not just selective ones so it’s directly
inherited by all. As to not have to declare in each POM.
> On Oct 7, 2015, at 9:29 AM, Karl Heinz Marbaise wrote:
>
> Hi,
>
> i'm currently looking into the Maven code and stumbled over one thing which i
> don't understan
>From what I can tell, alternative logging backend can be distributed as
an extension that is dropped into M2_HOME/lib/ext folder.
The only real limitation is that you can't provide default logging
configuration as part of the extension. This is due to odd/wrong order
of entries in m2.conf file,
Hi,
i'm currently looking into the Maven code and stumbled over one thing
which i don't understand at the moment is:
The root pom contains directly dependencies to junit
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob_plain;f=pom.xml;hb=HEAD
But it does not contain junit in depen
Hi Igor,
I didn't know this part of the code. It seems to be the right place to do
it like you did here :
https://github.com/takari/io.takari.m2e.lifecycle/blob/master/io.takari.m2e.incrementalbuild.core/src/io/takari/m2e/incrementalbuild/core/internal/MavenComponentContributor.java
Thus in t
Of course one parent POM can have another parent.
This is usual practice to have specific configuration in second parent POM
which is aggregator in reactor (multi-module) project.
Regarding plugin inheritance the parent POM (single inheritance) would be
the way to go.
Regarding complex dependencies
Here are few photos. Sorry for the bad quality
https://plus.google.com/photos/114843822427522708527/albums/6202834822544999585
Don’t hesitate to add your own photos guys
It was a really good moment
Thanks a lot
> On 03 Oct 2015, at 19:55, Tibor Digana wrote:
>
> Hi Apache geeks,
>
> I hope
Thanks for your suggestions.
I am not making this plugin for one particular project (although I am
using the Open PHACTS data as a use case), but for any project that
needs to distribute datasets.
Maven-based projects and organizations typically already have existing
parent poms.
Is it possible
Hi Robert, not a developer list question, better use the users list for
that kind of questions.
Indeed, like what Karl-Heinz says, I suspect you're trying to release from
a submodule/subdirectory.
Cheers
2015-10-07 9:23 GMT+02:00 Karl Heinz Marbaise :
> Hi Robert,
>
> Is this a mult module proj
Hi Robert,
Is this a mult module project ? Have you defined the scm connection
only in the root module ? Are you trying to release from the root of ?
Kind regards
Karl Heinz Marbaise
On 10/7/15 4:48 AM, Robert Patrick wrote:
Hi,
Sorry for the noise but it seems like the Maven Release Plu
44 matches
Mail list logo
