[JBoss JIRA] (JBIDE-18835) repository-utils should support Tycho 0.22.0
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18835?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-18835:
-----------------------------------
Issue Type: Enhancement (was: Bug)
> repository-utils should support Tycho 0.22.0
> --------------------------------------------
>
> Key: JBIDE-18835
> URL: https://issues.jboss.org/browse/JBIDE-18835
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.3.x
>
>
> Per details in http://lists.jboss.org/pipermail/jbosstools-dev/2014-November/009542.html I tried to build the parent pom in master branch and got this error:
> {code}
> [INFO] --- repository-utils:0.21.0:generate-repository-facade (generate-facade) @ parent ---
> [WARNING] Error injecting: org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo
> java.lang.NoClassDefFoundError: org/eclipse/tycho/core/facade/BuildProperties
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2451)
> at java.lang.Class.getDeclaredMethods(Class.java:1810)
> at com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java:674)
> at com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(InjectionPoint.java:366)
> at com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies(ConstructorBindingImpl.java:165)
> at com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorImpl.java:609)
> at com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:565)
> at com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl.java:551)
> at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:865)
> at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:790)
> at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:278)
> at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:210)
> at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:986)
> at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1019)
> at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:982)
> at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1032)
> at org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
> at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86)
> at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55)
> at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
> at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:100)
> at org.eclipse.sisu.plexus.PlexusLifecycleManager.onProvision(PlexusLifecycleManager.java:133)
> at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:109)
> at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55)
> at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
> at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47)
> at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:997)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1047)
> at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:993)
> at com.google.inject.Scopes$1$1.get(Scopes.java:59)
> at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:82)
> at org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:51)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:260)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:252)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:459)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:97)
> 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:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> 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:601)
> 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: java.lang.ClassNotFoundException: org.eclipse.tycho.core.facade.BuildProperties
> at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227)
> ... 57 more
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 38.487s
> [INFO] Finished at: Wed Nov 26 09:26:48 EST 2014
> [INFO] Final Memory: 18M/490M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.21.0:generate-repository-facade (generate-facade) on project parent: Execution generate-facade of goal org.jboss.tools.tycho-plugins:repository-utils:0.21.0:generate-repository-facade failed: A required class was missing while executing org.jboss.tools.tycho-plugins:repository-utils:0.21.0:generate-repository-facade: org/eclipse/tycho/core/facade/BuildProperties
> [ERROR] -----------------------------------------------------
> [ERROR] realm = plugin>org.jboss.tools.tycho-plugins:repository-utils:0.21.0
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] = file:/home/nboldt/.m2/repository/org/jboss/tools/tycho-plugins/repository-utils/0.21.0/repository-utils-0.21.0.jar
> [ERROR] urls[1] = file:/home/nboldt/.m2/repository/org/eclipse/tycho/tycho-packaging-plugin/0.21.0/tycho-packaging-plugin-0.21.0.jar
> [ERROR] urls[2] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-utils/3.0.7/plexus-utils-3.0.7.jar
> [ERROR] urls[3] = file:/home/nboldt/.m2/repository/org/apache/maven/maven-archiver/2.5/maven-archiver-2.5.jar
> [ERROR] urls[4] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-archiver/2.2/plexus-archiver-2.2.jar
> [ERROR] urls[5] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-io/2.0.4/plexus-io-2.0.4.jar
> [ERROR] urls[6] = file:/home/nboldt/.m2/repository/org/eclipse/tycho/org.eclipse.osgi.compatibility.state/1.0.0.v20140403-1907/org.eclipse.osgi.compatibility.state-1.0.0.v20140403-1907.jar
> [ERROR] urls[7] = file:/home/nboldt/.m2/repository/net/sf/saxon/saxon/8.7/saxon-8.7.jar
> [ERROR] urls[8] = file:/home/nboldt/.m2/repository/net/sf/saxon/saxon-dom/8.7/saxon-dom-8.7.jar
> [ERROR] urls[9] = file:/home/nboldt/.m2/repository/com/googlecode/maven-download-plugin/download-maven-plugin/1.2.0/download-maven-plugin-1.2.0.jar
> [ERROR] urls[10] = file:/home/nboldt/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> [ERROR] urls[11] = file:/home/nboldt/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar
> [ERROR] urls[12] = file:/home/nboldt/.m2/repository/org/apache/httpcomponents/httpclient/4.0-beta2/httpclient-4.0-beta2.jar
> [ERROR] urls[13] = file:/home/nboldt/.m2/repository/org/apache/httpcomponents/httpcore/4.0-beta3/httpcore-4.0-beta3.jar
> [ERROR] urls[14] = file:/home/nboldt/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar
> [ERROR] urls[15] = file:/home/nboldt/.m2/repository/commons-codec/commons-codec/1.3/commons-codec-1.3.jar
> [ERROR] urls[16] = file:/home/nboldt/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
> [ERROR] urls[17] = file:/home/nboldt/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
> [ERROR] urls[18] = file:/home/nboldt/.m2/repository/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
> [ERROR] urls[19] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> [ERROR] urls[20] = file:/home/nboldt/.m2/repository/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
> [ERROR] urls[21] = file:/home/nboldt/.m2/repository/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
> [ERROR] urls[22] = file:/home/nboldt/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.4/plexus-component-annotations-1.5.4.jar
> [ERROR] Number of foreign imports: 1
> [ERROR] import: Entry[import from realm ClassRealm[project>org.jboss.tools:parent:4.3.0.Alpha1-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
> [ERROR]
> [ERROR] -----------------------------------------------------: org.eclipse.tycho.core.facade.BuildProperties
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18826) ClassNotFoundException for creating new Hybrid project
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18826?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-18826:
-----------------------------------
Component/s: target-platform
(was: build)
> ClassNotFoundException for creating new Hybrid project
> ------------------------------------------------------
>
> Key: JBIDE-18826
> URL: https://issues.jboss.org/browse/JBIDE-18826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, target-platform, upstream
> Affects Versions: 4.3.0.Alpha1
> Reporter: Ilya Buziuk
> Assignee: Gorkem Ercan
> Fix For: 4.3.0.Alpha1
>
>
> stack trace:
> {code}
> Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_0.1.0.201411202306
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:432)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:345)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:337)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 64 more
> {code}
> this is most likely a version range issue - http://snag.gy/6EHNd.jpg
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-18837:
-----------------------------------
Issue Type: Enhancement (was: Bug)
> because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18837
> URL: https://issues.jboss.org/browse/JBIDE-18837
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, central, common/jst/core, project-examples
> Affects Versions: 4.2.1.CR1
> Reporter: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples.
> Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating.
> And we need to use the maven enforcer plugin to fail the build if these versions get out of sync.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18846?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-18846:
-----------------------------------
Issue Type: Enhancement (was: Bug)
> create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18846
> URL: https://issues.jboss.org/browse/JBIDE-18846
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, website
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Alpha1
>
>
> Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as:
> builds (nightly, staging, dev, stable)
> updates (nightly, staging, dev, stable)
> Jenkins jobs
> discovery sites (nightly, staging, dev, stable)
> target platforms
> etc.
> And for each component, we can list:
> build
> update
> Jenkins job
> etc.
> The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html
> Unsure whether generated HTML (via script) or simple .adoc is better for this.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-17180.
---------------------------------
Resolution: Done
Pushed to master+maintenance: https://github.com/jbosstools/jbosstools-server/pull/308
> Disable custom deployment settings for remote servers without management port exposed
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-17180
> URL: https://issues.jboss.org/browse/JBIDE-17180
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: JBIDE-17180v2.png, wide-window.png
>
>
> JBIDE-13445 added the possibility to use custom deploy dir on remote server.
> {quote}
> Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail.
> {quote}
> We should disable this option in such case, because right now it just adds confusion - you have a server without management port exposed and not knowing about all the details you change the deployment dir, you will end up with non-working deployment.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-17180) Disable custom deployment settings for remote servers without management port exposed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17180?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-17180:
--------------------------------
Attachment: JBIDE-17180v2.png
Screenshot with max width on label plus wrap.
> Disable custom deployment settings for remote servers without management port exposed
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-17180
> URL: https://issues.jboss.org/browse/JBIDE-17180
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: JBIDE-17180v2.png, wide-window.png
>
>
> JBIDE-13445 added the possibility to use custom deploy dir on remote server.
> {quote}
> Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail.
> {quote}
> We should disable this option in such case, because right now it just adds confusion - you have a server without management port exposed and not knowing about all the details you change the deployment dir, you will end up with non-working deployment.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (JBIDE-13445) Enable possibility of deployment scanner additions for remote servers
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13445?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-13445.
---------------------------------
Fix Version/s: 4.2.1.CR1
(was: 4.2.x)
Resolution: Done
Works in 4.2.1 as expected
> Enable possibility of deployment scanner additions for remote servers
> ---------------------------------------------------------------------
>
> Key: JBIDE-13445
> URL: https://issues.jboss.org/browse/JBIDE-13445
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.1.CR1
>
>
> Currently, additions tot he deployment scanners are limited to locally running servers. This is due to a lack of API allowing accurate discovery of what folders need to be added for remote servers, specifically no way for as.core classes to discover what the remote server home is, what the remote configuration folder is, etc. There is a lack of api here, and that will need to be fixed before this issue can work.
> Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
