[JBoss JIRA] (JBIDE-16371) Application wizard: provide toggles for markers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16371?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16371:
-------------------------------------
Description:
Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845
We should offer these markers as toggles in the Application wizard on the project configuration page:
!progject-page.png!
In a mail with Max and Burr:
{quote}
for EAP/wildfly/tomcat enable_jpda, disable build and maybe the java7 toggle etc. would be interesting and for other app types other markers could make sense?
{quote}
was:
Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845
We should offer these markers as toggles in the Application wizard on the project configuration page:
!progject-page.png!
> Application wizard: provide toggles for markers
> -----------------------------------------------
>
> Key: JBIDE-16371
> URL: https://issues.jboss.org/browse/JBIDE-16371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.2.x
>
> Attachments: project-page.png
>
>
> Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845
> We should offer these markers as toggles in the Application wizard on the project configuration page:
> !progject-page.png!
> In a mail with Max and Burr:
> {quote}
> for EAP/wildfly/tomcat enable_jpda, disable build and maybe the java7 toggle etc. would be interesting and for other app types other markers could make sense?
> {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
12 years, 2 months
[JBoss JIRA] (JBIDE-16371) Application wizard: provide toggles for markers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16371?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16371:
-------------------------------------
Description:
Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845
We should offer these markers as toggles in the Application wizard on the project configuration page:
!progject-page.png!
In a mail with Max and Burr:
{quote}
for EAP/wildfly/tomcat enable_jpda, disable build and maybe the java7 toggle etc. would be interesting and for other app types other markers could make sense?
{quote}
When implementing this we should consider that most markers, which are not sourcecode related, are by now considered as deprected in OpenShift.
was:
Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845
We should offer these markers as toggles in the Application wizard on the project configuration page:
!progject-page.png!
In a mail with Max and Burr:
{quote}
for EAP/wildfly/tomcat enable_jpda, disable build and maybe the java7 toggle etc. would be interesting and for other app types other markers could make sense?
{quote}
> Application wizard: provide toggles for markers
> -----------------------------------------------
>
> Key: JBIDE-16371
> URL: https://issues.jboss.org/browse/JBIDE-16371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Labels: application_wizard
> Fix For: 4.2.x
>
> Attachments: project-page.png
>
>
> Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845
> We should offer these markers as toggles in the Application wizard on the project configuration page:
> !progject-page.png!
> In a mail with Max and Burr:
> {quote}
> for EAP/wildfly/tomcat enable_jpda, disable build and maybe the java7 toggle etc. would be interesting and for other app types other markers could make sense?
> {quote}
> When implementing this we should consider that most markers, which are not sourcecode related, are by now considered as deprected in OpenShift.
--
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, 2 months
[JBoss JIRA] (JBIDE-16351) FixClasspathConfigurator isn't obliged in a newer m2e
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16351?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16351:
---------------------------------------------
Can this explain why wildfly is so slow to build ?
What jira introduced this configurator ? I assume it was requested in context of WFK Seam 2 maven projects which still are part of wfk so just wondering if it is still relevant for them ?
Should also consider removing this in maintanence branch if no use for it.
> FixClasspathConfigurator isn't obliged in a newer m2e
> -----------------------------------------------------
>
> Key: JBIDE-16351
> URL: https://issues.jboss.org/browse/JBIDE-16351
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Fred Bricon
> Fix For: 4.2.0.Alpha2
>
>
> The FixClasspathConfigurator configurator has been introduced to solve https://issues.sonatype.org/browse/MNGECLIPSE-2433.
> The issue happens with a mavenized seam 2 project that has a flat layout structure.
> This configurator refreshes the old maven facade causing m2e to solve dependencies twice when ever building a project.
> It is the configurator for maven-compiler-plugin so it is called for every Java project.
> Since solving dependencies can take a long, it can slow down building projects up to 15% (depends on the project's dependencies)
> The solution:
> - removing the configurator. The issue is only related to the mavenized Seam projects that aren't included into project examples anymore and a required classpath entry can be manually added(newer m2 versions won't remove the existing classpath entry).
--
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, 2 months
[JBoss JIRA] (JBIDE-16371) Application wizard: provide toggles for markers
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-16371:
----------------------------------------
Summary: Application wizard: provide toggles for markers
Key: JBIDE-16371
URL: https://issues.jboss.org/browse/JBIDE-16371
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.1.1.Final
Reporter: Andre Dietisheim
Fix For: 4.2.x
Markers in OpenShift allow users to enable/disable functionalities: see JBIDE-14845
We should offer these markers as toggles in the Application wizard
--
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, 2 months
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16309:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70, https://github.com/jbosstools/jbosstools-openshift/pull/344, https://github.com/jbosstools/jbosstools-portlet/pull/25, https://github.com/jbosstools/jbosstools-server/pull/186, https://github.com/jbosstools/jbosstools-webservices/pull/106 (was: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70, https://github.com/jbosstools/jbosstools-openshift/pull/344, https://github.com/jbosstools/jbosstools-portlet/pull/25, https://github.com/jbosstools/jbosstools-server/pull/186)
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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, 2 months
[JBoss JIRA] (JBIDE-14850) Markers wizard: Restrict available markers depending on application type
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14850?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14850:
------------------------------------------
In the last sync discussion with the OpenShift team we were told that not all but the majority of markers will get deprecated. The rule of thumb is that markers will only get used for source related switches. All non sourcecode related switches will get replaced by env variables.
> Markers wizard: Restrict available markers depending on application type
> ------------------------------------------------------------------------
>
> Key: JBIDE-14850
> URL: https://issues.jboss.org/browse/JBIDE-14850
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Labels: markers_wizard
> Fix For: 4.2.x
>
>
> In JBIDE-14845 we allow users to add and remove markers. We dont filter the markers whether we have a java (jbossas, jbossews) or php, node, ruby etc. application even though some markers are specific to certain application types. We should tell the user what markers may make sense and suggest upon that.
--
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, 2 months
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16309:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70, https://github.com/jbosstools/jbosstools-openshift/pull/344, https://github.com/jbosstools/jbosstools-portlet/pull/25, https://github.com/jbosstools/jbosstools-server/pull/186 (was: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70, https://github.com/jbosstools/jbosstools-openshift/pull/344, https://github.com/jbosstools/jbosstools-portlet/pull/25)
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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, 2 months
[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16309:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70, https://github.com/jbosstools/jbosstools-openshift/pull/344, https://github.com/jbosstools/jbosstools-portlet/pull/25 (was: https://github.com/jbosstools/jbosstools-build/pull/131, https://github.com/jbosstools/jbosstools-javaee/pull/186, https://github.com/jbosstools/jbosstools-jst/pull/248, https://github.com/jbosstools/jbosstools-arquillian/pull/50, https://github.com/jbosstools/jbosstools-central/pull/201, https://github.com/jbosstools/jbosstools-hibernate/pull/35, https://github.com/jbosstools/jbosstools-livereload/pull/70, https://github.com/jbosstools/jbosstools-openshift/pull/344)
> Move inter-JBT dependencies to component poms
> ---------------------------------------------
>
> Key: JBIDE-16309
> URL: https://issues.jboss.org/browse/JBIDE-16309
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build.
> The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous.
> So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309
> You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver
> https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
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, 2 months
[JBoss JIRA] (TOOLSDOC-447) Explain how to configure SSL options for connecting to Enterprise Servers.
by Eric Rich (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ]
Eric Rich commented on TOOLSDOC-447:
------------------------------------
Chapter 9. OpenShift Tools in the User Guide is where I think these examples should go.
This request comes out of there being a lack of information on how to setup the connection to different servers, IE Enterprise and Online or multiple Enterprise Servers. The documentation should also include similar details as the ones provided in 2.3. Configuring Client Tools of the Client Tools Installation Guide for OpenShift.
The case attached to this doc bug in particular seems to need information on configuring the SSL certificate to talk to a service (OpenShift Enterprise), its important to note that rhc the client tool for Openshift in its setup and configuration provides the following prompt:
Connect without checking the certificate? (yes|no):
Does JDBS have a similar option and if so how is it configured for this plugin?
> Explain how to configure SSL options for connecting to Enterprise Servers.
> --------------------------------------------------------------------------
>
> Key: TOOLSDOC-447
> URL: https://issues.jboss.org/browse/TOOLSDOC-447
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide - OpenShift Tools
> Affects Versions: 4.1.1
> Environment: Build Name: 22443, User Guide-7.1
> Build Date: 11-12-2013 15:10:49
> Topic ID: 25166-566980 [Latest]
> Reporter: Eric Rich
> Assignee: Michelle Murray
> Priority: Minor
> Fix For: 4.2.0
>
>
> Title: Customizing Overview
> Describe the issue:
> It would be good to explain configuration options for connecting to multiple or different Enterprise Servers.
> Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful.
> Suggestions for improvement:
> Additional information:
--
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, 2 months