Am Do., 14. Feb. 2019 um 14:22 Uhr schrieb Tibor Digana <
tibordig...@apache.org>:
> Benedikt, it does not mean that something with public IP is for public use.
> We made only a compromise for some users to verify some functionality.
>
Please read the information about Apache repositories:
Good idea to cut a release (been affected by
https://issues.apache.org/jira/browse/MNG-6590)
I don't mind if someone move the remaining open to next 3.6.x :)
On Thu, 14 Feb 2019 at 04:48, Michael Osipov wrote:
> Am 2019-02-13 um 19:28 schrieb Dan Tran:
> > love to see 3.6.1 out soon :)
>
>
makes sense for me. I will update master branch with correct version
On Thu, 14 Feb 2019 at 20:42, Benedikt Ritter wrote:
> Am Mi., 13. Feb. 2019 um 17:48 Uhr schrieb Tibor Digana <
> tibordig...@apache.org>:
>
> > Is it so a big problem to keep both versions? This is our internal Nexus
> >
Hi Robert,
Am 12.02.19 um 20:09 schrieb Robert Scholte:
[...]
> Hi Markus,
>
> first of all thanks for the insights, it is important for us to know how
> Maven is used and in which way we can improve that way-of-work. Hervé is
> already working hard on the reproducible builds specs with your
Dear developers,
I'm Carmine, a researcher at the University of Zurich interested in
supporting developers working with CI/CD.
Among the benefits provided by Continuous Integration (CI), increased team
productivity and release frequency are perceived as the main advantages.
However, changes that
Am Mi., 13. Feb. 2019 um 17:48 Uhr schrieb Tibor Digana <
tibordig...@apache.org>:
> Is it so a big problem to keep both versions? This is our internal Nexus
> server anyway.
>
>From my PoV the metadata is incorrect. Latest should point to the latest
available build. At the moment it does not.
Paul Hammant writes:
> mvn clean install -DskipTests
> -Dmaven.repo.local=/usr/local/var/MAVEN_CI_REPOSITORY
This would compile and test-compile for the first time...
> mvn surefire:test -Dmaven.repo.local=/usr/local/var/MAVEN_CI_REPOSITORY
Run compile and test-compile one more time, on the
Why you change POM if there is no problem?
If the problem is in deploy-plugin then it should be fixed.
On Thu, Feb 14, 2019 at 11:57 AM Olivier Lamy wrote:
> makes sense for me. I will update master branch with correct version
>
> On Thu, 14 Feb 2019 at 20:42, Benedikt Ritter wrote:
>
> > Am
Jar manifest files carry data like "built-by" and implementation
information:
https://docs.oracle.com/javase/tutorial/deployment/jar/packageman.html
Why not reuse "Implementation-Vendor" or invent a new entry and put
"Debian" in there. Maven can display this additional information on "mvn
Yeah, maybe that makes sense.
On Thu, Feb 14, 2019 at 1:45 PM Mykola Nikishov wrote:
> Paul Hammant writes:
>
> > mvn clean install -DskipTests
> -Dmaven.repo.local=/usr/local/var/MAVEN_CI_REPOSITORY
>
> This would compile and test-compile for the first time...
>
> > mvn surefire:test
I have proposed a similar approach with maven.vendor in the build.properties.
> Gesendet: Donnerstag, 14. Februar 2019 um 14:24 Uhr
> Von: "Gary Gregory"
> An: "Maven Developers List"
> Cc: "Robert Scholte" , "Dalibor Topic"
> , debian-j...@lists.debian.org, "Matthias Klose"
>
> Betreff: Re:
Benedikt, it does not mean that something with public IP is for public use.
We made only a compromise for some users to verify some functionality.
On Thu, Feb 14, 2019 at 11:42 AM Benedikt Ritter wrote:
> Am Mi., 13. Feb. 2019 um 17:48 Uhr schrieb Tibor Digana <
> tibordig...@apache.org>:
>
> >
Hi to all,
currently there are 3 issue open in JIRA for 3.6.1:
* MNG-6506 Mojos are unable to load package annotations on Java >= 9
* MNG-6538 Upgrade Maven Artifact Resolver to 1.3.2 to restore API
* MNG-6543 Upgrade plexus classworld to support java 9+
On branch MNG-6543
Hi Robert,
Some comments with my Maven package maintainer hat.
Le 12/02/2019 à 20:09, Robert Scholte a écrit :
> I'm also wondering how you build Maven, since Maven is
> being built with Maven. That should be a challenge to also rebuild all
> plugins, etc.
The maven package is rebuilt with the
14 matches
Mail list logo