On 5/7/09, Heiko Seeberger <heiko.seeber...@googlemail.com> wrote:
> I provision via Maven, e.g.
>
> <dependency>
>
> <groupId>org.scalamodules</groupId>
>
> <artifactId>scalamodules-core</artifactId>
>
> <version>${project.version}</version>
>
> <scope>provided</scope>
>
> </dependency>
> with ${project.version} == 1.1-SNAPSHOT
>
> Here is my maven-paxexam-plugin config:
>
> <plugin>
>
> <groupId>org.ops4j.pax.exam</groupId>
>
> <artifactId>maven-paxexam-plugin</artifactId>
>
> <executions>
>
> <execution>
>
> <id>generate-config</id>
>
> <goals>
>
> <goal>generate-config</goal>
>
> </goals>
>
> </execution>
>
> </executions>
>
> <configuration>
>
> <settings>
>
> <platform>felix</platform>
>
> </settings>
>
> </configuration>
>
> </plugin>
>
> The paxexam-config.args looks like that:
> # Configurations generated by the Pax Exam Maven Plugin
> # Generated at: Thu May 07 10:48:48 CEST 2009
>
> # groupId = org.scalamodules
> # artifactId = scalamodules-core-test
> # version = 1.1-SNAPSHOT
> # org.scalamodules/scalamodules-core-test/version = 1.1-SNAPSHOT
>
> # provisioning
>
> scan-bundle:file:/Users/heiko/dev/projects/scalamodules/core/core/target/scalamodules-core-1.1-SNAPSHOT.jar
> scan-bundle:file:/Users/heiko/dev/projects/scalamodules/util/util/target/scalamodules-util-1.1-SNAPSHOT.jar
> scan-bundle:file:/Users/heiko/.m2/repository/org/scala-lang-osgi/scala-library/2.7.4/scala-library-2.7.4.jar
> scan-bundle:file:/Users/heiko/.m2/repository/org/apache/felix/org.apache.felix.configadmin/1.0.10/org.apache.felix.configadmin-1.0.10.jar
>
> # Settings parsed from pom.xml in settings of plugin
>
> I cannot reproduce this with plain Pax Runner, because these are test cases
> executed by Pax Exam. But I use Pax Runner successfully with the scala
> profile to run demos like that:
> scan-bundle:mvn:org.scalamodules/scalamodules-util/1.1-snaps...@update
> scan-bundle:mvn:org.scalamodules/scalamodules-core/1.1-snaps...@update
> scan-bundle:mvn:org.scalamodules/scalamodules-services/1.1-snaps...@update
> scan-bundle:mvn:org.scalamodules/scalamodules-core/1.1-snaps...@update
> scan-bundle:mvn:org.scalamodules/scalamodules-demo/1.1-snaps...@update
> scan-bundle:mvn:org.scalamodules/scalamodules-demo-depend/1.1-snaps...@update
> scan-bundle:mvn:org.scalamodules/scalamodules-demo-get/1.1-snaps...@update
> scan-bundle:mvn:org.scalamodules/scalamodules-demo-register/1.1-snaps...@update
> scan-bundle:mvn:org.scalamodules/scalamodules-demo-track/1.1-snaps...@update
>
> Maybe the generated paxexam-config.args should also have @update ?!
Yes, thats what i wanted to hear.
I think this is a sole bug in the plugin (no @update) that does not
happen when priovisioning in java directly.
I am locked away from any internet service other than html pages for
the daytime, so do you want to fix that in 0.5.1-SNAPSHOT ?
Else, i will do at nighttime.
Sorry for inconvinience. Also open an Issue on Jira pls. ;)
Toni
>
> Cheers
> Heiko
>
> 2009/5/7 Toni Menzel <t...@okidokiteam.com>
>
>> How do you provision?
>> --> maven plugin ? any settings set in plugin config ?
>> How does the generated paxexam.args look like (the one that sits in
>> target/classes/META-INF/.. e.g. after running maven2 once (generated
>> by the plugin)
>> ?
>>
>> Same happens with "just" pax runner?
>>
>>
>> On 5/7/09, Heiko Seeberger <heiko.seeber...@googlemail.com> wrote:
>> > Hi,
>> > Today I spotted a
>> very-hard-to-spot-and-make-you-believe-that-you-are-crazy
>> > problem:
>> >
>> > In my setup Pax Exam (Pax Runner) copies the bundles which are to be
>> > provisioned for the tests into the temporary directory
>> > /tmp/paxexam_runner_heiko/bundles/. OK, I know that behavior from using
>> Pax
>> > Runner standalone, then I see a runner/ directory local to the directory
>> > where I start Pax Runner.
>> >
>> > The problem is, that obviously the bundles in that temporary directory
>> > /tmp/paxexam_runner_heiko/bundles/ are NOT updated when I rebuild my
>> > project(s). On my local machine I did not run into problems, because
>> > /tmp
>> > will be erased pretty often, hence there is kind of a forced update. But
>> on
>> > the scala-tools Hudson build server I got into trouble.
>> >
>> > Now I wonder if my setup is somehow crappy or if this is a bug. In my
>> > opinion the default should be that Pax Exam uses Pax Runner in a way
>> > that
>> on
>> > each build the fresh artifacts are provisioned, not some old copies.
>> >
>> > Thanx
>> > Heiko
>> > --
>> > My blog: heikoseeberger.name
>> > Follow me: twitter.com/hseeberger
>> > OSGi on Scala: www.scalamodules.org
>> > Lift, the simply functional web framework: liftweb.net
>> >
>>
>>
>> --
>> Toni Menzel
>> Independent Software Developer - Looking for new projects!
>> Professional Profile: http://www.osgify.com
>> Blog: tonitcom.blogspot.com
>> t...@okidokiteam.com
>> http://www.ops4j.org - New Energy for OSS Communities - Open
>> Participation Software.
>>
>> _______________________________________________
>> general mailing list
>> general@lists.ops4j.org
>> http://lists.ops4j.org/mailman/listinfo/general
>>
>
>
>
> --
> My blog: heikoseeberger.name
> Follow me: twitter.com/hseeberger
> OSGi on Scala: www.scalamodules.org
> Lift, the simply functional web framework: liftweb.net
>
--
Toni Menzel
Independent Software Developer - Looking for new projects!
Professional Profile: http://www.osgify.com
Blog: tonitcom.blogspot.com
t...@okidokiteam.com
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
