jira-importer commented on issue #208:
URL:
https://github.com/apache/maven-install-plugin/issues/208#issuecomment-2771849887
**[Brett
Porter](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=brettporter)**
commented
fixing filing
--
This is an automated message fr
501956430 commented on issue #589:
URL: https://github.com/apache/maven-mvnd/issues/589#issuecomment-1018320749
@gnodet When to support?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the speci
gnodet commented on issue #589:
URL: https://github.com/apache/maven-mvnd/issues/589#issuecomment-1018310879
It looks like if Jenkins is trying to run `mvn mvnd` which will obviously
fail.
Please configure Jenkins correctly.
Also note that at this point, running `mvnd` inside a CI sys
gnodet closed issue #589:
URL: https://github.com/apache/maven-mvnd/issues/589
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@
501956430 opened a new issue #589:
URL: https://github.com/apache/maven-mvnd/issues/589
1、In container configuration information：
https://user-images.githubusercontent.com/20204491/150455225-ebe3ecab-f851-4bcd-9ddf-262ccff63bb2.png";>
2、jenkins build error：
http
marcphilipp closed pull request #334:
URL: https://github.com/apache/maven-surefire/pull/334
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above
Tibor17 commented on pull request #334:
URL: https://github.com/apache/maven-surefire/pull/334#issuecomment-791377408
@marcphilipp
The profile `jdk9+` was deleted. Now it is not needed. Feel free to close
this PR. thx T
mthmulders commented on pull request #334:
URL: https://github.com/apache/maven-surefire/pull/334#issuecomment-774744989
> @Tibor17 I think it's caused by this commit:
[apache/maven@8defd16#diff-690df442061d3325c6a7cf7b687e90ae79dd3639d45b8d1e606ad1bbc97a00e2](https://github.com/apache/mave
marcphilipp commented on pull request #334:
URL: https://github.com/apache/maven-surefire/pull/334#issuecomment-774730627
@Tibor17 I think it's caused by this commit:
https://github.com/apache/maven/commit/8defd169651db30fe0ac3ad3f318e471f0241d02#diff-690df442061d3325c6a7cf7b687e90ae79dd363
Tibor17 edited a comment on pull request #334:
URL: https://github.com/apache/maven-surefire/pull/334#issuecomment-774729429
It looks like something has changed in Maven. Was it reasonable change or it
is a bug in Maven. I checked Maven 3.6.3 and it worked fine. So i guess we
should start
Tibor17 commented on pull request #334:
URL: https://github.com/apache/maven-surefire/pull/334#issuecomment-774729429
It looks like something has changed in Maven. Was it reasonable change or it
is a bug in Maven. I checked Maven 3.6.3 and it work fine. So i guess we should
start with aski
marcphilipp commented on pull request #334:
URL: https://github.com/apache/maven-surefire/pull/334#issuecomment-772450994
@Tibor17 What name would you prefer?
This is an automated message from the Apache Git Service.
To respo
pzygielo commented on pull request #334:
URL: https://github.com/apache/maven-surefire/pull/334#issuecomment-772418612
> Removing the `+` from the profile name solves the issue.
But now the profile id does not cover the open range of JDKs. If `+` is
disallowed indeed - perhaps change
marcphilipp opened a new pull request #334:
URL: https://github.com/apache/maven-surefire/pull/334
With the latest Maven snapshot version based on
https://github.com/apache/maven/commit/eae3074c63dbba24680d7049dc36217323c7d00b,
the build fails with the following exception:
$ mvn
availabe in Central, I see no bug in Maven here.
> Maven build error when upgrade to 3.6.3
> ---
>
> Key: MNG-6822
> URL: https://issues.apache.org/jira/browse/MNG-6822
> Project: Maven
> Issue T
ery old apache parent
{quote}
We will update pom file soon
> Maven build error when upgrade to 3.6.3
> ---
>
> Key: MNG-6822
> URL: https://issues.apache.org/jira/browse/MNG-6822
> Project: Maven
>
try to skip Tests first, you will get the same error with me.
{quote}By having a short look into your pom file you are using very old plugin
versions...very old apache parent
{quote}
We will update pom file soon
> Maven build error when upgrade to 3.6.3
> -
, you will get the same error with me.
{quote}By having a short look into your pom file you are using very old plugin
versions...very old apache parent
{quote}
We will update pom file soon
> Maven build error when upgrade to 3.6.3
> ---
>
>
ve 10.14.4
JDK: "1.8.0_221"
Maven: 3.6.2
latest submarine version
If we use maven-3.6.1, it can successfully build the project.
We can't resolve this problem in our community , so I post here and try to
figure out the error.
> Maven
marine version
If we use maven-3.6.1, it can successfully build the project.
We can't resolve this problem in our community , so I post here and try to
figure out the error.
> Maven build error when upgrade to 3.6.3
> ---
>
>
;t resolve this problem in our community , so I post here and try to
figure out the error.
> Maven build error when upgrade to 3.6.3
> ---
>
> Key: MNG-6822
> URL: https://issues.apache.org/jira/browse/MNG-6822
>
se describe which exact state of the project you have referencing and which
exact calling parameters (profiles etc.) you have used.
> Maven build error when upgrade to 3.6.3
> ---
>
> Key: MNG-6822
> URL: https://issu
ttp://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
{code}
Please describe which exact state of the project you have referencing and which
exact calling parameters (profiles etc.) you have used.
> Maven build error when upgrade to 3.6.3
> ---
; Maven build error when upgrade to 3.6.3
> ---
>
> Key: MNG-6822
> URL: https://issues.apache.org/jira/browse/MNG-6822
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.6.2, 3.6.3
RROR] and
.
OS: macOS Mojave 10.14.4
JDK: "1.8.0_221"
Maven: 3.6.2
latest submarine version
If we use maven-3.6.1, it can successfully build the project.
We can't resolve this problem in our community , so I post here and try to
figure out the error.
> Maven
[
https://issues.apache.org/jira/browse/MNG-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated MNG-6822:
--
Summary: Maven build error when upgrade to 3.6.3 (was: Maven compile error
when upgrade to 3.6.3)
> Ma
a long period
of time. If you think this issue still persists, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Maven assembly plugin throws build error when a pom dependency has a version
> that contains the bracke
[
https://jira.codehaus.org/browse/MGPG-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MGPG-8:
--
Fix Version/s: (was: 1.0-alpha-4)
> Build error when plugin tries to sign nonexistent jar file in a
+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> Build error when publishing a new version of the site through the command
> line. Error: Embedded error: Unable to commit file. The svn command failed.
> svn: URL '-
Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> Usage dependency-plugin with source-plugin causes BUILD ERROR
> -
>
> Key: MSOURCES-32
> URL: https:/
[
https://jira.codehaus.org/browse/MASSEMBLY-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MASSEMBLY-453:
--
Summary: Maven assembly plugin throws build error when a pom dependency has
a version
Igor created MNG-5334:
-
Summary: Maven build error: The type or namespace name does not
exist in the namespace
Key: MNG-5334
URL: https://jira.codehaus.org/browse/MNG-5334
Project: Maven 2 & 3
I
eived.
The {{ArtifactDeployer}} has been rewritten for Maven 3 since the introduction
of Aether. Maybe the message has improved.
Anyhow, it's not a {{maven-release-plugin}} bug.
> Inadequate explanation of "BUILD ERROR:
[
https://jira.codehaus.org/browse/MRELEASE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MRELEASE-569:
Issue Type: Improvement (was: Bug)
> Inadequate explanation of "BUILD ERROR: ...
that this message should tell the user
that their authentication settings are incorrect.
Here is a rather complete explanation of what is wrong and how to set things up
properly:
http://www.sonatype.com/people/2010/11/what-to-do-when-nexus-returns-401/
> Inadequate explanation of "
The POM file is like this:
com.xxx.yyy
1.1.1
3.0.0
jar
1.0.0-SNAPSHOT
..
What should I do to solve this?
--
View this message in context:
http://maven.40175.n5.nabble.com/build-error-tp3259695p3259695.html
Sen
turn code for HTTP operation is: 401
Or:
Return code for HTTP operation is: 401. Check HTTP status codes here
http://www.w3.org/Protocols/HTTP/HTRESP.html
Instead of the following as it is vague:
Return code is: 401
> Inadequate explanation of "BUILD ERROR: Return
e settings.xml correctly
> Inadequate explanation of "BUILD ERROR: Return Code is 401"
>
>
> Key: MRELEASE-569
> URL: http://jira.codehaus.org/browse/MRELEASE-569
>
Inadequate explanation of "BUILD ERROR: Return Code is 401"
Key: MRELEASE-569
URL: http://jira.codehaus.org/browse/MRELEASE-569
Project: Maven 2.x Release Plugin
not using Subversion 1.5+
which is related to SCM-487).
> Build error when publishing a new version of the site through the command
> line. Error: Embedded error: Unable to commit file. The svn command failed.
> svn: URL '---
-scm-manager-plexus and
maven-scm-provider-svnexe. A different error related to plexus-utils occurs
instead for version 1.2 and 1.3-SNAPSHOT.
> Build error when publishing a new version of the site through the command
> line. Error: Embedded error: Unable to commit file. The svn comm
Build error when publishing a new version of the site through the command line.
Error: Embedded error: Unable to commit file. The svn command failed. svn: URL
'--' doe
age dependency-plugin with source-plugin causes BUILD ERROR
> -
>
> Key: MSOURCES-32
> URL: http://jira.codehaus.org/browse/MSOURCES-32
> Project: Maven 2.x Source Plugin
>
tion elements and it is being evaluated in the scope of a
cloned project which doesn't include the plugin definition.
> Usage dependency-plugin with source-plugin causes BUILD ERROR
> -
>
>
environment - more information would
be needed. Please post to the [EMAIL PROTECTED] list if you still have this
problem
> build error while building for a corporate
> --
>
> Key: WAGON-168
> URL: http://jira.code
: WAGON-168 (was: WAGONSSH-59)
Project: Maven Wagon (was: wagon-ssh)
> build error while building for a corporate
> --
>
> Key: WAGON-168
> URL: http://jira.codehaus.org/browse/WAGON-168
> Pr
ses BUILD ERROR
> -
>
> Key: MSOURCES-32
> URL: http://jira.codehaus.org/browse/MSOURCES-32
> Project: Maven 2.x Source Plugin
> Issue Type: Bug
> Environme
ncy-plugin with source-plugin causes BUILD ERROR
> -
>
> Key: MSOURCES-32
> URL: http://jira.codehaus.org/browse/MSOURCES-32
> Project: Maven 2.x Source Plugin
>
Usage dependency-plugin with source-plugin causes BUILD ERROR
-
Key: MSOURCES-32
URL: http://jira.codehaus.org/browse/MSOURCES-32
Project: Maven 2.x Source Plugin
Issue Type: Bug
eed to change into the project directory before executing 'mvn install'.
If you're still having trouble, please ask on the user list. You can find
subscription info here: http://maven.apache.org/mail-lists.html
> mvn install failed due to build error : Cannot execute mojo:
mvn install failed due to build error : Cannot execute mojo: resources. See
descr.
--
Key: MNG-3338
URL: http://jira.codehaus.org/browse/MNG-3338
Project: Maven 2
build error while building for a corporate
--
Key: WAGONSSH-59
URL: http://jira.codehaus.org/browse/WAGONSSH-59
Project: wagon-ssh
Issue Type: Bug
Reporter: deepak chavan
[INFO
annot reproduce it so I assume
it fixed.
> Build error when plugin tries to sign nonexistent jar file in a war module
> --
>
> Key: MGPG-8
> URL: http://jira.codeha
, I'll close it and release 1.0-alpha-4 that fixes a bunch of
the other bugs.
> Build error when plugin tries to sign nonexistent jar file in a war module
> --
>
> Key: MGPG-8
>
le of
days, and was about to comment that the issue seems to be fixed for us in
beta-2 too. Thank you for the fix.
> Build error when enqueing happens during SCM update
> ---
>
> Key: CONTINUUM-1384
>
: 1.1-beta-3
I tested with 1.1-beta-2/beta-3 with a schedule defined to every second to try
to reproduce this issue and all works fine without error
> Build error when enqueing happens during SCM update
> ---
>
> Key: CO
. The lifecycle executor should have a public method validate the
goals so that we don't want to prin the reactor projects first. The lifecycle
executor fires after we show the projects, but it's only inside the lifecycle
executor where the phase/goal is validated. Not very helpful.
> B
a problem in the reactor.
> Build error is ignored at the end of the build
> --
>
> Key: MNG-2938
> URL: http://jira.codehaus.org/browse/MNG-2938
> Project: Maven 2
> Issue Type: Bug
ple if you find this is still the case.
> Build error is ignored at the end of the build
> --
>
> Key: MNG-2938
> URL: http://jira.codehaus.org/browse/MNG-2938
> Project: Maven
Build error when enqueing happens during SCM update
---
Key: CONTINUUM-1384
URL: http://jira.codehaus.org/browse/CONTINUUM-1384
Project: Continuum
Issue Type: Bug
Affects Versions: 1.1
oblem
> Project build error null
>
>
> Key: MECLIPSE-311
> URL: http://jira.codehaus.org/browse/MECLIPSE-311
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
>Reporter: Thomas Hart
>
uld observe, it seems that the build fails when an scm update is
>being performed while the scheduler triggers a new build.
> Build Error while queueing projects to be built
> ---
>
> Key: CONTINUUM-384
>
Project build error null
Key: MECLIPSE-311
URL: http://jira.codehaus.org/browse/MECLIPSE-311
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Reporter: Thomas Hart
Priority: Critical
In
: Reviewed Pending Version Assignment)
2.1-alpha-1
> Build error is ignored at the end of the build
> --
>
> Key: MNG-2938
> URL: http://jira.codehaus.org/browse/MNG-2938
>
t snapshot. I remember building the plugin, but I might not have updated
the plugin version number in the pom. Jesse seems to have gotten it to work
for the Continuum release.
> Build error when plugin tries to sign nonexistent jar file in
Build error when plugin tries to sign nonexistent jar file in a war module
--
Key: MGPG-8
URL: http://jira.codehaus.org/browse/MGPG-8
Project: Maven 2.x GPG Plugin
Build error is ignored at the end of the build
--
Key: MNG-2938
URL: http://jira.codehaus.org/browse/MNG-2938
Project: Maven 2
Issue Type: Bug
Components: Command Line
Affects
[
http://jira.codehaus.org/browse/CONTINUUM-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse McConnell updated CONTINUUM-384:
--
Fix Version/s: 1.1-alpha-#
> Build Error while queueing projects to be bu
[ http://jira.codehaus.org/browse/CONTINUUM-925?page=all ]
Carlos Sanchez closed CONTINUUM-925.
Assignee: Carlos Sanchez (was: Lester Ecarma)
Resolution: Fixed
> build error not displayed in emails or web p
more
[INFO]
[INFO] Total time: < 1 second
[INFO] Finished at: Sun Sep 17 23:47:11 PDT 2006
[INFO] Final Memory: 1M/2M
[INFO] ----
> build error not displayed
-1] INFO org.apache.maven.continuum.scm.ContinuumScm -
Updating project: id: '41', name 'Maven User Management'.
> build error not displayed in emails or web page
> ---
>
> Key: CONTINUUM-925
>
[ http://jira.codehaus.org/browse/CONTINUUM-925?page=all ]
Carlos Sanchez updated CONTINUUM-925:
-
Fix Version/s: 1.1
> build error not displayed in emails or web page
> ---
>
>
build error not displayed in emails or web page
---
Key: CONTINUUM-925
URL: http://jira.codehaus.org/browse/CONTINUUM-925
Project: Continuum
Issue Type: Bug
Components: Mail Notifier
doesn't work on a fresh directory.
> build error while: mvn archetype:create -DgroupId=com.mycompany.app
> -DartifactId=my-app -DarchetypeGroupId=org.apache.maven.archetypes
> -Dar
build error while: mvn archetype:create -DgroupId=com.mycompany.app
-DartifactId=my-app -DarchetypeGroupId=org.apache.maven.archetypes
-DarchetypeArtifactId=maven-archetype-site
[ http://jira.codehaus.org/browse/CONTINUUM-662?page=all ]
Emmanuel Venisse closed CONTINUUM-662:
--
Assign To: Emmanuel Venisse
Resolution: Duplicate
Fix Version: (was: 1.1)
> "Show Projects" page shows a "Buil
[ http://jira.codehaus.org/browse/CONTINUUM-662?page=all ]
Emmanuel Venisse updated CONTINUUM-662:
---
Component: Web interface
> "Show Projects" page shows a "Build Error" icon, but clicking on the "Build"
> numb
[ http://jira.codehaus.org/browse/CONTINUUM-662?page=all ]
Emmanuel Venisse updated CONTINUUM-662:
---
Fix Version: 1.1
> "Show Projects" page shows a "Build Error" icon, but clicking on the "Build"
> numb
.
> "Show Projects" page shows a "Build Error" icon, but clicking on the "Build"
> number link, the State is "Build Success".
> ---
>
"Show Projects" page shows a "Build Error" icon, but clicking on the "Build"
number link, the State is "Build Success".
---
80 matches
Mail list logo
