yeah I am using package to build the war (so its standard war packaging) and then the BRMS assembly grabs that war, as a file, and assembles it seperately - seems to work fine (also means I could have war exploded for deployment - which I may yet to as it means people can configure bits they need to tweak).
<br><br><div><span class="gmail_quote">On 4/24/07, <b class="gmail_sendername">Geoffrey De Smet</b> <<a href="mailto:ge0ffrey.spam@gmail.com">ge0ffrey.spam@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I 'll take a look, hopefully friday afternoon :)<br><br>But I did notice you using assembly 2.1 instead 2.2-beta-1 (in parent pom).<br><br>With kind regards,<br>Geoffrey De Smet<br><br><br>Mark Proctor wrote:<br>> geoffrey,
<br>><br>> I believe you have commit rights ;)<br>><br>> Mark<br>> Geoffrey De Smet wrote:<br>>><br>>> With kind regards,<br>>> Geoffrey De Smet<br>>><br>>><br>>> Mark Proctor wrote:
<br>>>> At the moment we have 3 assemblies, bin, src, brms. I couldn't get<br>>>> the drools-*.jar libs to go i na different direction to the<br>>>> dependencies, so now all jars are in the same directory.
<br>>><br>>> In maven-assembly-plugin 2.2-beta1 you can use <excludes> and<br>>> <includes> in dependency sets, so you can define 2 <dependencySet>,<br>>> each to a different dir.
<br>>> <a href="http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html">http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html</a><br>>><br>>>> Also for ease of distribution I don't think I'm going to have a bin
<br>>>> (without deps) and bin-withdeps, I'll just package the deps in as<br>>>> default now.<br>>>> <a href="http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/src/main/assembly/">http://anonsvn.labs.jboss.com/labs/jbossrules/trunk/src/main/assembly/
</a><br>>>><br>>>> build.xml and ant are now deprecated and most likely don't work, we<br>>>> will remove soon.<br>>>><br>>>> The documentation and the eclipse plugin are now profiles
<br>>>> -Ddocumentation=true and -Declipse=true. However it seems that<br>>>> somehow the docbook pathing has got screwed and isn't outputting<br>>>> properly, edson?<br>>>><br>>>> Mark
<br>>>> Geoffrey De Smet wrote:<br>>>>> > PS I was trying to make a way to put dependencies in a seperate "lib"<br>>>>> > folder, but maven didn't recognise the <dependencySets> tag - just
<br>>>>> > thought it would make for a neater distro for those not using maven.<br>>>>><br>>>>> Are you using the war or the assembly plugin to create the war?<br>>>>><br>
>>>> Both versions are locked down in the parent pom (which will be<br>>>>> enforced from maven 2.1 btw)?<br>>>>><br>>>>> They released maven-assembly-plugin 2.2-beta1, and I used
<br>>>>> dependencySet successfully in there. What exactly do you want to<br>>>>> assemble?<br>>>>><br>>>>> PS: to keep the "mvn install" on the parent pom with all modules
<br>>>>> fast, I can really recommend to do assembly's in a seperate profile.<br>>>>> I usually call this profile "production", but "complete" would be a<br>>>>> good name too.
<br>>>>><br>>>>> <profiles><br>>>>> <profile><br>>>>> <id>production</id><br>>>>> <build/plugins/plugin><br>>>>> <artifactId>maven-assembly-plugin</>
<br>>>>> <execution><br>>>>> <phase>package</><br>>>>> <goals/goal>assembly:attached</><br>>>>> </><br>>>>> <configuration>...
<br>>>>><br>>>>> So normal builds do:<br>>>>> mvn install<br>>>>><br>>>>> Complete builds do:<br>>>>> mvn -Pproduction install<br>>>>>
<br>>>>> Other examples of goals that take to long are jar signing etc for<br>>>>> webstart, that really needs to be in the "production" profile.<br>>>>><br>>>>> With kind regards,
<br>>>>> Geoffrey De Smet<br>>>>><br>>>>><br>>>>> Michael Neale wrote:<br>>>>>> BRMS is now added as a seperate file (just the war).<br>>>>>> Its a largish file (~20 meg it will be, all told) - so one other
<br>>>>>> idea is a seperate download.<br>>>>>><br>>>>>> Thoughts?<br>>>>>><br>>>>>> Michael.<br>>>>>><br>>>>><br>>>>>>
<br>>>>>> Michael.<br>>>>>><br>>>>>><br>>>>>> ------------------------------------------------------------------------<br>>>>>><br>>>>>>
<br>>>>>> _______________________________________________<br>>>>>> rules-dev mailing list<br>>>>>> <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>>>>>>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>>>>><br>>>>> _______________________________________________<br>>>>> rules-dev mailing list
<br>>>>> <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>>>>> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev
</a><br>>>>><br>>>><br>>>> _______________________________________________<br>>>> rules-dev mailing list<br>>>> <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org
</a><br>>>> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>>>><br>>><br>>> _______________________________________________
<br>>> rules-dev mailing list<br>>> <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>>> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev
</a><br>>><br>><br>> _______________________________________________<br>> rules-dev mailing list<br>> <a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>> <a href="https://lists.jboss.org/mailman/listinfo/rules-dev">
https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>><br><br>_______________________________________________<br>rules-dev mailing list<br><a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br></blockquote></div><br>