Re: git release:prepare does not commit the poms (Linux)
I believe I did try that as well, but I will give it another try, I will let you know the results, I also did release:clean and a -Dresume=false, so any lingering release.properties should not be of influence... thanks for the reply! Willem 2013/3/7 Mark Derricutt m...@talios.com The 2.4 git problems are related to the release plugin ignoring local checkout/disabling push settings primarily, so that your release is tagged locally, but then MRP tries to clone the tag from upstream and fails. Either way, dropping back to 2.3.2 to eliminate those issues would be a good point of call. One thing I've also noticed that sounds familiar, make sure you don't have a release.properties in your working directory prior to a new release - sometimes I've noticed it gets left behind somehow and depending on whats in that file, MRP will resume the release from a point where it thinks your version number has already been updated - and thus releases/deploys a -SNAPSHOT to your release repo. Mark Robert Scholte wrote: could you try to use maven-release-plugin 2.3.2? There are some known issues with GIT and the maven-release-plugin 2.4, which need to be fixed in the SCM project first. --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unpacking jars into target/classes
Am 02.03.2013 21:32, schrieb Joachim Durchholz:
Hi all,
I have two jars from an external source and need to merge their contents
into the target/classes tree until the process-classes phase.
I'm not sure what plugin(s) can be used to achieve this effect.
As wholeheartedly as I agree to all what was said about Maven being
opinionated (in a good way) and that one is best advised to stick to the
conventions, there are cases where you just can't... and in my
experience maven is quit good at handling these edge cases.
For the problem at hand, have a look at the truezip-m-p over at the
codehaus mojo project, it should provide what you want:
properties
mylib1.archive${project.basedir}/libs/lib1.jar/mylib1.archive
/properties
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdtruezip-maven-plugin/artifactId
version1.1/version
executions
execution
idcopy-lib1-classes/id
goals
goalcopy/goal
/goals
phaseprocess-classes/phase
configuration
fileset
directory${mylib1.archive}/directory
includes
include**/*/include
/includes
excludes
excludeMETA-INF/MANIFEST.MF/exclude
/excludes
outputDirectory${project.build.outputDirectory}/outputDirectory
/fileset
/configuration
/execution
/executions
/plugin
/plugins
/build
Directory structure:
- external (directory tree that holds the externally-provided files)
- libs
- cubes.jar (class files)
- cubes-resources.jar (nonclass files)
- license etc. (other data, irrelevant to task at hand)
(yeah I know the structure sucks, can't do anything about it)
- target (maven scratchpad)
- classes (files for main artifact jar are collected here I think)
I need the files inside libs/cubes.jar and libs/cubes-resource.jar
unpacked and placed inside target/classes, preserving the in-jar
directory structure.
I want this to run in the process-classes, latest, because that's the
last pertinent phase that m2e will run.
What's the best (least-hassle) plugin that will do this?
Regards,
Jo
-Tim
P.S.: Please resist the temptation to tell me that I want the wrong
thing. I need help with solving a problem, I don't need a lecture.
-
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: git release:prepare does not commit the poms (Linux)
BTW With 2.4 the tag *is* set remote as well, according to my milage... Op 07-03-13 20:01, Mark Derricutt schreef: The 2.4 git problems are related to the release plugin ignoring local checkout/disabling push settings primarily, so that your release is tagged locally, but then MRP tries to clone the tag from upstream and fails. Either way, dropping back to 2.3.2 to eliminate those issues would be a good point of call. One thing I've also noticed that sounds familiar, make sure you don't have a release.properties in your working directory prior to a new release - sometimes I've noticed it gets left behind somehow and depending on whats in that file, MRP will resume the release from a point where it thinks your version number has already been updated - and thus releases/deploys a -SNAPSHOT to your release repo. Mark Robert Scholte wrote: could you try to use maven-release-plugin 2.3.2? There are some known issues with GIT and the maven-release-plugin 2.4, which need to be fixed in the SCM project first. - 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: Unpacking jars into target/classes
Thanks, somehow I overlooked the truezip plugin. It should do the trick. Regards, Jo - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
No mojo definitions were found for plugin
Hi,
I'm working on the Debian package for the maven-plugin-tools. In this package
we first use a prepared plugin.xml and just copy it into the maven-plugin-
plugin.jar. Then we call the plugin:descriptor goal to actually generate the
plugin.xml and repackage again afterwards.
But maven doesn't like debian... :-) Do you have any hint where I could start
to debug? The class files are there in target/classes. Maven is executed in
the maven-plugin-plugin directory.
[DEBUG] (f) local = Repository[local|file:///tmp/buildd/maven-plugin-
tools-3.2/debian/tmp/maven-repo/]
[DEBUG] (f) outputDirectory = /tmp/buildd/maven-plugin-tools-3.2/maven-
plugin-plugin/target/classes/META-INF/maven
[DEBUG] (f) remoteRepos = [Repository[central|
http://repo1.maven.org/maven2]]
[DEBUG] (f) skip = false
[DEBUG] (f) skipDescriptor = false
[DEBUG] (f) skipErrorNoDescriptorsFound = false
[DEBUG] (f) project = MavenProject: org.apache.maven.plugins:maven-plugin-
plugin:3.2 @ /tmp/buildd/maven-plugin-tools-3.2/maven-plugin-plugin/pom.xml
[DEBUG] -- end configuration --
[INFO] [plugin:descriptor {execution: default-cli}]
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to read mojo
metadata, i.e. build is platform dependent!
[DEBUG] Using 0 mojo extractors.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error extracting plugin descriptor: 'No mojo definitions were found for
plugin: org.apache.maven.plugins:maven-plugin-plugin.'
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error extracting
plugin descriptor: 'No mojo definitions were found for plugin:
org.apache.maven.plugins:maven-plugin-plugin.'
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:100)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error extracting
plugin descriptor: 'No mojo definitions were found for plugin:
org.apache.maven.plugins:maven-plugin-plugin.'
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:245)
at
org.apache.maven.plugin.plugin.DescriptorGeneratorMojo.execute(DescriptorGeneratorMojo.java:92)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 9 more
Caused by:
org.apache.maven.plugin.descriptor.InvalidPluginDescriptorException: No mojo
definitions were found for plugin: org.apache.maven.plugins:maven-plugin-
plugin.
at
org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:126)
at
org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:233)
... 12 more
Regards,
Thomas Koch, http://www.koch.ro
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Release:perform failing on git ...
Mirko, Thanks. I got around this for the moment by temporarily adding an IdentityFile line to my ~/.ssh/config. However, I'd rather be able to configure this in Maven somehow. I guess I have a JIRA in my future. --benson On Fri, Mar 8, 2013 at 12:51 AM, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello Benson, when this repository is on a host of it's own adding an entry to ssh-config may help (http://linux.die.net/man/5/ssh_config) . Regards Mirko -- Sent from my mobile On Mar 8, 2013 2:53 AM, Benson Margulies bimargul...@gmail.com wrote: Actually, I know what's happening. To talk to this repo, I need to use a custom ssh key. At command level, I use a shell script: git clone --config ssh.key=/users/benson/.ssh/id_basis_rsa $@ THe question is, how do I get the m-r-p to do this? On Thu, Mar 7, 2013 at 8:49 PM, Tim Wu T tim.t...@ericsson.com wrote: I think it should better for you to provide more stacktrace. [ERROR] The git-clone command failed. This message is too limited to find the root cause. Br, Tim -Original Message- From: Benson Margulies [mailto:bimargul...@gmail.com] Sent: Friday, March 08, 2013 9:47 AM To: Maven Users List Subject: Release:perform failing on git ... release plugin 2.3.2 prepare does fine. perform fails with: [INFO] --- maven-release-plugin:2.3.2:perform (default-cli) @ find-jug-dist-dir-maven-plugin --- [INFO] Checking out the project to perform the release ... [INFO] Executing: /bin/sh -c cd /Users/benson/x/find-jug-dist-dir-maven-plugin/target git clone --branch find-jug-dist-dir-maven-plugin-1 g...@github.com:basis-technology-corp/find-jug-dist-dir-maven-plugin.git /Users/benson/x/find-jug-dist-dir-maven-plugin/target/checkout [INFO] Working directory: /Users/benson/x/find-jug-dist-dir-maven-plugin/target [ERROR] The git-clone command failed. scm looks like: scm connectionscm:git:g...@github.com: basis-technology-corp/find-jug-dist-dir-maven-plugin.git/connection developerConnectionscm:git:g...@github.com: basis-technology-corp/find-jug-dist-dir-maven-plugin.git/developerConnection url https://github.com/basis-technology-corp/find-jug-dist-dir-maven-plugin /url tagHEAD/tag /scm - 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: Unpacking jars into target/classes
Le 8 mars 2013 08:29, Joachim Durchholz j...@durchholz.org a écrit : Am 08.03.2013 04:48, schrieb Ron Wheeler: I am not sure what you expect us to say. Simply stick with the question at hand and don't waste everybody's time with evangelizing and philosophy. By your own experience, your approach doesn't work; you won't try to do it the right way; If there's no way to get it to work (and that's the answer I got from Baptiste), then it's not me who's doing it wrong. Where did I write there's no way to get it to work? Initially I actually just gave you a hint of the path I would look at. You then transformed this thread into a troll... -- Baptiste
Re: Unpacking jars into target/classes
Maybe you could have a look at the truezip maven plugin: http://mojo.codehaus.org/truezip/truezip-maven-plugin/ Regards Jeff On Fri, Mar 8, 2013 at 2:05 PM, Baptiste MATHUS m...@batmat.net wrote: Le 8 mars 2013 08:29, Joachim Durchholz j...@durchholz.org a écrit : Am 08.03.2013 04:48, schrieb Ron Wheeler: I am not sure what you expect us to say. Simply stick with the question at hand and don't waste everybody's time with evangelizing and philosophy. By your own experience, your approach doesn't work; you won't try to do it the right way; If there's no way to get it to work (and that's the answer I got from Baptiste), then it's not me who's doing it wrong. Where did I write there's no way to get it to work? Initially I actually just gave you a hint of the path I would look at. You then transformed this thread into a troll... -- Baptiste -- Jeff MAURY Legacy code often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
Re: Unpacking jars into target/classes
On Fri, Mar 8, 2013 at 12:28 AM, Joachim Durchholz j...@durchholz.org wrote: Matthew mentioned install-file, but I already explained why a Maven repo is not an option. Just a point of clarification, install-file installs artifacts into a machines local repository cache, and in no way requires an MRM. I think Matthew was suggesting to use install-file specifically because you are not using an MRM. Unfortunately, the local repository cache is often referred to simply as a repository and this frequently causes confusion. Perhaps we (the maven community) should refer to the local repository cache by a different name e.g. artifact cache. Cheers
[ANN] Maven Indexer 5.1.1 Released
The Apache Maven team is pleased to announce the release of the Maven Indexer, version 5.1.1. Apache Maven Indexer (former Sonatype Nexus Indexer) is the defacto standard for producing indexes of Maven repositories. The Indexes are produced and consumed by all major tools in the ecosystem. http://maven.apache.org/maven-indexer/ Release notes - Maven Indexer 5.1.1 Link: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12112version=18988 Bug [MINDEXER-70] - SearchEngine does not releaseIndexSearcher in some cases [MINDEXER-71] - Do not implicitely close indexing context Have fun, -The Apache Maven team
Re: [ANN] Maven Indexer 5.1.1 Released
are there any steps to be taken by 3rd party integrators when upgrading? Milos Kleint On Fri, Mar 8, 2013 at 3:10 PM, Tamás Cservenák ta...@cservenak.net wrote: The Apache Maven team is pleased to announce the release of the Maven Indexer, version 5.1.1. Apache Maven Indexer (former Sonatype Nexus Indexer) is the defacto standard for producing indexes of Maven repositories. The Indexes are produced and consumed by all major tools in the ecosystem. http://maven.apache.org/maven-indexer/ Release notes - Maven Indexer 5.1.1 Link: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12112version=18988 Bug [MINDEXER-70] - SearchEngine does not releaseIndexSearcher in some cases [MINDEXER-71] - Do not implicitely close indexing context Have fun, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unpacking jars into target/classes
On 08/03/2013 9:07 AM, Doug Douglass wrote: On Fri, Mar 8, 2013 at 12:28 AM, Joachim Durchholz j...@durchholz.org wrote: Matthew mentioned install-file, but I already explained why a Maven repo is not an option. Just a point of clarification, install-file installs artifacts into a machines local repository cache, and in no way requires an MRM. I think Matthew was suggesting to use install-file specifically because you are not using an MRM. Unfortunately, the local repository cache is often referred to simply as a repository and this frequently causes confusion. Perhaps we (the maven community) should refer to the local repository cache by a different name e.g. artifact cache. Cheers workstation cache? -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unpacking jars into target/classes
I have always referred to it as the local dot m2 cache. people know exactly what I am talking about when I say that... Thanks, Roy Lyons On 3/8/13 8:16 AM, Ron Wheeler rwhee...@artifact-software.com wrote: On 08/03/2013 9:07 AM, Doug Douglass wrote: On Fri, Mar 8, 2013 at 12:28 AM, Joachim Durchholz j...@durchholz.org wrote: Matthew mentioned install-file, but I already explained why a Maven repo is not an option. Just a point of clarification, install-file installs artifacts into a machines local repository cache, and in no way requires an MRM. I think Matthew was suggesting to use install-file specifically because you are not using an MRM. Unfortunately, the local repository cache is often referred to simply as a repository and this frequently causes confusion. Perhaps we (the maven community) should refer to the local repository cache by a different name e.g. artifact cache. Cheers workstation cache? -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - 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: No mojo definitions were found for plugin
Thomas Koch: [DEBUG] Using 0 mojo extractors. I could track down the problem. The field mojoDescriptorExtractors in the DefaultMojoScanner class is not filed by plexus with the available extractors although they should be available on the classpath. Now I don't know how to debug this issue. Why doesn't plexus find those extractors? Thomas Koch, http://www.koch.ro - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Shared Utils 0.3 Released
The Maven team is pleased to announce the release of
maven-shared-utils, version 0.3
This project aims to be a functional replacement for
{{{http://plexus.codehaus.org/plexus-utils}plexus-utils}} in Maven.
It is not a 100% API compatible replacement though but a replacement
with improvements:
lots of methods got cleaned up, generics got added and we dropped a
lot of unused code. Although all
the classes are in different packages from plexus-utils, if the method
is present it will have the same
semantics, facilitating easy conversion.
http://maven.apache.org/shared/maven-shared-utils/
You should specify the version in your project's plugin configuration:
dependency
groupIdorg.apache.maven.shared/groupId
artifactIdmaven-shared-utils/artifactId
version0.3/version
plugin
Release Notes - Maven Shared Components - Version maven-shared-utils-0.3
** Improvement
* [MSHARED-272] - Make ShutdownHookUtils public
** BUGS
* SUREFIRE-946
* SUREFIRE-950
Enjoy,
-The Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven properties of dependencies
I have a plugin that uses DependencyGraphBuilder to find the dependencies of a MavenProject. Traversing the graph I get a DependencyNode , however, I need to access a particular maven property of the dependency's pom and this is not possible AFAIK. Is this true? is it really not possible to access the properties of a dependency pom using DependencyGraphBuilder component? if so, how could I manage to grab those? Thank you, Alejandro DISCLAIMER: Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.
Re: [ANN] Maven Indexer 5.1.1 Released
None I am aware of. Igor? Thanks, ~t~ (mobile) On Mar 8, 2013 3:15 PM, Milos Kleint mkle...@gmail.com wrote: are there any steps to be taken by 3rd party integrators when upgrading? Milos Kleint On Fri, Mar 8, 2013 at 3:10 PM, Tamás Cservenák ta...@cservenak.net wrote: The Apache Maven team is pleased to announce the release of the Maven Indexer, version 5.1.1. Apache Maven Indexer (former Sonatype Nexus Indexer) is the defacto standard for producing indexes of Maven repositories. The Indexes are produced and consumed by all major tools in the ecosystem. http://maven.apache.org/maven-indexer/ Release notes - Maven Indexer 5.1.1 Link: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12112version=18988 Bug [MINDEXER-70] - SearchEngine does not releaseIndexSearcher in some cases [MINDEXER-71] - Do not implicitely close indexing context Have fun, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
