Since yesterday I cannot checkout anymore, getting errors like this:
svn: In directory 'hibernatetools/docs/task-reference/en-US'
svn: Can't open file 'hibernatetools/docs/task-reference/en-US/.svn/tmp/text-base/sect-Hibernate_Tools_Reference_Guide-Concepts-Ant_tasks-Hibernate_configurations.xml.svn-base': No such file or directory
not sure what is causing it yet, but why on earth do we have so insanely long filenames in the first place ?
The org.jboss.tools.ui.bot.ext.test project contains a bundle with the
Bundle-Name: WebService SWTBot Tests
These name and id are invalid because there is the
trunk/ws/tests/org.jboss.tools.ws.ui.bot.test project with the same id
The trunk/jst/tests/org.jboss.tools.ui.bot.ext.test project needs to be
fixed or removed.
WebService SWTBot tests can't be run if the workspace contains both of
FYI, I created a deltacloud component which jjohnstn has started working on - for now its just prototyping so not to be in the overall build.
We'll see how it goes before we add it in permanently.
I also changed the jira notification for the overall mailing list to only include "new content" instead of *every* change.
i.e. now the maling list will get notified on issue creation, update, comment, comment edited, resolved & closed.
list will no longer get "work logged", "assign changed" , "moved issue" etc.
Those events will still be sent to those who actively are on the issue as either assignee, reporter or watcher.
@leifoolsen posted this http://www.glxn.net/seam-maven-refimpl/doc/tutorial/05-eclipse-3.6-worklo...
this is him explaining how to use JBoss Tools + Maven on a seam project.
The walkthrough illustrates how resource filtering in maven + the WTP assembly is fighting against each other ;(
it also shows that he also bumped into JBIDE-6596 with respect to lib/jboss-seam.jar.
Its an excellent read to see some of the problems we are facing....
the issue https://jira.jboss.org/browse/JBIDE-6596 New Seam WAR project
has incorrect deployment artifact structure is fixed in trunk and branch.
I was able replicate it without patch and was not on patched version.
There are no issues for 3.2.0.M1 anymore :)
We in out team are considering using seam, hibernate etc. But
jbosstools is in eclipse. Presently we use netbeans and do not want to
move to eclipse. We are condering adapting JBosstools for netbeans.
If anyone knows what needs to be done to achieve this, please assist
with the info.
If you develop/contribute to hibernate tools core then you should update your svn checkouts to use https://svn.jboss.org/repos/hibernate/tools/trunk
hibernate tools core (i.e. *not* the eclipse plugins) is now in the same structure as all the other hibernate modules.
I've moved trunk and the 3.2. branch into https://svn.jboss.org/repos/hibernate/tools
I've left the old tags in place since they all rely on the old hibernateext structure so felt wrong/broken to have them in the new one
(I believe it is the same Emmanuel did when annotations/validator "moved" - if not let me know :)
M1 is being build/baked and its due time we get M1 news and noteworthy docs finished.
I've talked with most today about this but in case I missed you then please if you've done any jiras
for M1 that are news and noteworthy then mark them as such with a label AND
add description/screenshot to the appropriate part in /trunk/documentation/whatsnew
Please do so ASAP since we hope to get M1 as soon as its ready and gotten a quick smoketest.