[jira] [Commented] (MDEPLOY-267) add parameters to deploy or not non snapshots or release (-DskipRelease or -DskipSnapshot)
[
https://issues.apache.org/jira/browse/MDEPLOY-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109890#comment-17109890
]
Hudson commented on MDEPLOY-267:
Build succeeded in Jenkins: Maven TLP » maven-deploy-plugin »
MDEPLOY-267_skip_release_snapshot_deply_parameter #2
See
https://builds.apache.org/job/maven-box/job/maven-deploy-plugin/job/MDEPLOY-267_skip_release_snapshot_deply_parameter/2/
> add parameters to deploy or not non snapshots or release (-DskipRelease or
> -DskipSnapshot)
> --
>
> Key: MDEPLOY-267
> URL: https://issues.apache.org/jira/browse/MDEPLOY-267
> Project: Maven Deploy Plugin
> Issue Type: New Feature
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: 3.0.0
>
>
> maven-release-plugin creates a commit where the pom is not a SNAPSHOT
> version: if CI system is configured to build on every commit and to deploy
> the artifacts on every build (with the intent in general to deploy updated
> SNAPSHOTs on every commit), the CI will deploy the non-SNAPSHOT that has
> already been deployed by the user who launched {{mvn release:perform}}, then
> it will generate an error (trying to override existing release artifact)
> and/or create new staging repository and/or override artifacts partially (if
> repository not configured to block overrides)
> we can add a new parameter {{-DdeployOnlySnaphots=true/false}}: it will be
> false per default for normal use, but can be configured to true in users' CI
> system.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MDEPLOY-267) add parameters to deploy or not non snapshots or release (-DskipRelease or -DskipSnapshot)
[
https://issues.apache.org/jira/browse/MDEPLOY-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109889#comment-17109889
]
Olivier Lamy commented on MDEPLOY-267:
--
finally I changed skip to not being anymore a boolean.. easier to use but
breaks the common pattern we have in place.
> add parameters to deploy or not non snapshots or release (-DskipRelease or
> -DskipSnapshot)
> --
>
> Key: MDEPLOY-267
> URL: https://issues.apache.org/jira/browse/MDEPLOY-267
> Project: Maven Deploy Plugin
> Issue Type: New Feature
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
>Priority: Major
> Fix For: 3.0.0
>
>
> maven-release-plugin creates a commit where the pom is not a SNAPSHOT
> version: if CI system is configured to build on every commit and to deploy
> the artifacts on every build (with the intent in general to deploy updated
> SNAPSHOTs on every commit), the CI will deploy the non-SNAPSHOT that has
> already been deployed by the user who launched {{mvn release:perform}}, then
> it will generate an error (trying to override existing release artifact)
> and/or create new staging repository and/or override artifacts partially (if
> repository not configured to block overrides)
> we can add a new parameter {{-DdeployOnlySnaphots=true/false}}: it will be
> false per default for normal use, but can be configured to true in users' CI
> system.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MNGSITE-412) Add Reposilite to the list of available repository managers
[ https://issues.apache.org/jira/browse/MNGSITE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dzikoysk updated MNGSITE-412: - Summary: Add Reposilite to the list of available repository managers (was: Add NanoMaven to the list of available repository managers) > Add Reposilite to the list of available repository managers > --- > > Key: MNGSITE-412 > URL: https://issues.apache.org/jira/browse/MNGSITE-412 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: dzikoysk >Priority: Minor > > NanoMaven repository: https://github.com/dzikoysk/nanomaven > Motivation: Project is active for 3 years now and it is a good solution for > developers hosting their projects at low cost. > At this moment, people are forced to use huge ecosystems like Nexus or > Artifactory. I think it might be a good idea to show an alternative. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNGSITE-412) Add Reposilite to the list of available repository managers
[ https://issues.apache.org/jira/browse/MNGSITE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dzikoysk updated MNGSITE-412: - Description: Reposilite repository: https://github.com/dzikoysk/reposilite Motivation: Project is active for 3 years now and it is a good solution for developers hosting their projects at low cost. At this moment, people are forced to use huge ecosystems like Nexus or Artifactory. I think it might be a good idea to show an alternative. was: NanoMaven repository: https://github.com/dzikoysk/nanomaven Motivation: Project is active for 3 years now and it is a good solution for developers hosting their projects at low cost. At this moment, people are forced to use huge ecosystems like Nexus or Artifactory. I think it might be a good idea to show an alternative. > Add Reposilite to the list of available repository managers > --- > > Key: MNGSITE-412 > URL: https://issues.apache.org/jira/browse/MNGSITE-412 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: dzikoysk >Priority: Minor > > Reposilite repository: https://github.com/dzikoysk/reposilite > Motivation: Project is active for 3 years now and it is a good solution for > developers hosting their projects at low cost. > At this moment, people are forced to use huge ecosystems like Nexus or > Artifactory. I think it might be a good idea to show an alternative. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1570) Maven-fail-safe doesn't put testing JPMS module on module path
[
https://issues.apache.org/jira/browse/SUREFIRE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109705#comment-17109705
]
Tibor Digana commented on SUREFIRE-1570:
[~Pavel_K]
Check my commit above. There is the integration test motivated by your project.
Compare them.
> Maven-fail-safe doesn't put testing JPMS module on module path
> --
>
> Key: SUREFIRE-1570
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1570
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 2.22.0
>Reporter: Pavel_K
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M5
>
> Attachments: mavenproject20.zip
>
>
> I uploaded project - mavenproject20. Run `mvn verify`. You will see the
> following:
> {code:java}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building mavenproject20 0.1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> mavenproject20 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @
> mavenproject20 ---
> [WARNING]
>
> [WARNING] * Required filename-based automodules detected. Please don't
> publish this project to a public artifact repository! *
> [WARNING]
>
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 3 source files to
> /home/Jim/NetBeansProjects/mavenproject20/target/classes
> [WARNING]
> /home/Jim/NetBeansProjects/mavenproject20/src/main/java/module-info.java:[1,8]
> module name component Mavenproject20 should avoid terminal digits
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
> mavenproject20 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /home/Jim/NetBeansProjects/mavenproject20/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @
> mavenproject20 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/Jim/NetBeansProjects/mavenproject20/target/test-classes
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ mavenproject20
> ---
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ mavenproject20 ---
> [INFO] Building jar:
> /home/Jim/NetBeansProjects/mavenproject20/target/mavenproject20-0.1.0-SNAPSHOT.jar
> [INFO]
> [INFO] --- maven-failsafe-plugin:2.22.0:integration-test (integration-tests)
> @ mavenproject20 ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running me.pavel.mavenproject20.ServiceIT
> JDKModulePath:null
> ModuleName:null
> module jdk.unsupported
> module jdk.sctp
> module java.naming
> module java.jnlp
> module jdk.httpserver
> module java.xml
> module javafx.controls
> module java.datatransfer
> module jdk.javadoc
> module jdk.jconsole
> module java.instrument
> module jdk.packager
> module jdk.deploy
> module jdk.jfr
> module jdk.management
> module jdk.charsets
> module oracle.net
> module jdk.jdeps
> module java.sql.rowset
> module jdk.net
> module jdk.accessibility
> module jdk.attach
> module jdk.internal.le
> module jdk.snmp
> module java.base
> module jdk.plugin
> module jdk.dynalink
> module jdk.naming.rmi
> module jdk.internal.opt
> module java.management.rmi
> module jdk.management.jfr
> module javafx.swing
> module jdk.editpad
> module jdk.crypto.ec
> module jdk.javaws
> module jdk.jstatd
> module jdk.management.agent
> module javafx.graphics
> module javafx.media
> module java.rmi
> module java.prefs
> module jdk.security.jgss
> module javafx.fxml
> module java.smartcardio
> module jdk.xml.dom
> module java.xml.crypto
> module jdk.jsobject
> module jdk.jdi
> module jdk.compiler
> module java.management
> module jdk.management.cmm
> module jdk.packager.services
> module jdk.jartool
> module jdk.scripting.nashorn
> module java.security.jgss
> module jdk.localedata
> module java.desktop
> module jdk.zipfs
> module jdk.jshell
> module oracle.desktop
> module jdk.internal.ed
> module java.security.sasl
> module jdk.jdwp.agent
> module
[jira] [Closed] (WAGON-596) Add configuration property 'http.protocol.handle-uri-normalization'
[
https://issues.apache.org/jira/browse/WAGON-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed WAGON-596.
Resolution: Fixed
Fixed with
[4a9cdc2996e3f0f3ffa673f8d4ae4a0c051d0c41|https://gitbox.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=4a9cdc2996e3f0f3ffa673f8d4ae4a0c051d0c41].
> Add configuration property 'http.protocol.handle-uri-normalization'
> ---
>
> Key: WAGON-596
> URL: https://issues.apache.org/jira/browse/WAGON-596
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http
>Affects Versions: 3.4.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.4.1
>
>
> Add support for disabling/enabling URI normalization. The default value is
> {{true}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-shared-utils] roxspring commented on a change in pull request #31: [MSHARED-681] createSymbolicLink() overwrites existing different symlinks
roxspring commented on a change in pull request #31:
URL: https://github.com/apache/maven-shared-utils/pull/31#discussion_r426311011
##
File path: src/test/java/org/apache/maven/shared/utils/io/FileUtilsTest.java
##
@@ -1475,6 +1475,30 @@ public void createAndReadSymlink()
Files.delete( file.toPath() );
}
+@Test
+public void createSymbolicLinkWithDifferentTargetOverwritesSymlink()
+throws Exception
+{
+assumeThat( System.getProperty( "os.name" ), not( startsWith(
"Windows" ) ) );
Review comment:
An understandable concern. ~~Can the Jenkins results be seen somewhere
obvious?~~ I presume it'll appear at
https://builds.apache.org/job/maven-box/job/maven-shared-utils/ (it's a shame
they're not linked from the PR)
FWIW the condition was copied from the symlink test immediately above, which
itself was moved from `Java7SupportTest` only yesterday. Prior to that it
appears to have been unchanged here for 3 years:
https://github.com/apache/maven-shared-utils/blob/bb2f85e98c3c651ae50b7f642500cb74f50abb0d/src/test/java/org/apache/maven/shared/utils/io/Java7SupportTest.java#L50
On closer inspection it seems that `FileUtilsTest` is already making Windows
related assumptions in a variety of ways:
-
https://github.com/apache/maven-shared-utils/blob/bb2f85e98c3c651ae50b7f642500cb74f50abb0d/src/test/java/org/apache/maven/shared/utils/io/FileUtilsTest.java#L446
-
https://github.com/apache/maven-shared-utils/blob/92a5ba3c431affcabb2cebd11ca17fe02b15748c/src/test/java/org/apache/maven/shared/utils/io/FileUtilsTest.java#L1206
-
https://github.com/apache/maven-shared-utils/blob/92a5ba3c431affcabb2cebd11ca17fe02b15748c/src/test/java/org/apache/maven/shared/utils/io/FileUtilsTest.java#L1461
-
https://github.com/apache/maven-shared-utils/blob/92a5ba3c431affcabb2cebd11ca17fe02b15748c/src/test/java/org/apache/maven/shared/utils/io/FileUtilsTest.java#L1432
If there's a preferred approach to such assumptions then I'm happy to unify
on that - but perhaps in a separate PR?
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-shared-utils] roxspring commented on a change in pull request #31: [MSHARED-681] createSymbolicLink() overwrites existing different symlinks
roxspring commented on a change in pull request #31:
URL: https://github.com/apache/maven-shared-utils/pull/31#discussion_r426311011
##
File path: src/test/java/org/apache/maven/shared/utils/io/FileUtilsTest.java
##
@@ -1475,6 +1475,30 @@ public void createAndReadSymlink()
Files.delete( file.toPath() );
}
+@Test
+public void createSymbolicLinkWithDifferentTargetOverwritesSymlink()
+throws Exception
+{
+assumeThat( System.getProperty( "os.name" ), not( startsWith(
"Windows" ) ) );
Review comment:
An understandable concern. Can the Jenkins results be seen somewhere
obvious? (it's a shame they're not linked from the PR)
FWIW the condition was copied from the symlink test immediately above, which
itself was moved from `Java7SupportTest` only yesterday. Prior to that it
appears to have been unchanged here for 3 years:
https://github.com/apache/maven-shared-utils/blob/bb2f85e98c3c651ae50b7f642500cb74f50abb0d/src/test/java/org/apache/maven/shared/utils/io/Java7SupportTest.java#L50
On closer inspection it seems that `FileUtilsTest` is already making Windows
related assumptions in a variety of ways:
-
https://github.com/apache/maven-shared-utils/blob/bb2f85e98c3c651ae50b7f642500cb74f50abb0d/src/test/java/org/apache/maven/shared/utils/io/FileUtilsTest.java#L446
-
https://github.com/apache/maven-shared-utils/blob/92a5ba3c431affcabb2cebd11ca17fe02b15748c/src/test/java/org/apache/maven/shared/utils/io/FileUtilsTest.java#L1206
-
https://github.com/apache/maven-shared-utils/blob/92a5ba3c431affcabb2cebd11ca17fe02b15748c/src/test/java/org/apache/maven/shared/utils/io/FileUtilsTest.java#L1461
-
https://github.com/apache/maven-shared-utils/blob/92a5ba3c431affcabb2cebd11ca17fe02b15748c/src/test/java/org/apache/maven/shared/utils/io/FileUtilsTest.java#L1432
If there's a preferred approach to such assumptions then I'm happy to unify
on that - but perhaps in a separate PR?
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-shared-utils] elharo commented on a change in pull request #31: [MSHARED-681] createSymbolicLink() overwrites existing different symlinks
elharo commented on a change in pull request #31:
URL: https://github.com/apache/maven-shared-utils/pull/31#discussion_r426307551
##
File path: src/test/java/org/apache/maven/shared/utils/io/FileUtilsTest.java
##
@@ -1475,6 +1475,30 @@ public void createAndReadSymlink()
Files.delete( file.toPath() );
}
+@Test
+public void createSymbolicLinkWithDifferentTargetOverwritesSymlink()
+throws Exception
+{
+assumeThat( System.getProperty( "os.name" ), not( startsWith(
"Windows" ) ) );
Review comment:
I'm a little concerned this might not work (it doesn't in some repos for
reasons) so we need to check this in Jenkins to make sure it passes on windows.
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [maven-release] elharo merged pull request #54: Ignore .checkstyle
elharo merged pull request #54: URL: https://github.com/apache/maven-release/pull/54 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-scm] elharo merged pull request #99: [SCM-930] update plexus-utils
elharo merged pull request #99: URL: https://github.com/apache/maven-scm/pull/99 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-scm] elharo merged pull request #106: [SCM-941] fix path tests
elharo merged pull request #106: URL: https://github.com/apache/maven-scm/pull/106 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-assembly-plugin] elharo merged pull request #24: question mark
elharo merged pull request #24: URL: https://github.com/apache/maven-assembly-plugin/pull/24 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (MNGSITE-411) on website, Maven Issue Management page, markdown is showing in plaintext
[ https://issues.apache.org/jira/browse/MNGSITE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNGSITE-411. - Assignee: Herve Boutemy Resolution: Fixed workaround done in https://github.com/apache/maven-site/commit/8a4a0fc46273553b204a6aaf72a8b37458d7d1fd thanks for the report (don't hesitate to follow the "edit" icon and propose PRs to improve content) > on website, Maven Issue Management page, markdown is showing in plaintext > - > > Key: MNGSITE-411 > URL: https://issues.apache.org/jira/browse/MNGSITE-411 > Project: Maven Project Web Site > Issue Type: Bug > Environment: website >Reporter: Tim Stewart >Assignee: Herve Boutemy >Priority: Minor > Labels: typo, website > Attachments: markdownbroken.png > > > on page [https://maven.apache.org/issue-management.html], in the first > Overview section, there is markdown code showing in plain text. See attached > screenshot. Don't know what's causing it, but surely it should render as a > clickable hyperlink -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MNGSITE-386) markdown not always resolved
[ https://issues.apache.org/jira/browse/MNGSITE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNGSITE-386. - Assignee: Herve Boutemy Resolution: Fixed workaround done in https://github.com/apache/maven-site/commit/60042f18c4ba42e5c413d1df667e1173ed4fa38e > markdown not always resolved > > > Key: MNGSITE-386 > URL: https://issues.apache.org/jira/browse/MNGSITE-386 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Assignee: Herve Boutemy >Priority: Minor > > On several pages including https://maven.apache.org/what-is-maven.html I > notice that markdown is slipping through into the site instead of being > rendered into HTML. I don't know why. > E.g. it says > Maven, a [Yiddish word](https://en.wikipedia.org/wiki/Maven) meaning > *accumulator of knowledge*, > instead of > Maven, a Yiddish word > meaning accumulator of knowledge > This usually seems to happen only in the first paragraph. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNGSITE-386) markdown not always resolved
[ https://issues.apache.org/jira/browse/MNGSITE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109654#comment-17109654 ] Hudson commented on MNGSITE-386: Build succeeded in Jenkins: Maven TLP » maven-site » master #284 See https://builds.apache.org/job/maven-box/job/maven-site/job/master/284/ > markdown not always resolved > > > Key: MNGSITE-386 > URL: https://issues.apache.org/jira/browse/MNGSITE-386 > Project: Maven Project Web Site > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Minor > > On several pages including https://maven.apache.org/what-is-maven.html I > notice that markdown is slipping through into the site instead of being > rendered into HTML. I don't know why. > E.g. it says > Maven, a [Yiddish word](https://en.wikipedia.org/wiki/Maven) meaning > *accumulator of knowledge*, > instead of > Maven, a Yiddish word > meaning accumulator of knowledge > This usually seems to happen only in the first paragraph. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (WAGON-596) Add configuration property 'http.protocol.handle-uri-normalization'
[
https://issues.apache.org/jira/browse/WAGON-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated WAGON-596:
-
Description: Add support for disabling/enabling URI normalization. The
default value is {{true}}. (was: Add support for disabling/enabling content
compression (decompression on the fly). The default value is {{true}}.)
> Add configuration property 'http.protocol.handle-uri-normalization'
> ---
>
> Key: WAGON-596
> URL: https://issues.apache.org/jira/browse/WAGON-596
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http
>Affects Versions: 3.4.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.4.1
>
>
> Add support for disabling/enabling URI normalization. The default value is
> {{true}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (WAGON-596) CLONE - Add configuration property 'http.protocol.handle-uri-nomalization'
Michael Osipov created WAGON-596:
Summary: CLONE - Add configuration property
'http.protocol.handle-uri-nomalization'
Key: WAGON-596
URL: https://issues.apache.org/jira/browse/WAGON-596
Project: Maven Wagon
Issue Type: Improvement
Components: wagon-http
Affects Versions: 3.4.0
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.4.1
Add support for disabling/enabling content compression (decompression on the
fly). The default value is {{true}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSHARED-681) Maven-Shared: Java7Support silently fails overwriting symlinks
[ https://issues.apache.org/jira/browse/MSHARED-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109652#comment-17109652 ] Robert James Oxspring commented on MSHARED-681: --- Updated PR opened, inspired by [~mkarg]'s changes but avoiding recreation of identical symlinks and adding a test: https://github.com/apache/maven-shared-utils/pull/31 > Maven-Shared: Java7Support silently fails overwriting symlinks > -- > > Key: MSHARED-681 > URL: https://issues.apache.org/jira/browse/MSHARED-681 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-shared-utils >Reporter: Markus Karg >Priority: Critical > > When A is an existing symlink to B, then createSymbolicLink(A,C) does > neither overwrite A->B by A->C (as expected in analogy to the behavior > of copy(A,C)) nor does it throw an exception nor does it return A->B to > indicate the failure, but it actually "silently fails", i. e. it returns > A->C! > This certainly is heavily problematic, unsymmetric to what > copy(File,File) and Files.createSymbolicLink(Path,Path) do, and > certainly unwanted and buggy behavior. > The solution is to delete any existing target before creating the > symlic, hence copying the behavior of copy(File,File). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (WAGON-596) Add configuration property 'http.protocol.handle-uri-normalization'
[
https://issues.apache.org/jira/browse/WAGON-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated WAGON-596:
-
Summary: Add configuration property
'http.protocol.handle-uri-normalization' (was: CLONE - Add configuration
property 'http.protocol.handle-uri-nomalization')
> Add configuration property 'http.protocol.handle-uri-normalization'
> ---
>
> Key: WAGON-596
> URL: https://issues.apache.org/jira/browse/WAGON-596
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http
>Affects Versions: 3.4.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.4.1
>
>
> Add support for disabling/enabling content compression (decompression on the
> fly). The default value is {{true}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNGSITE-411) on website, Maven Issue Management page, markdown is showing in plaintext
[ https://issues.apache.org/jira/browse/MNGSITE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109651#comment-17109651 ] Hudson commented on MNGSITE-411: Build succeeded in Jenkins: Maven TLP » maven-site » master #283 See https://builds.apache.org/job/maven-box/job/maven-site/job/master/283/ > on website, Maven Issue Management page, markdown is showing in plaintext > - > > Key: MNGSITE-411 > URL: https://issues.apache.org/jira/browse/MNGSITE-411 > Project: Maven Project Web Site > Issue Type: Bug > Environment: website >Reporter: Tim Stewart >Priority: Minor > Labels: typo, website > Attachments: markdownbroken.png > > > on page [https://maven.apache.org/issue-management.html], in the first > Overview section, there is markdown code showing in plain text. See attached > screenshot. Don't know what's causing it, but surely it should render as a > clickable hyperlink -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (WAGON-595) Add configuration property 'http.protocol.handle-content-compression'
[
https://issues.apache.org/jira/browse/WAGON-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed WAGON-595.
Resolution: Fixed
Fixed with
[8882fa12426e9db9f2e94cafa363985941a4a227|https://gitbox.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=8882fa12426e9db9f2e94cafa363985941a4a227].
> Add configuration property 'http.protocol.handle-content-compression'
> -
>
> Key: WAGON-595
> URL: https://issues.apache.org/jira/browse/WAGON-595
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http
>Affects Versions: 3.4.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.4.1
>
>
> Add support for disabling/enabling content compression (decompression on the
> fly). The default value is {{true}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-shared-utils] roxspring opened a new pull request #31: [MSHARED-681] createSymbolicLink() overwrites existing different symlinks
roxspring opened a new pull request #31: URL: https://github.com/apache/maven-shared-utils/pull/31 Inspired by @mkarg's https://github.com/apache/maven-shared/pull/12/files but: - Reimplemented in `FileUtils.createSymbolicLink()` since the utility method was moved from `Java7Support`. - Read the existing symlink and only delete if it's incorrectly targeted - Added a test confirming that symlinks are correctly overwritten 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SUREFIRE-1570) Maven-fail-safe doesn't put testing JPMS module on module path
[
https://issues.apache.org/jira/browse/SUREFIRE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109645#comment-17109645
]
Pavel_K commented on SUREFIRE-1570:
---
[~tibordigana] I've seen that you resolved this issue and wanted to test it. I
compiled plugins from master and did
{code:java}
git clone https://github.com/PashaTurok/plugin-jpms
cd plugin-jpms
mvn clean install
{code}
However, no one of my test run - neither unit, nor integration. Do I do
something wrong?
> Maven-fail-safe doesn't put testing JPMS module on module path
> --
>
> Key: SUREFIRE-1570
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1570
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin
>Affects Versions: 2.22.0
>Reporter: Pavel_K
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M5
>
> Attachments: mavenproject20.zip
>
>
> I uploaded project - mavenproject20. Run `mvn verify`. You will see the
> following:
> {code:java}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building mavenproject20 0.1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
> mavenproject20 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.0:compile (default-compile) @
> mavenproject20 ---
> [WARNING]
>
> [WARNING] * Required filename-based automodules detected. Please don't
> publish this project to a public artifact repository! *
> [WARNING]
>
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 3 source files to
> /home/Jim/NetBeansProjects/mavenproject20/target/classes
> [WARNING]
> /home/Jim/NetBeansProjects/mavenproject20/src/main/java/module-info.java:[1,8]
> module name component Mavenproject20 should avoid terminal digits
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
> mavenproject20 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory
> /home/Jim/NetBeansProjects/mavenproject20/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.0:testCompile (default-testCompile) @
> mavenproject20 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /home/Jim/NetBeansProjects/mavenproject20/target/test-classes
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ mavenproject20
> ---
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ mavenproject20 ---
> [INFO] Building jar:
> /home/Jim/NetBeansProjects/mavenproject20/target/mavenproject20-0.1.0-SNAPSHOT.jar
> [INFO]
> [INFO] --- maven-failsafe-plugin:2.22.0:integration-test (integration-tests)
> @ mavenproject20 ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running me.pavel.mavenproject20.ServiceIT
> JDKModulePath:null
> ModuleName:null
> module jdk.unsupported
> module jdk.sctp
> module java.naming
> module java.jnlp
> module jdk.httpserver
> module java.xml
> module javafx.controls
> module java.datatransfer
> module jdk.javadoc
> module jdk.jconsole
> module java.instrument
> module jdk.packager
> module jdk.deploy
> module jdk.jfr
> module jdk.management
> module jdk.charsets
> module oracle.net
> module jdk.jdeps
> module java.sql.rowset
> module jdk.net
> module jdk.accessibility
> module jdk.attach
> module jdk.internal.le
> module jdk.snmp
> module java.base
> module jdk.plugin
> module jdk.dynalink
> module jdk.naming.rmi
> module jdk.internal.opt
> module java.management.rmi
> module jdk.management.jfr
> module javafx.swing
> module jdk.editpad
> module jdk.crypto.ec
> module jdk.javaws
> module jdk.jstatd
> module jdk.management.agent
> module javafx.graphics
> module javafx.media
> module java.rmi
> module java.prefs
> module jdk.security.jgss
> module javafx.fxml
> module java.smartcardio
> module jdk.xml.dom
> module java.xml.crypto
> module jdk.jsobject
> module jdk.jdi
> module jdk.compiler
> module java.management
> module jdk.management.cmm
> module jdk.packager.services
> module jdk.jartool
> module jdk.scripting.nashorn
> module
[GitHub] [maven-filtering] roxspring commented on pull request #5: [MSHARED-884] Only overwrite filtered resources when contents differ
roxspring commented on pull request #5: URL: https://github.com/apache/maven-filtering/pull/5#issuecomment-629859905 See https://github.com/apache/maven-shared-utils/pull/28 for better targeted approach using no temporary files. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-filtering] roxspring closed pull request #5: [MSHARED-884] Only overwrite filtered resources when contents differ
roxspring closed pull request #5: URL: https://github.com/apache/maven-filtering/pull/5 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (WAGON-595) Add configuration property 'http.protocol.handle-content-compression'
[
https://issues.apache.org/jira/browse/WAGON-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated WAGON-595:
-
Description: Add support for disabling/enabling content compression
(decompression on the fly). The default value is {{true}}. (was: Add support
for disabling/enabling content compression (decompression on the fly).)
> Add configuration property 'http.protocol.handle-content-compression'
> -
>
> Key: WAGON-595
> URL: https://issues.apache.org/jira/browse/WAGON-595
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http
>Affects Versions: 3.4.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.4.1
>
>
> Add support for disabling/enabling content compression (decompression on the
> fly). The default value is {{true}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (WAGON-595) Add configuration property 'http.protocol.handle-content-compression'
[ https://issues.apache.org/jira/browse/WAGON-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-595: - Summary: Add configuration property 'http.protocol.handle-content-compression' (was: Add configuration property 'http.protocol.content-compression') > Add configuration property 'http.protocol.handle-content-compression' > - > > Key: WAGON-595 > URL: https://issues.apache.org/jira/browse/WAGON-595 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http >Affects Versions: 3.4.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.4.1 > > > Add support for disabling/enabling content compression (decompression on the > fly). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (WAGON-595) Add configuration property 'http.protocol.content-compression'
Michael Osipov created WAGON-595: Summary: Add configuration property 'http.protocol.content-compression' Key: WAGON-595 URL: https://issues.apache.org/jira/browse/WAGON-595 Project: Maven Wagon Issue Type: Improvement Components: wagon-http Affects Versions: 3.4.0 Reporter: Michael Osipov Assignee: Michael Osipov Add support for disabling/enabling content compression (decompression on the fly). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (WAGON-595) Add configuration property 'http.protocol.content-compression'
[ https://issues.apache.org/jira/browse/WAGON-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-595: - Fix Version/s: 3.4.1 > Add configuration property 'http.protocol.content-compression' > -- > > Key: WAGON-595 > URL: https://issues.apache.org/jira/browse/WAGON-595 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http >Affects Versions: 3.4.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.4.1 > > > Add support for disabling/enabling content compression (decompression on the > fly). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (WAGON-566) Add support for URI normalization
[
https://issues.apache.org/jira/browse/WAGON-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109632#comment-17109632
]
Michael Osipov commented on WAGON-566:
--
[~stvricbr...@gmail.com], do you still want to provide a PR?
> Add support for URI normalization
> -
>
> Key: WAGON-566
> URL: https://issues.apache.org/jira/browse/WAGON-566
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-http
>Affects Versions: 3.3.3
>Reporter: Steve Brown
>Priority: Major
> Labels: easyfix, newbie
> Fix For: waiting-for-feedback
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> This is a simple fix for MSITE-738. I have set the priority as Major because
> that is the priority set for MSITE-738
> Some Repository Managers, e.g. JFrog's Artifactory, do not allow puts to a
> URL with relative path elements ("." or "..").
> Artifactory are addressing the issue for downloads from remote sites
> ([RTFACT-16457|https://www.jfrog.com/jira/browse/RTFACT-16457]). Artifactory
> returns this error:
> {{"status" : 500,"}}
> {{"Path element cannot end with a dot: sites/ ... redacted ... */../*"}}
> The fix is to amend
> {{org.apache.maven.wagon.shared.http.EncodeUtils.encodeURL( String url )}}
> to normalize the returned URI.
> I will create a pull request.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (WAGON-594) http.route.default-proxy config property never passes protocol and port of proxy server
[
https://issues.apache.org/jira/browse/WAGON-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed WAGON-594.
Resolution: Fixed
Fixed with
[e227cdf59674c5a2ae82cfd313690fd2c17d3973|https://gitbox.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=e227cdf59674c5a2ae82cfd313690fd2c17d3973].
> http.route.default-proxy config property never passes protocol and port of
> proxy server
> ---
>
> Key: WAGON-594
> URL: https://issues.apache.org/jira/browse/WAGON-594
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 3.4.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.4.1
>
>
> Instead of using {{org.apache.http.HttpHost.create(String)}} the code uses
> {{org.apache.http.HttpHost.HttpHost(String)}} which accepts the host only.
> One can never set any other port than default one (80).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (WAGON-594) http.route.default-proxy config property never passes protocol and port of proxy server
[
https://issues.apache.org/jira/browse/WAGON-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated WAGON-594:
-
Summary: http.route.default-proxy config property never passes protocol and
port of proxy server (was: http.route.default-proxy config property never
passed protocol and port of proxy server)
> http.route.default-proxy config property never passes protocol and port of
> proxy server
> ---
>
> Key: WAGON-594
> URL: https://issues.apache.org/jira/browse/WAGON-594
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 3.4.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.4.1
>
>
> Instead of using {{org.apache.http.HttpHost.create(String)}} the code uses
> {{org.apache.http.HttpHost.HttpHost(String)}} which accepts the host only.
> One can never set any other port than default one (80).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (WAGON-594) http.route.default-proxy config property never passed protocol and port of proxy server
Michael Osipov created WAGON-594:
Summary: http.route.default-proxy config property never passed
protocol and port of proxy server
Key: WAGON-594
URL: https://issues.apache.org/jira/browse/WAGON-594
Project: Maven Wagon
Issue Type: Bug
Components: wagon-http
Affects Versions: 3.4.0
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.4.1
Instead of using {{org.apache.http.HttpHost.create(String)}} the code uses
{{org.apache.http.HttpHost.HttpHost(String)}} which accepts the host only. One
can never set any other port than default one (80).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (WAGON-593) Remove non-existent cache header
[
https://issues.apache.org/jira/browse/WAGON-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed WAGON-593.
Resolution: Fixed
Fixed with
[bb12d4ed2467f8deb543fa99d8d9a180e4ab1ea6|https://gitbox.apache.org/repos/asf?p=maven-wagon.git;a=commit;h=bb12d4ed2467f8deb543fa99d8d9a180e4ab1ea6].
> Remove non-existent cache header
>
>
> Key: WAGON-593
> URL: https://issues.apache.org/jira/browse/WAGON-593
> Project: Maven Wagon
> Issue Type: Task
> Components: wagon-http
>Affects Versions: 3.4.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.4.1
>
>
> The header {{Cache-store}} does not exist. Remove it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (WAGON-593) Remove non-existent cache header
Michael Osipov created WAGON-593:
Summary: Remove non-existent cache header
Key: WAGON-593
URL: https://issues.apache.org/jira/browse/WAGON-593
Project: Maven Wagon
Issue Type: Task
Components: wagon-http
Affects Versions: 3.4.0
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 3.4.1
The header {{Cache-store}} does not exist. Remove it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MNG-6907) endless loop in StringSearchModelInterpolator
Michael Keppler created MNG-6907: Summary: endless loop in StringSearchModelInterpolator Key: MNG-6907 URL: https://issues.apache.org/jira/browse/MNG-6907 Project: Maven Issue Type: Bug Components: Inheritance and Interpolation Affects Versions: 3.6.3 Reporter: Michael Keppler I have some company confidential projects (therefore no reproduction pom), which cause an endless loop when running mvn versions:display-plugin-updates The endless loop happens in [StringSearchModelInterpolator.traverseObjectWithParents|https://github.com/apache/maven/blob/5397fb66e7ea45dd756cd48c18f7dc476e2a06a6/maven-model-builder/src/main/java/org/apache/maven/model/interpolation/StringSearchModelInterpolator.java#L176] calling itself (which I can see by attaching a profiler to the process). Please add a check for whether the superClass is identical to the class, before entering the recursion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6598) Maven 3.6.0 and Surefire problem
[
https://issues.apache.org/jira/browse/MNG-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109581#comment-17109581
]
Michael Osipov commented on MNG-6598:
-
[~clausfod], can you confirm?
> Maven 3.6.0 and Surefire problem
>
>
> Key: MNG-6598
> URL: https://issues.apache.org/jira/browse/MNG-6598
> Project: Maven
> Issue Type: Task
> Components: General
>Affects Versions: 3.6.0
> Environment: windows 7, 64bit Oracle jdk 1.8 (see stacktrace)
>Reporter: Lars Borup Jensen
>Priority: Critical
> Fix For: 3.7.0-candidate
>
>
> We've been using 3.5.2 for a longer period of time and just recently upgraded
> to 3.6.0 and then the problems started.
> First we experienced way longer build times when running the absolutely same
> build in 3.6.0 than 3.5.2. Using -B when running locally does seem to improve
> build time but still not quite the same.
> The main issue and one that is really causing us headaches is that Surefire
> 2.22.0 suddently started failing to create forks when running tests - setting
> forkCount does help on this, but then we come back to the above mentioned
> problem: build time, which then becomes painfully slow.
> So our discovery is: same source, same POM (same versions of plugins etc)
> fails to build on 3.6.0 but works on 3.5.2 (and even faster) - do you have
> any pointers for us, what to look for?
> Stacktrace from Maven
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.22.0:test (default-test) on
> project myproj: There are test failures.
> [ERROR]
> [ERROR] Please refer to C:\projects\myproj\proj\target\surefire-reports for
> the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
> -jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582\surefirebooter6297886391209366508.jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582
> 2019-02-22T09-01-49_197-jvmRun1 surefire7364437855153295156tmp
> surefire_13521419335267356208tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] dk.company.proj.persistence.RepositoryTest
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or System.exit
> called?
> [ERROR] Command was cmd.exe /X /C "C:\tools\oracle\jdk\1.8.0_192\jre\bin\java
> -javaagent:C:\\tools\\apache\\maven\\m2repository\\org\\jacoco\\org.jacoco.agent\\0.8.2\\org.jacoco.agent-0.8.2-runtime.jar=destfile=C:\\projects\\myproj\\proj\\target\\jacoco.exec,append=true,excludes=*_javassist_*:**/com/**/*:**/dk/company/schemas/**/*:**/dk/oio/**/*:**/net/companynet/**/*:**/dk/othercompany/**/*:**/dk/othercompany/integration/**/*:**/dk/company/stub/**/*
> -jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582\surefirebooter6297886391209366508.jar
> C:\Users\someuser\AppData\Local\Temp\surefire1255787583870225582
> 2019-02-22T09-01-49_197-jvmRun1 surefire7364437855153295156tmp
> surefire_13521419335267356208tmp"
> [ERROR] Process Exit Code: 0
> [ERROR] Crashed tests:
> [ERROR] dk.company.proj.persistence.RepositoryTest
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:671)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:533)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:278)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:244)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MNGSITE-412) Add NanoMaven to the list of available repository managers
[ https://issues.apache.org/jira/browse/MNGSITE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNGSITE-412: - Priority: Minor (was: Major) > Add NanoMaven to the list of available repository managers > -- > > Key: MNGSITE-412 > URL: https://issues.apache.org/jira/browse/MNGSITE-412 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: dzikoysk >Priority: Minor > > NanoMaven repository: https://github.com/dzikoysk/nanomaven > Motivation: Project is active for 3 years now and it is a good solution for > developers hosting their projects at low cost. > At this moment, people are forced to use huge ecosystems like Nexus or > Artifactory. I think it might be a good idea to show an alternative. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNGSITE-412) Add NanoMaven to the list of available repository managers
[ https://issues.apache.org/jira/browse/MNGSITE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dzikoysk updated MNGSITE-412: - Description: NanoMaven repository: https://github.com/dzikoysk/nanomaven Motivation: Project is active for 3 years now and it is a good solution for developers hosting their projects at low cost. At this moment, people are forced to use huge ecosystems like Nexus or Artifactory. I think it might be a good idea to show an alternative. was: NanoMaven repository: https://github.com/dzikoysk/nanomaven Motivation: Project is active for 3 years now and it is a good solution for developers hosting their projects at low cost. > Add NanoMaven to the list of available repository managers > -- > > Key: MNGSITE-412 > URL: https://issues.apache.org/jira/browse/MNGSITE-412 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: dzikoysk >Priority: Major > > NanoMaven repository: https://github.com/dzikoysk/nanomaven > Motivation: Project is active for 3 years now and it is a good solution for > developers hosting their projects at low cost. > At this moment, people are forced to use huge ecosystems like Nexus or > Artifactory. I think it might be a good idea to show an alternative. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MNGSITE-412) Add NanoMaven to the list of available repository managers
[ https://issues.apache.org/jira/browse/MNGSITE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dzikoysk updated MNGSITE-412: - Description: NanoMaven repository: https://github.com/dzikoysk/nanomaven Motivation: Project is active for 3 years now and it is a good solution for developers hosting their projects at low cost. was:NanoMaven repository: https://github.com/dzikoysk/nanomaven > Add NanoMaven to the list of available repository managers > -- > > Key: MNGSITE-412 > URL: https://issues.apache.org/jira/browse/MNGSITE-412 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: dzikoysk >Priority: Major > > NanoMaven repository: https://github.com/dzikoysk/nanomaven > Motivation: Project is active for 3 years now and it is a good solution for > developers hosting their projects at low cost. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MNGSITE-412) Add NanoMaven to the list of available repository managers
dzikoysk created MNGSITE-412: Summary: Add NanoMaven to the list of available repository managers Key: MNGSITE-412 URL: https://issues.apache.org/jira/browse/MNGSITE-412 Project: Maven Project Web Site Issue Type: Improvement Reporter: dzikoysk NanoMaven repository: https://github.com/dzikoysk/nanomaven -- This message was sent by Atlassian Jira (v8.3.4#803005)
