the documentation is here http://maven.apache.org/plugin-tools/maven-plugin-
plugin/examples/using-annotations.html
and a lot of plugins now use these annotations:
http://jira.codehaus.org/browse/MPLUGIN-203
Regards,
Hervé
Le vendredi 28 septembre 2012 11:43:30 Sascha Vogt a écrit :
Am
thanks Denis for the analysis
I think the culprit is http://jira.codehaus.org/browse/MPLUGIN-227
and javadoc plugin is just intolerant at this case where there is some code in
unnamed package: not a regression, just a case that wasn't seen in real
world before the bug in plugin tools
I just
no problem, svn can revert such things easily too (even if I had to look at
the doc since I don't do such things everyday)
I should have tested before commit and found this stupid typo I did
thanks
Hervé
Le vendredi 28 septembre 2012 21:15:54 Kristian Rosenvold a écrit :
Hervé;
In an
+1
Regards,
Hervé
Le vendredi 28 septembre 2012 08:08:20 Dennis Lundberg a écrit :
Hi,
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150styleName=H
tmlversion=18298
There are still a couple of issues left in JIRA:
Given this milestone will be available in central repo [1], I don't see any
problem: I created MNG-5354 to track this.
Of course, as requested by our dependency policy [2], we need a formal vote
approved by PMC majority: this intent declaration is useful before calling for
a formal vote just to
Le lundi 1 octobre 2012 19:34:27 Jason van Zyl a écrit :
On Oct 1, 2012, at 4:38 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
Given this milestone will be available in central repo [1], I don't see
any
problem: I created MNG-5354 to track this.
Cool, thanks.
Of course, as requested
Aether 0.9.0.M1 is now in central [1]
and Benjamin did the upgrade on his own Maven 3 branch [2]
Question: do we need a formal vote for the upgrade of this dependency?
Any objection to do the upgrade without vote, given it's just a new home for a
compoennt we already use?
Regards,
Hervé
[1]
+1
Regards,
Hervé
Le mardi 9 octobre 2012 13:02:51 Olivier Lamy a écrit :
Hi,
I'd like to release Maven Sources Plugin 2.2.1.
We fix 1 blocking issue which prevent some users to upgrade:
http://jira.codehaus.org/browse/MSOURCES-62
Staging repository:
+1
Regards,
Hervé
Le jeudi 11 octobre 2012 23:47:09 Dennis Lundberg a écrit :
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleName=H
tmlversion=18456
There are still a couple of issues left in JIRA:
ok, I can reproduce the issue
this happens during DependencyManagement report
I created MPIR-255 and I'm working on it
Regards,
Hervé
Le samedi 13 octobre 2012 16:36:27 Kristian Rosenvold a écrit :
Hervé/Dennis;
Dennis sent me a mail some time ago that there was a problem with the
if maven-dependency-tree[1]'s DependencyGraphBuilder can be used, it gives
you both Maven 2 3 compatibility without hard code
Regards,
Hervé
[1] http://maven.apache.org/shared/maven-dependency-tree/
Le lundi 22 octobre 2012 19:09:48 Arnaud Héritier a écrit :
As discussed on IRC for now I
Le lundi 22 octobre 2012 17:38:10 Paul Gier a écrit :
I did some more testing, and the tests only seem to fail using Maven
3.0.4 for me. I was testing locally with Maven 3.0.3 previously. For
Robert, the ITs passed with Maven 2.2.1, but failed with 3.0.x. If you
want to release this week
Add missing 'read only' flag to internal injection parameter
no it's not missing at all, it's a configuration needed when user wants to use
another dependency analyzer thatn the default one
Notice this is a feature and Jira issue I discovered when using blame on code,
and I don't know any
and it
died with the same wierd classworlds error that the ITs die with. I'm
willing to help fix this up, but I;m not following the logic of a
release. Feel free to explain why I'm confused.
I'll do more diagnosis later today.
Arnaud
On Wed, Oct 24, 2012 at 1:02 AM, Hervé BOUTEMY
:(
if my explanations are right, we should open a MNG issue and create either an
IT or a UT: I don't have time to work on it for the moment, but if nobody
beats me, I'll keep this on my TODO list
Arnaud
On Wed, Oct 24, 2012 at 7:25 PM, Hervé BOUTEMY herve.bout...@free.frwrote:
I had a look
/**
- * Class intended to be used by clients who wish to invoke a forked Maven
process from their applications - *
* @author jdcasey
- * @plexus.component role=org.apache.maven.shared.invoker.Invoker
role-hint=default */
+@Component( role = Invoker.class, hint = default,
think it's better for the moment then plexus descriptor extractor
should be fixed to get description from javadoc
Regards,
Hervé
-Robert
Op Thu, 25 Oct 2012 00:01:24 +0200 schreef Hervé BOUTEMY
herve.bout...@free.fr:
/**
- * Class intended to be used by clients who wish to invoke
+1
Regards,
Hervé
Le mercredi 24 octobre 2012 23:22:44 Dennis Lundberg a écrit :
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11391styleName=H
tmlversion=18793
There are still a couple of issues left in JIRA:
+1
Regards,
Hervé
Le jeudi 25 octobre 2012 11:58:11 Kristian Rosenvold a écrit :
Hi,
Important bugfix, avatar/image support !
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18761styleName=Htm
lprojectId=11142
There are still a couple of issues left in
+1
Regards,
Hervé
Le jeudi 25 octobre 2012 22:04:06 Robert Scholte a écrit :
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761version=164
60
There are still a couple of issues left in JIRA:
Warning: Jackrabbit 2.5 requires Java 6 (just discovered the problem looking
at Jenkins build failure)
Can we really upgrade wagon? then Maven core?
We at least need a strong warning to users requiring webdav support
Regards,
Hervé
Le jeudi 11 octobre 2012 21:03:03 ol...@apache.org a écrit :
maven-shared-utils in dependencyManagement and m-plugin-p update of Maven
parent pom are all for Maven poms, ie later
the first step is Apache parent POM, which doesn't contain anything Maven
specific, only common plugins [1]: I just updated as much plugins as I found
I don't have anything more
+1
(and thanks for the improvements on release instructions)
Regards,
Hervé
Le jeudi 1 novembre 2012 23:14:45 Dennis Lundberg a écrit :
Hi,
Changes since the last release:
http://svn.apache.org/viewvc/maven/pom/tags/apache-12/pom.xml?r1=HEADr2=136
9674diff_format=h
Staging repo:
+1
Regards,
Hervé
Le jeudi 1 novembre 2012 20:35:50 Mark Hobson a écrit :
Hi,
We solved 4
issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527sty
leName=Htmlversion=18930
There are still plenty of issues left in
+1
Regards,
Hervé
Le jeudi 1 novembre 2012 22:04:22 Mark Hobson a écrit :
Hi,
Note that this release is dependent upon the maven-scm-1.8.1 vote
currently taking place.
We solved 2
issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12730sty
leName=Htmlversion=18939
I'm done with MPLUGIN-227, which was my favorite :)
Regards,
Hervé
Le lundi 29 octobre 2012 18:21:53 Kristian Rosenvold a écrit :
I'm fixing MPLUGIN-229. If anyone else wants to hack away at
something, now is the time to start ;)
I'll start the release in a day or so unless someone wants
+1
there is sufficient change to deserve a 3.2
I'm switching Jira and svn
Regards,
Hervé
Le dimanche 4 novembre 2012 17:51:42 Kristian Rosenvold a écrit :
The dependency change alone should be sufficient for 3.2
Kristian
Den 4. nov. 2012 kl. 16:57 skrev Dennis Lundberg
yes, I understand the problem, but didn't find for the moment a way to
implement something.
I'm interested in working with anybody trying to make something
Here are some pointers:
- plugin documentation generation is done by PluginXdocGenerator in plugin-
tools [1]
- Modello model documentation
code generator from Modello is JavaModelloGenerator [1]
Regards,
Hervé
[1] http://modello.codehaus.org/modello-plugins/modello-plugin-
java/xref/org/codehaus/modello/plugin/java/JavaModelloGenerator.html
On Sun, Nov 4, 2012 at 2:50 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
yes, I
+1
I closed the issue, since it was fixed in maven-site-plugin (not a bug of the
reports that printed this message)
Regards,
Hervé
Le mardi 6 novembre 2012 07:12:15 Lukas Theussl a écrit :
+1 !!! (non-binding)
There is still one open issue [1] scheduled for this release. I am not
using
IMHO, it's not because of plugin annotations but use of reportPlugins
parameter of site plugin which blocks reports from classical reporting
section: mpir, javadoc, jxr, nothing is generated, not only plugin report
I tried to replace this reportPlugins section with reports, but it fails with
I just committed an improvement to replace this NPE with nice explanation why
this should never happen if plugin version is used consistently in every build
phase
see http://svn.apache.org/viewvc?rev=1406480view=rev
this can help discover what happens on this project which should not
IMHO,
+1
tested on maven-clean-plugin
everything seems ok now in the site
thank you for finishing my initial updates on MPLUGIN-227: I knew it wasn't
perfect but didn't have sufficient time to do more and hoped this would at
least
help finding the right direction
Regards,
Hervé
Le mercredi 7
yes, the behaviour is known - probably not from many people, but I do know it
was a consequence of maven-dependency-tree-2.0 MSHARED-167
I wouldn't say intentional, but that's a consequence of using Aether in
Maven 3 instead of tracking internal Maven 2 dependency resolution events.
Maven
I fixed job configuration, it is now available
FYI, as README explains, building Eclipse Doxia Editor requires building
doxia-osgi/pom.xml then eclipse-plugins/pom.xml, but the second build had
disappeared from job configuration (don't know how/when)
I just added the sedond step back and the
IMHO, whatever we do, we need to be able to write plugins that work with Maven
2 and Maven 3.0.x and 3.1 and 3.2 and...: that's my key objective
Then I found a solution in maven-dependency-tree (or at least that's the
intent): create a thin layer that maps to the past internal 2.x and 3.0.x
Le samedi 10 novembre 2012 19:15:47 Karl Heinz Marbaise a écrit :
Hi Hervè,
many for the explanation...
yes, the behaviour is known - probably not from many people, but I do
know it
was a consequence of maven-dependency-tree-2.0 MSHARED-167
I wouldn't say intentional, but
+1
Regards,
Hervé
Le jeudi 8 novembre 2012 23:53:00 Robert Scholte a écrit :
Hi,
We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761version=189
27styleName=Html
There are still 2 issues left in JIRA:
if it's for Maven core, I just added Markdown support while I was upgrading
MPIR, in r1407910
Regards,
Hervé
Le samedi 10 novembre 2012 14:36:14 Jason van Zyl a écrit :
Hi,
When I first tried using Markdown with the site plugin a couple weeks ago
for the SLF4 document it didn't work.
yes, the question of which slf4j implementation we should use in Maven is a
different question from how to manage progress display during transfert.
And I like
My goal was to
introduce SLF4J in a minimal way, at least to start.
more than what I read previously, which gave me bad feeling
IMHO, this doesn't sound really risky feature, so I don't see any reason why
not to include it in the next version
Regards,
Hervé
Le dimanche 11 novembre 2012 13:19:01 Anders Hammar a écrit :
If I speed things up on MNG-5356, would anyone object to get that into
3.1.0 as well?
/Anders
Le samedi 10 novembre 2012 18:08:02 Jason van Zyl a écrit :
2. plugins or components: using Aether API would mean that it won't work
with Maven 2 or 3.0. With maven-dependency-tree layer as compatibility
layer, the problem disappears. But DependencyGraphBuilder API is rather
limited: any
Le dimanche 11 novembre 2012 18:18:58 Jason van Zyl a écrit :
On Nov 11, 2012, at 5:49 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
Le samedi 10 novembre 2012 18:08:02 Jason van Zyl a écrit :
2. plugins or components: using Aether API would mean that it won't work
with Maven 2 or 3.0
Le samedi 10 novembre 2012 14:52:38 Jason van Zyl a écrit :
Ok, I'll just keep using my Github pages for now until it's supported.
Thanks.
where do you want it, so we can work together on slf4j docs?
-
To unsubscribe, e-mail:
Le mardi 13 novembre 2012 10:09:51 Jason van Zyl a écrit :
But again really, I believe the decision is to determine whether all this
really necessary. I think the order of operations that folks think is
reasonable is:
1) Get the release out with SLF4J
2) Determine whether we need logging
no
core only needs to compare version
core never need to calculate next version
some plugines like release or versions need to try to guess which is the next
one: nothing that belong to core IMHO
Regards,
Hervé
Le mardi 13 novembre 2012 14:28:18 Manfred Moser a écrit :
True... separate, but
+1
Regards,
Hervé
Le jeudi 15 novembre 2012 00:11:45 Dennis Lundberg a écrit :
Hi,
We solved 29 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126styleName=H
tmlversion=18308
There are still a couple of issues left in JIRA:
Le jeudi 15 novembre 2012 08:30:11 Jason van Zyl a écrit :
On Nov 15, 2012, at 8:18 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Currently logger for all mojos is the DefaultPluginManager logger.
So it's a bit hard to have filtering per plugin (i.e. only compiler in
debug etc..)
So
+1 for the idea
other complementary ideas:
- groupId is not really useful, plugins's artifactId is in general sufficient
- I'd add goal name
- dot separator, since this is the classical separator in every java logging
implementations (due to the classical class name as logger pattern)
- add
+1
Regards,
Hervé
Le vendredi 16 novembre 2012 00:36:20 Olivier Lamy a écrit :
Hi,
I'd like to release Maven Compiler 3.0
We fixed 9 issues.
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18537styleName=Tex
tprojectId=11130Create=Create
Staging repository:
the SLF4J logger factory and use that with the underlying
component descriptor's implementation definition which is the class
name.
-Chris
On Fri, Nov 16, 2012 at 5:39 PM, Hervé BOUTEMY
herve.bout...@free.frwrote:
+1 for the idea
other complementary ideas:
- groupId is not really
-Chris
On Fri, Nov 16, 2012 at 5:39 PM, Hervé BOUTEMY
herve.bout...@free.frwrote:
+1 for the idea
other complementary ideas:
- groupId is not really useful, plugins's artifactId is in general
sufficient
- I'd add goal name
- dot separator, since this is the classical
Le samedi 17 novembre 2012 08:33:07 Jason van Zyl a écrit :
On Nov 17, 2012, at 8:01 AM, Hervé BOUTEMY herve.bout...@free.fr wrote:
Inject the SLF4J logger factory and use that with the underlying
component
descriptor's implementation definition which is the class name.
if we change
I just implemented MODELLO-256, which will permit to preserve whitespace in
Maven plugins configuration: see MNG-5380 [1].
The question is: should we change the overall behaviour (plugins can trim when
they need, and usually, there is no extra space in plugin configurations so
nothing will
Le dimanche 18 novembre 2012 09:10:33 Olivier Lamy a écrit :
2012/11/18 Hervé BOUTEMY herve.bout...@free.fr:
I just implemented MODELLO-256, which will permit to preserve whitespace
in
Maven plugins configuration: see MNG-5380 [1].
The question is: should we change the overall
, November 18, 2012 9:10 AM
Subject: Re: Preserve whitespace in Maven plugin configuration?
2012/11/18 Hervé BOUTEMY herve.bout...@free.fr:
I just implemented MODELLO-256, which will permit to preserve whitespace
in
Maven plugins configuration: see MNG-5380 [1].
The question
Le dimanche 18 novembre 2012 17:24:14 Benson Margulies a écrit :
Folks,
I myself feel like a bit of a looping site build myself on this
subject, and I apologize.
The build of Apache Accumulo is showing the 'classic' symptoms of
running more or less forever with 'site:site', due,
cobertura, another usual suspect
I really don't understand this aspect, and for the moment, I gave up...
Le dimanche 18 novembre 2012 17:50:02 Benson Margulies a écrit :
On Sun, Nov 18, 2012 at 5:45 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
Le dimanche 18 novembre 2012 17:24:14 Benson
+1
Regards,
Hervé
Le lundi 19 novembre 2012 23:09:06 Olivier Lamy a écrit :
Hi,
Last release is from feb 2007.
We fixed 7 issues: http://s.apache.org/RAR-PLUGIN-2.3
Staging repo: https://repository.apache.org/content/repositories/maven-048/
Source release:
MENFORCER-144 fixed
I'd like to MENFORCER-145 before the release, please wait a few more hours
Regards,
Hervé
Le mardi 20 novembre 2012 12:02:40 Jason van Zyl a écrit :
Sure, I can take a look as I'm doing releases this week.
Hervé, you mind if I push out MENFORCER-144 to the next version
Le mardi 20 novembre 2012 19:50:22 Benson Margulies a écrit :
On Tue, Nov 20, 2012 at 7:45 PM, Brett Porter br...@apache.org wrote:
On 21/11/2012, at 7:37 AM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
I think I found at least one cause of too many forked lifecycles within
+1
Regards,
Hervé
Le mardi 20 novembre 2012 20:15:29 Tamás Cservenák a écrit :
Hi,
we'd like to release Maven Indexer 5.1.0.
We fixed 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12112version=189
72
Staging repository:
+1
don't forget to deploy the site (see release instructions for more details),
please
Regards,
Hervé
Le mardi 20 novembre 2012 11:37:39 Jason van Zyl a écrit :
Hi,
There have been eight issues fixed in this version of Wagon. It's a
dependency for Maven 3.1.0 so I wanted to get it up for
2*+1
Regards,
Hervé
Le mardi 20 novembre 2012 23:28:41 Arnaud HERITIER a écrit :
Hi,
Sorry for the long delay since the first attempt. I have more free time now
to be back on this subject.
We solved 3 issues in Maven Dependency Analyzer :
Since this is a plexus component implemented in Maven core [1], I don't see
any problem with adding a new Method: if the method exists in interface, it
exists in implementation.
We would have a problem if it was an interface that is expected to be
implemented by external code
So I don't see
+1
Regards,
Hervé
Le vendredi 23 novembre 2012 19:04:07 Robert Scholte a écrit :
Hi,
We solved 14 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11441styleName=H
tmlversion=18730
There are no more open bugs, but still a couple of issues left in JIRA:
I had a second thought about aggregate reporting plugins (or more precisely
goal).
Since some time, we're applying a new pattern where there is a separate
reporting goal for aggregate (previously, aggregate was a parameter).
In the maven parent pom, we're explicitely setting a reportSet
Le mardi 27 novembre 2012 21:45:16 Benson Margulies a écrit :
On Tue, Nov 27, 2012 at 8:48 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
I had a second thought about aggregate reporting plugins (or more
precisely
goal).
Since some time, we're applying a new pattern where
+1
Regards
Hervé
Le mercredi 28 novembre 2012 18:26:13 Paul Gier a écrit :
Hi,
We solved 10 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530version=18
491
There are still a couple of issues left in JIRA:
I just created and fixed MNG-5395 and MNG-5396, which are logger names
enhancements from the actual values that will give value even with slf4j-
simple
These should be a starting point for more global discussion about our logging
conventions then fixed in our global codebase, since IMHO, these
+1
Regards,
Hervé
Le mercredi 28 novembre 2012 11:03:06 Olivier Lamy a écrit :
Hi,
I'd like to release the archetype for maven plugin.
The goal is to have an archetype which generate project using new mojo
annotations (and a sample to run maven-invoker-plugin)
We fixed 2 issues:
Le samedi 1 décembre 2012 18:52:51 Dennis Lundberg a écrit :
I would -1 any suggestion to start using the beta moniker again, at
least for the changes made this far.
I completely agree
would it be more a milestone, to show the stable but work in progress state?
3.1.0-m1?
Le samedi 1 décembre 2012 10:08:21 Jason van Zyl a écrit :
[1]:
http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Flogging%2Flog4j%2Flog4j2
just for side-by-side comparison:
https://github.com/qos-ch/logback/graphs/contributors
Le samedi 1 décembre 2012 12:10:43 Stuart McCulloch a écrit :
You might want to take a look at
http://logback.qos.ch/manual/layouts.html#coloring for additional
background
thank you Stuart, really useful
I made the same research for log4j2, to continue my personal comparison and
found
help while hacking configuration files, like
auto-completion.
Is there something available in log4j2 or logback for this?
Or will I have to learn the XML structure of each by trial-error?
Le dimanche 2 décembre 2012 00:30:48 Hervé BOUTEMY a écrit :
Le samedi 1 décembre 2012 12:10:43 Stuart
I created MNG-5397 Jira issue for Use SLF4J for logging, with a classical
comment to link to svn revision.
I just added a link to equivalent git commit, now we're using git.
One thing I used to do with svn in such a case is changing svn:log to add Jira
issue reference to the revision commit
reference, you need to add the
jira-reference to the commit up-front with the classical [MNG-5379]
prefix in the message.
Kristia
2012/12/2 Hervé BOUTEMY herve.bout...@free.fr:
I created MNG-5397 Jira issue for Use SLF4J for logging, with a
classical
comment to link to svn
I'm interested to help working on adding a metadata to enable slf4j visibility
from a plugin: by default, slf4j is not visible, plugins are expected to use
plugin-api's Log. But if the plugin wants to use core's slf4j, he would be
able to add an annotation in the goal requiring shared core
Le vendredi 7 décembre 2012 09:32:33 Jason van Zyl a écrit :
Hervé I will assume you're looking at this. Let me know if you need any
help.
yes, I'm working on it
from latest discussion, the ideal is:
1. compatibility:
for plugin descriptors without information, don't expose core's slf4j-api,
I just committed a starting point for MNG-5406: don't expose core's slf4j-api
by default, add a plugin-descriptor option to expose
this is a new field in plugin descriptor.
I still don't know how to effectively use it in
DefaultClassRealmManager.createPluginRealm() to avoid importing slf4j-api
Le dimanche 9 décembre 2012 20:50:33 Jason van Zyl a écrit :
I think it's time to stop patching SLF4J Simple. I have an inefficient fix
for the embedding problem, but we're likely to run into issues concurrency
with parallel builds and who knows what else. This will patch/change #5 and
many
trying to be concise and neutral
1. because slf4j-api is well known, it has lots of back-ends, that will
provide powerfull configuration techniques for filtering, display, recording
and
so on Maven output: precise use case still need to be described
2. the discussion is not much about the api
same for me
with one precision: IMHO, the few places where we'll have to write
implementation-specific code need to be placed in a separate class to ease
changing implementation
Regards,
Hervé
Le mardi 11 décembre 2012 16:19:12 Daniel Kulp a écrit :
My thoughts:
99.5% (or more) of the
, this could give an idea of what new API would be useful in slf4j-api in
future versions: I don't expect much methods
Regards,
Hervé
On Dec 11, 2012, at 7:39 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
same for me
with one precision: IMHO, the few places where we'll have to write
+1
Regards,
Hervé
Le jeudi 13 décembre 2012 23:48:24 Robert Scholte a écrit :
Hi,
We solved 24 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?styleName=HtmlprojectId=11
144version=17453
There are still a couple of issues left in JIRA:
wow, nice idea!
a little bit tricky, since the effective deploy is done ate end using the
reactor as if it was a post-execution aggegate
but definitely a nice idea
we need such an approach with scm-publish to be able to publish a multi-module
site as part of site-deploy phase
Regards,
Hervé
+1
a Jira issue to show which methods have been made public would be useful IMHO
Regards,
Hervé
Le jeudi 13 décembre 2012 22:39:50 Kristian Rosenvold a écrit :
Hi,
We solved 1 issue and made a few methods public. This release is
necessary for surefire 2.13.
yes, there is interpolation in poms: see the reference [1]
I suppose this is treated with more explanation in any Maven book
Regards,
Hervé
[1] http://maven.apache.org/ref/3.0.4/maven-model-builder/
Le dimanche 16 décembre 2012 15:26:45 jinwei zhu a écrit :
Hi, community,
In this url
/39e11cf2
Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/39e11cf2
Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/39e11cf2
Branch: refs/heads/master
Commit: 39e11cf2e51a41fc47001f0fe59da251dab87587
Parents: 73ffdaf
Author: Hervé Boutemy hbout...@apache.org
Authored: Sun
in a build.
Also, please do not start multiple mail threads about the same topic.
One
thread is enough.
/Anders
2012/12/16 Hervé BOUTEMY herve.bout...@free.fr javascript:;:
yes, there is interpolation in poms: see the reference [1]
I suppose this is treated
in command, maven will
cover setting.xml repository configuration.
Do you think so ?
2012/12/17 Hervé BOUTEMY herve.bout...@free.fr:
those 2 questions don't have a real meaning in Maven 2 3: install
doesn't
use maven.repo.local [1]
perhaps you're looking for settings configuration [2], ie
in your ideas, do you intend to rebuild the artifact at each promotion, or
make promotion of the already built artifact (then without rebuilding it),
only changing its status metatada?
Regards,
Hervé
Le mercredi 19 décembre 2012 15:37:18 Gábor Guta a écrit :
Can you give me feedback feedback
update the
metadata. e.g.: if the corresponding integration tests are fine, the
status of the artifact change to milestone.
Regards, Gabor.
On Thu, Dec 20, 2012 at 7:17 AM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
in your ideas, do you intend to rebuild the artifact at each promotion
+1
Regards,
Hervé
Le lundi 17 décembre 2012 16:33:25 Kristian Rosenvold a écrit :
Hi,
We solved 3 issues
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761version=174
32
There are 2 issues left in jira;
hope this helped to
clarify the role of module statuses.
Regards, Gabor
On Thu, Dec 20, 2012 at 8:35 AM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
ok, I see the workflow for single artifact promotion
Once this artifact is promoted, you want to update another project's
dependency
done
Le mardi 1 janvier 2013 20:25:40 Robert Scholte a écrit :
http://maven.apache.org/developers/website/deploy-maven-website.html#Modify_
Maven_Website_with_CMS_UI
tells you how you should adjust this.
Op Tue, 01 Jan 2013 19:47:13 +0100 schreef Benson Margulies
bimargul...@gmail.com:
Le samedi 22 décembre 2012 23:37:05 Olivier Lamy a écrit :
2012/12/22 Robert Scholte rfscho...@apache.org:
Hi,
I'm not really pleased with these scripts. The maven-release had cloned
these files, and now they're out of sync. We must think of a better way to
solve this.
I have just
Le lundi 24 décembre 2012 14:17:02 Brett Porter a écrit :
I had the same feeling pushing up Continuum's Maven site recently...
On 23/12/2012, at 9:36 AM, Olivier Lamy ol...@apache.org wrote:
2012/12/22 Kristian Rosenvold kristian.rosenv...@zenior.no:
Svnsubpub is just ridiculously
yes, an next times, it's just inefficient to navigate: we need some menus
opened
by default
IMHO, top bar menu isn't ready for the moment: still need to find an idea to
make it efficient
for the moment, I stringly prefer to stay with the classic left column
placement
Regards,
Hervé
Le
can actually dispatch menus in bars
a first step would be to have both bars, instead of top bar replacing left one
Regards,
Hervé
Le mardi 1 janvier 2013 19:30:13 Jesse Farinacci a écrit :
Greetings,
On Tue, Jan 1, 2013 at 6:48 PM, Hervé BOUTEMY herve.bout...@free.fr wrote:
IMHO, top bar
801 - 900 of 3649 matches
Mail list logo
