May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9726) inconsistent licensing terms across JBoss Tools - SOA Tooling site

by Nick Boldt (JIRA)

inconsistent licensing terms across JBoss Tools - SOA Tooling site ------------------------------------------------------------------ Key: JBIDE-9726 URL: https://issues.jboss.org/browse/JBIDE-9726 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools, pi4soa, Savara, teiid, updatesite Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Kris Verlaenen Fix For: 3.3.0.M4 Attachments: inconsistent-license-details.png Most features in JBoss Tools have a license from Red Hat which mentions EPL, GPL, and other licenses. It's a catch-all which allows a cleaner view of what's being installed. !inconsistent-license-details.png! The following features should adopt this statement in their features so that we're consistent across the board: Savara (GPL) Drools (ASL) pi4soa (ASL) Teiid (EPL) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

9
15
0 / 0

[JBoss JIRA] Created: (JBIDE-9727) Drools license terms could be consistent w/ rest of JBoss Tools - SOA Tooling site

by Nick Boldt (JIRA)

Drools license terms could be consistent w/ rest of JBoss Tools - SOA Tooling site ---------------------------------------------------------------------------------- Key: JBIDE-9727 URL: https://issues.jboss.org/browse/JBIDE-9727 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: drools Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Kris Verlaenen Fix For: 3.3.0.M4 Most features in JBoss Tools have a license from Red Hat which mentions EPL, GPL, and other licenses. It's a catch-all which allows a cleaner view of what's being installed. See parent task for details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

6
10
0 / 0

[JBoss JIRA] (JBIDE-11523) jbossas link in examples is broken

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-11523: ---------------------------------------- Summary: jbossas link in examples is broken Key: JBIDE-11523 URL: https://issues.jboss.org/browse/JBIDE-11523 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.3.0.Beta2 Reporter: Rastislav Wagner Assignee: Snjezana Peco Fix For: 3.3.0.Beta3 Java EE Web Project, Java EE Project and GWT Web Project points to jboss.org/jbossas which makes browser to look for localhost:8080/appName/jboss.org/jbossas We need to change url to http://jboss.org/jbossas -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
9
0 / 0

[JBoss JIRA] (JBIDE-11969) configure maven repo adds jbosstools-maven-repository profile

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11969: ------------------------------------------- Summary: configure maven repo adds jbosstools-maven-repository profile Key: JBIDE-11969 URL: https://issues.jboss.org/browse/JBIDE-11969 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Reporter: Max Rydahl Andersen Assignee: Fred Bricon Priority: Critical Fix For: 3.3.0.CR1 trying out changes after JBIDE-11818 now without changing anything configure maven repositories is trying to add: <profile> <id>jbosstools-maven-profile</id> <activation> <activeByDefault>true</activeByDefault> </activation> <repositories/> <pluginRepositories/> </profile> 1) we shouldn't have a "jbosstools" profile - this is for use both in and outside of eclipse. 2) why aren't we just adding the profile(s) under activeProfile instead of using activebydefault ? and use the name (without spaces) of the repo as the profile id ? i.e. jboss-eap-repository, jboss-wfk-repository etc. ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
4
0 / 0

[JBoss JIRA] (JBIDE-11953) UI challenges with "Configure maven repositories"

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11953: ------------------------------------------- Summary: UI challenges with "Configure maven repositories" Key: JBIDE-11953 URL: https://issues.jboss.org/browse/JBIDE-11953 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Reporter: Max Rydahl Andersen Assignee: Fred Bricon Priority: Blocker Fix For: 3.3.0.CR1 Finally got to try out the "configure maven repositories" quickfixing for missing -redhat and .org dependencies. Some of this feels and works very "backwards" to me and not sure how to fix it yet so im going to list out the issues I found and we can split it up/add as subtasks afterwards. A) Both the "Configure Maven repositories" AND the "See how to setup XYZ repositories in your settings.xml". I think Very few would select the "Configure maven repositories" option over the more explanatory "See how to setup.." quickfix. Why do we need both ? Why move the link to the "configure maven repositories" and just let ocnfigure maven repositories know what kind of dependency we are looking for and adjust its UI based on it ? B) When using Configure Maven Repositiories not a single message or confirmation dialog is telling or asking that this is going to change settings.xml - that *must* be fixed. C) When doing the quickfix on a -redhat missing repository why do I as a user have to know I should ignore the long list of public repositories in here, incl. jboss.org which in case of -redhat we do not want to encourage users to use unless they really know what they are doing ? D) Recognize JBoss Maven Enterprise Repositories... (RJBMER) - If I point it to something that is not a repository it just ignores it and says nothing. Not even info on what it is actually looking for - I would expect it to say "Could not recognize this repository on disk since I could not find <xyz>. Do you still want to add this as Maven repository ?" E) RJBMER - if I add multiple EAP repositories they get added with the same name and thus you don't know which is which. F) when pressing finish no confirmation/no delta/no warning given when actually overwriting one of the possibly most important setting files on a developers machine. G) in the generated settings.xml existing <id>'s seem to be put at the end instaed of at the beginning - aren't ordering hornored in the serialization ? H) all comments are gone. I) it does not seem to activate/deactive the profiles - at least not listed in <activeProfiles>; so how are these fixes actually going to help ? J) naming seem to be based on some hardcoded constants with no option for users to influence them instead of just getting "jboss-eap-maven-repository.0" K) and couldn't the dialog actually tell me the repository i'm adding actually have the artifact I'm quickfixing for ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-11818) Repository Configurator Wizard deletes existing comments when updating the user settings.xml

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-11818: ----------------------------------- Summary: Repository Configurator Wizard deletes existing comments when updating the user settings.xml Key: JBIDE-11818 URL: https://issues.jboss.org/browse/JBIDE-11818 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.CR1 Reporter: Fred Bricon Assignee: Snjezana Peco Priority: Critical Fix For: 3.3.0.CR1 After adding a maven repo via the Repository Configurator wizard, my settings.xml is cleansed of all comments, as the updated maven Settings model is serialized directly to file, overwriting the existing settings.xml. I lost some important stuff that was commented in that file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-11905) ConfigureRepositoriesWizard was incorrectly adding the repository element to the pluginRepositories element

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-11905: ------------------------------------- Summary: ConfigureRepositoriesWizard was incorrectly adding the repository element to the pluginRepositories element Key: JBIDE-11905 URL: https://issues.jboss.org/browse/JBIDE-11905 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.Beta3 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11606) Mavenize JBoss Tools releases

by Tomas Vala (JIRA)

Tomas Vala created JBIDE-11606: ---------------------------------- Summary: Mavenize JBoss Tools releases Key: JBIDE-11606 URL: https://issues.jboss.org/browse/JBIDE-11606 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Tomas Vala Priority: Minor Hello, please consider making JBoss Tools releases available through maven repository. For reference: Eclipse is aiming to officialy provide maven feed for BIRT Runtime (Business Intelligence and Reporting Tools) from Juno release on (2012/6). It would be nice and practical if at least portion of JBoss Tools, JBoss BIRT Integration ODA plugin would follow this trend. {noformat} Personal opinion based on recent experience: I consider current distribution channels and methods to be somewhat lacking compared to nowadays possibilities. Weird artificial dependencies of JBoss BIRT Integration Eclipse feature, direct download links for individual jars are rather difficult to find on the web site. {noformat} Tomas -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11793) Repository Configurator Wizard should ignore local maven repository during search

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-11793: ----------------------------------- Summary: Repository Configurator Wizard should ignore local maven repository during search Key: JBIDE-11793 URL: https://issues.jboss.org/browse/JBIDE-11793 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.CR1 Reporter: Fred Bricon Assignee: Snjezana Peco Priority: Minor Fix For: 3.3.0.CR1 I have a repository c:/Dev/maven containing all my maven repos, including the default local maven repository. If I start searching from c:/Dev/maven, then c:/Dev/maven/local will be identified as a JBoss WFK Maven Repository and added as a remote repository. It should be ignored completely. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
3
0 / 0

[JBoss JIRA] (JBDS-2133) Creating a new Maven project adds a JSE-1.5 environment - regardless of the default installed JRE

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2133: ---------------------------------- Summary: Creating a new Maven project adds a JSE-1.5 environment - regardless of the default installed JRE Key: JBDS-2133 URL: https://issues.jboss.org/browse/JBDS-2133 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: maven Affects Versions: 5.0.0.Beta3 Environment: Version: 5.0.0.Beta3 Build id: v20120430-1703-H125-Beta3 Build date: 20120430-1703 java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.6) (rhel-1.43.1.10.6.el6_2-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) Reporter: Len DiMaggio Assignee: Snjezana Peco Fix For: 5.0.0.CR1 Attachments: JBDS-2133.png If a new Maven project is created - the project's build path always references a 1.5 JSE environment - regardless of the installed/configured JREs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
3
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 May 2012