March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2456) JBDS should be buildable from source zip (or at least document the limitations)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2456?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2456 at 3/4/13 4:42 PM: ---------------------------------------------------------- Not true. It doesn't take much to have the build-from-sources point at the latest released upstream JBT update site and latest released TP. Possibly need to add a profile to the root pom or document the URLs & therefore commandline flags to use to point to something other than the default CI/nightly URLs. In fact we could generate the root pom when zipping up the sources. was (Author: nickboldt): Not true. It doesn't take much to have the build-from-sources point at the latest released upstream JBT update site and latest released TP. Possibly need to add a profile to the root pom or document the URLs & therefore commandline flags to use to point to something other than the default CI/nightly URLs. > JBDS should be buildable from source zip (or at least document the limitations) > ------------------------------------------------------------------------------- > > Key: JBDS-2456 > URL: https://issues.jboss.org/browse/JBDS-2456 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 6.0.0.GA, 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 7.0.0.Alpha2 > > > As reported here: http://stackoverflow.com/questions/12807472/how-build-jboss-developer-stu... it would be nice if one could build JBDS from the sources zip. [~mmurray] reports that it sort of works but izPack is missing: > {quote}it failed to find the devstudio/product/installer/IzPack-4.3.4.zip{quote} > It should be noted that JBT can be built from github sources (but I don't think we've ever tried to build it from the source zip either). > Ref: https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2456) JBDS should be buildable from source zip (or at least document the limitations)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2456?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2456: ---------------------------------- Not true. It doesn't take much to have the build-from-sources point at the latest released upstream JBT update site and latest released TP. Possibly need to add a profile to the root pom or document the URLs & therefore commandline flags to use to point to something other than the default CI/nightly URLs. > JBDS should be buildable from source zip (or at least document the limitations) > ------------------------------------------------------------------------------- > > Key: JBDS-2456 > URL: https://issues.jboss.org/browse/JBDS-2456 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Affects Versions: 6.0.0.GA, 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 7.0.0.Alpha2 > > > As reported here: http://stackoverflow.com/questions/12807472/how-build-jboss-developer-stu... it would be nice if one could build JBDS from the sources zip. [~mmurray] reports that it sort of works but izPack is missing: > {quote}it failed to find the devstudio/product/installer/IzPack-4.3.4.zip{quote} > It should be noted that JBT can be built from github sources (but I don't think we've ever tried to build it from the source zip either). > Ref: https://community.jboss.org/wiki/HowtoBuildJBossToolswithMaven3 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13619) Mark Struts tooling as deprecated in release notes and optimally inside eclipse

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13619?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13619 at 3/4/13 4:19 PM: ------------------------------------------------------------ Assigning back to project lead, [~akazakov]. Just update your feature.xml/feature.properties and MANIFEST.MF/plugin.properties files to add " (Deprecated)" to each feature & plugin name & description. Should also ensure copyrights are bumped up to 2013 (eg., 2011 -> 2011-2013, 2011-2012 -> 2011-2013). I would throw you a PR but having some problems connecting to github today. was (Author: nickboldt): Just update your feature.xml/feature.properties and plugin.properties/MANIFEST.MF files to add " (Deprecated)" to each feature & plugin name & description. Should also ensure copyrights are bumped up to 2013 (eg., 2011 -> 2011-2013, 2011-2012 -> 2011-2013). I would throw you a PR but having some problems connecting to github today. > Mark Struts tooling as deprecated in release notes and optimally inside eclipse > ------------------------------------------------------------------------------- > > Key: JBIDE-13619 > URL: https://issues.jboss.org/browse/JBIDE-13619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: struts/shale > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.0.1.Final > > > This should be clearly marked in the release notes and would be great if also done in the installation/update somewhere. > My best suggestion is to add "(Deprecated)" into the feature label and description. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13619) Mark Struts tooling as deprecated in release notes and optimally inside eclipse

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13619?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-13619: ---------------------------------- Assignee: Alexey Kazakov (was: Nick Boldt) Just update your feature.xml/feature.properties and plugin.properties/MANIFEST.MF files to add " (Deprecated)" to each feature & plugin name & description. Should also ensure copyrights are bumped up to 2013 (eg., 2011 -> 2011-2013, 2011-2012 -> 2011-2013). I would throw you a PR but having some problems connecting to github today. > Mark Struts tooling as deprecated in release notes and optimally inside eclipse > ------------------------------------------------------------------------------- > > Key: JBIDE-13619 > URL: https://issues.jboss.org/browse/JBIDE-13619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: struts/shale > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.0.1.Final > > > This should be clearly marked in the release notes and would be great if also done in the installation/update somewhere. > My best suggestion is to add "(Deprecated)" into the feature label and description. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13550) Remove JBoss Maven JPA, JSF, JAX-RS features from the JBT4/JBDS6 update sites, installers

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13550?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-13550. --------------------------------- Resolution: Won't Fix > Remove JBoss Maven JPA, JSF, JAX-RS features from the JBT4/JBDS6 update sites, installers > ----------------------------------------------------------------------------------------- > > Key: JBIDE-13550 > URL: https://issues.jboss.org/browse/JBIDE-13550 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Fred Bricon > Assignee: Nick Boldt > Labels: respin-a > Fix For: 4.0.1.Final > > > The JBoss Maven JPA, JSF, JAX-RS being migrated over m2e-wtp, the plugins and features have been removed from the git repo. > We need to make sure the the JBT4/JBDS6 update sites, installers are curated as well. > *Waiting on Juno SR2 release in a couple weeks* -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13619) Mark Struts tooling as deprecated in release notes and optimally inside eclipse

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13619?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-13619: --------------------------------------- I have marked it as "Affects Release Notes" and assigned Nick as a writer > Mark Struts tooling as deprecated in release notes and optimally inside eclipse > ------------------------------------------------------------------------------- > > Key: JBIDE-13619 > URL: https://issues.jboss.org/browse/JBIDE-13619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: struts/shale > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.0.1.Final > > > This should be clearly marked in the release notes and would be great if also done in the installation/update somewhere. > My best suggestion is to add "(Deprecated)" into the feature label and description. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13619) Mark Struts tooling as deprecated in release notes and optimally inside eclipse

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13619?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13619: ---------------------------------- Writer: nickboldt (was: akazakov) > Mark Struts tooling as deprecated in release notes and optimally inside eclipse > ------------------------------------------------------------------------------- > > Key: JBIDE-13619 > URL: https://issues.jboss.org/browse/JBIDE-13619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: struts/shale > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.0.1.Final > > > This should be clearly marked in the release notes and would be great if also done in the installation/update somewhere. > My best suggestion is to add "(Deprecated)" into the feature label and description. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13619) Mark Struts tooling as deprecated in release notes and optimally inside eclipse

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13619?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13619: ---------------------------------- Writer: akazakov > Mark Struts tooling as deprecated in release notes and optimally inside eclipse > ------------------------------------------------------------------------------- > > Key: JBIDE-13619 > URL: https://issues.jboss.org/browse/JBIDE-13619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: struts/shale > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.0.1.Final > > > This should be clearly marked in the release notes and would be great if also done in the installation/update somewhere. > My best suggestion is to add "(Deprecated)" into the feature label and description. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13619) Mark Struts tooling as deprecated in release notes and optimally inside eclipse

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13619?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13619: ---------------------------------- Release Notes Docs Status: Not Yet Documented Affects: Release Notes > Mark Struts tooling as deprecated in release notes and optimally inside eclipse > ------------------------------------------------------------------------------- > > Key: JBIDE-13619 > URL: https://issues.jboss.org/browse/JBIDE-13619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: struts/shale > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.0.1.Final > > > This should be clearly marked in the release notes and would be great if also done in the installation/update somewhere. > My best suggestion is to add "(Deprecated)" into the feature label and description. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13594) org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13594?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13594. ------------------------------ Resolution: Done integration-tests issue moved to JBIDE-13709. > 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-tools > 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, 1 month

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 March 2013