March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2284) Investigate use of Findbugs 2.0.2 (was 2.0.1) in JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2284?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2284: ----------------------------- Release Notes Text: Cause: FindBugs 2.0.1 site was old, and hard to mirror Consequence: we had to manually hack up an update site, which was hard to maintain Fix: move up to FindBugs 2.0.2 and improve mirroring to suppress 3rd party references in the site metadata Result: JBT4.0.1/JBDS6.0.1 now includes FindBugs 2.0.2 within Central. was: Cause: Consequence: Fix: Result: > Investigate use of Findbugs 2.0.2 (was 2.0.1) in JBoss Central > --------------------------------------------------------------- > > Key: JBDS-2284 > URL: https://issues.jboss.org/browse/JBDS-2284 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 6.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 6.0.1.GA > > > Bits mirrored here: > http://download.jboss.org/jbosstools/updates/requirements/findbugs/2.0.1.... -- 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-2438) include EAP 6.0.1 in JBDS 6.0.1 installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2438?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2438: ----------------------------- Release Notes Text: Cause: EAP 6.0.0 is old Consequence: EAP 6.0.0 should be replaced by EAP 6.0.1 Fix: replace EAP 6.0.0 with 6.0.1 Result: installer has been updated to include EAP 6.0.1 instead of 6.0.0 (Really? Do RN need to be this verbose?) was: Cause: Consequence: Fix: Result: > include EAP 6.0.1 in JBDS 6.0.1 installer > ----------------------------------------- > > Key: JBDS-2438 > URL: https://issues.jboss.org/browse/JBDS-2438 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 6.0.1.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 6.0.1.GA > > Attachments: JBDS2438.patch.txt, JBDS2438.patch2.txt > > > EAP 6.0.1 is out. Time to update the installer to include the latest n' greatest EAP 6. -- 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-11495) Improve ability to configure dependent hudson jobs and provide accessable documentation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11495?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11495: --------------------------------------------- maybe im reading this wrong but how does this *not* apply to core too ? > Improve ability to configure dependent hudson jobs and provide accessable documentation > --------------------------------------------------------------------------------------- > > Key: JBIDE-11495 > URL: https://issues.jboss.org/browse/JBIDE-11495 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Barry LaFond > Assignee: Douglas Palmer > Fix For: 4.0.x > > > SOA decoupling has elevated the need to have more configurable control over upstream and downstream dependencies. > Notes from Nick: > * a number of jobs are now set to build only when triggered by upstream, but SOA stuff is not as well handled > * ideally you'd want: a) check svn every N hours (usually 6) and b) upstream should use Parameterized Trigger to cause downstream to fire > * you can also ensure that you're building against a stable aggregate using an override like the one I've set up for SOA Tooling aggregate... > * in your maven invocation, under Properties, you can do this: # use latest upstream nightly Core update site instead of "wild components" in the composite staging site jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools... > * that way you pull from the aggregate (updates weekly) instead of the composite (updates every time a component respins) > * means if you depended on something like tests/common/jst/vpe/jsf/seam/maven/central/usage stack, you wouldn't need to worry about getting incompatible pieces -- 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-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13408: ------------------------------------ https://github.com/jbosstools/jbosstools-target-platforms/wiki reviewed. Added missing steps to release process, fixed typos, and corrected numbering. Looks good. Did no read the rest of the doc, just the before/after release process. Diff: https://github.com/jbosstools/jbosstools-target-platforms/wiki/_compare/b... > investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus > ----------------------------------------------------------------------------------- > > Key: JBIDE-13408 > URL: https://issues.jboss.org/browse/JBIDE-13408 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots. > Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error: > {quote} > {code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos.... Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1] > {code} > {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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13408 at 3/7/13 1:59 PM: ------------------------------------------------------------ https://github.com/jbosstools/jbosstools-target-platforms/wiki reviewed. Added missing steps to release process, fixed typos, and corrected numbering. Looks good. Did not read the rest of the doc, just the before/after release process. Diff: https://github.com/jbosstools/jbosstools-target-platforms/wiki/_compare/b... was (Author: nickboldt): https://github.com/jbosstools/jbosstools-target-platforms/wiki reviewed. Added missing steps to release process, fixed typos, and corrected numbering. Looks good. Did no read the rest of the doc, just the before/after release process. Diff: https://github.com/jbosstools/jbosstools-target-platforms/wiki/_compare/b... > investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus > ----------------------------------------------------------------------------------- > > Key: JBIDE-13408 > URL: https://issues.jboss.org/browse/JBIDE-13408 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots. > Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error: > {quote} > {code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos.... Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1] > {code} > {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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13703) Team - Verify the workflow

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13703?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13703: --------------------------------------------- Yes, this is similar to what I suggested for 'our own "import existing project"'. Eclipse don't have such project factory API currently. > Team - Verify the workflow > -------------------------- > > Key: JBIDE-13703 > URL: https://issues.jboss.org/browse/JBIDE-13703 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Burr Sutter > Assignee: Burr Sutter > Attachments: JBDS-usability.pdf, Netbeans-Open-project.PNG > > > The average end-user would like to: > 1) check out (clone) a project from CVS, SVN or Git > -- add repo, navigate repo, check out a project > -- project may or may not have .classpath, .project or .settings files > -- project may be Maven-based > and see if the following work > 2) Are the appropriate facets enabled? > 3) Does it build immediately? > 4) Can I immediately hit the run button to launch it on my app server? > 5) Can I immediately hit the debug button to debug it on my app server? > -- how do I step if there are no break points? > 6) Make a change to a file, re-run/debug again > 7) Run JUnit tests > 8) Check the change back into the repo with comments -- 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-11495) Improve ability to configure dependent hudson jobs and provide accessable documentation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11495?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-11495: ------------------------------------ +1 to move this to JBTIS and let Paul have a look at it. Paul owns JBTIS, JBTIS owns Teiid, Barry opened this issue. Therefore... JBTIS. > Improve ability to configure dependent hudson jobs and provide accessable documentation > --------------------------------------------------------------------------------------- > > Key: JBIDE-11495 > URL: https://issues.jboss.org/browse/JBIDE-11495 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Barry LaFond > Assignee: Douglas Palmer > Fix For: 4.0.x > > > SOA decoupling has elevated the need to have more configurable control over upstream and downstream dependencies. > Notes from Nick: > * a number of jobs are now set to build only when triggered by upstream, but SOA stuff is not as well handled > * ideally you'd want: a) check svn every N hours (usually 6) and b) upstream should use Parameterized Trigger to cause downstream to fire > * you can also ensure that you're building against a stable aggregate using an override like the one I've set up for SOA Tooling aggregate... > * in your maven invocation, under Properties, you can do this: # use latest upstream nightly Core update site instead of "wild components" in the composite staging site jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools... > * that way you pull from the aggregate (updates weekly) instead of the composite (updates every time a component respins) > * means if you depended on something like tests/common/jst/vpe/jsf/seam/maven/central/usage stack, you wouldn't need to worry about getting incompatible pieces -- 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-13577) refactor & clean up jbosstools-target-platforms repo

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13577?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13577. ------------------------------ Resolution: Done Explain to me how having a "publish" branch would be the same as all the other projects which do not have a "publish" branch? Or how having a .x branch for JBT 3.2.x, 3.3.x, 4.0.x, and soon 4.1.x is so different from having TPs with branches called 4.20.x, 4.21.x, 4.22.x, and 4.30.x? .x branches in projects. .x branches in target platform project. Seems pretty similar. :D ---- As to moving a single shell script which is ONLY useful in the context of target platforms to the build-ci repo where I'll have to rename it so it doesn't collide name-wise with the OTHER publish.sh script (used by all the projects, so it makes sense as a shared/common script), and making me update Jenkins jobs to pull from a different raw.github URL... yes, that sounds logical. Please open a new jira for that bit of arbitrary make-work. > refactor & clean up jbosstools-target-platforms repo > ---------------------------------------------------- > > Key: JBIDE-13577 > URL: https://issues.jboss.org/browse/JBIDE-13577 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.0.0.Final, 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2, 4.0.0.Final > > > Rename branches as follows: > 4.2.0 -> 4.20.x (currently contains 4.20.6) > 4.2.1 -> 4.21.x (currently contains 4.21.4) > (new) -> 4.22.x (soon will contain 4.22.0) > 4.3.0 -> master (currently contains 4.30.3) > Also, purge any large binaries that are causing the repo to be >50M in size. > When Kepler R is released (Eclipse 4.3.0.Final) we can branch a 4.30.x branch and work on the new 4.31.x target platforms (Kepler SR1) in the master branch. -- 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-13749) "Abridged Jboss Tools" category has 4.0 version in label

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13749?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13749: ------------------------------------ Forgot to update the site descriptions too: {code} - <description>JBoss Tools 4.0 - Core Tests</description> + <description>JBoss Tools 4.1 (Kepler) - Core Tests</description> - <description>JBoss Tools 4.0 (Juno) Updates - Core</description> + <description>JBoss Tools 4.1 (Kepler) Updates - Core</description> {code} Committed and pushed. > "Abridged Jboss Tools" category has 4.0 version in label > -------------------------------------------------------- > > Key: JBIDE-13749 > URL: https://issues.jboss.org/browse/JBIDE-13749 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Radim Hopp > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > Attachments: installDialog.png > > > AbridgedTools category still has label "Abridged JBoss Tools 4.0" (version should be 4.1) > !installDialog.png! -- 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-13749) "Abridged Jboss Tools" category has 4.0 version in label

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13749?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13749 at 3/7/13 1:32 PM: ------------------------------------------------------------ Forgot to update the site descriptions too: {code:title=coretests-site/site.xml and site/site.xml} - <description>JBoss Tools 4.0 - Core Tests</description> + <description>JBoss Tools 4.1 (Kepler) - Core Tests</description> - <description>JBoss Tools 4.0 (Juno) Updates - Core</description> + <description>JBoss Tools 4.1 (Kepler) Updates - Core</description> {code} Committed and pushed. was (Author: nickboldt): Forgot to update the site descriptions too: {code} - <description>JBoss Tools 4.0 - Core Tests</description> + <description>JBoss Tools 4.1 (Kepler) - Core Tests</description> - <description>JBoss Tools 4.0 (Juno) Updates - Core</description> + <description>JBoss Tools 4.1 (Kepler) Updates - Core</description> {code} Committed and pushed. > "Abridged Jboss Tools" category has 4.0 version in label > -------------------------------------------------------- > > Key: JBIDE-13749 > URL: https://issues.jboss.org/browse/JBIDE-13749 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Radim Hopp > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > Attachments: installDialog.png > > > AbridgedTools category still has label "Abridged JBoss Tools 4.0" (version should be 4.1) > !installDialog.png! -- 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