I like red wine, but who is paying? -:)
-
BR, tibor17
--
View this message in context:
http://maven.40175.n5.nabble.com/Re-ApacheCon-EU-2014-Budapest-tp5811661p5812094.html
Sent from the Maven Developers mailing list archive at Nabble.com.
Hi,
I'm just starting to look at toolchains, with the goal of using Java 5 for
jobs in latest Jenkins LTS version.
Here are a few reflections from what I've read so far.
Great to have a toolchains reference. It is in core site where it belongs.
It needs to be expanded with more explanations
The vote has passed with the following result:
+1 binding by
Kristian Roselvold,
Olivier Lamy,
Karl Heinz Marbaise,
Hervé Boutemy
+1 non-binding by
Mirko Friedenhagen,
Dan Tran
I will promote the artifact to Maven Central.
Kind regards
Karl Heinz Marbaise
On 1 Nov 2014, at 22:41, Dennis Lundberg wrote:
so that we can update it quickly when new plugins support it. The others
should just link to that page. The current info on supporting
For reference - my clojure-maven-plugin has supported it for ages now, and I
think I rolled that over onto my
Hi,
anyone giving me a binding vote cause i miss only one...
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi,
I get a rat failure when trying to build the project based on
jxr-2.5-source-release.zip:
Apache Licensed: 8
Generated Documents: 0
JavaDocs are generated and so license header is optional
Generated files do not required license headers
1 Unknown Licenses
Le samedi 1 novembre 2014 23:45:32 Mark Derricutt a écrit :
On 1 Nov 2014, at 22:41, Dennis Lundberg wrote:
so that we can update it quickly when new plugins support it. The others
should just link to that page. The current info on supporting
+1
this could be the mini guide, transforming
Hi Robert,
the file is added during the release process and is not in the
scmsounds like an addition to the exclude for the release...or a
change in RAT...
Kind regards
Karl Heinz Marbaise
On 11/1/14 2:39 PM, Robert Scholte wrote:
Hi,
I get a rat failure when trying to build the
Le samedi 1 novembre 2014 10:41:40 Dennis Lundberg a écrit :
The xsd used needs to be added
to the main Maven site in the xsd directory.
+1 didn't see it wasn't there
I just did it: http://maven.apache.org/xsd/
There are currently 3 wiki pages used or referenced. One Codehaus page [1]
that
Op Sun, 19 Oct 2014 20:19:07 +0200 schreef Karl Heinz Marbaise
khmarba...@gmx.de:
Hi,
On 10/19/14 7:25 PM, Robert Scholte wrote:
Maybe I found an explanation for the location.
Current 'global' isn't really global. It's bound to the Maven
installation. So for instance: whenever you upgrade
Hi Karl-Heinz,
I know it is added afterwards as part of the distribution-zip, but that's
also the official source (so it is not the tag as many would expect). Now
we have a distribution, which can't be build without adjusting the rat
plugin arguments.
So for me +0 since it is considered
this makes me have another idea:
why are toolchains configured in a specific toolchains.xml file instead as
settings.xml?
Regards,
Hervé
Le samedi 1 novembre 2014 15:53:16 Robert Scholte a écrit :
Op Sun, 19 Oct 2014 20:19:07 +0200 schreef Karl Heinz Marbaise
khmarba...@gmx.de:
Hi,
Very interesting suggestion.
And it shouldn't be a problem since the settings.xml is a Maven specific
file (unlike the pom.xml).
Robert
Op Sat, 01 Nov 2014 16:02:02 +0100 schreef Hervé BOUTEMY
herve.bout...@free.fr:
this makes me have another idea:
why are toolchains configured in a
Op Sat, 01 Nov 2014 14:56:56 +0100 schreef Hervé BOUTEMY
herve.bout...@free.fr:
Le samedi 1 novembre 2014 23:45:32 Mark Derricutt a écrit :
On 1 Nov 2014, at 22:41, Dennis Lundberg wrote:
so that we can update it quickly when new plugins support it. The
others
should just link to that
+1
26. Okt. 2014 23:16 skrev Karl Heinz Marbaise khmarba...@gmx.de
følgende:
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?
projectId=11085version=19853
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%
Hi Robert,
On 11/1/14 3:58 PM, Robert Scholte wrote:
Hi Karl-Heinz,
I know it is added afterwards as part of the distribution-zip, but
that's also the official source (so it is not the tag as many would
expect). Now we have a distribution, which can't be build without
adjusting the rat plugin
I will cancel this vote based on the problem with DEPENDENCIES file in
relationship with apache-rat-plugin which would result in a release
which couldn't be built without touching configuration which couldn't be
the right way...
Kind regards
Karl Heinz Marbaise
On 10/26/14 11:15 PM, Karl
Hi,
based on the canceled vote i would like to know what's the best solution
to solve the problem...
The short path solution is to add a exclude line to the
apache-rat-plugin...in my case of maven-jxr ...
but what about the other plugins etc. ? Don't they ran into the same
trap...?
WDYT
Hi Karl-Heinz,
my compliments for taking the responsibility as release manager to cancel
this vote, even when there were enough binding votes.
best,
Robert
Op Sat, 01 Nov 2014 16:41:05 +0100 schreef Karl Heinz Marbaise
khmarba...@gmx.de:
I will cancel this vote based on the problem with
Hi,
I think this should be fixed at the source and try to do the releases of
these parents asap.
Even though it is a minor change, every(!) project will hit this issue.
I'm not sure where files like LICENSE, README and NOTICE are ignored, but
I would expect that it should be the same
Hi,
I think a short time solution would be to add this exclude into
org.apache.maven:maven-parent:26-SNAPSHOT and release it as soon as
possible...
URL: https://svn.apache.org/repos/asf/maven/pom/trunk/maven
The long term solution would be to improve apache-rat-plugin accordingly:
I have
Looks like this source-zip can't be built due to the failing rat-check on
the generated DEPENDENCIES file as well.
I'm supposed to cancel the vote now, right? I would do a respin with an
exclusion for that file in the rat-config.
What about the other votes in progress?
2014-10-31 20:10
Hi Andreas,
I have canceled the vote for Maven JXR based on this problem...
Filed in an issue https://issues.apache.org/jira/browse/RAT-184
Kind regards
Karl Heinz Marbaise
On 11/1/14 7:05 PM, Andreas Gudian wrote:
Looks like this source-zip can't be built due to the failing rat-check on
Hello,
i can see advantage and disadvantage to having it in the settings file.
In my case I have multiple settings files for different repo and
security settings but only one toolchain describes the host
installed software.
One option would be to allow includes in the settings.xml, then you can
Vote cancelled, as the source-zip can't be built due to the failing
rat-check on the DEPENDENCIES file.
I'll start respinning the release and put up a new vote later tonight.
Andreas
2014-11-01 19:08 GMT+01:00 Karl Heinz Marbaise khmarba...@gmx.de:
Hi Andreas,
I have canceled the vote for
Hi,
am i not allowed to assign issue to me and solve them by a commit ?
Or did i miss a thing...
Or only allowed to PMC Chair ?
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For
Hi,
I've been working on the merger for Toolchains and my conclusion is that
we shouldn't add it to the settings.xml like it is specified right now.
Merging the settings.xml is quite easy: all complex types have a key,
which is used to merge.
The toolchain entries don't have such an
Hi,
We solved 31 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=20175
There are still lots of issues left in JIRA:
Is this something we could back port to 3.0.6?
On 1 November 2014 19:52, Robert Scholte rfscho...@apache.org wrote:
Hi,
I've been working on the merger for Toolchains and my conclusion is that
we shouldn't add it to the settings.xml like it is specified right now.
Merging the settings.xml
Personally I think the canceling of this vote is on the boundary of
absolute silliness. We have been releasing stuff with incorrect
license headers for years, and we are working to improve it. As long
as we are showing clear progress in the proper direction, I find this
process utterly wasteful.
Hmm, I would find it a bit embarrassing to release a source zip that I know
does not build without either deleting a file or skipping the rat-check,
which, as of only recently, is otherwise part of the build. That was not
the case for the previous releases... :-/
Am Sonntag, 2. November 2014
31 matches
Mail list logo
