Github user MysterionRise commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-46524647
First of all - thanks for your email.
I understand, that this will ruin current ORing technique, but at least it
could be fixed with copying for a while.
Github user FredipusRex commented on the pull request:
https://github.com/apache/maven/pull/20#issuecomment-46523185
You do realize that the current OR condition is actually out in use right
now in many POM files, right? This was previously the subject of a patch
(MNG-3106) - original
I asked on maven-users but didn't get any viable responses. So I'm hoping
someone here can help.
--
I have a Mojo that needs to work with Maven 3.0.* and 3.1+
In the Mojo I have an Artifact and I need to resolve it's dependencies. How
can/should I do it?
If I can resolve
Hi,
the vote has passed with the following result:
+1 (binding): Robert Scholte, Oliver Lamy, Stephane Nicoll, Hervè Boutemy
0: None
+1 (non binding): None.
I will promote the artifacts to the central repo.
Kind regards
Karl-Heinz Marbaise
HiOn 6/15/14 4:23 PM, Karl Heinz Marbaise wrote:
Hi,
Github user rfscholte commented on the pull request:
https://github.com/apache/maven/pull/22#issuecomment-46476155
I read about the failing test. I'm looking for the differences. I've tried
it with 1.7.0_55 as well, still that test succeeds. So it failure is either
caused by the OS, t
Release notes are still be written for all the features. They will be complete
before the release.
On Jun 18, 2014, at 10:32 AM, Igor Fedorenko wrote:
> FWIW, m2e is happy with the staged 3.2.2 and so is one of the bigger
> projects I deal with at $DAY_WORK.
>
> Noticed a couple of small-ish p
I got 503 page several times during the day and evening yesterday.
--
Regards,
Igor
On 2014-06-18, 9:13, Jason van Zyl wrote:
Two times during the one hour window that I was trying to release that the
service was not available. It was an Apache page but I assume Nexus wasn't
running behind it
FWIW, m2e is happy with the staged 3.2.2 and so is one of the bigger
projects I deal with at $DAY_WORK.
Noticed a couple of small-ish problems
release notes are missing MNG-2199 [1], which I believe was merged to
master and is part of staged 3.2.2.
the release binary includes license files for
Two times during the one hour window that I was trying to release that the
service was not available. It was an Apache page but I assume Nexus wasn't
running behind it or not responding.
On Jun 18, 2014, at 8:57 AM, Brian Fox wrote:
> I haven't received any alerts that it's been down although
https://issues.apache.org/jira/browse/INFRA-7915
On Wed, Jun 18, 2014 at 9:01 AM, Arnaud Héritier wrote:
> When I noticed it was down on my side it was 503 errors
>
>
> On Wed, Jun 18, 2014 at 2:57 PM, Brian Fox wrote:
>
>> I haven't received any alerts that it's been down although there are
>>
When I noticed it was down on my side it was 503 errors
On Wed, Jun 18, 2014 at 2:57 PM, Brian Fox wrote:
> I haven't received any alerts that it's been down although there are
> sporadic reports of timeouts. Did you receive a timeout, 502 or
> something else?
>
> Nexus is on shared vm hosts an
I haven't received any alerts that it's been down although there are
sporadic reports of timeouts. Did you receive a timeout, 502 or
something else?
Nexus is on shared vm hosts and shared disks and I suspect that some
other guest is occasionally bursting and screwing up the io
throughput.
On Tue,
Thanks.
On Jun 17, 2014, at 9:04 PM, Hervé BOUTEMY wrote:
> I did "the work", ie I ran the classical commands:
>
> mvn -Preporting site site:stage
> mvn scm-publish:publish-scm
>
> so the site is ready at http://maven.apache.org/ref/3-LATEST/
>
> Notice:
> 1. it takes a little time because th
Github user a-horst commented on the pull request:
https://github.com/apache/maven/pull/22#issuecomment-46421059
This is mine:
```
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T18:37:52+01:00)
Maven home: C:\Program Files\Apache\apache-maven-3.2.1
On 18 Jun 2014, at 17:05, Barrie Treloar wrote:
It takes a small (but not negligible) amount of time to haul the
release
jars from you local Maven Repository - likely also hosted on your CI
server.
Plus pulling in any snapshots previously deployed.
The problem gets extended further when you'
On 18 Jun 2014, at 20:50, Stephen Connolly wrote:
Thus you can declare upstream literate projects and branch matching
criteria... an upstream project's local repository
The problem here is the way Gerrit presents its reviews, they're not
publicly accessible branches so there IS no matching br
Well one of the features I want to write for the literate project type in
Jenkins is a smarter Maven awareness...
Thus you can declare upstream literate projects and branch matching
criteria... an upstream project's local repository cache will then be
exposed to downstream projects... but on a bra
17 matches
Mail list logo
