Re: AW: No such provider: 'git'
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: No, you were so close before, did you read what I wrote? Try this: reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId !-- best practice is to add the version for your plugin here -- dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-gitexe/artifactId version1.2/version /dependency /dependencies /plugin /plugins /reporting 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: No, you were so close before, did you read what I wrote? Try this: reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-changelog-plugin/artifactId !-- best practice is to add the version for your plugin here -- dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-gitexe/artifactId version1.2/version /dependency /dependencies /plugin /plugins /reporting I did try that, but that is illegal syntax, based on the POM 4.0.0 XML schema definition (at http://maven.apache.org/maven-v4_0_0.xsd), the relevant parts of which I have paraphrased below: ... xs:complexType name=ReportPlugin xs:all xs:element name=groupId minOccurs=0 type=xs:string default=org.apache.maven.plugins xs:element name=artifactId minOccurs=0 type=xs:string xs:element name=version minOccurs=0 type=xs:string xs:element name=inherited minOccurs=0 type=xs:string xs:element name=configuration minOccurs=0 xs:element name=reportSets minOccurs=0 /xs:all /xs:complexType ... Running Maven with the POM as you have described it in your above post results in a parse error. By the way, my output from mvn --version is as follows: snip Apache Maven 2.2.1 (rdebian-1) Java version: 1.6.0_0 Java home: /usr/lib/jvm/java-6-openjdk/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux version: 2.6.31-16-generic arch: i386 Family: unix /snip -- View this message in context: http://old.nabble.com/No-such-provider%3A-%27git%27-tp26859089p26865475.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 ?
This helped me! Thanks a lot!
19 декабря 2009 г. 14:45 пользователь Anders Hammar and...@hammar.netнаписал:
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
Re: AW: No such provider: 'git'
I did try that, but that is illegal syntax, based on the POM 4.0.0 XML schema definition (at http://maven.apache.org/maven-v4_0_0.xsd), the relevant parts of which I have paraphrased below: Perhaps try adding it as an extension (google for info here)? I have zero experience with what you're trying to do, so just throwing out guesses. 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: Perhaps try adding it as an extension (google for info here)? Same error with an extensions element in the POM, like this: ... build extensions extension groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-gitexe/artifactId version1.2/version /extension /extensions /build ... -- View this message in context: http://old.nabble.com/No-such-provider%3A-%27git%27-tp26859089p2688.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'
Oh, it looks like this issue was fixed in maven-changelog-plugin version 2.2: http://jira.codehaus.org/browse/MCHANGELOG-92 But version 2.2 is not in the repository yet... -- View this message in context: http://old.nabble.com/No-such-provider%3A-%27git%27-tp26859089p26866688.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
maven-invoker-plugin, plugin testing, and IT's with plugin snapshot dependencies
Hello Maven users, If one installs a snapshot of a plugin (P1) in local repository, and for other plugin (P2) an IT, run using maven-invoker-plugin configured as recommended to use isolated local repository for integration tests, is a project which makes use of P1 snapshot, IT will fail since P1 snapshot is not available in IT local repository. Seems it's not currently (v1.5) possible to configure maven-invoker-plugin's install mojo to install given plugin artifacts into IT local repository. Regards, Stevo.
Re: AW: No such provider: 'git'
hi! You catched a very old finesse of reporting plugin configuration (in fact, lots of Jira issues have been opened for that very topic). Please read http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html for an example how it should work. LieGrue, strub --- jfinkels jeffrey.finkelst...@gmail.com schrieb am So, 20.12.2009: Von: jfinkels jeffrey.finkelst...@gmail.com Betreff: Re: AW: No such provider: 'git' An: users@maven.apache.org Datum: Sonntag, 20. Dezember 2009, 20:49 Oh, it looks like this issue was fixed in maven-changelog-plugin version 2.2: http://jira.codehaus.org/browse/MCHANGELOG-92 But version 2.2 is not in the repository yet... -- View this message in context: http://old.nabble.com/No-such-provider%3A-%27git%27-tp26859089p26866688.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: java 1.4 versus the maven-eclipse-plugin
On Sat, Dec 19, 2009 at 9:48 AM, Benson Margulies bimargul...@gmail.com wrote: The eclipse plugin forces the compiler source version to 1.4 for maven plugins. I'm building a maven plugin that I want to require 1.5. Is there a way to tell the eclipse plugin to stop harassing me? Did you check the docs? http://maven.apache.org/plugins/maven-eclipse-plugin/trouble-shooting/index.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: java 1.4 versus the maven-eclipse-plugin
I did. On Sun, Dec 20, 2009 at 5:26 PM, Barrie Treloar baerr...@gmail.com wrote: On Sat, Dec 19, 2009 at 9:48 AM, Benson Margulies bimargul...@gmail.com wrote: The eclipse plugin forces the compiler source version to 1.4 for maven plugins. I'm building a maven plugin that I want to require 1.5. Is there a way to tell the eclipse plugin to stop harassing me? Did you check the docs? http://maven.apache.org/plugins/maven-eclipse-plugin/trouble-shooting/index.html - 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: java 1.4 versus the maven-eclipse-plugin
On Sun, Dec 20, 2009 at 5:26 PM, Barrie Treloar baerr...@gmail.com wrote: On Sat, Dec 19, 2009 at 9:48 AM, Benson Margulies bimargul...@gmail.com wrote: The eclipse plugin forces the compiler source version to 1.4 for maven plugins. I'm building a maven plugin that I want to require 1.5. Is there a way to tell the eclipse plugin to stop harassing me? Did you check the docs? http://maven.apache.org/plugins/maven-eclipse-plugin/trouble-shooting/index.html On Mon, Dec 21, 2009 at 9:34 AM, Benson Margulies bimargul...@gmail.com wrote: I did. To my knowledge there is nothing in the eclipse plugin that forces compiler source values. This, as described in the above links, is taken from the maven-compiler-plugin. What do the relevant bits of your pom look like? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: java 1.4 versus the maven-eclipse-plugin
While I read the doc, it didn't seem applicable. Now that you tell me that there's no special trickery going on that tries to force 1.4 on mojo projects, I'm off to revisit all the poms to see there's something I missed. On Sun, Dec 20, 2009 at 8:51 PM, Barrie Treloar baerr...@gmail.com wrote: On Sun, Dec 20, 2009 at 5:26 PM, Barrie Treloar baerr...@gmail.com wrote: On Sat, Dec 19, 2009 at 9:48 AM, Benson Margulies bimargul...@gmail.com wrote: The eclipse plugin forces the compiler source version to 1.4 for maven plugins. I'm building a maven plugin that I want to require 1.5. Is there a way to tell the eclipse plugin to stop harassing me? Did you check the docs? http://maven.apache.org/plugins/maven-eclipse-plugin/trouble-shooting/index.html On Mon, Dec 21, 2009 at 9:34 AM, Benson Margulies bimargul...@gmail.com wrote: I did. To my knowledge there is nothing in the eclipse plugin that forces compiler source values. This, as described in the above links, is taken from the maven-compiler-plugin. What do the relevant bits of your pom look like? - 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
Amazon EC2 EBS Volume for Maven central repository
Cheers, After experimenting a bit with EC2, It seems it would be ideal if there were an EBS volume that had all the Maven central repository within it. Does anyone know of such a thing? thanks, Mark - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Amazon EC2 EBS Volume for Maven central repository
I imagine there have to be a number of projects/companies out there using Maven artifacts and incurring bandwidth costs to build systems. Atlassian seems to be recommending the practice to its Bamboo users... http://confluence.atlassian.com/display/BAMBOO/Populating+your+EBS+volume#PopulatingyourEBSvolume-UploadingMaven2repositorydata I know its not much, but on large builds and continuous integration projects would benefit. What's the current storage requirements for the central repository at this time? I wonder if the maven central repo could qualify as a public dataset? http://aws.amazon.com/publicdatasets/ http://developer.amazonwebservices.com/connect/forum.jspa?forumID=55 Mark On Sun, Dec 20, 2009 at 8:28 PM, Carlos Sanchez car...@apache.org wrote: there was some talk about it during ApacheCON but there are some costs associated - S3 storage of the EBS snapshot - bandwidth to upload the repo and keep it up to date - an EC2 machine to do the rsync and scheduled snapshots of the EBS volume There's an option to sell it so users end paying the fees On Sun, Dec 20, 2009 at 8:18 PM, Mark Diggory mdigg...@gmail.com wrote: Cheers, After experimenting a bit with EC2, It seems it would be ideal if there were an EBS volume that had all the Maven central repository within it. Does anyone know of such a thing? thanks, Mark - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
