April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-26) Cannot install bpel from update site

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-26?page=com.atlassian.jira.plugin.s... ] Paul Leacu reassigned JBTIS-26: ------------------------------- Assignee: Robert (Bob) Brodt Hey Bob - I don't know why I didn't see this before. It's critical for the JBTIS alpha - can you take a look? Thanks! --paull > Cannot install bpel from update site > ------------------------------------ > > Key: JBTIS-26 > URL: https://issues.jboss.org/browse/JBTIS-26 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: releng > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Attachments: bpel-error.txt > > > I'm not able to install JBoss BPEL Editor into Eclipse Juno JEE (see the attached file) from JBTIS update site > http://download.jboss.org/jbosstools/updates/integration/juno/integration... > Maybe there is something wrong with the aggregation definition because I'm able to install the same BPEL editor from > http://download.jboss.org/jbosstools/updates/integration/juno/integration... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-26) Cannot install bpel from update site

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-26?page=com.atlassian.jira.plugin.s... ] Paul Leacu commented on JBTIS-26: --------------------------------- I'm unable to install as well - same issue. The JBTIS composites are using this for BPEL:  <child location="http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.0_stable..."/> Is that correct? I get the same failure using: <child location="http://download.jboss.org/jbosstools/updates/integration/juno/integration..."/> Error: An error occurred while collecting items to be installed session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). No repository found containing: osgi.bundle,org.eclipse.bpel.apache.ode.deploy.model,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.apache.ode.deploy.ui,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.apache.ode.runtime,1.0.2.v20121121-1634-CI No repository found containing: org.eclipse.update.feature,org.eclipse.bpel.apache.ode.runtime.feature,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.cheatsheet,1.0.2.v20121121-1634-CI No repository found containing: org.eclipse.update.feature,org.eclipse.bpel.common.feature,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.common.model,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.common.ui,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.common.wsdl,1.0.2.v20121121-1634-CI No repository found containing: org.eclipse.update.feature,org.eclipse.bpel.feature,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.help,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.model,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.runtimes,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.ui,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.validator,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.wsil.model,1.0.2.v20121121-1634-CI No repository found containing: osgi.bundle,org.eclipse.bpel.xpath10,1.0.2.v20121121-1634-CI > Cannot install bpel from update site > ------------------------------------ > > Key: JBTIS-26 > URL: https://issues.jboss.org/browse/JBTIS-26 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: releng > Reporter: Andrej Podhradsky > Attachments: bpel-error.txt > > > I'm not able to install JBoss BPEL Editor into Eclipse Juno JEE (see the attached file) from JBTIS update site > http://download.jboss.org/jbosstools/updates/integration/juno/integration... > Maybe there is something wrong with the aggregation definition because I'm able to install the same BPEL editor from > http://download.jboss.org/jbosstools/updates/integration/juno/integration... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13928) Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13928?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13928. ------------------------------ Resolution: Rejected Sounds like the consensus here is that while maven.apt needs to be included, sources do not. Even though the namespace is org.jboss, maven.apt is treated like an upstream 3rd party component, not a part of JBT/JBDS proper, so sources are not required to be included in distributions. > Should JBoss Tools and JBDS include org.jboss.tools.maven.apt.feature.source, or just org.jboss.tools.maven.apt.feature? > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13928 > URL: https://issues.jboss.org/browse/JBIDE-13928 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Affects Versions: 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > > In JBIDE-12310 a source feature was added to org.jboss.tools.maven.apt.feature, but the second part of the JIRA was never done -- adding that feature to JBT and JBDS. > Today, I attempted to add it, and realized that unless we add org.jboss.tools.maven.apt.feature.source to the target platform it won't be available when creating the JBT or JBDS aggregate sites. > Do we care? Do we need the sources for this feature/plugin included in JBT and JBDS? > If we only need it in JBDS I can add the latest m2e mirror to the Central/Extras site [1] and be able to resolve it from there. > [1] https://devstudio.jboss.com/updates/7.0-development/extras/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-47) Create 4.1 branch for Eclipse Kepler release

by Rob Cernich (JIRA)

Rob Cernich created JBTIS-47: -------------------------------- Summary: Create 4.1 branch for Eclipse Kepler release Key: JBTIS-47 URL: https://issues.jboss.org/browse/JBTIS-47 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Components: distribution, target-platform Reporter: Rob Cernich Assignee: Paul Leacu Please update the target platform to point to the JBT Eclipse Kepler base and JBT 4.1. Update additional integration stack dependencies to their Kepler versions (e.g. EMF compare, Graphiti, etc.). This should involve the creation of a 4.1 branch in the integration-stack project and a 4.1 version in JIRA. Notify component owners per the release process under platform updates here https://community.jboss.org/wiki/IntegrationToolingReleaseProcess This effort should begin the end of April, beginning of May. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13940) SiteTest.testInvalidSites fails

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-13940: ------------------------------------- Summary: SiteTest.testInvalidSites fails Key: JBIDE-13940 URL: https://issues.jboss.org/browse/JBIDE-13940 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.1.0.Alpha1 Reporter: Snjezana Peco Assignee: Snjezana Peco The http://download.jboss.org/gatein/quickstarts/gatein-3.6/project-examples-... project example has been added to the o.j.t.community.project.examples plugin, but the corresponding link hasn't been created. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13929) Cannot install m2 facet when jst.seam facet is missing

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13929?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13929: -------------------------------- Fix Version/s: 4.1.0.Alpha2 4.1.0.Beta1 > Cannot install m2 facet when jst.seam facet is missing > ------------------------------------------------------ > > Key: JBIDE-13929 > URL: https://issues.jboss.org/browse/JBIDE-13929 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.0.0.Final > Reporter: Rob Cernich > Assignee: Fred Bricon > Fix For: 4.1.0.Alpha2, 4.1.0.Beta1 > > > An IllegalArgumentException is produced when loading MavenFacetInstallPage when the jst.seam facet is missing. One should be able to install the m2 facet regardless of whether or not seam tooling is installed. > This is the line where the exception is thrown: > public static final IProjectFacet SEAM_FACET = ProjectFacetsManager.getProjectFacet(SEAM_FACET_ID); > This should be moved to a static init block to either catch the exception or check to see if the facet is defined first. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13905) portlet-api library of JPP 6 is not imported

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13905?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-13905 at 4/5/13 9:50 AM: --------------------------------------------------------------- {quote} The existing hardcodings are equally broken. {quote} I know that isn't the best option. We can use a better solution for JBoss servers when it is found. {quote} EAP 6.1 has a different module layout structure so don't assume that will work if you are hardcoding this. {quote} {quote} [~mstruk] says that in JPP 6.1 (which will be based on EAP 6.1), portlet-api.jar module should be located at modules/system/add-ons/gatein/javax/portlet/api/main/ {quote} I have included this directory when searching portlet-api.jar. was (Author: snjeza): {quote} The existing hardcodings are equally broken. {quote} I know that isn't the best option. We can use a better solution for JBoss servers when it is found. {quote} EAP 6.1 has a different module layout structure so don't assume that will work if you are hardcoding this. {quote} {quote} Marko Strukelj says that in JPP 6.1 (which will be based on EAP 6.1), portlet-api.jar module should be located at modules/system/add-ons/gatein/javax/portlet/api/main/ {quote} I have included this directory when searching portlet-api.jar. > portlet-api library of JPP 6 is not imported > -------------------------------------------- > > Key: JBIDE-13905 > URL: https://issues.jboss.org/browse/JBIDE-13905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Portal/GateIn > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Petr Suchý > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > When you want to create Dynamic Web Project using JPP 6.0.0.GA, you cannot simply choose Portlet implementation library as a Portlet Target Runtime Provider in a New Dynamic Web Project Wizard. You are forced to add _portlet-api.jar_ manually from here: > {code} > ${JPP6}/modules/javax/portlet/api/main/ > {code} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13905) portlet-api library of JPP 6 is not imported

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13905?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13905: --------------------------------------- {quote} The existing hardcodings are equally broken. {quote} I know that isn't the best option. We can use a better solution for JBoss servers when it is found. {quote} EAP 6.1 has a different module layout structure so don't assume that will work if you are hardcoding this. {quote} {quote} Marko Strukelj says that in JPP 6.1 (which will be based on EAP 6.1), portlet-api.jar module should be located at modules/system/add-ons/gatein/javax/portlet/api/main/ {quote} I have included this directory when searching portlet-api.jar. > portlet-api library of JPP 6 is not imported > -------------------------------------------- > > Key: JBIDE-13905 > URL: https://issues.jboss.org/browse/JBIDE-13905 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Portal/GateIn > Affects Versions: 4.0.1.Final, 4.1.0.Alpha1 > Reporter: Petr Suchý > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > When you want to create Dynamic Web Project using JPP 6.0.0.GA, you cannot simply choose Portlet implementation library as a Portlet Target Runtime Provider in a New Dynamic Web Project Wizard. You are forced to add _portlet-api.jar_ manually from here: > {code} > ${JPP6}/modules/javax/portlet/api/main/ > {code} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13939) Usage tests freeze on Kepler M6

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-13939: ------------------------------------- Summary: Usage tests freeze on Kepler M6 Key: JBIDE-13939 URL: https://issues.jboss.org/browse/JBIDE-13939 Project: Tools (JBoss Tools) Issue Type: Bug Components: usage Affects Versions: 4.1.0.Alpha1, 4.1.0.Alpha2 Reporter: Snjezana Peco Assignee: Snjezana Peco The usage tests freezes because they are executed before calling the UsageReportEnablementDialog dialog. They set the "usage_reporting_enabled" property to true which enables opening the UsageReportEnablementDialog dialog. The fix is to set usage_reporting_enabled=false after the latest test (UsageIntegrationTest). The issue happens on Kepler M6. I suppose it is caused by some changes related to the handling UI messagess/jobs. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13919) Integrate LiveReload in JBT site

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13919?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13919: ---------------------------------------- New PR for master: https://github.com/jbosstools/jbosstools-build-sites/pull/61 > Integrate LiveReload in JBT site > -------------------------------- > > Key: JBIDE-13919 > URL: https://issues.jboss.org/browse/JBIDE-13919 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > Add the livereload feature to aggregation. -- 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, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2013