[JBoss JIRA] (JBIDE-20474) combine fewer CI builds into generated composite site
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20474?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-20474.
---------------------------------
I just checked the examples which work as advertised. Closing.
> combine fewer CI builds into generated composite site
> -----------------------------------------------------
>
> Key: JBIDE-20474
> URL: https://issues.jboss.org/browse/JBIDE-20474
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.4.0.Final
>
>
> [18/08/2015 15:29:34] Fred Bricon: when building central, I see
> [18/08/2015 15:29:36] Fred Bricon: [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,58kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,18kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,93kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,88kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,25kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,77kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,43kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,94kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 14,74kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,7kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,58kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,95kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,11kB at 0B/s)
> [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-hib... (0B of 13,86kB at 0B/s)
> Nick sez:
> {quote}
> somethign something "store fewer instances of /snapshots/builds /JOB_NAME/TIMESTAMP; more aggressive cleanup required; suggest only keeping 5 builds max"
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBTIS-729) Teiid Designer depends on bundle in JBT/devstudio TP which no longer exists
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-729?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-729:
----------------------------------
Hey [~blafond] - The JBDS core plugins removed their Birt dependencies because Birt's support staff is effectively 0 and it adds a couple of seconds to the Eclipse startup time. I've added it back into the JBTIS TP to get Teiid Designer to build but could you look into the dependence Teiid Designer has on Birt and whether that can be removed? That would simplify the IS TP, speed up JBDS/Eclipse start time and reduce dependence on an unsupported plugin.
WDYT?
> Teiid Designer depends on bundle in JBT/devstudio TP which no longer exists
> ---------------------------------------------------------------------------
>
> Key: JBTIS-729
> URL: https://issues.jboss.org/browse/JBTIS-729
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform, teiid
> Affects Versions: 4.4.0.Alpha1-TP, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Barry LaFond
> Fix For: 4.4.0.Alpha1-TP
>
>
> org.eclipse.core.runtime.compatibility was removed from the JBT and devstudio target platforms because nothing in JBT/devstudio requires it any more.
> As a result, when you try to install Teiid Designer into the staged JBT 4.4.0.Final or devstudio 10.0.0.GA via Central, you get this error:
> {code}
> !MESSAGE Missing requirement: Teiid DataTools Connectivity 10.0.0.Beta3-v20160218-1807-B4076 (org.teiid.datatools.connectivity.feature.feature.group 10.0.0.Beta3-v20160218-1807-B4076) requires 'org.eclipse.core.runtime.compatibility [3.2.200,4.0.0)' but it could not be found
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22362:
------------------------------------------
[~akazakov] I agree, we should let people know, but it's not all clear to me yet, who to bother with this.
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.1.Alpha1
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21391) upstream IU version decreases
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21391?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-21391.
---------------------------------
I verified that both of the affected features have their versions bumped now (as of Neon RC2 in devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar):
{code}
devstudio-10.0.0.GA-5510/studio/devstudio.app/Contents/Eclipse/features/org.eclipse.equinox.p2.rcp.feature_1.2.200.v20160504-1450
devstudio-10.0.0.GA-5510/studio/devstudio.app/Contents/Eclipse/features/org.eclipse.equinox.p2.user.ui_2.2.200.v20160504-1450
{code}
> upstream IU version decreases
> -----------------------------
>
> Key: JBIDE-21391
> URL: https://issues.jboss.org/browse/JBIDE-21391
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> As of Neon M4, -three- two IUs have versions which decreased relative to their Mars.1 versions.
> {code}
> org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 Version must be higher than 1.2.101.v20150826-1318
> org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 Version must be higher than 2.2.101.v20150826-1318
> {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> Additionally, this IU is incorrectly reported as being a version decrease:
> {code}org.eclipse.ecf.provider.filetransfer.httpclient4 1.0.2000.v20150810-1719 Error: Version 1.1.0.v20151130-0157 must be higher than 1.0.2000.v20150810-1719
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service
by Thomas Mäder (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ]
Thomas Mäder commented on JBIDE-21828:
--------------------------------------
Sent pull request. Will continue to improve (tests, doc)
> OpenShift Explorer view flickers when refreshing a service
> ----------------------------------------------------------
>
> Key: JBIDE-21828
> URL: https://issues.jboss.org/browse/JBIDE-21828
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Thomas Mäder
> Fix For: 4.4.x
>
> Attachments: Screenshot 2016-03-08 10.32.39.png
>
>
> When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls.
> Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod.
> Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services.
> Custom/added logs in the console:
> {code}
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/mongodb
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/jee-sample
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from sample/nodejs-mongodb-example
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22373) discovery site build does not need to fetch ant-contrib repeatedly when already available as maven dependency
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22373?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22373.
---------------------------------
I haven't really verified this, but I assume we would have noticed if the build didn't work after this change. So closing.
> discovery site build does not need to fetch ant-contrib repeatedly when already available as maven dependency
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22373
> URL: https://issues.jboss.org/browse/JBIDE-22373
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, central-update
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha2
>
>
> Realized due to a network glitch that the process of building the discovery sites currently attempts to fetch & unzip ant-contrib 4 times.
> {code}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (install) on project org.jboss.tools.central.discovery: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-discovery/build.xml:37: The following error occurred while executing this line:
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-discovery/build.xml:52: Error while expanding /home/hudson/static_build_env/jbds/tools/ant-contrib-1.0b2-bin.zip
> [ERROR] java.io.IOException: Negative seek offset
> [ERROR] around Ant part ...<ant antfile="build.xml" dir="../../" target="basic.build">... @ 4:62 in /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-discovery/jbosstools/org.jboss.tools.central.discovery/target/antrun/build-main.xml
> [ERROR] -> [Help 1]
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (install) on project org.jboss.tools.central.discovery.earlyaccess: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-discovery/build.xml:37: The following error occurred while executing this line:
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-discovery/build.xml:52: Error while expanding /home/hudson/static_build_env/jbds/tools/ant-contrib-1.0b2-bin.zip
> [ERROR] java.io.IOException: Negative seek offset
> [ERROR] around Ant part ...<ant antfile="build.xml" dir="../../" target="basic.build">... @ 4:62 in /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-discovery/jbosstools/org.jboss.tools.central.discovery.earlyaccess/target/antrun/build-main.xml
> [ERROR] -> [Help 1]
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (install) on project com.jboss.jbds.central.discovery: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-discovery/build.xml:37: The following error occurred while executing this line:
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-discovery/build.xml:52: Error while expanding /home/hudson/static_build_env/jbds/tools/ant-contrib-1.0b2-bin.zip
> [ERROR] java.io.IOException: Negative seek offset
> [ERROR] around Ant part ...<ant antfile="build.xml" dir="../../" target="basic.build">... @ 4:62 in /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-discovery/jbdevstudio/com.jboss.jbds.central.discovery/target/antrun/build-main.xml
> [ERROR] -> [Help 1]
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (install) on project com.jboss.jbds.central.discovery.earlyaccess: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-discovery/build.xml:37: The following error occurred while executing this line:
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-discovery/build.xml:52: Error while expanding /home/hudson/static_build_env/jbds/tools/ant-contrib-1.0b2-bin.zip
> [ERROR] java.io.IOException: Negative seek offset
> [ERROR] around Ant part ...<ant antfile="build.xml" dir="../../" target="basic.build">... @ 4:62 in /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-discovery/jbdevstudio/com.jboss.jbds.central.discovery.earlyaccess/target/antrun/build-main.xml
> {code}
> But this is declared as a dependency in each pom that uses the build.xml script.
> So we can probably skip this step entirely and just rely on the maven dep.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-19554) Show actual error for target-platform validation error in maven build
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19554?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19554:
---------------------------------------
[~dgolovin], can you report back if you see this fixed now that we use Tycho 0.25 please? Or provide steps to reproduce?
Thanks!
> Show actual error for target-platform validation error in maven build
> ----------------------------------------------------------------------
>
> Key: JBIDE-19554
> URL: https://issues.jboss.org/browse/JBIDE-19554
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, upstream
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Mickael Istria
> Fix For: 4.4.0.Alpha2
>
>
> Currently error is printed out only with -X maven option. To findout what is the problem build have be executed twice in case of error:
> 1. Normal maven call - you see the message
> {code}[INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4....
> [INFO] Failed, see Error log below
> [ERROR] Validation found errors in 1 .target files:
> Could not resolve content of jbdevstudio-unified.target{code}
> 2. Run with -X and you get the error details
> {code}Could not resolve content of jbdevstudio-unified.target
> org.eclipse.tycho.core.ee.shared.BuildFailureException: Failed to resolve target definition /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target: Could not find "org.eclipse.jetty.http/8.1.14.v20131031" in the repositories of the current location
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:99)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.resolveFromArguments(TargetDefinitionResolverService.java:70)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.getTargetDefinitionContent(TargetDefinitionResolverService.java:60)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.resolveTargetDefinitions(TargetPlatformFactoryImpl.java:213)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:153)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:126)
> at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveMetadata(P2ResolverImpl.java:130)
> at org.eclipse.tycho.extras.tpvalidator.TPValidationMojo.validateTarget(TPValidationMojo.java:135)
> at org.eclipse.tycho.extras.tpvalidator.TPValidationMojo.execute(TPValidationMojo.java:83)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.eclipse.tycho.p2.target.facade.TargetDefinitionResolutionException: Could not find "org.eclipse.jetty.http/8.1.14.v20131031" in the repositories of the current location
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver$LoadedIULocation.findUnitInThisLocation(TargetDefinitionResolver.java:313)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver$LoadedIULocation.getRootIUs(TargetDefinitionResolver.java:303)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver$ResolverRun.addLocation(TargetDefinitionResolver.java:155)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContentWithExceptions(TargetDefinitionResolver.java:121)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:94)
> ... 29 more
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Validation found errors in 1 .target files:
> Could not resolve content of jbdevstudio-unified.target
> org.eclipse.tycho.core.ee.shared.BuildFailureException: Failed to resolve target definition /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-target-platforms/jbdevstudio/unified/target/jbdevstudio-unified.target: Could not find "org.eclipse.jetty.http/8.1.14.v20131031" in the repositories of the current location
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:99)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.resolveFromArguments(TargetDefinitionResolverService.java:70)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolverService.getTargetDefinitionContent(TargetDefinitionResolverService.java:60)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.resolveTargetDefinitions(TargetPlatformFactoryImpl.java:213)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:153)
> at org.eclipse.tycho.p2.target.TargetPlatformFactoryImpl.createTargetPlatform(TargetPlatformFactoryImpl.java:126)
> at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveMetadata(P2ResolverImpl.java:130)
> at org.eclipse.tycho.extras.tpvalidator.TPValidationMojo.validateTarget(TPValidationMojo.java:135)
> at org.eclipse.tycho.extras.tpvalidator.TPValidationMojo.execute(TPValidationMojo.java:83)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.eclipse.tycho.p2.target.facade.TargetDefinitionResolutionException: Could not find "org.eclipse.jetty.http/8.1.14.v20131031" in the repositories of the current location
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver$LoadedIULocation.findUnitInThisLocation(TargetDefinitionResolver.java:313)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver$LoadedIULocation.getRootIUs(TargetDefinitionResolver.java:303)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver$ResolverRun.addLocation(TargetDefinitionResolver.java:155)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContentWithExceptions(TargetDefinitionResolver.java:121)
> at org.eclipse.tycho.p2.target.TargetDefinitionResolver.resolveContent(TargetDefinitionResolver.java:94)
> ... 29 more
> at org.eclipse.tycho.extras.tpvalidator.TPValidationMojo.execute(TPValidationMojo.java:95)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 more{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months