Re: Issues to be reviewed for 3.x
Am 2014-07-01 18:21, schrieb Paul Benedict: I was just about to bulk change these and but could not find the Send Email for this Update checkbox. Based on what I read, it's an option only available to project admins. So... either someone with more karma can do this change or we just accept 200 email updates :-) I don't like the latter. Thoughts? I'd do it anyway! On Tue, Jul 1, 2014 at 3:28 AM, Michael-O 1983-01...@gmx.net wrote: Hi Paul, There are about 295 closed issues in Issues to be reviews for 3.x, presumably all closed due to the massive issue cleanup. I can do a query to find out for sure. For the ones I can verify, does anyone care if I remove the version from these tickets? They aren't being released and that's our policy now -- not to set the Fix Version for issues that are incomplete/invalid. this is a very good idea. I have done that already for all pre-3.3.2 versions which aren't going to come. I think, we strictly follow that no-fix-version-for-incomplete/invalid/wontfix. If you are able to assign to real versions that's great. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [MJAVADOC-398] pull request
Am 2014-07-01 12:59, schrieb Michal Srb: Hello, I filed a bug [1] and opened pull request [2] for maven-javadoc-plugin. Please see links below for context. The real problem seems to be in javadoc tool, but it can be avoided by not putting compiled project classes on javadoc's -classpath. The question is: can such change break something? All comments and suggestions are appreciated. Thanks Michal [1]: http://jira.codehaus.org/browse/MJAVADOC-398 [2]: https://github.com/apache/maven-plugins/pull/25 For what it's worth, I have asked Michal to do so because this is a change in behavior. If no one opposes, I will perform the merge. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [MJAVADOC-398] pull request
On 2 Jul 2014, at 07:18, Michael Osipov micha...@apache.org wrote: Am 2014-07-01 12:59, schrieb Michal Srb: Hello, I filed a bug [1] and opened pull request [2] for maven-javadoc-plugin. Please see links below for context. The real problem seems to be in javadoc tool, but it can be avoided by not putting compiled project classes on javadoc's -classpath. The question is: can such change break something? All comments and suggestions are appreciated. Thanks Michal [1]: http://jira.codehaus.org/browse/MJAVADOC-398 [2]: https://github.com/apache/maven-plugins/pull/25 For what it's worth, I have asked Michal to do so because this is a change in behavior. If no one opposes, I will perform the merge. Only thing I can think of are situations where the output directory contains code that has no equivalent in the source directory - not adding the output directory would then make a difference to javadoc. No idea if this is actually an issue in real-life, but IMHO it would be safer to add a new configuration option to control whether the output directories are passed to javadoc or not (and then default it to add). That way Michal can solve his particular use-case without changing the current behaviour (or if you chose to default it to not add then people who are affected by this change could still get the original behaviour). ( there may also be custom doclets that use class files for additional analysis? ) Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Issues to be reviewed for 3.x
Thanks for cleaning that up. Any help is welcomed. After the cleanup and a couple releases the issue count is still hovering around 200 even after closing another 30 issues. On Jul 2, 2014, at 2:15 AM, Michael Osipov micha...@apache.org wrote: Am 2014-07-01 18:21, schrieb Paul Benedict: I was just about to bulk change these and but could not find the Send Email for this Update checkbox. Based on what I read, it's an option only available to project admins. So... either someone with more karma can do this change or we just accept 200 email updates :-) I don't like the latter. Thoughts? I'd do it anyway! On Tue, Jul 1, 2014 at 3:28 AM, Michael-O 1983-01...@gmx.net wrote: Hi Paul, There are about 295 closed issues in Issues to be reviews for 3.x, presumably all closed due to the massive issue cleanup. I can do a query to find out for sure. For the ones I can verify, does anyone care if I remove the version from these tickets? They aren't being released and that's our policy now -- not to set the Fix Version for issues that are incomplete/invalid. this is a very good idea. I have done that already for all pre-3.3.2 versions which aren't going to come. I think, we strictly follow that no-fix-version-for-incomplete/invalid/wontfix. If you are able to assign to real versions that's great. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Selfish deeds are the shortest path to self destruction. -- The Seven Samuari, Akira Kurosawa
Re: Issues to be reviewed for 3.x
Okay guys. It's done. Our issue list is much cleaner. Almost 300 issues were removed. This gives what is left for 3.x a much clearer perspective. Cheers, Paul On Wed, Jul 2, 2014 at 7:35 AM, Jason van Zyl ja...@takari.io wrote: Thanks for cleaning that up. Any help is welcomed. After the cleanup and a couple releases the issue count is still hovering around 200 even after closing another 30 issues. On Jul 2, 2014, at 2:15 AM, Michael Osipov micha...@apache.org wrote: Am 2014-07-01 18:21, schrieb Paul Benedict: I was just about to bulk change these and but could not find the Send Email for this Update checkbox. Based on what I read, it's an option only available to project admins. So... either someone with more karma can do this change or we just accept 200 email updates :-) I don't like the latter. Thoughts? I'd do it anyway! On Tue, Jul 1, 2014 at 3:28 AM, Michael-O 1983-01...@gmx.net wrote: Hi Paul, There are about 295 closed issues in Issues to be reviews for 3.x, presumably all closed due to the massive issue cleanup. I can do a query to find out for sure. For the ones I can verify, does anyone care if I remove the version from these tickets? They aren't being released and that's our policy now -- not to set the Fix Version for issues that are incomplete/invalid. this is a very good idea. I have done that already for all pre-3.3.2 versions which aren't going to come. I think, we strictly follow that no-fix-version-for-incomplete/invalid/wontfix. If you are able to assign to real versions that's great. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Selfish deeds are the shortest path to self destruction. -- The Seven Samuari, Akira Kurosawa
Re: Resolving the dependencies for an Artifact
Thanks Dan.
I didn't appreciate at first the impact of setResolveTransitively(true).
NB I needed to change request.setResolveRoot(false) to exclude the provided
artifact.
William
On Fri, Jun 20, 2014 at 11:44 AM, Daniel Kulp dk...@apache.org wrote:
On Jun 19, 2014, at 6:36 PM, William Ferguson
william.fergu...@xandar.com.au wrote:
Hi Dan,
if the ArtifactResolutionResult contains the deps for the Artifact in the
request then that's exactly what I want. However I can't see that it
does.
What am I missing?
ArtifactResolutionResult.getArtifacts() is a list of all the artifacts
that it resolved.
NB the resolution also needs to be able to resolve Artifacts in the
reactor. I'm pretty certain that
@Component
private org.apache.maven.repository.RepositorySystem repository;
is only going to resolve from the local repo, not the reactor, right?
This I don’t know. I haven’t tried to have it resolve anything in the
reactor.
Dan
William
On Fri, Jun 20, 2014 at 4:58 AM, Daniel Kulp dk...@apache.org wrote:
For Aries, I ended up doing:
@Component
private org.apache.maven.repository.RepositorySystem repository;
private File resolve(String artifactDescriptor) {
String[] s = artifactDescriptor.split(:);
String type = (s.length = 4 ? s[3] : jar);
Artifact artifact = repository.createArtifact(s[0], s[1], s[2],
type);
ArtifactResolutionRequest request = new
ArtifactResolutionRequest();
request.setArtifact(artifact);
request.setResolveRoot(true).setResolveTransitively(false);
request.setServers( session.getRequest().getServers() );
request.setMirrors( session.getRequest().getMirrors() );
request.setProxies( session.getRequest().getProxies() );
request.setLocalRepository(session.getLocalRepository());
request.setRemoteRepositories(session.getRequest().getRemoteRepositories());
repository.resolve(request);
return artifact.getFile();
}
If you set “setResolveTransitively(true)” then the
ArtifactResolutionResponse would have all the deps available in it.
That seems to work for both Maven 3.0 and 3.1/3.2.
Dan
Op Thu, 19 Jun 2014 00:01:52 +0200 schreef William Ferguson
william.fergu...@xandar.com.au:
I asked on maven-users but didn't get any viable responses. So I'm
hoping
someone here can help.
--
I have a Mojo that needs to work with Maven 3.0.* and 3.1+
In the Mojo I have an Artifact and I need to resolve it's dependencies.
How
can/should I do it?
If I can resolve the Artifact to a MavenProject then I can use
DependencyGraphBuilder (from maven-dependency-tree) to construct a
graph
of
the deps. But I'm struggling to make the Artifact to MavenProject
conversion happen.
I thought that If I could get a URL to the Artifact's POM file then I
could
use DefaultMavenRuntime (maven-runtime) to resolve the URL into a
MavenProject. But
1. I can't work out how to get a URL to the artifact's POM file (it
needs to handle both reactor artifacts and repo artifacts)
2. Even with a URL to the POM file, MavenRuntime#getProject) is
returning null.
Can someone please point me in the right direction?
Am I even on the right path or is there a much more straight forward
way
of
getting the dependencies for the Artifact?
--
William
--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Re: Re: Issues to be reviewed for 3.x
Okay guys. It's done. Our issue list is much cleaner. Almost 300 issues were removed. This gives what is left for 3.x a much clearer perspective. Hi Paul, looks way better now. Some thing though, most of alread fixed issue can be bound to a distinct Maven version. Do you want to change them? E.g., MNG-4226. Michael On Wed, Jul 2, 2014 at 7:35 AM, Jason van Zyl ja...@takari.io wrote: Thanks for cleaning that up. Any help is welcomed. After the cleanup and a couple releases the issue count is still hovering around 200 even after closing another 30 issues. On Jul 2, 2014, at 2:15 AM, Michael Osipov micha...@apache.org wrote: Am 2014-07-01 18:21, schrieb Paul Benedict: I was just about to bulk change these and but could not find the Send Email for this Update checkbox. Based on what I read, it's an option only available to project admins. So... either someone with more karma can do this change or we just accept 200 email updates :-) I don't like the latter. Thoughts? I'd do it anyway! On Tue, Jul 1, 2014 at 3:28 AM, Michael-O 1983-01...@gmx.net wrote: Hi Paul, There are about 295 closed issues in Issues to be reviews for 3.x, presumably all closed due to the massive issue cleanup. I can do a query to find out for sure. For the ones I can verify, does anyone care if I remove the version from these tickets? They aren't being released and that's our policy now -- not to set the Fix Version for issues that are incomplete/invalid. this is a very good idea. I have done that already for all pre-3.3.2 versions which aren't going to come. I think, we strictly follow that no-fix-version-for-incomplete/invalid/wontfix. If you are able to assign to real versions that's great. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Selfish deeds are the shortest path to self destruction. -- The Seven Samuari, Akira Kurosawa - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven Developer Hangout
The hangout is the same time as last week: https://plus.google.com/u/0/events/c5dc2fimb4mau0anec7i1nde500 I figure we'll just always schedule it even if few or no one shows up. Just a standing meeting to discuss anything. Robert, maybe you would like to talk about your lifecycle proposal? We can also discuss anything else, the floor is open. With holidays in Canada this week I haven't finished writing up the POM Evolved proposal. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
Re: Re: Issues to be reviewed for 3.x
I noticed that too. There are fixed issues hanging around in that JIRA version but I don't know which version they were officially fixed in. It will require an archelogical dig. I don't have the time to sort that out but if you can figure it out and mail the list, I'll update the tickets. Cheers, Paul On Wed, Jul 2, 2014 at 9:10 AM, Michael-O 1983-01...@gmx.net wrote: Okay guys. It's done. Our issue list is much cleaner. Almost 300 issues were removed. This gives what is left for 3.x a much clearer perspective. Hi Paul, looks way better now. Some thing though, most of alread fixed issue can be bound to a distinct Maven version. Do you want to change them? E.g., MNG-4226. Michael On Wed, Jul 2, 2014 at 7:35 AM, Jason van Zyl ja...@takari.io wrote: Thanks for cleaning that up. Any help is welcomed. After the cleanup and a couple releases the issue count is still hovering around 200 even after closing another 30 issues. On Jul 2, 2014, at 2:15 AM, Michael Osipov micha...@apache.org wrote: Am 2014-07-01 18:21, schrieb Paul Benedict: I was just about to bulk change these and but could not find the Send Email for this Update checkbox. Based on what I read, it's an option only available to project admins. So... either someone with more karma can do this change or we just accept 200 email updates :-) I don't like the latter. Thoughts? I'd do it anyway! On Tue, Jul 1, 2014 at 3:28 AM, Michael-O 1983-01...@gmx.net wrote: Hi Paul, There are about 295 closed issues in Issues to be reviews for 3.x, presumably all closed due to the massive issue cleanup. I can do a query to find out for sure. For the ones I can verify, does anyone care if I remove the version from these tickets? They aren't being released and that's our policy now -- not to set the Fix Version for issues that are incomplete/invalid. this is a very good idea. I have done that already for all pre-3.3.2 versions which aren't going to come. I think, we strictly follow that no-fix-version-for-incomplete/invalid/wontfix. If you are able to assign to real versions that's great. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Selfish deeds are the shortest path to self destruction. -- The Seven Samuari, Akira Kurosawa - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Fwd: Project Jigsaw: Phase Two
Forwarding this to the team. Perhaps or perhaps not this will help the Maven 4.0 discussion. IIRC, Jason is interested in polishing how Maven perceives artifacts at compile time vs runtime, which Oracle seems to also want to address through Java. Cheers, Paul -- Forwarded message -- From: mark.reinh...@oracle.com Date: Wed, Jul 2, 2014 at 11:47 AM Subject: Project Jigsaw: Phase Two To: jigsaw-...@openjdk.java.net Project Jigsaw has, for the last several years, been in an exploratory phase in which we've designed and prototyped one particular approach [1] to addressing a draft set of requirements [2]. It's now time to switch gears and focus on creating a production-quality design and implementation suitable for JDK 9 and thence Java SE 9, as previously proposed [3]. To begin this phase I've drafted a new document to collect goals and requirements [4]. It reflects a new emphasis on security, as motivated by recent experience [5], it takes into account lessons learned from the prototype, and it's written at a broader and more abstract level than the previous document [2] so as not to over-constrain the solution space. This document will be one of the starting points of the upcoming Java Platform Module System JSR. Please send comments and suggestions on the new goals and requirements document [4] to this list, jigsaw-...@openjdk.java.net. Jigsaw as a whole will bring enormous changes to the JDK; it would be unwise to wait until it's completely finished before merging any of it. Our intent, therefore, is to proceed in large steps, each of which will have a corresponding JEP. The first three JEPs, which I'll also post here for review, will propose a specific modular structure for the JDK, reorganize the JDK source code (but not binaries) along those lines, and then later modularize the binary images. A fourth JEP will introduce the module system itself, which will be aligned with the module-system JSR. It may seem odd that the module system JEP comes last, but the earlier JEPs need make only minimal assumptions about its capabilities, hence work on them can proceed in parallel with work on the module-system JEP and JSR. - Mark [1] http://cr.openjdk.java.net/~mr/jigsaw/notes/jigsaw-big-picture-01 [2] http://openjdk.java.net/projects/jigsaw/doc/draft-java-module-system-requirements-12 [3] http://mreinhold.org/blog/on-the-next-train [4] http://openjdk.java.net/projects/jigsaw/goals-reqs/03 [5] http://mreinhold.org/blog/secure-the-train
Re: Maven Developer Hangout
Sure, I can fill some time with my proposal.[1] Another thing that comes to my mind is Stephens proposal on supplies concept[2] And an interesting talk would be about the proposal Removing ability for plugins to dynamically inject dependencies[3]. For most cases I can think of a solution, however what to do with pom-less goals dependency:get? This is probably more than enough for tomorrow. Robert [1] http://markmail.org/message/cmia5vylzh2lzp3t [2] http://markmail.org/message/sx4slb2dwbvth7u6 [3] http://markmail.org/message/7f55pruyc6pt2hlw Op Wed, 02 Jul 2014 16:34:46 +0200 schreef Jason van Zyl ja...@takari.io: The hangout is the same time as last week: https://plus.google.com/u/0/events/c5dc2fimb4mau0anec7i1nde500 I figure we'll just always schedule it even if few or no one shows up. Just a standing meeting to discuss anything. Robert, maybe you would like to talk about your lifecycle proposal? We can also discuss anything else, the floor is open. With holidays in Canada this week I haven't finished writing up the POM Evolved proposal. Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Re: Re: Issues to be reviewed for 3.x
All updated as good as possible. Gesendet: Mittwoch, 02. Juli 2014 um 16:36 Uhr Von: Paul Benedict pbened...@apache.org An: Maven Developers List dev@maven.apache.org Betreff: Re: Re: Issues to be reviewed for 3.x I noticed that too. There are fixed issues hanging around in that JIRA version but I don't know which version they were officially fixed in. It will require an archelogical dig. I don't have the time to sort that out but if you can figure it out and mail the list, I'll update the tickets. Cheers, Paul On Wed, Jul 2, 2014 at 9:10 AM, Michael-O 1983-01...@gmx.net wrote: Okay guys. It's done. Our issue list is much cleaner. Almost 300 issues were removed. This gives what is left for 3.x a much clearer perspective. Hi Paul, looks way better now. Some thing though, most of alread fixed issue can be bound to a distinct Maven version. Do you want to change them? E.g., MNG-4226. Michael On Wed, Jul 2, 2014 at 7:35 AM, Jason van Zyl ja...@takari.io wrote: Thanks for cleaning that up. Any help is welcomed. After the cleanup and a couple releases the issue count is still hovering around 200 even after closing another 30 issues. On Jul 2, 2014, at 2:15 AM, Michael Osipov micha...@apache.org wrote: Am 2014-07-01 18:21, schrieb Paul Benedict: I was just about to bulk change these and but could not find the Send Email for this Update checkbox. Based on what I read, it's an option only available to project admins. So... either someone with more karma can do this change or we just accept 200 email updates :-) I don't like the latter. Thoughts? I'd do it anyway! On Tue, Jul 1, 2014 at 3:28 AM, Michael-O 1983-01...@gmx.net wrote: Hi Paul, There are about 295 closed issues in Issues to be reviews for 3.x, presumably all closed due to the massive issue cleanup. I can do a query to find out for sure. For the ones I can verify, does anyone care if I remove the version from these tickets? They aren't being released and that's our policy now -- not to set the Fix Version for issues that are incomplete/invalid. this is a very good idea. I have done that already for all pre-3.3.2 versions which aren't going to come. I think, we strictly follow that no-fix-version-for-incomplete/invalid/wontfix. If you are able to assign to real versions that's great. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Selfish deeds are the shortest path to self destruction. -- The Seven Samuari, Akira Kurosawa - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Issues to be reviewed for 3.x
Cool, thanks. On Jul 2, 2014, at 3:45 PM, Michael-O 1983-01...@gmx.net wrote: All updated as good as possible. Gesendet: Mittwoch, 02. Juli 2014 um 16:36 Uhr Von: Paul Benedict pbened...@apache.org An: Maven Developers List dev@maven.apache.org Betreff: Re: Re: Issues to be reviewed for 3.x I noticed that too. There are fixed issues hanging around in that JIRA version but I don't know which version they were officially fixed in. It will require an archelogical dig. I don't have the time to sort that out but if you can figure it out and mail the list, I'll update the tickets. Cheers, Paul On Wed, Jul 2, 2014 at 9:10 AM, Michael-O 1983-01...@gmx.net wrote: Okay guys. It's done. Our issue list is much cleaner. Almost 300 issues were removed. This gives what is left for 3.x a much clearer perspective. Hi Paul, looks way better now. Some thing though, most of alread fixed issue can be bound to a distinct Maven version. Do you want to change them? E.g., MNG-4226. Michael On Wed, Jul 2, 2014 at 7:35 AM, Jason van Zyl ja...@takari.io wrote: Thanks for cleaning that up. Any help is welcomed. After the cleanup and a couple releases the issue count is still hovering around 200 even after closing another 30 issues. On Jul 2, 2014, at 2:15 AM, Michael Osipov micha...@apache.org wrote: Am 2014-07-01 18:21, schrieb Paul Benedict: I was just about to bulk change these and but could not find the Send Email for this Update checkbox. Based on what I read, it's an option only available to project admins. So... either someone with more karma can do this change or we just accept 200 email updates :-) I don't like the latter. Thoughts? I'd do it anyway! On Tue, Jul 1, 2014 at 3:28 AM, Michael-O 1983-01...@gmx.net wrote: Hi Paul, There are about 295 closed issues in Issues to be reviews for 3.x, presumably all closed due to the massive issue cleanup. I can do a query to find out for sure. For the ones I can verify, does anyone care if I remove the version from these tickets? They aren't being released and that's our policy now -- not to set the Fix Version for issues that are incomplete/invalid. this is a very good idea. I have done that already for all pre-3.3.2 versions which aren't going to come. I think, we strictly follow that no-fix-version-for-incomplete/invalid/wontfix. If you are able to assign to real versions that's great. Michael - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Selfish deeds are the shortest path to self destruction. -- The Seven Samuari, Akira Kurosawa - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - Our achievements speak for themselves. What we have to keep track of are our failures, discouragements and doubts. We tend to forget the past difficulties, the many false starts, and the painful groping. We see our past achievements as the end result of a clean forward thrust, and our present difficulties as signs of decline and decay. -- Eric Hoffer, Reflections on the Human Condition
maven-plugin-testing-harness and maven 3.2.x
SessionScope and MojoExecutionScope introduced in maven 3.2.1 require explicit support from maven-plugin-testing-harness. Unfortunately, there is no clean/straightforward way to introduce such support and still be able to use maven-plugin-testing-harness with earlier versions of maven. What people think if I bump maven-plugin-testing-harness version to 3.2.0 and make it work with maven 3.2.1 or newer? -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: maven-plugin-testing-harness and maven 3.2.x
Sounds reasonable. On Jul 2, 2014, at 4:04 PM, Igor Fedorenko i...@ifedorenko.com wrote: SessionScope and MojoExecutionScope introduced in maven 3.2.1 require explicit support from maven-plugin-testing-harness. Unfortunately, there is no clean/straightforward way to introduce such support and still be able to use maven-plugin-testing-harness with earlier versions of maven. What people think if I bump maven-plugin-testing-harness version to 3.2.0 and make it work with maven 3.2.1 or newer? -- Regards, Igor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt
Project Jigsaw - Phase 2
Mark Rheinhold just posted about Phase 2 of Project Jigsaw: http://mreinhold.org/blog/jigsaw-phase-two and the draft doc: http://openjdk.java.net/projects/jigsaw/goals-reqs/03 Some really good ideas in here, something to think about with Maven going forward maybe. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven Developer Hangout
On 3 Jul 2014, at 6:25, Robert Scholte wrote: This is probably more than enough for tomorrow. A discussion on a merits and flaws of repositories (when combined with mirrors) is also warranted after some previous discussion on the list. Mark - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
