Encryption for SCM password?
Is there a way to encrypt the SCM password used in configuration of the SCM plugin? I've been able to use a clear text password in my settings file, but when I try to use a Maven encrypted password it doesn't seem to be able to decrypt it on the fly. From checking out the source code for the SCM plugin it doesn't seem that this ability is there. Is this something that is on the list for an upcoming release? Kurt
RE: Maven java.lang.OutOfMemoryError
Thanks alexander Thanks Regards Sammaiah Nagapuri Inaction breeds doubt and fear. Action breeds confidence and courage. If you want to conquer fear, do not sit home and think about it. Go out and get busy. -Original Message- From: Alexander [mailto:the.malk...@gmail.com] Sent: Thursday, August 13, 2009 7:34 PM To: Maven Users List Subject: Re: Maven java.lang.OutOfMemoryError Hi, No, If you already resolved all dependencies there is no need to compile again in online mode. You could force turn on offline mode with -o or --offline command line option. Reason why maven is trying to acces Internet is smth like update dependencies with SNAPSHOTS version and similar. And what about your stacktrace - there is clearly said that connection was dropped in cause of timeout. You should run maven commands in offline mode as your computure (not laptop) dont have access to internet. P.S. BTW also you could manually resolve all dependencies via mvn dependensy:resolve 2009/8/13 Sammaiah Nagapuri sammaiah.nagap...@hcl.in Hi all, This is sammaiah nagapuri. Sorry if I am asking trivial issue. I am the new user for this community and I am just learning now. What the problem I am getting is in my company we don't have access to lot of cites. Is it really necessary to work with maven? And one more thing is if we download all the plugins while connecting to the internet and I am trying now to perform one task like compile (mvn compile). This time also is it really necessary the internet connection? As we already downloaded all the plugins. Then why it will connect to internet once again even though we are having some plugins in our repository? I am facing this problem nearly from 2 weeks. I am searching in google about this. But I am not getting any info. I am getting the stacktrace like following one. -- F:\Ravi\sammvn compile [INFO] Scanning for projects... [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [compile] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository central (http://repo1.maven.org/maven2): Er ror transferring file: Connection timed out: connect Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.3/maven-resources-plugin-2.3.pom [WARNING] Unable to get resource 'org.apache.maven.plugins:maven-resources-plugin:pom:2.3' from repository central (http://repo1.maven.org/maven2): Er ror transferring file: Connection timed out: connect [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-resources-plugin Version: 2.3 Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-resources-plugin:pom:2.3 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 43 seconds [INFO] Finished at: Thu Aug 13 18:04:40 GMT+05:30 2009 [INFO] Final Memory: 1M/2M Here what I done is my laptop is having internet connection. So there I done like 'mvn install'. Later I copied those repositories into another system (which is not having internet connection). There I am getting this problem? I am working in Bangalore. If anybody is there in Bangalore please share the mobile number. Then I'll call you. Please show me some way. Thanks in advance. Thanks Regards Sammaiah Nagapuri Inaction breeds doubt and fear. Action breeds confidence and courage. If you want to conquer fear, do not sit home and think about it. Go out and get busy. -Original Message- From: Bruno Aranda [mailto:brunoara...@gmail.com] Sent: Thursday, August 13, 2009 5:10 PM To: Maven Users List Subject: Re: Maven java.lang.OutOfMemoryError It's MAVEN_OPTS Cheers, Bruno 2009/8/13 kopemor developm...@knollenstein.nl: Hello, I am getting java.lang.OutOfMemoryError: Java heap space exception when I compile my project using Maven. I have tried several options: 1. Setting variable: export MAVEN_OPT=-Xmx1024m 2. Using Maven compile plugin: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration
RE: Hibernate 3 Plugin
Hello Neil I think the problem is it doesn't find the persistence.xml because it isn't the standard META-INF/persistence.xml as per the hibernatools documentation: https://www.hibernate.org/hib_docs/tools/reference/en/html/ant.html jpaconfiguration will simply just try and auto-configure itself based on the available classpath, e.g. look for META-INF/persistence.xml. Try moving your persistence.xml to the META-INF directory and try it again Regards Johann Reyes -Original Message- From: Neil Chaudhuri [mailto:nchaudh...@potomacfusion.com] Sent: Thursday, August 13, 2009 2:26 PM To: users@maven.apache.org Subject: Hibernate 3 Plugin I am using Maven with JPA/Hibernate, and I would like to generate a DDL file to give to my DBAs. I am using the Hibernate 3 Maven plugin to do this. However, I keep getting the error [ERROR] Persistence unit not found: 'myapp'. Here is the relevant portion of the POM: plugin groupIdorg.codehaus.mojo/groupId artifactIdhibernate3-maven-plugin/artifactId version2.2/version configuration components component namehbm2ddl/name implementationjpaconfiguration/implementation /component /components componentProperties createtrue/create dropfalse/drop exportfalse/export configurationfile/target/classes/persistence.xml/configurationfile persistenceunitmyapp/persistenceunit outputfilenamemyapp.sql/outputfilename formattrue/format /componentProperties /configuration dependencies dependency groupIdcom.oracle.jdbc/groupId artifactIdojdbc6/artifactId version11.1.0.7.0/version /dependency /dependencies /plugin Here is the persistence.xml founf in src/main/resources as well as target/classes: persistence-unit name=myapp transaction-type=RESOURCE_LOCAL providerorg.hibernate.ejb.HibernatePersistence/provider jta-data-sourceMYAPP_DS/jta-data-source properties property name=hibernate.show_sql value=true/ property name=hibernate.format_sql value=true/ property name=hibernate.dialect value=org.hibernate.dialect.Oracle10gDialect/ property name=hibernate.cache.provider_class value=org.hibernate.cache.HashtableCacheProvider/ /properties /persistence-unit The files are where they are supposed to be, and surely the plugin knows to look in the target folder for everything. I would appreciate any insight into what the issue might be. Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
SCM plugin password encryption
I feel like I must be missing something because I have yet found a way to
encrypt my SCM password in my Maven POM. I am using the maven release plugin
and need to use some credentials on the CI server, but I don't want to store
the password in clear text. Is there a way to encrypt the password and
reference it in the Maven SCM plugin?
I've tried using the Maven encryption guide
(http://maven.apache.org/guides/mini/guide-encryption.html) which works well
for encrypting Maven repository credentials. The problem is that you can't
(from what I've seen) reference the id for a server in the Maven SCM plugin.
Here's an example of what I'd like to see in the POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
configuration
usernamekurt.tometich/username
password{encrypted password here}/password
/configuration
/plugin
Any ideas of how to do this would be welcome. Thanks in advance.
Kurt
Re: How to add SYSTEM scope dependency to manifest?
If you can't or won't follow the advice to install the artifact into a repository manager, then simply use install-file to install it to your local repo, the change the scope to compile. Best Brett On 8/13/09, REMIJAN, MICHAEL J [AG/1000] michael.j.remi...@monsanto.com wrote: There are many reasons why a project would use a JAR file which isn't in a repository. So I'm assuming Maven cannot be configured to handle this? It seems to me if I can configure the dependencySet to include scopesystem/scope dependencies then I should also be able to make a similar configuration with the manifestaddClasspath. Or is there another way of accomplishing the same thing? -Original Message- From: Brian Fox [mailto:bri...@infinity.nu] Sent: Wednesday, August 12, 2009 1:58 PM To: Maven Users List Subject: Re: How to add SYSTEM scope dependency to manifest? System scope is meant for system objects that would be present on the target os, something like MFC.dll etc. Using it to work around having the jar in a repository is a definite anti-pattern. Instead have it uploaded to your Corporate Nexus repository. On Wed, Aug 12, 2009 at 1:10 PM, REMIJAN, MICHAEL J [AG/1000]michael.j.remi...@monsanto.com wrote: The jar is not in any repository so I read it off of the file system by setting the dependency to scopesystem/scope This is the only scope which can read jars off the file system. If the scope is changed to compile, Maven will want to pull it from a repository. The m2 plugin for eclipse gives an error if systemPath is set and the scope is not system. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Wednesday, August 12, 2009 9:46 AM To: Maven Users List Subject: Re: How to add SYSTEM scope dependency to manifest? if a dependency is defined as scopesystem/scope then addClasspath does not include it in the manifest. I need to include it in the manifest. Any ideas? Is there a reason the obvious answer -- change it to a different scope eg compile -- is not acceptable? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of Viruses or other Malware. Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of Viruses or other Malware. Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Sent from my mobile device -
animal-sniffer on central?
Hi, I'm following the guide: http://maven.apache.org/guides/mini/guide-building-jdk14-on-jdk15.html The issue is I can't find animal-sniffer on the central Maven repository. I think it would be easier for users to have it on central repo. Or at least update the guide to tell that the dependency is only available on java.net repository. Thanks, Julien
RE: SCM plugin password encryption
We just need to add this feature to maven-scm-plugin.
We could use maven-sql-plugin as an example, it can read encrypted DB
password in the same manner as repository credentials.
Andrei Solntsev,
Software Developer,
HireRight Estonia
-Original Message-
From: KURT TOMETICH [mailto:boomtow...@msn.com]
Sent: Thursday, August 13, 2009 7:07 PM
To: users@maven.apache.org
Subject: SCM plugin password encryption
I feel like I must be missing something because I have yet found a way
to encrypt my SCM password in my Maven POM. I am using the maven
release plugin and need to use some credentials on the CI server, but I
don't want to store the password in clear text. Is there a way to
encrypt the password and reference it in the Maven SCM plugin?
I've tried using the Maven encryption guide
(http://maven.apache.org/guides/mini/guide-encryption.html) which works
well for encrypting Maven repository credentials. The problem is that
you can't (from what I've seen) reference the id for a server in the
Maven SCM plugin. Here's an example of what I'd like to see in the POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
configuration
usernamekurt.tometich/username
password{encrypted password here}/password
/configuration
/plugin
Any ideas of how to do this would be welcome. Thanks in advance.
Kurt
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: SCM plugin password encryption
please create a jira!
I'll try to go over a few scm issues this weekend, maybe I have time for this
too.
LieGrue,
strub
- Original Message
From: Andrei Solntsev asolnt...@hireright.ee
To: Maven Users List users@maven.apache.org
Sent: Friday, August 14, 2009 9:23:28 AM
Subject: RE: SCM plugin password encryption
We just need to add this feature to maven-scm-plugin.
We could use maven-sql-plugin as an example, it can read encrypted DB
password in the same manner as repository credentials.
Andrei Solntsev,
Software Developer,
HireRight Estonia
-Original Message-
From: KURT TOMETICH [mailto:boomtow...@msn.com]
Sent: Thursday, August 13, 2009 7:07 PM
To: users@maven.apache.org
Subject: SCM plugin password encryption
I feel like I must be missing something because I have yet found a way
to encrypt my SCM password in my Maven POM. I am using the maven
release plugin and need to use some credentials on the CI server, but I
don't want to store the password in clear text. Is there a way to
encrypt the password and reference it in the Maven SCM plugin?
I've tried using the Maven encryption guide
(http://maven.apache.org/guides/mini/guide-encryption.html) which works
well for encrypting Maven repository credentials. The problem is that
you can't (from what I've seen) reference the id for a server in the
Maven SCM plugin. Here's an example of what I'd like to see in the POM:
org.apache.maven.plugins
maven-scm-plugin
kurt.tometich
{encrypted password here}
Any ideas of how to do this would be welcome. Thanks in advance.
Kurt
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: animal-sniffer on central?
This is correct, in fact we got kohsuke added as a m...@codehaus developer so that he could publish animal sniffer through the mojo.codehaus.org project (among other reasons). I know Kohsuke is has a different perspective w.r.t. whether the current policy of central (i.e. that all artifacts published to central must be self-contained on central)... and has quite ligitimately pointed out that there are a number of artifacts published on central which break this policy... We (as in Kohsuke and I) have just recently identified that the jaxws-api 2,1 pom's on central are invalid, and are missing some dependencies (see issue VCC-2 @ vcc.dev.java.net) Perhaps Kosuke might consider pushing animal sniffer to central, or even moving the animal sniffer project into mojo as it is yet another of his fabulous projects... [I only wish I was 1/10th as prolific as Kohsuke] -Stephen 2009/8/14 Julien HENRY henr...@yahoo.fr: Hi, I'm following the guide: http://maven.apache.org/guides/mini/guide-building-jdk14-on-jdk15.html The issue is I can't find animal-sniffer on the central Maven repository. I think it would be easier for users to have it on central repo. Or at least update the guide to tell that the dependency is only available on java.net repository. Thanks, Julien - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: SCM plugin password encryption
can you not put your password in a property defined in your
~/.m2/settings.xml file and then reference that property in your scm
config section?
that way you can change the permissions on your ~/.m2/settings.xml
file to make it only readable by yourself (unless you are using
FAT/FAT32 as your filesystem eek!)
-Stephen
2009/8/13 KURT TOMETICH boomtow...@msn.com:
I feel like I must be missing something because I have yet found a way to
encrypt my SCM password in my Maven POM. I am using the maven release plugin
and need to use some credentials on the CI server, but I don't want to store
the password in clear text. Is there a way to encrypt the password and
reference it in the Maven SCM plugin?
I've tried using the Maven encryption guide
(http://maven.apache.org/guides/mini/guide-encryption.html) which works well
for encrypting Maven repository credentials. The problem is that you can't
(from what I've seen) reference the id for a server in the Maven SCM plugin.
Here's an example of what I'd like to see in the POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
configuration
usernamekurt.tometich/username
password{encrypted password here}/password
/configuration
/plugin
Any ideas of how to do this would be welcome. Thanks in advance.
Kurt
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: SCM plugin password encryption
can you not put your password in a property defined in your
~/.m2/settings.xml file and then reference that property in your scm
config section?
Writing passwords into poms is surely always a dirty hack and using the private
settings.xml is a good point indeed.
But on a CI server, the CI user usually is accessible by a lot of people.
Storing private credentials imho simply doesn't work in this case.
Otoh, for shadow password functionality, I fear this won't work since there is
no way to restore the original password for sending it to the SCM system.
Imho the best way would be to create an own user for the CI system in the SCM
which only has readonly access.
LieGrue,
strub
- Original Message
From: Stephen Connolly stephen.alan.conno...@gmail.com
To: Maven Users List users@maven.apache.org
Sent: Friday, August 14, 2009 10:10:32 AM
Subject: Re: SCM plugin password encryption
can you not put your password in a property defined in your
~/.m2/settings.xml file and then reference that property in your scm
config section?
that way you can change the permissions on your ~/.m2/settings.xml
file to make it only readable by yourself (unless you are using
FAT/FAT32 as your filesystem eek!)
-Stephen
2009/8/13 KURT TOMETICH :
I feel like I must be missing something because I have yet found a way to
encrypt my SCM password in my Maven POM. I am using the maven release plugin
and need to use some credentials on the CI server, but I don't want to store
the
password in clear text. Is there a way to encrypt the password and reference
it
in the Maven SCM plugin?
I've tried using the Maven encryption guide
(http://maven.apache.org/guides/mini/guide-encryption.html) which works well
for
encrypting Maven repository credentials. The problem is that you can't (from
what I've seen) reference the id for a server in the Maven SCM plugin.
Here's
an example of what I'd like to see in the POM:
org.apache.maven.plugins
maven-scm-plugin
kurt.tometich
{encrypted password here}
Any ideas of how to do this would be welcome. Thanks in advance.
Kurt
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Project and external file Deployment?
Hi, I was just wondering how I can configure Maven to deploy a whole project, e.g. a web application that needs other war files to also be deployed on the server as well as probable configuration files. Is it possible to copy other projects jar/war files together with the projects war into a web container e.g.? Image I have several web applications that interact with each other but which are not contained in a single war file. I could use maven to deploy each file separately. But maybe there are 3rd party war files which I like to deploy together with my files. Can I somehow specify files that belong to the project that I like to be deployed? Thanks, Jan
RE: Hibernate 3 Plugin
Hello Neil I think the problem is it doesn't find the persistence.xml because it isn't the standard META-INF/persistence.xml as per the hibernatools documentation: https://www.hibernate.org/hib_docs/tools/reference/en/html/ant.html jpaconfiguration will simply just try and auto-configure itself based on the available classpath, e.g. look for META-INF/persistence.xml. Try moving your persistence.xml to the META-INF directory and try it again Regards Johann Reyes -Original Message- From: Neil Chaudhuri [mailto:nchaudh...@potomacfusion.com] Sent: Thursday, August 13, 2009 2:26 PM To: users@maven.apache.org Subject: Hibernate 3 Plugin I am using Maven with JPA/Hibernate, and I would like to generate a DDL file to give to my DBAs. I am using the Hibernate 3 Maven plugin to do this. However, I keep getting the error [ERROR] Persistence unit not found: 'myapp'. Here is the relevant portion of the POM: plugin groupIdorg.codehaus.mojo/groupId artifactIdhibernate3-maven-plugin/artifactId version2.2/version configuration components component namehbm2ddl/name implementationjpaconfiguration/implementation /component /components componentProperties createtrue/create dropfalse/drop exportfalse/export configurationfile/target/classes/persistence.xml/configurationfile persistenceunitmyapp/persistenceunit outputfilenamemyapp.sql/outputfilename formattrue/format /componentProperties /configuration dependencies dependency groupIdcom.oracle.jdbc/groupId artifactIdojdbc6/artifactId version11.1.0.7.0/version /dependency /dependencies /plugin Here is the persistence.xml founf in src/main/resources as well as target/classes: persistence-unit name=myapp transaction-type=RESOURCE_LOCAL providerorg.hibernate.ejb.HibernatePersistence/provider jta-data-sourceMYAPP_DS/jta-data-source properties property name=hibernate.show_sql value=true/ property name=hibernate.format_sql value=true/ property name=hibernate.dialect value=org.hibernate.dialect.Oracle10gDialect/ property name=hibernate.cache.provider_class value=org.hibernate.cache.HashtableCacheProvider/ /properties /persistence-unit The files are where they are supposed to be, and surely the plugin knows to look in the target folder for everything. I would appreciate any insight into what the issue might be. Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Project and external file Deployment?
what about using an EAR? LieGrue, strub - Original Message From: Jan Wedel jan.we...@ettex.de To: users@maven.apache.org Sent: Friday, August 14, 2009 11:26:03 AM Subject: Project and external file Deployment? Hi, I was just wondering how I can configure Maven to deploy a whole project, e.g. a web application that needs other war files to also be deployed on the server as well as probable configuration files. Is it possible to copy other projects jar/war files together with the projects war into a web container e.g.? Image I have several web applications that interact with each other but which are not contained in a single war file. I could use maven to deploy each file separately. But maybe there are 3rd party war files which I like to deploy together with my files. Can I somehow specify files that belong to the project that I like to be deployed? Thanks, Jan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
beginner problem
Hi thanks for giving the prompt reply for my first question. Here my another problem is If I run the normal command like 'mvn archetype:create' I am getting the following console output which is showing unable to create the project. See the following one. I am running this command in offline mode as I don't have the internet connection. F:\Ravi\sammvn archetype:create -DgroupId=org.sonatype.mavenbook.ch03 -DartifactId=simple -DpackageName=org.sonatype.mavenbook --offline [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-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: Fri Aug 14 14:57:41 GMT+05:30 2009 [INFO] Final Memory: 1M/2M [INFO] F:\Ravi\sam Where as if I run this command differently while giving the settings.xml as an argument it is perfectly creating. What is the problem? Is there any other way to give this setting file as an argument like setting in classpath? But I have already mentioned in path but it is not resolving. F:\Ravi\sammvn -Dorg.apache.maven.global-settings=.m2/settings.xml archetype:create -DgroupId=org.sonatype.mavenbook.ch03 -DartifactId=simple -Dpacka geName=org.sonatype.mavenbook [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:create] (aggregator-style) [INFO] [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:create] [WARNING] This goal is deprecated. Please use mvn archetype:generate instead [INFO] artifact org.apache.maven.archetypes:maven-archetype-quickstart: checking for updates from central [INFO] [INFO] Using following parameters for creating OldArchetype: maven-archetype-quickstart:RELEASE [INFO] [INFO] Parameter: groupId, Value: org.sonatype.mavenbook.ch03 [INFO] Parameter: packageName, Value: org.sonatype.mavenbook [INFO] Parameter: basedir, Value: F:\Ravi\sam [INFO] Parameter: package, Value: org.sonatype.mavenbook [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] Parameter: artifactId, Value: simple [INFO] * End of debug info from resources from generated POM *** [INFO] OldArchetype created in dir: F:\Ravi\sam\simple [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 6 seconds [INFO] Finished at: Fri Aug 14 14:40:57 GMT+05:30 2009 [INFO] Final Memory: 8M/15M [INFO] Where as my .m2/settings.xml file is following one settings xmlns=http://maven.apache.org/settings/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd; localRepository/.m2/repository/localRepository offlinetrue/offline proxies proxy activetrue/active protocolhttp/protocol port3128/port host10.123.123.157/host /proxy /proxies servers /servers mirrors /mirrors profiles /profiles /settings By seeing the above two stacktraces I come to know (The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found ) then why it is creating the project in second scenario ? And one more thing is after successfully creating the project by giving the settings.xml file as an argument I tried to compile the project. Here it is raising some more problems. F:\Ravi\sammvn compile --offline [INFO] NOTE: Maven is executing in offline mode.
AW: RE: AW: Re: AW: Re: Maven for Non-Java Projects
Hi, I recently did not receive any Mails from the list..so I'm answering now. Vincent, this sounds very interesting! Yesterday, I tried hours to compile the example program bundled with the nar plugin and got strange errors about not having specified any include files...but the project does not contain include files at all because its a hello world... I was really frustrated and almost gave up until I read your post. Could you probably provide your version with the applied patches or at least the patches themselves? This would be really helpful to get it working. I also need to apply some patches for enabling embedded support. Rémy, Do you also use it for Perl? Perl also uses a lot of libraries (.pm files e.g.) and even perl make scripts sometimes. I couldn't find any maven plugin supporting perl projects. Do you have any idea if this is possible? Jan -Ursprüngliche Nachricht- Von: Jan Wedel Gesendet: Dienstag, 11. August 2009 16:28 An: users@maven.apache.org Betreff: AW: RE: AW: Re: AW: Re: Maven for Non-Java Projects As stated before by John, There is a PHP plugin. Moreover, I found a .NET plugin. For C, Fortran and C++, the NAR plugin can be used. The maven-native-plugin indeed seems to be discontinued and on the maven nar website, they say they created their plugin because the maven native plugin wasn't flexible enough. As far as I can say, their procedure sound very interesting. They bundle Header and object files and POM in a zip file called .nar which can be used as any Java artifact in the repository. Thats the theory. But I'd like to hear anybody who really used it, because most often, it's the small things that matter the most meaning that some small issues / missing features could have a drastic influence on the whole project workflow/ building process. -Ursprüngliche Nachricht- Von: Martin Gainty [mailto:mgai...@hotmail.com] Gesendet: Dienstag, 11. August 2009 15:37 An: users@maven.apache.org Betreff: RE: AW: Re: AW: Re: Maven for Non-Java Projects Since PHP,Python and even Perl (mod form or exe) are library or executable binaries the only solution I can envision is to pass control to maven-antrun-plugin and have build.xml spawn some manner of make or c compiler for these modules here is an example maven-antrun-plugin calling a build.xml with a specific target http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html i would be interested in hearing other solutions *gruss* Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Tue, 11 Aug 2009 13:34:02 +0200 From: jan.we...@ettex.de To: users@maven.apache.org Subject: AW: Re: AW: Re: Maven for Non-Java Projects Thanks John! But our aim is not to use Maven at any cost. We are searching for a tool that can be used on many platforms and compilers. Sometime we have one project ported to different languages and sometimes we have have a project that is composed of several sub-projects in different languages. So, we are searching for a tool that can be triggered to build such a heterogeneous project. So, still the question is: Does Maven provide enough flexibility to support such a development environment as explained? Either by existing plug-in or by providing the necessary framework and structures to allow us writing own plugins. What I mean is, are there any limitation in maven that would prevent writing and/or using native plugins while maintaining the terminology and structure of artifacts, groups, dependencies, repositories etc. together with C, Python and other languages. Thanks, Jan -Ursprüngliche Nachricht- Von: John Dunlap [mailto:john.dun...@exceter.com] Gesendet: Dienstag, 11. August 2009 13:18 An: Maven Users List Betreff: Re: AW: Re: Maven for Non-Java Projects You could always try using something like the maven exec-maven-plugin to execute CMake (which supports generating project files
animal-sniffer and cobertura issues
Hi, I'm testing animal-sniffer with my build. All was fine until I tried to generate the site. First, it seems that animal-sniffer is executed a lot of times during site generation. And worst is it is failing on Cobertura instrumented classes : [INFO] Checking unresolved references to org.jvnet.animal-sniffer:java1.4:1.0 [ERROR] Undefined reference: net/sourceforge/cobertura/coveragedata/ProjectData.getGlobalProjectData()Lnet/sourceforge/cobertura/coveragedata/ProjectData; in D:\Projects\X\myproject\x-myproject-webapp\target\generated-classes\cobertura\com\xx\myproject\action\ActionListAction.class ... ...(1 error for each and every class of my software) ... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Signature errors found. Verify them and put @IgnoreJRERequirement on them. Do you have any solution? Thanks Julien
Re: beginner problem
Hello Sammaiah, You have started maven in offline mode in first case. And maven wrote about it in log. Reason: System is offline. ... *NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible.* When you start maven firstly, it's download some parts of itself from net. But you have run it in oflline mode. You you have caught errors.. *--offline* - exclude this key from command line and this tag *offlinetrue/offline* from settings.xml. Be careful, use offline mode only if you are fully sure, that you have all what you need in your local repository, Aleksey. Sammaiah Nagapuri ?: Hi thanks for giving the prompt reply for my first question. Here my another problem is If I run the normal command like 'mvn archetype:create' I am getting the following console output which is showing unable to create the project. See the following one. I am running this command in offline mode as I don't have the internet connection. F:\Ravi\sammvn archetype:create -DgroupId=org.sonatype.mavenbook.ch03 -DartifactId=simple -DpackageName=org.sonatype.mavenbook --offline [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-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: Fri Aug 14 14:57:41 GMT+05:30 2009 [INFO] Final Memory: 1M/2M [INFO] F:\Ravi\sam Where as if I run this command differently while giving the settings.xml as an argument it is perfectly creating. What is the problem? Is there any other way to give this setting file as an argument like setting in classpath? But I have already mentioned in path but it is not resolving. F:\Ravi\sammvn -Dorg.apache.maven.global-settings=.m2/settings.xml archetype:create -DgroupId=org.sonatype.mavenbook.ch03 -DartifactId=simple -Dpacka geName=org.sonatype.mavenbook [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:create] (aggregator-style) [INFO] [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:create] [WARNING] This goal is deprecated. Please use mvn archetype:generate instead [INFO] artifact org.apache.maven.archetypes:maven-archetype-quickstart: checking for updates from central [INFO] [INFO] Using following parameters for creating OldArchetype: maven-archetype-quickstart:RELEASE [INFO] [INFO] Parameter: groupId, Value: org.sonatype.mavenbook.ch03 [INFO] Parameter: packageName, Value: org.sonatype.mavenbook [INFO] Parameter: basedir, Value: F:\Ravi\sam [INFO] Parameter: package, Value: org.sonatype.mavenbook [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] Parameter: artifactId, Value: simple [INFO] * End of debug info from resources from generated POM *** [INFO] OldArchetype created in dir: F:\Ravi\sam\simple [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 6 seconds [INFO] Finished at: Fri Aug 14 14:40:57 GMT+05:30 2009 [INFO] Final Memory: 8M/15M [INFO] Where as my .m2/settings.xml file is following one settings xmlns=http://maven.apache.org/settings/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd; localRepository/.m2/repository/localRepository offlinetrue/offline proxies proxy activetrue/active
Re: Project and external file Deployment?
Do you want to do this as part of your integration tests? Or is it for the actual deployment (to prod servers)? In the latter case Maven would not be the typical tool as it is a build tool. In the first case there are several plugins, one being the generic cargo plugin (http://cargo.codehaus.org/Maven2+plugin). But there are also server specific ones. In general, to deploy other artifacts than the one from the project at hands, they should be avalaible (already built) in a repo (such as your corporate repo). /Anders On Fri, Aug 14, 2009 at 11:26, Jan Wedel jan.we...@ettex.de wrote: Hi, I was just wondering how I can configure Maven to deploy a whole project, e.g. a web application that needs other war files to also be deployed on the server as well as probable configuration files. Is it possible to copy other projects jar/war files together with the projects war into a web container e.g.? Image I have several web applications that interact with each other but which are not contained in a single war file. I could use maven to deploy each file separately. But maybe there are 3rd party war files which I like to deploy together with my files. Can I somehow specify files that belong to the project that I like to be deployed? Thanks, Jan
javadoc plugin aggregation woes
Hi all, My first maven project, plain JavaSE. I want to build javadoc jars, independent of any site - I'm trying to get that working as well, but for now I'm considering them separately. For organisation purposes, I've split my work into several projects, which I've now made modules of a parent. Creating a source bundle with source:aggregate (having also done source:jar-no-fork on the modules) was easy. Now I want to create a combined javadoc bundle, and that's not proving easy. I've successfully got javadoc:jar running on the modules. However, javadoc:aggregate-jar on the parent does nothing, as far as I can tell. Now, since I'm using m2eclipse, I can happily create a javadoc by running the eclipse javadoc builder over multiple projects, but I'd rather integrate with maven if at all possible. Anyone have any ideas? -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: Re: Project and external file Deployment?
Thanks, I think the Cargo plug-in looks quite like what I was looking for! -Ursprüngliche Nachricht- Von: Anders Hammar [mailto:and...@hammar.net] Gesendet: Freitag, 14. August 2009 12:51 An: Maven Users List Betreff: Re: Project and external file Deployment? Do you want to do this as part of your integration tests? Or is it for the actual deployment (to prod servers)? In the latter case Maven would not be the typical tool as it is a build tool. In the first case there are several plugins, one being the generic cargo plugin (http://cargo.codehaus.org/Maven2+plugin). But there are also server specific ones. In general, to deploy other artifacts than the one from the project at hands, they should be avalaible (already built) in a repo (such as your corporate repo). /Anders On Fri, Aug 14, 2009 at 11:26, Jan Wedel jan.we...@ettex.de wrote: Hi, I was just wondering how I can configure Maven to deploy a whole project, e.g. a web application that needs other war files to also be deployed on the server as well as probable configuration files. Is it possible to copy other projects jar/war files together with the projects war into a web container e.g.? Image I have several web applications that interact with each other but which are not contained in a single war file. I could use maven to deploy each file separately. But maybe there are 3rd party war files which I like to deploy together with my files. Can I somehow specify files that belong to the project that I like to be deployed? Thanks, Jan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: RE: AW: Re: AW: Re: Maven for Non-Java Projects
Hi Jan, Rémy, Do you also use it for Perl? Perl also uses a lot of libraries (.pm files e.g.) and even perl make scripts sometimes. I couldn't find any maven plugin supporting perl projects. Do you have any idea if this is possible? No we haven't try it and I am not aware about perl plugin. As I don't really know perl I can't say if it possible/difficult or not to create a perl plugin. Sorry. Rémy
Broken by design
Hi, while I was searching for a Perl plugin for maven, I found this link in interesting discussion: http://fishbowl.pastiche.org/2007/12/20/maven_broken_by_design/ Since this is quite old, I guess this was already discussed on this list. I am interested if there are solutions for the mentioned problems. At first maven looks like an attractive girl. But I've got a little idea that this girls is gonna get real bitchy once put a ring on her finger and live together. What I'm trying to say is, the idea behind maven is promising. But maybe you end up dealing with maven repository and resolution issues as well as plugin version issues instead of working on your project. I can remember other colleagues telling my Damn, I spend the last day resolving a maven problem I especially have concerns about the reliability and repeatability issues. Transitive resolving is a really helpful, but it would be nice if you could do it just once and then have everything on your internal repository, frozen within a version and not having maven touching it again... And if you need to reproduce an earlier version, you just need to check out that particular version and have everything together instead of maven starting to search for plugins again. Any comment is appreciated! Jan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
This works for us, try this in your parent pom: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version executions execution idattach-javadocs/id goals goaljar/goal /goals /execution /executions /plugin /plugins /build reporting ... plugin !--Provides javadocs-- groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version configuration aggregatetrue/aggregate /configuration /plugin /reporting -Dave On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk wrote: Hi all, My first maven project, plain JavaSE. I want to build javadoc jars, independent of any site - I'm trying to get that working as well, but for now I'm considering them separately. For organisation purposes, I've split my work into several projects, which I've now made modules of a parent. Creating a source bundle with source:aggregate (having also done source:jar-no-fork on the modules) was easy. Now I want to create a combined javadoc bundle, and that's not proving easy. I've successfully got javadoc:jar running on the modules. However, javadoc:aggregate-jar on the parent does nothing, as far as I can tell. Now, since I'm using m2eclipse, I can happily create a javadoc by running the eclipse javadoc builder over multiple projects, but I'd rather integrate with maven if at all possible. Anyone have any ideas? -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Broken by design
I can remember other colleagues telling my Damn, I spend the last day resolving a maven problem Before Maven, I would spend just as much, if not more time, fighting with builds. As for the link you provided, I think there is some truth to it. But in my view the pros far out way the cons. So ya sure Maven may need to download artifacts a lot. But because everything is modular, very rarely do you need to compile a lot of code. This greatly speeds up build times. So overall, we have seen our build times actually decrease when we went to Maven, not increase. And having a local repo manager does solve most of the issues discussed on that blog (in my view anyway). Contrary to what the author states. We have had some problems with build reproduciblity though. But it was because of downloading artifacts. I believe, although I have not confirmed, is that a plugin is behaving differently on Windows than it does on Linux. But I wouldn't say this is a core Maven issue and conclude that Maven is broken by design. I would say the design is very sound. My 2 cents... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Broken by design
We have had some problems with build reproduciblity though. But it was because of downloading artifacts. Sorry... I meant so say here... It was NOT because of downloading artifacts... Bah. Friday morning... Brain is still not in gear ;-). - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: animal-sniffer and cobertura issues
bind animal sniffer to a phase after test, that way it will not be executed in the forked lifecycle 2009/8/14 Julien HENRY henr...@yahoo.fr: Hi, I'm testing animal-sniffer with my build. All was fine until I tried to generate the site. First, it seems that animal-sniffer is executed a lot of times during site generation. And worst is it is failing on Cobertura instrumented classes : [INFO] Checking unresolved references to org.jvnet.animal-sniffer:java1.4:1.0 [ERROR] Undefined reference: net/sourceforge/cobertura/coveragedata/ProjectData.getGlobalProjectData()Lnet/sourceforge/cobertura/coveragedata/ProjectData; in D:\Projects\X\myproject\x-myproject-webapp\target\generated-classes\cobertura\com\xx\myproject\action\ActionListAction.class ... ...(1 error for each and every class of my software) ... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Signature errors found. Verify them and put @IgnoreJRERequirement on them. Do you have any solution? Thanks Julien - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
you might also want to separate aggregation from inheritance and have the parent pom depend on the child poms, thereby ensuring that the build plan is correct. 2009/8/14 David Hoffer dhoff...@gmail.com: This works for us, try this in your parent pom: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version executions execution idattach-javadocs/id goals goaljar/goal /goals /execution /executions /plugin /plugins /build reporting ... plugin !--Provides javadocs-- groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version configuration aggregatetrue/aggregate /configuration /plugin /reporting -Dave On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk wrote: Hi all, My first maven project, plain JavaSE. I want to build javadoc jars, independent of any site - I'm trying to get that working as well, but for now I'm considering them separately. For organisation purposes, I've split my work into several projects, which I've now made modules of a parent. Creating a source bundle with source:aggregate (having also done source:jar-no-fork on the modules) was easy. Now I want to create a combined javadoc bundle, and that's not proving easy. I've successfully got javadoc:jar running on the modules. However, javadoc:aggregate-jar on the parent does nothing, as far as I can tell. Now, since I'm using m2eclipse, I can happily create a javadoc by running the eclipse javadoc builder over multiple projects, but I'd rather integrate with maven if at all possible. Anyone have any ideas? -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
sorry i'll correct that... you might also want to separate aggregation from inheritance and have the aggregator pom depend on the child poms, thereby ensuring that the build plan is correct. 2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com: you might also want to separate aggregation from inheritance and have the parent pom depend on the child poms, thereby ensuring that the build plan is correct. 2009/8/14 David Hoffer dhoff...@gmail.com: This works for us, try this in your parent pom: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version executions execution idattach-javadocs/id goals goaljar/goal /goals /execution /executions /plugin /plugins /build reporting ... plugin !--Provides javadocs-- groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version configuration aggregatetrue/aggregate /configuration /plugin /reporting -Dave On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk wrote: Hi all, My first maven project, plain JavaSE. I want to build javadoc jars, independent of any site - I'm trying to get that working as well, but for now I'm considering them separately. For organisation purposes, I've split my work into several projects, which I've now made modules of a parent. Creating a source bundle with source:aggregate (having also done source:jar-no-fork on the modules) was easy. Now I want to create a combined javadoc bundle, and that's not proving easy. I've successfully got javadoc:jar running on the modules. However, javadoc:aggregate-jar on the parent does nothing, as far as I can tell. Now, since I'm using m2eclipse, I can happily create a javadoc by running the eclipse javadoc builder over multiple projects, but I'd rather integrate with maven if at all possible. Anyone have any ideas? -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be
project-{a,b,c,d,e,}, the modules of project-master would be the same,
and project-{a,b,c,d,e,complete} would declare project-master as their
parent. That make sense?
Sam
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer dhoff...@gmail.com:
This works for us, try this in your parent pom:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects, which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules) was
easy. Now I want to create a combined javadoc bundle, and that's not proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by running
the eclipse javadoc builder over multiple projects, but I'd rather integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
David Hoffer wrote: This works for us, try this in your parent pom: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version executions execution idattach-javadocs/id goals goaljar/goal /goals /execution /executions /plugin /plugins /build reporting ... plugin !--Provides javadocs-- groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version configuration aggregatetrue/aggregate ^^^ /configuration /plugin /reporting Isn't that deprecated now? Just using the aggregate-jar target does no good... I'll try using this. Maybe using the older version also helps. -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
2009/8/14 Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk:
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
I would make project-complete the project with the modules section
and add project-master as a child of project-complete
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be project-{a,b,c,d,e,},
the modules of project-master would be the same, and
project-{a,b,c,d,e,complete} would declare project-master as their parent.
That make sense?
Sam
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer dhoff...@gmail.com:
This works for us, try this in your parent pom:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
So the one doing the aggregating would have the modules section *and*
have the dependencies? When I've done that and set the parent in each
module, it's complained of cyclic dependencies.
Stephen Connolly wrote:
2009/8/14 Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk:
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
I would make project-complete the project with the modules section
and add project-master as a child of project-complete
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be project-{a,b,c,d,e,},
the modules of project-master would be the same, and
project-{a,b,c,d,e,complete} would declare project-master as their parent.
That make sense?
Sam
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer dhoff...@gmail.com:
This works for us, try this in your parent pom:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
so to summarize:
/project-complete
+- project-parent
+- project-a
+- project-b
...
\- project-e
project-complete has the following
project
parent
artifactIdproject-parent/artifactId
/parent
artifactIdproject-___/artifactId
modules
moduleproject-parent/module
moduleproject-a/module
moduleproject-b/module
...
moduleproject-e/module
/modules
/project
project-parent has no parent section... or at least does not
reference project-complete
project-a, project-b, ..., project-e have the following
project
parent
artifactIdproject-parent/artifactId
/parent
artifactIdproject-___/artifactId
/project
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/8/14 Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk:
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
I would make project-complete the project with the modules section
and add project-master as a child of project-complete
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be project-{a,b,c,d,e,},
the modules of project-master would be the same, and
project-{a,b,c,d,e,complete} would declare project-master as their parent.
That make sense?
Sam
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer dhoff...@gmail.com:
This works for us, try this in your parent pom:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
SEPARATE aggregation FROM inheritance... otherwise you will get cyclic
2009/8/14 Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk:
So the one doing the aggregating would have the modules section *and* have
the dependencies? When I've done that and set the parent in each module,
it's complained of cyclic dependencies.
Stephen Connolly wrote:
2009/8/14 Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk:
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
I would make project-complete the project with the modules section
and add project-master as a child of project-complete
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be
project-{a,b,c,d,e,},
the modules of project-master would be the same, and
project-{a,b,c,d,e,complete} would declare project-master as their
parent.
That make sense?
Sam
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer dhoff...@gmail.com:
This works for us, try this in your parent pom:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can
tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
Ah. Exactly what I meant, but with the names complete and parent the
other way around. With the names your way around, the source and javadoc
aggregators would go in where?
Stephen Connolly wrote:
so to summarize:
/project-complete
+- project-parent
+- project-a
+- project-b
...
\- project-e
project-complete has the following
project
parent
artifactIdproject-parent/artifactId
/parent
artifactIdproject-___/artifactId
modules
moduleproject-parent/module
moduleproject-a/module
moduleproject-b/module
...
moduleproject-e/module
/modules
/project
project-parent has no parent section... or at least does not
reference project-complete
project-a, project-b, ..., project-e have the following
project
parent
artifactIdproject-parent/artifactId
/parent
artifactIdproject-___/artifactId
/project
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/8/14 Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk:
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
I would make project-complete the project with the modules section
and add project-master as a child of project-complete
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be project-{a,b,c,d,e,},
the modules of project-master would be the same, and
project-{a,b,c,d,e,complete} would declare project-master as their parent.
That make sense?
Sam
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer dhoff...@gmail.com:
This works for us, try this in your parent pom:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
my understanding of aggregate is that it has to go where the modules
( by implication the dependencies) are
2009/8/14 Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk:
Ah. Exactly what I meant, but with the names complete and parent the other
way around. With the names your way around, the source and javadoc
aggregators would go in where?
Stephen Connolly wrote:
so to summarize:
/project-complete
+- project-parent
+- project-a
+- project-b
...
\- project-e
project-complete has the following
project
parent
artifactIdproject-parent/artifactId
/parent
artifactIdproject-___/artifactId
modules
moduleproject-parent/module
moduleproject-a/module
moduleproject-b/module
...
moduleproject-e/module
/modules
/project
project-parent has no parent section... or at least does not
reference project-complete
project-a, project-b, ..., project-e have the following
project
parent
artifactIdproject-parent/artifactId
/parent
artifactIdproject-___/artifactId
/project
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/8/14 Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk:
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
I would make project-complete the project with the modules section
and add project-master as a child of project-complete
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be
project-{a,b,c,d,e,},
the modules of project-master would be the same, and
project-{a,b,c,d,e,complete} would declare project-master as their
parent.
That make sense?
Sam
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer dhoff...@gmail.com:
This works for us, try this in your parent pom:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well,
but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the
modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can
tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands,
Re: javadoc plugin aggregation woes
project
parent
artifactIdproject-parent/artifactId
/parent
artifactIdproject-___/artifactId
modules
moduleproject-parent/module
moduleproject-a/module
moduleproject-b/module
...
moduleproject-e/module
/modules
dependencies
dependency
artifactIdproject-a/artifactId
/dependency
dependency
artifactIdproject-b/artifactId
/dependency
...
dependency
artifactIdproject-e/artifactId
/dependency
/dependencies
build
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
inheritedfalse/inherited !-- not strictly speaking
necesaary, but best practice as we are binding an aggregator goal --
...
/plugin
/plugins
/build
/project
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
my understanding of aggregate is that it has to go where the modules
( by implication the dependencies) are
2009/8/14 Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk:
Ah. Exactly what I meant, but with the names complete and parent the other
way around. With the names your way around, the source and javadoc
aggregators would go in where?
Stephen Connolly wrote:
so to summarize:
/project-complete
+- project-parent
+- project-a
+- project-b
...
\- project-e
project-complete has the following
project
parent
artifactIdproject-parent/artifactId
/parent
artifactIdproject-___/artifactId
modules
moduleproject-parent/module
moduleproject-a/module
moduleproject-b/module
...
moduleproject-e/module
/modules
/project
project-parent has no parent section... or at least does not
reference project-complete
project-a, project-b, ..., project-e have the following
project
parent
artifactIdproject-parent/artifactId
/parent
artifactIdproject-___/artifactId
/project
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/8/14 Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk:
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
I would make project-complete the project with the modules section
and add project-master as a child of project-complete
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be
project-{a,b,c,d,e,},
the modules of project-master would be the same, and
project-{a,b,c,d,e,complete} would declare project-master as their
parent.
That make sense?
Sam
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer dhoff...@gmail.com:
This works for us, try this in your parent pom:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well,
but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the
modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can
tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any
Re: javadoc plugin aggregation woes
damn copy-pase project parent artifactIdproject-parent/artifactId /parent artifactIdproject-complete/artifactId modules moduleproject-parent/module moduleproject-a/module moduleproject-b/module ... moduleproject-e/module /modules dependencies dependency artifactIdproject-a/artifactId /dependency dependency artifactIdproject-b/artifactId /dependency ... dependency artifactIdproject-e/artifactId /dependency /dependencies build plugins plugin artifactIdmaven-javadoc-plugin/artifactId inheritedfalse/inherited !-- not strictly speaking necesary, but best practice as we are binding an aggregator goal -- ... /plugin /plugins /build /project - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
Stephen Connolly wrote:
my understanding of aggregate is that it has to go where the modules
( by implication the dependencies) are
Ah, I see! I got the separation slightly wrong. I've got you now, that's
great. So everything is a module of complete, and a dependency of it,
but a-e declare parent to be their parent. Good.
2009/8/14 Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk:
Ah. Exactly what I meant, but with the names complete and parent the other
way around. With the names your way around, the source and javadoc
aggregators would go in where?
Stephen Connolly wrote:
so to summarize:
/project-complete
+- project-parent
+- project-a
+- project-b
...
\- project-e
project-complete has the following
project
parent
artifactIdproject-parent/artifactId
/parent
artifactIdproject-___/artifactId
modules
moduleproject-parent/module
moduleproject-a/module
moduleproject-b/module
...
moduleproject-e/module
/modules
/project
project-parent has no parent section... or at least does not
reference project-complete
project-a, project-b, ..., project-e have the following
project
parent
artifactIdproject-parent/artifactId
/parent
artifactIdproject-___/artifactId
/project
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
2009/8/14 Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk:
Stephen Connolly wrote:
sorry i'll correct that...
you might also want to separate aggregation from inheritance and have
the aggregator pom depend on the child poms, thereby ensuring that the
build plan is correct.
Yeah, I'm feeling that... my plan now is to have the modules, say:
project-a
project-b
project-c
project-d
project-e
with module/parent relationship with
I would make project-complete the project with the modules section
and add project-master as a child of project-complete
project-master
and then aggregate in
project-complete
So then, the dependencies of project-complete would be
project-{a,b,c,d,e,},
the modules of project-master would be the same, and
project-{a,b,c,d,e,complete} would declare project-master as their
parent.
That make sense?
Sam
2009/8/14 Stephen Connolly stephen.alan.conno...@gmail.com:
you might also want to separate aggregation from inheritance and have
the parent pom depend on the child poms, thereby ensuring that the
build plan is correct.
2009/8/14 David Hoffer dhoff...@gmail.com:
This works for us, try this in your parent pom:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well,
but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the
modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can
tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
David Hoffer wrote: This works for us, try this in your parent pom: When running this, does it need site:site running to build the javadoc before running a build that'll generate the jar? build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version executions execution idattach-javadocs/id goals goaljar/goal /goals /execution /executions /plugin /plugins /build reporting ... plugin !--Provides javadocs-- groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version configuration aggregatetrue/aggregate /configuration /plugin /reporting -Dave On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk wrote: Hi all, My first maven project, plain JavaSE. I want to build javadoc jars, independent of any site - I'm trying to get that working as well, but for now I'm considering them separately. For organisation purposes, I've split my work into several projects, which I've now made modules of a parent. Creating a source bundle with source:aggregate (having also done source:jar-no-fork on the modules) was easy. Now I want to create a combined javadoc bundle, and that's not proving easy. I've successfully got javadoc:jar running on the modules. However, javadoc:aggregate-jar on the parent does nothing, as far as I can tell. Now, since I'm using m2eclipse, I can happily create a javadoc by running the eclipse javadoc builder over multiple projects, but I'd rather integrate with maven if at all possible. Anyone have any ideas? -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: disclaimer of warranty license issue with artifact downloads?
Create a plugin and tell people that they must configure it as an 'extension', and make it do the click-through thing. On Thu, Aug 13, 2009 at 10:15 PM, Jeff Jensenjeffjen...@upstairstechnology.com wrote: Interesting option...thanks for the idea. A little bit more packaged than download the artifact, manually move it there or run this script that copies it. Still doesn't avoid the manual download though. -Original Message- From: Benson Margulies [mailto:bimargul...@gmail.com] Sent: Thursday, August 13, 2009 7:14 PM To: Maven Users List Subject: Re: disclaimer of warranty license issue with artifact downloads? Provide an installer that drops into the local user's personal repo. On Thu, Aug 13, 2009 at 8:04 PM, Wendy Smoakwsm...@gmail.com wrote: On Thu, Aug 13, 2009 at 4:06 PM, Jeff Jensenjeffjen...@upstairstechnology.com wrote: For vendors that have software downloads (freely available to anyone) from their website with a click-through disclaimer of warranty that there is no intended warranty covering the use of the product, how do we provide similar legal comfort to them to enable hosting the artifacts in Maven Central? Obviously, the licenses POM element exists with a url element to point to the license. Has this sufficed in the past? What are the options? IIRC one of the reasons we can't distribute the older Sun jars is because of their click-through license. So no, if that's a requirement, just putting a url to the license in the pom isn't sufficient. There was some talk of implementing a click-through for the Maven repo, but I don't think it ever happened. In that particular case, Sun changed the license on the newer binaries. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
No any call to install or deploy will build it. This isn't required but we do wrap the build section in a profile so we only do this on the CI system...as this takes a while. -Dave On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk wrote: David Hoffer wrote: This works for us, try this in your parent pom: When running this, does it need site:site running to build the javadoc before running a build that'll generate the jar? build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version executions execution idattach-javadocs/id goals goaljar/goal /goals /execution /executions /plugin /plugins /build reporting ... plugin !--Provides javadocs-- groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version configuration aggregatetrue/aggregate /configuration /plugin /reporting -Dave On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk wrote: Hi all, My first maven project, plain JavaSE. I want to build javadoc jars, independent of any site - I'm trying to get that working as well, but for now I'm considering them separately. For organisation purposes, I've split my work into several projects, which I've now made modules of a parent. Creating a source bundle with source:aggregate (having also done source:jar-no-fork on the modules) was easy. Now I want to create a combined javadoc bundle, and that's not proving easy. I've successfully got javadoc:jar running on the modules. However, javadoc:aggregate-jar on the parent does nothing, as far as I can tell. Now, since I'm using m2eclipse, I can happily create a javadoc by running the eclipse javadoc builder over multiple projects, but I'd rather integrate with maven if at all possible. Anyone have any ideas? -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
I might add, we do also run site-deploy which takes the javadocs and adds to the site generated. -Dave On Fri, Aug 14, 2009 at 8:21 AM, David Hoffer dhoff...@gmail.com wrote: No any call to install or deploy will build it. This isn't required but we do wrap the build section in a profile so we only do this on the CI system...as this takes a while. -Dave On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk wrote: David Hoffer wrote: This works for us, try this in your parent pom: When running this, does it need site:site running to build the javadoc before running a build that'll generate the jar? build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version executions execution idattach-javadocs/id goals goaljar/goal /goals /execution /executions /plugin /plugins /build reporting ... plugin !--Provides javadocs-- groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.5/version configuration aggregatetrue/aggregate /configuration /plugin /reporting -Dave On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack s.barnett-corm...@lancaster.ac.uk wrote: Hi all, My first maven project, plain JavaSE. I want to build javadoc jars, independent of any site - I'm trying to get that working as well, but for now I'm considering them separately. For organisation purposes, I've split my work into several projects, which I've now made modules of a parent. Creating a source bundle with source:aggregate (having also done source:jar-no-fork on the modules) was easy. Now I want to create a combined javadoc bundle, and that's not proving easy. I've successfully got javadoc:jar running on the modules. However, javadoc:aggregate-jar on the parent does nothing, as far as I can tell. Now, since I'm using m2eclipse, I can happily create a javadoc by running the eclipse javadoc builder over multiple projects, but I'd rather integrate with maven if at all possible. Anyone have any ideas? -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Sam Barnett-Cormack - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
David Hoffer wrote:
No any call to install or deploy will build it. This isn't required but we
do wrap the build section in a profile so we only do this on the CI
system...as this takes a while.
Well, that works very well for putting the aggregated javadoc on the
generated site (once I configured it to generate a site), but the
attempt to javadoc:jar gives me:
[INFO]
[INFO] Building ASN.1 Java Implementation
[INFO]task-segment: [javadoc:jar]
[INFO]
[WARNING] DEPRECATED [aggregate]: As of version 2.5, use the goals
codejavadoc
:aggregate/code and
codejavadoc:test-aggregate/code instead.
[INFO] [javadoc:jar {execution: default-cli}]
[INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
The deprecation I can deal with later, but the not-running-javadoc is a
pain.
On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
David Hoffer wrote:
This works for us, try this in your parent pom:
When running this, does it need site:site running to build the javadoc
before running a build that'll generate the jar?
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules) was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
I don't know about running from the command line...we have our CI system
auto deploy javadocs/source jars to our internal repo so IDE's get this
integrated with the binaries. This is the functionality I was looking for.
-Dave
On Fri, Aug 14, 2009 at 8:29 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
David Hoffer wrote:
No any call to install or deploy will build it. This isn't required but
we
do wrap the build section in a profile so we only do this on the CI
system...as this takes a while.
Well, that works very well for putting the aggregated javadoc on the
generated site (once I configured it to generate a site), but the attempt to
javadoc:jar gives me:
[INFO]
[INFO] Building ASN.1 Java Implementation
[INFO]task-segment: [javadoc:jar]
[INFO]
[WARNING] DEPRECATED [aggregate]: As of version 2.5, use the goals
codejavadoc
:aggregate/code and
codejavadoc:test-aggregate/code instead.
[INFO] [javadoc:jar {execution: default-cli}]
[INFO] Not executing Javadoc as the project is not a Java classpath-capable
package
The deprecation I can deal with later, but the not-running-javadoc is a
pain.
On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
David Hoffer wrote:
This works for us, try this in your parent pom:
When running this, does it need site:site running to build the javadoc
before running a build that'll generate the jar?
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
David Hoffer wrote:
I don't know about running from the command line...we have our CI system
auto deploy javadocs/source jars to our internal repo so IDE's get this
integrated with the binaries. This is the functionality I was looking for.
Well, I'm getting the website combined javadocs, and I'm getting the
per-module jar'ed javadocs, but not the combined jar'ed javadocs,
because of the message below (afaict). Anyone know how I'd bring this to
the attention of the devs of the maven-javadoc-plugin?
On Fri, Aug 14, 2009 at 8:29 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
David Hoffer wrote:
No any call to install or deploy will build it. This isn't required but
we
do wrap the build section in a profile so we only do this on the CI
system...as this takes a while.
Well, that works very well for putting the aggregated javadoc on the
generated site (once I configured it to generate a site), but the attempt to
javadoc:jar gives me:
[INFO]
[INFO] Building ASN.1 Java Implementation
[INFO]task-segment: [javadoc:jar]
[INFO]
[WARNING] DEPRECATED [aggregate]: As of version 2.5, use the goals
codejavadoc
:aggregate/code and
codejavadoc:test-aggregate/code instead.
[INFO] [javadoc:jar {execution: default-cli}]
[INFO] Not executing Javadoc as the project is not a Java classpath-capable
package
The deprecation I can deal with later, but the not-running-javadoc is a
pain.
On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
David Hoffer wrote:
This works for us, try this in your parent pom:
When running this, does it need site:site running to build the javadoc
before running a build that'll generate the jar?
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well, but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Dependency broke
After upgrading debian lenny my maven2 broke with: Exception in thread main java.lang.NoClassDefFoundError: org/codehaus/plexus/embed/Embedder (full trace etc below) Tried it with: sun java 6 openjdk java sun java 5 gjc java tried downgrading: libplexus-interactivity-api from (1.0-alpha-6-4) to (1.0-alpha-6-2) libplexus-container-default-java (1.0-alpha-9-stable-1-4) = (1.0-alpha-9-stable-1-2) libplexus-containers-java (1.0~beta3.0.7-2) = (1.0~beta2-2) which was the oldest I had availible but without any luck Anyone experienced the same issues or know how to fix it? ===Additional Info= Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages maven2 depends on: ii libcommons-cli-java 1.2-2 API for working with the command l ii libdoxia-java1.1-3 a powerful content generation fram ii libjsch-java 0.1.41-2pure Java implementation of the SS ii libjtidy-java7+svn20070309-4 a Java port of HTML Tidy, a HTML s ii libplexus-interactivity- 1.0-alpha-6-4 interactivity API for the Plexus f ii libplexus-utils-java 1:1.5.15-2 utilities for the Plexus framework ii libwagon-java1.0-beta-2-4tools to manage Maven artifacts an ii libxalan2-java 2.7.1-5 XSL Transformations (XSLT) process albat...@gara:~$ mvn -version Maven version: 2.0.9 Java version: 1.6.0_15 OS name: linux version: 2.6.30-1-686 arch: i386 Family: unix albat...@gara:~$ mvn --- constituent[0]: file:/usr/share/maven2/lib/plexus-interactivity-api.jar constituent[1]: file:/usr/share/maven2/lib/jtidy.jar constituent[2]: file:/usr/share/maven2/lib/commons-cli.jar constituent[3]: file:/usr/share/maven2/lib/xml-apis.jar constituent[4]: file:/usr/share/maven2/lib/plexus-utils.jar constituent[5]: file:/usr/share/maven2/lib/wagon-file.jar constituent[6]: file:/usr/share/maven2/lib/wagon-ssh-external.jar constituent[7]: file:/usr/share/maven2/lib/wagon-http-lightweight.jar constituent[8]: file:/usr/share/maven2/lib/jsch.jar constituent[9]: file:/usr/share/maven2/lib/wagon-ssh.jar constituent[10]: file:/usr/share/maven2/lib/maven2.jar constituent[11]: file:/usr/share/maven2/lib/doxia-sink-api.jar constituent[12]: file:/usr/share/maven2/lib/wagon-http-shared.jar constituent[13]: file:/usr/share/maven2/lib/wagon-ssh-common.jar constituent[14]: file:/usr/share/maven2/lib/wagon-provider-api.jar constituent[15]: file:/usr/share/maven2/lib/plexus-container-default.jar --- Exception in thread main java.lang.NoClassDefFoundError: org/codehaus/plexus/embed/Embedder at org.apache.maven.cli.MavenCli.main(MavenCli.java:165) 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 org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.lang.ClassNotFoundException: org.codehaus.plexus.embed.Embedder at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 9 more albat...@gara:~$ java -version java version 1.6.0_15 Java(TM) SE Runtime Environment (build 1.6.0_15-b03) Java HotSpot(TM) Server VM (build 14.1-b02, mixed mode) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Encryption for SCM password?
Is there a way to encrypt the SCM password used in configuration of the SCM plugin? I've been able to use a clear text password in my settings file, but when I try to use a Maven encrypted password it doesn't seem to be able to decrypt it on the fly. From checking out the source code for the SCM plugin it doesn't seem that this ability is there. Is this something that is on the list for an upcoming release? Kurt
Re: Encryption for SCM password?
http://www.sonatype.com/people/2009/03/maven-210-released/ * * On Fri, Aug 14, 2009 at 17:10, KURT TOMETICH boomtow...@msn.com wrote: Is there a way to encrypt the SCM password used in configuration of the SCM plugin? I've been able to use a clear text password in my settings file, but when I try to use a Maven encrypted password it doesn't seem to be able to decrypt it on the fly. From checking out the source code for the SCM plugin it doesn't seem that this ability is there. Is this something that is on the list for an upcoming release? Kurt
Re: RE : AW: RE: AW: Re: AW: Re: Maven for Non-Java Projects
Hi Vincent, Thanks for your interesting feedback. I have some more questions : - Are your patches applied in the trunk of the nar plugin ? - Is the nar plugin works well also for other phase than compile (for instance, test phase) ? If yes, which unit test framework are you using (CppUnit, CxxTest, googletest...) ? - In C++ with the same code, you need to build one binary for each platform. Worst, you need to build on each platform to generate the good binary. Agree and it's quite pain with platform dependent languages such C/C++ How do you cope with this problem ? Rémy
Re: animal-sniffer on central?
I'll request a sync of org.jvnet.* to central. Stephen Connolly wrote: This is correct, in fact we got kohsuke added as a m...@codehaus developer so that he could publish animal sniffer through the mojo.codehaus.org project (among other reasons). I know Kohsuke is has a different perspective w.r.t. whether the current policy of central (i.e. that all artifacts published to central must be self-contained on central)... and has quite ligitimately pointed out that there are a number of artifacts published on central which break this policy... We (as in Kohsuke and I) have just recently identified that the jaxws-api 2,1 pom's on central are invalid, and are missing some dependencies (see issue VCC-2 @ vcc.dev.java.net) Perhaps Kosuke might consider pushing animal sniffer to central, or even moving the animal sniffer project into mojo as it is yet another of his fabulous projects... [I only wish I was 1/10th as prolific as Kohsuke] -Stephen 2009/8/14 Julien HENRY henr...@yahoo.fr: Hi, I'm following the guide: http://maven.apache.org/guides/mini/guide-building-jdk14-on-jdk15.html The issue is I can't find animal-sniffer on the central Maven repository. I think it would be easier for users to have it on central repo. Or at least update the guide to tell that the dependency is only available on java.net repository. Thanks, Julien -- Kohsuke Kawaguchi Sun Microsystems http://weblogs.java.net/blog/kohsuke/ smime.p7s Description: S/MIME Cryptographic Signature
Maven release plugin issue
Hello everyone,
i have an issue when trying to release from the hudson CI tool. The
releasing works fine until the deployment to the repository where it
fails with the following error:
---snip---
[INFO] [INFO] [deploy:deploy {execution: default-deploy}] [INFO]
Uploading:https://maven.adorsys.de/archiva/repository/adorsys.releases//org/adorsys/mavenTestProject/1.1/mavenTestProject-1.1.war
[INFO] [INFO]
[INFO
] [ERROR] BUILD ERROR [INFO] [INFO]
[INFO
] [INFO] Error deploying artifact: java.lang.RuntimeException:
Unexpected error: java.security.InvalidAlgorithmParameterException:
the trustAnchors parameter must be non-empty [INFO] [INFO] [INFO]
[INFO
] [INFO] For more information, run Maven with the -e switch [INFO]
[INFO]
[INFO
] [INFO] Total time: 9 seconds [INFO] [INFO] Finished at: Fri Aug 14
10:31:13 GMT+01:00 2009 [INFO] [INFO] Final Memory: 34M/115M [INFO]
[INFO]
[HUDSON
] Archiving /data/apps/hudson/home/jobs/MavenTestProject/workspace/
mavenTestProject/pom.xml to /data/apps/hudson/home/jobs/
MavenTestProject/modules/org.adorsys$mavenTestProject/builds/
2009-08-14_10-30-47/archive/org.adorsys/mavenTestProject/1.1-SNAPSHOT/
pom.xml [INFO]
[ERROR
] BUILD ERROR [INFO]
[INFO
] Maven execution failed, exit code: '1'
---snap---
The weird thing is that the maven release works fine from the command
line, thus there must be some parameters that maven cant see when
called by the maven release plugin in hudson... Does anyone knows what
causes the trustAnchors issue and possibly how i can directly give
those missing parameters in the command used by the plugin in hudson?
Best regards
Edi
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Broken by design
I must admit the download the internet effect is true: everybody can see it when running Maven for the first time on a computer. Is that really a problem? IMHO no: - for personal use, this is done only once (and my ADSL line is fine) - for corporate use, a repository manager is really welcome, yes The most problematic thing in this post is build reproducibility: yes, build reproducibility is crucial, Maven team knows it. Maven builds are reproducible. But back in '2007: people discovered that build reproducibility was not free, since you had to define a version in your pom for *every* plugin, even those that you even don't imagine it's really defined in a plugin (maven-clean-plugin, for example). The myths of a 5-ligns pom.xml being sufficient, or auto-update of plugins being a kewl feature, were broken ;) Yes, this was learned the hard way by many people at that time... Later, in Maven 2.0.9, default plugins versions were added in Maven core, so that even a 5-ligns pom.xml gives a reproducible build: if you stick with a precise Maven version, you'll get the same build. It's not the best way of ensuring reproducible build, explicitely defining your plugin version is still better, but it works. For more information, see [1] Maven 2.0.9 release notes. HTH Hervé [1] http://maven.apache.org/release-notes-older.html - Mail Original - De: Todd Thiessen thies...@nortel.com À: Todd Thiessen thies...@nortel.com, Maven Users List users@maven.apache.org Envoyé: Vendredi 14 Août 2009 14h55:57 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: RE: Broken by design We have had some problems with build reproduciblity though. But it was because of downloading artifacts. Sorry... I meant so say here... It was NOT because of downloading artifacts... Bah. Friday morning... Brain is still not in gear ;-). - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Broken by design
Download from the internet was one of my biggest fear as well as versions of underying poms/jars could change which would affect reproducibilty. Additiionally, download from internet could mean you might not be able to build at all if some external site cound not be reached or someone else released a bad version of something. Happily, with a locally maintained artifacory which is configured to not automatically look for newer versions we do not have these types of problems (any more). Regards, Gord On Fri, Aug 14, 2009 at 1:26 PM, herve.bout...@free.fr wrote: I must admit the download the internet effect is true: everybody can see it when running Maven for the first time on a computer. Is that really a problem? IMHO no: - for personal use, this is done only once (and my ADSL line is fine) - for corporate use, a repository manager is really welcome, yes The most problematic thing in this post is build reproducibility: yes, build reproducibility is crucial, Maven team knows it. Maven builds are reproducible. But back in '2007: people discovered that build reproducibility was not free, since you had to define a version in your pom for *every* plugin, even those that you even don't imagine it's really defined in a plugin (maven-clean-plugin, for example). The myths of a 5-ligns pom.xml being sufficient, or auto-update of plugins being a kewl feature, were broken ;) Yes, this was learned the hard way by many people at that time... Later, in Maven 2.0.9, default plugins versions were added in Maven core, so that even a 5-ligns pom.xml gives a reproducible build: if you stick with a precise Maven version, you'll get the same build. It's not the best way of ensuring reproducible build, explicitely defining your plugin version is still better, but it works. For more information, see [1] Maven 2.0.9 release notes. HTH Hervé [1] http://maven.apache.org/release-notes-older.html - Mail Original - De: Todd Thiessen thies...@nortel.com À: Todd Thiessen thies...@nortel.com, Maven Users List users@maven.apache.org Envoyé: Vendredi 14 Août 2009 14h55:57 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: RE: Broken by design We have had some problems with build reproduciblity though. But it was because of downloading artifacts. Sorry... I meant so say here... It was NOT because of downloading artifacts... Bah. Friday morning... Brain is still not in gear ;-). - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release plugin issue
The keystore/some root certificates are not available to the JVM. Are
you running Hudson as the same user as you logged on and run the
release successfully? Also the same came up before, see
http://www.nabble.com/Plugins-Upgrades:-java.security.InvalidAlgorithmParameterException:--the-trustAnchors-parameter-must-be-non-empty-td22475522.html
it may or may not help, but would need much more info from you (your
environment, platform, deployment protocol etc.) before can give you
more concrete advice.
Kalle
On Fri, Aug 14, 2009 at 10:01 AM, Enguerrand Dibandae...@adorsys.com wrote:
Hello everyone,
i have an issue when trying to release from the hudson CI tool. The
releasing works fine until the deployment to the repository where it fails
with the following error:
---snip---
[INFO] [INFO] [deploy:deploy {execution: default-deploy}] [INFO]
Uploading:https://maven.adorsys.de/archiva/repository/adorsys.releases//org/adorsys/mavenTestProject/1.1/mavenTestProject-1.1.war [INFO]
[INFO]
[INFO] [ERROR] BUILD ERROR [INFO] [INFO]
[INFO] [INFO] Error deploying artifact: java.lang.RuntimeException:
Unexpected error: java.security.InvalidAlgorithmParameterException: the
trustAnchors parameter must be non-empty [INFO] [INFO] [INFO]
[INFO] [INFO] For more information, run Maven with the -e switch [INFO]
[INFO]
[INFO] [INFO] Total time: 9 seconds [INFO] [INFO] Finished at: Fri Aug 14
10:31:13 GMT+01:00 2009 [INFO] [INFO] Final Memory: 34M/115M [INFO] [INFO]
[HUDSON] Archiving
/data/apps/hudson/home/jobs/MavenTestProject/workspace/mavenTestProject/pom.xml
to
/data/apps/hudson/home/jobs/MavenTestProject/modules/org.adorsys$mavenTestProject/builds/2009-08-14_10-30-47/archive/org.adorsys/mavenTestProject/1.1-SNAPSHOT/pom.xml
[INFO]
[ERROR] BUILD ERROR [INFO]
[INFO] Maven execution failed, exit code: '1'
---snap---
The weird thing is that the maven release works fine from the command line,
thus there must be some parameters that maven cant see when called by the
maven release plugin in hudson... Does anyone knows what causes the
trustAnchors issue and possibly how i can directly give those missing
parameters in the command used by the plugin in hudson?
Best regards
Edi
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven repo reverse dependency search
Hi Luke. Yes, I believe this could be because the repository is still being built. However I did do a search for all dependencies with regex *scala* and it returned me 296 results including some scalaplugin related jars. I hope that's what you were looking for? You might want to try that. My search was: classes matching regex leave blank and dependencies matching regex *scala* Please do the check Using ellipsis xray from left menu bar to see what kind of searches are possible. Essentially it's pretty straightforward right now. Feel free to let me know if you need any help. Your feedback is greatly appreciated and if needed I'll update the utility/documentation. cheers, Gautam Tandon ellipsis solutions pvt. ltd. ellipsis xray - Search And Download Java Dependencies http://www.ellipsissolutions.com/xray.php Quoting Luke Patterson lukewpatter...@gmail.com: On Wed, Aug 12, 2009 at 12:35 PM, gautam.tan...@ellipsissolutions.com wrote: Try this: http://www.ellipsissolutions.com/xray.php Thanks Gautam. For an example, I tried looking for usages of maven-scala-plugin. It didn't reveal any results. Maybe your server is still caching up though. It would be nice if the search page showed some example search patterns and declared which dialect of regex it is using. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Mysterious error on site:site
At least, it's a mystery to me. To someone who knows what's going on, it
probably makes perfect sense.
The following is the end of the output of 'mvn site' on my aggregator.
I've no idea what this from parameter it's talking about is. Am I
being dumb?
[INFO]
[INFO] Building ASN.1 Syntax Modelling
[INFO]task-segment: [site]
[INFO]
[INFO] Preparing javadoc:javadoc
[INFO] No goals needed for project - skipping
[INFO] [site:site {execution: default-site}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] The parameter 'from' can not be null
[INFO]
[INFO] Trace
java.lang.IllegalArgumentException: The parameter 'from' can not be null
at
org.apache.maven.doxia.tools.DefaultSiteTool.getRelativePath(DefaultS
iteTool.java:197)
at
org.apache.maven.doxia.tools.DefaultSiteTool.populateParentMenu(Defau
ltSiteTool.java:822)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(Defau
ltSiteTool.java:540)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRen
deringContext(AbstractSiteRenderingMojo.java:226)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:117
)
at
org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
0)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.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 org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
[INFO] Total time: 26 seconds
[INFO] Finished at: Fri Aug 14 22:40:22 BST 2009
[INFO] Final Memory: 49M/254M
[INFO]
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: javadoc plugin aggregation woes
Ah, switch the aggregator to do aggregate-jar and it all works now
(afaict). Nice.
Sam Barnett-Cormack wrote:
David Hoffer wrote:
I don't know about running from the command line...we have our CI system
auto deploy javadocs/source jars to our internal repo so IDE's get this
integrated with the binaries. This is the functionality I was looking
for.
Well, I'm getting the website combined javadocs, and I'm getting the
per-module jar'ed javadocs, but not the combined jar'ed javadocs,
because of the message below (afaict). Anyone know how I'd bring this to
the attention of the devs of the maven-javadoc-plugin?
On Fri, Aug 14, 2009 at 8:29 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
David Hoffer wrote:
No any call to install or deploy will build it. This isn't required
but
we
do wrap the build section in a profile so we only do this on the CI
system...as this takes a while.
Well, that works very well for putting the aggregated javadoc on the
generated site (once I configured it to generate a site), but the
attempt to
javadoc:jar gives me:
[INFO]
[INFO] Building ASN.1 Java Implementation
[INFO]task-segment: [javadoc:jar]
[INFO]
[WARNING] DEPRECATED [aggregate]: As of version 2.5, use the goals
codejavadoc
:aggregate/code and
codejavadoc:test-aggregate/code instead.
[INFO] [javadoc:jar {execution: default-cli}]
[INFO] Not executing Javadoc as the project is not a Java
classpath-capable
package
The deprecation I can deal with later, but the not-running-javadoc is a
pain.
On Fri, Aug 14, 2009 at 7:40 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
David Hoffer wrote:
This works for us, try this in your parent pom:
When running this, does it need site:site running to build the
javadoc
before running a build that'll generate the jar?
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
executions
execution
idattach-javadocs/id
goals
goaljar/goal
/goals
/execution
/executions
/plugin
/plugins
/build
reporting
...
plugin
!--Provides javadocs--
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.5/version
configuration
aggregatetrue/aggregate
/configuration
/plugin
/reporting
-Dave
On Fri, Aug 14, 2009 at 5:00 AM, Sam Barnett-Cormack
s.barnett-corm...@lancaster.ac.uk wrote:
Hi all,
My first maven project, plain JavaSE. I want to build javadoc jars,
independent of any site - I'm trying to get that working as well,
but
for
now I'm considering them separately.
For organisation purposes, I've split my work into several projects,
which
I've now made modules of a parent. Creating a source bundle with
source:aggregate (having also done source:jar-no-fork on the
modules)
was
easy. Now I want to create a combined javadoc bundle, and that's not
proving
easy.
I've successfully got javadoc:jar running on the modules. However,
javadoc:aggregate-jar on the parent does nothing, as far as I can
tell.
Now, since I'm using m2eclipse, I can happily create a javadoc by
running
the eclipse javadoc builder over multiple projects, but I'd rather
integrate
with maven if at all possible. Anyone have any ideas?
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Mysterious error on site:site
Further note:
this happened when I added the following (host address edited):
urlhttp://host.domain.co.uk/~sdb/maven/${project.artifactId}/url
to the *parent* POM. I comment it out, it's all fine. I call this weird,
but would love an explanation.
Sam Barnett-Cormack wrote:
At least, it's a mystery to me. To someone who knows what's going on, it
probably makes perfect sense.
The following is the end of the output of 'mvn site' on my aggregator.
I've no idea what this from parameter it's talking about is. Am I
being dumb?
[INFO]
[INFO] Building ASN.1 Syntax Modelling
[INFO]task-segment: [site]
[INFO]
[INFO] Preparing javadoc:javadoc
[INFO] No goals needed for project - skipping
[INFO] [site:site {execution: default-site}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] The parameter 'from' can not be null
[INFO]
[INFO] Trace
java.lang.IllegalArgumentException: The parameter 'from' can not be null
at
org.apache.maven.doxia.tools.DefaultSiteTool.getRelativePath(DefaultS
iteTool.java:197)
at
org.apache.maven.doxia.tools.DefaultSiteTool.populateParentMenu(Defau
ltSiteTool.java:822)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(Defau
ltSiteTool.java:540)
at
org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRen
deringContext(AbstractSiteRenderingMojo.java:226)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:117
)
at
org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
0)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.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 org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
[INFO] Total time: 26 seconds
[INFO] Finished at: Fri Aug 14 22:40:22 BST 2009
[INFO] Final Memory: 49M/254M
[INFO]
--
Sam Barnett-Cormack
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Please remove me
Hi, As much as I enjoy getting the emails from this list every day, I would really like to get off of it. I've tried sending an email to users-unsubscr...@maven.apache.org, to users-unsubscribe-jnhagelb=us.ibm.com, users-unsubscribe-jnhagelberg=us.ibm.com. As far as I can tell, these emails seem to be going into a black hole. Is there a way someone can manually remove me? I believe I am subscribed using the email address jnhagelb...@us.ibm.com. Interestingly, users-h...@us.ibm.com appears to be a black hole as well. I'm wondering if our firewall and mail filters are keeping the confirmation messages from reaching me. Thanks! Jeffrey Hagelberg, Software Engineer XMeta Development IBM Software Group Phone: 978-899-2055 T/L:276-2055) Email:jnhag...@us.ibm.com
Re: Please remove me
Done. On 14/08/2009, at 6:50 PM, Jeffrey N Hagelberg wrote: Hi, As much as I enjoy getting the emails from this list every day, I would really like to get off of it. I've tried sending an email to users-unsubscr...@maven.apache.org, to users-unsubscribe-jnhagelb=us.ibm.com, users-unsubscribe-jnhagelberg=us.ibm.com. As far as I can tell, these emails seem to be going into a black hole. Is there a way someone can manually remove me? I believe I am subscribed using the email address jnhagelb...@us.ibm.com . Interestingly, users-h...@us.ibm.com appears to be a black hole as well. I'm wondering if our firewall and mail filters are keeping the confirmation messages from reaching me. Thanks! Jeffrey Hagelberg, Software Engineer XMeta Development IBM Software Group Phone: 978-899-2055 T/L:276-2055) Email:jnhag...@us.ibm.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Can I reference a dependency artifactId in a POM?
Hi,
I'm wondering if there's a way in Maven 2 to reference the artifactId
of a dependency that was used for a build. For example, I have a flex
module with:
finalName${project.artifactId}-r${build.vcs.number}/finalName
It produces an artifactId like:
my-flex-ui-1.0-SNAPSHOT-r12345
I'm trying to include the artifact id in a .html wrapper task provided
by flexmojos. The artifactId of the dependency should get injected
into the .html file created by the wrapper execution. So far the only
solution I've found is to use the stripVersiontrue/stripVersion
parameter of the dependency plugin when copying my resources over (I
actually use the flexmojos-maven-plugin for this, but it works the
same way). I'd prefer to use a more verbose artifactId for my
dependency. Here's my execution portion of the
'flexmojos-maven-plugin'
!--
This execution creates a html wrapper for my flex project (module).
The artifact
name specified in the 'swf' parameter is injected into the .html wrapper.
--
execution
idcreate-wrapper/id
goals
goalwrapper/goal
/goals
configuration
htmlNameindex/htmlName
outputDirectory${project.build.directory}/html-wrapper/outputDirectory
parameters
titleITMA Flex UI/title
applicationitma-flex-ui/application
!--
This is the artifact name (prefix) that will be
injected into the
.html wrapper that is created. I'd prefer to use
something like:
dependencies:ca.jptech.itma:itma-flex-ui:artifactId
that references the exact artifactId for the
itma-flex-ui
dependency used for this build. For example:
itma-flex-ui-1.0-SNAPSHOT-r12345
Does anything like that exist?
--
swfitma-flex-ui/swf
width100%/width
height100%/height
/parameters
/configuration
/execution
I hope that gets formatted properly. Here is the usage doc for the execution:
http://sites.sonatype.org/flexmojos/flexmojos-maven-plugin/wrapper-mojo.html
TIA for any help,
Ryan
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
