Re: how to get latest plugin-version using mvn versions:display-plugin-updates?

[Stephan Wissel]

Update: When I run:

mvn versions:plugin-updates-report

newer plugin versions are mentioned in the report file

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
<https://www.xing.com/profile/StephanH_Wissel>


On Thu, Jul 28, 2022 at 1:28 AM Stephan Wissel  wrote:

> I use:
>
> mvn versions:display-plugin-updates
>
> org.codehaus.mojo:versions-maven-plugin:2.11.0
>
> -U didn't do anything different
>
> Create a nice day!
> Stephan H. Wissel
>
> Phone: +65 96673269
> Blog <https://www.wissel.net/blog> Twitter
> <http://twitter.com/notessensei> LinkedIn
> <http://sg.linkedin.com/in/notessensei> Xing
> <https://www.xing.com/profile/StephanH_Wissel>
>
>
> On Wed, Jul 27, 2022 at 7:43 PM Delany  wrote:
>
>> What version of Maven are you running, and, more importantly, what version
>> of the versions-maven-plugin?
>> Are you invoking it like this:
>> mvn org.codehaus.mojo:versions-maven-plugin:2.11.0:display-plugin-updates
>> -U
>> Delany
>>
>>
>> On Wed, 27 Jul 2022 at 15:59, Stephan Wissel  wrote:
>>
>> > AFAIK -U updates Snapshot releases. It doesn't update or display newer
>> > plugin releases
>> >
>> > Create a nice day!
>> > Stephan H. Wissel
>> >
>> > Phone: +65 96673269
>> > Blog <https://www.wissel.net/blog> Twitter <
>> http://twitter.com/notessensei
>> > >
>> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
>> > <https://www.xing.com/profile/StephanH_Wissel>
>> >
>> >
>> > On Tue, Jul 26, 2022 at 10:44 AM Delany 
>> > wrote:
>> >
>> > > Always force an update with the -U switch.
>> > > Delany
>> > >
>> > > On Tue, 26 Jul 2022, 06:55 Stephan Wissel, 
>> wrote:
>> > >
>> > > > When I run
>> > > >
>> > > > mvn versions:display-plugin-updates
>> > > >
>> > > > on my project, I get the result:
>> > > >
>> > > > [*INFO*] All plugins with a version specified are using the latest
>> > > > versions.
>> > > >
>> > > > [*INFO*]
>> > > >
>> > > > [*INFO*] All plugins have a version specified.
>> > > >
>> > > > [*INFO*]
>> > > >
>> > > > [*INFO*] Project requires minimum Maven version for build of: 3.8.1
>> > > >
>> > > > [*INFO*] Plugins require minimum Maven version of: null
>> > > >
>> > > > [*INFO*]
>> > > >
>> > > > [*INFO*] No plugins require a newer version of Maven than specified
>> by
>> > > the
>> > > > pom.
>> > > >
>> > > > However when checking maven central, I find newer versions of the
>> > plugins
>> > > > used.
>> > > > (e.g. spotless-maven-plugin -> 2.22.8 -> 2.23.0)
>> > > > What do I miss?
>> > > >
>> > > > Create a nice day!
>> > > > Stephan H. Wissel
>> > > >
>> > > > Blog <https://www.wissel.net/blog> Twitter <
>> > > http://twitter.com/notessensei
>> > > > >
>> > > > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
>> > > > <https://www.xing.com/profile/StephanH_Wissel>
>> > > >
>> > >
>> >
>>
>

Re: how to get latest plugin-version using mvn versions:display-plugin-updates?

[Stephan Wissel]

I use:

mvn versions:display-plugin-updates

org.codehaus.mojo:versions-maven-plugin:2.11.0

-U didn't do anything different

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
<https://www.xing.com/profile/StephanH_Wissel>


On Wed, Jul 27, 2022 at 7:43 PM Delany  wrote:

> What version of Maven are you running, and, more importantly, what version
> of the versions-maven-plugin?
> Are you invoking it like this:
> mvn org.codehaus.mojo:versions-maven-plugin:2.11.0:display-plugin-updates
> -U
> Delany
>
>
> On Wed, 27 Jul 2022 at 15:59, Stephan Wissel  wrote:
>
> > AFAIK -U updates Snapshot releases. It doesn't update or display newer
> > plugin releases
> >
> > Create a nice day!
> > Stephan H. Wissel
> >
> > Phone: +65 96673269
> > Blog <https://www.wissel.net/blog> Twitter <
> http://twitter.com/notessensei
> > >
> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > <https://www.xing.com/profile/StephanH_Wissel>
> >
> >
> > On Tue, Jul 26, 2022 at 10:44 AM Delany 
> > wrote:
> >
> > > Always force an update with the -U switch.
> > > Delany
> > >
> > > On Tue, 26 Jul 2022, 06:55 Stephan Wissel,  wrote:
> > >
> > > > When I run
> > > >
> > > > mvn versions:display-plugin-updates
> > > >
> > > > on my project, I get the result:
> > > >
> > > > [*INFO*] All plugins with a version specified are using the latest
> > > > versions.
> > > >
> > > > [*INFO*]
> > > >
> > > > [*INFO*] All plugins have a version specified.
> > > >
> > > > [*INFO*]
> > > >
> > > > [*INFO*] Project requires minimum Maven version for build of: 3.8.1
> > > >
> > > > [*INFO*] Plugins require minimum Maven version of: null
> > > >
> > > > [*INFO*]
> > > >
> > > > [*INFO*] No plugins require a newer version of Maven than specified
> by
> > > the
> > > > pom.
> > > >
> > > > However when checking maven central, I find newer versions of the
> > plugins
> > > > used.
> > > > (e.g. spotless-maven-plugin -> 2.22.8 -> 2.23.0)
> > > > What do I miss?
> > > >
> > > > Create a nice day!
> > > > Stephan H. Wissel
> > > >
> > > > Blog <https://www.wissel.net/blog> Twitter <
> > > http://twitter.com/notessensei
> > > > >
> > > > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > > > <https://www.xing.com/profile/StephanH_Wissel>
> > > >
> > >
> >
>

Re: how to get latest plugin-version using mvn versions:display-plugin-updates?

[Stephan Wissel]

AFAIK -U updates Snapshot releases. It doesn't update or display newer
plugin releases

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
<https://www.xing.com/profile/StephanH_Wissel>


On Tue, Jul 26, 2022 at 10:44 AM Delany  wrote:

> Always force an update with the -U switch.
> Delany
>
> On Tue, 26 Jul 2022, 06:55 Stephan Wissel,  wrote:
>
> > When I run
> >
> > mvn versions:display-plugin-updates
> >
> > on my project, I get the result:
> >
> > [*INFO*] All plugins with a version specified are using the latest
> > versions.
> >
> > [*INFO*]
> >
> > [*INFO*] All plugins have a version specified.
> >
> > [*INFO*]
> >
> > [*INFO*] Project requires minimum Maven version for build of: 3.8.1
> >
> > [*INFO*] Plugins require minimum Maven version of: null
> >
> > [*INFO*]
> >
> > [*INFO*] No plugins require a newer version of Maven than specified by
> the
> > pom.
> >
> > However when checking maven central, I find newer versions of the plugins
> > used.
> > (e.g. spotless-maven-plugin -> 2.22.8 -> 2.23.0)
> > What do I miss?
> >
> > Create a nice day!
> > Stephan H. Wissel
> >
> > Blog <https://www.wissel.net/blog> Twitter <
> http://twitter.com/notessensei
> > >
> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > <https://www.xing.com/profile/StephanH_Wissel>
> >
>

how to get latest plugin-version using mvn versions:display-plugin-updates?

[Stephan Wissel]

When I run

mvn versions:display-plugin-updates

on my project, I get the result:

[*INFO*] All plugins with a version specified are using the latest versions.

[*INFO*]

[*INFO*] All plugins have a version specified.

[*INFO*]

[*INFO*] Project requires minimum Maven version for build of: 3.8.1

[*INFO*] Plugins require minimum Maven version of: null

[*INFO*]

[*INFO*] No plugins require a newer version of Maven than specified by the
pom.

However when checking maven central, I find newer versions of the plugins
used.
(e.g. spotless-maven-plugin -> 2.22.8 -> 2.23.0)
What do I miss?

Create a nice day!
Stephan H. Wissel

Blog  Twitter 
LinkedIn  Xing

Where can find a working plugin test example

[Stephan Wissel]

Trying to write a plugin following TDD practices.
Tried to follow:
https://maven.apache.org/plugin-testing/maven-plugin-testing-harness/getting-started/index.html

which already fails on maven archetype:create (generate works, but doesn't
create a test case).

last published version of
org.apache.maven.plugin-testing/maven-plugin-testing-harness
was 2014:
https://search.maven.org/artifact/org.apache.maven.plugin-testing/maven-plugin-testing-harness/3.3.0/jar

However there's a 2021
com.github.codeteapot.maven.plugin-testing:maven-plugin-testing-harness

Where can I find a working example of a plugin-test with contemporary
dependencies?

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog  Twitter 
LinkedIn  Xing

Re: OSS Nexus vs GitHub Packages

[Stephan Wissel]

We worked with all sorts of repos and I have to say GitHub provided the
least stressful environment. The combination of Git functionality with
GitHub actions is delightful. You can ditch your CI and bug tracker.

Especially nice the VSCode integration where a //TODO in code reflects as
issue in GitHub

On Tue, 27 Jul 2021 at 21:22, Stephen Coy  wrote:

> Hi all,
>
> Just wondering if anyone has any thoughts on using GitHub Packages as a
> company repo vs Nexus.
>
> Right now we (about 30-40 devs) are using an ageing version of Sonatype
> Nexus for onsite builds and S3 for “cloud” based builds (a process
> inherited from using Spring Boot).
>
> Now there is a push for us to migrate everything to GitHub Packages.
>
> Personally, I would just run up a Nexus OSS instance in an EC2 instance
> and use that.
>
> There does not seem to be much discussion about this around.
>
> What is everyone else doing right now?
>
> Cheers,
>
> Steve C
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
> --

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog  Twitter 
LinkedIn  Xing

Re: Customizing the maven-site-plugin Markdown renderer?

[Stephan Wissel]

Did you have a chance to look at this?

On Thu, Apr 9, 2020 at 2:10 AM Stephan Wissel  wrote:

> Hello Hervé,
>
> I created a Flexmark sample that is as close as possible to the way
> Flexmark is used in Doxia:
>
> https://github.com/Stwissel/maven-site-extension/tree/master/simple-flexmark-example
> The result can be seen here:
> https://projectcastle.io/sample.html
> (I copied a site-plugin generated page and just removed the body part and
> replace it with the markdown conversion result)
>
> As it seems, to get Adminition working in the rendering, you need to add a
> single line (and the import/dependency of course)
>
> https://github.com/Stwissel/maven-site-extension/blob/master/simple-flexmark-example/src/main/java/com/notessensei/demo/Demo1.java#L78
>
> Would you need more samples?
>
>
> Create a nice day!
> Stephan H. Wissel
>
> Phone: +65 96673269
> Blog <https://www.wissel.net/blog> Twitter
> <http://twitter.com/notessensei> LinkedIn
> <http://sg.linkedin.com/in/notessensei> Xing
> <https://www.xing.com/profile/StephanH_Wissel>
>
>
> On Mon, Apr 6, 2020 at 2:42 PM Hervé BOUTEMY 
> wrote:
>
>> don't hesitate to share every single concrete step, even the flexmark
>> standalone test: this will ease working together, ensuring we understand
>> each
>> other
>>
>> even before updating doxia-module-markdown with an updated version, there
>> is a
>> test with a Maven site to be done with the normal Doxia, to show the
>> result
>> (perhaps there is a partial failure only): this will be interesting to
>> compare
>> the result against the flexmark standalone test.
>>
>> then once we'll be at updating doxia-module-markdown, yes, you can
>> override
>> the version used by the maven-site-plugin by setting dependencies in
>> plugin
>> definition
>>
>> Regards,
>>
>> Hervé
>>
>> Le lundi 6 avril 2020, 07:12:14 CEST Stephan Wissel a écrit :
>> > Sorry for not being clear. The GitHub part is easy.
>> > What I'm not sure about is how I can test my modification in the
>> context of
>> > the site plugin.
>> > Would defining my markdown renderer as dependency of the site plugin
>> > overwrite the build in renderer or do I have to modify the source of the
>> > site plugin too?
>> >
>> > Create a nice day!
>> > Stephan H. Wissel
>> >
>> > Phone: +65 96673269
>> > Blog <https://www.wissel.net/blog> Twitter <
>> http://twitter.com/notessensei>
>> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
>> > <https://www.xing.com/profile/StephanH_Wissel>
>> >
>> > On Mon, Apr 6, 2020 at 6:16 AM Hervé BOUTEMY 
>> wrote:
>> > > you can create a GitHub repository, or a collection of repositories
>> > > whatever is necessary
>> > >
>> > > Regards,
>> > >
>> > > Hervé
>> > >
>> > > Le dimanche 5 avril 2020, 18:38:50 CEST Stephan Wissel a écrit :
>> > > > I did a flexmark standalone test, happy to try to integrate that.
>> > > > I presume I would define my local moxia modification (after mvn
>> clean
>> > > > install) as a site plugin dependency?
>> > > >
>> > > > Along those lines:
>> > > >
>> > > >
>> > > > org.apache.maven.plugins
>> > > > maven-site-plugin
>> > > > ${maven.site.plugin.version}
>> > > > 
>> > > > 
>> > > > org.apache.maven.plugins
>> > > > doxia-module-markdown
>> > > > 1.9.1-stw
>> > > > 
>> > > > 
>> > > > 
>> > > >
>> > > > Would that work for providing a demo?
>> > > >
>> > > > Create a nice day!
>> > > > Stephan H. Wissel
>> > > >
>> > > > Phone: +65 96673269
>> > > > Blog <https://www.wissel.net/blog> Twitter <
>> > >
>> > > http://twitter.com/notessensei>
>> > >
>> > > > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
>> > > > <https://www.xing.com/profile/StephanH_Wissel>
>> > > >
>> > > > On Sun, Apr 5, 2020 at 10:11 PM Hervé BOUTEMY <
>> herve.bout...@free.fr>
>> > >
>> > > wrote:
>> > > > > nice work: dos it mean that you managed to have the rendering as
>> > >
&

Re: Customizing the maven-site-plugin Markdown renderer?

[Stephan Wissel]

Hello Hervé,

I created a Flexmark sample that is as close as possible to the way
Flexmark is used in Doxia:
https://github.com/Stwissel/maven-site-extension/tree/master/simple-flexmark-example
The result can be seen here:
https://projectcastle.io/sample.html
(I copied a site-plugin generated page and just removed the body part and
replace it with the markdown conversion result)

As it seems, to get Adminition working in the rendering, you need to add a
single line (and the import/dependency of course)
https://github.com/Stwissel/maven-site-extension/blob/master/simple-flexmark-example/src/main/java/com/notessensei/demo/Demo1.java#L78

Would you need more samples?


Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
<https://www.xing.com/profile/StephanH_Wissel>


On Mon, Apr 6, 2020 at 2:42 PM Hervé BOUTEMY  wrote:

> don't hesitate to share every single concrete step, even the flexmark
> standalone test: this will ease working together, ensuring we understand
> each
> other
>
> even before updating doxia-module-markdown with an updated version, there
> is a
> test with a Maven site to be done with the normal Doxia, to show the
> result
> (perhaps there is a partial failure only): this will be interesting to
> compare
> the result against the flexmark standalone test.
>
> then once we'll be at updating doxia-module-markdown, yes, you can
> override
> the version used by the maven-site-plugin by setting dependencies in
> plugin
> definition
>
> Regards,
>
> Hervé
>
> Le lundi 6 avril 2020, 07:12:14 CEST Stephan Wissel a écrit :
> > Sorry for not being clear. The GitHub part is easy.
> > What I'm not sure about is how I can test my modification in the context
> of
> > the site plugin.
> > Would defining my markdown renderer as dependency of the site plugin
> > overwrite the build in renderer or do I have to modify the source of the
> > site plugin too?
> >
> > Create a nice day!
> > Stephan H. Wissel
> >
> > Phone: +65 96673269
> > Blog <https://www.wissel.net/blog> Twitter <
> http://twitter.com/notessensei>
> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > <https://www.xing.com/profile/StephanH_Wissel>
> >
> > On Mon, Apr 6, 2020 at 6:16 AM Hervé BOUTEMY 
> wrote:
> > > you can create a GitHub repository, or a collection of repositories
> > > whatever is necessary
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le dimanche 5 avril 2020, 18:38:50 CEST Stephan Wissel a écrit :
> > > > I did a flexmark standalone test, happy to try to integrate that.
> > > > I presume I would define my local moxia modification (after mvn clean
> > > > install) as a site plugin dependency?
> > > >
> > > > Along those lines:
> > > >
> > > >
> > > > org.apache.maven.plugins
> > > > maven-site-plugin
> > > > ${maven.site.plugin.version}
> > > > 
> > > > 
> > > > org.apache.maven.plugins
> > > > doxia-module-markdown
> > > > 1.9.1-stw
> > > > 
> > > > 
> > > > 
> > > >
> > > > Would that work for providing a demo?
> > > >
> > > > Create a nice day!
> > > > Stephan H. Wissel
> > > >
> > > > Phone: +65 96673269
> > > > Blog <https://www.wissel.net/blog> Twitter <
> > >
> > > http://twitter.com/notessensei>
> > >
> > > > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > > > <https://www.xing.com/profile/StephanH_Wissel>
> > > >
> > > > On Sun, Apr 5, 2020 at 10:11 PM Hervé BOUTEMY  >
> > >
> > > wrote:
> > > > > nice work: dos it mean that you managed to have the rendering as
> > >
> > > expected?
> > >
> > > > > Can you create a little demo and share?
> > > > >
> > > > > On making the extension configurable and easy to use, it will be
> > >
> > > complex
> > >
> > > > > from a
> > > > > Maven Site Plugin perspective: its relationship with Doxia (the
> core
> > > > > rendering
> > > > > engine), Doxia Markdown Module (the markdown parser for Doxia),
> Doxia
> > > > > Sitetools and Doxia Skins will bring some challenges
> > > > >
> &

Re: Customizing the maven-site-plugin Markdown renderer?

[Stephan Wissel]

Sorry for not being clear. The GitHub part is easy.
What I'm not sure about is how I can test my modification in the context of
the site plugin.
Would defining my markdown renderer as dependency of the site plugin
overwrite the build in renderer or do I have to modify the source of the
site plugin too?

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
<https://www.xing.com/profile/StephanH_Wissel>


On Mon, Apr 6, 2020 at 6:16 AM Hervé BOUTEMY  wrote:

> you can create a GitHub repository, or a collection of repositories
> whatever is necessary
>
> Regards,
>
> Hervé
>
> Le dimanche 5 avril 2020, 18:38:50 CEST Stephan Wissel a écrit :
> > I did a flexmark standalone test, happy to try to integrate that.
> > I presume I would define my local moxia modification (after mvn clean
> > install) as a site plugin dependency?
> > Along those lines:
> >
> >
> > org.apache.maven.plugins
> > maven-site-plugin
> > ${maven.site.plugin.version}
> > 
> > 
> > org.apache.maven.plugins
> > doxia-module-markdown
> > 1.9.1-stw
> > 
> > 
> > 
> >
> > Would that work for providing a demo?
> >
> > Create a nice day!
> > Stephan H. Wissel
> >
> > Phone: +65 96673269
> > Blog <https://www.wissel.net/blog> Twitter <
> http://twitter.com/notessensei>
> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > <https://www.xing.com/profile/StephanH_Wissel>
> >
> > On Sun, Apr 5, 2020 at 10:11 PM Hervé BOUTEMY 
> wrote:
> > > nice work: dos it mean that you managed to have the rendering as
> expected?
> > > Can you create a little demo and share?
> > >
> > > On making the extension configurable and easy to use, it will be
> complex
> > > from a
> > > Maven Site Plugin perspective: its relationship with Doxia (the core
> > > rendering
> > > engine), Doxia Markdown Module (the markdown parser for Doxia), Doxia
> > > Sitetools and Doxia Skins will bring some challenges
> > >
> > > That's why we'll need ot go step by step: sharing a first result with a
> > > lot of
> > > manual config first, then looking on improvement to replace manual
> config
> > > with
> > > nice parameters
> > >
> > > I would really love to add such extensions, I'll really need your help
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le vendredi 3 avril 2020, 21:56:41 CEST Stephan Wissel a écrit :
> > > > Hi Hervé,
> > > >
> > > > thank you for your reply, appreciate your swift response.
> > > > It seems to be a little more complex ;-) , but started easy (looked
> like
> > >
> > > 1
> > >
> > > > line and 1 import)
> > > >
> > > > Extensions are loaded like line 145 in the MarkdownParser.class:
> > > > extensions.add(
> > > > AdminitionExtension.create() );
> > > >
> > > > I did a quick check on CSS/JS. When I put them in
> > > > /src/site/resources/css
> > > > and /src/site/resources/js, they get copied into the target site.
> > > > Then I added   
> > > > to the site.xml - which also worked. So the prerequites can be
> handled
> > > > in
> > > > the site.xml without the need to change any code.
> > > >
> > > > However I wouldn't see just to load that one extra plugin always,
> more
> > >
> > > like
> > >
> > > > make it configurable. I see two approaches:
> > > > - read the name of the plugins from a config setting and leave it to
> the
> > > > user - with all consequences - which one they specify
> > > > - pick one (for starters) and have a config true/false flag whether
> to
> > >
> > > load
> > >
> > > > it (default false)
> > > >
> > > > The first might be the more flexible solution, but could add a can of
> > > > (support) worms.
> > > >
> > > > What do you think?
> > > >
> > > > Create a nice day!
> > > > Stephan H. Wissel
> > > >
> > > > Phone: +65 96673269
> > > > Blog <https://www.wissel.net/blog> Twitter <
> > >
> > > http://twitter.com/notessensei>
> > >
> > >

Re: Customizing the maven-site-plugin Markdown renderer?

[Stephan Wissel]

I did a flexmark standalone test, happy to try to integrate that.
I presume I would define my local moxia modification (after mvn clean
install) as a site plugin dependency?
Along those lines:

   
org.apache.maven.plugins
maven-site-plugin
${maven.site.plugin.version}


org.apache.maven.plugins
doxia-module-markdown
1.9.1-stw




Would that work for providing a demo?

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
<https://www.xing.com/profile/StephanH_Wissel>


On Sun, Apr 5, 2020 at 10:11 PM Hervé BOUTEMY  wrote:

> nice work: dos it mean that you managed to have the rendering as expected?
> Can you create a little demo and share?
>
> On making the extension configurable and easy to use, it will be complex
> from a
> Maven Site Plugin perspective: its relationship with Doxia (the core
> rendering
> engine), Doxia Markdown Module (the markdown parser for Doxia), Doxia
> Sitetools and Doxia Skins will bring some challenges
>
> That's why we'll need ot go step by step: sharing a first result with a
> lot of
> manual config first, then looking on improvement to replace manual config
> with
> nice parameters
>
> I would really love to add such extensions, I'll really need your help
>
> Regards,
>
> Hervé
>
> Le vendredi 3 avril 2020, 21:56:41 CEST Stephan Wissel a écrit :
> > Hi Hervé,
> >
> > thank you for your reply, appreciate your swift response.
> > It seems to be a little more complex ;-) , but started easy (looked like
> 1
> > line and 1 import)
> >
> > Extensions are loaded like line 145 in the MarkdownParser.class:
> > extensions.add(
> > AdminitionExtension.create() );
> >
> > I did a quick check on CSS/JS. When I put them in /src/site/resources/css
> > and /src/site/resources/js, they get copied into the target site.
> > Then I added   
> > to the site.xml - which also worked. So the prerequites can be handled in
> > the site.xml without the need to change any code.
> >
> > However I wouldn't see just to load that one extra plugin always, more
> like
> > make it configurable. I see two approaches:
> > - read the name of the plugins from a config setting and leave it to the
> > user - with all consequences - which one they specify
> > - pick one (for starters) and have a config true/false flag whether to
> load
> > it (default false)
> >
> > The first might be the more flexible solution, but could add a can of
> > (support) worms.
> >
> > What do you think?
> >
> > Create a nice day!
> > Stephan H. Wissel
> >
> > Phone: +65 96673269
> > Blog <https://www.wissel.net/blog> Twitter <
> http://twitter.com/notessensei>
> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > <https://www.xing.com/profile/StephanH_Wissel>
> >
> > On Sat, Apr 4, 2020 at 1:55 AM Hervé BOUTEMY 
> wrote:
> > > Hi Stefan,
> > >
> > > The code for Markdown parsing and extensions activation is in Doxia
> > > Markdown module:
> > >
> > >
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-markdown/x
> > > ref/org/apache/maven/doxia/module/markdown/MarkdownParser.html#L133
> > >
> > > I don't really reviewed how extensions are really activated, but having
> > > now a quick look at this admonition one, I see that flexmark-java
> explains
> > > some prerequisites that have not been integrated in Doxia:
> > > https://github.com/vsch/flexmark-java/wiki/Extensions#admonition
> > >
> > > Then I suppose from the code that:
> > > 1. adding admonition markup will create some html
> > > 2. but the rendering will not be ok because prerequisites have not been
> > > integrated
> > > 3. and I fear that the issue will be more complex than these
> prerequisites
> > >
> > > Then it's a full topic to investigate, create samples to test, look at
> > > current result, then debug ot see what improvements are necessary
> > >
> > > I personnally don't have time to work on this, but if a group start
> > > working on this topic, I'd be happy to help
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le vendredi 3 avril 2020, 16:31:49 CEST Stephan Wissel a écrit :
> > > > Hi there,
> > > >
> > > > We are using Markdown in our Maven generated site
> > > > <http://maven.apache.org/

Re: Customizing the maven-site-plugin Markdown renderer?

[Stephan Wissel]

Hi Hervé,

thank you for your reply, appreciate your swift response.
It seems to be a little more complex ;-) , but started easy (looked like 1
line and 1 import)

Extensions are loaded like line 145 in the MarkdownParser.class:
extensions.add(
AdminitionExtension.create() );

I did a quick check on CSS/JS. When I put them in /src/site/resources/css
and /src/site/resources/js, they get copied into the target site.
Then I added   
to the site.xml - which also worked. So the prerequites can be handled in
the site.xml without the need to change any code.

However I wouldn't see just to load that one extra plugin always, more like
make it configurable. I see two approaches:
- read the name of the plugins from a config setting and leave it to the
user - with all consequences - which one they specify
- pick one (for starters) and have a config true/false flag whether to load
it (default false)

The first might be the more flexible solution, but could add a can of
(support) worms.

What do you think?

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog <https://www.wissel.net/blog> Twitter <http://twitter.com/notessensei>
LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
<https://www.xing.com/profile/StephanH_Wissel>


On Sat, Apr 4, 2020 at 1:55 AM Hervé BOUTEMY  wrote:

> Hi Stefan,
>
> The code for Markdown parsing and extensions activation is in Doxia
> Markdown module:
>
> https://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-markdown/xref/org/apache/maven/doxia/module/markdown/MarkdownParser.html#L133
>
> I don't really reviewed how extensions are really activated, but having
> now a quick look at this admonition one, I see that flexmark-java explains
> some prerequisites that have not been integrated in Doxia:
> https://github.com/vsch/flexmark-java/wiki/Extensions#admonition
>
> Then I suppose from the code that:
> 1. adding admonition markup will create some html
> 2. but the rendering will not be ok because prerequisites have not been
> integrated
> 3. and I fear that the issue will be more complex than these prerequisites
>
> Then it's a full topic to investigate, create samples to test, look at
> current result, then debug ot see what improvements are necessary
>
> I personnally don't have time to work on this, but if a group start
> working on this topic, I'd be happy to help
>
> Regards,
>
> Hervé
>
> Le vendredi 3 avril 2020, 16:31:49 CEST Stephan Wissel a écrit :
> > Hi there,
> >
> > We are using Markdown in our Maven generated site
> > <http://maven.apache.org/plugins/maven-site-plugin/index.html>. Works
> like
> > a charm. AFAIK the plugin uses Flexmark
> > <https://github.com/vsch/flexmark-java> under the hood, which supports
> > the Admonition
> > extensions
> > <https://squidfunk.github.io/mkdocs-material/extensions/admonition/>.
> >
> > We would like to use them too, the infoboxes are quite helpful for
> > documentation. Our site configuration in the pom.xml looks like this:
> >
> > 
> > org.apache.maven.plugins
> > maven-site-plugin
> > 3.8.2
> >
> > How could we configure it to recognise the additional markdown?
> >
> > Also can be found here:
> >
> https://stackoverflow.com/questions/61001709/maven-site-generation-using-adv
> > anced-markdown
> >
> > Create a nice day!
> > Stephan H. Wissel
> >
> > Phone: +65 96673269
> > Blog <https://www.wissel.net/blog> Twitter <
> http://twitter.com/notessensei>
> > LinkedIn <http://sg.linkedin.com/in/notessensei> Xing
> > <https://www.xing.com/profile/StephanH_Wissel>
>
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Customizing the maven-site-plugin Markdown renderer?

[Stephan Wissel]

Hi there,

We are using Markdown in our Maven generated site
. Works like
a charm. AFAIK the plugin uses Flexmark
 under the hood, which supports
the Admonition
extensions
.

We would like to use them too, the infoboxes are quite helpful for
documentation. Our site configuration in the pom.xml looks like this:


org.apache.maven.plugins
maven-site-plugin
3.8.2

How could we configure it to recognise the additional markdown?

Also can be found here:
https://stackoverflow.com/questions/61001709/maven-site-generation-using-advanced-markdown

Create a nice day!
Stephan H. Wissel

Phone: +65 96673269
Blog  Twitter 
LinkedIn  Xing