mvn AS7 plugin - use of ..deploy goals with different standalone servers
by Wolf-Dieter Fink
Hi,
I'm looking for a possibility to test a clustered environment and to use
the
mvn jboss-as:deploy
command with different servers from the commandline by giving host:port
as parameter to avoid hard-coded properties within the pom.xml.
Or is it only possible by setting up a domain?
Wolf
14 years
Re: [jboss-as7-dev] JBOSGI docs
by Thomas Diesler
Hi David
On 05/15/2012 08:41 AM, David Bosschaert wrote:
> Hi Thomas,
>
> I made the OSGi subsystem section in AS7 point to JBOSGI documentation
> wiki as it contained pretty much all of the documentation needed.
>
> I had a look at the JBOSGI docs at
> https://docs.jboss.org/author/display/JBOSGI/JBoss+OSGi+Home and had a
> few thoughts, just thought I'd run them by you before changing
> anything...
>
> * The Getting Started page focuses on the JBOSGi installer and
> obtaining JBoss OSGi that way. I think it should focus on pure AS7
> where it mention that the AS7 installer can be used to obtain extra
> functionality, but I think people should realize that no additional
> download is needed to obtain JBoss OSGI...
We expect to have a faster release cycle than AS7. In future the jbosgi
installer can be used to update the osgi components in a given AS7
community release. We would update our binaries but not any of the
AS/integration code. The jbosgi examples demonstrate/document the scope
of supported functionality, which is the second aspect of an jbosgi
release. The third is a snapshot of documentation.
>
> * The bundle deployment section on the getting started page needs
> updating
yes
>
> * The CLI documentation needs to be added, do you agree that this can
> be added somewhere in the Application Server Integration section?
yes that'd be the right place. ConfigAdmin coverage is missing too.
>
> I am happy to make these changes but wanted to get your opinion first...
That'd be awesome.
cheers
>
> Cheers,
>
> David
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
14 years
Re: [jboss-as7-dev] Cannot find jboss-as-dist-7.1.2.Final
by Thomas Diesler
It seems bizarre that community has access to the 7.1.2.Final SCM tag
but cannot download the readily build artefacts from maven. As a result
I would have to tell jbosgi users to build AS7 themselves from the tag
to get access to the updated features. Is this really intended to work
that way?
I suggest to also publish the maven artefacts when there is a public SCM
tag. I understand that the download does not necessarily need to be
available here: http://www.jboss.org/jbossas/downloads.html
cheers
-thomas
On 05/14/2012 09:37 AM, Tristan Tarrant wrote:
> No dates AFAICT. Jason is probably under EAP pressure ;)
>
> Tristan
>
> On 05/14/2012 09:25 AM, Thomas Diesler wrote:
>> Thanks, do you also know details about the next community release?
>> This info is currently not visible in jira.
>>
>> On 05/14/2012 09:01 AM, Tristan Tarrant wrote:
>>> Thomas,
>>>
>>> 7.1.2.Final and onwards are tags for EAP only.
>>>
>>> Tristan
>>>
>>> On 05/14/2012 08:43 AM, Thomas Diesler wrote:
>>>> Folks,
>>>>
>>>> I don't see 7.1.2.Final in
>>>> https://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbo...
>>>>
>>>> Could you please have a look?
>>>>
>>>> cheers
>>>> -thomas
>>>>
>>>
>>
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
14 years
Consolidating ports under 80/443
by Bill Burke
Was screwing around with a web socket implementation and thought, why
don't we use HTTP Upgrade as the basis for all of our proprietary
protocols? That way we can consolidate and remove a bunch of different
ports we expose and have a standard way to initiate each of our pet
protocols.
That would of course require our Web container to actually allow and be
optimized for this, but that's a different conversation.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
14 years
PropertyEditorManager usage in JDK 7
by Carlo de Wolf
As of JDK 7 the function of PropertyEditorManager has been changed to
only work per ThreadGroup.
See https://issues.jboss.org/browse/AS7-4763
How is this issue going to be resolved for AS 7?
Then I can adapt something similar for EAP 5.
I myself am thinking about ditching PropertyEditorManager in favor of an
InstanceFinder<PropertyEditor> through the jar service loader.
Carlo
14 years
New 7.1 Branch and Pull Request Process
by Jason T. Greene
I have just updated our pull request testomg automation to handle
multiple branches. So from now on all pull requests need to made against
all active branches you want the fix to be included on.
We have just created a 7.1 branch, which will contain all fixes that go
into EAP6. master at this point in time is 7.2 only.
This means that many of your bug fixes will require 2 separate pull
requests (one for master and one for 7.1). It's a little bit of a burden
but its the best way to scale the process.
Thanks
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
14 years
Re: [jboss-as7-dev] Process for patching localized translation files
by Brian Stansberry
OK, thanks. We won't merge changes to these localized properties files then.
I added Component "Localization" to the AS7 project in JIRA. So problems
with the translations can be filed against the component to make it easy
for your team to find them.
We'll encourage contributors to help via zanata, but if they don't want
to an option is to attach patches to JIRAs filed against the
Localization component.
On 5/13/12 11:30 PM, Manuel Ospina wrote:
> Hello Brian,
>
> The best is to fix the error in Zanata itself. Otherwise it would be necessary to pull the content from Zanata, apply the patch and push the translations back to zanata.
>
> Regards,
> Manuel
>
> ----- Original Message -----
> From: "Brian Stansberry"<brian.stansberry(a)redhat.com>
> To: "Manuel Ospina"<mospina(a)redhat.com>
> Cc: "jboss-as7-dev(a)lists.jboss.org Development"<jboss-as7-dev(a)lists.jboss.org>
> Sent: Friday, May 11, 2012 3:47:40 AM
> Subject: Process for patching localized translation files
>
> Hi Manuel,
>
> Can you describe a bit what process we should follow for handling
> community updates to the localized text files in the AS? For example,
> the various LocalDescriptions_fr.properties files.
>
> The files are now in the AS codebase itself, so naturally people are
> going to start sending in patches that directly edit them [1]. But I
> suspect that's not the correct process, and perhaps changes need to go
> through https://translate.jboss.org/ with the person proposing the patch
> signing up and joining the appropriate language team?
>
> If the process isn't as simple as us directly accepting patches via
> github, it would be great to include some comments at the top of each
> file pointing to instructions on how to submit fixes.
>
> [1] For example, https://github.com/jbossas/jboss-as/pull/2292
>
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
14 years
Loggers/Message Bundles New Line Characters
by James Perkins
Hello All,
I've seen some usage of "\n" in logger messages and message bundles.
Since by default we're using the java.util.Formatter to format messages
it's preferred to use "%n" instead. This does two things; one (and most
important) it works with Zanata and two it's platform independent.
While you're adding or updating message, feel free to update any that
you see :-)
--
James R. Perkins
JBoss by Red Hat
14 years
Can not run testsuite - mvn dependency problem
by Wolf-Dieter Fink
I try to start a test after I build AS7 with 'mvn clean install'
(current upstream) with:
./integration-tests.sh
-Dtest=org.jboss.as.test.clustering.cluster.singleton.SingletonTestCase.java
but it fails with:
[WARNING] The POM for
org.jboss.as:jboss-as-testsuite-shared:jar:7.2.0.Alpha1-SNAPSHOT is
missing, no dependency information available
[WARNING] The POM for
org.jboss.as:jboss-as-build:pom:7.2.0.Alpha1-SNAPSHOT is missing, no
dependency information available
[WARNING] The POM for
org.jboss.as:jboss-as-arquillian-container-managed:jar:7.2.0.Alpha1-SNAPSHOT
is missing, no dependency information available
[WARNING] The POM for
org.jboss.as:jboss-as-build-config:jar:7.2.0.Alpha1-SNAPSHOT is missing,
no dependency information available
This is the same if I run
./integration-tests.sh install
Do I miss something or are there some wrong dependencies?
- Wolf
14 years
