plugin then... perhaps a pseudo-tag
option is needed for the release plugin then...
On 29 May 2013 13:40, Barrie Treloar wrote:
> On 29 May 2013 20:53, Stephen Connolly
> wrote:
> > The issue with that is when using the Maven Release Plugin, you will not
> be
> ...
>
> Can&#
On Thursday, 30 May 2013, Chris Graham wrote:
> What do we currently do for plugins?
What do we currently do for core?
> Is there in difference in the approach taken?
No difference. In each case we currently respin failed votes reusing the
version number until we get an actual successful vote.
lic version numbers.
>
> For the same reason, I would recommend offering different approaches to
> core/plugins/whatever: let's not complicate things.
>
> So, to that end,
>
> -1 (ie respin) for all
>
> (non binding)
>
> -Chris
>
>
>
> On Thu, May 3
pt of immutability, which is a reason NOT to
> allow the reuse of numbers; however, that does not appear to have been too
> much of a problem up until now.
>
> -Chris
>
>
>
>
> On Thu, May 30, 2013 at 7:55 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com&g
On 30 May 2013 11:38, Fred Cooke wrote:
> When I first witnessed the deletion of tags
> and re-spinning of versions some months ago it was the most disturbing
> thing that's happened to me since I found out that Santa Claus wasn't real.
>
WHAT THE F*CK!!! Are you suggesting to me that he isn't r
;>
>> Robert
>>
>>
>> Op Wed, 29 May 2013 15:20:17 +0200 schreef Daniel Kulp > >:
>>
>> +1 for "qualified" releases (alpha, beta, RC, etc…) that are working
>>> toward the full blow release but aren't intended to
On Thursday, 30 May 2013, Wayne Fay wrote:
> On Thu, May 30, 2013 at 4:55 AM, Stephen Connolly <...> wrote:
> >
> > And I am considering whether I want to change my vote ;-)
Nope I'm sticking with
+1 no reusing version numbers
After Fred pointed out the immutabili
You are the release manager. My vote on respinning specifically stated that
any releases in progress, the release manager can decide.
If it were me I'd call it 3.1.0-beta-1 as we have had enough eyes by now
that its better than alpha... I'd also be happy going straight for the
3.1.0 end game... Bu
h doesn't, to me, constitute any reasonably sized population. I'll roll
> it out in the morning.
>
> On May 30, 2013, at 4:15 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > You are the release manager. My vote on respinning specifically stated
>
On 31 May 2013 10:22, James Nord (jnord) wrote:
> > This discussion about respins is really strange to me. I've been cutting
> > releases, with Maven, at Apache, for years now. And all of them have
> reused
> > version numbers for respins. And all of them have carefully used staging
> > technolog
On 31 May 2013 10:41, James Nord (jnord) wrote:
> > -Original Message-
> > From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> > Sent: 31 May 2013 10:29
> > To: Maven Developers List
> > Subject: Re: [VOTE] Should we respin CANCELLED rele
On 31 May 2013 12:01, jieryn wrote:
> Greetings,
>
> On Fri, May 31, 2013 at 1:34 AM, Hervé BOUTEMY
> wrote:
> > I don't know what you mean by "send pull requests to Jenkins", if you're
> > talking about Apache's Jenkins instance or something more general from
> the
> > Jenkins project
>
> There
I will need to recheck the tally, but I think the result is -3
So looks like we will be reusing version numbers on respins
On Wednesday, 29 May 2013, Stephen Connolly wrote:
> We have been using a policy of only making releases without skipping
> version numbers, e.g.
>
> 3.0.0,
I will point out that for this specific vote I listed three options and a
criteria. So this vote has no vetoes. Simple sum of all binding votes
defines the result. If the sum is < -3 then that says majority dont want to
burn version numbers. If the sum > +3 then that says the majority want to
keep
Now the issue with componentX-1.4 that you wan to test is one that only
shows up behind your corporate proxy, and you have a system set up with the
failing case and you dare not change anything...
So you add the staging repo to your mirror, run the test case, and drop the
test artifact from the mi
rning version numbers, and the exception tests (or proves in old English)
the rule
(Anyway vote is over, so issue is moot. I don't care enough to call a
second vote)
> (I have yet to come across a scenaro where multiple
> users share this ;)
>
> Kristian
>
>
> 20
+1 (binding)
On 1 June 2013 14:13, Jason van Zyl wrote:
> Here are the release bits for 3.1.0-alpha-1:
>
> Release notes:
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18967
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-046/
>
On Friday, 7 June 2013, Andreas Gudian wrote:
> Hi,
>
> This is my first release, so please check carefully what I may have missed
> :).
>
> We solved 16 issues:
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=19174
>
> This is the first release that does not support
relocation pom will not work for plugins... (we maybe should look into that
though)
Simplest is just to move to the new ID and tell your users to change...
that's what jetty did
On 18 June 2013 16:00, Christian Schulte wrote:
> >> Perhaps we are at the point where we should start breaking buil
... is even better, in that it works. That is the only functional way in a
> large organisation, and I believe the maven community can be perceived as
> such.
>
>
>
> 2013/6/18 Christian Schulte
>
> > Am 06/18/13 17:32, schrieb Stephen Connolly:
> > > relocation
On Wednesday, 26 June 2013, Barrie Treloar wrote:
> On 26 June 2013 18:44, sebb > wrote:
> > Howewer the ASF releases source.
> > If you don't provide a download link to the source how are users
> > supposed to find it?
> >
> > I agree that most people are not going to want to download the origina
On Friday, 28 June 2013, Fred Cooke wrote:
> For git the unique hash is sufficient, you don't really need the tag at
> all, they simply point to the unique hash (or another tag, in a chain). If
> Git was the SCM of choice, I'd use RCX tags, and then not retag for final,
> but rather point the fina
On Sunday, 30 June 2013, sebb wrote:
> On 29 June 2013 11:47, Robert Scholte >
> wrote:
> > Hi Sebb,
> >
> > none of these files will end up in Maven Central, they are all used for
> > tests.
>
> However, they do end up in the source release which is published via
> the ASF mirrors.
> It's vital t
On Sunday, 30 June 2013, sebb wrote:
> On 30 June 2013 21:56, Fred Cooke >
> wrote:
> >>
> >> OK, so what is the Git command to download a copy of the sources that
> >>
> > are part of the hash?
> >>
> >
> > git checkout
>
> Does not work for me.
Until I hear otherwise, the reviewers for whom t
On Monday, 1 July 2013, Baptiste MATHUS wrote:
> Guys, even if not convinced this is really useful,
> I suppose voting template could just be adjusted so that the sha1
> or svn revision be added in the VOTE thread, and then get back to code as
> usual?
+1
>
> As it is just a 5 seconds additional
Anyone who has suggestions for improvements or additional content, please
shout out or commit your changes...
The aim is to let people understand the different roles and
responsibilities in the Maven community
On 2 July 2013 16:13, wrote:
> Author: stephenc
> Date: Tue Jul 2 15:13:59 2013
> N
block - assuming they make sense for the current sentence structure.
On 3 July 2013 10:17, Olivier Lamy wrote:
> 2013/7/3 Stephen Connolly :
> > Anyone who has suggestions for improvements or additional content, please
> > shout out or commit your changes...
> >
> &g
On 3 July 2013 11:39, Olivier Lamy wrote:
> 2013/7/3 Stephen Connolly :
> > It is important, but it interrupts the flow of the sentence. It is good
> > english to put interruptions in a subordinate clause so that the reader
> > knows to skip them in making sense of the
s they say, with great power comes great responsibility. :-)
>
> -Chris
>
> Sent from my iPhone
>
> On 03/07/2013, at 8:12 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > It is important, but it interrupts the flow of the sentence. It is goo
I have asked the legal-discuss list for an opinion on test data sets and
license headers. From my reading of the current ASF position:
http://www.apache.org/legal/src-headers.html#faq-exceptions we do not
currently have an exception for test data sets.
Pending the outcome of that discussion I will
On 4 July 2013 12:32, sebb wrote:
> On 4 July 2013 11:05, Stephen Connolly
> wrote:
> > I have asked the legal-discuss list for an opinion on test data sets and
> > license headers. From my reading of the current ASF position:
> > http://www.apache.org/legal/src-header
On 4 July 2013 13:14, sebb wrote:
> On 4 July 2013 12:52, Stephen Connolly
> wrote:
> > On 4 July 2013 12:32, sebb wrote:
> >
> >> On 4 July 2013 11:05, Stephen Connolly >
> >> wrote:
> >> > I have asked the legal-discuss list for an opi
s. If we know what it should be like then we might as
> well just do it, as it's likely to take less time than asking if an
> exception can be made.
>
> I can cancel the vote. Make the changes you think are required for
> compliance and I'll cut it again.
&g
testing the distribution tomorrow unless this vote gets cancelled
;-)
- Stephen
On Thursday, 4 July 2013, Jason van Zyl wrote:
> Fair enough.
>
> On Jul 4, 2013, at 8:59 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > I will let Barrie decide on
On Thursday, 4 July 2013, sebb wrote:
> On 4 July 2013 20:35, Stephen Connolly
> >
> wrote:
> > I am withdrawing my -1 on the basis of the feedback I have received from
> > legal-discuss.
>
> The question to legal-discuss was specifically about test data, not
On 5 July 2013 14:32, sebb wrote:
> On 5 July 2013 12:48, Olivier Lamy wrote:
> > Hi,
> > I'd like to release Apache Maven War Plugin 2.4.
> >
> > We fixed 10 issue
> >
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18840&styleName=Text&projectId=11150
> >
> > Staging repository:
> h
On 5 July 2013 14:43, Stephen Connolly wrote:
> On 5 July 2013 14:32, sebb wrote:
>
>> On 5 July 2013 12:48, Olivier Lamy wrote:
>> > Hi,
>> > I'd like to release Apache Maven War Plugin 2.4.
>> >
>> > We fixed 10 issue
>> >
>
On 5 July 2013 14:52, sebb wrote:
> On 5 July 2013 14:43, Stephen Connolly wrote:
> > On 5 July 2013 14:32, sebb wrote:
> >
> >> On 5 July 2013 12:48, Olivier Lamy wrote:
> >> > Hi,
> >> > I'd like to release Apache Maven War Plugin 2.
On 5 July 2013 14:56, sebb wrote:
> On 5 July 2013 14:46, Stephen Connolly wrote:
> > On 5 July 2013 14:43, Stephen Connolly wrote:
> >
> >> On 5 July 2013 14:32, sebb wrote:
> >>
> >>> On 5 July 2013 12:48, Olivier Lamy wrote:
> >>>
On Sunday, 7 July 2013, Arnaud Héritier wrote:
> I understand the issue but for me all that problems will never disappear if
> we don't find a solution to automate the process.
> Yes PMCs (and devs) are responsible to do various controls as you mentioned
> but I suppose that we aren't different to
On 8 July 2013 09:23, Arnaud Héritier wrote:
> Hi,
>
> Last night I introduced by error a dependency requiring Java 6 in the
> archetype plugin whereas we are always supposed to support Java 5 (Yes we
> can :-) )
> Myself I don't have anymore a Java 5 on my computer and I'm often using
> Java
lly by committers (and CI?) or
> in the release profile
> Something to add at which level ? plugins parent ? maven parent ?
>
>
> On Mon, Jul 8, 2013 at 10:52 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > On 8 July 2013 09:2
s.apache.org/repos/asf/maven/commit/50a24e54
> > Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/50a24e54
> > Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/50a24e54
> >
> > Branch: refs/heads/master
> > Commit: 50a24e5418a5eecfec5caa2502c59be3b
+1
On 4 July 2013 20:35, Stephen Connolly wrote:
> I am withdrawing my -1 on the basis of the feedback I have received from
> legal-discuss.
>
> My vote is now +0 as I have not tested the distribution and I am waiting
> for somebody else on the PMC to do the running and make a
Remember folks, we are CTR not RTC so we shouldn't be holding up getting
stuff done
On Monday, 15 July 2013, Arnaud Héritier wrote:
> I think we won't debate a lot :-)
> Pushed
>
>
> On Mon, Jul 15, 2013 at 10:02 PM, Hervé BOUTEMY
>
> >wrote:
>
> > +1
> >
> > Regards,
> >
> > Hervé
> >
> > Le l
So what I am hearing is that until we bump core to require JDK6 (or 7) then
logback is the only runner from a technical point of view (never mind that
log4j2 is still not GA)
OTOH I would be interested in bumping JDK all the way to 7 if we were happy
that toolchains is good enough and we had tests
Given that Oracle have stated they will be more aggressive in forcing
people to upgrade, eg -target (and I think -source too) will not got all
the way down to 1.2 any more from JDK8 IIRC, we will need to sort out a few
things:
- is toolchains the way to go?
- have we good test coverage with toolc
As long as surefire can fork down to 1.5 and as long as tool chains can
compile with 1.5, the only issue I can see is if the development
environments where these older JVMs are running do not have newer JDKs
available also.
This is the same issue we face in the Jenkins project, were we are
(consid
I've put a question on Stack Overflow:
http://stackoverflow.com/questions/17671899/when-is-java-6-end-of-life-in-the-context-of-writing-developer-toolsto
see if we can get something that is a bit more focus on facts.
e.g. we are all OSS developers: thus premium/extended/sustaining support
contract
egory Nyberg, and Philip Aston
> with Josh Bregman and Paul Done
> Book Home Page: http://www.wrox.com/
> Kindle Version: http://www.amazon.com/
>
>
>
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Tuesday, July 16,
>
> > > --
> > > Robert Patrick
> > > VP, FMW Architects Team: The A-Team
> > > Oracle Corporation Office: +1.940.725.0011
> > > 1148 Triple Crown Court Fax: +1.940.725.0012
> > > Bartonville, TX 76226, USA
On 16 July 2013 21:52, Kristian Rosenvold wrote:
> Look you chickens; until quite recently I kept a 1.3 JVM running on
> windows to do the occasional
> test of surefire on jdk 1.3. (I kept a vmware image since installing 1.3
> on linux required surrendering your first born to Sauron) All your
> c
On 16 July 2013 23:01, Arnaud Héritier wrote:
> > >
> >
> > Until Jenkins gets upgraded to 1.520+ at which point the (crappy in my
> > personal view) Maven job type will be unable to run 1.5
> >
> >
> The crappy one which doesn't work with Maven 3.1.0 too (I tested it this
> afternoon)
>
I'm su
On 16 July 2013 23:25, Barrie Treloar wrote:
> On 17 July 2013 07:31, Arnaud Héritier wrote:
> >> Can still keep trucking with a FreeStyle + Maven Build Step though (and
> I
> >> prefer that way anyway)
> >>
> >>
> >
> > Me too if we backport features from the crappy maven integration into the
On 17 July 2013 10:09, Olivier Lamy wrote:
> 2013/7/17 Olivier Lamy :
> > 2013/7/17 Stephen Connolly :
> >> On 16 July 2013 23:01, Arnaud Héritier wrote:
> >>
> >>> > >
> >>> >
> >>> > Until Jenkins gets upgraded to
which won't be soon for many of them
> (Myself I'm using the latest really stable one : the 1.480 LTS)
>
>
> On Wed, Jul 17, 2013 at 11:31 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > On 17 July 2013 10:09, Olivier Lamy wrote:
>
Why is 3.1.0 labelled as 3.1.0-alpha-1 (and why have we two 3.1.0-alpha-1
labels... I expect the same answer)
On 17 July 2013 21:01, Hervé BOUTEMY wrote:
> Le mercredi 17 juillet 2013 14:13:38 Paul Benedict a écrit :
> > Is 3.0.5 still the preferred version? I ask because the right-hand aside
>
If it's not in JIRA it doesn't exist
On 18 July 2013 17:18, sebb wrote:
> On 18 July 2013 16:35, Arnaud Héritier wrote:
> > There are open issues with the detail of changes to do ?
>
> Create N&L files for the top-level of SCM.
> As the source archive must be created from SCM, these N&L files
http://jira.codehaus.org/browse/MNG
On 18 July 2013 17:39, sebb wrote:
> Which JIRA would that be?
>
> On 18 July 2013 17:24, Stephen Connolly
> wrote:
> > If it's not in JIRA it doesn't exist
> >
> >
> > On 18 July 2013 17:18, sebb wrote:
&
+1
On Saturday, 20 July 2013, 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 last release w
On Sunday, 21 July 2013, Benson Margulies wrote:
> On Sun, Jul 21, 2013 at 1:52 PM, Robert Scholte
>
> >wrote:
>
> > Hi Benson,
> >
> > I don't understand, because deploy:deploy-file should be able to upload
> > pom + artifact + classified-artifacts at once.
> >
>
> There's no provision for uplo
Revert my change upping to RAT 0.9
Stupid plugin has major regression in performance, but 0.8 needs excludes
for git
If I'd had notice I'd have reverted it my self but on a phone so no access
to revert it... Once they get a proper usable release we *should* be ok...
Though they don't seem to know
+1 (binding)
On 23 July 2013 14:59, Stephen Connolly wrote:
> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baselin
This vote is to cover the minimum required version of Java for Maven Core.
Maven Plugins produced by the Apache Maven Project that are flagged as
compatible with older versions of Maven Core as their baseline will still
require to stick to the minimum Java requirements of that Maven Core
version.
On 23 July 2013 15:29, Lennart Jörelid wrote:
> +1000 which is a rather odd number for a vote; blame Stephen instead
> of me. :)
>
> I think we can skip the 1.6 release of the JDK as a Maven basis; JDK 1.6 is
> at or near EOL and the step from one
> minimum JDK version to another (i.e. JD
On Tuesday, 23 July 2013, Michael-O <1983-01...@gmx.net> wrote:
> Am 2013-07-23 15:59, schrieb Stephen Connolly:
>
>> This vote is to cover the minimum required version of Java for Maven Core.
>>
>>
> Given than most companies/folks react only when something has
+1
On Tuesday, 23 July 2013, Dennis Lundberg wrote:
> Hi,
>
> This is the final release of this plugin. After this release it will
> be retired, see separate vote thread for more info on that.
>
> We solved 1 issue:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11135&styleName=Ht
The split verifier should improve cli performance once core and most
plugins are on -target 1.6
Any committer is free to call a vote to up the minimum to 1.7 if they want
to.
>From a build tool perspective there are some advantages in 1.6 as a
baseline (compiler api, scripting api, split verifier
This is generally a tad tricky.
1. Because of class unloading it may not be possible to use the Hack-type
solution of stashing the data in a Class level static field. Though that
solution will work as long as the field uses a collection type that allows
for GC when the MavenProject that it is cach
that for build-helper. It was for many executions of the
> same mojo though, not sure how it behaves with different mojos.
> See
>
> http://mojo.10943.n7.nabble.com/build-helper-m-p-thread-safety-issue-td39561.htmland
> the ReserveListenerPortMojo
>
> My 2 cents.
>
>
t serializing the information somewhere in the
> ${project.build.directory} folder?
>
> Are there any issues I should aware of if I implement this solution?
>
>
> 2013/7/24 Stephen Connolly
>
> > Ahh yes... that's the one... I spent 3-5 min searching for it.
> >
>
+1
On 23 July 2013 20:45, Dennis Lundberg wrote:
> Hi,
>
> This will be the final release of this shared component. After this
> release it will retire from the Apache Maven project and move to the
> Apache Archiva project. See separate vote thread about that.
>
> We solved 6 issues:
>
> http:/
I'm all for it
On 24 July 2013 23:06, Dennis Lundberg wrote:
> Hi
>
> I've been going through our shared components making sure they all
> follow ASF branding rules. While doing this I became curious about a
> couple of the components that seemed alien to me. It turns out that of
> our 30 share
k and white... The answer can be grey... And everyone is
human so can make mistakes...
So community, what are you expecting?
- Stephen Connolly
On Thursday, 25 July 2013, wrote:
> Author: jdcasey
> Date: Wed Jul 24 23:21:58 2013
> New Revision: 1506778
>
> URL: http://svn.apach
; As a Maven user I think that everybody who is working on a project should
> > behave the same. Hence, I would say, PMC members should rather certainly
> > demonstrate how to live the community rules.
> >
> > -Ursprüngliche Nachricht-
> > Von: Stephen Connolly [
s us back to what does the community expect from its PMC?
> I ask rhetorically,
> to solicit answers, of course... and I see where this is going and what
> historical processes within Maven are being addressed.
>
>
> On Thu, Jul 25, 2013 at 4:05 PM, Stephen Connolly <
> ste
On 25 July 2013 22:34, Nigel Magnay wrote:
> >
> >
> > Should the PMC encourage people experimenting on new improvements to
> Maven
> > to do that work at the ASF? And if so, should they then practice what
> they
> > preach, and ensure that any experiments with Maven take place on the ASF
> > SCM
fics about specific individuals.
>
> Fred.
>
> On Fri, Jul 26, 2013 at 12:07 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > On 25 July 2013 22:34, Nigel Magnay wrote:
> >
> > > >
> > > >
> > > > Should th
On 23 July 2013 14:59, Stephen Connolly wrote:
> This vote is to cover the minimum required version of Java for Maven Core.
>
> Maven Plugins produced by the Apache Maven Project that are flagged as
> compatible with older versions of Maven Core as their baseline will still
> requ
://maven.apache.org/guides/mini/guide-using-toolchains.html which can
be used to simplify using a different JDK for compiling and running unit
tests.
Thank you.
-Stephen Connolly on behalf of the Maven Developers.
+1
On 27 July 2013 22:25, Dennis Lundberg wrote:
> Hi,
>
> We solved 4 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11241&styleName=Html&version=13719
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=tru
On Sunday, 28 July 2013, Robert Scholte wrote:
> Hi,
>
> Personally I'm not a huge fan of the release-model as done by Jenkins,
> meaning releasing once or twice a week with only a few fixes.
I am a really big fan of this model... But it won't work the same for
Maven...
Where the model falls do
http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/build-monitor-plugin/1.0+build.14/
Has anyone noticed that we don't seem to be encoding the + character when
mapping GAV to URL?
And we haven't had the vote thread yet... so still time for rot13:froo to
chime in again!
On 29 July 2013 15:06, Baptiste MATHUS wrote:
> 2013/7/29 Fred Cooke
>
> > On Mon, Jul 29, 2013 at 3:57 PM, Baptiste MATHUS wrote:
> >
> >> 2013/7/29 Fred Cooke
> >>
> >> > Tag deleted? :-/
> >> >
> >>
I find the lure of the custom scopes to be a siren's call.
There are maybe 2-3 "missing" scopes. all other needs are better addressed
with a different project structure in my view.
We have the separation between test and non-test... but test is an all or
nothing... need the symmetry between the n
on. The "exported"
transitive dependencies will fit neatly into the existing scopes, but you
would like a simplified *build time* configuration?
> 2013/7/30 Stephen Connolly :
> > I find the lure of the custom scopes to be a siren's call.
> >
> > There are maybe
question for
plugins, IMHO
On 30 July 2013 15:39, Francesco Mari wrote:
> Correct. I don't want to duplicate the configuration twice, the first
> time in my plugin and the second time in the section to
> let Maven correctly compute the build plan.
>
> 2013/7/30 Stephen Conno
This looks to be https://builds.apache.org/job/maven-indexer going to
Failed... somebody needs to fix the $DEFAULT_CONTENT in the editable email
template as a token parse error is rendering email notification kind of
useless
On 31 July 2013 12:24, Apache Jenkins Server wrote:
> The Apache Jenkin
I have updated the project-roles with my thoughts resulting from the
healthy debate on the list and some debates elsewhere.
If anyone wants to look at the resulting Work In Progress document as a
whole:
http://svn.apache.org/viewvc/maven/site/trunk/content/markdown/project-roles.md?revision=150959
ly the core of the concerns... the extra diligence required to
> consume large bodies of work is bigger. That doesn't mean that code
> contributions are inherently bad just because they were developed
> elsewhere, it's just harder to pull in.
>
Correct.
>
> On Fri,
Committers... but keep in mind that none of us
enjoy that!!!
>
> Regards,
> Curtis
>
> P.S. For those interested, Stephen's changes are more clear when reading
> the side-by-side diff:
>
> http://svn.apache.org/viewvc/maven/site/trunk/content/markdown/project-rol
On 2 August 2013 16:32, Paul Benedict wrote:
> Furthermore, I'd like to see explicit procedural rules on Maven Core and
> forking. For example, if there's a critical component needing development
> for Core, and a PMC expresses that such development will be done outside of
> Apache and then used
pment outside of Apache. The vote
> would lead to a consensus, no?
>
>
> On Fri, Aug 2, 2013 at 10:41 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > On 2 August 2013 16:32, Paul Benedict wrote:
> >
> > > Furthermore, I'd like
ther. The
> other OSS community has other committers, other mailing lists, other
> deliberations, etc. Community work and input becomes marginalized here.
>
> Does this make sense to you? That kind of community-splitting effort needs
> to stop and that's what I am trying to ad
ted anywhere? I searched but
> failed.
>
> I assume Cat A = permissive and Cat B = copyleft? or?
>
> On Fri, Aug 2, 2013 at 6:54 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > Correct. And it would be subject to the same CTR and potential veto if
&
- Stephen
On Friday, 2 August 2013, Stephen Connolly wrote:
> On 2 August 2013 16:07, Brian Fox 'cvml', 'bri...@infinity.nu');>> wrote:
>
>> I think the bulk of this is pretty good. On the fork section,
>> specifically:
>>
>> "
>&
On 8 August 2013 02:12, Olivier Lamy wrote:
> mvn clean install -pl :maven-scm-provider-jgit -am
works on my mac
http://javaadventure.blogspot.ie/2012/07/do-you-want-to-become-maven-committer.html
On 8 August 2013 01:37, Jigar Joshi wrote:
> I want to check in some code in maven
>
> How can I have svn access
>
> Thanks!
> Jigar
>
+1
On 11 August 2013 00:09, Dennis Lundberg wrote:
> Hi,
>
> This is a new shared component consisting of code from Maven WAR
> Plugin, that has been repackaged for reuse by other plugins.
>
> We solved 1 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Htm
On 14 August 2013 09:47, sebb wrote:
> On 13 August 2013 18:58, Dennis Lundberg wrote:
> > On Tue, Aug 13, 2013 at 12:30 AM, sebb wrote:
> >> On 12 August 2013 20:10, Jason van Zyl wrote:
> >>>
> >
> > I have now read the threads that are referring to, and have not found
> > a sing
1 - 100 of 2711 matches
Mail list logo
