Re: Changes plugin contribution
Emmanuel Venisse a écrit : Emmanuel Hugonnet a écrit : zze-HUGONNET E ext RD-BIZZ a écrit : Emmanuel Hugonnet a écrit : Stephane Nicoll a écrit : Hi, Where is the source code of your plugin? If it's valuable we can certainly have a look :) Thanks, Stéphane On 5/3/07, ehsavoie [EMAIL PROTECTED] wrote: Hi, I have developped a Maven2 plugin that build a report equivalent to the changes report but which uses svn comment parsing instead of changes.xml. The parsing rules are configurable and can be overriden (I am providing 2 rules as examples). Links to the bug trackers are also configurable with currently 2 kinds of links (JIRA and Sourceforge) but it supports also a pattern to create them. I would like to contribute it to the maven-changes-plugin since it loks to be a feature improvement of it. The only problem with this plugin is that is doesn't use plexus-utils for the cli but my 'own' implementation using the jdk API for processes. Is the changes-plugin team interested in it ? Should I move it to codehaus and wait for a possible merger after ? Thanks, Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sorry if I make a double post. Well it is currently on my workstation. I can send it to you by mail or maybe I could create a JIRA for the changes-plugin and put it there. What is the best solution ? Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok I have attached the code with the JIRA *MCHANGES-78 http://jira.codehaus.org/browse/MCHANGES-78. *Give it a try ;o) You should have some comment on your svn with @fix:bug_ref; Comment or @update:;Comment etc. Feel free to ask any question if it is not clear as I am not an english spoken person ;o) Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I have rewritten it to be compatible with JDK 1.4 . As for Emmanuel's remarks I agree that it should be better but Maven-SCM is not easy to use since I have to create my own svn provider (extending the current one) just to add the xml option. Also it seems to execute the list and log commands recursively (maybe I made some mistakes while trying to use it) and I just gave up :o( If you think that this plugin is useful and someone could spare some time or some example on own to start with plexus cli and Maven-SCM considering these issues I would gratefully comply to Emmanuel's remarks and clean my code. I don't know why you need the list command (haven't look at your code yet) but for the log command, you can look at the changelog plugin, it's its job. Emmanuel Thanks, Emmanuel - 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] Hi, I use the list command to get all the tags and their revision numbers so I can group comments per releases (assuming each entry in tags is a release). This way you get your changelog per release and what is currently in the trunk. Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release maven-release-plugin 2.0-beta-5
Vote results:
+1 Binding: Emmanuel, Arnaud, Fabrizio, Vincent S., Stéphane
+1 non binding: Daniel Kulp
The release will be available on central at the next sync.
Thanks,
Stéphane
On 5/1/07, Stephane Nicoll [EMAIL PROTECTED] wrote:
Hi,
I'd like to release the maven release plugin which includes the maven
release manager and the maven release parent pom.
The staging bits are available here:
http://people.apache.org/~snicoll/maven-staging/repo/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
** Bug
* [MRELEASE-3] - release:prepare should not require multimodule
artifacts to be in the local repository
* [MRELEASE-6] - Multiproject Release: No check in
* [MRELEASE-16] - release-pom is changed too much
* [MRELEASE-35] - release plugin doesn't tag correctly with
svn+ssh when remote and local username don't match
* [MRELEASE-90] - Exception if version is SNAPSHOT
* [MRELEASE-91] - Updating of dependencyManagement inconsistent
with updating of dependencies with regard to SNAPSHOTs
* [MRELEASE-94] - Modified Parent POM is not commited
* [MRELEASE-107] - scm.url gets translated incorrectly during release
* [MRELEASE-110] - release:prepare generates tags with dots,
causing problems with CVS
* [MRELEASE-114] - ${project.artifactId} was replaced with it's
value during release:perform
* [MRELEASE-115] - Issue URL on pom is incorrect
* [MRELEASE-116] - Wrong SCM info put by the release plugin for modules
* [MRELEASE-122] - Versionless Extension causes
NullPointerException in release:prepare
* [MRELEASE-128] - SCM properties being replaced during release:perform
* [MRELEASE-131] - release:prepare failed in 'cvs ... commit'
phase for multi-module build
* [MRELEASE-137] - proposed SCM release tag or label in multiproject
* [MRELEASE-142] - Batch mode release plugin uses an invalid tag
* [MRELEASE-144] - Release plugin did not ask for a Subversion tag
* [MRELEASE-147] - Version number for a dependency with
${pom.groupId} not updated in multi-module.
* [MRELEASE-151] - All child modules are forced to share the same parent POM
* [MRELEASE-160] - The next snapshot version is not used un submodules
* [MRELEASE-168] - All submodule projects must be from the same
subversion repository
* [MRELEASE-180] - Rewritten poms loose comments
* [MRELEASE-190] - scmTagPhase scm comment when creating the
branch/tag directory uses the prefix [maven-scm]
* [MRELEASE-191] - Certain tests fail when checked-out in 'projects' subdir
* [MRELEASE-194] - SNAPSHOT as property bypasses dependency snapshot check
* [MRELEASE-197] - Release plugin documentation on
maven.apache.org has broken link to release:rollback
* [MRELEASE-202] - snapshot versions in dependencyManagement are not updated
* [MRELEASE-209] - Snapshot versions are not restored correctly on
next development version
* [MRELEASE-219] - Spurious warnings given when a release contains
subversion externals
* [MRELEASE-221] - XML header missing in modified POM after release:prepare
* [MRELEASE-222] - Wrong default tag name when used in a reactor environment
** Improvement
* [MRELEASE-112] - release plugin should have option to ignore
snapshots of the release plugin
* [MRELEASE-145] - release:prepare requires all modules to be SNAPSHOTS
* [MRELEASE-183] - should report all unresolved dependencies, not
just the first encountered.
* [MRELEASE-208] - Support for ClearCase, and other SCMs that do
checkout projects to subdirectories of the checkout directory
* [MRELEASE-214] - scm:tag with scmCommentPrefix
* [MRELEASE-220] - Add property to keep released versions for dependencies
** New Feature
* [MRELEASE-130] - Create a model for a release
* [MRELEASE-157] - Share version for multi-module releases
* [MRELEASE-169] - Provide a mechanism to undo the effects of prepare
** Task
* [MRELEASE-141] - Review Plugin Documentation
* [MRELEASE-162] - Move all release core code in maven/shared
Vote open for 72 hours
My +1
Thanks,
Stéphane
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Release Plugin 2.0-beta-5 Released
The Maven team is pleased to announce the release of the Maven Release Plugin,
version 2.0-beta-5
http://maven.apache.org/plugins/maven-release-plugin/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
** Bug
* [MRELEASE-3] - release:prepare should not require multimodule
artifacts to be in the local repository
* [MRELEASE-6] - Multiproject Release: No check in
* [MRELEASE-16] - release-pom is changed too much
* [MRELEASE-35] - release plugin doesn't tag correctly with
svn+ssh when remote and local username don't match
* [MRELEASE-90] - Exception if version is SNAPSHOT
* [MRELEASE-91] - Updating of dependencyManagement inconsistent
with updating of dependencies with regard to SNAPSHOTs
* [MRELEASE-94] - Modified Parent POM is not commited
* [MRELEASE-107] - scm.url gets translated incorrectly during release
* [MRELEASE-110] - release:prepare generates tags with dots,
causing problems with CVS
* [MRELEASE-114] - ${project.artifactId} was replaced with it's
value during release:perform
* [MRELEASE-115] - Issue URL on pom is incorrect
* [MRELEASE-116] - Wrong SCM info put by the release plugin for modules
* [MRELEASE-122] - Versionless Extension causes
NullPointerException in release:prepare
* [MRELEASE-128] - SCM properties being replaced during release:perform
* [MRELEASE-131] - release:prepare failed in 'cvs ... commit'
phase for multi-module build
* [MRELEASE-137] - proposed SCM release tag or label in multiproject
* [MRELEASE-142] - Batch mode release plugin uses an invalid tag
* [MRELEASE-144] - Release plugin did not ask for a Subversion tag
* [MRELEASE-147] - Version number for a dependency with
${pom.groupId} not updated in multi-module.
* [MRELEASE-151] - All child modules are forced to share the same parent POM
* [MRELEASE-160] - The next snapshot version is not used un submodules
* [MRELEASE-168] - All submodule projects must be from the same
subversion repository
* [MRELEASE-180] - Rewritten poms loose comments
* [MRELEASE-190] - scmTagPhase scm comment when creating the
branch/tag directory uses the prefix [maven-scm]
* [MRELEASE-191] - Certain tests fail when checked-out in 'projects' subdir
* [MRELEASE-194] - SNAPSHOT as property bypasses dependency snapshot check
* [MRELEASE-197] - Release plugin documentation on
maven.apache.org has broken link to release:rollback
* [MRELEASE-202] - snapshot versions in dependencyManagement are not updated
* [MRELEASE-209] - Snapshot versions are not restored correctly on
next development version
* [MRELEASE-219] - Spurious warnings given when a release contains
subversion externals
* [MRELEASE-221] - XML header missing in modified POM after release:prepare
* [MRELEASE-222] - Wrong default tag name when used in a reactor environment
** Improvement
* [MRELEASE-112] - release plugin should have option to ignore
snapshots of the release plugin
* [MRELEASE-145] - release:prepare requires all modules to be SNAPSHOTS
* [MRELEASE-183] - should report all unresolved dependencies, not
just the first encountered.
* [MRELEASE-208] - Support for ClearCase, and other SCMs that do
checkout projects to subdirectories of the checkout directory
* [MRELEASE-214] - scm:tag with scmCommentPrefix
* [MRELEASE-220] - Add property to keep released versions for dependencies
** New Feature
* [MRELEASE-130] - Create a model for a release
* [MRELEASE-157] - Share version for multi-module releases
* [MRELEASE-169] - Provide a mechanism to undo the effects of prepare
** Task
* [MRELEASE-141] - Review Plugin Documentation
* [MRELEASE-162] - Move all release core code in maven/shared
Enjoy!
- The Maven Team
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
apache-jar-resource-bundle and dependencies license
Hi all, I'm a PMC member of the Apache JAMES project. Few months ago we worked together with Cliff Schmidt on Legal/licensing issues and our JAMES Server product and the result was that we had to add this text in the bottom of our *LICENSE* file: THIS PRODUCT ALSO INCLUDES THIRD PARTY SOFTWARE REDISTRIBUTED UNDER THE FOLLOWING LICENSES: Concurrent, Public Domain (see lib/concurrent.LICENSE) BouncyCastle, MIT License (see lib/BouncyCastle.LICENSE) http://www.bouncycastle.org/licence.html DnsJava, BSD License (see lib/dnsjava.LICENSE) http://www.dnsjava.org/README JavaBeans Activation Framework, CDDL License http://glassfish.dev.java.net/public/CDDLv1.0.html JavaMail, CDDL License http://glassfish.dev.java.net/public/CDDLv1.0.html QDox, ASL 1.1 License (see tools/lib/qdox.LICENSE) http://qdox.codehaus.org/license.html MX4J, ASL 1.1 License (see phoenix-bin/bin/lib/mx4j.LICENSE) Spice, ASL 1.1 License (see phoenix-bin/bin/lib/spice.LICENSE) http://spice.codehaus.org/license.html Wrapper, MIT License (see phoenix-bin/bin/Wrapper.LICENSE) http://wrapper.tanukisoftware.org/doc/english/license.html ISO-Relax, MIT License (see phoenix-bin/tools/lib/isorelax.LICENSE) MSV, BSD License (see phoenix-bin/tools/lib/msv.LICENSE) RelaxNG-Datatype, BSD License (see phoenix-bin/tools/lib/relaxngDatatype.LICENSE) XSDLib, BSD License (see phoenix-bin/tools/lib/xsdlib.LICENSE) I see, instead, that apache-jar-resource-bundle include licenses informations in the NOTICE file. IIRC this is not the right place for LICENSEs. I know I can create our own (james-project) remote-resource and change the velocity scripts to put licenses in LICENSE instead of NOTICE, but I wanted to check this issue with you, first. Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
avoid that central repo gets garbage dump
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I am seeing more and more the need that the community takes better control over what is dumped into the central repo. This seems to get more and more like a rubbish dump. There are duplications of the logically same artifacts. This causes extremly ugly situations in projects with a high level of integration, because you may end up with the same code multiple times in your classpath. To point this out just two examples: javax.persistence with 3 different groupId's: http://repo1.maven.org/maven2/javax/persistence/ http://download.java.net/maven/1/javax.ejb/jars/ spring: http://repo1.maven.org/maven2/org/springframework/ there is an all-in-one actifact (spring) as well as fine modularized artifacts (spring-core, etc.). You might say that this is the problem of the projects producing such artifacts. If you ask me this is also a question about wether maven2 is a real success or not. In such situations I hear many people scream that dependency management is the gate to hell. It is definetly not, but you get punished by the bad work of the others. And if you look at the zoo of senseless dependecies of apache artifacts such as xerces or some of the commons it is really a pitty! Please also consider that it is NOT an option to remove or modify an artifact from the central repository. There is the need to tripple-think about it before adding an artifact to the central repository ESPECIALLY if the one putting it into the repository is NOT the creator of the artifact. I am already active on the mailing-lists of several other open-source projects trying to convince the people about the need and the impact of maintaining their artifacts properly themselves for being uploaded to ibiblio. It is somewhat strange that even apache-projects like lucene or POI dont think much of maven and need to be convinced that it is worth the effort of providing valid and senseful POMs for their artifacts and staging them to ibiblio. For lucene I provided the POMs for some contrib half a year ago and nothing happened so far. Greetings from a maven fan that is a little frustrated Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGO5dymPuec2Dcv/8RAhS7AJsFQK0ro4tECUhvtdqXNJ2GYy2WgACdGBXY igNS02rPP8PH1lA1rVYiIJg= =9+xA -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] [m1] couple of plugins for rc1
+1 for all Arnaud On 02/05/07, Stephane Nicoll [EMAIL PROTECTED] wrote: +1 Stéphane On 5/1/07, Lukas Theussl [EMAIL PROTECTED] wrote: Hi, Here's a bunch of plugins I'd like to release for inclusion in m11-rc1: maven-artifact-plugin-1.9 maven-changelog-plugin-1.9.2 maven-dist-plugin-1.7.1 maven-eclipse-plugin-1.12 maven-ejb-plugin-1.7.3 maven-linkcheck-plugin-1.4.1 maven-multiproject-plugin-1.5.1 maven-test-plugin-1.8.1 maven-war-plugin-1.6.3 maven-xdoc-plugin-1.10.1 Most of them were ready since a long time and were only waiting for the maven-model-3.0.2 release that happened last week. Otherwise changes are mostly minor, except for the artifact plugin, which will now only work with rc1. Due to the maven-model dependency, I plan to announce the release of these plugins together with the rc1 release only. +1 from me, 72h to vote... Thanks, -Lukas http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugins/artifact/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugins/changelog/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugins/dist/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugins/eclipse/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugins/ejb/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugins/linkcheck/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugins/multiproject/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugins/test/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugins/war/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugins/xdoc/ maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-artifact-plugin -Dversion= 1.9-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-changelog-plugin -Dversion= 1.9.2-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-dist-plugin -Dversion=1.7.1-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-eclipse-plugin -Dversion= 1.12-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-ejb-plugin -Dversion=1.7.3-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-linkcheck-plugin -Dversion= 1.4.1-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-multiproject-plugin -Dversion=1.5.1-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-test-plugin -Dversion=1.8.1-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-war-plugin -Dversion=1.6.3-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-xdoc-plugin -Dversion=1.10.1-SNAPSHOT - 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] -- .. Arnaud Héritier OCTO Technology [EMAIL PROTECTED] .. 50, Avenue des Champs-Elysées 75008 Paris Tél : (33) 1 58 56 10 00 Fax : (33) 1 58 56 10 01 GSM : (33) 6 03 52 71 31 www.octo.com | blog.octo.com ...
Re: Central Repository for Maven 2.0.6
2007/5/3, Jorg Heymans [EMAIL PROTECTED]: Thierry Barnier wrote: Hi Jaish, I would recommend you the following maven proxies -AbstractHorizon Proximity http://proximity.abstracthorizon.org/ -Apache Archiva http://maven.apache.org/archiva/ -Mergere Maestro http://www.mergere.com/ -Maven proxy http://maven-proxy.codehaus.org/ You left out the one i consider to be the best for the moment: Artifactory (jfrog.org) Jorg My bad :) Thierry -- Thierry Barnier - cell: 404-771-3048 - [EMAIL PROTECTED]
Re: [vote][m1] maven-nsis-plugin 2.1
+1
-Lukas
Arnaud HERITIER wrote:
And now, Ladies and Gentlemen,
(the drum is rumbling )
This is the last plugin that we need to release for maven 1.1 RC1 ;-)
Changes included in this version :
New Features:
o Add a new template using MODERN_UI macros for a better Look and Feel.
Fixes MPNSIS-15.
o The script remove-shortcuts.nsh can be used to remove shortcuts created
in startmenu-shortcuts.nsh and desktop-shortcuts.nsh. Fixes MPNSIS-13.
Changes:
o Set compress options (force/lzma).
o NSIS plugin does not support silent uninstall. Remove the final dialog
box. Fixes MPNSIS-12.
o Add directories ${maven.nsis.src}, ${maven.build.dir}, and ${
plugin.resources} to search NSIS plugins.
Download :
maven plugin:download
-Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/,
http://repo1.maven.org/maven
-DgroupId=maven
-DartifactId=maven-nsis-plugin
-Dversion=2.1-SNAPSHOT
Staging site :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/nsis/http://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/plugin/
Screenshots (of the future setup of M1.1 RC1) :
http://people.apache.org/~aheritier/staging-sites/m1-plugins/maven-1.x/plugins/nsis/screenshots.htmlhttp://people.apache.org/%7Eaheritier/staging-sites/m1-plugins/maven-1.x/plugins/nsis/screenshots.html
Normal voting rules, 72 hours, +1/0/-1
My +1
Arnaud
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: apache-jar-resource-bundle and dependencies license
Stefano, This is kind of frustrating. The current bundle format is the format that the incubator folks (which Cliff is one of) pushed a bunch of projects into using about 6 months ago. MANY projects have been released using this format in the past few months.Several in the last couple weeks in fact. I guess my thought at this point is to hand the two templates to Cliff and have him fix them. I'm pretty sick of dealing with the ever changing requirements from them. If we can get them to sign off on exact templates, then we'll create a new bundle with those. They need to get their act together, get the requirements nailed down and documented, then we can actual implement it. Dan On Friday 04 May 2007 14:46, Stefano Bagnara wrote: Hi all, I'm a PMC member of the Apache JAMES project. Few months ago we worked together with Cliff Schmidt on Legal/licensing issues and our JAMES Server product and the result was that we had to add this text in the bottom of our *LICENSE* file: THIS PRODUCT ALSO INCLUDES THIRD PARTY SOFTWARE REDISTRIBUTED UNDER THE FOLLOWING LICENSES: Concurrent, Public Domain (see lib/concurrent.LICENSE) BouncyCastle, MIT License (see lib/BouncyCastle.LICENSE) http://www.bouncycastle.org/licence.html DnsJava, BSD License (see lib/dnsjava.LICENSE) http://www.dnsjava.org/README JavaBeans Activation Framework, CDDL License http://glassfish.dev.java.net/public/CDDLv1.0.html JavaMail, CDDL License http://glassfish.dev.java.net/public/CDDLv1.0.html QDox, ASL 1.1 License (see tools/lib/qdox.LICENSE) http://qdox.codehaus.org/license.html MX4J, ASL 1.1 License (see phoenix-bin/bin/lib/mx4j.LICENSE) Spice, ASL 1.1 License (see phoenix-bin/bin/lib/spice.LICENSE) http://spice.codehaus.org/license.html Wrapper, MIT License (see phoenix-bin/bin/Wrapper.LICENSE) http://wrapper.tanukisoftware.org/doc/english/license.html ISO-Relax, MIT License (see phoenix-bin/tools/lib/isorelax.LICENSE) MSV, BSD License (see phoenix-bin/tools/lib/msv.LICENSE) RelaxNG-Datatype, BSD License (see phoenix-bin/tools/lib/relaxngDatatype.LICENSE) XSDLib, BSD License (see phoenix-bin/tools/lib/xsdlib.LICENSE) I see, instead, that apache-jar-resource-bundle include licenses informations in the NOTICE file. IIRC this is not the right place for LICENSEs. I know I can create our own (james-project) remote-resource and change the velocity scripts to put licenses in LICENSE instead of NOTICE, but I wanted to check this issue with you, first. Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: eclipse plugin and custom lyfecycle
On 5/2/07, nicolas de loof [EMAIL PROTECTED] wrote: The eclipse plugin currently requires code-generation plugins to attain the generate-x phase. To integrate the eclipse checkstyle plugin, we need to put the .checkstyle file either in SVN or in the POM. We put it in our top level POM for company wide settings. It does require that the user configure their Eclipse with a checkstyle configuration named exactly as per the POM. But you get warnings if you have forgotten that step. What about defining a custom lyfecycle phase for developper environement setting ? Not sure how this would work. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: avoid that central repo gets garbage dump
We are really aware of these problems, and it's not just Maven, Ant, Ivy and other tools also make use of the repository. There are mailing lists [EMAIL PROTECTED] (for ASF repository) and [EMAIL PROTECTED] (for the whole central repo). i'd just point to http://maven.apache.org/guides/mini/guide-maven-evangelism.html http://maven.apache.org/guides/mini/guide-central-repository-upload.html to fix problems when the original projects don't care about the repository On 5/4/07, Joerg Hohwiller [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I am seeing more and more the need that the community takes better control over what is dumped into the central repo. This seems to get more and more like a rubbish dump. There are duplications of the logically same artifacts. This causes extremly ugly situations in projects with a high level of integration, because you may end up with the same code multiple times in your classpath. To point this out just two examples: javax.persistence with 3 different groupId's: http://repo1.maven.org/maven2/javax/persistence/ http://download.java.net/maven/1/javax.ejb/jars/ spring: http://repo1.maven.org/maven2/org/springframework/ there is an all-in-one actifact (spring) as well as fine modularized artifacts (spring-core, etc.). You might say that this is the problem of the projects producing such artifacts. If you ask me this is also a question about wether maven2 is a real success or not. In such situations I hear many people scream that dependency management is the gate to hell. It is definetly not, but you get punished by the bad work of the others. And if you look at the zoo of senseless dependecies of apache artifacts such as xerces or some of the commons it is really a pitty! Please also consider that it is NOT an option to remove or modify an artifact from the central repository. There is the need to tripple-think about it before adding an artifact to the central repository ESPECIALLY if the one putting it into the repository is NOT the creator of the artifact. I am already active on the mailing-lists of several other open-source projects trying to convince the people about the need and the impact of maintaining their artifacts properly themselves for being uploaded to ibiblio. It is somewhat strange that even apache-projects like lucene or POI dont think much of maven and need to be convinced that it is worth the effort of providing valid and senseful POMs for their artifacts and staging them to ibiblio. For lucene I provided the POMs for some contrib half a year ago and nothing happened so far. Greetings from a maven fan that is a little frustrated Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGO5dymPuec2Dcv/8RAhS7AJsFQK0ro4tECUhvtdqXNJ2GYy2WgACdGBXY igNS02rPP8PH1lA1rVYiIJg= =9+xA -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] [m1] couple of plugins for rc1
+1 for all -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Friday, May 04, 2007 4:41 PM To: Maven Developers List Subject: Re: [vote] [m1] couple of plugins for rc1 +1 for all Arnaud On 02/05/07, Stephane Nicoll [EMAIL PROTECTED] wrote: +1 Stéphane On 5/1/07, Lukas Theussl [EMAIL PROTECTED] wrote: Hi, Here's a bunch of plugins I'd like to release for inclusion in m11-rc1: maven-artifact-plugin-1.9 maven-changelog-plugin-1.9.2 maven-dist-plugin-1.7.1 maven-eclipse-plugin-1.12 maven-ejb-plugin-1.7.3 maven-linkcheck-plugin-1.4.1 maven-multiproject-plugin-1.5.1 maven-test-plugin-1.8.1 maven-war-plugin-1.6.3 maven-xdoc-plugin-1.10.1 Most of them were ready since a long time and were only waiting for the maven-model-3.0.2 release that happened last week. Otherwise changes are mostly minor, except for the artifact plugin, which will now only work with rc1. Due to the maven-model dependency, I plan to announce the release of these plugins together with the rc1 release only. +1 from me, 72h to vote... Thanks, -Lukas http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugin s/artifact/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugin s/changelog/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugin s/dist/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugin s/eclipse/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugin s/ejb/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugin s/linkcheck/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugin s/multiproject/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugin s/test/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugin s/war/ http://people.apache.org/~ltheussl/staging-sites/m1-plugins/maven-1.x/plugin s/xdoc/ maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-artifact-plugin -Dversion= 1.9-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-changelog-plugin -Dversion= 1.9.2-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-dist-plugin -Dversion=1.7.1-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-eclipse-plugin -Dversion= 1.12-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-ejb-plugin -Dversion=1.7.3-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-linkcheck-plugin -Dversion= 1.4.1-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-multiproject-plugin -Dversion=1.5.1-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-test-plugin -Dversion=1.8.1-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-war-plugin -Dversion=1.6.3-SNAPSHOT maven plugin:download - Dmaven.repo.remote=http://people.apache.org/repo/m1-snapshot-repository/, http://repo1.maven.org/maven -DgroupId=maven -DartifactId=maven-xdoc-plugin -Dversion=1.10.1-SNAPSHOT - 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] -- .. Arnaud Héritier OCTO Technology [EMAIL PROTECTED] .. 50, Avenue des Champs-Elysées 75008 Paris Tél : (33) 1 58 56 10 00 Fax : (33) 1 58 56 10 01 GSM : (33) 6 03 52 71 31 www.octo.com | blog.octo.com ... - To unsubscribe, e-mail: [EMAIL PROTECTED]
