Re: [PR] [MSITE-1010] Add documentation how site repository inheritance [maven-site-plugin]

jira-importer commented on PR #194: URL: https://github.com/apache/maven-site-plugin/pull/194#issuecomment-2974825655 Resolve #1141 -- 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 c

Re: Maven site plugin 4 documentation

gt; > > https://maven.apache.org/plugins/maven-site-plugin/history.html#maven-site-p > > lugin-vs-doxia-vs-doxia-sitetools[1] > > Le lundi 17 mars 2025, 21:00:27 CET Michael Osipov a écrit : > > > 4.x is reserved for Maven 4.x. Stick with 3.x+ > > > > >

Re: Maven site plugin 4 documentation

+ > > > > On 2025/03/17 13:50:39 Tony Chemit wrote: > > > Hi, > > > > > > I can't find any documentation about this plugin, everything is still > > > on version 3.x. > > > > > > Should I stay on the 3.x versions ? > > > &g

Re: Maven site plugin 4 documentation

n) https://maven.apache.org/plugins/maven-site-plugin/history.html#maven-site-plugin-vs-doxia-vs-doxia-sitetools[1] Le lundi 17 mars 2025, 21:00:27 CET Michael Osipov a écrit : > 4.x is reserved for Maven 4.x. Stick with 3.x+ > > On 2025/03/17 13:50:39 Tony Chemit wrote: > > Hi, > > >

Re: Maven site plugin 4 documentation

4.x is reserved for Maven 4.x. Stick with 3.x+ On 2025/03/17 13:50:39 Tony Chemit wrote: > Hi, > > I can't find any documentation about this plugin, everything is still > on version 3.x. > > Should I stay on the 3.x versions ? > > Using the last version of the flu

Maven site plugin 4 documentation

Hi, I can't find any documentation about this plugin, everything is still on version 3.x. Should I stay on the 3.x versions ? Using the last version of the fluido skin requires some update aroud doxia which is not presetn of the version 4.x of the site plugin. I am a bit lost about

Re: Documentation for 4.x/3.x plugins and components

sounds good. +1. Thanks On Sat, Feb 8, 2025 at 12:49 PM Slawomir Jaranowski wrote: > > Hi, > > After discussion I think that model like: > > https://maven.apache.org/plugins/maven-clean-plugin/ > - documentation for branch 3.x > > https://maven.apache.org/plu

Re: Documentation for 4.x/3.x plugins and components

Hi, After discussion I think that model like: https://maven.apache.org/plugins/maven-clean-plugin/ - documentation for branch 3.x https://maven.apache.org/plugins/maven-clean-plugin-4.x/ - documentation for master version 4.x and according to above for stage version https://maven.apache.org

Re: Documentation for 4.x/3.x plugins and components

ter the release final version of Maven 4. Software deployment moves a lot slower than devs would like. I don't expect Maven 4 to be more common than Maven 3 this decade. If Maven 4 isn't a drop-in replacement for Maven 3, then maybe not next decade either. When it comes to documentation, w

Re: Documentation for 4.x/3.x plugins and components

.apache.org/plugins/maven-clean-plugin-4.x/ > > > > > > and https://maven.apache.org/plugins/maven-clean-plugin/ [or LATEST] > > > > > > points to 3.x now, when 4 is release to 4.x, when 5 is released on 5.x, > > > ... > > > > > > -- > &

Re: Documentation for 4.x/3.x plugins and components

On Fri, 7 Feb 2025 at 07:44, Hervé Boutemy wrote: > > site plugin has a big history of parallel 3 vs 4: it's probably a good > location to look at for learning As I remember we didn't talk about documentation publishing for both versions. > > need to add new columns to

Re: Documentation for 4.x/3.x plugins and components

maven-clean-plugin-3.x/ > > > > > > > > https://maven.apache.org/plugins/maven-clean-plugin-4.x/ > > > > > > > > and https://maven.apache.org/plugins/maven-clean-plugin/ [or LATEST] > > > > > > > > points to 3.x now, when 4 is release to 4

Re: Documentation for 4.x/3.x plugins and components

g/plugins/maven-clean-plugin/ [or LATEST] > > > > > > points to 3.x now, when 4 is release to 4.x, when 5 is released on 5.x, > > > ... > > > > > > -- > > > Matthias > > > > > > Am 06.02.2025 um 10:41 schr

Re: Documentation for 4.x/3.x plugins and components

clean-plugin/ [or LATEST] > > > > points to 3.x now, when 4 is release to 4.x, when 5 is released on 5.x, > > ... > > > > -- > > Matthias > > > > Am 06.02.2025 um 10:41 schrieb Slawomir Jaranowski: > > > Hi, > > > > > > Maybe in su

Re: Documentation for 4.x/3.x plugins and components

-plugin/ [or LATEST] > > points to 3.x now, when 4 is release to 4.x, when 5 is released on 5.x, ... > > -- > Matthias > > Am 06.02.2025 um 10:41 schrieb Slawomir Jaranowski: > > Hi, > > > > Maybe in such way: > > > > https://maven.apache

Re: Documentation for 4.x/3.x plugins and components

5 is released on 5.x, ... -- Matthias Am 06.02.2025 um 10:41 schrieb Slawomir Jaranowski: Hi, Maybe in such way: https://maven.apache.org/plugins/maven-clean-plugin/ - documentation for branch 3.x https://maven.apache.org/plugins/maven-clean-plugin-4.x/ - documentation for master version

Re: Documentation for 4.x/3.x plugins and components

Hi, Maybe in such way: https://maven.apache.org/plugins/maven-clean-plugin/ - documentation for branch 3.x https://maven.apache.org/plugins/maven-clean-plugin-4.x/ - documentation for master version 4.x and according to above for stage version https://maven.apache.org/plugins-archives/maven

Re: Documentation for 4.x/3.x plugins and components

.x, > probably more will be in the future. > > Proposition to have 4.x documentation as in now, and add suffix -3.x > for 3.x versions, example: > > https://maven.apache.org/plugins/maven-clean-plugin/ - documentation > for master branch 4.x > https://maven.apache.org/plugins/m

Documentation for 4.x/3.x plugins and components

Hi, We have some plugins in both versions for Maven 4.x and for 3.x, probably more will be in the future. Proposition to have 4.x documentation as in now, and add suffix -3.x for 3.x versions, example: https://maven.apache.org/plugins/maven-clean-plugin/ - documentation for master branch 4.x

Re: The problem with the lack of documentation

Yes, those not in maven-api-impl are deprecated (should be marked as such). This is true for all classes that have counterpart (copy) in api-impl. T On Sun, Sep 22, 2024, 13:52 Martin Desruisseaux < martin.desruisse...@geomatys.com> wrote: > Hello > > I just realized that there is two "DefaultMo

Re: The problem with the lack of documentation

Hello I just realized that there is two "DefaultModelPathTranslator" classes with almost identical code: one in the "maven-model-builder" module and one in the "maven-api-impl" module. I presume that one of them is deprecated in the favor of the other? If so, can we put a @Deprecated annotati

Re: The problem with the lack of documentation

Le 2024-09-21 à 17 h 45, Tamás Cservenák a écrit : PR seems ok https://github.com/apache/maven/pull/1735 @Martin Desruisseaux pls confirm is this what you had in mind? Yes, this is my guess of what was intended. Thanks!     Martin ---

Re: The problem with the lack of documentation

gt;> > > >> > I'm starting to work on a prototype using the new build element > >> > (a proposal for a unified replacement for , > >> > , , etc.) proposed in a previous discussion on > >> > this mailing list. For starting, I'm searching f

Re: The problem with the lack of documentation

Le 2024-09-21 à 16 h 43, Tamás Cservenák a écrit : AFAIK, as I see, the point is that it nullifies if "default" value is present, and those come from corresponding super POM? Basically, keep only the non-default values? But just above that method, there is another method which performs the

Re: The problem with the lack of documentation

or , >> > , , etc.) proposed in a previous discussion on >> > this mailing list. For starting, I'm searching for usages of >> > in Maven source code and I try to add codes doing >> > something equivalent for . >> > >> > However, a difficulty I

Re: The problem with the lack of documentation

r , > > , , etc.) proposed in a previous discussion on > > this mailing list. For starting, I'm searching for usages of > > in Maven source code and I try to add codes doing > > something equivalent for . > > > > However, a difficulty I'm facing i

Re: The problem with the lack of documentation

ssion on > this mailing list. For starting, I'm searching for usages of > in Maven source code and I try to add codes doing > something equivalent for . > > However, a difficulty I'm facing is the quasi-absence of documentation > in Maven source code. The vast majority o

The problem with the lack of documentation

something equivalent for . However, a difficulty I'm facing is the quasi-absence of documentation in Maven source code. The vast majority of code has no comment at all. I miss in particular comments that would explain *why* a code is designed the way it is. One example I ha

[DISCUSS][MSC] "How to write plugins" documentation

Hi all, as already mentioned, I will create a mail thread for each epic that we defined for the “Support & Care for Apache Maven” initiative (https://open-elements.com/support-care-maven/). All information about this specific epic can be found at https://github.com/OpenElements/maven-support-c

[DISCUSS][MSC] "How to contribute" documentation

Hi all, as already mentioned, I will create a mail thread for each epic that we defined for the “Support & Care for Apache Maven” initiative (https://open-elements.com/support-care-maven/). All information about this specific epic can be found at https://github.com/OpenElements/maven-support-c

[DISCUSS][MSC] "How to write extensions" documentation

Hi all, as already mentioned, I will create a mail thread for each epic that we defined for the “Support & Care for Apache Maven” initiative (https://open-elements.com/support-care-maven/). All information about this specific epic can be found at https://github.com/OpenElements/maven-support-c

[DISCUSS][MSC] "Maven internals" documentation

Hi all, as already mentioned, I will create a mail thread for each epic that we defined for the “Support & Care for Apache Maven” initiative (https://open-elements.com/support-care-maven/). All information about this specific epic can be found at https://github.com/OpenElements/maven-support-c

[DISCUSS][MSC] "Getting started" documentation

Hi all, as already mentioned, I will create a mail thread for each epic that we defined for the “Support & Care for Apache Maven” initiative (https://open-elements.com/support-care-maven/). All information about this specific epic can be found at https://github.com/OpenElements/maven-support-c

[DISCUSS][MSC] "Best practices" documentation

Hi all, as already mentioned, I will create a mail thread for each epic that we defined for the “Support & Care for Apache Maven” initiative (https://open-elements.com/support-care-maven/). All information about this specific epic can be found at https://github.com/OpenElements/maven-support-c

Re: Mojo Descriptor ... outdated documentation?

and documentation can help other plugin developers. śr., 22 wrz 2021 o 21:33 Tamás Cservenák napisał(a): > Howdy, > > requiresReports is unsupported since Maven 3, unsure if I would add it > doco at all (rather would remove it). > > Thanks > T > > On Wed, Sep 2

[GitHub] [maven-site] michael-o commented on a change in pull request #246: [MNGSITE-246] Adding .mavenrc documentation

michael-o commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r718236995 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project

[GitHub] [maven-site] michael-o commented on a change in pull request #246: [MNGSITE-246] Adding .mavenrc documentation

michael-o commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r718236995 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project

[GitHub] [maven-site] elharo commented on a change in pull request #246: [MNGSITE-246] Adding .mavenrc documentation

elharo commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r717781493 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project You

[GitHub] [maven-site] michael-o commented on a change in pull request #246: [MNGSITE-246] Adding .mavenrc documentation

michael-o commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r673488916 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project

[GitHub] [maven-site] pat-lego commented on a change in pull request #246: [MNGSITE-246] Adding .mavenrc documentation

pat-lego commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r717839471 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project Y

[GitHub] [maven-site] pat-lego commented on a change in pull request #246: [MNGSITE-246] Adding .mavenrc documentation

pat-lego commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r717842723 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project Y

[GitHub] [maven-site] michael-o commented on a change in pull request #246: [MNGSITE-246] Adding .mavenrc documentation

michael-o commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r717840438 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project

[GitHub] [maven-site] pat-lego commented on a change in pull request #246: [MNGSITE-246] Adding .mavenrc documentation

pat-lego commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r717839471 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project Y

[GitHub] [maven-site] michael-o commented on a change in pull request #246: [MNGSITE-246] Adding .mavenrc documentation

michael-o commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r673488916 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project

[GitHub] [maven-site] elharo commented on a change in pull request #246: [MNGSITE-246] Adding .mavenrc documentation

elharo commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r717781493 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project You

Re: Mojo Descriptor ... outdated documentation?

Howdy, requiresReports is unsupported since Maven 3, unsure if I would add it doco at all (rather would remove it). Thanks T On Wed, Sep 22, 2021 at 9:15 PM Slawomir Jaranowski wrote: > Hi, > > We have documentation about the Mojo descriptor and plugin api... [1] > > Its l

Mojo Descriptor ... outdated documentation?

Hi, We have documentation about the Mojo descriptor and plugin api... [1] Its look like params: - executionStrategy - requiresDirectInvocation - inheritByDefault (PluginDescriptorBuilder - use only inheritedByDefault) - requiresReports are not used currently, I was looking in 3.8.x and

[GitHub] [maven-site] elharo merged pull request #261: [MNGSITE-461] Remove IRC contact channel from documentation

elharo merged pull request #261: URL: https://github.com/apache/maven-site/pull/261 -- 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. To unsubscribe, e-mail: dev-unsubscr..

[GitHub] [maven-site] elharo commented on pull request #261: [MNGSITE-461] Remove IRC contact channel from documentation

elharo commented on pull request #261: URL: https://github.com/apache/maven-site/pull/261#issuecomment-922465915 https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-site/job/MNGSITE-461/ -- This is an automated message from the Apache Git Service. To respond to the message, ple

[GitHub] [maven-site] puradawid commented on a change in pull request #261: [MNGSITE-461] Remove IRC contact channel from documentation

puradawid commented on a change in pull request #261: URL: https://github.com/apache/maven-site/pull/261#discussion_r711733178 ## File path: content/markdown/community.md ## @@ -85,8 +85,8 @@ Maven has a number of [Mailing Lists](./mailing-lists.html), and the Maven User List

[GitHub] [maven-site] elharo commented on a change in pull request #261: [MNGSITE-461] Remove IRC contact channel from documentation

elharo commented on a change in pull request #261: URL: https://github.com/apache/maven-site/pull/261#discussion_r711726877 ## File path: content/markdown/community.md ## @@ -85,8 +85,8 @@ Maven has a number of [Mailing Lists](./mailing-lists.html), and the Maven User List is

[GitHub] [maven-site] elharo commented on a change in pull request #261: [MNGSITE-461] Remove IRC contact channel from documentation

elharo commented on a change in pull request #261: URL: https://github.com/apache/maven-site/pull/261#discussion_r711726877 ## File path: content/markdown/community.md ## @@ -85,8 +85,8 @@ Maven has a number of [Mailing Lists](./mailing-lists.html), and the Maven User List is

[GitHub] [maven-site] puradawid opened a new pull request #261: MNGSITE-461 Remove IRC contact channel from documentation

puradawid opened a new pull request #261: URL: https://github.com/apache/maven-site/pull/261 FreeNode's #maven is not active anymore. Replaced with some Slack information is more pointing to the right communication channel. -- This is an automated message from the Apache Git Service. To

Re: Removing IRC channel mentions from official website documentation

it > > just for clarification. > > > > Kind regards > > Enno > > > > From: Bernd Eckenfels > > Sent: Wednesday, September 8, 2021 10:30 PM > > To: Maven Developers List > > Subject: Re: Removing IRC channel me

Re: Removing IRC channel mentions from official website documentation

how would help a great deal, I think, albeit > just for clarification. > > Kind regards > Enno > > From: Bernd Eckenfels > Sent: Wednesday, September 8, 2021 10:30 PM > To: Maven Developers List > Subject: Re: Removing IRC channel mention

Re: Removing IRC channel mentions from official website documentation

lopers List Subject: Re: Removing IRC channel mentions from official website documentation Thanks for bringing this to our attention and I agree we should remove the irc channel in this case. Not sure about the slack since I don’t use it, but the website is not only for the public, it’s also th

Re: Removing IRC channel mentions from official website documentation

documentation Hello all, I have noticed it's misleading for new contributors to find out the proper communication channel for this project. The documentation says there is an IRC channel which topic says "we moved to Slack". Then, it takes some time to figure out a newcomer cannot get in

Removing IRC channel mentions from official website documentation

Hello all, I have noticed it's misleading for new contributors to find out the proper communication channel for this project. The documentation says there is an IRC channel which topic says "we moved to Slack". Then, it takes some time to figure out a newcomer cannot get in, sinc

[GitHub] [maven-site] elharo merged pull request #254: "site documentation" → "web site"

elharo merged pull request #254: URL: https://github.com/apache/maven-site/pull/254 -- 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. To unsubscribe, e-mail: dev-unsubscr..

[GitHub] [maven-site] waldyrious commented on pull request #254: "site documentation" → "web site"

waldyrious commented on pull request #254: URL: https://github.com/apache/maven-site/pull/254#issuecomment-901490383 I've edited this directly on GitHub's web interface, which generates a new commit. Let me know if you'd like me to squash the commits. -- This is an automated message from

[GitHub] [maven-site] waldyrious commented on pull request #254: "site documentation" → "documentation web site"

waldyrious commented on pull request #254: URL: https://github.com/apache/maven-site/pull/254#issuecomment-901489589 Sure, makes sense — will change. -- 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

[GitHub] [maven-site] waldyrious opened a new pull request #254: "site documentation" → "documentation web site"

waldyrious opened a new pull request #254: URL: https://github.com/apache/maven-site/pull/254 Changed the wording to be clearer and more accessible. -- 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

[GitHub] [maven-site] michael-o commented on a change in pull request #246: Adding .mavenrc documentation

michael-o commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r673489743 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project

[GitHub] [maven-site] pat-lego commented on a change in pull request #246: Adding .mavenrc documentation

pat-lego commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r673484045 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project Y

Re: Documentation 404 links

Please create a PR for  https://github.com/apache/maven-toolchains-plugin/blob/master/src/site/apt/index.apt.vm thanks, Robert On 17-7-2021 02:44:32, leerho wrote: The docs page for the maven-toolchains-plugin has 4 non-working links: user mailing list -> https://maven.apache.org/plugins/maven-to

Documentation 404 links

The docs page for the maven-toolchains-plugin has 4 non-working links: user mailing list -> https://maven.apache.org/plugins/maven-toolchains-plugin/mail-lists.html Mail archive -> https://maven.apache.org/plugins/maven-toolchains-

[GitHub] [maven-site] pat-lego opened a new pull request #246: Adding .mavenrc documentation

pat-lego opened a new pull request #246: URL: https://github.com/apache/maven-site/pull/246 -- 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. To unsubscribe, e-mail: dev-un

[GitHub] [maven-site] michael-o commented on a change in pull request #246: Adding .mavenrc documentation

michael-o commented on a change in pull request #246: URL: https://github.com/apache/maven-site/pull/246#discussion_r668139207 ## File path: content/markdown/configure.md ## @@ -80,6 +80,12 @@ Starting with Maven 3.3.1+ you can define JVM configuration via `${maven.project

[GitHub] [maven-site] MartinKanters closed pull request #236: [MNGSITE-444] Add missing reactor documentation

MartinKanters closed pull request #236: URL: https://github.com/apache/maven-site/pull/236 -- 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,

[GitHub] [maven-site] mthmulders commented on a change in pull request #236: [MNGSITE-444] Add missing reactor documentation

tioned there, as CLI flags only exist in the maven-cli module. It would effectively split the page in two: "here's how it works" vs "here's how you can use it". We feel it would make it _harder_ for our users to find the relevant documentation. So, we propos

[GitHub] [maven-site] MartinKanters commented on a change in pull request #236: [MNGSITE-444] Add missing reactor documentation

MartinKanters commented on a change in pull request #236: URL: https://github.com/apache/maven-site/pull/236#discussion_r626841415 ## File path: content/apt/guides/mini/guide-multiple-modules.apt ## @@ -59,25 +75,117 @@ Guide to Working with Multiple Modules Note that only

[GitHub] [maven-site] MartinKanters commented on a change in pull request #236: [MNGSITE-444] Add missing reactor documentation

MartinKanters commented on a change in pull request #236: URL: https://github.com/apache/maven-site/pull/236#discussion_r624514244 ## File path: content/apt/guides/mini/guide-multiple-modules.apt ## @@ -59,25 +75,117 @@ Guide to Working with Multiple Modules Note that only

[GitHub] [maven-site] MartinKanters commented on pull request #236: [MNGSITE-444] Add missing reactor documentation

MartinKanters commented on pull request #236: URL: https://github.com/apache/maven-site/pull/236#issuecomment-830636724 @elharo @hboutemy Thanks for your feedback! I've processed all points. -- This is an automated message from the Apache Git Service. To respond to the message, please lo

[GitHub] [maven-site] hboutemy commented on a change in pull request #236: [MNGSITE-444] Add missing reactor documentation

hboutemy commented on a change in pull request #236: URL: https://github.com/apache/maven-site/pull/236#discussion_r624362868 ## File path: content/apt/guides/mini/guide-multiple-modules.apt ## @@ -59,25 +75,117 @@ Guide to Working with Multiple Modules Note that only "ins

[GitHub] [maven-site] hboutemy commented on a change in pull request #236: [MNGSITE-444] Add missing reactor documentation

hboutemy commented on a change in pull request #236: URL: https://github.com/apache/maven-site/pull/236#discussion_r624362541 ## File path: content/apt/guides/mini/guide-multiple-modules.apt ## @@ -59,25 +75,117 @@ Guide to Working with Multiple Modules Note that only "ins

[GitHub] [maven-site] hboutemy commented on a change in pull request #236: [MNGSITE-444] Add missing reactor documentation

hboutemy commented on a change in pull request #236: URL: https://github.com/apache/maven-site/pull/236#discussion_r624361148 ## File path: content/apt/guides/mini/guide-multiple-modules.apt ## @@ -37,11 +39,25 @@ Guide to Working with Multiple Modules * Collects all the

[GitHub] [maven-site] hboutemy commented on a change in pull request #236: [MNGSITE-444] Add missing reactor documentation

hboutemy commented on a change in pull request #236: URL: https://github.com/apache/maven-site/pull/236#discussion_r624361148 ## File path: content/apt/guides/mini/guide-multiple-modules.apt ## @@ -37,11 +39,25 @@ Guide to Working with Multiple Modules * Collects all the

[GitHub] [maven-site] elharo commented on a change in pull request #236: [MNGSITE-444] Add missing reactor documentation

elharo commented on a change in pull request #236: URL: https://github.com/apache/maven-site/pull/236#discussion_r624241259 ## File path: content/apt/guides/mini/guide-multiple-modules.apt ## @@ -37,11 +39,25 @@ Guide to Working with Multiple Modules * Collects all the a

[GitHub] [maven-site] mthmulders commented on pull request #236: [MNGSITE-444] Add missing reactor documentation

mthmulders commented on pull request #236: URL: https://github.com/apache/maven-site/pull/236#issuecomment-830141468 > I would prefer no priorpritary format/application to be necessary to draw stuff. SVG is preferred or as @hboutemy did a dep over view with LO Draw. I found some .ai

[GitHub] [maven-site] michael-o commented on pull request #236: [MNGSITE-444] Add missing reactor documentation

michael-o commented on pull request #236: URL: https://github.com/apache/maven-site/pull/236#issuecomment-830131062 I would prefer no priorpritary format/application to be necessary to draw stuff. SVG is preferred or as @hboutemy did a dep over view with LO Draw. -- This is an automated

[GitHub] [maven-site] MartinKanters opened a new pull request #236: [MNGSITE-444] Add missing reactor documentation

MartinKanters opened a new pull request #236: URL: https://github.com/apache/maven-site/pull/236 This PR describes most of the changes to the reactor that are coming in Maven 4. @mthmulders and I also extended the existing docs. @elharo We would like to ask you for a review at lea

[GitHub] [maven-site] elharo commented on a change in pull request #235: Updated one typo in pom documentation

elharo commented on a change in pull request #235: URL: https://github.com/apache/maven-site/pull/235#discussion_r621142216 ## File path: content/apt/guides/introduction/introduction-to-the-pom.apt ## @@ -212,8 +212,8 @@ Introduction to the POM parent of our POM. And we do so

[GitHub] [maven-site] lokesh090297 opened a new pull request #235: Updated one typo in pom documentation

lokesh090297 opened a new pull request #235: URL: https://github.com/apache/maven-site/pull/235 -- 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 ser

[GitHub] [maven-doxia] asfgit closed pull request #38: [DOXIA-606] fix javadoc issues with JDK 8 when generating documentation

asfgit closed pull request #38: URL: https://github.com/apache/maven-doxia/pull/38 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 t

[GitHub] [maven-doxia] michaelboyles opened a new pull request #38: [DOXIA-606] fix javadoc issues with JDK 8 when generating documentation

michaelboyles opened a new pull request #38: URL: https://github.com/apache/maven-doxia/pull/38 https://issues.apache.org/jira/browse/DOXIA-606 Boy does this thing take a while to build! ``` [INFO]

Re: [INFRA-16467] move components documentation out of CMS space

:23:11 CEST Karl Heinz Marbaise a écrit : > Hi Hervé, > > On 19/06/18 07:54, Hervé BOUTEMY wrote: > > just tested the full component documentation lifecycle for Maven [1] and > > Doxia [2]: works like a charm > > I can acknowledge that it worked like a charm. &

Re: [INFRA-16467] move components documentation out of CMS space

:23:11 CEST Karl Heinz Marbaise a écrit : > Hi Hervé, > > On 19/06/18 07:54, Hervé BOUTEMY wrote: > > just tested the full component documentation lifecycle for Maven [1] and > > Doxia [2]: works like a charm > > I can acknowledge that it worked like a charm. &

Re: [INFRA-16467] move components documentation out of CMS space

Hi Hervé, On 19/06/18 07:54, Hervé BOUTEMY wrote: just tested the full component documentation lifecycle for Maven [1] and Doxia [2]: works like a charm I can acknowledge that it worked like a charm. Great work. Thanks. Kind regards Karl Heinz Marbaise *IMPORTANT NOTICE: you'll ha

Re: [INFRA-16467] move components documentation out of CMS space

just tested the full component documentation lifecycle for Maven [1] and Doxia [2]: works like a charm *IMPORTANT NOTICE: you'll have to delete your ~/maven-sites cache* since the cache contains svn checkouts to the old location, that will be updated: you need to delete to make the chec

[INFRA-16467] move components documentation out of CMS space

Hi, As you may have noticed from a load of commits, the location for html publication of components documentation is switching from CMS space to ASF repo, as requested by INFRA when working on site migration from svn to Git. see https://issues.apache.org/jira/browse/INFRA-16467 Please wait a

[GitHub] asfgit closed pull request #6: For Groovy/Scala Mojos: Allow Mojo documentation in annotations, too.

asfgit closed pull request #6: For Groovy/Scala Mojos: Allow Mojo documentation in annotations, too. URL: https://github.com/apache/maven-plugin-tools/pull/6 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of

[GitHub] maven-plugins pull request #132: MPDF-48: Update site documentation & non su...

Github user sgarelle closed the pull request at: https://github.com/apache/maven-plugins/pull/132 --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

[GitHub] maven-plugins pull request #132: MPDF-48: Update site documentation & non su...

GitHub user sgarelle opened a pull request: https://github.com/apache/maven-plugins/pull/132 MPDF-48: Update site documentation & non supported report plugins. Ready for 1.4 release. You can merge this pull request into a Git repository by running: $ git pull h

Re: Is the Maven 3 lifecycle extensions documentation page up to date?

this is the last time I mention it :) - Paul On Fri, Jun 2, 2017 at 6:47 AM, Paul Hammant wrote: > The tongue-stickty-outy thing was more about the fact that Maven would be > much better off shifting *all* of is documentation into something where > every page has an edit-this-page link. Even

Re: Is the Maven 3 lifecycle extensions documentation page up to date?

The tongue-stickty-outy thing was more about the fact that Maven would be much better off shifting *all* of is documentation into something where every page has an edit-this-page link. Even if that took the user to a GH page, where you have to do a fork before you can edit some markdown to make a

Re: Is the Maven 3 lifecycle extensions documentation page up to date?

following to > >> > their build (and set some env props - one of which I admit changed in > >> > that > >> > diff, but that's not the problem). > >> > > >> > ... > >> > > >> > > >> >

Re: Is the Maven 3 lifecycle extensions documentation page up to date?

in >> > that >> > diff, but that's not the problem). >> > >> > ... >> > >> > >> > com.paulhammant >> > buildradiatorextension >> > 1.1-SNAPSHOT >> > >> > >> &

Re: Is the Maven 3 lifecycle extensions documentation page up to date?

> ... > > > > > > com.paulhammant > > buildradiatorextension > > 1.1-SNAPSHOT > > > > > > ... > > > > ^ exception that doesn't do anything. > > > > Worse, if I go back to the old way with

Re: Is the Maven 3 lifecycle extensions documentation page up to date?

ldradiatorextension > 1.1-SNAPSHOT > > > ... > > ^ exception that doesn't do anything. > > Worse, if I go back to the old way with the post-diff version (dropping > the > jar into ext/) if doesn't work either. > > TL;DR - EventSpy I made

Is the Maven 3 lifecycle extensions documentation page up to date?

I made won't work with /build/extensions element. Am questioning the documentation. Oh, I'm standing up https://buildradiator.org/ for the benefit of all. Jooby/Java8/Vue.js and a 35 second Maven build including WebDriver tests (tests in three executions from one compilation). - Paul

  1   2   3   4   5   6   7   8   9   10   >