Re: How can I automate the testing of my archetype? Maven Build from TestNG?
i'd use the invoker plugin 2009/12/18 JavaGeek nos...@boscarine.com Hello All, Does anyone have advice on automating the testing of an archetype? I am a community volunteer helping out the JBoss folks with their Weld Java EE 6 archetypes. I currently have a bash script I use to test it, but it requires *NIX and presently requires manually running a selenium test. I'd like to automate it so Hudson can catch my mistakes. Surely I am not the first guy who built an archetype and wanted to test it from Continuous Integration, has someone already solved this problem? I would guess the ideal would be to have a TestNG/JUnit test that does the following: 1. Create new project from archetype in memory or a temp directory somewhere. It won't be needed once the test has finished running. 2. Run maven commands on the new project (mvn test jetty:run) to confirm the unit tests pass. 3. Trigger an HttpUnit test to confirm the JSF code renders correctly. If there's no pre-canned solution to this problem, how difficult would it be to have one project run maven from TestNG to trigger the archetype:generate and then a maven build from JUnit or TestNG? Thanks in advance, Steven -- View this message in context: http://old.nabble.com/How-can-I-automate-the-testing-of-my-archetype---Maven-Build-from-TestNG--tp26850764p26850764.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release plugin: version change not only in POMs ?
I've inserted the following configuration to my pom.xml (taken from here
http://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html
):
plugin
artifactIdmaven-resources-plugin/artifactId
version2.4.1/version
executions
execution
idcopy-resources/id
!-- here the phase you need --
phasevalidate/phase
goals
goalcopy-resources/goal
/goals
configuration
outputDirectory${basedir}/outputDirectory
resources
resource
directorysrc/non-packaged-resources/directory
filteringtrue/filtering
/resource
/resources
/configuration
/execution
/executions
/plugin
The directory src/non-packaged-resources exists and my file is in there.
When I run mvn resources:copy-resources I get the following:
[ERROR] BUILD ERROR
[INFO]
[INFO] One or more required plugin parameters are invalid/missing for
'resources:copy-resources'
[0] Inside the definition for plugin 'maven-resources-plugin' specify the
following:
configuration
...
outputDirectoryVALUE/outputDirectory
/configuration.
[1] Inside the definition for plugin 'maven-resources-plugin' specify the
following:
configuration
...
resourcesVALUE/resources
/configuration.
But I specified both directories as in the configuration snippet above. What
am I doing wrong?
2009/12/19 Roland Asmann roland.asm...@adesso.at
Hi,
Sorry, didn't read the mail good enough and made some errors in my
previous reply!
- Put your files in src/main/config with the variables configured
- Have the resource-plugin copyfilter them to the root of the project
(make sure this is done before the pax-plugin runs)
If you use the clean-plugin, it would be a good idea to put the 2 files in
the root of the project in the list of files to delete as well!
Roland
Sorry for the mess but actually this is not directly the MANIFEST file.
It
is a file used by other plugin to create the MANIFEST file. I am talking
about the pax plugin and osgi.bnd file which must reside in the root of
the
maven project along with the pom.xml. This file is a not resource, it is
not
going to the jar at all. It is like a config file for the pax plugin. And
it
is a text file.
I read the info in the link about the resources plugin - it is exactly
what
I need but without packing this file to the resulting jar and it must not
go
to the target directory during the build process.
19 декабря 2009 г. 0:45 пользователь Dennis Lundberg
denn...@apache.orgнаписал:
You should try to go about this in another way. Instead of having the
version explicitly in text files, you should filter these files using
the Resources Plugin. See
http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
As for the example of the manifest file, you should let the JAR Plugin
handle the version in there instead of managing it yourself. See
http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html
and
http://maven.apache.org/shared/maven-archiver/index.html
Grigory Ptashko wrote:
Hello.
Recently I've got acquainted with the release plugin. I started using
it,
it
works great but I am missing one feature. The problem is the
following:
the
version that is specified in a POM is used not only in this POM but
also
in
another place in a plain-text format. Actually it is used in the
MANIFEST.MF
in the special header. So when I perform a release the release version
have
the new version, the trunk version gets the new y-SNAPSHOT version but
that
MANIFEST.MF file has old version x-SNAPSHOT which becomes wrong both
in
trunk and in the release.
What I want is two steps to be executed while release:perform (phrases
in
quotes are taken from here
http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html
):
- The first is after the step Change the version in the poms from
x-SNAPSHOT to a new version (you will be prompted for the versions
to
use):
the same transformation must be done with the text file that I
specify.
- The second is after the step Bump the version in the POMs to a
new
value y-SNAPSHOT (these values will also be prompted for): the
same
transformation must be done with text file that I specify.
How can I achieve this?
Thank you.
--
Dennis Lundberg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
С уважением,
Григорий Пташко
+7
Re: How can I automate the testing of my archetype? Maven Build from TestNG?
Hi do you have an example ? Regards Mark Donszelmann On Dec 19, 2009, at 9:36 AM, Stephen Connolly wrote: i'd use the invoker plugin 2009/12/18 JavaGeek nos...@boscarine.com Hello All, Does anyone have advice on automating the testing of an archetype? I am a community volunteer helping out the JBoss folks with their Weld Java EE 6 archetypes. I currently have a bash script I use to test it, but it requires *NIX and presently requires manually running a selenium test. I'd like to automate it so Hudson can catch my mistakes. Surely I am not the first guy who built an archetype and wanted to test it from Continuous Integration, has someone already solved this problem? I would guess the ideal would be to have a TestNG/JUnit test that does the following: 1. Create new project from archetype in memory or a temp directory somewhere. It won't be needed once the test has finished running. 2. Run maven commands on the new project (mvn test jetty:run) to confirm the unit tests pass. 3. Trigger an HttpUnit test to confirm the JSF code renders correctly. If there's no pre-canned solution to this problem, how difficult would it be to have one project run maven from TestNG to trigger the archetype:generate and then a maven build from JUnit or TestNG? Thanks in advance, Steven -- View this message in context: http://old.nabble.com/How-can-I-automate-the-testing-of-my-archetype---Maven-Build-from-TestNG--tp26850764p26850764.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How can I automate the testing of my archetype? Maven Build from TestNG?
Have a look at the documentation or consult the source code for the maven-compiler-plugin to see it in action. Regards Jeff On Sat, Dec 19, 2009 at 10:20 AM, Donszelmann Mark mark.donszelm...@gmail.com wrote: Hi do you have an example ? Regards Mark Donszelmann On Dec 19, 2009, at 9:36 AM, Stephen Connolly wrote: i'd use the invoker plugin 2009/12/18 JavaGeek nos...@boscarine.com Hello All, Does anyone have advice on automating the testing of an archetype? I am a community volunteer helping out the JBoss folks with their Weld Java EE 6 archetypes. I currently have a bash script I use to test it, but it requires *NIX and presently requires manually running a selenium test. I'd like to automate it so Hudson can catch my mistakes. Surely I am not the first guy who built an archetype and wanted to test it from Continuous Integration, has someone already solved this problem? I would guess the ideal would be to have a TestNG/JUnit test that does the following: 1. Create new project from archetype in memory or a temp directory somewhere. It won't be needed once the test has finished running. 2. Run maven commands on the new project (mvn test jetty:run) to confirm the unit tests pass. 3. Trigger an HttpUnit test to confirm the JSF code renders correctly. If there's no pre-canned solution to this problem, how difficult would it be to have one project run maven from TestNG to trigger the archetype:generate and then a maven build from JUnit or TestNG? Thanks in advance, Steven -- View this message in context: http://old.nabble.com/How-can-I-automate-the-testing-of-my-archetype---Maven-Build-from-TestNG--tp26850764p26850764.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal
Re: Maven 3 deprecated properties
Stevo, I think it would be great if you could file a jira for the pom.nameproperty to be deprecated in Maven 3.0! /Anders On Sat, Dec 19, 2009 at 05:26, Brian Fox bri...@infinity.nu wrote: Yes, a long time ago. On Fri, Dec 18, 2009 at 5:39 PM, Paul Benedict pbened...@apache.org wrote: Stevo, I thought all pom.* properties were gone. Weren't they replaced by project.* ? On Fri, Dec 18, 2009 at 4:35 PM, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, When building project with Maven 3.0-alpha-5, warnings appear that pom.version and pom.artifactId properties have been deprecated in favor of their project.* variants. Is it same with pom.name property? I'm asking this because pom.name is not being reported as deprecated, but I expect it to be for consistency reason. Wish this deprecated stuff was listed in Maven 3 compatibility noteshttp://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html . Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: release plugin: version change not only in POMs ?
Your plugin binding binds the resources plugin as configured to the Maven
lifecycle. But you're executing
mvn resources:copy-resources
which isn't executing the lifecycle (it justs executed the copy-resources
goal). Try
mvn install
instead!
If you need to be able to run mvn resources:copy-resources (with the config)
there are ways to solve that as well. Basically you need to move the
configuration part into the pluginManagement section.
/Anders
2009/12/19 Grigory Ptashko gptas...@cmmt.ru
I've inserted the following configuration to my pom.xml (taken from here
http://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html
):
plugin
artifactIdmaven-resources-plugin/artifactId
version2.4.1/version
executions
execution
idcopy-resources/id
!-- here the phase you need --
phasevalidate/phase
goals
goalcopy-resources/goal
/goals
configuration
outputDirectory${basedir}/outputDirectory
resources
resource
directorysrc/non-packaged-resources/directory
filteringtrue/filtering
/resource
/resources
/configuration
/execution
/executions
/plugin
The directory src/non-packaged-resources exists and my file is in there.
When I run mvn resources:copy-resources I get the following:
[ERROR] BUILD ERROR
[INFO]
[INFO] One or more required plugin parameters are invalid/missing for
'resources:copy-resources'
[0] Inside the definition for plugin 'maven-resources-plugin' specify the
following:
configuration
...
outputDirectoryVALUE/outputDirectory
/configuration.
[1] Inside the definition for plugin 'maven-resources-plugin' specify the
following:
configuration
...
resourcesVALUE/resources
/configuration.
But I specified both directories as in the configuration snippet above.
What
am I doing wrong?
2009/12/19 Roland Asmann roland.asm...@adesso.at
Hi,
Sorry, didn't read the mail good enough and made some errors in my
previous reply!
- Put your files in src/main/config with the variables configured
- Have the resource-plugin copyfilter them to the root of the project
(make sure this is done before the pax-plugin runs)
If you use the clean-plugin, it would be a good idea to put the 2 files
in
the root of the project in the list of files to delete as well!
Roland
Sorry for the mess but actually this is not directly the MANIFEST file.
It
is a file used by other plugin to create the MANIFEST file. I am
talking
about the pax plugin and osgi.bnd file which must reside in the root of
the
maven project along with the pom.xml. This file is a not resource, it
is
not
going to the jar at all. It is like a config file for the pax plugin.
And
it
is a text file.
I read the info in the link about the resources plugin - it is exactly
what
I need but without packing this file to the resulting jar and it must
not
go
to the target directory during the build process.
19 декабря 2009 г. 0:45 пользователь Dennis Lundberg
denn...@apache.orgнаписал:
You should try to go about this in another way. Instead of having the
version explicitly in text files, you should filter these files using
the Resources Plugin. See
http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
As for the example of the manifest file, you should let the JAR Plugin
handle the version in there instead of managing it yourself. See
http://maven.apache.org/plugins/maven-jar-plugin/examples/manifest-customization.html
and
http://maven.apache.org/shared/maven-archiver/index.html
Grigory Ptashko wrote:
Hello.
Recently I've got acquainted with the release plugin. I started
using
it,
it
works great but I am missing one feature. The problem is the
following:
the
version that is specified in a POM is used not only in this POM but
also
in
another place in a plain-text format. Actually it is used in the
MANIFEST.MF
in the special header. So when I perform a release the release
version
have
the new version, the trunk version gets the new y-SNAPSHOT version
but
that
MANIFEST.MF file has old version x-SNAPSHOT which becomes wrong both
in
trunk and in the release.
What I want is two steps to be executed while release:perform
(phrases
in
quotes are taken from here
http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html
):
- The first is after the step Change the version in the poms
from
x-SNAPSHOT to a new version (you will be prompted for the
versions
to
use):
Re: Maven 3 deprecated properties
It works well, pom.name deprecation is reported as warning too; I believe it didn't initially because of parent POM resolutionhttp://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ParentPOMResolutionissue project had. Regards, Stevo. On Sat, Dec 19, 2009 at 12:37 PM, Anders Hammar and...@hammar.net wrote: Stevo, I think it would be great if you could file a jira for the pom.nameproperty to be deprecated in Maven 3.0! /Anders On Sat, Dec 19, 2009 at 05:26, Brian Fox bri...@infinity.nu wrote: Yes, a long time ago. On Fri, Dec 18, 2009 at 5:39 PM, Paul Benedict pbened...@apache.org wrote: Stevo, I thought all pom.* properties were gone. Weren't they replaced by project.* ? On Fri, Dec 18, 2009 at 4:35 PM, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, When building project with Maven 3.0-alpha-5, warnings appear that pom.version and pom.artifactId properties have been deprecated in favor of their project.* variants. Is it same with pom.name property? I'm asking this because pom.name is not being reported as deprecated, but I expect it to be for consistency reason. Wish this deprecated stuff was listed in Maven 3 compatibility noteshttp://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html . Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
can pom file be filtered?
dear all:
I have a problem about how to configure war plugin, the details are below.
A file(contain the password and username) as a resource in our project, it
should be
stored in different places with different machine; So i configure the pom as
below, but
maven can't get the varaible!
The pom.xml file
build
filters
filtersrc/main/webconfig/config.properties/filter
/filters
finalNamemonitor/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.1-alpha-1/version
configuration
webResources
resource
directory${file.dir}/directory
filteringtrue/filtering
targetPathWEB-INF/targetPath
/resource
/webResources
/configuration
/plugin
/plugins
/build
and the config.properties file in my windows would be like this:
file.dir = D:/file
but the config.properties file in the server would be like file.dir =
/home/user/test/config
but when i run the mvn package, it should copy the file under the D:/file or
/home/user/test/config
to the WEB-INF
but, the maven tell me the webresource directory is null . maven has not got
the varaible ${file.dir}
how can i make the webresource become a configurable?
Ant suggestion are appreciated!
alien.sulin(苏琳冲)
SuLinchong
Qq387973308
Msn sulinch...@hotmail.com
Maven 3.0 ProjectCycleException
Hi there,
I have a project that contains a build-tools subproject used only to store
configuration files for checkstyle, jalopy and so forth... the parent
project contains plugins that reference the build-tools subproject and the
subproject reference the parent in its parent tag. I'm moving to the new
version of Maven (alpha5) and I got this exception
[INFO] Scanning for projects...
[ERROR] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='net.sourceforge.floggy:build-tools:1.3.0-SNAPSHOT'}' and
'Vertex{label='net.sourceforge.floggy:floggy:1.3.0-SNAPSHOT'}' introduces to
cycle in the graph net.sourceforge.floggy:floggy:1.3.0-SNAPSHOT --
net.sourceforge.floggy:build-tools:1.3.0-SNAPSHOT --
net.sourceforge.floggy:floggy:1.3.0-SNAPSHOT - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectCycleException
How can I fix my issue? What is the common sense to solve this cyclic
reference??
BTW this page doesn't exist
http://cwiki.apache.org/confluence/display/MAVEN/ProjectCycleException
Cheers
Thiago Moreira
No such provider: 'git'
I am unable to generate a changelog report using a git provider. I have set up my POM with the following sections: ... build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId configuration connectionTypeconnection/connectionType /configuration dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-gitexe/artifactId version1.2/version /dependency /dependencies /plugin /plugins /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId /plugin /plugins /reporting scm connectionscm:git:git://github.com/jfinkels/jmona.git/connection urlhttp://github.com/jfinkels/jmona/url /scm ... But I get the following error when trying to generate a report with mvn site: Embedded error: Error rendering Maven report: Cannot run changelog command : No such provider: 'git'. There is a thread from June 2008 related to this topic here: http://www.mail-archive.com/scm-us...@maven.apache.org/msg00055.html How can I get a changelog report using git? -- View this message in context: http://old.nabble.com/No-such-provider%3A-%27git%27-tp26859089p26859089.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: No such provider: 'git'
Hi! You need to add the dependency of the gitexe provider to the maven-changelog-plugin and not to the build. Maven is basically a container like you know from a ServletEngine: it separates classloaders of different plugins from each other - and the build for compile and test are 2 others of that kind. Which means: if you add a dependency (of scopecompile) to your build section, this will not be available on the classpath of your plugin. Instead, as mentioned above, you have to add the dependency to the plugin itself (you might need a pluginManagement section in your case). LieGrue, strub --- jfinkels jeffrey.finkelst...@gmail.com schrieb am Sa, 19.12.2009: Von: jfinkels jeffrey.finkelst...@gmail.com Betreff: No such provider: 'git' An: users@maven.apache.org Datum: Samstag, 19. Dezember 2009, 23:16 I am unable to generate a changelog report using a git provider. I have set up my POM with the following sections: ... build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId configuration connectionTypeconnection/connectionType /configuration dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-gitexe/artifactId version1.2/version /dependency /dependencies /plugin /plugins /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId /plugin /plugins /reporting scm connectionscm:git:git://github.com/jfinkels/jmona.git/connection urlhttp://github.com/jfinkels/jmona/url /scm ... But I get the following error when trying to generate a report with mvn site: Embedded error: Error rendering Maven report: Cannot run changelog command : No such provider: 'git'. There is a thread from June 2008 related to this topic here: http://www.mail-archive.com/scm-us...@maven.apache.org/msg00055.html How can I get a changelog report using git? -- View this message in context: http://old.nabble.com/No-such-provider%3A-%27git%27-tp26859089p26859089.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3 deprecated properties
Maven properties guidehttp://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuideshould be updated to document that pom.* properties are deprecated. Regards, Stevo. On Sat, Dec 19, 2009 at 6:03 PM, Stevo Slavić ssla...@gmail.com wrote: It works well, pom.name deprecation is reported as warning too; I believe it didn't initially because of parent POM resolutionhttp://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ParentPOMResolutionissue project had. Regards, Stevo. On Sat, Dec 19, 2009 at 12:37 PM, Anders Hammar and...@hammar.net wrote: Stevo, I think it would be great if you could file a jira for the pom.nameproperty to be deprecated in Maven 3.0! /Anders On Sat, Dec 19, 2009 at 05:26, Brian Fox bri...@infinity.nu wrote: Yes, a long time ago. On Fri, Dec 18, 2009 at 5:39 PM, Paul Benedict pbened...@apache.org wrote: Stevo, I thought all pom.* properties were gone. Weren't they replaced by project.* ? On Fri, Dec 18, 2009 at 4:35 PM, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, When building project with Maven 3.0-alpha-5, warnings appear that pom.version and pom.artifactId properties have been deprecated in favor of their project.* variants. Is it same with pom.name property? I'm asking this because pom.name is not being reported as deprecated, but I expect it to be for consistency reason. Wish this deprecated stuff was listed in Maven 3 compatibility notes http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html . Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: No such provider: 'git'
struberg wrote: Hi! You need to add the dependency of the gitexe provider to the maven-changelog-plugin and not to the build. Maven is basically a container like you know from a ServletEngine: it separates classloaders of different plugins from each other - and the build for compile and test are 2 others of that kind. Which means: if you add a dependency (of scopecompile) to your build section, this will not be available on the classpath of your plugin. Instead, as mentioned above, you have to add the dependency to the plugin itself (you might need a pluginManagement section in your case). I'm not really sure that I understood what you were trying to say, but I've changed my POM and I still get the same error: ... build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-gitexe/artifactId version1.2/version /dependency /dependencies /plugin /plugins /pluginManagement /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId /plugin /plugins /reporting ... -- View this message in context: http://old.nabble.com/No-such-provider%3A-%27git%27-tp26859089p26860457.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: No such provider: 'git'
You need to add the dependency of the gitexe provider to the maven-changelog-plugin and not to the build. I'm not really sure that I understood what you were trying to say, but I've changed my POM and I still get the same error: DepMgmt does not affect reporting plugins in M2. You need to add the dep directly to the plugin in the reporting section. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: No such provider: 'git'
Wayne Fay wrote: DepMgmt does not affect reporting plugins in M2. You need to add the dep directly to the plugin in the reporting section. I've added the plugin directly to the reporting section, like this: ... reporting plugins plugin groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-gitexe/artifactId /plugin /plugins /reporting ... but now I get an error when running mvn site: snip [ERROR] FATAL ERROR [INFO] [INFO] The plugin descriptor for the plugin Plugin [org.apache.maven.scm:maven-scm-provider-gitexe] was not found. Please verify that the plugin JAR /home/jeff/.m2/repository/org/apache/maven/scm/maven-scm-provider-gitexe/1.2/maven-scm-provider-gitexe-1.2.jar is intact. [INFO] [INFO] Trace java.lang.IllegalStateException: The plugin descriptor for the plugin Plugin [org.apache.maven.scm:maven-scm-provider-gitexe] was not found. Please verify that the plugin JAR /home/jeff/.m2/repository/org/apache/maven/scm/maven-scm-provider-gitexe/1.2/maven-scm-provider-gitexe-1.2.jar is intact. /snip -- View this message in context: http://old.nabble.com/No-such-provider%3A-%27git%27-tp26859089p26860814.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
