The Apache Maven team is pleased to announce the release of the Maven
Skins Parent version 8
http://maven.apache.org/pom/skins/
You should specify the version in your project's configuration:
plugin
groupIdorg.apache.maven.skins/groupId
artifactIdmaven-skins/artifactId
The Apache Maven team is pleased to announce the release of the Maven
Fluido Skin, version 1.3.1
http://maven.apache.org/skins/maven-fluido-skin/
You should specify the version in your project's site configuration:
skin
groupIdorg.apache.maven.skins/groupId
Hi,
The vote has passed with the following result:
+1 (binding): Olivier Lamy, Hervé Boutemy, Kristian Rosenvold
+1 (non-binding): Maarten Storm
I will promote the artifacts to the central repo.
PMCs please promote the source release ZIP file and add this release the
board report.
The Apache Maven team is pleased to announce the release of the Apache
Maven JXR, version 2.4
This module generates browsable HTML pages from Java source code.
http://maven.apache.org/jxr/
You should specify the version in your project's plugin configuration:
plugin
Am 2013-12-22 01:58, schrieb Olivier Lamy:
done.
Merci!
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Am 2014-01-07 16:25, schrieb Stephen Connolly:
OK we are now at 38 open issues anyone else feel like scrubbing some
more?
I'd like to add another issue to 3.2:
https://jira.codehaus.org/browse/MNG-5176 Print build times in an ISO
8601-style manner
It adds readability to the time output.
Am 2014-01-07 22:38, schrieb Stephen Connolly:
Add it if you promise to implement it, otherwise put it against 3.2.x for
the patch releases.
That is not going to be a problem because I have a patch and can commit
right away.
On Tuesday, 7 January 2014, Michael Osipov wrote:
Am 2014-01-07
Am 2014-01-20 18:32, schrieb Stephen Connolly:
If we are going wholesale dumping issues (and I am not against that), I
have a more radical suggestion... let's just move core to the ASF JIRA...
with next to no issues needing migration it would be easy ;-)
+1
I head this idea in mind for
Am 2014-02-02 11:42, schrieb Hervé BOUTEMY:
good idea: at least, it give good hints on what updates are available
so here is it:
$ mvn versions:display-plugin-updates
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO]
Am 2014-02-03 22:59, schrieb Hervé BOUTEMY:
I just updated some plugins
now, we have:
$ mvn versions:display-plugin-updates
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building The Apache Software Foundation
+1 with a side remark. For those, who still rely on Maven 2 one should
first annouce an EOL roadmap like this:
1. Make the announcement
2. Release 2.2.2 (only one open ticket in JIRA which can me dismissed)
say 4 weeks later and announce that as the last version of 2.x
3. Encourage to switch
Am 2014-02-18 16:26, schrieb Stephen Connolly:
I have set up a chain of build jobs in Jenkins.
The root of the chain is
https://builds.apache.org/job/maven-3.2-release-status/
The certificate has expired today, hopefully infra will fix this ASAP.
Michael
Am 2014-02-22 00:58, schrieb Dennis Lundberg:
Hi,
If anyone wants to add something to the next release of the Checkstyle
plugin, now would be a good time to do it, as I intend to make a
release next week. If you need more time to squeeze something in, just
let me know.
Thanks for that
Am 2014-02-23 19:06, schrieb Benson Margulies:
I propose to make releases of our parent stack that are suitable for
components and plugins that are making the leap to Java 1.6 and Maven
3 as their base requirements.
What do people think is the right approach in terms of what stays on
trunk and
Am 2014-02-01 11:20, schrieb Hervé BOUTEMY:
after m-scm-publish-p 1.0 is released, I intend to release ASF parent pom
Then every Maven parent poms
please have a look at these if you want to be sure your favorite plugin
version + configuration, or you position, is correct
Hervé,
did you check
Am 2014-02-23 21:20, schrieb Stephen Connolly:
On Sunday, 23 February 2014, Michael Osipov micha...@apache.org wrote:
Am 2014-02-23 19:06, schrieb Benson Margulies:
I propose to make releases of our parent stack that are suitable for
components and plugins that are making the leap to Java
Hi folks,
did anyone already check
http://maven.apache.org/docs/3.2.1/release-notes.html?
The link See complete release notes for all versions links to
http://maven.apache.org/ and is missing a period. Release notes not
available.
http://maven.apache.org/ref/3.2.1/ is a 404.
I forgot:
System Requirements: JDK 1.5 or above
Depends on the Mavn version.
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Am 2014-03-07 20:25, schrieb Robert Scholte:
Hi,
This is the standard (preferred) directory layout, so it doesn't have to
be the default.
I actually think that src/main/assembly/ should be src/assembly/,
otherwise it would imply that there can also be a src/test/assembly/. I
wouldn't separate
Am 2014-03-07 20:25, schrieb Robert Scholte:
Hi,
This is the standard (preferred) directory layout, so it doesn't have to
be the default.
I actually think that src/main/assembly/ should be src/assembly/,
otherwise it would imply that there can also be a src/test/assembly/. I
wouldn't separate
Am 2014-03-08 22:24, schrieb Dennis Lundberg:
Hi
I agree with Karl Heinz that the Assembly Plugin should support the
documented default directory.
It seems that we disagree about what the preferred directory should
be. I think it should be src/main/assembly/ because almost all
assemblies I
Am 2014-03-08 23:49, schrieb Dennis Lundberg:
Hi,
We solved 15 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127styleName=Htmlversion=19723
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1
+1, but why not upgrade to 5.1 (MPMD-182) first?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Am 2014-03-12 06:43, schrieb Dennis Lundberg:
I want this release to be Java 5 compatible.
PMD 5.1 requires Java 6, even though it is not mentioned in their release
notes.
Fair enough but unprofessional from the PMD guys.
Michael
Am 2014-03-16 14:52, schrieb Mirko Friedenhagen:
RequireReactorProjectsHaveUniqueVersion?
This does not imply that they have the same version but only unique.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For
Am 2014-03-18 15:29, schrieb Baptiste Mathus:
Hi,
There seems to be a need for a release for buildnumber with @threadSafe
added.
https://jira.codehaus.org/browse/MBUILDNUM-115 and its dups.
I can act as RM if nobody objects against this release now. That'll help
users.
If anyone wants to try
Am 2014-03-17 20:53, schrieb Robert Scholte:
Hi,
On behalf of the Apache Maven PMC I am pleased to announce that Mirko
Friedenhagen (mfriedenhagen) has been voted in as a new Apache Maven
committer.
Mirko, welcome on board and have a lot of fun!
Ein herzliches Willkommen -- schön weitere
Am 2014-05-05 16:20, schrieb Paul Benedict:
One thing that I like about Eclipse is that it contains a log file to
capture the unexpected warning or error. These warnings or errors may not
kill the program but at least I can peer inside to see what's going on.
With regard to MNG-5626, it makes
Hi,
does it take special permissions on Github to process pull requests?
Neither am I allowed to perform the merge from the website directly, nor
does it display the command line steps as described in the GH help.
Close is not available to me too.
I simply pulled (PL 14) into my local repo
Am 2014-05-24 17:38, schrieb Alexander Kriegisch:
As for necessary permissions:
https://help.github.com/articles/what-are-the-different-access-permissions
That's good but how does one know whether he as Write Access Teams
Repository Access' or not. Especially for mirrored repos.
?
https://help.github.com/articles/using-pull-requests
--
Alexander Kriegisch
Am 24.05.2014 um 16:07 schrieb Jason van Zyl ja...@takari.io:
Yes, I'm interested as well.
On May 24, 2014, at 9:33 AM, Michael Osipov micha...@apache.org
wrote:
Hi,
does it take special permissions on Github
Hi,
does it take special permissions on Github to process pull requests?
Neither am I allowed to perform the merge from the website directly, nor
does it display the command line steps as described in the GH help.
Close is not available to me too.
I simply pulled (PL 14) into my local repo
Am 2014-05-26 14:54, schrieb Daniel Kulp:
On May 24, 2014, at 9:18 AM, Michael Osipov mosi...@gmx.de wrote:
Hi,
does it take special permissions on Github to process pull
requests?
Neither am I allowed to perform the merge from the website
directly, nor does it display the command line
Am 2014-05-30 15:57, schrieb Jason van Zyl:
I'm happy to look at pull requests but in the future can anyone making a pull
request please squash your commits before making the pull request.
Eventually I want to use Gerrit and create a mechanism where pull requests can
be tested against the ITs
Am 2014-06-17 18:03, schrieb Jason van Zyl:
Hi,
Time to release Maven 3.2.2!
I am confused?! There are nine unresolved issues for that release. If
you are not going to fix, remove the 'Fix Version' please.
-
To
Hi folks,
has anyone of you ever check the roadmap in JIRA lately?
There are several versions which will probably never be released.
Moveover, all tickets for 2.2.2 are fixed.
Can we clean up upcoming versions?
Are we going to release a EOL 2.2.2?
Thanks,
Michael
Am 2014-06-17 21:17, schrieb Karl Heinz Marbaise:
Hi,
has anyone of you ever check the roadmap in JIRA lately?
There are several versions which will probably never be released.
Moveover, all tickets for 2.2.2 are fixed.
Can we clean up upcoming versions?
Are we going to release a EOL 2.2.2?
? If not, people and me would assume that
it is still being worked on.
On Jun 17, 2014, at 3:05 PM, Michael Osipov micha...@apache.org wrote:
Hi folks,
has anyone of you ever check the roadmap in JIRA lately?
There are several versions which will probably never be released. Moveover, all
tickets for 2.2.2
Am 2014-06-17 21:57, schrieb Jason van Zyl:
On Jun 17, 2014, at 3:47 PM, Michael Osipov micha...@apache.org
wrote:
Am 2014-06-17 21:14, schrieb Jason van Zyl:
Just start nuking/moving/cleaning if you think it makes sense.
Just did for 2.2.x. But are we going to relase 3.0.6 or 3.1.2? I
? If yes, please proceed for Maven.
Michael
On Tue, Jun 17, 2014 at 3:03 PM, Michael Osipov micha...@apache.org wrote:
Am 2014-06-17 21:57, schrieb Jason van Zyl:
On Jun 17, 2014, at 3:47 PM, Michael Osipov micha...@apache.org
wrote:
Am 2014-06-17 21:14, schrieb Jason van Zyl:
Just start
Am 2014-06-24 13:08, schrieb Jason van Zyl:
Hi,
The vote passed with the following result:
+1 (binding): Jason van Zyl, Hervé Boutemy, Olivier Lamy, Arnaud Héritier,
Robert Scholte
+1 (non-binding): Karl-Heinz Marbaise, Mirko Friedenhagen, Mark Derricutt, Igor
Fedorenko, Baptiste Mathus
I
Am 2014-06-26 14:34, schrieb Mark Derricutt:
In last weeks dev hangout I raised the idea of removing repository
elements due to some issues with them regarding mirrors etc which was
somewhat negatively received, however I've been thinking about this a
bit and came up with an interesting idea
Am 2014-06-26 21:41, schrieb Mark Derricutt:
On 27 Jun 2014, at 7:27, Michael Osipov wrote:
2) Deploy transitive runtime dependencies along with your release
This beats DRY and reinvents the wheel.
I would obstain doing either one.
I don't see this as repeating oneself, just about
Am 2014-06-28 00:38, schrieb Hervé BOUTEMY:
Hi,
We solved 6 issues in Doxia base and 7 issues in Doxia Site Tools:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780styleName=Htmlversion=19820
Am 2014-06-28 14:16, schrieb Karl Heinz Marbaise:
Hi,
so after Hervé and I identified the problem of the failing test which is
caused by my ISP (Deutsche Telekom ;-)) which shows me a nice HTML page
instead of simply failing the request to an unknown page(dns failure).
This crap is also
Am 2014-07-01 18:21, schrieb Paul Benedict:
I was just about to bulk change these and but could not find the Send
Email for this Update checkbox. Based on what I read, it's an option only
available to project admins. So... either someone with more karma can do
this change or we just accept 200
Am 2014-07-01 12:59, schrieb Michal Srb:
Hello,
I filed a bug [1] and opened pull request [2] for maven-javadoc-plugin.
Please see links below for context. The real problem seems to be in
javadoc tool, but it can be avoided by not putting compiled project
classes on javadoc's -classpath. The
Am 2014-07-03 21:47, schrieb Hervé BOUTEMY:
nobody?
this is the last intermediate components release before releasing the main
objective: maven-site-plugin 3.4
+2
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
Am 2014-07-07 21:24, schrieb Hervé BOUTEMY:
Hi,
We solved 13 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleName=Htmlversion=19228
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11146status=1
Am 2014-09-05 um 12:32 schrieb WonderCsabo:
Hi guys!
I already posted my question
http://maven.40175.n5.nabble.com/Providing-settings-to-Aether-from-global-and-user-file-td5803227.html
to the users list, but i did not get any answers. I am posting now here,
maybe this kind of question better
Am 2014-09-26 um 21:28 schrieb Robert Scholte:
Hi Michael,
I'm missing action on the wise words from Hervé.
Are you planning to add an IT?
Actually, yes.
Concerning populateCompileArtifactMap, I guess it suffices to create a
sample project with some dependencies and have javadoc link to
Am 2014-09-26 um 21:28 schrieb Robert Scholte:
Hi Michael,
I'm missing action on the wise words from Hervé.
Are you planning to add an IT?
I am already on it.
Op Fri, 26 Sep 2014 21:14:37 +0200 schreef micha...@apache.org:
Author: michaelo
Date: Fri Sep 26 19:14:36 2014
New Revision:
Am 2014-09-26 um 21:28 schrieb Robert Scholte:
Hi Michael,
I'm missing action on the wise words from Hervé.
Are you planning to add an IT?
I have created an IT based off a real project I host on sourceforge.
It replicates MJAVADOC-407. If that is fine, I'd like to roll 2.10.1 on
Saturday.
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138version=20644
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MJAVADOC%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
Staging
We moved core to 1.6 some time ago. Time to move everything else as well ?
Kristian (Who's ready to say 1.7 but we stop by 1.6 first :)
I would favor the move to Java 1.7 if we make strong use of NIO2 for file
operations. A lot of pain should go away.
Michael
Guys,
I need one more binding vote!
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi,
The vote has passed with the following result:
+1 (binding): Karl-Heinz Marbaise, Robert Scholte, Hervé Boutemy,
Olivier Lamy
+1 (non-binding): Mirko Friedenhagen
I will promote the artifacts to the central repo.
PMCs please promote the source release ZIP file and add this release the
The Apache Maven team is pleased to announce the release of the Maven
Javadoc Plugin, version 2.10.1.
This module generates browsable HTML pages from Java source code.
http://maven.apache.org/plugins/maven-javadoc-plugin/
You should specify the version in your project's plugin configuration:
Hi folks,
how do we actually proceed with third-party plugins which do not comply to our
naming pattern [1]?
Given that a plugin has been created before this document has beeen first
published 2013-01-02.
Should they simply add a disclaimer for legacy reasons? What about plugins on
Central
They should rename going forward.
At some point (probably we could do so now) we will turn on enforcement in
the maven-plugin-plugin.
This will of course piss of a lot of people. Wouldn't it?
There are, of course, several reasons why people can't:
1. Popularity of the old name
2. Technical
be enforced.
On Fri, Oct 10, 2014 at 7:25 AM, Michael Osipov 1983-01...@gmx.net
wrote:
They should rename going forward.
At some point (probably we could do so now) we will turn on
enforcement
in
the maven-plugin-plugin.
This will of course piss of a lot of people
this thread in case I happen to be made aware of any
trademark misuse ;-)
On 10 October 2014 13:39, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
Yes
On 10 October 2014 13:12, Michael Osipov 1983-01...@gmx.net wrote:
If you do a quick search on Central, you'll that even other
, Michael Osipov 1983-01...@gmx.net wrote:
Yes, resposibility isn't always good.
Shouldn't simply make the build fail instead of log when such a collision
happens?
Michael
Thankfully for you, you are not on the PMC... if you were on the PMC and
you did such a search you would
Hi,
On 10/10/14 3:41 PM, Paul Benedict wrote:
I would prefer this should be part of Maven Core's warning system. If the
plugin starts with maven- and it's not an org.apache.maven.plugins group,
then we should spit out the error. I am not sure enforcer is the right
place for this rule;
Am 2014-10-11 um 18:39 schrieb Karl Heinz Marbaise:
Hi,
i want to summarize the current state of the maven plugins which can be
found here: http://maven.apache.org/plugins/ which are currently
at the Maven 2.2.1 minimum prerequesites state and which are not.
The following list of plugins do
I'd like to sum up the consensus we have hopefully reached already:
1. Make maven-plugin-plugin fail the build if the plugin being build
does not adhere to our convention (next minor version).
2. Warn a user when a build is performed with a plugin which violates
the naming convention, just
Am 2014-10-11 um 21:03 schrieb Benson Margulies:
I am very tempted to reopen the trademark question here. It seems to
me that this whole business ignores the groupId component of the name,
which distinguishes pretty clearly, and I would argue is enough to
avoid trademark dillution.
Well
Am 2014-10-11 um 21:28 schrieb Robert Munteanu:
On Sat, Oct 11, 2014 at 10:23 PM, Michael Osipov micha...@apache.org wrote:
Well said...
I guess it is all about the order of the words: Maven X Plugin. It simply
implies that is provided by the Maven team. Which is not.
But is the order
Am 2014-10-11 um 21:51 schrieb Robert Scholte:
[...]
maven/site/trunk/content/apt/guides/plugin/guide-java-plugin-development.apt
(original)
+++
maven/site/trunk/content/apt/guides/plugin/guide-java-plugin-development.apt
Sat Oct 11 18:31:32 2014
@@ -508,6 +508,44 @@ mvn archetype:generate \
Am 2014-10-12 um 00:30 schrieb Stephen Connolly:
On Saturday, 11 October 2014, Michael Osipov micha...@apache.org wrote:
Am 2014-10-11 um 21:28 schrieb Robert Munteanu:
On Sat, Oct 11, 2014 at 10:23 PM, Michael Osipov micha...@apache.org
wrote:
Well said...
I guess it is all about
Am 2014-10-12 um 16:10 schrieb Benson Margulies:
On Sun, Oct 12, 2014 at 9:25 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi Robert,
from my point of view minimum to 3.0.5 ...nothing below...afterwards
3.1.1.and then 3.2.1...the latest releases from the appropriate release
lines
Have you received any respone from trademarks@a.o?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi folks,
do we have a policy for Maven dependencies for non-plugins after Karl
Heinz has raised the baseline to 2.2.1?
I'd like to release Maven Archiver and raise dependency versions,
especially Maven to 2.2.1.
Michael
Am 2014-10-26 um 17:32 schrieb Dennis Lundberg:
Hi,
In my opinion the new minimum level of Maven (2.2.1) should cover all of
our projects, not just plugins. Standardizing on a single base version will
also mean less artifacts to download for new Maven installations.
This reminds me of
Hi,
We solved 9 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18325projectId=11761
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/browse/MSHARED-168?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
Am 2014-10-26 um 23:15 schrieb Karl Heinz Marbaise:
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11085version=19853
JXR-116: Doxia is already at 1.6. Shouldn't we upgrade first?
Michael
Hi Michael,
On 10/27/14 7:23 AM, Michael Osipov wrote:
Am 2014-10-26 um 23:15 schrieb Karl Heinz Marbaise:
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11085version=19853
JXR-116: Doxia is already at 1.6. Shouldn't we upgrade first?
Yes
Hi Michael,
there had gone something completely wrongcause
the staging repository is empty...from the given url as well as from the
Nexus...
On 10/27/14 10:45 AM, Mikolaj Izdebski wrote:
On 10/26/2014 10:06 PM, Michael Osipov wrote:
Staging repo:
https
Hi Michael,
there had gone something completely wrongcause
the staging repository is empty...from the given url as well as from the
Nexus...
On 10/27/14 10:45 AM, Mikolaj Izdebski wrote:
On 10/26/2014 10:06 PM, Michael Osipov wrote:
Staging repo:
https
On 10/27/14 11:02 AM, Michael Osipov wrote:
Hi Michael,
On 10/27/14 7:23 AM, Michael Osipov wrote:
Am 2014-10-26 um 23:15 schrieb Karl Heinz Marbaise:
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11085version=19853
JXR-116: Doxia
Am 2014-10-27 um 21:21 schrieb Karl Heinz Marbaise:
Hi Dan,
On 10/27/14 9:01 PM, Dan Tran wrote:
@Karl
Are you planing to release a new maven-jar-plugin?
Thanks
Yeah...working on a missging single issue...apart from the current down
issue of the nexus ...
Am 2014-10-28 um 03:17 schrieb yanshuai:
hi, all,
I found a mistake in slf4j-configuration.properties of maven-embedder project,
org.slf4j.helpers.Log4JLoggerFactory should be
org.slf4j.helpers.Log4jLoggerFactory. Otherwise, when I use log4j2 instead of
slf4j-simple, it will not find the
Nexus operation has been resumed. Please vote/test.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi,
I'd like to fix MPIR-279 and by applying the logic from above. I am
having a hard time to find that spot which actually evalutes the snippet
above.
Does someone know?
Thanks,
Michael
-
To unsubscribe, e-mail:
Am 2014-10-28 um 20:31 schrieb Karl Heinz Marbaise:
Hi,
checked SHA1 Ok..
tested with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.1, 3.2.2, 3.2.3 no issues found.
So +1 from me...
Unfortunately the number of checkstyle errors has increased from 29 in
version 2.5 to 39 in version 2.6...created an
Am 2014-10-26 um 22:06 schrieb Michael Osipov:
Hi,
We solved 9 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18325projectId=11761
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/browse/MSHARED-168?jql=project%20%3D%20MSHARED%20AND%20resolution%20
Am 2014-10-29 um 02:39 schrieb Hervé BOUTEMY:
see doxia-integration-tools DefaultSiteTool populateParentMenu(...) [1] and
populateModulesMenu(...) [2] called by getDecorationModel(...)
then getDecorationModel(...) is called from
AbstractSiteRenderingMojo.createSiteRenderingContext(...)
But
Am 2014-10-29 um 03:24 schrieb Hervé BOUTEMY:
we currently propose 3 versions: 3.0.5, 3.1.1 and 3.2.3
which suppose we may release 3.0.6, 3.1.2 and 3.2.4 in the future
I see why we would release 3.0.6: Aether change force some users to stay to
3.0.x, and I started to define some backports I'd
Am 2014-10-29 um 02:39 schrieb Hervé BOUTEMY:
see doxia-integration-tools DefaultSiteTool populateParentMenu(...) [1] and
populateModulesMenu(...) [2] called by getDecorationModel(...)
then getDecorationModel(...) is called from
AbstractSiteRenderingMojo.createSiteRenderingContext(...)
But
Am 2014-10-29 um 22:48 schrieb Barrie Treloar:
On 30 October 2014 07:33, Michael Osipov micha...@apache.org wrote:
[del]
I did a code analysis now.
[del]
Is that a manual inspection - or are you using tooling?
Purely manual
Hi,
The vote has passed with the following result:
+1 (binding): Karl Heinz Marbaise, Hervé Boutemy, Kristian Rosenvold
+1 (non-binding): Anders Hammar
I will promote the artifacts to the central repo.
PMCs please promote the source release ZIP file and add this release the
board report.
The Apache Maven team is pleased to announce the release of the Maven
Archiver, version 2.6.
This module generates browsable HTML pages from Java source code.
http://maven.apache.org/shared/maven-archiver/
You should specify the version in your project's dependency configuration:
dependency
Am 2014-10-31 um 09:17 schrieb Hervé BOUTEMY:
thank you for the feedback
looks like you found issues for MPIR:
1. enhancement, to list only direct modules, not modules of modules
MPIR-279.
-
To unsubscribe, e-mail:
Hi folks,
I have prepared a working branch for that issue but cannot fix a test to
pass. It signals a NPE whereas a normal execution works as expected.
Is anyone able to figure out the cause? Otherwise I am not able to
proceed with this issue.
Branch:
Am 2014-11-13 um 01:40 schrieb Hervé BOUTEMY:
Sorry, I tried but I'm stuck with maven-plugin-testing-harness too...
I have committed another changed where I have missed to assigned the
localRepository. Though it gives me now:
testReport(org.apache.maven.report.projectinfo.ModulesReportTest)
Am 2014-11-13 um 12:07 schrieb Stuart McCulloch:
On Thursday, 13 November 2014 at 09:43, Michael Osipov wrote:
Am 2014-11-13 um 01:40 schrieb Hervé BOUTEMY:
Sorry, I tried but I'm stuck with maven-plugin-testing-harness too...
I have committed another changed where I have missed to assigned
Am 2014-11-13 um 22:01 schrieb Mirko Friedenhagen:
Hello everybody.
I am really out of ideas here. MPMD-89 is a test to ensure that test
classes whose name *does not* end on Test are recognized as tests by
inspecting their inheritage. I do not think that this is a a major use
case. Succeeds
Hi folks,
I'd like to know if we have a general concensus on this:
I am investigating MPIR-242 and figured out the cause. The input stream
is obtained from the HTTP URL and no encoding is given, so ISO-8859-1 is
provided as default (yuck!). While I know that some reporting related
modules
within the file itself
The only option would be inspect the content type header and make
further assumptions.
Michael
2014-11-13 23:15 GMT+01:00 Michael Osipov micha...@apache.org:
Hi folks,
I'd like to know if we have a general concensus on this:
I am investigating MPIR-242 and figured out
vendredi 14 novembre 2014 10:37:22 Michael Osipov a écrit :
Am 2014-11-14 um 04:02 schrieb Kristian Rosenvold:
Isn't this handled by the content-type headers normally ?
No, for two reasons:
1. The currect code does not inspect the content type
2. The server does send text/html but not the used
1 - 100 of 2401 matches
Mail list logo
