March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2881) Make clear the distinction between update.zip and central.zip on access.redhat

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2881?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2881: ---------------------------------- [~mmurray] [~maxandersen] [~burrsutter] I've set the fixvversion on this to JBDS 7.1.1 so we don't forget this. > Make clear the distinction between update.zip and central.zip on access.redhat > ------------------------------------------------------------------------------ > > Key: JBDS-2881 > URL: https://issues.jboss.org/browse/JBDS-2881 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: build, updatesite > Affects Versions: 7.1.0.GA > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 7.1.1.GA > > > [1] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > [2] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > On the download pages for individual JBDS zips, we need to make clear the distinction between update.zip and central.zip. > update.zip and central.zip Detailed Description both read: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation." > Can the text [1] for update.zip be modified to: "It can be used to install JBoss Developer Studio features into your existing Eclipse 4.3 installation if working offline." > Can the text [2] for central.zip be modified to read something like: "It can be used to install additional JBoss Developer Studio and third-party features available from JBoss Central into JBoss Developer Studio if working offline." -- 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-16665) Add Sapphire to TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16665?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16665: ------------------------------- Assignee: Len DiMaggio > Add Sapphire to TP > ------------------ > > Key: JBIDE-16665 > URL: https://issues.jboss.org/browse/JBIDE-16665 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, testing-tools > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Len DiMaggio > > Reason: Required by new feature described in JBIDE-15394 > License and owner: EPL, Eclipse > Original repository: http://download.eclipse.org/sapphire/0.7/repository > JBoss Mirrored repository: http://downloads.jboss.org/jbosstools/updates/requirements/sapphire > Source: Yes > Affected projects: arquillian > Required in devstudio: No > Type of dependency: > List of bundles added: > org.eclipse.sapphire.java > org.eclipse.sapphire.java.jdt > org.eclipse.sapphire.java.jdt.ui > org.eclipse.sapphire.modeling > org.eclipse.sapphire.modeling.xml > org.eclipse.sapphire.osgi > org.eclipse.sapphire.osgi.fragment > org.eclipse.sapphire.platform > org.eclipse.sapphire.ui > org.eclipse.sapphire.ui.swt.gef > org.eclipse.sapphire.ui.swt.xml.editor > org.eclipse.sapphire.workspace > org.eclipse.sapphire.workspace.ui > org.objectweb.asm -- 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-16665) Add Sapphire to TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16665?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16665: ------------------------------------ This needs a +1 from QE before we do anything, so assigning to [~ldimaggio] for now. > Add Sapphire to TP > ------------------ > > Key: JBIDE-16665 > URL: https://issues.jboss.org/browse/JBIDE-16665 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, testing-tools > Affects Versions: 4.2.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Len DiMaggio > > Reason: Required by new feature described in JBIDE-15394 > License and owner: EPL, Eclipse > Original repository: http://download.eclipse.org/sapphire/0.7/repository > JBoss Mirrored repository: http://downloads.jboss.org/jbosstools/updates/requirements/sapphire > Source: Yes > Affected projects: arquillian > Required in devstudio: No > Type of dependency: > List of bundles added: > org.eclipse.sapphire.java > org.eclipse.sapphire.java.jdt > org.eclipse.sapphire.java.jdt.ui > org.eclipse.sapphire.modeling > org.eclipse.sapphire.modeling.xml > org.eclipse.sapphire.osgi > org.eclipse.sapphire.osgi.fragment > org.eclipse.sapphire.platform > org.eclipse.sapphire.ui > org.eclipse.sapphire.ui.swt.gef > org.eclipse.sapphire.ui.swt.xml.editor > org.eclipse.sapphire.workspace > org.eclipse.sapphire.workspace.ui > org.objectweb.asm -- 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-16728) New project dialog should allow selection of Cordova plug-ins

by Gorkem Ercan (JIRA)

Gorkem Ercan created JBIDE-16728: ------------------------------------ Summary: New project dialog should allow selection of Cordova plug-ins Key: JBIDE-16728 URL: https://issues.jboss.org/browse/JBIDE-16728 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aerogear-hybrid Reporter: Gorkem Ercan Priority: Minor Fix For: 4.2.x When creating a new Hybrid mobile project it should be possible to select an initial set of Cordova plug-ins to be installed to the project. This would allow Cordova plugins such as Console to be added to the project by the developers form the beginning. -- 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-16727) Change in New Arquillian Deployment Method dialog

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-16727: ------------------------------------- Summary: Change in New Arquillian Deployment Method dialog Key: JBIDE-16727 URL: https://issues.jboss.org/browse/JBIDE-16727 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing-tools Affects Versions: 4.2.0.Alpha2 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 4.2.0.Beta1 We need to convert the Archive name validation error to a warning. -- 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-16726) Change Add Arqillian Support dialog

by Snjezana Peco (JIRA)

Snjezana Peco created JBIDE-16726: ------------------------------------- Summary: Change Add Arqillian Support dialog Key: JBIDE-16726 URL: https://issues.jboss.org/browse/JBIDE-16726 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing-tools Affects Versions: 4.2.0.Alpha2 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 4.2.0.Beta1 We should move the Arquillian version combo from the bottom to the top of the dialog. -- 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-16632) Aggregate source zip doesn't include sources

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16632?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16632: ------------------------------------ Now works locally but spinning in Jenkins to verify. Had some problems w/ NFS and relative file paths, but should be fixed now. I hope. Fixes: https://github.com/jbosstools/jbosstools-maven-plugins/commits/master Spins: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... >=8701 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_ma... >=?? (can't see Jenkins atm, so not sure which is the next good build) Artifacts: http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... > ALL_REVISIONS.txt http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... > ALL_REVISIONS.txt Added bonus: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_71... now includes GIT rev for JBDS (rather than being blank as not in SVN anymore) > Aggregate source zip doesn't include sources > -------------------------------------------- > > Key: JBIDE-16632 > URL: https://issues.jboss.org/browse/JBIDE-16632 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.2.0.Alpha2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.2.0.Beta1 > > > The latest JBT Source Zip doesn't include sources. It's probably a side effect of JBIDE-16376. -- 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-16632) Aggregate source zip doesn't include sources

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16632?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-16632: ---------------------------------- Assignee: Nick Boldt > Aggregate source zip doesn't include sources > -------------------------------------------- > > Key: JBIDE-16632 > URL: https://issues.jboss.org/browse/JBIDE-16632 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.2.0.Alpha2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.2.0.Beta1 > > > The latest JBT Source Zip doesn't include sources. It's probably a side effect of JBIDE-16376. -- 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-16725) clean up jbosstools-maven-plugins/tycho-plugins/*

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16725?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16725: ------------------------------- Description: A couple PRs/commits to clean stuff up, including: * deprecation warnings (Maven) * unused variables / imports (Eclipse) * copyright dates This one [1] was applied already, as it was a simple substitution: {code} [WARNING] org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo#session: [WARNING] The syntax [WARNING] @parameter expression="${property}" [WARNING] is deprecated, please use [WARNING] @parameter property="property" [WARNING] instead. {code} [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/eac10476e65... However, this one [2] was a bit more complicated as I switched from expression="" to default-value="" instead. Not sure if this is correct: [2] https://github.com/jbosstools/jbosstools-maven-plugins/pull/18 was: A couple PRs/commits to clean stuff up, including: * deprecation warnings (Maven) * unused variables / imports (Eclipse) * copyright dates This one [1] was applied already, as it was a simple substitution: {code} [WARNING] org.jboss.tools.tycho.targets.TargetToRepoMojo#outputRepository: [WARNING] The syntax [WARNING] @parameter expression="${property}" [WARNING] is deprecated, please use [WARNING] @parameter property="property" [WARNING] instead. {code} [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/eac10476e65... However, this one [2] was a bit more complicated as I switched from expression="" to default-value="" instead. Not sure if this is correct: [2] https://github.com/jbosstools/jbosstools-maven-plugins/pull/18 > clean up jbosstools-maven-plugins/tycho-plugins/* > ------------------------------------------------- > > Key: JBIDE-16725 > URL: https://issues.jboss.org/browse/JBIDE-16725 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Beta1 > > > A couple PRs/commits to clean stuff up, including: > * deprecation warnings (Maven) > * unused variables / imports (Eclipse) > * copyright dates > This one [1] was applied already, as it was a simple substitution: > {code} > [WARNING] org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo#session: > [WARNING] The syntax > [WARNING] @parameter expression="${property}" > [WARNING] is deprecated, please use > [WARNING] @parameter property="property" > [WARNING] instead. > {code} > [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/eac10476e65... > However, this one [2] was a bit more complicated as I switched from expression="" to default-value="" instead. Not sure if this is correct: > [2] https://github.com/jbosstools/jbosstools-maven-plugins/pull/18 -- 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-16725) clean up jbosstools-maven-plugins/tycho-plugins/*

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16725?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16725: ------------------------------- Fix Version/s: 4.2.0.Beta1 Priority: Minor (was: Major) Assignee: Mickael Istria Component/s: build > clean up jbosstools-maven-plugins/tycho-plugins/* > ------------------------------------------------- > > Key: JBIDE-16725 > URL: https://issues.jboss.org/browse/JBIDE-16725 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Beta1 > > > A couple PRs/commits to clean stuff up, including: > * deprecation warnings (Maven) > * unused variables / imports (Eclipse) > * copyright dates > Applied already, as it was a simple substitution: > {code} > [WARNING] org.jboss.tools.tycho.targets.TargetToRepoMojo#outputRepository: > [WARNING] The syntax > [WARNING] @parameter expression="${property}" > [WARNING] is deprecated, please use > [WARNING] @parameter property="property" > [WARNING] instead. > {code} > https://github.com/jbosstools/jbosstools-maven-plugins/commit/eac10476e65... > However, this one was a bit more complicated as I switched from expression="" to default-value="" instead. Not sure if this is correct: > https://github.com/jbosstools/jbosstools-maven-plugins/pull/18 -- 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 March 2014