The toolchain.xsd schema seems to be unaccessible according to header and xsd
storage on maven-apache.
http://maven.apache.org/ref/3.1.1/maven-core/toolchains.html
http://maven.apache.org/xsd/
-
BR, tibor17
--
View this message in context:
http://maven.40175.n5.nabble.com/ANN-Apache-Maven-T
http://repository.apache.org/content/repositories/maven-1097/org/apache/maven/wagon/wagon/2.8/wagon-2.8-source-release.zip
sha1 signature: f1b6672581db8123960d1a47281f95d60a6c79f4
+1
Regards,
Hervé
Le mercredi 12 novembre 2014 14:34:14 Olivier Lamy a écrit :
> Hi,
>
> We fixed 2 issues:
> ht
+1
Regards,
Hervé
Le jeudi 13 novembre 2014 20:50:19 Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 1/4/1 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&ve
> rsion=12328739
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250&v
> er
The Maven team is pleased to announce the release of the Apache Maven
Toolchains Plugin, version 1.1
The Toolchains Plugins allows to share configuration across plugins. For
example to make sure the plugins like compiler, surefire, javadoc, webstart
etc. all use the same JDK for execution.
htt
Hi,
The vote has passed with the following result:
+1 (binding): Robert Scholte, Karl Heinz Marbaise, Hervé Boutemy
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
F
here is my +1
Regards,
Hervé
Le mardi 11 novembre 2014 23:26:45 Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 8 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12063&styleName=H
> tml&version=15920
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.o
Here's my +1 :-)
On Fri, Nov 14, 2014 at 10:16 PM, Mirko Friedenhagen
wrote:
> Hi,
>
> We solve 3 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11140&version=20557
>
> Bug
>
> * [MPMD-192] Regression MPMD-89 is showing up with Maven 2.2.1 again
> for maven-pmd-plugin-3.3
>
Hi,
We solve 3 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11140&version=20557
Bug
* [MPMD-192] Regression MPMD-89 is showing up with Maven 2.2.1 again
for maven-pmd-plugin-3.3
Improvement
* [MPMD-191] Update to PMD 5.2.1
* [MPMD-189] MavenProject/MavenSession Injecti
Hi,
We solved 21 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20750&styleName=&projectId=11126
This puts the 2.5.X range at an accumulated 73 bug fixes; this release
contains a few regressions from 2.5 and 2.5.1.
Most notable for this release are:
Rewritten duplicate handling
Very simple ;-)
Let's do it so.
Am 2014-11-14 um 19:50 schrieb Hervé BOUTEMY:
more stupid simple:
1. If paremeter is set, use that regardless of the rest
2. if not set, assume UTF-8
Regards,
Hervé
Le vendredi 14 novembre 2014 19:30:54 Michael Osipov a écrit :
Just to be clear, you are favo
more stupid simple:
1. If paremeter is set, use that regardless of the rest
2. if not set, assume UTF-8
Regards,
Hervé
Le vendredi 14 novembre 2014 19:30:54 Michael Osipov a écrit :
> Just to be clear, you are favoring:
>
> Alternative:
> 1. If paremeter is set, use that regardless of the rest
Just to be clear, you are favoring:
Alternative:
1. If paremeter is set, use that regardless of the rest
2. if not set, obtain the content type
3. Check whether is contains charset qualifier, yes use, use that
4. If not check whether this is an HTML file and pass to JSoup (do magic)
5. If nothing
I prefer the alternative
and if no parameter is set, just keep it stupid simple: assume UTF-8
IMHO, this will give good results and will be easy to explain
anything more complex is harder to maintain and to explain in case magic does
not do what was dreamt of
Regards,
Hervé
Le vendredi 14 nov
Am 2014-11-14 um 18:07 schrieb Hervé BOUTEMY:
[..]
The parameter won't help if there are several licenses with several
encodings used.
looks like the parameter can be either simple or complex: need a syntax
or just ignore: is it theory or reality?
Pure theory.
My approach would be this:
pr
Le vendredi 14 novembre 2014 17:58:44 Michael Osipov a écrit :
> Am 2014-11-14 um 17:47 schrieb Hervé BOUTEMY:
> > since it is the encoding of a downloaded license, it has nothing to do
> > with
> > encoding of project sources: using ${project.build.sourceEncoding} is IMHO
> > wrong algorithm (whic
Am 2014-11-14 um 17:47 schrieb Hervé BOUTEMY:
since it is the encoding of a downloaded license, it has nothing to do with
encoding of project sources: using ${project.build.sourceEncoding} is IMHO
wrong algorithm (which happen to give good results since a lot of people use
UTF-8)
then I'd go eit
since it is the encoding of a downloaded license, it has nothing to do with
encoding of project sources: using ${project.build.sourceEncoding} is IMHO
wrong algorithm (which happen to give good results since a lot of people use
UTF-8)
then I'd go either for a parameter for the goal, or JSoup th
no
some explanations:
- XML parser used by Maven is Xpp3 from plexus-utils [1]
- ${...} interpolation is done in model-builder with internal interpolator [2]
Regards,
Hervé
[1]
http://plexus.codehaus.org/plexus-utils/apidocs/org/codehaus/plexus/util/xml/pull/package-summary.html
[2] http://
I went through the JIRA in surefire project and prepared a list of issues
which can be either closed or apply the provided patches or easy to fix.
I have assigned other issues waiting for response from Reporter to close.
There is 150 open bugs and therefore we can improve the statistics by fixing
obligatory:
http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html
On 14 November 2014 14:50, Stephen Connolly wrote:
> You can use JDK 5 if you stop using the evil job type
>
> On 14 November 2014 14:45, Dennis Lundberg wrote:
>
>> Yes, that's the case. The curren
You can use JDK 5 if you stop using the evil job type
On 14 November 2014 14:45, Dennis Lundberg wrote:
> Yes, that's the case. The current Jenkins version used at the ASF can
> no longer use JDK5, unless we start using toolchains :-)
>
> We stumbled across that for the Apache Rat builds as well
Yes, that's the case. The current Jenkins version used at the ASF can
no longer use JDK5, unless we start using toolchains :-)
We stumbled across that for the Apache Rat builds as well, and changed
to JDK6 to make the builds pass. Using a conbination of animal-sniffer
and maven-enforcer makes a be
Is it possible to use EL in POM, something like this?
http://www.w3.org/TR/xexpr/#id-0042
-
BR, tibor17
--
View this message in context:
http://maven.40175.n5.nabble.com/Is-Expression-Language-Supported-in-Maven-POM-tp5814057.html
Sent from the Maven Developers mailing list archive at Nabb
Ok, I think it will be on Herve to grab people interested in being kidnapped :)
Currently it seems that there are some plans for wed 19th evening… anyone
interested can sync up with Herve or me over email.
Thanks,
~t~
On 5 Nov 2014 at 11:17:54 , Mark Struberg (strub...@yahoo.de) wrote:
Hiho!
Am 2014-11-14 um 04:02 schrieb Kristian Rosenvold:
Isn't this handled by the content-type headers normally ?
No, for two reasons:
1. The currect code does not inspect the content type
2. The server does send text/html but not the used encoding which is not
necessary because it is located with
25 matches
Mail list logo
