[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
Denis Golovin (JIRA)
jira-events at lists.jboss.org
Fri Sep 23 02:18:27 EDT 2011
[ https://issues.jboss.org/browse/JBIDE-8667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630134#comment-12630134 ]
Denis Golovin commented on JBIDE-8667:
--------------------------------------
{code}[INFO] Adding repository (cached) http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/
[INFO] Adding repository (cached) http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/latest/
[INFO] Downloading org.jboss.tools.jst.web
[INFO] Downloading org.jboss.tools.jst.web
[INFO] o.h.m.e.h.MavenExecutionResultHandler - Build failed with exception(s)
[INFO] o.h.m.e.h.MavenExecutionResultHandler - [1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not download artifacts from any repository
osgi.bundle,org.jboss.tools.jst.web,3.3.0.v20110922-1359-H514-M4
[DEBUG] Closing connection to remote
[ERROR] Internal error: java.lang.RuntimeException: Could not download artifacts from any repository
[ERROR] osgi.bundle,org.jboss.tools.jst.web,3.3.0.v20110922-1359-H514-M4
[ERROR] -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not download artifacts from any repository
osgi.bundle,org.jboss.tools.jst.web,3.3.0.v20110922-1359-H514-M4
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.RuntimeException: Could not download artifacts from any repository
osgi.bundle,org.jboss.tools.jst.web,3.3.0.v20110922-1359-H514-M4
at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:360)
at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:293)
at org.eclipse.tycho.p2.facade.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:389)
at org.eclipse.tycho.p2.facade.P2TargetPlatformResolver.resolvePlatform(P2TargetPlatformResolver.java:150)
at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:90)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:91)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:273)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
... 11 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.{code}
> improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-8667
> URL: https://issues.jboss.org/browse/JBIDE-8667
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 3.3.0.M1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 3.3.0.M4
>
> Attachments: screenshot103.png
>
>
> (2011-04-01 10:11:04) nickboldt: and while I'd love to do:
> (2011-04-01 10:11:12) nickboldt: mkdir whatever-new
> (2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new
> (2011-04-01 10:11:25) nickboldt: rm -fr whatever
> (2011-04-01 10:11:29) nickboldt: mv whatever-new whatever
> (2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and "it's there and updated" is less
> (2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have
> (2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the same folder on top
> (2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of whack w.r.t the site content
> (2011-04-01 10:12:17) maxandersen: hmmm
> (2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then rename" instead of "push into existing and clean out cruft"
> (2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm all ears
> (2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply connect over ssh and run a script directly
> (2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete the existing one..
> (2011-04-01 10:14:10) maxandersen: sftp rm should work?
> (2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete
> (2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont need to rename anything
> (2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know "locally"
> (2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in the composite*.xml files
> (2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site
> (2011-04-01 10:15:17) nickboldt: and then delete the old one
> 1. generate composite metadata files on the fly
> 2. publish that into root dir, all/repo/
> 3. purge previous build's folder over scripted sftp?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list