for example:
spring-tx
jpa
transaction
jndi
assembly:file:///D:\\Projects\\JeetConsulting\\jeet-core\\Sources\\jeet-core\\jeet-core-api\\target\\classes
it helps to have when we develop hav
Will we perform this RC off of our current SVN scm or wait for the git
infrastructure to be in place?
In either case let's do a quick review of current 2.3.2 pending issues, and
bump out those we can to 2.3.3. Once the 2.3.2 RC is up we should be in a
good position to spin up 3.0.0.RC2 as well for
No, I would prefer to cut off 2.3.2 and 3.0.0.RC2 from svn (I'm working
on the latest issues).
We will switch to git just after these releases.
Regards
JB
On 06/30/2013 07:35 PM, Jamie G. wrote:
Will we perform this RC off of our current SVN scm or wait for the git
infrastructure to be in pla
Sounds good. If anyone has an issue assigned to them that they know can be
bumped out to the next RC please feel free to update Jira fix version.
-J
On Sun, Jun 30, 2013 at 5:07 PM, Jean-Baptiste Onofré wrote:
> No, I would prefer to cut off 2.3.2 and 3.0.0.RC2 from svn (I'm working on
> the la
Hi all,
the vote passed with the following result:
+1 (binding): Jamie Goodyear, Jean-Baptiste Onofré, Achim Nierbeck
I'm promoting the artifacts to Central, update Jira, and announce the
release on the website and mailing lists.
Thanks all for your vote.
Regards
JB
On 06/25/2013 10:02 PM,
Have you tried the "bundle:watch" command?
Assuming your project constists of multiple bundles, you can just
rebuild a single bundle (via mvn install). and karaf will automatically
pickup the new SNAPSHOT-version from your local .m2.
I'm not sure how well that works with wars (I remember havi
