Addon dependencies in tests
by Ivan St. Ivanov
Hi folks,
As you might know I am working on the Git tools plugin migration to Forge
2.0 addon. I reached the point of migrating the tests and am trying to
understand how to declare the dependencies of the test to the current and
to other addons. I see five ways to do that:
1) In the test project's pom.xml
2) In the addon project's pom.xml
3) In the parent project's pom.xml
4) As @AddonDependency annotation of the getDeployment method
5) As parameter of ShrikWrap's addAsAddonDependencies method
Should I declare all my dependencies in those five places? Or there is a
difference between them. I need to understand especially the difference
between 4) and 5) and why do we need them both.
Thanks,
Ivan
12 years, 11 months
Fwd: [wildfly-dev] 8.0.0.Beta1 released
by Lincoln Baxter, III
FYI.
---------- Forwarded message ----------
From: Jason Greene <jason.greene(a)redhat.com>
Date: Mon, Oct 7, 2013 at 2:20 PM
Subject: [wildfly-dev] 8.0.0.Beta1 released
To: "wildfly-dev(a)lists.jboss.org" <wildfly-dev(a)lists.jboss.org>
Hello Everyone,
As many of you have already noticed, on Friday we released our first Beta
of WildFly 8. This is a significant release because all major features on
the 8 plan have been implemented; most notably all user facing Java EE7
APIs.
As always you can download the latest release here:
http://wildfly.org/download
Our overall status of the primary features follows. You can find this
information, along with additional details in the official release notes:
https://community.jboss.org/wiki/WildFly800Beta1ReleaseNotes
Java EE7
========
Java EE7 offers applications several productivity improving capabilities
including support for the modern web, batch processing, simplified
concurrent task processing, and improvements in dependency injection. At
this point all user facing EE7 APIs have been implemented! Aside from
achieving compliance certification, the only remaining work is to implement
a few updates in the security integration SPIs, JASPIC and JACC.
High Performance Web Server (Undertow.io)
=========================================
Undertow, the new cutting-edge web server in WildFly 8 is designed for
maximum throughput and scalability, including environments with over a
million connections. It supports non-blocking and blocking handlers,
traditional and asynchronous servlets, and JSR-356 web socket handlers. It
is highly customizable, with the ability for applications to implement
nearly anything from dynamic request routing to custom protocols. It can
also function as a very efficient, pure non-blocking reverse proxy,
allowing WildFly to delegate to other web servers with minimal impact to
running applications. Undertow has been fully integrated for several
releases now. This release finalizes the key features of this integration
with the addition of reverse proxy support.
Port Reduction
==============
An important goal of WildFly 8 was to greatly reduce the number of ports
used by multiplexing protocols over HTTP using HTTP Upgrade. This is a big
benefit to cloud providers (such as OpenShift) who run hundreds to
thousands of instances on a single server. Our default configuration now
only has three ports, and will become two ports by final. We decided to
preserve the original native management port for this Beta release to give
those using legacy clients time to update before the final release.The
native management port, 9999, is deprecated and will be removed by final.
Port Bound Interface Protocols
---- --------------- ---------
9990 management HTTP/JSON Management
HTTP Upgraded Remoting - (Native
Management & JMX)
Web Administration Console
8080 application HTTP (Servlet, JAX-RPC)
Web Sockets
HTTP Upgraded Remoting (EJB
Invocation, Remote JNDI)
9999 (deprecated) management Remoting - Native Management
Management Role Based Access Control (RBAC) & Auditing
======================================================
WildFly can now support organizations with separated management
responsibilities and restrictions. Roles represent different sets of
permissions such as runtime operation execution, configuration areas that
can read or written, and the ability to audit changes and manage users. In
addition a new restricted audit log can be enabled including the ability to
offload to a secure syslog server.
Patching
========
The infrastructure to support the application of patches to an existing
install has been implemented. This capability allows for a remote client to
install and rollback new static modules and binary files using the WildFly
management protocol.
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
12 years, 11 months
Announcing 2.0.0.Alpha13 of JBoss Forge (Lucky Thirteen)
by Lincoln Baxter
http://forge.jboss.org/news/2013/10/03/post-forge-2.html
We are pleased to announce the release of “Lucky Thirteen”, a Forge Runtime that features a streamlined programming model for Addon developers (no more @Exported annotation,) as well as a wide array of new Commands for developing Java EE applications.
***** Resource Transactions and Resource Change Monitoring *****
There are a lot of exciting features (as you can see by the release notes below); however, there are some outstanding features that we are proud to present. The first of which are resource transactions and monitoring.
***** Release Notes – Check out all the new stuff! *****
Bug
[FORGE-1192] – Ill behaved addons can screw up the command popup in Eclipse
[FORGE-1203] – Furnace CDI is unable to create proxies for services that are backed by Weld proxies (@ApplicationScoped, etc)
[FORGE-1206] – Imported<?>.get() has a different behavior compared to iterator()
[FORGE-1223] – CheckboxTableControlBuilder does not properly initialize data collection when default values are set
Enhancement
[FORGE-757] – Forge tests should delete the created folders
[FORGE-1196] – Rename flag forge.compatibility.IDE to forge.standalone
[FORGE-1239] – UISelectOne and UISelectMany components could have dynamic value choices
Feature Request
[FORGE-220] – Forge should listen to filesystem changes on the system and publish events for plugins to observe
[FORGE-801] – Support for Transactional Resources
[FORGE-846] – Create a template processor addon
[FORGE-1193] – Eclipse plugin doesn't handle subflows correctly
[FORGE-1194] – Support addition of warnings to a validation context
[FORGE-1195] – Support addition of information messages to a validation context
[FORGE-1197] – Eclipse plugin should render a Spinner component for Number types
[FORGE-1198] – UIValidationContext should reference the current input being validated
[FORGE-1200] – Add A@Column(length) on Entity attributes of type String
[FORGE-1202] – Furnace Maven plugin should allow generation of the full addon dependency graph
[FORGE-1205] – Migrate CommandScoped to Forge 2
[FORGE-1217] – UIProvider should provide a isGUI() method
Task
[FORGE-1111] – Write a test to ensure that furnace fails deployment if multiple containers are specified
Sub-task
[FORGE-1171] – Port the JMS commands
[FORGE-1174] – Port the JSTL commands
[FORGE-1175] – Port the JTA commands
[FORGE-1176] – Port the JAX-RS (REST) commands
[FORGE-1177] – Port the Servlet commands
[FORGE-1178] – Port the JAX-WS (SOAP) commands
[FORGE-1179] – Port the Bean validation commands
--
Lincoln Baxter, III
JBoss, by Red Hat
lbaxter(a)redhat.com
"If you want something, you'll find a way; if you don't, you'll find an excuse."
12 years, 11 months
JDK on 2.0.0.Alpha13
by George Gastaldi
Hello,
We found out that due to some last minute changes in our core pom.xml, the classes were compiled targetting 1.7. We already fixed that and it should be available in the next release.
In the meantime, do yourself a favor and use JDK7 :)
Best Regards,
George Gastaldi
12 years, 11 months
Announcing 2.0.0.Alpha13 of JBoss Forge (Lucky Thirteen)
by Lincoln Baxter
http://forge.jboss.org/news/2013/10/03/post-forge-2.html
We are pleased to announce the release of “Lucky Thirteen”, a Forge Runtime that features a streamlined programming model for Addon developers (no more @Exported annotation,) as well as a wide array of new Commands for developing Java EE applications.
***** Resource Transactions and Resource Change Monitoring *****
There are a lot of exciting features (as you can see by the release notes below); however, there are some outstanding features that we are proud to present. The first of which are resource transactions and monitoring.
***** Release Notes – Check out all the new stuff! *****
Bug
[FORGE-1192] – Ill behaved addons can screw up the command popup in Eclipse
[FORGE-1203] – Furnace CDI is unable to create proxies for services that are backed by Weld proxies (@ApplicationScoped, etc)
[FORGE-1206] – Imported<?>.get() has a different behavior compared to iterator()
[FORGE-1223] – CheckboxTableControlBuilder does not properly initialize data collection when default values are set
Enhancement
[FORGE-757] – Forge tests should delete the created folders
[FORGE-1196] – Rename flag forge.compatibility.IDE to forge.standalone
[FORGE-1239] – UISelectOne and UISelectMany components could have dynamic value choices
Feature Request
[FORGE-220] – Forge should listen to filesystem changes on the system and publish events for plugins to observe
[FORGE-801] – Support for Transactional Resources
[FORGE-846] – Create a template processor addon
[FORGE-1193] – Eclipse plugin doesn't handle subflows correctly
[FORGE-1194] – Support addition of warnings to a validation context
[FORGE-1195] – Support addition of information messages to a validation context
[FORGE-1197] – Eclipse plugin should render a Spinner component for Number types
[FORGE-1198] – UIValidationContext should reference the current input being validated
[FORGE-1200] – Add A@Column(length) on Entity attributes of type String
[FORGE-1202] – Furnace Maven plugin should allow generation of the full addon dependency graph
[FORGE-1205] – Migrate CommandScoped to Forge 2
[FORGE-1217] – UIProvider should provide a isGUI() method
Task
[FORGE-1111] – Write a test to ensure that furnace fails deployment if multiple containers are specified
Sub-task
[FORGE-1171] – Port the JMS commands
[FORGE-1174] – Port the JSTL commands
[FORGE-1175] – Port the JTA commands
[FORGE-1176] – Port the JAX-RS (REST) commands
[FORGE-1177] – Port the Servlet commands
[FORGE-1178] – Port the JAX-WS (SOAP) commands
[FORGE-1179] – Port the Bean validation commands
--
Lincoln Baxter, III
JBoss, by Red Hat
lbaxter(a)redhat.com
"If you want something, you'll find a way; if you don't, you'll find an excuse."
12 years, 11 months
