[jira] Closed: (SCM-295) NullPointerException in VSS SCM provider
[ http://jira.codehaus.org/browse/SCM-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Venisse closed SCM-295. Assignee: Emmanuel Venisse Resolution: Duplicate > NullPointerException in VSS SCM provider > > > Key: SCM-295 > URL: http://jira.codehaus.org/browse/SCM-295 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-vss >Affects Versions: 1.0-beta-4 > Environment: Operating system : Windows XP(Service Pack 2) > Java version : 1.5.0_11(Sun Microsystems Inc.) > continuum 1.0.3 with the scm packages upgraded to 1.0-beta4 >Reporter: Laszlo Hornyak Kocka > Assigned To: Emmanuel Venisse > > org.apache.maven.continuum.scm.ContinuumScmException: Error while update > sources. > at > org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:272) > at > org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166) > at > org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) > at java.lang.Thread.run(Thread.java:595) > Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM > command. > at > org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:62) > at > org.apache.maven.scm.provider.vss.VssScmProvider.update(VssScmProvider.java:209) > at > org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:418) > at > org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:395) > at > org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:242) > ... 5 more > Caused by: java.lang.NullPointerException > at java.util.Calendar.setTime(Calendar.java:1032) > at java.text.SimpleDateFormat.format(SimpleDateFormat.java:785) > at java.text.SimpleDateFormat.format(SimpleDateFormat.java:778) > at java.text.DateFormat.format(DateFormat.java:314) > at > org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.buildCmdLine(VssHistoryCommand.java:114) > at > org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommand.executeChangeLogCommand(VssHistoryCommand.java:52) > at -- 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: (DOXIA-91) Update Doxia Decoration model to actually work in reactor build.
[ http://jira.codehaus.org/browse/DOXIA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92311 ] Henning Schmiedehausen commented on DOXIA-91: - Ok, you got me confused. This is only possible when a PathDescriptor contains null for both the PathUrl and the relativePath. Which can only happen when the PathDescriptor has been constructed using a 'null' path. And the only place where this is possible is in PathUtils line 47 and there is an explicit null test in front of it. Can you give some pointers on what project exactly you tried to build the sites for? Or is that some non-public site? If possible, could you put a breakpoint at PathUtils::getRelativePath(String, String) and tell me what exactly goes in there. I'd guess that oldPath is null. I'll add another patch shortly which has another minor fix and I will add some explicit testing on that. Also some unit tests. > Update Doxia Decoration model to actually work in reactor build. > > > Key: DOXIA-91 > URL: http://jira.codehaus.org/browse/DOXIA-91 > Project: doxia > Issue Type: Improvement > Components: Decoration Model >Reporter: Henning Schmiedehausen > Fix For: 1.0 > > Attachments: doxia-decoration-3.patch, doxia-decoration.patch, > doxia-decoration.patch, > org.apache.maven.doxia.site.decoration.inheritance.DecorationModelInheritenceAssemblerTest.txt > > > This is a major patch to the decoration model to bring some sanity in the > link resolution when it is used under the reactor build. It generates > breadcrumbs and item links correctly in all scenarios that I have tested (the > current HEAD code does not) and passes all the unit tests that are already > there. -- 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: (MANTTASKS-44) bootstrap of components/trunk fails with ant-1.7.0RC1
[ http://jira.codehaus.org/browse/MANTTASKS-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92312 ] Herve Boutemy commented on MANTTASKS-44: ok, found in javadoc: "org.apache.tools.ant.ProjectComponent#getLocation() Returns the file/location where this task was defined." We wouldn't care if it only affected bootstrap, but this affects Maven Ant Tasks in their "normal user" usage with Ant 1.7 (though only localRepository task is affected AFAIK). we'l have to change "location" property in proposal: root? dir? basedir? Changing code is easy, changing documentation and communication about the change will need some work, but the most important thing is to find a good target... WDYT? > bootstrap of components/trunk fails with ant-1.7.0RC1 > - > > Key: MANTTASKS-44 > URL: http://jira.codehaus.org/browse/MANTTASKS-44 > Project: Maven 2.x Ant Tasks > Issue Type: Improvement >Reporter: Alfred Nathaniel >Priority: Blocker > > Bootstrap build of components/trunk with ant-1.7.0RC1 fails. > [javac] > /home/alfred/apache/maven/components/trunk/maven-artifact-ant/src/main/java/org/apache/maven/artifact/ant/LocalRepository.java:32: > getLocation() in org.apache.maven.artifact.ant.LocalRepository cannot > override getLocation() in org.apache.tools.ant.ProjectComponent; attempting > to use incompatible return type[javac] found : java.io.File > [javac] required: org.apache.tools.ant.Location > [javac] public File getLocation() > [javac] ^ -- 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-1463) TestNG 5.5 ibiblio upload
TestNG 5.5 ibiblio upload -- Key: MAVENUPLOAD-1463 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1463 Project: maven-upload-requests Issue Type: Task Reporter: Jesse Kuhnert Attachments: testng-5.5-jdk14-bundle.jar, testng-5.5-jdk15-bundle.jar Would like to publish the 5.5 version of testng to ibiblio. -- 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-1464) Request to upload greenmail 1.2 bundle
Request to upload greenmail 1.2 bundle -- Key: MAVENUPLOAD-1464 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1464 Project: maven-upload-requests Issue Type: Task Reporter: Marcel May Attachments: greenmail-1.2-bundle.jar GreenMail is an open source, intuitive and easy-to-use test suite of email servers for testing purposes. Supports SMTP, POP3, IMAP with SSL socket support. Thanks alot - Marcel -- 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: (DOXIA-91) Update Doxia Decoration model to actually work in reactor build.
[ http://jira.codehaus.org/browse/DOXIA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henning Schmiedehausen updated DOXIA-91: Attachment: doxia-decoration-4.patch Updated version for the doxia decoration patch. This should now avoid all possible NPE problems even with complex builds. Also adds some unit tests for the code. > Update Doxia Decoration model to actually work in reactor build. > > > Key: DOXIA-91 > URL: http://jira.codehaus.org/browse/DOXIA-91 > Project: doxia > Issue Type: Improvement > Components: Decoration Model >Reporter: Henning Schmiedehausen > Fix For: 1.0 > > Attachments: doxia-decoration-3.patch, doxia-decoration-4.patch, > doxia-decoration.patch, doxia-decoration.patch, > org.apache.maven.doxia.site.decoration.inheritance.DecorationModelInheritenceAssemblerTest.txt > > > This is a major patch to the decoration model to bring some sanity in the > link resolution when it is used under the reactor build. It generates > breadcrumbs and item links correctly in all scenarios that I have tested (the > current HEAD code does not) and passes all the unit tests that are already > there. -- 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: (DOXIA-91) Update Doxia Decoration model to actually work in reactor build.
[ http://jira.codehaus.org/browse/DOXIA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92323 ] Henning Schmiedehausen commented on DOXIA-91: - This patch also adds a number of unit tests. Unfortunately as I can not modify the issue, I can not change the "contains unit tests" field. > Update Doxia Decoration model to actually work in reactor build. > > > Key: DOXIA-91 > URL: http://jira.codehaus.org/browse/DOXIA-91 > Project: doxia > Issue Type: Improvement > Components: Decoration Model >Reporter: Henning Schmiedehausen > Fix For: 1.0 > > Attachments: doxia-decoration-3.patch, doxia-decoration-4.patch, > doxia-decoration.patch, doxia-decoration.patch, > org.apache.maven.doxia.site.decoration.inheritance.DecorationModelInheritenceAssemblerTest.txt > > > This is a major patch to the decoration model to bring some sanity in the > link resolution when it is used under the reactor build. It generates > breadcrumbs and item links correctly in all scenarios that I have tested (the > current HEAD code does not) and passes all the unit tests that are already > there. -- 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-2926) group search order for plugins is inverted
[ http://jira.codehaus.org/browse/MNG-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-2926. -- Resolution: Fixed created it0119 to check this and applied fix to 2.0.7-SNAPSHOT and trunk. I also found that the pluginGroups in the settings wasn't being searched prior to the defaults either (docs say it should). This is also fixed. > group search order for plugins is inverted > -- > > Key: MNG-2926 > URL: http://jira.codehaus.org/browse/MNG-2926 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6 >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 2.0.7 > > > currently the mojo.codehaus.org is used if a plugin name conflicts with > maven.apache.org. It should be the other way around. -- 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-1284) upload new artifact to The Central Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92327 ] Fernando Boaglio commented on MAVENUPLOAD-1284: --- Junit will be used in near future, but for now we can just remove it. I've replaced groovy-all as requested. The fixed bundle is in the same place: http://www.mentaframework.org/download/mentawai-1.7-bundle.jar > upload new artifact to The Central Repository > - > > Key: MAVENUPLOAD-1284 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1284 > Project: maven-upload-requests > Issue Type: Task >Reporter: Fernando Boaglio > > Hello, I'm one of the developers of Mentawai Web Framework, an open source > Java web framework. > Please upload! =) > > > -- 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-2432) Apache and Mojo plugins take precendence over plugins in the pom.
[ http://jira.codehaus.org/browse/MNG-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-2432. -- Assignee: Brian Fox Resolution: Fixed Fix Version/s: (was: 2.1-alpha-1) 2.0.7 > Apache and Mojo plugins take precendence over plugins in the pom. > - > > Key: MNG-2432 > URL: http://jira.codehaus.org/browse/MNG-2432 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.4 >Reporter: Jan Bartel >Assignee: Brian Fox > Fix For: 2.0.7 > > > When resolving plugin prefixes, plugins from apache and mojo take precendence > over plugins explicitly in the pom.xml. For example, an old plugin with > prefix "jetty" at org.codehaus.mojo.jetty-maven-plugin is always used in > preference to the new maven-jetty-plugin with prefix "jetty", even though it > is specified in the pom like so: > > org.mortbay.jetty > maven-jetty-plugin > 6.0-SNAPSHOT > -- 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-980) Provide control over precedence of org.apache.maven.plugins group in search path
[ http://jira.codehaus.org/browse/MNG-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-980. - Assignee: Brian Fox Resolution: Fixed Fix Version/s: (was: 2.1.x) 2.0.7 > Provide control over precedence of org.apache.maven.plugins group in search > path > > > Key: MNG-980 > URL: http://jira.codehaus.org/browse/MNG-980 > Project: Maven 2 > Issue Type: Improvement > Components: Plugins and Lifecycle >Affects Versions: 2.0-beta-1 >Reporter: John Fallows >Assignee: Brian Fox > Fix For: 2.0.7 > > > settings.xml has a section to list additional groupIds to > search for top level m2 plugin goals. > By default, "org.apache.maven.plugins" is not required to be present in this > list, and always wins if there is a collision. > that explicitly list "org.apache.maven.plugins" should be able > to control this default behavior, so that a different plugin groupId can > always win in the case of a collision. > For example, in settings.xml: > > org.example.maven.plugins > org.apache.maven.plugins > > This would allow "org.example.maven.plugins" to always win in the case of a > collision, whereas: > > org.example.maven.plugins > > would still allow "org.apache.maven.plugins" to always win, as it does today. -- 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-2885) improve os activation documentation
[ http://jira.codehaus.org/browse/MNG-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-2885. -- Resolution: Fixed Fix Version/s: 2.0.7 > improve os activation documentation > --- > > Key: MNG-2885 > URL: http://jira.codehaus.org/browse/MNG-2885 > Project: Maven 2 > Issue Type: Improvement > Components: Documentation: General >Affects Versions: 2.0.5 >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 2.0.7 > > > The docs on os activation is lacking. > http://maven.apache.org/guides/introduction/introduction-to-profiles.html > doesn't reference os activation > http://maven.apache.org/pom.html only mentions an example. -- 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-2639) Broken link on Maven page
[ http://jira.codehaus.org/browse/MNG-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-2639. -- Assignee: Brian Fox Resolution: Cannot Reproduce This link doesn't appear to be there anymore. > Broken link on Maven page > - > > Key: MNG-2639 > URL: http://jira.codehaus.org/browse/MNG-2639 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General > Environment: Maven homepage >Reporter: Jakob Bornecrantz >Assignee: Brian Fox >Priority: Minor > > The page http://maven.apache.org/quick.html is missing. > Its on the link sidebar one some of the subpages of the mainpage: > http://maven.apache.org/general.html > http://maven.apache.org/guides/index.html > http://maven.apache.org/plugins/index.html > Among others... -- 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-2247) Release-Dates of maven releases not documented on website?
[ http://jira.codehaus.org/browse/MNG-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-2247. -- Resolution: Fixed Fix Version/s: 2.0.7 The release date of the most recent release is now shown right above the download link on the main page. > Release-Dates of maven releases not documented on website? > -- > > Key: MNG-2247 > URL: http://jira.codehaus.org/browse/MNG-2247 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General > Environment: firefox >Reporter: Oliver Nölle >Assignee: Alex Mayorga Adame >Priority: Minor > Fix For: 2.0.7 > > > Scanning projects on the web I often want to know how "active" these projects > are by checking the dates of the last release(s). > After browsing for half an hour on the maven website > (http://maven.apache.org/) I give up to find the dates of the last releases... > => Please add them somewhere in a prominent place (in many open source > projects there is something like a news section with release dates or in > sourceforge you find the release dates looking into the "files" section) > (In case the information is there, please check whether it's me who was too > stupid to find it or whether it's really hidden...) > Same thing applies for http://m2eclipse.codehaus.org/: I find 5 versions, but > no date information... > => I guess you might want to forward this bug to the maven plugin generating > the website? -- 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-1212) apply new style to plugins sites
[ http://jira.codehaus.org/browse/MNG-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MNG-1212. -- Assignee: Brian Fox Resolution: Fixed plugin sites already have the same style as the main page > apply new style to plugins sites > > > Key: MNG-1212 > URL: http://jira.codehaus.org/browse/MNG-1212 > Project: Maven 2 > Issue Type: Task > Components: Documentation: General >Reporter: Brett Porter >Assignee: Brian Fox > -- 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-2941) Sometime SNAPSHOTs can not be downloaded in an an online build
Sometime SNAPSHOTs can not be downloaded in an an online build -- Key: MNG-2941 URL: http://jira.codehaus.org/browse/MNG-2941 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.5 Environment: All Reporter: Anita Kulshreshtha When an offline build fails because a SNPSHOT was not available locally, the SNAPSHOT can not be downloaded during a subsequent online build. During the offline build a file maven-metadata-apache-snpshots.xml (with the following contents in this example) is created in .m2 repo: org.apache.geronimo.genesis genesis 1.2-SNAPSHOT All subsequent online builds fail to download this artifact from the repository with error message given below. After deleting the metadata file corresponding to the repository in which this artifact is available (maven-metadata-apache-snpshots.xml file in this example) , the artifact can be downloaded successfully. This trace can be produced by any SNAPSHOT in any project, the following steps are for geronimo: 1. Delete the above SNAPSHOT from the local repo. 2. Build geronimo offlne, the build will fail. 3. Build online, the following message will be generated. 4. Delete the above metadata file, and build online, the SNAPSHOT will get downloaded successfully. [INFO] Scanning for projects... Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/ger onimo/genesis/genesis/1.2-SNAPSHOT/genesis-1.2-SNAPSHOT.pom [WARNING] Unable to get resource 'org.apache.geronimo.genesis:genesis:pom:1.2-SN APSHOT' from repository apache-snapshots (http://people.apache.org/repo/m2-snaps hot-repository) Downloading: http://snapshots.repository.codehaus.org/org/apache/geronimo/genesi s/genesis/1.2-SNAPSHOT/genesis-1.2-SNAPSHOT.pom [WARNING] Unable to get resource 'org.apache.geronimo.genesis:genesis:pom:1.2-SN APSHOT' from repository codehaus-snapshots (http://snapshots.repository.codehaus .org) [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.geronimo.genesis ArtifactId: genesis Version: 1.2-SNAPSHOT Reason: Unable to download the artifact from any repository org.apache.geronimo.genesis:genesis:pom:1.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository) [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.apache .geronimo.genesis:genesis for project: org.apache.geronimo.genesis.config:config :pom:null at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:373) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:286) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent : org.apache.geronimo.genesis:genesis for project: org.apache.geronimo.genesis.c onfig:config:pom:null at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D efaultMavenProjectBuilder.java:1198) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D efaultMavenProjectBuilder.java:1214) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D efaultMavenProjectBuilder.java:1214) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def aultMavenProjectBuilder.java:697) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi leInternal(DefaultMavenProjectBuilder.java:431) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave nProjectBuilder.java:195) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:523) at org.apache.maven.Def
[jira] Commented: (MNG-2941) Sometime SNAPSHOTs can not be downloaded in an an online build
[ http://jira.codehaus.org/browse/MNG-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92335 ] Wendy Smoak commented on MNG-2941: -- The default update policy is 'daily', so I think the behavior is as described. http://maven.apache.org/ref/2.0.4/maven-model/maven.html#class_pluginRepository You can change the update policy to 'always' or 'interval:###' for the snapshot repos, or use -U on the command line to force updates. > Sometime SNAPSHOTs can not be downloaded in an an online build > -- > > Key: MNG-2941 > URL: http://jira.codehaus.org/browse/MNG-2941 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.5 > Environment: All >Reporter: Anita Kulshreshtha > > When an offline build fails because a SNPSHOT was not available locally, > the SNAPSHOT can not be downloaded during a subsequent online build. During > the offline build a file maven-metadata-apache-snpshots.xml (with the > following contents in this example) is created in .m2 repo: > > org.apache.geronimo.genesis > genesis > 1.2-SNAPSHOT > >All subsequent online builds fail to download this artifact from the > repository with error message given below. After deleting the metadata file > corresponding to the repository in which this artifact is available > (maven-metadata-apache-snpshots.xml file in this example) , the artifact can > be downloaded successfully. > This trace can be produced by any SNAPSHOT in any project, the following > steps are for geronimo: > 1. Delete the above SNAPSHOT from the local repo. > 2. Build geronimo offlne, the build will fail. > 3. Build online, the following message will be generated. > 4. Delete the above metadata file, and build online, the SNAPSHOT will get > downloaded successfully. > [INFO] Scanning for projects... > Downloading: > http://people.apache.org/repo/m2-snapshot-repository/org/apache/ger > onimo/genesis/genesis/1.2-SNAPSHOT/genesis-1.2-SNAPSHOT.pom > [WARNING] Unable to get resource > 'org.apache.geronimo.genesis:genesis:pom:1.2-SN > APSHOT' from repository apache-snapshots > (http://people.apache.org/repo/m2-snaps > hot-repository) > Downloading: > http://snapshots.repository.codehaus.org/org/apache/geronimo/genesi > s/genesis/1.2-SNAPSHOT/genesis-1.2-SNAPSHOT.pom > [WARNING] Unable to get resource > 'org.apache.geronimo.genesis:genesis:pom:1.2-SN > APSHOT' from repository codehaus-snapshots > (http://snapshots.repository.codehaus > .org) > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] Failed to resolve artifact. > GroupId: org.apache.geronimo.genesis > ArtifactId: genesis > Version: 1.2-SNAPSHOT > Reason: Unable to download the artifact from any repository > org.apache.geronimo.genesis:genesis:pom:1.2-SNAPSHOT > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), > codehaus-snapshots (http://snapshots.repository.codehaus.org), > apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), > tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository) > [INFO] > > [INFO] Trace > org.apache.maven.reactor.MavenExecutionException: Cannot find parent: > org.apache > .geronimo.genesis:genesis for project: > org.apache.geronimo.genesis.config:config > :pom:null > at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:373) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:286) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find > parent > : org.apache.geronimo.genesis:genesis for project: > org.apache.geronimo.genesis.c > onfig:config:pom:null > at > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D > efaultMavenProjectBuilder
