[JBoss JIRA] (JBDS-2390) Do not rely on discovery.url system property, rely on a more standard extension system instead.
by Mickael Istria (JIRA)
Mickael Istria created JBDS-2390:
------------------------------------
Summary: Do not rely on discovery.url system property, rely on a more standard extension system instead.
Key: JBDS-2390
URL: https://issues.jboss.org/browse/JBDS-2390
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: central
Reporter: Mickael Istria
Assignee: Snjezana Peco
Fix For: 6.1.0.Alpha1
In JBDS, we override the discovery.url to set it to the value for JBDS extras site.
However, this is done by hacking system properties. Instead, we could think of using the "discoveryProviderUrl" extension point in JBT.
JBT would provide an extension to define this URL.
JBDS would provide another extension to define this URL.
Changing URL happens by updating the extension plugin.
So JBT and JBDS would behave the same way when dealing with discovery, and we remove the system properties settings from JBDS. System proprty would still be available for testing only.
--
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, 7 months
[JBoss JIRA] (JBDS-2257) Project archives loses "Library File Set" definition after closing and reopening JBDS
by Andrig Miller (JIRA)
Andrig Miller created JBDS-2257:
-----------------------------------
Summary: Project archives loses "Library File Set" definition after closing and reopening JBDS
Key: JBDS-2257
URL: https://issues.jboss.org/browse/JBDS-2257
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.0.0.GA
Environment: Fedora 17 x86_64
Reporter: Andrig Miller
Fix For: 5.0.1.GA
I recently created a new project to build a native management client to do some performance monitoring.
In that project I created to "User Libraries". One for Apache Commons CLI, for handling the CLI needs of the tool, and one for our own EAP libraries that make up the Native Management Client libraries.
I used the "Project Archives" feature to create the executable jar (also using the OneJar open source project so I could have dependent jars for runtime within the executable jar). In that executable jar, I have a lib folder, where I defined two "User Library Fileset"'s. This works fine, but after I close JDBS, and later go back and start it again to continue development work, that part of the "Project Archives" definition is always missing, and I have re-add it to the project.
--
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, 7 months
[JBoss JIRA] (JBIDE-13183) Seam Components 2.0 Editor: Wrong icon for node components.xml
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-13183:
-------------------------------------
Summary: Seam Components 2.0 Editor: Wrong icon for node components.xml
Key: JBIDE-13183
URL: https://issues.jboss.org/browse/JBIDE-13183
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 4.0.0.CR1
Environment: Ubuntu, jbdevstudio-product-eap-universal-6.0.0.CR1-v20121118-2035-B111.jar
Reporter: Daniel Azarov
Assignee: Alexey Kazakov
Attachments: SeamComponents.png
Now it is the same icon which is used for faces-config.xml, but should be icon from wizard "New Seam Components file"
See:
!SeamComponents.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, 7 months
[JBoss JIRA] (JBDS-2416) label Central connectors that are sourced from 3rd party sites (rather than our mirrors) as being External and provide detailed description/notice of ownership
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2416:
--------------------------------
Summary: label Central connectors that are sourced from 3rd party sites (rather than our mirrors) as being External and provide detailed description/notice of ownership
Key: JBDS-2416
URL: https://issues.jboss.org/browse/JBDS-2416
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: central
Affects Versions: 6.0.0.GA
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Fix For: 6.1.0.Alpha1
We currently use "Supported" to define JBoss-built/maintained content in Central, and "Tested" for 3rd party stuff we mirror and try to keep up to date.
However, for content that changes frequently (Android Tooling) or for which we do not have license to redistribute (JRebel), we need to link directly to a vendor's site and simply hope for the best.
But, to make it clear this is the case, we should in JBDS provide a note about this using a some term such as:
* External
* Other
* 3rdParty
and then provide a tooltip which reads:
{quote}This content, while compatible with JBoss Developer Studio at the time of release, comes directly from another vendor's site and is subject to change without notice.{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, 7 months
[JBoss JIRA] (JBIDE-12946) add code coverage support to jbosstools-4.0_trunk.tests
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-12946:
----------------------------------
Summary: add code coverage support to jbosstools-4.0_trunk.tests
Key: JBIDE-12946
URL: https://issues.jboss.org/browse/JBIDE-12946
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng, testing
Affects Versions: 4.0.0.CR1
Reporter: Nick Boldt
Assignee: Mickael Istria
Fix For: 4.0.0.CR1
Need your help here.
I've migrated https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... to use 15 git repos and run a mvn build 7 times (2 x bootstrap builds for central and birt, then 5 x single component builds).
But I'm getting this error:
{code}
[WARNING] The requested profile "coverage" could not be activated because it does not exist.
[WARNING] The requested profile "local.requirements" could not be activated because it does not exist.
{code}
Can you work your magic to enable code coverage for this job?
--
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, 7 months