In that case: let's push it to 1.3.0
On Mon, 01 Oct 2018 22:47:23 +0200, Michael Osipov <1983-01...@gmx.net>
wrote:
Correct!
Gesendet: Montag, 01. Oktober 2018 um 18:46 Uhr
Von: "Robert Scholte"
An: "Maven Developers List"
Betreff: Re: Re: Skipping Resolver 1.2.0
Just to refresh my memo
On 2 Oct 2018, at 4:32, Karl Heinz Marbaise wrote:
> * [MINSTALL-118] - MavenProject with only attachments must have packaging
> "pom"
Ik, this just hit me with the `karaf-assembly` packaging - and seemingly not
setting a main file it seems.
Time to go lock that install plugin back down, and
> Hi,
>
> currently I see only the following open issues:
>
>
> MNG-6412
> - currently open @Sylwester can you check this?
>
> MNG-6391
>- currently the last Tests are done. Something
> which should be changed?
>
> Adding WAGON newest version (3.2.0) to core release?
Yes.
> anythi
Correct!
> Gesendet: Montag, 01. Oktober 2018 um 18:46 Uhr
> Von: "Robert Scholte"
> An: "Maven Developers List"
> Betreff: Re: Re: Skipping Resolver 1.2.0
>
> Just to refresh my memory: When working on Maven 3.4.x there were also
> changes to Maven Resolver, targeted as 1.2.0.
> For Maven we
Hi,
currently I see only the following open issues:
MNG-6412
- currently open @Sylwester can you check this?
MNG-6391
- currently the last Tests are done. Something
which should be changed?
Adding WAGON newest version (3.2.0) to core release?
anything else which should be part of it?
Hi,
On 01/10/18 20:28, Robert Scholte wrote:
[INFO] Reactor Summary (7.8.9-SNAPSHOT):
hmmm, somehow I don't like the braces here, looks odd here.
How about
[INFO] Reactor Summary for 7.8.9-SNAPSHOT:
Sure no poblem. No big deal to change that...
Kind regards
Karl Heinz Marbaise
thanks,
Ro
[INFO] Reactor Summary (7.8.9-SNAPSHOT):
hmmm, somehow I don't like the braces here, looks odd here.
How about
[INFO] Reactor Summary for 7.8.9-SNAPSHOT:
thanks,
Robert
On Mon, 01 Oct 2018 20:20:16 +0200, Karl Heinz Marbaise
wrote:
Hi,
I have changed the implementation which now looks
Hi,
I have changed the implementation which now looks like this:
[INFO] --- maven-assembly-plugin:3.1.0:single (assemblies) @ assembly ---
[INFO] Reading assembly descriptor: assembly.xml
[INFO] Reading assembly descriptor: jar-with-prod.xml
[INFO] Reading assembly descriptor: jar-with-dev.xml
[
Just to refresh my memory: When working on Maven 3.4.x there were also
changes to Maven Resolver, targeted as 1.2.0.
For Maven we did a reset and pushed the version to 3.5.0.
In case as Resolver you want to have the same approach, right?
Robert
On Mon, 01 Oct 2018 12:44:38 +0200, Michael Osipo
The Apache Maven team is pleased to announce the release of the
Apache Maven Deploy Plugin Version 3.0.0-M1.
https://maven.apache.org/plugins/maven-deploy-plugin/
Important Note since 3.0.0-M1:
* Maven 3.X only
* Minimum JDK 7+
* The maven-deploy-plugin will generate the needed checksums
The Apache Maven team is pleased to announce the release of the
Apache Maven Install Plugin Version 3.0.0-M1.
https://maven.apache.org/plugins/maven-install-plugin/
Important Note since 3.0.0-M1:
* Maven 3.X only
* Minimum JDK 7+
* The maven-install-plugin does not generate any kind of chec
You probably misunderstood. I just want to rename 1.2.0 to 1.3.0 to avoid
confusion. Nothing is lost. The target 1.2.0 was broken, therefore we have
resetted to 1.1.1 and bringing 1.2.0 back is confusing.
> Gesendet: Montag, 01. Oktober 2018 um 10:43 Uhr
> Von: "Robert Scholte"
> An: "Maven Dev
For the FileTransformer I've already updated the version from 1.1.2 to 1.2.0 in
Jira. I see no reason to push it further to 1.3.0
Robert
Verzonden vanaf mijn Samsung Galaxy-smartphone.
Oorspronkelijk bericht Van: Michael Osipov
Datum: 30-09-18 22:27 (GMT+01:00) Aan: Maven Deve
For the FileTransformer I've already updated the version from 1.1.2 to 1.2.0 in
Jira. I see no reason to push it further to 1.3.0
Robert
Verzonden vanaf mijn Samsung Galaxy-smartphone.
Oorspronkelijk bericht Van: Michael Osipov
Datum: 30-09-18 22:27 (GMT+01:00) Aan: Maven Deve
14 matches
Mail list logo
