Hi Hervé,
On 2/19/16 12:22 AM, Hervé BOUTEMY wrote:
Hi Karl Heinz,
I know this issue: I opened https://issues.apache.org/jira/browse/INFRA-10688
a few months ago with description of the issue and ideas of fixes.
Without success...
Hm...do you think this is related to the currently not working
You should try `mvn clean install -DskipTests`
Putting package in there is redundant (in most cases), as install is later
in the maven build lifecycle and will include the package phase, and it's
probably triggering a second lifecycle execution (only up to the package
phase) after it goes through
The Apache Maven team is pleased to announce the release of the Apache Maven
Site Plugin, version 3.5
The Site Plugin is used to generate a site for the project. The generated site
also includes the project's reports that were configured in the POM.
http://maven.apache.org/plugins/maven-site-
Hi,
The vote has passed with the following result:
+1 : Michael Osipov, Andreas Veithen, Olivier Lamy, Hervé Boutemy
-1 : jieryn
PMC quorum reached
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail
Here is my +1
Regards,
Hervé
Le lundi 15 février 2016 01:55:07 Hervé BOUTEMY a écrit :
> Hi,
>
> After Doxia 1.7 and Doxia Sitetools 1.7, we're now at the user-visible
> release: Maven Site Plugin 3.5
> Notice there are breaking changes to know when upgrading:
> http://maven.apache.org/plugins-
Hi Karl Heinz,
I know this issue: I opened https://issues.apache.org/jira/browse/INFRA-10688
a few months ago with description of the issue and ideas of fixes.
Without success...
Regards,
Hervé
Le jeudi 18 février 2016 12:58:16 Karl Heinz Marbaise a écrit :
> Hi,
>
> currently all download pa
+1
On 15 February 2016 at 11:55, Hervé BOUTEMY wrote:
> Hi,
>
> After Doxia 1.7 and Doxia Sitetools 1.7, we're now at the user-visible
> release: Maven Site Plugin 3.5
> Notice there are breaking changes to know when upgrading:
>
> http://maven.apache.org/plugins-archives/maven-site-plugin-LATES
the quorum is not reached: nobody to test the plugin?
Currently, the only issues found are expected and documented changes
Regards,
Hervé
Le lundi 15 février 2016 01:55:07 Hervé BOUTEMY a écrit :
> Hi,
>
> After Doxia 1.7 and Doxia Sitetools 1.7, we're now at the user-visible
> release: Maven S
Le lundi 15 février 2016 11:06:19 Michael Osipov a écrit :
> +1, though there are some minor doc issues related to MSITE-759.
don't hesitate to improve the docs: I'll publish the updates when clogin the
release
> Downgrade advise for Velocity should have noted with caution because there
> is no g
Github user asfgit closed the pull request at:
https://github.com/apache/maven/pull/78
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enable
Am 2016-02-18 um 21:58 schrieb Andreas Veithen:
On Thu, Feb 18, 2016 at 8:36 PM, Michael Osipov wrote:
Am 2016-02-18 um 20:56 schrieb Andreas Veithen:
-1 (non binding).
I think that somehow inheritance for the element is broken. I
have a project that configures a Google Analytics snippet in
On Thu, Feb 18, 2016 at 8:36 PM, Michael Osipov wrote:
> Am 2016-02-18 um 20:56 schrieb Andreas Veithen:
>>
>> -1 (non binding).
>>
>> I think that somehow inheritance for the element is broken. I
>> have a project that configures a Google Analytics snippet in the root
>> module's site descriptor
Am 2016-02-18 um 20:56 schrieb Andreas Veithen:
-1 (non binding).
I think that somehow inheritance for the element is broken. I
have a project that configures a Google Analytics snippet in the root
module's site descriptor. I changed that to use a CDATA section and
that works for the root modul
Github user michael-o commented on the pull request:
https://github.com/apache/maven/pull/70#issuecomment-185895693
@barthel much but I won't be able to take a closer at it before next week.
@jvanzyl if you can do it sooner, just go again and do it.
---
If your project is set up for
Github user barthel commented on the pull request:
https://github.com/apache/maven/pull/70#issuecomment-185894318
@dinoboy197 : Fantastic. Thanks for your help. After reading your post, it
sounds so logical.
@michael-o , @jvanzyl : Now the merge comes true? :-D
---
If your p
-1 (non binding).
I think that somehow inheritance for the element is broken. I
have a project that configures a Google Analytics snippet in the root
module's site descriptor. I changed that to use a CDATA section and
that works for the root module, but the element is ignored in
submodules. The
Am 2016-02-18 um 19:07 schrieb jieryn:
-1, non-binding, mvn-3.3.9, openjdk 1.8.0_71 ... works with 3.4, fails with 3.5
src/site/site.xml snippet
mvn-3.3.9 log:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.5:run (default-cli) on
pr
Github user dinoboy197 commented on the pull request:
https://github.com/apache/maven/pull/70#issuecomment-185839435
@barthel - I think all you should need to do is to rebase your feature
branch (MNG-3092) against upstream/master.
Something like this should do it (assuming tha
-1, non-binding, mvn-3.3.9, openjdk 1.8.0_71 ... works with 3.4, fails with 3.5
src/site/site.xml snippet
mvn-3.3.9 log:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.5:run (default-cli) on
project parent: Unable to set up webapp: SiteToo
Guys, vote are cheap these days. Please help Hervé and me to finalize
this release.
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Github user michael-o commented on the pull request:
https://github.com/apache/maven-wagon/pull/23#issuecomment-185731400
It wasn't one because we added documentation benefit to the issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user hyPiRion closed the pull request at:
https://github.com/apache/maven-wagon/pull/23
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature i
Github user hyPiRion commented on the pull request:
https://github.com/apache/maven-wagon/pull/23#issuecomment-185701951
Alright, sorry for the disturbance.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user michael-o commented on the pull request:
https://github.com/apache/maven-wagon/pull/23#issuecomment-185689164
If I were at Ivy, I would have reject the PR at all. It is silly to
workaround such isues if you can fix the root cause. What repo managers are we
talking about? I
Github user michael-o commented on the pull request:
https://github.com/apache/maven-wagon/pull/23#issuecomment-185688540
If I were at Ivy, I would have reject the PR at all. It is silly to
workaround such isues if you can fix the root cause. What repo managers are we
talking about? I
Hi,
currently all download pages for plugins look broken...
I have opened a issue at INFRA[1] is there something what we can do ?
Kind regards
Karl Heinz Marbaise
[1]: https://issues.apache.org/jira/browse/INFRA-11290
-
To uns
Github user hyPiRion commented on the pull request:
https://github.com/apache/maven-wagon/pull/23#issuecomment-185625955
> > Some maven repositories may respond with 204 NO CONTENT instead of 200
OK when sending in HTTP HEAD requests.
>
> If so, they are violating the RFCs. Fi
27 matches
Mail list logo
