this is one of the problems when using version ranges, tied to reproducibility
and definition of the algorithm for Maven to choose one version in the range
adapted to the actual context.
This is sometimes incorrectly (IMHO) told as "maven ranges with non-SNAPSHOT
bounds should not contain SNAPS
@requiresSession?
I can't find this annotation in plugin-tools's javadoc annotations
documentation [1]
And what part of plugin descriptor should it configure?
so I can tell you that if it is an undocumented feature as javadoc annotation,
it does not exist as Java 5 annotation: when working on it
Am 06/14/14 04:50, schrieb talios:
> Github user talios commented on the pull request:
>
> https://github.com/apache/maven/pull/21#issuecomment-46076519
>
> Interesting about the version range changes in aether there - whilst the
> [2.2.*] range is nice, that doesn't offer SNAPSHOT exc
+1 to recording for posterity.
8am next Wednesday is queuing time at Google IO :-)
On Sat, Jun 14, 2014 at 3:36 AM, Jason van Zyl wrote:
> Ok, here's the link for next Wednesday. We'll try it once and see how it
> goes, if people like it we'll keep going. It's setup so that it records so
> peop
Github user talios commented on the pull request:
https://github.com/apache/maven/pull/21#issuecomment-46076519
Interesting about the version range changes in aether there - whilst the
[2.2.*] range is nice, that doesn't offer SNAPSHOT exclusion - unless the
`VersionFilter` is being e
What does @requiresSession do (or did)?
--
Regards,
Igor
On 2014-06-13, 21:39, Benson Margulies wrote:
Is there one?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.ap
Is there one?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
GitHub user ChristianSchulte opened a pull request:
https://github.com/apache/maven-integration-testing/pull/7
[MNG-2199] Version ranges not supported for parent artifacts
Integration tests corresponding to Maven PR #21.
You can merge this pull request into a Git repository by runni
Le vendredi 13 juin 2014 10:51:35 Simon Wang a écrit :
> exactly.
>
> by that way, not only simplify pom.
> Also for one maven build, could identify project dependency hierarchy
> easier.
>
> base on that, could do further things:
> 1. to ensure whether could parallel build for module projects.
>
Github user asfgit closed the pull request at:
https://github.com/apache/maven-integration-testing/pull/5
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if th
Ok, here's the link for next Wednesday. We'll try it once and see how it goes,
if people like it we'll keep going. It's setup so that it records so people who
miss it can review it later if they like:
https://plus.google.com/u/0/events/cvbjktccvtp8cj9pru9u7r511fs
Thanks,
Jason
---
Ok, I'll setup a hangout for
http://www.timeanddate.com/worldclock/meetingdetails.html?year=2014&month=6&day=25&hour=15&min=0&sec=0&p1=224&p2=250&p3=136&p4=166
and we'll see how that works.
Concretely let's try and talk about the POM 5.0 model, and I might try and do a
little demo of the Maven
Is there any value in letting the 5.0.0 be like HTML in that new elements
may continuously introduced but older clients must allow "graceful
degradation"?
Cheers,
Paul
On Thu, Jun 12, 2014 at 9:51 PM, Simon Wang wrote:
> exactly.
>
> by that way, not only simplify pom.
> Also for one maven bu
13 matches
Mail list logo
