update done
Regards,
Hervé
Le mardi 30 septembre 2014 07:39:00 James Nord a écrit :
Sorry don’t know what happened with my mailer there - hadn't finished
writing and wasn't ready for sending.
The re-direct works - but shouldn't it redirect to the plugin page rather
than the top level jxr
we have scm-publish plugin for that
http://maven.apache.org/plugins/maven-scm-publish-plugin/
Regards,
Hervé
Le samedi 27 septembre 2014 10:09:35 Kevin Burton a écrit :
I don't think github would work but would love to be wrong.
Their static page hosting is acceptable but it's tricky to
probably a bug in dependency:tree
dependency:list just displays info directly taken from Maven core: you can
trust it
dependency:tree does a lot of logic to track resolution, with different
implementations for Maven 2, 3.0.x and 3.1+: at the moment, I had a lot of
work to be sure that
The Apache Maven team is pleased to announce the release of the Apache Maven
Shared Component: Maven Reporting Implementation, version 2.3
This component provides abstract classes to manage report generation, which
can be run both:
- as part of a site generation, as a maven-reporting-api's
The Apache Maven team is pleased to announce the release of the Apache Maven
Checkstyle Plugin, version 2.13
This plugin generates a report regarding the code style used by the
developers.
http://maven.apache.org/plugins/maven-checkstyle-plugin/
You should specify the version in your
yes, you should remove this explicit module
FYI, you can't use Doxia Markdown 1.5 with m-site-p that uses Doxia 1.6
natively: there was a little refactoring in Doxia 1.6 that is backward
compatible (you can use new parsers with old Doxia core) but not forward
compatible (you cannot use old
to have
the 'forked-duplication' problem.
All of our reports are being generated post-build by Jenkins, so everything
is working.
Thanks,
Mike
On Fri, Aug 22, 2014 at 8:25 AM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
- use Maven 3.2.2 at least: MNG-5630 will really help you
- use Maven 3.2.2 at least: MNG-5630 will really help you understand
- if not possible, use m-site-p 3.4: MSHARED-333 does something quite
equivalent and doesn't require a specific Maven version
and you can read MJAVADOC-171, where I managed to analyze the problem (quite
recently...) and
to artifactId,
could be added: don't hesitate to open a Jira issue and work on a patch
Regards,
Hervé
在 2014-08-18 19:25, Hervé BOUTEMY 写道:
ah ok
so you don't need a custom plugin to add artifactId: just put content in a
directory named __artifactId__
see
http://stackoverflow.com
Le mardi 19 août 2014 15:28:40 Robert Munteanu a écrit :
On Sun, Aug 17, 2014 at 8:47 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
, at least for the
eclipse+java+maven environment we're using.
but you're right, I didn't find a good one as Eclipse plugin either
and even
this is not reporting but reportPlugins
but in fact, you should not use this but use standard pom's reporting section
instead of m-site-p configuration: see
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Configuration_formats
Regards,
Hervé
Le mardi 19 août 2014 14:42:37 SEAN
includes
include**/*.java/include
/includes
/fileSet
在 2014-08-18 0:10, Hervé BOUTEMY 写道:
use packaged=true [1]
Regards,
Hervé
[1]
http://maven.apache.org/archetype/archetype-models/archetype-descriptor/a
rchetype-descriptor.html
Le mardi 12
deal with the artifactId in the
path,am i right?
i wrote a plugin to adjust file path myself
在 2014-08-18 15:54, Hervé BOUTEMY 写道:
ok, need to investigate
can you create a Jira issue and attach an example project?
Regards,
Hervé
Le lundi 18 août 2014 10:01:16 TOM a écrit
Le mercredi 13 août 2014 23:22:52 Nick Burch a écrit :
Hi All
For Apache Tika, we currently use the Maven Site plugin, along with the
APT format for our site content. We are looking to automatically pull in
snippets of code from svn into the published site, much as the ASF CMS
supports
use packaged=true [1]
Regards,
Hervé
[1]
http://maven.apache.org/archetype/archetype-models/archetype-descriptor/archetype-descriptor.html
Le mardi 12 août 2014 16:58:53 TOM a écrit :
I use mvn archetype:create-from-project to generate a archetype project.
and use it to generate a project
notice this is referenced as DOXIA-373 [1] and used in DOXIATOOLS-15 [2]
notice that you should:
- avoid ${basedir} and prefer ${project.basedir}
- not need the property in pom
Regards,
Hervé
[1] http://jira.codehaus.org/browse/DOXIA-373
[2] http://jira.codehaus.org/browse/DOXIATOOLS-15
Le
Le samedi 16 août 2014 15:08:53 Pablo León a écrit :
I've been messing around with markdown for a while, and I feel that APT
tools are more mature
if you know of other tools, please share: AFAIK, Doxia Eclipse Editor was
written because we didn't find any tooling (ne it in Eclipse or not)
Le jeudi 24 juillet 2014 12:05:37 Barrie Treloar a écrit :
On 24 July 2014 01:08, Vincent Zurczak vincent.zurc...@linagora.com wrote:
Hi,
I am not sure this is the right mailing-list.
Maybe I should have posted to the dev list. Anyway...
I have started working on new Maven plug-in
The Apache Maven team is pleased to announce the release of the Apache Maven
Site Plugin, version 3.4
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.
The Apache Maven team is pleased to announce the release of the Apache Doxia
base and Doxia Site Tools 1.6, version 1.6
Doxia is a content generation framework that provides powerful techniques for
generating static and dynamic content, supporting a variety of markup
languages.
Doxia Site
Le vendredi 27 juin 2014 07:25:08 Jason van Zyl a écrit :
I've never seen those mirrors before. The Apache Maven PMC is a aware of and
collaborate with Sonatype on the canonical Maven Central and collectively
we would assert the content is valid. Anything else and you're on your own.
I
Le vendredi 27 juin 2014 17:36:17 Jason van Zyl a écrit :
On Jun 27, 2014, at 4:11 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
Le vendredi 27 juin 2014 07:25:08 Jason van Zyl a écrit :
I've never seen those mirrors before. The Apache Maven PMC is a aware of
and collaborate with Sonatype
naming welcome
Regards,
Hervé
Le samedi 14 juin 2014 21:19:53 Hervé BOUTEMY a écrit :
yes, seems a good idea:
project name=.. inherit=false
http://maven.apache.org/doxia/doxia-sitetools/doxia-decoration-model/decorat
ion.html
tell me if you need help
Regards,
Hervé
Le samedi 14
Hello,
Yes, it's expected behaviour: forking happens when preparing the plugin,
before running report generation. Skip happens at the beginning of report
generation, just to not do it.
Notice the situation will get better with m-site-p 3.4, with
http://jira.codehaus.org/browse/MSITE-454 fixed
issues?
https://xircles.codehaus.org/signup
Regards,
Hervé
On 16 June 2014 13:09, Hervé BOUTEMY herve.bout...@free.fr wrote:
Hello,
Yes, it's expected behaviour: forking happens when preparing the plugin,
before running report generation. Skip happens at the beginning of report
how to express, I don't
want to inherit any breadcrumbs at all all.
On Fri, Jun 13, 2014 at 2:04 AM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
true that there isn't much doc on this
any idea on how/where to document this site.xml inheritence is welcome
Regards,
Hervé
Le
that turns off all
inheritance? The case I'm dealing with is a project that wants to
inherit build stuff from a parent but not site stuff. I'll tackle this
if you think it's reasonable.
On Sat, Jun 14, 2014 at 12:58 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
you can't inherit nothing with what
true that there isn't much doc on this
any idea on how/where to document this site.xml inheritence is welcome
Regards,
Hervé
Le jeudi 12 juin 2014 09:14:06 Andreas Sewe a écrit :
Hi,
that wasn't possible during my time of activity, not sure if anything
changed since:
The Apache Maven team is pleased to announce the release of the Apache Maven
SCM Publish Plugin, version 1.1
This plugin is a utility plugin to allow publishing Maven website to any
supported SCM. The primary goal was to have an utility plugin to allow Apache
projects to publish Maven websites
AFAIK, the m-site-p itself doesn't have any problem with jdk 8, since it
doesn't care about jdk
but from the little trace you give, there seem to be a reporting plugin that
is sensitive to jdk 8: yes, some plugins have problems, we track them here [1]
just look at your error traces and you'll
Hi Simo,
The maven-shanges-plugin does such a thing [1]
Now, let's talk about about the beers...
Regards,
Hervé
[1]
http://maven.apache.org/plugins/maven-changes-plugin/xref/org/apache/maven/plugin/changes/ChangesMojo.html#L461
Le mardi 13 mai 2014 00:29:04 Simone Tripodi a écrit :
Hi all
The Apache Maven team is pleased to announce the release of the Apache Maven
Plugin Tools, version 3.3
The Maven Plugin Tools contains the necessary tools to be able to produce
Maven Plugins in scripting languages and to generate rebarbative content like
descriptor, help and documentation.
already reported and fixed
http://jira.codehaus.org/browse/MPLUGIN-260
Regards,
Hervé
Le samedi 26 avril 2014 11:43:34 james northrup a écrit :
i have created a maven plugin from the plugin archetype.
i have a mojo which apparently does not matter to repeating this process,
any mojo will
we'll try to not be overly choosy
but both as Maven developper and as Maven user, I prefer to have separate
focused issues with focused bug descriptions, then separate patches
thanks for your help
Regards,
Hervé
Le vendredi 18 avril 2014 20:55:38 Laird Nelson a écrit :
On Fri, Apr 18, 2014
the difference still exists, and will never be fixed: that's the reasoning
behind deprecating DependencyTreeBuilder
I you need additional info about version conflicts, you should use Aether API +
Maven Aether Provider for Maven 3, which will give you everything
But at this precise level, you
I wish we could just do a post-release step to strip out debugging
information and compress Javascript / CSS . . .
post-release?
I suppose you mean post-package
see the complete phase list[1]
there are a lot of phases after complie = the place where code with debug
symbols are generated, so a
and
Maven31DependencyGraphBuilder?
William
On Thu, Mar 20, 2014 at 5:36 PM, Hervé BOUTEMY herve.bout...@free.frwrote:
I don't really know: that's a precise feature that I didn't sudy
dependency-tree is used in Maven plugins in contexts where components are
already installed: so there is not much
I was surprised too, but lilyevsky is right: par packaging is defined in Maven
default lifecycles [1] and it points to a non-existent
org.apache.maven.plugins:maven-par-plugin plugin
it was added in r332151 [2], for MNG-699 [3] in Maven 2.0.1, with a link to
MOJO-98 [4] for corresponding
maven-dependency-tree offers a really simple API: that's its objective.
The drawback is that it is not very flexible
The value is that it hides Maven 2, Maven 3.0.x and Maven 3.1.x+
implementations, which are completely different (initial Maven 2 is made of
listeners, Maven 3 uses Aether and
saying that it doesn't
support resolution of projects in the current reactor?
William
On Thu, Mar 20, 2014 at 5:16 PM, Hervé BOUTEMY herve.bout...@free.frwrote:
maven-dependency-tree offers a really simple API: that's its objective.
The drawback is that it is not very flexible
befaore deploying, you'll have to package, which usually attaches the artifact
for later automatic deployment by deploy plugin
see http://maven.apache.org/archetype/maven-archetype-plugin/
and the maven-archetype packaging automating it
http://maven.apache.org/archetype/archetype-packaging/
but
looks like a bug in maven-project-info-reports-plugin, which is the plugin
launched by maven-site-plugin to generate every Project information reports
Notice: m-site-p launches plugins for each report, then a failure when
generating a site is not always a m-site-p bug. But every bug in every
I'll make it short: please don't use reportPlugins in m-site-p configuration
see
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Configuration_formats
use classic configuration and everything will work fine
Regards,
Hervé
Le jeudi 13 février 2014 15:34:03 Alex Potsides a écrit
:
Brevity appreciated. You sound like someone who has answered that question
before.
Thanks,
Alex
On Thu, Feb 13, 2014 at 5:50 PM, Hervé BOUTEMY herve.bout...@free.frwrote:
I'll make it short: please don't use reportPlugins in m-site-p
configuration
see
http://maven.apache.org/plugins
The Apache Maven team is pleased to announce the release of the Apache Maven
SCM Publish Plugin, version 1.0
The maven-scm-publish-plugin is a utility plugin to allow publishing Maven
website to any supported SCM. The primary goal was to have an utility plugin
to allow Apache projects to
ok
defining profiles to have 2 site runs without same reporting plugins is ok: the
2 site runs share the same site.xml
what would be an issue would be to require 2 different site.xml files. But from
your description, you don't need such thing, no?
Regards,
Hervé
Le lundi 27 janvier 2014
I don't really understand what you want to do
see http://svn.apache.org/viewvc/maven/pom/trunk/maven/ for something quite
similar
In our case, the change to use src/site-docs instead of src/site is done in a
separate site-pom.xml instead of a profile in pom.xml, but it doesn't change
the
since the value is readonly, it doesn't go to the user-documentation because
user can't do anything: it's pure internal code
for yourself, you can change readonly to false and see user documentation
generated
Regards,
Hervé
Le dimanche 15 décembre 2013 21:15:32 Martin Gainty a écrit :
not exactly: the question is not about parent and childs, but about
pluginManagement injection into build plugins, which works exactly like
dependencyManagement injection into dependencies
if you define a precise version in the build plugins (or in a dependency),
dependencyManagement does not
why site:stage-deploy and not site:stage?
I suppose we made a mistake in this doc
Regards,
Hervé
Le samedi 16 novembre 2013 14:51:36 Benson Margulies a écrit :
I can't get the github example to work with a multi-module site.
I follow the instructions
I suppose you're using Maven 3.1.x
you should read
https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound then
upgrade plugins versions accordingly
or use Maven 3.0.x
Regards,
Hervé
Le lundi 11 novembre 2013 09:38:40 Collins Solutions a écrit :
I am trying to use the maven
Le vendredi 2 août 2013 10:08:42 Curtis Rueden a écrit :
True, and it is good to warn about this. However, ultimately I think Git is
a better choice (than SVN) because it often makes code review much easier.
I didn't use gerrit nor have seen anybody using it. But I hear about it more
and more
On Fri, Aug 2, 2013 at 10:47 AM, Hervé BOUTEMY herve.bout...@free.frwrote:
Le vendredi 2 août 2013 10:08:42 Curtis Rueden a écrit :
True, and it is good to warn about this. However, ultimately I think Git
is
a better choice (than SVN) because it often makes code review much
we didn't write specific documentation, neither on how to detect if your plugin
will break nor how to fix it: we don't expect much problems
if you need help, just ask: and if sufficient people need help, I'll try to sum
up the different cases we found
Regards,
Hervé
Le dimanche 14 juillet
I think there are some little inconsistencies in vocabulary, causing wrong
analysis
there are 3 lifecycles: default, clean and site [1]
and packaging selects default plugin bindings for default lifecycle [2]
For the moment, I didn't dig sufficiently into everything to have every answers
and
default plugin version can effectively be injected
but that's *default* plugin versions
since actual lifecycle definitions are done in Maven core, you can't count on
it to upgrade version in your projects
in your case, where you want to define a new lifecycle, perhaps it will be
possible to
the approach i used in a company was in 2 steps:
1. continue to build with Ant, but with Maven Ant Tasks for dependency
management
2. use Maven to try to build, in parallel with Ant, to check if you get the
same result. A first result here was to get a reporting site working, even if
the
yes, I worked recently on this exact issue: site *staging* on complex cases
like yours, which is not as usual as you expect
It took me a good number of hours with the issue reporter to understand what
he was doing, what he was expecting that wasn't trivial, and I found a
solution with this
http://mojo.codehaus.org/animal-sniffer-maven-plugin/
Le vendredi 24 mai 2013 13:29:03 Russell Gold a écrit :
By default, as I understand it, Maven 3 compiles with the source and target
options set to 1.5. This guarantees that later language features (such as
diamond notation) will result in
notice that there is another case to take care: if you use dependencies
compiled in Java 6 (like guava, for example)
the solution for this additional case is
http://mojo.codehaus.org/extra-enforcer-rules/enforceBytecodeVersion.html
Regards,
Hervé
Le vendredi 24 mai 2013 19:44:10 Hervé BOUTEMY
can you give us the result of mvn -version?
Regards,
Hervé
Le vendredi 17 mai 2013 11:49:07 coolguy a écrit :
I've a project that uses maven 3. I get the following error when I run mvn
dependency:tree command. Could someone advise why would I get this error?
[ERROR] Failed to execute
The Apache Maven team is pleased to announce the release of the Maven
Dependency Plugin, version 2.8
The dependency plugin provides the capability to manipulate artifacts. It can
copy and/or unpack artifacts from local or remote repositories to a specified
location.
The Apache Maven team is pleased to announce the release of the Maven *Project
Info Reports Plugin, version 2.7*
The Maven Project Info Reports plugin is used to generate reports information
about the project.
http://maven.apache.org/plugins/maven-project-info-reports-plugin/
You should
The Apache Maven team is pleased to announce the release of the Maven Site
Plugin, version 3.3
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-plugin/
looking at https://jira.codehaus.org/browse/MCHECKSTYLE-144
it seems fixed in 2.10, so 2.9.1 has the bug
Regards,
Hervé
Le jeudi 18 avril 2013 10:02:22 Itai Frenkel a écrit :
Hello,
It seems like I've encountered Checkstyle doesn't run on projects
containing only test classes bug in
if anybody submits patches, I can review and commit
Regards,
Hervé
Le lundi 15 avril 2013 06:03:19 davide.cavestro a écrit :
Hi all,
I've sketched a rough plugin
https://github.com/davidecavestro/gradle-jxr-plugin to spread JXR even
to gradle users. It just works, but it is limited by
yes, see Selecting Reports from a Plugin: Configuring Report Sets in [1]
notice you're using the new configuration format (ie reportPlugins inside
maven-site-plugin), which is not recommended at the moment [2]
Regards,
Hervé
[1]
1. warning if you don't define plugin version
you can believe Maven 3 doc, version is taken from pluginManagement: coded
here [1]
But I must confess I never tried with CLI, since we use to continue defining
plugin version directly to keep Maven 2.x compatibility
I just tried and confirm this
a reference list does not exist per-se, because the structure is extensible:
it's not really properties but more pseudo-properties with multiple sources
one reference source of information is the structure documentation:
http://maven.apache.org/ref/3-LATEST/maven-model-builder/
Regards,
Hervé
I suppose you're hitting https://jira.codehaus.org/browse/DOXIA-480
It is fixed in trunk, but we didn't release Doxia 1.4 yet
regards,
Hervé
Le samedi 16 février 2013 14:21:27 Laird Nelson a écrit :
Hello; how do I render an em dash using the Doxia Markdown module?
The following source
I wrote some documentation about properties available during Velocity
processing in Doxia [1]
project (type MavenProject) should be available, which has getProperties()
method: this should be what you are looking for
this documentation can probably be enhanced: any feedback appreciated
the Maven core reference doc is http://maven.apache.org/ref/3.1-
SNAPSHOT/maven-
artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html
Le jeudi 20 décembre 2012 14:02:02 org.apache.maven.u...@io7m.com a écrit :
Hi.
I can't find any documentation on the Maven site about
, Dec 5, 2012 at 11:23 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
please read the last two lines
F:\work\7832e3bc4d2f257b\dashboard-core\target\classes (Access is
denied)
Le mercredi 5 décembre 2012 15:00:24 David Hoffer a écrit :
I have a multi-module maven build
manor?
-Dave
On Thu, Dec 6, 2012 at 11:06 AM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
if you run with mvn -X and give us the full stack trace, perhaps we can
see
what's going wrong
Le jeudi 6 décembre 2012 06:34:52 David Hoffer a écrit :
Note that the copy-dependencies goal
please read the last two lines
F:\work\7832e3bc4d2f257b\dashboard-core\target\classes (Access is
denied)
Le mercredi 5 décembre 2012 15:00:24 David Hoffer a écrit :
I have a multi-module maven build and can't get the site build to
work. It's currently failing with this error. The module its
magic has been done:
see http://maven.apache.org/plugin-tools/apidocs/src-
html/org/apache/maven/tools/plugin/util/PluginUtils.html#line.40
Le mercredi 28 novembre 2012 18:54:11 Jason van Zyl a écrit :
Internally the way @component works is to take the role of component
supplied or figure it
:00:03 Jason van Zyl a écrit :
That's not right, and confusing. It's not a component.
jvz
On 2012-11-28, at 6:57 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
magic has been done:
see http://maven.apache.org/plugin-tools/apidocs/src-
html/org/apache/maven/tools/plugin/util
keep that method.
jvz
On 2012-11-28, at 6:57 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
magic has been done:
see http://maven.apache.org/plugin-tools/apidocs/src-
html/org/apache/maven/tools/plugin/util/PluginUtils.html#line.40
Le mercredi 28 novembre 2012 18:54:11 Jason van Zyl
incorrect? A component
has a specific definition of being an instance created by the container.
On Nov 28, 2012, at 7:23 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
no, we choose to do that for ease of use for the average plugin developer
we had a long discussion on how to ease plugin
uyou can have a look at http://maven.apache.org/ref/3.1-SNAPSHOT/maven-
core/artifact-handlers.html for a reference of default types and classifiers
Regards,
Hervé
Le jeudi 25 octobre 2012 20:09:58 John Kramer a écrit :
Hey guys,
I have a question regarding the maven dependencies section.
schema on http://maven.apache.org/archetype/maven-archetype-plugin/ explains
the full cycle
what are you trying to create: an archetype project by hand (instead of from a
sample project)? or a project from an existing archetype?
Regards,
Hervé
Le mardi 2 octobre 2012 08:34:55 Nisha a écrit :
yes, please share experience about ranges: when it is useful, how, and so on
we really need to write this Guide to using version ranges
https://jira.codehaus.org/browse/MNG-1368
so we stop telling ranges are a bad practice but tell what they are useful
for
Regards,
Hervé
Le samedi 29
Le lundi 1 octobre 2012 02:31:44 Jesse Long a écrit :
I have created a ticket - http://jira.codehaus.org/browse/MNG-5353
thank you
I changed it from Bug to Wish: no, nobody ever asked for such a behaviour,
it's really a new idea AFAIK
which BTW seems a good enhancement IMHO
now we need to check
even think about regexp based versioning...
sure, there is something to create here, but IMHO not into version ranges:
into conflict resolution specification and switch (with CLI or IDE)
LieGrue,
strub
- Original Message -
From: Hervé BOUTEMY herve.bout...@free.fr
you ideally want every version. But that matrixes out to an
impossible combinatorial.
On Saturday, 29 September 2012, Hervé BOUTEMY wrote:
Le samedi 29 septembre 2012 09:46:28 Mark Struberg a écrit :
I thought about mathematical ranges as well, and the outcome for me
personally
Comparator
class MavenVersion implements
ComparableMavenVersion
{
public int compareTo(MavenVersion o)
{
// your implementation
}
}
Then we can all do whatever we need.
On 27/09/2012 21:40, Hervé BOUTEMY wrote:
I
yes, https://jira.codehaus.org/browse/MNG-3092 is still here
I'm not comfortable with the idea of excluding SNAPSHOT from ranges: if we do
so, it's not a *range* any more but a range + a filter
(1.7.1-SNAPSHOT is in [1.7,1.8] range,in plain english)
and actual discussion helps me dig into other
Le vendredi 28 septembre 2012 09:52:50 Jesse Long a écrit :
My point is really about exclusive upper bounds.
ok, now I'm starting to see the precise idea and believe it can avoid breaking
subtle logic
[1.7,1.8) could exclude anything starting with 1.8: betas, alphas, alphas-
alphas, snapshots
I understand that many people get caught
But what do you expect from [1.7,1.8]?
And [1.7,1.8-beta)?
The actual semantic is pure mathematical range, including or excluding an
extreme
since 1.8-alpha1.8-beta-1.8-rc1.8-SNAPSHOT1.8, it's pure math
IMHO, anything that doesn't conform mathematical
Le jeudi 27 septembre 2012 15:41:25 Jesse Long a écrit :
I have not logged a Jira issue, as I cannot log into CodeHaus Jira. The
signup link on this page displays an error:
http://maven.apache.org/users/getting-help.html
thanks for the report
I updated the link, should be visible in the page
The Maven team is pleased to announce the release of the Maven Project Info
Reports Plugin, version 2.5.1
The Maven Project Info Reports Plugin is a plugin that generates standard
reports for the specified project.
http://maven.apache.org/plugins/maven-project-info-reports-plugin/
You should
I was trying to fix as much issues as posible before releasing
It seems we're now at the maximum feasible for the moment (MPIR-251 will be
postponed)
I'll start the release tonight
Regards
Hervé
Le samedi 25 août 2012 18:45:15 Olivier Lamy a écrit :
2012/8/25 Dennis Lundberg
the most interesting code is probably in maven-reporting-executor
http://maven.apache.org/shared/maven-reporting-exec/, which is used by m-site-
p
Regards,
Hervé
Le jeudi 9 août 2012 12:29:44 Olivier Lamy a écrit :
Hi
Have a look at how we solve that in the site plugin sources
That will
The Maven team is pleased to announce the release of the Maven Project Info
Reports Plugin, version 2.5
The Maven Project Info Reports Plugin is a plugin that generates standard
reports for the specified project.
http://maven.apache.org/plugins/maven-project-info-reports-plugin
You should
The Maven team is pleased to announce the release of the Maven Dependency
Plugin, version 2.5
The dependency plugin provides the capability to manipulate artifacts. It can
copy and/or unpack artifacts from local or remote repositories to a specified
location.
the pluginManagement section is used for reports only when run with Maven 3,
but not supported by Maven 2
Notice this has nothing to do with the new configuration format: this new
format doesn't add any feature, it's only an implementation detail made
visible to users, and it's even more
choosing format is a question of taste: some prefer apt, some prefer xdoc,
you'll have to make your own choice
for the editor, there is a good Doxia Eclipse plugin [1]
It help writing wiki syntax, or preview, but there is nothing tied to code
references.
Regards,
Hervé
[1]
Le lundi 16 juillet 2012 10:13:06 Jesse Farinacci a écrit :
Greetings,
On Mon, Jul 16, 2012 at 9:13 AM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
for the editor, there is a good Doxia Eclipse plugin [1]
[1] http://maven.apache.org/doxia/doxia-ide/eclipse/usage.html
Except
The Maven team is pleased to announce the release of the Maven Plugin
Plugin, version 3.1.
This version fixes mostly the support of Java annotations for Maven plugins (
http://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-
annotations.html
)
The Maven Plugin Plugin is used to
I tried to build the project but got compilation failures
[INFO] Compilation failure
/tmp/opennms-maven-plugins/features-maven-
plugin/src/main/java/org/opennms/maven/plugins/karaf/FeatureBuilder.java:
[79,9] error: no suitable method found for addBundle(String,int,null,null)
Regards,
Hervé
Le
301 - 400 of 553 matches
Mail list logo
