Re: Resolving plugin dependency versions from

[Andres Almiray]

Oliver,

A ticket already exists: https://issues.apache.org/jira/browse/MNG-5588

Coincidentally, Hervé and I did a quick spike last week and have a PoC
(with red tests at the moment).

Cheers,
Andres

---
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.


On Tue, Apr 13, 2021 at 10:55 PM Romain Manni-Bucau 
wrote:

> Hi Oliver,
>
> Did you try to write this feature as an extension?
> For plugins it sounds more relevant since not transitive nor consumed
> (compared to dependencies).
> You fully control it this way and can potentially kind of inject a bom in
> plugin dependencies.
>
> Hope it helps,
> Romain
>
>
> Le mar. 13 avr. 2021 à 22:41, Oliver Drotbohm  a
> écrit :
>
> > Hi all,
> >
> > I was wondering if you have ever discussed to apply versions defined in
> >  to plugin dependencies? BOMs have become a
> > ubiquitous thing today but as a BOM author, you currently have no way to
> > define the version for dependencies to be used with plugins.
> >
> > Happy to file a ticket if you think it's worthwhile discussing.
> >
> > Cheers,
> > Ollie
> >
>

Re: Resolving plugin dependency versions from

[Romain Manni-Bucau]

Hi Oliver,

Did you try to write this feature as an extension?
For plugins it sounds more relevant since not transitive nor consumed
(compared to dependencies).
You fully control it this way and can potentially kind of inject a bom in
plugin dependencies.

Hope it helps,
Romain


Le mar. 13 avr. 2021 à 22:41, Oliver Drotbohm  a
écrit :

> Hi all,
>
> I was wondering if you have ever discussed to apply versions defined in
>  to plugin dependencies? BOMs have become a
> ubiquitous thing today but as a BOM author, you currently have no way to
> define the version for dependencies to be used with plugins.
>
> Happy to file a ticket if you think it's worthwhile discussing.
>
> Cheers,
> Ollie
>

Resolving plugin dependency versions from

[Oliver Drotbohm]

Hi all,

I was wondering if you have ever discussed to apply versions defined in 
 to plugin dependencies? BOMs have become a ubiquitous 
thing today but as a BOM author, you currently have no way to define the 
version for dependencies to be used with plugins.

Happy to file a ticket if you think it's worthwhile discussing.

Cheers,
Ollie


signature.asc
Description: Message signed with OpenPGP

Requesting release of maven-jxr-plugin and maven-changes-plugin

[Nelson,Matt]

Requesting release of maven-jxr-plugin and maven-changes-plugin. Is there 
anything blocking these releases that I can assist with?

Looking forward to using the contributions I made a while ago.
https://issues.apache.org/jira/browse/JXR-143
https://issues.apache.org/jira/browse/MCHANGES-340



CONFIDENTIALITY NOTICE This message and any included attachments are from 
Cerner Corporation and are intended only for the addressee. The information 
contained in this message is confidential and may constitute inside or 
non-public information under international, federal, or state securities laws. 
Unauthorized forwarding, printing, copying, distribution, or use of such 
information is strictly prohibited and may be unlawful. If you are not the 
addressee, please promptly delete this message and notify the sender of the 
delivery error by e-mail or you may call Cerner's corporate offices in Kansas 
City, Missouri, U.S.A at (+1) (816)221-1024.

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Robert Scholte]

Hi Rémy

I don't see it as PR under https://github.com/apache/maven-release/pulls
I did a quick scan over this list and the open Jira issues and decided not to 
add more to this milestone release.

Robert
On 13-4-2021 09:09:21, Rémy Sanlaville  wrote:
Hi Robert,

What about
https://github.com/apache/maven-release/compare/master...sanlaville:patch-1
?

Cf.
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com%3E
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E

Rémy

On Mon, Apr 12, 2021 at 7:31 PM Robert Scholte wrote:

> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348079=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317824%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1639
>
> https://repository.apache.org/content/repositories/maven-1639/org/apache/maven/release/maven-release/3.0.0-M4/maven-release-3.0.0-M4-source-release.zip
>
> Source release checksum(s):
>
> maven-release-3.0.0-M4-source-release.zip sha512: 
> 49ec8c495b11696671e83ccdeee3408223d0aef3cfd5f48e2a4afc66e225f550069a060702205152e3e59238f9db64efd85ac626b25b05596be3ef422b991895
>
> Staging site:
> https://maven.apache.org/maven-release-archives\maven-release-LATEST
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>

[GitHub] [maven-site] elharo commented on pull request #233: Clarify usage of '-' for profile deactivation

[GitBox]

elharo commented on pull request #233:
URL: https://github.com/apache/maven-site/pull/233#issuecomment-818647151


   I think you can create a JIRA account and file issues without permission, 
unlike some other projects. 
   
   Also, if there's an existing JIRA for this feature you might as well use 
that for the doc update too. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] [maven-site] shoffmeister commented on pull request #233: Clarify usage of '-' for profile deactivation

[GitBox]

shoffmeister commented on pull request #233:
URL: https://github.com/apache/maven-site/pull/233#issuecomment-818572392


   I understand that a JIRA ticket would be required to cover this - perhaps 
someone with an account can create that, or take the commit and run with it, or 
...?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] [maven-site] shoffmeister opened a new pull request #233: Clarify usage of '-' for profile deactivation

[GitBox]

shoffmeister opened a new pull request #233:
URL: https://github.com/apache/maven-site/pull/233


   With the introduction of "?" as an optionality indicator, the example for 
profile deactivation became slightly overloaded. To really demonstrate use of 
'-' (which is happily not interpreted by the shell, hence not requiring 
escaping), introduce a separate example.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Issues to be done for Maven Core 4.0.0-alpha-1?

[Martin Kanters]

Hi Guillaume,

Do you know why maven-shared-utils has not been released yet? It sounds
like a good idea to include this at least in the official 4.0.0 release, so
I think it makes sense to include it in either this alpha release or
perhaps a next one. I'm not familiar with the jansi changes or the status
of maven-shared-utils though, maybe others who are can chime in.

Martin

Op ma 12 apr. 2021 om 11:13 schreef Guillaume Nodet :

> Would it be possible to include all the jansi related issues ?  That
> requires a release of maven-shared-utils
>   MNG-7080, MNG-7079, MNG-6719, MNG-6239, MNG-6755, MNG-6380, MNG-6915
> I'm willing to help, but all the PRs are kinda blocked because of the need
> for a maven-shared-utils release, so they include a snapshot dependency and
> obviously fail the tests...
>
> Guillaume
>
>
> Le lun. 12 avr. 2021 à 09:06, Martin Kanters  a
> écrit :
>
>> Great to see the enthusiasm. I also expected more work to be done for this
>> release, but apparently that's not the case (if we aren't missing
>> something
>> else).
>>
>> As Romain is saying, I think we should put some work into documenting. At
>> least some of the new changes. Maarten Mulders and I are working on
>> documenting all reactor changes, listed under MNGSITE-444 [1]. Have we
>> documented other big features, like the Maven Wrapper and Build/Consumer
>> POM already? If not, should we make tickets for it? Also, not sure whether
>> this is required for alpha-1.
>>
>> Regarding MNG-6772 / MNG-6397 / MRESOLVER-168, I think we can either try
>> to
>> include all in this release, or make that part of alpha-2. I'm unfamiliar
>> with the consequences, so I'll let you decide that ;) Let me know if I can
>> help.
>>
>> Regards,
>> Martin
>>
>> [1] https://issues.apache.org/jira/browse/MNGSITE-444
>>
>> Op zo 11 apr. 2021 om 20:07 schreef Romain Manni-Bucau <
>> rmannibu...@gmail.com>:
>>
>> > +1, I just suspect we should be clear on the status of this alpha
>> (unstable
>> > and unexpected to hit CI for ex) and breaking changes which can break
>> again
>> > in final potentially (this is what generally upset people with
>> alpha/beta
>> > and prevent their usage in later versions). In any case having some
>> preview
>> > is generally always worth it before ;).
>> >
>> > Romain Manni-Bucau
>> > @rmannibucau  |  Blog
>> >  | Old Blog
>> >  | Github <
>> > https://github.com/rmannibucau> |
>> > LinkedIn  | Book
>> > <
>> >
>> https://www.packtpub.com/application-development/java-ee-8-high-performance
>> > >
>> >
>> >
>> > Le dim. 11 avr. 2021 à 17:59, Michael Osipov  a
>> > écrit :
>> >
>> > > Attention: MNG-6772 is already on master and Robert and me have
>> decided
>> > > to reopen it to give it more thought. It must be reverted from master
>> > > first before you cut a release until we have decided how to procede
>> with
>> > > this as well as related MNG-6397.
>> > >
>> > > Except that I see no reason not to continue with alpha-1. I am certain
>> > > that this is a good release, but we will require more rounds of it.
>> > >
>> > > Michael
>> > >
>> > > Am 2021-04-11 um 17:32 schrieb Hervé BOUTEMY:
>> > > > cutting 4.0.0-alpha release: very good idea!!!
>> > > >
>> > > > on the 3 issues, I can tell that MNG-6397 is a long standing issue
>> that
>> > > looks
>> > > > relevant (caused by MNG-6772 [1] that better describes it)
>> > > >
>> > > > But I don't see why this particular issue is an absolute must for
>> > > 4.0.0-alpha:
>> > > > I would propose to mark it for 4.0.x-candidate
>> > > >
>> > > >
>> > > > And I'm interested in people wanting to help on it (in a separate
>> > > thread).
>> > > >
>> > > >
>> > > > on the question of cutting the first alpha release, shouldn't we
>> > include
>> > > Maven
>> > > > Resolver 1.7.0? It would help to have MRESOLVER-168 to work on
>> > > MNG-6772...
>> > > >
>> > > > Regards,
>> > > >
>> > > > Hervé
>> > > >
>> > > >
>> > > > [1] https://issues.apache.org/jira/browse/MNG-6772
>> > > >
>> > > > Le dimanche 11 avril 2021, 16:19:49 CEST Martin Kanters a écrit :
>> > > >> Hi all,
>> > > >>
>> > > >> I am wondering if we have a good idea of what we want to have
>> finished
>> > > >> before cutting the first 4.0.0-alpha release.
>> > > >> I would love to work towards the actual release, and thus am
>> wondering
>> > > >> whether there's a list of issues we can finish.
>> > > >> When selecting all unresolved issues targeted for 4.0.0-alpha-1,
>> JIRA
>> > > comes
>> > > >> up with just 3 issues, which I'm not sure if they are still
>> relevant.
>> > > [1]
>> > > >> I guess there might be more we need to include in the version, but
>> > > that's
>> > > >> unknown to me.
>> > > >>
>> > > >> Thanks,
>> > > >> Martin
>> > > >>
>> > > >> [1]
>> > > >>
>> > >
>> >
>> https://issues.apache.org/jira/issues/?filter=-5=project%20%3D%20MNG%20A
>> > > >>
>> > >
>> >

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M4

[Rémy Sanlaville]

Hi Robert,

What about
https://github.com/apache/maven-release/compare/master...sanlaville:patch-1
?

Cf.
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CCAK8JC1TqE3CAQbD%3DAC6p9%2BXtO9uk1kjRsVY9YctdVSmPeB7YWQ%40mail.gmail.com%3E
https://mail-archives.apache.org/mod_mbox/maven-dev/202006.mbox/%3CMailbird-3058d9d5-b625-4621-bd90-e20080d523ce%40apache.org%3E

Rémy

On Mon, Apr 12, 2021 at 7:31 PM Robert Scholte  wrote:

> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348079=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317824%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1639
>
> https://repository.apache.org/content/repositories/maven-1639/org/apache/maven/release/maven-release/3.0.0-M4/maven-release-3.0.0-M4-source-release.zip
>
> Source release checksum(s):
>
> maven-release-3.0.0-M4-source-release.zip sha512: 
> 49ec8c495b11696671e83ccdeee3408223d0aef3cfd5f48e2a4afc66e225f550069a060702205152e3e59238f9db64efd85ac626b25b05596be3ef422b991895
>
> Staging site:
> https://maven.apache.org/maven-release-archives\maven-release-LATEST
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>