Re: Publish Artifact with test

2019-12-16 Thread Anders Hammar
You never specify the scope of an artifact when you publish it. When
someone declares a dependency to your artifact, they can specify the scope
for that dependency (e.g. "test").

/Anders

On Mon, Dec 16, 2019 at 7:01 PM Mohamed Ennahdi El Idrissi <
mohamed.enna...@gmail.com> wrote:

> Dear all,
>
> What should I mention in pom.xml to make my dependency published with
> test?
>
> https://stackoverflow.com/questions/59360773/publish-artifact-with-scopetest-scope
>
> --
> Merci,
> Mohamed ENNAHDI EL IDRISSI
>
> Oracle Certified Professional, Java SE 6 Programmer
> <
> https://www.youracclaim.com/badges/dd563cd0-d35f-458c-bc0a-dac60362416e/public_url
> >
>


Publish Artifact with test

2019-12-16 Thread Mohamed Ennahdi El Idrissi
Dear all,

What should I mention in pom.xml to make my dependency published with
test?
https://stackoverflow.com/questions/59360773/publish-artifact-with-scopetest-scope

-- 
Merci,
Mohamed ENNAHDI EL IDRISSI

Oracle Certified Professional, Java SE 6 Programmer



[ANN] Apache Maven Release Plugin 3.0.0-M1 Released

2019-12-16 Thread Hervé Boutemy
The Apache Maven team is pleased to announce the release of the Apache Maven 
Release Plugin, version 3.0.0-M1.
 
This plugin is used to release a project with Maven, saving a lot of 
repetitive, manual work. Releasing a project is made in two steps: prepare and 
perform.
 
https://maven.apache.org/plugins/maven-release-plugin/
 
You should specify the version in your project's plugin configuration:
 

  org.apache.maven.plugins
  maven-release-plugin
  3.0.0-M1

 
You can download the appropriate sources etc. from the download page:

https://maven.apache.org/plugins/maven-release-plugin/download.cgi
 

Release Notes - Maven Release Plugin - Version 3.0.0-M1

** Bug
* [MRELEASE-229] - release:rollback is missing remove tag implementation
* [MRELEASE-601] - The Maven 2 release plugin modifies CDATA elements in 
pom.xml files.
* [MRELEASE-694] - -SNAPSHOT is unexpectedly appended to version in 
branched pom.xml
* [MRELEASE-908] - Git HTTP authentication failing if there are spaces in 
the password
* [MRELEASE-928] - exposing the password for SCM URL if build failed to 
commit files to SCM
* [MRELEASE-947] - Wiki page URL for maven-release-plugin is wrong - post 
Codehaus termination
* [MRELEASE-964] - Error injecting: 
org.apache.maven.shared.release.phase.RewritePomsForReleasePhase
* [MRELEASE-966] - release plugin does not respect "mvn -f"
* [MRELEASE-968] - Maven release plugin missing plexus-cipher dependency
* [MRELEASE-975] - NPE when using an unknown project versionpolicy id
* [MRELEASE-997] - Unable to release:perform on windows if a file name 
contains spaces on windows
* [MRELEASE-1009] - Compilation failure when using Java 10
* [MRELEASE-1034] - Remove SCM tag blocks rollback in some situations

** New Feature
* [MRELEASE-956] - Release Strategy Interface
* [MRELEASE-980] - Provide the ability to control commit messages
* [MRELEASE-985] - Override SNAPSHOT dependencies from command line
* [MRELEASE-998] - Add ability to create custom phases
* [MRELEASE-1029] - update project.build.outputTimestamp property on prepare
* [MRELEASE-1031] - display release phases to give insight on what's going 
on during release

** Improvement
* [MRELEASE-703] - [PATCH] Migration from obsolete plexus-maven-plugin to 
plexus-containers-component-metadata
* [MRELEASE-873] - Remove possibly confusing non-standard goals from example
* [MRELEASE-896] - Disable by default and deprecate useReleaseProfile 
parameter
* [MRELEASE-909] - Add workItem/task support for scm deliver
* [MRELEASE-958] - Using three digit version number (semver)
* [MRELEASE-976] - release:branch should also support project version 
policies
* [MRELEASE-977] - release:branch should prompt for branch name if none is 
given
* [MRELEASE-979] - Support NamingPolicies to manage Branch and Tag names
* [MRELEASE-992] - Deprecated maven flag --no-plugin-updates shows warnings 
in the console output
* [MRELEASE-993] - Use shallow checkout per default (git scm)
* [MRELEASE-994] - Drop Maven2 support
* [MRELEASE-1005] - Extract ResourceGenerator from ReleasePhase
* [MRELEASE-1007] - Rework usage workingDirectory and commonBasedir
* [MRELEASE-1023] - Minor code cleanups
* [MRELEASE-1032] - add https://m.a.o/xsd/maven-4.0.0.xsd schema instead of 
http://m.a.o/maven-v4_0_0.xsd

** Task
* [MRELEASE-356] - Deprecate the automated release profile
* [MRELEASE-990] - switch to Git
* [MRELEASE-1027] - New Release
* [MRELEASE-1033] - Site: Dead link to wiki

** Dependency upgrade
* [MRELEASE-952] - Replace JDom as XML transformer
* [MRELEASE-1010] - Upgrade maven-plugins parent to version 32
* [MRELEASE-1024] - Upgrade to SCM 1.11.2
 
Enjoy,
 
-The Apache Maven team



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org