On 19 November 2010 01:32, Pete Carapetyan <[email protected]>wrote:
> As a follow up, it seems that create-bundle works fine in Maven3, it > is only one of these two lines in the batch file that appears as if it > might not work in Maven3 > $ pax-add-repository -i com.springsource.repository.bundles.external > -u http://repository.springsource.com/maven/bundles/external > $ pax-import-bundle -g org.springframework.osgi -a > spring-osgi-extender -v 1.1.2 -- -DimportTransitive -DwidenScope afaict there are two separate issues both involving use of (internal) Maven APIs which changed in Maven 3 :/ 1) MavenProject.addPlugin / PAXCONSTRUCT-128 2) Dependency traversal --> this affects the pax-import-bundle, which is why you get different results above Unfortunately I'm snowed under with other projects at the moment, so if anyone else wants to pick this up and get things working on Maven 3 please feel free - it should just be a matter of updating the code to use the latest MavenProject and dependency APIs... > On Thu, Nov 18, 2010 at 7:14 PM, Pete Carapetyan > <[email protected]> wrote: > > Regarding this really nifty batch file that creates a springDM > > project: You still have a little coding to do, but it works great! > > http://www.ops4j.org/projects/pax/construct/examples/spring-osgi.html > > > > What is really cool is you can see your service running even before > > using pax-exam, just type in services at the osgi> prompt > > > > Then, Maven3 broke the above batch file, so you have to employ this > > workaround by moving some xml around if you want to use Maven3: > > http://issues.ops4j.org/browse/PAXCONSTRUCT-128 > > > > What I am finding is that projects created with the Maven 2 and this > > batch file (and with the above workaround done anyway! ) work great, > > even when run later with Maven3. > > > > However, the same projects created with Maven 3 and this batch file > > (and the above workaround done properly) never allows the spring > > service to launch. > > > > I have repeated this several times with fresh artifacts just to make > > sure, it always seems to work - or not - the same way. > > > > Is this a familiar and expected result? It is a very sneaky bug > > because it leaves no traces of errors that I can find, it just doesn't > > work at runtime, after the artifacts are created, apparently without > > error. > > > > Comments? Suggestions? This actually may be a huge breakthrough for > > me, because I've been trying to use Maven3 (m2eclipse) for months, and > > never knowing why it didn't work at runtime. But a fix would be very > > helpful. > > > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > -- Cheers, Stuart
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
