Arnaud Héritier a écrit :
> On Wed, May 29, 2013 at 7:39 AM, Hervé BOUTEMY wrote:
> > good idea: can you open a Jira issue?
>
> Done : https://jira.codehaus.org/browse/MNG-5482
> Another probably more stupid idea : Wasn't it possible to use the shade
> plugin or someth
I agree with Dan and Wayne
+1 for "qualified" releases (alpha, beta, RC, etc…) that are working toward the
full blow release but aren't intended to be that.
-1 for the actual releases.
And I don't care if the next 3.1.0-alpha is alpha-2 or alpha-4: what I care is
that it is not alpha-1 any mor
https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
page created
improvements welcome
Regards,
Hervé
Le jeudi 30 mai 2013 09:10:50 Arnaud Héritier a écrit :
> Perfect. Thx
>
> On Thu, May 30, 2013 at 3:27 AM, Hervé BOUTEMY wrote:
> > MNG-5482 fixed: ok for me
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
but I'm interested by the "it would be auto-installable" objective at least on
Apache's Jenkins instance
so I'll read any pointer
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 is something call
yes, the vote for one unique rule is clearly "-1"
but as I see, there seems to be a consensus around a 2-sided rule:
- don't reuse version number for pre-releases (RC, etc)
- reuse version number for actual releases
Regards,
Hervé
Le samedi 1 juin 2013 08:27:38 Stephen Connolly a écrit :
> I wi
alid version nos, so I think that
> the no re-spin rule should still apply in the same manner.
>
> -Chris
>
> On Sat, Jun 1, 2013 at 8:41 PM, Hervé BOUTEMY wrote:
> > yes, the vote for one unique rule is clearly "-1"
> >
> > but as I see, there seems to
> what is the error message ? and svn url you are using ?
>
> 2013/5/29 Eric Barboni :
> > Sorry, but Maven sandbox is write protected for me.
> >
> > I created a svn patch file but I don't know where to fill the issue
> > (project, component in jira).
&g
+1
Regards,
Hervé
Le samedi 1 juin 2013 09:13:17 Jason van Zyl a écrit :
> Here are the release bits for 3.1.0-alpha-1:
>
> Release notes:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
> 967
>
> Staging repository:
> https://repository.apache.org/content/reposi
I added the Android Maven Pugin to
https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
Do you have any issue tracking reference to link to?
On fixing the issue: I had a very quick look at your poms, and IIUC, you're
using much Aether API directly from your plugin code. With s
Hervé BOUTEMY a écrit :
> I added the Android Maven Pugin to
> https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
>
> Do you have any issue tracking reference to link to?
>
>
> On fixing the issue: I had a very quick look at your poms, and IIUC, you'
I just committed the distro into the dist area, to let it spread to mirrors
Regards,
Hervé
Le jeudi 6 juin 2013 13:20:19 Jason van Zyl a écrit :
> I've pushed in the initial cut at the release notes if anyone wants to take
> a look:
>
> http://svn.apache.org/r1490364
>
> I will push out the bi
tooling for mobiles can go as fast as mobiles: lucky man not requiring too
much backward compatibility :)
Regards,
Hervé
Le vendredi 7 juin 2013 12:03:25 Manfred Moser a écrit :
> > I added the Android Maven Pugin to
> > https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
> >
n be fixed.
> Somewhere next week I'll prepare the release, so if others like to fix
> some issues for this version, it should be done quickly ;)
>
> Robert
>
> Op Fri, 07 Jun 2013 08:20:01 +0200 schreef Hervé BOUTEMY
>
> :
> > I added the Android Maven Pugin
vendredi 7 juin 2013 12:45:49 Jason van Zyl a écrit :
> How long does it take for the site to publish? I don't see the release notes
> for 3.1.0-alpha-1 up there yet:
>
> http://maven.apache.org/docs/3.1.0-alpha-1/release-notes.html
>
> On Jun 7, 2013, at 2:31 AM, Hervé BOU
the dist area so it should be on the mirrors, and everything is
> synced to Central.
>
> I think we're ready for the announcement. Anything else need to be done?
>
> On Jun 7, 2013, at 5:27 PM, Hervé BOUTEMY wrote:
> > modifications are only staged, available on maven.s
done
Regards,
Hervé
Le lundi 10 juin 2013 08:50:34 Andreas Gudian a écrit :
> Hi,
>
> The vote has passed with the following result:
>
> +1 (binding): Kristian Rosenvold, Olivier Lamy, Mark Struberg
> +1 (non binding): Matthias Fraass, Karl Heinz Marbaise, Mirko
> Friedenhagen, Andreas Gudian
Thanks to Eric, we now have a tool to check dist content
And I just added it to our Jenkins instance, to build once a day: you can look
at the result [1]
I just had to remove the preview of site, since Firefox isn't available on the
CI server (or not able to start in headless mode)
Any feedback
yes, there doesn't seem to be much people reporting any issues.
Do we have any meaning of measuring the use of this new version?
I'm missing time at the moment to work on code.
But I'd like to work on little POM schema additions, like encoding
configuration: the precise list of additions that can
o.
> > Give me a couple of days.
> >
> > Robert
> >
> > Op Wed, 19 Jun 2013 00:11:55 +0200 schreef Hervé BOUTEMY
> >
> > :
> >> Thanks to Eric, we now have a tool to check dist content
> >>
> >> And I just added it to our Jenkins
(oracle
> >
> > version) they found jdk 7, jdk 6 is shown as end of life (with security
> > warning everywhere).
> >
> >Side effect is that, you play with the new features. (student later
> >
> > learn backward compatibility)
> >
> >
Le mardi 25 juin 2013 17:52:20 sebb a écrit :
> And it's not unknown for spurious files to creep into a release
> (perhaps from a stale workspace - are releases always built from a
> fresh checkout of the tag?)
we use the release plugin, which does the release from a fresh checkout (FYI
causing pr
Le mardi 25 juin 2013 21:15:11 Uwe Schindler a écrit :
> This is a slightly different
> workflow, but is proven to work since years now.
great workflow
here, at maven project, we use release plugin: this is a slightly different
workflow, but is proven to work since years now.
Regards,
Hervé
---
the jar content isn't updated: so you have jar artifacts inconsistent with svn
Le mercredi 26 juin 2013 01:08:59 sebb a écrit :
> On 26 June 2013 01:04, Chris Graham wrote:
> > -1
> > Except then the poms will point to the wrong place.
>
> Depends how the poms are updated.
>
> > On Wed, Jun 26,
+1
easy to use, very powerful, and produces artifacts consistent with scm
and for those who didn't read the doc: prepare [1] and perform [2]
[1]
http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html
[2]
http://maven.apache.org/maven-release/maven-release-plug
+1
Regards,
Hervé
Le mardi 25 juin 2013 11:48:55 Olivier Lamy a écrit :
> Hi,
> I'd like to release Apache Maven Javadoc Plugin 2.9.1.
>
> This version contains the code to fix the javadoc security issue after
> the javadoc generation.
>
> Since previous try I fix the @since for applying the j
+1
Regards,
Hervé
Le mardi 25 juin 2013 22:23:13 Robert Scholte a écrit :
> Hi,
>
> We solved 15 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=190
> 11
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jsp
Hi Jason,
Ok, I'll do it tonight.
Regards,
Hervé
Le vendredi 28 juin 2013 14:12:34 Jason van Zyl a écrit :
> Hervé,
>
> Can you please stage the site for 3.1.0?
>
> I'm going to put 3.1.0 up for vote.
>
> Thanks,
>
> Jason
>
> --
> Ja
site published
http://maven.apache.org/ref/3.1.0/
Regards,
Hervé
Le samedi 29 juin 2013 11:15:27 Jason van Zyl a écrit :
> Great, thanks. I'll push out the vote tomorrow.
>
> On Jun 29, 2013, at 2:07 AM, Hervé BOUTEMY wrote:
> > Hi Jason,
> >
> > Ok, I&#x
+1
thank you for useful work
Regards,
Hervé
Le vendredi 5 juillet 2013 21:48:56 Olivier Lamy a écrit :
> 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=Tex
> t&projectId=11150
>
> Staging
+1
works fine here
Regards,
Hervé
Le dimanche 30 juin 2013 15:00:40 Jason van Zyl a écrit :
> Here are the release bits for 3.1.0:
>
> Release notes:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=18
> 967
>
> Staging repository:
> https://repository.apache.org/co
yes, such doc is useful IMHO, since it took myself a lot of time to get it
clear in my mind (particularly lifecycle->phase->goal)
for the moment, I didn't find energy to write it down since I didn't know where
to put it to get us work on improvements (and even if anybody would find it
useful)
Le dimanche 7 juillet 2013 20:53:02 sebb a écrit :
> On 7 July 2013 20:39, 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.
>
> The point is that processes and people are not infallible
good idea: I hate these broken log messages, but as they are only log
messages, I didn't dig into it
Le lundi 8 juillet 2013 02:04:18 sebb a écrit :
> On 7 July 2013 23:36, wrote:
> > Author: hboutemy
> > Date: Sun Jul 7 22:36:42 2013
> > New Revision: 1500547
> >
> > URL: http://svn.apache.o
+1
Regards,
Hervé
Le lundi 15 juillet 2013 21:02:37 Arnaud Héritier a écrit :
> Hi all,
>
> Now that 3.1 is out we'll have to think to the future.
> I saw on twitter that Jason has already many ideas to share.
> For now the version in master is 3.1-SNAPSHOT.
> Do we bump it to 3.2-SNAPS
uh, another bot?
Le lundi 15 juillet 2013 22:28:26 Fred Cooke a écrit :
> What was the hash for future reference? This is why sebb is sooo right. If
> you have a unique coordinate, you're good for life, no matter what gets
> done to the SCM. (more or less)
>
> On Mon, Jul 15, 2013 at 9:53 PM, Arn
+1
Regards,
Hervé
Le vendredi 12 juillet 2013 23:12:02 Robert Scholte a écrit :
> Hi,
>
> We solved 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&styleName=H
> tml&version=19426
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secur
Le mardi 16 juillet 2013 22:42:23 sebb a écrit :
> On 16 July 2013 22:37, Jason van Zyl wrote:
> > Typo on my part. There are 48 things to change when updating a release.
> >
> > I updated and triggered the publish an hour ago. I'm not sure when/how it
> > updates.
> Should be immediate (within a
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 is
> still "Get Maven 3.0.5" -- which makes sense if 3.1 is not GA, but I think
> it is, right?
>
> PS: None of the release-notes.html pages include the release d
e viewed that page
> if it was accessible and visible through the site's home page.
>
> On Wed, Jul 17, 2013 at 3:01 PM, Hervé BOUTEMY wrote:
> > Le mercredi 17 juillet 2013 14:13:38 Paul Benedict a écrit :
> > > Is 3.0.5 still the preferred version? I as
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
> >
> > is
> >
> > > still &
sure :)
Le jeudi 18 juillet 2013 11:54:19 Jason van Zyl a écrit :
> Am I staging and not publishing? Maybe that's why my stuff never comes up.
>
> On Jul 18, 2013, at 11:48 AM, Hervé BOUTEMY wrote:
> > I fixed the typo a few days ago, it was staged but not published
> >
>
> > Branch: refs/heads/master
> > Commit: a2d30c322e6d54272a230ee39bf129f43ea8324a
> > Parents: 9f7d517
> > Author: Hervé Boutemy
> > Authored: Fri Jul 19 19:31:00 2013 +0200
> > Committer: Hervé Boutemy
> > Committed: Fri Jul 19 19:31:00 2013 +0
+1
Regards,
Hervé
Le samedi 20 juillet 2013 11:13:17 Dennis Lundberg a écrit :
> 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.
>
+1
Regards,
Hervé
Le samedi 20 juillet 2013 19:26:50 Dennis Lundberg a écrit :
> 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 Con
what's this commit?
I'm not a git master, but I suppose a rebase before committing should avoid
such things, no?
Regards,
Hervé
Le dimanche 21 juillet 2013 18:10:09 jvan...@apache.org a écrit :
> Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/maven
>
>
> Project: http://git-
I had a look at this issue a few monthes ago
I'd expect http://maven.apache.org/resource/ (like /plugins/) instead of
http://maven.apache.org/apache-resource-bundles/ .
But I didn't really understand which modules were really useful, and doing
such a change would require doing a release to reall
+1
thanks for the hard work
Regards,
Hervé
Le mardi 23 juillet 2013 20:23:19 Dennis Lundberg a écrit :
> 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/
+1
Regards,
Hervé
Le mardi 23 juillet 2013 21:45:52 Dennis Lundberg a écrit :
> 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.
>
>
Le vendredi 26 juillet 2013 01:05:44 Fred Cooke a écrit :
> About the fork, though, I'm interested. I'm interested in why it's
> maintained and how it differs. I'm interested because I intend to fork it
> myself to fix things which would break others which I know won't change
> upstream (site and r
Le jeudi 25 juillet 2013 19:17:08 Brian Fox a écrit :
> > There is at least one Maven Committer who has been maintaining a fork of
> > Maven for perhaps the greater part of a year.
>
> Is it really a fork? Or is it a superset? I think people throw around
> fork but is that really true?
without:
-
IIUC, this is a fix to https://jira.codehaus.org/browse/MNG-5499
I'm not a git blackbelt: can the comment be updated to add the classical
[MNG-5499]?
(and next time not be forgotten from initial comment :) )
I'm adding a reference to the commit in the Jira issue
Regards,
Hervé
Le samedi 27 ju
> -i
> > then mark the one of interest for
> > comment edit and proceed.
> >
> > On Sat, Jul 27, 2013 at 1:28 PM, Hervé BOUTEMY
wrote:
> >> IIUC, this is a fix to https://jira.codehaus.org/browse/MNG-5499
> >>
> >> I'm not a git blackb
; >>>
> >>>
> >>> On Sat, Jul 27, 2013 at 8:38 AM, Fred Cooke
> >>>
> >>> wrote:
> >>>> On Sat, Jul 27, 2013 at 3:36 PM, Arnaud Héritier >>>>
> >>>>> >wrote:
> >>>>>
been pushed/shared.
> >
> > On Sat, Jul 27, 2013 at 8:08 AM, Hervé BOUTEMY
wrote:
> >> the last 2 commits are to be amended: lst one for MNG-5499, previous one
> >> for MNG-5495
> >>
> >> I tried git commit --amend -m "[MNG-5499]...&q
+1
Regards,
Hervé
Le samedi 27 juillet 2013 23:25:36 Dennis Lundberg a écrit :
> Hi,
>
> We solved 4 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11241&styleName=H
> tml&version=13719
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure
if someone is interested: this build fails when run in parallel mode (-T3) but
builds fine with this -T3 removed
I could reproduce the failure on my local machine.
If someone is interested to discover what goes wrong in parallel...
I won't investigate myself: I just wanted no false positive on A
I'd like to work on http://jira.codehaus.org/browse/MNG-5319 tonight
so if you wait for tomorrow...
notice there are 2 ITs failing on ASF's Jenkins because of a failure to find
artifacts that are available AFAIK in the local repo: I suppose I'm missing
something trivial in the configuration
Can
ok, I see the reasoning, and since "tomorrow" is another day...
if you can wait for the end of the day to launch the release, it will give me
the few hours to find if I can get it done rapidly
Le dimanche 28 juillet 2013 12:36:32 Jason van Zyl a écrit :
> On Jul 28, 2013, at 12
Le dimanche 28 juillet 2013 18:48:44 Robert Scholte a écrit :
> 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.
> As a user I'm not going to update for every new release, it most have real
> value before
>check:90 ClassNotFoundException message was not
> found in output.
>
> Tests in error:
>
> MavenITmng3703ExecutionProjectWithRelativePathsTest>AbstractMavenIntegratio
> nTestCase.runTest:220->testForkFromReport:86 » Verification
>
> Tests run: 718, Failures: 1
Zyl a écrit :
> Fix for the ITs pushed, as I noted in the commit this needs to be examined
> again to simply the process. It's very annoying.
> On Jul 28, 2013, at 12:25 PM, Hervé BOUTEMY wrote:
> > I'd like to work on http://jira.codehaus.org/browse/MNG-5319
a lot of things were done in 0.9.0.M3: will need to review
notice the apidocs is not published yet
http://download.eclipse.org/aether/aether-core/0.9.0.M3/apidocs/
we need it to publish Maven core site
then we probably should create a Jira issue to keep track of this important
change (I have no
I was distracted from Maven yesterday (yes, there is a life...)
Will need to work on it later
Regards,
Hervé
Le dimanche 28 juillet 2013 18:25:58 Hervé BOUTEMY a écrit :
> I'd like to work on http://jira.codehaus.org/browse/MNG-5319 tonight
>
> so if you wait for tomorrow...
>
On Jul 29, 2013, at 2:13 AM, Hervé BOUTEMY wrote:
> > a lot of things were done in 0.9.0.M3: will need to review
> >
> > notice the apidocs is not published yet
> > http://download.eclipse.org/aether/aether-core/0.9.0.M3/apidocs/
> >
> > we need it to publi
ok, I'm back from vacations, and I'll try to be in the timeline
or it will be for next version if I can't...
Regards,
Hervé
Le dimanche 18 août 2013 19:41:21 Jason van Zyl a écrit :
> I will push out a vote for 3.1.1 on Tuesday if there are no objections. I
> get the fix for the regression and a
I think it's a good idea to move this page into the site, like /pom, /plugins,
/shared
the svnpubsub "externals" file is extpaths.txt [1]
"apache-resource-bundles" line in it should be replaced by one line per bundle
if you need help to configure svnpubsub on modules, just tell me and I'll have
he "apache-resource-bundles" line from
> extpaths.txt and add a corresponding page under /content ?
>
> On Tue, Aug 20, 2013 at 7:04 PM, Hervé BOUTEMY wrote:
> > I think it's a good idea to move this page into the site, like /pom,
> > /plugins,
> > /shared
> >
Le mercredi 21 août 2013 10:37:40 Phillip Hellewell a écrit :
> On Wed, Aug 21, 2013 at 3:19 AM, Baptiste Mathus wrote:
> > Wondering: is this strategy still gonna choose the newest version
> > specified
> > even if I specify a version inside my pom? Or is it only gonna be used
> > between depende
Le mercredi 21 août 2013 19:28:03 Robert Scholte a écrit :
> The problem with newest is that it can *never* be overridden by the active
> project, for whatever reason.
> Instead of newest I'd prefer to use the RequireUpperBoundDependencies
> Enforcer Rule[1] which give you the same result (otherwis
I made some research and tests and here are my findings
for the scm url, ie. web access like we have ViewVC url for svn, git provides
GitWeb equivalent to ViewVC (even if a lot of other solutions exist [1]),
which is what is configured on Apache git http
Then the GitWeb url format is in the git
. I did this knowing it would fail to illustrate the
> > > point:
> > >
> > > fred@cheetah:~/workspaces$ git clone
> > > https://git-wip-us.apache.org/repos/asf/maven.git/tree/heads/maven-2.2.x
> > > Cloning into 'maven-2.2.x'...
> >
>
Le samedi 24 août 2013 23:08:05 Robert Scholte a écrit :
> I agree that a single SCM line doesn't really match anymore with systems
> like DSCM (git, Mercurial)
> It would have been better if we could think of a better way to define this
> in a newer POM-model.
it was overkill at the time Maven was
Really strange
I can reproduce m-doap-p IT failures from my machine but not m-eclipse-p ones
notice in m-doap-p IT, the url should get a 404 not found
but in m-eclipse-p IT, the url points to existing content
IMHO, the behaviour change between Maven versions is tied to MNG-5175 change
from wagon
s'.
> > Now it still succeeds, but the log shows me the access denied exception
> > again.
> > My conclusion: Maven falls back to the file available in the local repo.
> >
> > I thought it was an infrastructure issue at Maven Central, but it seems
> > wa
lt;<
> Content-Length: 401
> 2013-08-31 16:18:16,747 [main] DEBUG org.apache.http.headers - <<
> Accept-Ranges: bytes
> 2013-08-31 16:18:16,747 [main] DEBUG org.apache.http.headers - << Date:
> Sat, 31 Aug 2013 14:18:19 GMT
> 2013-08-31 16:18:16,747 [main] DEBUG org.apach
yeah, I just tested m-doap-p ITs with *MNG-5509 fix and it works!*
*well done*
*Regards,*
*Hervé*
Le samedi 31 août 2013 17:10:53 Hervé BOUTEMY a écrit :
> nice unit test
>
> now hack AbstractHttpClientWagon.setHeaders to add a User-Agent header:
> method.addHeader(
ert Scholte :
> > Nice :D
> >
> > Case closed
> >
> > Op Sat, 31 Aug 2013 23:39:31 +0200 schreef Hervé BOUTEMY
> >
> > :
> >> yeah, I just tested m-doap-p ITs with *MNG-5509 fix and it works!*
> >>
> >> *well done*
> >&
smarted. And that's local to the
> provider, so go nuts. I also put lots of unit tests in there to illustrate
> the correct and incorrect usage.
>
> -Chris
>
> On Fri, Aug 30, 2013 at 6:33 AM, Hervé BOUTEMY wrote:
> > Le samedi 24 août 2013 23:08:05 Robert Scholte a écri
+1
Regards,
Hervé
Le vendredi 6 septembre 2013 21:35:56 Robert Scholte a écrit :
> Hi,
>
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?styleName=Html&projectId=11
> 136&version=18760
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secu
7:13:27 +0200 schreef Chris Graham
>
> :
> > On Sun, Sep 1, 2013 at 8:21 PM, Hervé BOUTEMY
> >
> > wrote:
> >> if I read Jazz SCM url format [1], in a multi-module build, scm info
> >> automatically calculated from root to modules (ie appending artifact-id)
>
I prefer this 3.1.x-SNAPSHOT value: the intent is more clear
Regards,
Hervé
Le samedi 14 septembre 2013 19:42:23 Arnaud Héritier a écrit :
> No problem for me. At work I'm also applying this rule but we use
> 3.1.x-SNAPSHOT. I didn't notice issues with this
>
> Cheers.
>
> -
> Arnaud
>
+1
tested with Maven core and ITs
Regards,
Hervé
Le jeudi 12 septembre 2013 13:29:32 Tamás Cservenák a écrit :
> Hi,
>
> We solved 6 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&version=19
> 092
>
> There are still a couple of issues left in JIRA:
> https://jira
I didn't have time to test this release for the moment
but I updated a few days ago Maven core release instructions [1] to stage core
reference documentation:
http://maven.apache.org/ref/3-LATEST/
Actual state is the staging from previous release vote: it should be updated
from actual tag, but I
I suppose each circle is a module
but I don't understand what the levels are, and how modules are dispatched
into levels
Regards,
Hervé
Le jeudi 19 septembre 2013 18:36:49 Kristian Rosenvold a écrit :
> Jason sent me some questions about the parallel build that included a
> real nice figure. Si
, which distributes it to live
http server through svnpubsub
Regards,
Hervé
Le jeudi 19 septembre 2013 07:00:13 Jason van Zyl a écrit :
> Are you just manually copying that or is there an option on the CMS to make
> the staging site?
> On Sep 18, 2013, at 10:18 PM, Hervé BOUTEMY wrote:
>
a module in a multi-module build,
> the "levels" simply indicate the distance to the first module in the
> internal reactor dependency graph.
>
> Kristian
>
> 2013/9/19 Hervé BOUTEMY :
> > I suppose each circle is a module
> > but I don't
help us reach a
> state of more automation.
>
> I'll follow those steps for the time being.
>
> On Sep 19, 2013, at 10:19 AM, Hervé BOUTEMY wrote:
> > it does not use CMS
> > I split the instructions in 2 parts to make things as clear as possible:
> >
&
aging site that can be used for all core releases.
> On Sep 19, 2013, at 1:19 PM, Hervé BOUTEMY wrote:
> > what do you call "a standard staging location"?
> > what more automation do you expect?
> >
> > Le jeudi 19 septembre 2013 11:02:46 Jason van Zyl a écrit :
I just published a documentation about CMS + svnpubsub for Maven, with schema
for global overview of the differences and synchronization points between Maven
site and components reference documentations [1]
The documentation about Maven website is expected to be complete, but
components referen
Starting a separate thread to not pollute any vote.
Isn't Apache Creadur the right place to:
1. discuss and refine Apache requirements
2. work on tooling
Regards,
Hervé
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
the Release"[2] chapter is missing a direct link to the page
> explaining how to publish the site.
>
> Robert
>
> [1]
> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html
> #waitBeforeTagging [2]
> http://maven.apache.org/developers/release/maven-
I didn't have any problem in my tests
but the release reference documentation staging is still missing: I tried to
continue helping on IRC, but couldn't get in touch with you thses last 2 days
Tell me if anything prevents you from publishing the doc
Regards,
Hervé
Le mercredi 25 septembre 2013
lopers/release/maven-plugin-release.html
> [2] http://maven.apache.org/developers/website/deploy-maven-website.html
>
>
> Op Thu, 26 Sep 2013 00:12:10 +0200 schreef Hervé BOUTEMY
>
> :
> > yes, the first issue is a svn-eu issue: I'll add a FAQ
> >
> > the s
+1
Regards,
Hervé
Le mercredi 25 septembre 2013 08:22:45 Jason van Zyl a écrit :
> Anyone else going to give the release a whirl?
>
> On Sep 17, 2013, at 8:39 AM, Jason van Zyl wrote:
> > Hi,
> >
> > Maven Core ITs are good, and the license/notice issue has been resolved so
> > I'm rolling 3.
true, having this version during development does not permit core its range as
usual: an IT for a minor version will be run only at release time, but not
before and after
that's a major issue, IMHO
Regards,
Hervé
Le vendredi 4 octobre 2013 07:18:50 Igor Fedorenko a écrit :
> Practical questio
+1 for 1.6 in Maven 3.2.0
Le samedi 5 octobre 2013 13:22:41 Anders Hammar a écrit :
> +1 for 3.2 (or greater)
> -1 for 3.1.x
>
> /Anders
>
> On Sat, Oct 5, 2013 at 1:00 PM, Mark Struberg wrote:
> > +1
> >
> > LieGrue,
> > strub
> >
> >
> >
> >
> > - Original Message -
> >
> > > Fr
ok for the rationale
Markdown seems to have been chosen in Apache CMS too [1]
DOXIA-472 is a show stopper IMHO for the moment: I hope someone will fix it
Stephen wrote about asciidoc, but it is not supported by Doxia at the moment
[2], so not an option until someone adds this format to Doxia
For
FML is used in a few places, not only main sites [1] but plugins and
components too [2]
So perhaps FML will remain until we find some macro tooling.
I prefer keeping FML than maintaing index by hand
If we can replace apt and xdoc, that will already be a good step
Regards,
Hervé
[1] http://mav
+1 *2
Regards,
Hervé
Le lundi 14 octobre 2013 23:09:54 Robert Scholte a écrit :
> Hi,
>
> since the same type of issues have been fixed for both the Apache Maven
> Install Plugin and Apache Maven Deploy Plugin, I've decided to stage both
> plugins at once.
>
> We solved 2x2 issues:
> MINSTALL:
1 - 100 of 3744 matches
Mail list logo
