This is actually what I did here:
https://issues.apache.org/jira/projects/MSITE/versions/12354044, but I have no
clue how to upgrade to Maven 4 APIs.
On 2025/03/18 07:22:46 Hervé Boutemy wrote:
> @michaelo I don't know how the plugin works with Maven 4, but perhaps we
> should get to a state wh
@michaelo I don't know how the plugin works with Maven 4, but perhaps we
should get to a state where we can release Maven Site Plugin 4.0.0-alpha1 or
beta1, so the milestones series (not Maven 4 but Doxia 2) is not seen by end
users any more => less confusion
Le mardi 18 mars 2025, 07:55:41 CET
I tried to clarify the 4.0 Milestones series in the version history, that were
upgraded to
3.20.0 (yes, wrong from a mathematical perspective, but right from the intent)
as they
were targetting Doxia 2 (before we have the "plugin 4.x = Maven 4 prerequisite"
convention)
https://maven.apache.o
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 fluido skin requires some update a
On Sat, 17 Apr 2021 at 13:47, Elliotte Rusty Harold
wrote:
> I'd certainly prefer to use a fully supported, maintained, and
> documented framework instead of Plexus. So about Sisu:
>
Sisu is basically a few modules installed on top of Guice to make it more
dynamic, plus a thin compatibility laye
I'd certainly prefer to use a fully supported, maintained, and
documented framework instead of Plexus. So about Sisu:
Where is it documented?
Is it under active development?
When will 1.0 be released?
Which projects besides Maven use it?
On Sat, Apr 17, 2021 at 12:29 PM Tamás Cservenák wrote:
>
To be clear, am talking about this artifact (sisu plexus shim):
https://repo1.maven.org/maven2/org/eclipse/sisu/org.eclipse.sisu.plexus/0.3.4/
Whenever you see plexus-container-default, you SHOULD replace it with this
above (or better yet, convert to plain sisu).
T
On Sat, Apr 17, 2021, 14:25 Ta
Plexus-container-default is NOT (and SHOULD NOT) be used anywhere, but the
drop in sisu-plexus drop replacement should be used instead.
If we use p-c-d anywhere (even in UTs), that's bad, as maven uses s-p
instead.
p-c-d is not used in maven for sure.
T
On Sat, Apr 17, 2021, 14:02 Elliotte Rust
So maybe it is time to start removing unnecessary code ...
There is needed clear decision what component should be removed, what
replaces it.
In order to everybody know direction and target goal.
Eg. plexus-container-default - should be removed at all
org.codehaus.plexus.logging -> sl4j .. and so
plexus-container-default is used by Maven shared utils and thus by
almost everything in Maven. Not that this is a good thing, but c'est
la vie.
There's a lot of over-engineered, unnecessary code splitting between
Maven, Aether, Plexus, and Modello. Maven's a pretty classic example
of why developer
PlexusContainer is used by AbstractDeployMojo: it's a good thing to keep an
explicit direct dependency, even if it's also a transitive
on this class being both in plexus-container and sisu-inject, it's because
sisu-inject is meant to be a replacement: it's not a bug, it's a feature
on runtime e
Sorry, but I have to clarify this "Plexus et al is one of the reasons..."
misleading statement:
It is not Plexus per se THE reason, but the "neglected and stale"
dependencies, or better "dependencies like these"...
T
On Tue, Feb 9, 2021 at 5:38 PM Tamás Cservenák wrote:
> Howdy,
>
> my 5 cents:
Howdy,
my 5 cents:
Something is stale, very stale in there, as plexus-container-default was
abandoned about 10 (maybe 12?) years ago, and sisu "shim"
(sisu-inject-plexus) was created as the direct replacement (as functional
and as API).
If your project has Plexus "the old container" (plexus-cont
Project used class like org.codehaus.plexus.PlexusContainer
We can remove direct dependency because we have transitive dependency
from other artifacts - of course we needn't remove it.
[INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @
maven-site-plugin ---
[WARNING] Using Maven 2 depen
Seems maven dependency:analyze thinks we need this one. At least it
doesn't call it out as unused:
[WARNING] Used undeclared dependencies found:
[WARNING]javax.servlet:javax.servlet-api:jar:3.1.0:compile
[WARNING] Unused declared dependencies found:
[WARNING]org.apache.maven.doxia:doxia-co
What does maven dependency:analyze say?
On Tue, Feb 9, 2021 at 2:25 PM Emmanuel Bourg wrote:
>
> Hi,
>
> maven-site-plugin has a dependency on sisu-inject-plexus [1] but it
> doesn't seem to be used. The project still builds and the tests pass
> without it.
>
> Is it safe to assume it can be remo
Le mercredi 20 mai 2020, 10:10:12 CEST Olivier Lamy a écrit :
> Hervé,
>
> On Wed, 20 May 2020 at 17:06, Hervé BOUTEMY wrote:
> > instead of continuing discussion here and there about Maven and Java
> > prerequisites, I started to describe our past plan to work on defining our
> > future plan:
>
Some commit cleanup can be done but in general +1 from me.
Sylwester
wt., 19 maj 2020 o 09:17 Karl Heinz Marbaise napisał(a):
> Hi,
>
> On 19.05.20 07:45, Olivier Lamy wrote:
> > Hi
> > Any objections for this PR
> > https://github.com/apache/maven-site-plugin/pull/21 ?
> > I prefer to ask rath
Hervé,
On Wed, 20 May 2020 at 17:06, Hervé BOUTEMY wrote:
> instead of continuing discussion here and there about Maven and Java
> prerequisites, I started to describe our past plan to work on defining our
> future plan:
> https://maven.apache.org/developers/compatibility-plan.html
I do not di
instead of continuing discussion here and there about Maven and Java
prerequisites, I started to describe our past plan to work on defining our
future plan:
https://maven.apache.org/developers/compatibility-plan.html
Don't hesitate to contribute
on the future upgrade of prerequisites, one usefu
Hi,
On 19.05.20 07:45, Olivier Lamy wrote:
Hi
Any objections for this PR
https://github.com/apache/maven-site-plugin/pull/21 ?
I prefer to ask rather than seeing my commit reverted
+1 from me.
Kind regards
Karl Heinz Marbaise
--
On Mon, 8 Jul 2019 at 17:31, Tibor Digana wrote:
> Hello Olivier,
>
> After seen the repo, it was obvious that Jetty was developed in three code
> lines namely 9.2.x, 9.3.x and 9.4.x.
> The next fact is that the Maven team agreed to use Java compiler 1.7. The
> user can use JDK 1.8 or higher with
Hello Olivier,
After seen the repo, it was obvious that Jetty was developed in three code
lines namely 9.2.x, 9.3.x and 9.4.x.
The next fact is that the Maven team agreed to use Java compiler 1.7. The
user can use JDK 1.8 or higher with security patches.
These two facts mean that we can stick to t
Please update the jira[1] with a more descriptive title really saying what
it does. (maybe saying "We are not ready to use java 8 that's modern for
us..")
Sorry to be so sarcastic but It's really ridiculous "Back to the future"
change..
Please note first I wanted to veto this commit but honestl
On 15 Apr 2018, at 1:29 AM, Hervé BOUTEMY wrote:
> yes, this will require a xhtml5 Doxia sink
>
> since each skin defines a site template as direct html source (without Doxia
> interaction), the maven-site-plugin switch from xhtml to xhtml5 would have to
> be done on configuration from the ski
On 15 Apr 2018, at 1:29 AM, Hervé BOUTEMY wrote:
> yes, this will require a xhtml5 Doxia sink
>
> since each skin defines a site template as direct html source (without Doxia
> interaction), the maven-site-plugin switch from xhtml to xhtml5 would have to
> be done on configuration from the ski
Hi,
yes, this will require a xhtml5 Doxia sink
since each skin defines a site template as direct html source (without Doxia
interaction), the maven-site-plugin switch from xhtml to xhtml5 would have to
be done on configuration from the skin: looks like a good addition to skin
model [1]
finall
Hi,
I must confess I don't know any report plugin doing a multi-page: if someone
knows about any eisting report plugin, don't hesitate to share.
But the general idea is that with the SinkFactory instance you get from
MavenMultiPageReport.generate( Sink sink, SinkFactory sinkFactory, Locale
loc
Hi Hervé,
Tunaki propose to update the PR with an IT based on a push on local file
... more simple & sustainable, and will push it.
Many thanks to you.
Best regards.
2016-10-13 8:44 GMT+02:00 Hervé BOUTEMY :
> Hi Alix,
>
> Thanks for the patch: I'll review it this WE.
>
>
> See you soon at next
Hi Alix,
Thanks for the patch: I'll review it this WE.
See you soon at next Paris Hackergarten Meetup :)
http://www.meetup.com/fr-FR/Paris-Hackergarten/
If other people near Paris are interested, don't hesitate to come also.
And if other Maven devs are involved in equivalent meetings in other
Hi Petar,
I didn't have time to ask before: what entries do you want to publish in a
feed?
Reading the code, IIUC, you propose to publish each menu entry as feed entry:
I don't see how this can be useful, be in for the main Maven site or any site
generated by maven-site-plugin.
Please open a J
Hello,
I didn't get any feedback if the RSS/Atom feeds for the site would be of
any benefit for the team, so I decided to implement it. Here's a pull
request
https://github.com/apache/maven-plugins/pull/37
that could be used as a base for this feature. The implementation is far
from perfect, but
ok for me
For Doxia and Doxia Sitetools, I'd like these release to be the last ones on
JDK 1.4, and work on Java 5 migration after the release if nobody objects.
Regards,
Hervé
Le mercredi 16 mars 2011, Dennis Lundberg a écrit :
> Hi
>
> I've gone through JIRA tonight and have made sure that
Thanks Lukas,
Yes, I did see your comment, and I could update the patch if/when necessary.
Feel free to test it and let me know if/how we could improve it.
Yevgeny
On Thu, Mar 17, 2011 at 4:03 AM, Lukas Theussl wrote:
>
> Dear Yevgeny,
>
> I had a quick look at your patch and saw that it modi
Dear Yevgeny,
I had a quick look at your patch and saw that it modifies the decoration
model. IMO this change should go into a major new version of doxia, not
the point release we are targeting now. The patch also modifies
maven-base.css, which I feel uncomfortable about. That said, I haven't
Dennis, what's the plan for MSITE-41? I was actually thinking on building up
on that change and continue to work on improving locale switcher and the
default velocity template. It's been a few months since I sent you guys my
changes and didn't hear much so far. Starting to feel a little frustrated.
Dennis Lundberg wrote:
Hi
I've gone through JIRA tonight and have made sure that fixed issues have
the correct fix version(s), as many issues have been fixed for both 2.3
and 3.0-beta-4.
Looking at the road map [1] there are 24 of 25 issues fixed for 2.3 and
29 of 30 issues fixed for 3.0-beta
On 17-Jun-09, at 7:55 AM, Olivier Lamy wrote:
Hi,
Thanks for the tip.
But as I see you have patched the trunk to fix that (thanks
again :-) ).
Just FYI, as I have started some work on maven-site-plugin [1], I have
discovered we can't use anymore the current plugin testing harness
when a
pl
On 17-Jun-09, at 7:55 AM, Olivier Lamy wrote:
Hi,
Thanks for the tip.
But as I see you have patched the trunk to fix that (thanks
again :-) ).
Just FYI, as I have started some work on maven-site-plugin [1], I have
discovered we can't use anymore the current plugin testing harness
when a
pl
Yes, we are fixing it now.
-Original Message-
From: oliver.l...@gmail.com [mailto:oliver.l...@gmail.com] On Behalf Of Olivier
Lamy
Sent: Friday, March 13, 2009 5:26 AM
To: Maven Developers List
Subject: Fwd: maven-site-plugin pre 2.0 not in maven-metadata.xml
Hi,
First sorry for cross po
Hi Fabrice,
This is definitely not the intended behaviour - sounds like a bug.
FWIW, I've successfully built sites in this fashion before - so
perhaps you could expand on how you do this (perhaps a sample project?).
Thanks,
Brett
On 07/07/2007, at 1:05 AM, Fabrice Bellingard wrote:
Hi g
Also worthy of note is MSITE-209 which I found a couple of weeks ago (been
on holiday)
J
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: 16 January 2007 19:53
To: Maven Developers List
Subject: Re: Maven Site Plugin
The @deprecated tag seems broken BTW.
Does
Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Monday, January 15, 2007 10:08 PM
To: Maven Developers List
Subject: Re: Maven Site Plugin
On 12/17/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> The maven-site-plugin should be good now.
This problem is back. When site.xml contains ${mod
Can someone confirm where the @since info ends up on the generated
plugin pages? I haven't seen that info anywhere.
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Monday, January 15, 2007 10:08 PM
To: Maven Developers List
Subject: Re: Maven Site Plugin
On
On 12/17/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
The maven-site-plugin should be good now.
This problem is back. When site.xml contains ${modules}, I get:
[INFO]
[ERROR] BUILD ERROR
[INFO] -
On 18/12/2006, at 1:49 AM, Kenney Westerhof wrote:
(btw mvn site takes about 4 minutes since it pings all snapshot
repos multiple
times for each artifact)
How recent is your 2.1 build? I thought I recently fixed that.
- Brett
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jason,
[cut]
>> thanks for your work. I tried to build my site with maven 2.0.4. and
>> maven-site-plugin 2.0-SNAPSHOT and now javadoc seems to work even if
>> the site is staged (site:stage). I do not know if that was intended by your
>> fix.
>>
On 17 Dec 06, at 10:27 AM 17 Dec 06, Kenney Westerhof wrote:
Yes - built from trunk. The jar includes it. But see below:
Now for some of the new classworlds magic! :-) Don't be frightened :-)
which is to be expected. Too bad this doesn't work, since all
reporting plugins are really
plug
Jason van Zyl wrote:
On 17 Dec 06, at 9:49 AM 17 Dec 06, Kenney Westerhof wrote:
Ok, I've tested with my schemadoc-maven-plugin
(svn://svn.neonics.com/m2-plugins/trunk/schemadoc-maven-plugin)
(after purging local repo and rebuilding plugin-tools and
plugin-plugin since I require qdox 1.6):
On 17 Dec 06, at 9:49 AM 17 Dec 06, Kenney Westerhof wrote:
Ok, I've tested with my schemadoc-maven-plugin (svn://
svn.neonics.com/m2-plugins/trunk/schemadoc-maven-plugin)
(after purging local repo and rebuilding plugin-tools and plugin-
plugin since I require qdox 1.6):
I'm testing the Maven
Ok, I've tested with my schemadoc-maven-plugin
(svn://svn.neonics.com/m2-plugins/trunk/schemadoc-maven-plugin)
(after purging local repo and rebuilding plugin-tools and plugin-plugin since I
require qdox 1.6):
I'm testing the MavenMultiPage report - I'm assuming others are testing the
normal r
The maven-site-plugin should be good now.
Jason.
On 17 Dec 06, at 8:16 AM 17 Dec 06, Kenney Westerhof wrote:
Hi Jason,
In trunk, I'm finding 2 maven-site-plugin dirs: maven-site-plugin
and maven-site-plugin-with-compat-for-2.0.4
There are lots of changes between these two - almost all files
a
Hi Jason,
In trunk, I'm finding 2 maven-site-plugin dirs: maven-site-plugin
and maven-site-plugin-with-compat-for-2.0.4
There are lots of changes between these two - almost all files
are different (mostly license headers).
Which version is the right one? Which one will be merged to the other?
Sh
On 16 Dec 06, at 6:32 PM 16 Dec 06, Joerg Hohwiller wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason van Zyl wrote:
Hi,
Hi Jason,
thanks for your work. I tried to build my site with maven 2.0.4. and
maven-site-plugin 2.0-SNAPSHOT and now javadoc seems to work even if
the site is s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason van Zyl wrote:
> Hi,
Hi Jason,
thanks for your work. I tried to build my site with maven 2.0.4. and
maven-site-plugin 2.0-SNAPSHOT and now javadoc seems to work even if
the site is staged (site:stage). I do not know if that was intended by your
On 15 Dec 06, at 2:35 PM 15 Dec 06, Wendy Smoak wrote:
On 12/15/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I'll work with you today if you have time and we'll try out the
struts site.
It ran with no errors on the Struts 1.x and top-level sites, but I
won't have time to make sure everything
On 12/15/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I'll work with you today if you have time and we'll try out the
struts site.
It ran with no errors on the Struts 1.x and top-level sites, but I
won't have time to make sure everything looks okay until tomorrow
afternoon.
--
Wendy
Wendy,
I'll work with you today if you have time and we'll try out the
struts site. The ${modules} reference will now be replaced with the
new references. I put back in support for all the legacy stuff I
noticed as it changed drastically from beta-5 to the present. The
configuration for t
On 15 Dec 06, at 3:03 AM 15 Dec 06, Brett Porter wrote:
I haven't looked, but this can't be right. Thte only things you
need to match are:
- doxia-sink-api
- maven-reporting-api
I started with the doxia version that was in 2.0.4 to make sure there
were no problems. So I've whittled it do
I haven't looked, but this can't be right. Thte only things you need
to match are:
- doxia-sink-api
- maven-reporting-api
These are quite small, but were impacted by Kenney's change which is
where the incompat. came in. I have certainly used newer doxia site
renderer/etc. code with maven 2.
On 14 Dec 06, at 11:29 PM 14 Dec 06, Wendy Smoak wrote:
On 12/14/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I have managed to get the site plugin working with 2.0.4 and it
really wasn't a simple matter of rolling back some stuff.
...
Thanks for doing this. But... (you knew it was coming)
On 12/14/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I have managed to get the site plugin working with 2.0.4 and it
really wasn't a simple matter of rolling back some stuff.
...
Thanks for doing this. But... (you knew it was coming) I'm having
trouble with it when site.xml contains ${modul
On 07/11/2006, at 3:07 AM, Kenney Westerhof wrote:
I don't think rollback is the way to go, but since we're almost
releasing 2.0.5 I'd like
to suggest that we merge the reporting api changes to the 2.0.x
branch.
That might be the best path forward, though I'm generally reluctant
to make
Mike Perham wrote:
The only thing keeping the site plugin from compiling out of the box on
my machine is a reliance on an unpublished plexus-velocity version. If
this component is stable, can it be released for ease of development?
This was sorted out a few days ago, for the record.
As a si
64 matches
Mail list logo
