RE: SNAPSHOT
This is indeed a buggy feature: the retrieved snpashot dependency, in the case of a war module for example, is sometime included as mydependency-1.0-SNAPSHOT.jar, and sometimes as mydependency-1.0-TIMESTAMP.jar. If a mvn clean is not done, a dependency can also be included twice as mydependency-1.0-TIMESTAMP1.jar and mydependency-1.0-TIMESTAMP2.jar. My two cents, Sebastien -Original Message- From: amit kumar [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 09:52 To: Maven Users List Subject: Re: SNAPSHOT It seems to work for me. Whenever a new SNAPSHOT version(1.0.0-SNAPSHOT) is deployed to the reposiroty maven stores it with timestamp witn in the 1.0.0-SNAPSHOT folder. As I can see the artifact-1.0.0-SNAPSHOT.jar keeps on getting updated corresponding to the latest deployed jar. So in the repository the 1.0.0-SNAPSHOT folder has all the so far deployed jar files along with the timestamp and a artifact-1.0.0-SNAPSHOT.jar, which gets retrieved. Regards, Amit On 2/18/08, Wendy Smoak [EMAIL PROTECTED] wrote: On Feb 17, 2008 10:14 PM, Ryan H. [EMAIL PROTECTED] wrote: If my maven2 repository persists each artifact with time stamp as part of their filename, is SNAPSHOT version still going to work? Yes. It uses the metadata file in the repository to decide which timestamped file to retrieve. (Are you using just 'SNAPSHOT' as a version? Usually it's 1.0-SNAPSHOT or similar.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Timestamp in snapshot dependencies names
Hi, When I build a war artifact that has some snapshot jar dependencies, the jar packaged in WEB-INF/lib are sometime named my-dependency-version-SNAPSHOT.jar and sometime named my-dependency-version-LONG_18_CHARS_TIMETAMP_HERE.jar. When the jar dependencies are named with a timestamp, I've got classpath related issues when deploying my web app on Jboss / windows (because the path to the jars, including their name, is too long). So I need to make sure that my snapshot jars under WEB-INF/lib are always named my-dependency-version-SNAPSHOT.jar. Is there a way to do this ? Note that using the outputFileNameMapping configuration parameter of the war plugin is unfortunately not an option for me because of (http://jira.codehaus.org/browse/MWAR-116). Thanks for your help, Sebastien Brunot Make simple things simple before making complex things possible (David S. Platt in Why Software Sucks ?) and then... Make complex things simple and accessible (Steve Demuth) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to not include POM in packaged artifacts
Hi all, jar, war and ear artifacts packages by maven includes the POM (and a pom property file) under META-INF. How to not include the POM files into META-INF ? Thanks for your help, Sebastien
RE: EJB JAR Manifest
On my side, I did not observe substantial timing differences adding classpath entries (automatically regarding the dependencies or manualy providing my own manifest.mf file) to the EJB jar. Perhaps you could send the output of mvn -X package to the list as an attached file ? Sebastien -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 6:13 AM To: users@maven.apache.org Subject: RE: EJB JAR Manifest Sebastein, Is it taking too long to add the classpath entry in the manifest? Since i made the ejb plugin to add the classpath entry, it is taking almost 1 min more to complete the ejb goal. Is it working normally for you? Thanks Sebastien Brunot wrote: Thanks for your help Jörg. Sebastien -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Thursday, November 09, 2006 2:20 PM To: Maven Users List Subject: RE: EJB JAR Manifest Sebastien Brunot wrote on Thursday, November 09, 2006 1:59 PM: Hi all, how can one specify a Class-Path: entry in the manifest of an EJB jar ? You have to configure it: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration /plugin - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/EJB-JAR-Manifest-tf2601563s177.html#a7271531 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Model object XML representation
Hi, Where can i find reference documentation regarding the mapping of maven model object into XML (for mojo parameters) ? Thanks for your help, Sebastien
MavenProjectBuilder injection in a Mojo
Hi all, what is the expression to use for injection of an org.apache.maven.project.DefaultMavenProjectBuilder instance as the value of a pojo parameter: /** * A MavenProjectBuilder instance * * @parameter expression= * @readonly * @required */ private MavenProjectBuilder projectBuilder; what should i set as expression ? Thanks for your help, Sebastien
RE: MavenProjectBuilder injection in a Mojo
A recent mail from franz see gives me the answers (use @component instead of @parameter). Sorry for the annoyance. Sebastien -Original Message- From: Sebastien Brunot [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 1:58 PM To: Maven Users List Subject: MavenProjectBuilder injection in a Mojo Hi all, what is the expression to use for injection of an org.apache.maven.project.DefaultMavenProjectBuilder instance as the value of a pojo parameter: /** * A MavenProjectBuilder instance * * @parameter expression= * @readonly * @required */ private MavenProjectBuilder projectBuilder; what should i set as expression ? Thanks for your help, Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: MavenProjectBuilder injection in a Mojo
I tried it the first time but it throws an exception and indicates it
can't find org.apache.maven.project.MavenProjectBuilder in the
component repository.
Using @component instead of @parameters raises no errors. I don't know
if it do the job yet...
Sebastien
-Original Message-
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Friday, November 10, 2006 2:03 PM
To: Maven Users List
Subject: Re: MavenProjectBuilder injection in a Mojo
On 10/11/06, Sebastien Brunot [EMAIL PROTECTED] wrote:
what is the expression to use for injection of an
org.apache.maven.project.DefaultMavenProjectBuilder instance as the
value of a pojo parameter:
Use:
/**
* @parameter
expression=${component.org.apache.maven.project.MavenProjectBuilder}
* @required
* @readonly
*/
private MavenProjectBuilder projectBuilder;
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
XML representation of an Artifact in the configuration section of the POM
Hi all,
i have a mojo that defines a parameter names sourcePom which type is
Artifact :
/**
* The POM where jar dependencies are declared.
*
* @parameter expression=${merge-jar-dependencies.sourcePom}
default-value=${project.artifact}
*/
private Artifact sourcePom;
I don't know how to specify an artifact under configuration
sourcePom ...
Thanks for your help,
Sebastien
RE: XML representation of an Artifact in the configuration section of the POM
Thanks for your help franz, it's nice to have the kind of support you
provides.
In fact, I've adopted the strategy I've seen in the
maven-dependency-plugin :
1) I've included in my plugin a java bean PomArtifact that declares
three String attributes : groupId, artifactId and version. Public
getters and setters are defined for those attributes, and the attributes
javadoc uses the @parameter and @required annotations (note that
defining default values such as ${project.groupId} fot those attributes
doen not seems to work)
2) In my mojo, sourcePom type is now PomArtifact
3) Everything works fine using the following xml in the POM :
project
...
build
plugins
plugin
groupId.../groupId
artifactId.../artifactId
version.../version
executions
execution
configuration
sourcePom
artifactId.../artifactId
groupId.../groupId
version.../version
/sourcePom
configuration
/execution
/executions
/plugin
/plugins
/build
/project
4) In my Mojo execute method, I will now create an Artifact object using
the values retrieved from sourcePom.
Sebastien
-Original Message-
From: franz see [mailto:[EMAIL PROTECTED]
Sent: Friday, November 10, 2006 2:54 PM
To: users@maven.apache.org
Subject: Re: XML representation of an Artifact in the configuration
section of the POM
Good day to you, Sebastien,
Note: I don't know everything about mojo parameters but i'll show what i
know so far
Here's the break down of a mojo parameter:
/**
* @parameter expression=${merge-jar-dependencies.sourcePom}
default-value=${project.artifact}
*/
private Aritfact sourcePom;
expression (in your case, merge-jar-dependencies.sourcePom).
`-- Used to inject a Property value to that parameter (sourcePom).
Properties may come from System / Environment Variables, POM properties,
Commandline Properties, Filter properties, or other predefined
properties (i.e project.artifact).
default-value (in your case, project.artifact) `-- Injects a property
to your parameter.
you class's field (in your case, soucePom) `-- This is your paramater.
If the first two discussed here is injected by properties, this one is
injected from the configuration element in your pom. (Note: AFAIK, if
you set your experssion as a predefined property such as
project.artifact, the parameter can no longer be configured in your pom)
To answer your question, since you're using a class, you use the
parameter.
project
...
build
plugins
plugin
groupId.../groupId
artifactId.../artifactId
version.../version
executions
execution
configuration
sourcePom
artifactId.../artifactId
groupId.../groupId
version.../version
...
/sourcePom
configuration
/execution
/executions
/plugin
/plugins
/build
/project
the sourcePom represents your sourcePom field in your class.
the elements of sourcePom are the fields of the Artifact.
Things I am unsure of:
1. I am not sure if sourcePom will work as it is. But if not, you may
want to try sourcePom
implementation=org.apache.maven.artifact.DefaultArtifact.
2. I am not sure if private Aritfact sourcePom will work as well, you
may want to try DefaultArtifact.
3. Most likely, #1 #2 will work withouth those workarounds i
mentioned, Im just not sure how.
4. I am not sure whether it is the fields of the Artifact that you
access with the elements of sourcePom or the setters.
If you find the answers to those, or if somebody out there who knows,
kindly share it with us :-)
Thanks,
Franz
Sebastien Brunot wrote:
Hi all,
i have a mojo that defines a parameter names sourcePom which type is
Artifact :
/**
* The POM where jar dependencies are declared.
*
* @parameter expression=${merge-jar-dependencies.sourcePom}
default-value=${project.artifact}
*/
private Artifact sourcePom;
I don't know how to specify an artifact under configuration
sourcePom ...
Thanks for your help,
Sebastien
--
View this message in context:
http://www.nabble.com/XML-representation-of-an-Artifact-in-the-%3Cconfig
uration%3E-section-of-the-POM-tf2607681s177.html#a7277297
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Resolving project dependencies
Hi all, how do you programmaticaly resolve the dependencies of a MavenProject object ? I've got a MavenProject object in my mojo (that i've created from an Artifact object), and i now want to resolves its dependencies in ordre to get them as artifacts using the getArtifactDependencies() method. What previous steps are implied before calling the getArtifactDependencies() method ? Thanks for your help, Sebastien
RE: Resolving project dependencies
I'm not sure I undestand your question, but I want to get a list of all the artifact that correspond to a dependency declared in the MavenProject POM, with or without transitivity depending on a parameter set in my plugin configuration. Without transitivity is mandatory, with transitivity is optional. Sebastien -Original Message- From: Mark Hobson [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 4:38 PM To: Maven Users List Subject: Re: Resolving project dependencies On 10/11/06, Sebastien Brunot [EMAIL PROTECTED] wrote: how do you programmaticaly resolve the dependencies of a MavenProject object ? Are you trying to resolve: the project's declared dependencies; all the project's transitive dependencies; or traverse the project's dependency tree? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Resolving project dependencies
What I'm doing exactly is as following: 1) I create an Artifact object using groupId, artifactId and version provided in the plugin configuration (the type is always pom) 2) Using this artifact, I create a MavenProject object (with the buildFromRepository(...) method of a MavenProjectBuilder instance) 3) At this step, I want that a call to getArtifacts or getDependenciesArtifact returns the list of dependencies (non transitive or transitive) = in fact, it does not: getArtifacts returns an empty set while getDependenciesArtifact returns null. I've discovered the createArtifacts method of MavenProject thanks to your code, and it seems to create the set of (non transitive) dependencies artifact I was looking for. But what about transitive dependencies ? Do I have to take each artifact in the set returned by createArtifacts and resolve it recursively to get the transitive set of dependencies ? If yes, which method do I use knowing that I have an Artifact object and I want its set of artifact dependencies ? Thanks for your help, Sebastien -Original Message- From: Mark Hobson [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 4:53 PM To: Maven Users List Subject: Re: Resolving project dependencies On 10/11/06, Sebastien Brunot [EMAIL PROTECTED] wrote: I'm not sure I undestand your question, but I want to get a list of all the artifact that correspond to a dependency declared in the MavenProject POM, with or without transitivity depending on a parameter set in my plugin configuration. Without transitivity is mandatory, with transitivity is optional. I believe that: project.getArtifacts() returns all the project's dependencies, including transitive ones; and project.getDependencyArtifacts() only returns the immediate dependencies declared in the project's pom. Although you say you're trying to resolve the dependencies of a dependency in a project? As soon as you start traversing deeper than the first level of dependencies in the pom, you need to start resolving them yourself. I've recently extracted code to do this into a shared component that's currently sitting in JIRA, see: http://jira.codehaus.org/browse/MNG-2654 Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Resolving project dependencies
Thanks for your help tom, I now have all the information I needed. Sebastien -Original Message- From: Tom Huybrechts [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 5:26 PM To: Maven Users List Subject: Re: Resolving project dependencies This works for me: Artifact pomArtifact = this.factory.createArtifact( groupId, artifactId, version, , pom ); MavenProject pomProject = mavenProjectBuilder.buildFromRepository( pomArtifact, this.remoteRepos, this.local ); Set artifacts = pomProject.createArtifacts( this.factory, null, null); ScopeArtifactFilter filter = new ScopeArtifactFilter(DefaultArtifact.SCOPE_RUNTIME); ArtifactResolutionResult arr = resolver.resolveTransitively(artifacts, pomArtifact, local, remoteRepos, source, filter); Set result = arr.getArtifacts(); On 11/10/06, Sebastien Brunot [EMAIL PROTECTED] wrote: What I'm doing exactly is as following: 1) I create an Artifact object using groupId, artifactId and version provided in the plugin configuration (the type is always pom) 2) Using this artifact, I create a MavenProject object (with the buildFromRepository(...) method of a MavenProjectBuilder instance) 3) At this step, I want that a call to getArtifacts or getDependenciesArtifact returns the list of dependencies (non transitive or transitive) = in fact, it does not: getArtifacts returns an empty set while getDependenciesArtifact returns null. I've discovered the createArtifacts method of MavenProject thanks to your code, and it seems to create the set of (non transitive) dependencies artifact I was looking for. But what about transitive dependencies ? Do I have to take each artifact in the set returned by createArtifacts and resolve it recursively to get the transitive set of dependencies ? If yes, which method do I use knowing that I have an Artifact object and I want its set of artifact dependencies ? Thanks for your help, Sebastien -Original Message- From: Mark Hobson [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 4:53 PM To: Maven Users List Subject: Re: Resolving project dependencies On 10/11/06, Sebastien Brunot [EMAIL PROTECTED] wrote: I'm not sure I undestand your question, but I want to get a list of all the artifact that correspond to a dependency declared in the MavenProject POM, with or without transitivity depending on a parameter set in my plugin configuration. Without transitivity is mandatory, with transitivity is optional. I believe that: project.getArtifacts() returns all the project's dependencies, including transitive ones; and project.getDependencyArtifacts() only returns the immediate dependencies declared in the project's pom. Although you say you're trying to resolve the dependencies of a dependency in a project? As soon as you start traversing deeper than the first level of dependencies in the pom, you need to start resolving them yourself. I've recently extracted code to do this into a shared component that's currently sitting in JIRA, see: http://jira.codehaus.org/browse/MNG-2654 Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Resolving project dependencies
Or in the javadoc (the closer from the code, the better) !!! Sebastien -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 5:45 PM To: Maven Users List Subject: Re: Resolving project dependencies This is the kind of stuff that needs to land in a Maven Plugin Developers doc/wiki/etc somewhere... Wayne On 11/10/06, Sebastien Brunot [EMAIL PROTECTED] wrote: Thanks for your help tom, I now have all the information I needed. Sebastien -Original Message- From: Tom Huybrechts [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 5:26 PM To: Maven Users List Subject: Re: Resolving project dependencies This works for me: Artifact pomArtifact = this.factory.createArtifact( groupId, artifactId, version, , pom ); MavenProject pomProject = mavenProjectBuilder.buildFromRepository( pomArtifact, this.remoteRepos, this.local ); Set artifacts = pomProject.createArtifacts( this.factory, null, null); ScopeArtifactFilter filter = new ScopeArtifactFilter(DefaultArtifact.SCOPE_RUNTIME); ArtifactResolutionResult arr = resolver.resolveTransitively(artifacts, pomArtifact, local, remoteRepos, source, filter); Set result = arr.getArtifacts(); On 11/10/06, Sebastien Brunot [EMAIL PROTECTED] wrote: What I'm doing exactly is as following: 1) I create an Artifact object using groupId, artifactId and version provided in the plugin configuration (the type is always pom) 2) Using this artifact, I create a MavenProject object (with the buildFromRepository(...) method of a MavenProjectBuilder instance) 3) At this step, I want that a call to getArtifacts or getDependenciesArtifact returns the list of dependencies (non transitive or transitive) = in fact, it does not: getArtifacts returns an empty set while getDependenciesArtifact returns null. I've discovered the createArtifacts method of MavenProject thanks to your code, and it seems to create the set of (non transitive) dependencies artifact I was looking for. But what about transitive dependencies ? Do I have to take each artifact in the set returned by createArtifacts and resolve it recursively to get the transitive set of dependencies ? If yes, which method do I use knowing that I have an Artifact object and I want its set of artifact dependencies ? Thanks for your help, Sebastien -Original Message- From: Mark Hobson [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 4:53 PM To: Maven Users List Subject: Re: Resolving project dependencies On 10/11/06, Sebastien Brunot [EMAIL PROTECTED] wrote: I'm not sure I undestand your question, but I want to get a list of all the artifact that correspond to a dependency declared in the MavenProject POM, with or without transitivity depending on a parameter set in my plugin configuration. Without transitivity is mandatory, with transitivity is optional. I believe that: project.getArtifacts() returns all the project's dependencies, including transitive ones; and project.getDependencyArtifacts() only returns the immediate dependencies declared in the project's pom. Although you say you're trying to resolve the dependencies of a dependency in a project? As soon as you start traversing deeper than the first level of dependencies in the pom, you need to start resolving them yourself. I've recently extracted code to do this into a shared component that's currently sitting in JIRA, see: http://jira.codehaus.org/browse/MNG-2654 Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] List of All Dependencies for any project X
Hi, Mark Hobson seems to have authored mojos that does this: http://jira.codehaus.org/browse/MNG-2654 Hope it helps, Sebastien -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, November 10, 2006 6:27 PM To: users@maven.apache.org Subject: [m2] List of All Dependencies for any project X Hi Jason, Brett et al How do you get a list of all dependencies (transitive or declared) for any M2 project? Basically I want to find out the list so I can cross reference against an in-house repository here at UBS. The idea is to tell the administrator here with the in-house what dependencies they should be including, so that we don't have to use any external sites. Is this possible? -- Peter Pilgrim UBS Investment Bank, PTS Portal / IT FIRC OPS LDN, 100 Liverpool Street, London EC2M 2RH, United Kingdom +44 (0) 20 75 75692 :: Java EE / E-Commerce / Enterprise Integration / Development :: Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: dependency plugin
In fact I've already have a pom that describes the dependencies, as they are shared by many modules. Using artifactItems on this pom with unpack-dependencies will help me, except that I don't want the transitive dependencies from the pom dependencies to be copied... Can I use some sorts of exclusions tags with artifactItem ? Thanks for your help, Sebastien -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 08, 2006 7:18 PM To: Maven Users List Subject: Re: dependency plugin The main purpose of artifactItems is so that we dont need to use dependencies elements. perhaps, you need http://maven.apache.org/plugins/maven-dependency-plugin/unpack-dependenc ies-mojo.html -D On 11/8/06, Sebastien Brunot [EMAIL PROTECTED] wrote: Hi all, is it possible to parameterize the dependency plugin unpack goal so that it uses a pom dependencies section as input instead of an artifactItems list ? Thanks for your help, Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: dependency plugin
I think I didn't manage to express clearly my concern: I have a pom artifact that declare a list of (many) dependencies (let's name it the optimized-3dparties-dependencies pom). In another module (actually an EAR module), I want to pack the list of artifact declared in optimized-3dparties-dependencies and build a single jar that contains everything. I don't want transitivity on the dependencies declared in optimized-3dparties-dependencies. So I was wondering how to do this without re declaring my dependencies in an artifactItems tag. Do you think it is possible with the existing plugins ? Thanks for your help, Sebastien -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Thursday, November 09, 2006 11:17 AM To: Maven Users List Subject: Re: dependency plugin artifactItem does not support transitive dependencies. so no need for exclusion. But you need to specify every item. -D On 11/9/06, Sebastien Brunot [EMAIL PROTECTED] wrote: In fact I've already have a pom that describes the dependencies, as they are shared by many modules. Using artifactItems on this pom with unpack-dependencies will help me, except that I don't want the transitive dependencies from the pom dependencies to be copied... Can I use some sorts of exclusions tags with artifactItem ? Thanks for your help, Sebastien -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 08, 2006 7:18 PM To: Maven Users List Subject: Re: dependency plugin The main purpose of artifactItems is so that we dont need to use dependencies elements. perhaps, you need http://maven.apache.org/plugins/maven-dependency-plugin/unpack-depende nc ies-mojo.html -D On 11/8/06, Sebastien Brunot [EMAIL PROTECTED] wrote: Hi all, is it possible to parameterize the dependency plugin unpack goal so that it uses a pom dependencies section as input instead of an artifactItems list ? Thanks for your help, Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
EJB JAR Manifest
Hi all, how can one specify a Class-Path: entry in the manifest of an EJB jar ? Thanks for your help, Sebastien
RE: EJB JAR Manifest
Maybe I'm facing a bug similar to http://jira.codehaus.org/browse/PLX-158 ..., but with the EJB plugin ? Sebastien -Original Message- From: Sebastien Brunot [mailto:[EMAIL PROTECTED] Sent: Thursday, November 09, 2006 1:59 PM To: Maven Users List Subject: EJB JAR Manifest Hi all, how can one specify a Class-Path: entry in the manifest of an EJB jar ? Thanks for your help, Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: EJB JAR Manifest
Thanks for your help Jörg. Sebastien -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Thursday, November 09, 2006 2:20 PM To: Maven Users List Subject: RE: EJB JAR Manifest Sebastien Brunot wrote on Thursday, November 09, 2006 1:59 PM: Hi all, how can one specify a Class-Path: entry in the manifest of an EJB jar ? You have to configure it: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration /plugin - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: EJB JAR Manifest
I also tried with: configuration generateClienttrue/generateClient archive manifest manifestFilepath/to/my/file/manifestFile /manifest /archive /configuration But it break the build with message: Cause: Cannot find setter nor field in org.apache.maven.archiver.ManifestConfiguration for 'manifestFile' Any idea of how to provides one's own custom MANIFEST.MF file ? Sebastien -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Thursday, November 09, 2006 2:20 PM To: Maven Users List Subject: RE: EJB JAR Manifest Sebastien Brunot wrote on Thursday, November 09, 2006 1:59 PM: Hi all, how can one specify a Class-Path: entry in the manifest of an EJB jar ? You have to configure it: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration /plugin - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: EJB JAR Manifest
Ok, I've found the error (there should be no enclosing manifest tags around manifestFile). Sorry for the annoyance... Sebastien -Original Message- From: Sebastien Brunot [mailto:[EMAIL PROTECTED] Sent: Thursday, November 09, 2006 3:00 PM To: Maven Users List Subject: RE: EJB JAR Manifest I also tried with: configuration generateClienttrue/generateClient archive manifest manifestFilepath/to/my/file/manifestFile /manifest /archive /configuration But it break the build with message: Cause: Cannot find setter nor field in org.apache.maven.archiver.ManifestConfiguration for 'manifestFile' Any idea of how to provides one's own custom MANIFEST.MF file ? Sebastien -Original Message- From: Jörg Schaible [mailto:[EMAIL PROTECTED] Sent: Thursday, November 09, 2006 2:20 PM To: Maven Users List Subject: RE: EJB JAR Manifest Sebastien Brunot wrote on Thursday, November 09, 2006 1:59 PM: Hi all, how can one specify a Class-Path: entry in the manifest of an EJB jar ? You have to configure it: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration generateClienttrue/generateClient archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration /plugin - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Testing Mojos
Hi, does anyone have a good documentation starting point regarding unit testing and integration testing of mojos ? Thanks for your help, Sebastien
RE: Transitive dependecies
Yes. I would like to have something like excludes excludeALLexclude /excludes. Sebastien -Original Message- From: Edwin Punzalan [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 07, 2006 6:22 PM To: Maven Users List Subject: Re: Transitive dependecies Yes, I agree with that... and that's a good reason for using excludes. But you don't really disable transitivity completely with it. You just select from the list of dependencies to not use, in your example, library B. Sebastien Brunot wrote: Even if the POM are correct, transitivity can copy much more classes than really needed : you're using library A, which a subset of class uses library B. If you don't use this particular subset of classes in library A, you don't need the dependency on library B (I hope it's clear). Sebastien -Original Message- From: Edwin Punzalan [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 07, 2006 5:53 PM To: Maven Users List Subject: Re: Transitive dependecies Dependencies should be marked as optional if it is not required. There's nothing bad with transitivity if the poms are correct... it actually makes dependency management easier. Broken poms make transitivity look bad. Wendy Smoak wrote: On 11/7/06, Sebastien Brunot [EMAIL PROTECTED] wrote: transitive dependencies can be a real pain when you have a lot of external dependencies in your project. Using exclusions tags is a tedious operation in this case, so I was wondering if a quicker way exists... Having to use a lot of exclusions generally means that the poms are broken. (For example, things that should be marked optional, aren't.) What dependencies are causing problems? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
dependency plugin
Hi all, is it possible to parameterize the dependency plugin unpack goal so that it uses a pom dependencies section as input instead of an artifactItems list ? Thanks for your help, Sebastien
Configuring war plugin for using a jar instead of WEB-INF/classes
Hi all, i've got a war project which pom build section contains the following statements: !-- Package webapp classes into a jar instead of under WEB-INF/classes -- plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-war-plugin/artifactId executions execution goals goalwar/goal /goals configuration archiveClassestrue/archiveClasses /configuration /execution /executions /plugin As a result, all the classes and resources from my war project are packaged in a jar that is copied in the WEB-INF/lib directory of the war artifact. But i don't understand why the war artifact still contains copy of the classes and resources under WEB-INF/classes... Does anybody think that i've misconfigured the war plugin ? Thanks for your help, Sebastien
RE: Configuring war plugin for using a jar instead of WEB-INF/classes
Issue has been created as MWAR-82
(http://jira.codehaus.org/browse/MWAR-82).
Sebastien
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 07, 2006 3:59 PM
To: users@maven.apache.org
Subject: Re: Configuring war plugin for using a jar instead of
WEB-INF/classes
Hi Sebastien
It seems to be a bug.
In the code [1] we have :
if ( archiveClasses )
{
createJarArchive( libDirectory );
}
else
{
copyDirectoryStructureIfModified( classesDirectory,
webappClassesDirectory );
}
The content of the classes directory is never removed (neither in
createJarArchive nor somewhere else).
Can you create an issue please ?
Thx
Arnaud
[1]
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-war-plugin/src/ma
in/java/org/apache/maven/plugin/war/AbstractWarMojo.java?revision=471624
Sebastien Brunot wrote:
Hi all,
i've got a war project which pom build section contains the following
statements:
!-- Package webapp classes into a jar instead of under
WEB-INF/classes --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
executions
execution
goals
goalwar/goal
/goals
configuration
archiveClassestrue/archiveClasses
/configuration
/execution
/executions
/plugin
As a result, all the classes and resources from my war project are
packaged in a jar that is copied in the WEB-INF/lib directory of the
war artifact.
But i don't understand why the war artifact still contains copy of the
classes and resources under WEB-INF/classes... Does anybody think that
i've misconfigured the war plugin ?
Thanks for your help,
Sebastien
--
View this message in context:
http://www.nabble.com/Configuring-war-plugin-for-using-a-jar-instead-of-
WEB-INF-classes-tf2589199s177.html#a7219855
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Transitive dependecies
Hi all, transitive dependencies can be a real pain when you have a lot of external dependencies in your project. Using exclusions tags is a tedious operation in this case, so I was wondering if a quicker way exists... How can one create a pom module that contains a list of dependencies (let's name it lib pom), so that when the lib pom is added as a dependecy in let's say a war project, the exact list of dependencies from lib pom (no more, no less = no transitivity) are added to the war WEB-INF/lib ? Thanks for your help, Sebastien
RE: Transitive dependecies
Hi Wendy, Are you trying to tell me that the feature I'm asking about does not exists in maven 2 (inheriting dependencies from a pom without transitivity, but with a scope that makes them copied in WEB-INF/lib when I'm working on a war project) ? Sebastien -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 07, 2006 5:18 PM To: Maven Users List Subject: Re: Transitive dependecies On 11/7/06, Sebastien Brunot [EMAIL PROTECTED] wrote: transitive dependencies can be a real pain when you have a lot of external dependencies in your project. Using exclusions tags is a tedious operation in this case, so I was wondering if a quicker way exists... Having to use a lot of exclusions generally means that the poms are broken. (For example, things that should be marked optional, aren't.) What dependencies are causing problems? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Transitive dependecies
Hi barrett, I think I'm actually proceeding quite the same (the lib pom I was talking about). I really want to know if I can move a step further and make the dependencies not transitive while included in the WAR (actually an EAR in my case ;-). If the feature does not exists yet in maven (using scope settings or something else), I might ask for it: this is why I want to know if it is already possible or not. Sebastien -Original Message- From: Barrett Nuzum [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 07, 2006 5:28 PM To: Maven Users List Subject: RE: Transitive dependecies Sebastien: On my current assignment, we solved this by having one POM for the main dependencies of all projects, and a child POM called WebDependencies. All child projects of type WAR specify WebDependencies as a direct dependency. This *does* include transitive dependencies -- but you should be able to trim down the list of total dependencies included by a significant amount. (The ones you probably actually need.) If you bundle your WAR in an EAR, you can use this Dependencies POM in both the EAR and WAR projects and suppress everything in the WAR's WEB-INF/lib to eliminate duplication further. Hope that helps. Barrett Barrett Nuzum Consultant, Skill Development [EMAIL PROTECTED] T: +1 (918) 640 4414 F: +1 (972) 789 1340 Valtech 5080 Spectrum Drive Suite 700 West Addison, Texas 75001 USA T: +1 (972) 789 1200 From: Sebastien Brunot [mailto:[EMAIL PROTECTED] Sent: Tue 11/7/2006 10:13 AM To: Maven Users List Subject: Transitive dependecies Hi all, transitive dependencies can be a real pain when you have a lot of external dependencies in your project. Using exclusions tags is a tedious operation in this case, so I was wondering if a quicker way exists... How can one create a pom module that contains a list of dependencies (let's name it lib pom), so that when the lib pom is added as a dependecy in let's say a war project, the exact list of dependencies from lib pom (no more, no less = no transitivity) are added to the war WEB-INF/lib ? Thanks for your help, Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Transitive dependecies
In fact, the dependencies I don't want in the lib directory are the one obtained because of the transitivity mechanism. So I want all dependencies included, but not the one they might have themselves (and I may not have access to the POM of those dependencies to set their scope to provided). Sebastien -Original Message- From: Martin Vysny [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 07, 2006 5:44 PM To: Maven Users List Subject: RE: Transitive dependecies On Tue, 2006-11-07 at 17:27 +0100, Sebastien Brunot wrote: Hi Wendy, Are you trying to tell me that the feature I'm asking about does not exists in maven 2 (inheriting dependencies from a pom without transitivity, but with a scope that makes them copied in WEB-INF/lib when I'm working on a war project) ? Try to define those dependencies you *don't* want to appear in the lib directory with scope 'provided'. Dependency with 'provided' scope is defined as being provided by the environment (for example by the JEE server). Sebastien -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 07, 2006 5:18 PM To: Maven Users List Subject: Re: Transitive dependecies On 11/7/06, Sebastien Brunot [EMAIL PROTECTED] wrote: transitive dependencies can be a real pain when you have a lot of external dependencies in your project. Using exclusions tags is a tedious operation in this case, so I was wondering if a quicker way exists... Having to use a lot of exclusions generally means that the poms are broken. (For example, things that should be marked optional, aren't.) What dependencies are causing problems? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Transitive dependecies
Even if the POM are correct, transitivity can copy much more classes than really needed : you're using library A, which a subset of class uses library B. If you don't use this particular subset of classes in library A, you don't need the dependency on library B (I hope it's clear). Sebastien -Original Message- From: Edwin Punzalan [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 07, 2006 5:53 PM To: Maven Users List Subject: Re: Transitive dependecies Dependencies should be marked as optional if it is not required. There's nothing bad with transitivity if the poms are correct... it actually makes dependency management easier. Broken poms make transitivity look bad. Wendy Smoak wrote: On 11/7/06, Sebastien Brunot [EMAIL PROTECTED] wrote: transitive dependencies can be a real pain when you have a lot of external dependencies in your project. Using exclusions tags is a tedious operation in this case, so I was wondering if a quicker way exists... Having to use a lot of exclusions generally means that the poms are broken. (For example, things that should be marked optional, aren't.) What dependencies are causing problems? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Transitive dependecies
Thanks for the hint barrett, it is valuable to me (using dependency plugin to copy jars in WEB-INF/lib instead of declaring dependencies). Sebastien -Original Message- From: Barrett Nuzum [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 07, 2006 5:54 PM To: Maven Users List Subject: RE: Transitive dependecies Sebastien: I think most people instead suppress all dependencies from war bundling and then use the maven-dependency-plugin to copy specific artifacts. (It provides more fine grained control at the expense of some extensibility.) It's not a core maven feature, though, as far as I know. Barrett Barrett Nuzum Consultant, Skill Development [EMAIL PROTECTED] T: +1 (918) 640 4414 F: +1 (972) 789 1340 Valtech 5080 Spectrum Drive Suite 700 West Addison, Texas 75001 USA T: +1 (972) 789 1200 From: Sebastien Brunot [mailto:[EMAIL PROTECTED] Sent: Tue 11/7/2006 10:41 AM To: Maven Users List Subject: RE: Transitive dependecies Hi barrett, I think I'm actually proceeding quite the same (the lib pom I was talking about). I really want to know if I can move a step further and make the dependencies not transitive while included in the WAR (actually an EAR in my case ;-). If the feature does not exists yet in maven (using scope settings or something else), I might ask for it: this is why I want to know if it is already possible or not. Sebastien -Original Message- From: Barrett Nuzum [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 07, 2006 5:28 PM To: Maven Users List Subject: RE: Transitive dependecies Sebastien: On my current assignment, we solved this by having one POM for the main dependencies of all projects, and a child POM called WebDependencies. All child projects of type WAR specify WebDependencies as a direct dependency. This *does* include transitive dependencies -- but you should be able to trim down the list of total dependencies included by a significant amount. (The ones you probably actually need.) If you bundle your WAR in an EAR, you can use this Dependencies POM in both the EAR and WAR projects and suppress everything in the WAR's WEB-INF/lib to eliminate duplication further. Hope that helps. Barrett Barrett Nuzum Consultant, Skill Development [EMAIL PROTECTED] T: +1 (918) 640 4414 F: +1 (972) 789 1340 Valtech 5080 Spectrum Drive Suite 700 West Addison, Texas 75001 USA T: +1 (972) 789 1200 From: Sebastien Brunot [mailto:[EMAIL PROTECTED] Sent: Tue 11/7/2006 10:13 AM To: Maven Users List Subject: Transitive dependecies Hi all, transitive dependencies can be a real pain when you have a lot of external dependencies in your project. Using exclusions tags is a tedious operation in this case, so I was wondering if a quicker way exists... How can one create a pom module that contains a list of dependencies (let's name it lib pom), so that when the lib pom is added as a dependecy in let's say a war project, the exact list of dependencies from lib pom (no more, no less = no transitivity) are added to the war WEB-INF/lib ? Thanks for your help, Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Increase maven runtime heap space
Hi, I actually increase the heap space by setting the MAVEN_OPTS variable in the mvn.bat script, it works fine. I've just added the following line at the top of the script (after the two first paragraphs of comments): set MAVEN_OPTS=-DXms_1024M -DXmx=1024M Sebastien -Original Message- From: Van Niekerk, Ida [mailto:[EMAIL PROTECTED] Sent: Friday, November 03, 2006 11:29 AM To: users@maven.apache.org Subject: Increase maven runtime heap space Hi there, Maven is currently hanging and I was advised to increase the available heap space in the Maven runtime, but executing the following command: export MAVEN_OPTS=-Xmx1024m I am just not sure in which file to put this. Do I have to put this in mvn.bat in my parent pom? Any help will be much appreciated. Thanks :-) To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven rant
I'm just joining, but what about creating a wiki with the entire free maven book content so that the (user) community can update it ? I agree to the fact that you need some predefined structure to ensure effective documentation by users / developers. Adding a snipet of documentation should be a no cost operation, and having a predefined structure may help to achieve this goal. Sebastien -Original Message- From: Sebastien Arbogast [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 2:45 PM To: Maven Users List Subject: Re: Maven rant 2 thoughts about what you wrote Vincent: I totally agree on the fact that a few people have to write the core of the documentation before any community effort can be considered. But at some point, a PDF and an errata page is not the best way to create a community effort in order to keep this book up-to-date and more accessible. This leads me to the second point: Maven's wiki doesn't work for the very same reason Cocoon one didn't, for the very same reason I've never seen one good documentation effort based solely on a WIKI: no structure! And that's exactly what your book could be useful as: some sort of a spinal cord on which other content can be aggregated and accumulated over time, and sometimes assimilated on a rewrite. Moreover, I don't believe in Wikis at all because instead of adding some information, it just replaces it, even if it keeps some kind of version tracking behind the scenes. IMHO, Maven documentation should look like that: http://drupal.org/handbooks 2006/10/31, Vincent Massol [EMAIL PROTECTED]: -Original Message- From: Sebastien Arbogast [mailto:[EMAIL PROTECTED] Sent: mardi 31 octobre 2006 14:18 To: Maven Users List Subject: Re: Maven rant I totally agree but I think that the problem is very difficult to solve, especially with all the incredible amount of undeocumented features that Maven has. Moreover, the problem is amplified by the fact that Maven allows the generation of most of the documentation: but if you don't write it, it won't write itself, so you will endup with dead links everywhere. As I see it, the problem in most Open Source projects is that developers do that on their free time, and developers aren't writers: those are two completely different tasks and the second one is not the most enjoyable. And last but not least: Open Source software is highly evolutive: why bother write some documentation for a feature that can be replaced by something more interesting in no-time and without any possible anticipation. The thing is that Maven is not the first Maven project I work with which faces that very issue. I had exactly the same problems a few months ago with Cocoon guys, and my remark is still the same: why do project leaders keep on considering documentation as a static thing. Think of Hibernate or PHP documentation: one base reference book with DYNAMIC comments in which people can share their thoughts and experiences about each feature/chapter, remarks that can be later integrated when the reference is rewritten. The problem is that, whereas development itself is a highly-collaborative and efficient process, nothing is really done so that documentation writing is collaborative enough: no workflow, no direct input, no dynamic comments, etc. Think of it: Better Builds With Maven is the most comprehensive documentation about Maven2. But was it written collaboratively? No. And I'm convinced that if it had been, it would be much higher quality and much more accessible today. Sebastien, I don't believe this is true. This is the same as any open source project. It's not the community that creates an open source project. It's one or two guys (possibly 3 ;-)). Then once there is a strong kernel developed by these few guys then others will join and help. The same is true for documentation. You need one or 2 leaders to first write the core of it. This is what we've done with BBWM. Now I agree that a good idea could be to build on it by opening it up to the community. But don't believe a single instant that the community will write a good quality book by itself. BTW there's already a Maven wiki which is opened to anyone interested. It's been there for more than a year but I wouldn't call the result comprehensive documentation. Thanks -Vincent 2006/10/31, dhoffer [EMAIL PROTECTED]: Jeff, I use maven and I really like it and I don't want this to sound like negative criticism but you are right, the learning curve for maven newbie's is huge and there just isn't much good docs available. I have wound up getting bits of pieces of info from here and there...it just takes so long. It would be great if some maven gurus could solve this problem and make maven more accessible. Jeff Mutonho wrote: Is maven in the process of
RE: Maven rant
I agree that the problem may be faced, but what about trying it the agile way : just putting everything online in a new wiki instance, and waiting a few month to see which how it evolves ? Sebastien (the other one ;-) -Original Message- From: Sebastien Arbogast [mailto:[EMAIL PROTECTED] Sent: Thursday, November 02, 2006 10:31 AM To: Maven Users List Subject: Re: Maven rant But you won't solve the main issue of a wiki system: information replacement. I still think that a comment system would be more reliable on the long term. 2006/11/2, Sebastien Brunot [EMAIL PROTECTED]: I'm just joining, but what about creating a wiki with the entire free maven book content so that the (user) community can update it ? I agree to the fact that you need some predefined structure to ensure effective documentation by users / developers. Adding a snipet of documentation should be a no cost operation, and having a predefined structure may help to achieve this goal. Sebastien -Original Message- From: Sebastien Arbogast [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 2:45 PM To: Maven Users List Subject: Re: Maven rant 2 thoughts about what you wrote Vincent: I totally agree on the fact that a few people have to write the core of the documentation before any community effort can be considered. But at some point, a PDF and an errata page is not the best way to create a community effort in order to keep this book up-to-date and more accessible. This leads me to the second point: Maven's wiki doesn't work for the very same reason Cocoon one didn't, for the very same reason I've never seen one good documentation effort based solely on a WIKI: no structure! And that's exactly what your book could be useful as: some sort of a spinal cord on which other content can be aggregated and accumulated over time, and sometimes assimilated on a rewrite. Moreover, I don't believe in Wikis at all because instead of adding some information, it just replaces it, even if it keeps some kind of version tracking behind the scenes. IMHO, Maven documentation should look like that: http://drupal.org/handbooks 2006/10/31, Vincent Massol [EMAIL PROTECTED]: -Original Message- From: Sebastien Arbogast [mailto:[EMAIL PROTECTED] Sent: mardi 31 octobre 2006 14:18 To: Maven Users List Subject: Re: Maven rant I totally agree but I think that the problem is very difficult to solve, especially with all the incredible amount of undeocumented features that Maven has. Moreover, the problem is amplified by the fact that Maven allows the generation of most of the documentation: but if you don't write it, it won't write itself, so you will endup with dead links everywhere. As I see it, the problem in most Open Source projects is that developers do that on their free time, and developers aren't writers: those are two completely different tasks and the second one is not the most enjoyable. And last but not least: Open Source software is highly evolutive: why bother write some documentation for a feature that can be replaced by something more interesting in no-time and without any possible anticipation. The thing is that Maven is not the first Maven project I work with which faces that very issue. I had exactly the same problems a few months ago with Cocoon guys, and my remark is still the same: why do project leaders keep on considering documentation as a static thing. Think of Hibernate or PHP documentation: one base reference book with DYNAMIC comments in which people can share their thoughts and experiences about each feature/chapter, remarks that can be later integrated when the reference is rewritten. The problem is that, whereas development itself is a highly-collaborative and efficient process, nothing is really done so that documentation writing is collaborative enough: no workflow, no direct input, no dynamic comments, etc. Think of it: Better Builds With Maven is the most comprehensive documentation about Maven2. But was it written collaboratively? No. And I'm convinced that if it had been, it would be much higher quality and much more accessible today. Sebastien, I don't believe this is true. This is the same as any open source project. It's not the community that creates an open source project. It's one or two guys (possibly 3 ;-)). Then once there is a strong kernel developed by these few guys then others will join and help. The same is true for documentation. You need one or 2 leaders to first write the core of it. This is what we've done with BBWM. Now I agree that a good idea could be to build on it by opening it up to the community. But don't believe a single instant that the community will write a good quality book by itself. BTW there's already a Maven wiki which is opened to anyone interested
RE: Maven rant
Good ! When do you think it would be possible to have it online ? Sebastien -Original Message- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Thursday, November 02, 2006 11:44 AM To: Maven Users List Subject: Re: Maven rant Wendy Smoak wrote: On 10/31/06, Sebastien Arbogast [EMAIL PROTECTED] wrote: Think of Hibernate or PHP documentation: one base reference book with DYNAMIC comments in which people can share their thoughts and experiences about each feature/chapter, remarks that can be later integrated when the reference is rewritten. The problem is that, whereas development itself is a highly-collaborative and efficient process, nothing is really done so that documentation writing is collaborative enough: no workflow, no direct input, no dynamic comments, etc. Many of the plugins have improved docs that haven't been published yet. That's on my list for this weekend, determining whether it's okay to publish them, or whether we need to establish a separate area for the latest-and-greatest docs that may not match the released version. What I'd like to do for comments is make use of the MAVENUSER wiki [1]. I'd like to see a link on every plugin site so that users can share configuration examples or tell us that something is just plain wrong. What do you think? Any ideas on how to present that as an option? What would the menu link be called? How should the pages on the wiki be organized? (The Better Builds book belongs to Mergere, so they would have to agree to any changes in the way it is produced.) [1] http://docs.codehaus.org/display/MAVENUSER/Home I think the comments-based approach is the best option. Users can post examples that work. Authors can improve the documentation really easily, taking on board comments. An indication of the page's documentation quality would be the amount of newby questions just asking what to do. Gaps in the documentation would also be identified quickly by users. I think it is by far the most agile approach to documentation. Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven rant
What I meant by it was the comment mechanism. Sebastien -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Thursday, November 02, 2006 3:35 PM To: Maven Users List Subject: Re: Maven rant On 11/2/06, Sebastien Brunot [EMAIL PROTECTED] wrote: Good ! When do you think it would be possible to have it online ? Have what online? We need to decide what it is first. :) What we have available is all of Maven's documentation, (some of which is generated, some is in APT format,) and the MAVENUSER wiki space. Currently, the only connection between the two is the 'User Contributed' link on the main site menu. How do you see this working? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Not embedding pom is jars
Hi, is there an easy way to specify that the pom files shouldn't be embedded in a jar artifact (resulting from the package command) under META-INF ? thaks for your advices, Sebastien
Maven 2 SCM ?
Hi, does anybody know the URL of the maven 2 sources repository ? I can't find it on the maven web site... Thanks, Sebastien
RE: Maven 2 SCM ?
Thanks, that's exactly what I was looking for... Sebastien -Original Message- From: Rémy Sanlaville [mailto:[EMAIL PROTECTED] Sent: Monday, October 30, 2006 4:55 PM To: Maven Users List Subject: Re: Maven 2 SCM ? Hi, Have a look to https://svn.apache.org/repos/asf/maven/ HTH, Rémy 2006/10/30, Sebastien Brunot [EMAIL PROTECTED]: Hi, does anybody know the URL of the maven 2 sources repository ? I can't find it on the maven web site... Thanks, Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
conditionals ant execution
Hi, is it possible to specify a conditional (as in target if=[...]) for the antrun plugin execution ? A conditional would specify something to be verified for the ant script scnipet below the tasks tags to be executed. Sebastien
