thank you Stephen: vacations are over for everybody! :)
Regards,
Hervé
Le mercredi 23 août 2017, 19:09:03 CEST Stephen Connolly a écrit :
> Advance warning, my intent is to start cutting RCs towards the end of next
> week.
>
> Focus on bugs and Java 9 compatibility would be best at this stage
they are waiting for love, for somebody to really test and release
I did the integration in our Maven structure (with git, site [1], CI) while I
was migrating Aether to Maven Artifact Resolver, checking that the build
passes: but nobody seemed interested (until now?) to test it and have a
https://github.com/apache/maven-resolver
see ant-tasks branch.
On 24 August 2017 at 12:45, Mark Derricutt wrote:
> Hey all,
>
> Now that Aether has moved it's way back to Apache as the Maven Resolver,
> what's become of the Aether/Ant taks?
>
>
Hey all,
Now that Aether has moved it's way back to Apache as the Maven Resolver, what's
become of the Aether/Ant taks?
https://wiki.eclipse.org/Aether/Ant_Tasks
Mark
---
"The ease with which a change can be implemented has no relevance at all to
whether it is the right change for the
Hi
Well makes sense!. I was only thinking about the shaded uber jar use case
(we have to keep this one in mind as well)
We probably need to make an extra component if we want to reuse this in
both plugins.
On 24 August 2017 at 08:07, Andreas Gudian wrote:
> I find the
Github user jon-bell commented on the issue:
https://github.com/apache/maven-surefire/pull/161
@Tibor17 Is there anything else I can do to help get this merged?
---
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
I find the arguments by Plamen very convincing. As a user I would look for
that configuration where I previously did the same thing when it ended up
in the Manifest: in the config of the jar plugin.
I wouldn't expect to suddenly switch to the shade plugin to be able to
define the main class or the
On 24 Aug 2017, at 9:49, Andreas Gudian wrote:
> Yupp, I'm afraid neither version ranges nor information from any
> dependencyManagement sections are considered.
>
> Only the plain versions or properties work, and transitive dependencies are
> pulled in
Yeh, we use properties as a workaround
Yupp, I'm afraid neither version ranges nor information from any
dependencyManagement sections are considered.
Only the plain versions or properties work, and transitive dependencies are
pulled in.
And I agree that a special scope would have been a nice alternative
solution, but that would have
GitHub user shafiullas opened a pull request:
https://github.com/apache/maven-surefire/pull/163
Surefire-report
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gmuecke/maven-surefire SUREFIRE-1183
Alternatively you can review
Advance warning, my intent is to start cutting RCs towards the end of next
week.
Focus on bugs and Java 9 compatibility would be best at this stage
(Getting to an actual release will take as long as it takes, but I intend
actively triage of the scope and RCs every 1-2 weeks until we get there)
Github user grkvlt commented on the issue:
https://github.com/apache/maven/pull/127
ping?
---
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
On Wed, 23 Aug 2017 08:11:35 +0200, Plamen Totev
wrote:
On Tue, Aug 22, 2017 at 11:03 PM, Robert Scholte
wrote:
The maven-shade-plugin has the ability to re-package a jar and
manipulate any type of file, including class files. The best
On Tue, Aug 22, 2017 at 11:03 PM, Robert Scholte wrote:
>
>
> The maven-shade-plugin has the ability to re-package a jar and manipulate any
> type of file, including class files. The best example is relocation, where
> you give a set of classes a different package to
14 matches
Mail list logo