[jira] Commented: (MNG-4238) Custom ArtifactHandler provided by build extension isn't used for project artifact
[ http://jira.codehaus.org/browse/MNG-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189472#action_189472 ] Gabriel Dogaru commented on MNG-4238: - I am using true. This happens if I use @requiresDependencyResolution test and my dependency has test scope. If I use compile for the dependency scope the artifact appears in the list of projects artifacts. > Custom ArtifactHandler provided by build extension isn't used for project > artifact > -- > > Key: MNG-4238 > URL: http://jira.codehaus.org/browse/MNG-4238 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.2.0 >Reporter: John Casey >Assignee: John Casey > Fix For: 2.2.1 > > > If I reference a build extension which provides a custom ArtifactHandler, > then set the packaging for the project so that it should use the custom > ArtifactHandler when it installs, I find that a default on-demand > ArtifactHandler is used instead. > Looking at this more closely, it appears that ArtifactHandlers brought in by > extensions (NOT plugins with extensions == true) are never registered with > the already-loaded ArtifactHandlerManager. Since Maven < 3.0 doesn't support > dynamic collections of components which would detect and include the new > extension handler, these handlers are never used. -- 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: (MDEPLOY-111) Deploy:deploy should target/pom-transformed.xml
Deploy:deploy should target/pom-transformed.xml --- Key: MDEPLOY-111 URL: http://jira.codehaus.org/browse/MDEPLOY-111 Project: Maven 2.x Deploy Plugin Issue Type: Improvement Components: deploy:deploy Affects Versions: 2.4 Reporter: Erlend Hamnaberg The installed artifact's POM should be used when deploying. This is useful if you have resolved all properties in the target/pom-transformed.xml, but cannot resolve the properties in the project POM. i.e for versions. -- 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-2586) Checksum failed
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189474#action_189474 ] Erik Martino Hansen commented on MAVENUPLOAD-2586: -- makes it impossible to use a local artifactory > Checksum failed > --- > > Key: MAVENUPLOAD-2586 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2586 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Erik Martino Hansen > > Downloading: > http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar > 511K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '1930b57270ff5b22e32f20cc895a07ee4a0e84e6'; remote = > 'a16d56474c1ac1496c89aa14cf28bbbd6b457bcc' - RETRYING > Downloading: > http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar > 511K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '1930b57270ff5b22e32f20cc895a07ee4a0e84e6'; remote = > 'a16d56474c1ac1496c89aa14cf28bbbd6b457bcc' - IGNORING -- 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-2586) Checksum failed
Checksum failed --- Key: MAVENUPLOAD-2586 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2586 Project: Maven Upload Requests Issue Type: Bug Reporter: Erik Martino Hansen Downloading: http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar 511K downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '1930b57270ff5b22e32f20cc895a07ee4a0e84e6'; remote = 'a16d56474c1ac1496c89aa14cf28bbbd6b457bcc' - RETRYING Downloading: http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar 511K downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '1930b57270ff5b22e32f20cc895a07ee4a0e84e6'; remote = 'a16d56474c1ac1496c89aa14cf28bbbd6b457bcc' - IGNORING -- 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: (MEV-636) Woodstox Checksum failed
[ http://jira.codehaus.org/browse/MEV-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MEV-636: - Summary: Woodstox Checksum failed (was: Checksum failed) > Woodstox Checksum failed > > > Key: MEV-636 > URL: http://jira.codehaus.org/browse/MEV-636 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Erik Martino Hansen > > Downloading: > http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar > 511K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '1930b57270ff5b22e32f20cc895a07ee4a0e84e6'; remote = > 'a16d56474c1ac1496c89aa14cf28bbbd6b457bcc' - RETRYING > Downloading: > http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar > 511K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '1930b57270ff5b22e32f20cc895a07ee4a0e84e6'; remote = > 'a16d56474c1ac1496c89aa14cf28bbbd6b457bcc' - IGNORING -- 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: (MEV-636) Checksum failed
[ http://jira.codehaus.org/browse/MEV-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter moved MAVENUPLOAD-2586 to MEV-636: --- Group ID: org.codehaus.woodstox Bundle URL: (was: http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar) Artifact ID: wstx-asl Version: 3.2.8 Workflow: jira (was: Maven New) Key: MEV-636 (was: MAVENUPLOAD-2586) Project: Maven Evangelism (was: Maven Upload Requests) > Checksum failed > --- > > Key: MEV-636 > URL: http://jira.codehaus.org/browse/MEV-636 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Erik Martino Hansen > > Downloading: > http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar > 511K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '1930b57270ff5b22e32f20cc895a07ee4a0e84e6'; remote = > 'a16d56474c1ac1496c89aa14cf28bbbd6b457bcc' - RETRYING > Downloading: > http://repo1.maven.org/maven2/org/codehaus/woodstox/wstx-asl/3.2.8/wstx-asl-3.2.8.jar > 511K downloaded > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = > '1930b57270ff5b22e32f20cc895a07ee4a0e84e6'; remote = > 'a16d56474c1ac1496c89aa14cf28bbbd6b457bcc' - IGNORING -- 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: (MNG-4334) maven core caches settings.xml
[
http://jira.codehaus.org/browse/MNG-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4334.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 3.0-alpha-3
Moved proxies into requests in
[r810444|http://svn.apache.org/viewvc?view=rev&revision=810444].
> maven core caches settings.xml
> --
>
> Key: MNG-4334
> URL: http://jira.codehaus.org/browse/MNG-4334
> Project: Maven 2
> Issue Type: Bug
> Components: Embedding
>Affects Versions: 3.0
>Reporter: Igor Fedorenko
>Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
>
> From https://issues.sonatype.org/browse/MNGECLIPSE-1553
> {quote}
> m2e does not always use current settings.xml. For example, changes to mirror
> configuration are not picked up until m2e restart.
> After initial investigation the problem comes from mirror information cached
> in DefaultMirrorBuilder. LegacyRepositorySystem#authentications and
> LegacyRepositorySystem#proxies will likely cause similar problem for
> authentication and proxy configuration respectively.
> Proper solution most will likely require changes to the way maven core
> handles configuration from settings.xml. Ideally, everything should be
> encapsulated in MavenExecutionRequest and all maven core components should be
> completely stateless.
> {quote}
--
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: (SUREFIRE-572) NPE on maven surefire report generation for testng
[ http://jira.codehaus.org/browse/SUREFIRE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189478#action_189478 ] Mircea Markus commented on SUREFIRE-572: to reproduce, unpack the tar.zip and run mvn:site within the root > NPE on maven surefire report generation for testng > -- > > Key: SUREFIRE-572 > URL: http://jira.codehaus.org/browse/SUREFIRE-572 > Project: Maven Surefire > Issue Type: Bug > Environment: mirce-markuss-macbook-pro:ispn mmarkus$ mvn -version > Apache Maven 2.2.0 (r788681; 2009-06-26 16:04:01+0300) > Java version: 1.5.0_19 > Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home > Default locale: en_US, platform encoding: MacRoman > OS name: "mac os x" version: "10.5.8" arch: "i386" Family: "unix" >Reporter: Mircea Markus > Attachments: mvn_npe_issue.tar.zip > > > java.lang.NullPointerException > at > org.apache.maven.plugins.surefire.report.ReportTestSuite.characters(ReportTestSuite.java:204) > at > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.characters(AbstractSAXParser.java:570) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanCDATASection(XMLDocumentFragmentScannerImpl.java:1119) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1740) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) > at > com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) > at > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:311) > at > org.apache.maven.plugins.surefire.report.ReportTestSuite.parse(ReportTestSuite.java:76) > at > org.apache.maven.plugins.surefire.report.SurefireReportParser.parseXMLReportFiles(SurefireReportParser.java:76) > at > org.apache.maven.plugins.surefire.report.SurefireReportGenerator.doGenerateReport(SurefireReportGenerator.java:57) > at > org.apache.maven.plugins.surefire.report.SurefireReportMojo.executeReport(SurefireReportMojo.java:115) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41) > 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.mainWithE
[jira] Created: (SUREFIRE-572) NPE on maven surefire report generation for testng
NPE on maven surefire report generation for testng -- Key: SUREFIRE-572 URL: http://jira.codehaus.org/browse/SUREFIRE-572 Project: Maven Surefire Issue Type: Bug Environment: mirce-markuss-macbook-pro:ispn mmarkus$ mvn -version Apache Maven 2.2.0 (r788681; 2009-06-26 16:04:01+0300) Java version: 1.5.0_19 Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x" version: "10.5.8" arch: "i386" Family: "unix" Reporter: Mircea Markus Attachments: mvn_npe_issue.tar.zip java.lang.NullPointerException at org.apache.maven.plugins.surefire.report.ReportTestSuite.characters(ReportTestSuite.java:204) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.characters(AbstractSAXParser.java:570) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanCDATASection(XMLDocumentFragmentScannerImpl.java:1119) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1740) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) at javax.xml.parsers.SAXParser.parse(SAXParser.java:311) at org.apache.maven.plugins.surefire.report.ReportTestSuite.parse(ReportTestSuite.java:76) at org.apache.maven.plugins.surefire.report.SurefireReportParser.parseXMLReportFiles(SurefireReportParser.java:76) at org.apache.maven.plugins.surefire.report.SurefireReportGenerator.doGenerateReport(SurefireReportGenerator.java:57) at org.apache.maven.plugins.surefire.report.SurefireReportMojo.executeReport(SurefireReportMojo.java:115) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41) 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) -- 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-427) Internal error when running mvn site with mvn 2.2.1
Internal error when running mvn site with mvn 2.2.1
---
Key: MSITE-427
URL: http://jira.codehaus.org/browse/MSITE-427
Project: Maven 2.x Site Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: r809302 mvn 2.2.1 jdk 5 and 6
Reporter: Vincent Siveton
Priority: Blocker
Try to call mvn site on the Doxia Site (which uses maven-site-plugin:2.1-snap)
{noformat}
#trunks\doxia\site>mvn site
[INFO] Scanning for projects...
[INFO]
[INFO] Building Doxia Site
[INFO]task-segment: [site]
[INFO]
-
this realm =
app0.child-container[org.apache.maven.doxia:doxia-maven-plugin:1.1.1]
urls[0] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/maven/doxia/d
oxia-maven-plugin/1.1.1/doxia-maven-plugin-1.1.1.jar
urls[1] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/maven/doxia/d
oxia-book/1.1.1/doxia-book-1.1.1.jar
urls[2] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/maven/doxia/d
oxia-core/1.1.1/doxia-core-1.1.1.jar
urls[3] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/codehaus/plexus/plex
us-utils/1.5.15/plexus-utils-1.5.15.jar
urls[4] = file:/C:/Documents and
Settings/Administrator/.m2/repository/xerces/xercesImpl/2.8.1/
xercesImpl-2.8.1.jar
urls[5] = file:/C:/Documents and
Settings/Administrator/.m2/repository/xml-apis/xml-apis/1.3.03
/xml-apis-1.3.03.jar
urls[6] = file:/C:/Documents and
Settings/Administrator/.m2/repository/commons-lang/commons-lan
g/2.4/commons-lang-2.4.jar
urls[7] = file:/C:/Documents and
Settings/Administrator/.m2/repository/commons-httpclient/commo
ns-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] = file:/C:/Documents and
Settings/Administrator/.m2/repository/commons-logging/commons-
logging/1.0.4/commons-logging-1.0.4.jar
urls[9] = file:/C:/Documents and
Settings/Administrator/.m2/repository/commons-codec/commons-co
dec/1.2/commons-codec-1.2.jar
urls[10] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/maven/doxia/
doxia-module-apt/1.1.1/doxia-module-apt-1.1.1.jar
urls[11] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/maven/doxia/
doxia-module-docbook-simple/1.1.1/doxia-module-docbook-simple-1.1.1.jar
urls[12] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/maven/doxia/
doxia-module-itext/1.1.1/doxia-module-itext-1.1.1.jar
urls[13] = file:/C:/Documents and
Settings/Administrator/.m2/repository/com/lowagie/itext/1.4/i
text-1.4.jar
urls[14] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/maven/doxia/
doxia-module-latex/1.1.1/doxia-module-latex-1.1.1.jar
urls[15] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/maven/doxia/
doxia-module-xdoc/1.1.1/doxia-module-xdoc-1.1.1.jar
urls[16] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/maven/doxia/
doxia-module-xhtml/1.1.1/doxia-module-xhtml-1.1.1.jar
urls[17] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/codehaus/plexus/ple
xus-i18n/1.0-beta-6/plexus-i18n-1.0-beta-6.jar
urls[18] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/maven/shared
/maven-doxia-tools/1.0.1/maven-doxia-tools-1.0.1.jar
urls[19] = file:/C:/Documents and
Settings/Administrator/.m2/repository/commons-io/commons-io/1
.4/commons-io-1.4.jar
urls[20] = file:/C:/Documents and
Settings/Administrator/.m2/repository/org/apache/maven/doxia/
doxia-decoration-model/1.0-alpha-11/doxia-decoration-model-1.0-alpha-11.jar
Number of imports: 10
import: org.codehaus.classworlds.en...@a6c57a42
import: org.codehaus.classworlds.en...@12f43f3b
import: org.codehaus.classworlds.en...@20025374
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@92758522
import: org.codehaus.classworlds.en...@ebf2705b
import: org.codehaus.classworlds.en...@bb25e54
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
this realm = plexus.core
urls[0] =
file:/D:/java/apache.org/maven/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar
Number of imports: 10
import: org.codehaus.classworlds.en...@a6c57a42
import: org.codehaus.classworlds.en...@12f43f3b
import: org.codehaus.classworlds.en...@20025374
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@92758522
import: org.codehaus.classworlds.en...@ebf2705b
import: org.codehaus.classworlds.en...@bb25e54
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
---
[jira] Updated: (MSITE-427) Internal error when running mvn site with mvn 2.2.1
[
http://jira.codehaus.org/browse/MSITE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated MSITE-427:
--
Description:
Try to call mvn site on the Doxia Site (which uses maven-site-plugin:2.1-snap)
{noformat}
#trunks\doxia\site>mvn site
[INFO] Scanning for projects...
[INFO]
[INFO] Building Doxia Site
[INFO]task-segment: [site]
[INFO]
-
this realm =
app0.child-container[org.apache.maven.doxia:doxia-maven-plugin:1.1.1]
urls[0] =
file://.m2/repository/org/apache/maven/doxia/doxia-maven-plugin/1.1.1/doxia-maven-plugin-1.1.1.jar
urls[1] =
file://.m2/repository/org/apache/maven/doxia/doxia-book/1.1.1/doxia-book-1.1.1.jar
urls[2] =
file://.m2/repository/org/apache/maven/doxia/doxia-core/1.1.1/doxia-core-1.1.1.jar
urls[3] =
file://.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar
urls[4] = file://.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
urls[5] = file://.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar
urls[6] =
file://.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
urls[7] =
file://.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar
urls[8] =
file://.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
urls[9] =
file://.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
urls[10] =
file://.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.1/doxia-module-apt-1.1.1.jar
urls[11] =
file://.m2/repository/org/apache/maven/doxia/doxia-module-docbook-simple/1.1.1/doxia-module-docbook-simple-1.1.1.jar
urls[12] =
file://.m2/repository/org/apache/maven/doxia/doxia-module-itext/1.1.1/doxia-module-itext-1.1.1.jar
urls[13] = file://.m2/repository/com/lowagie/itext/1.4/itext-1.4.jar
urls[14] =
file://.m2/repository/org/apache/maven/doxia/doxia-module-latex/1.1.1/doxia-module-latex-1.1.1.jar
urls[15] =
file://.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.1/doxia-module-xdoc-1.1.1.jar
urls[16] =
file://.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.1/doxia-module-xhtml-1.1.1.jar
urls[17] =
file://.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-6/plexus-i18n-1.0-beta-6.jar
urls[18] =
file://.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.0.1/maven-doxia-tools-1.0.1.jar
urls[19] =
file://.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
urls[20] =
file://.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0-alpha-11/doxia-decoration-model-1.0-alpha-11.jar
Number of imports: 10
import: org.codehaus.classworlds.en...@a6c57a42
import: org.codehaus.classworlds.en...@12f43f3b
import: org.codehaus.classworlds.en...@20025374
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@92758522
import: org.codehaus.classworlds.en...@ebf2705b
import: org.codehaus.classworlds.en...@bb25e54
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
this realm = plexus.core
urls[0] = file://apache-maven-2.2.1/lib/maven-2.2.1-uber.jar
Number of imports: 10
import: org.codehaus.classworlds.en...@a6c57a42
import: org.codehaus.classworlds.en...@12f43f3b
import: org.codehaus.classworlds.en...@20025374
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@92758522
import: org.codehaus.classworlds.en...@ebf2705b
import: org.codehaus.classworlds.en...@bb25e54
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
-
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.doxia:doxia-maven-
plugin:1.1.1:render-books': Unable to load the mojo
'org.apache.maven.doxia:doxia-maven-plugin:
1.1.1:render-books' in the plugin 'org.apache.maven.doxia:doxia-maven-plugin'.
A required class
is missing: hidden/org/codehaus/plexus/interpolation/ValueSource
{noformat}
Using mvn 2.2.0 seems to work
Sounds be related to PLXUTILS-117
BTW 2 questions on the realms:
* Why Doxia 1.1.1 in the realms? The site-plugin:2.1-snap (r810450) specifies
1.1.2-SNAPSHOT!
* Why doxia-decoration-model-1.0-alpha-11
was:
Try to call mvn site on the Doxia Site (which uses maven-site-plugin:2.1-snap)
{noformat}
#trunks\doxia\site>mvn site
[INFO] Scanning for projects...
[INFO] -
[jira] Created: (MCHANGES-175) SSLHandshakeException when accessing Jira using https
SSLHandshakeException when accessing Jira using https - Key: MCHANGES-175 URL: http://jira.codehaus.org/browse/MCHANGES-175 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira-report Affects Versions: 2.1 Reporter: Krishna Pothula Priority: Blocker We have an intranet Jira setup with https to have integration with LDAP. The certificate used is an internal one not issued by any CA. While accessing this repository jira-report throws below Exception: --- javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1476) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:847) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:815) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1025) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:619) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:827) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1975) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324) at org.apache.maven.plugin.jira.JiraHelper.getPidFromJira(JiraHelper.java:55) at org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:363) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:245) -- 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: (MCHANGES-175) SSLHandshakeException when accessing Jira using https
[ http://jira.codehaus.org/browse/MCHANGES-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189484#action_189484 ] Krishna Pothula commented on MCHANGES-175: -- And the root cause is... Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:236) at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:194) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:216) > SSLHandshakeException when accessing Jira using https > - > > Key: MCHANGES-175 > URL: http://jira.codehaus.org/browse/MCHANGES-175 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira-report >Affects Versions: 2.1 >Reporter: Krishna Pothula >Priority: Blocker > > We have an intranet Jira setup with https to have integration with LDAP. The > certificate used is an internal one not issued by any CA. > While accessing this repository jira-report throws below Exception: > --- > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target > at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1476) > at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174) > at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168) > at > com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:847) > at > com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106) > at > com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495) > at > com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:815) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1025) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:619) > at > com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) > at > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) > at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) > at > org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:827) > at > org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1975) > at > org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) > at > org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) > at > org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) > at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) > at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324) > at > org.apache.maven.plugin.jira.JiraHelper.getPidFromJira(JiraHelper.java:55) > at > org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:363) > at > org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:245) > -- 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] Deleted: (MSITE-427) Internal error when running mvn site with mvn 2.2.1
[
http://jira.codehaus.org/browse/MSITE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton deleted MSITE-427:
--
> Internal error when running mvn site with mvn 2.2.1
> ---
>
> Key: MSITE-427
> URL: http://jira.codehaus.org/browse/MSITE-427
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Environment: r809302 mvn 2.2.1 jdk 5 and 6
>Reporter: Vincent Siveton
>Priority: Blocker
>
> Try to call mvn site on the Doxia Site (which uses maven-site-plugin:2.1-snap)
> {noformat}
> #trunks\doxia\site>mvn site
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Doxia Site
> [INFO]task-segment: [site]
> [INFO]
>
> -
> this realm =
> app0.child-container[org.apache.maven.doxia:doxia-maven-plugin:1.1.1]
> urls[0] =
> file://.m2/repository/org/apache/maven/doxia/doxia-maven-plugin/1.1.1/doxia-maven-plugin-1.1.1.jar
> urls[1] =
> file://.m2/repository/org/apache/maven/doxia/doxia-book/1.1.1/doxia-book-1.1.1.jar
> urls[2] =
> file://.m2/repository/org/apache/maven/doxia/doxia-core/1.1.1/doxia-core-1.1.1.jar
> urls[3] =
> file://.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar
> urls[4] =
> file://.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar
> urls[5] =
> file://.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar
> urls[6] =
> file://.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
> urls[7] =
> file://.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar
> urls[8] =
> file://.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
> urls[9] =
> file://.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar
> urls[10] =
> file://.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.1/doxia-module-apt-1.1.1.jar
> urls[11] =
> file://.m2/repository/org/apache/maven/doxia/doxia-module-docbook-simple/1.1.1/doxia-module-docbook-simple-1.1.1.jar
> urls[12] =
> file://.m2/repository/org/apache/maven/doxia/doxia-module-itext/1.1.1/doxia-module-itext-1.1.1.jar
> urls[13] = file://.m2/repository/com/lowagie/itext/1.4/itext-1.4.jar
> urls[14] =
> file://.m2/repository/org/apache/maven/doxia/doxia-module-latex/1.1.1/doxia-module-latex-1.1.1.jar
> urls[15] =
> file://.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.1/doxia-module-xdoc-1.1.1.jar
> urls[16] =
> file://.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.1/doxia-module-xhtml-1.1.1.jar
> urls[17] =
> file://.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-6/plexus-i18n-1.0-beta-6.jar
> urls[18] =
> file://.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.0.1/maven-doxia-tools-1.0.1.jar
> urls[19] =
> file://.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
> urls[20] =
> file://.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.0-alpha-11/doxia-decoration-model-1.0-alpha-11.jar
> Number of imports: 10
> import: org.codehaus.classworlds.en...@a6c57a42
> import: org.codehaus.classworlds.en...@12f43f3b
> import: org.codehaus.classworlds.en...@20025374
> import: org.codehaus.classworlds.en...@f8e44ca4
> import: org.codehaus.classworlds.en...@92758522
> import: org.codehaus.classworlds.en...@ebf2705b
> import: org.codehaus.classworlds.en...@bb25e54
> import: org.codehaus.classworlds.en...@bece5185
> import: org.codehaus.classworlds.en...@3fee8e37
> import: org.codehaus.classworlds.en...@3fee19d8
> this realm = plexus.core
> urls[0] = file://apache-maven-2.2.1/lib/maven-2.2.1-uber.jar
> Number of imports: 10
> import: org.codehaus.classworlds.en...@a6c57a42
> import: org.codehaus.classworlds.en...@12f43f3b
> import: org.codehaus.classworlds.en...@20025374
> import: org.codehaus.classworlds.en...@f8e44ca4
> import: org.codehaus.classworlds.en...@92758522
> import: org.codehaus.classworlds.en...@ebf2705b
> import: org.codehaus.classworlds.en...@bb25e54
> import: org.codehaus.classworlds.en...@bece5185
> import: org.codehaus.classworlds.en...@3fee8e37
> import: org.codehaus.classworlds.en...@3fee19d8
> -
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Internal error in the plugin manager executing goal
> 'org.apache.maven.doxia:doxia-maven-
> plugin:1.1.1:render-books': Unable to load the mojo
> 'org.apache.maven.doxia:doxia-maven-plugin:
> 1.1.1:render-bo
[jira] Commented: (MCHANGES-175) SSLHandshakeException when accessing Jira using https
[ http://jira.codehaus.org/browse/MCHANGES-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189489#action_189489 ] Krishna Pothula commented on MCHANGES-175: -- Thank you for the quick response. I can add that cert to my local trust store but we have Hudson where we actually do the builds and site documentation generation. Most of the users dont have permissions to do that on CI server. I have been trying to use the jira-report from quite sometime and I could not because of this error. I currently found a solution and am testing it by building changes-plugin locally. It seems to work fine. Solution is to use a Custom SocketFactory with HttpClient. http://hc.apache.org/httpclient-3.x/sslguide.html I am planning to submit a patch for this bug by tomorrow. > SSLHandshakeException when accessing Jira using https > - > > Key: MCHANGES-175 > URL: http://jira.codehaus.org/browse/MCHANGES-175 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira-report >Affects Versions: 2.1 >Reporter: Krishna Pothula >Priority: Blocker > > We have an intranet Jira setup with https to have integration with LDAP. The > certificate used is an internal one not issued by any CA. > While accessing this repository jira-report throws below Exception: > --- > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target > at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1476) > at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174) > at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168) > at > com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:847) > at > com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106) > at > com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495) > at > com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:815) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1025) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:619) > at > com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) > at > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) > at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) > at > org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:827) > at > org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1975) > at > org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) > at > org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) > at > org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) > at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) > at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324) > at > org.apache.maven.plugin.jira.JiraHelper.getPidFromJira(JiraHelper.java:55) > at > org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:363) > at > org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:245) > -- 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: (MPDF-31) LinkageError using JDK6
LinkageError using JDK6
---
Key: MPDF-31
URL: http://jira.codehaus.org/browse/MPDF-31
Project: Maven 2.x PDF Plugin
Issue Type: Bug
Affects Versions: 1.1
Environment: mvn 2.1 or later, jdk 6
Reporter: Vincent Siveton
{noformat}
#mvn -version
Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.6.0_15
Java home: jdk1.6.0_15\jre
Default locale: fr_CA, platform encoding: Cp1252
OS name: "windows xp" version: "5.2" arch: "x86" Family: "windows"
{noformat}
{noformat}
#mvn site
...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] loader constraint violation in interface itable initialization: when
resolving method "o
rg.apache.maven.doxia.sink.AbstractSink.enableLogging(Lorg/apache/maven/doxia/logging/Log;)V"
t
he class loader (instance of org/codehaus/classworlds/RealmClassLoader) of the
current class, o
rg/apache/maven/plugins/pdf/PdfMojo$PdfSink, and the class loader (instance of
org/codehaus/cla
ssworlds/RealmClassLoader) for interface
org/apache/maven/doxia/logging/LogEnabled have differe
nt Class objects for the type org/apache/maven/doxia/logging/Log used in the
signature
[INFO]
...
{noformat}
BUT using JDK 1.5 no error when running mvn site:
{noformat}
#mvn -version
Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.5.0_18
Java home: dk1.5.0_18\jre
Default locale: fr_CA, platform encoding: Cp1252
OS name: "windows xp" version: "5.2" arch: "x86" Family: "windows"
{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] Updated: (MPDF-31) LinkageError using JDK6
[
http://jira.codehaus.org/browse/MPDF-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated MPDF-31:
Attachment: myapp.zip
simple project
> LinkageError using JDK6
> ---
>
> Key: MPDF-31
> URL: http://jira.codehaus.org/browse/MPDF-31
> Project: Maven 2.x PDF Plugin
> Issue Type: Bug
>Affects Versions: 1.1
> Environment: mvn 2.1 or later, jdk 6
>Reporter: Vincent Siveton
> Attachments: myapp.zip
>
>
> {noformat}
> #mvn -version
> Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
> Java version: 1.6.0_15
> Java home: jdk1.6.0_15\jre
> Default locale: fr_CA, platform encoding: Cp1252
> OS name: "windows xp" version: "5.2" arch: "x86" Family: "windows"
> {noformat}
> {noformat}
> #mvn site
> ...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] loader constraint violation in interface itable initialization: when
> resolving method "o
> rg.apache.maven.doxia.sink.AbstractSink.enableLogging(Lorg/apache/maven/doxia/logging/Log;)V"
> t
> he class loader (instance of org/codehaus/classworlds/RealmClassLoader) of
> the current class, o
> rg/apache/maven/plugins/pdf/PdfMojo$PdfSink, and the class loader (instance
> of org/codehaus/cla
> ssworlds/RealmClassLoader) for interface
> org/apache/maven/doxia/logging/LogEnabled have differe
> nt Class objects for the type org/apache/maven/doxia/logging/Log used in the
> signature
> [INFO]
>
> ...
> {noformat}
> BUT using JDK 1.5 no error when running mvn site:
> {noformat}
> #mvn -version
> Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
> Java version: 1.5.0_18
> Java home: dk1.5.0_18\jre
> Default locale: fr_CA, platform encoding: Cp1252
> OS name: "windows xp" version: "5.2" arch: "x86" Family: "windows"
> {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] Commented: (MNG-4324) Add the ability to launch a reactor build with -amd or -am options from a submodule
[
http://jira.codehaus.org/browse/MNG-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189492#action_189492
]
jieryn commented on MNG-4324:
-
I solved this problem in a very specific way for my use case
(maven-reactor-plugin) with the following Perl tidbit:
{code}
#!/usr/bin/env perl
# jie...@gmail.com
use strict;
use warnings;
use XML::XPath;
my $xp = XML::XPath->new( filename => 'pom.xml' );
my $packaging = $xp->findvalue('/project/packaging') || 'jar';
die 'Packaging is POM, nothing to do.' if $packaging eq 'pom';
my $groupId= $xp->findvalue('/project/groupId');
my $artifactId = $xp->findvalue('/project/artifactId');
chdir '..' or die 'Could not CHDIR to parent.';
system "mvn reactor:make -Dmake.artifacts=$groupId:$artifactId"
{code}
Maybe it will help someone out there.
> Add the ability to launch a reactor build with -amd or -am options from a
> submodule
> ---
>
> Key: MNG-4324
> URL: http://jira.codehaus.org/browse/MNG-4324
> Project: Maven 2
> Issue Type: New Feature
> Components: Command Line, Reactor and workspace
>Affects Versions: 2.2.1
>Reporter: Arnaud Heritier
>
> This is an idea comming from this thread :
> http://www.nabble.com/Hibernate-feedback-about-Maven-usage.-td25137434.html
> And more particularly from this blog post :
> http://relation.to/12116.lace
> The idea is to not have to set the -pl option, and use the current module for
> it. Maven will have to search the reactor through parents to construct and
> launch the build.
--
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: (MCHANGES-175) SSLHandshakeException when accessing Jira using https
[ http://jira.codehaus.org/browse/MCHANGES-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189485#action_189485 ] Benjamin Bentmann commented on MCHANGES-175: That doesn't look like an issue in the plugin itself but usually means that the server uses a certificate that is not part of your JDK's trust store. See the [keytool|http://java.sun.com/javase/6/docs/technotes/tools/windows/keytool.html] help for details on how to import either the certificate of the server or the certificates of the issuers of the server certificate. > SSLHandshakeException when accessing Jira using https > - > > Key: MCHANGES-175 > URL: http://jira.codehaus.org/browse/MCHANGES-175 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira-report >Affects Versions: 2.1 >Reporter: Krishna Pothula >Priority: Blocker > > We have an intranet Jira setup with https to have integration with LDAP. The > certificate used is an internal one not issued by any CA. > While accessing this repository jira-report throws below Exception: > --- > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target > at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1476) > at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174) > at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168) > at > com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:847) > at > com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106) > at > com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495) > at > com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:815) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1025) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:619) > at > com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) > at > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) > at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) > at > org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:827) > at > org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1975) > at > org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) > at > org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) > at > org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) > at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) > at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324) > at > org.apache.maven.plugin.jira.JiraHelper.getPidFromJira(JiraHelper.java:55) > at > org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:363) > at > org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:245) > -- 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: (MCHANGES-175) SSLHandshakeException when accessing Jira using https
[ http://jira.codehaus.org/browse/MCHANGES-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishna Pothula updated MCHANGES-175: - Attachment: patch_MCHANGES-175.diff Attached is the Patch that'll fix the bug. In this patch a new plugin property is introduced "acceptUntrustedCert". If this property is set to true then this plugin will work with self-signed or untrusted SSL certificates. I sincerely hope this will be added to the 2.2 version of this plugin. > SSLHandshakeException when accessing Jira using https > - > > Key: MCHANGES-175 > URL: http://jira.codehaus.org/browse/MCHANGES-175 > Project: Maven 2.x Changes Plugin > Issue Type: Bug > Components: jira-report >Affects Versions: 2.1 >Reporter: Krishna Pothula >Priority: Blocker > Attachments: patch_MCHANGES-175.diff > > > We have an intranet Jira setup with https to have integration with LDAP. The > certificate used is an internal one not issued by any CA. > While accessing this repository jira-report throws below Exception: > --- > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target > at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1476) > at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174) > at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168) > at > com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:847) > at > com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106) > at > com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495) > at > com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:815) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1025) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:619) > at > com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) > at > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) > at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) > at > org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:827) > at > org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1975) > at > org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) > at > org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) > at > org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) > at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) > at > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324) > at > org.apache.maven.plugin.jira.JiraHelper.getPidFromJira(JiraHelper.java:55) > at > org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:363) > at > org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:245) > -- 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: (MDEP-184) Download a dependency without pom
[ http://jira.codehaus.org/browse/MDEP-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MDEP-184. Resolution: Fixed Fix Version/s: 2.1 > Download a dependency without pom > - > > Key: MDEP-184 > URL: http://jira.codehaus.org/browse/MDEP-184 > Project: Maven 2.x Dependency Plugin > Issue Type: New Feature >Affects Versions: 2.0 >Reporter: creyle >Assignee: Brian Fox > Fix For: 2.1 > > > I want a new goal like > "mvn dependency:get -DgroupId=... -DartifactId=... -Dversion=... > -Dclassifier=..." > This goal is very helpful to have local dependencies managed by maven, > especially for us in such an imperfect world that not every project has > adopted maven. > By running the above command, the corresponding artifact would be downloaded > into local maven repository. > groupId -- required > artifactId -- required > version -- optional, download the latest release if omitted > classifier -- optional, this should be artifact specific, some may require a > classifier, some may not. > The idea is from the discussion in the maven users list, thread > http://www.nabble.com/-M2--Manually-download-artifact--td19949345.html > Thanks Wendy for the idea -- 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: (MECLIPSE-459) missing artifact references with pde mode enabled
[
http://jira.codehaus.org/browse/MECLIPSE-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189528#action_189528
]
Eugene Voytitsky commented on MECLIPSE-459:
---
Maybe plugin's author had reasons for implementing such a skipping
but nowadays the more and more maven artifacts became osgi-fied,
so skipping osgi-bundled artifact from being included in MANIFEST classpath
(and skipping it beign linked to project as linkedResource)
looks as unpractical.
Currently there are at least 2 places in src where fixes should be applied:
already mentioned EclipseClasspathWriter.java and also
EclipseProjectWriter.java around the code:
if ( dep.isAddedToClasspath() && !dep.isProvided() && !dep.isReferencedProject()
&& !dep.isTestDependency() && !dep.isOsgiBundle() )
{
Actually it would be great to have ability to specify whether include osgi
bundles or not in plugin configuration options.
Thanks.
> missing artifact references with pde mode enabled
> -
>
> Key: MECLIPSE-459
> URL: http://jira.codehaus.org/browse/MECLIPSE-459
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath), PDE support
>Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.5.1
> Environment: Maven version: 2.0.9
> Java version: 1.5.0_11
> OS name: "linux" version: "2.6.15-51-686" arch: "i386" Family: "unix"
>Reporter: Benjamin Voigt
>Priority: Critical
> Attachments: pde_dep_missing.zip
>
>
> Some artifacts are not referenced after executing mvn eclipse:eclipse and
> having pde mode enabled. The strange thing is, that this does only happen for
> particluar versions of an artifact.
> Two artifacts that I found with this problem are jetty (org.mortbay.jetty)
> and slf4j-log4j12 (org.slf4j-log4j12). Jetty versions beyond 6.1.5 work with
> pde enabled, higher versions do not. Same for slf4j-log4j12 versions =< 1.1.0.
> Attached is an example project demonstrating the problem. Turn pde mode
> on/off in the pom and execute mvn eclipse:eclipse.
--
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: (MDEPLOY-112) deployed snapshot name has different build numbers for multiple artifacts of the same build
deployed snapshot name has different build numbers for multiple artifacts of the same build --- Key: MDEPLOY-112 URL: http://jira.codehaus.org/browse/MDEPLOY-112 Project: Maven 2.x Deploy Plugin Issue Type: Bug Components: deploy:deploy Affects Versions: 2.2.1 Environment: windows xp Reporter: Gabriel Dogaru I have a module that deploys 2 artifacts,1 jar and 1 of them is custom type. The build number from the snapshot name is different for the 2 (in the repository). It get incremented every time an artifact is deployed. When I try to make a local build it searches for the highest build number, and tries to bring both the artifacts with the latest build number but only one of them has that number. I found a workaround for this by false for the snapshotRepository. -- 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: (MDEPLOY-112) deployed snapshot name has different build numbers for multiple artifacts of the same build
[ http://jira.codehaus.org/browse/MDEPLOY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189541#action_189541 ] Benjamin Bentmann commented on MDEPLOY-112: --- An example POM or at least the relevant lines from the log output where Maven prints what it deploys would be helpful. > deployed snapshot name has different build numbers for multiple artifacts of > the same build > --- > > Key: MDEPLOY-112 > URL: http://jira.codehaus.org/browse/MDEPLOY-112 > Project: Maven 2.x Deploy Plugin > Issue Type: Bug > Components: deploy:deploy >Affects Versions: 2.2.1 > Environment: windows xp >Reporter: Gabriel Dogaru > > I have a module that deploys 2 artifacts,1 jar and 1 of them is custom type. > The build number from the snapshot name is different for the 2 (in the > repository). It get incremented every time an artifact is deployed. When I > try to make a local build it searches for the highest build number, and tries > to bring both the artifacts with the latest build number but only one of them > has that number. > I found a workaround for this by false for > the snapshotRepository. -- 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: (MGPG-16) Allow to configure homedir for gpg invocation
Allow to configure homedir for gpg invocation - Key: MGPG-16 URL: http://jira.codehaus.org/browse/MGPG-16 Project: Maven 2.x GPG Plugin Issue Type: New Feature Affects Versions: 1.0-alpha-4 Reporter: Benjamin Bentmann Exposal of gpg's [--homedir option|http://www.gnupg.org/documentation/manuals/gnupg/GPG-Configuration-Options.html#index-homedir-175] would enable more control of the employed keyrings. In particular, this enables us to run automated tests against the plugin using a predefined keyring from the project sources. -- 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: (MGPG-16) Allow to configure homedir for gpg invocation
[ http://jira.codehaus.org/browse/MGPG-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MGPG-16. - Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 1.0 Added in [r810636|http://svn.apache.org/viewvc?view=rev&revision=810636]. > Allow to configure homedir for gpg invocation > - > > Key: MGPG-16 > URL: http://jira.codehaus.org/browse/MGPG-16 > Project: Maven 2.x GPG Plugin > Issue Type: New Feature >Affects Versions: 1.0-alpha-4 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann > Fix For: 1.0 > > > Exposal of gpg's [--homedir > option|http://www.gnupg.org/documentation/manuals/gnupg/GPG-Configuration-Options.html#index-homedir-175] > would enable more control of the employed keyrings. In particular, this > enables us to run automated tests against the plugin using a predefined > keyring from the project sources. -- 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: (MGPG-13) NPE if no config defined
[ http://jira.codehaus.org/browse/MGPG-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MGPG-13. - Assignee: Benjamin Bentmann Resolution: Incomplete Couldn't reproduce with the little information provided. > NPE if no config defined > > > Key: MGPG-13 > URL: http://jira.codehaus.org/browse/MGPG-13 > Project: Maven 2.x GPG Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-4 >Reporter: Geert Schuring >Assignee: Benjamin Bentmann > > If no special configuration has been set, a NPE will be thrown without any > error message. -- 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: (MDEPLOY-112) deployed snapshot name has different build numbers for multiple artifacts of the same build
[
http://jira.codehaus.org/browse/MDEPLOY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189575#action_189575
]
Gabriel Dogaru commented on MDEPLOY-112:
[04:41:21]: [INFO] [deploy:deploy {execution: default-deploy}]
[04:41:21]: [INFO] No primary artifact to deploy, deploy attached artifacts
instead.
[04:41:21]: [INFO] Retrieving previous build number from snapshots_repo
[04:41:21]: Uploading:
file:build/m2repository/snapshots/myapp/testutils/11.6-SNAPSHOT/testutils-11.6-20090902.084121-24.jar
[04:41:21]: 78K uploaded (testutils-11.6-20090902.084121-24.jar)
[04:41:21]: [INFO] Retrieving previous metadata from snapshots_repo
[04:41:21]: [INFO] Uploading repository metadata for: 'artifact myapptestutils'
[04:41:21]: [INFO] Retrieving previous metadata from snapshots_repo
[04:41:21]: [INFO] Uploading repository metadata for: 'snapshot
myapp:testutils:11.6-SNAPSHOT'
[04:41:21]: [INFO] Retrieving previous build number from snapshots_repo
[04:41:21]: Uploading:
file:build/m2repository/snapshots/myapp/testutils/11.6-SNAPSHOT/testutils-11.6-20090902.084121-25.resource
[04:41:21]: 2K uploaded (testutils-11.6-20090902.084121-25.resource)
[04:41:21]: [INFO] Retrieving previous metadata from snapshots_build
[04:41:22]: [INFO] Uploading repository metadata for: 'artifact myapp:testutils'
[04:41:22]: [INFO] Retrieving previous metadata from snapshots_repo
[04:41:22]: [INFO] Uploading repository metadata for: 'snapshot
myapp:testutils:11.6-SNAPSHOT'
[04:41:22]: [INFO]
[04:41:22]: [INFO] BUILD SUCCESSFUL
> deployed snapshot name has different build numbers for multiple artifacts of
> the same build
> ---
>
> Key: MDEPLOY-112
> URL: http://jira.codehaus.org/browse/MDEPLOY-112
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
>Affects Versions: 2.2.1
> Environment: windows xp
>Reporter: Gabriel Dogaru
>
> I have a module that deploys 2 artifacts,1 jar and 1 of them is custom type.
> The build number from the snapshot name is different for the 2 (in the
> repository). It get incremented every time an artifact is deployed. When I
> try to make a local build it searches for the highest build number, and tries
> to bring both the artifacts with the latest build number but only one of them
> has that number.
> I found a workaround for this by false for
> the snapshotRepository.
--
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] Issue Comment Edited: (MDEPLOY-112) deployed snapshot name has different build numbers for multiple artifacts of the same build
[
http://jira.codehaus.org/browse/MDEPLOY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189575#action_189575
]
Gabriel Dogaru edited comment on MDEPLOY-112 at 9/2/09 1:52 PM:
[04:41:21]: [INFO] [deploy:deploy {execution: default-deploy}]
[04:41:21]: [INFO] No primary artifact to deploy, deploy attached artifacts
instead.
[04:41:21]: [INFO] Retrieving previous build number from snapshots_repo
[04:41:21]: Uploading:
file:build/m2repository/snapshots/myapp/testutils/11.6-SNAPSHOT/testutils-11.6-20090902.084121-24.jar
[04:41:21]: 78K uploaded (testutils-11.6-20090902.084121-24.jar)
[04:41:21]: [INFO] Retrieving previous metadata from snapshots_repo
[04:41:21]: [INFO] Uploading repository metadata for: 'artifact myapptestutils'
[04:41:21]: [INFO] Retrieving previous metadata from snapshots_repo
[04:41:21]: [INFO] Uploading repository metadata for: 'snapshot
myapp:testutils:11.6-SNAPSHOT'
[04:41:21]: [INFO] Retrieving previous build number from snapshots_repo
[04:41:21]: Uploading:
file:build/m2repository/snapshots/myapp/testutils/11.6-SNAPSHOT/testutils-11.6-20090902.084121-25.resource
[04:41:21]: 2K uploaded (testutils-11.6-20090902.084121-25.resource)
[04:41:21]: [INFO] Retrieving previous metadata from snapshots_build
[04:41:22]: [INFO] Uploading repository metadata for: 'artifact myapp:testutils'
[04:41:22]: [INFO] Retrieving previous metadata from snapshots_repo
[04:41:22]: [INFO] Uploading repository metadata for: 'snapshot
myapp:testutils:11.6-SNAPSHOT'
[04:41:22]: [INFO]
[04:41:22]: [INFO] BUILD SUCCESSFUL
I am using project.addAttachedArtifact(artifact); in my mojo to attach the
artifact
Pom for distribution management:
.
snapshots_repo
snapshots_repo
file:build/m2repository/snapshots
was (Author: gdogaru):
[04:41:21]: [INFO] [deploy:deploy {execution: default-deploy}]
[04:41:21]: [INFO] No primary artifact to deploy, deploy attached artifacts
instead.
[04:41:21]: [INFO] Retrieving previous build number from snapshots_repo
[04:41:21]: Uploading:
file:build/m2repository/snapshots/myapp/testutils/11.6-SNAPSHOT/testutils-11.6-20090902.084121-24.jar
[04:41:21]: 78K uploaded (testutils-11.6-20090902.084121-24.jar)
[04:41:21]: [INFO] Retrieving previous metadata from snapshots_repo
[04:41:21]: [INFO] Uploading repository metadata for: 'artifact myapptestutils'
[04:41:21]: [INFO] Retrieving previous metadata from snapshots_repo
[04:41:21]: [INFO] Uploading repository metadata for: 'snapshot
myapp:testutils:11.6-SNAPSHOT'
[04:41:21]: [INFO] Retrieving previous build number from snapshots_repo
[04:41:21]: Uploading:
file:build/m2repository/snapshots/myapp/testutils/11.6-SNAPSHOT/testutils-11.6-20090902.084121-25.resource
[04:41:21]: 2K uploaded (testutils-11.6-20090902.084121-25.resource)
[04:41:21]: [INFO] Retrieving previous metadata from snapshots_build
[04:41:22]: [INFO] Uploading repository metadata for: 'artifact myapp:testutils'
[04:41:22]: [INFO] Retrieving previous metadata from snapshots_repo
[04:41:22]: [INFO] Uploading repository metadata for: 'snapshot
myapp:testutils:11.6-SNAPSHOT'
[04:41:22]: [INFO]
[04:41:22]: [INFO] BUILD SUCCESSFUL
> deployed snapshot name has different build numbers for multiple artifacts of
> the same build
> ---
>
> Key: MDEPLOY-112
> URL: http://jira.codehaus.org/browse/MDEPLOY-112
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
>Affects Versions: 2.2.1
> Environment: windows xp
>Reporter: Gabriel Dogaru
>
> I have a module that deploys 2 artifacts,1 jar and 1 of them is custom type.
> The build number from the snapshot name is different for the 2 (in the
> repository). It get incremented every time an artifact is deployed. When I
> try to make a local build it searches for the highest build number, and tries
> to bring both the artifacts with the latest build number but only one of them
> has that number.
> I found a workaround for this by false for
> the snapshotRepository.
--
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: (MDEPLOY-112) deployed snapshot name has different build numbers for multiple artifacts of the same build
[
http://jira.codehaus.org/browse/MDEPLOY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189576#action_189576
]
Benjamin Bentmann commented on MDEPLOY-112:
---
bq. I am using project.addAttachedArtifact(artifact); in my mojo to attach the
artifact
That's a valuable piece of info. Could you try calling
{{MavenProjectHelper.attachArtifact()}} instead of directly mutating the
project? Use something like
{code:java}
/**
* @component
*/
private MavenProjectHelper projectHelper;
{code}
to get the component injected into your mojo.
> deployed snapshot name has different build numbers for multiple artifacts of
> the same build
> ---
>
> Key: MDEPLOY-112
> URL: http://jira.codehaus.org/browse/MDEPLOY-112
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
>Affects Versions: 2.2.1
> Environment: windows xp
>Reporter: Gabriel Dogaru
>
> I have a module that deploys 2 artifacts,1 jar and 1 of them is custom type.
> The build number from the snapshot name is different for the 2 (in the
> repository). It get incremented every time an artifact is deployed. When I
> try to make a local build it searches for the highest build number, and tries
> to bring both the artifacts with the latest build number but only one of them
> has that number.
> I found a workaround for this by false for
> the snapshotRepository.
--
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: (MCHANGES-174) Release v2.2
[ http://jira.codehaus.org/browse/MCHANGES-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-174. Resolution: Not A Bug Please ask questions on the users or dev mailing lists. > Release v2.2 > > > Key: MCHANGES-174 > URL: http://jira.codehaus.org/browse/MCHANGES-174 > Project: Maven 2.x Changes Plugin > Issue Type: Wish >Affects Versions: 2.2 >Reporter: Bruno Marti >Priority: Minor > > Which is the roadmap/timeline for release 2.2? -- 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-4336) Exceptions thrown by org.apache.maven.shared.jar.JarAnalyzer constructor should include pathname of the offending file
Exceptions thrown by org.apache.maven.shared.jar.JarAnalyzer constructor should include pathname of the offending file -- Key: MNG-4336 URL: http://jira.codehaus.org/browse/MNG-4336 Project: Maven 2 Issue Type: Improvement Reporter: Rafal Krzewski Attachments: maven-shared-jar_exception_message.patch A corrupted jar file in the repository, or an attempt to use classes directory in place of a jar during a build is tricky do diagnose, because the exception message does not reveal which file could not been opened. The attached patch includes the pathname in the exception message. JarAnalyzerTest was enhanced accordingly. -- 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: (MSHARED-128) Exceptions thrown by org.apache.maven.shared.jar.JarAnalyzer constructor should include pathname of the offending file
[ http://jira.codehaus.org/browse/MSHARED-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-4336 to MSHARED-128: Complexity: (was: Intermediate) Key: MSHARED-128 (was: MNG-4336) Project: Maven Shared Components (was: Maven 2) > Exceptions thrown by org.apache.maven.shared.jar.JarAnalyzer constructor > should include pathname of the offending file > -- > > Key: MSHARED-128 > URL: http://jira.codehaus.org/browse/MSHARED-128 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-shared-jar >Reporter: Rafal Krzewski > Attachments: maven-shared-jar_exception_message.patch > > > A corrupted jar file in the repository, or an attempt to use classes > directory in place of a jar during a build is tricky do diagnose, because the > exception message does not reveal which file could not been opened. > The attached patch includes the pathname in the exception message. > JarAnalyzerTest was enhanced accordingly. -- 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: (MSHARED-128) Exceptions thrown by org.apache.maven.shared.jar.JarAnalyzer constructor should include pathname of the offending file
[ http://jira.codehaus.org/browse/MSHARED-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MSHARED-128: -- Component/s: maven-shared-jar > Exceptions thrown by org.apache.maven.shared.jar.JarAnalyzer constructor > should include pathname of the offending file > -- > > Key: MSHARED-128 > URL: http://jira.codehaus.org/browse/MSHARED-128 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-shared-jar >Reporter: Rafal Krzewski > Attachments: maven-shared-jar_exception_message.patch > > > A corrupted jar file in the repository, or an attempt to use classes > directory in place of a jar during a build is tricky do diagnose, because the > exception message does not reveal which file could not been opened. > The attached patch includes the pathname in the exception message. > JarAnalyzerTest was enhanced accordingly. -- 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: (MEJB-33) Add support for fewer dependencies in client-jars
[ http://jira.codehaus.org/browse/MEJB-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189610#action_189610 ] Gabriel Guerrero commented on MEJB-33: -- Hey guys I had a lot of issues because of this, some class loading problems because one of my ejb-client was bringing to much unnecesary dependencies it was also very used in several projects so we endend excluding lots of libs everywhere, the work arround works, so could you guys add the workaround at least to usage guide in the site or FAQ, it will save many people a lot of time Thanks > Add support for fewer dependencies in client-jars > - > > Key: MEJB-33 > URL: http://jira.codehaus.org/browse/MEJB-33 > Project: Maven 2.x EJB Plugin > Issue Type: New Feature >Affects Versions: 2.1 >Reporter: Karsten Tinnefeld > > Given a scenario, where several application tiers are installed on different > servers, are realized as EJB3 applications, and packaged using maven. > When configuring an ejb module, I give dependencies to all dependency jars > that are used to implement the features. However, they are currently all > added as dependency to the client-jar artifacts as well, so that unused > libraries are deployed on client servers. > I'd like to mark dependencies as server-jar only, e.g. by an > clientJarExclusions configuration element to the plugin, which takes a set of > exclusion elements like the exclusions-element in a dependency. These > dependencies should behave as compile-scope in the server- and provided-scope > in the client-jars. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
