[GitHub] maven-surefire issue #110: SUREFIRE-1216: TEST-*.xml files generated by Sure...

Github user stdweird commented on the issue: https://github.com/apache/maven-surefire/pull/110 is there any ETA for a release with this fix? or should i try to patch the local `.m2` cache? --- If your project is set up for it, you can reply to this email and have your reply appear on

Re: [DISCUSSION] finishing Aether import: help find a new name

Hi, I know Aether is one of the catchy non telling name. But, why not leave Aether with new Maven namespace like org.apache.maven.aether? -- barthel - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional comm

Re: [DISCUSSION] finishing Aether import: help find a new name

On Thu, Aug 4, 2016 at 3:24 PM, Christian Schulte wrote: > Am 08/05/16 um 00:15 schrieb Gary Gregory: > > But here you would just tell the manager: "I want to use Maven" as > opposed > > to "I want to use Ant and Ivy". > > So lets rename Maven. We need a name sounding cool to management. Just > s

Re: [DISCUSSION] finishing Aether import: help find a new name

Am 08/05/16 um 00:15 schrieb Gary Gregory: > But here you would just tell the manager: "I want to use Maven" as opposed > to "I want to use Ant and Ivy". So lets rename Maven. We need a name sounding cool to management. Just so that we do not need to discuss why we want to use it...something imply

Re: [DISCUSSION] finishing Aether import: help find a new name

On Thu, Aug 4, 2016 at 2:53 PM, Christian Schulte wrote: > Am 08/04/16 um 23:08 schrieb Jason van Zyl: > > When in doubt I have tried Velocity, Turbine, Plexus, Nexus, Aether and > Tycho. None of them very useful for people to understand what they actually > do. I think I’m done with catchy names

Re: [DISCUSSION] finishing Aether import: help find a new name

Am 08/04/16 um 23:08 schrieb Jason van Zyl: > When in doubt I have tried Velocity, Turbine, Plexus, Nexus, Aether and > Tycho. None of them very useful for people to understand what they actually > do. I think I’m done with catchy names. I’m old. There is one quote I can make here. Working on a

Re: PR Inquiry

Hi, Please have a look at answers from Robert and myself on https://issues.apache.org/jira/browse/MDEP-519 (for the second PR) Regards, Hervé - Mail original - De: "Rajiv Jain" À: "Maven Developers List" Envoyé: Jeudi 4 Août 2016 22:45:40 Objet: PR Inquiry Hi I opened 2 pull reques

Re: [DISCUSSION] finishing Aether import: help find a new name

When in doubt I have tried Velocity, Turbine, Plexus, Nexus, Aether and Tycho. None of them very useful for people to understand what they actually do. I think I’m done with catchy names. I’m old. > On Aug 4, 2016, at 4:33 PM, Christian Schulte wrote: > > Am 08/04/16 um 22:22 schrieb Jason van

Re: [DISCUSSION] finishing Aether import: help find a new name

if I let apart the confusion with java jars... it's not a specification: the specification of the repository is in maven-aether-provider dependencies Regards, Hervé - Mail original - De: "Christian Schulte" À: "Maven Developers List" Envoyé: Jeudi 4 Août 2016 01:29:17 Objet: Re: [DIS

Re: [DISCUSSION] finishing Aether import: help find a new name

sorry, I find it somewhat abstract: it does not tell anything about the interactions Even if I agree that resolver does not tell everything, just the majority and most complex Regards, Hervé (sorry, on holidays with unusual email access: tracking such thread is not easy...) - Mail origi

Re: [DISCUSSION] finishing Aether import: help find a new name

the whole functionality of the lib is visible in one interface: RepositorySystem http://maven.apache.org/aether-archives/aether-LATEST/apidocs/org/eclipse/aether/RepositorySystem.html in this interface, 6 methods are about resolution + 1 about collection (a special "sort of" resolution) + 1 to re

PR Inquiry

Hi I opened 2 pull requests and wanted to chase up whether somebody can look over it? I believe that it can be merged in. My company is dependent on some changes. I have made some changes that I think will make the fix. The pull requests are https://github.com/apache/maven/pull/88

Re: Building Apache Maven

Hi I wanted to chase up whether anybody can reply to the below e-mail? Basically, I would like to produce a fresh build and test my changes on my fresh build. I am using mvn - DdistributionTargetFolder=/Users/rajivpjs/tools/maven-test/apache-maven-3.4.0-SNAPSHOT clean package From this I use

Re: [DISCUSSION] finishing Aether import: help find a new name

Am 08/04/16 um 22:22 schrieb Jason van Zyl: > These are all discussions about abstractions we had when talking about Maven > 1.x, so let me save you the circuitous route back to the fact that users > don’t care about having an abstraction that lets them store artifacts as > blobs in any potentia

Re: [DISCUSSION] finishing Aether import: help find a new name

These are all discussions about abstractions we had when talking about Maven 1.x, so let me save you the circuitous route back to the fact that users don’t care about having an abstraction that lets them store artifacts as blobs in any potential systems coming from any potential source. People t

Re: [DISCUSSION] finishing Aether import: help find a new name

We have this body of code. People in the world use it. Refactoring this code to break its existing users, just to avoid an awkward name, strike me as a poor use of time. My suggestion remains that we pick some inoffensive descriptive string and use it.

Re: [DISCUSSION] finishing Aether import: help find a new name

If I wanted to store my artifacts in a database instead of putting files into some well-known locations. Can I write an implementation of 'RepositorySystem' which allows me to do that? No. It's way too file-system based. A database would give me a blob. A path or a filename is meaningless for the w

Re: [DISCUSSION] finishing Aether import: help find a new name

Am 08/04/16 um 18:27 schrieb Robert Scholte: > It is all about Maven coordinates: groupId + artifactId + version + > extension ( + classifier) > This all together results in a URL to a repository. In case of remote > repositories these work both with M1 and M2 repository layouts (yes, the > n

Re: [DISCUSSION] finishing Aether import: help find a new name

Am 08/04/16 um 18:44 schrieb Paul Benedict: > In my own experience regarding the difficulty of naming something, it has > always indicated the codebase is too big and multi-functional. > > Thus, there are two paths to take: > 1) Slap a brand name on it because no descriptive name can succinctly >

Re: [1/2] maven-scm git commit: [SCM-824] Upgrade of 'plexus-utils' to 3.0.23.

Hi, Thank you for releasing a new version of maven-scm. I have incorporated this new version in the Jenkins SCM Sync Configuration plugin and it has helped. -- Craig On Fri, Jul 1, 2016 at 4:26 AM, Karl Heinz Marbaise w

Re: Maven Web Site

For info I've deployed this patch on the site of my project : https://dev.lutece.paris.fr/plugins/lutece-core/ Le 20 juil. 2016 16:12, "Jon Harper" a écrit : Hi Karl, I made a JIRA: https://issues.apache.org/jira/browse/MSKINS-131 Cheers, Jon Jon On Thu, Jul 7, 2016 at 10:14 PM, Karl Heinz Mar

Re: [DISCUSSION] finishing Aether import: help find a new name

In my own experience regarding the difficulty of naming something, it has always indicated the codebase is too big and multi-functional. Thus, there are two paths to take: 1) Slap a brand name on it because no descriptive name can succinctly capture all the provided functionality 2) Break down the

Re: [DISCUSSION] finishing Aether import: help find a new name

It is all about Maven coordinates: groupId + artifactId + version + extension ( + classifier) This all together results in a URL to a repository. In case of remote repositories these work both with M1 and M2 repository layouts (yes, the name is confusing...) So it is not just about java files

Re: [DISCUSSION] finishing Aether import: help find a new name

Because we otherwise end up with really long names and even wrong names for such external facing components. E.g. we have Maven Artifact Resolver Ant Plugin as the new name. It would be a long name ... and it would be wrong too. Since it can also install and deploy build outputs. Of course

Re: opinions on MJAVADOC-451

Anyone want to give this a quick read/opinion? :-) -Richard -- Original Message -- From: "Richard Sand" To: dev@maven.apache.org Sent: 8/1/2016 6:33:30 PM Subject: opinions on MJAVADOC-451 Hi all, I'd like to ask for opinions on https://issues.apache.org/jira/browse/MJAVADOC-451. R

Re: [DISCUSSION] finishing Aether import: help find a new name

I my view, we should not be inventing brand names for miscellaneous internal pieces of Maven. We have hundreds of such pieces. Why give nicknames to some? On Thu, Aug 4, 2016 at 11:40 AM, Manfred Moser wrote: > I also prefer something like a short name even if its a shortcut like Mars. > In fact

Re: [DISCUSSION] finishing Aether import: help find a new name

I also prefer something like a short name even if its a shortcut like Mars. In fact.. I like Mars. We would have the mars-core and other artifacts and maybe also the Mars Ant Task (port of Aether Ant Tasks.. https://maven.apache.org/components/aether-archives/aether-ant-tasks-LATEST/) Manfred

RE: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

Hi Christian, Thanks for the hint to try maven 3.4.0-SNAPSHOT I tried, and the result is again BUILD FAILURE - but with a nice colored system out, and - more seriously - a different, and IMHO misleading, error message. (Cf. full reproducible commands at https://github.com/iroif/iroif-parent/b

Re: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

Am 08/04/16 um 12:36 schrieb Thiebaud, Christophe: > I understand that pom file of lib 0.0.1-SNAPSHOT dependency cannot be built > because of missing (evicted) parent 0.0.1-SNAPSHOT. > > The point is that failing to build lib 0.0.1-SNAPSHOT pom file should not > result in a app failed build, as

RE: project having a dependency with a version range fails building when parent pom of dependency is evicted from remote repo

I understand that pom file of lib 0.0.1-SNAPSHOT dependency cannot be built because of missing (evicted) parent 0.0.1-SNAPSHOT. The point is that failing to build lib 0.0.1-SNAPSHOT pom file should not result in a app failed build, as there exists another valid lib 0.0.2-SNAPSHOT (having parent

Re: [DISCUSSION] finishing Aether import: help find a new name

Am 08/04/16 um 02:34 schrieb Ralph Goers: > I much prefer MARS, especially if you can come up with corresponding wordplay > for VENUS… ;-) Better than 'resolver'. > > Seriously, the overlap with Java ARchive is bound to be confusing, and might > even make people think that the component has so