...it'd be so much better if we
had a way to support a proper format for Git SCM information, rather
than embedding all that information in a really complex pseudo-URL.
On 7/14/11 4:19 PM, Hervé BOUTEMY wrote:
SCM url have mutiple parts when multiple parts mean something.
As you speak about
Le vendredi 15 juillet 2011, John Casey a écrit :
On 7/14/11 6:41 PM, Hervé BOUTEMY wrote:
we call it a URL, but it's a String in the POM [2]
Nothing prevents another way of interpreting this String: say properties
format?
If we want to transform this String to a DOM object in the POM
+1
tested in Maven 3.0.4-SNAPSHOT [1] (sync pending)
notice that there are some glitches with documentation:
- plugin-info.html isn't there nor goals documentation (?)
- aggregating example should be modified like javadoc to show new goals and
mark aggregate parameter as obsolete
nothing that
against the label?
Is the idea to go ahead and make fixes to a checkout of the tag,
publish the site, and then patch them into trunk?
--benson
On Sat, Jul 16, 2011 at 5:06 AM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
+1
tested in Maven 3.0.4-SNAPSHOT [1] (sync pending)
notice
release of
JXR? It's not obvious how I could have caused these issues.
On Sat, Jul 16, 2011 at 3:36 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
qhat I usually do is patch the trunk
and when publishing the final version, I copy modified files from site to
my local checkout
yes
Good question :)
Current Maven versions (3.0.3 and 3.0.4-SNAPSHOT) use Aether 1.11, which has a
dual EPL/ASLv2 license [1].
As far new versions of Aether stay under ASLv2 license, there is no question
for Maven when upgrading dependency.
Now, Aether 1.12 was released under EPL license only,
Vincent S did a lot of work on JXR, and has a branch in sandbox
He's actually on holiday and should reply when he's back to make the good
choice
Regards,
Hervé
Le dimanche 17 juillet 2011, Benson Margulies a écrit :
For the next release, how would you feel about moving the plugin in
with the
, perhaps Sonatype might go back to dual-licensing
if asked?
On Sat, Jul 16, 2011 at 5:36 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
Good question :)
Current Maven versions (3.0.3 and 3.0.4-SNAPSHOT) use Aether 1.11, which
has a dual EPL/ASLv2 license [1].
As far new versions of Aether
I worked on Aether to extract Maven specific parts (into maven-aether-
provider): AFAIK, we are completely free to change anything in the formats
used by Maven, either for POM or repositories.
About licensing, I don't have any concern about EPL at Eclipse. The initial
announced intend was to
Maven Site Plugin 3.0 is now ready for release (with its documentation) for me
If anybody still has something to change, please explain what so we can fix it
and release ASAP
Regards,
Hervé
Le samedi 2 juillet 2011, Dennis Lundberg a écrit :
Hi
What's the status on this? I know Hervé
, Dennis Lundberg a écrit :
On 2011-07-22 00:48, Hervé BOUTEMY wrote:
Maven Site Plugin 3.0 is now ready for release (with its documentation)
for me
If anybody still has something to change, please explain what so we can
fix it and release ASAP
Thanks for all your work Hervé!
Now that we
:48, Hervé BOUTEMY wrote:
Maven Site Plugin 3.0 is now ready for release (with its documentation)
for me
If anybody still has something to change, please explain what so we can
fix it and release ASAP
Thanks for all your work Hervé!
Now that we plan for 3.0 to be the main version
-TransportProtocols%2528Wagons%2529
Le vendredi 22 juillet 2011, Dennis Lundberg a écrit :
On 2011-07-22 00:48, Hervé BOUTEMY wrote:
Maven Site Plugin 3.0 is now ready for release (with its
documentation) for me
If anybody still has something to change, please explain what so we
can
did you try what an end-user can see when he tries to use an unavailable
protocol?
I'm ok with more detailed error message.
But the stacktrace, which is the only message which is displayed at the end of
Maven reactor run, stating that protocol could not be found, is not helpful:
the detailed
I still need to investigate what's happenning with m-site-p 2.3 and Maven 2.2
yes, it's better to have same behaviour with every Maven version
I'll work on it tomorrow
Regards,
Hervé
Le mercredi 27 juillet 2011, Dennis Lundberg a écrit :
Hervé,
Do you have an idea how to fix this for Maven
if it is ok
Regards,
Hervé
-Lukas
On 07/27/2011 12:15 AM, Hervé BOUTEMY wrote:
did you try what an end-user can see when he tries to use an unavailable
protocol?
I'm ok with more detailed error message.
But the stacktrace, which is the only message which is displayed at the
end of Maven
just for the record, -1 too
waiting for Eclipse release, which is coming soon: great!
Regards,
Hervé
Le mercredi 27 juillet 2011, Benson Margulies a écrit :
As per the approved policy, this message opens a vote to allow Maven
releases to depend on EPL (and thus Category B) versions of Aether.
Le mercredi 27 juillet 2011, Tim O'Brien a écrit :
Vincent that seems like a mistake. Why add more specific elements like
Wiki and API. Why make the POM syntax this specific. Why not make it
free from, something like:
resource type=wiki
url!--- some Wiki URL --/url
/resource
Which
I found the culprit: MNG-5140
and the impact is reduced: only reports in a reportSet are affected
Given this, I think it is safe to keep the fix
Regards,
Hervé
Le mercredi 27 juillet 2011, Hervé BOUTEMY a écrit :
I still need to investigate what's happenning with m-site-p 2.3 and Maven
2.2
Le vendredi 29 juillet 2011, Mark Struberg a écrit :
Is it as simple as that for all SCMs?
Yes it is.
Remember the old days: this is only a fix for a 'fix'. Originally the SCM
URLs haven't been changed for child modules. This 'feature' only got
introduce later to make life easier for SVN
+1
Regards,
Hervé
Le jeudi 28 juillet 2011, Brett Porter a écrit :
On 28/07/2011, at 10:32 PM, Jason van Zyl wrote:
On Jul 28, 2011, at 8:25 AM, Mark Struberg wrote:
mom jason.
Before we ship 3.0.4 I'd like to fix the SCM URL postfix problem which
exists in lots of DSCMs. Will do
yes, I tried too and couldn't find (then chose to continue on m-site-p...), but
your conclusion is really plausible
I tried on every CI failures, fixed what I could fix, but actual failures are
really hard to fix (AFAIK, were the same on previous Sonatype's CI, then there
is really some logic
nice plan
the most important thing about 3.0 is that we shouldn't need to maintain 2
branches in parallel, which was a nightmare
With 3.0 out and the only branch to maintain, no doubt we can continue to
improve faster than previously
Regards,
Hervé
Le samedi 30 juillet 2011, Benson Margulies
Le samedi 30 juillet 2011, John Casey a écrit :
But, how can we keep it from leaking into plugins, when it's using the
same plexus component system as the rest of Maven?
This has long been a problem inside Maven, namely that we can't control
_which_ components plugin devs have access to, and
IMHO, it can make sense as a CLI option, to let you try multiple strategies
(normal, GUMP-like ie. LATEST, compatibility ie. OLDEST)
But I doubt it has a meaning neither at project level nor user level, nor
install level.
Project level is IMHO impossible, like Igor seems to have tried :)
User
I see this one regularly and don't frankly understand the need other than pure
theory.
Actual version comparison supports every numbering scheme I ever saw in
reality. The only choice that has been made that is a pure choice (neither
good nor bad, just a choice had to be made) is that unknown
Le dimanche 31 juillet 2011, Mark Derricutt a écrit :
The use case that we originally came with in our discussions revolved
around version ranges,
ok, that's not a version comparison but version (range) resolution question:
version ordering is here to define how artifacts are ordered, then the
+1
tested on Maven Core with success
Regards,
Hervé
Le samedi 30 juillet 2011, Dennis Lundberg a écrit :
Hi,
We solved 46+1 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleName=
Htmlversion=16829
ah, I knew you did something like this but could not find it :)
question: ok, random port, but random and guaranteed to success? ie it makes
the effort to find an unused port?
see r1152587: I chose an arbitrary port
we should add this to a FAQ, since this is a common use case
Regards,
Hervé
I recently used lookupMap API [1] to detect which wagon providers was
available in m-site-p 3.0
It worked like a charm
Regards,
Hervé
[1] http://plexus.codehaus.org/plexus-containers/plexus-container-
default/apidocs/org/codehaus/plexus/PlexusContainer.html#lookupMap(java.lang.Class)
Le mardi
Hi,
This project consists of a POM that contains settings that are likely to be
useful to any Apache project that is building and releasing code with Maven
2/3.
We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250version=12316643
There are still a
yeah, great!
now we should be able to trust the failure notifications: a great help.
thank you guys
Hervé
Le dimanche 7 août 2011, Mark Struberg a écrit :
w hot! :)
All our plugin builds (m2 m3) are now green again!
txs 2 all who worked very hard on fixing our plugins CI build!
Hi,
I feared the change was done inadvertently
I'm ok with the reasoning: I'll fix it immediately
thanks for the feedback
Hervé
Le dimanche 7 août 2011, Dennis Lundberg a écrit :
Hi
I think that the links to Maven sub projects are more important than the
ASF links, so they should be
yes, you found the source of the copy/paste
removing seems safe
Regards,
Hervé
Le lundi 8 août 2011, Arnaud Héritier a écrit :
I agree. For me it is also an erroneous copy/paste
On Mon, Aug 8, 2011 at 12:44 PM, Benjamin Bentmann
benjamin.bentm...@udo.edu wrote:
Hi,
does anybody
yes, this one is lasting for a long time
I added the traces a few months ago to track it when it was at Sonatype CI
server, but without finding the cause
if anybody find a solution, I'm interested in understanding...
Regards,
Hervé
Le lundi 8 août 2011, Robert Scholte a écrit :
Another
The Maven team is pleased to announce the release of the Apache Parent POM,
version 10.
This POM contains settings that are likely to be useful to any Apache project
that is building and releasing code with Maven 2/3.
http://maven.apache.org/pom/asf/
You should specify the version in your
Hi,
These are parent POMs for Maven projects: version 21 for Maven parent, version
22 for Maven Plugins parent and version 17 for Maven Shared Components parent.
We solved 11/7/7 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250version=12316641
Le mercredi 17 août 2011, Brett Porter a écrit :
+1
Though I'm not sure why the snapshots repository is now repeated?
it is repeated to let the pom resolve its parent when it is a SNAPSHOT and the
relativePath doesn't point to it (no global checkout from trunks), for example
in a CI server
Le jeudi 18 août 2011, jdca...@apache.org a écrit :
Author: jdcasey
Date: Thu Aug 18 02:25:18 2011
New Revision: 1158995
URL: http://svn.apache.org/viewvc?rev=1158995view=rev
Log:
reverting to vanilla sisu,
great!
I don't really know why this modified sisu was needed in the first place,
+1 binding
Hervé
Le jeudi 18 août 2011, Arnaud Héritier a écrit :
Hi all,
Thus as decided with Mark and Kristian I relaunch a new vote with a
better scope about what we are voting for.
Next releases of SISU and Aether will be released at Eclipse.org under
EPL 1.0 license.
Before
Here is my +1
Hervé
Le lundi 15 août 2011, Hervé BOUTEMY a écrit :
Hi,
These are parent POMs for Maven projects: version 21 for Maven parent,
version 22 for Maven Plugins parent and version 17 for Maven Shared
Components parent.
We solved 11/7/7 issues:
https://issues.apache.org/jira
Hi,
The vote has passed with the following result :
+1 (binding): John Casey, Mark Struberg, Stephen Connolly, Olivier Lamy,
Vincent Siveton, Brett Porter, Hervé BOUTEMY
I will promote the artifacts to the central repo.
Hervé
The Maven team is pleased to announce the release of the parent POMs for Maven
projects: version 21 for Maven parent, version 22 for Maven Plugins parent and
version 17 for Maven Shared Components parent.
http://maven.apache.org/pom/maven/
http://maven.apache.org/pom/maven-plugins/
+1
Hervé
Le jeudi 18 août 2011, Kristian Rosenvold a écrit :
Hi,
The main intention of this release is to get java7 file attribute api's
in use, which can be a great performance improvment for java7 mac
linux users. There should also be some improvement for 1.5/1.6 users,
and this
code is in sandbox: [1]
it has better syntax highlighting features (since it knows java syntax), and
even UML graphing features: would be terrible IMHO
but the problem is actually updating javaG.g [2] with latest grammar from
antlr site, to support annotations.
For the moment, we tried to stay
Hi,
I want to to make a release in a few days with what is actually done: there
are a lot of new things.
If anybody has something to add before the release, please tell.
Regards,
Hervé
-
To unsubscribe, e-mail:
yes, it has already been improved in svn, but I suppose there is still room
for improvement
regards,
Hervé
Le lundi 22 août 2011, Vincent Siveton a écrit :
Very cool Hervé and thanks for your efforts.
If you have time, review the documentation!
Cheers,
Vincent
2011/8/21 Hervé
I have been confused for a long time too, but finally had some explanations I
can try to summary here: not sure it will give every answers, but at least I
suppose it will help.
It has to do with the difference in API between a maven plugin (execute method
from plugin-api [1]) and a reporting
,
Hervé
[1] http://maven.apache.org/plugins/maven-javadoc-plugin/examples/selective-
javadocs-report.html
Le mardi 23 août 2011, Benson Margulies a écrit :
On Tue, Aug 23, 2011 at 5:26 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
I have been confused for a long time too, but finally had some
Le samedi 27 août 2011, Benson Margulies a écrit :
The doxia 1.2 POM has some rather surprising things in it. Notably,
the dependencyManagement picks up the version of the current project,
so they all tend to turn into 1.0-SNAPSHOT.
yes, I saw it even if I don't understand how/why it does that
Hi,
We solved 24 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095styleName=Htmlversion=16795
There are still a good number of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11095status=1
Staging repo:
Hervé BOUTEMY herve.bout...@free.fr:
Hi,
We solved 24 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095styleNam
e=Htmlversion=16795
There are still a good number of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11095
+1
FYI, I re-deployed the site with aggregate reports and site.xml improvements
and with -Preporting, that you seemed to have forgotten
Le vendredi 2 septembre 2011, Benson Margulies a écrit :
Hi,
We solved 5 issues:
here is my +1
Le mercredi 31 août 2011, Hervé BOUTEMY a écrit :
Hi,
We solved 24 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095styleName=
Htmlversion=16795
There are still a good number of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa
Hi,
The vote has passed with the following result :
+1 (binding): Kristian Rosenvold, Vincent Siveton, John Casey, Olivier Lamy,
Emmanuel Venisse, Hervé Boutemy
+1 (non binding): Tamás Cservenák, Jesse Glick
I will promote the artifacts to the central repo
The Maven team is pleased to announce the release of the Maven Archetype
Plugin, version 2.1
Archetype is a Maven project templating toolkit.
http://maven.apache.org/archetype/maven-archetype-plugin/
Release Notes - Maven Archetype - Version 2.1
** Bug
* [ARCHETYPE-220] - Unable to
there is a good article on MAVENUSER to introduce to lifecycle:
http://docs.codehaus.org/display/MAVENUSER/introduction-to-the-lifecycle
adding a last customizing lifecycle bindings chapter would make sense
(directly or with a link to your blog post)
notice: your article is about customizing
+1
Hervé
Le dimanche 11 septembre 2011, Vincent Siveton a écrit :
Hi,
I like to move the Eclipse Doxia Editor to the trunk ie
http://svn.apache.org/repos/asf/maven/sandbox/trunk/doxia/doxia-ide/eclipse
/ to
http://svn.apache.org/repos/asf/maven/doxia/doxia-ide/eclipse/
Here is a
please open a Jira issue in http://jira.codehaus.org/browse/MJAVADOC
and adding a unit test or integration test would help us be sure that the
improvement does really improve the plugin
Regards,
Hervé
Le lundi 12 septembre 2011, Erik Lindblad a écrit :
The docletPath parameter is
thanks, I missed that
does it mean we should remove the dev profile?
Its intent seems exactly what is done without this configuration: use current
instead of stable
Le mardi 13 septembre 2011, Dennis Lundberg a écrit :
See below...
On 2011-09-13 20:49, hbout...@apache.org wrote:
Author:
all Doxia-related Jira projects are on Codehaus: I suppose we won't change
just for this one, it would be hard to follow
regards,
Hervé
Le samedi 17 septembre 2011, Olivier Lamy a écrit :
Hello
In Apache Jira ?
--
Olivier
Le 17 sept. 2011 00:11, Vincent Siveton vsive...@apache.org a
Le vendredi 16 septembre 2011, ol...@apache.org a écrit :
Author: olamy
Date: Fri Sep 16 21:07:28 2011
New Revision: 1171784
URL: http://svn.apache.org/viewvc?rev=1171784view=rev
Log:
[MCHANGELOG-123] Patch with support for SCM provider implementations
(similar to release plugin) add
I don't have a view on the way things happen nor how much steps are still
pending, but FYI, things are on their way: there is now a project page [1]
(even if empty), and CLAs are on their way: I was asked for it a week ago (i
suppose it's the same for others) and replied a few days ago, I'm now
my comments are in the Jira issue
but the summary is: I don't think this scenario requires a new feature
Regards,
Hervé
Le samedi 17 septembre 2011, Jason Pyeron a écrit :
-Original Message-
From: Jason van Zyl
Sent: Saturday, September 17, 2011 11:13
To: Maven Developers List
with ${maven.home}, you can have your use case
for other options:
- POM is a nonsense to me
- WORKINGDIRECTORY too: notice that it can be done with ${user.dir}, if you
really want to
the more I'm thinking at this, the more I'm convinced we should not accept
relative path at all: with java
we have multiple jobs on ASF's Jenkins instance that fail when publishing the
result (after a success in the build)
does anybody know the cause?
Regards,
Hervé
Le dimanche 18 septembre 2011, Apache Jenkins Server a écrit :
See https://builds.apache.org/job/maven-wagon/56/changes
Changes:
ok
how do we upgrade?
Le dimanche 18 septembre 2011, Olivier Lamy a écrit :
I think about a jenkins issue which should be fix in more recent version.
--
Olivier from a vt100 mobile device
Le 18 sept. 2011 07:47, Hervé BOUTEMY herve.bout...@free.fr a écrit :
we have multiple jobs
done: https://issues.apache.org/jira/browse/INFRA-3935
Le dimanche 18 septembre 2011, Olivier Lamy a écrit :
Create a jira @ https://issues.apache.org/jira/browse/INFRA
to upgrade to 1.430.
2011/9/18 Hervé BOUTEMY herve.bout...@free.fr:
ok
how do we upgrade?
Le dimanche 18 septembre
+1
Hervé
Le mercredi 21 septembre 2011, Olivier Lamy a écrit :
Hello,
I'd like to release Apache Maven Indexer 4.1.2.
We fixed 5 issues :
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truejqlQuery=pro
ject+%3D+MINDEXER+AND+fixVersion+%3D+%224.1.2%22+AND+status+%3D+Closed+ORDE
+1
Hervé
Le lundi 26 septembre 2011, Olivier Lamy a écrit :
Hello,
I'd like to release Apache Maven Wagon 2.0.
We fixed 31 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?version=17379styleName=T
extprojectId=10335Create=Create
Staging repo :
+1
Hervé
Le mardi 27 septembre 2011, Paul Gier a écrit :
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=17
431
There are still lots of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejq
Hi,
have a look at [1]
Regards,
Hervé
[1] http://maven.apache.org/ref/3.0.3/maven-model-
builder/apidocs/org/apache/maven/model/io/package-frame.html
Le mercredi 28 septembre 2011, Samuel Robert a écrit :
Hi,
I am starting with writing a custom Maven plugin for my projects (Maven
2). I
ok, then you'll have to duplicate the code: it's not really big nor complex
regards,
Hervé
Le mercredi 28 septembre 2011, Samuel Robert a écrit :
Thanks.
However it seems to work only with a Maven 3 environment. I am still using
Maven 2.
Samuel
On 28 September 2011 15:28, Hervé BOUTEMY
Hi Benjamin,
Thanks for the feedback, since this is an unexpected fact!
Is there a difference between configuration block and
parameter.implementation element?
Regards,
Hervé
Le Mercredi 19 Octobre 2011 10:15:44 Benjamin Bentmann a écrit :
Hi Hervé,
Author: hboutemy
Date: Tue Oct 18
+1
Regards,
Hervé
Le Lundi 24 Octobre 2011 15:03:47 Mark Hobson a écrit :
Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127version=175
20
There are still a couple of issues left in JIRA:
Ip updated DOXIASITETOOLS-51
please review and propose improvements
Regards,
Hervé
Le Jeudi 27 Octobre 2011 16:03:40 Ivan Habunek a écrit :
On 27 October 2011 15:56, Simone Tripodi simonetrip...@apache.org wrote:
I'll update later bot samples of generated site to see the results :)
I
+1
Hervé
Le Mercredi 26 Octobre 2011 17:36:48 John Casey a écrit :
Hi everyone,
MAE is a new project that I've been working on for about a year and a
half. It's goal is to wrap the Maven APIs and make them easier to embed
inside other applications. This enables applications to orchestrate
np: I liked the idea (and was sorry to not have done it before...)
:)
Le Samedi 29 Octobre 2011 09:34:08 Olivier Lamy a écrit :
Yup, sorry for the issue.
I have fixed that locally but not yet committed as I worked on an other
issue.
2011/10/29 hbout...@apache.org:
Author: hboutemy
+1
Hervé
Le Vendredi 28 Octobre 2011 19:58:14 Benson Margulies a écrit :
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540version=166
95
There are still a couple of issues left in JIRA:
+1
tested on archetype-common
Regards,
Hervé
Le Vendredi 28 Octobre 2011 20:09:22 Benson Margulies a écrit :
To: Maven Developers List dev@maven.apache.org
Subject: [VOTE] Release Maven XXX Plugin version Y.Z
Hi,
We solved 9 issues:
Hi,
I reworked on Java 5 Annotations for Plugins proposal started a while ago: [1]
Before going deeper into code, I'd like to have some review of the proposed
form of the tool. Any comment is welcome.
Regards,
Hervé
[1]
+1 (binding)
Regards,
Hervé
Le Jeudi 10 Novembre 2011 16:53:34 Olivier Lamy a écrit :
Hello,
Since last vote things have changed:
* aether is in incubation process @eclipse
* sisu is in incubation process @eclipse
Due to the fact that those process can be long before having an
+1
Regards,
Hervé
Le Mardi 8 Novembre 2011 19:05:16 Olivier Lamy a écrit :
Hello,
I'd like to release Apache Maven PMD Plugin 2.6.
We fixed 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11140version=164
37.
Staging repository:
really nice!
Just to understand, why do you publish each IT separately when they are
integrated into the skin documentation with a simple mvn -Prun-its,reporting
install site?
(notice I just fixed it, it was broken since sample IT was renamed)
Yes, I think it's time for graduation.
Regards,
+1
Hervé
Le Mardi 29 Novembre 2011 06:44:29 Benson Margulies a écrit :
Hi,
We solved an issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?atl_token=ACIO-CAVI-QX7G-9I
AS%7C083f4f243731b9ee702e76ba2ccc07788ab70ac3%7Clinversion=16798styleName=
TextprojectId=11761Create=Create
+1
Hervé
Le Mardi 29 Novembre 2011 12:02:48 Benson Margulies a écrit :
Hi,
We solved N issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126version=13
669
There are still a couple of issues left in JIRA:
+1
Hervé
Le Mercredi 30 Novembre 2011 15:07:03 Kristian Rosenvold a écrit :
Hi,
We solved 22 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=178
56
This version supports JUnit 4.8 @Category annotation, using the
groups parameter on the plugin (using the
the code is in DefaultModelBuilder [1]
Regards,
Hervé
[1] http://maven.apache.org/ref/3.0.4/maven-model-builder/
Le Lundi 5 Décembre 2011 23:31:03 Mark Derricutt a écrit :
I've not yet looked at maven internal code about how one might implement
this ( to be honest, at this point in time I'm
+1
Hervé
Le Mardi 13 Décembre 2011 17:20:52 Stephen Connolly a écrit :
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=H
tmlversion=18224
There are still a couple of issues left in JIRA:
+1
Hervé
Le Jeudi 15 Décembre 2011 16:07:43 Olivier Lamy a écrit :
Hello,
I'd like to release Apache Maven Wagon 2.2
We fixed 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335version=180
90
The staged repo is available here:
Hi Robert,
I just subscribed to rat-dev to try to help.
From your last message on the rat-dev list, I suppose you'll be interested in
the following documentation [1] :)
Regards,
Hervé
[1] http://maven.apache.org/guides/plugin/guide-java-plugin-
development.html#Shortening_the_Command_Line
Hi Simone,
The classical way to do such versioned + non-versioned site deployment is by
using stagingSiteURL configuration in site plugin, see [1]
Then the release documentation explains how to stage the versionned doc
I suppose this is usable in this case, instead of this rc profile, no?
forgot the link...
[1] http://svn.apache.org/viewvc/maven/plugins/tags/maven-
plugins-22/pom.xml?view=markup
and the doc to staging release:
http://maven.apache.org/developers/release/maven-plugin-release.html
Le vendredi 6 janvier 2012 01:14:01 Hervé BOUTEMY a écrit :
Hi Simone
://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Fri, Jan 6, 2012 at 1:16 AM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
forgot the link...
[1] http://svn.apache.org/viewvc/maven/plugins/tags/maven-
plugins
I don't know precisely if the configuration of the release plugin will be ok
without the rc profile.
But with the stagingSiteURL configuration, you can run the Staging the latest
documentation part of the standard plugin release process [1]:
cd target/checkout
mvn site site:stage-deploy
Hi Dennis,
It's still here [1], it was duplicated before [2] (then caused mvn to fail)
Regards,
Hervé
[1] http://svn.apache.org/viewvc/maven/skins/trunk/maven-fluido-
skin/pom.xml?view=markup
[2] http://svn.apache.org/viewvc/maven/skins/trunk/maven-fluido-
+1
Le mercredi 11 janvier 2012 18:22:29 Benson Margulies a écrit :
I tend to feel that this community is a bit whelmed, and that we'd do
better service to the world at large if we drew a line in the sand at
2.2.1. Anyone who really wants new functionality with older core maven
can step up and
Le samedi 14 janvier 2012 20:22:15 Stephen Connolly a écrit :
personally i think we need to draw a line in the sand for all plugins...
2.2.1 is the best line at the moment imho...
+1
2.1.0 and 2.2.0 are not recommended versions, and drawing a line above them
makes our message to users that
+1
Hervé
Le jeudi 12 janvier 2012 23:40:27 Dennis Lundberg a écrit :
Hi,
We solved 4 issues, including
[MEAR-60] Improve support for skinny war files
which has 50 votes:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132styleName=H
tmlversion=17293
There are still a
+1
Core ITs published as run with this release
http://maven.apache.org/core-its/core-it-suite/
Hervé
Le mardi 17 janvier 2012 11:14:02 Olivier Lamy a écrit :
Hello,
After some RCs, it's now time to cut the release. So I start the vote
for Apache Maven 3.0.4.
The release notes is
501 - 600 of 3649 matches
Mail list logo
