April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14341: --------------------------------------------- I think it is too late for 4.1.x to include this - but we can look at seeing how we can create a basic "cartridge" project just to get started - this won't anyway be able to use Forge 2 since Forge 2 is not ready before June. If Forge 2 will be used, it won't be available when installing OpenShift tooling, but if that requirement is not vital then OpenShift tooling cuold just focus on doing an editor for the file format maybe ? But in general - requiring all of forge 2 plugins for creating a projects makes things tricky IMO. That said what could this plugin do (no matter if forge or IDE driven): Creating the project layout ? Have editor for the manifest.yml ? btw. I assume all this is very Linux OS specific...? is there a way to "run" these modules on a VM remotely somehow ? > Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse > ----------------------------------------------------------------------- > > Key: JBIDE-14341 > URL: https://issues.jboss.org/browse/JBIDE-14341 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Joe Fernandes > Priority: Optional > > OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. > This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE. This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings. > Some key information on the new OpenShift v2 cartridge format: > -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June). All current cartridges are being migrated to the new v2 cartridge format. > -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them. That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL. That is really the core feature of being able to start a cartridge ecosystem. > -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular. Main goal there was to try and simplify, cleanup and better document the process. H > -Here are some of the docs: > Technical docs: > https://github.com/openshift/origin-server/blob/master/node/README.writin... > https://github.com/openshift/origin-server/blob/master/node/README.node_m... > https://github.com/openshift/origin-server/blob/master/node/README.writin... > Getting Started: > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1 > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2 > If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-...) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14341: --------------------------------------------- Requiring Forge for this sounds like super overkill IMO. What would the advantage be for having OpenShift tooling depend on all of Forge 2 for implementing what for now looks like a simple project template ? > Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse > ----------------------------------------------------------------------- > > Key: JBIDE-14341 > URL: https://issues.jboss.org/browse/JBIDE-14341 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Joe Fernandes > Priority: Optional > > OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. > This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE. This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings. > Some key information on the new OpenShift v2 cartridge format: > -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June). All current cartridges are being migrated to the new v2 cartridge format. > -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them. That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL. That is really the core feature of being able to start a cartridge ecosystem. > -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular. Main goal there was to try and simplify, cleanup and better document the process. H > -Here are some of the docs: > Technical docs: > https://github.com/openshift/origin-server/blob/master/node/README.writin... > https://github.com/openshift/origin-server/blob/master/node/README.node_m... > https://github.com/openshift/origin-server/blob/master/node/README.writin... > Getting Started: > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1 > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2 > If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-...) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13863) org.junit4 replaced w/ org.junit; please update your test plugins' manifest.mf files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13863?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13863: ---------------------------------------- Fix Version/s: 4.0.0.Alpha1-SOA > org.junit4 replaced w/ org.junit; please update your test plugins' manifest.mf files > ------------------------------------------------------------------------------------ > > Key: JBIDE-13863 > URL: https://issues.jboss.org/browse/JBIDE-13863 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: modeshape > Affects Versions: 4.0.0.Alpha1-SOA > Reporter: Nick Boldt > Assignee: Dan Florian > Fix For: 4.0.0.Alpha1-SOA > > > Because Kepler M6 target platform no longer includes org.junit4_4.8, and instead includes org.junit_4.11, you will need to adjust your tests' manifest.mf files. > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-integration-tests.aggregate_master/78/console} > [ERROR] Software being installed: site raw:1.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):1.0.0-SNAPSHOT > [ERROR] Missing requirement: org.jboss.tools.modeshape.jcr.test 3.2.0.Alpha1-v20130308-0851-B89 requires 'bundle org.junit4 0.0.0' but it could not be found > [ERROR] Missing requirement: org.jboss.tools.modeshape.jcr.test 3.2.0.Alpha1-v20130313-1951-B90 requires 'bundle org.junit4 0.0.0' but it could not be found > [ERROR] Cannot satisfy dependency: org.jboss.tools.modeshape.jcr.test.feature.feature.group 3.2.0.Alpha1-v20130308-0851-B89 depends on: org.jboss.tools.modeshape.jcr.test [3.2.0.Alpha1-v20130308-0851-B89] > [ERROR] Cannot satisfy dependency: org.jboss.tools.modeshape.jcr.test.feature.feature.group 3.2.0.Alpha1-v20130313-1951-B90 depends on: org.jboss.tools.modeshape.jcr.test [3.2.0.Alpha1-v20130313-1951-B90] > [ERROR] Cannot satisfy dependency: site raw:1.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):1.0.0-SNAPSHOT depends on: org.jboss.tools.modeshape.jcr.test.feature.feature.group 0.0.0 > {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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13799) Source Lookup enhancements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13799?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13799: --------------------------------------------- Put these on 4.1.0.Beta1 for review and at least inclusion of the plain project source lookup which seem to be useful for any kind of project and without affecting users in a bad way. > Source Lookup enhancements > -------------------------- > > Key: JBIDE-13799 > URL: https://issues.jboss.org/browse/JBIDE-13799 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta1 > > > The PR includes the following enhancements: > - AS 7.2/EAP 6.1 are now recognized correctly > - the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2 > - the fix for the ConcurrentModificationException exception > - included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container > - JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search) > - JBoss Java Project Source Container > See http://screencast.com/t/39LHqYx5m > Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2. > Note: > You have to have some deployment on the servers in order the WeldBootstrap class to be created. > You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason. > The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance). -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13836) Add tests to Source Lookup plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13836?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13836: ---------------------------------------- Assignee: Fred Bricon (was: Snjezana Peco) > Add tests to Source Lookup plugin > --------------------------------- > > Key: JBIDE-13836 > URL: https://issues.jboss.org/browse/JBIDE-13836 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Fred Bricon > Fix For: 4.1.0.Beta1 > > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13799) Source Lookup enhancements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13799?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13799: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 > Source Lookup enhancements > -------------------------- > > Key: JBIDE-13799 > URL: https://issues.jboss.org/browse/JBIDE-13799 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta1 > > > The PR includes the following enhancements: > - AS 7.2/EAP 6.1 are now recognized correctly > - the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2 > - the fix for the ConcurrentModificationException exception > - included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container > - JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search) > - JBoss Java Project Source Container > See http://screencast.com/t/39LHqYx5m > Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2. > Note: > You have to have some deployment on the servers in order the WeldBootstrap class to be created. > You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason. > The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance). -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] George Gastaldi edited comment on JBIDE-14341 at 4/29/13 11:06 AM: ------------------------------------------------------------------- This would be an excellent use-case to develop using JBoss Forge. Forge 2 now supports writing IDE Wizards (decoupled from Eclipse) using CDI which could be an excellent choice for this. Alternatively a plugin using JBoss Forge 1 could be another good option as well. was (Author: gastaldi): This would be an excellent use-case to develop using JBoss Forge. Forge 2 now supports writing IDE Wizards (decoupled from Eclipse) using CDI which could be an excellent choice for this. Alternatively a plugin for JBoss Forge could be another option as well. > Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse > ----------------------------------------------------------------------- > > Key: JBIDE-14341 > URL: https://issues.jboss.org/browse/JBIDE-14341 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Joe Fernandes > Priority: Optional > > OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. > This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE. This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings. > Some key information on the new OpenShift v2 cartridge format: > -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June). All current cartridges are being migrated to the new v2 cartridge format. > -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them. That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL. That is really the core feature of being able to start a cartridge ecosystem. > -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular. Main goal there was to try and simplify, cleanup and better document the process. H > -Here are some of the docs: > Technical docs: > https://github.com/openshift/origin-server/blob/master/node/README.writin... > https://github.com/openshift/origin-server/blob/master/node/README.node_m... > https://github.com/openshift/origin-server/blob/master/node/README.writin... > Getting Started: > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1 > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2 > If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-...) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13836) Add tests to Source Lookup plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13836?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13836: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 > Add tests to Source Lookup plugin > --------------------------------- > > Key: JBIDE-13836 > URL: https://issues.jboss.org/browse/JBIDE-13836 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta1 > > -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13851) Add source lookup classes to Java Search

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13851?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-13851: ------------------------------------- This corresponds to a feature that was removed from m2e 1.0 : http://www.sonatype.com/people/2010/03/adding-dependencies-using-m2eclipse/ > Add source lookup classes to Java Search > ---------------------------------------- > > Key: JBIDE-13851 > URL: https://issues.jboss.org/browse/JBIDE-13851 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta1 > > > This feature would be implemented in a similar way to adding PDE plugins to the Java Search. -- 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-14341: ----------------------------------------- This would be an excellent use-case to develop using JBoss Forge. Forge 2 now supports writing IDE Wizards (decoupled from Eclipse) using CDI which could be an excellent choice for this. Alternatively a plugin for JBoss Forge could be another option as well. > Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse > ----------------------------------------------------------------------- > > Key: JBIDE-14341 > URL: https://issues.jboss.org/browse/JBIDE-14341 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Joe Fernandes > Priority: Optional > > OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. > This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE. This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings. > Some key information on the new OpenShift v2 cartridge format: > -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June). All current cartridges are being migrated to the new v2 cartridge format. > -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them. That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL. That is really the core feature of being able to start a cartridge ecosystem. > -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular. Main goal there was to try and simplify, cleanup and better document the process. H > -Here are some of the docs: > Technical docs: > https://github.com/openshift/origin-server/blob/master/node/README.writin... > https://github.com/openshift/origin-server/blob/master/node/README.node_m... > https://github.com/openshift/origin-server/blob/master/node/README.writin... > Getting Started: > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1 > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2 > If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-...) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know. -- 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

12 years, 11 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