Syncing repository-staging/maven to ibiblio?
Hi (Brett), Yesterday I've copied the cargo artifacts to repository-staging/to-ibiblio/maven (this was required because our m1 plugin uses the "cargo" groupid). However the sync has not happened and I can't the new 0.7 artifacts on ibiblio (http://www.ibiblio.org/maven/cargo/jars/). Is the sync turned off? If so how can I get those artifacts to show up on ibiblio? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[result] [vote] m1 plugin releases
5 binding (Arnaud, Jason, John, Emmanuel, Lukas) 3 non-binding (Fabrizio, Stephane, Vincent S) Cheers, Lukas Lukas Theussl wrote: Hi, Here are some more m1 plugins that I would be ready to release: [] maven-html2xdoc-plugin-1.4 [] maven-jalopy-plugin-1.4 [] maven-javadoc-plugin-1.8 [] maven-native-plugin-1.2 They all have still a few issues open, mainly feature requests and enhancements, but all major bugs have been fixed. Snapshots have been published for testing (see below), the future documentation is here: http://people.apache.org/~ltheussl/maven-stage-site/maven-1.x/reference/plugins/ Vote is open for 72h. +1 Lukas maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-html2xdoc-plugin -Dversion=1.4-SNAPSHOT maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-jalopy-plugin -Dversion=1.4-SNAPSHOT maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-javadoc-plugin -Dversion=1.8-SNAPSHOT maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-native-plugin -Dversion=1.2-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]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Mon Jan 16 03:45:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060116.034500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060116.034500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Mon Jan 16 02:45:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060116.024500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060116.024500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-35) add repository metadata indexer
[ http://jira.codehaus.org/browse/MRM-35?page=all ] Maria Odea Ching updated MRM-35: Attachment: MRM-35-maven-repository-indexer.patch > add repository metadata indexer > --- > > Key: MRM-35 > URL: http://jira.codehaus.org/browse/MRM-35 > Project: Maven Repository Manager > Type: Sub-task > Components: indexing > Reporter: Brett Porter > Assignee: Maria Odea Ching > Fix For: 1.0-alpha-1 > Attachments: MRM-35-maven-repository-indexer.patch > > Original Estimate: 8 hours > Remaining: 8 hours > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - update] Mon Jan 16 02:00:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060116.020001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060116.020001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1345) Upgrade to dom4j 1.4
[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_55945 ] Kohsuke Kawaguchi commented on MAVEN-1345: -- dom4j 1.4 causes MPXDOC-188 (and MPXDOC-38.) (note that even though they are marked as closed, the issue isn't fixed yet.) > Upgrade to dom4j 1.4 > > > Key: MAVEN-1345 > URL: http://jira.codehaus.org/browse/MAVEN-1345 > Project: Maven > Type: Bug > Components: core > Versions: 1.0-rc3 > Reporter: Paul Libbrecht > Assignee: Brett Porter > Priority: Critical > Fix For: 1.1-beta-3 > > > Currently, Maven relies on dom4j beta 8. > This is bad in many respects, the worst being that the XML output, for > example provided by Jelly XML plugin, has wrong xmlns attributes. > At least the 1.5 betas of dom4j all fix this, they also fix the html output > which was, otherwise, inserting random (kind-of) spaces in the text. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPXDOC-188) relative references from xdocs/*.xml resolve incorrectly
[ http://jira.codehaus.org/browse/MPXDOC-188?page=comments#action_55942 ] Kohsuke Kawaguchi commented on MPXDOC-188: -- See MAVEN-1345 for a discussion about the versions of dom4j and their issues. > relative references from xdocs/*.xml resolve incorrectly > > > Key: MPXDOC-188 > URL: http://jira.codehaus.org/browse/MPXDOC-188 > Project: maven-xdoc-plugin > Type: Bug > Versions: 1.9.2 > Reporter: Kohsuke Kawaguchi > > > I'm filing this as a separate bug since I couldn't figure out how to re-open > MPXDOC-38. > The comment on the original bug report is correct that the problem is really > an issue of dom4j. > Further investigation on the dom4j source code revealed that dom4j 1.4 has a > lot of issues wrt > SAXReader.read(File). Besides this issue, it ignores the XML encoding > declaration. > dom4j 1.5 has a proper fix to these issues, so please consider upgrading to > dom4j 1.5 or later. > If for some reason using a later version of dom4j is not an option, then > please consider using > other versions of the read method (one that takes URL, by using File.toURL) > File.toURL() is broken for some inputs, but in the context of Maven xdoc > plugin, it shouldn't be a problem. > See > http://cvs.sourceforge.net/viewcvs.py/dom4j/dom4j/src/java/org/dom4j/io/SAXReader.java?rev=1.58&view=log > for the chanlog of SAXReader. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPXDOC-188) relative references from xdocs/*.xml resolve incorrectly
[ http://jira.codehaus.org/browse/MPXDOC-188?page=all ] Kohsuke Kawaguchi closed MPXDOC-188: Resolution: Incomplete It turns out dom4j is loaded from $MAVEN_HOME/lib, regardless of what the plugin dependency specifies. Therefore, I realized that the bug needs to be filed against the maven core. > relative references from xdocs/*.xml resolve incorrectly > > > Key: MPXDOC-188 > URL: http://jira.codehaus.org/browse/MPXDOC-188 > Project: maven-xdoc-plugin > Type: Bug > Versions: 1.9.2 > Reporter: Kohsuke Kawaguchi > > > I'm filing this as a separate bug since I couldn't figure out how to re-open > MPXDOC-38. > The comment on the original bug report is correct that the problem is really > an issue of dom4j. > Further investigation on the dom4j source code revealed that dom4j 1.4 has a > lot of issues wrt > SAXReader.read(File). Besides this issue, it ignores the XML encoding > declaration. > dom4j 1.5 has a proper fix to these issues, so please consider upgrading to > dom4j 1.5 or later. > If for some reason using a later version of dom4j is not an option, then > please consider using > other versions of the read method (one that takes URL, by using File.toURL) > File.toURL() is broken for some inputs, but in the context of Maven xdoc > plugin, it shouldn't be a problem. > See > http://cvs.sourceforge.net/viewcvs.py/dom4j/dom4j/src/java/org/dom4j/io/SAXReader.java?rev=1.58&view=log > for the chanlog of SAXReader. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNGECLIPSE-43) M2 console should suppredd debug output if debug is disabled in preferences
[ http://jira.codehaus.org/browse/MNGECLIPSE-43?page=all ] Dmitri Maximovich closed MNGECLIPSE-43: --- Resolution: Fixed > M2 console should suppredd debug output if debug is disabled in preferences > --- > > Key: MNGECLIPSE-43 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-43 > Project: Maven 2.x Plug-in for Eclipse > Type: Improvement > Versions: 0.0.3 > Reporter: Dmitri Maximovich > Assignee: Dmitri Maximovich > Priority: Trivial > Fix For: 0.0.4 > > Original Estimate: 30 minutes >Time Spent: 15 minutes > Remaining: 15 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNGECLIPSE-43) M2 console should suppredd debug output if debug is disabled in preferences
M2 console should suppredd debug output if debug is disabled in preferences --- Key: MNGECLIPSE-43 URL: http://jira.codehaus.org/browse/MNGECLIPSE-43 Project: Maven 2.x Plug-in for Eclipse Type: Improvement Versions: 0.0.3 Reporter: Dmitri Maximovich Assigned to: Dmitri Maximovich Priority: Trivial Fix For: 0.0.4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPXDOC-188) relative references from xdocs/*.xml resolve incorrectly
relative references from xdocs/*.xml resolve incorrectly Key: MPXDOC-188 URL: http://jira.codehaus.org/browse/MPXDOC-188 Project: maven-xdoc-plugin Type: Bug Versions: 1.9.2 Reporter: Kohsuke Kawaguchi I'm filing this as a separate bug since I couldn't figure out how to re-open MPXDOC-38. The comment on the original bug report is correct that the problem is really an issue of dom4j. Further investigation on the dom4j source code revealed that dom4j 1.4 has a lot of issues wrt SAXReader.read(File). Besides this issue, it ignores the XML encoding declaration. dom4j 1.5 has a proper fix to these issues, so please consider upgrading to dom4j 1.5 or later. If for some reason using a later version of dom4j is not an option, then please consider using other versions of the read method (one that takes URL, by using File.toURL) File.toURL() is broken for some inputs, but in the context of Maven xdoc plugin, it shouldn't be a problem. See http://cvs.sourceforge.net/viewcvs.py/dom4j/dom4j/src/java/org/dom4j/io/SAXReader.java?rev=1.58&view=log for the chanlog of SAXReader. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Mon Jan 16 01:15:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060116.011501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060116.011501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNGECLIPSE-4) Problems with dependencies other that jar and war (ie. par, ejb3)
[ http://jira.codehaus.org/browse/MNGECLIPSE-4?page=all ] Dmitri Maximovich closed MNGECLIPSE-4: -- Resolution: Fixed > Problems with dependencies other that jar and war (ie. par, ejb3) > - > > Key: MNGECLIPSE-4 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-4 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Versions: 0.0.3 > Environment: MS Windows XP, Eclipse 3.2M2, plugin ver. 0.0.3 > Reporter: Piotr Bzdyl > Assignee: Dmitri Maximovich > Fix For: 0.0.4 > Attachments: MNGECLIPSE-4.jpg, patch.txt, test-projects-MNGECLIPSE-4.zip > > Time Spent: 15 minutes >Remaining: 0 minutes > > I found a problem in eclipse with projects producing artifacts with other > than war and jar types. I use mvn eclipse:eclipse to generate .project and > .classpath on the pom.xml with war which contains > dependency to the mymodel.par artifact (Persistence archive jar file) (I > still don't know how to open project in eclipse with only pom.xml - no > .project and .classpath files), then I import this project to the workspace. > Until now everything is working fine. Then I use context menu on the project > and select Maven 2 -> Enable. I got errors with duplicated dependencies (in > .classpath and in the Maven2 Dependencies node) so I remove duplicated > entries from eclipse java build path. Then I have one more error which I > can't remove: Illegal type of archive for required library: 'C:\Documents and > Settings\piotr\.m2\repository\com\example\mymodel\1.0\mymodel-1.0.par' in > project mywar. How to cope with this error? I think that maven2 plugin should > try to treat all dependencies as jar files and if it fails generate this > error. This same occurs with mylogic.ejb3 (plain jar file with EJB3 session > beans). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - checkout] Mon Jan 16 00:30:00 GMT 2006
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060116.003000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - checkout] Mon Jan 16 00:00:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060116.01.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060116.01.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNGECLIPSE-42) Submodules should not be added as jars to the build path
[ http://jira.codehaus.org/browse/MNGECLIPSE-42?page=all ] Eugene Kuleshov closed MNGECLIPSE-42: - Resolution: Fixed Fixed > Submodules should not be added as jars to the build path > > > Key: MNGECLIPSE-42 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-42 > Project: Maven 2.x Plug-in for Eclipse > Type: Improvement > Components: Dependency Resolver > Versions: 0.0.3 > Reporter: Eugene Kuleshov > Assignee: Eugene Kuleshov > Fix For: 0.0.4 > > > Dependency resolver should not add submodules as jars to the build path -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MSUREFIRE-45) The test attribute is incorrectly described
The test attribute is incorrectly described --- Key: MSUREFIRE-45 URL: http://jira.codehaus.org/browse/MSUREFIRE-45 Project: Maven 2.x Surefire Plugin Type: Improvement Reporter: Grégory Joseph Priority: Trivial The the surefire plugin describe its test parameter with "Specify this parameter if you want to use the test regex notation to select tests to run." However, from what I see in the SurefirePlugin code, this is abusing the "regex" term, since it is concatening "**/" + regex + ".java", which doesn't look much like a standard regex. i.e, using the regex syntax, one would expect to set "test" to ".*TestCase", but this doesn't work - "*TestCase" gives the expected results. All in all, I think this is just a matter of claryfiyng the doc - I haven't checked the surefire code itself, but from the results I get, I bet it doesn't use "real" regexes either. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPSCM-67) scm:prepare-release fails because project.xml has been locally modified
[ http://jira.codehaus.org/browse/MPSCM-67?page=all ] Dennis Lundberg updated MPSCM-67: - Attachment: MPSCM-67-2.patch > scm:prepare-release fails because project.xml has been locally modified > --- > > Key: MPSCM-67 > URL: http://jira.codehaus.org/browse/MPSCM-67 > Project: maven-scm-plugin > Type: Bug > Versions: 1.5 > Environment: Windows XP, Maven 1.0.2, Sun JDK 1.4.2_08, CVSNT 2.0.51 on > localhost, maven-release-plugin-1.4.1 > Reporter: Dennis Lundberg > Attachments: MPSCM-67-2.patch, MPSCM-67.patch > > > This is weird. When I try to prepare a release using > maven scm:prepare-release > it complains that "project.xml has been locally modified". > Well, it's supposed to change that's the idea of running scm:prepare-release, > right? Anyway, if I manually check in the modified project.xml and run the > command again it succeeds. > Let me know if you need more information. > Here's the output I get: > -- > G:\cvs\dennislundberg-codegeneration-HEAD>maven scm:prepare-release > __ __ > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.0.2 > build:start: > scm:find-connection: > [echo] Using connection: scm|cvs|pserver|[EMAIL > PROTECTED]|C:/Program/cvsnt/repositories|dennislundberg-codegeneration > scm:parse-connection: > [echo] Using SCM method: cvs > [echo] Using CVSROOT: :pserver:[EMAIL > PROTECTED]:C:/Program/cvsnt/repositories > [echo] Using module: dennislundberg-codegeneration > scm:check-deprecated-cvs-vars: > scm:prepare-release: > [echo] Verifying no modifications are present > [INFO] Executing: cvs -f -n -q update -d > [INFO] Working directory: G:\cvs\dennislundberg-codegeneration-HEAD > What is the new tag name? > RELEASE-2_8 > What is the new version? [RELEASE-2_8] > 2.8 > [echo] Updating POM with version 2.8; tag RELEASE-2_8 > [echo] Committing descriptors > [echo] Tagging source tree > [WARNING] Unknown status: '? '. > [WARNING] Unknown status: '? '. > Provider message: > The cvs tag command failed. > Command output: > cvs server: project.xml is locally modified > cvs [server aborted]: correct the above errors first! > BUILD FAILED > File.. C:\Documents and > Settings\dlg01\.maven\cache\maven-scm-plugin-1.5\plugin.jelly > Element... scm:tag > Line.. 244 > Column 189 > Error! > Total time: 29 seconds > Finished at: Mon Sep 26 17:25:24 CEST 2005 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1968) allow disabling of plugin version discovery
allow disabling of plugin version discovery --- Key: MNG-1968 URL: http://jira.codehaus.org/browse/MNG-1968 Project: Maven 2 Type: Bug Components: Plugins and Lifecycle, Artifacts and Repositories Reporter: Brett Porter Fix For: 2.1 for verifying reproducibility (and enable it on release:perform) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (SCM-121) Intermittent CVS test failures
[ http://jira.codehaus.org/browse/SCM-121?page=comments#action_55931 ] Dennis Lundberg commented on SCM-121: - I tried to issue the cvs command on the command line and got back the same error as when it was run from maven. To see is this is a Windows issue, I zipped my cvs-provider directory and put it on a Solaris machine. I then ran the same command line cvs command there, and it produced the exact same error message. The Solaris machine has "Concurrent Versions System (CVS) 1.11.20 (client/server)" from FSF. Is there someone who is able to run the tests for the cvs-provider? > Intermittent CVS test failures > -- > > Key: SCM-121 > URL: http://jira.codehaus.org/browse/SCM-121 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-cvs > Versions: 1.0-beta-3 > Reporter: Mike Perham > Fix For: 1.0-beta-3 > > > Dan and I continue to have test failures when trying to compile the cvs > plugin in our environment. I emailed these problems to the scm-dev list > about a week ago. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: To unsubscribe - UNSUBSCRIBE ME NOW !!!!
Done, with pleasure. /me dances for joy It was [EMAIL PROTECTED] Obviously they alias the host name. Also took them off the allow list (no idea how that happened) so we'll not hear from them again, unless they resubscribe. - Brett Brett Porter wrote: > I don't get it. Unless they were -allow'ed in the past, they must be > subscribed from this address to post. But unsubscribe fails. > > I'll try and figure it out, as I'd like to see the back of them (there > was also some company spam in a later message on this list). > > I suspect that they are attempting to actually spam a bunch of addresses > with their company info and not doing a very good job of it. I hope > their clients recognise this :) > > - Brett > > Jens Fournais wrote: >> Best Regards >> Global Identity A/S, >> >> >> Jens Fournais >> CEO >> >> >> Bygstubben 3 | DK-2950 Vedbaek | Denmark >> Phone: +45 45 99 31 00 | E-mail: [EMAIL PROTECTED] >> MSN: [EMAIL PROTECTED] >> >> Please visit our website at: http://www.elibitum.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]
[jira] Created: (MNGECLIPSE-42) Submodules should not be added as jars to the build path
Submodules should not be added as jars to the build path Key: MNGECLIPSE-42 URL: http://jira.codehaus.org/browse/MNGECLIPSE-42 Project: Maven 2.x Plug-in for Eclipse Type: Improvement Components: Dependency Resolver Versions: 0.0.3 Reporter: Eugene Kuleshov Assigned to: Eugene Kuleshov Fix For: 0.0.4 Dependency resolver should not add submodules as jars to the build path -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MJAVADOC-50) Allow configuration for whether images and css are copied to destDir
Allow configuration for whether images and css are copied to destDir Key: MJAVADOC-50 URL: http://jira.codehaus.org/browse/MJAVADOC-50 Project: Maven 2.x Javadoc Plugin Type: New Feature Reporter: Wendy Smoak Priority: Minor Not all doclets produce HTML output, so copying the css and images should be configurable. For example, the UMLGraph doclet produces ".dot" files which can be transformed into images. In addition, the plugin behaves differently when configured in the and sections: * When run with 'mvn javadoc:javadoc' from the section, stylesheet.css, the 'images' directory and the 'css' directory are copied to . * When run with 'mvn site' from the section, only stylesheet.css is copied in (and is ignored, see MJAVADOC-47). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: To unsubscribe - UNSUBSCRIBE ME NOW !!!!
I don't get it. Unless they were -allow'ed in the past, they must be subscribed from this address to post. But unsubscribe fails. I'll try and figure it out, as I'd like to see the back of them (there was also some company spam in a later message on this list). I suspect that they are attempting to actually spam a bunch of addresses with their company info and not doing a very good job of it. I hope their clients recognise this :) - Brett Jens Fournais wrote: > Best Regards > Global Identity A/S, > > > Jens Fournais > CEO > > > Bygstubben 3 | DK-2950 Vedbaek | Denmark > Phone: +45 45 99 31 00 | E-mail: [EMAIL PROTECTED] > MSN: [EMAIL PROTECTED] > > Please visit our website at: http://www.elibitum.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: To unsubscribe - UNSUBSCRIBE ME NOW !!!!
You've received instructions from us in the past several times. When you fail to unsubscribe, you get an email how to find out. [EMAIL PROTECTED] is *not* subscribed to any lists here. I have no way of telling what address you are receiving them at. Email to this address will *not* get you any further help. Our patience is thin enough with all the spam coming from your infected accounts as it is. I'm sending this to any email addresses google has for you (also empty mail junk to other lists!). Hopefully you will figure it out. - Brett Jens Fournais wrote: > Best Regards > Global Identity A/S, > > > Jens Fournais > CEO > > > Bygstubben 3 | DK-2950 Vedbaek | Denmark > Phone: +45 45 99 31 00 | E-mail: [EMAIL PROTECTED] > MSN: [EMAIL PROTECTED] > > Please visit our website at: http://www.elibitum.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Current Maven SVN misses build dependency "doxia-sink-api-1.0-alpha-7"
Dear Partner, An open-minded company is always on the look-out for new partners Global Identity A/S is one of Denmark’s premier IT volume distributors selling all kinds of IT & IT related products to more that 22 different countries all over the world. The company caters for its customers’ diverse language requirements, employing 25 export sales staff that together speaks 11 different languages. Global Identity's business strategy is to "Think global - act local", and customers should consider Global Identity A/S as a local distributor regardless of where they are located. Thanks to its international presence, Global Identity A/S can offer better local prices and services than many local competitors. Business projections for the next eighteen months anticipate a doubling in the number of sales staff for the export market. Global Identity A/S is a niche distributor, and the firm is divided further into two specialist divisions: The High-End Division and the PC Components Division. The High End Division sells original retail boxed option products from IBM, Compaq, HP and SUN Microsystems. These products are resold to wholesalers, retail chains and VARs. The product range includes: memory, hard disk drives, hard disk raid-controllers, CPU upgrades, networking products and other IT equipment. The PC Components Division also sells memory, hard disk drives, hard disk raid-controllers, CPU upgrades, networking products and other IT equipment (such as motherboards, VGA/sound cards CD-ROMs, DVD, and CD-RW). All of these products also come from the world’s leading manufacturers, including Hyundai, Intel, AMD, ASUS, Matrox, ATI, Plextor, Creative, Seagate, Yamaha, and Quantum. These products are sold to PC-assemblers, wholesalers and retail chains. Global Identity A/S has concentrated its attention on working in large volumes of IT & IT related products, the company is able to offer its registered dealers and partners some of the market's most attractive business terms. The firm provides 24-hour delivery all over Europe, flexible credit facilities and of course the best and most competitive prices. Global Identity A/S is in a phase of rapid development, both in terms of its business set up and fostering technological advances. The company is therefore always on the look-out for potential partners, that can inspire it in new directions. The company’s strong financial background is recognised by the "A" rating (AAA) it has been awarded by Dun & Bradstreet. By achieving the highest credit rating, Global Identity A/S has assured its customers that there is simply no more stable IT distributor in the market place. Global Identity A/S provides both extensive pre- and after sales support, which is carried out by a specially trained support team. Global Identity A/S enjoys a significant market share throughout Europe for its PC components. In 2005 sales have already gone up by as much as 21 percent due to a proactive sales department providing the best prices on the market, and one of the best websites in the IT-industry. Part of Global identity A/S’ successful business strategy is the emphasis it places on its Internet services, both in terms of trade and communication. Today customers benefit from many innovative Internet services that have become invaluable daily tools. Among other website innovations, Global Identity A/S offers a completely new online supplier system: Supplier Relationship Management (SRM), which makes it possible for suppliers worldwide to meet the purchasing demands of Global Identity A/S as soon as they arise. Global Identity A/S also offers its customers a unique real-time PC-Component/PC-assembly service, which is a 24-hour real-time update of the best prices for all PC components on the market. At the same site Global Identity A/S updates customers on the latest IT news, with a specific focus on PC components and PC-assembly products. And the company's current enterprise is implementing a further service improvement on its site with a unique UPS-tracking service, that makes it possible for customers to track their products from departure to safe arrival. Global Identity A/S is one of world’s largest distributors of upgrade products for the IT-industry. The company prides itself on never compromising its high standards and excellent value-for-money. Global Identity A/S was established in 1992 by Jens Fournais and Tommy F. Olesen, and has expanded dramatically ever since. The company has approximately 4,500 customers worldwide and an annual turnover of US$ 175 million (2004/2005). At Global Identity A/S the company strives to lead in the distribution of the industry's most advanced information technologies, including networking products and storage devices. The firm is characterized by a constant search for new paths to pursue and new areas to capture. Global Identity A/S’ future vision consists of an ever-growing,
To unsubscribe - UNSUBSCRIBE ME NOW !!!!
Best Regards Global Identity A/S, Jens Fournais CEO Bygstubben 3 | DK-2950 Vedbaek | Denmark Phone: +45 45 99 31 00 | E-mail: [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] Please visit our website at: http://www.elibitum.com
[jira] Closed: (MNG-1967) Local repository URL containing / does not work under windows
[ http://jira.codehaus.org/browse/MNG-1967?page=all ] Brett Porter closed MNG-1967: - Resolution: Duplicate > Local repository URL containing / does not work under windows > - > > Key: MNG-1967 > URL: http://jira.codehaus.org/browse/MNG-1967 > Project: Maven 2 > Type: Bug > Components: Artifacts and Repositories > Versions: 2.0.1 > Environment: Windows 2000 Pro, > java version "1.4.2_03" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02) > Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) > Reporter: Loic Lefevre > Assignee: Brett Porter > Attachments: bug-multiproject.zip, bug.zip > > > When using / in a local repository URL, it does not work under windows. > Replacing it with \ solves the problem. > See testcase included (run under windows environment). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1967) Local repository URL containing / does not work under windows
[ http://jira.codehaus.org/browse/MNG-1967?page=all ] Loïc Lefèvre updated MNG-1967: -- Attachment: bug-multiproject.zip > Local repository URL containing / does not work under windows > - > > Key: MNG-1967 > URL: http://jira.codehaus.org/browse/MNG-1967 > Project: Maven 2 > Type: Bug > Components: Artifacts and Repositories > Versions: 2.0.1 > Environment: Windows 2000 Pro, > java version "1.4.2_03" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02) > Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) > Reporter: Loïc Lefèvre > Assignee: Brett Porter > Attachments: bug-multiproject.zip, bug.zip > > > When using / in a local repository URL, it does not work under windows. > Replacing it with \ solves the problem. > See testcase included (run under windows environment). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MNG-1967) Local repository URL containing / does not work under windows
[ http://jira.codehaus.org/browse/MNG-1967?page=all ] Loïc Lefèvre reopened MNG-1967: --- By trying file:///${basedir}/thirdparty in the testcase it works fine. However, the testcase did not relate what was my real problem. In fact, I have a multiproject and in this case the problem is not solved yet. See the second testcase. > Local repository URL containing / does not work under windows > - > > Key: MNG-1967 > URL: http://jira.codehaus.org/browse/MNG-1967 > Project: Maven 2 > Type: Bug > Components: Artifacts and Repositories > Versions: 2.0.1 > Environment: Windows 2000 Pro, > java version "1.4.2_03" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02) > Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) > Reporter: Loïc Lefèvre > Assignee: Brett Porter > Attachments: bug.zip > > > When using / in a local repository URL, it does not work under windows. > Replacing it with \ solves the problem. > See testcase included (run under windows environment). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPIR-21) no generated for archive URL
[ http://jira.codehaus.org/browse/MPIR-21?page=comments#action_55925 ] Jorg Heymans commented on MPIR-21: -- I just updated to 2.0.2 snapshot and maven-site-plugin-2.0-20060106.225541-3.jar , the behaviour is still there. > no generated for archive URL > -- > > Key: MPIR-21 > URL: http://jira.codehaus.org/browse/MPIR-21 > Project: Maven 2.x Project Info Reports Plugin > Type: Bug > Versions: 2.0-beta-3 > Reporter: Jorg Heymans > > > Add below mailinglist configuration to a project, and run mvn site:site . > Then look at the page and you'll see that only a > http://marc.theaimsgroup.com/?l=xml-cocoon-dev section is generated > for the second otherArchive. > > Cocoon User List > [EMAIL PROTECTED] > [EMAIL PROTECTED] > users@cocoon.apache.org > http://mail-archives.apache.org/mod_mbox/cocoon-users > > > http://www.mail-archive.com/users@cocoon.apache.org/ > > > http://marc.theaimsgroup.com/?l=xml-cocoon-user > > > http://news.gmane.org/gmane.text.xml.cocoon.user > > > When i remove everything from the questionmark onwards it works again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-49) Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath
[ http://jira.codehaus.org/browse/MJAVADOC-49?page=all ] Brett Porter moved MPJAVADOC-70 to MJAVADOC-49: --- Workflow: Maven (was: jira) Key: MJAVADOC-49 (was: MPJAVADOC-70) Project: Maven 2.x Javadoc Plugin (was: maven-javadoc-plugin) > Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath > - > > Key: MJAVADOC-49 > URL: http://jira.codehaus.org/browse/MJAVADOC-49 > Project: Maven 2.x Javadoc Plugin > Type: Bug > Environment: Windows XP java 1.4.2_05 > Reporter: Sebastian Bloch > Priority: Blocker > > > [INFO] c:\bea81sp4\jdk142_05\jre\..\bin\javadoc.exe -J-Xmx512m -J-Xms128m > @options @files > usage: javadoc [options] [packagenames] [sourcefiles] [classnames] [EMAIL > PROTECTED] > -overview Read overview documentation from HTML file > -public Show only public classes and members > -protectedShow protected/public classes and members (default) > -package Show package/protected/public classes and members > -private Show all classes and members > -help Display command line options and exit > -docletGenerate output via alternate doclet > -docletpath Specify where to find doclet class files > -sourcepath Specify where to find source files > -classpath Specify where to find user class files > -exclude Specify a list of packages to exclude > -subpackages Specify subpackages to recursively load > -breakiteratorCompute 1st sentence with BreakIterator > -bootclasspath Override location of class files loaded > by the bootstrap class loader > -source Provide source compatibility with specified release > -extdirs Override location of installed extensions > -verbose Output messages about what Javadoc is doing > -locale Locale to be used, e.g. en_US or en_US_WIN > -encoding Source file encoding name > -J Pass directly to the runtime system > 1 error > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] An error has occurred in JavaDocs report generation. > Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 7 seconds > [INFO] Finished at: Sun Jan 15 20:27:35 CET 2006 > [INFO] Final Memory: 3M/7M > may be -sourcepath would help? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNGECLIPSE-37) Update references to the plugin Update Site
[ http://jira.codehaus.org/browse/MNGECLIPSE-37?page=all ] Eugene Kuleshov updated MNGECLIPSE-37: -- Summary: Update references to the plugin Update Site (was: Eclipse Update Site for Plug-in not working) > Update references to the plugin Update Site > --- > > Key: MNGECLIPSE-37 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-37 > Project: Maven 2.x Plug-in for Eclipse > Type: Bug > Components: Documentation > Reporter: Werner Keil > Assignee: Eugene Kuleshov > Priority: Minor > Attachments: m2p1.jpg, m2p2.jpg > > > The Update Site for The Plug-in as described in the Codehaus install demo > does not seem to work any more. > The URL http://www.md.pp.ru/~eu/12/ worked to install the latest version > 0.0.3 of the plugin, but trying to updte or search for 0.0.4 it did not even > find the older ones (incl. 0.0.3) any more. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPJAVADOC-70) Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath
[ http://jira.codehaus.org/browse/MPJAVADOC-70?page=comments#action_55923 ] Wendy Smoak commented on MPJAVADOC-70: -- I think this belongs in MJAVADOC (Maven 2.x Javadoc Plugin). If so, the problem with -sourcepath was corrected on January 10th in r367728. > Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath > - > > Key: MPJAVADOC-70 > URL: http://jira.codehaus.org/browse/MPJAVADOC-70 > Project: maven-javadoc-plugin > Type: Bug > Environment: Windows XP java 1.4.2_05 > Reporter: Sebastian Bloch > Priority: Blocker > > > [INFO] c:\bea81sp4\jdk142_05\jre\..\bin\javadoc.exe -J-Xmx512m -J-Xms128m > @options @files > usage: javadoc [options] [packagenames] [sourcefiles] [classnames] [EMAIL > PROTECTED] > -overview Read overview documentation from HTML file > -public Show only public classes and members > -protectedShow protected/public classes and members (default) > -package Show package/protected/public classes and members > -private Show all classes and members > -help Display command line options and exit > -docletGenerate output via alternate doclet > -docletpath Specify where to find doclet class files > -sourcepath Specify where to find source files > -classpath Specify where to find user class files > -exclude Specify a list of packages to exclude > -subpackages Specify subpackages to recursively load > -breakiteratorCompute 1st sentence with BreakIterator > -bootclasspath Override location of class files loaded > by the bootstrap class loader > -source Provide source compatibility with specified release > -extdirs Override location of installed extensions > -verbose Output messages about what Javadoc is doing > -locale Locale to be used, e.g. en_US or en_US_WIN > -encoding Source file encoding name > -J Pass directly to the runtime system > 1 error > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] An error has occurred in JavaDocs report generation. > Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 7 seconds > [INFO] Finished at: Sun Jan 15 20:27:35 CET 2006 > [INFO] Final Memory: 3M/7M > may be -sourcepath would help? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNGECLIPSE-41) Pickup latest embedder component
[ http://jira.codehaus.org/browse/MNGECLIPSE-41?page=all ] Eugene Kuleshov updated MNGECLIPSE-41: -- Version: (was: 0.0.4) 0.0.3 Fix Version: 0.0.4 > Pickup latest embedder component > > > Key: MNGECLIPSE-41 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-41 > Project: Maven 2.x Plug-in for Eclipse > Type: Task > Versions: 0.0.3 > Reporter: Eugene Kuleshov > Assignee: Eugene Kuleshov > Fix For: 0.0.4 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNGECLIPSE-41) Pickup latest embedder component
Pickup latest embedder component Key: MNGECLIPSE-41 URL: http://jira.codehaus.org/browse/MNGECLIPSE-41 Project: Maven 2.x Plug-in for Eclipse Type: Task Versions: 0.0.4 Reporter: Eugene Kuleshov Assigned to: Eugene Kuleshov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJAVADOC-70) Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath
Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath - Key: MPJAVADOC-70 URL: http://jira.codehaus.org/browse/MPJAVADOC-70 Project: maven-javadoc-plugin Type: Bug Environment: Windows XP java 1.4.2_05 Reporter: Sebastian Bloch Priority: Blocker [INFO] c:\bea81sp4\jdk142_05\jre\..\bin\javadoc.exe -J-Xmx512m -J-Xms128m @options @files usage: javadoc [options] [packagenames] [sourcefiles] [classnames] [EMAIL PROTECTED] -overview Read overview documentation from HTML file -public Show only public classes and members -protectedShow protected/public classes and members (default) -package Show package/protected/public classes and members -private Show all classes and members -help Display command line options and exit -docletGenerate output via alternate doclet -docletpath Specify where to find doclet class files -sourcepath Specify where to find source files -classpath Specify where to find user class files -exclude Specify a list of packages to exclude -subpackages Specify subpackages to recursively load -breakiteratorCompute 1st sentence with BreakIterator -bootclasspath Override location of class files loaded by the bootstrap class loader -source Provide source compatibility with specified release -extdirs Override location of installed extensions -verbose Output messages about what Javadoc is doing -locale Locale to be used, e.g. en_US or en_US_WIN -encoding Source file encoding name -J Pass directly to the runtime system 1 error [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error has occurred in JavaDocs report generation. Embedded error: Exit code: 1 - javadoc: invalid flag: -sourcePath [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 7 seconds [INFO] Finished at: Sun Jan 15 20:27:35 CET 2006 [INFO] Final Memory: 3M/7M may be -sourcepath would help? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPIR-21) no generated for archive URL
[ http://jira.codehaus.org/browse/MPIR-21?page=comments#action_55922 ] Brett Porter commented on MPIR-21: -- I think this might already be fixed in the SVN version of this plugin. not yet confirmed. > no generated for archive URL > -- > > Key: MPIR-21 > URL: http://jira.codehaus.org/browse/MPIR-21 > Project: Maven 2.x Project Info Reports Plugin > Type: Bug > Versions: 2.0-beta-3 > Reporter: Jorg Heymans > > > Add below mailinglist configuration to a project, and run mvn site:site . > Then look at the page and you'll see that only a > http://marc.theaimsgroup.com/?l=xml-cocoon-dev section is generated > for the second otherArchive. > > Cocoon User List > [EMAIL PROTECTED] > [EMAIL PROTECTED] > users@cocoon.apache.org > http://mail-archives.apache.org/mod_mbox/cocoon-users > > > http://www.mail-archive.com/users@cocoon.apache.org/ > > > http://marc.theaimsgroup.com/?l=xml-cocoon-user > > > http://news.gmane.org/gmane.text.xml.cocoon.user > > > When i remove everything from the questionmark onwards it works again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MPIR-21) no generated for archive URL
[ http://jira.codehaus.org/browse/MPIR-21?page=all ] Brett Porter moved MSITE-76 to MPIR-21: --- Version: (was: 2.0-beta-4) 2.0-beta-3 Key: MPIR-21 (was: MSITE-76) Project: Maven 2.x Project Info Reports Plugin (was: Maven 2.x Site Plugin) > no generated for archive URL > -- > > Key: MPIR-21 > URL: http://jira.codehaus.org/browse/MPIR-21 > Project: Maven 2.x Project Info Reports Plugin > Type: Bug > Versions: 2.0-beta-3 > Reporter: Jorg Heymans > > > Add below mailinglist configuration to a project, and run mvn site:site . > Then look at the page and you'll see that only a > http://marc.theaimsgroup.com/?l=xml-cocoon-dev section is generated > for the second otherArchive. > > Cocoon User List > [EMAIL PROTECTED] > [EMAIL PROTECTED] > users@cocoon.apache.org > http://mail-archives.apache.org/mod_mbox/cocoon-users > > > http://www.mail-archive.com/users@cocoon.apache.org/ > > > http://marc.theaimsgroup.com/?l=xml-cocoon-user > > > http://news.gmane.org/gmane.text.xml.cocoon.user > > > When i remove everything from the questionmark onwards it works again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MWAR-22) patch to allow extra webapp and webapp/WEB-INF/classes files to be specified that override existing files
[ http://jira.codehaus.org/browse/MWAR-22?page=comments#action_55921 ] Brett Porter commented on MWAR-22: -- Thanks for the help. Personally, I'm -1 on the patch as is. I think we need to move to a unified solution regarding resources, that takes into account filtering and also should split the goal in two so it can be wired in at the appropriate place. > patch to allow extra webapp and webapp/WEB-INF/classes files to be specified > that override existing files > - > > Key: MWAR-22 > URL: http://jira.codehaus.org/browse/MWAR-22 > Project: Maven 2.x War Plugin > Type: Improvement > Reporter: Cameron Braid > Attachments: maven-war-plugin-extraWarResources.patch > > > Currnelty, there is no way to execute a plugin inbetween the 'build exploded > webapp' part of this plugin, and the 'zip up resources' bit. > I have the need to override classpath resources, and sometimes other webapp > resources, based on a deployment target, such as test / staging or production. > With this patch, I will be able to have files layed out like this : > /profile/test/config.properties > /src/main/resources/config.properties > then configure the war plugin : > > profile/test > > thus producing a war that contains profile/test/config.properties instead of > the default /src/main/resources/config.properties > I have investigated alternative ways to achive this goal, and none of them > seemed easy. > Some ideas : > * split the package phase into 2 phases - preparePackage and package > * provide a generic technique to allow plugins to expose extension points > where other plugins can hook into > * create a plugin that runs after the war plugin, that creates a new war - > slow since the ziping will need to be done twice > i'm keen to hear anyone's thoughts on the mailing list or in irc - my nick is > Fracture -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m1] source plugin
Stephane Nicoll wrote: Once this is done, you'll be able to download On 1/15/06, Doug Douglass <[EMAIL PROTECTED]> wrote: Sure that works, presuming you have the source in a local project in which you can run source:install. But, if the source jar is in a remote repo already, I don't currently see a way to download that jar to the local repo via either the eclipse or the source plugin. You need to take the latest version of the eclipse plugin (1.11-SNAPSHOT). I don't think it's deployed so you'll have to rebuild it from SVN. Running the eclipe goal with this version will download the sources from the remote repository. Thanks, Stéphane AH! There it is. Appears to work very well. Nicely done, a good addition to m1. Thanks, Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-1967) Local repository URL containing / does not work under windows
[ http://jira.codehaus.org/browse/MNG-1967?page=all ] Brett Porter closed MNG-1967: - Assign To: Brett Porter Resolution: Won't Fix as I understand it, relative paths are not valid in URLs. Try: file:///${basedir}/test > Local repository URL containing / does not work under windows > - > > Key: MNG-1967 > URL: http://jira.codehaus.org/browse/MNG-1967 > Project: Maven 2 > Type: Bug > Components: Artifacts and Repositories > Versions: 2.0.1 > Environment: Windows 2000 Pro, > java version "1.4.2_03" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02) > Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) > Reporter: Loïc Lefèvre > Assignee: Brett Porter > Attachments: bug.zip > > > When using / in a local repository URL, it does not work under windows. > Replacing it with \ solves the problem. > See testcase included (run under windows environment). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MSITE-76) no generated for archive URL
no generated for archive URL -- Key: MSITE-76 URL: http://jira.codehaus.org/browse/MSITE-76 Project: Maven 2.x Site Plugin Type: Bug Versions: 2.0-beta-4 Reporter: Jorg Heymans Add below mailinglist configuration to a project, and run mvn site:site . Then look at the page and you'll see that only a http://marc.theaimsgroup.com/?l=xml-cocoon-dev section is generated for the second otherArchive. Cocoon User List [EMAIL PROTECTED] [EMAIL PROTECTED] users@cocoon.apache.org http://mail-archives.apache.org/mod_mbox/cocoon-users http://www.mail-archive.com/users@cocoon.apache.org/ http://marc.theaimsgroup.com/?l=xml-cocoon-user http://news.gmane.org/gmane.text.xml.cocoon.user When i remove everything from the questionmark onwards it works again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cargo artifacts not served by the m1 repo on ibiblio
It's not disabled (it just goes to the original m1 repo which is not updated with your changes not deployed there). If anyone wants to volunteer to add the rewrite rule to the source file in maven-meeper, we can upload it. - Brett Vincent Massol wrote: > >> -Original Message- >> From: Brett Porter [mailto:[EMAIL PROTECTED] >> Sent: dimanche 15 janvier 2006 18:54 >> To: Maven Developers List >> Subject: Re: Cargo artifacts not served by the m1 repo on ibiblio >> >> It's just browsing that is disabled. Doesn't going direct to the >> artifact work? > > Thanks Brett. I wasn't aware browsing was disabled. It works fine indeed. > > -Vincent > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cargo artifacts not served by the m1 repo on ibiblio
It only really makes sense at the groupId level if it is being translated. We can't do much more than that. My hope is that everyone will use the repo manager in the next month or so :) - Brett Felipe Leme wrote: > Brett, > > Is the browsing going to be fixed? I mean, browsing 'by humans' is > important as well... > > -- Felipe > > > Brett Porter wrote: >> It's just browsing that is disabled. Doesn't going direct to the >> artifact work? > > > > - > 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: Cargo artifacts not served by the m1 repo on ibiblio
Brett, Is the browsing going to be fixed? I mean, browsing 'by humans' is important as well... -- Felipe Brett Porter wrote: It's just browsing that is disabled. Doesn't going direct to the artifact work? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: No longer syncing Maven 1.x repository to Ibiblio
Brett Porter wrote: Would you mind sending some details out to that list? I am not subscribed so I can't get to the archives. Neither am I, actually :-( - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Cargo artifacts not served by the m1 repo on ibiblio
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: dimanche 15 janvier 2006 18:54 > To: Maven Developers List > Subject: Re: Cargo artifacts not served by the m1 repo on ibiblio > > It's just browsing that is disabled. Doesn't going direct to the > artifact work? Thanks Brett. I wasn't aware browsing was disabled. It works fine indeed. -Vincent > Vincent Massol wrote: > > Hi (Brett), > > > > The Cargo 0.7 artifacts are correctly served by the m2 repo on ibiblio > > (http://www.ibiblio.org/maven2/org/codehaus/cargo/). However the URL > > rewriting rules for making the m2 repo a m1 repo do not seem to work. > > > > I'm not sure what the URL should be but I've tried: > > > > http://www.ibiblio.org/maven/org.codehaus.cargo/ (does not work) > > > > http://www.ibiblio.org/maven/org/codehaus/cargo/ (does not work but > that's > > expected as it would violate m1 repo rules) > > > > http://www.ibiblio.org/maven/cargo/ (this works but delivers the old > Cargo > > files and not the new ones) > > > > How do we make the new 0.7 artifacts visible under m1? > > > > Thanks > > -Vincent > > > > > > - > > 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: [m1] source plugin
Once this is done, you'll be able to download On 1/15/06, Doug Douglass <[EMAIL PROTECTED]> wrote: > Sure that works, presuming you have the source in a local project in > which you can run source:install. > > But, if the source jar is in a remote repo already, I don't currently > see a way to download that jar to the local repo via either the eclipse > or the source plugin. You need to take the latest version of the eclipse plugin (1.11-SNAPSHOT). I don't think it's deployed so you'll have to rebuild it from SVN. Running the eclipe goal with this version will download the sources from the remote repository. Thanks, Stéphane > > Doug > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .::You're welcome ::. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Policy for linking between different maven sites
I'm creating a patch for MNG-1677 and need to know what the policy is for linking between sites for different parts of Maven. In this case I need to create a link from maven-components (maven-model) to maven-scm. Should I use an absolute or a relative link? http://maven.apache.org/scm/scm-url-format.html";>link or link -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: No longer syncing Maven 1.x repository to Ibiblio
The admins were (I had to enable .htaccess via the helpdesk). Would you mind sending some details out to that list? I am not subscribed so I can't get to the archives. - Brett Felipe Leme wrote: > BTW, when these rewrite rules were created, were the ibiblio admins been > notified on the changes? > > I'm asking because we mirrors ibiblio at work and the guy responsible > for the job wasn't aware of the change, even though he is subscribed to > the ibiblio-mirrors list > (http://lists.ibiblio.org/mailman/listinfo/ibiblio-mirrors). > > -- Felipe > > > Carlos Sanchez wrote: >> I believe that's caused by the rewrite rules, they don't work well >> with dirs but they do with artifacts > > - > 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: Cargo artifacts not served by the m1 repo on ibiblio
It's just browsing that is disabled. Doesn't going direct to the artifact work? - Brett Vincent Massol wrote: > Hi (Brett), > > The Cargo 0.7 artifacts are correctly served by the m2 repo on ibiblio > (http://www.ibiblio.org/maven2/org/codehaus/cargo/). However the URL > rewriting rules for making the m2 repo a m1 repo do not seem to work. > > I'm not sure what the URL should be but I've tried: > > http://www.ibiblio.org/maven/org.codehaus.cargo/ (does not work) > > http://www.ibiblio.org/maven/org/codehaus/cargo/ (does not work but that's > expected as it would violate m1 repo rules) > > http://www.ibiblio.org/maven/cargo/ (this works but delivers the old Cargo > files and not the new ones) > > How do we make the new 0.7 artifacts visible under m1? > > Thanks > -Vincent > > > - > 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] Javadoc plugin - using alternate UMLGraph doclet?
Wendy Smoak wrote: > Not to mention that it's an interface, so instantiating it would be > pretty difficult. Right, though a converter would know to instantiate a useful implementation using an artifactFactory. > No problem... though it does seem like duplication, I think because > DefaultArtifact exists. But this isn't really _the_ Artifact, it's > just a container for the properties that will be used to create it. I > think. (First plugin... still trying to figure this all out.) I actually agree. I'd prefer Artifact to be a bean. It has too much functionality and indeterminate state right now. > One more question. Your factory.createArtifact(...) call is missing > the 'scope' parameter. Do I just hard-code it like the type? > > Artifact artifact = factory.createArtifact( > docletArtifact.getGroupId(), >docletArtifact.getArtifactId(), > docletArtifact.getVersion(), "compile", "jar" ); There are some constants on the Artifact interface you can use for scope. I think "null" is actually a valid scope here. > > Thanks. I suppose you're going to want to see a patch after doing all > this work. :) Please! :D - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: No longer syncing Maven 1.x repository to Ibiblio
BTW, when these rewrite rules were created, were the ibiblio admins been notified on the changes? I'm asking because we mirrors ibiblio at work and the guy responsible for the job wasn't aware of the change, even though he is subscribed to the ibiblio-mirrors list (http://lists.ibiblio.org/mailman/listinfo/ibiblio-mirrors). -- Felipe Carlos Sanchez wrote: I believe that's caused by the rewrite rules, they don't work well with dirs but they do with artifacts - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MJAR-5) no Implementation-Vendor-Id in META-INF/MANIFEST.MF
[ http://jira.codehaus.org/browse/MJAR-5?page=comments#action_55913 ] Lukas Theussl commented on MJAR-5: -- See MPJAR-51 and MPJAR-7 for related discussions in the m1 plugin. > no Implementation-Vendor-Id in META-INF/MANIFEST.MF > --- > > Key: MJAR-5 > URL: http://jira.codehaus.org/browse/MJAR-5 > Project: Maven 2.x Jar Plugin > Type: Bug > Environment: Linux 2.6.12-9-386 Kubuntu java version "1.4.2-02" > Reporter: Pascal Grange > Priority: Blocker > > > mvn package does not generate an entry "Implementation-Vendor-Id". This is a > blocker when we use the extension mechanisme with tomcat. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MJAR-3) LICENSE.txt no longer saved in META-INF
[ http://jira.codehaus.org/browse/MJAR-3?page=all ] Mike Perham closed MJAR-3: -- Assign To: Mike Perham Resolution: Duplicate MJAR-10 > LICENSE.txt no longer saved in META-INF > --- > > Key: MJAR-3 > URL: http://jira.codehaus.org/browse/MJAR-3 > Project: Maven 2.x Jar Plugin > Type: Bug > Reporter: Joerg Schaible > Assignee: Mike Perham > Priority: Minor > > > The M1 jar plugin copied the LICENSE.txt file into the MTEA-INF folder of the > resulting artifact. The jar plugin for M2 does this no longer. It should be > at least configurable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MJAR-5) no Implementation-Vendor-Id in META-INF/MANIFEST.MF
[ http://jira.codehaus.org/browse/MJAR-5?page=comments#action_55907 ] Mike Perham commented on MJAR-5: Here's an example I found from the Sun spec. What data from the POM should be used though? I can't think any elements which fit this requirement. Maybe groupId? Implementation-Vendor-Id: com.sun Implementation-Vendor: Sun Microsystems, Inc Implementation-Version: 1.0 > no Implementation-Vendor-Id in META-INF/MANIFEST.MF > --- > > Key: MJAR-5 > URL: http://jira.codehaus.org/browse/MJAR-5 > Project: Maven 2.x Jar Plugin > Type: Bug > Environment: Linux 2.6.12-9-386 Kubuntu java version "1.4.2-02" > Reporter: Pascal Grange > Priority: Blocker > > > mvn package does not generate an entry "Implementation-Vendor-Id". This is a > blocker when we use the extension mechanisme with tomcat. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-302) Invalid m2 pom for joda-time-hibernate-0.8
Invalid m2 pom for joda-time-hibernate-0.8 -- Key: MEV-302 URL: http://jira.codehaus.org/browse/MEV-302 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Grégory Joseph Attachments: pom.patch The pom at http://www.ibiblio.org/maven2/joda-time/joda-time-hibernate/0.8/joda-time-hibernate-0.8.pom is invalid. I'll attach a patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MEV-302) Invalid m2 pom for joda-time-hibernate-0.8
[ http://jira.codehaus.org/browse/MEV-302?page=all ] Grégory Joseph updated MEV-302: --- Attachment: pom.patch > Invalid m2 pom for joda-time-hibernate-0.8 > -- > > Key: MEV-302 > URL: http://jira.codehaus.org/browse/MEV-302 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Grégory Joseph > Attachments: pom.patch > > > The pom at > http://www.ibiblio.org/maven2/joda-time/joda-time-hibernate/0.8/joda-time-hibernate-0.8.pom > is invalid. > I'll attach a patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MEV-301) relocate xerces:xerces or xerces:xercesImpl
relocate xerces:xerces or xerces:xercesImpl --- Key: MEV-301 URL: http://jira.codehaus.org/browse/MEV-301 Project: Maven Evangelism Type: Bug Reporter: fabrizio giustina At the moment xerces jars are distributed both with the "xerces" and "xercesImpl" artifact id. Jars are identical, at the moment some versions are in "xerces", other in "xercesImpl" and some in both. For example the following are the same artifact: http://www.ibiblio.org/maven2/xerces/xerces/2.0.2/ http://www.ibiblio.org/maven2/xerces/xercesImpl/2.0.2/ xerces:xercesImpl should be relocated to xerces:xerces and all the jars should be moved there. At the moment the duplicate artifact name often causes two copies of xerces to be included due to transitive dependencies resolution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-1967) Local repository URL containing / does not work under windows
Local repository URL containing / does not work under windows - Key: MNG-1967 URL: http://jira.codehaus.org/browse/MNG-1967 Project: Maven 2 Type: Bug Components: Artifacts and Repositories Versions: 2.0.1 Environment: Windows 2000 Pro, java version "1.4.2_03" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_03-b02) Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) Reporter: Loïc Lefèvre Attachments: bug.zip When using / in a local repository URL, it does not work under windows. Replacing it with \ solves the problem. See testcase included (run under windows environment). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MWAR-22) patch to allow extra webapp and webapp/WEB-INF/classes files to be specified that override existing files
[ http://jira.codehaus.org/browse/MWAR-22?page=comments#action_55905 ] Cameron Braid commented on MWAR-22: --- related to http://www.mail-archive.com/users@maven.apache.org/msg10554.html thread > patch to allow extra webapp and webapp/WEB-INF/classes files to be specified > that override existing files > - > > Key: MWAR-22 > URL: http://jira.codehaus.org/browse/MWAR-22 > Project: Maven 2.x War Plugin > Type: Improvement > Reporter: Cameron Braid > Attachments: maven-war-plugin-extraWarResources.patch > > > Currnelty, there is no way to execute a plugin inbetween the 'build exploded > webapp' part of this plugin, and the 'zip up resources' bit. > I have the need to override classpath resources, and sometimes other webapp > resources, based on a deployment target, such as test / staging or production. > With this patch, I will be able to have files layed out like this : > /profile/test/config.properties > /src/main/resources/config.properties > then configure the war plugin : > > profile/test > > thus producing a war that contains profile/test/config.properties instead of > the default /src/main/resources/config.properties > I have investigated alternative ways to achive this goal, and none of them > seemed easy. > Some ideas : > * split the package phase into 2 phases - preparePackage and package > * provide a generic technique to allow plugins to expose extension points > where other plugins can hook into > * create a plugin that runs after the war plugin, that creates a new war - > slow since the ziping will need to be done twice > i'm keen to hear anyone's thoughts on the mailing list or in irc - my nick is > Fracture -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MWAR-22) patch to allow extra webapp and webapp/WEB-INF/classes files to be specified that override existing files
patch to allow extra webapp and webapp/WEB-INF/classes files to be specified that override existing files - Key: MWAR-22 URL: http://jira.codehaus.org/browse/MWAR-22 Project: Maven 2.x War Plugin Type: Improvement Reporter: Cameron Braid Attachments: maven-war-plugin-extraWarResources.patch Currnelty, there is no way to execute a plugin inbetween the 'build exploded webapp' part of this plugin, and the 'zip up resources' bit. I have the need to override classpath resources, and sometimes other webapp resources, based on a deployment target, such as test / staging or production. With this patch, I will be able to have files layed out like this : /profile/test/config.properties /src/main/resources/config.properties then configure the war plugin : profile/test thus producing a war that contains profile/test/config.properties instead of the default /src/main/resources/config.properties I have investigated alternative ways to achive this goal, and none of them seemed easy. Some ideas : * split the package phase into 2 phases - preparePackage and package * provide a generic technique to allow plugins to expose extension points where other plugins can hook into * create a plugin that runs after the war plugin, that creates a new war - slow since the ziping will need to be done twice i'm keen to hear anyone's thoughts on the mailing list or in irc - my nick is Fracture -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m1] source plugin
Stephane Nicoll wrote: On 1/14/06, Doug Douglass <[EMAIL PROTECTED]> wrote: The only problem I see is that the eclipse plugin does not install the sources in the local repository, thus making it appear that it does not work. Perhaps this is the reason it's not working for you Arnaud? What do you mean? To install the source in the local repo, source:install Sure that works, presuming you have the source in a local project in which you can run source:install. But, if the source jar is in a remote repo already, I don't currently see a way to download that jar to the local repo via either the eclipse or the source plugin. Doug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-683) javacc version 4.0
javacc version 4.0 -- Key: MAVENUPLOAD-683 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-683 Project: maven-upload-requests Type: Task Reporter: Greg Kick I am requesting that version 4.0 of javacc be added to the repository. Please see the project url for any information about the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Sun Jan 15 13:15:01 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060115.131501.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060115.131501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - update] Sun Jan 15 13:00:01 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060115.130001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060115.130001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - SUCCESS - update] Sun Jan 15 11:45:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060115.114500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060115.114500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build trunk - SUCCESS - update] Sun Jan 15 11:30:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060115.113001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060115.113001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MJAVADOC-48) Quotes in project produce 'illegal package name' error
Quotes in project produce 'illegal package name' error - Key: MJAVADOC-48 URL: http://jira.codehaus.org/browse/MJAVADOC-48 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: Kenney Westerhof Priority: Trivial Specifying a Foo 'bar' will produce the following output: --- [INFO] Error during report generation Embedded error: Exit code: 1 - javadoc: error - Illegal package name: " 1.0 API" javadoc: error - Illegal package name: " 1.0 API" javadoc: warning - No source files for package protocol javadoc: warning - No source files for package protocol The ' 1.0 API' comes from another project, but removing the ' makes the error go away. As everything else seems to work fine with quotes in the project name I assume this is a bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1740) https repositories are not supported
[ http://jira.codehaus.org/browse/MAVEN-1740?page=comments#action_55901 ] Kohsuke Kawaguchi commented on MAVEN-1740: -- This currently prevents Maven 1.1 beta2 users from accessing the java.net maven repository. See WAGONHTTP-5 for another blocker. > https repositories are not supported > > > Key: MAVEN-1740 > URL: http://jira.codehaus.org/browse/MAVEN-1740 > Project: Maven > Type: Bug > Components: core > Versions: 1.1-beta-2 > Environment: Windows XP > Reporter: Kohsuke Kawaguchi > > > Maven 1.1 beta2 doesn't support the https repositories (it tries to handle it > as file protocol) > In fact, org.apache.maven.verifier.DependencyVerifier line 374 reads: > if ( repository.getProtocol().equals( "http" ) ) > { > wagon = new HttpWagon(); > } > else > { > wagon = new FileWagon(); > } > This used to work with Maven 1.0.2 (which apparently isn't using Wagon for > downloading dependency jars.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MAVEN-1740) https repositories are not supported
[ http://jira.codehaus.org/browse/MAVEN-1740?page=comments#action_55900 ] Kohsuke Kawaguchi commented on MAVEN-1740: -- Simply changing the problematic line to: if ( repository.getProtocol().equals( "http" ) || repository.getProtocol().equals( "https" ) ) seems to make it work. > https repositories are not supported > > > Key: MAVEN-1740 > URL: http://jira.codehaus.org/browse/MAVEN-1740 > Project: Maven > Type: Bug > Components: core > Versions: 1.1-beta-2 > Environment: Windows XP > Reporter: Kohsuke Kawaguchi > > > Maven 1.1 beta2 doesn't support the https repositories (it tries to handle it > as file protocol) > In fact, org.apache.maven.verifier.DependencyVerifier line 374 reads: > if ( repository.getProtocol().equals( "http" ) ) > { > wagon = new HttpWagon(); > } > else > { > wagon = new FileWagon(); > } > This used to work with Maven 1.0.2 (which apparently isn't using Wagon for > downloading dependency jars.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cargo artifacts not served by the m1 repo on ibiblio
Hi (Brett), The Cargo 0.7 artifacts are correctly served by the m2 repo on ibiblio (http://www.ibiblio.org/maven2/org/codehaus/cargo/). However the URL rewriting rules for making the m2 repo a m1 repo do not seem to work. I'm not sure what the URL should be but I've tried: http://www.ibiblio.org/maven/org.codehaus.cargo/ (does not work) http://www.ibiblio.org/maven/org/codehaus/cargo/ (does not work but that's expected as it would violate m1 repo rules) http://www.ibiblio.org/maven/cargo/ (this works but delivers the old Cargo files and not the new ones) How do we make the new 0.7 artifacts visible under m1? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1740) https repositories are not supported
https repositories are not supported Key: MAVEN-1740 URL: http://jira.codehaus.org/browse/MAVEN-1740 Project: Maven Type: Bug Components: core Versions: 1.1-beta-2 Environment: Windows XP Reporter: Kohsuke Kawaguchi Maven 1.1 beta2 doesn't support the https repositories (it tries to handle it as file protocol) In fact, org.apache.maven.verifier.DependencyVerifier line 374 reads: if ( repository.getProtocol().equals( "http" ) ) { wagon = new HttpWagon(); } else { wagon = new FileWagon(); } This used to work with Maven 1.0.2 (which apparently isn't using Wagon for downloading dependency jars.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]