January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16309: ------------------------------------ Careful, we don't want to end up with a property for jbosstools-site-base and another for the jbosstools-base project's site, eg., jbosstools-base-site. Because that could be confusing. :) > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16367) Drop sourceforge.net archiving?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16367?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16367: ------------------------------------ Sourceforge archving == poor man's Akamai. So until we have a better option, we should continue to host w/ SF. It only takes a few mins to open an SSH connection to SF, then another few mins to upload the zips & md5 files. And then we get around-the-globe mirroring instead of "everything served from one server". > Drop sourceforge.net archiving? > ------------------------------- > > Key: JBIDE-16367 > URL: https://issues.jboss.org/browse/JBIDE-16367 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Fix For: 4.2.x > > > We currently do archive stuff on sf.net. This adds an extra piece in build process and infrastructure, which does not seem to provide additional value upon keeping binaries on download.jboss.org. > I'd be in favour of abandoning sf.net to find something which is more comfortable for us to use (download.jboss.org is IMO the best candidate). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-447) Explain how to configure SSL options for connecting to Enterprise Servers.

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ] Mustafa Musaji commented on TOOLSDOC-447: ----------------------------------------- Correction, JBDS 7.x has openshift bits in the user guide. > 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 > 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 > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-447) Explain how to configure SSL options for connecting to Enterprise Servers.

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ] Mustafa Musaji commented on TOOLSDOC-447: ----------------------------------------- There are currently no live docs for JBDS 7.x for openshift. Any new docs should request more information in regards to improving readability and usage. [~edrich], if you can please give us screenshots/chapters that is missing from JBDS 6.x the docs team will have something to build on for future releases Thanks Mus > 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 > 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 > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16356) OpenShift project wizard does not handle a dirty/modified git project gracefully

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16356?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-16356: ------------------------------------- [~maxandersen]just do the git clone in step 1 above - if gives you all of Joshua's quickstarts, though I am only importing one of those, which does not have its own individual .git directory. > OpenShift project wizard does not handle a dirty/modified git project gracefully > -------------------------------------------------------------------------------- > > Key: JBIDE-16356 > URL: https://issues.jboss.org/browse/JBIDE-16356 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Burr Sutter > Attachments: contacts-mobile-basic.zip > > > I am getting an odd error message. > Here are the steps: > 1) git clone https://github.com/joshuawilson/jboss-wfk-quickstarts.git > 2) git checkout WFK-113 > 3) JBDS 7.1 import as Maven project > 4) tweak the pom.xml (it was broken but now fixed) > 5) it deploys to a local EAP, now attempt to send to OpenShift > 6) run the OpenShift wizard as seen in the video > http://screencast.com/t/NVTPK4pL -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2851) Team Usability

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2851: ----------------------------------- [~mmurray]CVS is part of core Eclipse, we have eGit "out of the box" (needed it for Openshift interaction), Subclipse is available on Software/Update Tab of JBoss Central. > Team Usability > -------------- > > Key: JBDS-2851 > URL: https://issues.jboss.org/browse/JBDS-2851 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Burr Sutter > > It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as > - how to integrate with CVS, SVN, Git > - how to "import" a Maven-based project from SCM > "Check out Maven Projects from SCM" has misfired for some users > - how to "checkin" changes back to the SCM > To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things. > For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2852) Database/source/connection Usability

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2852: ----------------------------------- [~mmurray]One of our challenges is...I am not sure if we even know how it is supposed to work in its current form. I have found the best way to achieve better usability is to first document the N step "ugly" process/workflow that is experienced by the end-user, then tweak, normally with just a few hours of effort you can get from N steps to N / 2 pretty easily - half the steps normally makes things a little more usable. :-) In this particular case, here is an example of a possible user story: a) As a Java EE JAX-RS+JPA developer, I need to be able to: 1) connect to my Oracle, MySQL, MS SQL Server, DB/2 or Postgres databases (local machine or remotely across the network, in openshift) with my provided credentials 2) view its schema/tables/fields 3) view the relationships amongst the tables/views 4) run some sql queries (insert, update, delete, select) 5) generate initial JPA entity classes (via Forge) 6) generate a persistence.xml, being able to tweak it 7) generate a datasource.xml, being able to tweak it 9) generate initial JAX-RS endpoints 10) run an interactive test of a JAX-RS endpoint (CRUD ops) 11) go back to the database to see if the CRUD op has occurred in the database itself 12) add bean validations to my entities.... > Database/source/connection Usability > ------------------------------------ > > Key: JBDS-2852 > URL: https://issues.jboss.org/browse/JBDS-2852 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: integration, requirements > Reporter: Burr Sutter > > Connecting to a database from within JBDS/Eclipse is a multi-step, multi-screen, potentially error-prone challenge. > Forge is involved as it can generate entities from schema > Datasources are needed in/on AS/Wildfly/EAP in order for the project deploy > Persistence.xml may needed to be tweaked for the datasource > End-user would like to navigate the schema in the DTP/Hibernate Tools, interactively review the data and there was once a feature for viewing an ORM diagram that I seem to have forgotten how it is displayed. > What happens when a project that needs a database connection is imported into the IDE? > This was partially addressed with > https://issues.jboss.org/browse/JBIDE-15263 > Let's see if we can continue to improve the workflow by reducing steps, making it more obvious what steps are required (e.g. hey developer, get the mysql driver .jar), auto generating the -ds.xml, with a decent explanation for the end-user to follow. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15969) Investigate removing some m2e extensions for TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15969?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-15969. ------------------------------------ Resolution: Done Re-added m2e.apt dependency that is shipped in JBT and JBDS. > Investigate removing some m2e extensions for TP > ----------------------------------------------- > > Key: JBIDE-15969 > URL: https://issues.jboss.org/browse/JBIDE-15969 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.1.1.CR1, 4.2.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Alpha2 > > > It looks like m2e-wro4j is not used at all in JBoss Tools (only referenced in Central). > It also appears that other m2e extensions (maven.apt and m2e.jdt) are not necessary to build JBT, and are only made available by default in JBDS installer and on Central. > So I suggest the following changes: > * Remove the 3 maven extensions (m2e.wro4j, maven.apt, m2e.jdt) from the JBT target-platform, and keep them only in Central > * Remove m2e.wro4j from JBDS TP (as it's not part of installer) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16368) Clean useless features from TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16368?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-16368: ----------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.Alpha1) > Clean useless features from TP > ------------------------------ > > Key: JBIDE-16368 > URL: https://issues.jboss.org/browse/JBIDE-16368 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.2.x > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.x > > > In order to trim some stuff out of our target-platform, we should: > * Install JBDS from installer > * Look at its content in plugins/ and features/ and compare it with content of the TP site. > Everything that is in TP site but not in JBDS is probably worth being removed from TP. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Fixing SWT issues in Luna

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16290: ------------------------------------ PR 199 was applied a week ago, so I've set this from 4.2.x fixversion to 4.2.0.Alpha2. Is this issue resolved? > Fixing SWT issues in Luna > ------------------------- > > Key: JBIDE-16290 > URL: https://issues.jboss.org/browse/JBIDE-16290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Snjezana Peco > Fix For: 4.2.0.Alpha2 > > Attachments: Java - Eclipse _001.png, luna-crashing-on-outcomplete.ogv > > > This ticket is meant to list the bugs related to GTK3 affecting JBDS: > * JBIDE-16280 VPE/XulRunner crashes workbench > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 > * Central tests uses SWT_GTK3=0 in its pom. > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=425123 > We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. > On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. -- 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, 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 January 2014