[jira] Updated: (MRM-69) Simple "query everything" search
[ http://jira.codehaus.org/browse/MRM-69?page=all ] Maria Odea Ching updated MRM-69: Attachment: MRM-69-maven-repository-indexer.patch > Simple "query everything" search > > > Key: MRM-69 > URL: http://jira.codehaus.org/browse/MRM-69 > Project: Maven Repository Manager > Type: Task > Reporter: Maria Odea Ching > Assignee: Maria Odea Ching > Attachments: MRM-69-maven-repository-indexer.patch > > Original Estimate: 15 hours >Time Spent: 8 hours > Remaining: 7 hours > > Search keyword/term in any of the fields in the index. -- 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] Thu Feb 9 05:45:01 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060209.054502.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060209.054502.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-43) integrate maven-proxy and/or proximity
[ http://jira.codehaus.org/browse/MRM-43?page=all ] Edwin Punzalan closed MRM-43: - Resolution: Fixed > integrate maven-proxy and/or proximity > -- > > Key: MRM-43 > URL: http://jira.codehaus.org/browse/MRM-43 > Project: Maven Repository Manager > Type: Task > Components: remote proxy > Reporter: Brett Porter > Assignee: Edwin Punzalan > Fix For: 1.0-alpha-1 > > Original Estimate: 5 days >Time Spent: 1 week, 1 day > Remaining: 0 minutes > > http://maven-proxy.codehaus.org/ > https://is-micro.myip.hu/projects/ismicro-commons/proximity/ -- 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: (MRM-93) Use wagon for local cache operations
Use wagon for local cache operations Key: MRM-93 URL: http://jira.codehaus.org/browse/MRM-93 Project: Maven Repository Manager Type: Task Components: remote proxy Reporter: Edwin Punzalan Currently, the proxy module uses File operations for the local repository because wagon does not support path-based file retrieval. As of now, wagon supports only Artifact and Metadata retrieval among its public methods. -- 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] Thu Feb 9 05:00:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060209.050001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060209.050001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPMD-12) Use PMD 3.5
[ http://jira.codehaus.org/browse/MPMD-12?page=all ] Brett Porter closed MPMD-12: Assign To: Brett Porter Resolution: Fixed Fix Version: 2.0-beta-2 > Use PMD 3.5 > --- > > Key: MPMD-12 > URL: http://jira.codehaus.org/browse/MPMD-12 > Project: Maven 2.x Pmd Plugin > Type: Improvement > Reporter: Wim Deblauwe > Assignee: Brett Porter > Fix For: 2.0-beta-2 > > > A new version of PMD has been released: 3.5 -- 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 - update] Thu Feb 9 04:45:01 GMT 2006
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060209.044501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPMD-12) Use PMD 3.5
[ http://jira.codehaus.org/browse/MPMD-12?page=comments#action_58211 ] Brett Porter commented on MPMD-12: -- I think "* TODO: Remove deprecated RuleViolation.getLine()" means they actually removed it, because it no longer compiles :) > Use PMD 3.5 > --- > > Key: MPMD-12 > URL: http://jira.codehaus.org/browse/MPMD-12 > Project: Maven 2.x Pmd Plugin > Type: Improvement > Reporter: Wim Deblauwe > > > A new version of PMD has been released: 3.5 -- 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: repository manager overview
Milos Kleint wrote: > is it already running somewhere to try it out? no > witn IDE integration what's the best approach using it? connect to > server in interactive mode or download the index and reuse the manager > code to do the searching? no xmlrpc on it at this point in time. You can download the index - that's how the eclipse plugin is doing it. The embedder will eventually expose the code directly so the local repo can be indexed too. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: repository manager overview
is it already running somewhere to try it out? witn IDE integration what's the best approach using it? connect to server in interactive mode or download the index and reuse the manager code to do the searching? Milos On 2/8/06, Brett Porter <[EMAIL PROTECTED]> wrote: > Some folks seem interested, so I wanted to give a quick overview of the > repository manager. > > It is an application that runs either standalone or as a webapp with the > following functionality: > - repository search > - repository/artifact browsing and display of artifacts and their > relationships > - repository health reports (missing transitive dependencies, > incorrect/missing checksums, incorrect/missing digital signatures, out > of place artifacts, missing poms, etc) > - maven-proxy like support > - repository conversion > > It has the following modules: > - discovery: walks a repository and finds all the artifacts in it so you > can perform a certain action on each, or just the ones that are > new/deleted since last walked. > - indexer: used to add artifacts and metadata to the lucene index. > Includes elements of the POM and checksums > - converter: copy artifacts from one repository to the other, changing > layout, converting metadata if required. > - artifact-applet: applet to allow you to checksum a large artifact on > your local machine and upload the checksum to the server to search > - reports-standard: a bunch of reports on the status of an artifact in > the repository > - proxy: maven-proxy like functionality > - utils: checksum, pathing, etc > - webapp: webwork 2 and plexus based webapp for running it all > > Any questions? > > - Brett > > - > 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: (MEAR-18) The EAR plugin will not properly handle WSR (Jboss web service archives) specified as dependencies in the pom.xml
The EAR plugin will not properly handle WSR (Jboss web service archives) specified as dependencies in the pom.xml - Key: MEAR-18 URL: http://jira.codehaus.org/browse/MEAR-18 Project: Maven 2.x Ear Plugin Type: Wish Versions: 2.0, 2.1 Reporter: Brad O'Hearne If you try to include a Jboss web service archive (WSR file) in your EAR, by listing it as a dependency in your EAR project's pom.xml, you will get an error that says: [INFO] Trace java.lang.IllegalStateException: Could not handle artifact type[wsr] at org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFa ctory.java:75) at org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.j ava:119) I have created a plugin that creates wsr files, and have referenced that in my pom.xml, so I am confident that this error is a result of the EAR plugin not recognizing wsr files. -- 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-2058) New plugin to handle jboss web service archives (WSR) files
New plugin to handle jboss web service archives (WSR) files --- Key: MNG-2058 URL: http://jira.codehaus.org/browse/MNG-2058 Project: Maven 2 Type: New Feature Components: Plugins and Lifecycle Versions: 2.0, 2.0.1, 2.0.2 Reporter: Brad O'Hearne Attachments: jboss-wsr-maven-plugin.tar.gz This plugin is basically a ripoff of the existing jboss-sar-maven-plugin, changed to handle jboss web service archives (wsr files). Note that the present maven EAR plugin does not handle WSR files properly, if trying to include a WSR file in your EAR. -- 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 - update] Thu Feb 9 04:15:00 GMT 2006
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060209.041501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Is there a way to trigger a goal on another pom within a plugin?
Hi, I have a plugin that needs to checkout some resources then trigger a 'mvn site' on the checked out sources. Right now I've tried to fork mvn which works on unix but not on windows. I'd like to get maven to just execute the goal on the other pom.xml without having to fork it. Is there a way this can be done? Thanks, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Thu Feb 9 03:45:00 GMT 2006
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060209.034501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r374306 - in /maven/repository-manager/trunk/maven-repository-utils: pom.xml src/main/java/org/apache/maven/repository/ArtifactUtils.java src/test/java/org/apache/maven/repository/Arti
I think one of the commits after this fixed it. ^_^ Brett Porter wrote: [EMAIL PROTECTED] wrote: Modified: maven/repository-manager/trunk/maven-repository-utils/pom.xml URL: http://svn.apache.org/viewcvs/maven/repository-manager/trunk/maven-repository-utils/pom.xml?rev=374306&r1=374305&r2=374306&view=diff == --- maven/repository-manager/trunk/maven-repository-utils/pom.xml (original) +++ maven/repository-manager/trunk/maven-repository-utils/pom.xml Thu Feb 2 00:52:25 2006 @@ -27,6 +27,10 @@ org.codehaus.plexus + plexus-container-default + + + org.codehaus.plexus plexus-utils Should this be test ? - Brett - 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 - FAILED - update] Thu Feb 9 03:15:01 GMT 2006
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060209.031502.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-2000) Create comprehensive profiles documentation
[ http://jira.codehaus.org/browse/MNG-2000?page=all ] Allan Ramirez updated MNG-2000: --- Remaining Estimate: 16 hours Original Estimate: 16 hours > Create comprehensive profiles documentation > --- > > Key: MNG-2000 > URL: http://jira.codehaus.org/browse/MNG-2000 > Project: Maven 2 > Type: Task > Components: Documentation: Guides > Reporter: John Casey > Assignee: Allan Ramirez > Priority: Critical > Fix For: documentation > > Original Estimate: 16 hours > Remaining: 16 hours > > This document should draw from the mailing list, FAQ wiki, MNGFAQ jira > project (on codehaus), existing site documentation, project source code, and > any IRC conversations necessary. > It should include: > * How can I tell which profiles are in effect during a build? > * What are the different types of profile? Where is each defined? > * Which areas of a POM can be customized by each type of profile? Why? > - settings-defined and profiles.xml-defined only modify properties, > repositories, and pluginRepositories. This is necessary to preserve the > portability of the pom as much as possible, since these two locations are not > installed/deployed to the repository system. > * How can a profile be triggered? How does this vary according to the type of > profile being used? > * Profiles are not inherited, but their effects are, because they are applied > to the POM before it's used for inheritance. This means a parent POM will > have its profiles triggered and applied before it is used to calculate the > inherited values for the current POM. Please include this in the > documentation as well. > There's probably more, but I can't think of it off the top of my head. We > need to make this another one of those definitive documents for POM > configuration. -- 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: design docs for repositories?
Yes, in Maven you can have multiple remote repositories. This is most commonly done to have an "internal" repository for non-public distributions, in addition to the public open-source repository. But you can have as many remote repositories as you wish. -Stephen On 2/8/06, Lex Spoon <[EMAIL PROTECTED]> wrote: > Hi, we at the Scala group (scala.epfl.ch) are looking at community > infrastructure to share artifacts around. Joel Trunick pointed me > towards Maven. > > Maven is interesting for us to begin with as simply an improved ant for > building software. More specifically, though, its support for remote > repositories and for inter-package dependencies is intriguing, because > we've made a special effort to try and support Scala enthusiasts sharing > the things they make with each other. > > Our running approach in "Scala Bazaars" is to use something based on > Linux distributions called "package universes".I am wondering if we > should adopt Maven's approach instead, or if our approach has something > Maven would find useful, or if otherwise there is a sensible way to > combine efforts? > > I have poked around on maven.apche.org but so far have not run into a > good description of the rationale and design for (1) repositories and > (2) dependencies between artifacts. Can anyone point me to a good read? > > For example, one question I have is: does Maven support haing multiple > remote repositories, analagous to non-standard Debian apt repositories? > And on a related note, does it support multiple streams of development, > analogous to stable and unstable streams for Debian distributions? > Package universes is careful to allow all of this. > > I look forward to any pointers and thoughts. Here's some info on where > Scala's artifact-sharing infrastructure is for now: > > http://lamp.epfl.ch/~spoon/sbaz > > > Regards, > > Lex Spoon > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Thu Feb 9 02:45:00 GMT 2006
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060209.024501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Thu Feb 9 02:15:00 GMT 2006
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060209.021501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2057) The Maven 2.0.2 XML parser fails to parse a UTF-8 POM that begins with the optional byte-order mark.
The Maven 2.0.2 XML parser fails to parse a UTF-8 POM that begins with the optional byte-order mark. Key: MNG-2057 URL: http://jira.codehaus.org/browse/MNG-2057 Project: Maven 2 Type: Bug Components: POM Versions: 2.0.2 Environment: java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing) Microsoft Windows XP [Version 5.1.2600] Reporter: Steven Coco Attachments: UTF8-BOM-pom.zip The Byte-Order mark is optional, and discouraged in the UTF-8 encoding; but the Unicode specification is clear that it is allowed -- if you read the Unicode Standard v4, section 2.6, and Table 2.3, and section 15.9, and table 15.3; it is clear that the BOM is allowed at the start of a UTF-8 file. It so happens that this is the way Windows NotePad saves files when you select UTF-8; and Maven will not parse it. I'll attach a small POM saved this way, and I'll put it into a ZIP file to hopefully preserve the encoding. Here is the Maven output: [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown POM Location: C:\Documents and Settings\Coco\Desktop\pom.xml Reason: Parse error reading POM. Reason: only whitespace content allowed before start tag and not \u ef (position: START_DOCUMENT seen \uef... @1:1) [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Parse error reading POM. Reason: only whitespace c ontent allowed before start tag and not \uef (position: START_DOCUMENT seen \uef... @1:1) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.InvalidProjectModelException: Parse error reading POM. Reason: o nly whitespace content allowed before start tag and not \uef (position: START_DOCUMENT seen \uef... @1:1) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder. java:1134) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder. java:1094) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProje ctBuilder.java:289) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java :274) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) ... 11 more Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: only whitespace content allowed before start tag and not \uef (position: START_DOCUMENT seen \uef... @1:1) at org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1516) at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1392) at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4545) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder. java:1130) ... 17 more [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Wed Feb 08 21:14:03 EST 2006 [INFO] Final Memory: 1M/2M [INFO] -- 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.atlass
[jira] Subscription: Outstanding Repository Maintenance: Uploads
Issue Subscription Filter: Outstanding Repository Maintenance: Uploads (5 issues) Subscriber: mavendevlist Key Summary MAVENUPLOAD-729Sourceforge project 'dozer' to be uploaded. http://jira.codehaus.org/browse/MAVENUPLOAD-729 MAVENUPLOAD-728Upload backport-util-concurrent version 2.1 http://jira.codehaus.org/browse/MAVENUPLOAD-728 MAVENUPLOAD-727Please add Hibernate 3.1.2 sources http://jira.codehaus.org/browse/MAVENUPLOAD-727 MAVENUPLOAD-726Please upload Canoo WebTest Release 1168 http://jira.codehaus.org/browse/MAVENUPLOAD-726 MAVENUPLOAD-725Please upload displaytag 12 tld http://jira.codehaus.org/browse/MAVENUPLOAD-725 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Subscription: Outstanding Repository Maintenance: Evangelism
Issue Subscription Filter: Outstanding Repository Maintenance: Evangelism (30 issues) Subscriber: mavendevlist Key Summary MEV-326 Spring 2.0 M2 is missing a POM http://jira.codehaus.org/browse/MEV-326 MEV-325 Description of jaxb-api 1.0.1 is wrong http://jira.codehaus.org/browse/MEV-325 MEV-324 Relocate javassist group to jboss http://jira.codehaus.org/browse/MEV-324 MEV-316 spring-support should have all dependencies be optional http://jira.codehaus.org/browse/MEV-316 MEV-313 publish seperate spring POM's for seperate dependencies http://jira.codehaus.org/browse/MEV-313 MEV-277 More Spring Dependencies Should be Optional http://jira.codehaus.org/browse/MEV-277 MEV-320 Hibernate 3.1.x POMs pull in Sun jars http://jira.codehaus.org/browse/MEV-320 MEV-318 Dependencies for Axion http://jira.codehaus.org/browse/MEV-318 MEV-314 asn1-ber lists incorrect groupId http://jira.codehaus.org/browse/MEV-314 MEV-310 POMs for hivemind:hivemind:1.1 and hivemind:hivemind-lib:1.1 are missing dependencies http://jira.codehaus.org/browse/MEV-310 MEV-312 tag is misspelled in maven2 ant-optional-1.5.3-1.pom http://jira.codehaus.org/browse/MEV-312 MEV-309 PicoContainer 1.0 POM invalid http://jira.codehaus.org/browse/MEV-309 MEV-302 Invalid m2 pom for joda-time-hibernate-0.8 http://jira.codehaus.org/browse/MEV-302 MEV-295 dom4j optional dependencies http://jira.codehaus.org/browse/MEV-295 MEV-308 dom4j-1.4-dev8 has an invalid pom http://jira.codehaus.org/browse/MEV-308 MEV-301 relocate xerces:xerces or xerces:xercesImpl http://jira.codehaus.org/browse/MEV-301 MEV-296 Activemq-core (and other activemq projects) 3.2.1 have unexpanded variables http://jira.codehaus.org/browse/MEV-296 MEV-298 Invalid deps in activemq projects http://jira.codehaus.org/browse/MEV-298 MEV-299 Pom for activeio-2.1 http://jira.codehaus.org/browse/MEV-299 MEV-282 Please relocate jspapi:jsp-api to javax.servlet:jsp-api http://jira.codehaus.org/browse/MEV-282 MEV-255 Problem with junit-addons 1.4 http://jira.codehaus.org/browse/MEV-255 MEV-126 poms for som emissing sun xml API + javamail 1.3.3 http://jira.codehaus.org/browse/MEV-126 MEV-201 should have dependency on org.relaxngdatatype.relaxngDatatype http://jira.codehaus.org/browse/MEV-201 MEV-173 xmlpull JARs exist in two different places on ibiblio http://jira.codehaus.org/browse/MEV-173 MEV-48 openejb poms http://jira.codehaus.org/browse/MEV-48 MEV-45 Full list of poms that doesn't respect the m2 format http://jira.codehaus.org/browse/MEV-45 MEV-36 Exo POM(s) missing dependency versions http://jira.codehaus.org/browse/MEV-36 MEV-33 XOM POM references xercesImpl v.2.2.1 which does not exist in repo http://jira.codehaus.org/browse/MEV-33 MEV-31 XOM POM references xmlParserAPIs v2.6.1 which is not in the repo http://jira.codehaus.org/browse/MEV-31 MEV-20 clean up bad IDs in the repository http://jira.codehaus.org/browse/MEV-20 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build branches/maven-2.0.x - FAILED - update] Thu Feb 9 01:45:00 GMT 2006
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060209.014501.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2056) Exception when starting new page with AbstractMavenMultiPageReport
Exception when starting new page with AbstractMavenMultiPageReport -- Key: MNG-2056 URL: http://jira.codehaus.org/browse/MNG-2056 Project: Maven 2 Type: Bug Components: Sites & Reporting Versions: 2.0.2 Environment: OS X 10.3.4. running JDK 1.5 (1.5.0_06-93) Reporter: Adam Winer Attempts to call AbstractMavenMultiPageReport.startPage() from a custom report result in the following exception: Caused by: java.io.EOFException: input contained no data at org.codehaus.plexus.util.xml.pull.MXParser.fillBuf(MXParser.java:2979) at org.codehaus.plexus.util.xml.pull.MXParser.more(MXParser.java:3022) at org.codehaus.plexus.util.xml.pull.MXParser.parseProlog(MXParser.java:1407) at org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1392) at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1090) at org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:172) at org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:83) at org.codehaus.plexus.util.xml.Xpp3DomBuilder.build(Xpp3DomBuilder.java:48) at org.codehaus.doxia.module.xhtml.decoration.model.DecorationModelReader.createNavigation(DecorationModelReader.java:30) at org.codehaus.doxia.site.renderer.DefaultSiteRenderer.createSink(DefaultSiteRenderer.java:244) at org.apache.maven.reporting.sink.SinkFactory.getSink(SinkFactory.java:76) at org.apache.maven.reporting.AbstractMavenMultiPageReport.getSink(AbstractMavenMultiPageReport.java:79) at org.apache.maven.reporting.AbstractMavenMultiPageReport.startPage(AbstractMavenMultiPageReport.java:85) FYI, I'm creating the SinkFactory for the multipage report using: SinkFactory factory = new SinkFactory(); factory.setSiteRenderer(getSiteRenderer()); factory.setSiteDirectory(getOutputDirectory()); setSinkFactory(factory); Without this code, you just get a NullPointerException in AbstractMavenMultiPageReport.getSink(). -- 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] Thu Feb 9 01:00:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060209.010001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060209.010001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPMD-13) Provide pmd:check (patch attached)
[ http://jira.codehaus.org/browse/MPMD-13?page=all ] Brett Porter closed MPMD-13: Assign To: Brett Porter Resolution: Fixed Fix Version: 2.0-beta-2 > Provide pmd:check (patch attached) > -- > > Key: MPMD-13 > URL: http://jira.codehaus.org/browse/MPMD-13 > Project: Maven 2.x Pmd Plugin > Type: New Feature > Reporter: John Allen > Assignee: Brett Porter > Fix For: 2.0-beta-2 > Attachments: PmdViolationCheckMojo.java > > > Attached file adds a pmd:check goal (a direct rip off of checkstyle:check) -- 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: (MPMD-13) Provide pmd:check (patch attached)
[ http://jira.codehaus.org/browse/MPMD-13?page=comments#action_58207 ] Brett Porter commented on MPMD-13: -- thanks! > Provide pmd:check (patch attached) > -- > > Key: MPMD-13 > URL: http://jira.codehaus.org/browse/MPMD-13 > Project: Maven 2.x Pmd Plugin > Type: New Feature > Reporter: John Allen > Attachments: PmdViolationCheckMojo.java > > > Attached file adds a pmd:check goal (a direct rip off of checkstyle:check) -- 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] Thu Feb 9 00:30:00 GMT 2006
Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060209.003000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPMD-13) Provide pmd:check (patch attached)
Provide pmd:check (patch attached) -- Key: MPMD-13 URL: http://jira.codehaus.org/browse/MPMD-13 Project: Maven 2.x Pmd Plugin Type: New Feature Reporter: John Allen Attachments: PmdViolationCheckMojo.java Attached file adds a pmd:check goal (a direct rip off of checkstyle:check) -- 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 - checkout] Thu Feb 9 00:00:01 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060209.02.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060209.02.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: repository manager overview
Brian E. Fox wrote: > I've been meaning to try this out. How much of the functionality listed > below is usable in some form? (I know it's still being developed) > Its not well integrated yet (the individual components are tested and usable on their own). The webapp will tie a lot together. dan tran wrote: > can it cleanup repository? I am doing daily release, and one a while to > need to > remove unused artifacts ( only milestone ones stay). We could add rules for that as an action on discovery. > Currently I > selectively remove > the version folders but leave meta data file untouch. > > Can this app fix up my metadata files? Yes. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPJALOPY-9) Jalopy Classes not found
[ http://jira.codehaus.org/browse/MPJALOPY-9?page=all ] Arnaud Heritier closed MPJALOPY-9: -- Resolution: Fixed Fixed. A Snapshot is deployed. > Jalopy Classes not found > > > Key: MPJALOPY-9 > URL: http://jira.codehaus.org/browse/MPJALOPY-9 > Project: maven-jalopy-plugin > Type: Bug > Versions: 1.3.1, 1.4 > Reporter: Arnaud Heritier > Assignee: Arnaud Heritier > Priority: Blocker > Fix For: 1.4.1 > > > Mail from Wendy Smoak : > Twice now, on two different machines (same codebase, though,) the > Jalopy plugin was working fine and then suddenly stopped working with > the error below. > Full output of maven jalopy -X is here: > http://wiki.wsmoak.net/cgi-bin/wiki.pl?Maven/Jalopy > The only thing that changed was Jalopy's config file. Reverting those > changes to a known good state didn't help. Other developers on the > project aren't having any trouble. Obviously I've done *something* to > it (twice!) but I have no idea what. > Does anyone see anything that looks suspicious? > -Wendy > /svn/struts/current/action > $ maven jalopy > __ __ > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.0.2 > java.lang.ClassCastException: java.lang.String >at > de.hunsicker.jalopy.storage.Convention.synchronize(Convention.java:24 > 19) >at > de.hunsicker.jalopy.storage.Convention.synchronize(Convention.java:24 > 45) >at de.hunsicker.jalopy.storage.Convention.(Convention.java:211) >at de.hunsicker.jalopy.plugin.ant.AntPlugin.(AntPlugin.java:60) >at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) >at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct > orAccessorImpl.java:39) >at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC > onstructorAccessorImpl.java:27) >at java.lang.reflect.Constructor.newInstance(Constructor.java:494) >at > org.apache.tools.ant.AntClassLoader.initializeClass(AntClassLoader.ja > va:490) >at > org.apache.tools.ant.taskdefs.Definer.addDefinition(Definer.java:231) >at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:162) >at org.apache.tools.ant.Task.perform(Task.java:341) >at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:185) > ... > build:start: > jalopy:taskdef: > java:prepare-filesystem: > java:compile: >[echo] Compiling to c:\svn\struts\current\action/target/classes > BUILD FAILED > File.. c:\java\m1-repository\cache\maven-jalopy-plugin-1.3.1\plugin.jelly > Element... ant:jalopy > Line.. 64 > Column 46 > java.lang.NoClassDefFoundError > Total time: 2 seconds > Finished at: Tue Feb 07 22:20:09 GMT-07:00 2006 > Arnaud's note : > I have a similar error with the jalopy plugin 1.4 and maven 1.1 beta 3 -- 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-73) Javadoc Warnings report is empty, has parse exception
[ http://jira.codehaus.org/browse/MPJAVADOC-73?page=comments#action_58205 ] Arnaud Heritier commented on MPJAVADOC-73: -- tell us if it's fixed for you tomorrow and we'll close the issue. Thanks > Javadoc Warnings report is empty, has parse exception > - > > Key: MPJAVADOC-73 > URL: http://jira.codehaus.org/browse/MPJAVADOC-73 > Project: maven-javadoc-plugin > Type: Bug > Versions: 1.8 > Environment: Maven 1.1b2 > Plugin versions: javadoc 1.8, xdoc 1.9.2, site 1.6.1 > Win2K > Reporter: Jeff Jensen > Attachments: site_javadoc-warnings.xml, site_report.txt, > xdoc_javadoc-warnings.xml, xdoc_report.txt > > > The report is empty: states the number of files, number of errors=0, and an > empty Files section. > Running it with maven.javadoc.debug=true, the following info is in the log > (the first error message): > Read 276 line(s) from input file > Building map from 276 input line(s) > Parsing line [javadoc] > C:\devroot\perforce\healthmatchcommon\main\src\java\us\state\vantage\hm\ar\entity\AccountAWPContainer.java:66: > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in > us.state.vantage.hm.ar.entity.AccountAWPContainer > *** WARNING: exception parsing line ' [javadoc] > C:\devroot\perforce\healthmatchcommon\main\src\java\us\state\vantage\hm\ar\entity\AccountAWPContainer.java:66: > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in > us.state.vantage.hm.ar.entity.AccountAWPContainer': > org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set; > java.lang.NoSuchMethodError: > org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set; > at > org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarningsTextToXml.java:295) > This failure repeats many times, I think for every warning in the file. > But, if I run "maven javadoc xdoc" only, the file parses correctly and xdoc > creates a correct web page. -- 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: repository manager overview
can it cleanup repository? I am doing daily release, and one a while to need to remove unused artifacts ( only milestone ones stay). Currently I selectively remove the version folders but leave meta data file untouch. Can this app fix up my metadata files? Thanks -Dan On 2/8/06, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > I've been meaning to try this out. How much of the functionality listed > below is usable in some form? (I know it's still being developed) > > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 08, 2006 5:40 PM > To: Maven Developers List > Subject: repository manager overview > > Some folks seem interested, so I wanted to give a quick overview of the > repository manager. > > It is an application that runs either standalone or as a webapp with the > following functionality: > - repository search > - repository/artifact browsing and display of artifacts and their > relationships > - repository health reports (missing transitive dependencies, > incorrect/missing checksums, incorrect/missing digital signatures, out > of place artifacts, missing poms, etc) > - maven-proxy like support > - repository conversion > > It has the following modules: > - discovery: walks a repository and finds all the artifacts in it so you > can perform a certain action on each, or just the ones that are > new/deleted since last walked. > - indexer: used to add artifacts and metadata to the lucene index. > Includes elements of the POM and checksums > - converter: copy artifacts from one repository to the other, changing > layout, converting metadata if required. > - artifact-applet: applet to allow you to checksum a large artifact on > your local machine and upload the checksum to the server to search > - reports-standard: a bunch of reports on the status of an artifact in > the repository > - proxy: maven-proxy like functionality > - utils: checksum, pathing, etc > - webapp: webwork 2 and plexus based webapp for running it all > > Any questions? > > - Brett > > - > 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: repository manager overview
I've been meaning to try this out. How much of the functionality listed below is usable in some form? (I know it's still being developed) -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 08, 2006 5:40 PM To: Maven Developers List Subject: repository manager overview Some folks seem interested, so I wanted to give a quick overview of the repository manager. It is an application that runs either standalone or as a webapp with the following functionality: - repository search - repository/artifact browsing and display of artifacts and their relationships - repository health reports (missing transitive dependencies, incorrect/missing checksums, incorrect/missing digital signatures, out of place artifacts, missing poms, etc) - maven-proxy like support - repository conversion It has the following modules: - discovery: walks a repository and finds all the artifacts in it so you can perform a certain action on each, or just the ones that are new/deleted since last walked. - indexer: used to add artifacts and metadata to the lucene index. Includes elements of the POM and checksums - converter: copy artifacts from one repository to the other, changing layout, converting metadata if required. - artifact-applet: applet to allow you to checksum a large artifact on your local machine and upload the checksum to the server to search - reports-standard: a bunch of reports on the status of an artifact in the repository - proxy: maven-proxy like functionality - utils: checksum, pathing, etc - webapp: webwork 2 and plexus based webapp for running it all Any questions? - Brett - 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] Commented: (MNG-1898) Plugin classpath broken from 2.0 to 2.0.1
[ http://jira.codehaus.org/browse/MNG-1898?page=comments#action_58204 ]
Carlos Sanchez commented on MNG-1898:
-
Try excluding xml-apis and xerces. That fixed a similar problem for me
> Plugin classpath broken from 2.0 to 2.0.1
> -
>
> Key: MNG-1898
> URL: http://jira.codehaus.org/browse/MNG-1898
> Project: Maven 2
> Type: Bug
> Environment: winxp
> Reporter: Brian Fox
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0.3
> Attachments: MNG-1898-coreit.tar.bz2, test-1.0.zip, test-case.zip
>
>
> I'm working on a kodo plugin in the codehaus mojo sandbox. Using 2.0, it
> works fine. In 2.1, it can't find xercesImpl, which is a transitive
> dependency of the plugin. Did something change to cause new behavior (aka a
> bug) related to this? Just eyeballing the info below, in 2.0, the instance of
> classloader was org.codehaus.classworlds.RealmClassLoader but in 2.0.1 it is
> org.codehaus.plexus.util.RealmDelegatingClassLoader
>
> I tried specifying xercesImpl as a direct dependency and that didn't work
> either so I'm not sure it's related to the transitivity.
>
> Output from 2.0.1: (2.0 follows further below)
>
> [DEBUG] org.codehaus.mojo:kodo-maven-plugin:maven-plugin:1.0-alpha-1-SNAPSHOT
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime)
> [DEBUG] Skipping disabled repository snapshots
> [DEBUG] com.solarmetric:kodo-jdo:jar:3.3.3 (setting version to: 3.3.3 from
> range: [3.0,])
> [DEBUG] com.solarmetric:kodo-jdo:jar:3.3.3 (selected for runtime)
> [DEBUG] com.solarmetric:kodo-wl81manage:jar:1.0 (selected for runtime)
> [DEBUG] com.solarmetric:kodo-workbench:jar:1.0 (selected for runtime)
> [DEBUG] org.hsqldb:jdbc-hsql:jar:1.7.0 (selected for runtime)
> [DEBUG] sqlline:sqlline:jar:1.0 (selected for runtime)
> [DEBUG] jcommon:jcommon:jar:0.9.1 (selected for runtime)
> [DEBUG] javax.jdo:jdo:jar:1.0.2 (selected for runtime)
> [DEBUG] xalan:xalan:jar:2.5.1 (selected for runtime)
> [DEBUG] jfreechart:jfreechart:jar:0.9.16 (selected for runtime)
> [DEBUG] com.solarmetric:kodo-jdo-runtime:jar:3.3.3 (selected for runtime)
> [DEBUG] javax.sql:jdbc-stdext:jar:2.0 (selected for runtime)
> [DEBUG] jline:jline:jar:0.9.1 (selected for runtime)
> [DEBUG] mx4j:mx4j-jmx:jar:1.1.1 (selected for runtime)
> [DEBUG] jta-spec:jta-spec:jar:1.0.1 (selected for runtime)
> [WARNING] While downloading xml-apis:xml-apis:2.0.0
> This artifact has been relocated to xml-apis:xml-apis:1.0.b2.
>
> [DEBUG] xml-apis:xml-apis:jar:1.0.b2 (selected for runtime)
> [DEBUG] xerces:xercesImpl:jar:2.5.0 (selected for runtime)
> [DEBUG] jca:jca:jar:1.0.0 (selected for runtime)
> [DEBUG] mx4j:mx4j-tools:jar:1.1.1 (selected for runtime)
> [DEBUG] jndi:jndi:jar:1.2.1 (selected for runtime)
> [DEBUG] Skipping disabled repository snapshots
> [DEBUG] log4j:log4j:jar:1.2.12 (setting version to: 1.2.12 from range:
> [1.2.9,])
> [DEBUG] log4j:log4j:jar:1.2.12 (selected for runtime)
> [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 (selected for runtime)
> [DEBUG] Configuring mojo
> 'org.codehaus.mojo:kodo-maven-plugin:1.0-alpha-1-SNAPSHOT:enhance' -->
> [DEBUG] (f) classDir =
> E:\STC\svn\modules\services\supplementaldata-jdo\trunk\target\classes
> [DEBUG] (f) resources = [EMAIL PROTECTED]
> [DEBUG] (f) searchDir =
> E:\STC\svn\modules\services\supplementaldata-jdo\trunk\target\classes
> [DEBUG] -- end configuration --
> [INFO] [kodo:enhance {execution: kodo-enhance}]
> [info] Found
> file:E:\STC\svn\modules\services\supplementaldata-jdo\trunk\target\classes\com\stchome\application\supplementalforms\persist\persist.jdo
> [info] [EMAIL PROTECTED]
> [debug] Added to Classpath:
> [debug]
> /E:/STC/svn/modules/services/supplementaldata-jdo/trunk/src/main/resources/
> [debug]
> /E:/STC/svn/modules/services/supplementaldata-jdo/trunk/target/classes/
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
> [INFO]
>
> [DEBUG] Trace
> javax.xml.parsers.FactoryConfigurationError: Provider
> org.apache.xerces.jaxp.SAXParserFactoryImpl not found
> at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:93)
> at serp.xml.XMLFactory.checkSAXCache(XMLFactory.java:217)
> at serp.xml.XMLFactory.getSAXParser(XMLFactory.java:66)
> at
> com.solarmetric.meta.XMLMetaDataParser.parseNew(XMLMetaDataParser.java:354)
> at com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:320)
> at
>
repository manager overview
Some folks seem interested, so I wanted to give a quick overview of the repository manager. It is an application that runs either standalone or as a webapp with the following functionality: - repository search - repository/artifact browsing and display of artifacts and their relationships - repository health reports (missing transitive dependencies, incorrect/missing checksums, incorrect/missing digital signatures, out of place artifacts, missing poms, etc) - maven-proxy like support - repository conversion It has the following modules: - discovery: walks a repository and finds all the artifacts in it so you can perform a certain action on each, or just the ones that are new/deleted since last walked. - indexer: used to add artifacts and metadata to the lucene index. Includes elements of the POM and checksums - converter: copy artifacts from one repository to the other, changing layout, converting metadata if required. - artifact-applet: applet to allow you to checksum a large artifact on your local machine and upload the checksum to the server to search - reports-standard: a bunch of reports on the status of an artifact in the repository - proxy: maven-proxy like functionality - utils: checksum, pathing, etc - webapp: webwork 2 and plexus based webapp for running it all Any questions? - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: graphing
I'll start a new thread "repository manager overview" Raphaël Piéroni wrote: > Brett, > can you explain me a bit of the repository manager ? > i have found the svn. > so i will try to create an in memory graph (and perhaps in the same time > a prolog fact base) > > In advance thanks for the answer. > > Raphaël > > Raphaël Piéroni a écrit : > >> That's why i do not have started yet. >> >> We should first sort the needs, then choose the appropriate language. >> >> Am i confused or the first thing to do is to create a in memory graph >> of the whole repository by crawling it ? >> after, i don't really see what to do. >> >> If we want to query a database with pre known queries, then we could >> use other than prolog, if the queries are to be known only after, then >> maybe, prolog is a good language. >> >> Raphaël >> >> >> Brett Porter a écrit : >> >>> That's an option, but I'd really prefer to look at other options first. >>> If you do something in prolog, how many other people are going to be >>> able to work with you on it? Is it something others are going to be able >>> to quickly understand and modify/improve? >>> >>> And I need to emphasise again that there is already some code around >>> that is trying to address this: the discovery and reports components of >>> the repository manager, and the graphing plugin at mojo.codehaus.org. >>> How do these relate to the tasks? >>> >>> I don't mean to discourage it - if you've got an itch, by all means >>> scratch it and we'll sort it out in the end. Just trying to give the >>> best chance of being able to reuse it later :) >>> >>> - Brett >>> >>> Piéroni Raphaël wrote: >>> >>> To overcome the license issue, maybe a tool which use a gpl prolog to the queries shown by Steve can be created at mojo.codehaus.org ? I don't remember the license policy. So whatever the means and the licences issues, are we agree about the task such a tool have to do (the needs expressed by Steve) ? In advance, thanks for any answer. Regards, Raphaël >>> >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >>> >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: graphing
Brett, can you explain me a bit of the repository manager ? i have found the svn. so i will try to create an in memory graph (and perhaps in the same time a prolog fact base) In advance thanks for the answer. Raphaël Raphaël Piéroni a écrit : That's why i do not have started yet. We should first sort the needs, then choose the appropriate language. Am i confused or the first thing to do is to create a in memory graph of the whole repository by crawling it ? after, i don't really see what to do. If we want to query a database with pre known queries, then we could use other than prolog, if the queries are to be known only after, then maybe, prolog is a good language. Raphaël Brett Porter a écrit : That's an option, but I'd really prefer to look at other options first. If you do something in prolog, how many other people are going to be able to work with you on it? Is it something others are going to be able to quickly understand and modify/improve? And I need to emphasise again that there is already some code around that is trying to address this: the discovery and reports components of the repository manager, and the graphing plugin at mojo.codehaus.org. How do these relate to the tasks? I don't mean to discourage it - if you've got an itch, by all means scratch it and we'll sort it out in the end. Just trying to give the best chance of being able to reuse it later :) - Brett Piéroni Raphaël wrote: To overcome the license issue, maybe a tool which use a gpl prolog to the queries shown by Steve can be created at mojo.codehaus.org ? I don't remember the license policy. So whatever the means and the licences issues, are we agree about the task such a tool have to do (the needs expressed by Steve) ? In advance, thanks for any answer. Regards, Raphaël - 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: graphing
That's why i do not have started yet. We should first sort the needs, then choose the appropriate language. Am i confused or the first thing to do is to create a in memory graph of the whole repository by crawling it ? after, i don't really see what to do. If we want to query a database with pre known queries, then we could use other than prolog, if the queries are to be known only after, then maybe, prolog is a good language. Raphaël Brett Porter a écrit : That's an option, but I'd really prefer to look at other options first. If you do something in prolog, how many other people are going to be able to work with you on it? Is it something others are going to be able to quickly understand and modify/improve? And I need to emphasise again that there is already some code around that is trying to address this: the discovery and reports components of the repository manager, and the graphing plugin at mojo.codehaus.org. How do these relate to the tasks? I don't mean to discourage it - if you've got an itch, by all means scratch it and we'll sort it out in the end. Just trying to give the best chance of being able to reuse it later :) - Brett Piéroni Raphaël wrote: To overcome the license issue, maybe a tool which use a gpl prolog to the queries shown by Steve can be created at mojo.codehaus.org ? I don't remember the license policy. So whatever the means and the licences issues, are we agree about the task such a tool have to do (the needs expressed by Steve) ? In advance, thanks for any answer. Regards, Raphaël - 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 trunk - SUCCESS - update] Wed Feb 8 22:00:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060208.22.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060208.22.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-2052) Transitive system deps are not interpolated correctly thus rendering them invalid
[ http://jira.codehaus.org/browse/MNG-2052?page=comments#action_58203 ]
Brett Porter commented on MNG-2052:
---
where is the property defined?
> Transitive system deps are not interpolated correctly thus rendering them
> invalid
> -
>
> Key: MNG-2052
> URL: http://jira.codehaus.org/browse/MNG-2052
> Project: Maven 2
> Type: Bug
> Components: POM, Artifacts and Repositories
> Environment: Windows XP, Java 1.5
> Reporter: Chris Stevenson
>
>
> When a library is loaded as a dependency if its dependencies contain one of
> type system which has a variable in the path the variable is not interpolated
> so that ${appHome}/lib/... is not an absolute path,
> rendering the dependency invalid.
> ex
> Lib A
> |-->Lib B
>|-->Lib C (System Dep, path=$appHome}/lib/jar)
> When resolving deps for lib B's pom will throw an error because path is not
> interpolated.
--
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: (MNG-2055) Error in Introduction to the Build Lifecycle
[ http://jira.codehaus.org/browse/MNG-2055?page=all ] Brett Porter closed MNG-2055: - Assign To: Brett Porter Resolution: Fixed > Error in Introduction to the Build Lifecycle > > > Key: MNG-2055 > URL: http://jira.codehaus.org/browse/MNG-2055 > Project: Maven 2 > Type: Bug > Components: Documentation: Introductions > Reporter: Prasad Kashyap > Assignee: Brett Porter > Priority: Minor > > > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > There is no phase called "before-integration-test". It should be replaced > with "pre-integration-test" -- 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: (MNG-1598) It should be possible not to include the META-INF/maven directory in produced jars
[ http://jira.codehaus.org/browse/MNG-1598?page=comments#action_58202 ] Brett Porter commented on MNG-1598: --- we don't release every time a single bug is fixed :) It will be included in the next release. > It should be possible not to include the META-INF/maven directory in produced > jars > -- > > Key: MNG-1598 > URL: http://jira.codehaus.org/browse/MNG-1598 > Project: Maven 2 > Type: Wish > Components: maven-archiver > Versions: 2.0 > Reporter: Julien S > Assignee: Emmanuel Venisse > Fix For: 2.0.1 > > > When packaging a jar, Maven includes several files (currently pom.xml and > pom.properties) in the META-INF directory. > Several people on the mailling list (including myself) indicated they wished > to be able to make this inclusion conditionnal. -- 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: (MNG-2055) Error in Introduction to the Build Lifecycle
[ http://jira.codehaus.org/browse/MNG-2055?page=comments#action_58201 ] Prasad Kashyap commented on MNG-2055: - I believe this has been fixed already here. maven-site\src\site\apt\guides\introduction\introduction-to-the-lifecycle.apt Maybe it has not yet been published to the site. But I'll let someone more knowledgeable to close this one out. Cheers Prasad > Error in Introduction to the Build Lifecycle > > > Key: MNG-2055 > URL: http://jira.codehaus.org/browse/MNG-2055 > Project: Maven 2 > Type: Bug > Components: Documentation: Introductions > Reporter: Prasad Kashyap > Priority: Minor > > > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > There is no phase called "before-integration-test". It should be replaced > with "pre-integration-test" -- 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]
graphing (was: critique of maven 2.0.2)
That's an option, but I'd really prefer to look at other options first. If you do something in prolog, how many other people are going to be able to work with you on it? Is it something others are going to be able to quickly understand and modify/improve? And I need to emphasise again that there is already some code around that is trying to address this: the discovery and reports components of the repository manager, and the graphing plugin at mojo.codehaus.org. How do these relate to the tasks? I don't mean to discourage it - if you've got an itch, by all means scratch it and we'll sort it out in the end. Just trying to give the best chance of being able to reuse it later :) - Brett Piéroni Raphaël wrote: > To overcome the license issue, > maybe a tool which use a gpl prolog to the queries shown by Steve can be > created at mojo.codehaus.org ? > > I don't remember the license policy. > > So whatever the means and the licences issues, are we agree about the task > such a tool have to do (the needs expressed by Steve) ? > > In advance, thanks for any answer. > > Regards, > > Raphaël > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPXDOC-185) maven.xdoc.date=navigation-top and navigation-bottom do not work
[ http://jira.codehaus.org/browse/MPXDOC-185?page=all ] Lukas Theussl closed MPXDOC-185: Resolution: Fixed > maven.xdoc.date=navigation-top and navigation-bottom do not work > > > Key: MPXDOC-185 > URL: http://jira.codehaus.org/browse/MPXDOC-185 > Project: maven-xdoc-plugin > Type: Bug > Environment: maven-1.1-beta2, xdoc-plugin-1.10-SNAPSHOT > Reporter: Lukas Theussl > Priority: Minor > Fix For: 1.10 > > -- 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: (MEV-328) HELP ! something wierd with resource in maven repo
[ http://jira.codehaus.org/browse/MEV-328?page=all ] Brett Porter closed MEV-328: Assign To: Brett Porter Resolution: Fixed > HELP ! something wierd with resource in maven repo > -- > > Key: MEV-328 > URL: http://jira.codehaus.org/browse/MEV-328 > Project: Maven Evangelism > Type: Bug > Reporter: Michael Neale > Assignee: Brett Porter > > > http://www.ibiblio.org/maven/jython/jars/jython-20020827-no-oro.jar is not > there, yet is is listed in > http://www.ibiblio.org/maven/jython/jars/ > and was there until recently. -- 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: (MEV-328) HELP ! something wierd with resource in maven repo
[ http://jira.codehaus.org/browse/MEV-328?page=all ] Brett Porter moved HAUS-1079 to MEV-328: Priority: (was: Major) Group ID: jython Artifact ID: jython Version: 20020827 Key: MEV-328 (was: HAUS-1079) Project: Maven Evangelism (was: Codehaus Chores) > HELP ! something wierd with resource in maven repo > -- > > Key: MEV-328 > URL: http://jira.codehaus.org/browse/MEV-328 > Project: Maven Evangelism > Type: Bug > Reporter: Michael Neale > > > http://www.ibiblio.org/maven/jython/jars/jython-20020827-no-oro.jar is not > there, yet is is listed in > http://www.ibiblio.org/maven/jython/jars/ > and was there until recently. -- 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-2055) Error in Introduction to the Build Lifecycle
Error in Introduction to the Build Lifecycle Key: MNG-2055 URL: http://jira.codehaus.org/browse/MNG-2055 Project: Maven 2 Type: Bug Components: Documentation: Introductions Reporter: Prasad Kashyap Priority: Minor http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html There is no phase called "before-integration-test". It should be replaced with "pre-integration-test" -- 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: jdk 1.4 and 1.5 in same install?
What about compiler and test plugins options like fork, executable, ... On 2/8/06, David Blevins <[EMAIL PROTECTED]> wrote: > So i find myself needing jdk 1.4 for 90% of what i have in the > geronimo continuum install, some of those actually can't compile with > 1.5 because of corba/vm ties. > > But alas I do need 1.5 now for at least two projects. > > Do i pretty much have to setup another continuum install for this? > > > -David > >
[jira] Commented: (MPJAVADOC-73) Javadoc Warnings report is empty, has parse exception
[ http://jira.codehaus.org/browse/MPJAVADOC-73?page=comments#action_58194 ] Jeff Jensen commented on MPJAVADOC-73: -- Arnaud, I think you nailed it! b3 successfully generates the Javadoc Warnings Report in my local environment. I have had b3 running our CruiseControl builds all day without problem, too. Our 5-hour nightly Maven site gen will run tonight, and I expect clean pages for all products. If not, I will let you know! Thanks to both of you for the fast response - very much appreciated. > Javadoc Warnings report is empty, has parse exception > - > > Key: MPJAVADOC-73 > URL: http://jira.codehaus.org/browse/MPJAVADOC-73 > Project: maven-javadoc-plugin > Type: Bug > Versions: 1.8 > Environment: Maven 1.1b2 > Plugin versions: javadoc 1.8, xdoc 1.9.2, site 1.6.1 > Win2K > Reporter: Jeff Jensen > Attachments: site_javadoc-warnings.xml, site_report.txt, > xdoc_javadoc-warnings.xml, xdoc_report.txt > > > The report is empty: states the number of files, number of errors=0, and an > empty Files section. > Running it with maven.javadoc.debug=true, the following info is in the log > (the first error message): > Read 276 line(s) from input file > Building map from 276 input line(s) > Parsing line [javadoc] > C:\devroot\perforce\healthmatchcommon\main\src\java\us\state\vantage\hm\ar\entity\AccountAWPContainer.java:66: > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in > us.state.vantage.hm.ar.entity.AccountAWPContainer > *** WARNING: exception parsing line ' [javadoc] > C:\devroot\perforce\healthmatchcommon\main\src\java\us\state\vantage\hm\ar\entity\AccountAWPContainer.java:66: > warning - Tag @see: can't find setAutomaticWithdrawalPlan. in > us.state.vantage.hm.ar.entity.AccountAWPContainer': > org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set; > java.lang.NoSuchMethodError: > org.apache.commons.collections.SetUtils.orderedSet(Ljava/util/Set;)Ljava/util/Set; > at > org.apache.maven.javadoc.JavadocWarningsTextToXml.buildMap(JavadocWarningsTextToXml.java:295) > This failure repeats many times, I think for every warning in the file. > But, if I run "maven javadoc xdoc" only, the file parses correctly and xdoc > creates a correct web page. -- 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]
jdk 1.4 and 1.5 in same install?
So i find myself needing jdk 1.4 for 90% of what i have in the geronimo continuum install, some of those actually can't compile with 1.5 because of corba/vm ties. But alas I do need 1.5 now for at least two projects. Do i pretty much have to setup another continuum install for this? -David
Re: Bringing plugins to Apache Maven
+1 for bringing and merging plugins. Vincent 2006/2/7, Brett Porter <[EMAIL PROTECTED]>: > This is not a vote. +1's here are just "I've read and think it's all > good", but generally I'm just looking for feedback on specific plugins > and decision points before taking this any further forward. > > Some of the plugins that wound up in mojo seem better suited to the main > Apache project due to a) originally coming from there b) having the core > libraries located there c) being essential to the day to day use of the > project. > > These are the ones I'm thinking of: > - jxr report (relates to jxr) > - surefire report (relates to surefire) > - changes/jira/announcement report (relates to issue stuff in sandbox) > - changelog report (relates to scm) > - dependency-maven-plugin (sounds generally handy in eliminating a lot > of small antrunning). > > The other ones I'm tossing up: > - taglist (generally useful report, originally came from m1) > > I put out a call for opinions and while the relevant mojo people were in > favour, some of the Maven developers were either on the fence or against > it. However, I didn't really receive an answer to my responses to those > concerns. > As a community we need to decide where we are going to develop > individual plugins. As I understand it, mojo.codehaus.org was > established to: > - develop things that can't be entirely under the ASL. > - avoid developing plugins that rotted and tied due to lack of community > in m1 > - give a place for individual plugin developers to start out but still > operate in the same way as the Maven community. > > It's always been my thought that plugins at maven.apache.org should be > those used by 80% of Maven users or essential to its operation, and > those that relate to the Maven subprojects themselves. Also, plugins in > like groups should be kept together. > > So, time to bring it here and get everyone's feedback again. If you > already had objections, please voice them again if they are still a concern. > > What do others think? Note that this would imply bringing in a couple of > new committers, but they are people that have been generally helpful. > > Cheers, > Brett > > - > 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] Updated: (MAVENUPLOAD-728) Upload backport-util-concurrent version 2.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-728?page=all ] Olivier Lamy updated MAVENUPLOAD-728: - Attachment: backport-util-concurrent-2.1-mev-upload.jar > Upload backport-util-concurrent version 2.1 > --- > > Key: MAVENUPLOAD-728 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-728 > Project: maven-upload-requests > Type: Bug > Reporter: Olivier Lamy > Attachments: backport-util-concurrent-2.1-mev-upload.jar, > backport-util-concurrent-2.1.jar, backport-util-concurrent-2.1.pom, pom.xml > > > Please upload last version (released one) of backport-util-concurrent > version . > Files included : > - backport-util-concurrent-2.1.pom > - backport-util-concurrent-2.1.jar -- 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: (MAVENUPLOAD-729) Sourceforge project 'dozer' to be uploaded.
Sourceforge project 'dozer' to be uploaded. --- Key: MAVENUPLOAD-729 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-729 Project: maven-upload-requests Type: Task Reporter: Franz Garsombke http://dozer.sourceforge.net/downloads/dozer-2.0.1-bundle.jar http://dozer.sourceforge.net http://dozer.sourceforge.net/team-list.html Dozer is a powerful, yet simple Java Bean to Java Bean mapper that recursively copies data from one object to another. Typically, these Java Beans will be of different complex types. -- 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: Build Failure on Windows
I'm preparing the build of a snapshot version after each commit, so you'll don't need to build trunk or branch. Emmanuel Stramel, Jay a écrit : The tests always fail when I try to build Continuum using the Build.bat batch file. I tried the build for the trunk and the 1.0.2 tag and both fail: [surefire] Running org.apache.maven.continuum.it.ShellIntegrationTest [surefire] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 6.011 sec FAILURE !! Is there some setup that I need to do in order to make this work? Jay Stramel | Senior Software Architect Intuit Eclipse 5340 Airport Boulevard Boulder, CO 80301 303.938.8801 Ext. 1152
Re: Build Failure on Windows
it doesn't require some setup. What is the error? trunk isn't stable! Emmanuel Stramel, Jay a écrit : The tests always fail when I try to build Continuum using the Build.bat batch file. I tried the build for the trunk and the 1.0.2 tag and both fail: [surefire] Running org.apache.maven.continuum.it.ShellIntegrationTest [surefire] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 6.011 sec FAILURE !! Is there some setup that I need to do in order to make this work? Jay Stramel | Senior Software Architect Intuit Eclipse 5340 Airport Boulevard Boulder, CO 80301 303.938.8801 Ext. 1152
[jira] Commented: (MAVENUPLOAD-728) Upload backport-util-concurrent version 2.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-728?page=comments#action_58185 ] Carlos Sanchez commented on MAVENUPLOAD-728: "you just need to make a JAR with the following format" means that you have to include those files in a jar pom.xml foo-1.0.jar (or whatever artifact is referred to in the pom.xml) foo-1.0-sources.jar (optional, jar containing java sources) > Upload backport-util-concurrent version 2.1 > --- > > Key: MAVENUPLOAD-728 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-728 > Project: maven-upload-requests > Type: Bug > Reporter: Olivier Lamy > Attachments: backport-util-concurrent-2.1.jar, > backport-util-concurrent-2.1.pom, pom.xml > > > Please upload last version (released one) of backport-util-concurrent > version . > Files included : > - backport-util-concurrent-2.1.pom > - backport-util-concurrent-2.1.jar -- 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]
Build Failure on Windows
The tests always fail when I try to build Continuum using the Build.bat batch file. I tried the build for the trunk and the 1.0.2 tag and both fail: [surefire] Running org.apache.maven.continuum.it.ShellIntegrationTest [surefire] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 6.011 sec FAILURE !! Is there some setup that I need to do in order to make this work? Jay Stramel | Senior Software Architect Intuit Eclipse 5340 Airport Boulevard Boulder, CO 80301 303.938.8801 Ext. 1152
[jira] Updated: (MNG-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)
[ http://jira.codehaus.org/browse/MNG-2054?page=all ]
Carlos Sanchez updated MNG-2054:
Priority: Critical (was: Major)
Fix Version: 2.0.3
> Multiple Inheritence causes plugin executions to run multiple times (Test
> Case Attached)
>
>
> Key: MNG-2054
> URL: http://jira.codehaus.org/browse/MNG-2054
> Project: Maven 2
> Type: Bug
> Components: Inheritence and Interpolation
> Versions: 2.0.2
> Environment: WinXp
> Reporter: Brian Fox
> Priority: Critical
> Fix For: 2.0.3
> Attachments: sample.zip
>
>
> See the attached sample. If a plugin execution is set in a parent of a
> parent, when the child is built from either aggregator, the plugin execution
> runs multiple times. In my sample, I set the sources to be generated, but
> when run, see that the sources are generated and installed 2x.
> [INFO] Building jar:
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
> [INFO] [install:install]
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT.jar to
> f:\mavenRepo\sampl
> e-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
> to f:\mavenRe
> po\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-sources.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
> to f:\mavenRe
> po\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-sources.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
> to f:\mavenRepo
> \sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-tests.jar
> [INFO]
> If run directly from the child build, the sources are only built 1x:
> [INFO] [jar:jar]
> [INFO] Building jar:
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT.jar
> [INFO] [source:jar {execution: attach-source}]
> [INFO] Building jar:
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
> [INFO] [jar:test-jar {execution: default}]
> [INFO] Building jar:
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
> [INFO] [install:install]
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT.jar to
> f:\mavenRepo\sampl
> e-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
> to f:\mavenRe
> po\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-sources.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
> to f:\mavenRepo
> \sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-tests.jar
--
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: (MAVENUPLOAD-728) Upload backport-util-concurrent version 2.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-728?page=all ] Olivier Lamy updated MAVENUPLOAD-728: - Attachment: pom.xml > Upload backport-util-concurrent version 2.1 > --- > > Key: MAVENUPLOAD-728 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-728 > Project: maven-upload-requests > Type: Bug > Reporter: Olivier Lamy > Attachments: backport-util-concurrent-2.1.jar, > backport-util-concurrent-2.1.pom, pom.xml > > > Please upload last version (released one) of backport-util-concurrent > version . > Files included : > - backport-util-concurrent-2.1.pom > - backport-util-concurrent-2.1.jar -- 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: (MNG-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)
[ http://jira.codehaus.org/browse/MNG-2054?page=comments#action_58178 ]
Brian Fox commented on MNG-2054:
Further investigation using help:effective-pom shows that the plugin
configuration actually gets included 2x in the pom. Shouldn't executions with
the same name be merged with their parent?
> Multiple Inheritence causes plugin executions to run multiple times (Test
> Case Attached)
>
>
> Key: MNG-2054
> URL: http://jira.codehaus.org/browse/MNG-2054
> Project: Maven 2
> Type: Bug
> Components: Inheritence and Interpolation
> Versions: 2.0.2
> Environment: WinXp
> Reporter: Brian Fox
> Attachments: sample.zip
>
>
> See the attached sample. If a plugin execution is set in a parent of a
> parent, when the child is built from either aggregator, the plugin execution
> runs multiple times. In my sample, I set the sources to be generated, but
> when run, see that the sources are generated and installed 2x.
> [INFO] Building jar:
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
> [INFO] [install:install]
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT.jar to
> f:\mavenRepo\sampl
> e-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
> to f:\mavenRe
> po\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-sources.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
> to f:\mavenRe
> po\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-sources.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
> to f:\mavenRepo
> \sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-tests.jar
> [INFO]
> If run directly from the child build, the sources are only built 1x:
> [INFO] [jar:jar]
> [INFO] Building jar:
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT.jar
> [INFO] [source:jar {execution: attach-source}]
> [INFO] Building jar:
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
> [INFO] [jar:test-jar {execution: default}]
> [INFO] Building jar:
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
> [INFO] [install:install]
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT.jar to
> f:\mavenRepo\sampl
> e-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
> to f:\mavenRe
> po\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-sources.jar
> [INFO] Installing
> E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
> to f:\mavenRepo
> \sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-tests.jar
--
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: (MSUREFIRE-59) JUnitBattery dies when TestSuite has an anonymous inner class
[ http://jira.codehaus.org/browse/MSUREFIRE-59?page=comments#action_58177 ]
Mike Perham commented on MSUREFIRE-59:
--
The outer class has the standard () and (String) JUnit constructors. The inner
class's code is posted right there. It's the FilenameFilter.
> JUnitBattery dies when TestSuite has an anonymous inner class
> -
>
> Key: MSUREFIRE-59
> URL: http://jira.codehaus.org/browse/MSUREFIRE-59
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Versions: 2.1.2
> Reporter: Mike Perham
> Fix For: 2.1.3
>
>
> I have this method in my test suite:
> {code}
> private static File[] getWSDLFiles() {
> URL directoryURL =
> WSDLImportTestSuite.class.getResource("/com/webify/wsf/studio/core/wsdl/wsdls");
> if (directoryURL != null) {
> File directory = new File(directoryURL.getPath());
> FilenameFilter filter = new FilenameFilter() {
> public boolean accept(File dir, String name) {
> return name.endsWith(".wsdl");
> }
> };
> return directory.listFiles(filter);
> }
> else {
> return null;
> }
> }
> {code}
> And surefire fails with this exception:
> java.lang.NoSuchMethodException:
> com.webify.wsf.studio.core.wsdl.WSDLImportTestSuite$1.()
> at java.lang.Class.getConstructor0(Class.java:1937)
> at java.lang.Class.getConstructor(Class.java:1027)
> at
> org.apache.maven.surefire.battery.JUnitBattery.getTestConstructor(JUnitBattery.java:307)
> at
> org.apache.maven.surefire.battery.JUnitBattery.processTestClass(JUnitBattery.java:150)
> at
> org.apache.maven.surefire.battery.JUnitBattery.(JUnitBattery.java:81)
> at
> org.apache.maven.surefire.SurefireUtils.instantiateBattery(SurefireUtils.java:63)
> at
> org.apache.maven.surefire.Surefire.instantiateBatteries(Surefire.java:262)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:140)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
--
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-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)
Multiple Inheritence causes plugin executions to run multiple times (Test Case
Attached)
Key: MNG-2054
URL: http://jira.codehaus.org/browse/MNG-2054
Project: Maven 2
Type: Bug
Components: Inheritence and Interpolation
Versions: 2.0.2
Environment: WinXp
Reporter: Brian Fox
Attachments: sample.zip
See the attached sample. If a plugin execution is set in a parent of a parent,
when the child is built from either aggregator, the plugin execution runs
multiple times. In my sample, I set the sources to be generated, but when run,
see that the sources are generated and installed 2x.
[INFO] Building jar:
E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
[INFO] [install:install]
[INFO] Installing
E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT.jar to
f:\mavenRepo\sampl
e-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT.jar
[INFO] Installing
E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
to f:\mavenRe
po\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-sources.jar
[INFO] Installing
E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
to f:\mavenRe
po\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-sources.jar
[INFO] Installing
E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar to
f:\mavenRepo
\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-tests.jar
[INFO]
If run directly from the child build, the sources are only built 1x:
[INFO] [jar:jar]
[INFO] Building jar:
E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT.jar
[INFO] [source:jar {execution: attach-source}]
[INFO] Building jar:
E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
[INFO] [jar:test-jar {execution: default}]
[INFO] Building jar:
E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar
[INFO] [install:install]
[INFO] Installing
E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT.jar to
f:\mavenRepo\sampl
e-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT.jar
[INFO] Installing
E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-sources.jar
to f:\mavenRe
po\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-sources.jar
[INFO] Installing
E:\STC\sample\sample-parent2\sample-jar\target\sample-jar-SNAPSHOT-tests.jar to
f:\mavenRepo
\sample-project\sample-jar\SNAPSHOT\sample-jar-SNAPSHOT-tests.jar
--
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: (MEV-323) Invalid hibernate dependency in hibernate-tools-3.1.0.beta4 pom
[ http://jira.codehaus.org/browse/MEV-323?page=all ] Carlos Sanchez closed MEV-323: -- Assign To: Carlos Sanchez Resolution: Fixed > Invalid hibernate dependency in hibernate-tools-3.1.0.beta4 pom > --- > > Key: MEV-323 > URL: http://jira.codehaus.org/browse/MEV-323 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Johann Reyes > Assignee: Carlos Sanchez > Attachments: hibernate-tools-3.1.0.beta4.pom > > > hibernate-tools-3.1.0.beta4 needs hibernate 3.1.2 instead of hibernate-3.1 > when is used along with hibernate-annotations. Hibernate-3.1.2 introduces a > new class that is missing from the 3.1 release -- 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: (MSUREFIRE-59) JUnitBattery dies when TestSuite has an anonymous inner class
[ http://jira.codehaus.org/browse/MSUREFIRE-59?page=comments#action_58175 ]
Carlos Sanchez commented on MSUREFIRE-59:
-
it's complaining about the constructor, can you paste the constructors you have?
> JUnitBattery dies when TestSuite has an anonymous inner class
> -
>
> Key: MSUREFIRE-59
> URL: http://jira.codehaus.org/browse/MSUREFIRE-59
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Versions: 2.1.2
> Reporter: Mike Perham
> Fix For: 2.1.3
>
>
> I have this method in my test suite:
> {code}
> private static File[] getWSDLFiles() {
> URL directoryURL =
> WSDLImportTestSuite.class.getResource("/com/webify/wsf/studio/core/wsdl/wsdls");
> if (directoryURL != null) {
> File directory = new File(directoryURL.getPath());
> FilenameFilter filter = new FilenameFilter() {
> public boolean accept(File dir, String name) {
> return name.endsWith(".wsdl");
> }
> };
> return directory.listFiles(filter);
> }
> else {
> return null;
> }
> }
> {code}
> And surefire fails with this exception:
> java.lang.NoSuchMethodException:
> com.webify.wsf.studio.core.wsdl.WSDLImportTestSuite$1.()
> at java.lang.Class.getConstructor0(Class.java:1937)
> at java.lang.Class.getConstructor(Class.java:1027)
> at
> org.apache.maven.surefire.battery.JUnitBattery.getTestConstructor(JUnitBattery.java:307)
> at
> org.apache.maven.surefire.battery.JUnitBattery.processTestClass(JUnitBattery.java:150)
> at
> org.apache.maven.surefire.battery.JUnitBattery.(JUnitBattery.java:81)
> at
> org.apache.maven.surefire.SurefireUtils.instantiateBattery(SurefireUtils.java:63)
> at
> org.apache.maven.surefire.Surefire.instantiateBatteries(Surefire.java:262)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:140)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
--
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: (MSUREFIRE-59) JUnitBattery dies when TestSuite has an anonymous inner class
[ http://jira.codehaus.org/browse/MSUREFIRE-59?page=all ]
Carlos Sanchez updated MSUREFIRE-59:
Fix Version: 2.1.3
> JUnitBattery dies when TestSuite has an anonymous inner class
> -
>
> Key: MSUREFIRE-59
> URL: http://jira.codehaus.org/browse/MSUREFIRE-59
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Versions: 2.1.2
> Reporter: Mike Perham
> Fix For: 2.1.3
>
>
> I have this method in my test suite:
> {code}
> private static File[] getWSDLFiles() {
> URL directoryURL =
> WSDLImportTestSuite.class.getResource("/com/webify/wsf/studio/core/wsdl/wsdls");
> if (directoryURL != null) {
> File directory = new File(directoryURL.getPath());
> FilenameFilter filter = new FilenameFilter() {
> public boolean accept(File dir, String name) {
> return name.endsWith(".wsdl");
> }
> };
> return directory.listFiles(filter);
> }
> else {
> return null;
> }
> }
> {code}
> And surefire fails with this exception:
> java.lang.NoSuchMethodException:
> com.webify.wsf.studio.core.wsdl.WSDLImportTestSuite$1.()
> at java.lang.Class.getConstructor0(Class.java:1937)
> at java.lang.Class.getConstructor(Class.java:1027)
> at
> org.apache.maven.surefire.battery.JUnitBattery.getTestConstructor(JUnitBattery.java:307)
> at
> org.apache.maven.surefire.battery.JUnitBattery.processTestClass(JUnitBattery.java:150)
> at
> org.apache.maven.surefire.battery.JUnitBattery.(JUnitBattery.java:81)
> at
> org.apache.maven.surefire.SurefireUtils.instantiateBattery(SurefireUtils.java:63)
> at
> org.apache.maven.surefire.Surefire.instantiateBatteries(Surefire.java:262)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:140)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
--
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: (MEV-303) POM for Tapestry 4.0
[ http://jira.codehaus.org/browse/MEV-303?page=all ] Carlos Sanchez closed MEV-303: -- Resolution: Fixed Don't know what happened. I've increased logging level in case this happens again > POM for Tapestry 4.0 > > > Key: MEV-303 > URL: http://jira.codehaus.org/browse/MEV-303 > Project: Maven Evangelism > Type: Task > Reporter: Howard M. Lewis Ship > Assignee: Carlos Sanchez > > > Tapestry 4.1 will build with Maven 2, in the meantime, here's the proper POM > for Tapestry 4.0. -- 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: (MSUREFIRE-59) JUnitBattery dies when TestSuite has an anonymous inner class
[ http://jira.codehaus.org/browse/MSUREFIRE-59?page=comments#action_58172 ]
Mike Perham commented on MSUREFIRE-59:
--
This works in 2.0 but fails when we upgrade to 2.1.2.
> JUnitBattery dies when TestSuite has an anonymous inner class
> -
>
> Key: MSUREFIRE-59
> URL: http://jira.codehaus.org/browse/MSUREFIRE-59
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Versions: 2.1.2
> Reporter: Mike Perham
>
>
> I have this method in my test suite:
> {code}
> private static File[] getWSDLFiles() {
> URL directoryURL =
> WSDLImportTestSuite.class.getResource("/com/webify/wsf/studio/core/wsdl/wsdls");
> if (directoryURL != null) {
> File directory = new File(directoryURL.getPath());
> FilenameFilter filter = new FilenameFilter() {
> public boolean accept(File dir, String name) {
> return name.endsWith(".wsdl");
> }
> };
> return directory.listFiles(filter);
> }
> else {
> return null;
> }
> }
> {code}
> And surefire fails with this exception:
> java.lang.NoSuchMethodException:
> com.webify.wsf.studio.core.wsdl.WSDLImportTestSuite$1.()
> at java.lang.Class.getConstructor0(Class.java:1937)
> at java.lang.Class.getConstructor(Class.java:1027)
> at
> org.apache.maven.surefire.battery.JUnitBattery.getTestConstructor(JUnitBattery.java:307)
> at
> org.apache.maven.surefire.battery.JUnitBattery.processTestClass(JUnitBattery.java:150)
> at
> org.apache.maven.surefire.battery.JUnitBattery.(JUnitBattery.java:81)
> at
> org.apache.maven.surefire.SurefireUtils.instantiateBattery(SurefireUtils.java:63)
> at
> org.apache.maven.surefire.Surefire.instantiateBatteries(Surefire.java:262)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:140)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
--
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: (MSUREFIRE-59) JUnitBattery dies when TestSuite has an anonymous inner class
[ http://jira.codehaus.org/browse/MSUREFIRE-59?page=all ]
Mike Perham updated MSUREFIRE-59:
-
Description:
I have this method in my test suite:
{code}
private static File[] getWSDLFiles() {
URL directoryURL =
WSDLImportTestSuite.class.getResource("/com/webify/wsf/studio/core/wsdl/wsdls");
if (directoryURL != null) {
File directory = new File(directoryURL.getPath());
FilenameFilter filter = new FilenameFilter() {
public boolean accept(File dir, String name) {
return name.endsWith(".wsdl");
}
};
return directory.listFiles(filter);
}
else {
return null;
}
}
{code}
And surefire fails with this exception:
java.lang.NoSuchMethodException:
com.webify.wsf.studio.core.wsdl.WSDLImportTestSuite$1.()
at java.lang.Class.getConstructor0(Class.java:1937)
at java.lang.Class.getConstructor(Class.java:1027)
at
org.apache.maven.surefire.battery.JUnitBattery.getTestConstructor(JUnitBattery.java:307)
at
org.apache.maven.surefire.battery.JUnitBattery.processTestClass(JUnitBattery.java:150)
at
org.apache.maven.surefire.battery.JUnitBattery.(JUnitBattery.java:81)
at
org.apache.maven.surefire.SurefireUtils.instantiateBattery(SurefireUtils.java:63)
at
org.apache.maven.surefire.Surefire.instantiateBatteries(Surefire.java:262)
at org.apache.maven.surefire.Surefire.run(Surefire.java:140)
at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
was:
I have this method in my test suite:
private static File[] getWSDLFiles() {
URL directoryURL =
WSDLImportTestSuite.class.getResource("/com/webify/wsf/studio/core/wsdl/wsdls");
if (directoryURL != null) {
File directory = new File(directoryURL.getPath());
FilenameFilter filter = new FilenameFilter() {
public boolean accept(File dir, String name) {
return name.endsWith(".wsdl");
}
};
return directory.listFiles(filter);
}
else {
return null;
}
}
And surefire fails with this exception:
java.lang.NoSuchMethodException:
com.webify.wsf.studio.core.wsdl.WSDLImportTestSuite$1.()
at java.lang.Class.getConstructor0(Class.java:1937)
at java.lang.Class.getConstructor(Class.java:1027)
at
org.apache.maven.surefire.battery.JUnitBattery.getTestConstructor(JUnitBattery.java:307)
at
org.apache.maven.surefire.battery.JUnitBattery.processTestClass(JUnitBattery.java:150)
at
org.apache.maven.surefire.battery.JUnitBattery.(JUnitBattery.java:81)
at
org.apache.maven.surefire.SurefireUtils.instantiateBattery(SurefireUtils.java:63)
at
org.apache.maven.surefire.Surefire.instantiateBatteries(Surefire.java:262)
at org.apache.maven.surefire.Surefire.run(Surefire.java:140)
at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
> JUnitBattery dies when TestSuite has an anonymous inner class
> -
>
> Key: MSUREFIRE-59
> URL: http://jira.codehaus.org/browse/MSUREFIRE-59
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Versions: 2.1.2
> Reporter: Mike Perham
>
>
> I have this method in my test suite:
> {code}
> private static File[] getWSDLFiles() {
> URL directoryURL =
> WSDLImportTestSuite.class.getResource("/com/webify/wsf/studio/core/wsdl/wsdls");
> if (directoryURL != null) {
> File directory = new File(directoryURL.getPath());
> FilenameFilter filter = new FilenameFilter() {
> public boolean accept(File dir, String name) {
> return name.endsWith(".wsdl");
> }
> };
> return directory.listFiles(filter);
> }
> else {
> return null;
> }
> }
> {code}
> And surefire fails with this exception:
> java.lang.NoSuchMethodException:
> com.webify.wsf.studio.core.wsdl.WSDLImportTestSuite$1.()
> at java.lang.Class.getConstructor0(Class.java:1937)
> at java.lang.Class.getConstructor(Class.java:1027)
> at
> org.apache.maven.surefire.battery.JUnitBattery.getTestConstructor(JUnitBattery.java:307)
> at
> org.apache.maven.surefire.battery.JUnitBattery.processTestClass(JUnitBattery.java:150)
> at
> org.apache.maven.surefire.battery.JUnitBattery.(JUnitBattery.java:81)
> at
> org.apache.maven.surefire.SurefireUtils.instantiateBattery(SurefireUtils.java:63)
> at
> org.apache.maven.surefire.Surefire.instantiateBatteries(Surefire.java:262)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:140)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
--
This messag
[jira] Created: (MSUREFIRE-59) JUnitBattery dies when TestSuite has an anonymous inner class
JUnitBattery dies when TestSuite has an anonymous inner class
-
Key: MSUREFIRE-59
URL: http://jira.codehaus.org/browse/MSUREFIRE-59
Project: Maven 2.x Surefire Plugin
Type: Bug
Versions: 2.1.2
Reporter: Mike Perham
I have this method in my test suite:
private static File[] getWSDLFiles() {
URL directoryURL =
WSDLImportTestSuite.class.getResource("/com/webify/wsf/studio/core/wsdl/wsdls");
if (directoryURL != null) {
File directory = new File(directoryURL.getPath());
FilenameFilter filter = new FilenameFilter() {
public boolean accept(File dir, String name) {
return name.endsWith(".wsdl");
}
};
return directory.listFiles(filter);
}
else {
return null;
}
}
And surefire fails with this exception:
java.lang.NoSuchMethodException:
com.webify.wsf.studio.core.wsdl.WSDLImportTestSuite$1.()
at java.lang.Class.getConstructor0(Class.java:1937)
at java.lang.Class.getConstructor(Class.java:1027)
at
org.apache.maven.surefire.battery.JUnitBattery.getTestConstructor(JUnitBattery.java:307)
at
org.apache.maven.surefire.battery.JUnitBattery.processTestClass(JUnitBattery.java:150)
at
org.apache.maven.surefire.battery.JUnitBattery.(JUnitBattery.java:81)
at
org.apache.maven.surefire.SurefireUtils.instantiateBattery(SurefireUtils.java:63)
at
org.apache.maven.surefire.Surefire.instantiateBatteries(Surefire.java:262)
at org.apache.maven.surefire.Surefire.run(Surefire.java:140)
at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
--
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: (MAVENUPLOAD-728) Upload backport-util-concurrent version 2.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-728?page=comments#action_58171 ] Carlos Sanchez commented on MAVENUPLOAD-728: Please read http://maven.apache.org/guides/mini/guide-ibiblio-upload.html > Upload backport-util-concurrent version 2.1 > --- > > Key: MAVENUPLOAD-728 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-728 > Project: maven-upload-requests > Type: Bug > Reporter: Olivier Lamy > Attachments: backport-util-concurrent-2.1.jar, > backport-util-concurrent-2.1.pom > > > Please upload last version (released one) of backport-util-concurrent > version . > Files included : > - backport-util-concurrent-2.1.pom > - backport-util-concurrent-2.1.jar -- 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-326) Spring 2.0 M2 is missing a POM
[ http://jira.codehaus.org/browse/MEV-326?page=all ] Carlos Sanchez updated MEV-326: --- Attachment: pom.xml > Spring 2.0 M2 is missing a POM > -- > > Key: MEV-326 > URL: http://jira.codehaus.org/browse/MEV-326 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Matt Raible > Attachments: pom.xml > > > http://www.ibiblio.org/maven2/org/springframework/spring/2.0-m2/ > The one for 2.0-m1 seems to be correct. -- 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: (MEV-326) Spring 2.0 M2 is missing a POM
[ http://jira.codehaus.org/browse/MEV-326?page=comments#action_58169 ] Carlos Sanchez commented on MEV-326: No, it's not, lot of changes from m1 to m2 http://cvs.sourceforge.net/viewcvs.py/springframework/spring/lib/readme.txt?r1=1.85&r2=1.94 Very busy this week, i'll upload my m1 pom to see if somebody can help > Spring 2.0 M2 is missing a POM > -- > > Key: MEV-326 > URL: http://jira.codehaus.org/browse/MEV-326 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Matt Raible > Attachments: pom.xml > > > http://www.ibiblio.org/maven2/org/springframework/spring/2.0-m2/ > The one for 2.0-m1 seems to be correct. -- 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: (MAVENUPLOAD-728) Upload backport-util-concurrent version 2.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-728?page=all ] Carlos Sanchez moved MEV-327 to MAVENUPLOAD-728: Group ID: (was: backport-util-concurrent) Bundle URL: ? Artifact ID: (was: backport-util-concurrent) Version: (was: 2.1) Key: MAVENUPLOAD-728 (was: MEV-327) Project: maven-upload-requests (was: Maven Evangelism) > Upload backport-util-concurrent version 2.1 > --- > > Key: MAVENUPLOAD-728 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-728 > Project: maven-upload-requests > Type: Bug > Reporter: Olivier Lamy > Attachments: backport-util-concurrent-2.1.jar, > backport-util-concurrent-2.1.pom > > > Please upload last version (released one) of backport-util-concurrent > version . > Files included : > - backport-util-concurrent-2.1.pom > - backport-util-concurrent-2.1.jar -- 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: (MNGECLIPSE-22) The Plug-In fails to run under Eclipse 3.0.x and IBM Rational Developer (RAD)
[ http://jira.codehaus.org/browse/MNGECLIPSE-22?page=comments#action_58168 ] Eugene Kuleshov commented on MNGECLIPSE-22: --- Rik, shanges include some SWT incompatibilities as well as entirely new API for the launch configurations. If you wan't to know more details you can email me eu at javatx dot org. > The Plug-In fails to run under Eclipse 3.0.x and IBM Rational Developer (RAD) > - > > Key: MNGECLIPSE-22 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-22 > Project: Maven 2.x Extension for Eclipse > Type: Improvement > Versions: 0.0.3 > Environment: Windows XP, IBM Rational Developer (RAD) 6.0.x > Reporter: Cyrill Ruettimann > Assignee: Dmitri Maximovich > Priority: Minor > Fix For: 1.0.0 > Attachments: eclipse30_build_errors.JPG, eclipse30_build_errors.txt > > > The Plug-In fails to run under Eclipse 3.0: > !ENTRY org.eclipse.ui 4 0 Jan 03, 2006 08:32:07.968 > !MESSAGE org/eclipse/swt/layout/GridData.verticalIndent > !STACK 0 > java.lang.NoSuchFieldError: org/eclipse/swt/layout/GridData.verticalIndent > at > org.maven.ide.eclipse.wizards.Maven2PomWizardPage.createControl(Maven2PomWizardPage.java:101) > at org.eclipse.jface.wizard.Wizard.createPageControls(Unknown Source) > at org.eclipse.jface.wizard.WizardDialog.createPageControls(Unknown > Source) > at org.eclipse.jface.wizard.WizardDialog.createContents(Unknown Source) > at org.eclipse.jface.window.Window.create(Unknown Source) > at org.eclipse.jface.dialogs.Dialog.create(Unknown Source) > at > org.maven.ide.eclipse.actions.ToggleNatureAction.toggleNature(ToggleNatureAction.java:108) > at > org.maven.ide.eclipse.actions.ToggleNatureAction.run(ToggleNatureAction.java:51) > at org.eclipse.ui.internal.PluginAction.runWithEvent(Unknown Source) > at > org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Unknown > Source) > at org.eclipse.jface.action.ActionContributionItem.access$2(Unknown > Source) > at > org.eclipse.jface.action.ActionContributionItem$7.handleEvent(Unknown Source) > at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source) > at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source) > at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source) > at org.eclipse.ui.internal.Workbench.runUI(Unknown Source) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown > Source) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source) > at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source) > at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown > Source) > at > org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273) > at > org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) > at java.lang.reflect.Method.invoke(Method.java:391) > at org.eclipse.core.launcher.Main.basicRun(Main.java:185) > at org.eclipse.core.launcher.Main.run(Main.java:704) > at org.eclipse.core.launcher.Main.main(Main.java:688) -- 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: (MNGECLIPSE-22) The Plug-In fails to run under Eclipse 3.0.x and IBM Rational Developer (RAD)
[ http://jira.codehaus.org/browse/MNGECLIPSE-22?page=comments#action_58167 ] Rik Bosman commented on MNGECLIPSE-22: -- My company is moving t oRSA (which is a subset of RAD) in a couple of months. Eclipse 3.0 based How much work would it cost to make the plugin available for Eclipse 3.0, e.g. what has changed between these versions that is of such important use for the maven2 plugin? > The Plug-In fails to run under Eclipse 3.0.x and IBM Rational Developer (RAD) > - > > Key: MNGECLIPSE-22 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-22 > Project: Maven 2.x Extension for Eclipse > Type: Improvement > Versions: 0.0.3 > Environment: Windows XP, IBM Rational Developer (RAD) 6.0.x > Reporter: Cyrill Ruettimann > Assignee: Dmitri Maximovich > Priority: Minor > Fix For: 1.0.0 > Attachments: eclipse30_build_errors.JPG, eclipse30_build_errors.txt > > > The Plug-In fails to run under Eclipse 3.0: > !ENTRY org.eclipse.ui 4 0 Jan 03, 2006 08:32:07.968 > !MESSAGE org/eclipse/swt/layout/GridData.verticalIndent > !STACK 0 > java.lang.NoSuchFieldError: org/eclipse/swt/layout/GridData.verticalIndent > at > org.maven.ide.eclipse.wizards.Maven2PomWizardPage.createControl(Maven2PomWizardPage.java:101) > at org.eclipse.jface.wizard.Wizard.createPageControls(Unknown Source) > at org.eclipse.jface.wizard.WizardDialog.createPageControls(Unknown > Source) > at org.eclipse.jface.wizard.WizardDialog.createContents(Unknown Source) > at org.eclipse.jface.window.Window.create(Unknown Source) > at org.eclipse.jface.dialogs.Dialog.create(Unknown Source) > at > org.maven.ide.eclipse.actions.ToggleNatureAction.toggleNature(ToggleNatureAction.java:108) > at > org.maven.ide.eclipse.actions.ToggleNatureAction.run(ToggleNatureAction.java:51) > at org.eclipse.ui.internal.PluginAction.runWithEvent(Unknown Source) > at > org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Unknown > Source) > at org.eclipse.jface.action.ActionContributionItem.access$2(Unknown > Source) > at > org.eclipse.jface.action.ActionContributionItem$7.handleEvent(Unknown Source) > at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source) > at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source) > at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source) > at org.eclipse.ui.internal.Workbench.runUI(Unknown Source) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown > Source) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source) > at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source) > at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown > Source) > at > org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273) > at > org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) > at java.lang.reflect.Method.invoke(Method.java:391) > at org.eclipse.core.launcher.Main.basicRun(Main.java:185) > at org.eclipse.core.launcher.Main.run(Main.java:704) > at org.eclipse.core.launcher.Main.main(Main.java:688) -- 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: (MPSCM-67) scm:prepare-release fails because project.xml has been locally modified
[ http://jira.codehaus.org/browse/MPSCM-67?page=comments#action_58164 ] Lukas Theussl commented on MPSCM-67: Dennis, I think with the fix for MPSCM-77 you should have a workaround for your problem (it allows you to remove the backup files by hand before committing and tagging). I'd like to release scm-plugin-1.6, so I will schedule this issue for a later release, is that ok? > 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 > Assignee: Lukas Theussl > Fix For: 1.6 > 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] Closed: (MPSCM-77) It should be possible to check changes made by prepare-release before they are checked in and tagged
[ http://jira.codehaus.org/browse/MPSCM-77?page=all ] Lukas Theussl closed MPSCM-77: -- Resolution: Fixed I finally opted for a new property maven.scm.testmode (default: false) which was easier to implement (otherwise we would have had to check whether the same tag and version were used in different goals). It's also more similar to the m2 behavior. > It should be possible to check changes made by prepare-release before they > are checked in and tagged > > > Key: MPSCM-77 > URL: http://jira.codehaus.org/browse/MPSCM-77 > Project: maven-scm-plugin > Type: Improvement > Environment: m11b3, scm plugin > Reporter: Lukas Theussl > Priority: Critical > Fix For: 1.6 > > > See MRELEASE-77 for the equivalent m2 problem. > Currently, the scm:prepare-release goal modifies the files project.xml and > changes.xml, then commits the changes and tags the entire source tree, all in > one step. If there is a problem with updating the files, we have a faulty > version checked in and tagged in the repository. And usually, there are > problems (see MPSCM-1, MPSCM-12, MPSCM-43, MPSCM-67, ...?). > Given this immature state of the plugin, I think it is necessary that we > provide the possibility to undo any unwanted modifications before anything > gets checked in and tagged. I'm just not sure about the best way to do that: > - move the check-in and tagging into the scm:perform-release goal, so prepare > release only updates project.xml and changes.xml > - add a new goal for updating project.xml and changes.xml > - add a property 'testmode' like in m2, that skips the check-in and tagging > (not sure how that would help when there are problems though) > I'd prefer the second choice, what do others think? -- 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: critique of maven 2.0.2
To overcome the license issue, maybe a tool which use a gpl prolog to the queries shown by Steve can be created at mojo.codehaus.org ? I don't remember the license policy. So whatever the means and the licences issues, are we agree about the task such a tool have to do (the needs expressed by Steve) ? In advance, thanks for any answer. Regards, Raphaël 2006/2/8, Piéroni Raphaël <[EMAIL PROTECTED]>: > > > > 2006/2/8, Steve Loughran <[EMAIL PROTECTED]>: > > > > Piéroni Raphaël wrote: > > > 2006/2/8, Steve Loughran <[EMAIL PROTECTED]>: > > >> Piéroni Raphaël wrote: > > >>> I don't know if it is the right tool. i jumped on Steve proposition > > as i > > >> was > > >>> found of prolog during my school years. > > >>> > > >> I don't know if it is right either. One good reason for not using it, > > >> but for sticking in java, is ease of integration with the existing > > maven > > >> codebase; nobody could add anything that depended on GPL code to the > > >> repository, even LGPL is a bit sensitive. > > > > > > > > > I do not understand this license issue. > > > is it because Jlog is GPL that its artifact and pom are not in ibiblio > > ? > > > > no, it should be on ibiblio if it is popular. Lots of GPL things are > > (like the mysql jdbc driver, bits of JBoss, etc) > > > > > is it because Jlog is GPL that we could not import class of jlog into > > maven > > > code ? > > > > yes > > > So we can't use Jlog i checked the amine-platform (another prolog) : it is > LGPL. does LGPL also not usable in maven ? > if yes, the prolog approach is not the correct one as i don't know any > other open source prolog library. > > Regards, > > Raphaël > >
Re: critique of maven 2.0.2
2006/2/8, Steve Loughran <[EMAIL PROTECTED]>: > > Piéroni Raphaël wrote: > > 2006/2/8, Steve Loughran <[EMAIL PROTECTED]>: > >> Piéroni Raphaël wrote: > >>> I don't know if it is the right tool. i jumped on Steve proposition as > i > >> was > >>> found of prolog during my school years. > >>> > >> I don't know if it is right either. One good reason for not using it, > >> but for sticking in java, is ease of integration with the existing > maven > >> codebase; nobody could add anything that depended on GPL code to the > >> repository, even LGPL is a bit sensitive. > > > > > > I do not understand this license issue. > > is it because Jlog is GPL that its artifact and pom are not in ibiblio ? > > no, it should be on ibiblio if it is popular. Lots of GPL things are > (like the mysql jdbc driver, bits of JBoss, etc) > > > is it because Jlog is GPL that we could not import class of jlog into > maven > > code ? > > yes So we can't use Jlog i checked the amine-platform (another prolog) : it is LGPL. does LGPL also not usable in maven ? if yes, the prolog approach is not the correct one as i don't know any other open source prolog library. Regards, Raphaël
[maven2 build trunk - SUCCESS - update] Wed Feb 8 16:00:00 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/trunk/m2-20060208.160001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060208.160001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-727) Please add Hibernate 3.1.2 sources
Please add Hibernate 3.1.2 sources -- Key: MAVENUPLOAD-727 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-727 Project: maven-upload-requests Type: Task Reporter: Nicolás Lichtmaier Please, add this sources jar (http://www.modhelus.com/x/hibernate-3.1.2-sources.jar) to the Hibernate 3.1.2 directory. Many thanks! -- 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] Wed Feb 8 15:15:01 GMT 2006
Distribution: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060208.151502.tar.gz Log: http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060208.151502.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MECLIPSE-67) subprojects not included when the root pom has packaging pom
subprojects not included when the root pom has packaging pom Key: MECLIPSE-67 URL: http://jira.codehaus.org/browse/MECLIPSE-67 Project: Maven 2.x Eclipse Plugin Type: Bug Versions: 2.1 Environment: all Reporter: Olivier Lamy Priority: Blocker I have the following structure : root-directory : pom.xml (root one which declares modules) - module model (pom.xml) - module services (pom.xml which depends on model) - module dao (pom.xml which depends on model) - .. - module responder (pom.xml which depends on model , dao and other modules) When i use mvn eclipse:eclipse in the directory containing the root pom. My services eclipse project doesn't contains a reference to the other eclipse project model but to the jar in my local repository. I can do it manually but automatic could be great. Do I have a particular setting to do in my eclipse plugin or I misunderstood something ? Thanks, - Olivier -- 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: a little more on site structure
Why are these permanent? Developers come and go. Projects migrate locations and SCM systems change occasionally. These reports don't change as frequently but they still do change. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 07, 2006 11:10 PM To: Maven Developers List Subject: a little more on site structure c) is there a way to designate informational, permanent reports (mailing list, scm, plugin reference) from point in time reports (junit, cobertura, even javadoc)? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
design docs for repositories?
Hi, we at the Scala group (scala.epfl.ch) are looking at community infrastructure to share artifacts around. Joel Trunick pointed me towards Maven. Maven is interesting for us to begin with as simply an improved ant for building software. More specifically, though, its support for remote repositories and for inter-package dependencies is intriguing, because we've made a special effort to try and support Scala enthusiasts sharing the things they make with each other. Our running approach in "Scala Bazaars" is to use something based on Linux distributions called "package universes".I am wondering if we should adopt Maven's approach instead, or if our approach has something Maven would find useful, or if otherwise there is a sensible way to combine efforts? I have poked around on maven.apche.org but so far have not run into a good description of the rationale and design for (1) repositories and (2) dependencies between artifacts. Can anyone point me to a good read? For example, one question I have is: does Maven support haing multiple remote repositories, analagous to non-standard Debian apt repositories? And on a related note, does it support multiple streams of development, analogous to stable and unstable streams for Debian distributions? Package universes is careful to allow all of this. I look forward to any pointers and thoughts. Here's some info on where Scala's artifact-sharing infrastructure is for now: http://lamp.epfl.ch/~spoon/sbaz Regards, Lex Spoon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Type: Bug Versions: 2.0 Reporter: Mark J. Titorenko When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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: (MPJALOPY-9) Jalopy Classes not found
[ http://jira.codehaus.org/browse/MPJALOPY-9?page=all ] Arnaud Heritier updated MPJALOPY-9: --- Version: 1.3.1 > Jalopy Classes not found > > > Key: MPJALOPY-9 > URL: http://jira.codehaus.org/browse/MPJALOPY-9 > Project: maven-jalopy-plugin > Type: Bug > Versions: 1.3.1, 1.4 > Reporter: Arnaud Heritier > Assignee: Arnaud Heritier > Priority: Blocker > Fix For: 1.4.1 > > > Mail from Wendy Smoak : > Twice now, on two different machines (same codebase, though,) the > Jalopy plugin was working fine and then suddenly stopped working with > the error below. > Full output of maven jalopy -X is here: > http://wiki.wsmoak.net/cgi-bin/wiki.pl?Maven/Jalopy > The only thing that changed was Jalopy's config file. Reverting those > changes to a known good state didn't help. Other developers on the > project aren't having any trouble. Obviously I've done *something* to > it (twice!) but I have no idea what. > Does anyone see anything that looks suspicious? > -Wendy > /svn/struts/current/action > $ maven jalopy > __ __ > | \/ |__ _Apache__ ___ > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > |_| |_\__,_|\_/\___|_||_| v. 1.0.2 > java.lang.ClassCastException: java.lang.String >at > de.hunsicker.jalopy.storage.Convention.synchronize(Convention.java:24 > 19) >at > de.hunsicker.jalopy.storage.Convention.synchronize(Convention.java:24 > 45) >at de.hunsicker.jalopy.storage.Convention.(Convention.java:211) >at de.hunsicker.jalopy.plugin.ant.AntPlugin.(AntPlugin.java:60) >at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) >at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct > orAccessorImpl.java:39) >at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC > onstructorAccessorImpl.java:27) >at java.lang.reflect.Constructor.newInstance(Constructor.java:494) >at > org.apache.tools.ant.AntClassLoader.initializeClass(AntClassLoader.ja > va:490) >at > org.apache.tools.ant.taskdefs.Definer.addDefinition(Definer.java:231) >at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:162) >at org.apache.tools.ant.Task.perform(Task.java:341) >at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:185) > ... > build:start: > jalopy:taskdef: > java:prepare-filesystem: > java:compile: >[echo] Compiling to c:\svn\struts\current\action/target/classes > BUILD FAILED > File.. c:\java\m1-repository\cache\maven-jalopy-plugin-1.3.1\plugin.jelly > Element... ant:jalopy > Line.. 64 > Column 46 > java.lang.NoClassDefFoundError > Total time: 2 seconds > Finished at: Tue Feb 07 22:20:09 GMT-07:00 2006 > Arnaud's note : > I have a similar error with the jalopy plugin 1.4 and maven 1.1 beta 3 -- 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-2053) Implements a better toString method in the maven objects exemple in : o.a.m.p.MavenProject
Implements a better toString method in the maven objects exemple in : o.a.m.p.MavenProject -- Key: MNG-2053 URL: http://jira.codehaus.org/browse/MNG-2053 Project: Maven 2 Type: Improvement Versions: 2.0.2 Environment: all Reporter: Olivier Lamy In order to debug mojo, I use mvn -X. Exemple with the eclipse plugin, I have something like this in the output : [DEBUG] (f) reactorProjects = [EMAIL PROTECTED], [EMAIL PROTECTED], org.apache.maven.project.MavenP [EMAIL PROTECTED], [EMAIL PROTECTED], org.apache.maven. [EMAIL PROTECTED], [EMAIL PROTECTED], o [EMAIL PROTECTED], org.apache.maven.project.MavenPro [EMAIL PROTECTED], [EMAIL PROTECTED] Could we have a better toString() method with the minimum of information in case of maven project groupId, artifactId and version ? This could be done with a lot of core object Resource Olivier -- 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: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}
[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_58158 ]
Mark J. Titorenko commented on MASSEMBLY-67:
The issue title should read "assembling dependent jars that contain snapshots"
not "assembling dependent jars or snapshots".
This is still happening. I have a feeling that the assembly is doing the
correct thing while the jar plugin is not, so I'll also open an issue within
the jar plugin project and link it to this one.
This seems to occur when snapshot versions have been uploaded to the remote
repository. If snapshot versions exist within the local repository then
everything works out fine (jars are named version-SNAPSHOT in both plugins).
> assembling dependent jars or snapshots uses timestamp formatted version
> instead of ${version}
> -
>
> Key: MASSEMBLY-67
> URL: http://jira.codehaus.org/browse/MASSEMBLY-67
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Reporter: Mark J. Titorenko
>
>
> I'm using the jar plugin to add my dependencies to the manifest. I'm also
> using the assembly plugin to package all dependencies into one archive. The
> problem is that the jar manifest adds my dependencies as "foo-SNAPHOT" and
> the archiver adds them as "foo-20041113.jar".
> This causes my snapshot classes to not be found at runtime.
--
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: (CONTINUUM-588) cvs checkout does not honor sub-directories
cvs checkout does not honor sub-directories --- Key: CONTINUUM-588 URL: http://jira.codehaus.org/browse/CONTINUUM-588 Project: Continuum Type: Bug Components: Core system Versions: 1.0.2 Environment: linux, cvs, continuum 1.0.2, maven1 project Reporter: Aaron Smuts I have multiple projects in the same cvs module and I want to build them as separate projects. If my scm usrl has a subdirectory, the checkout brings in the entire module regardless. The end of my scm string looks like this ":my-module/my-project". Continuum checks out my-module instead of my-module/my-project To get around this I set the address of my project.xml as "my-module/project.xml". It was able ti find it, but there were other problems. The working directory was now at the root of the module and not the project, so tests that needed files in target/some-directory and log4j with a relative path defined to the log directory failed as well . . . . -- 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
[jira] Created: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}
assembling dependent jars or snapshots uses timestamp formatted version instead
of ${version}
-
Key: MASSEMBLY-67
URL: http://jira.codehaus.org/browse/MASSEMBLY-67
Project: Maven 2.x Assembly Plugin
Type: Bug
Reporter: Mark J. Titorenko
I'm using the jar plugin to add my dependencies to the manifest. I'm also
using the assembly plugin to package all dependencies into one archive. The
problem is that the jar manifest adds my dependencies as "foo-SNAPHOT" and the
archiver adds them as "foo-20041113.jar".
This causes my snapshot classes to not be found at runtime.
--
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-2052) Transitive system deps are not interpolated correctly thus rendering them invalid
Transitive system deps are not interpolated correctly thus rendering them
invalid
-
Key: MNG-2052
URL: http://jira.codehaus.org/browse/MNG-2052
Project: Maven 2
Type: Bug
Components: POM, Artifacts and Repositories
Environment: Windows XP, Java 1.5
Reporter: Chris Stevenson
When a library is loaded as a dependency if its dependencies contain one of
type system which has a variable in the path the variable is not interpolated
so that ${appHome}/lib/... is not an absolute path,
rendering the dependency invalid.
ex
Lib A
|-->Lib B
|-->Lib C (System Dep, path=$appHome}/lib/jar)
When resolving deps for lib B's pom will throw an error because path is not
interpolated.
--
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: critique of maven 2.0.2
Piéroni Raphaël wrote: 2006/2/8, Steve Loughran <[EMAIL PROTECTED]>: Piéroni Raphaël wrote: I don't know if it is the right tool. i jumped on Steve proposition as i was found of prolog during my school years. I don't know if it is right either. One good reason for not using it, but for sticking in java, is ease of integration with the existing maven codebase; nobody could add anything that depended on GPL code to the repository, even LGPL is a bit sensitive. I do not understand this license issue. is it because Jlog is GPL that its artifact and pom are not in ibiblio ? no, it should be on ibiblio if it is popular. Lots of GPL things are (like the mysql jdbc driver, bits of JBoss, etc) is it because Jlog is GPL that we could not import class of jlog into maven code ? yes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MPJALOPY-7) replace textarea dependency by jext
[ http://jira.codehaus.org/browse/MPJALOPY-7?page=all ] Arnaud Heritier updated MPJALOPY-7: --- type: Wish (was: Bug) > replace textarea dependency by jext > --- > > Key: MPJALOPY-7 > URL: http://jira.codehaus.org/browse/MPJALOPY-7 > Project: maven-jalopy-plugin > Type: Wish > Reporter: Ralph Apel > Priority: Minor > > > After some long searches it seems to me that > net.sf.textarea (textarea.jar) > may be replaced by packages > org.gjt.sp.jedit.syntax > and > org.gjt.sp.jedit.textarea > as contained in jext.jar -- 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: (MPJALOPY-9) Jalopy Classes not found
Jalopy Classes not found Key: MPJALOPY-9 URL: http://jira.codehaus.org/browse/MPJALOPY-9 Project: maven-jalopy-plugin Type: Bug Versions: 1.4 Reporter: Arnaud Heritier Assigned to: Arnaud Heritier Priority: Blocker Fix For: 1.4.1 Mail from Wendy Smoak : Twice now, on two different machines (same codebase, though,) the Jalopy plugin was working fine and then suddenly stopped working with the error below. Full output of maven jalopy -X is here: http://wiki.wsmoak.net/cgi-bin/wiki.pl?Maven/Jalopy The only thing that changed was Jalopy's config file. Reverting those changes to a known good state didn't help. Other developers on the project aren't having any trouble. Obviously I've done *something* to it (twice!) but I have no idea what. Does anyone see anything that looks suspicious? -Wendy /svn/struts/current/action $ maven jalopy __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 java.lang.ClassCastException: java.lang.String at de.hunsicker.jalopy.storage.Convention.synchronize(Convention.java:24 19) at de.hunsicker.jalopy.storage.Convention.synchronize(Convention.java:24 45) at de.hunsicker.jalopy.storage.Convention.(Convention.java:211) at de.hunsicker.jalopy.plugin.ant.AntPlugin.(AntPlugin.java:60) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct orAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC onstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.apache.tools.ant.AntClassLoader.initializeClass(AntClassLoader.ja va:490) at org.apache.tools.ant.taskdefs.Definer.addDefinition(Definer.java:231) at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:162) at org.apache.tools.ant.Task.perform(Task.java:341) at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:185) ... build:start: jalopy:taskdef: java:prepare-filesystem: java:compile: [echo] Compiling to c:\svn\struts\current\action/target/classes BUILD FAILED File.. c:\java\m1-repository\cache\maven-jalopy-plugin-1.3.1\plugin.jelly Element... ant:jalopy Line.. 64 Column 46 java.lang.NoClassDefFoundError Total time: 2 seconds Finished at: Tue Feb 07 22:20:09 GMT-07:00 2006 Arnaud's note : I have a similar error with the jalopy plugin 1.4 and maven 1.1 beta 3 -- 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]
