|> use them) very useful for things like specifying the number of iterations |> on stress tests. I think the big problem is people trying to check 2.4
Don't even get me started on the test stuff... I had to rip everything out in XML just to run one test at a time and then we don't get the gui anymore so I can't run just one method etc etc. marcf |out |> using jboss-all and 3.0 out without using jboss-all. I can't find any |> instructions on building 2.4, and the ones for 3 are hard to find. |> |> I think the semi-unfinished state of 3 may be a more likely |barrier to new |> work. |> |> david jencks |> |> On 2001.11.02 20:36:23 -0500 marc fleury wrote: |> > While I agree that this is not a bug, and it should therefore |be closed, |> > I |> > do agree with the guy who gave that bug. It is true that "buildmagic" |is |> > WAAAAAAY too complex for what it does and introduces an unnecessarily |> > scary |> > barrier to entry. |> > |> > I don't use the 1000 configuration files that come with it, never will. |> > The |> > only thing that is useful there is the capacity to build all |the modules |> > in |> > a dependent way, that is good. |> > |> > The rest is useless. |> > |> > marcf |> > |> > PS: The deeper scare for me is that we were commenting with Scott that |> > no-one has really come into the code lately, meaning no new |blood in the |> > last 2 month. That is not good and it corresponds to the introduction |of |> > buildmagic. It will need to be simplified A LOT or it will need to be |> > replaced by something simpler. A un-necessarily complex build |> > environment |> > is the surest way to kill the development on JBoss. |> > |> > As a first step I don't think there should be ANY configuration file |> > besides |> > the xml build. |> > |> > |> > |-----Original Message----- |> > |From: [EMAIL PROTECTED] |> > |[mailto:[EMAIL PROTECTED]]On Behalf Of |> > |[EMAIL PROTECTED] |> > |Sent: Friday, November 02, 2001 6:55 PM |> > |To: [EMAIL PROTECTED] |> > |Subject: [JBoss-dev] [ jboss-Bugs-450615 ] Build instructions???? |> > | |> > | |> > |Bugs item #450615, was opened at 2001-08-13 14:11 |> > |You can respond by visiting: |> > |http://sourceforge.net/tracker/?func=detail&atid=376685&aid=450615&; |> > |group_id=22866 |> > | |> > |Category: None |> > |Group: None |> > |>Status: Closed |> > |>Resolution: Rejected |> > |Priority: 5 |> > |Submitted By: Nobody/Anonymous (nobody) |> > |Assigned to: Andreas Schaefer (schaefera) |> > |Summary: Build instructions???? |> > | |> > |Initial Comment: |> > |There are no build instructions anywhere. |> > | |> > |Simply downloading the cvs projects listed, and running a build.sh |> > |doesn't do the trick. |> > | |> > |Also, not all the projects are listed. Looking in the developer |> > |archive suggested a project called |> > |jboss-all, which did put some more stuff on disk, but nothing that |> > |made the build run. |> > | |> > |Firing off ant on some build.xml files also doesn't go very far. |> > | |> > |So, what are the secret steps to build jboss from source? |> > | |> > |Thanks! |> > | |> > |---------------------------------------------------------------------- |> > | |> > |Comment By: Andreas Schaefer (schaefera) |> > |Date: 2001-10-29 20:21 |> > | |> > |Message: |> > |Logged In: YES |> > |user_id=70434 |> > | |> > |Build current CVS HEAD for Rabbit Hole: |> > |- checkout CVS module "jboss-all" |> > |- go to "jboss-all/build" |> > |- start either "build.sh" or "build.bat" |> > | |> > |Run then the builded JBoss instance: |> > |- go to "jboss-all/build/output/jboss*/bin" where * means |> > |the current version |> > |- start either "run.sh" or "run.bat" |> > | |> > |Further options (inclusive running the test suite): |> > |- go to "jboss-all/build" |> > |- start either "build.sh help" or "build.bat help" but do |> > |not mix this up with "build -help" |> > |- go from there |> > | |> > |Building components: |> > |- go to the component you want like "jboss-all/server" |> > |- start either "build.sh" or "build.bat" from there |> > |- the compiled code can be found under "jboss- |> > |all/server/output" |> > | |> > |Andy |> > | |> > |---------------------------------------------------------------------- |> > | |> > |Comment By: Christian Biasuzzi (bchristian) |> > |Date: 2001-08-22 03:26 |> > | |> > |Message: |> > |Logged In: YES |> > |user_id=220544 |> > | |> > |I checked-out the whole list of projects listed, including |> > | build, thirdparty, tools |> > |I renamed folder names according to a config.xml as follows: |> > | jboss -> server |> > | jnp -> naming |> > | jbossmp -> messaging |> > | jbosscx -> connector |> > | jboss-j2ee -> j2ee |> > | contrib -> plugins |> > | jbosspool -> pool |> > | jbosssx -> security |> > | jbossmx -> cluster |> > |I copied build/jboss content to build/ and launched build |> > | script from there. The former dist folder is now in |> > | build/output |> > | |> > |it worked from me! |> > | |> > | |> > | |> > |---------------------------------------------------------------------- |> > | |> > |You can respond by visiting: |> > |http://sourceforge.net/tracker/?func=detail&atid=376685&aid=450615&; |> > |group_id=22866 |> > | |> > |_______________________________________________ |> > |Jboss-development mailing list |> > |[EMAIL PROTECTED] |> > |https://lists.sourceforge.net/lists/listinfo/jboss-development |> > |> > |> > _______________________________________________ |> > Jboss-development mailing list |> > [EMAIL PROTECTED] |> > https://lists.sourceforge.net/lists/listinfo/jboss-development |> > |> > |> |> _______________________________________________ |> Jboss-development mailing list |> [EMAIL PROTECTED] |> https://lists.sourceforge.net/lists/listinfo/jboss-development |> | | |_______________________________________________ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
