For this, there is already an enforcer rule available:
https://github.com/gary-rowe/BitcoinjEnforcerRules
Domi
On 24.03.2014, at 20:31, Martijn Dashorst wrote:
> On Mon, Mar 24, 2014 at 8:06 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>> I see the checksums then as being
If no one else minds I'll convert it all to single markdown document.
On Mar 24, 2014, at 7:50 PM, Olivier Lamy wrote:
> sounds good go for that
>
> On 25 March 2014 10:13, Jason van Zyl wrote:
>> Fat fingers. I meant to say a single curated set of release notes.
>>
>> On Mar 24, 2014, at 3:4
sounds good go for that
On 25 March 2014 10:13, Jason van Zyl wrote:
> Fat fingers. I meant to say a single curated set of release notes.
>
> On Mar 24, 2014, at 3:49 PM, Olivier Lamy wrote:
>
>> so need some work.
>> The release-notes-all.apt.vm expect to parse apt file but the 3.2.1
>> release
Le mardi 25 mars 2014 12:02:51 Olivier Lamy a écrit :
> On 21 March 2014 22:31, Hervé BOUTEMY wrote:
> > I'm not in phase with such analysis
> >
> > that's:
> > 1. something logic: if you have ${url} for a path, ${url}/sub-directory is
> > expected for the url to the sub-directory. Anything more
On 21 March 2014 22:31, Hervé BOUTEMY wrote:
> I'm not in phase with such analysis
>
> that's:
> 1. something logic: if you have ${url} for a path, ${url}/sub-directory is
> expected for the url to the sub-directory. Anything more complex should be
> avoided as much as possible. POM inheritance ac
ok, I'll have a look to try to move code
Regards,
Hervé
Le lundi 24 mars 2014 19:14:02 Robert Scholte a écrit :
> In fact, a ModelValidator validates both the rawModel and effectiveModel[1]
>
> regards,
> Robert
>
> [1]
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model
Fat fingers. I meant to say a single curated set of release notes.
On Mar 24, 2014, at 3:49 PM, Olivier Lamy wrote:
> so need some work.
> The release-notes-all.apt.vm expect to parse apt file but the 3.2.1
> release notes has been made using markdown.
> If someone has idea go for it (ATM I don'
How about moving to a single curating release notes file with the latest
version at the top. The aggregation of the release notes from all over the
place is a little funky. I would vote for removing the magic and just use a
single well-crafted file describing all the releases.
On Mar 24, 2014,
Hello,
it is not yet finished, and I am not sure if it actually would work for
most scenarios. But I was starting a plugin which allows to maintain
and create a "checksum lock file" for dependencies.
The basic idea is, that when I distribute a released maven project
(source) via for example Git,
so need some work.
The release-notes-all.apt.vm expect to parse apt file but the 3.2.1
release notes has been made using markdown.
If someone has idea go for it (ATM I don't have enough time for that).
Cheers
Olivier
On 25 March 2014 09:27, Olivier Lamy wrote:
> working on fixing that.
> As the
working on fixing that.
As the format has changed (apt -> md) the velocity script cannot see it.
On 25 March 2014 08:45, Andrew Holland wrote:
> Hi,
>
> Maven 3.2.1 release notes seem to be missing from
> http://maven.apache.org/release-notes-all.html
>
> Regards
>
> Andy
--
Olivier Lamy
Ecet
Hi,
Maven 3.2.1 release notes seem to be missing from
http://maven.apache.org/release-notes-all.html
Regards
Andy
+1
Best regards / Met vriendelijke groet,
Kees van Dieren
Squins IT Solutions BV
Oranjestraat 30
2983 HS Ridderkerk
The Netherlands
Mobile: +31 (0)6 30413841
www.squins.com
Chamber of commerce Rotterdam: 24435103
2014-03-22 22:52 GMT+01:00 Karl Heinz Marbaise :
> Hi,
>
> based on the decision
On Mon, Mar 24, 2014 at 8:06 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> I see the checksums then as being another potential side artifact... No
> need for modelVersion 5.0.0
>
I see it differently: the checksum validates the GAV coordinates. "I mean
'com.example.foo:foo:1.0'
Hi,
sorry i missed Robert Scholte +1 (binding)...
Kind regards
Karl-Heinz Marbaise
On 3/24/14 12:11 PM, Karl Heinz Marbaise wrote:
Hi,
the vote has passed with the following results:
+1 (binding):
Hervé Boutemy,
Olivier Lamy,
Kristian Rosenvold,
Stephen Connolly,
I see the checksums then as being another potential side artifact... No
need for modelVersion 5.0.0
A plugin right now could capture them and deploy to repo, and you could
have same plugin verify the resolved dependencies against the same file.
On Monday, 24 March 2014, Baptiste Mathus
>
wrote:
On Mon, Mar 24, 2014 at 7:29 PM, Robert Scholte wrote:
> I have to admit I have never used it, but aren't the -c / -C Maven
> commandline options meant for this?
>
Only if you trust the repository where you get the checksums from. The idea
advocated by Baptiste is that as a project owner you spec
I have to admit I have never used it, but aren't the -c / -C Maven
commandline options meant for this?
Robert
Op Mon, 24 Mar 2014 13:33:11 +0100 schreef Baptiste Mathus :
I guess if you manage to lose your repo, there could be either a special
switch to disable it, or maybe better, being abl
In fact, a ModelValidator validates both the rawModel and effectiveModel[1]
regards,
Robert
[1]
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model-builder/src/main/java/org/apache/maven/model/validation/ModelValidator.java;h=34bd97a5dc3d0a2d5f694d069ab80328d4adee1c;hb=HEA
I guess if you manage to lose your repo, there could be either a special
switch to disable it, or maybe better, being able to fix selectively those
exceptions in *your* pom like you currently do for versions of a
transitively retrieved artifact.
> Why
I'd say because you'd like to prevent some ki
2014-03-24 12:52 GMT+01:00 Gary Gregory :
> You'd need a checksum for jar, javadoc, sources and so on. Also what about
> md5 vs sha1?
>
Well. For javadoc and sources I don't see really the need, though granted
it might be half-baked to not be able to handle these if we realize we
actually need th
You'd need a checksum for jar, javadoc, sources and so on. Also what about md5
vs sha1?
Gary
Original message
From: Baptiste Mathus
Date:03/24/2014 06:19 (GMT-05:00)
To: Maven Developers List
Subject: Re: Model Version 5.0.0
Hi,
Sorry if it's the wrong thread, just le
Why? Sounds like just one more thing that could go wrong, plus if you lost
your repo and are rebuilding all from source because the timestamps will
differ, so the .zip checksums will differ too
On Monday, 24 March 2014, Baptiste Mathus wrote:
> Hi,
>
> Sorry if it's the wrong thread, just let me
Hi,
the vote has passed with the following results:
+1 (binding):
Hervé Boutemy,
Olivier Lamy,
Kristian Rosenvold,
Stephen Connolly,
Stephane Nicoll,
+1 (non binding):
Mirko Friedenhagen,
Jason van Zyl,
Toni Chemit,
Anders Hammar,
Dominik Bartho
Hi,
Sorry if it's the wrong thread, just let me know.
I thought I'd dump that thought I've had for some time here: was enriching
a bit the block already discussed?
So that one can somehow express a tag. I'm posting this here
since this would also require a pom upgrade.
I've re-read the recent
Hi again Robert,
I checked in the odd-even module in r1580793 - every
feedback/suggestion/... is, as usual, much more than welcome and
appreciated :)
All the best!
-Simo
http://people.apache.org/~simonetripodi/
http://twitter.com/simonetripodi
On Sat, Mar 22, 2014 at 1:10 PM, Robert Scholte wr
Hello,
I want to generate a JIRA report using Changes Plugin. I've managed to
re-produce a situation which is contradictory:
1. I use Maven and POM to generate the JIRA report.
2. I checkout 2.9 source and use a JUnit test class to verify.
In case (1), the following Maven configuration is
Hello Robert,
thanks a lot for your help, much more than appreciated!
>
> I've added the projectVersionPolicyId to the releaseDescriptor. We might
> need to add dependencyVersionPolicyId, parentVersionPolicyId and
> pluginVersionPolicyId in the future as well.
> So the manager is ready to switch
The Maven team is pleased to announce the release of the Apache Maven
Jarsigner,
version 1.3.2
This component provides some utilities to sign/verify jars/files in your Mojos.
http://maven.apache.org/shared/maven-jarsigner/
To use the Maven Jarsigner, add the following dependency to your proje
The Apache Maven team is pleased to announce the release of the
maven-shared-utils, version 0.6
This project aims to be a functional replacement for
{{{http://plexus.codehaus.org/plexus-utils}plexus-utils}} in Maven.
It is not a 100% API compatible replacement though but a replacement
:
lots of
The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.3.2.
This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:
http://maven.apache.org/plugins/maven-jarsigner-plugin/
This plugin is meant
31 matches
Mail list logo
