Le lundi 9 avril 2007 05:39, vous avez écrit :
-1
The uberjar does not work equivalently to the last release, as it
does not contain the lightweight http wagon. I've filed this as
MANTTASKS-64. I also noticed that the uberjar is larger than the
previous one, despite omitting some things - I
Le dimanche 22 avril 2007 08:42, Hervé BOUTEMY a écrit :
I'll work on documentation enhancement, to reflect new features on
http://maven.apache.org/ant-tasks.html
work done: a patch has been added to MANTTASKS-64
as written in the comment: My (fr)english is not so good, you'll probably
need
Le dimanche 22 avril 2007 17:32, Jason van Zyl a écrit :
I staged the Ant Tasks to the same place and
they look fine now.
I checked them today: they seem fine to me
Time for a second take ?
Hervé
-
To unsubscribe, e-mail:
Le lundi 23 avril 2007 21:00, Jason van Zyl a écrit :
I checked them today: they seem fine to me
Time for a second take ?
Yup, I guess I just wanted to see if anyone thought it wise to
include the libraries necessary for SSH deployment. Currently you
could not deploy via SSH without adding
Le lundi 23 avril 2007 22:05, Jason van Zyl a écrit :
you mean:
artifact:install-provider artifactId=wagon-ssh version=1.0-
beta-2/
is not sufficient?
and wagon-ftp? and wagon-webdav?
Doesn't take much to make it that much easier.
ok, why not.
I tried to get how many KB each
...
Hervé
Le mardi 24 avril 2007 09:12, Hervé BOUTEMY a écrit :
Le lundi 23 avril 2007 22:05, Jason van Zyl a écrit :
you mean:
artifact:install-provider artifactId=wagon-ssh version=1.0-
beta-2/
is not sufficient?
and wagon-ftp? and wagon-webdav?
Doesn't take much to make
Le mardi 1 mai 2007, Jerome Lacoste a écrit :
Maybe there could be an easy way to let users use the latest ? maybe
something like
mvn -L ... ( L for latest)
that would ignore all specified versions, without requiring a POM
change ? Maybe too radical.
such a LATEST option would be very
Le mardi 1 mai 2007, Tomasz Pik a écrit :
On 5/1/07, Hervé BOUTEMY [EMAIL PROTECTED] wrote:
Le mardi 1 mai 2007, Jerome Lacoste a écrit :
Maybe there could be an easy way to let users use the latest ? maybe
something like
mvn -L ... ( L for latest)
that would ignore all
Le jeudi 26 avril 2007, Jason van Zyl a écrit :
Nice, thanks.
I'm doing some Ant (well, a conversion) so I'll take a look as soon
as I can.
Thanks,
Jason.
Any news on Maven Ant Tasks?
What can I do to help release 2.0.6?
Hervé
+1 non-binding :)
Hervé
Le mercredi 16 mai 2007, Jason van Zyl a écrit :
Hi,
Repost of the vote after fixing the issues with the uber JAR that was
produced. Hervé and I have tried them and they appear to work fine.
The staging repository is here:
Here is a little patch for the 3 pages that have to be updated in maven-site
and published.
The binaires are not yet in the distribution library
http://www.apache.org/dyn/closer.cgi/maven/binaries: I suppose this is
different from the production repository.
Hervé
Le mardi 22 mai 2007, Jason
Le mercredi 23 mai 2007, Jason van Zyl a écrit :
On 22 May 07, at 5:10 PM 22 May 07, Hervé BOUTEMY wrote:
Here is a little patch for the 3 pages that have to be updated in
maven-site
and published.
The binaires are not yet in the distribution library
http://www.apache.org/dyn
Hi,
If you look at dependencies Maven Ant Task, you'll see this API at work.
Hervé
Le vendredi 25 mai 2007, Kevin Stembridge a écrit :
Hi folks,
I'm writing a patch for the webstart-maven-plugin and I'm having some
trouble trying to use ArtifactResolver to resovle transitive
dependencies.
really great!
Thank you
Le lundi 28 mai 2007, Jason van Zyl a écrit :
The Apache Maven team would like to announce the availability of the
Maven Ant Tasks 2.0.6.
You can find the binaries here:
http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-ant-
tasks-2.0.6.jar
You can find
Le lundi 28 mai 2007, Jason van Zyl a écrit :
Hi,
Thanks to a big push by Herve Boutemy we have a lot of improvements
to the Maven Ant Tasks and accompanying documentation.
Thanks for your time committing patches.
We can probably do another release shortly.
This time, Maven Ant Tasks 2.0.7
Le lundi 28 mai 2007, Jason van Zyl a écrit :
This time, Maven Ant Tasks 2.0.7 could be ready before Maven 2.0.7
itself :)
Heh, yah we should probably just stick with 2.0.6.1 not to confuse
people ... We need to come up with a standard versioning system for
tools based on a fixed version
Hi Jason,
No problem for sunday (PM for me, AM for you) : there are only 2 Jira to
commit, one of which is really important (and finally reduced to 1 line
patch: MANTTASKS-18).
Regards,
Hervé
Le mercredi 13 juin 2007, Jason van Zyl a écrit :
Herve,
You going to be free anytime this
Le mercredi 20 juin 2007, Brian E. Fox a écrit :
I discovered http://jira.codehaus.org/browse/MNG-2961 while working on
mdep a while back.
same for me while working on http://jira.codehaus.org/browse/MANTTASKS-18
It should be an easy fix but I'm pondering what the
least intrusive fix is.
set to xxx-SNAPSHOT and never changed
after, even if the parameter during the call was xxx-timestamp.
Is this ok to do so, or should we investigate why it is called sometimes with
a timestamped version and not -SNAPSHOT?
Hervé
-- Kenney
Hervé BOUTEMY wrote:
Le mercredi 20 juin 2007, Brian
Le jeudi 21 juin 2007, Jason van Zyl a écrit :
It seems like there are many problems with encoding that could be
easily solved with a couple tweaks to modello, specifically the
reader and writing so I've scheduled these for 2.0.8. There some
patches for these and hopefully Herve will work his
integrating it the code generation mechanism of
Modello would be a lot better: Jason, if your proposal to have access to
Modello is still valid, I'm interested.
Regards
Hervé
-- Kenney
Hervé BOUTEMY wrote:
Le jeudi 21 juin 2007, Jason van Zyl a écrit :
It seems like there are many problems
Le vendredi 22 juin 2007, Kenney Westerhof a écrit :
* There are multiple methods for version modification/retrieval:
* resolved version (setter only - sets version)
* version (sets version, baseversion, and versionrange; gets version)
* base version (sets base version, gets baseversion
term, it could be coded to permit relative entities.
WDYT?
Hervé
This is not a problem because we discourage the usage of xml entities in
our xml documents, but we have to continue to say it !!!
Arnaud
On 22/06/07, Hervé BOUTEMY [EMAIL PROTECTED] wrote:
Le vendredi 22 juin 2007, Kenney
Le samedi 23 juin 2007, Brett Porter a écrit :
We shouldn't permit relative entities in the POM - it would cause
grief when deployed to the repository.
- Brett
ok, then the target API is read(InputStream)
I won't add read(URL).
regards,
Hervé
On 23/06/2007, at 5:29 AM, Hervé BOUTEMY wrote
Le samedi 23 juin 2007, Kenney Westerhof a écrit :
Hervé BOUTEMY wrote:
Le samedi 23 juin 2007, Brett Porter a écrit :
We shouldn't permit relative entities in the POM - it would cause
grief when deployed to the repository.
- Brett
ok, then the target API is read(InputStream)
I
Le vendredi 22 juin 2007, Hervé BOUTEMY a écrit :
Le vendredi 22 juin 2007, Kenney Westerhof a écrit :
* There are multiple methods for version modification/retrieval:
* resolved version (setter only - sets version)
* version (sets version, baseversion, and versionrange; gets version
Hi,
Just a little note on this release.
There are a lot of bugfixes (SNAPSHOT downloading, for example), new features
(VersionMapper, remoteRepository support for pom and install-provider tasks)
documented on http://maven.apache.org/ant-tasks.html.
But there are 2 incompatible changes that you
Le jeudi 28 juin 2007, John Casey a écrit :
On Jun 28, 2007, at 2:29 AM, Hervé BOUTEMY wrote:
2. MANTTASKS-65: central is not automatically added any more if a
remoteRepository is set: the code has been changed to work as the
documentation said
This seems inconsistent with the way Maven
://maven.apache.org/release-notes.html ?
The change for localRepository is documented at the end of the doc, in Type
ReferencelocalRepository section. But it is not really easy to find it...
On 27 Jun 07, at 11:29 PM 27 Jun 07, Hervé BOUTEMY wrote:
Hi,
Just a little note on this release
Le jeudi 28 juin 2007, Jason van Zyl a écrit :
On 28 Jun 07, at 1:33 PM 28 Jun 07, Hervé BOUTEMY wrote:
Le jeudi 28 juin 2007, John Casey a écrit :
On Jun 28, 2007, at 2:29 AM, Hervé BOUTEMY wrote:
2. MANTTASKS-65: central is not automatically added any more if a
remoteRepository is set
patch MANTTASKS-76_site-release.diff added to MANTTASKS-76
Ready for the release!
Hervé
Le jeudi 28 juin 2007, Jason van Zyl a écrit :
On 28 Jun 07, at 1:54 PM 28 Jun 07, Hervé BOUTEMY wrote:
Le jeudi 28 juin 2007, Jason van Zyl a écrit :
Thanks Herve, I forgot about adding that even
Le vendredi 29 juin 2007, Hervé BOUTEMY a écrit :
Le vendredi 29 juin 2007, Hervé BOUTEMY a écrit :
patch MANTTASKS-76_site-release.diff added to MANTTASKS-76
added patch MANTTASKS-76_license.diff too, while we're at it...
are these patches ok to get the release out, or should I change
Le mercredi 4 juillet 2007, Jason van Zyl a écrit :
Cool, thanks I will take a look. The only comment I would make is
that all the categories on the bottom of that page can be merged into
the list of the main body of the page.
We also need to represent sub-categories. For example
+1
but it seems that actual Continuum server is compiling with jdk 1.5 instead of
1.4
The following build should have failed since the commit makes use of
String.contains(String) API in CheckDependencySnapshotsPhase class
see
I looked at this build failure and found misc problem when investigating:
1. I can't reproduce the problem on my machine:
same Maven version, same JDK version, no SNAPSHOT dependency, but I get no
surefire failure
Do I miss something in my configuration? Does somebody reproduce the problem
on
to be able to run the builds
manually.
Hervé BOUTEMY wrote:
I looked at this build failure and found misc problem when investigating:
1. I can't reproduce the problem on my machine:
same Maven version, same JDK version, no SNAPSHOT dependency, but I get
no surefire failure
Do I miss
Le samedi 1 septembre 2007, Brian E. Fox a écrit :
I think we can do this just by generating a sample pluginManagement
snippet on the site somewhere. I don't think anything fancy is needed,
simply providing the snipet so someone can copy and paste will be more
than sufficient. Having it
can somebody with proper karma remove this project definition?
And perhaps create a new project group for enforcer:
http://svn.apache.org/viewvc/maven/enforcer/trunk/
Adding a jdk14 profile would be useful too.
Hervé
Le samedi 1 septembre 2007, [EMAIL PROTECTED] a écrit :
Online report :
B
Hervé
Le dimanche 2 septembre 2007, Brett Porter a écrit :
I'd like to hear from as many people as possible their opinion this
topic (even if you just want to say '0' so we know where you stand).
[ ] (A) All plugin versions must be specified by the project or its
parent hierarchy
, Vincent, Brett, Dennis)
This vote has passed.
Please join me in congratulating Hervé!
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 12, 2007 6:44 PM
To: Maven Developers List
Subject: [VOTE] Commit Access for Hervé Boutemy
work done:
- r585265 for trunk
- r585268 for 2.0.x branch
I didn't add the integration-test attached to MNG-2254: Brian, if you can take
a look at it, please.
More explanations about these encoding fixes can be found at
http://docs.codehaus.org/display/MAVENUSER/XML+encoding in the Technical
Le mercredi 24 octobre 2007, Dennis Lundberg a écrit :
[EMAIL PROTECTED] wrote:
Author: hboutemy
Date: Tue Oct 23 14:36:41 2007
New Revision: 587665
URL: http://svn.apache.org/viewvc?rev=587665view=rev
Log:
encoding fixes
Modified:
it is a known limitation that before Maven 2.0.6, plexus-utils version was
tied to Maven Core and could not be changed by plugins launched: it has been
fixed in Maven 2.0.6 with MNG-2892
that perfectly explains why you have problems when using Maven 2.0.4 but not
when using Maven 2.0.6
Hervé
Hi,
I'm working on XML encoding support for Maven 2.0.8: did you know? ;)
Everything is ready for Maven itself: IT mng-2254-PomEncoding passes.
Now I'm looking at plugins, and I just found one important issue: there are 4
core plugins reading and writing POM files - install, deploy, release
-Original Message-
From: Hervé BOUTEMY [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 25, 2007 5:44 PM
To: Maven Developers List
Subject: XML encoding, Maven and plugins
Hi,
I'm working on XML encoding support for Maven 2.0.8: did you know? ;)
Everything is ready for Maven itself
Le jeudi 30 août 2007, Dennis Lundberg a écrit :
Hi
Would someone be so kind and add karma for me (dennisl) on
maven.zones.apache.org, so that I can run plugin builds from Continuum.
Hi,
Can I (hboutemy) have some karma too to work on encoding for plugins? I'm
fighting with a stupid problem
Le jeudi 01 novembre 2007, Brett Porter a écrit :
On 01/11/2007, at 9:18 PM, Hervé BOUTEMY wrote:
Le jeudi 30 août 2007, Dennis Lundberg a écrit :
Hi
Would someone be so kind and add karma for me (dennisl) on
maven.zones.apache.org, so that I can run plugin builds from
Continuum
plugin
On 10/25/07, Hervé BOUTEMY [EMAIL PROTECTED] wrote:
Le jeudi 25 octobre 2007, Brian E. Fox a écrit :
Herve,
The enforcer-rules also reads the pom files in the requirePluginVersion
rule.
ok, thanks for the information
I'll fix it, there should be no problem since:
1
pfew, couldn't have been faster on IRC
:)
thanks
Hervé
Le jeudi 01 novembre 2007, Brett Porter a écrit :
added :)
On 02/11/2007, at 9:29 AM, Hervé BOUTEMY wrote:
Le jeudi 01 novembre 2007, Brett Porter a écrit :
On 01/11/2007, at 9:18 PM, Hervé BOUTEMY wrote:
Le jeudi 30 août 2007
Le jeudi 01 novembre 2007, Dennis Lundberg a écrit :
Will this really work?
good question: I'll need to make a real world test to confirm that, which I
didn't do for the moment.
The site-plugin depends on doxia, which depends on plexus-utils-1.4.x.
And IIUC we need Maven 2.0.6 to be able to
Le vendredi 02 novembre 2007, Hervé BOUTEMY a écrit :
Le jeudi 01 novembre 2007, Dennis Lundberg a écrit :
Will this really work?
good question: I'll need to make a real world test to confirm that, which
I didn't do for the moment.
I just tried to compile and install the site plugin
I just found http://docs.codehaus.org/display/MAVEN/Releases, which is exactly
the page I was looking for. I'd like to add some informations in it, but I
can't edit it.
Can someone give me sufficient karma, please?
Hervé
-
To
they know it's ok.
- Brett
On 03/11/2007, at 6:14 AM, Hervé BOUTEMY wrote:
I just found http://docs.codehaus.org/display/MAVEN/Releases, which
is exactly
the page I was looking for. I'd like to add some informations in
it, but I
can't edit it.
Can someone give me sufficient karma
can someone expert in release plugin review this commit?
I had to upgrade the dependency and fix expected POM files: I don't see any
problem in the new POM content, but I prefer to ask for review
If it is ok, I'll be able to merge the changes from branch back to trunk and
close MRELEASE-87.
novembre 2007, Brian E. Fox a écrit :
Herve,
Any of the plugins that were changed need to have a prerequisite on maven
2.0.6 because they need a new plexus-utils. I found and fixed this already
in enforcer.
--Brian
-Original Message-
From: Hervé BOUTEMY [mailto:[EMAIL PROTECTED
2007, Brian E. Fox a écrit :
I must have missed that thread. It wasn't working in the enforcer so I'm
not sure.
-Original Message-
From: Hervé BOUTEMY [mailto:[EMAIL PROTECTED]
Sent: Monday, November 05, 2007 11:25 PM
To: Maven Developers List
Subject: Re: XML encoding, Maven
Perhaps I know the code that changed the order:
while fixing [MANTTASKS-22] ensure proper order of artifacts in
ArtifactResolutionResult, the fix in trunk (r591996) was to transform a
HashSet to a LinkedHashSet in
o.a.m.artifact.resolver.ArtifactResolutionResult.
But when porting the fix back
nobody to review the change?
nobody against me merging it to trunk?
Le dimanche 04 novembre 2007, Hervé BOUTEMY a écrit :
can someone expert in release plugin review this commit?
I had to upgrade the dependency and fix expected POM files: I don't see any
problem in the new POM content, but I
+1
Hervé
Le jeudi 22 novembre 2007, nicolas de loof a écrit :
+1
I really like the run-in-debug mode introduced by MNG-2105.
2007/11/22, Brian E. Fox [EMAIL PROTECTED]:
It's that time again, finally. The RC's have been floating for a few
weeks now and no new issues have surfaced. (the
+1
Hervé
Le vendredi 23 novembre 2007, Brett Porter a écrit :
Alex did the work to make TestNG support pretty much fully functional
on Surefire trunk some months back and he and Dan Fabulich are now
discussing this on the surefire-dev list and looking to complete the
work. Alex is already a
+1
Hervé
Le mercredi 21 novembre 2007, Brett Porter a écrit :
I'd like to call a vote for Nicolas de Loof as a committer, based
primarily on his work for Archiva, but also from being active in the
general Maven community for quite some time. He has been relentlessly
testing and identifying
+1
Hervé
Le mercredi 21 novembre 2007, Vincent Siveton a écrit :
Hi,
In the preparation of the Maven Clean Plugin release, I would like to
release the maven-shared-io:1.1
The last release was done around one year ago.
Staging repo:
http://people.apache.org/~vsiveton/staging-repo/
Vote
-0: I found 2 problems
1. problem with xdoc files: an additional newline is added to the generated
HTML after every closing tag.
If there shouldn't be any space between the tag and the text immediately
following, this causes an unwanted space. This causes trouble in pre
sections too, where
issue and fix the code. I'll do it later
if nobody else does inbetween.
regards,
Hervé
Le mardi 27 novembre 2007, Hervé BOUTEMY a écrit :
-0: I found 2 problems
1. problem with xdoc files: an additional newline is added to the generated
HTML after every closing tag.
If there shouldn't
Le vendredi 30 novembre 2007, Vincent Siveton a écrit :
Hi Hervé,
The goal of this branch was originaly to release the site plugin and
MPIR, without an important issue found in the doxia-1.0-alpha-9.
Now that site plugin is out, I dont think that we need to maintain it:
I hope we will
Le samedi 01 décembre 2007, Vincent Siveton a écrit :
Hi Hervé,
Is it a test requirement to use svn:mime-type?
They are text files in UTF-16, and are considered as binary by svn.
Or I don't know how to declare them as UTF-16 text.
Did you try to checkout and use them?
regards,
Hervé
Hi,
Code in svn is ready to be released.
I'm committer, not PMC member.
Any objection if I prepare the release using instructions on
http://maven.apache.org/developers/release/releasing.html and call for a
vote?
I know the discussion in august about this question:
Hi,
Following Maven release, I'd like to release Maven Ant Tasks 2.0.8.
We solved 17 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533styleName=Htmlversion=13618
The tasks can be downloaded from:
yes, it has a corresponding commit on trunk:
URL: http://svn.apache.org/viewvc?rev=601096view=rev
It's not the first time someone doesn't find one of my corresponding commits.
Do I do something wrong? or at least should I do something to have it more
easy to follow?
There is no issue
finally, I have to vote -1
I found that a bug was added when fixing MANTTASKS-91 that cause dependencies
order being wrong when read from a pom.xml file.
I have a test-case and fix. I'll commit them in the week and call for a new
vote
Regards,
Hervé
Le mardi 04 décembre 2007, Hervé BOUTEMY
Hi,
Following Maven release, I'd like to release (again) Maven Ant Tasks 2.0.8.
Problem with dependencies order has been fixed.
We solved 16 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533styleName=Htmlversion=13618
The tasks can be downloaded from:
I still miss 2 PMC votes: anybody interested in MANTTASKS?
This time, I promise I won't cancel the vote :)
Hervé
Le lundi 10 décembre 2007, Hervé BOUTEMY a écrit :
Hi,
Following Maven release, I'd like to release (again) Maven Ant Tasks 2.0.8.
Problem with dependencies order has been fixed
This vote passed with the following votes:
+1 (binding): Jason van Zyl, Brian E. Fox, Lukas Theussl
+1 (non-binding): Hervé Boutemy, Mauro Talevi, dndiaye
No other votes.
I will move the artifacts over to the ASF repository.
Regards,
Hervé
Le lundi 10 décembre 2007, Hervé BOUTEMY a écrit
The Maven team is pleased to announce the release of the Maven Ant Tasks,
version 2.0.8.
You can find the binaries here:
http://maven.apache.org/download.html
You can find the release notes here:
http://maven.apache.org/ant-tasks-release-notes.html
Enjoy,
-The Maven team
no, it is for p-u != 1.1 (the version in Maven 2.0.5- )
regards,
Hervé
Le vendredi 01 février 2008, Vincent Siveton a écrit :
I was thinking that prerequisites 2.0.6+ was for p-u 1.4.5, isn't?
Cheers,
Vincent
2008/1/31, Dennis Lundberg [EMAIL PROTECTED]:
The new plexus-utils version
+1
Le dimanche 2 mars 2008, Brett Porter a écrit :
Hi,
The Shade plugin is ready to be released. This is needed for the 2.0.9
release as well.
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540styleName=
Htmlversion=13994
The remaining issues in JIRA are
I fixed the test in r630474 (a conflict with wrong manifest in Surefire 2.4,
caused by maven-shade-plugin, which is fixed for the release currently being
voted on).
Now, I don't understand the comment in code:
MavenITmng1412DependenciesOrderTest.class ); -- MNG-1412 -- this is a
poorly
+1
Le samedi 8 mars 2008, Brian E. Fox a écrit :
It's time to release the next Javadoc plugin. Besides the fixes listed
below, the most important change is the reverting of javadoc acting as
an aggregator. This caused most users tons of grief during releases. The
issue for this is
+1
Le samedi 15 mars 2008, Arnaud HERITIER a écrit :
Hi,
We solved more than 50 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13593styleName=Ht
mlprojectId=11133 Important changes are :
- Add support for WTP 2.0
- Add support for MyEclipse
- Improve RAD6 support
-
AFAIK, the problem doesn't show for japanese nor chinese developers: even in
Japan or China, platform encoding on Unix or Windows is ASCII based,
precisely to avoid problems on simple ascii characters
like Benjamin says, the encoding issue is more subtle
There is one situation I know for this
I like the idea: easier to do than having access to a Z/OS box (anyone able to
deploy a CI on a Z/OS box?), even if every aspect is not covered (for example
it doesn't fail if encoding parameter has not been set in compiler plugin)
But if we do so on a whole CI server, I fear the havoc will be
I haven't had yet the time to setup some nice IT for this, but the fix is
here: MPLUGIN-101.
great!
There is one feature in this patch I don't like: you hardcoded a default
encoding to ISO-8859-1 instead of no default value (which means platform
encoding).
I understand that platform encoding
it should fail as soon as testitMNG3473 (the second test actually)
I copied the shell script used by Hudson to launch tests on my machine and
tried it: same problem as the CI server, the IT tests don't fail
I think I found the cause:
- I already have a MAVEN_OPTS environment variable
- Hudson
Le mercredi 26 mars 2008, Benjamin Bentmann a écrit :
What about just unifying the expressions that refer to encoding in
plugins?
As an intermediate solution until Maven 2.1 provides an extended POM, this
seems like a good approach.
+1
core plugins to be modified:
- compiler
- javadoc
-
that's it
thanks for the precise explanations
Le samedi 29 mars 2008, Stuart McCulloch a écrit :
On 29/03/2008, Hervé BOUTEMY [EMAIL PROTECTED] wrote:
it should fail as soon as testitMNG3473 (the second test actually)
I copied the shell script used by Hudson to launch tests on my machine
Le samedi 29 mars 2008, Benjamin Bentmann a écrit :
core plugins to be modified:
I moved this list over to the wiki article [0] in Confluence, think it's
easier to maintain there instead of being splattered through this mailing
thread.
great
I added a link in
Le samedi 29 mars 2008, Brian E. Fox a écrit :
Hi Herve, Yes those can be changed as I used the shell execution to try
and force the options. You should be able to edit directly with your
account.
-
To unsubscribe, e-mail:
Le samedi 29 mars 2008, Benjamin Bentmann a écrit :
The convention has to be shared between every plugin and the super POM. I
dislike the pure formal convention, that every plugin would copy/paste.
Coded as an API like String checkSourceEncoding(String encoding) method
to
AbstractMojo,
Hi,
Since the discussion on the list about Maven and encoding 2 weeks ago,
Benjamin and I worked on a proposal to have:
1. a central point of configuration of sources encoding, to be used by each
and every plugin,
2. a default value set to ISO-8859-1 (instead of platform encoding) to have
file encoding is not tied to a developer's environment: it's precisely
the contrary, it has to be configured in the project and the project only
(hence the problem with default value being platform encoding, which is
implicitely dependent on developer's environment)
Nico
2008/4/5, Hervé
Le lundi 07 avril 2008, Asgeir S. Nilsen a écrit :
2008/4/5, Hervé BOUTEMY [EMAIL PROTECTED]:
Hi,
Since the discussion on the list about Maven and encoding 2 weeks ago,
Benjamin and I worked on a proposal to have:
1. a central point of configuration of sources encoding, to be used
Le dimanche 06 avril 2008, Jason van Zyl a écrit :
I specifically meant the core changes, but I would still recommending
what Milos did which was to create branches for a few of the affected
plugins to try it all together.
ok, I created
+1
Hervé
Le lundi 07 avril 2008, Brian E. Fox a écrit :
Time to vote on the final Maven 2.0.9 Release. We went through 8 Release
Candidates and fixed all know regressions from 2.0.8 to 2.0.9 during
that time. Note that there were no source changes between RC8 and this
final build.
the encoding help with making this less
complicated. Something JChardet?
Sorry, something like JCharet:
http://jchardet.sourceforge.net/
On 7-Apr-08, at 2:31 PM, Hervé BOUTEMY wrote:
Le dimanche 06 avril 2008, Jason van Zyl a écrit :
I specifically meant the core changes, but I would
Le mardi 08 avril 2008, Martin von Gagern a écrit :
+1 for the original proposal, if a newcomer like me is allowed to vote.
The concept with the property, which can be set with the properties
until the model is updated, and which can be the default expression for
affected plugins, is simply
Le mercredi 09 avril 2008, Benjamin Bentmann a écrit :
I see your point. Worth another vote? Or should this switch be postponed
to 2.1, trading consistency in minor version upgrades for a longer time
for these Latin1 defaults to be established?
[...]
So while I agree that a change in
Le mercredi 09 avril 2008, Jason van Zyl a écrit :
All sounds fine. Just wanted you to think about the bigger picture in
mind.
Please do the work on a branch and go through the rigor of Brian's
example and make sure it works before you merge it into something we
would release to users. This
I created http://svn.apache.org/viewvc/maven/sandbox/branches/MNG-2216/
with javadoc and jxr plugins branches to test the change, and sample use
case.
no reaction: I suppose this is lazy consensus :)
I'll start to merge to plugins trunks tomorrow
regards
Hervé
/MAVENUSER/POM+Element+for+Source+File+Encoding
any objection?
Hervé
-Original Message-
From: Hervé BOUTEMY [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 12, 2008 10:06 AM
To: Maven Developers List
Subject: Re: [VOTE] POM Element for Source File Encoding
I created http
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533styleName=Htmlversion=13935
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11533status=1
Staging repo:
1 - 100 of 3647 matches
Mail list logo
