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 technology (old: directories, new: Nexus) to
ensure that artifacts don't esca
-1 binding to changing to burning versions.
On Sun, Jun 2, 2013 at 10:56 AM, Ralph Goers wrote:
> -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.
On Sun, Jun 2, 2013 at 2:42 PM, Fred Cooke wrote:
>> from my experience, even if this question is not absolutely scm-specific,
>> git
>> brings us a new problem we didn't have with svn: once a tag is set on the
>> canonical repo and replicated on developers' repos, it is not automatically
>> updat
* this action."
>
> +1 + -1 != 0
>
> On Sun, Jun 2, 2013 at 8:55 PM, Benson Margulies wrote:
>
>> On Sun, Jun 2, 2013 at 2:42 PM, Fred Cooke wrote:
>> >> from my experience, even if this question is not absolutely
>> scm-specific,
>> >> git
&
t;, not "procedural" issues .
>
> Cheers
>
>
> 2013/6/2 Fred Cooke
>
>> Benson, read the rules:
>>
>> http://httpd.apache.org/dev/voting.html
>>
>> "*-1 *No, I *veto* this action."
>>
>> +1 + -1 != 0
>>
>&g
I would consider it delux if the release plugin were enhanced to
support a more sophisticated mapping between artifact versions and
tags -- as per Kristian, wouldn't it be cool if it could iterate over
tags while repeating itself on customer-visible release numbers? I'd
help to code this is we had
On Sun, Jun 2, 2013 at 8:44 PM, Fred Cooke wrote:
> Although I prefer to use Git, it's totally irrelevant. I'm unsure how you
> came to the conclusion that I thought this was anything to do with Git.
> Subversion tags, though mutable, should not EVER be committed against or in
> any other way modi
On the one hand, I think that, in many Apache communities, comparing the
source release to the VCS is the exception and not the rule, and may never
have happened, even once. (I think that there is at least an even chance
that some crusty veteran of httpd will arrive in this thread and call me
out o
> >
> > So, if everyone here likes this idea, by all means let's do that. On the
> > other hand, if there is no consensus here, I wish that the Foundation
> had a
> > clearer venue for discussing global policies like this.
>
> I hope I don't have to argue that it is ASF policy to only release
> sou
Other than in the source of the deploy plugin, do we have a document for
'deploy'?
I sporadically run into the fact that the command-line deploy plugin isn't
so hot when one has multiple classified objects.
On the one hand, I'm thinking of creating deploy:deploy-files (note the
's') with some sch
ts in a single transation.
>
> Robert
>
>
> Op Sun, 21 Jul 2013 19:40:04 +0200 schreef Benson Margulies <
> bimargul...@gmail.com>:
>
>
> Other than in the source of the deploy plugin, do we have a document for
>> 'deploy'?
>>
>> I spora
On Sun, Jul 21, 2013 at 2:26 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On Sunday, 21 July 2013, Benson Margulies wrote:
>
> > On Sun, Jul 21, 2013 at 1:52 PM, Robert Scholte
> > >wrote:
> >
> > > Hi Benson,
> > >
> >
On Sun, Jul 21, 2013 at 2:29 PM, Benson Margulies wrote:
>
>
>
> On Sun, Jul 21, 2013 at 2:26 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>> On Sunday, 21 July 2013, Benson Margulies wrote:
>>
>> > On Sun, Jul 21, 2
The Apache Software Foundation releases open _source_ products. If one
of our users wants to build the product from source, instead of using
our convenience binaries, we should be helping, not pushing them to
the binaries.
On Thu, Nov 7, 2013 at 8:37 AM, Baptiste Mathus wrote:
> Hi,
> I'm under t
I've just coded up the answers to two checkstyle issues that are a
major itch for me and committed them. There are some jiras complaining
of doc issues, I plan to see if I can fix them up. After that, I'd
like to release 2.11, and will do so in a day or two if I hear no
objections.
---
http://maven.apache.org/developers/release/maven-project-release-procedure.html
says so. I don't know where I'm going to get that environment.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-
Hi,
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=19110&styleName=Text&projectId=11127&Create=Create&atl_token=ACIO-CAVI-QX7G-9IAS%7C963c6bebb9ceae25b98c7c7add910785a302a0b4%7Clin
(or see below)
There are still a couple of issues left in JIRA:
http://jira.codehaus
On Wed, Nov 13, 2013 at 10:54 AM, Stephen Connolly
wrote:
> On 27 October 2012 22:00, wrote:
>
>> Author: bimargulies
>> Date: Sat Oct 27 21:00:24 2012
>> New Revision: 1402867
>>
>> URL: http://svn.apache.org/viewvc?rev=1402867&view=rev
>> Log:
>> MPOM-38: Enable RAT to help us get maven release
On Wed, Nov 13, 2013 at 11:33 AM, Stephen Connolly
wrote:
> The profiles are not being activated... this is why in the asf pom we use
> the -P... in the tag
Why aren't the profiles activated? Does 'arguments' disable 'releaseProfiles'?
>
>
> On 13 Nove
IT (SCM-709), so for the apache-pom we
> should either stay on m-release-p 2.3.2 or m-release-p 2.4.2 with scm-1.7
> (if possible)
>
> Robert
>
> [1] https://jira.codehaus.org/browse/MRELEASE-459
>
> Op Wed, 13 Nov 2013 17:50:02 +0100 schreef Benson Margulies
> :
>
&
I realize that I've rarely been seen to do the work of checking and
voting for other people's releases, but none the less here I am
begging for one more vote on mine. I promise to pitch in more in the
future.
-
To unsubscribe, e-m
This vote has passed with the following results:
+1 (binding): bimargulies, olamy, hboutemy
I will promote the artifacts to the central repo.
On Thu, Nov 14, 2013 at 1:22 PM, Hervé BOUTEMY wrote:
> +1
>
> Regards,
>
> Hervé
>
> Le lundi 11 novembre 2013 19:36:29 Ben
-- Forwarded message --
From: Benson Margulies
Date: Sat, Nov 16, 2013 at 9:07 AM
Subject: [ANN] Apache Maven Checkstyle Plugin 2.11 Released
To: annou...@maven.apache.org, Maven Users List
Cc: e...@maven.apache.org
The Apache Maven team is pleased to announce the release of
http://maven.apache.org/plugins/maven-scm-publish-plugin/examples/one-module-configuration.html
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
than regenerating a new documentation
>>
>> Regards,
>>
>> Hervé
>>
>> Le samedi 16 novembre 2013 14:32:00 Benson Margulies a écrit :
>>> http://maven.apache.org/plugins/maven-scm-publish-plugin/examples/one-module
>>> -configurat
+1
> On Nov 17, 2013, at 12:50 PM, Stephen Connolly
> wrote:
>
> It can wait for next release, I'm staged already and just need one more
> binding vote and most of the 72h are expired already
>
>
>> On 17 November 2013 12:02, Michael-O <1983-01...@gmx.net> wrote:
>>
>> Am 2013-11-15 00:59, schri
It seems to me that this thread is mixing two topics.
Topic #1: How to we move to pom 5.0, given a giant ecosystem of crappy
XML-parsing POM consumers?
Topic #2: To what extent does the pom mix a 'description of contract'
(dependencies, etc) with a 'specification of build'?
On the first topic, t
I have one more remark to contribute to this.
In my view, the first step should be to make a 4.0-beta version of
Maven that has a '5.0.0' pom that is _identical_ to the 4.0.0 pom. The
difference is that we will document, after the fashion of HTML5, our
intent to change it over time. We can then ad
I dunno, change the version to 2.0 and remove support for CVS?
On Mon, Dec 2, 2013 at 8:57 PM, Olivier Lamy wrote:
> On 3 December 2013 12:52, Bernd Eckenfels wrote:
>> Am 03.12.2013, 02:47 Uhr, schrieb Olivier Lamy :
>>
>>> For some reasons I don't understand yet why defaultExclude=false
>>> do
On Sun, Dec 15, 2013 at 5:30 PM, Hervé BOUTEMY wrote:
> nice!
>
> the first step IMHO is to add deployAtEnd feature: you're a specialist :)
>
> then, deploy should detect "scm:" url to avoid classical wagon deployment but
> instead:
> 1. stage content when not at end
> 2. scm-publish when at end
>
intervening target/site
directories so that the links work. OK, so, here comes another stupid
suggestion: make a mode of the site plugin in which we don't need
site:stage, because site:site in a multi-module build directly writes
to TOPLEVEL/target/site/WHATEVER. That requires some way to
co
A large, not very bright, species of deer that wears giant antlers and
attacks what it doesn't understand. If that's what strikes you all as
a great metaphor for us, Maven, or both, go right ahead.
-
To unsubscribe, e-mail: dev-un
nimals you can render for a
> 75px tall image placeholder...
>
> But seriously, we just want something that is more than just our name in a
> fancy font. I think we need a mascot to help drive us onwards...
>
> -Stephen
>
>
>
> On 18 December 2013 13:27, Benson Margu
globe
>
>
>> On 18 December 2013 15:20, Benson Margulies wrote:
>>
>> Personally, I think we need a new POM version to drive us forward.
>>
>> As a visual goes, I'd look for something like a beaver (who builds
>> things) wearing geek eye-glasses (indicating &#
n 18 December 2013 15:38, Jason van Zyl wrote:
>
>> On Dec 18, 2013, at 10:20 AM, Benson Margulies
>> wrote:
>>
>> > Personally, I think we need a new POM version to drive us forward.
>> >
>>
>> I agree. If no one else gets to it I'll write u
A user asked for one. I'll do the mechanics if there's nothing
standing in the way.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I ran one build of maven-wagon as a warmup for releasing. No problems.
All subsequent attempts have died in the http wagon tests, with a
variety of failures.
Has anyone got some reliable way to run these builds?
-
To unsubscribe
+1 from me.
On Sun, Dec 29, 2013 at 9:36 PM, Benson Margulies wrote:
> Hi,
>
> We solved 3 issues:
>
>
> ** Improvement
> * [WAGON-401] - Access Denied due to missing User-Agent
> * [WAGON-402] - Upgrade Apache HttpClient based wagon provider to
> HttpClient 4.
Hi,
We solved 3 issues:
** Improvement
* [WAGON-401] - Access Denied due to missing User-Agent
* [WAGON-402] - Upgrade Apache HttpClient based wagon provider to
HttpClient 4.3
* [WAGON-403] - SSH agent support for wagon-ssh
There are still a couple of issues left in JIRA:
http://ji
ssed after multiple runs. I am using java 7 and maven
> 2.2.
>
> I'm not sure what the build process is that you are running but if there is
> some documentation somewhere I'd be willing to try to reproduce locally and
> try to submit a fix.
> Let me know.
>
> D
That wagon release is out there to help a user, and awaits two PMC members.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi,
The vote has passed with the following result:
+1 (binding): bimargulies, Stephen Connolly, Robert Scholte
+1 (non binding): Dan Beaulieu
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail: dev-unsub
+1 binding, it looks oK here.
On Wed, Jan 1, 2014 at 5:47 PM, Olivier Lamy wrote:
> +1
>
> On 29 December 2013 09:01, Tony Chemit wrote:
>> Maven shared JarSigner 1.3
>> --
>>
>> The version 1.3 just fix an important bug while unsigning jar.
>>
>> We solved 1 issues:
>> h
Did you log into repository.apache.org?
On Mon, Jan 6, 2014 at 1:44 PM, Dominik Bartholdi wrote:
>
> Hey guys,
> I finally started the release of scm-1.9 - I was able to stage the artifacts,
> but now , following this process
> http://www.apache.org/dev/publishing-maven-artifacts.html#close-sta
Are you imod? If so, the repo is sitting there. I can close it for
you, but you should try logging in and closing it for yourself.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h..
Why isn't this copied to the dev list?
I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
remotely under consideration. It is a proposal, to start with, to add
an element to the POM:
some text
...
which would make it a job for 4.0. It was never my inten
On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
wrote:
> On 13 January 2014 16:13, Benson Margulies wrote:
>>
>> Why isn't this copied to the dev list?
>
>
> It was, check the headers
I see. GMail has learned a new prank, which is to skip 'dev' in t
Done.
On Mon, Jan 13, 2014 at 12:53 PM, Benson Margulies
wrote:
> On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
> wrote:
>> On 13 January 2014 16:13, Benson Margulies wrote:
>>>
>>> Why isn't this copied to the dev list?
>>
>>
>> It
I am
> willing to listen and learn.
>
>
> On Mon, Jan 13, 2014 at 10:59 AM, Stephen Connolly
> wrote:
>>
>> On 13 January 2014 16:13, Benson Margulies wrote:
>>
>> > Why isn't this copied to the dev list?
>> >
>>
>> It was, check
I am experimenting with a new wagon. I see various plexus
'annotations' in the comments, but the packaging in the pom is plain
old jar. How does this get turned on?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For ad
xample in the Maven
> Core POM.
>
> On Jan 15, 2014, at 7:36 AM, Benson Margulies wrote:
>
>> I am experimenting with a new wagon. I see various plexus
>> 'annotations' in the comments, but the packaging in the pom is pl
n.
> But it seems there's more to it.
>
> Robert
>
> Op Wed, 15 Jan 2014 16:17:29 +0100 schreef Benson Margulies
> :
>
>
>> OK, I got it all going. Thanks.
>>
>> On Wed, Jan 15, 2014 at 8:23 AM, Jason van Zyl wrote:
>>>
>>> Ultimately
I really didn't follow the thread from my private experiment with a
trick wagon to an update to Aether in Maven. Thanks for the help, I
got my experiment to work, and, again, no one need be concerned about
my messing about in the Aether, either.
How about asking also asking this question: should all the function
currently in packaging need to be extensions? What users want is to
define certain kinds of things as one big build.
On Sun, Jan 19, 2014 at 4:06 PM, Jason van Zyl wrote:
> Sure, so this issue I think can be closed and another on
+1 here.
On Mon, Jan 20, 2014 at 1:12 PM, Anders Hammar wrote:
> +1 on clean up if we communicate this (and explain why).
> 0 on move
>
> /Anders
>
>
> On Mon, Jan 20, 2014 at 6:53 PM, Dominik Bartholdi wrote:
>
>> +1 cleanup is a really good idea!
>>
>> On 20.01.2014, at 18:50, Arnaud Héritier
There's a 'rumor' that I made a mistake editing the parents some
months back that has made component releases clumsy. I think I took
out an explicit profile spec that I mistakenly thought was obviated by
the profile feature of the m-r-p. If someone can send me a reminder
I'll repair, unless someone
Since the mailing list archive links on
http://plexus.codehaus.org/mail-lists.html are dead, I thought that
I'd probably reach relevant people here.
I'm using Sisu/Guice in a project, and I'm looking for a _lightweight_
way to add classpath isolation. OSGi goes not qualify. Does anyone
still care
oks like more Google people are
> working on it now than Square employees. This looks like the successor to
> Guice and is 24 classes currently, easy to read and works super well in
> constrained environments like Android and therefore is super fast for normal
> applications.
>
>
On Sat, Feb 8, 2014 at 12:32 PM, Benson Margulies wrote:
> On Sat, Feb 8, 2014 at 12:22 PM, Jason van Zyl wrote:
>> The original Plexus implementation is dead and has been for quite a while,
>> even for us. We don't actually use Plexus the container anymore. The
>> ex
On Tue, Feb 11, 2014 at 2:48 PM, Igor Fedorenko wrote:
>> 890593b10fe868f57fa52e37aacdaa05d8803bd4
+1 (binding). It would be helpful if the template said that the
checksum was sha1 :-)
-
To unsubscribe, e-mail: dev-unsubscr...@m
3.2.0.1 :-)
On Tue, Feb 11, 2014 at 7:42 PM, Tony Chemit wrote:
> On Wed, 12 Feb 2014 00:29:58 +
> Stephen Connolly wrote:
>
>> Hurrah! At last!
>>
>> (at least until the "there must be a .0 release or the world will end" gang
>> on the PMC bash us back to 3.2.0)
>
> Stephen, I won't survive
+1
On Thu, Feb 13, 2014 at 10:14 AM, Stephen Connolly
wrote:
> We have not made a release of Maven 2.x since 2.2.1 which was August 2009.
>
> During that period no release manager has stepped up to cut a release.
>
> I would argue that we should just therefore just declare Maven 2.x as end
> of l
On Thu, Feb 13, 2014 at 10:30 AM, Jason van Zyl wrote:
>
> On Feb 13, 2014, at 10:03 AM, Stephen Connolly
> wrote:
>
>> On 13 February 2014 14:51, Jason van Zyl wrote:
>>
>>> I've proposed the shorter vote period and criteria for releasing. I think
>>> if the ITs pass and it is for fixes to reg
On Feb 13, 2014 10:47 AM, "Jason van Zyl" wrote:
>
>
> On Feb 13, 2014, at 10:38 AM, Benson Margulies
wrote:
>
> >>
> >
> > EOL is an Apache Thing. If we're not going to fix it, it's considered
> > polite to EOL it.
>
> Then I d
Looking for common ground here, how about we start by documenting the core
release procedure so that someone else could plausibly take a turn? Without
knowing the details of the release process, I don't see how I could disagree
with JvZ.
It mostly seems to me that Stephen's desired schedule co
Looking for common ground here, how about we start by documenting the core
release procedure so that someone else could plausibly take a turn? Without
knowing the details of the release process, I don't see how I could disagree
with JvZ.
It mostly seems to me that Stephen's desired schedule co
There's an Apache nuance to highlight here.
We may not advertise non-voted items to the general public. We may
offer non-voted items to engaged community members.
I do not know enough about Eclipse to offer an intelligent comparison.
--
A bit of a recap:
Let's say that our goal as a group was to be very responsive to user's
bug reports.
So, we'd want to make fixes and releases, 'promptly', for some
definition of prompt.
But no one will install those releases if they are not confident that
they are, in fact, not going to have un
;
>> I don't see any necessity to restrict patch releases to patches only -- as
>> long as any new functionality is a tiny enhancement and doesn't make
>> incompatibilities. Save medium/major structural changes for a new minor
>> version.
>>
>>
>>
Register for an xircles account on Codehaus and you will have JIRA access.
Commit comes from sustained participation.
On February 20, 2014 8:33:12 AM EST, Ashish Patel
wrote:
>Hi,
>
>What would it take for me to get JIRA access to create tickets and/or
>comment?
>
>I would like to add patch fil
On Thu, Feb 20, 2014 at 4:27 PM, Jason van Zyl wrote:
>
> On Feb 20, 2014, at 1:07 PM, Dennis Lundberg wrote:
>
>> Hi Jason
>>
>> While I'm finally starting to see the potential with a DVCS like git,
>> there are a couple of things that stands in the way of migrating, for
>> example plugins, to g
I checked out the trunk and tried a simple 'mvn test', and I'm
drowning in test failures. Anyone have a hint?
---
Test set: org.apache.maven.shared.release.DefaultReleaseManagerTest
3.0.5 java 7
On February 21, 2014 1:44:06 PM EST, Patrick Decat wrote:
>Hi Benson,
>
>is that with Maven 3.2.1?
>
>I'm having random test failures with 3.2.1 on some projects.
>Switching back to 3.1.1, everything's fine.
>
>Regards,
>Patrick.
>
>
>
>--
>View this message in context:
>http://mave
tionFailure: file
>> org\codehaus\plexus\component\annotations\Component.class not found
>>
>> I doubt that Sun (Oracle) will accept bug reports for Java 5
>though...
>>
>> Any idea on what could be the cause?
On Sat, Feb 22, 2014 at 7:38 AM, Robert Scholte wrote:
> src/test/resources/org/apache/maven/shared/release/phase
I'm trying to use a less ancient version of plexus-container-default,
it requires some test changes, I'll let you know what happens.
-
over. I am checking if I can make it go
away. the scm component error is gone, or at least hiding.
On Sat, Feb 22, 2014 at 11:44 AM, Benson Margulies
wrote:
> On Sat, Feb 22, 2014 at 7:38 AM, Robert Scholte wrote:
>> src/test/resources/org/apache/maven/shared/release/phase
>
>
Further down the message, this boils down to a failure to find an
ArtifactResolver.
On Sat, Feb 22, 2014 at 12:04 PM, Benson Margulies
wrote:
> Plexus-container-default 1.5.5 changes some issues.
>
> This seems to make some things better.
>
> The first failure is:
>
> testN
ipe.java:466)
... 43 more
On Sat, Feb 22, 2014 at 12:29 PM, Igor Fedorenko wrote:
> You need to add maven-compat as a dependency.
>
> --
> Regards,
> Igor
>
>
> On 2/22/2014, 12:27, Benson Margulies wrote:
>>
>> Further down the message, this boils down to a failu
I'm sorry, I did mislead you. Not surprisingly, adding maven-compat
did not fix the problem with the apparently unmodifiable list.
On Sat, Feb 22, 2014 at 12:33 PM, Benson Margulies
wrote:
> I may have misled you, but I'll try it.
nko wrote:
> What version of Maven does release plugin depend on? I think
> DefaultArtifactTransformationManager.initialize was removed in 3.x, at
> least it's not present in 3.2.1 and 3.1.1.
>
> --
> Regards,
> Igor
>
>
> On 2/22/2014, 12:35, Benson Margulies w
> serious issue here.
>
> Robert
>
> Op Sat, 22 Feb 2014 18:48:53 +0100 schreef Benson Margulies
> :
>
>
>> Still 2.2.1.
>>
>> So, in version 2.2.1,
>> org.apache.maven.artifact.transform.DefaultArtifactTransformationManager
>> tries to patch a l
flecting the claims of others.
>
> Robert
>
> Op Sat, 22 Feb 2014 19:12:05 +0100 schreef Benson Margulies
> :
>
>> This, of course, does not help the people pining for the git support in
>> 1.9.
>>
>>
>> On Sat, Feb 22, 2014 at 1:10 PM, Robert Scholt
I am willing to do the work of RM'ing what we have here, since no one
out there will test anything before it's released.
On Sat, Feb 22, 2014 at 1:34 PM, Benson Margulies wrote:
> On Sat, Feb 22, 2014 at 1:23 PM, Robert Scholte wrote:
>> I've only changed maven-scm-ma
ve forward.
>
> On Feb 22, 2014, at 10:34 AM, Benson Margulies wrote:
>
>> I am willing to do the work of RM'ing what we have here, since no one
>> out there will test anything before it's released.
>>
>>
>> On Sat, Feb 22, 2014 at 1:34 PM, Benson M
Jason, I can't help suspecting that the first step in housecleaning
here will be a new-tech SCM release, do you think so?
On Sat, Feb 22, 2014 at 1:56 PM, Benson Margulies wrote:
> Seems to me we might as well make one last release with what's there
> now, just in case it hel
How much longer with this Java 1.5 business? It' a giant pain.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
The business of being required to use it in all Maven releases, which
adds a layer of VM complexity to my process.
On Sat, Feb 22, 2014 at 2:31 PM, Dennis Lundberg wrote:
> Which business are you referring to?
>
> On Sat, Feb 22, 2014 at 8:02 PM, Benson Margulies
> wrote:
>&g
pdating scm. I think users on Git are also more likely to be on
> m3 which is where the scm issues are yes? If you want to cut a quick release
> for 2.x users I would try and leave as many of the existing deps alone.
>
> jvz
>
>> On Feb 22, 2014, at 10:58 AM, Benson Marguli
I can't built the m-r-p with Java 1.5. The compiler plugin fails.
Don't we have source and target set so that I can leave JAVA_HOME at
1.6 and still cut a release?
On Sat, Feb 22, 2014 at 5:13 PM, Benson Margulies wrote:
> That's my plan. Cut a release with things as they
I've staged 2.5 of the maven-release component. However, the
documentation staging process is failing.
mvn -Preporting site site:stage
does not write into the ~/maven-sites directory where the scm plugin expects it.
Could some kind soul either checkout the tag and patch this up and
stage it,
Hi,
maven-release is a component that provides the maven-release-manager
and the maven-release-plugin.
This release integrates version 1.9 of Maven SCM, which addresses a
number of problems with git.
We resolved 10 issues:
** Bug
* [MRELEASE-166] - release:prepare should always check for
+1 - binding.
On Sun, Feb 23, 2014 at 9:49 AM, Benson Margulies wrote:
> Hi,
>
> maven-release is a component that provides the maven-release-manager
> and the maven-release-plugin.
>
> This release integrates version 1.9 of Maven SCM, which addresses a
> number of prob
Never mind, I found the shell script left behind by the last person
who did this. I
On Sun, Feb 23, 2014 at 7:38 AM, Benson Margulies wrote:
> I've staged 2.5 of the maven-release component. However, the
> documentation staging process is failing.
>
> mvn -Preporting site si
work but for now I didn't investigate. I'm
>not sure if something was reported about it. —
>Sent from Mailbox for iPhone
>
>On Sun, Feb 23, 2014 at 3:50 PM, Benson Margulies
>
>wrote:
>
>> Hi,
>> maven-release is a component that provides the maven-releas
I propose to make releases of our parent stack that are suitable for
components and plugins that are making the leap to Java 1.6 and Maven
3 as their base requirements.
What do people think is the right approach in terms of what stays on
trunk and what goes on a branch, and whether to do anything
h plugins requiring java 1.6 and maven
> 3.2.1 as a minimum, but I'd rather see 3.3.x get some legs first and I
> suspect we'll have a few 3.2.x releases as we have EOL'd 2.x
>
> On Sunday, 23 February 2014, Benson Margulies wrote:
>
>> I propose to make releases
For this thread, I'd be content to get a plan for how to manage the
poms to reflect the EOL of 2.x. The actual content of those poms can
argued over by committing an initial proposal.
On Sun, Feb 23, 2014 at 1:50 PM, Benson Margulies wrote:
> I would have expected our first step would b
at we are moving to only checking java
>1.5
>compat via animal sniffer and that we will be building plugins with 1.6
>or
>1.7
>
>On Sunday, 23 February 2014, Benson Margulies
>wrote:
>
>> For this thread, I'd be content to get a plan for how to manage the
>>
So, my 'maven 3' parent project comes after this, in case anyone wonders.
On Sun, Feb 23, 2014 at 3:55 PM, Hervé BOUTEMY wrote:
> I'm still on ASF parent: Maven parent POMs will be later
>
> Regards,
>
> Hervé
>
> Le dimanche 23 février 2014 21:25:35 Michael Osipov a écrit :
>> Am 2014-02-01 11:2
.
On Sun, Feb 23, 2014 at 3:38 PM, Michael Osipov wrote:
> Am 2014-02-23 21:20, schrieb Stephen Connolly:
>
>> On Sunday, 23 February 2014, Michael Osipov wrote:
>>
>>> Am 2014-02-23 19:06, schrieb Benson Margulies:
>>>
>>>> I propose to make re
1 - 100 of 1315 matches
Mail list logo
