dependabot[bot] opened a new pull request #250:
URL: https://github.com/apache/maven-site/pull/250
Bumps [maven-enforcer-plugin](https://github.com/apache/maven-enforcer) from
3.0.0-M3 to 3.0.0.
Commits
https://github.com/apache/maven-enforcer/commit/b1b22822174bc92857a2e674c9
Hello!
I may not understand much of this discussion going on here. But we use the -B
option for having the default behaviour of maven-release in literally thousands
of our Jenkins build jobs. Even only having to wait on a debug timeout would
not be acceptable and would force us to remove this i
I guess you mean suspend and not server.
Your idea may work, but still is problematic. If the breakpoint is quite
early you will miss in your IDE and then you need to start over.
I think -B and --debug are special cases and I believe that a timeout is
acceptible since the build is halted, but mo
I wonder if this is a realistic issue. In the cases I know with the batch-mode
the interactive part is skipped and code falls back to defaults.
If there are issues, they're more much likely to happen in the interactive
mode.
Maybe a more reasonable solution is to use server="n" (default) for bat
@Hervé:
The NPM `deprecated` property exists in NPM registry package metadata. (Some of
this is derived from package.json, but it is not the same as package.json.)
It is described here:
https://github.com/npm/registry/blob/master/docs/responses/package-metadata.md
The library which NPM itself
Am 2021-07-30 um 14:31 schrieb Stephen Connolly:
So now I cannot debug Maven issues that happen when running in batch mode?
We should document that specific case uses MAVEN_OPTS
Not now, nothing has been committed/merged yet. This is just a PoC.
Robert and me thought about this. We could add a
@Hervé:
The NuGet `deprecation` object exists in the NuGet package metadata.
It is described here:
https://docs.microsoft.com/en-us/nuget/api/registration-base-url-resource#package-deprecation
Example snippet from the docs:
{
"@id":
"https://api.nuget.org/v3/registration3/nuget.protocol
elharo closed pull request #69:
URL: https://github.com/apache/maven-doxia/pull/69
--
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: dev-unsubscr...
elharo merged pull request #40:
URL: https://github.com/apache/maven-artifact-transfer/pull/40
--
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: dev
elharo closed pull request #57:
URL: https://github.com/apache/maven-site-plugin/pull/57
--
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: dev-unsub
dependabot[bot] commented on pull request #57:
URL: https://github.com/apache/maven-site-plugin/pull/57#issuecomment-889862919
OK, I won't notify you again about this release, but will get in touch when
a new version is available. You can also ignore all major, minor, or patch
releases for
elharo merged pull request #58:
URL: https://github.com/apache/maven-site-plugin/pull/58
--
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: dev-unsub
So now I cannot debug Maven issues that happen when running in batch mode?
We should document that specific case uses MAVEN_OPTS
On Tue 27 Jul 2021 at 16:01, Michael Osipov wrote:
> So you say that -B will implicitly disable --debug without any further
> notice?
>
> I logically agree that batch
elharo closed pull request #59:
URL: https://github.com/apache/maven-site-plugin/pull/59
--
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: dev-unsub
dependabot[bot] commented on pull request #59:
URL: https://github.com/apache/maven-site-plugin/pull/59#issuecomment-889860653
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
major or mi
elharo closed pull request #41:
URL: https://github.com/apache/maven-artifact-transfer/pull/41
--
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: dev
dependabot[bot] commented on pull request #41:
URL:
https://github.com/apache/maven-artifact-transfer/pull/41#issuecomment-889860340
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
majo
dependabot[bot] opened a new pull request #41:
URL: https://github.com/apache/maven-artifact-transfer/pull/41
Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from
3.3.0 to 3.4.0.
Release notes
Sourced from https://github.com/codehaus-plexus/plexus-utils/relea
dependabot[bot] opened a new pull request #69:
URL: https://github.com/apache/maven-doxia/pull/69
Bumps [plexus-utils](https://github.com/codehaus-plexus/plexus-utils) from
3.3.0 to 3.4.0.
Release notes
Sourced from https://github.com/codehaus-plexus/plexus-utils/releases";>plexus
The Apache Maven team is pleased to announce the release of the Apache Maven
Enforcer Plugin and Extension, version 3.0.0
The Enforcer plugin is the Loving Iron Fist of Maven and provides goals to
control certain environmental constraints such as Maven version, JDK version
and OS family along w
Hi Chris,
working for some clients in the last years, I saw nearly all of them
struggling with their dependency management. Sad, but true.
I see various use cases for the feature you propose, not only in the
public space. This feature could be also very interessting for
companies, if they wo
@Sławomir:
I know the POM and the contents of the artifact itself don't change after
publication (at least on Central). This is one reason I suggested putting
deprecation indicators in something like maven-metadata.xml instead. Are you
saying that maven-metadata.xml is immutable as well?
I thi
Hi,
@Oliver:
Glad of the help :) My definition of 'deprecated' would be roughly 'this
artifact is not actively developed and should not be used any more'.
One example I have in mind for deprecation is Joda Time - a library which was
superseded years ago by java.time in Java 8 and Android API 2
Hi,
The vote has passed with the following result:
+1 : Hervé BOUTEMY, Michael Osipov, Robert Scholte, Arnaud Héritier
PMC quorum: reached
I will promote the artifacts to the central repo.
On 26-7-2021 23:17:57, Robert Scholte wrote:
Hi,
We solved 37 issues:
https://issues.apache.org/jira/se
24 matches
Mail list logo
