[JBoss AS7 Development] - Logging deployment errors on start-up
by Alexey Loubyansky
Alexey Loubyansky [http://community.jboss.org/people/alex.loubyansky%40jboss.com] created the discussion
"Logging deployment errors on start-up"
To view the discussion, visit: http://community.jboss.org/message/571259#571259
--------------------------------------------------------------
At the moment it's silent. Suppose there is a deployment unit in the repository and listed in the config in <deployments> which is invalid and can't be deployed. Starting the server (standalone, at least) the logs will contain a line like
"INFO [org.jboss.as.deployment] (pool-1-thread-2) Activating deployment: managedbeans.jar"
but nothing more even if the deployment fails. One of the easiest ways to fix this would probably be using a UpdateResultHandler which would log things from AbstractServerModelUpdate
/** * Apply the boot action for this update. This action is only executed when the update is processed during * server startup. By default, this method simply invokes {@link #applyUpdate(UpdateContext, UpdateResultHandler, Object)} * directly, but this behavior should be overriden if a different action must be taken at boot time. * * @param updateContext the update context */ public void applyUpdateBootAction(UpdateContext updateContext) { applyUpdate(updateContext, UpdateResultHandler.NULL, null); }
instead of using UpdateResultHandler.NULL.
Any objections or other suggestions?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/571259#571259]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 4 months
Re: [jboss-dev-forums] [JBoss Tools Development] - Eclipse Summit 2010 Mini-Agenda
by Nick Boldt
Nick Boldt [http://community.jboss.org/people/nickboldt] commented on the document
"Eclipse Summit 2010 Mini-Agenda"
To view all comments on this document, visit: http://community.jboss.org/docs/DOC-16029#comment-4594
--------------------------------------------------
== Parent Pom & Target Platform Building == You can now build the parent pom & TP locally, and it will by default use the "unified.target" file, which points to [1]. [1] http://download.jboss.org/jbosstools/updates/target-platform/latest/ http://download.jboss.org/jbosstools/updates/target-platform/latest/ $ cd ~/trunk/build/parent; mvn3 clean install Next, build a component using the "bootstrap" profiles: $ cd ~/trunk/build/; mvn3 clean install -P jmx-bootstrap ---- You can also generate a local copy of the Latest TP update site [1] like this: $ cd ~/trunk/build/target-platform; mvn3 clean install -P get.local.target Then, to use that local target instead of the remote one: $ cd ~/trunk/build/parent; mvn3 clean install -P local.target Next, build a component using the "bootstrap" profiles: $ cd ~/trunk/build/; mvn3 clean install -P jmx-bootstrap,local.target ---- Behind the scenes, every time I run the build.xml script in ~/trunk/build/target-platform, we now generate/update BOTH the multiple.target (all the Eclipse.org and google.com repos) and unified.target (a single URL [1]) files. ---- Relative path issues still unresolved. I've published a copy of our parent pom into Nexus, but Tycho could not find it. Could be a misconfiguration in Nexus, but so far the JBQA folks haven't proven to be helpful here. == Source Bundles == I now have a Maven plugin / mojo for generating .source features from other features, but it's not quite complete. I'm also not sure how to hook it into a build so that it can run automatically. https://github.com/nickboldt/maven-plugins/tree/master/tycho-p2-source-fe... https://github.com/nickboldt/maven-plugins/tree/master/tycho-p2-source-fe... Need to also look at what Max did for JMX (not sure if it ever got committed to SVN). == Maven depoy == Target platform and Parent Pom now being published to Nexus: http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o... http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o... http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o... http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o... HOWEVER, last week the metadata wasn't being updated so builds that attempted to resolve the parent pom / target platform from the Nexus repo were failing. Today it seems OK so I'll try again. #weird == Documentation & Auditing == > Tracking contents of JBT/JBDS when built as aggregation - JBIDE-7444 > Create new HTML generator for both jboss.org and standalone index.html page (JBIDE-6958, JBIDE-7045) In progress. Here's a taste (some links + all images broken; need to aggregate upstream data into single file): http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta... http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.2.0.Beta... ---- Created a new mojo for testing GAV uniqueness and cleaning up ugly GAV values. Currently will fix groudId values and report info/warning/errors for all pom.xml files found under a given directory tree. https://github.com/nickboldt/maven-plugins/tree/master/tycho-p2-unique-GA... https://github.com/nickboldt/maven-plugins/tree/master/tycho-p2-unique-GA...
--------------------------------------------------
13 years, 4 months