[JBoss JIRA] (JBDS-3970) NullPointerException in Maven Project Builder'
by Josef Ludvicek (JIRA)
[ https://issues.jboss.org/browse/JBDS-3970?page=com.atlassian.jira.plugin.... ]
Josef Ludvicek updated JBDS-3970:
---------------------------------
Description:
RHDS shows {{Errors running builder 'Maven Project Builder' on project 'fafram8-docker'.}} when I save {{pom.xml}}.
There is Fuse tooling installed.
{code}
java.lang.NullPointerException
at org.fusesource.ide.projecttemplates.maven.CamelProjectConfigurator.installDefaultFacets(CamelProjectConfigurator.java:158)
at org.fusesource.ide.projecttemplates.maven.CamelProjectConfigurator.mavenProjectChanged(CamelProjectConfigurator.java:72)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:1000)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:783)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:930)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:300)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.getProjectFacade(MavenBuilder.java:154)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:89)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
was:
RHDS shows {{Errors running builder 'Maven Project Builder' on project 'fafram8-docker'.}} when I save {{pom.xml}}.
{code}
java.lang.NullPointerException
at org.fusesource.ide.projecttemplates.maven.CamelProjectConfigurator.installDefaultFacets(CamelProjectConfigurator.java:158)
at org.fusesource.ide.projecttemplates.maven.CamelProjectConfigurator.mavenProjectChanged(CamelProjectConfigurator.java:72)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:1000)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:783)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:930)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:300)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.getProjectFacade(MavenBuilder.java:154)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:89)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
> NullPointerException in Maven Project Builder'
> ----------------------------------------------
>
> Key: JBDS-3970
> URL: https://issues.jboss.org/browse/JBDS-3970
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: maven
> Affects Versions: 10.0.0.GA
> Reporter: Josef Ludvicek
>
> RHDS shows {{Errors running builder 'Maven Project Builder' on project 'fafram8-docker'.}} when I save {{pom.xml}}.
> There is Fuse tooling installed.
> {code}
> java.lang.NullPointerException
> at org.fusesource.ide.projecttemplates.maven.CamelProjectConfigurator.installDefaultFacets(CamelProjectConfigurator.java:158)
> at org.fusesource.ide.projecttemplates.maven.CamelProjectConfigurator.mavenProjectChanged(CamelProjectConfigurator.java:72)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:1000)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:783)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:930)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:300)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.getProjectFacade(MavenBuilder.java:154)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:89)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
> at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3970) NullPointerException in Maven Project Builder'
by Josef Ludvicek (JIRA)
Josef Ludvicek created JBDS-3970:
------------------------------------
Summary: NullPointerException in Maven Project Builder'
Key: JBDS-3970
URL: https://issues.jboss.org/browse/JBDS-3970
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: maven
Affects Versions: 10.0.0.GA
Reporter: Josef Ludvicek
RHDS shows {{Errors running builder 'Maven Project Builder' on project 'fafram8-docker'.}} when I save {{pom.xml}}.
{code}
java.lang.NullPointerException
at org.fusesource.ide.projecttemplates.maven.CamelProjectConfigurator.installDefaultFacets(CamelProjectConfigurator.java:158)
at org.fusesource.ide.projecttemplates.maven.CamelProjectConfigurator.mavenProjectChanged(CamelProjectConfigurator.java:72)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:1000)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:783)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:930)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:300)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.getProjectFacade(MavenBuilder.java:154)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:89)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-22757:
----------------------------------------
Referencing BUILD_ID is fine and isn't the cause of the issue as far as I understand. The issue is more in the scripts that have assumption that BUILD_ID is a timestamp. Although fixing BUILD_ID to look again as it used to is valid, maybe we should also consider it as an opportunity to think about reducing coupling from the scripts to such conventions. For example, rather than looking at timestamps in URL, scripts could just assume URLs alphabetical order is the same as temporary one to decide what to clean/publish.
Most of the linked scripts/pom do not assume much about the format or value of BUILD_ID and could work with any kind of value in it. So it's more likely "only" the publish and cleanup jobs that cause all the trouble and might be worth considering for a reduced coupling.
> jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
> -----------------------------------------------------------------
>
> Key: JBIDE-22757
> URL: https://issues.jboss.org/browse/JBIDE-22757
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.1.AM2
>
> Attachments: buildID-broken.png
>
>
> Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER.
> [1] https://issues.jenkins-ci.org/browse/JENKINS-26520
> [2] https://issues.jenkins-ci.org/browse/JENKINS-26626
> So instead of timestamped build folders, we're seeing things like this:
> !buildID-broken.png|thumbnail!
> Workaround until fixed in Jenkins:
> {code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code}
> Or, try using BUILD_TIMESTAMP instead?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3853) Installer: use node-rcedit instead of resourceHacker
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3853?page=com.atlassian.jira.plugin.... ]
Jan Richter reassigned JBDS-3853:
---------------------------------
Assignee: Jan Richter (was: Denis Golovin)
> Installer: use node-rcedit instead of resourceHacker
> ----------------------------------------------------
>
> Key: JBDS-3853
> URL: https://issues.jboss.org/browse/JBDS-3853
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Pavol Pitonak
> Assignee: Jan Richter
> Labels: havoc
> Fix For: 10.1.0.AM2
>
>
> Installer's metadata and icon are changed by Gulp using Resource Hacker which requires that we manually pre-compile its configuration on every change in metadata (e.g. project version).
> Change it to node-rcedit module (already used by electron-packager to do the same thing for binary inside self-extracting zip)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3965) Add a note on how to launch cdk in last page of devsuite installer
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3965?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3965:
-----------------------------
> Add a note on how to launch cdk in last page of devsuite installer
> ------------------------------------------------------------------
>
> Key: JBDS-3965
> URL: https://issues.jboss.org/browse/JBDS-3965
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 10.1.0.AM3
>
>
> Recently, [~rick_wagner] gave us some feedback on how he tried to use the devsuite installer and then connect to the docker daemon running in cdk.
> This is described here: JBIDE-22734
> What happened was that Rick didn't know he was supposed to start CDK from the Servers view. Having some prior knowledge of CDK, he started it from CLI. Then he went to the Docker Explorer view and wanted to connect to cdk's docker daemon.
> Normally, the docker connection will be created for you automatically, but that assumes you start the cdk adapter in Servers View.
> So here's a proposal:
> Perhaps at the end of the devsuite installer, just before devstudio is launched, we could briefly note that to start using CDK, you can start it from the Server view, once devstudio is launched?
> Please note that the actual name of the server adapter is probably Container Runtime Environment, but I'm not 100 % sure, this needs to be verified.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3965) Add a note on how to launch cdk in last page of devsuite installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3965?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3965:
--------------------------------
Status: New (was: New)
Target Release: 10.1.0.GA
> Add a note on how to launch cdk in last page of devsuite installer
> ------------------------------------------------------------------
>
> Key: JBDS-3965
> URL: https://issues.jboss.org/browse/JBDS-3965
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 10.1.0.AM3
>
>
> Recently, [~rick_wagner] gave us some feedback on how he tried to use the devsuite installer and then connect to the docker daemon running in cdk.
> This is described here: JBIDE-22734
> What happened was that Rick didn't know he was supposed to start CDK from the Servers view. Having some prior knowledge of CDK, he started it from CLI. Then he went to the Docker Explorer view and wanted to connect to cdk's docker daemon.
> Normally, the docker connection will be created for you automatically, but that assumes you start the cdk adapter in Servers View.
> So here's a proposal:
> Perhaps at the end of the devsuite installer, just before devstudio is launched, we could briefly note that to start using CDK, you can start it from the Server view, once devstudio is launched?
> Please note that the actual name of the server adapter is probably Container Runtime Environment, but I'm not 100 % sure, this needs to be verified.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3965) Add a note on how to launch cdk in last page of devsuite installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3965?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3965:
-------------------------------------
With very limited space on last page we cannot put there everything what is noteworthy, that's why we have link to
http://developers.redhat.com/devstudio-preview which redirects to article "Using JBoss Developer Studio 9.x's Container Development Kit Tooling".
IMO that article should cover this case and if it is not we should update it.
> Add a note on how to launch cdk in last page of devsuite installer
> ------------------------------------------------------------------
>
> Key: JBDS-3965
> URL: https://issues.jboss.org/browse/JBDS-3965
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 10.1.0.AM3
>
>
> Recently, [~rick_wagner] gave us some feedback on how he tried to use the devsuite installer and then connect to the docker daemon running in cdk.
> This is described here: JBIDE-22734
> What happened was that Rick didn't know he was supposed to start CDK from the Servers view. Having some prior knowledge of CDK, he started it from CLI. Then he went to the Docker Explorer view and wanted to connect to cdk's docker daemon.
> Normally, the docker connection will be created for you automatically, but that assumes you start the cdk adapter in Servers View.
> So here's a proposal:
> Perhaps at the end of the devsuite installer, just before devstudio is launched, we could briefly note that to start using CDK, you can start it from the Server view, once devstudio is launched?
> Please note that the actual name of the server adapter is probably Container Runtime Environment, but I'm not 100 % sure, this needs to be verified.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (TOOLSDOC-489) Add info about jQM properties tab
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-489?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-489:
------------------------------------
This may be worth looking into for the HTML5 docs. This is an older feature but may be useful in the workflow.
> Add info about jQM properties tab
> ---------------------------------
>
> Key: TOOLSDOC-489
> URL: https://issues.jboss.org/browse/TOOLSDOC-489
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: User Guide
> Affects Versions: devstudio 10.0
> Reporter: Michelle Murray
> Assignee: Supriya Bharadwaj
> Original Estimate: 3 hours, 15 minutes
> Remaining Estimate: 3 hours, 15 minutes
>
> Use Case: widget wizard offers useful way for those new to jQM to edit output code snippets. But widget wizards are only for adding new items to files. So need feature to edit in widget wizard manner once in file.
> Feature: Properties view has been enhanced for jQuery Mobile and HTML(5). Previously properties view was simply a table with attributes and values. Now has fields similar to those in widget wizards making it easier for those new to jQM to modify code snippets once in file.
> Writer Task: Create new topic within Features section, 'Managing??' Add info about purpose of enhanced properties view and how to access and edit. Add a screen cap of a sample properties tab view. Also update 'About Features' topic with new bullet for action.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (TOOLSDOC-489) Add info about jQM properties tab
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-489?page=com.atlassian.jira.plug... ]
Misha Ali reassigned TOOLSDOC-489:
----------------------------------
Assignee: Supriya Bharadwaj (was: Misha Ali)
> Add info about jQM properties tab
> ---------------------------------
>
> Key: TOOLSDOC-489
> URL: https://issues.jboss.org/browse/TOOLSDOC-489
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: User Guide
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Supriya Bharadwaj
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 3 hours, 15 minutes
> Remaining Estimate: 3 hours, 15 minutes
>
> Use Case: widget wizard offers useful way for those new to jQM to edit output code snippets. But widget wizards are only for adding new items to files. So need feature to edit in widget wizard manner once in file.
> Feature: Properties view has been enhanced for jQuery Mobile and HTML(5). Previously properties view was simply a table with attributes and values. Now has fields similar to those in widget wizards making it easier for those new to jQM to modify code snippets once in file.
> Writer Task: Create new topic within Features section, 'Managing??' Add info about purpose of enhanced properties view and how to access and edit. Add a screen cap of a sample properties tab view. Also update 'About Features' topic with new bullet for action.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months