Hi, I guess you hit the artifacts that are loaded on runtime but never referenced in the poms. It is not a maven dependency but an artifact that is derived from maven repositories. It also uses the maven semantics (GAV) in order to describe the dependency. So, this quite special behavior is implemented in an OPS4J project called Pax URL (there, look for the mvn protocol handler, which basically simulates maven artifact resolution just using plain java.net.URL)
When building the 1.2.1-SNAPSHOT trunk you'll get all artifacts required. Also the "special" artifact required at runtime. When changing the codebase (which is totally valid to do) please use snapshot versions (1.2.1-SNAPSHOT is the ops4j trunk) or change the source you are using to produce snapshot versions. Internally, paxexam will then look for the corresponding SNAPSHOT version. (just changing a released version is not meant to work, at least i never tried). So at best start working with snapshot versions, then share full logs, so we can help. Also do not hesitate to share your changes. cheers, Toni On Wed, Aug 4, 2010 at 7:17 PM, Gabor Komaromi <gabor_komar...@epam.com>wrote: > > > Hello there! > > I slightly modified the available PAX 1.2.0 codebase to fit my needs. > > > > What I need help in: > > 1. I removed the "-SNAPSHOT" trailings whereever I found throughout the > project from version specifications. > --Will that affect the compiled project in any bad way?-- > > 2. Then I made the "mvn install" and harvested the JARs from the created > M2 repo. > All new "pax-exam-*" and "pax-swissbox-*" JARs had 1.2.0 version > numbers. > --Is that normal?-- > > 3. I created a simple PAX test project (listing bundles, logging): > On classpath: > .; > ops4j-base-store-1.2.1.jar; > pax-exam-1.2.0.jar; > pax-exam-container-default-1.2.0.jar; > pax-exam-container-rbc-1.2.0.jar; > pax-exam-container-rbc-client-1.2.0.jar; > pax-exam-junit-1.2.0.jar; > pax-exam-junit-extender-1.2.0.jar; > pax-exam-runtime-1.2.0.jar; > pax-exam-spi-1.2.0.jar; > pax-runner-no-jcl-1.3.0.jar; > commons-discovery-0.4.jar; > commons-logging-1.1.jar; > junit-4.8.1.jar > > other options: > -Dorg.ops4j.pax.logging.DefaultServiceLog.level=INFO > -Dfile.encoding=Cp1252 > > Running: > org.junit.runner.JunitCore > > --What puzzles me most is that the tests run successfully, but when > I remove my local local M2 repo dir (from my Doc&Settings dir), it starts to > fail!-- > I could track back, that the tests need the > "pax-exam-container-rbc-1.2.0.jar" from my M2 repo. > Even if it is on the classpath (in an other directory of course) the > tests try to access the one in the repository. If they cannot access it, the > test FAIL! > Can anyone give an explanation on this dependency? > > Can anyone confirm, that "mvn install" on current 1.2.0 PAX EXAM > source produces a valid and distributable set of jars, and what are these? > > > I much await for your response as I'm not really experienced in maven > driven project development. > > Thanks in advance! > > Cheers, > Gábor > > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- Toni Menzel Independent Software Developer Professional Profile: http://okidokiteam.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
