[jira] (WAGON-416) Lightweight HTTP Wagon doesn't set Proxy-Authorization header
[
https://jira.codehaus.org/browse/WAGON-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek updated WAGON-416:
---
Summary: Lightweight HTTP Wagon doesn't set Proxy-Authorization header
(was: Lightweight HTTP Wagon doesn't set Proxy-Authorization headers)
> Lightweight HTTP Wagon doesn't set Proxy-Authorization header
> -
>
> Key: WAGON-416
> URL: https://jira.codehaus.org/browse/WAGON-416
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http-lightweight
>Reporter: Grzegorz Grzybek
>
> When using
> {code:java}
> org.apache.maven.wagon.AbstractWagon#connect(org.apache.maven.wagon.repository.Repository,
> org.apache.maven.wagon.authentication.AuthenticationInfo,
> org.apache.maven.wagon.proxy.ProxyInfoProvider)
> {code}
> method (using {{ProxyInfoProvider}}) the {{proxyInfo}} field in Wagon isn't
> initialized. Then, when connecting to secure HTTP proxy,
> {{Proxy-Authorization}} header is not set.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSITE-717) The generated xhtml document has the entire content on a single line
Herve Boutemy created MSITE-717: --- Summary: The generated xhtml document has the entire content on a single line Key: MSITE-717 URL: https://jira.codehaus.org/browse/MSITE-717 Project: Maven Site Plugin Issue Type: Improvement Components: doxia integration Affects Versions: 3.2 Reporter: Herve Boutemy fixed in DOXIA-405: need to upgrade to Doxia 1.4 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSITE-717) The generated xhtml document has the entire content on a single line
[ https://jira.codehaus.org/browse/MSITE-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MSITE-717. --- Resolution: Fixed Fix Version/s: 3.3 Assignee: Herve Boutemy > The generated xhtml document has the entire content on a single line > > > Key: MSITE-717 > URL: https://jira.codehaus.org/browse/MSITE-717 > Project: Maven Site Plugin > Issue Type: Improvement > Components: doxia integration >Affects Versions: 3.2 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 3.3 > > > fixed in DOXIA-405: need to upgrade to Doxia 1.4 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348845#comment-348845
]
Alexander Klimetschek edited comment on MRELEASE-875 at 6/26/14 9:39 PM:
-
h3. Issue with untracked files in git status --porcelain output
One problem (but not the only one) is in those lines:
{code}
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties
{code}
These prevent the {{git commit}} from happening - WARNING here is an
understatement, it should be ERROR since the execution is aborted and with no
commit the following steps won't work ;-)
The issue is that apparently in some git version the output of {{git status
--porcelain}} changed to show untracked files using the {{??}} markers, and
this will hit the 2 files that the maven release always creates,
{{pom.xml.releaseBackup}} {{release.properties}}.
>From what I can see the problem was actually just recently introduced by
>SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit
>[fa5b0dd8|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=blobdiff;f=maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java;h=11c541a169d32c388547f3e73b25c935ee198db8;hp=d9cc75a9b5c4b8421465d29e48ffa4bc51dd3c7f;hb=fa5b0dd8f01da05f2e67be412bff231a620c295c;hpb=c96ca2477eb0c8227631784417173afa7805a410]
> which made it fail on unknown lines (such as ??) instead of ignoring it as
>before.
So one can fix that by telling git to not output any untracked files (??) by
setting the git config {{status.showUntrackedFiles = no}}.
**However**, after doing so, those WARNING lines are gone (good), but still the
{{git commit}} doesn't happen (bad). Something else must make the scm plugin
think there is no change to the pom.xml and not execute the commit (did not dig
deeper).
h3. Workaround
What worked for me was going back to an older release plugin, as @Martin Ellis
above did:
* git 2.0.0
* release plugin 2.3.2 (did not try other versions)
* git config: {{status.displayCommentPrefix = true}} (changed in git 1.8.5,
afaiu that's what the release plugin 2.5 tries to fix)
{code}
git config status.displayCommentPrefix true
mvn org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare
mvn org.apache.maven.plugins:maven-release-plugin:2.3.2:perform
{code}
was (Author: aklimets):
h3. Issue with untracked files in git status --porcelain output
One problem (but not the only one) is in those lines:
{code}
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties
{code}
These prevent the {{git commit}} from happening - WARNING here is an
understatement, it should be ERROR since the execution is aborted and with no
commit the following steps won't work ;-)
The issue is that apparently in some git version the output of {{git status
--porcelain}} changed to show untracked files using the {{??}} markers, and
this will hit the 2 files that the maven release always creates,
{{pom.xml.releaseBackup}} {{release.properties}}.
>From what I can see the problem was actually just recently introduced by
>SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit
>[fa5b0dd8|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=blobdiff;f=maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java;h=11c541a169d32c388547f3e73b25c935ee198db8;hp=d9cc75a9b5c4b8421465d29e48ffa4bc51dd3c7f;hb=fa5b0dd8f01da05f2e67be412bff231a620c295c;hpb=c96ca2477eb0c8227631784417173afa7805a410]
> which made it fail on unknown lines (such as ??) instead of ignoring it as
>before.
So one can fix that by telling git to not output any untracked files (??) by
setting the git config {{status.showUntrackedFiles = no}}.
**However**, after doing so, those WARNING lines are gone (good), but still the
{{git commit}} doesn't happen (bad). Something else must make the scm plugin
think there is no change to the pom.xml and not execute the commit (did not dig
deeper).
h3. Workaround
What worked for me was going back to an older release plugin, as @Martin Ellis
above did:
* git 2.0.0
* release plugin 2.3.2 (did not try other versions)
* git config: {{status.displayCommentPrefix = true}} (changed in git 1.8.5,
afaiu that's what the release plugin 2.5 tries to fix)
{code}
git config status.displayCommentPrefix true
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform
{code}
> release:prepare does not commit pom.xml if not in the git root
> -
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348845#comment-348845
]
Alexander Klimetschek edited comment on MRELEASE-875 at 6/26/14 9:37 PM:
-
h3. Issue with untracked files in git status --porcelain output
One problem (but not the only one) is in those lines:
{code}
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties
{code}
These prevent the {{git commit}} from happening - WARNING here is an
understatement, it should be ERROR since the execution is aborted and with no
commit the following steps won't work ;-)
The issue is that apparently in some git version the output of {{git status
--porcelain}} changed to show untracked files using the {{??}} markers, and
this will hit the 2 files that the maven release always creates,
{{pom.xml.releaseBackup}} {{release.properties}}.
>From what I can see the problem was actually just recently introduced by
>SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit
>[fa5b0dd8|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=blobdiff;f=maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java;h=11c541a169d32c388547f3e73b25c935ee198db8;hp=d9cc75a9b5c4b8421465d29e48ffa4bc51dd3c7f;hb=fa5b0dd8f01da05f2e67be412bff231a620c295c;hpb=c96ca2477eb0c8227631784417173afa7805a410]
> which made it fail on unknown lines (such as ??) instead of ignoring it as
>before.
So one can fix that by telling git to not output any untracked files (??) by
setting the git config {{status.showUntrackedFiles = no}}.
**However**, after doing so, those WARNING lines are gone (good), but still the
{{git commit}} doesn't happen (bad). Something else must make the scm plugin
think there is no change to the pom.xml and not execute the commit (did not dig
deeper).
h3. Workaround
What worked for me was going back to an older release plugin, as @Martin Ellis
above did:
* git 2.0.0
* release plugin 2.3.2 (did not try other versions)
* git config: {{status.displayCommentPrefix = true}} (changed in git 1.8.5,
afaiu that's what the release plugin 2.5 tries to fix)
{code}
git config status.displayCommentPrefix true
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform
{code}
was (Author: aklimets):
h3. Issue with untracked files in git status --porcelain output
One problem (but not the only one) is in those lines:
{code}
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties
{code}
These prevent the {{git commit}} from happening - WARNING here is an
understatement, it should be ERROR since the execution is aborted and with no
commit the following steps won't work ;-)
The issue is that apparently in some git version the output of {{git status
--porcelain}} changed to show untracked files using the {{??}} markers, and
this will hit the 2 files that the maven release always creates,
{{pom.xml.releaseBackup}} {{release.properties}}.
>From what I can see the problem was actually just recently introduced by
>SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit
>[fa5b0dd8|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=blobdiff;f=maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java;h=11c541a169d32c388547f3e73b25c935ee198db8;hp=d9cc75a9b5c4b8421465d29e48ffa4bc51dd3c7f;hb=fa5b0dd8f01da05f2e67be412bff231a620c295c;hpb=c96ca2477eb0c8227631784417173afa7805a410]
> which made it fail on unknown lines (such as ??) instead of ignoring it as
>before.
So one can fix that by telling git to not output any untracked files (??) by
setting the git config {{status.showUntrackedFiles = no}}.
**However**, after doing so, those WARNING lines are gone (good), but still the
{{git commit}} doesn't happen (bad). Something else must make the scm plugin
think there is no change to the pom.xml and not execute the commit (did not dig
deeper).
h3. Workaround
What worked for me was going back to an older release plugin, as @Martin Ellis
above did:
* git 2.0.0
* release plugin 2.3.2 (did not try other versions)
* git config: {{status.displayCommentPrefix = true}} (changed in git 1.8.5,
afaiu that's what the release plugin 2.5 tries to fix)
{code}
git config status.displayCommentPrefix true
mvn maven-release-plugin:2.3.2:prepare
mvn maven-release-plugin:2.3.2:perform
{code}
> release:prepare does not commit pom.xml if not in the git root
> --
>
>
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348845#comment-348845
]
Alexander Klimetschek edited comment on MRELEASE-875 at 6/26/14 9:29 PM:
-
h3. Issue with untracked files in git status --porcelain output
One problem (but not the only one) is in those lines:
{code}
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties
{code}
These prevent the {{git commit}} from happening - WARNING here is an
understatement, it should be ERROR since the execution is aborted and with no
commit the following steps won't work ;-)
The issue is that apparently in some git version the output of {{git status
--porcelain}} changed to show untracked files using the {{??}} markers, and
this will hit the 2 files that the maven release always creates,
{{pom.xml.releaseBackup}} {{release.properties}}.
>From what I can see the problem was actually just recently introduced by
>SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit
>[fa5b0dd8|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=blobdiff;f=maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java;h=11c541a169d32c388547f3e73b25c935ee198db8;hp=d9cc75a9b5c4b8421465d29e48ffa4bc51dd3c7f;hb=fa5b0dd8f01da05f2e67be412bff231a620c295c;hpb=c96ca2477eb0c8227631784417173afa7805a410]
> which made it fail on unknown lines (such as ??) instead of ignoring it as
>before.
So one can fix that by telling git to not output any untracked files (??) by
setting the git config {{status.showUntrackedFiles = no}}.
**However**, after doing so, those WARNING lines are gone (good), but still the
{{git commit}} doesn't happen (bad). Something else must make the scm plugin
think there is no change to the pom.xml and not execute the commit (did not dig
deeper).
h3. Workaround
What worked for me was going back to an older release plugin, as @Martin Ellis
above did:
* git 2.0.0
* release plugin 2.3.2 (did not try other versions)
* git config: {{status.displayCommentPrefix = true}} (changed in git 1.8.5,
afaiu that's what the release plugin 2.5 tries to fix)
{code}
git config status.displayCommentPrefix true
mvn maven-release-plugin:2.3.2:prepare
mvn maven-release-plugin:2.3.2:perform
{code}
was (Author: aklimets):
h3. Issue with untracked files in git status --porcelain output
One problem (but not the only one) is in those lines:
{code}
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties
{code}
These prevent the {{git commit}} from happening - WARNING here is an
understatement, it should be ERROR since the execution is aborted and with no
commit the following steps won't work ;-)
The issue is that apparently in some git version the output of {{git status
--porcelain}} changed to show untracked files using the {{??}} markers, and
this will hit the 2 files that the maven release always creates,
{{pom.xml.releaseBackup}} {{release.properties}}.
>From what I can see the problem was actually just recently introduced by
>SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit
>[fa5b0dd8|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=blobdiff;f=maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java;h=11c541a169d32c388547f3e73b25c935ee198db8;hp=d9cc75a9b5c4b8421465d29e48ffa4bc51dd3c7f;hb=fa5b0dd8f01da05f2e67be412bff231a620c295c;hpb=c96ca2477eb0c8227631784417173afa7805a410]
> which made it fail on unknown lines (such as ??) instead of ignoring it as
>before.
So one can fix that by telling git to not output any untracked files (??) by
setting the git config {{status.showUntrackedFiles = no}}.
**However**, after doing so, those WARNING lines are gone (good), but still the
{{git commit}} doesn't happen (bad). Something else must make the scm plugin
think there is no change to the pom.xml and not execute the commit (did not dig
deeper).
h3. Workaround
What worked for me was going back to an older release plugin, as @Martin Ellis
above did:
* git 2.0.0
* release plugin 2.3.2 (did not try other versions)
* git config: {{status.displayCommentPrefix = true}} (changed in git 1.8.5,
afaiu that's what the release plugin 2.5 tries to fix)
{code}
git config status.displayCommentPrefix false
mvn maven-release-plugin:2.3.2:prepare
mvn maven-release-plugin:2.3.2:perform
{code}
> release:prepare does not commit pom.xml if not in the git root
> --
>
> Key: MRELEASE-875
> URL:
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348845#comment-348845
]
Alexander Klimetschek edited comment on MRELEASE-875 at 6/26/14 9:28 PM:
-
h3. Issue with untracked files in git status --porcelain output
One problem (but not the only one) is in those lines:
{code}
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties
{code}
These prevent the {{git commit}} from happening - WARNING here is an
understatement, it should be ERROR since the execution is aborted and with no
commit the following steps won't work ;-)
The issue is that apparently in some git version the output of {{git status
--porcelain}} changed to show untracked files using the {{??}} markers, and
this will hit the 2 files that the maven release always creates,
{{pom.xml.releaseBackup}} {{release.properties}}.
>From what I can see the problem was actually just recently introduced by
>SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit
>[fa5b0dd8|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=blobdiff;f=maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java;h=11c541a169d32c388547f3e73b25c935ee198db8;hp=d9cc75a9b5c4b8421465d29e48ffa4bc51dd3c7f;hb=fa5b0dd8f01da05f2e67be412bff231a620c295c;hpb=c96ca2477eb0c8227631784417173afa7805a410]
> which made it fail on unknown lines (such as ??) instead of ignoring it as
>before.
So one can fix that by telling git to not output any untracked files (??) by
setting the git config {{status.showUntrackedFiles = no}}.
**However**, after doing so, those WARNING lines are gone (good), but still the
{{git commit}} doesn't happen (bad). Something else must make the scm plugin
think there is no change to the pom.xml and not execute the commit (did not dig
deeper).
h3. Workaround
What worked for me was going back to an older release plugin, as @Martin Ellis
above did:
* git 2.0.0
* release plugin 2.3.2 (did not try other versions)
* git config: {{status.displayCommentPrefix = true}} (changed in git 1.8.5,
afaiu that's what the release plugin 2.5 tries to fix)
{code}
git config status.displayCommentPrefix false
mvn maven-release-plugin:2.3.2:prepare
mvn maven-release-plugin:2.3.2:perform
{code}
was (Author: aklimets):
h3. Issue with untracked files in git status --porcelain output
One problem (but not the only one) is in those lines:
{code}
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties
{code}
These prevent the {{git commit}} from happening - WARNING here is an
understatement, it should be ERROR since the execution is aborted and with no
commit the following steps won't work ;-)
The issue is that apparently in some git version the output of {{git status
--porcelain}} changed to show untracked files using the {{??}} markers, and
this will hit the 2 files that the maven release always creates,
{{pom.xml.releaseBackup}} {{release.properties}}.
>From what I can see the problem was actually just recently introduced by
>SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit
>[fa5b0dd8|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=blobdiff;f=maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java;h=11c541a169d32c388547f3e73b25c935ee198db8;hp=d9cc75a9b5c4b8421465d29e48ffa4bc51dd3c7f;hb=fa5b0dd8f01da05f2e67be412bff231a620c295c;hpb=c96ca2477eb0c8227631784417173afa7805a410]
> which made it fail on unknown lines (such as ??) instead of ignoring it as
>before.
So one can fix that by telling git to not output any untracked files (??) by
setting the git config {{status.showUntrackedFiles = no}}.
**However**, after doing so, those WARNING lines are gone (good), but still the
{{git commit}} doesn't happen (bad). Something else must make the scm plugin
think there is no change to the pom.xml and not execute the commit (did not dig
deeper).
h3. Workaround so far
What worked for me at some point was this combination:
* release plugin 2.3.2: {{mvn maven-release-plugin:2.3.2:prepare}} (did not try
other versions)
* git 2.0.0
* git config: {{status.displayCommentPrefix = true}} and
{{status.showUntrackedFiles = no}} (maybe optional)
> release:prepare does not commit pom.xml if not in the git root
> --
>
> Key: MRELEASE-875
> URL: https://jira.codehaus.org/browse/MRELEASE-875
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: pre
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348845#comment-348845
]
Alexander Klimetschek edited comment on MRELEASE-875 at 6/26/14 9:20 PM:
-
h3. Issue with untracked files in git status --porcelain output
One problem (but not the only one) is in those lines:
{code}
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties
{code}
These prevent the {{git commit}} from happening - WARNING here is an
understatement, it should be ERROR since the execution is aborted and with no
commit the following steps won't work ;-)
The issue is that apparently in some git version the output of {{git status
--porcelain}} changed to show untracked files using the {{??}} markers, and
this will hit the 2 files that the maven release always creates,
{{pom.xml.releaseBackup}} {{release.properties}}.
>From what I can see the problem was actually just recently introduced by
>SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit
>[fa5b0dd8|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=blobdiff;f=maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java;h=11c541a169d32c388547f3e73b25c935ee198db8;hp=d9cc75a9b5c4b8421465d29e48ffa4bc51dd3c7f;hb=fa5b0dd8f01da05f2e67be412bff231a620c295c;hpb=c96ca2477eb0c8227631784417173afa7805a410]
> which made it fail on unknown lines (such as ??) instead of ignoring it as
>before.
So one can fix that by telling git to not output any untracked files (??) by
setting the git config {{status.showUntrackedFiles = no}}.
**However**, after doing so, those WARNING lines are gone (good), but still the
{{git commit}} doesn't happen (bad). Something else must make the scm plugin
think there is no change to the pom.xml and not execute the commit (did not dig
deeper).
h3. Workaround so far
What worked for me at some point was this combination:
* release plugin 2.3.2: {{mvn maven-release-plugin:2.3.2:prepare}} (did not try
other versions)
* git 2.0.0
* git config: {{status.displayCommentPrefix = true}} and
{{status.showUntrackedFiles = no}} (maybe optional)
was (Author: aklimets):
h3. Issue with untracked files in git status --porcelain output
One problem (but not the only one) is in those lines:
{code}
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties
{code}
These prevent the {{git commit}} from happening - WARNING here is an
understatement, it should be ERROR since the execution is aborted and with no
commit the following steps won't work ;-)
The issue is that apparently in some git version the output of {{git status
--porcelain}} changed to show untracked files using the {{??}} markers, and
this will hit the 2 files that the maven release always creates,
{{pom.xml.releaseBackup}} {{release.properties}}.
>From what I can see the problem was actually just recently introduced by
>SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit
>[fa5b0dd8|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=blobdiff;f=maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java;h=11c541a169d32c388547f3e73b25c935ee198db8;hp=d9cc75a9b5c4b8421465d29e48ffa4bc51dd3c7f;hb=fa5b0dd8f01da05f2e67be412bff231a620c295c;hpb=c96ca2477eb0c8227631784417173afa7805a410]
> which made it fail on unknown lines (such as ??) instead of ignoring it as
>before.
So one can fix that by telling git to not output any untracked files (??) by
setting the git config {{status.showUntrackedFiles = no}}.
**However**, after doing so, those WARNING lines are gone (good), but still the
{{git commit}} doesn't happen (bad). Something else must make the scm plugin
think there is no change to the pom.xml and not execute the commit (did not dig
deeper).
h3. Workaround so far
What worked for me at some point was this combination:
* release plugin 2.3.2: {{mvn maven-release-plugin:2.3.2:prepare}} (did not try
other versions)
* git config: {{status.displayCommentPrefix = true}} and
{{status.showUntrackedFiles = no}} (maybe optional)
> release:prepare does not commit pom.xml if not in the git root
> --
>
> Key: MRELEASE-875
> URL: https://jira.codehaus.org/browse/MRELEASE-875
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.5
> Environment: git 1.9.0
>Reporter: john ten Den
>
> When the project pom.xml is not in the Git project
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[ https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348843#comment-348843 ] Alexander Klimetschek edited comment on MRELEASE-875 at 6/26/14 9:20 PM: - Same issue here, with git 1.8.5.2 or 1.9.3 or 2.0.0 plus maven-release-plugin 2.5. was (Author: aklimets): Same issue here, with git 1.8.5.2 or 1.9.3 plus maven-release-plugin 2.5. > release:prepare does not commit pom.xml if not in the git root > -- > > Key: MRELEASE-875 > URL: https://jira.codehaus.org/browse/MRELEASE-875 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.5 > Environment: git 1.9.0 >Reporter: john ten Den > > When the project pom.xml is not in the Git project root (f.e. in the "src" > directory) the pom.xml not committed and pushed (before tagging) > Commit of the pom.xml during release:prepare works fine if it is in the / > (root) of the git repository > Using the pom.xml in a subdirectory worked well with version 2.4.2 using git > 1.7. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[
https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348845#comment-348845
]
Alexander Klimetschek commented on MRELEASE-875:
h3. Issue with untracked files in git status --porcelain output
One problem (but not the only one) is in those lines:
{code}
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? bundles/s7imaging/release.properties
{code}
These prevent the {{git commit}} from happening - WARNING here is an
understatement, it should be ERROR since the execution is aborted and with no
commit the following steps won't work ;-)
The issue is that apparently in some git version the output of {{git status
--porcelain}} changed to show untracked files using the {{??}} markers, and
this will hit the 2 files that the maven release always creates,
{{pom.xml.releaseBackup}} {{release.properties}}.
>From what I can see the problem was actually just recently introduced by
>SCM-709 (scm 1.9, maven-release-plugin 2.5 afaik) and commit
>[fa5b0dd8|https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=blobdiff;f=maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/src/main/java/org/apache/maven/scm/provider/git/gitexe/command/status/GitStatusConsumer.java;h=11c541a169d32c388547f3e73b25c935ee198db8;hp=d9cc75a9b5c4b8421465d29e48ffa4bc51dd3c7f;hb=fa5b0dd8f01da05f2e67be412bff231a620c295c;hpb=c96ca2477eb0c8227631784417173afa7805a410]
> which made it fail on unknown lines (such as ??) instead of ignoring it as
>before.
So one can fix that by telling git to not output any untracked files (??) by
setting the git config {{status.showUntrackedFiles = no}}.
**However**, after doing so, those WARNING lines are gone (good), but still the
{{git commit}} doesn't happen (bad). Something else must make the scm plugin
think there is no change to the pom.xml and not execute the commit (did not dig
deeper).
h3. Workaround so far
What worked for me at some point was this combination:
* release plugin 2.3.2: {{mvn maven-release-plugin:2.3.2:prepare}} (did not try
other versions)
* git config: {{status.displayCommentPrefix = true}} and
{{status.showUntrackedFiles = no}} (maybe optional)
> release:prepare does not commit pom.xml if not in the git root
> --
>
> Key: MRELEASE-875
> URL: https://jira.codehaus.org/browse/MRELEASE-875
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.5
> Environment: git 1.9.0
>Reporter: john ten Den
>
> When the project pom.xml is not in the Git project root (f.e. in the "src"
> directory) the pom.xml not committed and pushed (before tagging)
> Commit of the pom.xml during release:prepare works fine if it is in the /
> (root) of the git repository
> Using the pom.xml in a subdirectory worked well with version 2.4.2 using git
> 1.7.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SCM-740) Maven Release Plugin releases SNAPSHOT instead of STABLE version
[ https://jira.codehaus.org/browse/SCM-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348844#comment-348844 ] Alexander Klimetschek commented on SCM-740: --- See also MRELEASE-875, might be the same issue. > Maven Release Plugin releases SNAPSHOT instead of STABLE version > > > Key: SCM-740 > URL: https://jira.codehaus.org/browse/SCM-740 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git > Environment: Everywhere with maven-scm-provider-gitexe of version 1.9 > (and maybe older) >Reporter: Jan Novotný >Assignee: Mark Struberg > Fix For: 1.10 > > Attachments: Wrong_base_directory_used1.patch > > > If you have following project structure: > - superproject [Git repository root] > - projectA [release target] > - projectB [release target] > in other words you release subproject of a larger Git repository separately, > you probably run at the same issue as we did. No recipe from above mentioned > sources solves your problems and during release:prepare phase still no commit > of stable pom.xml occurs. There is another bug in GitStatusConsumer class > that checks output of the git status --porcelain command and verifies > existency of the mentioned files on local filesystem. Regretfully it uses > working directory instead of git repository root as the base folder and thus > it constructs invalid path to the file where project folder directory is > duplicated. > Problem is better described here: > http://blog.novoj.net/2014/01/24/maven-release-plugin-releases-snapshot-instead-of-stable-version -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MRELEASE-875) release:prepare does not commit pom.xml if not in the git root
[ https://jira.codehaus.org/browse/MRELEASE-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348843#comment-348843 ] Alexander Klimetschek commented on MRELEASE-875: Same issue here, with git 1.8.5.2 or 1.9.3 plus maven-release-plugin 2.5. > release:prepare does not commit pom.xml if not in the git root > -- > > Key: MRELEASE-875 > URL: https://jira.codehaus.org/browse/MRELEASE-875 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.5 > Environment: git 1.9.0 >Reporter: john ten Den > > When the project pom.xml is not in the Git project root (f.e. in the "src" > directory) the pom.xml not committed and pushed (before tagging) > Commit of the pom.xml during release:prepare works fine if it is in the / > (root) of the git repository > Using the pom.xml in a subdirectory worked well with version 2.4.2 using git > 1.7. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGELOG-138) Upgrade to newest Maven SCM
Karl-Heinz Marbaise created MCHANGELOG-138: -- Summary: Upgrade to newest Maven SCM Key: MCHANGELOG-138 URL: https://jira.codehaus.org/browse/MCHANGELOG-138 Project: Maven Changelog Plugin Issue Type: Improvement Affects Versions: 2.3 Reporter: Karl-Heinz Marbaise Priority: Minor May be do this after the current release has made it to central. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGELOG-138) Upgrade to newest Maven SCM
[ https://jira.codehaus.org/browse/MCHANGELOG-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MCHANGELOG-138: --- Fix Version/s: future-release > Upgrade to newest Maven SCM > --- > > Key: MCHANGELOG-138 > URL: https://jira.codehaus.org/browse/MCHANGELOG-138 > Project: Maven Changelog Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: future-release > > > May be do this after the current release has made it to central. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5657) distributionManagement moved it to settings.xml but out of the pom
[
https://jira.codehaus.org/browse/MNG-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348840#comment-348840
]
Robert Scholte commented on MNG-5657:
-
{{settings.xml}} won't work. How would you separate your deployments to the
Apache and Codehaus Repositories? It's project-specific information, not system
specific. And yes, in the end only m-deploy-p and m-site-p are interested in
this information, that could be the right path.
> distributionManagement moved it to settings.xml but out of the pom
> --
>
> Key: MNG-5657
> URL: https://jira.codehaus.org/browse/MNG-5657
> Project: Maven
> Issue Type: Improvement
> Components: FDPFC
>Reporter: Karl-Heinz Marbaise
>
> I would suggest to remove the distributionManagement out of the pom. It could
> be part of the settings.xml file
> As far as i remember there are plans to move the site distribution already
> out of the pom...
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348839#comment-348839
]
Karl-Heinz Marbaise commented on MINVOKER-166:
--
Cody could you do a retest on your build (mvn -U ...) with a new SNAPSHOT?
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Blocker
> Fix For: 1.8.1
>
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGELOG-123) Patch with support for SCM provider implementations (similar to release plugin)
[
https://jira.codehaus.org/browse/MCHANGELOG-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MCHANGELOG-123:
-
Description:
Hi,
The attached patch includes support for SCM 'provider implementations', similar
to what is included in the Maven Release Plugin. I made this change because I
wanted to use the Changelog plugin with the maven-scm-provider-svnjava project
(an SVN provider that uses SVNkit):
http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/
I can confirm the patch works, and appears to generate a valid changelog report
in the Maven site, when used with Maven 3.0.3 and a Maven project that follows
this example POM structure:
{code:xml}http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
uk.co.example
example-project
pom
1.0.0-SNAPSHOT
Example Project
http://example.co.uk/example-project
scm:svn:http://svn.example.co.uk/example-project/trunk
scm:svn:http://svn.example.co.uk/example-project/trunk
org.apache.maven.plugins
maven-changelog-plugin
2.3-SNAPSHOT
com.google.code.maven-scm-provider-svnjava
maven-scm-provider-svnjava
1.13
maven-site-plugin
3.0-beta-3
org.apache.maven.plugins
maven-changelog-plugin
[A-Z]{2,}-\d+
http://jira.example.co.uk
javasvn
{code}
was:
Hi,
The attached patch includes support for SCM 'provider implementations', similar
to what is included in the Maven Release Plugin. I made this change because I
wanted to use the Changelog plugin with the maven-scm-provider-svnjava project
(an SVN provider that uses SVNkit):
http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/
I can confirm the patch works, and appears to generate a valid changelog report
in the Maven site, when used with Maven 3.0.3 and a Maven project that follows
this example POM structure:
{noformat}
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
uk.co.example
example-project
pom
1.0.0-SNAPSHOT
Example Project
http://example.co.uk/example-project
scm:svn:http://svn.example.co.uk/example-project/trunk
scm:svn:http://svn.example.co.uk/example-project/trunk
org.apache.maven.plugins
maven-changelog-plugin
2.3-SNAPSHOT
com.google.code.maven-scm-provider-svnjava
maven-scm-provider-svnjava
1.13
maven-site-plugin
3.0-beta-3
org.apache.maven.plugins
maven-changelog-plugin
[A-Z]{2,}-\d+
http://jira.example.co.uk
javasvn
{noformat}
> Patch with support for SCM provider implementations (similar to release
> plugin)
> ---
>
> Key: MCHANGELOG-123
> URL: https://jira.codehaus.org/browse/MCHANGELOG-123
> Project: Maven Changelog Plugin
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Alex Coyle
>Assignee: Olivier Lamy
> Fix For: 2.3
>
> Attachments: maven-changelog-plugin-scmproviderimpl.patch
>
>
> Hi,
> The attached patch includes support for SCM 'provider implementations',
> similar to what is included in the Maven Release Plugin. I made this change
> because I wanted to use the Changelog plugin with the
> maven-scm-provider-svnjava project (an SVN provider that uses SVNkit):
> http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/
> I can confirm the patch works, and appears to generate a valid changelog
> report in the Maven site, when used with Maven 3.0.3 and a Maven project that
> follows this example POM structure:
> {code:xml}http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> 4.0.0
> uk.co.example
> example-project
> pom
> 1.0.0-SNAPSHOT
> Example Project
>
> http://example.co.uk/example-project
>
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MINVOKER-166.
Resolution: Fixed
I have been pointed out by the IT's that there was something wrong (Thanks
Robert for the hint about testing with older versions)
The following change [r1605914|http://svn.apache.org/r1605914] I have made
has been tested with the following Maven versions:
Maven 2.2.1
Maven 3.1.1
Maven 3.2.2
and works.
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Blocker
> Fix For: 1.8.1
>
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGELOG-108) read/write changelog.xml inconsistency
[
https://jira.codehaus.org/browse/MCHANGELOG-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MCHANGELOG-108:
-
Description:
ChangelogHandler.java:165
{code:java}bufSet.setStartVersion(new
ScmTag(attributes.getValue("startTag")));
bufSet.setEndVersion(new
ScmTag(attributes.getValue("endTag")));{code}
ChangeLogSet.java:180
{code:java}if ( startVersion != null )
{
buffer.append( " startVersion=\"" )
.append( getStartVersion() )
.append( "\"" );
}
if ( endVersion != null )
{
buffer.append( " endVersion=\"" )
.append( getEndVersion() )
.append( "\"" );
}{code}
Please fix field name to startVersion/endVersion.
When changelog.xml is present then settings like: type, range, dates should be
taken from this file during repoprt generation.
was:
ChangelogHandler.java:165
bufSet.setStartVersion(new ScmTag(attributes.getValue("startTag")));
bufSet.setEndVersion(new ScmTag(attributes.getValue("endTag")));
ChangeLogSet.java:180
if ( startVersion != null )
{
buffer.append( " startVersion=\"" )
.append( getStartVersion() )
.append( "\"" );
}
if ( endVersion != null )
{
buffer.append( " endVersion=\"" )
.append( getEndVersion() )
.append( "\"" );
}
Please fix field name to startVersion/endVersion.
When changelog.xml is present then settings like: type, range, dates should be
taken from this file during repoprt generation.
> read/write changelog.xml inconsistency
> --
>
> Key: MCHANGELOG-108
> URL: https://jira.codehaus.org/browse/MCHANGELOG-108
> Project: Maven Changelog Plugin
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Grzegorz Kochanski
>Assignee: Dennis Lundberg
>Priority: Minor
> Fix For: 2.3
>
> Attachments: MCHANGELOG-108-useTagNamesFromChangeLogSetClass.patch
>
>
> ChangelogHandler.java:165
> {code:java}bufSet.setStartVersion(new
> ScmTag(attributes.getValue("startTag")));
> bufSet.setEndVersion(new
> ScmTag(attributes.getValue("endTag")));{code}
> ChangeLogSet.java:180
> {code:java}if ( startVersion != null )
> {
> buffer.append( " startVersion=\"" )
> .append( getStartVersion() )
> .append( "\"" );
> }
> if ( endVersion != null )
> {
> buffer.append( " endVersion=\"" )
> .append( getEndVersion() )
> .append( "\"" );
> }{code}
> Please fix field name to startVersion/endVersion.
> When changelog.xml is present then settings like: type, range, dates should
> be taken from this file during repoprt generation.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348837#comment-348837
]
Cody Fyler commented on MINVOKER-166:
-
Yuck. Can't you just check the currently running maven version?
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Blocker
> Fix For: 1.8.1
>
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348836#comment-348836
]
Robert Scholte commented on MINVOKER-166:
-
You probably need to verify with reflection if the method exists...
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Blocker
> Fix For: 1.8.1
>
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348835#comment-348835
]
Karl-Heinz Marbaise commented on MINVOKER-166:
--
Cool Cody. Now i'm facing an issue with Maven 2.2.1 but i'm working on it...
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Blocker
> Fix For: 1.8.1
>
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348834#comment-348834
]
Cody Fyler commented on MINVOKER-166:
-
My build with 3.2.2 completed successfully.
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Blocker
> Fix For: 1.8.1
>
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5658) Syntax error in bin/mvn on Solaris SPARC
Frank Langelage created MNG-5658: Summary: Syntax error in bin/mvn on Solaris SPARC Key: MNG-5658 URL: https://jira.codehaus.org/browse/MNG-5658 Project: Maven Issue Type: Bug Affects Versions: 3.2.2 Environment: Solaris SPARC 10 with Oracle JDK 1.7.0_60 Reporter: Frank Langelage The latest addition to bin/mvn breaks mvn running on Solaris. Syntax error in line 86. The Bourne shell /bin/sh does not understand this syntax with the brackets. if [[ -z "$JAVA_HOME" && -x /usr/libexec/java_home ]] ; then # # Apple JDKs # export JAVA_HOME=$(/usr/libexec/java_home) fi ;; changing the line with the assignment to export JAVA_HOME=/usr/libexec/java_home like the lines before makes it running again. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise reopened MINVOKER-166:
--
My tests with Maven 2.2.1 failed.
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Blocker
> Fix For: 1.8.1
>
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5657) distributionManagement moved it to settings.xml but out of the pom
[ https://jira.codehaus.org/browse/MNG-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348832#comment-348832 ] Karl-Heinz Marbaise commented on MNG-5657: -- Based on the hangout i understand that the parts of the for example distributionManagement like the site URL in this case should be handled by the maven-site-plugin, so the maven-deploy-plugin could handle the parts for snapshots and repository ? > distributionManagement moved it to settings.xml but out of the pom > -- > > Key: MNG-5657 > URL: https://jira.codehaus.org/browse/MNG-5657 > Project: Maven > Issue Type: Improvement > Components: FDPFC >Reporter: Karl-Heinz Marbaise > > I would suggest to remove the distributionManagement out of the pom. It could > be part of the settings.xml file > As far as i remember there are plans to move the site distribution already > out of the pom... > WDYT? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348831#comment-348831
]
Robert Scholte commented on MINVOKER-166:
-
Be sure to verify this with older Maven version too, at least with the one
specified as the prerequisite. I know it should be dead code, but IIRC this
code was required for a successful merge of the settings.xml
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Blocker
> Fix For: 1.8.1
>
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5657) distributionManagement moved it to settings.xml but out of the pom
[ https://jira.codehaus.org/browse/MNG-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MNG-5657: - Component/s: FDPFC > distributionManagement moved it to settings.xml but out of the pom > -- > > Key: MNG-5657 > URL: https://jira.codehaus.org/browse/MNG-5657 > Project: Maven > Issue Type: Improvement > Components: FDPFC >Reporter: Karl-Heinz Marbaise > > I would suggest to remove the distributionManagement out of the pom. It could > be part of the settings.xml file > As far as i remember there are plans to move the site distribution already > out of the pom... > WDYT? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MINVOKER-166.
Resolution: Fixed
Fix Version/s: 1.9
Assignee: Karl-Heinz Marbaise
Based on the feedback the problem is solved.
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Assignee: Karl-Heinz Marbaise
>Priority: Blocker
> Fix For: 1.8.1
>
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348829#comment-348829
]
Karl-Heinz Marbaise commented on MINVOKER-166:
--
Wow thanks for your support. So i can close the issue. All IT's working with
Maven 3.2.2 and i would say to create a bug fix release of Maven Invoker Plugin
which solves the bug.
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348828#comment-348828
]
Cody Fyler commented on MINVOKER-166:
-
It's a slow build, so it's taking a while, but so far, we are well past the
original error.
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5657) distributionManagement moved it to settings.xml but out of the pom
Karl-Heinz Marbaise created MNG-5657: Summary: distributionManagement moved it to settings.xml but out of the pom Key: MNG-5657 URL: https://jira.codehaus.org/browse/MNG-5657 Project: Maven Issue Type: Improvement Reporter: Karl-Heinz Marbaise I would suggest to remove the distributionManagement out of the pom. It could be part of the settings.xml file As far as i remember there are plans to move the site distribution already out of the pom... WDYT? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-3522) Cannot define Mojo execution order explicitly
[
https://jira.codehaus.org/browse/MNG-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-3522:
---
Summary: Cannot define Mojo execution order explicitly (was: Cannot define
execution order explicitly)
> Cannot define Mojo execution order explicitly
> -
>
> Key: MNG-3522
> URL: https://jira.codehaus.org/browse/MNG-3522
> Project: Maven
> Issue Type: New Feature
> Components: FDPFC, Plugins and Lifecycle
>Affects Versions: 2.0.9
>Reporter: Thomas Diesler
> Fix For: Issues to be reviewed for 3.x
>
>
> In this example antrun:run is excuted after dependency:copy-dependencies by
> virtue of plugin order. Preferable would be an explicit order definition. For
> example, a plugin could export a 'phase-id' that another uses in its 'phase'
> element.
> {code:xml}
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> copy-dependencies
> package
>
> copy-dependencies
>
>
>
> ${project.build.directory}/thirdparty
> true
>
>
>
>
>
> maven-antrun-plugin
>
>
> package
>
> run
>
>
>
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5650) Allow better profile support including custom profile activators
[ https://jira.codehaus.org/browse/MNG-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5650: --- Summary: Allow better profile support including custom profile activators (was: Allow custom profile activators) > Allow better profile support including custom profile activators > > > Key: MNG-5650 > URL: https://jira.codehaus.org/browse/MNG-5650 > Project: Maven > Issue Type: New Feature > Components: FDPFC, POM >Affects Versions: 3.2.2 >Reporter: Jason van Zyl > > It is no longer possible to create custom profile activators in Maven 3.x. > This is something that can be restored as part of a new format for the POM. > The profiles can be put in the . -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348826#comment-348826
]
Karl-Heinz Marbaise edited comment on MINVOKER-166 at 6/26/14 2:25 PM:
---
Hi Cody, do you have the possibility to test a snapshot version of this plugin
in the snapshot repository
https://repository.apache.org/content/groups/snapshots/ ? I have created a
snapshot version (1.9-SNAPSHOT). It would be nice if you could check your build
with it and give feedback if this solves the problem with Maven 3.2.2
[r1605886|http://svn.apache.org/r1605886].
was (Author: khmarbaise):
Hi Cody, do you have the possibility to test a snapshot version of this plugin
in the snapshot repository
https://repository.apache.org/content/groups/snapshots/ ? I have created a
snapshot version (1.9-SNAPSHOT). It would be nice if you could check your build
with it and give feedback if this solves the problem with Maven 3.2.2
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348826#comment-348826
]
Karl-Heinz Marbaise commented on MINVOKER-166:
--
Hi Cody, do you have the possibility to test a snapshot version of this plugin
in the snapshot repository
https://repository.apache.org/content/groups/snapshots/ ? I have created a
snapshot version (1.9-SNAPSHOT). It would be nice if you could check your build
with it and give feedback is this solves the problem with Maven 3.2.2
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348826#comment-348826
]
Karl-Heinz Marbaise edited comment on MINVOKER-166 at 6/26/14 2:17 PM:
---
Hi Cody, do you have the possibility to test a snapshot version of this plugin
in the snapshot repository
https://repository.apache.org/content/groups/snapshots/ ? I have created a
snapshot version (1.9-SNAPSHOT). It would be nice if you could check your build
with it and give feedback if this solves the problem with Maven 3.2.2
was (Author: khmarbaise):
Hi Cody, do you have the possibility to test a snapshot version of this plugin
in the snapshot repository
https://repository.apache.org/content/groups/snapshots/ ? I have created a
snapshot version (1.9-SNAPSHOT). It would be nice if you could check your build
with it and give feedback is this solves the problem with Maven 3.2.2
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348825#comment-348825
]
Karl-Heinz Marbaise commented on MINVOKER-166:
--
This reduced the location onto a very limited area which makes it simpler to
solve that problem.
Thanks for your help.
So the following area is the culprit (lines1110-) of AbstractInvokerMojo.java:
{code:java}
if ( dominantSettings.getRuntimeInfo() == null )
{
RuntimeInfo rtInfo = new RuntimeInfo( dominantSettings );
rtInfo.setFile( interpolatedSettingsFile );
dominantSettings.setRuntimeInfo( rtInfo );
}
{code}
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348823#comment-348823
]
Cody Fyler commented on MINVOKER-166:
-
That worked!
So I take it there is a bug in this section of code?
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348822#comment-348822
]
Karl-Heinz Marbaise edited comment on MINVOKER-166 at 6/26/14 1:03 PM:
---
Do you say it will fail on a pom artifact? Where you have packaging pom? If yes
there is something wrong with your project configuration which is an other
story...
Can you please remove the line
{code}
true
{code}
Just for checking it?
was (Author: khmarbaise):
Can you please remove the line
{code}
true
{code}
Just for checking it?
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348822#comment-348822
]
Karl-Heinz Marbaise commented on MINVOKER-166:
--
Can you please remove the line
{code}
true
{code}
Just for checking it?
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348819#comment-348819
]
Cody Fyler edited comment on MINVOKER-166 at 6/26/14 12:59 PM:
---
$ mvn -v
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e;
2014-06-17T08:51:42-05:00)
Maven home: C:\bin\apache-maven-3.2.2
Java version: 1.8.0_20-ea, vendor: Oracle Corporation
Java home: C:\Java\jdk1.8.0_20\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
I removed the parallel threads element, same error.
My test project has a parent pom with submodules of jar, war, aar, and mar
types. It fails at the top level on the parent pom.
was (Author: javacody):
$ mvn -v
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e;
2014-06-17T08:51:42-05:00)
Maven home: C:\bin\apache-maven-3.2.2
Java version: 1.8.0_20-ea, vendor: Oracle Corporation
Java home: C:\Java\jdk1.8.0_20\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
I removed the parallel threads element, same error.
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348819#comment-348819
]
Cody Fyler edited comment on MINVOKER-166 at 6/26/14 12:56 PM:
---
$ mvn -v
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e;
2014-06-17T08:51:42-05:00)
Maven home: C:\bin\apache-maven-3.2.2
Java version: 1.8.0_20-ea, vendor: Oracle Corporation
Java home: C:\Java\jdk1.8.0_20\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
I removed the parallel threads element, same error.
was (Author: javacody):
$ mvn -v
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e;
2014-06-17T08:51:42-05:00)
Maven home: C:\bin\apache-maven-3.2.2
Java version: 1.8.0_20-ea, vendor: Oracle Corporation
Java home: C:\Java\jdk1.8.0_20\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5654) Move pluginManagement out of build area
[
https://jira.codehaus.org/browse/MNG-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MNG-5654.
Resolution: Won't Fix
Both of your arguments are really good so i close this issue. Thanks for
your comments.
> Move pluginManagement out of build area
> ---
>
> Key: MNG-5654
> URL: https://jira.codehaus.org/browse/MNG-5654
> Project: Maven
> Issue Type: Improvement
> Components: FDPFC
>Reporter: Karl-Heinz Marbaise
>
> The pluginManagement area has more or less the same meaning as
> dependencyManagement so it should also be located at the same level which
> means:
> {code:xml}
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348819#comment-348819
]
Cody Fyler commented on MINVOKER-166:
-
$ mvn -v
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e;
2014-06-17T08:51:42-05:00)
Maven home: C:\bin\apache-maven-3.2.2
Java version: 1.8.0_20-ea, vendor: Oracle Corporation
Java home: C:\Java\jdk1.8.0_20\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348817#comment-348817
]
Karl-Heinz Marbaise commented on MINVOKER-166:
--
I have found one thing which could be a problem you defined
{code}
4
{code}
which i known that it will not correctly work in some situations.
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348816#comment-348816
]
Karl-Heinz Marbaise commented on MINVOKER-166:
--
After checking i can't reproduce this failure that simple...Can you give more
details? Do you have a project which reproduces the problem ? May be you can
create something on Github or just attach it to this ticket...
{code}
mvn --version
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e;
2014-06-17T15:51:42+02:00)
Maven home: /usr/share/maven
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.8.5", arch: "x86_64", family: "mac"
{code}
Can you add the information as above..
I have tested it with other projects (maven-war-plugin, maven-ear-plugin, my
own projects...)...where i can't reproduce the problem...
> Failing in relationship with Maven 3.2.2
>
>
> Key: MINVOKER-166
> URL: https://jira.codehaus.org/browse/MINVOKER-166
> Project: Maven Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Maven 3.2.2
>Reporter: Karl-Heinz Marbaise
>Priority: Blocker
>
> Message of Cody Fyler on the users list:
> I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
> maven-invoker-plugin. Using Java 1.8.20.
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
> project base-pom: Execution integration-test of goal
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
> {code}
> Here is the configuration from my pom.xml:
> {code:xml}
>
> org.apache.maven.plugins
> maven-invoker-plugin
> 1.8
> false
>
>
> pre-integration-test
>
> install
>
>
>
> integration-test
>
> run
>
>
> false
>
> ${basedir}/src/test/resources/settings.xml
> true
> true
>
> ${project.build.directory}/it/projects
> true
> 4
>
> ${basedir}/src/test/resources/parent
>
>
> ${BUILD_NUMBER}
> true
> true
>
> ${BUILD_NUMBER}
>
> true
>
>
> ${basedir}/src/test/resources/parent/pom.xml
> true
> true
> true
> false
>
>
> install
> sonar:sonar
> release:prepare
> release:perform
>
>
>
>
>
>
> something.com
>
>
> ${localRepositoryPath}
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MINVOKER-166:
---
Description:
Message of Cody Fyler on the users list:
I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
maven-invoker-plugin. Using Java 1.8.20.
{noformat}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
project base-pom: Execution integration-test of goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
java.lang.NoSuchMethodError:
org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;{noformat}
Here is the configuration from my pom.xml:
{code:xml}
org.apache.maven.plugins
maven-invoker-plugin
1.8
false
pre-integration-test
install
integration-test
run
false
${basedir}/src/test/resources/settings.xml
true
true
${project.build.directory}/it/projects
true
4
${basedir}/src/test/resources/parent
${BUILD_NUMBER}
true
true
${BUILD_NUMBER}
true
${basedir}/src/test/resources/parent/pom.xml
true
true
true
false
install
sonar:sonar
release:prepare
release:perform
something.com
${localRepositoryPath}
{code}
was:
Message of Cody Fyler on the users list:
I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
maven-invoker-plugin. Using Java 1.8.20.
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
project base-pom: Execution integration-test of goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
java.lang.NoSuchMethodError:
org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
Here is the configuration from my pom.xml:
org.apache.maven.plugins
maven-invoker-plugin
1.8
false
pre-integration-test
install
integration-test
run
false
${basedir}/src/test/resources/settings.xml
true
true
${project.build.directory}/it/projects
true
4
${basedir}/src/test/resources/parent
${BUILD_NUMBER}
true
true
${BUILD_NUMBER}
true
${basedir}/src/test/resources/parent/pom.xml
true
true
true
false
install
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MINVOKER-166:
-
Description:
Message of Cody Fyler on the users list:
I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
maven-invoker-plugin. Using Java 1.8.20.
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
project base-pom: Execution integration-test of goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
java.lang.NoSuchMethodError:
org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
{code}
Here is the configuration from my pom.xml:
{code:xml}
org.apache.maven.plugins
maven-invoker-plugin
1.8
false
pre-integration-test
install
integration-test
run
false
${basedir}/src/test/resources/settings.xml
true
true
${project.build.directory}/it/projects
true
4
${basedir}/src/test/resources/parent
${BUILD_NUMBER}
true
true
${BUILD_NUMBER}
true
${basedir}/src/test/resources/parent/pom.xml
true
true
true
false
install
sonar:sonar
release:prepare
release:perform
something.com
${localRepositoryPath}
{code}
was:
Message of Cody Fyler on the users list:
I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
maven-invoker-plugin. Using Java 1.8.20.
{noformat}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
project base-pom: Execution integration-test of goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
java.lang.NoSuchMethodError:
org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;{noformat}
Here is the configuration from my pom.xml:
{code:xml}
org.apache.maven.plugins
maven-invoker-plugin
1.8
false
pre-integration-test
install
integration-test
run
false
${basedir}/src/test/resources/settings.xml
true
true
${project.build.directory}/it/projects
true
4
${basedir}/src/test/resources/parent
${BUILD_NUMBER}
true
true
${BUILD_NUMBER}
true
${basedir}/src/test/resources/parent/pom.xml
true
true
true
false
[jira] (MNG-5654) Move pluginManagement out of build area
[
https://jira.codehaus.org/browse/MNG-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348814#comment-348814
]
Jason van Zyl commented on MNG-5654:
I disagree with this as plugins are purely build-time related. Anything build
related should be in the element and then stripped out for consumption
use as it's not a requirement for consumption.
> Move pluginManagement out of build area
> ---
>
> Key: MNG-5654
> URL: https://jira.codehaus.org/browse/MNG-5654
> Project: Maven
> Issue Type: Improvement
> Components: FDPFC
>Reporter: Karl-Heinz Marbaise
>
> The pluginManagement area has more or less the same meaning as
> dependencyManagement so it should also be located at the same level which
> means:
> {code:xml}
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
[
https://jira.codehaus.org/browse/MINVOKER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MINVOKER-166:
-
Description:
Message of Cody Fyler on the users list:
I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
maven-invoker-plugin. Using Java 1.8.20.
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
project base-pom: Execution integration-test of goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
java.lang.NoSuchMethodError:
org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
Here is the configuration from my pom.xml:
org.apache.maven.plugins
maven-invoker-plugin
1.8
false
pre-integration-test
install
integration-test
run
false
${basedir}/src/test/resources/settings.xml
true
true
${project.build.directory}/it/projects
true
4
${basedir}/src/test/resources/parent
${BUILD_NUMBER}
true
true
${BUILD_NUMBER}
true
${basedir}/src/test/resources/parent/pom.xml
true
true
true
false
install
sonar:sonar
release:prepare
release:perform
something.com
${localRepositoryPath}
{code}
was:
I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
maven-invoker-plugin. Using Java 1.8.20.
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
project base-pom: Execution integration-test of goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
java.lang.NoSuchMethodError:
org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
Here is the configuration from my pom.xml:
org.apache.maven.plugins
maven-invoker-plugin
1.8
false
pre-integration-test
install
integration-test
run
false
${basedir}/src/test/resources/settings.xml
true
true
${project.build.directory}/it/projects
true
4
${basedir}/src/test/resources/parent
${BUILD_NUMBER}
true
true
${BUILD_NUMBER}
true
${basedir}/src/test/resources/parent/pom.xml
true
true
true
false
install
sonar:sonar
[jira] (MINVOKER-166) Failing in relationship with Maven 3.2.2
Karl-Heinz Marbaise created MINVOKER-166:
Summary: Failing in relationship with Maven 3.2.2
Key: MINVOKER-166
URL: https://jira.codehaus.org/browse/MINVOKER-166
Project: Maven Invoker Plugin
Issue Type: Bug
Affects Versions: 1.8
Environment: Maven 3.2.2
Reporter: Karl-Heinz Marbaise
Priority: Blocker
I just update to 3.2.2 from 3.2.1 and am now getting the error below from the
maven-invoker-plugin. Using Java 1.8.20.
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run (integration-test) on
project base-pom: Execution integration-test of goal
org.apache.maven.plugins:maven-invoker-plugin:1.8:run failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-invoker-plugin:1.8:run:
java.lang.NoSuchMethodError:
org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/settings/RuntimeInfo;
Here is the configuration from my pom.xml:
org.apache.maven.plugins
maven-invoker-plugin
1.8
false
pre-integration-test
install
integration-test
run
false
${basedir}/src/test/resources/settings.xml
true
true
${project.build.directory}/it/projects
true
4
${basedir}/src/test/resources/parent
${BUILD_NUMBER}
true
true
${BUILD_NUMBER}
true
${basedir}/src/test/resources/parent/pom.xml
true
true
true
false
install
sonar:sonar
release:prepare
release:perform
something.com
${localRepositoryPath}
{code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5656) Update maven-compiler-plugin in the default-bindings.xml
[ https://jira.codehaus.org/browse/MNG-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5656: --- Fix Version/s: 3.2.3 > Update maven-compiler-plugin in the default-bindings.xml > > > Key: MNG-5656 > URL: https://jira.codehaus.org/browse/MNG-5656 > Project: Maven > Issue Type: New Feature >Affects Versions: 3.2.2 >Reporter: Jason van Zyl > Fix For: 3.2.3 > > > The maven-compiler-plugin is currently pinned at 2.5.1 in the > default-bindings.xml in maven-core. Evaluate whether updating makes sense. I > think 3.1 has been out for quite a while. I believe the incremental behaviour > is broken though. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5656) Update maven-compiler-plugin in the default-bindings.xml
Jason van Zyl created MNG-5656: -- Summary: Update maven-compiler-plugin in the default-bindings.xml Key: MNG-5656 URL: https://jira.codehaus.org/browse/MNG-5656 Project: Maven Issue Type: New Feature Affects Versions: 3.2.2 Reporter: Jason van Zyl The maven-compiler-plugin is currently pinned at 2.5.1 in the default-bindings.xml in maven-core. Evaluate whether updating makes sense. I think 3.1 has been out for quite a while. I believe the incremental behaviour is broken though. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5655) WeakMojoExecutionListener callbacks invoked multiple times in some cases
[ https://jira.codehaus.org/browse/MNG-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko closed MNG-5655. --- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=963373726d900c8e093931af7baa94f3a08cb44d > WeakMojoExecutionListener callbacks invoked multiple times in some cases > > > Key: MNG-5655 > URL: https://jira.codehaus.org/browse/MNG-5655 > Project: Maven > Issue Type: Bug >Affects Versions: 3.1.1, 3.2.1, 3.2.2 >Reporter: Igor Fedorenko >Assignee: Igor Fedorenko > Fix For: 3.2.3 > > > When the same WeakMojoExecutionListener instance is injected under multiple > component Key's, the instance before/after execution callbacks are invoked > multiple times. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-416) Lightweight HTTP Wagon doesn't set Proxy-Authorization headers
[
https://jira.codehaus.org/browse/WAGON-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348786#comment-348786
]
Grzegorz Grzybek edited comment on WAGON-416 at 6/26/14 8:13 AM:
-
Pull Request ready: https://github.com/apache/maven-wagon/pull/11
The above pull request correctly sets the {{proxyInfo}} field in both
{{connect()}} variants (using ProxyInfo and ProxyInfoProvider). I've provided
also a test that shows the problem.
was (Author: gr.grzybek):
Pull Request ready: https://github.com/apache/maven-wagon/pull/11
> Lightweight HTTP Wagon doesn't set Proxy-Authorization headers
> --
>
> Key: WAGON-416
> URL: https://jira.codehaus.org/browse/WAGON-416
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http-lightweight
>Reporter: Grzegorz Grzybek
>
> When using
> {code:java}
> org.apache.maven.wagon.AbstractWagon#connect(org.apache.maven.wagon.repository.Repository,
> org.apache.maven.wagon.authentication.AuthenticationInfo,
> org.apache.maven.wagon.proxy.ProxyInfoProvider)
> {code}
> method (using {{ProxyInfoProvider}}) the {{proxyInfo}} field in Wagon isn't
> initialized. Then, when connecting to secure HTTP proxy,
> {{Proxy-Authorization}} header is not set.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (WAGON-416) Lightweight HTTP Wagon doesn't set Proxy-Authorization headers
[
https://jira.codehaus.org/browse/WAGON-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348785#comment-348785
]
Grzegorz Grzybek commented on WAGON-416:
The {{connect()}} method with {{ProxyInfoProvider}} is used by e.g.,
{{org.sonatype.aether.connector.wagon.WagonRepositoryConnector#connectWagon()}}
> Lightweight HTTP Wagon doesn't set Proxy-Authorization headers
> --
>
> Key: WAGON-416
> URL: https://jira.codehaus.org/browse/WAGON-416
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http-lightweight
>Reporter: Grzegorz Grzybek
>
> When using
> {code:java}
> org.apache.maven.wagon.AbstractWagon#connect(org.apache.maven.wagon.repository.Repository,
> org.apache.maven.wagon.authentication.AuthenticationInfo,
> org.apache.maven.wagon.proxy.ProxyInfoProvider)
> {code}
> method (using {{ProxyInfoProvider}}) the {{proxyInfo}} field in Wagon isn't
> initialized. Then, when connecting to secure HTTP proxy,
> {{Proxy-Authorization}} header is not set.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (WAGON-416) Lightweight HTTP Wagon doesn't set Proxy-Authorization headers
[
https://jira.codehaus.org/browse/WAGON-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=348786#comment-348786
]
Grzegorz Grzybek commented on WAGON-416:
Pull Request ready: https://github.com/apache/maven-wagon/pull/11
> Lightweight HTTP Wagon doesn't set Proxy-Authorization headers
> --
>
> Key: WAGON-416
> URL: https://jira.codehaus.org/browse/WAGON-416
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http-lightweight
>Reporter: Grzegorz Grzybek
>
> When using
> {code:java}
> org.apache.maven.wagon.AbstractWagon#connect(org.apache.maven.wagon.repository.Repository,
> org.apache.maven.wagon.authentication.AuthenticationInfo,
> org.apache.maven.wagon.proxy.ProxyInfoProvider)
> {code}
> method (using {{ProxyInfoProvider}}) the {{proxyInfo}} field in Wagon isn't
> initialized. Then, when connecting to secure HTTP proxy,
> {{Proxy-Authorization}} header is not set.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5655) WeakMojoExecutionListener callbacks invoked multiple times in some cases
Igor Fedorenko created MNG-5655: --- Summary: WeakMojoExecutionListener callbacks invoked multiple times in some cases Key: MNG-5655 URL: https://jira.codehaus.org/browse/MNG-5655 Project: Maven Issue Type: Bug Affects Versions: 3.2.1, 3.1.1, 3.2.2 Reporter: Igor Fedorenko When the same WeakMojoExecutionListener instance is injected under multiple component Key's, the instance before/after execution callbacks are invoked multiple times. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5655) WeakMojoExecutionListener callbacks invoked multiple times in some cases
[ https://jira.codehaus.org/browse/MNG-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko reassigned MNG-5655: --- Assignee: Igor Fedorenko > WeakMojoExecutionListener callbacks invoked multiple times in some cases > > > Key: MNG-5655 > URL: https://jira.codehaus.org/browse/MNG-5655 > Project: Maven > Issue Type: Bug >Affects Versions: 3.1.1, 3.2.1, 3.2.2 >Reporter: Igor Fedorenko >Assignee: Igor Fedorenko > Fix For: 3.2.3 > > > When the same WeakMojoExecutionListener instance is injected under multiple > component Key's, the instance before/after execution callbacks are invoked > multiple times. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5655) WeakMojoExecutionListener callbacks invoked multiple times in some cases
[ https://jira.codehaus.org/browse/MNG-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Fedorenko updated MNG-5655: Fix Version/s: 3.2.3 > WeakMojoExecutionListener callbacks invoked multiple times in some cases > > > Key: MNG-5655 > URL: https://jira.codehaus.org/browse/MNG-5655 > Project: Maven > Issue Type: Bug >Affects Versions: 3.1.1, 3.2.1, 3.2.2 >Reporter: Igor Fedorenko >Assignee: Igor Fedorenko > Fix For: 3.2.3 > > > When the same WeakMojoExecutionListener instance is injected under multiple > component Key's, the instance before/after execution callbacks are invoked > multiple times. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (WAGON-416) Lightweight HTTP Wagon doesn't set Proxy-Authorization headers
Grzegorz Grzybek created WAGON-416:
--
Summary: Lightweight HTTP Wagon doesn't set Proxy-Authorization
headers
Key: WAGON-416
URL: https://jira.codehaus.org/browse/WAGON-416
Project: Maven Wagon
Issue Type: Bug
Components: wagon-http-lightweight
Reporter: Grzegorz Grzybek
When using
{code:java}
org.apache.maven.wagon.AbstractWagon#connect(org.apache.maven.wagon.repository.Repository,
org.apache.maven.wagon.authentication.AuthenticationInfo,
org.apache.maven.wagon.proxy.ProxyInfoProvider)
{code}
method (using {{ProxyInfoProvider}}) the {{proxyInfo}} field in Wagon isn't
initialized. Then, when connecting to secure HTTP proxy,
{{Proxy-Authorization}} header is not set.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1082) Parallelization does not work as expected when using jUnit Parameterized
Bayley Gaillard created SUREFIRE-1082: - Summary: Parallelization does not work as expected when using jUnit Parameterized Key: SUREFIRE-1082 URL: https://jira.codehaus.org/browse/SUREFIRE-1082 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Reporter: Bayley Gaillard I am using jUnit's Parameterized annotation on some Selenium tests to specify the browsers they should run with. I am also using SureFire's new parallel parameter (set to "classes") to try and run them in parallel. However, this is nerfing the parallelization. Let's say I have my parameter list set to Firefox and Chrome, and I have 10 test classes. When I execute the tests with Maven, I'm seeing one Firefox window and one Chrome window appear on my remote server at a time. I expected to see 20 windows, 10 Firefox and 10 Chrome: one for each test class with each parameter. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
