[ANN] Castor Maven plugin 2.0 released
The Mojo team is pleased to announce the release of the Castor Maven Plugin version 2.0. http://mojo.codehaus.org/castor-maven-plugin/ This is a major release that depends on Castor XML 1.3, version 1.3, and thus requires Java 5.0 and higher. To get this update, simply specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdcastor-maven-plugin/artifactId version2.0/version /plugin Please allow up to 24 hours for the new release to synchronize with the central repository. Regards, The Mojo team. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven 3 warning on dependency scope import?
I'm using maven 3.0-alpha-3 and getting a warning on use of dependencies of scope import in sub-modules although verything works as it did in 2.x. there a way to address this warning either through correcting my usage (assuming it is a valid warning) or some sort of pragma to turn off the warning? Thanks, Gabe
antrun messes up classloader ?
I have a submodule that executes antrun in order to comile some webservices files ( using weblogic web services compiler ). This works fine when I executes maven from the submodule directory. But when this submodule is called from a parent pom ( which also calls other submodules ), it complains about a missing class for the weblogic compiler. 1. Is it possible that invoking maven directly from a submodule is different from invoking it from a parent pom ( using module ) 2. Does maven use a separate classloader for each invocation of antrun ? ( Is it possible that the previous invocation of antrun affected/corrupted the classloader ) How else can this be explained. --sony
mvn site error -Port should only contain digits!
Hi, We have an error as i wrote below.It started after i added the maven-xradar-plugin to the reporting section of the pom.xml. The error log is the result of the command mvn site.It works normal on the local pc but ıt gives the error only on the server that has Bamboo(continuous integration tool) on it. What may be the cause of the problem,any ideas? Thanks, Caner, ERROR: 'javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.URI$MalformedURIException: \bamboo- home\xml-data\build-dir\TEXANBASE-SITE\texan-base-api\target\site\xradar is invalid. *Port should only contain digits!'* javax.xml.transform.TransformerException: com.sun.org.apache.xalan.internal.xsltc.TransletException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.URI$MalformedURIException: \bamboo-home\xml-data\build-dir\TEXANBASE-SITE\texan-base-api\target\site\xradar is invalid. Port should only contain digits!
pmd, checkstyle and cobertura in multi module project
I am using pmd, checkstyle and cobertura in my project. I have configured them all in my parent pom, which is get shared across all my modules. Now i want that one of the module dont use these pmd, checkstyle and cobertura checks. What configuration is required to do that. Please help me out. Thanks in advance. -- View this message in context: http://old.nabble.com/pmd%2C-checkstyle-and-cobertura-in-multi-module-project-tp26388033p26388033.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven 3.0-alpha-4 Released
The Maven team is pleased to announce the release of Apache Maven 3.0-alpha-4. Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project. You can read more here: http://maven.apache.org/ Downloads of source and binary distributions are already available on the central Maven repository and various Apache download mirrors and will be listed soon in our download section once the updated site gets synced to the live server: http://maven.apache.org/download.html A major goal of Maven 3.0 is to be compatible with existing plugins and projects designed for Maven 2.x. Users interested in testing this alpha release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x: http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html If you encounter unexpected problems while using Maven 3.0-alpha-4, please feel free to contact us via the Maven developer list: http://maven.apache.org/mail-lists.html Release Notes - Maven 2 - Version 3.0-alpha-4 ** Bug * [MNG-4361] - [regression] command line option -update-snapshots does not work * [MNG-4433] - [regression] command line option -update-snapshots does not work for parent POMs * [MNG-4436] - [regression] Singleton components can get instantianted multiple times ** Improvement * [MNG-4439] - apache-maven project should not deploy a source JAR or JAR, as it is only a distribution module ** Task * [MNG-3913] - Figure out why MavenEmbedderExampleTest fails on the grid and reenable when fixed. * [MNG-4412] - Make legacy entry points to repository system pick offline mode from session Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven not taking the latest snapshot
Hello, We have a set of products some of them depending on the others. We use Maven to control dependencies and a continuous integration server to check whether the changes are compatible. Continuous integration server first builds and deploys (to local Nexus-based repository) snapshot versions of the parent component and then builds the dependent components (which take and use the parent SNAPSHOTS). The problem is that sometimes the continuous integration server caches a SNAPSHOT artifact in the local repository and then refuses to take newer one from the remote repository. This leads to failing builds. This happens periodically, but not all the time. Deletion of the local repository on the build server helps, but it is very inconvenient. Builds are run with the -U switch, but it seems to have no effect. We're using Maven 2.1.0 on Ubuntu. Please advise what can be the cause of the problem. Thank you. -- Yury Kudryashov - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven Embedder thread safety
Hi all. I'm using Maven Embedder 3.0-alpha-2 to execute a dependency:resolve goal on a large number of POM files (several thousand), using a Java batch runtime. For performance reasons, I use a thread pool (ThreadPoolExecutor) to parallelize the calls to the embedder's execute method. However, after a quick look at the code, it seems that the execute method is not thread safe, is that correct ? Secondary question : I downloaded both maven-embedder-3.0-alpha-3.jar and maven-embedder-3.0-alpha-4.jar, and in both jars the org.apache.maven.embedder API is missing. Any reasons why ? Fabien - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven assembly: how to create an execution JAR without packing the dependencies
Hi, i'm trying to figure out how can i create a working executable JAR that has dependencies (in-house maven projects plus external lib such as Log4J). I tried using the assembly plugin by creating a jar-with-dependencies. but this creates a big JAR with all the dependencies included. I want to be able to install commons dependencies in a commons directory (/usr/lib/maven-projects/ for e.g.), and that every project that depends on them can use them. What should i do in the pom file of the infrastructure project and the project that depends on it? i've read almost all the complete maven-definite-guide, but didn't find a concise answer... thanks, -- Eyal Edri
Re: maven assembly: how to create an execution JAR without packing the dependencies
You could do this without assembly plugin. Just copy all dependencies with maven-dependency-plugin to some folder and than add this folder as classpath prefix in maven-jar-plugin. example for second part plugin artifactIdmaven-jar-plugin/artifactId configuration archive manifest mainClassyou.main.class/mainClass addClasspathtrue/addClasspath classpathPrefixlib/classpathPrefix /manifest /archive /configuration /plugin 2009/11/17 eyal edri eyal.e...@gmail.com Hi, i'm trying to figure out how can i create a working executable JAR that has dependencies (in-house maven projects plus external lib such as Log4J). I tried using the assembly plugin by creating a jar-with-dependencies. but this creates a big JAR with all the dependencies included. I want to be able to install commons dependencies in a commons directory (/usr/lib/maven-projects/ for e.g.), and that every project that depends on them can use them. What should i do in the pom file of the infrastructure project and the project that depends on it? i've read almost all the complete maven-definite-guide, but didn't find a concise answer... thanks, -- Eyal Edri -- Regards, Alexander
Re: antrun messes up classloader ?
But when this submodule is called from a parent pom ( which also calls other submodules ), it complains about a missing class for the weblogic compiler. This is a known problem in M2. Maven only loads the plugin once (the first time it sees it) in a build, and only loads plugin dependencies it sees at that time. You need to collect your Antrun plugin dependencies from the various places you have declared it and copy them so each declaration has the full set of plugin deps (or figure out which one will be seen first and just ensure it has the full set of plugin deps). Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: antrun messes up classloader ?
Thank you very much Wayne ( I didnt know that ) :
But in out case we explicitly specified teh jar files within the tasks
path id=wl-jars4compiler
fileset
dir=${project.build.directory}/weblogic10.3supportfiles
include name=**/*.jar/
/fileset
pathelement
location=${java.home}/../lib/tools.jar/
/path
taskdef name=jwsc
classname=weblogic.wsee.tools.anttasks.JwscTask
classpathref=wl-jars4compiler/
jwsc srcdir=${project.basedir}/src/main/java
destdir=${project.build.directory} verbose=true debug=on
keepGenerated=true deprecation=true keepTempFiles=true
listfiles=true classpathref=j2eejar4app fork=true
module contextPath=cramerwrapper name=cramerprotocolbroker
jws type=JAXWS
file=com/att/canopi/idis/ordermanagement/cramerinterface/impl/CramerQueryService_CramerQueryPortImpl.java
compiledWsdl=${project.build.directory}/wsdlcjar/cramerinterface-wsdlc-3.1-SNAPSHOT.jar/
jws type=JAXWS
file=com/att/canopi/idis/ordermanagement/cramerinterface/impl/FeasibilityService_FeasibilityPortImpl.java
compiledWsdl=${project.build.directory}/wsdlcjar/cramerinterface-wsdlc-3.1-SNAPSHOT.jar/
/module
/jwsc
wont this result in all teh classes being reloaded again ? ( because taskdef
forced it to reload )
--sony
On Tue, Nov 17, 2009 at 10:11 AM, Wayne Fay wayne...@gmail.com wrote:
But when this submodule is called from a parent pom ( which also calls
other
submodules ), it complains about a missing class for the weblogic
compiler.
This is a known problem in M2. Maven only loads the plugin once (the
first time it sees it) in a build, and only loads plugin dependencies
it sees at that time.
You need to collect your Antrun plugin dependencies from the various
places you have declared it and copy them so each declaration has the
full set of plugin deps (or figure out which one will be seen first
and just ensure it has the full set of plugin deps).
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Support for ditaa diagrams in APT
Not scheduled and I dont think we will make efforts to. You could always provide a module for it and create an issue. Cheers, Vincent 2009/11/17 Lóránt Pintér l.pin...@topdesk.com: Hi, Are there any plans to support ditaa ( http://ditaa.sourceforge.net/ ) in the future? It would be a nice addition to the APT format. Lóránt
Remote resource plugin doesn't work in release plugin
Hi everybody,
I have a project which uses remote-resources (hibernate mapping files).
My pom.xml
...
plugin
artifactIdmaven-remote-resources-plugin/artifactId
version1.1/version
executions
execution
goals
goalprocess/goal
/goals
configuration
resourceBundles
resourceBundlecom.myproj.sws2:sws-mapping:${sws.mapping.version}/resourceBundle
/resourceBundles
outputDirectory${project.build.directory}/outputDirectory
attachedfalse/attached
/configuration
/execution
/executions
/plugin
...
plugin
artifactIdmaven-release-plugin/artifactId
version2.0-beta-9/version
configuration
tagBasehttps://path-to-svn/tags/tagBase
/configuration
/plugin
...
When I make mvn package -Dsws.mapping.version=2.0.0 - everything's ok and
resources are resolved and downloaded also they are put to WAR file.
But when I try to release this project:
mvn release:clean release:prepare -Dsws.mapping.version=2.0.0
-Dusername=svn_user -Dpassword=svn_passwd
And I receive error:
[INFO] [INFO] [remote-resources:process {execution: default}]
[INFO] [WARNING] Unable to get resource 'com.myproj.sws2:sws-mapping:jar:null'
from repository myrep (http://maven.myrepcom:8081): While configuring wagon for
'mavuser':
Unable to apply wagon configuration.
[INFO] [INFO]
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]
[INFO] [INFO] Resources JAR cannot be found.
As you can see, resource version is unset -
'com.myproj.sws2:sws-mapping:jar:null'.
Why my property (sws.mapping.version) is null not 2.0.0 as I set in command
line ?
Thanks
maven javadoc plugin -both aggregate and non-aggregate
Hi, How can i ensure that maven-javadoc-plugin generates both the aggregate report and report for each submodule(with mvn site command) in a multi-module maven project. Thanks, Caner,
Re: antrun messes up classloader ?
But in out case we explicitly specified teh jar files within the tasks wont this result in all teh classes being reloaded again ? ( because taskdef forced it to reload ) Obviously not, or it would work properly, right? Also, I would convert those Ant scripts into proper Maven plugins. It is easier than you might initially think. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: install repeats building of dependencies
Jörg Schaible wrote: Seth Milder wrote at Dienstag, 17. November 2009 02:12: Seth Milder wrote: The WarProject1 and 2 poms also use the maven-assembly plugin, in case this matters. What happens is it builds the dependencies (Project1 and Project2), then it goes and builds WarProject1, which causes it to build the dependencies all over again, then it builds WarProject2 and again kicks off a build of all dependencies. Has anyone else experienced this? It is making my builds take an hour! For what it's worth, this does seem to be an issue with the assembly plugin. You're using the wrong goals. A very astute observance. It appears RTFM works again! What we needed was goalsingle/goal. Thanks! Seth - Jörg - 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
Problem with running antscripts in a plugin
I have a plugin that was originally written for 2.0.5, but was happy through 2.1.0. We are now trying to upgrade to 2.2.1 and it is failing miserably. I upgraded the maven.plugin.plugin to be 2.2.1 and am now able to compile the plugin. Unfortunately, it no longer works. I have two mojos that I wrote in ant. They are called through the lifecyclemapping defined in components.xml. With 2.2.1 I get the error: [INFO] Required goal not found: com.pragmatics.package-tools:maven-package-plugin:package in com.pragmatics.package-tools:maven-package-plugin:1.49-SNAPSHOT This happens for both of the mojos that were written in ant. Is there a new way of working with ant mojos in the 2.2.x series? If there is, where can I find information on it? Elizabeth Sommers Build and Release Engineer Pragmatics, Inc. 703.761.4033 www.pragmatics.com Practical. Reliable. Secure. This e-mail message, including any attachments, is intended only for the identified recipient(s). It may contain proprietary or otherwise legally protected information of Pragmatics, Inc. Any unauthorized review, use, copying, disclosure or distribution is strictly prohibited. If you have received this communication in error and are not the intended recipient, please immediately notify the sender of this message by reply e-mail and delete or otherwise destroy the e-mail, attachments, and any copies. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven not taking the latest snapshot
First, I would not use 2.1.0, use 2.0.10 or 2.2.1 instead. I'm fairly certain that -U works properly in those versions. (2.1.0 shouldn't be used at all, there were lots of issues there and we went right to 2.2.x) On Tue, Nov 17, 2009 at 6:24 AM, Yury Kudryashov ykudryas...@devexperts.com wrote: Hello, We have a set of products some of them depending on the others. We use Maven to control dependencies and a continuous integration server to check whether the changes are compatible. Continuous integration server first builds and deploys (to local Nexus-based repository) snapshot versions of the parent component and then builds the dependent components (which take and use the parent SNAPSHOTS). The problem is that sometimes the continuous integration server caches a SNAPSHOT artifact in the local repository and then refuses to take newer one from the remote repository. This leads to failing builds. This happens periodically, but not all the time. Deletion of the local repository on the build server helps, but it is very inconvenient. Builds are run with the -U switch, but it seems to have no effect. We're using Maven 2.1.0 on Ubuntu. Please advise what can be the cause of the problem. Thank you. -- Yury Kudryashov - 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: Non-unique Snapshot Deployments is not in Maven 3
This use case currently isn't covered, you're right and it's really the only reason anymore to use non unique snapshots. Bringing this over to @dev to figure out what to do. On Mon, Nov 16, 2009 at 3:41 PM, Paul Benedict pbened...@apache.org wrote: I did read the link. I thought Jason was saying Maven's metadata isn't complete -- that the classifier isn't included in the repository's description of the snapshot deployment. Paul On Mon, Nov 16, 2009 at 2:38 PM, Dan Tran dant...@gmail.com wrote: I dont have a solution, Jason however did propose an alternative metadata handling ( see the discussion link ) 0D On Mon, Nov 16, 2009 at 12:28 PM, Paul Benedict pbened...@apache.org wrote: So are you asking for the classifier to be part of the snapshot metadata? On Mon, Nov 16, 2009 at 1:57 PM, Dan Tran dant...@gmail.com wrote: of course, we must use classifier per platform. see this link for other fundamental issues when not using non-unique snapshot http://old.nabble.com/Multi-Platform-snapshots-td25295999.html -Dan On Mon, Nov 16, 2009 at 11:53 AM, Paul Benedict pbened...@apache.org wrote: If you are creating artifacts for different environments, you can use custom classifiers. I have done this. This will add a suffix to your artifacts. Paul On Mon, Nov 16, 2009 at 1:50 PM, Dan Tran dant...@gmail.com wrote: How about an alternative solution to replace that feature? -D On Sun, Nov 15, 2009 at 11:26 AM, Dan Tran dant...@gmail.com wrote: Hi According to http://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-NonuniqueSnapshotDeployments The setting uniqueVersionfalse/uniqueVersion for a distribution repository has no effect in version 3.x, snapshot artifacts will always be deployed using a timestamped version. This is a huge lost to those projects with multiple profile to build per platform specific. see http://old.nabble.com/Multi-Platform-snapshots-td25295999.html for details For my case, we might be able to go forward with maven 3 .. Can the dev team put it back? -Dan - 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 - 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: Non-unique Snapshot Deployments is not in Maven 3
Just read my own post again, For my case, we might be able to go forward with maven 3 .. should be For my case, we might NOT be able to go forward with maven 3 .. sorry about the confusion -Dan On Sun, Nov 15, 2009 at 11:26 AM, Dan Tran dant...@gmail.com wrote: Hi According to http://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-NonuniqueSnapshotDeployments The setting uniqueVersionfalse/uniqueVersion for a distribution repository has no effect in version 3.x, snapshot artifacts will always be deployed using a timestamped version. This is a huge lost to those projects with multiple profile to build per platform specific. see http://old.nabble.com/Multi-Platform-snapshots-td25295999.html for details For my case, we might be able to go forward with maven 3 .. Can the dev team put it back? -Dan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven assembly: how to create an execution JAR without packing the dependencies
can i use the 'dependency:copy-dependencieshttp://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html' goal in this project to tell it to copy all it's dependencies to the lib dir? like shown in here: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution idcopy-dependencies/id phasepackage/phase goals goalcopy-dependencies/goal /goals configuration outputDirectory/usr/local/app/outputDirectory overWriteReleasesfalse/overWriteReleases overWriteSnapshotsfalse/overWriteSnapshots overWriteIfNewertrue/overWriteIfNewer /configuration /execution /executions /plugin /plugins /build btw: (when you said classpathPrefix*lib*/classpathPrefix, does this means projectHome/lib is the classPath?) On Tue, Nov 17, 2009 at 4:51 PM, Alexander the.malk...@gmail.com wrote: You could do this without assembly plugin. Just copy all dependencies with maven-dependency-plugin to some folder and than add this folder as classpath prefix in maven-jar-plugin. example for second part plugin artifactIdmaven-jar-plugin/artifactId configuration archive manifest mainClassyou.main.class/mainClass addClasspathtrue/addClasspath classpathPrefixlib/classpathPrefix /manifest /archive /configuration /plugin 2009/11/17 eyal edri eyal.e...@gmail.com Hi, i'm trying to figure out how can i create a working executable JAR that has dependencies (in-house maven projects plus external lib such as Log4J). I tried using the assembly plugin by creating a jar-with-dependencies. but this creates a big JAR with all the dependencies included. I want to be able to install commons dependencies in a commons directory (/usr/lib/maven-projects/ for e.g.), and that every project that depends on them can use them. What should i do in the pom file of the infrastructure project and the project that depends on it? i've read almost all the complete maven-definite-guide, but didn't find a concise answer... thanks, -- Eyal Edri -- Regards, Alexander -- Eyal Edri
Re: maven assembly: how to create an execution JAR without packing the dependencies
Dont be shy, just try it. 2009/11/17 eyal edri eyal.e...@gmail.com can i use the 'dependency:copy-dependencies http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html ' goal in this project to tell it to copy all it's dependencies to the lib dir? like shown in here: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution idcopy-dependencies/id phasepackage/phase goals goalcopy-dependencies/goal /goals configuration outputDirectory/usr/local/app/outputDirectory overWriteReleasesfalse/overWriteReleases overWriteSnapshotsfalse/overWriteSnapshots overWriteIfNewertrue/overWriteIfNewer /configuration /execution /executions /plugin /plugins /build btw: (when you said classpathPrefix*lib*/classpathPrefix, does this means projectHome/lib is the classPath?) On Tue, Nov 17, 2009 at 4:51 PM, Alexander the.malk...@gmail.com wrote: You could do this without assembly plugin. Just copy all dependencies with maven-dependency-plugin to some folder and than add this folder as classpath prefix in maven-jar-plugin. example for second part plugin artifactIdmaven-jar-plugin/artifactId configuration archive manifest mainClassyou.main.class/mainClass addClasspathtrue/addClasspath classpathPrefixlib/classpathPrefix /manifest /archive /configuration /plugin 2009/11/17 eyal edri eyal.e...@gmail.com Hi, i'm trying to figure out how can i create a working executable JAR that has dependencies (in-house maven projects plus external lib such as Log4J). I tried using the assembly plugin by creating a jar-with-dependencies. but this creates a big JAR with all the dependencies included. I want to be able to install commons dependencies in a commons directory (/usr/lib/maven-projects/ for e.g.), and that every project that depends on them can use them. What should i do in the pom file of the infrastructure project and the project that depends on it? i've read almost all the complete maven-definite-guide, but didn't find a concise answer... thanks, -- Eyal Edri -- Regards, Alexander -- Eyal Edri -- Regards, Alexander
Re: maven assembly: how to create an execution JAR without packing the dependencies
i will, once i get to work tomorrow :) thanks for the help. On Tue, Nov 17, 2009 at 8:05 PM, Alexander the.malk...@gmail.com wrote: Dont be shy, just try it. 2009/11/17 eyal edri eyal.e...@gmail.com can i use the 'dependency:copy-dependencies http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html ' goal in this project to tell it to copy all it's dependencies to the lib dir? like shown in here: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution idcopy-dependencies/id phasepackage/phase goals goalcopy-dependencies/goal /goals configuration outputDirectory/usr/local/app/outputDirectory overWriteReleasesfalse/overWriteReleases overWriteSnapshotsfalse/overWriteSnapshots overWriteIfNewertrue/overWriteIfNewer /configuration /execution /executions /plugin /plugins /build btw: (when you said classpathPrefix*lib*/classpathPrefix, does this means projectHome/lib is the classPath?) On Tue, Nov 17, 2009 at 4:51 PM, Alexander the.malk...@gmail.com wrote: You could do this without assembly plugin. Just copy all dependencies with maven-dependency-plugin to some folder and than add this folder as classpath prefix in maven-jar-plugin. example for second part plugin artifactIdmaven-jar-plugin/artifactId configuration archive manifest mainClassyou.main.class/mainClass addClasspathtrue/addClasspath classpathPrefixlib/classpathPrefix /manifest /archive /configuration /plugin 2009/11/17 eyal edri eyal.e...@gmail.com Hi, i'm trying to figure out how can i create a working executable JAR that has dependencies (in-house maven projects plus external lib such as Log4J). I tried using the assembly plugin by creating a jar-with-dependencies. but this creates a big JAR with all the dependencies included. I want to be able to install commons dependencies in a commons directory (/usr/lib/maven-projects/ for e.g.), and that every project that depends on them can use them. What should i do in the pom file of the infrastructure project and the project that depends on it? i've read almost all the complete maven-definite-guide, but didn't find a concise answer... thanks, -- Eyal Edri -- Regards, Alexander -- Eyal Edri -- Regards, Alexander -- Eyal Edri
Re: maven assembly: how to create an execution JAR without packing the dependencies
http://www.sonatype.com/people/2009/08/how-to-make-an-executable-jar-in-maven/ On Tue, Nov 17, 2009 at 1:12 PM, eyal edri eyal.e...@gmail.com wrote: i will, once i get to work tomorrow :) thanks for the help. On Tue, Nov 17, 2009 at 8:05 PM, Alexander the.malk...@gmail.com wrote: Dont be shy, just try it. 2009/11/17 eyal edri eyal.e...@gmail.com can i use the 'dependency:copy-dependencies http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html ' goal in this project to tell it to copy all it's dependencies to the lib dir? like shown in here: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution idcopy-dependencies/id phasepackage/phase goals goalcopy-dependencies/goal /goals configuration outputDirectory/usr/local/app/outputDirectory overWriteReleasesfalse/overWriteReleases overWriteSnapshotsfalse/overWriteSnapshots overWriteIfNewertrue/overWriteIfNewer /configuration /execution /executions /plugin /plugins /build btw: (when you said classpathPrefix*lib*/classpathPrefix, does this means projectHome/lib is the classPath?) On Tue, Nov 17, 2009 at 4:51 PM, Alexander the.malk...@gmail.com wrote: You could do this without assembly plugin. Just copy all dependencies with maven-dependency-plugin to some folder and than add this folder as classpath prefix in maven-jar-plugin. example for second part plugin artifactIdmaven-jar-plugin/artifactId configuration archive manifest mainClassyou.main.class/mainClass addClasspathtrue/addClasspath classpathPrefixlib/classpathPrefix /manifest /archive /configuration /plugin 2009/11/17 eyal edri eyal.e...@gmail.com Hi, i'm trying to figure out how can i create a working executable JAR that has dependencies (in-house maven projects plus external lib such as Log4J). I tried using the assembly plugin by creating a jar-with-dependencies. but this creates a big JAR with all the dependencies included. I want to be able to install commons dependencies in a commons directory (/usr/lib/maven-projects/ for e.g.), and that every project that depends on them can use them. What should i do in the pom file of the infrastructure project and the project that depends on it? i've read almost all the complete maven-definite-guide, but didn't find a concise answer... thanks, -- Eyal Edri -- Regards, Alexander -- Eyal Edri -- Regards, Alexander -- Eyal Edri - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven assembly: how to create an execution JAR without packing the dependencies
Question was how make executable jar without including all dependencies in application jar but in separate folder. 2009/11/18 Brian Fox bri...@infinity.nu http://www.sonatype.com/people/2009/08/how-to-make-an-executable-jar-in-maven/ On Tue, Nov 17, 2009 at 1:12 PM, eyal edri eyal.e...@gmail.com wrote: i will, once i get to work tomorrow :) thanks for the help. On Tue, Nov 17, 2009 at 8:05 PM, Alexander the.malk...@gmail.com wrote: Dont be shy, just try it. 2009/11/17 eyal edri eyal.e...@gmail.com can i use the 'dependency:copy-dependencies http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html ' goal in this project to tell it to copy all it's dependencies to the lib dir? like shown in here: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution idcopy-dependencies/id phasepackage/phase goals goalcopy-dependencies/goal /goals configuration outputDirectory/usr/local/app/outputDirectory overWriteReleasesfalse/overWriteReleases overWriteSnapshotsfalse/overWriteSnapshots overWriteIfNewertrue/overWriteIfNewer /configuration /execution /executions /plugin /plugins /build btw: (when you said classpathPrefix*lib*/classpathPrefix, does this means projectHome/lib is the classPath?) On Tue, Nov 17, 2009 at 4:51 PM, Alexander the.malk...@gmail.com wrote: You could do this without assembly plugin. Just copy all dependencies with maven-dependency-plugin to some folder and than add this folder as classpath prefix in maven-jar-plugin. example for second part plugin artifactIdmaven-jar-plugin/artifactId configuration archive manifest mainClassyou.main.class/mainClass addClasspathtrue/addClasspath classpathPrefixlib/classpathPrefix /manifest /archive /configuration /plugin 2009/11/17 eyal edri eyal.e...@gmail.com Hi, i'm trying to figure out how can i create a working executable JAR that has dependencies (in-house maven projects plus external lib such as Log4J). I tried using the assembly plugin by creating a jar-with-dependencies. but this creates a big JAR with all the dependencies included. I want to be able to install commons dependencies in a commons directory (/usr/lib/maven-projects/ for e.g.), and that every project that depends on them can use them. What should i do in the pom file of the infrastructure project and the project that depends on it? i've read almost all the complete maven-definite-guide, but didn't find a concise answer... thanks, -- Eyal Edri -- Regards, Alexander -- Eyal Edri -- Regards, Alexander -- Eyal Edri - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Regards, Alexander
Re: Best practice for declaring repos in open source projects
Sure, I agree with both of you that there are conflicts in the various repos, but neither of you gave any suggestions/answers for my practical question. Brian others, do you think its better to keep the extra repos in a profile, always use them if build requires some dependencies from the extra repos or insist that users manually resolve the missing dependencies (by running their own proxy and configuring it correctly)? See the second paragraph below. Kalle On Mon, Nov 16, 2009 at 1:39 AM, Jörg Schaible joerg.schai...@gmx.de wrote: Stephen Connolly wrote at Montag, 16. November 2009 09:41: 2009/11/16 Kalle Korhonen kalle.o.korho...@gmail.com: There's been quite a few threads on declaring Maven repos in poms, most of them referring to Brian's blog post http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/. I agree with that 100%, but as you mention Brian, it's not black and white for open source projects. I ran into the same issue again while working on http://bamboo.ci.codehaus.org/browse/TYNAMO-SEEDENTITY-1. The module depends on some artifacts located in Jboss repo. Their repo is not synched to repo1 but artifacts originating from JBoss may or may not be deployed to repo1 depending on version and project. I'm naturally running my own nexus instance for my team's needs but anybody else just checking out the module from svn or a CI system that I'm not in control of (as in this case, it's Codehaus Bamboo instance) will have a problem building this module. To avoid burning the entries forever into my released POMs I figured I could just the declare the repositories in a profile, for example named repositories. Technically they would still be in the pom but wouldn't be used in normal dependency resolution, only if the user specifically activated it. Since I typically never depend on external snapshots, the profile would only be needed roughly once per set-up, and it would also be easy to document and users to use. Brian, others, do you think this would be a good idea for best practice? Better than declaring them by default or not declaring them at all (and thus either trying to strictly use only modules available in repo1, lobbying required libs to be deployed to repo1 or just having to document this for users and lobbying CI administrators to proxy additional Maven repos)? The issue is that some repositories have different versions of artifacts deployed for the same version number. If you download the artifact from repoA it will never be re-downloaded even if repoA is no longer in your list of repositories and repoB has a different binary. This is especially an issue with java.net, but other (non repo1.maven.org) repositories have the same issue. Especially the jboss repos have this issue also, because - as I understood - they build all artifacts themselves from the source i.e. they also publish a lot of stuff not directly originating from them and that is also available in central. While they *should* produce the same things, you actually can never be sure. [snip] - Jörg - 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
Request Review of Presentation on Maven and MyEclipse
I've put together a presentation on using Maven with MyEclipse for my fellow Java developers at the University of Kansas. We use MyEclipse as our Java IDE. The presentation as an Adobe PDF is attached. If you can review it and provide me an corrections/suggestions it would be most appreciated. The audience are all Maven beginners. Thank You, Bruce Phillips http://www.brucephillips.name/blog http://www.brucephillips.name/blog http://old.nabble.com/file/p26396465/Introduction%2Bto%2BMaven%2BWith%2BMyEclipse%2BDraft.pdf Introduction+to+Maven+With+MyEclipse+Draft.pdf -- View this message in context: http://old.nabble.com/Request-Review-of-Presentation-on-Maven-and-MyEclipse-tp26396465p26396465.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
compiler plugin problems with compilerOptions
'lo all,
I'm starting to experiment with using some annotation processors in my build
and have the following compiler plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source1.5/source
target1.5/target
compilerArgument-AauditXml=${basedir}/test-audit.xml
-AoutputDir=${basedir}/target/compilerArgument
/configuration
/plugin
However, when the build runs (using Maven 2.2.1), javac seems to get an
auditXml property set to ${basedir}/test-audit.xml
-AoutputDir=${basedir}/target rather than two properties set to their
respective values, when I was using Maven 3 at home I don't recall seeing
this issue (about to try it here under M3 as well).
Has anyone seen this behaviour before?
--
Pull me down under...
Re: compiler plugin problems with compilerOptions
Looks like this problem occurs under Maven 3 as well.
I also tried:
compilerArguments
AauditXml${basedir}/test-audit.xml/AauditXml
AoutpurDir${basedir}/target/AoutpurDir
/compilerArguments
but that just gives me:
[ERROR] Compilation failure
Failure executing javac, but could not parse the error:
javac: invalid flag:
/home/amrk/IdeaProjects/securemx/smx3.git/integration/launchpad-tests/test-audit.xml
Usage: javac options source files
use -help for a list of possible options
- [Help 1]
[ERROR]
--
Pull me down under...
On Wed, Nov 18, 2009 at 10:35 AM, Mark Derricutt m...@talios.com wrote:
'lo all,
I'm starting to experiment with using some annotation processors in my
build and have the following compiler plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source1.5/source
target1.5/target
compilerArgument-AauditXml=${basedir}/test-audit.xml
-AoutputDir=${basedir}/target/compilerArgument
/configuration
/plugin
However, when the build runs (using Maven 2.2.1), javac seems to get an
auditXml property set to ${basedir}/test-audit.xml
-AoutputDir=${basedir}/target rather than two properties set to their
respective values, when I was using Maven 3 at home I don't recall seeing
this issue (about to try it here under M3 as well).
Has anyone seen this behaviour before?
--
Pull me down under...
Re: compiler plugin problems with compilerOptions
AoutpurDir${basedir}/target/AoutpurDir
[ERROR] Compilation failure
Failure executing javac, but could not parse the error:
javac: invalid flag:
Isn't that supposed to be AoutputDir ? Is that the invalid flag that
javac is complaining about?
Try mvn -X ... to see the full line being passed to javac, then copy
and paste that line into your own CLI and make sure it works. If not,
tweak in CLI until it works, then tweak Maven config.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Out of memory = out of mind
In XmlSchema, I have a unit test that has been working, more or less unchanged, for over a year. It still works when run from Eclipse. Tonight, launched from maven, it fails instantly with an OutOfMemory exception. This with MAVEN_OPTS set to -Xmx1g. Or 2g. Changing forkMode to always has no effect. This is maven 2.2.1. It fails while parsing a pile of test cases into a DOM tree. There is no way that there is 1G of memory happening there.
maven pom.xml deployment...
Hi, all: I'm using jahmm open source downloaded form http://jahmm.googlecode.com/svn/repo/be/ac/ulg/montefiore/run/jahmm/jahmm/0.6.2/ As you can see, this is a maven version . However, when I port this jahmm project into my Eclipse 3.5.1+maven 2.2.1 (I'm using m2Eclipse http://m2eclipse.sonatype.org/ ) pom.xml always indicate the following error message: *POM 'org.jvnet.wagon-svn:wagon-svn' not found in repository: Unable to download the artifact from any repository org.jvnet.wagon-svn:wagon-svn:pom:1.8 from the specified remote repositories: central (http://repo1.maven.org/maven2) for project org.jvnet.wagon-svn:wagon-svn* I'm wondering how to revise it to make the pom.xml compilable without those red crosses error messages? Best Regards JIA -- Welcome to Vision Open http://www.visionopen.com
Re: compiler plugin problems with compilerOptions
You're right it was supposed to be AoutputDir, however thats just
the annotation processor option, one thing I noticed in the compiler
plugin docs is that it equates:
compilerArgument-verbose -bootclasspath
${java.home}\lib\rt.jar/compilerArgument
with
compilerArguments
verbose /
bootclasspath${java.home}\lib\rt.jar/bootclasspath
/compilerArguments
/configuration
which implies that the contents of the bootclasspath subelement are
appended SPACE delimitered after the key, and not with an equals sign
as I expected, and that would explain the javac problem. Using
compilerArgument alone with only ONE -Axxx=fff setting works fine,
its when I add two.
I'm pulling down the compiler plugin source to see if I can spot whats
it, or I am doing wrong.
--
Pull me down under...
On Wed, Nov 18, 2009 at 12:08 PM, Wayne Fay wayne...@gmail.com wrote:
AoutpurDir${basedir}/target/AoutpurDir
[ERROR] Compilation failure
Failure executing javac, but could not parse the error:
javac: invalid flag:
Isn't that supposed to be AoutputDir ? Is that the invalid flag that
javac is complaining about?
Try mvn -X ... to see the full line being passed to javac, then copy
and paste that line into your own CLI and make sure it works. If not,
tweak in CLI until it works, then tweak Maven config.
Wayne
-
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: Out of memory = out of mind
To my recollection, the Java memory settings are not propagated to the child process, so its getting the default. Try using the following for your memory settings: http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#argLine Cheers, Brett On 18/11/2009, at 10:20 AM, Benson Margulies wrote: In XmlSchema, I have a unit test that has been working, more or less unchanged, for over a year. It still works when run from Eclipse. Tonight, launched from maven, it fails instantly with an OutOfMemory exception. This with MAVEN_OPTS set to -Xmx1g. Or 2g. Changing forkMode to always has no effect. This is maven 2.2.1. It fails while parsing a pile of test cases into a DOM tree. There is no way that there is 1G of memory happening there. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Out of memory = out of mind
I think the older versions of Surefire defaulted to forkMode never in which case the MAVEN_OPTS settings would have applied. The newer versions default to once so they don't. It could be a year ago, you were using Maven 2.0.9 or similar that brought in an older surefire or something. You COULD configure surefire to be forkMode never and see if that makes the test pass.Just a thought. Dan On Tue November 17 2009 6:20:41 pm Benson Margulies wrote: In XmlSchema, I have a unit test that has been working, more or less unchanged, for over a year. It still works when run from Eclipse. Tonight, launched from maven, it fails instantly with an OutOfMemory exception. This with MAVEN_OPTS set to -Xmx1g. Or 2g. Changing forkMode to always has no effect. This is maven 2.2.1. It fails while parsing a pile of test cases into a DOM tree. There is no way that there is 1G of memory happening there. -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: compiler plugin problems with compilerOptions
-A assumes Annotation processor?
javac -help
Usage: javac options source files
javac options include:
-proc:{none,only} Control whether annotation processing and/or
compilation is done.
!-- select the annotation processor you wish to implement --
-processor class1[,class2,class3...]Names of the annotation processors
to run; bypasses default discovery process
!-- specify attributes to pass to the annotation processor --
-Akey[=value] Options to pass to annotation processors
and here is an example of an AnnotationProcessor (with applicable attributes)
http://proactive.inria.fr/release-doc/pa/multiple_html/Annotations.html
Assuming you are implementing a specific Annotation Processor..can you
construct a script which will call the AnnotationProcessor with the proper
attributes
once the script is working you should be able to populate those attributes in
the compilerArgument
compilerArgumentAnnotationProcessorAttributesGoHere/compilerArgument
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.
From: m...@talios.com
Date: Wed, 18 Nov 2009 12:27:45 +1300
Subject: Re: compiler plugin problems with compilerOptions
To: users@maven.apache.org
You're right it was supposed to be AoutputDir, however thats just
the annotation processor option, one thing I noticed in the compiler
plugin docs is that it equates:
compilerArgument-verbose -bootclasspath
${java.home}\lib\rt.jar/compilerArgument
with
compilerArguments
verbose /
bootclasspath${java.home}\lib\rt.jar/bootclasspath
/compilerArguments
/configuration
which implies that the contents of the bootclasspath subelement are
appended SPACE delimitered after the key, and not with an equals sign
as I expected, and that would explain the javac problem. Using
compilerArgument alone with only ONE -Axxx=fff setting works fine,
its when I add two.
I'm pulling down the compiler plugin source to see if I can spot whats
it, or I am doing wrong.
--
Pull me down under...
On Wed, Nov 18, 2009 at 12:08 PM, Wayne Fay wayne...@gmail.com wrote:
AoutpurDir${basedir}/target/AoutpurDir
[ERROR] Compilation failure
Failure executing javac, but could not parse the error:
javac: invalid flag:
Isn't that supposed to be AoutputDir ? Is that the invalid flag that
javac is complaining about?
Try mvn -X ... to see the full line being passed to javac, then copy
and paste that line into your own CLI and make sure it works. If not,
tweak in CLI until it works, then tweak Maven config.
Wayne
-
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
_
Bing brings you maps, menus, and reviews organized in one place.
http://www.bing.com/search?q=restaurantsform=MFESRPpubl=WLHMTAGcrea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1
Format for manually creating source and javadoc bundles?
Hi -- I'm new to Maven, and think it seems nice, but am having some problems finding the details on what the layout is for a source bundle. I've searched the web a good bit, and can find lots of info about the source plugin used to generate them, but not about the expected format of a source bundle. The reason I need to know is that I need to use a non-Maven build system to produce source/javadoc bundles that can be used by other Maven users (and via things like the eclipse:eclipse plugin with -DdownloadSources=true). Is there somewhere I should be looking to find the canonical format I need to produce? I'm targeting maven 2.1 users, if that helps. Thanks for any help! jon - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Format for manually creating source and javadoc bundles?
(Minor edit: I meant that I'm targeting maven 2.2 users, not 2.1) jon On Tue, Nov 17, 2009 at 09:34:44PM -0800, Jonathan Gold wrote: Hi -- I'm new to Maven, and think it seems nice, but am having some problems finding the details on what the layout is for a source bundle. I've searched the web a good bit, and can find lots of info about the source plugin used to generate them, but not about the expected format of a source bundle. The reason I need to know is that I need to use a non-Maven build system to produce source/javadoc bundles that can be used by other Maven users (and via things like the eclipse:eclipse plugin with -DdownloadSources=true). Is there somewhere I should be looking to find the canonical format I need to produce? I'm targeting maven 2.1 users, if that helps. Thanks for any help! jon - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Format for manually creating source and javadoc bundles?
The format of the bundles are: *-source.jar - it's the java source simply archived. Start archiving from where you think src/main/java would be. Just make sure you remember your archive utility retains the paths of the file you choose. I use WinZip for this. *-docs.jar - same above except for the javadoc site Paul On Tue, Nov 17, 2009 at 11:34 PM, Jonathan Gold jgold...@gmail.com wrote: Hi -- I'm new to Maven, and think it seems nice, but am having some problems finding the details on what the layout is for a source bundle. I've searched the web a good bit, and can find lots of info about the source plugin used to generate them, but not about the expected format of a source bundle. The reason I need to know is that I need to use a non-Maven build system to produce source/javadoc bundles that can be used by other Maven users (and via things like the eclipse:eclipse plugin with -DdownloadSources=true). Is there somewhere I should be looking to find the canonical format I need to produce? I'm targeting maven 2.1 users, if that helps. Thanks for any help! jon - 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: Format for manually creating source and javadoc bundles?
Thanks! jon On Tue, Nov 17, 2009 at 11:38:40PM -0600, Paul Benedict wrote: The format of the bundles are: *-source.jar - it's the java source simply archived. Start archiving from where you think src/main/java would be. Just make sure you remember your archive utility retains the paths of the file you choose. I use WinZip for this. *-docs.jar - same above except for the javadoc site Paul On Tue, Nov 17, 2009 at 11:34 PM, Jonathan Gold jgold...@gmail.com wrote: Hi -- I'm new to Maven, and think it seems nice, but am having some problems finding the details on what the layout is for a source bundle. I've searched the web a good bit, and can find lots of info about the source plugin used to generate them, but not about the expected format of a source bundle. The reason I need to know is that I need to use a non-Maven build system to produce source/javadoc bundles that can be used by other Maven users (and via things like the eclipse:eclipse plugin with -DdownloadSources=true). Is there somewhere I should be looking to find the canonical format I need to produce? I'm targeting maven 2.1 users, if that helps. Thanks for any help! jon - 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
