[jira] Commented: (MPIR-158) Artifact ###### has no file error.
[ http://jira.codehaus.org/browse/MPIR-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186219#action_186219 ] Ryan Connolly commented on MPIR-158: FYI: I am seeing the exact same behaviour using project-info-reports-plugin version 2.1.2 with maven-site-plugin version 2.0-beta-7 when running goal site-deploy. Below is the m-p-i-r-p snippet i have configured in my parent POM. maven-project-info-reports-plugin 2.1.2 false false [18:12:56]: [ERROR] Artifact: javax.transaction:jta:jar:1.0.1B has no file. [18:12:56]: [ERROR] Artifact: jaxen:jaxen:jar:1.1.1 has no file. [18:12:56]: [ERROR] Artifact: jdom:jdom:jar:1.0 has no file. [18:12:56]: [ERROR] Artifact: net.sf.ehcache:ehcache:jar:1.2.3 has no file. [18:12:56]: [ERROR] Artifact: net.sf.ezmorph:ezmorph:jar:1.0.6 has no file. [18:12:56]: [ERROR] Artifact: org.hibernate:ejb3-persistence:jar:1.0.2.GA has no file. [18:12:56]: [ERROR] Artifact: org.hibernate:hibernate:jar:3.2.5.ga has no file. [18:12:56]: [ERROR] Artifact: org.hibernate:hibernate-annotations:jar:3.4.0.GA has no file. [18:12:56]: [ERROR] Artifact: org.hibernate:hibernate-commons-annotations:jar:3.1.0.GA has no file. [18:12:56]: [ERROR] Artifact: org.hibernate:hibernate-core:jar:3.3.0.SP1 has no file. [18:12:56]: [ERROR] Artifact: org.jdom:jdom:jar:1.1 has no file. [18:12:56]: [ERROR] Artifact: org.slf4j:slf4j-api:jar:1.5.6 has no file. [18:12:57]: [ERROR] Artifact: xalan:xalan:jar:2.6.0 has no file. [18:12:57]: [ERROR] Artifact: xerces:xercesImpl:jar:2.8.1 has no file. [18:12:57]: [ERROR] Artifact: xerces:xmlParserAPIs:jar:2.6.2 has no file. [18:12:57]: [ERROR] Artifact: xml-apis:xml-apis:jar:1.3.03 has no file. [18:12:57]: [ERROR] Artifact: xom:xom:jar:1.0 has no file. > Artifact ## has no file error. > -- > > Key: MPIR-158 > URL: http://jira.codehaus.org/browse/MPIR-158 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.1.1 > Environment: Windows xp, tomcat 5.5 server >Reporter: Damian Sinczak >Priority: Minor > > During 'mvn site' command on project i receive some strange errors. Their are > no critical, but they are still errors. > Console dump: > [ERROR] Artifact: org.apache.abdera:abdera-core:jar:0.4.0-incubating has no > file > . > [ERROR] Artifact: > org.apache.abdera:abdera-extensions-json:jar:0.4.0-incubating > has no file. > [ERROR] Artifact: > org.apache.abdera:abdera-extensions-main:jar:0.4.0-incubating > has no file. > [ERROR] Artifact: org.apache.abdera:abdera-i18n:jar:0.4.0-incubating has no > file > . > [ERROR] Artifact: org.apache.abdera:abdera-parser:jar:0.4.0-incubating has no > fi > le. > [ERROR] Artifact: org.apache.cxf:cxf-api:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-common-schemas:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-common-utilities:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-bindings-soap:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-bindings-xml:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-core:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-frontend-simple:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-ws-addr:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-tools-common:jar:2.2 has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0 > .2 has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-annotation_1.0_spec:jar:1.1 > .1 has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.5 h > as no file. > [ERROR] Artifact: org.apache.geronimo.specs:geronimo-jaxws_2.1_spec:jar:1.0 > has > no file. > [ERROR] Artifact: org.apache.geronimo.specs:geronimo-servlet_2.5_spec:jar:1.2 > ha > s no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1 > has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-ws-metadata_2.0_spec:jar:1. > 1.2 has no file. > [ERROR] Artifact: org.apache.neethi:neethi:jar:2.0.4 has no file. > [ERROR] Artifact: org.apache.ws.commons.axiom:axiom-api:jar:1.2.7 has no file. > [ERROR] Artifact: org.apache.ws.commons.axiom:axiom-impl:jar:1.2.7 has no > file. > [ERROR] Artifact: org.apache.ws.commons.schema:XmlSchema:jar:1.4.4 has no > file. > [ERROR] Artifact: org.apache.xmlbeans:xmlbeans:jar:2.3.0 has no file. > [ERROR] Artifact: org.codehaus.jettison:jettison:jar:1.0.1 has no file. > [ERROR] Artifact: org.codehaus.woodstox:wstx-asl:jar:3.2.6 has no file. > [ERROR] Artifact: org.hibernate:ejb3-persistence:jar:1.0.1.GA has no file. > [ERROR] Artifact: org.hibernate:hibernate-c
[jira] Commented: (MPIR-158) Artifact ###### has no file error.
[ http://jira.codehaus.org/browse/MPIR-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186223#action_186223 ] Stevo Slavic commented on MPIR-158: --- True, it started appearing again with 2.1.2 on a very complex project, but can not reproduce it on a simple project that could be attached to the issue. Can not reopen the issue, maybe new one will have to be created with maybe a link to this one. > Artifact ## has no file error. > -- > > Key: MPIR-158 > URL: http://jira.codehaus.org/browse/MPIR-158 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.1.1 > Environment: Windows xp, tomcat 5.5 server >Reporter: Damian Sinczak >Priority: Minor > > During 'mvn site' command on project i receive some strange errors. Their are > no critical, but they are still errors. > Console dump: > [ERROR] Artifact: org.apache.abdera:abdera-core:jar:0.4.0-incubating has no > file > . > [ERROR] Artifact: > org.apache.abdera:abdera-extensions-json:jar:0.4.0-incubating > has no file. > [ERROR] Artifact: > org.apache.abdera:abdera-extensions-main:jar:0.4.0-incubating > has no file. > [ERROR] Artifact: org.apache.abdera:abdera-i18n:jar:0.4.0-incubating has no > file > . > [ERROR] Artifact: org.apache.abdera:abdera-parser:jar:0.4.0-incubating has no > fi > le. > [ERROR] Artifact: org.apache.cxf:cxf-api:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-common-schemas:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-common-utilities:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-bindings-soap:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-bindings-xml:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-core:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-frontend-simple:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-ws-addr:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-tools-common:jar:2.2 has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0 > .2 has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-annotation_1.0_spec:jar:1.1 > .1 has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.5 h > as no file. > [ERROR] Artifact: org.apache.geronimo.specs:geronimo-jaxws_2.1_spec:jar:1.0 > has > no file. > [ERROR] Artifact: org.apache.geronimo.specs:geronimo-servlet_2.5_spec:jar:1.2 > ha > s no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1 > has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-ws-metadata_2.0_spec:jar:1. > 1.2 has no file. > [ERROR] Artifact: org.apache.neethi:neethi:jar:2.0.4 has no file. > [ERROR] Artifact: org.apache.ws.commons.axiom:axiom-api:jar:1.2.7 has no file. > [ERROR] Artifact: org.apache.ws.commons.axiom:axiom-impl:jar:1.2.7 has no > file. > [ERROR] Artifact: org.apache.ws.commons.schema:XmlSchema:jar:1.4.4 has no > file. > [ERROR] Artifact: org.apache.xmlbeans:xmlbeans:jar:2.3.0 has no file. > [ERROR] Artifact: org.codehaus.jettison:jettison:jar:1.0.1 has no file. > [ERROR] Artifact: org.codehaus.woodstox:wstx-asl:jar:3.2.6 has no file. > [ERROR] Artifact: org.hibernate:ejb3-persistence:jar:1.0.1.GA has no file. > [ERROR] Artifact: org.hibernate:hibernate-commons-annotations:jar:3.0.0.ga > has n > o file. > [ERROR] Artifact: org.mortbay.jetty:jetty:jar:6.1.15 has no file. > [ERROR] Artifact: org.mortbay.jetty:jetty-util:jar:6.1.15 has no file. > [ERROR] Artifact: org.slf4j:slf4j-api:jar:1.3.1 has no file. > [ERROR] Artifact: org.slf4j:slf4j-jdk14:jar:1.3.1 has no file. > [ERROR] Artifact: org.springframework:spring-beans:jar:2.5.5 has no file. > [ERROR] Artifact: org.springframework:spring-context:jar:2.5.5 has no file. > [ERROR] Artifact: org.springframework:spring-core:jar:2.5.5 has no file. > [ERROR] Artifact: org.springframework:spring-web:jar:2.5.5 has no file. > [ERROR] Artifact: wsdl4j:wsdl4j:jar:1.6.2 has no file. > [ERROR] Artifact: xalan:xalan:jar:2.6.0 has no file. > [ERROR] Artifact: xerces:xercesImpl:jar:2.6.2 has no file. > [ERROR] Artifact: xerces:xmlParserAPIs:jar:2.6.2 has no file. > [ERROR] Artifact: xml-apis:xml-apis:jar:1.3.02 has no file. > [ERROR] Artifact: xml-resolver:xml-resolver:jar:1.2 has no file. > [ERROR] Artifact: xom:xom:jar:1.0 has no file. > [INFO] Generating "Project Team" report. > [INFO] Generating "Project License" report. > [INFO] Generating "Project Plugins" report. > [INFO] Generating "Maven Surefire Report" report. > [INFO] Generating "FindBugs Report" report. > [INFO] Using source root: > [INFO] C:\edys_workspace\edystok\tar
[jira] Closed: (MNG-4197) relocation doesn't work in trunk (rev 784345)
[ http://jira.codehaus.org/browse/MNG-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4197. -- Assignee: Benjamin Bentmann Resolution: Fixed Applied in [r801648|http://svn.apache.org/viewvc?view=rev&revision=801648], thanks Olivier. > relocation doesn't work in trunk (rev 784345) > - > > Key: MNG-4197 > URL: http://jira.codehaus.org/browse/MNG-4197 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Dependencies >Affects Versions: 3.0-alpha-3 >Reporter: Olivier Lamy >Assignee: Benjamin Bentmann >Priority: Blocker > Fix For: 3.0-alpha-3 > > Attachments: MNG-4197-2.x-code.patch > > > see it MavenITmng0507ArtifactRelocationTest -- 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] Reopened: (MPIR-158) Artifact ###### has no file error.
[ http://jira.codehaus.org/browse/MPIR-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann reopened MPIR-158: > Artifact ## has no file error. > -- > > Key: MPIR-158 > URL: http://jira.codehaus.org/browse/MPIR-158 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug > Components: dependencies >Affects Versions: 2.1.1 > Environment: Windows xp, tomcat 5.5 server >Reporter: Damian Sinczak >Priority: Minor > > During 'mvn site' command on project i receive some strange errors. Their are > no critical, but they are still errors. > Console dump: > [ERROR] Artifact: org.apache.abdera:abdera-core:jar:0.4.0-incubating has no > file > . > [ERROR] Artifact: > org.apache.abdera:abdera-extensions-json:jar:0.4.0-incubating > has no file. > [ERROR] Artifact: > org.apache.abdera:abdera-extensions-main:jar:0.4.0-incubating > has no file. > [ERROR] Artifact: org.apache.abdera:abdera-i18n:jar:0.4.0-incubating has no > file > . > [ERROR] Artifact: org.apache.abdera:abdera-parser:jar:0.4.0-incubating has no > fi > le. > [ERROR] Artifact: org.apache.cxf:cxf-api:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-common-schemas:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-common-utilities:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-bindings-soap:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-bindings-xml:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-core:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-frontend-simple:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-rt-ws-addr:jar:2.2 has no file. > [ERROR] Artifact: org.apache.cxf:cxf-tools-common:jar:2.2 has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0 > .2 has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-annotation_1.0_spec:jar:1.1 > .1 has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.5 h > as no file. > [ERROR] Artifact: org.apache.geronimo.specs:geronimo-jaxws_2.1_spec:jar:1.0 > has > no file. > [ERROR] Artifact: org.apache.geronimo.specs:geronimo-servlet_2.5_spec:jar:1.2 > ha > s no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1 > has no file. > [ERROR] Artifact: > org.apache.geronimo.specs:geronimo-ws-metadata_2.0_spec:jar:1. > 1.2 has no file. > [ERROR] Artifact: org.apache.neethi:neethi:jar:2.0.4 has no file. > [ERROR] Artifact: org.apache.ws.commons.axiom:axiom-api:jar:1.2.7 has no file. > [ERROR] Artifact: org.apache.ws.commons.axiom:axiom-impl:jar:1.2.7 has no > file. > [ERROR] Artifact: org.apache.ws.commons.schema:XmlSchema:jar:1.4.4 has no > file. > [ERROR] Artifact: org.apache.xmlbeans:xmlbeans:jar:2.3.0 has no file. > [ERROR] Artifact: org.codehaus.jettison:jettison:jar:1.0.1 has no file. > [ERROR] Artifact: org.codehaus.woodstox:wstx-asl:jar:3.2.6 has no file. > [ERROR] Artifact: org.hibernate:ejb3-persistence:jar:1.0.1.GA has no file. > [ERROR] Artifact: org.hibernate:hibernate-commons-annotations:jar:3.0.0.ga > has n > o file. > [ERROR] Artifact: org.mortbay.jetty:jetty:jar:6.1.15 has no file. > [ERROR] Artifact: org.mortbay.jetty:jetty-util:jar:6.1.15 has no file. > [ERROR] Artifact: org.slf4j:slf4j-api:jar:1.3.1 has no file. > [ERROR] Artifact: org.slf4j:slf4j-jdk14:jar:1.3.1 has no file. > [ERROR] Artifact: org.springframework:spring-beans:jar:2.5.5 has no file. > [ERROR] Artifact: org.springframework:spring-context:jar:2.5.5 has no file. > [ERROR] Artifact: org.springframework:spring-core:jar:2.5.5 has no file. > [ERROR] Artifact: org.springframework:spring-web:jar:2.5.5 has no file. > [ERROR] Artifact: wsdl4j:wsdl4j:jar:1.6.2 has no file. > [ERROR] Artifact: xalan:xalan:jar:2.6.0 has no file. > [ERROR] Artifact: xerces:xercesImpl:jar:2.6.2 has no file. > [ERROR] Artifact: xerces:xmlParserAPIs:jar:2.6.2 has no file. > [ERROR] Artifact: xml-apis:xml-apis:jar:1.3.02 has no file. > [ERROR] Artifact: xml-resolver:xml-resolver:jar:1.2 has no file. > [ERROR] Artifact: xom:xom:jar:1.0 has no file. > [INFO] Generating "Project Team" report. > [INFO] Generating "Project License" report. > [INFO] Generating "Project Plugins" report. > [INFO] Generating "Maven Surefire Report" report. > [INFO] Generating "FindBugs Report" report. > [INFO] Using source root: > [INFO] C:\edys_workspace\edystok\target\classes > [INFO] Using test source root: > [INFO] C:\edys_workspace\edystok\target\test-classes > [INFO] No effort provided, using default effort. > [INFO] Adding Source Directory: C:\edys_workspace\edystok\src\main\java > [INFO] No threshold provided, using default threshol
[jira] Created: (MPH-67) Add a way to merge inherited profiles with same id
Add a way to merge inherited profiles with same id
--
Key: MPH-67
URL: http://jira.codehaus.org/browse/MPH-67
Project: Maven 2.x Help Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Vincent Siveton
Take the following project:
{noformat}
apache:6:pom with has a "apache-release" profileId
|_ maven-parent:12
|_ doxia:1.1.2-SNAPSHOT with has a "apache-release" profileId
{noformat}
Call /doxia/doxia/mvn help:effective-pom -N
You will see only the apache-release from Doxia but Maven uses the
apache-release from parent.
Two way to see in the effective pom the inherited profiles with same id:
* merge child and parent profiles
* add parent profile with another id
--
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] Commented: (MNG-3230) HTTPS with self-signed certificate does not work, no error message.
[ http://jira.codehaus.org/browse/MNG-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186230#action_186230 ] Paul R. Saxman commented on MNG-3230: - I've had some luck using the Apache Commons HTTPClient EasySSLProtocolSocketFactory (http://hc.apache.org/httpclient-3.x/sslguide.html) for communicating with servers that have unsigned SSL certs. It's certainly more complicated than using the stock URLConenction, but perhaps worth the flexibility. > HTTPS with self-signed certificate does not work, no error message. > --- > > Key: MNG-3230 > URL: http://jira.codehaus.org/browse/MNG-3230 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.7 >Reporter: Andreas Krüger > Fix For: 2.2.x > > > We have a repository server that serves the same files both via HTTPS and > HTTP. > Maven is not able to find artifacts when using HTTPS. All goes well when > using HTTP. > The problem probably is that the HTTPS - certificate used by the repository > server is self-signed, and Maven has not been configured to accept that > certificate as genuine. (This is a guess.) > Expected behavior: With HTTPS, build does not continue. Maven gives an error > message indicating the problem is certificate-related. > Behavior seen: Maven reacts as if there were no problem connecting the > repository, but as if the artifact were missing from the repository. It > continues to search other repositories as happen to be configured. (However, > the artifact is clearly there, e.g., can be downloaded with "wget > --no-check-certificate " via HTTPS.) -- 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] Commented: (MNG-4284) [surefire] Command line parms not passed to tests on linux
[ http://jira.codehaus.org/browse/MNG-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186231#action_186231 ] Matthew Fleming commented on MNG-4284: -- It is the same problem as [SUREFIRE-121|http://jira.codehaus.org/browse/SUREFIRE-121]. > [surefire] Command line parms not passed to tests on linux > --- > > Key: MNG-4284 > URL: http://jira.codehaus.org/browse/MNG-4284 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.2.0 > Environment: fedora 8 32-bit linux >Reporter: Matthew Fleming > > When I use maven 2.2 on fedora, the command line properties are not passed > into the surefire tests. When I run the exact same build using maven 2.2 on > OSX, the parameters are passed. > Example: > mvn -Dsmr.jdbc.port=4306 -X > debug.log > On linux: > DEBUG] Setting system property [user.dir]=[/data2/apps/smr] > [DEBUG] Setting system property > [localRepository]=[/home/oabuild/.m2/repository] > [DEBUG] Setting system property [basedir]=[/data2/apps/smr] > [DEBUG] Using JVM: /opt/jdk1.5.0_18/jre/bin/java > On Mac: > A whole bunch of properties including: > [DEBUG] Setting system property [smr.jdbc.port]=[4306] > Any ideas? -- 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: (MAVENUPLOAD-2545) Please upload DynamicJasper 3.0.8
Please upload DynamicJasper 3.0.8 - Key: MAVENUPLOAD-2545 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2545 Project: Maven Upload Requests Issue Type: Task Reporter: Juan Manuel Alvarez I am DynamicJasper's project leader, please upload. DynamicJasper (DJ) is an API that hides the complexity of Jasper Reports, it helps developers to save time when designing simple/medium complexity reports generating the layout of the report elements automatically. It creates reports dynamically, defining at runtime the columns, column width (auto width), groups, variables, fonts, charts, crosstabs, sub reports (that can also be dynamic), page size and everything else that you can define at design time. -- 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] Closed: (MAVENUPLOAD-2539) Please upload DynamicJasper 3.0.7
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Manuel Alvarez closed MAVENUPLOAD-2539. Resolution: Won't Fix Do not upload this version, please proceed with issue related to DynamicJasper version 3.0.8 > Please upload DynamicJasper 3.0.7 > - > > Key: MAVENUPLOAD-2539 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2539 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Juan Manuel Alvarez > > I am DynamicJasper's project leader, please upload. > DynamicJasper (DJ) is an API that hides the complexity of Jasper Reports, it > helps developers to save time when designing simple/medium complexity reports > generating the layout of the report elements automatically. It creates > reports dynamically, defining at runtime the columns, column width (auto > width), groups, variables, fonts, charts, crosstabs, sub reports (that can > also be dynamic), page size and everything else that you can define at design > time. -- 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: (MNG-4285) CliManager.parse() cannot be called from within a mojo
CliManager.parse() cannot be called from within a mojo
--
Key: MNG-4285
URL: http://jira.codehaus.org/browse/MNG-4285
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.2.0, 2.1.0
Reporter: John Casey
As reported by Benjamin Bentmann:
{noformat}
as per MNG-4024, the CLIManager was exposed to the public API. Its parse()
method returns a CommandLine object from commons-cli. Per MNG-4166, commons-cli
is no longer filtered from the plugin realm.
This constellation prohibits the usage CLIManager.parse() from Maven 2.2.x in
plugins as the returned CommandLine originates from the core realm and isn't
type-compatible with the same class from the plugin realm.
So, do we have a better option than to extend the Javadoc of CLIManager in
order to clearly state that it's for integrators only and not for plugins?
{noformat}
After discussing with him a little more on IRC, he suggested wrapping the
return type from the CliManager.parse() method such that we're not passing
around objects from the commons-cli API. One ready-made alternative to the
commons-cli classes might be MavenExecutionRequest...returning this might
enable plugins to use a standard interface to interact with Maven's CLI-parsing
while at the same time hiding the conflicting commons-cli classes.
We can't make a change like this in 2.2.x, but it makes a lot of sense to
pursue for 2.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
[jira] Moved: (SUREFIRE-564) [surefire] Command line parms not passed to tests on linux
[ http://jira.codehaus.org/browse/SUREFIRE-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-4284 to SUREFIRE-564: - Affects Version/s: (was: 2.2.0) 2.4.3 Key: SUREFIRE-564 (was: MNG-4284) Project: Maven Surefire (was: Maven 2) > [surefire] Command line parms not passed to tests on linux > --- > > Key: SUREFIRE-564 > URL: http://jira.codehaus.org/browse/SUREFIRE-564 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.4.3 > Environment: fedora 8 32-bit linux >Reporter: Matthew Fleming > > When I use maven 2.2 on fedora, the command line properties are not passed > into the surefire tests. When I run the exact same build using maven 2.2 on > OSX, the parameters are passed. > Example: > mvn -Dsmr.jdbc.port=4306 -X > debug.log > On linux: > DEBUG] Setting system property [user.dir]=[/data2/apps/smr] > [DEBUG] Setting system property > [localRepository]=[/home/oabuild/.m2/repository] > [DEBUG] Setting system property [basedir]=[/data2/apps/smr] > [DEBUG] Using JVM: /opt/jdk1.5.0_18/jre/bin/java > On Mac: > A whole bunch of properties including: > [DEBUG] Setting system property [smr.jdbc.port]=[4306] > Any ideas? -- 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] Closed: (SUREFIRE-564) [surefire] Command line parms not passed to tests on linux
[ http://jira.codehaus.org/browse/SUREFIRE-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed SUREFIRE-564. -- Assignee: Benjamin Bentmann Resolution: Duplicate > [surefire] Command line parms not passed to tests on linux > --- > > Key: SUREFIRE-564 > URL: http://jira.codehaus.org/browse/SUREFIRE-564 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.4.3 > Environment: fedora 8 32-bit linux >Reporter: Matthew Fleming >Assignee: Benjamin Bentmann > > When I use maven 2.2 on fedora, the command line properties are not passed > into the surefire tests. When I run the exact same build using maven 2.2 on > OSX, the parameters are passed. > Example: > mvn -Dsmr.jdbc.port=4306 -X > debug.log > On linux: > DEBUG] Setting system property [user.dir]=[/data2/apps/smr] > [DEBUG] Setting system property > [localRepository]=[/home/oabuild/.m2/repository] > [DEBUG] Setting system property [basedir]=[/data2/apps/smr] > [DEBUG] Using JVM: /opt/jdk1.5.0_18/jre/bin/java > On Mac: > A whole bunch of properties including: > [DEBUG] Setting system property [smr.jdbc.port]=[4306] > Any ideas? -- 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: (MSITE-421) Still not working in maven-site-plugin/2.0-beta-6 [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader.
Still not working in maven-site-plugin/2.0-beta-6 [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. -- Key: MSITE-421 URL: http://jira.codehaus.org/browse/MSITE-421 Project: Maven 2.x Site Plugin Issue Type: Sub-task Reporter: Vladimir Nicolici I still get the error below in maven-site-plugin/2.0-beta-6, although issue 49190 is marked as fixed in 2.0-beta-6. [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. [INFO] Velocimacro : error using VM library template VM_global_library.vm : org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'VM_global_library.vm' -- 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] Updated: (MNG-4285) CliManager.parse() cannot be called from within a mojo
[
http://jira.codehaus.org/browse/MNG-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MNG-4285:
Fix Version/s: 2.3.x
> CliManager.parse() cannot be called from within a mojo
> --
>
> Key: MNG-4285
> URL: http://jira.codehaus.org/browse/MNG-4285
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.1.0, 2.2.0
>Reporter: John Casey
> Fix For: 2.3.x
>
>
> As reported by Benjamin Bentmann:
> {noformat}
> as per MNG-4024, the CLIManager was exposed to the public API. Its parse()
> method returns a CommandLine object from commons-cli. Per MNG-4166,
> commons-cli is no longer filtered from the plugin realm.
> This constellation prohibits the usage CLIManager.parse() from Maven 2.2.x in
> plugins as the returned CommandLine originates from the core realm and isn't
> type-compatible with the same class from the plugin realm.
> So, do we have a better option than to extend the Javadoc of CLIManager in
> order to clearly state that it's for integrators only and not for plugins?
> {noformat}
> After discussing with him a little more on IRC, he suggested wrapping the
> return type from the CliManager.parse() method such that we're not passing
> around objects from the commons-cli API. One ready-made alternative to the
> commons-cli classes might be MavenExecutionRequest...returning this might
> enable plugins to use a standard interface to interact with Maven's
> CLI-parsing while at the same time hiding the conflicting commons-cli classes.
> We can't make a change like this in 2.2.x, but it makes a lot of sense to
> pursue for 2.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
[jira] Moved: (MNGSITE-96) mojo-api-specification.html refers wrong package for the Log class
[ http://jira.codehaus.org/browse/MNGSITE-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MOJO-1326 to MNGSITE-96: --- Complexity: (was: Intermediate) Key: MNGSITE-96 (was: MOJO-1326) Project: Maven 2 Project Web Site (was: Mojo) > mojo-api-specification.html refers wrong package for the Log class > -- > > Key: MNGSITE-96 > URL: http://jira.codehaus.org/browse/MNGSITE-96 > Project: Maven 2 Project Web Site > Issue Type: Bug >Reporter: Anders Kr. Andersen >Priority: Minor > > In the http://maven.apache.org/developers/mojo-api-specification.html a > logger called org.apache.maven.monitor.logging.Log is referred. > The logger is now called org.apache.maven.plugin.logging. Log as far as I can > see. > import org.apache.maven.plugin.logging.Log; IS CORRECT > import org.apache.maven.monitor.logging.Log; IS WRONG -- 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] Commented: (MCHANGELOG-89) Dependency Conflict plexus-utils
[
http://jira.codehaus.org/browse/MCHANGELOG-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186244#action_186244
]
Vladimir Nicolici commented on MCHANGELOG-89:
-
When will version 2.2 be released? The current version, 2.1, was last released
in July 2007...
This issue is IMO a show stopper, I'm not able to use the changelog plugin
because of this problem.
> Dependency Conflict plexus-utils
>
>
> Key: MCHANGELOG-89
> URL: http://jira.codehaus.org/browse/MCHANGELOG-89
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Maven 3.x
>Reporter: Lammert Westerhoff
>Assignee: Benjamin Bentmann
> Fix For: 2.2
>
>
> The maven-changelog-plugin is using the maven-scm-provider-svnexe for svn
> repositories. The maven-scm-provider-svnexe is ugin plexus-utils 1.5.6.
> Because of a nearer dependency from maven-model the plugin will use
> plexus-utils 1.0.4, causing the plugin to fail.
> See below the dependencies and the stacktrace.
> {noformat}
> [DEBUG] Resolving plugin: org.apache.maven.plugins:maven-changelog-plugin
> with version: 2.1
> [DEBUG] In verifyVersionedPlugin for:
> org.apache.maven.plugins:maven-changelog-plugin
> [DEBUG]
> org.apache.maven.plugins:maven-changelog-plugin:maven-plugin:2.1:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-project:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected
> for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected
> for runtime)
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime
> (selected for runtime)
> [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime (selected
> for runtime)
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for
> runtime)
> [DEBUG]
> org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected
> for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for
> runtime)
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime
> (selected for runtime)
> [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0:runtime
> (selected for runtime)
> [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for runtime)
> [DEBUG] org.apache.maven.reporting:maven-reporting-impl:jar:2.0:runtime
> (selected for runtime)
> [DEBUG] commons-validator:commons-validator:jar:1.1.4:runtime (selected
> for runtime)
> [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] oro:oro:jar:2.0.7:runtime (selected for runtime)
> [DEBUG] doxia:doxia-core:jar:1.0-alpha-4:runtime (selected for runtime)
> [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (removed - nearer
> found: 1.0-alpha-5)
> [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-5:runtime (selected for runtime)
> [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven.scm:maven-scm-api:jar:1.0:runtime (selected for
> runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (removed -
> nearer found: 1.0.4)
> [DEBUG] org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0:runtime
> (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (removed -
> nearer found: 1.0.4)
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9:runtime (removed
> - nearer found: 1.0-alpha-8)
> [DEBUG] org.apache.maven.scm:maven-scm-provider-bazaar:jar:1.0:runtime
> (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (removed -
> nearer found: 1.0.4)
> [DEBUG] regexp:regexp:jar:1.3:runtime (selected for runtime)
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-7:runtim
[jira] Commented: (MCHANGELOG-89) Dependency Conflict plexus-utils
[
http://jira.codehaus.org/browse/MCHANGELOG-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186246#action_186246
]
Benjamin Bentmann commented on MCHANGELOG-89:
-
Simply declare plexus-utils:1.5.6 as a plugin dependency in your POM and you
have a workaround.
> Dependency Conflict plexus-utils
>
>
> Key: MCHANGELOG-89
> URL: http://jira.codehaus.org/browse/MCHANGELOG-89
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
>Affects Versions: 2.1
> Environment: Maven 3.x
>Reporter: Lammert Westerhoff
>Assignee: Benjamin Bentmann
> Fix For: 2.2
>
>
> The maven-changelog-plugin is using the maven-scm-provider-svnexe for svn
> repositories. The maven-scm-provider-svnexe is ugin plexus-utils 1.5.6.
> Because of a nearer dependency from maven-model the plugin will use
> plexus-utils 1.0.4, causing the plugin to fail.
> See below the dependencies and the stacktrace.
> {noformat}
> [DEBUG] Resolving plugin: org.apache.maven.plugins:maven-changelog-plugin
> with version: 2.1
> [DEBUG] In verifyVersionedPlugin for:
> org.apache.maven.plugins:maven-changelog-plugin
> [DEBUG]
> org.apache.maven.plugins:maven-changelog-plugin:maven-plugin:2.1:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-project:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-profile:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected
> for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected
> for runtime)
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime
> (selected for runtime)
> [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0:runtime (selected
> for runtime)
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0:runtime
> (selected for runtime)
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for
> runtime)
> [DEBUG]
> org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5:runtime (selected
> for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0:runtime (selected for
> runtime)
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime
> (selected for runtime)
> [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven.reporting:maven-reporting-api:jar:2.0:runtime
> (selected for runtime)
> [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven:maven-model:jar:2.0:runtime (selected for runtime)
> [DEBUG] org.apache.maven.reporting:maven-reporting-impl:jar:2.0:runtime
> (selected for runtime)
> [DEBUG] commons-validator:commons-validator:jar:1.1.4:runtime (selected
> for runtime)
> [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] oro:oro:jar:2.0.7:runtime (selected for runtime)
> [DEBUG] doxia:doxia-core:jar:1.0-alpha-4:runtime (selected for runtime)
> [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-4:runtime (removed - nearer
> found: 1.0-alpha-5)
> [DEBUG] doxia:doxia-sink-api:jar:1.0-alpha-5:runtime (selected for runtime)
> [DEBUG] org.apache.maven:maven-settings:jar:2.0:runtime (selected for
> runtime)
> [DEBUG] org.apache.maven.scm:maven-scm-api:jar:1.0:runtime (selected for
> runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (removed -
> nearer found: 1.0.4)
> [DEBUG] org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0:runtime
> (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (removed -
> nearer found: 1.0.4)
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9:runtime (removed
> - nearer found: 1.0-alpha-8)
> [DEBUG] org.apache.maven.scm:maven-scm-provider-bazaar:jar:1.0:runtime
> (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime (removed -
> nearer found: 1.0.4)
> [DEBUG] regexp:regexp:jar:1.3:runtime (selected for runtime)
> [DEBUG]
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-7:runtime (removed
> - nearer found: 1.0-alpha-8)
> [DEBUG] org.apache.maven.scm:maven-scm-provider-clearc
[jira] Closed: (MAVENUPLOAD-2472) New sychronization request for org.bushe (EventBus)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2472. --- Resolution: Fixed sorry, i think it should be working now > New sychronization request for org.bushe (EventBus) > --- > > Key: MAVENUPLOAD-2472 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2472 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Michael Bushe >Assignee: Carlos Sanchez > > I'd like to add my repo to synchronize releases of the EventBus (and future > projects) of bushe.org to the Central Maven Repository. Thank you for > supplying this essential service. > My comma delimited info for rsync over ssh is: > "org.bushe","rs...@bushe.com:/home/rsync/m2repo/releases","rsync_ssh","Michael > Bushe","mich...@bushe.com",, > The repo is browesable here: > http://www.bushe.com:8081/nexus/content/repositories/Bushe.orgSyncToCentral/ > Here's proof that I own bushe.org: > http://reports.internic.net/cgi/whois?whois_nic=bushe.org&type=domain > Let me know if you have any trouble syncing. I expect it to be set up > correctly, but you never know. > Thank you again! > Michael Bushe -- 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] Closed: (MAVENUPLOAD-2526) ICEfaces repository sync
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2526. --- Assignee: Carlos Sanchez Resolution: Fixed > ICEfaces repository sync > > > Key: MAVENUPLOAD-2526 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2526 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Ted Goddard >Assignee: Carlos Sanchez > > "org.icefaces","/home/maven/repository-staging/to-ibiblio/maven-svn","svn","Ted > > Goddard","ted.godd...@icesoft.com",,"http://server.ice:/svn/ossrepo/maven2/releases/"; -- 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] Closed: (MAVENUPLOAD-2545) Please upload DynamicJasper 3.0.8
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2545. --- Assignee: Carlos Sanchez Resolution: Fixed > Please upload DynamicJasper 3.0.8 > - > > Key: MAVENUPLOAD-2545 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2545 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Juan Manuel Alvarez >Assignee: Carlos Sanchez > > I am DynamicJasper's project leader, please upload. > DynamicJasper (DJ) is an API that hides the complexity of Jasper Reports, it > helps developers to save time when designing simple/medium complexity reports > generating the layout of the report elements automatically. It creates > reports dynamically, defining at runtime the columns, column width (auto > width), groups, variables, fonts, charts, crosstabs, sub reports (that can > also be dynamic), page size and everything else that you can define at design > time. -- 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] Closed: (MAVENUPLOAD-2540) Repository sync for project net.sf.blunder
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2540. --- Assignee: Carlos Sanchez Resolution: Fixed > Repository sync for project net.sf.blunder > --- > > Key: MAVENUPLOAD-2540 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2540 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Ambrosi Lucas >Assignee: Carlos Sanchez > > "net.sf.blunder","mavens...@web.sourceforge.net:/home/groups/b/bl/blunder/htdocs/m2repo","rsync_ssh","Ambrosi > Lucas","lambr...@users.sourceforge.net",, -- 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] Commented: (MAVENUPLOAD-2544) 'Sync my repo' request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186263#action_186263 ] Carlos Sanchez commented on MAVENUPLOAD-2544: - ssh ma...@rootdev.net asks for password, you need to configure the ssh key > 'Sync my repo' request > -- > > Key: MAVENUPLOAD-2544 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2544 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Damian Steer > > I believe you need the following: > "net.rootdev","ma...@rootdev.net:/home/maven/site/repo","rsync_ssh","Damian > Steer","pl...@mac.com",, > Hope this is all 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
[jira] Closed: (MAVENUPLOAD-2524) Project with Multiple groupID's need to be rsynced to central repo
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MAVENUPLOAD-2524.
---
Assignee: Carlos Sanchez
Resolution: Fixed
you were right, one entry for each top level groupId
> Project with Multiple groupID's need to be rsynced to central repo
> --
>
> Key: MAVENUPLOAD-2524
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2524
> Project: Maven Upload Requests
> Issue Type: Task
>Reporter: Mark Diggory
>Assignee: Carlos Sanchez
>
> Repo Maintainers,
> We have just successfully merged two OS projects (http://www.dspace.org,
> http://www.fedora-commons.org) into a new foundation
> (http://www.duraspace.org) and are looking to combine our maven local release
> repository
> ("org.dspace","mavens...@maven.dspace.org:/var/maven/release","rsync_ssh","DSpace
> Developers","dspace-de...@lists.sourceforge.net",,) for publishing
> artifacts from both projects into the maven central repository. What is the
> recommended practice in this area when one would want to have multiple
> groupId's rsync'd (org.dspace, org.fedora-commons, org.duraspace) from the
> same source repository? Do we need to request separate entries be added?
> ("org.duraspace","mavens...@maven.dspace.org:/var/maven/release","rsync_ssh","DSpace
> Developers","dspace-de...@lists.sourceforge.net",,)
> ("org.fedora-commons","mavens...@maven.dspace.org:/var/maven/release","rsync_ssh","DSpace
> Developers","dspace-de...@lists.sourceforge.net",,)
> ("org.dspace","mavens...@maven.dspace.org:/var/maven/release","rsync_ssh","DSpace
> Developers","dspace-de...@lists.sourceforge.net",,)
> Cheers,
> Mark Diggory
--
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] Closed: (MAVENUPLOAD-2544) 'Sync my repo' request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2544. --- Assignee: Carlos Sanchez Resolution: Fixed sorry, forget my last comment, everything looks fine > 'Sync my repo' request > -- > > Key: MAVENUPLOAD-2544 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2544 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Damian Steer >Assignee: Carlos Sanchez > > I believe you need the following: > "net.rootdev","ma...@rootdev.net:/home/maven/site/repo","rsync_ssh","Damian > Steer","pl...@mac.com",, > Hope this is all 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
[jira] Closed: (MAVENUPLOAD-2537) Upload bouncycastle bctsp
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2537. --- Assignee: Carlos Sanchez Resolution: Won't Fix MAVENUPLOAD-2479 is automatically syncing the org.bouncycastle group, so you just need to put the jars and poms in your repository. > Upload bouncycastle bctsp > - > > Key: MAVENUPLOAD-2537 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2537 > Project: Maven Upload Requests > Issue Type: New Feature >Reporter: Dave Syer >Assignee: Carlos Sanchez > > MAVENUPLOAD-2479 seems to have got us two other bouncy castles, but not this > one. -- 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] Closed: (MAVENUPLOAD-2535) JasperReports 3.5.3 upload
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2535. --- Assignee: Carlos Sanchez Resolution: Fixed > JasperReports 3.5.3 upload > -- > > Key: MAVENUPLOAD-2535 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2535 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Teodor Danciu >Assignee: Carlos Sanchez > > http://jasperreports.sf.net/maven/jasperreports-3.5.3-bundle.jar > http://sourceforge.net/projects/jasperreports > http://sourceforge.net/project/memberlist.php?group_id=36382 > Open Source Reporting Engine -- 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] Closed: (MAVENUPLOAD-2531) TestNG 5.10
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2531. --- Assignee: Carlos Sanchez Resolution: Fixed > TestNG 5.10 > --- > > Key: MAVENUPLOAD-2531 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2531 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Cedric Beust >Assignee: Carlos Sanchez > Attachments: testng-5.10-bundle.jar > > > I am the TestNG creator. -- 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] Closed: (MAVENUPLOAD-2529) Please update sync.csv for group org.jdtaus
[
http://jira.codehaus.org/browse/MAVENUPLOAD-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carlos Sanchez closed MAVENUPLOAD-2529.
---
Assignee: Carlos Sanchez
Resolution: Fixed
> Please update sync.csv for group org.jdtaus
> ---
>
> Key: MAVENUPLOAD-2529
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2529
> Project: Maven Upload Requests
> Issue Type: Task
>Reporter: Christian Schulte
>Assignee: Carlos Sanchez
>
> Hi,
> {code}
> http://svn.apache.org/viewvc/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv?revision=793783
> {code}
> currently contains the following line:
> {code}
> "org.jdtaus","rsync://repository.jdtaus.org/repository","rsync","Christian
> Schulte","c...@jdtaus.org",,
> {code}
> That repository has moved to Sourceforge. Please update that line to read:
> {code}
> "org.jdtaus","mavens...@web.sourceforge.net:/home/groups/j/jd/jdtaus/htdocs/central","rsync_ssh","Christian
> Schulte","schulte2...@users.sourceforge.net",,
> {code}
> I do not know if that mavensync user at sourceforge is available per default
> for any projects. If I need to setup something special with Sourceforge,
> please let me know.
> 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
[jira] Closed: (MAVENUPLOAD-2523) public key for openhms repository has been changed
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2523. --- Assignee: Carlos Sanchez Resolution: Fixed > public key for openhms repository has been changed > -- > > Key: MAVENUPLOAD-2523 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2523 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: james ahlborn >Assignee: Carlos Sanchez > > we recently had to rebuild the box on which the openhms repository lived, > open.hmsonline.com (serving the com.healthmarketscience package, see > MAVENUPLOAD-1842). thus, the RSA key for the box was changed, and the maven > sync script no longer functions (you get the output below). the public key > on the central repository sync box needs to be deleted so that the new public > key can be installed. thanks. > groupId: com.healthmarketscience > Error: > @@@ > @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @ > @@@ > The RSA host key for open.hmsonline.com has changed, > and the key for the according IP address 74.208.184.101 > is unknown. This could either mean that > DNS SPOOFING is happening or the IP address for the host > and its host key have changed at the same time. > @@@ > @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!@ > @@@ > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! > Someone could be eavesdropping on you right now (man-in-the-middle attack)! > It is also possible that the RSA host key has just been changed. > The fingerprint for the RSA key sent by the remote host is > 48:31:82:ab:ea:de:2d:e2:9a:61:61:97:1f:9e:2b:ad. > Please contact your system administrator. > Add correct host key in /home/maven/.ssh/known_hosts to get rid of this > message. > Offending key in /home/maven/.ssh/known_hosts:21 > RSA host key for open.hmsonline.com has changed and you have requested strict > checking. > Host key verification failed. > rsync: connection unexpectedly closed (0 bytes received so far) [receiver] > rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.3] > Error synchronizing metadata. Exit code: 255 -- 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] Closed: (MAVENUPLOAD-2517) jsch-0.1.42
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2517. --- Assignee: Carlos Sanchez Resolution: Fixed > jsch-0.1.42 > --- > > Key: MAVENUPLOAD-2517 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2517 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Joerg Schaible >Assignee: Carlos Sanchez > > JSch is a pure Java implementation of SSH2. > Version bump. -- 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] Closed: (MAVENUPLOAD-2527) Please sync with my repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2527. --- Assignee: Carlos Sanchez Resolution: Fixed > Please sync with my repo > > > Key: MAVENUPLOAD-2527 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2527 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Fabrizio Giudici >Assignee: Carlos Sanchez > > I'm Fabrizio Giudici, developer of TheseFoolishThings > (thesefoolishthings.kenai.com) and I want to sync my repo to the Central > Maven Repo. > "it.tidalwave.thesefoolishthings","/home/maven/repository-staging/to-ibiblio/maven-svn","svn","Fabrizio > > Giudici","fabrizio.giud...@tidalwave.it",,"https://kenai.com/svn/tidalwave~maven-repo/release/2/"; > > Proof of ownership for the tidalwave.it domain: http://www.tidalwave.it/people > 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
[jira] Commented: (MAVENUPLOAD-2533) upload svnkit 1.3.0.5847 (only jar as pom is already here)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=186270#action_186270 ] Carlos Sanchez commented on MAVENUPLOAD-2533: - I think this was not uploaded due to license > upload svnkit 1.3.0.5847 (only jar as pom is already here) > -- > > Key: MAVENUPLOAD-2533 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2533 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Olivier Lamy > > the jar is here : > http://people.apache.org/~olamy/bundles/svnkit-1.3.0.5847.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
[jira] Updated: (MNG-4286) Possible race condition in DefaultWagonManagerTest.testGetWagonMultithreaded()
[
http://jira.codehaus.org/browse/MNG-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MNG-4286:
Fix Version/s: 2.2.2
> Possible race condition in DefaultWagonManagerTest.testGetWagonMultithreaded()
> --
>
> Key: MNG-4286
> URL: http://jira.codehaus.org/browse/MNG-4286
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 2.2.1
>Reporter: John Casey
> Fix For: 2.2.2
>
>
> Periodically (especially when I'm trying to stage a release, but that may
> just be Maven's sense of humor) I'm seeing test failures that seem to be due
> to a race condition in the tearDown() functionality of
> DefaultWagonManagerTest.testGetWagonMultithreaded():
> {noformat}
> ---
> Test set: org.apache.maven.artifact.manager.DefaultWagonManagerTest
> ---
> Tests run: 14, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.817 sec
> <<< FAILURE!
> testGetWagonMultithreaded(org.apache.maven.artifact.manager.DefaultWagonManagerTest)
> Time elapsed: 0.338 sec <<< ERROR!
> java.util.NoSuchElementException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:844)
> at java.util.HashMap$ValueIterator.next(HashMap.java:871)
> at java.util.AbstractCollection.toArray(AbstractCollection.java:176)
> at java.util.ArrayList.(ArrayList.java:136)
> at
> org.codehaus.plexus.DefaultPlexusContainer.disposeAllComponents(DefaultPlexusContainer.java:828)
> at
> org.codehaus.plexus.DefaultPlexusContainer.dispose(DefaultPlexusContainer.java:803)
> at org.codehaus.plexus.PlexusTestCase.tearDown(PlexusTestCase.java:160)
> at junit.framework.TestCase.runBare(TestCase.java:130)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> 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.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
> 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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
> {noformat}
--
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: (MNG-4286) Possible race condition in DefaultWagonManagerTest.testGetWagonMultithreaded()
Possible race condition in DefaultWagonManagerTest.testGetWagonMultithreaded()
--
Key: MNG-4286
URL: http://jira.codehaus.org/browse/MNG-4286
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 2.2.1
Reporter: John Casey
Periodically (especially when I'm trying to stage a release, but that may just
be Maven's sense of humor) I'm seeing test failures that seem to be due to a
race condition in the tearDown() functionality of
DefaultWagonManagerTest.testGetWagonMultithreaded():
{noformat}
---
Test set: org.apache.maven.artifact.manager.DefaultWagonManagerTest
---
Tests run: 14, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.817 sec <<<
FAILURE!
testGetWagonMultithreaded(org.apache.maven.artifact.manager.DefaultWagonManagerTest)
Time elapsed: 0.338 sec <<< ERROR!
java.util.NoSuchElementException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:844)
at java.util.HashMap$ValueIterator.next(HashMap.java:871)
at java.util.AbstractCollection.toArray(AbstractCollection.java:176)
at java.util.ArrayList.(ArrayList.java:136)
at
org.codehaus.plexus.DefaultPlexusContainer.disposeAllComponents(DefaultPlexusContainer.java:828)
at
org.codehaus.plexus.DefaultPlexusContainer.dispose(DefaultPlexusContainer.java:803)
at org.codehaus.plexus.PlexusTestCase.tearDown(PlexusTestCase.java:160)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
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.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
{noformat}
--
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: (MJAR-126) Test Jar should not include src/main/* contents
Test Jar should not include src/main/* contents --- Key: MJAR-126 URL: http://jira.codehaus.org/browse/MJAR-126 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Paul Benedict My project creates a jar and a test-jar. The first one is obviously the main program, but the second one contains test harnesses for consumption with other projects. What is annoying is how the test-jar gets all the src/main/resources contents. I don't understand (or see why or how) it should receive anything from src/main/*. I actually think current behavior is incorrect; it should only get the contents from src/test/*. This is especially true since src/main/resources contains my Hibernate mappings. To prevent duplicate mappings at load time (when both jars are used), I have to exclude every resource in the test-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
[jira] Updated: (MJAR-126) Test Jar should not include src/main/* contents
[ http://jira.codehaus.org/browse/MJAR-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Benedict updated MJAR-126: --- Description: My project creates a jar and a test-jar. The first one is obviously the main program, but the second one contains test harnesses for consumption with other projects. What is annoying is how the test-jar gets all the src/main/resources contents. I don't understand (or see why or how) it should receive anything from src/main/. I actually think current behavior is incorrect; it should only get the contents from src/test/. This is especially true since src/main/resources contains my Hibernate mappings. To prevent duplicate mappings at load time (when both jars are used), I have to exclude every resource in the test-jar. was: My project creates a jar and a test-jar. The first one is obviously the main program, but the second one contains test harnesses for consumption with other projects. What is annoying is how the test-jar gets all the src/main/resources contents. I don't understand (or see why or how) it should receive anything from src/main/*. I actually think current behavior is incorrect; it should only get the contents from src/test/*. This is especially true since src/main/resources contains my Hibernate mappings. To prevent duplicate mappings at load time (when both jars are used), I have to exclude every resource in the test-jar. > Test Jar should not include src/main/* contents > --- > > Key: MJAR-126 > URL: http://jira.codehaus.org/browse/MJAR-126 > Project: Maven 2.x Jar Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Paul Benedict > > My project creates a jar and a test-jar. The first one is obviously the main > program, but the second one contains test harnesses for consumption with > other projects. What is annoying is how the test-jar gets all the > src/main/resources contents. I don't understand (or see why or how) it should > receive anything from src/main/. I actually think current behavior is > incorrect; it should only get the contents from src/test/. > This is especially true since src/main/resources contains my Hibernate > mappings. To prevent duplicate mappings at load time (when both jars are > used), I have to exclude every resource in the test-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
