Re: Release plugin & git repo with multiple projects
Thanks ! Migration would be a bit stiffer than I thought, but it make sense. Jean-Laurent On Mon, Apr 26, 2010 at 10:18 PM, Justin Edelson wrote: > Jean-Laurent de Morlhon wrote: > >> You say the git way of doing things is 1 project -> 1 git repository, I >> understand, and it's not very far of having a svn repo for every project in >> svn altough the release plugin do not enforce this. >> > Subversion doesn't enforce this. In fact, Subversion is designed to support > a 1 to many relationship between projects and repositories whereas Git is > designed for a 1 to 1 relationship. This has nothing to do with Maven. > > >> The current state of the release plugin force you to have the pom.xml at >> the root of your git repository or to say it differently if you have a >> pom.xml anywhere else than the root directory you can't release the project. >> (of course submodule of root located pom.xml do not count)... >> >> It's also common practice in the maven world to have a parent pom to share >> common settings. If I follow blindlessly the 1 project -> 1 git repository, >> it means I have to setup a git repository for a single parent pom ? >> > A multi-module project should be in a single git repository. An > organizational pom should be in its own repository which may, you are > correct, result in a repository with a single file in it. > > > I have the feeling, but I maybe wrong, that this is more a limitation of >> the release plugin / scm provider more than a design goal. >> > No. It's a design goal. See > https://git.wiki.kernel.org/index.php/GitSvnComparison#Partial_Checkout.2FUsed_bandwidth > > Justin > > >> Those who migrated to git, what do you do for the above cases, especially >> the parent pom one ? >> >> Jean-Laurent >> >> >> On Mon, Apr 26, 2010 at 5:37 PM, Justin Edelson >> > justinedel...@gmail.com>> wrote: >> >>OK. Then we're on the same page... >> >>On 4/26/10 11:32 AM, Kathryn Huxtable wrote: >>> Perhaps I wasn't clear. I don't support multiple projects in one >>repository. Definitely not. I was trying to criticize the >>svn-centric thinking, not support it. >>> >>> I think there should be a JIRA issue to make modules work, given >>that they'll be in separate repositories. >>> >>> I'm not going to file this because I have almost zero experience >>with nested projects. There have been places it would have made >>sense and I shied away. >>> >>> But the release plugin should work with git projects that have >>modules and it should do it in the standard git manner, which is >>one repository containing one project. (Distributed, of course.) >>> >>> -K >>> >>> On Apr 26, 2010, at 9:06 AM, Justin Edelson wrote: >>> >>>> Kathryn- >>>> Maybe I'm misunderstanding what you mean, but I think you have this >>>> exactly backwards. The "svn-centric thinking" is what's >>inspired someone >>>> to put multiple projects in the same repository. AFAIK, this is >>simply >>>> not supported by git, i.e. there's no way to clone, branch or >>tag _part_ >>>> of a repository. >>>> >>>> I am by no means a git expert, so I could be mistaken about this. >>>> >>>> Justin >>>> >>>> >>>> >>>> On 4/26/10 9:21 AM, Kathryn Huxtable wrote: >>>>> Having recently switched from svn to git for most of my >>projects, I have an opinion. >>>>> >>>>> I think you should create a JIRA ticket and consider this a bug. >>>>> >>>>> What we're dealing with here is a bit of svn-centric thinking >>during design. It needs to be fixed. >>>>> >>>>> -K >>>>> >>>>> On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote: >>>>> >>>>>> We're considering migrating from svn to git, we stumble on the >>>>>> maven-release-plugin usage with git. >>>>>> We think we prefer to use a single repository for many >>independently built >>>>>> projects like : >>>>>> >>>>>> foobar-repo.git >>>>
Re: Release plugin & git repo with multiple projects
You say the git way of doing things is 1 project -> 1 git repository, I understand, and it's not very far of having a svn repo for every project in svn altough the release plugin do not enforce this. The current state of the release plugin force you to have the pom.xml at the root of your git repository or to say it differently if you have a pom.xml anywhere else than the root directory you can't release the project. (of course submodule of root located pom.xml do not count)... It's also common practice in the maven world to have a parent pom to share common settings. If I follow blindlessly the 1 project -> 1 git repository, it means I have to setup a git repository for a single parent pom ? I have the feeling, but I maybe wrong, that this is more a limitation of the release plugin / scm provider more than a design goal. Those who migrated to git, what do you do for the above cases, especially the parent pom one ? Jean-Laurent On Mon, Apr 26, 2010 at 5:37 PM, Justin Edelson wrote: > OK. Then we're on the same page... > > On 4/26/10 11:32 AM, Kathryn Huxtable wrote: > > Perhaps I wasn't clear. I don't support multiple projects in one > repository. Definitely not. I was trying to criticize the svn-centric > thinking, not support it. > > > > I think there should be a JIRA issue to make modules work, given that > they'll be in separate repositories. > > > > I'm not going to file this because I have almost zero experience with > nested projects. There have been places it would have made sense and I shied > away. > > > > But the release plugin should work with git projects that have modules > and it should do it in the standard git manner, which is one repository > containing one project. (Distributed, of course.) > > > > -K > > > > On Apr 26, 2010, at 9:06 AM, Justin Edelson wrote: > > > >> Kathryn- > >> Maybe I'm misunderstanding what you mean, but I think you have this > >> exactly backwards. The "svn-centric thinking" is what's inspired someone > >> to put multiple projects in the same repository. AFAIK, this is simply > >> not supported by git, i.e. there's no way to clone, branch or tag _part_ > >> of a repository. > >> > >> I am by no means a git expert, so I could be mistaken about this. > >> > >> Justin > >> > >> > >> > >> On 4/26/10 9:21 AM, Kathryn Huxtable wrote: > >>> Having recently switched from svn to git for most of my projects, I > have an opinion. > >>> > >>> I think you should create a JIRA ticket and consider this a bug. > >>> > >>> What we're dealing with here is a bit of svn-centric thinking during > design. It needs to be fixed. > >>> > >>> -K > >>> > >>> On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote: > >>> > >>>> We're considering migrating from svn to git, we stumble on the > >>>> maven-release-plugin usage with git. > >>>> We think we prefer to use a single repository for many independently > built > >>>> projects like : > >>>> > >>>> foobar-repo.git > >>>> |-> project-foo/ > >>>> ||-> pom.xml > >>>> ||–> module A/ > >>>> ||-> module B/ > >>>> | > >>>> |-> project-bar/ > >>>> |-> pom.xml > >>>> > >>>> > >>>> project-bar scm url looks like : > >>>> scm:git:ssh://somehost.nowhere:/foobar-repo.git > > >>>> > >>>> This hints to the right repository but I can't write that the actual > >>>> project-bar is in the project-bar subdirectory. > >>>> > >>>> mvn release:prepare goes well and ends succesfully. > >>>> > >>>> mvn release:perform fails whenever it tries to build the project from > the > >>>> tag. It effectively clone correctly the repository. > >>>> But use the root of the repository rather than going into project-bar > >>>> subdirectory whenever it tries to clean deploy the tag. > >>>> > >>>> This prevent using git and multiple projects in the same directory. > >>>> Some may think we should use gitmodules but > >>>> 1) the release plugin does not support it [1] > >>>> 2) gitmodules is an aggregate of single repository > >>>> > >
Release plugin & git repo with multiple projects
We're considering migrating from svn to git, we stumble on the maven-release-plugin usage with git. We think we prefer to use a single repository for many independently built projects like : foobar-repo.git |-> project-foo/ ||-> pom.xml ||–> module A/ ||-> module B/ | |-> project-bar/ |-> pom.xml project-bar scm url looks like : scm:git:ssh://somehost.nowhere:/foobar-repo.git This hints to the right repository but I can't write that the actual project-bar is in the project-bar subdirectory. mvn release:prepare goes well and ends succesfully. mvn release:perform fails whenever it tries to build the project from the tag. It effectively clone correctly the repository. But use the root of the repository rather than going into project-bar subdirectory whenever it tries to clean deploy the tag. This prevent using git and multiple projects in the same directory. Some may think we should use gitmodules but 1) the release plugin does not support it [1] 2) gitmodules is an aggregate of single repository Should I issue a "new feature" ticket into jira project MRELEASE or SCM ? Or should I fall back to the current convention of 1 project = 1 git repository ?? Or maybe someone managed to do it ? any advice appreciated. [1] : http://jira.codehaus.org/browse/SCM-530
[ANN] Maven2 javancss plugin 2.0
The Mojo team is pleased to announce the javancss-maven-plugin 2.0 release !
http://mojo.codehaus.org/javancss-maven-plugin/
This plugin allows user to:
- Compute complexity (CCN) and quantity (NCSS) metrics on your code
- Create a report displaying those number.
Here's the release note :
Release Notes - Maven 2.x JavaNCSS Plugin - Version 2.0
** Bug
* [MJNCSS-11] - JavaNCSS report crashes if code contains some variable
called "enum"
* [MJNCSS-15] - UTF-8 Support
* [MJNCSS-16] - java annotations (within a method) cannot be parsed
correctly
* [MJNCSS-33] - Error parsing generics
* [MJNCSS-34] - NCSS crashes for class field declarations starting with
@Annotation
** Improvement
* [MJNCSS-13] - Typo in javancss:report parameters documentation
(includes)
* [MJNCSS-14] - Typo in includes/excludes example page
* [MJNCSS-27] - Do not let the check goal fail the build for projects
with no source
* [MJNCSS-28] - Integrate JavaNCSS Version 29.50
* [MJNCSS-36] - add an IT to automatically check if plugin is working
properly in a full site generation
* [MJNCSS-38] - Integrate JavaNCSS version 32.53
** New Feature
* [MJNCSS-31] - add an "encoding" parameter for source files and use
${project.build.sourceEncoding} as default value
** Wish
* [MJNCSS-32] - show the default javancss version used by the plugin in
its documentation introduction
* [MJNCSS-37] - add JavaNCSS version used in plugin's reports
Enjoy!
-The Mojo team
Re: [M2] Wagon FTP doesn't work in 2.0.5
AFAIK it's already in JIRA : http://jira.codehaus.org/browse/WAGONFTP-10 On 2/20/07, Siegmann Daniel, NY <[EMAIL PROTECTED]> wrote: <> <<> Can't even get my grammar right. :( ~Daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven2 javancss plugin 2.0-beta-2
The Mojo team is pleased to announce the javancss-maven-plugin 2.0-beta-2 release! http://mojo.codehaus.org/javancss-maven-plugin/ This plugin allows user to: - Compute complexity (CCN) and quantity (NCSS) metrics on your code - Create a report displaying those number. Here's the release note : Release Notes - Maven 2.x JavaNCSS Plugin - Version 2.0-beta-2 ** Bug * [MJNCSS-8] - NullPointerException when report are generated on ... Windows * [MJNCSS-10] - Plugin crashes when Java elements have special characters ** Improvement * [MJNCSS-2] - javancss-maven-plugin JXR integration * [MJNCSS-3] - exclude directory * [MJNCSS-4] - JavaNCSS may not fully support 1.5 annotations * [MJNCSS-5] - Drop Function and replace by Method where applicable in reports * [MJNCSS-6] - Make plugin documenation standard with docck. ** New Feature * [MJNCSS-1] - Create javancss:check mojo Enjoy! -The Mojo team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven2 javancss plugin 2.0-beta-1
It will be in the future. don't ask me when I have no ETA. In the meantime you can add to your pom : codehaus Codehaus maven repository http://repository.codehaus.org/ which will allow to retrieve all the latest mojo snaphsots. Keep in mind this is temporary. On 6/22/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote: Any chance that it will be synced to the central repo too? jean-laurent de morlhon wrote: > As stated at the end of the announcement email the repository where > this plugin is located is : > > repository.codehaus.org. > > You'll have to add this repository to your settings/project for now. > (Parent pom is over there too) > > On 6/22/06, Roald Bankras <[EMAIL PROTECTED]> wrote: >> Sounds very attractive, but through which repository is it available? >> BTW the source complains that it cannot find the parent pom. >> >> Roald Bankras >> Software Engineer >> JTeam b.v. >> >> -Original Message- >> From: jean-laurent de morlhon [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, June 21, 2006 5:08 PM >> To: Maven Users List; user@mojo.codehaus.org >> Subject: [ANN] Maven2 javancss plugin 2.0-beta-1 >> >> The Mojo team is pleased to announce the javancss-maven-plugin >> 2.0-beta-1 release! >> >> http://mojo.codehaus.org/javancss-maven-plugin/ >> >> This plugin allows user to: >> >> - Compute complexity (CCN) and quantity (NCSS) metrics on your code >> - Create a report displaying those numbers >> >> This plugin is currently available at repository.codehaus.org. >> >> Enjoy! >> >> -The Mojo team >> >> -- >> Jean-Laurent >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> -- >> No virus found in this incoming message. >> Checked by AVG Free Edition. >> Version: 7.1.394 / Virus Database: 268.9.2/370 - Release Date: 6/20/2006 >> >> >> -- >> No virus found in this outgoing message. >> Checked by AVG Free Edition. >> Version: 7.1.394 / Virus Database: 268.9.2/372 - Release Date: 6/21/2006 >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven2 javancss plugin 2.0-beta-1
As stated at the end of the announcement email the repository where this plugin is located is : repository.codehaus.org. You'll have to add this repository to your settings/project for now. (Parent pom is over there too) On 6/22/06, Roald Bankras <[EMAIL PROTECTED]> wrote: Sounds very attractive, but through which repository is it available? BTW the source complains that it cannot find the parent pom. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: jean-laurent de morlhon [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 21, 2006 5:08 PM To: Maven Users List; user@mojo.codehaus.org Subject: [ANN] Maven2 javancss plugin 2.0-beta-1 The Mojo team is pleased to announce the javancss-maven-plugin 2.0-beta-1 release! http://mojo.codehaus.org/javancss-maven-plugin/ This plugin allows user to: - Compute complexity (CCN) and quantity (NCSS) metrics on your code - Create a report displaying those numbers This plugin is currently available at repository.codehaus.org. Enjoy! -The Mojo team -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.2/370 - Release Date: 6/20/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.2/372 - Release Date: 6/21/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven2 javancss plugin 2.0-beta-1
The Mojo team is pleased to announce the javancss-maven-plugin 2.0-beta-1 release! http://mojo.codehaus.org/javancss-maven-plugin/ This plugin allows user to: - Compute complexity (CCN) and quantity (NCSS) metrics on your code - Create a report displaying those numbers This plugin is currently available at repository.codehaus.org. Enjoy! -The Mojo team -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Mojo Exec plugin 1.0.1
Doesn't seem to be synced, I dunno if this is expected or not. Compare http://www.ibiblio.org/maven2/org/codehaus/mojo/mojo/ with http://repository.codehaus.org/org/codehaus/mojo/mojo/ Ibiblio contains mojo parent pom version 1 to 7 and codehaus 8 to 9. Sames goes for plugins... Can somebody tell us if this is expected ? I assume if this is the case people have to add repository.codehaus.org has supplementary repository... On 6/20/06, jerome lacoste <[EMAIL PROTECTED]> wrote: On 6/20/06, dan tran <[EMAIL PROTECTED]> wrote: > Does The released plugin sync to http://www.ibiblio.org/maven? Plugin is deployed to repository.codehaus.org. Hope that one is sync'ed to ibiblio but not 100% sure. Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Stand-alone app
Erik, If I understand what you want to do clearly, you can do everything without writing a plugin. Just use the maven-jar-plugin and maven-assembly-plugin. The following is extracted from a standalone application I built with m2 a few month ago (assembly plugin as slightly changed since then and spurts some deprecation but it works fine) First make a executable jar and putting all dependencies into the manifest is done this way : maven-jar-plugin com.foo.bar.ClassHoldingAMainMethod true true ./lib/ Note that classpathPrefix is ./lib, of course you can use whatever you want. call the assembly plugin (plugin is not bound to any phase you can do it if you want) maven-assembly-plugin assembly.xml put in the assembly.xml the following : distribution zip readme.txt target *.jar /lib false runtime then call mvn assembly:directory. you'll find in the target directory the resulting jar and in the lib directory all the dependencies. No plugin code, all is proper declaration. hope it helps. On 5/31/06, Lee Meador <[EMAIL PROTECTED]> wrote: What I do is build the executable jar. It takes two options to the jar plugin to put the dependent jar references in the manifest and to put ./lib on the front of each reference. Then I have an assembly that puts that jar and its dependency jars all together in a zip or tar.gz that will extract into place to run. There are some properties files too. The assembly xml file is 40 lines. Most of them just define what goes inside. The rest has mostly to do with filtering the resouces for different deployment environments. The pom has a few lines to tell it to do the assembly as part of a full build. If I didn't do the properties files the way I do it would all run just fine with 'java -jar ...". As is, I run from the command line without change after extracting from the zip or tar.gz. I'm probably missing something but there isn't that much to configure and any plugin would need the information about what to put in the jar, what to filter and so forth. On 5/31/06, Midtskogen, Erik <[EMAIL PROTECTED]> wrote: > > OK, so it seems that it's not possible to manage the build of a > stand-alone, desktop application entirely in Maven without resorting to > one or more hacks or manual processes. I find it rather odd that the > most basic of all use-cases usually fulfilled by software build systems > is not yet supported by Maven. But I'm willing to try my hand at > writing a plugin or goal to fulfill this need and give something back to > the Maven community. > > Just to recap my earlier inquiry, what I'm looking for is a goal whose > resulting artifact is an executable jar file along with all the > dependencies it needs in order to run. The goal would automatically > make the appropriate entries into the artifact jar's manifest.mf for the > main class and the jar file dependencies. Then, it would copy the > dependency jar files themselves from the repository to the locations > specified in the manifest.mf. > > Would anybody else here have a need for such a goal, or am I the only > one using Maven to build stand-alone Java apps? If other people would > find such a goal useful, should I try to write it as a goal of the > assembly plugin, with the idea that I could submit it to a committer and > have it become a goal called, for example, assembly:stand-alone-app? > > Any feedback or tips would be great--especially from someone who has > written a Maven goal before. > > Thanks, > --Erik > > > *** > The information in this email (including any attachments) is confidential > and may be legally privileged. Access to this e-mail by anyone other than > the intended addressee is unauthorized. If you are not the intended > recipient of this message, any review, disclosure, copying, distribution, > retention, or any action taken or omitted to be taken in reliance on it > (including any attachments) is prohibited and may be unlawful. If you are > not the intended recipient, please reply to or forward a copy of this > message to the sender and delete the message, all attachments, and any > copies thereof from your system and destroy any printout thereof. > > __ > The information in this email (including any attachments) is confidential > and may be legally privileged. Access to this e-mail by anyone other than > the intended addressee is unauthorized. If you are not the intended > recipient of this message, any review, disclosure, copying, distribution, > retention,
Re: [M2] Newbie q: Looking for clear example on creating Ant Plugin/M ojo's
Your xxx.build.xml / xxx.mojos.xml should be placed by default into the src/main/scripts directory of your plugin. I didn't hjave a chance to take a look at this chapter of the book, but there is a rather comprehensive documentation here : http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html On 4/26/06, Dave Comeau <[EMAIL PROTECTED]> wrote: > > I'm new to Maven and trying to port our current Ant build system to M2. > > So I'm trying to take the route of creating separate plugins for the various > Ant tasks that we currently perform, such as obfuscation. > > I've been thrashing through lots of documentation, and finally discovered > the "Better Builds With Maven" book. I've been trying to model my own > simple plugin (with an Ant Mojo) after the examples in chapter 5, > "Developing Custom Maven Plugins". However, unlike the example in the book, > I'm not mixing Java and Ant Mojo's, I just have an Ant Mojo. > > Unfortunately I find the guide a bit vague in terms of how and where the > xxx.build.xml / xxx.mojos.xml (in my case I have obfuscate.build.xml and > obfuscate.mojos.xml) files live in the project's directory structure. > > When I build and install the plugin to my repository, the Jar file doesn't > contain the obfuscate.build.xml or obfuscate.mojos.xml files. > > So when I then build my project that has this plugin bound to the lifecycle > (in the process-classes phase), I get the error below. What I'm interested > in is finding some documentation that shows a more specific example of an > Ant plugin. > > Also, I'm surprised that there is no Ant plugin archetype available that can > be used with the "archetype:create" plugin goal. I used > "-DarchetypeArtifactId=maven-archetype-mojo" to setup this project, but it's > specific to Java Mojo's. Aren't Ant based plugins quite common? > > Thank you for your assistance. > Dave > > [ERROR] BUILD ERROR > [INFO] > > [INFO] 'obfuscate' was specified in an execution, but not found in the > plugin > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: 'obfuscate' was > specified in an execution, but not found in the plugin > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindExecutionToLifecycle > (DefaultLifecycleExecutor.java:1337) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(De > faultLifecycleExecutor.java:1238) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappin > gs(DefaultLifecycleExecutor.java:982) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec > ycleExecutor.java:453) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail > ures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa > ultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle > Executor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 > ) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl > .java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > [INFO] > > > > > > -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE : [m202] Custom built plugin
I've got the exact same problem. It's only happening with cobertura. As I have compiled other plugins which aren't affected by the problem. Can't find anything (tried playing with the various meta-data without any success) Anyone as found a viable solution, besides copying locally the plugin ? On 3/21/06, Arnaud Bailly <[EMAIL PROTECTED]> wrote: > I have got the same problem when I remove I think this is an issue with the metadata files but I don't know how to > handle it. > > > -- > Arnaud Bailly, Dr. - Ing�nieur de Recherche > NORSYS > 1, rue de la Cense des Raines > ZAC du Moulin > 59710 ENNEVELIN > Tel : (33) 3 28 76 56 76 > Mob : (33) 6 17 12 19 78 > Fax : (33) 3 28 76 57 00 > Web : http://www.norsys.fr > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Jean-Laurent
Re: [M2] Deploying jar with classifier fails...
I'm sure to have acces to the repository, since I deploy other artifacts there. Btw on this specific project removing the line of the maven-jar-plugin configuration, "tranforming" the target artifact to a classifier-less artifact, and calling mvn deploy works like a charm... I'll file a Jira issue within the day. On 3/6/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > You need to run mvn with -X and paste the output. > Accès refusé looks like you don't have permissions in the remote server > > On 3/1/06, jean-laurent de morlhon <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > In order to produce a single artifact with a classifier, I configured > > the jar plugin as follow in my pom. > > > > > > org.apache.maven.plugins > > maven-jar-plugin > > > > someclassifier > > > > > > > > however anytime I try do deploy (mvn deploy) it fails with : > > > > [ERROR] BUILD ERROR > > [INFO] > > > > [INFO] Error deploying artifact: > > c:\dev\ci-branch\presentation\vpm-core\target\c > > lasses (Accès refusé) > > > > Note that installation (mvn install) works like a charm. > > This is strangely similar to > > http://jira.codehaus.org/browse/MINSTALL-3 altough it's not for same > > lifecycle step ( install != deploy ). > > > > I'm using maven 2.0.2 and the deploy plugin is 2.2. > > > > What did I do wrong ? > > > > > > > > ps: I even just tried to do it with a sample project generated with > > mvn archetype:create with the exact same results as above. I can make > > available a test project if needed. > > -- > > Jean-Laurent > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > I could give you my word as a Spaniard. > No good. I've known too many Spaniards. > -- The Princess Bride > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Deploying jar with classifier fails...
Hi all, In order to produce a single artifact with a classifier, I configured the jar plugin as follow in my pom. org.apache.maven.plugins maven-jar-plugin someclassifier however anytime I try do deploy (mvn deploy) it fails with : [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: c:\dev\ci-branch\presentation\vpm-core\target\c lasses (Accès refusé) Note that installation (mvn install) works like a charm. This is strangely similar to http://jira.codehaus.org/browse/MINSTALL-3 altough it's not for same lifecycle step ( install != deploy ). I'm using maven 2.0.2 and the deploy plugin is 2.2. What did I do wrong ? ps: I even just tried to do it with a sample project generated with mvn archetype:create with the exact same results as above. I can make available a test project if needed. -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin for class line count?
I did the maven2 plugin port and I can confirm that javancss does not support java 1.5 syntax, the program itself (not the plugin) has not been updated since september 2002 :( I was looking for a way to get the source configuration parameter of the maven-compiler-plugin to skip the javancss analysis in the case the code is 1.5+. But I've read somewhere that looking at other plugin parameter is discouraged Should be in jira anyhow... On 2/10/06, Brett Porter <[EMAIL PROTECTED]> wrote: > Sorry, I don't know. I wouldn't be surprised if JavaNCSS doesn't > support it - I don't think it has been updated for some time. > > - Brett > > On 2/11/06, Brian Burridge <[EMAIL PROTECTED]> wrote: > > Thanks. Checked it out, built it and installed it. However, it is > > complaining about Java 1.5 syntax in my code. Is there a way to tell it that > > its 1.5, or does it not support that yet? > > > > Brian > > > > On 2/10/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > mojo.codehaus.org, in the sandbox. > > > > > > On 2/11/06, Brian Burridge <[EMAIL PROTECTED]> wrote: > > > > bingo! That was it. Doesn't look like its been ported to Maven 2 though. > > > > > > > > Brian > > > > > > > > On 2/10/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > > > > > > > > > it was javancss plugin, i think > > > > > > > > > > Brian Burridge a écrit : > > > > > > Over a year ago, when I used Maven on the project I was on at that > > > time, > > > > > I > > > > > > found a Maven plugin that gave a line count (also gave class and > > > package > > > > > > count). It was a very simple one, and I liked it because the IBM > > > project > > > > > I > > > > > > was on required line counts to be reported regularly (don't ask me > > > why). > > > > > > > > > > > > Now that I am setting up Maven for my current project, I'd like to > > > > > through > > > > > > that plugin/report in, but I can't find it anywhere. Anyone remember > > > it? > > > > > > > > > > > > Brian > > > > > > > > > > > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Doxia & color
I thought Doxia was some kind of abstraction layer enabling to create report for other things than html (like pdf or anything else). But, fair enough for css then. On 1/15/06, Brett Porter <[EMAIL PROTECTED]> wrote: > Color should ideally be done by CSS. > > Is there some reason we'd need this for other sinks that don't support CSS? > > - Brett > > On 1/13/06, jean-laurent de morlhon <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Is there a way using doxia to write a portion of text in color ? > > I mean something around this : > > > > sink.color( RED ); > > sink.text( "SomeTextToPutInColor" ); > > sink.color_(); > > > > The above does not exist, but I can't find a way to do it. Is it even > > possible today ? > > > > I just want to put in red an error-like within the javancss plugin for > > maven2 and don't know how to do it, just to say it's not to do fancy > > things. > > > > thx in advance > > -- > > Jean-Laurent > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Doxia & color
Hi, Is there a way using doxia to write a portion of text in color ? I mean something around this : sink.color( RED ); sink.text( "SomeTextToPutInColor" ); sink.color_(); The above does not exist, but I can't find a way to do it. Is it even possible today ? I just want to put in red an error-like within the javancss plugin for maven2 and don't know how to do it, just to say it's not to do fancy things. thx in advance -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
