Re: I18N
Hi Dirk, thank you for your response. I think you are referring to Maven 1.x documentation. Have a look at http://maven.apache.org/guides/mini/guide-site.html, it has an Internationalization section at the end which describes how to setup a multi-language site. Okay, with the described method it is easy to let the languages evolve independently. But I can only translate a few sites (from English to German), because it is a one man project. So I want to have a 'fall-back' method, which will show the English sites if no translation is available. How would you do this? 2. How I can avoid that maven tries to download the following pom http://repo1.maven.org/maven2/com/incors/plaf/kunststoff/2.0.2/kunststoff-2.0.2.pom Find the artifact that pulls in kunststoff (mvn dependency:tree) and have that pom fixed. This gives me: com.incors.plaf:kunststoff:jar:2.0.2 How should I fix this? Isn't this (a missing pom) an issue of the repository? Regards, Peter. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I18N
On 7/28/08, Peter Karich [EMAIL PROTECTED] wrote: Hi Dirk, thank you for your response. I think you are referring to Maven 1.x documentation. Have a look at http://maven.apache.org/guides/mini/guide-site.html, it has an Internationalization section at the end which describes how to setup a multi-language site. Okay, with the described method it is easy to let the languages evolve independently. But I can only translate a few sites (from English to German), because it is a one man project. So I want to have a 'fall-back' method, which will show the English sites if no translation is available. How would you do this? 2. How I can avoid that maven tries to download the following pom http://repo1.maven.org/maven2/com/incors/plaf/kunststoff/2.0.2/kunststoff-2.0.2.pom Find the artifact that pulls in kunststoff (mvn dependency:tree) and have that pom fixed. This gives me: com.incors.plaf:kunststoff:jar:2.0.2 Did you install manually this JAR in your local repository ? If this is true, then you must specify an option that creates also a POM for your JAR in the local repository. Regards Jeff MAURY How should I fix this? Isn't this (a missing pom) an issue of the repository? Regards, Peter. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.lastfm.fr/listen/user/jeffmaury/personal
Re: surefire doesn't detect failed tests. (forkMode = always and jdk1.4)
I have sometimes experienced this when a test did System.exit(), thus shutting down the Surefire JVM. Stefan Benoit Decherf wrote: Hi When I execute mvn deploy (from continuum), The surefire reports show that there are errors, but the execution doesn't fail : In the output I have: Results : Failed tests: Tests in error: Tests run: 212, Failures: 24, Errors: 8, Skipped: 0 [INFO] [jar:jar] That's strange. It show that some tests fails, but it doesn't show which tests fails and it doesn't fails the execution. The exact command is : mvn clean deploy -e --batch-mode The configuration to reproduce it is forkMode=always and jdk1.4. If I use jdk1.6, it works and if I use forkMode=once it also works. (but the list of failed tests is still missing). Can I open a bug in this ? Benoit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How can I know where part of my project has error?
Good morning, If you are using Eclipse IDE use the problems view to figure out what's wrong (Window--show view -- problems) this might happened because you have added some libraries or classes to your build path and those libraries\classes don't exist or they have problems - Original Message - From: youhaodeyi [EMAIL PROTECTED] To: users@maven.apache.org Sent: Sunday, July 27, 2008 4:46:34 AM GMT +03:00 Kuwait / Riyadh Subject: How can I know where part of my project has error? In my maven project, the icon of the project begin with a red fork which means this project has an error. But unfold this project, there is no error in any source code and configuration file. In addition, this project doesn't have any sub-module. So how can I get the error detail information? -- View this message in context: http://www.nabble.com/How-can-I-know-where-part-of-my-project-has-error--tp18672546p18672546.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Best Regards, Eman Ali al-Maktari Project Manager Technical Department LinkInTime Get Mobile ))) www.linkintime.com Mobile :: (00967) 71 2000 834 Office :: (00967) 1 427 377 Fax :: (00967) 1 428 851 LinkInTime Ltd. Iran Street Haddah - Sana'a - P.O.Box. 16871, YEMEN
Re: [m2] how to specify a tomcat context with the cargo plugin to run in maven?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mick Knutson a écrit :
| So is this going to startup my local tomcat, verse embedded tomcat for
| testing? Then the local tomcat just needs to be configured with my proper
| context.xml...???
Yes it works for me like this.
Marc.
| ---
| Thank You…
|
| Mick Knutson
| BASE Logic, inc.
| (415) 354-4215
|
| Website: http://baselogic.com
| Blog: http://baselogic.com/blog
| BLiNC Magazine: http://blincmagazine.com
| Linked IN: http://linkedin.com/in/mickknutson
| DJ Mick: http://djmick.com
| MySpace: http://myspace.com/mickknutson
| Vacation Rental: http://tahoe.baselogic.com
|
|
| On Fri, Jul 25, 2008 at 9:04 AM, Marc Schneider
[EMAIL PROTECTED]
| wrote:
|
| Mick Knutson a écrit :
|
| I want to specify a test version of my tomcat context with my cargo
| plugin,
| but can't seem to find anything about that on the site. Is this
possible?
|
| ---
| Thank You…
|
| Mick Knutson
| BASE Logic, inc.
| (415) 354-4215
|
| Website: http://baselogic.com
| Blog: http://baselogic.com/blog
| BLiNC Magazine: http://blincmagazine.com
| Linked IN: http://linkedin.com/in/mickknutson
| DJ Mick: http://djmick.com
| MySpace: http://myspace.com/mickknutson
| Vacation Rental: http://tahoe.baselogic.com
|
|
| May be you can try it like this :
| (For me it also works for Tomcat 6x)
|
| plugin
| groupIdorg.codehaus.cargo/groupId
| artifactIdcargo-maven2-plugin/artifactId
| configuration
|waitfalse/wait
|container
| containerIdtomcat5x/containerId
| home${tomcat.local.home}/home
|/container
|configuration
| properties
|cargo.logginghigh/cargo.logging
|cargo.servlet.port${servlet.port}/cargo.servlet.port
| /properties
|/configuration
| /configuration
| executions
|execution
| idstart-container/id
| phasepre-integration-test/phase
| goals
|goalstart/goal
| /goals
|/execution
|execution
| idstop-container/id
| phasepost-integration-test/phase
| goals
|goalstop/goal
| /goals
|/execution
| /executions
| /plugin
|
| Marc.
|
| -
| To unsubscribe, e-mail: [EMAIL PROTECTED]
| For additional commands, e-mail: [EMAIL PROTECTED]
|
|
|
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIjYtDOnFbH6/W/e8RAuSbAJ97HHej5t1ULDR+UGfKfC/AZ2jMPQCeM+dF
ChdukypIBCPXLXrs2CNmIMY=
=lfaN
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: surefire doesn't detect failed tests. (forkMode = always and jdk1.4)
We don't have any System.exit() in the code. And as I told you, this bug only appear with forkMode=always and jdk1.4. Benoit Stefan Seidel wrote: I have sometimes experienced this when a test did System.exit(), thus shutting down the Surefire JVM. Stefan Benoit Decherf wrote: Hi When I execute mvn deploy (from continuum), The surefire reports show that there are errors, but the execution doesn't fail : In the output I have: Results : Failed tests: Tests in error: Tests run: 212, Failures: 24, Errors: 8, Skipped: 0 [INFO] [jar:jar] That's strange. It show that some tests fails, but it doesn't show which tests fails and it doesn't fails the execution. The exact command is : mvn clean deploy -e --batch-mode The configuration to reproduce it is forkMode=always and jdk1.4. If I use jdk1.6, it works and if I use forkMode=once it also works. (but the list of failed tests is still missing). Can I open a bug in this ? Benoit - 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]
Is there any way to pass JVM arguments to a process other than MAVEN_OPTS
other than using MAVEN_OPTS.
I'm looking to pass a configuration file, for example
-Dcxf.config.file=${basedir}/CherryServer.cxf
I've tried below but this doesn't work..
profile
idserver/id
build
defaultGoaltest/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
executions
execution
phasetest/phase
goals
goalexec/goal
/goals
configuration
executablejava/executable
arguments
argument-classpath/argument
classpath/
argument-Dcxf.config.file=${basedir}/CherryServer.cxf/argument
argumentdemo.hw_https.server.Server/argument
/arguments
/configuration
/execution
/executions
/plugin
/plugins
/build
/profile
--
View this message in context:
http://www.nabble.com/Is-there-any-way-to-pass-JVM-arguments-to-a-process-other-than-MAVEN_OPTS-tp18687327p18687327.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is there any way to pass JVM arguments to a process other than MAVEN_OPTS
Maybe you can try using systemPorperties as describe here :
http://mojo.codehaus.org/exec-maven-plugin/usage.html
Exemple :
project
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
version1.1-beta-2/version
executions
execution
goals
goaljava/goal
/goals
/execution
/executions
configuration
mainClasscom.example.Main/mainClass
arguments
argumentargument1/argument
/arguments
systemProperties
systemProperty
keymyproperty/key
valuemyvalue/value
/systemProperty
/systemProperties
/configuration
/plugin
/plugins
/build
/project
--
Xebia IT Architects
FR : http://blog.xebia.fr
EN : http://blog.xebia.com
On Mon, Jul 28, 2008 at 12:04 PM, seanoc [EMAIL PROTECTED] wrote:
other than using MAVEN_OPTS.
I'm looking to pass a configuration file, for example
-Dcxf.config.file=${basedir}/CherryServer.cxf
I've tried below but this doesn't work..
profile
idserver/id
build
defaultGoaltest/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
executions
execution
phasetest/phase
goals
goalexec/goal
/goals
configuration
executablejava/executable
arguments
argument-classpath/argument
classpath/
argument-Dcxf.config.file=${basedir}/CherryServer.cxf/argument
argumentdemo.hw_https.server.Server/argument
/arguments
/configuration
/execution
/executions
/plugin
/plugins
/build
/profile
--
View this message in context:
http://www.nabble.com/Is-there-any-way-to-pass-JVM-arguments-to-a-process-other-than-MAVEN_OPTS-tp18687327p18687327.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Where is the default reports reference?
I'm wanting to edit the menu in my site for the Project Documentation, which is produced by the site.xml line menu ref=reports/ In particular, I want it not to be collapsable. An easy way to do that would be great, but I'm wondering where that information comes from. Surely it's not code... -K - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Why can't site links and breadcrumbs use https?
Using the latest and greatest site plugin (2.0-beta-7) when I include the link https://wiki.internet2.edu/confluence/display/i2miCommon/Ldappc in my links or breabcrumbs, it comes out as file://localhost/Users/huxtable/dev/workspace/ldappc/target/Ldappc Internally, it says href=../Ldappc. Why? All my http links work... And by the way, using a simple http link goes to the top-level wiki page because of how Internet2's Confluence is set up. I have no control over this. Inquiring minds want to know, -K - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
changelog clearcase offline mode
Hi, how can I force changelog plugin to run in offline mode. I invoke mvn -o clean install site and there is no changelog reports. changelog must cooperate with clearcase, so scm is defined. I think that problem is offline mode. Is there a possibility to run changelog in offline mode ? Best regards, Jakub Sokolowski. -- View this message in context: http://www.nabble.com/changelog-clearcase-offline-mode-tp18688545p18688545.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Archetype:create broken?
dkernekins wrote: And now Celebrate... now to push it to shared repository (Artifactory) so the rest of my world works again. -- dke p.s. note that the POM says it should be org.apache.velocity:velocity:pom:1.5 but that I had to put it into my local repository as if it was velocity:velocity:pom:1.5 ... perhaps I should use a .pom with a distributionManagement relocation and put the .pom where it belongs? To get the fix uploaded into my artifcatory I had to edit the pom and change the groupId from 'org.apache.velocity' to 'velocity'. Then a added the pom to the jar as META-INF\maven\velocity\velocity\pom.xml. Then I uploaded the jar to artifcatory, and it all worked fine. If I didn't fix the groupId then artifactory would put it in the wrong place. David -- View this message in context: http://www.nabble.com/Archetype%3Acreate-broken--tp17503659p18688768.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why can't site links and breadcrumbs use https?
I knew when I posted this that I was making the assumption that the https was the problem. It's not, of course. The problem is that the url element in my pom is the wiki site. The documentation is actually going to be deployed to a different server. I think it's appropriate that the url is the wiki site rather than the documentation site because the wiki is the primary source for downloading the software and such. Anyway, I'm trying one of the workarounds suggested in JIRA MSITE-159. So go ahead and ignore my question. -K On Jul 28, 2008, at 6:35 AM, Kathryn Huxtable wrote: Using the latest and greatest site plugin (2.0-beta-7) when I include the link https://wiki.internet2.edu/confluence/display/i2miCommon/Ldappc in my links or breabcrumbs, it comes out as file://localhost/Users/huxtable/dev/workspace/ldappc/target/Ldappc Internally, it says href=../Ldappc. Why? All my http links work... And by the way, using a simple http link goes to the top-level wiki page because of how Internet2's Confluence is set up. I have no control over this. Inquiring minds want to know, -K - 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]
maven-dependency-plugin fails if pom.xml contains a submodule
Hi,
Using maven-dependency-plugin, I go a build error since I've add a
module in the pom.
Principle is to be able to manage two different calls : from execution,
libraries go in target/lib/ and from a command-line call (or Ant),
libraries go into ${jboss.lib}.
All worked fine until I added a module. Now, calls from command line
unless we specify the -N option.
The plugin configuration is not inside a pluginManagement tag, so it
shouldn't be inherited, does it ?
I got this error from the submodule, not from the module containing the
dependency plugin configuration:
[ERROR] BUILD ERROR
[INFO]
[INFO] One or more required plugin parameters are invalid/missing
for 'dependency:copy'
[0] Inside the definition for plugin 'maven-dependency-plugin'
specify the following:
configuration
...
artifactItemsVALUE/artifactItems
/configuration.
- using -N on the command line solve the problem
- help:effective-pom result (ran on the failing child) doesn't contain
any reference to dependency-plugin except this one in the pluginManagement:
plugin
artifactIdmaven-dependency-plugin/artifactId
version2.0/version
/plugin
- call from execution, during an mvn package for example succeed.
Here's my configuration :
modules
moduleaModule/module
/modules
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
configuration
outputDirectory${jboss.lib}/outputDirectory
artifactItems
artifactItem
groupIdaGroupId/groupId
artifactIdanArtifactId/artifactId
versionaVersion/version
overWritetrue/overWrite
/artifactItem
/artifactItems
/configuration
executions
execution
idcopy-installed/id
phasepackage/phase
goals
goalcopy/goal
/goals
configuration
outputDirectory${project.build.directory}/lib/outputDirectory
/configuration
/execution
/executions
plugin
/plugins
/build
Thanks,
Julien
--
Julien CARSIQUE, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
[EMAIL PROTECTED] | Tel: +33 1 40 33 79 87
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why can't site links and breadcrumbs use https?
Okay, the workaround is broken in Firefox and Camino, making it useless. Someone should address MSITE-159. There are several use cases mentioned in the comments as to why it should be changed to at least provide an option to not rewrite URLs. Arrrgh! -K On Jul 28, 2008, at 6:53 AM, Kathryn Huxtable wrote: I knew when I posted this that I was making the assumption that the https was the problem. It's not, of course. The problem is that the url element in my pom is the wiki site. The documentation is actually going to be deployed to a different server. I think it's appropriate that the url is the wiki site rather than the documentation site because the wiki is the primary source for downloading the software and such. Anyway, I'm trying one of the workarounds suggested in JIRA MSITE-159. So go ahead and ignore my question. -K On Jul 28, 2008, at 6:35 AM, Kathryn Huxtable wrote: Using the latest and greatest site plugin (2.0-beta-7) when I include the link https://wiki.internet2.edu/confluence/display/i2miCommon/Ldappc in my links or breabcrumbs, it comes out as file://localhost/Users/huxtable/dev/workspace/ldappc/target/Ldappc Internally, it says href=../Ldappc. Why? All my http links work... And by the way, using a simple http link goes to the top-level wiki page because of how Internet2's Confluence is set up. I have no control over this. Inquiring minds want to know, -K - 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]
Eclipse build problem
Hi, I'm trying to build Eclipse build with maven. In my case there is a library bundle which is just a package of some jars used by other plugins. The problem is that other plugins being build by maven depend on some of those jars and unfortunately I get compilation errors for all of that cases. This leads me to conclusion that such a case is not supported by maven. Is it so? As a workaround I'm creating separate bundle for each jar in use which is not nice. Regards, Stoil
Re: surefire doesn't detect failed tests. (forkMode = always and jdk1.4)
I can reproduce this using the quickstart archetype : just change the assertion (assertTrue( false ) to make UT fail) And execute: $ export JAVA_HOME=/usr/java/j2sdk1.4.2_18/ $ mvn package -DforkMode=always Surefire show that UT fails, but it continue with the build. Benoit Benoit Decherf wrote: We don't have any System.exit() in the code. And as I told you, this bug only appear with forkMode=always and jdk1.4. Benoit Stefan Seidel wrote: I have sometimes experienced this when a test did System.exit(), thus shutting down the Surefire JVM. Stefan Benoit Decherf wrote: Hi When I execute mvn deploy (from continuum), The surefire reports show that there are errors, but the execution doesn't fail : In the output I have: Results : Failed tests: Tests in error: Tests run: 212, Failures: 24, Errors: 8, Skipped: 0 [INFO] [jar:jar] That's strange. It show that some tests fails, but it doesn't show which tests fails and it doesn't fails the execution. The exact command is : mvn clean deploy -e --batch-mode The configuration to reproduce it is forkMode=always and jdk1.4. If I use jdk1.6, it works and if I use forkMode=once it also works. (but the list of failed tests is still missing). Can I open a bug in this ? Benoit - 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]
Are System dependencies working on maven 2.0.9
Hi,
I have seen the same question posted on the web but I still didn't see a
jira created for it.
Are System dependencies working on maven 2.0.9 ?
It works fine with maven 2.0.7 but cannot find the following jar with
maven 2.0.9 ?
e.g.
dependency
groupIdcom.google.gwt/groupId
artifactIdgwt-dev-windows/artifactId
version${gwt-version}/version
scopesystem/scope
systemPath${google.webtoolkit.home}/gwt-dev-windows.jar/systemPath
/dependency
Cheers, Edell.
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
Presentation at Agile2008
Hey all, I'll be giving a presentation at Agile2008 next week called: Maven and Continuum - an infrastructure for reducing cycle-time in Agile and Lean development. I wanted to drop the basic outline here and make sure there isn't anything that absolutely must be talked about. It's a tutorial, so it's going to involve the theory, but will also get into real examples of setting up projects, modules/ parents, plugins, and site reports. I'll mention Hudson/Cruise- control, and others, and Nexus and Archiva will also be mentioned, but I have doubts as to whether any of that will be covered. Anyway, let me know if there's anything off this list that strikes you as needing to be on it. It's a 3 hour tutorial, and when I timed this material, I found it quite hard to fit it in, especially with QA. Cheers, Christian. P.S. Please don't spam the users lists with replies - reply to me, unless there's a genuine topic in your comment. I'm looking for suggestions, not to put a lot of extra traffic onto these lists. Thanks. -cg. Introduction Discussion of build environments, and their effects on developer efficiency, quality, etc. Part 1 - Apache Maven2 Basic Introduction Dependency Management Modules and Recursive Builds Eclipse IDE integration QA Part 2 - Apache Maven2 Reports “Site” plugin Project Metadata Almost Plain Text Developer Reports Additional Documentation QA Break Part 3 - Apache Continuum 1.1 Introduction to Apache Continuum Basic Setup Adding projects Schedules and Build Definitions QA Part 4 - Advanced Topics non-java builds (native, .NET) integration test strategies maven ant tasks software release process More QA if desired - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Project Info Reports Plugin 2.1 Released
The Maven team is pleased to announce the release of the Maven Project Info Reports Plugin, version 2.1 This plugin generates standard reports for the specified project. http://maven.apache.org/plugins/maven-project-info-reports-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.1/version /plugin Release Notes - Maven 2.x Project Info Reports Plugin - Version 2.1 ** Sub-task * [MPIR-126] - Move PluginManagementRenderer in an inner class of PluginManagementReport ** Bug * [MPIR-48] - Internal html references are not generated in the team-list.html * [MPIR-49] - team-list.html is not correctly generated when table is to large * [MPIR-52] - Wrong text on scm page for svn protocol * [MPIR-53] - there is no info about project-info-reports:summary in documentation * [MPIR-57] - URLs only link if they are FQDNs * [MPIR-59] - Site generation exception for french language, error with simple quote in translation S'inscrire for mailing list * [MPIR-60] - Current head throws NPE when generating reports * [MPIR-65] - Direct report generation breaks on skin version even though it is specified * [MPIR-66] - When run standalone, project metadata is missing * [MPIR-70] - NullPointerException when generating Dependencies report * [MPIR-75] - Typing mistake in properties file * [MPIR-76] - Dependencies report is incorrect * [MPIR-79] - Add explicit resource bundle for English * [MPIR-81] - DependenciesRenderer logs Exception when it can't find the artifact being built!!! * [MPIR-84] - StringIndexOutOfBoundsException when ML archive dont finish with a / * [MPIR-89] - Bad spelling in Project Information = Overview = Dependencies * [MPIR-90] - Bad style in text Access from behind a firewall * [MPIR-91] - Bad spelling in text Access through a proxy * [MPIR-92] - Wrong encoding in german properties * [MPIR-96] - Switched link text and target in license report * [MPIR-98] - Team list does not contain anchors on user ids * [MPIR-99] - Strange warnings when generating Plugin Management report * [MPIR-104] - Regression in 2.1-SNAPSHOT: SVN is no more recognized * [MPIR-106] - Regression in 2.1-SNAPSHOT, the Project Dependencies and the Project Transitive Dependencies are the same * [MPIR-109] - Wrong description of in source repository overview * [MPIR-119] - Dependency Repository Locations in Dependency Report doesn't allow snapshot artifacts url from the snapshot repositories * [MPIR-122] - Brazilian Portuguese language bundle - encoding problems and improvements * [MPIR-123] - Hungarian language bundle - encoding problems and improvements * [MPIR-124] - License report is empty in offline * [MPIR-129] - Duplicate entries of the same artifact in Licenses section of Dependencies report * [MPIR-130] - No mark or link to SNAPSHOT artifacts in Dependency Repository Locations section of Dependencies report ** Improvement * [MPIR-28] - improve convergence report * [MPIR-46] - Sample reports are out of date * [MPIR-47] - Dependency Report does not show origin of transitive dependency * [MPIR-54] - Team list table improvement * [MPIR-56] - Refactor the dependencies report * [MPIR-58] - The sandbox component Jar has been renamed to JarAnalyzer * [MPIR-61] - [PATCH] Updated CI Systems * [MPIR-62] - [PATCH] Dependency File Details : set right justification for numeric columns * [MPIR-64] - Korean translation resource file * [MPIR-67] - Please update the german localization. * [MPIR-69] - add anchors for developers * [MPIR-72] - Upgrade to doxia 1.0-alpha-9 * [MPIR-82] - Clarify usage of outputDirectory parameter * [MPIR-87] - Show repositories an artifact is deployed to as a report * [MPIR-94] - Change optional label in dependencies site * [MPIR-108] - Add validation of SCM urls * [MPIR-110] - Update code due to deprecated classes in maven-dependency-tree:1.1 * [MPIR-111] - Make Classifier and Optional column in dependencies report optional in the renderer * [MPIR-112] - Dependency Listings is too big: replace it by toogle entries in the dependency tree * [MPIR-113] - Dependency Tree lists all dependencies: needs to reduce to dependencies used by the project * [MPIR-115] - Make the Sealed column optional in dependencies report * [MPIR-116] - Make the classifier column optional in dependencies management report * [MPIR-117] - Replaced the table caption in the CI report * [MPIR-118] - Equalize links to project web site for artifactId * [MPIR-125] - Create a plugin report ** New Feature * [MPIR-26] - Could the Dependencies report show the size of the jars/etc... * [MPIR-55] - Detailed Artifact Information
problem copy resources to target on linux
Dear Developers, I have a problem using maven. I tried to build a Web project with maven installed on linux environment, but fails. The problem is that the resource files(*.properties, *.xml, *.xsd, *.txt) are not copied in the target directory, and so they are not part of the output ear file. I also tried to build the same project in windows machine and here runs ok, the resources are where they have to be. I checked all the pom.xml files in the project I don't have nothing windows specific in the files. I don't know what can be the problem, I appreciate any idea to solve the problem. I don't know if it is a bug or only a maven and linux incompatibility. If I run the mvn –verison command I get the following output: Maven version: 2.0.9 Java version: 1.5.0 OS name: linux version: 2.6.9-22.elsmp arch: x86 Family: unix Thanks for any help. == Üdvözlettel/Best Regards/Cu Stima: L rincz Csaba. It Specialist. @mail: [EMAIL PROTECTED] mobRO: +40720024581 fixRo: +40365409639 Skype: lrcsabi. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
managing relocated dependencies which don't have relocation poms
If one of my dependencies didn't deploy relocation poms after changing an artifactId, what is the best way to manage a dependency tree which includes a mix of old and new? Example: The SWT project exists in two different locations: groupIdorg.eclipse.swt/groupId artifactIdorg.eclipse.swt/artifactId see [1] and groupIdorg.eclipse/groupId artifactIdswt/artifactId see [2] There are no relocation poms which create a relationship between org.eclipse.swt:org.eclipse.swt (old) and org.eclipse.swt:swt (new). Currently, I use org.eclipse.swt:swt and then apply exclusion filters to remove org.eclipse.swt:org.eclipse.swt dependencies (Method A). Another team has continued to use org.eclipse.swt:org.eclipse.swt by maintaining an internal repo which includes newer versions with the old artifactId (Method B). Which method is recommended? If the SWT team now deploys relocation poms, will that cause problems for those using Method B? [1] versions 3.2.0 and 3.2.1 @ http://repo1.maven.org/eclipse/ [2] versions 3.3.0-v3339b, 3.3.0-v3345b and 3.3.0-v3346 @ http://repo1.maven.org/eclipse/, versions 3.2.1-v3235e and 3.3.0-v3346 @ http://repo1.maven.org/maven2/
managing relocated dependencies which don't have relocation poms
If one of my dependencies didn't deploy relocation poms after changing an artifactId, what is the best way to manage a dependency tree which includes a mix of old and new? Example: The SWT project exists in two different locations: groupIdorg.eclipse.swt/groupId artifactIdorg.eclipse.swt/artifactId see [1] and groupIdorg.eclipse/groupId artifactIdswt/artifactId see [2] There are no relocation poms which create a relationship between org.eclipse.swt:org.eclipse.swt (old) and org.eclipse.swt:swt (new). Currently, I use org.eclipse.swt:swt and then apply exclusion filters to remove org.eclipse.swt:org.eclipse.swt dependencies (Method A). Another team has continued to use org.eclipse.swt:org.eclipse.swt by maintaining an internal repo which includes newer versions with the old artifactId (Method B). Which method is recommended? If the SWT team now deploys relocation poms, will that cause problems for those using Method B? [1] versions 3.2.0 and 3.2.1 @ http://repo1.maven.org/eclipse/ [2] versions 3.3.0-v3339b, 3.3.0-v3345b and 3.3.0-v3346 @ http://repo1.maven.org/eclipse/, versions 3.2.1-v3235e and 3.3.0-v3346 @ http://repo1.maven.org/maven2/
Maven and BIRT Report Generation Engine
Maven gurus: I'm still finding my way with Maven, and am trying to convert a project from Ant to maven2. The biggest blocker I've found is integration with BIRT. The application I'm converting uses BIRT extensively, but there's 1) no BIRT in the main maven2 repo; 2) BIRT has dozens of un-mavenized dependencies; and 3) the BIRT community seems to have never actually heard of Maven, or reproduceable builds in general. There is literally *nothing* I've been able to find out there demonstrating any *sane* way of using Maven to build an application using BIRT runtime as a dependency. I'm sure I'm not the first person to have needed to do this, but it sure starting to feel that way... grr.. Any kind soul want to touch this? Thanks! --Ian
Re: Using a Pleus component in a plugin
Thank you for the hint, I have changed my code so that it directly references the Archiver now. Now I get the output below output from the plugin. I think there might be an incompatibbility of the plugins. Perhaps someone could give me a hint how I could debug this? In general, if I want to use a component that has the Contextualize interface implemented...do I need to pass the Plexus context explicitly to that component or does the framework do this magically. Moreover, the documentation says that I *should* implement the Contextualize interface if I plan to use plexus components. Even if I do this, the contextualize method is never called ... A pointer at a good example would really be great. For the acute problem I have atteched My plugin code and the pom.xml. Thanks Andreas [INFO] [ESBPlugin:package] [INFO] Packaging ESB application: [INFO] Project : iocc-esb-flow-pubopflightp [INFO] Group : com.lhsystems.iocc [INFO] Version : 1.0-SNAPSHOT [INFO] Source : E:\LHSys\maven\snapshots\com.lhsystems.iocc\iocc-esb-flow-pubopflightp\1.0-SNAPSHOT\src\main\ESB [INFO] Build : E:\LHSys\maven\snapshots\com.lhsystems.iocc\iocc-esb-flow-pubopflightp\1.0-SNAPSHOT\target [INFO] XAR : xar [INFO] Creating archive : E:\LHSys\maven\snapshots\com.lhsystems.iocc\iocc-esb-flow-pubopflightp\1.0-SNAPSHOT\target\iocc-esb-flow-pubopflightp-1.0-SNAPSHOT.xar [FATAL ERROR] com.sonicsw.maven.plugins.MavenEsbPackage#execute() caused a linkage error (java.lang.IncompatibleClassChangeError) and may be out-of-date. Check the realms: [FATAL ERROR] Plugin realm = app0.child-container[com.sonicsw.maven.plugins:ESBPlugin] urls[0] = file:/C:/Documents and Settings/agies/.m2/repository/com/sonicsw/maven/plugins/ESBPlugin/1.0-SNAPSHOT/ESBPlugin-1.0-SNAPSHOT.jar urls[1] = file:/C:/Documents and Settings/agies/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.5/plexus-utils-1.5.5.jar urls[2] = file:/C:/Documents and Settings/agies/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar urls[3] = file:/C:/Documents and Settings/agies/.m2/repository/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.jar urls[4] = file:/C:/Documents and Settings/agies/.m2/repository/org/codehaus/plexus/plexus-classworlds/1.2-alpha-6/plexus-classworlds-1.2-alpha-6.jar urls[5] = file:/C:/Documents and Settings/agies/.m2/repository/org/codehaus/plexus/plexus-io/1.0-alpha-2/plexus-io-1.0-alpha-2.jar urls[6] = file:/C:/Documents and Settings/agies/.m2/repository/com/sonicsw/pso/utilities/MFUtils/1.0-SNAPSHOT/MFUtils-1.0-SNAPSHOT.jar urls[7] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/mgmt_client/7.6.0/mgmt_client-7.6.0.jar urls[8] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/sonic_mgmt_client/7.6.0/sonic_mgmt_client-7.6.0.jar urls[9] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/mgmt_config/7.6.0/mgmt_config-7.6.0.jar urls[10] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/sonic_Client/7.6.0/sonic_Client-7.6.0.jar urls[11] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/sonic_Crypto/7.6.0/sonic_Crypto-7.6.0.jar urls[12] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-esb/xq_config/7.6.0/xq_config-7.6.0.jar urls[13] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-esb/commons-logging/7.6.0/commons-logging-7.6.0.jar urls[14] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-esb/xq_core/7.6.0/xq_core-7.6.0.jar urls[15] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-esb/xbean/7.6.0/xbean-7.6.0.jar urls[16] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-esb/jsr173_api/7.6.0/jsr173_api-7.6.0.jar urls[17] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/xercesImpl/7.6.0/xercesImpl-7.6.0.jar urls[18] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/MFdirectory/7.6.0/MFdirectory-7.6.0.jar urls[19] = file:/C:/Documents and Settings/agies/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar urls[20] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/mfcontext/7.6.0/mfcontext-7.6.0.jar [FATAL ERROR] Container realm = plexus.core urls[0] = file:/c:/tools/maven2/lib/maven-2.0.9-uber.jar [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.IncompatibleClassChangeError at org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:324) at org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:249) at org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:762) at
Re: Maven and BIRT Report Generation Engine
Ian, We maven-ized our local/custom build of OpenReports, which has dependencies on BIRT. We created a separate pom project to manage the entire set of BIRT dependencies as a single unit and had to manually install most the dependencies into our repository manager. Note, we haven't used the BIRT features of OpenReports much so I can't say the versions are perfect. They do produce a successful compile/package of the OpenReports war, I just can't confirm the runtime behavior. Here's the pom with only a few minor company-specific elements removed... ?xml version=1.0 encoding=UTF-8? project modelVersion4.0.0/modelVersion groupIdYOUR GROUP ID HERE/groupId artifactIdeclipse-birt-bundle/artifactId nameEclipse BiRT Bundle/name version2.2.0-1-SNAPSHOT/version packagingpom/packaging dependencies !-- Most of these dependencies required manual installation into our repositories so we could match as closely as possible the version that were delivered with OpenReports 3.0.0. If/when the Eclipse projects artifacts are deployed publicly and consistently then we can update this bundle POM and track their versions. -- dependency groupIdorg.eclipse.birt/groupId artifactIdchartengine/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIdcore/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIddataadapter/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIdengine/artifactId version2.2/version exclusions exclusion groupIddom4j/groupId artifactIddom4j/artifactId /exclusion /exclusions /dependency dependency groupIdorg.eclipse.birt/groupId artifactIdmodel/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIdscript/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIddte/artifactId version2.2/version /dependency !-- EMF (Eclipse Modeling Framework ) -- dependency groupIdorg.eclipse.emf/groupId artifactIdecore/artifactId version2.2.2.v200702131851/version /dependency dependency groupIdorg.eclipse.emf/groupId artifactIdecore-xmi/artifactId version2.2.2.v200702131851/version /dependency dependency groupIdorg.eclipse.emf/groupId artifactIdcommon/artifactId version2.2.1.v200702131851/version /dependency !-- W3C -- dependency groupIdorg.w3c/groupId artifactIdflute/artifactId version1.2/version /dependency dependency groupIdorg.w3c/groupId artifactIdsac/artifactId version1.3/version /dependency !-- Commons -- dependency groupIdcommons-codec/groupId artifactIdcommons-codec/artifactId version1.3/version !-- removing unwanted transitive dependencies -- exclusions exclusion artifactIdjunit/artifactId groupIdjunit/groupId /exclusion /exclusions /dependency dependency groupIdcommons-cli/groupId artifactIdcommons-cli/artifactId version1.0/version !-- removing unwanted transitive dependencies -- exclusions exclusion artifactIdcommons-lang/artifactId groupIdcommons-lang/groupId /exclusion exclusion artifactIdcommons-logging/artifactId groupIdcommons-logging/groupId /exclusion /exclusions /dependency dependency groupIdcommons-discovery/groupId artifactIdcommons-discovery/artifactId version0.2/version /dependency !-- misc -- dependency groupIdcom.lowagie/groupId artifactIditext/artifactId version1.3/version /dependency dependency groupIdcom.ibm.icu/groupId artifactIdicu4j/artifactId version3.6.1/version /dependency dependency groupIdrhino/groupId artifactIdjs/artifactId version1.6R2/version /dependency /dependencies /project On Mon, Jul 28, 2008 at 10:24 AM, Ian Coleman [EMAIL PROTECTED] wrote: Maven gurus: I'm still finding my way with Maven, and am trying to convert a project from Ant to maven2. The biggest blocker I've found is integration with BIRT. The application I'm converting uses BIRT extensively, but there's 1) no BIRT in the main maven2 repo; 2) BIRT has dozens of un-mavenized dependencies; and 3) the BIRT community seems to have never actually heard of Maven, or reproduceable builds in general. There is literally *nothing* I've been able to find out there demonstrating any *sane* way of using Maven to build an application using BIRT runtime as a dependency. I'm sure I'm not
Re: Using a Pleus component in a plugin
If you use plexus-archiver you have to add some exclusions in your pom. dependency groupIdorg.codehaus.plexus/groupId artifactIdplexus-archiver/artifactId version1.0-alpha-9/version exclusions exclusion groupIdorg.codehaus.plexus/groupId artifactIdplexus-container-default/artifactId /exclusion exclusion groupIdorg.codehaus.plexus/groupId artifactIdplexus-component-api/artifactId /exclusion /exclusions /dependency -- Olivier 2008/7/28 Andreas Gies [EMAIL PROTECTED]: Thank you for the hint, I have changed my code so that it directly references the Archiver now. Now I get the output below output from the plugin. I think there might be an incompatibbility of the plugins. Perhaps someone could give me a hint how I could debug this? In general, if I want to use a component that has the Contextualize interface implemented...do I need to pass the Plexus context explicitly to that component or does the framework do this magically. Moreover, the documentation says that I *should* implement the Contextualize interface if I plan to use plexus components. Even if I do this, the contextualize method is never called ... A pointer at a good example would really be great. For the acute problem I have atteched My plugin code and the pom.xml. Thanks Andreas [INFO] [ESBPlugin:package] [INFO] Packaging ESB application: [INFO] Project : iocc-esb-flow-pubopflightp [INFO] Group : com.lhsystems.iocc [INFO] Version : 1.0-SNAPSHOT [INFO] Source : E:\LHSys\maven\snapshots\com.lhsystems.iocc\iocc-esb-flow-pubopflightp\1.0-SNAPSHOT\src\main\ESB [INFO] Build : E:\LHSys\maven\snapshots\com.lhsystems.iocc\iocc-esb-flow-pubopflightp\1.0-SNAPSHOT\target [INFO] XAR : xar [INFO] Creating archive : E:\LHSys\maven\snapshots\com.lhsystems.iocc\iocc-esb-flow-pubopflightp\1.0-SNAPSHOT\target\iocc-esb-flow-pubopflightp-1.0-SNAPSHOT.xar [FATAL ERROR] com.sonicsw.maven.plugins.MavenEsbPackage#execute() caused a linkage error (java.lang.IncompatibleClassChangeError) and may be out-of-date. Check the realms: [FATAL ERROR] Plugin realm = app0.child-container[com.sonicsw.maven.plugins:ESBPlugin] urls[0] = file:/C:/Documents and Settings/agies/.m2/repository/com/sonicsw/maven/plugins/ESBPlugin/1.0-SNAPSHOT/ESBPlugin-1.0-SNAPSHOT.jar urls[1] = file:/C:/Documents and Settings/agies/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.5/plexus-utils-1.5.5.jar urls[2] = file:/C:/Documents and Settings/agies/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar urls[3] = file:/C:/Documents and Settings/agies/.m2/repository/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.jar urls[4] = file:/C:/Documents and Settings/agies/.m2/repository/org/codehaus/plexus/plexus-classworlds/1.2-alpha-6/plexus-classworlds-1.2-alpha-6.jar urls[5] = file:/C:/Documents and Settings/agies/.m2/repository/org/codehaus/plexus/plexus-io/1.0-alpha-2/plexus-io-1.0-alpha-2.jar urls[6] = file:/C:/Documents and Settings/agies/.m2/repository/com/sonicsw/pso/utilities/MFUtils/1.0-SNAPSHOT/MFUtils-1.0-SNAPSHOT.jar urls[7] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/mgmt_client/7.6.0/mgmt_client-7.6.0.jar urls[8] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/sonic_mgmt_client/7.6.0/sonic_mgmt_client-7.6.0.jar urls[9] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/mgmt_config/7.6.0/mgmt_config-7.6.0.jar urls[10] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/sonic_Client/7.6.0/sonic_Client-7.6.0.jar urls[11] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/sonic_Crypto/7.6.0/sonic_Crypto-7.6.0.jar urls[12] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-esb/xq_config/7.6.0/xq_config-7.6.0.jar urls[13] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-esb/commons-logging/7.6.0/commons-logging-7.6.0.jar urls[14] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-esb/xq_core/7.6.0/xq_core-7.6.0.jar urls[15] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-esb/xbean/7.6.0/xbean-7.6.0.jar urls[16] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-esb/jsr173_api/7.6.0/jsr173_api-7.6.0.jar urls[17] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/xercesImpl/7.6.0/xercesImpl-7.6.0.jar urls[18] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/MFdirectory/7.6.0/MFdirectory-7.6.0.jar urls[19] = file:/C:/Documents and Settings/agies/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar urls[20] = file:/C:/Documents and Settings/agies/.m2/repository/sonic-mq/mfcontext/7.6.0/mfcontext-7.6.0.jar [FATAL ERROR] Container realm = plexus.core urls[0] = file:/c:/tools/maven2/lib/maven-2.0.9-uber.jar [INFO]
Re: Maven and BIRT Report Generation Engine
Reading this ML, I foudn out another maven2 repository that can help you http://repo1.maven.org/eclipse At least there is some BIRT dependencies maybe in a good version (ex: org.eclipse.birt.chart.engine/2.1.0) Manuel -- Xebia IT Architects FR : http://blog.xebia.fr EN : http://blog.xebia.com On Mon, Jul 28, 2008 at 7:00 PM, Doug Douglass [EMAIL PROTECTED]wrote: Ian, We maven-ized our local/custom build of OpenReports, which has dependencies on BIRT. We created a separate pom project to manage the entire set of BIRT dependencies as a single unit and had to manually install most the dependencies into our repository manager. Note, we haven't used the BIRT features of OpenReports much so I can't say the versions are perfect. They do produce a successful compile/package of the OpenReports war, I just can't confirm the runtime behavior. Here's the pom with only a few minor company-specific elements removed... ?xml version=1.0 encoding=UTF-8? project modelVersion4.0.0/modelVersion groupIdYOUR GROUP ID HERE/groupId artifactIdeclipse-birt-bundle/artifactId nameEclipse BiRT Bundle/name version2.2.0-1-SNAPSHOT/version packagingpom/packaging dependencies !-- Most of these dependencies required manual installation into our repositories so we could match as closely as possible the version that were delivered with OpenReports 3.0.0. If/when the Eclipse projects artifacts are deployed publicly and consistently then we can update this bundle POM and track their versions. -- dependency groupIdorg.eclipse.birt/groupId artifactIdchartengine/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIdcore/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIddataadapter/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIdengine/artifactId version2.2/version exclusions exclusion groupIddom4j/groupId artifactIddom4j/artifactId /exclusion /exclusions /dependency dependency groupIdorg.eclipse.birt/groupId artifactIdmodel/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIdscript/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIddte/artifactId version2.2/version /dependency !-- EMF (Eclipse Modeling Framework ) -- dependency groupIdorg.eclipse.emf/groupId artifactIdecore/artifactId version2.2.2.v200702131851/version /dependency dependency groupIdorg.eclipse.emf/groupId artifactIdecore-xmi/artifactId version2.2.2.v200702131851/version /dependency dependency groupIdorg.eclipse.emf/groupId artifactIdcommon/artifactId version2.2.1.v200702131851/version /dependency !-- W3C -- dependency groupIdorg.w3c/groupId artifactIdflute/artifactId version1.2/version /dependency dependency groupIdorg.w3c/groupId artifactIdsac/artifactId version1.3/version /dependency !-- Commons -- dependency groupIdcommons-codec/groupId artifactIdcommons-codec/artifactId version1.3/version !-- removing unwanted transitive dependencies -- exclusions exclusion artifactIdjunit/artifactId groupIdjunit/groupId /exclusion /exclusions /dependency dependency groupIdcommons-cli/groupId artifactIdcommons-cli/artifactId version1.0/version !-- removing unwanted transitive dependencies -- exclusions exclusion artifactIdcommons-lang/artifactId groupIdcommons-lang/groupId /exclusion exclusion artifactIdcommons-logging/artifactId groupIdcommons-logging/groupId /exclusion /exclusions /dependency dependency groupIdcommons-discovery/groupId artifactIdcommons-discovery/artifactId version0.2/version /dependency !-- misc -- dependency groupIdcom.lowagie/groupId artifactIditext/artifactId version1.3/version /dependency dependency groupIdcom.ibm.icu/groupId artifactIdicu4j/artifactId version3.6.1/version /dependency dependency groupIdrhino/groupId artifactIdjs/artifactId version1.6R2/version /dependency /dependencies /project On Mon, Jul 28, 2008 at 10:24 AM, Ian Coleman [EMAIL PROTECTED] wrote: Maven gurus: I'm still finding my way with Maven, and am trying to convert a project from Ant to maven2. The biggest blocker I've found is integration with BIRT. The application I'm converting uses BIRT extensively, but
Re: Using a Pleus component in a plugin
Thanks again,
the exclusions did the trick and the following code now works:
/**
* To look up Archiver/UnArchiver implementations
*
* @component
* @required
*/
protected ArchiverManager archiverManager;
public void execute() throws MojoExecutionException,
MojoFailureException {
getLog().info(Packaging ESB application: );
getLog().info(Project : + artifactId);
getLog().info(Group : + groupId);
getLog().info(Version : + version);
getLog().info(Source : + sourceDirectory);
getLog().info(Build : + buildDirectory);
getLog().info(XAR : + xarDirectory);
File archiveFile = new File(buildDirectory, finalName + .xar);
try {
getLog().info(Creating archive : + archiveFile.getAbsolutePath());
Archiver archiver = archiverManager.getArchiver(zip);
archiver.setDestFile(archiveFile);
//archiver.addDirectory(new File(buildDirectory, xarDirectory));
archiver.addDirectory(new File(generated-src/ + xarDirectory));
archiver.createArchive();
} catch(Exception e) {
throw new MojoExecutionException(Failed to create ESB archive +
archiveFile.getAbsolutePath(), e);
}
}
My final question is...Where is the source of knowledge to know about
the inclusions / exclusions i would code in my pom? Is there a way of
telling or is it just experience ?
Thanks again
Andreas
Olivier Lamy schrieb:
If you use plexus-archiver you have to add some exclusions in your pom.
dependency
groupIdorg.codehaus.plexus/groupId
artifactIdplexus-archiver/artifactId
version1.0-alpha-9/version
exclusions
exclusion
groupIdorg.codehaus.plexus/groupId
artifactIdplexus-container-default/artifactId
/exclusion
exclusion
groupIdorg.codehaus.plexus/groupId
artifactIdplexus-component-api/artifactId
/exclusion
/exclusions
/dependency
--
Olivier
2008/7/28 Andreas Gies [EMAIL PROTECTED]:
Thank you for the hint,
I have changed my code so that it directly references the Archiver now. Now
I get the output below output from the plugin.
I think there might be an incompatibbility of the plugins. Perhaps someone
could give me a hint how I could debug this?
In general, if I want to use a component that has the Contextualize
interface implemented...do I need to pass the
Plexus context explicitly to that component or does the framework do this
magically. Moreover, the documentation
says that I *should* implement the Contextualize interface if I plan to use
plexus components. Even if I do this, the
contextualize method is never called ...
A pointer at a good example would really be great. For the acute problem I
have atteched My plugin code and the pom.xml.
Thanks
Andreas
[INFO] [ESBPlugin:package]
[INFO] Packaging ESB application:
[INFO] Project : iocc-esb-flow-pubopflightp
[INFO] Group : com.lhsystems.iocc
[INFO] Version : 1.0-SNAPSHOT
[INFO] Source :
E:\LHSys\maven\snapshots\com.lhsystems.iocc\iocc-esb-flow-pubopflightp\1.0-SNAPSHOT\src\main\ESB
[INFO] Build :
E:\LHSys\maven\snapshots\com.lhsystems.iocc\iocc-esb-flow-pubopflightp\1.0-SNAPSHOT\target
[INFO] XAR : xar
[INFO] Creating archive :
E:\LHSys\maven\snapshots\com.lhsystems.iocc\iocc-esb-flow-pubopflightp\1.0-SNAPSHOT\target\iocc-esb-flow-pubopflightp-1.0-SNAPSHOT.xar
[FATAL ERROR] com.sonicsw.maven.plugins.MavenEsbPackage#execute() caused a
linkage error (java.lang.IncompatibleClassChangeError) and may be
out-of-date. Check the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[com.sonicsw.maven.plugins:ESBPlugin]
urls[0] = file:/C:/Documents and
Settings/agies/.m2/repository/com/sonicsw/maven/plugins/ESBPlugin/1.0-SNAPSHOT/ESBPlugin-1.0-SNAPSHOT.jar
urls[1] = file:/C:/Documents and
Settings/agies/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.5/plexus-utils-1.5.5.jar
urls[2] = file:/C:/Documents and
Settings/agies/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
urls[3] = file:/C:/Documents and
Settings/agies/.m2/repository/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.jar
urls[4] = file:/C:/Documents and
Settings/agies/.m2/repository/org/codehaus/plexus/plexus-classworlds/1.2-alpha-6/plexus-classworlds-1.2-alpha-6.jar
urls[5] = file:/C:/Documents and
Settings/agies/.m2/repository/org/codehaus/plexus/plexus-io/1.0-alpha-2/plexus-io-1.0-alpha-2.jar
urls[6] = file:/C:/Documents and
Settings/agies/.m2/repository/com/sonicsw/pso/utilities/MFUtils/1.0-SNAPSHOT/MFUtils-1.0-SNAPSHOT.jar
urls[7] = file:/C:/Documents and
Settings/agies/.m2/repository/sonic-mq/mgmt_client/7.6.0/mgmt_client-7.6.0.jar
urls[8] = file:/C:/Documents and
Settings/agies/.m2/repository/sonic-mq/sonic_mgmt_client/7.6.0/sonic_mgmt_client-7.6.0.jar
urls[9] = file:/C:/Documents and
Settings/agies/.m2/repository/sonic-mq/mgmt_config/7.6.0/mgmt_config-7.6.0.jar
urls[10] = file:/C:/Documents and
Re: Using a Pleus component in a plugin
It's a know issue for maven dev.
See
http://maven.markmail.org/message/lvednyntn7a563s4?q=plexus-archiver+list:org.apache.maven.devpage=1
--
Olivier
2008/7/28 Andreas Gies [EMAIL PROTECTED]:
Thanks again,
the exclusions did the trick and the following code now works:
/**
* To look up Archiver/UnArchiver implementations
*
* @component
* @required
*/
protected ArchiverManager archiverManager;
public void execute() throws MojoExecutionException, MojoFailureException {
getLog().info(Packaging ESB application: );
getLog().info(Project : + artifactId); getLog().info(Group : +
groupId); getLog().info(Version : + version);
getLog().info(Source : + sourceDirectory);
getLog().info(Build : + buildDirectory);
getLog().info(XAR : + xarDirectory);
File archiveFile = new File(buildDirectory, finalName + .xar);
try {
getLog().info(Creating archive : + archiveFile.getAbsolutePath());
Archiver archiver = archiverManager.getArchiver(zip);
archiver.setDestFile(archiveFile);
//archiver.addDirectory(new File(buildDirectory, xarDirectory));
archiver.addDirectory(new File(generated-src/ + xarDirectory));
archiver.createArchive();
} catch(Exception e) {
throw new MojoExecutionException(Failed to create ESB archive +
archiveFile.getAbsolutePath(), e);
}
}
My final question is...Where is the source of knowledge to know about the
inclusions / exclusions i would code in my pom? Is there a way of telling or
is it just experience ?
Thanks again
Andreas
Olivier Lamy schrieb:
If you use plexus-archiver you have to add some exclusions in your pom.
dependency
groupIdorg.codehaus.plexus/groupId
artifactIdplexus-archiver/artifactId
version1.0-alpha-9/version
exclusions
exclusion
groupIdorg.codehaus.plexus/groupId
artifactIdplexus-container-default/artifactId
/exclusion
exclusion
groupIdorg.codehaus.plexus/groupId
artifactIdplexus-component-api/artifactId
/exclusion
/exclusions
/dependency
--
Olivier
2008/7/28 Andreas Gies [EMAIL PROTECTED]:
Thank you for the hint,
I have changed my code so that it directly references the Archiver now.
Now
I get the output below output from the plugin.
I think there might be an incompatibbility of the plugins. Perhaps
someone
could give me a hint how I could debug this?
In general, if I want to use a component that has the Contextualize
interface implemented...do I need to pass the
Plexus context explicitly to that component or does the framework do this
magically. Moreover, the documentation
says that I *should* implement the Contextualize interface if I plan to
use
plexus components. Even if I do this, the
contextualize method is never called ...
A pointer at a good example would really be great. For the acute problem
I
have atteched My plugin code and the pom.xml.
Thanks
Andreas
[INFO] [ESBPlugin:package]
[INFO] Packaging ESB application:
[INFO] Project : iocc-esb-flow-pubopflightp
[INFO] Group : com.lhsystems.iocc
[INFO] Version : 1.0-SNAPSHOT
[INFO] Source :
E:\LHSys\maven\snapshots\com.lhsystems.iocc\iocc-esb-flow-pubopflightp\1.0-SNAPSHOT\src\main\ESB
[INFO] Build :
E:\LHSys\maven\snapshots\com.lhsystems.iocc\iocc-esb-flow-pubopflightp\1.0-SNAPSHOT\target
[INFO] XAR : xar
[INFO] Creating archive :
E:\LHSys\maven\snapshots\com.lhsystems.iocc\iocc-esb-flow-pubopflightp\1.0-SNAPSHOT\target\iocc-esb-flow-pubopflightp-1.0-SNAPSHOT.xar
[FATAL ERROR] com.sonicsw.maven.plugins.MavenEsbPackage#execute() caused
a
linkage error (java.lang.IncompatibleClassChangeError) and may be
out-of-date. Check the realms:
[FATAL ERROR] Plugin realm =
app0.child-container[com.sonicsw.maven.plugins:ESBPlugin]
urls[0] = file:/C:/Documents and
Settings/agies/.m2/repository/com/sonicsw/maven/plugins/ESBPlugin/1.0-SNAPSHOT/ESBPlugin-1.0-SNAPSHOT.jar
urls[1] = file:/C:/Documents and
Settings/agies/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.5/plexus-utils-1.5.5.jar
urls[2] = file:/C:/Documents and
Settings/agies/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
urls[3] = file:/C:/Documents and
Settings/agies/.m2/repository/org/codehaus/plexus/plexus-component-api/1.0-alpha-15/plexus-component-api-1.0-alpha-15.jar
urls[4] = file:/C:/Documents and
Settings/agies/.m2/repository/org/codehaus/plexus/plexus-classworlds/1.2-alpha-6/plexus-classworlds-1.2-alpha-6.jar
urls[5] = file:/C:/Documents and
Settings/agies/.m2/repository/org/codehaus/plexus/plexus-io/1.0-alpha-2/plexus-io-1.0-alpha-2.jar
urls[6] = file:/C:/Documents and
Settings/agies/.m2/repository/com/sonicsw/pso/utilities/MFUtils/1.0-SNAPSHOT/MFUtils-1.0-SNAPSHOT.jar
urls[7] = file:/C:/Documents and
Settings/agies/.m2/repository/sonic-mq/mgmt_client/7.6.0/mgmt_client-7.6.0.jar
urls[8] =
Version ranges in maven bundles
Hi, I'm using a version range to include packages in a bundle using the maven assembly plugin. It's detecting the right versions, but it gives the following warnings followed by an error: [WARNING] Cannot include project artifact: org.trege:org.trege.product.product.updatesite:pom:6.2.1.0; it doesn't have an associated file or directory. [WARNING] Attempting to build MavenProject instance for Artifact (org.trege:org.trege.product.thirdparty:6.2.1.2) of type: jar; constructing POM artifact instead. [WARNING] Attempting to build MavenProject instance for Artifact (org.trege:org.trege.product.core.ui:6.2.1.1) of type: jar; constructing POM art ifact instead. [WARNING] Attempting to build MavenProject instance for Artifact (org.trege:org.trege.product.packager:6.2.1.1) of type: jar; constructing POM ar tifact instead. [WARNING] Attempting to build MavenProject instance for Artifact (org.trege:org.trege.product.packager.ui:6.2.1.1) of type: jar; constructing POM artifact instead. [WARNING] Attempting to build MavenProject instance for Artifact (org.trege:org.trege.product.test.core:6.2.1.1) of type: jar; constructing POM a rtifact instead. [WARNING] Attempting to build MavenProject instance for Artifact (org.trege:org.trege.product.test.plugins:6.2.1.1) of type: jar; constructing PO M artifact instead. [WARNING] Attempting to build MavenProject instance for Artifact (org.trege:org.trege.product.test.ui:6.2.1.1) of type: jar; constructing POM art ifact instead. [WARNING] Attempting to build MavenProject instance for Artifact (org.trege:org.trege.product.validation.core:6.2.1.1) of type: jar; constructing POM artifact instead. [WARNING] Attempting to build MavenProject instance for Artifact (org.trege:org.trege.product.validation.plugins:6.2.1.1) of type: jar; construct ing POM artifact instead. [WARNING] Attempting to build MavenProject instance for Artifact (org.trege:org.trege.product.validation.ui:6.2.1.1) of type: jar; constructing P OM artifact instead. java.lang.NullPointerException: version was null for org.trege:org.trege.product.thirdparty at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) at org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) at org.apache.maven.shared.artifact.filter.ScopeArtifactFilter.include(ScopeArtifactFilter.java:142) at org.apache.maven.project.artifact.MavenMetadataSource.createArtifacts(MavenMetadataSource.java:357) at org.apache.maven.plugin.assembly.artifact.DefaultDependencyResolver.resolveDependencies(DefaultDependencyResolver.java:123) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.resolveDependencyArtifacts(AddDependencySetsTask.java:205) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.addDependencySet(AddDependencySetsTask.java:132) at org.apache.maven.plugin.assembly.archive.task.AddDependencySetsTask.execute(AddDependencySetsTask.java:116) at org.apache.maven.plugin.assembly.archive.phase.DependencySetAssemblyPhase.execute(DependencySetAssemblyPhase.java:74) at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:129) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:322) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) 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:597) 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
Strange m2 2.0.9 behaviour
I'm seeing an issue with 2.0.9 I think. Between the 21st and the 22nd,
the only change in the build environment was upgrading from 2.0.5 to
2.0.9.
We're running cruise control and we are injecting the ${label} value
into some of our files during the build. On the 22nd, this stopped
working leaving behind ${label} in the files that used to be processed
by the process-resources phase.
Is this a known issue or anything? Anyone else seeing this?
Re: [ANN] Maven Project Info Reports Plugin 2.1 Released
Congrats for getting the release out and many thanks. It's been worth the wait, there's a lot of improvements in this one! Kalle On Mon, Jul 28, 2008 at 7:50 AM, Vincent Siveton [EMAIL PROTECTED]wrote: The Maven team is pleased to announce the release of the Maven Project Info Reports Plugin, version 2.1 This plugin generates standard reports for the specified project. http://maven.apache.org/plugins/maven-project-info-reports-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.1/version /plugin Release Notes - Maven 2.x Project Info Reports Plugin - Version 2.1 ** Sub-task * [MPIR-126] - Move PluginManagementRenderer in an inner class of PluginManagementReport ** Bug * [MPIR-48] - Internal html references are not generated in the team-list.html * [MPIR-49] - team-list.html is not correctly generated when table is to large * [MPIR-52] - Wrong text on scm page for svn protocol * [MPIR-53] - there is no info about project-info-reports:summary in documentation * [MPIR-57] - URLs only link if they are FQDNs * [MPIR-59] - Site generation exception for french language, error with simple quote in translation S'inscrire for mailing list * [MPIR-60] - Current head throws NPE when generating reports * [MPIR-65] - Direct report generation breaks on skin version even though it is specified * [MPIR-66] - When run standalone, project metadata is missing * [MPIR-70] - NullPointerException when generating Dependencies report * [MPIR-75] - Typing mistake in properties file * [MPIR-76] - Dependencies report is incorrect * [MPIR-79] - Add explicit resource bundle for English * [MPIR-81] - DependenciesRenderer logs Exception when it can't find the artifact being built!!! * [MPIR-84] - StringIndexOutOfBoundsException when ML archive dont finish with a / * [MPIR-89] - Bad spelling in Project Information = Overview = Dependencies * [MPIR-90] - Bad style in text Access from behind a firewall * [MPIR-91] - Bad spelling in text Access through a proxy * [MPIR-92] - Wrong encoding in german properties * [MPIR-96] - Switched link text and target in license report * [MPIR-98] - Team list does not contain anchors on user ids * [MPIR-99] - Strange warnings when generating Plugin Management report * [MPIR-104] - Regression in 2.1-SNAPSHOT: SVN is no more recognized * [MPIR-106] - Regression in 2.1-SNAPSHOT, the Project Dependencies and the Project Transitive Dependencies are the same * [MPIR-109] - Wrong description of in source repository overview * [MPIR-119] - Dependency Repository Locations in Dependency Report doesn't allow snapshot artifacts url from the snapshot repositories * [MPIR-122] - Brazilian Portuguese language bundle - encoding problems and improvements * [MPIR-123] - Hungarian language bundle - encoding problems and improvements * [MPIR-124] - License report is empty in offline * [MPIR-129] - Duplicate entries of the same artifact in Licenses section of Dependencies report * [MPIR-130] - No mark or link to SNAPSHOT artifacts in Dependency Repository Locations section of Dependencies report ** Improvement * [MPIR-28] - improve convergence report * [MPIR-46] - Sample reports are out of date * [MPIR-47] - Dependency Report does not show origin of transitive dependency * [MPIR-54] - Team list table improvement * [MPIR-56] - Refactor the dependencies report * [MPIR-58] - The sandbox component Jar has been renamed to JarAnalyzer * [MPIR-61] - [PATCH] Updated CI Systems * [MPIR-62] - [PATCH] Dependency File Details : set right justification for numeric columns * [MPIR-64] - Korean translation resource file * [MPIR-67] - Please update the german localization. * [MPIR-69] - add anchors for developers * [MPIR-72] - Upgrade to doxia 1.0-alpha-9 * [MPIR-82] - Clarify usage of outputDirectory parameter * [MPIR-87] - Show repositories an artifact is deployed to as a report * [MPIR-94] - Change optional label in dependencies site * [MPIR-108] - Add validation of SCM urls * [MPIR-110] - Update code due to deprecated classes in maven-dependency-tree:1.1 * [MPIR-111] - Make Classifier and Optional column in dependencies report optional in the renderer * [MPIR-112] - Dependency Listings is too big: replace it by toogle entries in the dependency tree * [MPIR-113] - Dependency Tree lists all dependencies: needs to reduce to dependencies used by the project * [MPIR-115] - Make the Sealed column optional in dependencies report * [MPIR-116] - Make the classifier column optional in dependencies management report * [MPIR-117] - Replaced the table caption in the CI report * [MPIR-118] -
Re: I18N
Hi Jeff! Did you install manually this JAR in your local repository ? No. Maybe I should explain it again: I downloaded it from the repository: http://repo1.maven.org/maven2/com/incors/plaf/kunststoff/2.0.2/ and there is the jar file, but no pom file. And so maven tries to download the pom on every build. I think that I could fix it locally, but as it is an open source projects the jar will be used from other developers. Couldn't one create the pom in the repository? Regards, Peter. PS: the pom should look like the following I think: ?xml version=1.0 encoding=UTF-8?project modelVersion4.0.0/modelVersion groupIdcom/incors/plaf/groupId artifactIdkunststoff/artifactId version2.0.2/version descriptionA nice look and feel./description /project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven-dependency-plugin fails if pom.xml contains a submodule
You need to see this:
http://maven.apache.org/plugins/maven-dependency-plugin/faq.html#cli
-Original Message-
From: Julien CARSIQUE [mailto:[EMAIL PROTECTED]
Sent: Monday, July 28, 2008 8:01 AM
To: Maven Users List
Subject: maven-dependency-plugin fails if pom.xml contains a submodule
Hi,
Using maven-dependency-plugin, I go a build error since I've add a
module in the pom.
Principle is to be able to manage two different calls : from execution,
libraries go in target/lib/ and from a command-line call (or Ant),
libraries go into ${jboss.lib}.
All worked fine until I added a module. Now, calls from command line
unless we specify the -N option.
The plugin configuration is not inside a pluginManagement tag, so it
shouldn't be inherited, does it ?
I got this error from the submodule, not from the module containing the
dependency plugin configuration:
[ERROR] BUILD ERROR
[INFO]
[INFO] One or more required plugin parameters are invalid/missing
for 'dependency:copy'
[0] Inside the definition for plugin 'maven-dependency-plugin'
specify the following:
configuration
...
artifactItemsVALUE/artifactItems
/configuration.
- using -N on the command line solve the problem
- help:effective-pom result (ran on the failing child) doesn't contain
any reference to dependency-plugin except this one in the
pluginManagement:
plugin
artifactIdmaven-dependency-plugin/artifactId
version2.0/version
/plugin
- call from execution, during an mvn package for example succeed.
Here's my configuration :
modules
moduleaModule/module
/modules
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
configuration
outputDirectory${jboss.lib}/outputDirectory
artifactItems
artifactItem
groupIdaGroupId/groupId
artifactIdanArtifactId/artifactId
versionaVersion/version
overWritetrue/overWrite
/artifactItem
/artifactItems
/configuration
executions
execution
idcopy-installed/id
phasepackage/phase
goals
goalcopy/goal
/goals
configuration
outputDirectory${project.build.directory}/lib/outputDirectory
/configuration
/execution
/executions
plugin
/plugins
/build
Thanks,
Julien
--
Julien CARSIQUE, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
[EMAIL PROTECTED] | Tel: +33 1 40 33 79 87
-
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]
mvn exec:java is giving error
Hi all, I am new to maven and I was trying to run a simple java program from maven. But its NOT working and complaining that the plugin does not exist or no valid version could be found. Here is the detailed output: $ mvn exec:java -Dexec.mainClass=simpleproject.App [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'exec'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-exec-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Jul 29 05:45:32 IST 2008 [INFO] Final Memory: 1M/2M [INFO] I created a simple project using: $ mvn archetype:create -DgroupId=simpleproject -DartifactId=simpleMavenProject It contains a default HelloWorld app in simpleproject.App.java which is what I am trying to run. NOTE: If I use the full name of the exec-maven plugin, it is working. $ mvn org.codehaus.mojo:exec-maven-plugin:1.1:java -Dexec.mainClass=simpleproject.App The above works. Any reason why mvn exec:java -Dexec.mainClass=simpleproject.App is not working??? I am using maven-2.0.9 $ mvn -version Maven version: 2.0.9 Java version: 1.5.0_13 OS name: mac os x version: 10.5.2 arch: i386 Family: unix Thanks for the help in advance. Regards, Abhishek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
