Dealing with buggy plugins

One of my projects depends on a couple of third-party plugins available on Central. These plugins provide key functionality for the build, but they also contain some serious bugs. Let's say I fix these bugs myself and submit patches to the maintainers. It could be months before the patches are

Re: Dealing with buggy plugins

This is common pattern, you must have your own repo and cut your own internal release of the plugin with your fixes. Then bug the maintainer to commit it, however the more tests you put in your patch, the quicker it is committed. -Dan On Sat, Dec 26, 2009 at 1:05 AM, Trevor Harmon

Re: Dealing with buggy plugins

On Dec 26, 2009, at 3:15 AM, Dan Tran wrote: you must have your own repo and cut your own internal release of the plugin with your fixes. Why exactly is a repo necessary? Setting one up just to host a couple of patched plugins for my personal use seems like overkill. If it is required, what

Re: Dealing with buggy plugins

On Sat, Dec 26, 2009 at 1:49 AM, Trevor Harmon tre...@vocaro.com wrote: On Dec 26, 2009, at 3:15 AM, Dan Tran wrote: you must have your own repo and cut your own internal release of the plugin with your fixes. Why exactly is a repo necessary? Setting one up just to host a couple of patched

release plugin doesnt update parent pom

Hi Consider a multi-module project with a root pom.xml and this root pom has another parent pom.xml which is considered as separated project parent groupIdcom.foo.core/groupId artifactIdcore-parent/artifactId version0.0.2-SNAPSHOT/version /parent when executing

AW: release plugin doesnt update parent pom

I think this is a minor bug. let's sum up the facts: a.) if you start the mvn release:prepare in a certain directory, maven will _not_ automatically step out of this directory. b.) If the parent pom is outside of your scm url location, then it cannot get updated. I think the correct

Re: Dealing with buggy plugins

Well, I'd say it's better to install the MRM (Nexus or Artifactory) on a server in your development network. All your developers will be dependent on this to get the patched plugins (or any other internal artifacts). Also, what you should do is to set up the MRM to proxy all external repos your

Re: AW: release plugin doesnt update parent pom

Thanks. Actually NO. it create the release version with the same parent SNAPSHOT version. This only happens if you have a parent pom and not dependency. To clarify let me tell you that we have a core-parent project which is contains only a pom.xml with common dependencies for all projects to be

Re: AW: release plugin doesnt update parent pom

hi! since I have not much time left now, I can only ask a quick hint: What about moving the parent pom.xml (containing the dependencyManagement) down into your build directory and create an own 'build' pom.xml (containing the modules) in the parent directory? This definitely works and is used

Re: AW: release plugin doesnt update parent pom

Thanks Well this definitely works but here in our company there are more than 15 projects each developed by a team and the parent dependencies placed in core-parent are actually needed for all the projects and they are considered as our local framework so I can't ask each project manager to move

JNI binaries to maven module

Hello, I need to use a JNI library in multiple modules of my maven project. The binaries of this library (dll and jars) are frequently updated so I don't want to manually add each file of the distribution to the maven repository. So I decided to write a maven module that packages all the

Re: JNI binaries to maven module

I'd suggest you do add each of the binaries of the library as separate artifacts. Then you could use the normal dependency machanism of Maven. Write a simple shell script that deploys all of the binaries to your repo whenever they are update. That shell script could do pretty much anything you

Apache parent pom

Hello Maven users, Apache parent pom, like one for version 7 which is being voted on these days, contains apache.snapshots repository declaration. Why is that apache.snapshots repository definition needed? IMO it is in contradiction with rules for deploying artifacts on central repository, and it

Re: JNI binaries to maven module

Hi or use the maven-nar-plugin at http://duns.github.com/maven-nar-plugin/ which handles most of this for you. Regards Mark Donszelmann On Dec 26, 2009, at 3:43 PM, Anders Hammar wrote: I'd suggest you do add each of the binaries of the library as separate artifacts. Then you could use the

Re: JNI binaries to maven module

This is certainly the simplest way to deploy the library but if I do it this way, I should have to write a pom file for each artifact to declare the dependencies between the artifacts of the library and, for convenience a parent pom that has a dependency on each artifact. So it can potentially

Re: JNI binaries to maven module

Hi, I just took a look on the maven-nar-plugin and it seems to be used to compile and package a JNI library but I don't have to compile my library. Perharps this plugin can be used so as it skips the compilation of the library ? duns wrote: Hi or use the maven-nar-plugin at

Maven Webstart plugin problem

Hello, I am having the same problem as mentionned in http://old.nabble.com/Maven-Webstart-Plugin-td3679895i20.html#a3763345 http://old.nabble.com/Maven-Webstart-Plugin-td3679895i20.html#a3763345 But I am unable to solve it with the information provided there. I have a maven project and I

Re: JNI binaries to maven module

you can use maven-dependency-plugin to unpack your zip for you, the zip dont have to be in dependency list ( via unpack's goal) On Sat, Dec 26, 2009 at 8:51 AM, Tich29 tic...@gmail.com wrote: This is certainly the simplest way to deploy the library but if I do it this way, I should have to

Re: Apache parent pom

this definition is for -Snapshot dependencies only. since artifacts deployed to central cannot have -snapshot dependencies, then the build should not be affected by the -snapshot only repository. the rules for central state that you cannot reference any repositories with the exception of

Re: JNI binaries to maven module

Hi there is an example in the source of a 3rd party jni library, which is what you want. Regards Mark On Dec 26, 2009, at 6:23 PM, Tich29 wrote: Hi, I just took a look on the maven-nar-plugin and it seems to be used to compile and package a JNI library but I don't have to compile my

I have to include a jar file in a deliverable

Hi, How to include a jar file in an application jar file I did read many documents and did not find anything. Let say fir example: I am delivering a application xyz.war and that depends on classes12.zip file at run time. I wanted to include this file in my application say I wanted to add the

Re: authentication problem to nexus repository with non-anonymous user

I just looked again at your stack traces. What I originally assumed was an auth problem appears to be a socket issue: Caused by: java.net.ConnectException: Connection refused: connect Do you have a firewall on your system? It appears that something is blocking the connection to the server,

Re: Dealing with buggy plugins

On Dec 26, 2009, at 5:41 AM, Anders Hammar wrote: Well, I'd say it's better to install the MRM (Nexus or Artifactory) on a server in your development network. All your developers will be dependent on this to get the patched plugins (or any other internal artifacts). A couple of issues with

Re: Dealing with buggy plugins

On Dec 26, 2009, at 4:04 AM, Dan Tran wrote: Another option is the fork the plugin into your SCM, that is even worse You mean the binaries or the source? I agree that managing JARs in an SCM is not a good idea, but I don't see anything wrong with putting a patched branch of the plugin into my

Re: I have to include a jar file in a deliverable

On Sat, Dec 26, 2009 at 4:01 PM, kunduruswaroop swaroo...@hotmail.com wrote: How to include a jar file in an application jar file I did read many documents and did not find anything. Let say fir example: I am delivering a application xyz.war and that depends on classes12.zip file at run

Re: Dealing with buggy plugins

yes, fork the source into your scm. This way you can build and install the plugin to your local repo -D On Sat, Dec 26, 2009 at 4:20 PM, Trevor Harmon tre...@vocaro.com wrote: On Dec 26, 2009, at 4:04 AM, Dan Tran wrote: Another option is the fork the plugin into your SCM, that is even worse

Re: Dealing with buggy plugins

yes, fork the source into your scm. This way you can build and install the plugin to your local repo You will also want to change the groupId of your forked plugin so you can eventually go back to the original plugin when they incorporate your diffs and release a new version... assuming you

Re: Dealing with buggy plugins

good advice from Wayne, but for those plugins belong to default lifecycle (ie surefire), the groudId must stay the same. -D On Sat, Dec 26, 2009 at 8:58 PM, Wayne Fay wayne...@gmail.com wrote: yes, fork the source into your scm. This way you can build and install the plugin to your local repo

filter some resources files and put them to other module.

Hi: I have a project containing three modules, Server,Io,and Webapp, and the webapp is a pakcage of war, the other two are jars. Since the web module need to read some config files,so I want to put them under the WEB-INF/conf. However I also want to file the config files under the Io module by

Canonical order of POM elements?

Has Maven ever produced a plugin to canonically order (rewrite) an existing POM (and respecting whitespace)? Validating against an XSD, I know element order doesn't matter -- but it would be nice if there was a way to uniformly order my POM. No such order apparently exists in the wild. Paul