[JBoss JIRA] (JBIDE-13594) org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13594?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-13594 at 2/26/13 6:16 PM:
----------------------------------------------------------------
You are mixing modules and sub-components in your comment. On picture above I show only modules (read - git repositories). Integration-stack/aggregated-site *subcomponent* which adds esb dependency to integration-stack module. At the same time esb requires integration-stack/target-platform *sub-component* to be built which adds integration-stack dependency to esb.
So there is a cycle between modules.
was (Author: dgolovin):
You are mixing modules and sub-components in your comment. On picture above I show only modules (read - git repositories). Integration-stack/aggregated-site *subcomponent* which adds esb dependency to integration-stack module. At the same time esb requires integration-stack/target-platform *sub-component* to be built which adds integration-stack dependency to esb.
So there is cycle between modules.
> org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-13594
> URL: https://issues.jboss.org/browse/JBIDE-13594
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, esb, testing
> Affects Versions: 4.1.0.Alpha1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
> Attachments: dependencies.png
>
>
> jbosstools integration tests job in jenkins is currently blocked because of unsatisfied dependency:
> {code}
> Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.layouts 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.layouts 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."]
> 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)
> {code}
> See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...
> This happens because zest has been removed from the core target platform into JBTIS target platform as described in JBIDE-13435.
> I originally thought this needs to be fixed by the esb compoment owner, but after learning that zest is now in JBTIS target platform, what actually seems needs to be done is use the JBTIS target platform for the job.
> Or disregard this JIRA and split the integration tests and soa integration tests sites/jobs as suggested in JBIDE-12974.
--
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-13594) org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13594?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-13594:
---------------------------------------
You are mixing modules and sub-components in your comment. On picture above I show only modules (read - git repositories). Integration-stack/aggregated-site *subcomponent* which adds esb dependency to integration-stack module. At the same time esb requires integration-stack/target-platform *sub-component* to be built which adds integration-stack dependency to esb.
So there is cycle between modules.
> org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-13594
> URL: https://issues.jboss.org/browse/JBIDE-13594
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, esb, testing
> Affects Versions: 4.1.0.Alpha1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
> Attachments: dependencies.png
>
>
> jbosstools integration tests job in jenkins is currently blocked because of unsatisfied dependency:
> {code}
> Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.layouts 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.layouts 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."]
> 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)
> {code}
> See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...
> This happens because zest has been removed from the core target platform into JBTIS target platform as described in JBIDE-13435.
> I originally thought this needs to be fixed by the esb compoment owner, but after learning that zest is now in JBTIS target platform, what actually seems needs to be done is use the JBTIS target platform for the job.
> Or disregard this JIRA and split the integration tests and soa integration tests sites/jobs as suggested in JBIDE-12974.
--
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-13594) org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13594?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-13594:
---------------------------------------
Where is SOA Tools then?
> org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-13594
> URL: https://issues.jboss.org/browse/JBIDE-13594
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, esb, testing
> Affects Versions: 4.1.0.Alpha1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
> Attachments: dependencies.png
>
>
> jbosstools integration tests job in jenkins is currently blocked because of unsatisfied dependency:
> {code}
> Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.layouts 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.layouts 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."]
> 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)
> {code}
> See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...
> This happens because zest has been removed from the core target platform into JBTIS target platform as described in JBIDE-13435.
> I originally thought this needs to be fixed by the esb compoment owner, but after learning that zest is now in JBTIS target platform, what actually seems needs to be done is use the JBTIS target platform for the job.
> Or disregard this JIRA and split the integration tests and soa integration tests sites/jobs as suggested in JBIDE-12974.
--
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-13641) tycho plugin snapshot 0.0.1 disappeared - causing failing builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13641?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-13641:
----------------------------------
Assignee: Mickael Istria (was: Nick Boldt)
I believe this should be assigned to [~mickael_istria] as he's handling releasing maven plugins being released to Nexus release site. Actually, I think this may already be done - 0.16.0.CR1 is released, right?
> tycho plugin snapshot 0.0.1 disappeared - causing failing builds
> ----------------------------------------------------------------
>
> Key: JBIDE-13641
> URL: https://issues.jboss.org/browse/JBIDE-13641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.1.0.Alpha2
>
>
> snapshots gets purged every 90-days and our builds were using old snapshot.
> for 4.1.0.Alpha1x i'll do the minimal fix but for 4.0.x and 4.1.x we need a more permanent solution.
--
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-13641) tycho plugin snapshot 0.0.1 disappeared - causing failing builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13641?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13641 at 2/26/13 4:46 PM:
-------------------------------------------------------------
I believe this should be assigned to [~mickael_istria] as he's handling releasing maven plugins being released to Nexus release site. Actually, I think this may already be done - 0.16.0.CR1 is released, right?
So, all that's left is to ensure that 4.0.x branch projects and 4.1.x projects can still build - perhaps some site/pom.xml files need updating?
was (Author: nickboldt):
I believe this should be assigned to [~mickael_istria] as he's handling releasing maven plugins being released to Nexus release site. Actually, I think this may already be done - 0.16.0.CR1 is released, right?
> tycho plugin snapshot 0.0.1 disappeared - causing failing builds
> ----------------------------------------------------------------
>
> Key: JBIDE-13641
> URL: https://issues.jboss.org/browse/JBIDE-13641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.1.0.Alpha2
>
>
> snapshots gets purged every 90-days and our builds were using old snapshot.
> for 4.1.0.Alpha1x i'll do the minimal fix but for 4.0.x and 4.1.x we need a more permanent solution.
--
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] (JBDS-2393) remove all references to JBDS Extras site from within JBDS 7
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2393?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2393:
-----------------------------
Fix Version/s: 7.0.0.Alpha2
(was: 7.0.0.Alpha1)
> remove all references to JBDS Extras site from within JBDS 7
> ------------------------------------------------------------
>
> Key: JBDS-2393
> URL: https://issues.jboss.org/browse/JBDS-2393
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, updatesite
> Affects Versions: 7.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 7.0.0.Alpha2
>
>
> The following files in devstudio svn trunk need to be revised to no longer reference an extras/ site, if in fact we're going to obsolete it in favour of the Central composite site.
> {quote}
> ./documentation/Release_Guide/2012_Release_JBDS_Staging_For_QE.txt
> ./devstudio.jboss.com/updates/6.0/central/core/compositeArtifacts.xml
> ./devstudio.jboss.com/updates/6.0/central/core/compositeContent.xml
> ./devstudio.jboss.com/updates/6.0-staging/central/core/compositeArtifacts.xml
> ./devstudio.jboss.com/updates/6.0-staging/central/core/compositeContent.xml
> ./devstudio.jboss.com/updates/6.0-staging/updatesites.xml
> ./devstudio.jboss.com/updates/6.0-staging/index.html
> ./devstudio.jboss.com/updates/6.0/index.html
> ./devstudio.jboss.com/updates/6.0/updatesites.xml
> ./product/features/com.jboss.jbds.product.feature.source/feature.xml
> ./product/site/associate.properties
> ./extras/site/associate.properties
> ./techpreview/features/com.jboss.jbds.byoe.feature/feature.xml
> ./techpreview/site/associate.properties
> ./product-soa/site/associate.properties
> ./qa/install-extras/jbds.properties
> {quote}
--
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] (JBDS-2389) cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2389?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2389:
-----------------------------
Fix Version/s: 7.0.0.Alpha2
(was: 7.0.0.Alpha1)
> cannot uninstall JBDS Product Feature - eclipse left in unusable state due to missing eclipse.ini directives
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2389
> URL: https://issues.jboss.org/browse/JBDS-2389
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, updatesite
> Affects Versions: 6.0.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.0.0.Alpha2
>
>
> Steps to repro:
> Unpack bare Juno JEE.
> Install JBDS BYOE feature ("Core Features"). Restart
> Install JBDS Branded Product Feature. Restart.
> Uninstall JBDS Branded Product Feature (or revert configuration to previous). Restart. Eclipse is now broken:
> {code}
> java.lang.RuntimeException: Application "" could not be found in the registry.
> {code}
> Addtional info:
> {quote}
> Bare Juno JEE eclipse.ini:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -product
> org.eclipse.epp.package.jee.product
> --launcher.defaultAction
> openFile
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Dosgi.requiredJavaVersion=1.5
> -Dhelp.lucene.tokenizer=standard
> -XX:MaxPermSize=256m
> -Xms40m
> -Xmx512m
> {code}
> or, for Eclipse Platform Binary:
> {code}
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms40m
> -Xmx384m
> {code}
> After installing JBDS BYOE:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Xms512m
> -Xmx1024m
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> {code}
> After installing JBDS branded product, eclipse.ini becomes jbdevstudio.ini:
> {code}
> $➔ cat eclipse/jbdevstudio.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> -Xms512m
> -Xmx1024m
> -Dosgi.instance.area.default=(a)user.home/workspace
> {code}
> After UNINSTALLING JBDS branded product (to drop back to Eclipse + JBDS BYOE), can no longer start Eclipse. Here is the resulting eclipse.ini file:
> {code}
> $➔ cat eclipse/eclipse.ini
> -startup
> plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20120522-1813
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> -vmargs
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/6.0-staging/devstudio-directory.xml
> -Xms512m
> -Xmx1024m
> {code}
> {quote}
> So, I think we need an instructions.unconfigure in com.jboss.jbds.p2.inf to remove these lines
> {code}
> -product
> com.jboss.jbds.product.product
> -showsplash
> platform:/base/plugins/com.jboss.jbds.product
> {code}
> and replace them with the following when JBDS is uninstalled:
> {code}
> -application
> org.eclipse.ui.ide.workbench
> -showsplash
> org.eclipse.platform
> {code}
> Also need to know what happens if there are two -product directives... can we just
> add (and later remove, when uninstalling) our product to the list, or must we replace
> any existing -product entries with ours?
--
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