Re: Maven Plugin to detect duplicate class files in a e.g. WAR
maven-shade-plugin's shade goalhttp://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.htmlwill display warnings for duplicate classes when generating uber-jar. Stephen, maybe you can reuse some parts of the logic from there for the new mojo. Regards, Stevo. On Sat, Dec 12, 2009 at 9:13 PM, lukewpatterson lukewpatter...@gmail.comwrote: Mirko Friedenhagen wrote: goal to check classpath for duplicate resources/classes I haven't tried it yet, but recently I was looking for the same functionality and ran across JBoss' tattletale tool: http://www.jboss.org/tattletale http://www.jboss.org/tattletale JBoss Tattletale is a tool that can help you get an overview of the project you are working on or a product that you depend on. The tool will provide you with reports that can help you Identify dependencies between JAR files Find missing classes from the classpath Spot if a class/package is located in multiple JAR files Spot if the same JAR file is located in multiple locations With a list of what each JAR file requires and provides Verify the SerialVersionUID of a class Find similar JAR files that have different version numbers Find JAR files without a version number Find unused JAR archives Identify sealed / signed JAR archives Locate a class in a JAR file Get the OSGi status of your project Remove black listed API usage -- View this message in context: http://old.nabble.com/Maven-Plugin-to-detect-duplicate-class-files-in-a-e.g.-WAR-tp26658458p26760767.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
Re: m2eclipse problem
Nabble shows it being active: http://old.nabble.com/Maven-Eclipse---User-f14525.html /Anders On Sat, Dec 12, 2009 at 23:50, Steve Cohen sco...@javactivity.org wrote: Steve Cohen wrote: I know there's an m2eclipse mailing list but it doesn't seem to be respoding to subscription requests so I thought maybe I'd ask this here. I have an old Eclipse workspace, in which the M2Eclipse functions properly, as far as scanning for dependencies is concerned. I created a new Eclipse workspace this afternoon. In this workspace, no matter what I do, the M2-Add Dependency menu item is non-functional. No matter what artifacts I ask to add dependencies for, it finds nothing. It appears not to be hooked up to any external repository. Yet the other workspace, for which every maven setting is exactly the same finds all dependencies easily. Using Eclipse 3.5 (Galileo) on Windows XP. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org As I stated above, this is not the place for this. The right place is the m2eclipse mailing list, but does anyone know what's wrong with the m2eclipse mailing list? It is not responding to my subscription requests. Does anyone know if that list is active? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: m2eclipse problem
Hi, Maybe you have download repository index updates at startup unchecked in your maven preferences ? I think M2Eclipse use these index to search for artefacts when adding dependency ... Frédéric On Sun, Dec 13, 2009 at 10:56 AM, Anders Hammar and...@hammar.net wrote: Nabble shows it being active: http://old.nabble.com/Maven-Eclipse---User-f14525.html /Anders On Sat, Dec 12, 2009 at 23:50, Steve Cohen sco...@javactivity.org wrote: Steve Cohen wrote: I know there's an m2eclipse mailing list but it doesn't seem to be respoding to subscription requests so I thought maybe I'd ask this here. I have an old Eclipse workspace, in which the M2Eclipse functions properly, as far as scanning for dependencies is concerned. I created a new Eclipse workspace this afternoon. In this workspace, no matter what I do, the M2-Add Dependency menu item is non-functional. No matter what artifacts I ask to add dependencies for, it finds nothing. It appears not to be hooked up to any external repository. Yet the other workspace, for which every maven setting is exactly the same finds all dependencies easily. Using Eclipse 3.5 (Galileo) on Windows XP. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org As I stated above, this is not the place for this. The right place is the m2eclipse mailing list, but does anyone know what's wrong with the m2eclipse mailing list? It is not responding to my subscription requests. Does anyone know if that list is active? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Assembly Plugin 2.2-beta-5 Released
The Maven team is pleased to announce the release of the Maven Assembly Plugin, version 2.2-beta-5. This plugin is useful in creating project artifacts that have custom layouts. It also includes a set of predefined standard custom artifact types you can choose to create. For more information, see the plugin's site: http://maven.apache.org/plugins/maven-assembly-plugin/ To use the updated plugin in your projects, you need to add the following snippet to the plugins or plugin management section of your POM: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.2-beta-5/version /plugin Release Notes - Maven 2.x Assembly Plugin - Version 2.2-beta-5 ** Bug * [MASSEMBLY-385] - Filtering replaces tokens it should not be replacing * [MASSEMBLY-416] - outputDirectory default value in fileSet seems changed; now seems to use directory name of fileSet sourcedir * [MASSEMBLY-427] - ComponentsXmlArchiverFileFilter misses component descriptors on Windows * [MASSEMBLY-446] - apache-source-release-assembly DOES NOT exclude target/** in maven-remote-resources-plugin build * [MASSEMBLY-452] - Shared Assembly Descriptor does not work in Maven3-alpha4 * [MASSEMBLY-456] - Usage of archiver or container descriptor handler configuration crashes with LinkageError on Maven 3.0-alpha-5 ** Improvement * [MASSEMBLY-290] - Improve error reporting in case of unlocatable component descriptor Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven PDF Plugin 1.1 Released
The Maven team is pleased to announce the release of the Maven PDF Plugin, version 1.1 This plug-in allows you to generate a PDF version of your project's documentation. http://maven.apache.org/plugins/maven-pdf-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pdf-plugin/artifactId version1.1/version /plugin Release Notes - Maven 2.x PDF Plugin - Version 1.1 ** Bug * [MPDF-17] - Test fails with JDK 1.5+ if base directory has a space in its path * [MPDF-28] - When specifying output dir, copy only the generated pdf * [MPDF-31] - LinkageError using JDK6 ** Improvement * [MPDF-23] - Definition Lists are not formatted correctly * [MPDF-26] - Add report generation in PDF * [MPDF-27] - Support Doxia files generated by Maven plugins * [MPDF-30] - Add a parameter to include or not the TOC ** New Feature * [MPDF-24] - Support Velocity files ** Wish * [MPDF-16] - Add German translation Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [Release] scm getting rewritten. how does it work?
Hi,
thanks a lot for the answers. And sorry for the delay, I was actually busy
with releases! that's how this post question got to mind.
In my case, it's a parent-pom only, no module included. We use aggregator
only to refactor dependencies, so that we can open the module and all it's
dependants.
We deploy everything with release:prepare release:perform.
If I get you correctly Stephen, the child module's artifactId is actually
replaced in the scm url, and not appended.
in this case, it's probably not useful to append ${artifactId} at the end of
my scm url, isn't it?
scm
connectionscm:svn:${svn.root}/trunk/${artifactId}/connection
developerConnectionscm:svn:${svn.root}/trunk/${artifactId}/developerConnection
url${svn.root}/trunk/${artifactId}/url
/scm
the last / part after trunk shouldn't be useful.
I'm actually using variables so that the scm url keeps flexible in case we
change anything with the versioning system, and so that it's valid for every
child project.
But if it's get solidified at deployment time, it means that all my release
of the parent-pom get a solidified scm.
How can this parent-pom with a solidified scm -
scm:svn:svn://company/trunk/company-parent - be valid for deployment of
child projects???
That's a lot of magic going here obviously!
In any case, even if I don't need the ${artifactId} in the scm url, I'd be
happy to keep the ${scm.root} flexibility.
How can I keep this if the url gets solidified and commited at each
deployment?? (I know this answer: by hand :) )
But it seems http://jira.codehaus.org/browse/MRELEASE-128 is still not
clsed, so I'm proabably not the only one asking for it!
cheers
-jean
Stephen Connolly-2 wrote:
you have to be clear about what I will call as release roots
A release root is a project that has an scm section.
It will typically be an aggregator project (i.e. packaging=pom
modules.size()0) but it does not need to be.
If it is a parent project (i.e. at least one of the modules it
aggregates references it as a parent you do know that aggregation
does not have to follow inheritance by the way) then the scm
information is transformed when being inherited, so that the child
module's artifactId is appended to the scm url.
in general, you should run mvn release:prepare release:perform from
a release root, it will generate one tag of everything that is
contained below the release root.
in this case, you should always ensure that your modules definitions
do not jump back up (e.g. you don't have
modules../someother/modules) as that would break the tagging for
you. If you have to 'jump back up' then you probably need to set the
configuration parameter commitByProject=true on the release plugin
and you should explicitly set the scm information on the 'jump back
up' modules.
the scm information has to be solidified at deployment time, so what
happens is that the ${project.artifactId} gets replaced with the
actual artifactId in the scm information... there are a number of bugs
in earlier versions of maven where this information was not getting
solidified.
Additionally there might be some magic about when the scm url ends
with a / or not which might control whether or not the inheriting
module gets it's artifactId appended to the inherited scm url
-Stephen
2009/12/3 nodje nodje...@gmail.com:
Hi,
I'm using maven-release-plugin 2.0-beta9 and I'm still getting scm urls
rewritten at each deployment.
http://jira.codehaus.org/browse/MRELEASE-231 is been closed quite a while
ago, so many we're not speaking about the same rewriting.
The way we use the SCM tag in our organization is trough a parent pom
that
is suppose to set the SCM for each every child project.
It looks like this:
scm
connectionscm:svn:${svn.root}/trunk/${artifactId}/connection
developerConnectionscm:svn:${svn.root}/trunk/${artifactId}/developerConnection
url${svn.root}/trunk/${artifactId}/url
/scm
What I'm not getting is that while it's the only SCM tag in the whole
maven configuration, it gets rewritten at parent-pom deployment time WITH
parent-pom properties.
Even though, when releasing a child project based on this parent release,
Release plugin seems to find it's way to our Subversion without any other
help.
I really don't understand how this can possibly work.
Could somebody enlighten me on this?
rgds
-jean
--
View this message in context:
http://old.nabble.com/-Release--%3Cscm%3E-getting-rewritten.-how-does-it-work--tp26621596p26621596.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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands,
Re: modules are built but not copied to local repository?
Kinh, When doing mvn clean, I get a message about a missing plugin: [INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=cosmos.distribution.deployment -DartifactId=fdf-plugin -Dversion=0.1.8-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=cosmos.distribution.deployment -DartifactId=fdf-plugin -Dversion=0.1.8-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] cosmos.distribution.deployment:fdf-plugin:maven-plugin:0.1.8-SNAPSHOT Where is that plugin? Some repo I need to configure in my settings.xml? /Anders On Fri, Dec 11, 2009 at 17:48, NGUYEN Cong Kinh cong_kinh.ngu...@it-sudparis.eu wrote: Please send this error to me. Because I haven't seen it. Thank you. Kinh Anders Hammar a écrit : After checking out and building for ages I get a NPE in helloworld ex 1... /Anders On Fri, Dec 11, 2009 at 13:55, NGUYEN Cong Kinh cong_kinh.ngu...@it-sudparis.eu wrote: In fact, in the trunk/B, there are some modules, for example B1 B2, but B2 uses B1 as the dependency. When executing the command mvn clean install for B2, Maven finds the dependency B1, but it is not located in local repository. Therefore, there's an error missing artifact You can check at svn co svn+ssh://gu...@picoforge.int-evry.fr/cosmos/trunk with guest as password (twice for entering password) Kinh Anders Hammar a écrit : What does the build output say - any errors? /Anders On Fri, Dec 11, 2009 at 13:38, NGUYEN Cong Kinh cong_kinh.ngu...@it-sudparis.eu wrote: Hello everybody, I'm using Maven 2.2.1, JDK 6. I have a problem concerning compilation by Maven. In fact, for example I have the following structure: - trunk + pom.xml +-- A + pom.xml +-- A1 + pom.xml +-- A11 ... +-- A12 ... +-- A2 +-- A3 +-- B +-- B1 In the trunk, I execute the mvn clean install (before executing this command, I used rm -rf ~/.m2/repository). Only modules in the trunk/A are copied to ~/.m2/repository. The other modules in trunk/B, they compiled to target/..., but they aren't copied to ~/.m2/repository. Is there any way to specify that they must be copied to local repository ? Thanks in advance, Kinh - 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
