Is there a reason the mvn version cannot include 2.2.1?
by Scott Stark
I'm using mvn 2.2.1, and when I try to build the embedded project its
failing with:
[WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireMavenVersion
failed with message:
Detected Maven Version: 2.2.1 is not in the allowed range [2.0.9,2.2.1).
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Some Enforcer rules have failed. Look above for specific messages
explaining why the rule failed.
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 8 seconds
[INFO] Finished at: Thu Dec 03 20:59:03 PST 2009
[INFO] Final Memory: 26M/80M
[INFO]
------------------------------------------------------------------------
When I update the version range to allow 2.2.1 the build completes fine,
so is there a known problem wiht 2.2.1 or was this just locked down
prior to the release of that version?
14 years, 5 months
Byteman 1.2.0 release now available
by Andrew Dinn
Byteman release 1.2.0 has now been released and is available from the
project downloads page http://www.jboss.org/byteman/downloads.
This release is primarily a feature upgrade extending the Byteman rule
language to support two new types of rules:
interface rules
-- rule code is injected through an interface into all classes which
implement the interface
overriding rules
-- rule code is injected down class hierarchies into a both the target
class's method and into the methods of subclasses which provides an
overriding implementation
These two new modes of injection may be used in isolation but they also
work in combination. For example, the following rule adds trace code to
the run method of every implementor of Runnable and to every overriding
implementation, effectively tracing every run() operation in the JVM.
RULE trace any Runnable.run() call
INTERFACE ^java.lang.Runnable
METHOD run()
IF TRUE
DO System.out.println("Running runnable " + $0 +
" " + $0.getClass().getName())
ENDRULE
Full details of the syntax and operation of these two new rule types are
included in the 1.2.0 programmers guide.
The release also includes several bug fixes including, most notably, a
much more reliable implementation of tool bytemancheck, which performs
offline rule syntax and type checking. Release notes are available from
the project downloads page http://www.jboss.org/byteman/downloads.
14 years, 5 months
[JBoss-dev] Verify with JSESSIONID
by Syamsundar
All,
What is the best way to verify if a given JSESSIONID is valid/not, if it is
going to be given to the app server through the web server (not through
browser submission but through another means).
Regular calls:
Client's Browser -> Originating Web Server -> App Server
New Way to verify JSESSIONID:
Client's Browser -> Another Web Server -> Originating App Server -> If
Verified -> Another App Server.
I hope I put it in clear words.
Thanks,
-Syam
-----
Learning web technologies... one at a time!
:working:
--
View this message in context: http://old.nabble.com/Verify-with-JSESSIONID-tp26605424p26605424.html
Sent from the JBoss - Dev mailing list archive at Nabble.com.
14 years, 5 months
6.0.0.M1 Tagged! (Branch_5_x removed)
by Jason T. Greene
6.0.0.M1 has been tagged, and will be released once it passes QA. There
will be another announcement once this occurs.
Also, Branch_5_x has been removed, and all hudson jobs against it have
been disabled.
We now have one community development branch, and that is trunk.
Thanks!
--
Jason T. Greene
JBoss, a division of Red Hat
14 years, 5 months
