Hi ,
How can I remove dependencies pom.xml from shaded jar in elegant way?
See https://issues.apache.org/jira/browse/SUREFIRE-1298
Cheers
Tibor
Github user hboutemy commented on the issue:
https://github.com/apache/maven/pull/94
IT moved to its own suite in
https://github.com/apache/maven-integration-testing/commit/3311f4e345fe7e6c343fae737631b727aba5b910
to avoid running this IT with Maven 3.3.x, as it will fail
---
If
Github user hboutemy commented on the issue:
https://github.com/apache/maven/pull/94
IT added
https://github.com/apache/maven-integration-testing/commit/2e74409fc2593b4478c40f28c7fdabc60202c06b
no change on existing ITs, just added an additional run with different
execution
Github user jvanzyl commented on the issue:
https://github.com/apache/maven/pull/94
Please do not change an existing test. The conditions under which this IT
passes should be left as-is and should continue running as it is in exactly the
form it runs now. Making purely additional
Github user rpatrick00 commented on the issue:
https://github.com/apache/maven/pull/94
I took a quick look at the MNG-5771 IT and it's not obvious to me exactly
what I need to do so if you can add this in a few minutes, that is probably the
best thing to do. If not, I will try to
Github user hboutemy commented on the issue:
https://github.com/apache/maven/pull/94
I know core ITs are intimidating: it took me years to really dig into the
code!
This case seems a simple one (what I didn't really expect when thinking at
it initially), since it's only improving
Thanks Stuart, I will check this :-)
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Sat, Nov 12, 2016 at 11:27 PM, Stuart McCulloch wrote:
> Also note the
Hi,
We solved 3 issues:
* [MRESOURCES-230] - Can't escape the escape string
* [MRESOURCES-233] - Upgrade of plexus-interpolation 1.24 to correct
escaping issue.
* [MRESOURCES-234] - Upgrade of commons-io to 2.5 and correction of
invalid scope.
There are still a couple of issues left
Github user michael-o commented on the issue:
https://github.com/apache/maven/pull/94
@hboutemy Thanks for helping out!
---
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
Pushing this job to the next java 9 ea... (#139 -> #142)
And I'll create another Java9 job, let's try plugin tools.
On Sun, 13 Nov 2016 19:05:03 +0100, wrote:
yay!
- Mail original -
De: "Apache Jenkins Server"
À: schu...@apache.org,
I also have huge problems when downloading snapshots from that
repository. That also is *very* slow here.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
[INFO] [WARNING] Could not transfer metadata
org.apache.maven.artifact.repository.metadata.MetadataBridge@31da0344
from/to apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2):
Connect to repository.apache.org:443
[repository.apache.org/207.244.88.143] failed:
Am 11/13/16 um 19:56 schrieb Christian Schulte:
> Am 11/13/16 um 19:42 schrieb Christian Schulte:
>> Am 11/13/16 um 18:53 schrieb herve.bout...@free.fr:
>>> seems you missed
>>> https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
>>>
>
> Wait. I have
>
>
Am 11/13/16 um 19:42 schrieb Christian Schulte:
> Am 11/13/16 um 18:53 schrieb herve.bout...@free.fr:
>> seems you missed
>> https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
>>
Wait. I have
-Djava.net.useSystemProxies=true
-Dhttp.keepAlive=false
Am 11/13/16 um 18:53 schrieb herve.bout...@free.fr:
> seems you missed
> https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
>
Settings should be fine. I already tried to increase the timeouts like
so in every server declaration.
Github user hboutemy commented on the issue:
https://github.com/apache/maven/pull/94
let's help: I dug into core-its, to find what existing IT to extend, since
.mvn feature should have an IT already
=> found mng-5771-core-extensions IT, which already tests 3 conditions: I
think
yay!
- Mail original -
De: "Apache Jenkins Server"
À: schu...@apache.org, micha...@apache.org, rfscho...@apache.org,
notificati...@maven.apache.org
Envoyé: Samedi 12 Novembre 2016 21:43:19
Objet: maven-3.x Jigsaw - Build # 10 - Fixed
The Apache Jenkins build
seems you missed
https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
Regards,
Hervé
- Mail original -
De: "Christian Schulte"
À: "Maven Developers List"
Envoyé: Dimanche 13 Novembre 2016 17:56:30
Objet: Releasing
Github user rpatrick00 commented on the issue:
https://github.com/apache/maven/pull/94
@michael-o, while I have no problem contributing, I have no familiarity
with the maven-integration-test project so it will likely take me some time to
reverse engineer it enough to figure out how
Hi,
this is the first time I am releasing a plugin. I've read the release
process documentation and am currently at the 'release:perform' step.
It's not possible for me to deploy to the repository. I tried it several
times now. It always fails with:
[INFO] [WARNING] Could not transfer metadata
Am 11/13/16 um 13:26 schrieb Guillaume Boué:
> Hi,
>
> About the OS name printed, it's a bug in Java 7, that is fixed for 9 and
> was backported down to 8u60, see
> https://bugs.openjdk.java.net/browse/JDK-8066504. This is what I have on
> my machine with Java 8u102:
>
> Apache Maven
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/131
---
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
Hi,
About the OS name printed, it's a bug in Java 7, that is fixed for 9 and
was backported down to 8u60, see
https://bugs.openjdk.java.net/browse/JDK-8066504. This is what I have on
my machine with Java 8u102:
Apache Maven 3.4.0-SNAPSHOT
(NON-CANONICAL_2016-11-12T18:53:10+01:00_Guillaume;
Am 2016-11-13 um 09:18 schrieb herve.bout...@free.fr:
no MSITE issue was created AFAIK this is classical issue with
dependencies: how to clearly show what is fixed by dependencies and
what is fixed directly by the released code if you have ideas on how
to better show this without giving too much
perhaps there are issue in how Maven sees some Windows OS: I don't have such
machines at hand to clearly tell how each precise OS version is displayed
Perhaps a Wiki page to have people fill cases could be useful
At least now, I see there are 2 versions that require precise tests: Windows 10
Pro
no MSITE issue was created AFAIK
this is classical issue with dependencies: how to clearly show what is fixed by
dependencies and what is fixed directly by the released code
if you have ideas on how to better show this without giving too much work
(abolutely requiring to create one MSITE issue
26 matches
Mail list logo