aajisaka closed pull request #22:
URL: https://github.com/apache/maven-artifact-transfer/pull/22
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
aajisaka commented on pull request #22:
URL:
https://github.com/apache/maven-artifact-transfer/pull/22#issuecomment-789778922
> It might sound a good idea to add this information to the repo itself so
people won't spend their time on a PR that would be closed.
Yes, that's a good
KroArtem commented on pull request #22:
URL:
https://github.com/apache/maven-artifact-transfer/pull/22#issuecomment-789706459
I was just passing near and remember that the plan was not to update maven
minimum version https://github.com/apache/maven-artifact-transfer/pull/20
(especially
aajisaka opened a new pull request #22:
URL: https://github.com/apache/maven-artifact-transfer/pull/22
Drop support for Maven 3.0.x
Maven Common Artifact Filters 3.2.0 only supports Maven 3.1.1+
(https://issues.apache.org/jira/browse/MSHARED-974), and after the dependency
upgrade,
elharo merged pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
bertysentry commented on pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39#issuecomment-788041050
Awesome news! :-)
This is an automated message from the Apache Git Service.
To respond to the
elharo commented on pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39#issuecomment-788034268
Looks good. CI is slow today, but I'll merge as soon as they all pass.
Thanks!
This is an automated
mthmulders commented on pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39#issuecomment-788023747
The remaining tests are also fixed by upgrading the Maven Javadoc Plugin.
Just pushed.
This is an
elharo commented on pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39#issuecomment-787975296
Running through Jenkins:
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-site-plugin/job/msite-871/
Given that this fixes some tests, and does
bertysentry commented on pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39#issuecomment-787963914
This is cool, thank you!
We're making good progress as only 2 integration tests are now failing:
```
Error: The following builds failed:
Error: *
mthmulders opened a new pull request #39:
URL: https://github.com/apache/maven-site-plugin/pull/39
These test failed on macOS with Java above 8; now they pass with
Java 8, 11 and 15 on macOS.
This is an automated message
The short answer: I just love this IDE and everything that is behind it!
I'm using it since I dropped the IBM VisualAge a long long time ago. ;-)
In my daily working needs with Java, OSGi, Vertx and Maven I have no
complains. it just give me what I need. Of course that are a bug here
and there,
Thanks all,
I've confirmed that upgrading this mavenarchiver connector and also m2e
(thanks Mickael) resolved my issue.
best regards,
Cristiano
On 10/06/2019 04:11, Anders Hammar wrote:
> Please read the bug report [1], which was reference in the first reply to
> this thread. It clearly
Hey StephenC,
I was looking for Anders' answer in Eclipse issue. Important is that the
issue was isolated to https://github.com/tesla/m2eclipse-mavenarchiver and
to Maven.
Issues are everywhere, in every tool, that's the life. Maybe some did not
reach such ratings to fix them nor contributor who
On Mon, 10 Jun 2019 at 13:36, Mickael Istria wrote:
> Hi,
>
> On Mon, Jun 10, 2019 at 11:37 AM Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > however
> > because of architectural history, Eclipse (last time I checked... some
> > years ago) had issues keeping the main and test
Hi,
On Mon, Jun 10, 2019 at 11:37 AM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> however
> because of architectural history, Eclipse (last time I checked... some
> years ago) had issues keeping the main and test classpaths separate
This was fixed last year, during development
Tibor,
If one is ranking correctness of integration with Maven of the various IDEs
then IntelliJ is not the "gold standard".
There are two *major* bugs in how IntelliJ handles Maven projects:
1. It does not allow different Java versions for test versus main trees:
Please read the bug report [1], which was reference in the first reply to
this thread. It clearly explains that the problem is in the mavenarchiver
m2e connector/plugin. The simplest solution is to just update that plugin.
URL to update site is in the bug report.
[1]
Hello Cristiano,
Original root cause not analysed but:
- Same problem here with Eclipse Oxygen (3a) + m2e - Maven Integration for
Eclipse 1.8.3.
- It works with Eclipse 2019-03 + m2e - Maven Integration for Eclipse 1.11.0
=> m2e - Maven Integration for Eclipe plugin upgrade could be a solution
Hi Cristiano,
I guess your architect who designed your company parent POM made everying
honestly right.
But we can prove or avoid the error on the tool if we simply add something,
then make a comparison test and we exclude added things which could not
change the outcome.
Open the project in
On Sat, Jun 8, 2019 at 6:14 PM Mickael Istria wrote:
> [...]
> Then seeing such negative comments towards them, which are more about
> opinion than technical facts, seems really not encouraging to contribute
> more to Maven.
[...]
It's the 2nd time in a short time-frame I find your comments
It's also interesting to see how much m2e cases and community has
contributed to improve Maven compared to other IDEs.
Then seeing such negative comments towards them, which are more about
opinion than technical facts, seems really not encouraging to contribute
more to Maven. Imagine if on the
Not really Tibor I think, for two reasons:
1. If it is true then the end of your sentence is "and dont use maven but
use gradle". Both IDE have pro and cons, depends who and for what,
2. Vscode uses eclipse as backend of a LSP so as a mvn dev you care of
eclipse whatever you think of the UI since
No, it is not truth. And the price is nothing one cannot survive. IDEA is
also OSS.
User exp of IDEA is ideally joined together with Maven and working
naturally well.
Try Maven + IDEA and you will see. I used both.
On Sat, Jun 8, 2019 at 4:51 PM Jeff MAURY wrote:
> because it's much better and
because it's much better and oss
Le sam. 8 juin 2019 à 10:29, Tibor Digana a écrit :
> Why you use Eclipse. Use InteliJ IDEA. It is professional tool. Every
> company has money to buy enterprise IDEA, the company wouln'd say no
> because it is price you pay once and you can upgrade to major
Why you use Eclipse. Use InteliJ IDEA. It is professional tool. Every
company has money to buy enterprise IDEA, the company wouln'd say no
because it is price you pay once and you can upgrade to major version
within whole year. You can use it forever without paying more after the
support period of
Hi,
This seems like https://bugs.eclipse.org/bugs/show_bug.cgi?id=547340 .
Please try updating to a more recent build of Eclipse m2e (using
https://download.eclipse.org/technology/m2e/snapshots/1.12.0/latest/ p2
repo), and if you see further issues with that version, please reopen the
m2e bug
Hello,
Yesterday I did an upgrade on some dependencies and plugins of my
company's master POM.
I used the versions-plugin and changed many of the suggested ones. After
conclude and build on CI without error, I ended up with a strange error
in Eclipse IDE (ubuntu, 201903, jdk11) on every project
Github user asfgit closed the pull request at:
https://github.com/apache/maven/pull/149
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Github user slachiewicz commented on the issue:
https://github.com/apache/maven/pull/149
Please verify after planned plugin release
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional
GitHub user slachiewicz opened a pull request:
https://github.com/apache/maven/pull/149
Upgrade maven-checkstyle-plugin to 3.0.0 (Checkstyle 6.18) and fix errors
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/slachiewicz/maven
Le 18/12/2016 à 01:09, Christian Schulte (JIRA) a écrit :
Christian Schulte created MPOM-152:
--
Summary: Upgrade maven-checkstyle-plugin to 2.17.
Key: MPOM-152
URL: https://issues.apache.org/jira/browse/MPOM
bject: RE: upgrade maven plugin to run with asm 6?
> To: dev@maven.apache.org
>
> Oh tested 3.4 but missed 3.5. 3.5 solved the issue!
>
> Thanks!
>
> Le 10 oct. 2016 20:31, "Martin Gainty" <mgai...@hotmail.com> a écrit :
> >
> >
> >
> >
&
Oh tested 3.4 but missed 3.5. 3.5 solved the issue!
Thanks!
Le 10 oct. 2016 20:31, "Martin Gainty" <mgai...@hotmail.com> a écrit :
>
>
>
>
> > From: rmannibu...@gmail.com
> > Date: Mon, 10 Oct 2016 17:07:54 +0200
> > Subject: Re: upgra
> From: rmannibu...@gmail.com
> Date: Mon, 10 Oct 2016 17:07:54 +0200
> Subject: Re: upgrade maven plugin to run with asm 6?
> To: dev@maven.apache.org
>
> 2016-10-10 16:54 GMT+02:00 Martin Gainty <mgai...@hotmail.com>:
>
> >
> >
> >
> > &g
+02:00 Martin Gainty <mgai...@hotmail.com>:
> From: rmannibu...@gmail.com
> Date: Mon, 10 Oct 2016 15:10:33 +0200
> Subject: upgrade maven plugin to run with asm 6?
> To: dev@maven.apache.org
>
> Hi guys,
>
> is there some plans to upgrade maven plugin to as
2016-10-10 16:54 GMT+02:00 Martin Gainty <mgai...@hotmail.com>:
>
>
>
> > From: rmannibu...@gmail.com
> > Date: Mon, 10 Oct 2016 15:10:33 +0200
> > Subject: upgrade maven plugin to run with asm 6?
> > To: dev@maven.apache.org
> >
> > Hi guys,
> From: rmannibu...@gmail.com
> Date: Mon, 10 Oct 2016 15:10:33 +0200
> Subject: upgrade maven plugin to run with asm 6?
> To: dev@maven.apache.org
>
> Hi guys,
>
> is there some plans to upgrade maven plugin to asm6 (thinking
> to maven-plugin-tools-annotati
Hi guys,
is there some plans to upgrade maven plugin to asm6 (thinking
to maven-plugin-tools-annotations and maven-plugin-plugin and more
concretely to DefaultMojoAnnotationsScanner used to generate the help mojo)?
I know there is only the alpha our ATM but I think it would enable users to
start
Github user asfgit closed the pull request at:
https://github.com/apache/maven-plugin-tools/pull/8
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user gslowikowski opened a pull request:
https://github.com/apache/maven-plugin-tools/pull/8
MPLUGIN-295 - upgrade Maven Invoker Plugin version to 1.10
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gslowikowski/maven
There is no hurry on this, but it would be good to know the release status
of this plugin.
Big thanks for all the efforts have been made to plugins lately
-D
On Mon, Oct 27, 2014 at 2:15 PM, Karl Heinz Marbaise khmarba...@gmx.de
wrote:
hi Michael,
On 10/27/14 9:53 PM, Michael Osipov wrote:
@Karl
Are you planing to release a new maven-jar-plugin?
Thanks
-D
Hi Dan,
On 10/27/14 9:01 PM, Dan Tran wrote:
@Karl
Are you planing to release a new maven-jar-plugin?
Thanks
Yeah...working on a missging single issue...apart from the current down
issue of the nexus ...
http://jira.codehaus.org/browse/MJAR
Kind regards
Karl Heinz Marbaise
Am 2014-10-27 um 21:21 schrieb Karl Heinz Marbaise:
Hi Dan,
On 10/27/14 9:01 PM, Dan Tran wrote:
@Karl
Are you planing to release a new maven-jar-plugin?
Thanks
Yeah...working on a missging single issue...apart from the current down
issue of the nexus ...
hi Michael,
On 10/27/14 9:53 PM, Michael Osipov wrote:
Am 2014-10-27 um 21:21 schrieb Karl Heinz Marbaise:
Hi Dan,
On 10/27/14 9:01 PM, Dan Tran wrote:
@Karl
Are you planing to release a new maven-jar-plugin?
Thanks
Yeah...working on a missging single issue...apart from the current down
Hi,
is there any documentation explaining how to upgrade from 1.0beta7 to
release 1.0?
Alexis
47 matches
Mail list logo
