May 2012 - jbosstools-dev - Jboss List Archives

jbosstools-3.3_trunk.aggregate - Build # 4816 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4816 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4816/ to view the results.

11 years, 11 months

1
0
0 / 0

jbosstools-3.3_trunk.aggregate - Build # 4813 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4813 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4813/ to view the results.

11 years, 11 months

1
1
0 / 0

jbosstools-3.3_trunk.aggregate - Build # 4811 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4811 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4811/ to view the results.

11 years, 11 months

1
0
0 / 0

Source lookup in maven component

by Max Andersen

Nick - forgot to mention snjezana will be adding sourcelookup to the maven component as a separate feature. If you spot something problematic dependency/build wise then let me know. /max (sent from my phone)

11 years, 11 months

7
19
0 / 0

jbosstools-3.3_trunk.aggregate - Build # 4798 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4798 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4798/ to view the results.

11 years, 11 months

1
0
0 / 0

jbosstools-3.3_trunk.aggregate - Build # 4796 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4796 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4796/ to view the results.

11 years, 11 months

1
0
0 / 0

new and noteworthy for Beta3

by Max Rydahl Andersen

Hi guys, It's that time again - get out the creative minds and fill in the blanks so users know what is changed/coming in Beta3. I've cloned last time round into https://issues.jboss.org/browse/JBIDE-11744 (and if you don't like CLONE CLONE CLONE then edit the title and it will be gone next time :) As always: :start if (N&N) { write it into the relevant section in trunk/documentation/whatsnew/* } else { Add N&N labels for those you forgot; if(still !N&N) reject; } goto start /max

11 years, 11 months

1
0
0 / 0

jbosstools-3.3_trunk.aggregate - Build # 4790 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_trunk.aggregate - Build # 4790 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/4790/ to view the results.

11 years, 11 months

1
3
0 / 0

jbosstools-3.3_stable_branch.aggregate - Build # 143 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_stable_branch.aggregate - Build # 143 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggreg... to view the results.

11 years, 11 months

1
0
0 / 0

What is expected of JBoss Seam 2.3 for JBoss Tools

by Daniel Hinojosa

I got done with a Skype conversation with Alexey Kazakov on how JBoss Tools will interact with the new Seam 2.3. The points are below. Some further questions are asked below. Many of you already know most of what is going on, this email is for clarification, information and to make this process as public as possible. * Latest JBT is used with Eclipse 3.7.2 Indigo * Seam 2.3 uses maven, therefore all dependencies are done through maven * JBT WILL NOT be using Maven * JBT only needs the initial seam distribution (zip file with lib) to have everything it needs to create a seam web project. * Once JBT has the initial distribution and libraries it can then use that to create a seam web project. * If the end user wishes to use JBT, they have to download the distribution, map it to SEAM_HOME. * If the end user doesn't wish to use JBT, they can just add dependencies to their maven pom files, and do what they want. * If the end user wants to use JBT AND Maven, that will not be supported currently (Need Verification) * JBT will expect that the end distribution of Seam will have a lib folder with required jars, a list of jars, and a seam.sh and seam.bat to run seam-gen * Seam 2.3 has a distribution module that creates the final distribution and uses the assembly plugin to achieve what JBT needs, this is the focus currently: https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/distribu... * JBT will still require seam.bat or seam.sh scripts so it can create entities and actions and that is already part of the current distribution https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/distribu... If this is not correct, please correct since if there is something wrong, it's because of a lack of understanding on my part. Hope this is beneficial. Danno

11 years, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev May 2012