CLI backspace on Mac OS
by Heiko Braun
What happened to the backspace support in the CLI?
It doesn't seem to work on MAC OS anymore.
Ike
13 years
IMPORTANT New JIRA Policy & Massive JBAS JIRA Reorg/Cleanup
by Jason T. Greene
Hi Everyone,
I'm sure many of you will agree that the JBAS jira has had a very poor
signal to noise ratio for awhile now. his has been a problem since
important issues often go unnoticed, and it's extremely time consuming
to do any kind of release or organization.
Our release model is such that we only focus on one major release at a
time. Once that happens it typically becomes part of the enterprise
product line which has it's own JIRA project (JBPAPP). Since we have a
very new architecture with 7, there isn't much value in keeping around
hundreds of stale issues which may not be relevant any more.
So, I have /closed all issues that were not assigned to an as7 release/
as out of date.
I have also renamed all components that are no longer relevant to be
prefixed with z - Legacy (to sort at the bottom).
From now on JIRA should accurately reflect our 7 timeline and work queue.
I am asking for everyone's help though in keeping this manageable by
doing the following:
1. When creating an issue that you intend to assign to yourself, pick a
fix-for release version that you can commit to achieving. Please be
realistic in making this choice, as very few of our issues do not get
rescheduled.
2. If you can not commit to a point in the schedule, but you just want
to log the issue to be worked on, then leave it unassigned and set the
fix-for to be "Open to Community". I am hoping this will be an easy
place to point people that want to jump in.
3. If you have an issue you know you cant work on, but think it is
timeline sensitive, then leave it unassigned and let me know about it.
We will figure out a way to resource it.
4. If you validate that a bug is valid then please schedule it or leave
a note so that when I go through them I can find a place for it.
5. If you are a component lead you will probably get auto-assigned. The
intention is that you will either take on the issue, delegate it to
someone else, verify it and unassign, or in the worst case just unassign.
Also note that I may close issues that are continually not resolved when
scheduled, so if you really care about the issue please schedule it
reliably.
If we do this right, we should start to see that each release has a
manageable number of issues on it, and that everyone has a reasonable
number assigned to them.
If you have any questions or any other ideas on how we can get a more
accurate reflection of our work in JIRA, then let me know.
Thanks!
--
Jason T. Greene
JBoss, a division of Red Hat
13 years
(JBAS-9163) "auto-start" not set for newly created sever-configs
by Heiko Braun
Brian wrote:
This is an example of a general issue that we need to resolve: whether the model should reflect only the actual user-provided configuration, with defaults omitted if not specified by the user, or should it include the default values?
If we don't include defaults in the model, they must be available via the model description.
We're inconsistent in our approach to this; for Beta3 we need to decide the approach we want.
I'm leaning toward including the defaults in the model. It takes more effort to not do that, and it's something that's likely to be done wrong.
13 years
JBAS-9225
by Scott Stark
I'm not sure what triggers the need to write out the standalone.xml in
the testing I'm doing, but under some circumstance, a new setup of the
server produces this warning, and then fails to start the next time
because the interfaces section is all but missing. In fixing JBAS-9225,
I'll add a comment to CommonXml.parseSimpleInterfaceCriterion that
changes there need to be matched by changes to
CommonXml.parseSimpleInterfaceCriterion
CommonXml.writePropertyInterfaceCriteria.
What would trigger a write of the standalone.xml if there are no admin
commands being issued?
10:58:21,807 WARN [org.jboss.as.controller] (pool-6-thread-2) Failed to
persist configuration change:
org.jboss.as.controller.persistence.ConfigurationPersistenceException:
Failed to store configuration:
org.jboss.as.controller.persistence.ConfigurationPersistenceException:
Failed to store configuration
at
org.jboss.as.controller.persistence.XmlConfigurationPersister.store(XmlConfigurationPersister.java:97)
at
org.jboss.as.controller.BasicModelController.persistConfiguration(BasicModelController.java:308)
at
org.jboss.as.server.ServerControllerImpl.persistConfiguration(ServerControllerImpl.java:215)
at
org.jboss.as.controller.BasicModelController$MultiStepOperationController.updateModelAndPersist(BasicModelController.java:668)
at
org.jboss.as.controller.BasicModelController$MultiStepOperationController.recordModelComplete(BasicModelController.java:652)
at
org.jboss.as.server.ServerControllerImpl$ServerMultiStepOperationController.recordModelComplete(ServerControllerImpl.java:475)
at
org.jboss.as.controller.BasicModelController$MultiStepOperationController.execute(BasicModelController.java:707)
at
org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:248)
at
org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:216)
at
org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:77)
at
org.jboss.as.controller.SynchronousOperationSupport.execute(SynchronousOperationSupport.java:88)
at
org.jboss.as.controller.AbstractModelController.execute(AbstractModelController.java:40)
at
org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentTask.call(FileSystemDeploymentService.java:1052)
at
org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentTask.call(FileSystemDeploymentService.java:1043)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
[:1.6.0_17]
at java.util.concurrent.FutureTask.run(FutureTask.java:166) [:1.6.0_17]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
[:1.6.0_17]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
[:1.6.0_17]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[:1.6.0_17]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[:1.6.0_17]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_17]
Caused by:
org.jboss.as.controller.persistence.ConfigurationPersistenceException:
Failed to write configuration
at
org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:108)
at
org.jboss.as.controller.persistence.XmlConfigurationPersister.store(XmlConfigurationPersister.java:90)
... 20 more
Caused by: java.lang.RuntimeException: Unknown property in interface
criteria list: org.jboss.dmr.Property@fbb8694
at
org.jboss.as.controller.parsing.CommonXml.writePropertyInterfaceCriteria(CommonXml.java:1311)
at
org.jboss.as.controller.parsing.CommonXml.writeInterfaceCriteria(CommonXml.java:1277)
at
org.jboss.as.controller.parsing.CommonXml.writeInterfaces(CommonXml.java:1262)
at
org.jboss.as.controller.parsing.StandaloneXml.writeContent(StandaloneXml.java:435)
at
org.jboss.as.controller.parsing.StandaloneXml.writeContent(StandaloneXml.java:77)
at org.jboss.staxmapper.XMLMapperImpl.doDeparse(XMLMapperImpl.java:78)
at
org.jboss.staxmapper.XMLMapperImpl.deparseDocument(XMLMapperImpl.java:73)
at
org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:102)
... 21 more
13 years
What is this Applying: Revert... I keep seeing?
by Scott Stark
Is is expected that I keep seeing this last message when pulling in
changes from upstream?
[27](ironmaiden:jboss-as) > git up upstream master
remote: Counting objects: 100, done.
remote: Compressing objects: 100% (31/31), done.
remote: Total 67 (delta 19), reused 59 (delta 12)
Unpacking objects: 100% (67/67), done.
From git://github.com/jbossas/jboss-as
* branch master -> FETCH_HEAD
First, rewinding head to replay your work on top of it...
Applying: Revert "refactoring + fixing bug in params processing method
(if all 'export', 'services' & 'optional' were specified on manifest
dependency, the last one in the param list have been improperly evaluated)"
13 years
update-resource-operation?
by Heiko Braun
I am wondering if we support update operations already?
I can only see add and remove.
Ike
13 years
7.0.0.Beta2-prerelease Tag
by Jason T. Greene
We have tagged and are now beating up Beta2. Provided it survives I will
cut the release this eventing (along with a detailed announcement).
--
Jason T. Greene
JBoss, a division of Red Hat
13 years
