Re: [VOTE] Release Apache Maven Reporting Impl version 4.0.0

[Tamás Cservenák]

+1

On Sat, Oct 12, 2024, 21:48 Michael Osipov  wrote:

> Hi,
>
> we solved 69 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354042
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2216/
>
> https://repository.apache.org/content/repositories/maven-2216/org/apache/maven/reporting/maven-reporting-impl/4.0.0/maven-reporting-impl-4.0.0-source-release.zip
>
> Source release checksum(s):
> maven-reporting-impl-4.0.0-source-release.zip
> sha512:
>
> c338cd213a3a152adec8aa0a36d557988e6678384aa0b18df9af7d2f3ae67ea318b79b833c5369e6c8c0239da73a95664b4127dc2498cd567eb9c688569fa933
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-impl-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Maven 3.9.7 generates dodgy snapshot maven-metadata.xml

[Dale Ogilvie]

3.9.9 demonstrates similar behaviour, where one of the snapshotVersions in
maven-metadata.xml lags one build behind. In this case it is not the jar,
but the sources which lags.

Should this be an issue in maven jira?



On Fri, Oct 11, 2024 at 4:52 PM Dale Ogilvie 
wrote:

> Hello,
>
> we do builds up against the latest snapshot in our dev environment. After
> switching our builds from maven 3.8.5 to 3.9.7 we find that the
> maven-metadata.xml generated for our snapshot libraries is incorrect,
> resulting in a build up against the **previous** snapshot. Switching back
> to 3.8.5 fixes the issue.
>
> The incorrect metadata is generated when we "mvn deploy" our library. I
> took a look at the release logs for 3.9.8 and 3.9.9 and could not see any
> fixed issues which seemed to resemble this problem. We will try out 3.9.9
> once we get it installed on our build system.
>
> We are using an updatePolicy of always on our snapshot repo.
>
> 
>   
> true
> always
>   
>   our-snapshot
>   our-snapshots
>   https://someurlhere
> 
>
> Example incorrect file below. The *jar snapshotVersion *is one build
> number back, it should be 516
>
> 
> 
>   redacted
>   also-redacted
>   0.30.17-SNAPSHOT
>   
> 
>   20241010.231422
>   516
> 
> 20241010231529
> 
>   
> sources
> jar
> 0.30.17-20241010.231422-516
> 20241010231422
>   
>   
> jar
> 0.30.17-20241010.215322-515
> 20241010215322
>   
>   
> pom
> 0.30.17-20241010.231422-516
> 20241010231422
>   
> 
>   
> 
>
> Thanks!
>
>

-- 
Dale Ogilvie
Senior Software Engineer,
Technical and Process Coach,
Business Systems
11 Birmingham Drive, Christchurch, New Zealand
+64-22-6005437 Mobile
dale_ogil...@trimble.com

Re: Maven 3.9.7 generates dodgy snapshot maven-metadata.xml

[Tamás Cservenák]

The only thing I can imagine this to happen is if you do something
funky about deployment, like you deploy separately classified
artifacts from the same reactor?

Thanks
T

On Sun, Oct 13, 2024 at 11:24 PM Tamás Cservenák  wrote:
>
> Howdy,
>
> can you create a reproducer that reproduces this behaviour?
>
> Thanks
> T
>
> On Sun, Oct 13, 2024 at 9:55 PM Dale Ogilvie  wrote:
> >
> > 3.9.9 demonstrates similar behaviour, where one of the snapshotVersions in
> > maven-metadata.xml lags one build behind. In this case it is not the jar,
> > but the sources which lags.
> >
> > Should this be an issue in maven jira?
> >
> >
> >
> > On Fri, Oct 11, 2024 at 4:52 PM Dale Ogilvie 
> > wrote:
> >
> > > Hello,
> > >
> > > we do builds up against the latest snapshot in our dev environment. After
> > > switching our builds from maven 3.8.5 to 3.9.7 we find that the
> > > maven-metadata.xml generated for our snapshot libraries is incorrect,
> > > resulting in a build up against the **previous** snapshot. Switching back
> > > to 3.8.5 fixes the issue.
> > >
> > > The incorrect metadata is generated when we "mvn deploy" our library. I
> > > took a look at the release logs for 3.9.8 and 3.9.9 and could not see any
> > > fixed issues which seemed to resemble this problem. We will try out 3.9.9
> > > once we get it installed on our build system.
> > >
> > > We are using an updatePolicy of always on our snapshot repo.
> > >
> > > 
> > >   
> > > true
> > > always
> > >   
> > >   our-snapshot
> > >   our-snapshots
> > >   https://someurlhere
> > > 
> > >
> > > Example incorrect file below. The *jar snapshotVersion *is one build
> > > number back, it should be 516
> > >
> > > 
> > > 
> > >   redacted
> > >   also-redacted
> > >   0.30.17-SNAPSHOT
> > >   
> > > 
> > >   20241010.231422
> > >   516
> > > 
> > > 20241010231529
> > > 
> > >   
> > > sources
> > > jar
> > > 0.30.17-20241010.231422-516
> > > 20241010231422
> > >   
> > >   
> > > jar
> > > 0.30.17-20241010.215322-515
> > > 20241010215322
> > >   
> > >   
> > > pom
> > > 0.30.17-20241010.231422-516
> > > 20241010231422
> > >   
> > > 
> > >   
> > > 
> > >
> > > Thanks!
> > >
> > >
> >
> > --
> > Dale Ogilvie
> > Senior Software Engineer,
> > Technical and Process Coach,
> > Business Systems
> > 11 Birmingham Drive, Christchurch, New Zealand
> > +64-22-6005437 Mobile
> > dale_ogil...@trimble.com
> > 

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

Re: Maven 3.9.7 generates dodgy snapshot maven-metadata.xml

[Tamás Cservenák]

Howdy,

can you create a reproducer that reproduces this behaviour?

Thanks
T

On Sun, Oct 13, 2024 at 9:55 PM Dale Ogilvie  wrote:
>
> 3.9.9 demonstrates similar behaviour, where one of the snapshotVersions in
> maven-metadata.xml lags one build behind. In this case it is not the jar,
> but the sources which lags.
>
> Should this be an issue in maven jira?
>
>
>
> On Fri, Oct 11, 2024 at 4:52 PM Dale Ogilvie 
> wrote:
>
> > Hello,
> >
> > we do builds up against the latest snapshot in our dev environment. After
> > switching our builds from maven 3.8.5 to 3.9.7 we find that the
> > maven-metadata.xml generated for our snapshot libraries is incorrect,
> > resulting in a build up against the **previous** snapshot. Switching back
> > to 3.8.5 fixes the issue.
> >
> > The incorrect metadata is generated when we "mvn deploy" our library. I
> > took a look at the release logs for 3.9.8 and 3.9.9 and could not see any
> > fixed issues which seemed to resemble this problem. We will try out 3.9.9
> > once we get it installed on our build system.
> >
> > We are using an updatePolicy of always on our snapshot repo.
> >
> > 
> >   
> > true
> > always
> >   
> >   our-snapshot
> >   our-snapshots
> >   https://someurlhere
> > 
> >
> > Example incorrect file below. The *jar snapshotVersion *is one build
> > number back, it should be 516
> >
> > 
> > 
> >   redacted
> >   also-redacted
> >   0.30.17-SNAPSHOT
> >   
> > 
> >   20241010.231422
> >   516
> > 
> > 20241010231529
> > 
> >   
> > sources
> > jar
> > 0.30.17-20241010.231422-516
> > 20241010231422
> >   
> >   
> > jar
> > 0.30.17-20241010.215322-515
> > 20241010215322
> >   
> >   
> > pom
> > 0.30.17-20241010.231422-516
> > 20241010231422
> >   
> > 
> >   
> > 
> >
> > Thanks!
> >
> >
>
> --
> Dale Ogilvie
> Senior Software Engineer,
> Technical and Process Coach,
> Business Systems
> 11 Birmingham Drive, Christchurch, New Zealand
> +64-22-6005437 Mobile
> dale_ogil...@trimble.com
> 

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

Re: [VOTE] Release Apache Maven Reporting Impl version 4.0.0

[Michael Osipov]

+1

On 2024/10/12 19:48:50 Michael Osipov wrote:
> Hi,
> 
> we solved 69 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354042
> 
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2216/
> https://repository.apache.org/content/repositories/maven-2216/org/apache/maven/reporting/maven-reporting-impl/4.0.0/maven-reporting-impl-4.0.0-source-release.zip
> 
> Source release checksum(s):
> maven-reporting-impl-4.0.0-source-release.zip
> sha512: 
> c338cd213a3a152adec8aa0a36d557988e6678384aa0b18df9af7d2f3ae67ea318b79b833c5369e6c8c0239da73a95664b4127dc2498cd567eb9c688569fa933
> 
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-impl-LATEST/
> 
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 

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

Re: [doxia] [DISCUSS] adding footnote processing to markdown

[Michael Osipov]

On 2024/10/13 11:07:45 Claude Warren wrote:
> Now that Doxia 2.0 is out is there something that has to be done to enable
> footnotes or are they enabled by default?

Wait until next Maven Site Plugin version is released unless you want to fiddle 
with deps.

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

Re: [VOTE] Release Apache Maven Reporting Impl version 4.0.0

[Sylwester Lachiewicz]

+1

niedz., 13 paź 2024, 13:56 użytkownik Michael Osipov 
napisał:

> +1
>
> On 2024/10/12 19:48:50 Michael Osipov wrote:
> > Hi,
> >
> > we solved 69 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354042
> >
> > There are still a couple of issues left in JIRA:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-2216/
> >
> https://repository.apache.org/content/repositories/maven-2216/org/apache/maven/reporting/maven-reporting-impl/4.0.0/maven-reporting-impl-4.0.0-source-release.zip
> >
> > Source release checksum(s):
> > maven-reporting-impl-4.0.0-source-release.zip
> > sha512:
> >
> c338cd213a3a152adec8aa0a36d557988e6678384aa0b18df9af7d2f3ae67ea318b79b833c5369e6c8c0239da73a95664b4127dc2498cd567eb9c688569fa933
> >
> > Staging site:
> > https://maven.apache.org/shared-archives/maven-reporting-impl-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: [doxia] [DISCUSS] adding footnote processing to markdown

[Claude Warren]

Now that Doxia 2.0 is out is there something that has to be done to enable
footnotes or are they enabled by default?

Thanks,
Claude


On Mon, Jul 8, 2024 at 12:31 PM Claude Warren  wrote:

> Michael,
>
> Thanks for the note.
>
> I am willing to spend some time working on a solution if we can design and
> acceptable one.
>
> Claude
>
> On Sun, Jul 7, 2024 at 4:22 PM Michael Osipov  wrote:
>
>> Am 2024-07-07 um 15:20 schrieb Claude Warren:
>> > In looking at some of the codebase it seems like the markdown processor
>> > could use lazy instantiation by using the init() method.  However, I
>> don't
>> > see any way to pass information to the processor.
>> >
>> > Perhaps the org.apache.maven.doxia.module.markdown could have 2
>> > constructors.
>> >
>> >
>> > 1. Takes a file as an argument and processes the file line by line
>> with
>> > each line being the name of an extension to load.
>> > 2. A no-argument constructor that sets up the system as though the
>> > configuration file contained the current list of extensions.
>> >
>> > The Maven Site plugin could then be modified to look for a hidden file
>> in
>> > the markdown directory (.configure perhaps) and if present use that to
>> > construct the MarkdownProcessor.
>> >
>> > Alternatively, an environment variable that specifies the list of
>> > extensions could be used to provide the list during the static
>> > construction.  I like the file based approach since the directory of
>> > markdown files would contain the configuration.
>>
>> While I need to think about this here might be a stop-gap solution:
>> I believe that we can use priorities for the same bean id during DI,
>> thus you could drop in your own impl of the parser and it would override
>> ours containing all the config you need. We do this in Resolver.
>>
>> @cstamas, can you shed some light on this for Warren until we can
>> provide something out of the box?
>>
>> Michael
>>
>> > On Mon, Jun 24, 2024 at 2:33 PM Michael Osipov 
>> wrote:
>> >
>> >> I see, you are referring to
>> >>
>> https://github.com/apache/maven-doxia/blob/master/doxia-modules/doxia-module-markdown/src/main/java/org/apache/maven/doxia/module/markdown/MarkdownParser.java#L126-L165
>> >>
>> >> One of the issue is that I personally do not know what the implications
>> >> might be in terms of performance, etc. Are parsers heavy weight or can
>> they
>> >> be created easily? If you have thousands of files and I had reports of
>> >> people that they process tens of thousands of files...
>> >> kwin@ has recently added a generic approach to configure a parser. I
>> >> think if we are going to make this non-static you should pick it up.
>> From
>> >> my PoV we need his expertise to give you a defitive answer.
>> >>
>> >> Downside: That configuration approach is available only for Doxia
>> 2.0.0.
>> >>
>> >> Konrad, can you look into Claude's request and tell us your opinion?
>> >>
>> >> On 2024/06/24 12:46:16 Claude Warren wrote:
>> >>> Michael,
>> >>>
>> >>> Flexmark has a number of extensions available, but both 1.12.0 and
>> >>> 2.0.0-M12 use a static to create the Flexmark parser.  It would be
>> nice
>> >> to
>> >>> be able to pass a list of Flexmark extensions to be added to the
>> >> defaults.
>> >>> The only way I can see to do this is to use configuration options and
>> >> make
>> >>> the parser non-static.  Would this be acceptable to you?
>> >>>
>> >>> I will start on the work but before I spend a lot of time figuring out
>> >> how
>> >>> to make it work, I want to know if the solution has a chance of being
>> >>> accepted.
>> >>>
>> >>> Claude
>> >>>
>> >>>
>> >>> On Sun, Jun 16, 2024 at 8:43 PM Michael Osipov 
>> >> wrote:
>> >>>
>>  Am 2024-06-16 um 15:58 schrieb Claude Warren:
>> > There is a standard footnote extension available from flexmark, and
>> I
>>  have
>> > a private branch of 1.12.0 that adds it.  It seems to work.  Is
>> >> there any
>> > reason not to add this?
>> >
>> > I want to use it for some commons collections documentation where I
>> >> want
>>  to
>> > refer to various published papers.
>> 
>>  Please create a JIRA issue, the PR with a test for the feature, but I
>>  won't merge anything into Doxia 1.x anymore because all is focused on
>>  upcoming Doxia 2.0.0 stack.
>> 
>>  Michael
>> 
>> 
>>  -
>>  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>  For additional commands, e-mail: dev-h...@maven.apache.org
>> 
>> 
>> >>>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> For additional commands, e-mail: dev-h...@maven.apache.org
>> >>
>> >>
>> >
>>
>>
>
> --
> LinkedIn: http://www.linkedin.com/in/claudewarren
>


-- 
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [doxia] [DISCUSS] adding footnote processing to markdown

[Claude Warren]

May i assist in the testing / dev.  Or are you far enough along that
bringing in a new head will take to much time away with bringing me op to
speed?

On Sun 13 Oct 2024, 12:55 Michael Osipov,  wrote:

> On 2024/10/13 11:07:45 Claude Warren wrote:
> > Now that Doxia 2.0 is out is there something that has to be done to
> enable
> > footnotes or are they enabled by default?
>
> Wait until next Maven Site Plugin version is released unless you want to
> fiddle with deps.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Maven 3.9.7 generates dodgy snapshot maven-metadata.xml

[Dale Ogilvie]

I don't follow your suggestion "you deploy separately classified artifacts
from the same reactor".

The only item in the build section of our pom.xml is the
maven-source-plugin.

The trick is, the generated maven-metadata.xml is fine when we use maven
3.8.5. This is a very mature build pipeline, and we have just started
noticing this, after a switch to 3.9.x

I'm taking a look at this off of our build infrastructure.


On Mon, Oct 14, 2024 at 10:26 AM Tamás Cservenák 
wrote:

> The only thing I can imagine this to happen is if you do something
> funky about deployment, like you deploy separately classified
> artifacts from the same reactor?
>
> Thanks
> T
>
> On Sun, Oct 13, 2024 at 11:24 PM Tamás Cservenák 
> wrote:
> >
> > Howdy,
> >
> > can you create a reproducer that reproduces this behaviour?
> >
> > Thanks
> > T
> >
> > On Sun, Oct 13, 2024 at 9:55 PM Dale Ogilvie 
> wrote:
> > >
> > > 3.9.9 demonstrates similar behaviour, where one of the
> snapshotVersions in
> > > maven-metadata.xml lags one build behind. In this case it is not the
> jar,
> > > but the sources which lags.
> > >
> > > Should this be an issue in maven jira?
> > >
> > >
> > >
> > > On Fri, Oct 11, 2024 at 4:52 PM Dale Ogilvie  >
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > we do builds up against the latest snapshot in our dev environment.
> After
> > > > switching our builds from maven 3.8.5 to 3.9.7 we find that the
> > > > maven-metadata.xml generated for our snapshot libraries is incorrect,
> > > > resulting in a build up against the **previous** snapshot. Switching
> back
> > > > to 3.8.5 fixes the issue.
> > > >
> > > > The incorrect metadata is generated when we "mvn deploy" our
> library. I
> > > > took a look at the release logs for 3.9.8 and 3.9.9 and could not
> see any
> > > > fixed issues which seemed to resemble this problem. We will try out
> 3.9.9
> > > > once we get it installed on our build system.
> > > >
> > > > We are using an updatePolicy of always on our snapshot repo.
> > > >
> > > > 
> > > >   
> > > > true
> > > > always
> > > >   
> > > >   our-snapshot
> > > >   our-snapshots
> > > >   https://someurlhere
> > > > 
> > > >
> > > > Example incorrect file below. The *jar snapshotVersion *is one build
> > > > number back, it should be 516
> > > >
> > > > 
> > > > 
> > > >   redacted
> > > >   also-redacted
> > > >   0.30.17-SNAPSHOT
> > > >   
> > > > 
> > > >   20241010.231422
> > > >   516
> > > > 
> > > > 20241010231529
> > > > 
> > > >   
> > > > sources
> > > > jar
> > > > 0.30.17-20241010.231422-516
> > > > 20241010231422
> > > >   
> > > >   
> > > > jar
> > > > 0.30.17-20241010.215322-515
> > > > 20241010215322
> > > >   
> > > >   
> > > > pom
> > > > 0.30.17-20241010.231422-516
> > > > 20241010231422
> > > >   
> > > > 
> > > >   
> > > > 
> > > >
> > > > Thanks!
> > > >
> > > >
> > >
> > > --
> > > Dale Ogilvie
> > > Senior Software Engineer,
> > > Technical and Process Coach,
> > > Business Systems
> > > 11 Birmingham Drive, Christchurch, New Zealand
> > > +64-22-6005437 Mobile
> > > dale_ogil...@trimble.com
> > > 
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

-- 
Dale Ogilvie
Senior Software Engineer,
Technical and Process Coach,
Business Systems
11 Birmingham Drive, Christchurch, New Zealand
+64-22-6005437 Mobile
dale_ogil...@trimble.com

Re: [VOTE] Release Apache Maven Reporting Impl version 4.0.0

[Slawomir Jaranowski]

+1

On Sat, 12 Oct 2024 at 21:48, Michael Osipov  wrote:
>
> Hi,
>
> we solved 69 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354042
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-reporting-impl
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2216/
> https://repository.apache.org/content/repositories/maven-2216/org/apache/maven/reporting/maven-reporting-impl/4.0.0/maven-reporting-impl-4.0.0-source-release.zip
>
> Source release checksum(s):
> maven-reporting-impl-4.0.0-source-release.zip
> sha512:
> c338cd213a3a152adec8aa0a36d557988e6678384aa0b18df9af7d2f3ae67ea318b79b833c5369e6c8c0239da73a95664b4127dc2498cd567eb9c688569fa933
>
> Staging site:
> https://maven.apache.org/shared-archives/maven-reporting-impl-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>


-- 
Sławomir Jaranowski

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