Sorry for the offtopic, but you probably got attention of a lot of Antons
with that subject :)
вс, 5 апр. 2020 г. в 20:16, Elliotte Rusty Harold :
> Are there up to date instructions for releasing a Maven plugin
> somewhere? If so, I could probably do this. I see
>
I was actually going to ask on the list eventually. Tried using it with -B
to no success a few days ago.
I've also had no luck finding where this option is documented on the maven
site.
The only place to look was in the Jira and PR, but those mostly have the
syntax that's not actually what was
What happened to the last attempt and the shotgun owl? :-D
On Fri, 21 Jul 2017, 18:22 Robert Scholte, wrote:
> Hi,
>
> I'd like to start an attempt to redesign our website.
> At ApacheCon Europe Hervé and I got in touch with Open Source Design[1].
> Any objections to
You're hitting an issue [1] in plexus-utils most probably. Check if you
have processing instructions in one of the poms.
[1] https://github.com/codehaus-plexus/plexus-utils/issues/22
2017-06-30 16:57 GMT+03:00 Brian Fox :
> I'm getting index out of bounds exceptions with
+1
Needed this for a performance fix in m2e.
2017-05-03 15:05 GMT+03:00 Igor Fedorenko :
> +1
>
> In the longer run I think we need to review the many caches we have in
> Maven (including the resolver) and come up with a coherent strategy how
> to manage those caches.
>
>
Hi guys, I've been reminded of another issue that was supposed to go into
3.4.0 at the time but seem to have forgotten about it when the 3.4-3.5
scrubbing thing happened.
It's https://issues.apache.org/jira/browse/MNG-6025
Really minor thing that doesn't affect maven itself, but could help a lot
1cdd0c2be545200a11d74c1055dcd0b16d96adc3>
> >>
> >> Regards,
> >>
> >
> > To clarify: It won't be possible to run the non-updated (tagged?) core
> > ITs against Maven >= 3.5.0. This is what made us reset the branches. You
> > need to review this, if you are going to run the non-updated ITs against
> > what will be voted for release.
> >
> > @Anton Tanasenko:
> > If what I just wrote is incorrect, please comment here. Thank you.
> >
> > Regards,
> >
>
> Merged to master.
>
>
--
Regards,
Anton.
New ITs should run successfully against 3.3.9 and 3.5.0-SNAPSHOT+changes.
It doesn't make sense to test a feature which is not in.
2017-01-19 22:46 GMT+02:00 Christian Schulte :
> Am 01/19/17 um 13:06 schrieb Stephen Connolly:
> > Ideal would be to create a *new throw-away
I've submitted the PR for MNG-5958 branch.
Changed the existing 5805 IT to work for 3.3.9 only ('phases' syntax), and
duplicated it to a one that works with 3.3.9+ ('lifecyclePhases' syntax).
2017-01-11 22:59 GMT+02:00 Christian Schulte <c...@schulte.it>:
> Am 01/11/17 um 15:05 schr
I'll submit a PR in these couple of days, if it waits a little bit.
2017-01-11 0:54 GMT+02:00 Christian Schulte <c...@schulte.it>:
> Am 01/10/17 um 09:30 schrieb Anton Tanasenko:
> > 3.3.9 (in 5805) introduced an additional syntax for specifying lifecycle
> > goals as
>
licate the test (second one being _mk2 or
> something like that) and ensure that the duplicate has a different range
> activation
>
> HTH
>
> On 10 January 2017 at 07:32, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > So 5805 should be marked as only
1d9>
> >
> > authorStuart McCulloch <mccu...@gmail.com>
> > Wed, 6 Jan 2016 12:23:06 +0100 (11:23 +)
> >
> > Commit to the ITs:
> > <https://git-wip-us.apache.org/repos/asf?p=maven-
> integration-testing.git;a=commit;h=8852538208e
FIX-3.5.0:
MNG- WONTFIX Add a ProjectArtifactsCache similar to
PluginArtifactsCache
That's actually a https://issues.apache.org/jira/browse/MNG-6025
2017-01-01 2:55 GMT+02:00 Michael Osipov :
> I just went through the list my issues. Here is a safe list I
Looks like the high failure count was due to
https://issues.apache.org/jira/browse/MNG-6023
The commit that reverted the slf4j version change came in some 9 hours ago
while we were running tests just before that.
https://github.com/apache/maven/commit/4b35102f0e3302e15a80d3ddb756463601b9217a
Hey,
M2E is effectively doing LifecycleExecutor#calculateExecutionPlan(session,
false, "default").getMojoExecutions(), and each returned mojo execution has
a final xml config.
2016-04-28 13:00 GMT+03:00 Tamás Cservenák :
> Hi there,
>
> there is a POC I was toying with
Hi,
MavenProject#getArtifacts() is returning a resolved list of all
dependencies, each artifact will have only one specific version.
Which scope is resolved - depends on the requiresDependencyResolution
attribute of your @Mojo.
Be aware, that not all of the projects provide licensing infromation
Tried out with a couple of projects that contributed to burning two of the
previous release attempts plus a couple more. All good!
+1
2015-10-29 23:37 GMT+02:00 jieryn :
> Tested with a few projects, I see no issues with this release. Thank you,
> +1 non-binding.
> On Oct 29,
think will help.
I’ll cut the release next Monday.
On Aug 2, 2015, at 5:46 PM, Anton Tanasenko atg.sleepl...@gmail.com
wrote:
Sure thing, I'll update pull request.
Thanks for reminding.
2015-08-02 21:00 GMT+03:00 Robert Scholte rfscho...@apache.org:
Even though the changes seem
:37 +0200 schreef Anton Tanasenko
atg.sleepl...@gmail.com:
I've created yet another PR for MNG-5805:
https://github.com/apache/maven/pull/62
Sorry guys, I was certain I had run m-enforcer-p its as well with 3.3.5
candidate.
2015-08-01 16:57 GMT+03:00 Anton Tanasenko atg.sleepl...@gmail.com
Oh not again,
The LifecyclePhase#toString() method was added by me along with toLegacyMap.
Looks like I didn't take care of 'mojos' field possibly being null. This
seems to be happening when an extension specifies a lifecycle phase but
doesn't assign any mojo executions to it.
2015-08-01 16:08
I've created yet another PR for MNG-5805:
https://github.com/apache/maven/pull/62
Sorry guys, I was certain I had run m-enforcer-p its as well with 3.3.5
candidate.
2015-08-01 16:57 GMT+03:00 Anton Tanasenko atg.sleepl...@gmail.com:
Oh not again,
The LifecyclePhase#toString() method was added
Hi Jörg,
The error message you posted says that java is unable to allocate 500mb of
heap. The machine you were running it on didn't have that much available at
the time.
2015-07-23 15:47 GMT+03:00 Jörg Schaible joerg.schai...@swisspost.com:
Hi folks,
M335 needs even more memory (see also
This looks to be a consequence of MNG -5805 :(
2015-07-19 23:12 GMT+03:00 Mirko Friedenhagen mfriedenha...@gmail.com:
This seems to affect project which use requirePluginVersions as an
enforcer-rule. After inserting this rule into another project I get a
similar stack trace.
I've renamed getter methods in question from xPhases to xLifecyclePhases
and reimplemented the original ones to preserve full compatibility. Setters
were left mostly as is since imo those are not called from outside of maven
core.
Pull request is submitted for
://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Sun, Jul 19, 2015 at 10:21 PM, Anton Tanasenko
atg.sleepl...@gmail.com wrote:
This looks to be a consequence of MNG -5805 :(
2015-07-19 23:12 GMT
+1 for MNG-5805, works perfectly.
2015-07-18 15:33 GMT+03:00 Jason van Zyl ja...@takari.io:
+1
Analyzing release validity...
stagingUrl: https://repository.apache.org/content/repositories/maven-1199
groupId: org.apache.maven
artifactId: apache-maven
version: 3.3.4
Source ZIP url
Hi,
There is no possibility right now to map goals to phases with a custom
configuration and/or dependencies when dealing with custom packagin types.
DefaultLifecycleMapping only has 'goals' parameter in components.xml, and
DefaultLifecyclePluginAnalyzer does not take those into account.
I
27 matches
Mail list logo