Re: [DISCUSS] Merge JPMS work in upcoming maven-compiler-plugin beta-2

What is the easiest way to determine what has been changed? When I was working on Log4j’s JPMS support Maven’s handling of JPMS frequently caused problems and forced us to do some things I consider kind of ugly. Ralph > On Oct 23, 2024, at 7:12 AM, Guillaume Nodet wrote: > > Following the b

Re: [DISCUSS] Project member emeritus policy change

FWIW, if Maven adopts the idea of modifying https://maven.apache.org/team.html similar to the Logging Services team page I linked too then I would likely move myself to the inactive list. Although I do occasionally participate in threads like this and vote on occasion I haven’t committed to the

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

GitHub can be a pain with all the email it generates. However, I would think Maven would be the perfect project to use discussions and issues. Every maven plugin would have its discussions in its repo so following along with areas one is interested in could be much easier. This list would still

Re: [DISCUSS] Project member emeritus policy change

I would suggest that just responding on mailing lists count as well. It is fairly easy to see if a user’s email shows up in any of the mailing lists. This would also include GitHub commits, PRs, discussions, etc. since they all generate email to a list. Also - do you truly mean “emeritus” (remo

Re: And while I'm on the subject of logging

Might I suggest that you are never going to make everyone happy. That is why Logging frameworks such as Log4j support using Logger names, Log Levels, and Markers as basic ways of categorizing log events. With those you can continue to log events but filter them down to just what the user wants.

Re: Adding extra "scope" type metadata to dependencies?

Extending the pom.xml has been discussed for years. Unfortunately, it validates the XSD, so when the pom is extended with new attributes older versions of Maven will fail. This is the main reason why import scope was introduced rather than using a new element. There were many discussions about

Re: Logging in Maven Plugins - Bridging

ote: > > On 6/11/2022 at 8:31:45 PM, Ralph Goers wrote: > >> I can absolutely guarantee you that if Google is actually using JUL that >> they >> have written plenty of their own code on top of it since JUL is woefully >> incomplete. > > > Google came up with

Re: Logging in Maven Plugins - Bridging

> On Nov 5, 2022, at 6:08 AM, Elliotte Rusty Harold wrote: > > After log4shell last year, I no longer have any patience for third > party logging libraries, full stop. > > IMO logging should be done through java.util.logging, nothing else. > This is fully functional since Java 1.4 twenty year

Re: Question - JDK Minimum of future Apache Maven 4.0.0

> On Jul 25, 2022, at 12:34 PM, Michael Osipov wrote: > > Am 2022-07-25 um 21:31 schrieb Ralph Goers: >> So my vote would be +1 for Maven 4 requiring Java 17 under the condition >> that Maven 3 continues to get new releases. > > This will not happen with me, only

Re: Question - JDK Minimum of future Apache Maven 4.0.0

Some statistics below. I think you are being very optimistic about how fast people will adopt JDK 17. If it follows the trends for Java 8 and 11 I would put money on betting it won’t be the predominant version until the next LTS is released. https://adoptium.net/support and https://aws.amazon.

Re: Change of Chair

Thanks for all you’ve done as chair Robert. It has been much appreciated. Congrats Karl! Ralph > On Apr 21, 2022, at 4:57 PM, Robert Scholte wrote: > > Hi all, > > as of now, Karl Heinz is the new chairman of the Apache Maven project. > I've done it for quite some time with a lot of pleasure

Re: Maven Dependency Plugin - Log4j vulnerabilities

This appears to be plugin dependencies though, not project dependencies. The issue should really be raised with whatever plugin is causing it to be used. My recollection is that Maven itself hasn’t used Log4j in quite some time for logging. Ralph > On Mar 3, 2022, at 8:21 AM, Gary Gregory wr

Re: JPMS data as first-class citizen of the POM

My 2 cents. I’ve spent many, many hours trying to make Log4j 2 JPMS compatible. It is still nowhere near done. While JPMS sounds simple the side effects it has permeate everything. If you were to look at the Log4j 2 master branch right now it is a complete mess. Adding Java 9 support was bad en

Re: JPMS, Maven and test jars

> On Jun 22, 2021, at 2:29 PM, Andres Almiray wrote: > > Ralph, > > Once you move test code to their own Maven module they become a top level > module, that is, they have a life of their own as any other top level module. > > In contrast -tests jars are not top level, but a “variant” (that’

Re: JPMS, Maven and test jars

> On Jun 22, 2021, at 11:16 AM, Robert Scholte wrote: > > If I understand correctly you want both log4j-core main classes and test > classes be distributed as modularized jars. > To me with JPMS you should move the modularized test-classes to a separate > Maven module as a first citizen arti

Re: JPMS, Maven and test jars

derstand recursion, we must first understand recursion. > > > On Tue, Jun 22, 2021 at 7:02 AM Ralph Goers > wrote: > >> Sorry for posting again. I really need to proof-read better. Please ignore >> the prior email. >> >> I have recently had quite an

Re: JPMS, Maven and test jars

Gary, the test jar doesn’t perform tests. It provides test utility classes like LoggerContextRule. > On Jun 22, 2021, at 12:31 PM, Gary Gregory wrote: > > It feels to me like JPMS just plainly breaks the informal industry standard > of the Maven project layout we have all been using for a mil

Re: JPMS, Maven and test jars

> On Jun 22, 2021, at 1:19 PM, Elliotte Rusty Harold wrote: > > On Tue, Jun 22, 2021 at 7:32 PM Gary Gregory wrote: > >> In addition, how is one supposed to test package private code if a test jar >> tests a main jar where all packages are now different? > > Some projects adhere to strictly

Re: JPMS, Maven and test jars

e main source before it will allow the unit tests to include one. > > This will also help your IDE recognize the code. > And as this is a common pattern, it will also help other coders to > more easily recognize the structure of your project. Yes, this will obviously make the IDE happie

Re: JPMS, Maven and test jars

ting > module, but to me for a good reason. > > Even with your very small reduction of steps to simplify the process, it > doesn't fit in the default lifecycle unless you write you introduce a new > lifecycle-binding or write a new extension. > > Robert > > On

Re: JPMS, Maven and test jars

Sorry for posting again. I really need to proof-read better. Please ignore the prior email. I have recently had quite an adventure modifying several of Log4j’s Maven modules to implement JPMS on our master branch. It was an adventure due to a few issues: 1. https://bugs.java.com/bugdatabase/vi

JPMS, Maven and test jars

I have recently had quite an adventure modifying several of Log4j’s Maven modules to implement JPMS on our master branch. It was quite an adventure due to a few issues: 1. https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8265826. This bug has been fixed in Java 17 but Log4j uses Ja

Re: JPMS compile problems

Thanks Christian, Thanks to either a good night’s sleep or reading the messages in this thread I realized deleting the module-info.class file generated to create the test jar might fix the problem. It did. After deleting it the compiler only used the class path to run the annotation processor an

JPMS compile problems

I am trying to convert Log4j 2 to be fully modularized and am running into problems with Log4j-core. First, I have hit a couple of nasty bugs when compiling on MacOS that are reflected in https://issues.apache.org/jira/browse/MCOMPILER-461

Re: Security/Versioning policy proposal

it upfront. >>> >>> So proposal can be: >>> >>> [Experimental policy until June 2022] >>> 1. We maintain two major releases, ie 3.x and 4.x as of today (no minor >> in >>> particular, just the highest one) >>> 2. We maintain versio

Re: Security/Versioning policy proposal

you >> can require them from a project which does not offer them by themself). >> >> >> -- >> http://bernd.eckenfels.net >> >> Von: Ralph Goers >> Gesendet: Sunday, April 4, 2021 9:55:50 PM >> An: Maven Deve

Re: Security/Versioning policy proposal

More than likely you will get whatever the next version number happens to be. I can’t think of a case where Maven needed to go back and patch a prior release. That could happen however, if Maven was modified to require Java 11 to run and a security fix had to be applied to the last version supp

Re: [VOTE] Release Apache Maven version 3.8.0

If I were a user and expected the feature to be in 3.7.0 then I would certainly also expect it in 3.8.0. The only ways to avoid this are a) stay on 3.6.x.x until the feature is available, b) specifically say the promised features aren’t available yet. That said I’m +0 on the version numbering.

Re: APT vs Markdown formats for site docs

Log4j didn’t switch everything. A couple pages had to be left as Markdown for things AsciiDoc doesn’t support, although at the moment I don’t remember what those things were at the moment. Ralph > On Feb 1, 2021, at 6:30 AM, Gary Gregory wrote: > > FYI, over at Log4j, we switched to Asciidoc.

Re: Maven plugin fails when a class compiled for Java 9 is present in a jar running in Java 8.

I spoke too soon. It appears my java9 classes are not being found in the multi-release jar so I still don’t know if it fixes the problem with the scanner. Ralph > On Jun 15, 2017, at 8:28 PM, Ralph Goers wrote: > > FWIW, building the jar as a multi-release jar did fix this pro

Re: Maven plugin fails when a class compiled for Java 9 is present in a jar running in Java 8.

support toolchains so it can’t be used to compile) and then call the jar plugin. The maven-bundle-plugin doesn’t support multi-release jars so it has to be called before the java9 classes are created. Ralph > On Jun 15, 2017, at 4:42 PM, Ralph Goers wrote: > > I have a plugin that uses a

Maven plugin fails when a class compiled for Java 9 is present in a jar running in Java 8.

I have a plugin that uses a jar that doesn’t have any Maven plugin annotations in it but does have classes compiled for Java 9 in it that are only used when executing on Java 9. Loading of the plugin is failing because the annotation scanner can’t read the class. What do I need to do to prevent

Re: [VOTE] Release Apache Maven 3.5.0-alpha-1

+1 Ralph > On Feb 27, 2017, at 11:51 AM, Stephen Connolly > wrote: > > Any more PMC members care to vote? > > -- Forwarded message - > From: Stephen Connolly > > Date: Mon 27 Feb 2017 at 14:42 > Subject: Re: [VOTE] Release Apache Maven

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

I much prefer MARS, especially if you can come up with corresponding wordplay for VENUS… ;-) Seriously, the overlap with Java ARchive is bound to be confusing, and might even make people think that the component has something to do with them. Ralph > On Aug 3, 2016, at 4:29 PM, Christian S

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Actually, for me the ideal would be a command line switch that could re-enable the feature that was deprecated. Then you don’t really have to wait a release, so long as it is documented. This makes sure user’s are aware since they have to take a minor action to continue to make things work. Ral

Re: 3.4.0 SNAPSHOT breaks Log4j build

This is an interesting situation. The classes that use Jackson are all considered optional in Log4j, so having optional set to true is indeed what is desired. However, we require those dependencies to compile and to run the unit tests. With scope set to test I would expect that the non-test cla

Re: [Discuss] [VOTE] Retire Maven Ant Tasks

Thanks. That is perfect. Ralph > On May 16, 2016, at 9:25 AM, Michael Osipov wrote: > > Am 2016-05-16 um 15:58 schrieb Ralph Goers: >> Where is the doc for Maven for Maven? I didn’t see anything on the maven >> plugins page or via a Google search. > > There is htt

Re: [VOTE] Retire Maven Ant Tasks

+1 Ralph > On May 15, 2016, at 4:24 PM, Michael Osipov wrote: > > Hi, > > this component hasn't been touched for years effectively and we rely now on > Maven for Maven (dog food). Additionally, Ant build support has already been > removed from Maven. This relic shouldn't be used with Maven 3

[Discuss] [VOTE] Retire Maven Ant Tasks

Where is the doc for Maven for Maven? I didn’t see anything on the maven plugins page or via a Google search. Ralph > On May 15, 2016, at 4:24 PM, Michael Osipov wrote: > > Hi, > > this component hasn't been touched for years effectively and we rely now on > Maven for Maven (dog food). Addit

Re: Log4j Warning

with that. > > Reasonable? > >> On Jan 7, 2016, at 1:47 PM, Ralph Goers wrote: >> >> He claims that Log4j 2 isn’t popular enough. The real reason, as you >> probably know, is that Jason seriously dislikes me, although he would never >> actually say t

Re: Log4j Warning

I apologize for this email. It was not meant for this list. Ralph > On Jan 7, 2016, at 11:47 AM, Ralph Goers wrote: > > He claims that Log4j 2 isn’t popular enough. The real reason, as you > probably know, is that Jason seriously dislikes me, although he would never > actua

Re: Log4j Warning

He claims that Log4j 2 isn’t popular enough. The real reason, as you probably know, is that Jason seriously dislikes me, although he would never actually say that as his reason. Ralph > On Jan 7, 2016, at 10:56 AM, Jason van Zyl wrote: > > >> On Jan 7, 2016, at 11:43 AM, Arnaud Héritier wr

Re: Log4j Warning

Jason, I really don’t care which logging framework Maven uses. There isn’t going to be much difference between Logback and Log4j 2 in a batch process like Maven, although asynchronous loggers might speed up larger builds somewhat. However, these comparisons are still incorrect. Log4j is using t

Re: logging during multithreaded builds

If you use the SLF4J MDC - which is supported by Logback, Log4j 1.x and 2.x - you can include anything stored in the MDC on every line of log output. Just use %X to include all MDC items or %MDC{key} to include the specific key. This would require storing the value(s) at the beginning of every

Re: [VOTE] Release Apache Maven Fluido Skin Version 1.4

See the section right above - http://www.apache.org/foundation/voting.html#ReleaseVotes . Notice the bold sentence that says release votes cannot be vetoed. You can vote -1 on a release, but that is not a veto. If someone has a conce

Re: [VOTE] Maven 3.3.1 Release

+1. Release looks good to me. Ralph > On Mar 13, 2015, at 6:08 PM, Paul Benedict wrote: > > There are about ten unresolved issues that need to be kicked out of this > version. > On Mar 13, 2015 7:14 PM, "Jason van Zyl" wrote: > >> Great, thanks for testing! >> >> jvz >> >>> On Mar 13, 2015

Re: [DISCUSS] Design by committee

> On Nov 25, 2014, at 8:14 AM, Stephen Connolly > wrote: > > On 25 November 2014 at 14:31, Ralph Goers > wrote: > >> -1 - only because a) I don’t understand the purpose of what is going on on >> the bird’s chest and > > > http

Re: [VOTE] Change project logo and adopt owl as mascot

-1 - only because a) I don’t understand the purpose of what is going on on the bird’s chest and b) I love the idea of putting the bird in a sweater with the letter “M” on it. Ralph > On Nov 25, 2014, at 5:05 AM, Andreas Gudian wrote: > > +1 > > Am Dienstag, 25. November 2014 schrieb Stephen

Re: [DISCUSS] Adopt Mr Couché-Tard as our mascot, change the logo font to Alte Haas Grotesk, change the colour letter to "v"

Why does the owl need chest hair? (or whatever the oval patch is supposed to represent). Ralph > On Nov 23, 2014, at 2:59 PM, Stephen Connolly > wrote: > > On 23 November 2014 at 02:53, Hervé BOUTEMY > wrote: > >> Le samedi 22 novembre 2014 19:22:29 Benson Marg

Re: New logo?

I like the owl, but why not just make the body a solid color? To me it now looks like one of those fancy “haircuts’ people get where they have something shaved into their head. Ralph > On Nov 20, 2014, at 2:43 AM, Stephen Connolly > wrote: > > Stop calling Couché-tard "shotgun owl"! > > Do

Re: [VOTE] Release Maven 3.1.1

Sent from my iPad > On Sep 22, 2013, at 4:41 PM, sebb wrote: > >> On 22 September 2013 05:03, Jason van Zyl wrote: >> >>> On Sep 21, 2013, at 7:44 PM, sebb wrote: >>> On 22 September 2013 03:09, Jason van Zyl wrote: > On Sep 21, 2013, at 6:16 PM, sebb wrote: > > On 21 S

Re: [VOTE] Retire Maven Model Converter

+1 Ralph On Jul 20, 2013, at 10:26 AM, Dennis Lundberg wrote: > Hi, > > The only consumer of Maven Model Converter we have left at the Apache > Maven project is Maven One Plugin. If the vote for the retirement of > Maven One Plugin succeeds we should also retire Maven Model Converter. > The las

Re: [VOTE] Retire Maven One Plugin

+1 Ralph On Jul 20, 2013, at 2:13 AM, Dennis Lundberg wrote: > Hi, > > Now that we have Maven 1 at End-Of-Life, I think it's time to retire > Maven One Plugin as well. It has been almost six years since the last > release. I therefor propose that we retire maven-one-plugin. > > http://maven.ap

Re: [VOTE] Retire maven-idea-plugin

+1 (binding) Ralph On Jul 19, 2013, at 10:01 AM, Dennis Lundberg wrote: > Hi > > It has been almost five years since I made the last release of > maven-idea-plugin. The features in IDEA to integrate Maven has been greatly > improved since then, making our own plugin obsolete. I therefor propose

Re: Release process updates

Mirko > -- > Sent from my mobile > On Jun 27, 2013 4:42 PM, "sebb" wrote: > >> On 27 June 2013 15:05, Ralph Goers wrote: >>> I do not believe that can be done with the release plugins as the pom >> has to specify the same version as the tag. If you then r

Re: Release process updates

GA tag. > > On 25 June 2013 19:38, Ralph Goers wrote: >> Yeah - I agree with this. I rename them to rc1, rc2, etc after a failed >> release vote instead of deleting them. >> >> >> On Jun 25, 2013, at 11:23 AM, Gary Gregory wrote: >> >>>

Re: Release process updates

Yeah - I agree with this. I rename them to rc1, rc2, etc after a failed release vote instead of deleting them. On Jun 25, 2013, at 11:23 AM, Gary Gregory wrote: > On Tue, Jun 25, 2013 at 2:19 PM, Ralph Goers > wrote: > >> Again I have to disagree. The release manager wil

Re: Release process updates

t; critical. Better to figure out how to support proper techniques now, rather > than wait until forced to. > > On Tue, Jun 25, 2013 at 7:52 PM, Ralph Goers > wrote: > >> I disagree that the revision is required. I know that the RM is going to >> recreate the tag with

Re: Release process updates

I disagree that the revision is required. I know that the RM is going to recreate the tag with each release candidate. Therefore, so long as I refetch that tag for every release vote I can be confident that I am reviewing the release contents. Ralph On Jun 25, 2013, at 9:52 AM, sebb wrote:

Re: [VOTE] Apache Maven Javadoc Plugin 2.9.1 (take 2)

KEYS file - http://svn.apache.org/repos/asf/maven/project/KEYS svn tag - http://svn.apache.org/repos/asf/maven/plugins/tags/maven-javadoc-plugin-2.9.1 +1 on the release however it is odd that the Release Notes page is empty. Ralph On Jun 24, 2013, at 7:15 PM, sebb wrote: > On 25 June 2013 02:

Re: [VOTE] Should we respin CANCELLED releases with the same version number?

-1 (binding) Ralph On May 29, 2013, at 3:01 AM, Stephen Connolly wrote: > We have been using a policy of only making releases without skipping > version numbers, e.g. > > 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, etc > > Whereby if there is something wrong with the artifacts staged for release,

Re: [VOTE] formally end support for Maven 1

+1 Ralph On Mar 2, 2013, at 7:18 AM, Benson Margulies wrote: > Based on the sentiment on the discussion thread, I call a formal vote > to end support for Maven 1.x. This is a vote to: > > 1: Remove maven 1 release materials from the primary distribution > area, leaving them only on the archive

Re: Logback in Maven Core

Oh - FWIW I'm running on OSX 10.7.5 with a 2.5 GHz Intel Core i7 with 16GB of memory. Ralph On Dec 12, 2012, at 12:27 AM, Ralph Goers wrote: > I checked out Maven and used its build as a comparison. First, I ran the > log4j 2 build and it was taking around 59 seconds. I then

Re: Logback in Maven Core

I checked out Maven and used its build as a comparison. First, I ran the log4j 2 build and it was taking around 59 seconds. I then changed the log4j2.xml to remove the colors. I then got an average time for Log4j 2 of 54.76s and for Logback I get an average of 55.225s. I consider these diff

Re: [VOTE] Release Maven PDF Plugin Version 1.2

+1 Ralph On Nov 5, 2012, at 2:40 PM, Benson Margulies wrote: > To: "Maven Developers List" > Subject: [VOTE] Release Maven XXX Plugin version Y.Z > > Hi, > > We solved 15 > issues:http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11932&version=16050 > > There are still a couple of

Re: Aether 0.9.0.M1

On Oct 6, 2012, at 4:23 AM, Hervé BOUTEMY wrote: > Aether 0.9.0.M1 is now in central [1] > and Benjamin did the upgrade on his own Maven 3 branch [2] > > Question: do we need a formal vote for the upgrade of this dependency? No. > Any objection to do the upgrade without vote, given it's just a

Re: SLF4J implementation [was Re: svn commit: r1380105 - in /maven/maven-3/trunk: ./ apache-maven/ maven-core/src/main/java/org/apache/maven/classrealm/ maven-embedder/ maven-embedder/src/main/java/or

Sorry - I should have added - "unless your facade uses LocationAwareLogger instead of the normal Logger". Ralph On Sep 10, 2012, at 9:21 AM, Ralph Goers wrote: > > On Sep 10, 2012, at 7:06 AM, Mark Struberg wrote: > >> >>> Absolutely. In light of commit

Re: SLF4J implementation [was Re: svn commit: r1380105 - in /maven/maven-3/trunk: ./ apache-maven/ maven-core/src/main/java/org/apache/maven/classrealm/ maven-embedder/ maven-embedder/src/main/java/or

On Sep 10, 2012, at 7:06 AM, Mark Struberg wrote: > >> Absolutely. In light of commit r1380105, the next step is for you >> (Maven folks) to formulate a policy for swapping out logging >> back-ends. > > Well that is what this is all about. And we have this solution available in > Maven since

Re: SLF4J implementation [was Re: svn commit: r1380105 - in /maven/maven-3/trunk: ./ apache-maven/ maven-core/src/main/java/org/apache/maven/classrealm/ maven-embedder/ maven-embedder/src/main/java/or

First, I also would recommend moving from plexus logging to SLF4J. Mark's concerns with incompatibilities only come about with the log4j bridge if you are trying to use APis that the SLF4J bridge hasn't implemented. Something being used in a plugin really shouldn't be using those. Although C

Re: RPMs for Maven 3?

On Mar 20, 2012, at 5:23 PM, Stephen Connolly wrote: > > Actually -1 votes don't count. You cannot veto releases, you only > need 3 x +1... so we could have 3 x +1 and 21 x -1 and the release > manager is still allowed to proceed with the release! [It would be bad > form to proceed from my PoV,

Re: [VOTE] Release Maven Fluido Skin version 1.0

+1 I didn't do an exhaustive review. The skin itself works fine in the project I've added it to. I verified the source zip builds. There aren't any release notes but I'm not sure that is required. I did notice that there is a NOTICE file and a NOTICE.txt file that are not identical. I'm not sur

Re: New plugin patch-tracker

Dennis - have you by chance modified the changes plugin so that there is a jar with most of the logic and the plugin? I recently wanted to create a new plugin that used logic from the changes plugin but couldn't see how to do it. Ralph On Nov 21, 2011, at 1:01 PM, Dennis Lundberg wrote: > On

Re: [VOTE] Usage of Aether and Sisu as dependencies of maven core with EPL licenses - take 2

+1 (binding) Ralph On Aug 18, 2011, at 2:23 AM, Arnaud Héritier wrote: > Hi all, > > Thus as decided with Mark and Kristian I relaunch a new vote with a better > scope about what we are voting for. > > Next releases of SISU and Aether will be released at Eclipse.org under EPL > 1.0 license.

Re: Pluggable Dependency Resolution

What you are suggesting here is something I've been advocating for the last several years - adding "provides" and "requires" to poms to indicate versions of things they require that are more granular than the jar. In the example below the driver might support several JDBC versions. Specifying ju

Re: [DISCUSS] incorporate EPL Aether

I would suggest you re-read Brett's last email as to why we continue to have this discussion. He seems to be able to word things a bit better than me. Sent from my iPhone On Jul 30, 2011, at 11:14 AM, Jason van Zyl wrote: > >> >> >>> > > >>> >>> >> > >

Re: [DISCUSS] incorporate EPL Aether

See below Sent from my iPhone On Jul 30, 2011, at 10:33 AM, Jason van Zyl wrote: > > On Jul 30, 2011, at 4:16 PM, Ralph Goers wrote: > >> See below. >> >> Sent from my iPhone >> >> On Jul 30, 2011, at 9:39 AM, Jason van Zyl wrote: >> >

Re: [DISCUSS] incorporate EPL Aether

See below. Sent from my iPhone On Jul 30, 2011, at 9:39 AM, Jason van Zyl wrote: > > On Jul 30, 2011, at 2:52 PM, Ralph Goers wrote: > >> The dual license makes a difference because if someone wants to make a >> change that Aether doesn't want it can easily be i

Re: [DISCUSS] incorporate EPL Aether

On Jul 30, 2011, at 11:58 AM, Benson Margulies wrote: > On Sat, Jul 30, 2011 at 2:52 PM, Ralph Goers > wrote: >> The dual license makes a difference because if someone wants to make a >> change that Aether doesn't want it can easily be incorporated here since the >

Re: [DISCUSS] incorporate EPL Aether

Actually, from the responses given to my question I'm sure the board would not look fondly on a fork at github either. On Jul 30, 2011, at 10:28 AM, Ralph Goers wrote: > The board will not look fondly on Maven switching to a fork hosted at Apache > Extras. However, I'm no

Re: [DISCUSS] incorporate EPL Aether

sn't this the basic concern over using > aether?). I don't see this as a plausible scenario. > > thanks > david jencks > > On Jul 30, 2011, at 10:14 AM, Ralph Goers wrote: > >> The board made it pretty clear that option b is also highly discouraged so I

Re: [DISCUSS] incorporate EPL Aether

Can we create our own, new API that plugins should use for this? Eventually all of Maven could use that instead of Aether directly. Ralph On Jul 30, 2011, at 10:25 AM, John Casey wrote: > On 7/30/11 9:00 AM, Stephen Connolly wrote: >> well it seems to me that we need to ensure that aether is n

Re: [DISCUSS] incorporate EPL Aether

The board will not look fondly on Maven switching to a fork hosted at Apache Extras. However, I'm not sure what they would think about a github fork since sonatype-aether is hosted there and that is precisely what github promotes. Ralph On Jul 30, 2011, at 9:50 AM, Mark Struberg wrote: > Th

Re: [DISCUSS] incorporate EPL Aether

The board made it pretty clear that option b is also highly discouraged so I wouldn't list that as an option. The only viable path I see will be to ultimately include the EPL version of Aether and then replace it with our own code when someone decides there is something they want to do that req

Re: [DISCUSS] SCM child-project URL composition

se-plugin to get the benefit of them. > > > On Sat, Jul 30, 2011 at 4:55 AM, Ralph Goers > wrote: >> i think I'm missing something. My understanding has been that any file named >> pom.xml that isn't compliant with 4.0.0 is going to break Maven 2 users. Am &g

Re: [VOTE] Incorporate EPL Ether in Maven Releases

I'm in the same boat. I can't in good conscience vote -1 because I am in no position to take on the task of doing a rewrite. OTOH, given the things people have said they would really like to do I am pretty sure this issue is going to keep coming up. For the same reasons as yours I'm going to ha

Re: [DISCUSS] SCM child-project URL composition

i think I'm missing something. My understanding has been that any file named pom.xml that isn't compliant with 4.0.0 is going to break Maven 2 users. Am I misunderstanding something about what is being proposed? Ralph On Jul 29, 2011, at 8:04 AM, Benson Margulies wrote: > I think Herve said so

Re: [DISCUSS] incorporate EPL Aether

On Jul 17, 2011, at 9:08 AM, Benson Margulies wrote: >> >> I think you are going to have to. Mark isn't the only one who has expressed >> the sentiment. Some of the discussions I've seen on changing the >> relationship Maven has with repository managers would surely require changes >> at the

Re: [DISCUSS] incorporate EPL Aether

On Jul 17, 2011, at 7:45 AM, Benson Margulies wrote: > So, the document states that the PMC decided that category B's are > acceptable by majority vote. As per standard ASF community norms, it's > better to give people a chance to achieve consensus and vote to affirm > it than to just stage a vot

Re: [Gentoo-maven-intg] Intermediary shaded source files generated by maven-shade-plugin

From Kasun's answers it is quite clear to me that we will need to add something to Jira where it asks for the operating system for all the Java projects I work on at the ASF. If the O.S. is Gentoo then we will have to reject any issues coming from the stuff that comes as part of the O.S. as it c

Re: [Gentoo-maven-intg] Intermediary shaded source files generated by maven-shade-plugin

ph On Jul 4, 2011, at 6:11 AM, Kasun Gajasinghe wrote: > On Mon, Jul 4, 2011 at 11:31 AM, Ralph Goers > wrote: > >> The point I am making is that if you have all those jars together something >> is not going to work correctly. SLF4J only allows one logging >> imple

Re: [Gentoo-maven-intg] Intermediary shaded source files generated by maven-shade-plugin

54 AM, Kasun Gajasinghe wrote: > On Sun, Jul 3, 2011 at 10:42 PM, Ralph Goers > wrote: > >> Out of curiosity, you said you are putting building your jars and putting >> them in a shared library. What are you going to do with SLF4J, Log4J, >> Commons Logging and Logback? >

Re: [Gentoo-maven-intg] Intermediary shaded source files generated by maven-shade-plugin

Out of curiosity, you said you are putting building your jars and putting them in a shared library. What are you going to do with SLF4J, Log4J, Commons Logging and Logback? Ralph On Jul 3, 2011, at 9:57 AM, Kasun Gajasinghe wrote: > On Sun, Jul 3, 2011 at 6:30 PM, Benson Margulies wrote: > >>

Re: [Gentoo-Maven-Intg] plexus-velocity missing - maven-remote-resources-plugin fails with a ClassNotFoundException

On Jul 2, 2011, at 8:38 AM, Kasun Gajasinghe wrote: >> > > Ralph, > No, you are not discouraging me in anyway. This stage is just the first step > of a much wider task. The ultimate goal of this work is to provide the > ability to package maven-based builds to Gentoo system. Gentoo encourages >

Re: [Gentoo-Maven-Intg] plexus-velocity missing - maven-remote-resources-plugin fails with a ClassNotFoundException

Not to belittle what you are doing, but on every system I use I 1) Download the maven gziip. 2) unzip it in /opt 3) create a symlink of /opt/maven to the maven I downloaded 4) add /opt/maven/bin to the path in /etc/profile 5) add an export for M2_HOME to /opt/maven in /etc/profile. Then I start us

Re: Experiments in vote counting

-1 I have used my dslextreme.com email for years and now have a couple dozen ASF email lists on it. rgo...@apache.org forwards to it. Event when I send as rgo...@apche.org from gmail (which hosts dslexteme.com) or Mac Mail it always still shows that it is sent by my dslextreme.com account (I t

Re: The JIRA chocolate box

My guess is a reference to Forrest Gump - you never know what you are going to get. Ralph On Jun 18, 2011, at 7:51 PM, Martin Gainty wrote: > > agreed > although scanning the Surefire JIRA i did notice some of jasons original > jiras were'nt addressed for upwards of 3-4 years (by Brett Porte

Re: [REDUX] Java Service Wrappers (JSW) unfortunate license change

On Jun 13, 2011, at 9:02 PM, Brett Porter wrote: > > On 14/06/2011, at 1:05 PM, Ralph Goers wrote: > >> >> On Jun 13, 2011, at 7:23 AM, Nigel Magnay wrote: >> >>> There is a fork under the old license here: >>> >>> https://bitbucket.o

Re: [REDUX] Java Service Wrappers (JSW) unfortunate license change

On Jun 13, 2011, at 7:23 AM, Nigel Magnay wrote: > There is a fork under the old license here: > > https://bitbucket.org/ivertex/java-service-wrapper/overview > I apologize if I missed it somewhere in this thread, but as I recall commons exec was created primarily due to the license change of

Re: Get thee to the Core...

t from my Android phone, so random spelling mistakes, random nonsense > words and other nonsense are a direct result of using swype to type on the > screen > On 11 Jun 2011 06:50, "Ralph Goers" wrote: - To unsubs

Re: Get thee to the Core...

berg wrote: > Ralph, are you working on log4j-2.0? > Is it (close to) production ready? > > Of course, I'd have no problem to use it. This would allow us to improve > log4j-2.0 plus we'd quickly get fixes/changes if we need them. > > LieGrue, > strub > >

  1   2   3   4   5   >