[JBoss JIRA] (JBIDE-13266) Use pack200 to speed up download and install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13266?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13266:
------------------------------------
Two comments in http://wiki.eclipse.org/Tycho/Pack200 that worry me:
a) "Note that deprecated eclipse-update-site doesn't consider packed artifacts. "
So we'll have to migrate the remaining eclipse-update-site poms to eclipse-repository (and may lose some of the post-processing steps we do right now in https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...)
b) "This does not apply on a full repository. eclipse-repository can only consume existing pack200'ed artifacts, not generate some. "
If I'm reading that correctly, I suspect that means that where today we can build an update site consisting of locally built AND upstream artifacts, in future this will have to be TWO builds: one to build stuff locally, then a second one to aggregate upstream and the local stuff into a single repo w/ pack.gz artifacts. I hope I'm wrong here, as that extra step would be a PITA.
> Use pack200 to speed up download and install
> --------------------------------------------
>
> Key: JBIDE-13266
> URL: https://issues.jboss.org/browse/JBIDE-13266
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Affects Versions: 4.0.0.CR1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
>
> p2 provides the pack200 stuff, which offers a better compressions for jars, and then that makes downloads faster when installing.
> We should set up our repo to create the pack200'd artifacts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-13446) Forge pick-up command throws NPE on Mac
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13446?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-13446:
-----------------------------------
I'll take a look at it
> Forge pick-up command throws NPE on Mac
> ---------------------------------------
>
> Key: JBIDE-13446
> URL: https://issues.jboss.org/browse/JBIDE-13446
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Environment: OS X Mountain Lion
> Apple JDK 1.6 32bit
> JBDS 6.0.0.GA / JBT master nightly 4.1.0.Alpha1-v20130129-1449-B6053 on Eclipse Kepler M4
> Reporter: Martin Malina
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.0.1.Final, 4.1.x
>
>
> When playing around w/ Ticket Monster [1] I found out that Show in -> Forge console does not work for me on a project or directory in Project Explorer.
> It throws this exception:
> {code}
> [no project] workspace $ set VERBOSE true
> [no project] workspace $ pick-up /Users/rasp/jbossqa/JBDS/nightly-jbt-2013-01-30/workspace/jboss-javaee6-webapp
> java.lang.NullPointerException***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)
> [no project] workspace $
> at org.apache.maven.RepositoryUtils.getLayout(RepositoryUtils.java:214)
> at org.apache.maven.RepositoryUtils.toRepo(RepositoryUtils.java:200)
> at org.apache.maven.RepositoryUtils.toRepos(RepositoryUtils.java:190)
> at org.apache.maven.project.DefaultProjectBuilder$InternalConfig.<init>(DefaultProjectBuilder.java:662)
> at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:102)
> at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:86)
> at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:304)
> at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:393)
> at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:171)
> at org.jboss.forge.shell.project.DependencyInstallerImpl.isInstalled(DependencyInstallerImpl.java:170)
> at org.jboss.forge.git.GitAPIFacet.isInstalled(GitAPIFacet.java:42)
> at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153)
> at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208)
> at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186)
> at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178)
> at org.jboss.forge.project.services.ProjectFactory.findProjectRecursively(ProjectFactory.java:117)
> at org.jboss.forge.shell.project.ProjectInitializer.doInit(ProjectInitializer.java:91)
> 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.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
> at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
> at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
> at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628)
> at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75)
> at org.jboss.forge.shell.project.CurrentProject.setCurrentResource(CurrentProject.java:80)
> at org.jboss.forge.shell.ShellImpl.setCurrentResource(ShellImpl.java:1239)
> at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.setCurrentResource(ShellImpl$Proxy$_$$_WeldClientProxy.java)
> at org.jboss.forge.shell.plugins.builtin.PickupResourcePlugin.run(PickupResourcePlugin.java:85)
> 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.jboss.forge.shell.command.Execution.perform(Execution.java:134)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
> at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:818)
> at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:841)
> at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:631)
> 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.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
> at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)
> 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.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
> at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
> at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
> at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)
> at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:172)
> at java.lang.Thread.run(Thread.java:722)
> {code}
> This happens in both JBDS 6 and JBT 4.1 nightly, but not in JBDS 5. It's probably only reproducible on Mac - psrna verified this on Linux today and it worked for him. I tried two different instances of JBDS 6 and one instance of JBT 4.1.0.Alpha1 nightly installed on Eclipse Kepler M4.
> Please let me know if I should create a FORGE issue.
> The forge runtime versions:
> JBDS 6: org.jboss.tools.forge.runtime_1.1.0.Final-v20121205-1934-B69
> JBT nightly: org.jboss.tools.forge.runtime_1.2.0.Alpha1-v20130128-1407-B204
> [1] http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/#_...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-13266) Use pack200 to speed up download and install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13266?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13266 at 1/30/13 9:44 AM:
-------------------------------------------------------------
If we start building w/ JDK 7, we will at least ensure that all clients can unpack our stuff:
{quote}Previously, the pack200 tool defaulted to using java6 packfiles in the absence of any java6 (or newer) classfiles in a segment. Starting with JDK 7, the pack200 tool defaults to using java5 packfiles for maximum compatibility.{quote}
-- http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html
And with everyone being forced to move to JRE7, this should probably be fine:
http://www.oracle.com/technetwork/java/javase/documentation/autoupdate-16...
That said, Kepler M5 contains 4442 plugins and 3618 packed plugins. If this tech was really enterprise-ready, wouldn't all the plugins in there be packed?
was (Author: nickboldt):
If we start building w/ JDK 7, we will at least ensure that all clients can unpack our stuff:
{quote}Previously, the pack200 tool defaulted to using java6 packfiles in the absence of any java6 (or newer) classfiles in a segment. Starting with JDK 7, the pack200 tool defaults to using java5 packfiles for maximum compatibility.{quote}
-- http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html
And with everyone being forced to move to JRE7, this should probably be fine:
http://www.oracle.com/technetwork/java/javase/documentation/autoupdate-16...
> Use pack200 to speed up download and install
> --------------------------------------------
>
> Key: JBIDE-13266
> URL: https://issues.jboss.org/browse/JBIDE-13266
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Affects Versions: 4.0.0.CR1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
>
> p2 provides the pack200 stuff, which offers a better compressions for jars, and then that makes downloads faster when installing.
> We should set up our repo to create the pack200'd artifacts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-13449) JBT 4.1.0.Alpha1 nightly will not install on Juno
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13449?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-13449.
------------------------------
Release Notes Text:
JBoss Tools 4.1 requires Kepler due to API changes within Dali (part of Web Tools Project) which prevents Hibernate Tools from installing to BOTH Juno and Kepler.
Therefore, Hibernate Tools in 4.1 will be updated to run on Kepler, and Hibernate Tools in 4.0 will continue to run on Juno.
Resolution: Won't Fix
Everything but Hibernate Tools, which relies on Dali, which broke API for the 3rd year in a row.
So, currently, the whole of JBT 4.1 requires Kepler. But the pieces of JBT which don't require Hibernate Tools can be installed to Juno.
> JBT 4.1.0.Alpha1 nightly will not install on Juno
> -------------------------------------------------
>
> Key: JBIDE-13449
> URL: https://issues.jboss.org/browse/JBIDE-13449
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment: OS X 10.8 Mountain Lion
> Java 1.6 32bit
> eclipse-jee-indigo-SR2-macosx-cocoa.tar.gz
> JBT nightly 4.1.0.Alpha1-v20130129-1449-B6053
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha1
>
>
> Today I tried installing JBT nightly [1] on a clean installation of Juno SR2 and there are many conflicts in dependencies:
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Maven Portlet Configurator 1.5.0.Alpha1-v20130124-1009-B213 (org.jboss.tools.maven.portlet.feature.feature.group 1.5.0.Alpha1-v20130124-1009-B213)
> Software currently installed: Eclipse IDE for Java EE Developers 1.4.2.20120213-0813 (epp.package.jee 1.4.2.20120213-0813)
> Only one of the following can be installed at once:
> Debug Core 3.7.0.v20110518 (org.eclipse.debug.core 3.7.0.v20110518)
> Debug Core 3.7.100.v20120521-2012 (org.eclipse.debug.core 3.7.100.v20120521-2012)
> Debug Core 3.7.1.v20111129-2031 (org.eclipse.debug.core 3.7.1.v20111129-2031)
> Cannot satisfy dependency:
> From: Eclipse IDE for Java EE Developers 1.4.2.20120213-0813 (epp.package.jee 1.4.2.20120213-0813)
> To: org.eclipse.epp.package.jee.feature.feature.group [1.4.2.20120213-0813]
> Cannot satisfy dependency:
> From: Java EE IDE Feature 1.4.2.20120213-0813 (org.eclipse.epp.package.jee.feature.feature.group 1.4.2.20120213-0813)
> To: org.eclipse.platform.feature.group [3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q]
> Cannot satisfy dependency:
> From: Eclipse Platform 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q (org.eclipse.platform.feature.group 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q)
> To: org.eclipse.debug.core [3.7.1.v20111129-2031]
> Cannot satisfy dependency:
> From: JBoss AS Core Plug-in 2.4.100.Alpha1-v20130129-1810-B163 (org.jboss.ide.eclipse.as.core 2.4.100.Alpha1-v20130129-1810-B163)
> To: bundle org.jboss.ide.eclipse.as.wtp.core 0.0.0
> Cannot satisfy dependency:
> From: WTP Overrides Core 2.4.100.Alpha1-v20130129-1810-B163 (org.jboss.ide.eclipse.as.wtp.core 2.4.100.Alpha1-v20130129-1810-B163)
> To: bundle org.eclipse.debug.core 3.7.100
> Cannot satisfy dependency:
> From: JBoss Maven Portlet Configurator 1.5.0.Alpha1-v20130124-1009-B213 (org.jboss.tools.maven.portlet 1.5.0.Alpha1-v20130124-1009-B213)
> To: bundle org.jboss.tools.portlet.core 0.0.0
> Cannot satisfy dependency:
> From: JBoss Maven Portlet Configurator 1.5.0.Alpha1-v20130124-1009-B213 (org.jboss.tools.maven.portlet.feature.feature.group 1.5.0.Alpha1-v20130124-1009-B213)
> To: org.jboss.tools.maven.portlet [1.5.0.Alpha1-v20130124-1009-B213]
> Cannot satisfy dependency:
> From: Portlet Core Plug-in 1.4.0.Alpha1-v20130128-2009-B183 (org.jboss.tools.portlet.core 1.4.0.Alpha1-v20130128-2009-B183)
> To: bundle org.jboss.ide.eclipse.as.core 0.0.0
> {code}
> It works on Kepler M4.
> AFAIK, 4.1.0 should work on both Juno and Kepler, correct?
> [1] http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-13450) New SSH Key Wizard: add a passphare confirmation field
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-13450:
-------------------------------------
Summary: New SSH Key Wizard: add a passphare confirmation field
Key: JBIDE-13450
URL: https://issues.jboss.org/browse/JBIDE-13450
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.0.0.Final
Reporter: Xavier Coulon
Assignee: Andre Dietisheim
Fix For: 4.1.x
There's a single passphare field when creating a new SSH Key Pair. This form could have a second "Confirm passphare" field to check that the user did not make a typo when typing his passphrase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-13449) JBT 4.1.0.Alpha1 nightly will not install on Juno
by Martin Malina (JIRA)
Martin Malina created JBIDE-13449:
-------------------------------------
Summary: JBT 4.1.0.Alpha1 nightly will not install on Juno
Key: JBIDE-13449
URL: https://issues.jboss.org/browse/JBIDE-13449
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.1.0.Alpha1
Environment: OS X 10.8 Mountain Lion
Java 1.6 32bit
eclipse-jee-indigo-SR2-macosx-cocoa.tar.gz
JBT nightly 4.1.0.Alpha1-v20130129-1449-B6053
Reporter: Martin Malina
Assignee: Nick Boldt
Fix For: 4.1.0.Alpha1
Today I tried installing JBT nightly [1] on a clean installation of Juno SR2 and there are many conflicts in dependencies:
{code}
Cannot complete the install because of a conflicting dependency.
Software being installed: JBoss Maven Portlet Configurator 1.5.0.Alpha1-v20130124-1009-B213 (org.jboss.tools.maven.portlet.feature.feature.group 1.5.0.Alpha1-v20130124-1009-B213)
Software currently installed: Eclipse IDE for Java EE Developers 1.4.2.20120213-0813 (epp.package.jee 1.4.2.20120213-0813)
Only one of the following can be installed at once:
Debug Core 3.7.0.v20110518 (org.eclipse.debug.core 3.7.0.v20110518)
Debug Core 3.7.100.v20120521-2012 (org.eclipse.debug.core 3.7.100.v20120521-2012)
Debug Core 3.7.1.v20111129-2031 (org.eclipse.debug.core 3.7.1.v20111129-2031)
Cannot satisfy dependency:
From: Eclipse IDE for Java EE Developers 1.4.2.20120213-0813 (epp.package.jee 1.4.2.20120213-0813)
To: org.eclipse.epp.package.jee.feature.feature.group [1.4.2.20120213-0813]
Cannot satisfy dependency:
From: Java EE IDE Feature 1.4.2.20120213-0813 (org.eclipse.epp.package.jee.feature.feature.group 1.4.2.20120213-0813)
To: org.eclipse.platform.feature.group [3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q]
Cannot satisfy dependency:
From: Eclipse Platform 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q (org.eclipse.platform.feature.group 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q)
To: org.eclipse.debug.core [3.7.1.v20111129-2031]
Cannot satisfy dependency:
From: JBoss AS Core Plug-in 2.4.100.Alpha1-v20130129-1810-B163 (org.jboss.ide.eclipse.as.core 2.4.100.Alpha1-v20130129-1810-B163)
To: bundle org.jboss.ide.eclipse.as.wtp.core 0.0.0
Cannot satisfy dependency:
From: WTP Overrides Core 2.4.100.Alpha1-v20130129-1810-B163 (org.jboss.ide.eclipse.as.wtp.core 2.4.100.Alpha1-v20130129-1810-B163)
To: bundle org.eclipse.debug.core 3.7.100
Cannot satisfy dependency:
From: JBoss Maven Portlet Configurator 1.5.0.Alpha1-v20130124-1009-B213 (org.jboss.tools.maven.portlet 1.5.0.Alpha1-v20130124-1009-B213)
To: bundle org.jboss.tools.portlet.core 0.0.0
Cannot satisfy dependency:
From: JBoss Maven Portlet Configurator 1.5.0.Alpha1-v20130124-1009-B213 (org.jboss.tools.maven.portlet.feature.feature.group 1.5.0.Alpha1-v20130124-1009-B213)
To: org.jboss.tools.maven.portlet [1.5.0.Alpha1-v20130124-1009-B213]
Cannot satisfy dependency:
From: Portlet Core Plug-in 1.4.0.Alpha1-v20130128-2009-B183 (org.jboss.tools.portlet.core 1.4.0.Alpha1-v20130128-2009-B183)
To: bundle org.jboss.ide.eclipse.as.core 0.0.0
{code}
It works on Kepler M4.
AFAIK, 4.1.0 should work on both Juno and Kepler, correct?
[1] http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-13448) New SSH Key Wizard: private key and public key accepted values
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-13448:
-------------------------------------
Summary: New SSH Key Wizard: private key and public key accepted values
Key: JBIDE-13448
URL: https://issues.jboss.org/browse/JBIDE-13448
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.0.0.Final
Reporter: Xavier Coulon
Assignee: Andre Dietisheim
Fix For: 4.1.x
In the "Add new SSH Key" wizard, the "Private Key" and "Public Key" fields allow for "/" character, which should not be allowed since the expected values are file names, not file paths.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-13447) SSH2 Creation Wizard: improve field readability
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-13447:
-------------------------------------
Summary: SSH2 Creation Wizard: improve field readability
Key: JBIDE-13447
URL: https://issues.jboss.org/browse/JBIDE-13447
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.0.0.Final
Reporter: Xavier Coulon
Assignee: Andre Dietisheim
Priority: Minor
Fix For: 4.1.x
In the "Add new SSH Key" wizard, the "Private Key" and "Public Key" fields could be labelled "Private Key Filename" and "Public Key Filename" to reflect the fact that expect inputs are filenames (relative to the path shown in the field above those two ones)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-13446) Forge pick-up command throws NPE on Mac
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13446?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-13446:
----------------------------------
Priority: Critical (was: Major)
> Forge pick-up command throws NPE on Mac
> ---------------------------------------
>
> Key: JBIDE-13446
> URL: https://issues.jboss.org/browse/JBIDE-13446
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Environment: OS X Mountain Lion
> Apple JDK 1.6 32bit
> JBDS 6.0.0.GA / JBT master nightly 4.1.0.Alpha1-v20130129-1449-B6053 on Eclipse Kepler M4
> Reporter: Martin Malina
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.0.1.Final, 4.1.x
>
>
> When playing around w/ Ticket Monster [1] I found out that Show in -> Forge console does not work for me on a project or directory in Project Explorer.
> It throws this exception:
> {code}
> [no project] workspace $ set VERBOSE true
> [no project] workspace $ pick-up /Users/rasp/jbossqa/JBDS/nightly-jbt-2013-01-30/workspace/jboss-javaee6-webapp
> java.lang.NullPointerException***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)
> [no project] workspace $
> at org.apache.maven.RepositoryUtils.getLayout(RepositoryUtils.java:214)
> at org.apache.maven.RepositoryUtils.toRepo(RepositoryUtils.java:200)
> at org.apache.maven.RepositoryUtils.toRepos(RepositoryUtils.java:190)
> at org.apache.maven.project.DefaultProjectBuilder$InternalConfig.<init>(DefaultProjectBuilder.java:662)
> at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:102)
> at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:86)
> at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:304)
> at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:393)
> at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:171)
> at org.jboss.forge.shell.project.DependencyInstallerImpl.isInstalled(DependencyInstallerImpl.java:170)
> at org.jboss.forge.git.GitAPIFacet.isInstalled(GitAPIFacet.java:42)
> at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153)
> at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208)
> at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186)
> at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178)
> at org.jboss.forge.project.services.ProjectFactory.findProjectRecursively(ProjectFactory.java:117)
> at org.jboss.forge.shell.project.ProjectInitializer.doInit(ProjectInitializer.java:91)
> 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.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
> at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
> at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
> at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628)
> at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75)
> at org.jboss.forge.shell.project.CurrentProject.setCurrentResource(CurrentProject.java:80)
> at org.jboss.forge.shell.ShellImpl.setCurrentResource(ShellImpl.java:1239)
> at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.setCurrentResource(ShellImpl$Proxy$_$$_WeldClientProxy.java)
> at org.jboss.forge.shell.plugins.builtin.PickupResourcePlugin.run(PickupResourcePlugin.java:85)
> 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.jboss.forge.shell.command.Execution.perform(Execution.java:134)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
> at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:818)
> at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:841)
> at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:631)
> 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.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
> at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)
> 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.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
> at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
> at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
> at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)
> at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:172)
> at java.lang.Thread.run(Thread.java:722)
> {code}
> This happens in both JBDS 6 and JBT 4.1 nightly, but not in JBDS 5. It's probably only reproducible on Mac - psrna verified this on Linux today and it worked for him. I tried two different instances of JBDS 6 and one instance of JBT 4.1.0.Alpha1 nightly installed on Eclipse Kepler M4.
> Please let me know if I should create a FORGE issue.
> The forge runtime versions:
> JBDS 6: org.jboss.tools.forge.runtime_1.1.0.Final-v20121205-1934-B69
> JBT nightly: org.jboss.tools.forge.runtime_1.2.0.Alpha1-v20130128-1407-B204
> [1] http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/#_...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months