Github user asfgit closed the pull request at:
https://github.com/apache/maven-plugins/pull/85
---
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 feature i
Github user asfgit closed the pull request at:
https://github.com/apache/maven-wagon/pull/20
---
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 feature is
Hi,
On 5/29/16 12:23 AM, Karl Heinz Marbaise wrote:
Hi,
We have solved 5 issues:
Should be 8 issues...
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20fixVersion%20%3D%20maven-shared-utils-3.0.1
There are still a couple of issues left in JIRA:
https://issues.ap
Hi,
We have solved 5 issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20fixVersion%20%3D%20maven-shared-utils-3.0.1
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20component%20%3D%20maven-
Hi,
We have solved 5 issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20fixVersion%20%3D%20maven-filtering-3.1.1
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20component%20%3D%20maven-fil
Github user michael-o commented on the pull request:
https://github.com/apache/maven-plugin-testing/pull/3#issuecomment-222330604
PR has been merged. Please close.
---
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 p
Github user pono closed the pull request at:
https://github.com/apache/maven-release/pull/3
---
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 feature is e
Github user pono closed the pull request at:
https://github.com/apache/maven-release/pull/2
---
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 feature is e
Github user pono closed the pull request at:
https://github.com/apache/maven-plugin-tools/pull/1
---
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 feature
Github user pono closed the pull request at:
https://github.com/apache/maven-plugin-tools/pull/2
---
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 feature
Github user pono closed the pull request at:
https://github.com/apache/maven-shared/pull/4
---
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 feature is en
Github user pono closed the pull request at:
https://github.com/apache/maven-release/pull/5
---
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 feature is e
Github user pono closed the pull request at:
https://github.com/apache/maven-enforcer/pull/1
---
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 feature is
Github user pono closed the pull request at:
https://github.com/apache/maven-doxia/pull/1
---
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 feature is ena
Github user pono closed the pull request at:
https://github.com/apache/maven-enforcer/pull/2
---
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 feature is
Github user pono closed the pull request at:
https://github.com/apache/maven-shared/pull/6
---
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 feature is en
Github user pono closed the pull request at:
https://github.com/apache/maven-shared/pull/5
---
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 feature is en
GitHub user august782 opened a pull request:
https://github.com/apache/maven/pull/86
Modifying test in DefaultWagonManagerTest
The two tests testGetMissingJar and testGetMissingJarForced have exactly
the same test bodies. From their names, it seems testGetMissingJarForced should
be
GitHub user pkozelka reopened a pull request:
https://github.com/apache/maven/pull/61
fix release profile to use source:jar-no-fork instead of source:jar
This fixes `release-profile` in Maven's default pom so that it invokes
`source:jar-no-fork` instead of `source:jar`, because the
Github user pono closed the pull request at:
https://github.com/apache/maven/pull/61
---
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 feature is enabled
Github user pono closed the pull request at:
https://github.com/apache/maven/pull/61
---
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 feature is enabled
Am 2016-05-28 um 13:32 schrieb Michael Osipov:
Hi folks,
just wanted to fix a few issues but wan't able to commit to the branch
and raised INFRA-11997 [1]. The branch is read only. Has this component
been retired w/o proper announcement or is that an error?
Michael
[1] https://issues.apache.o
Hi folks,
just wanted to fix a few issues but wan't able to commit to the branch
and raised INFRA-11997 [1]. The branch is read only. Has this component
been retired w/o proper announcement or is that an error?
Michael
[1] https://issues.apache.org/jira/browse/INFRA-11997
-
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 featu
Github user michael-o commented on the pull request:
https://github.com/apache/maven-wagon/pull/22#issuecomment-222300526
We don't use custom patched versions of our components (e.g., `flavio`
qualifier). Please redo or close this PR.
---
If your project is set up for it, you can rep
+1
Regards,
Hervé
Le samedi 28 mai 2016 00:42:00 Michael Osipov a écrit :
> Hi folks,
>
> I just have noticed that ASF Parent says:
>
>
>org.apache.maven.plugins
>maven-release-plugin
>2.5.3
>
> ...
> -Papache-release ${arguments}
> ..
>
>
>
> and Maven Pa
Github user asfgit closed the pull request at:
https://github.com/apache/maven/pull/85
---
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 feature is enable
On Sat, 28 May 2016 00:38:28 +0200, Michael Osipov
wrote:
Am 2016-05-28 um 00:21 schrieb Karl Heinz Marbaise:
Hi to all Devs,
I have made a setup for a toolchain example but I've found an issue
which i currently don't have good idea to solve.
https://github.com/khmarbaise/maven-toolchain-e
28 matches
Mail list logo
