So imagine there's a connection.properties file and in there there's
something like ${db.username}.I think we're giving up on this particularly flaky plugin and using dependency:unpack instead. That looks like a bit more flexibility is available and that the documentation was caringly crafted. -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 22, 2007 3:37 PM To: Maven Users List Subject: Re: remote-resources 1. Mine is the trivial java project created by archetype simple. So yes, it has App.java and AppTest.java as well as resources. Only the resources are included in the xml file. But all files are in the jar. 2. That was not part of my test. What tokens are you hoping to replace, for what purpose? I expect this should probably work, but can't know without tests. Wayne On 8/22/07, EJ Ciramella <[EMAIL PROTECTED]> wrote: > 1 - Is your test project strictly configuration or is it an actual java > jar file plus configuration (ours is the latter) > 2 - When your second project pulls down this jar and includes it, does > it successfully replace the tokens in the config files? > > We have a "utils" project that contains some configuration. We're > trying to decide if we should create a utils-resources project as well > and put all the config in this second one or determine if it is possible > to just have the main one generate the resource jar (which seems we > can't). > > -----Original Message----- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 22, 2007 3:16 PM > To: Maven Users List > Subject: Re: remote-resources > > I guess we're just talking past each other... Let's start from the top. > > I have a little test project, pasted your pom config, ran the same > command and I got a jar with the remote-resources.xml file in the > proper place (with my resource file mentioned) with the file I had in > my resource directory in it. > > From what I can see, the plugin works as I'd expect for creating the > jar. > > Then, I made another test project, added the xml node from "how to > use", and sure enough, during the build Maven went out to my repo, > retrieved the jar, unbundled the resource file, and included it in my > new build. I know it "worked" since the resouce was a Macker rules > file and my Macker plugin used it. > > So, from what I can see, the plugin works as I'd expect for getting > files out of remote-resource bundles. > > Things seem to be working for me, but not you. What seems to be wrong > on your end, and why do you think it is wrong? > > Wayne > > On 8/22/07, EJ Ciramella <[EMAIL PROTECTED]> wrote: > > I was expecting it to understand the resources as listed in the pom > this > > plugin is configured in. > > > > Considering this is what the source plugin does with the java sources > > and that the resources directory is something maven is expecting, this > > (to me at least) seemed like a safe assumption. > > > > And looking over the detailed and thorough documentation, I saw > nothing > > otherwise. > > > > "This will retrieve the apache-jar-resource-bundle-1.0.jar from the > > remote repositories specified in your POM, process each resource in > the > > bundle and deposit them in your projects $basedir/target/classes > > directory." > > > > > > > > -----Original Message----- > > From: Wayne Fay [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, August 22, 2007 2:33 PM > > To: Maven Users List > > Subject: Re: remote-resources > > > > I'm not the original author of m-r-r-p but it seems likely to me that > > you are simply using it wrong or assuming certain things about how it > > should be used. > > > > I think you are "supposed" to have a single project that contains only > > the items you want to include in your remote-resources jar. So ie > > you'd make a jar containing your checkstyle and cpd/pmd config files, > > then use m-r-r-p to grab that resouce jar and use those config files > > in your other projects. > > > > What exactly were you expecting / assuming? That it would pick out > > your resource files only and make yet another jar called > > project-1.0.0-resources.jar? > > > > Wayne > > > > On 8/22/07, EJ Ciramella <[EMAIL PROTECTED]> wrote: > > > I see things getting into our source and bin jars, but still, here's > > my > > > plugin config: > > > > > > <plugin> > > > <artifactId>maven-remote-resources-plugin</artifactId> > > > > > > <executions> > > > <execution> > > > <goals> > > > <goal>bundle</goal> > > > </goals> > > > </execution> > > > </executions> > > > <configuration> > > > <includes> > > > <include>**/*</include> > > > </includes> > > > </configuration> > > > </plugin> > > > > > > And I'm running "mvn remote-resources:bundle package" - and still I > > > don't get a resource ONLY jar. Am I missing something? > > > > > > -----Original Message----- > > > From: Wayne Fay [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, August 22, 2007 12:42 PM > > > To: Maven Users List > > > Subject: Re: remote-resources > > > > > > I believe you will need to use "mvn remote-resouces:bundle package", > > > or attach the bundle goal to a phase to have it invoked > automatically. > > > > > > Bundle only makes the remote-resources.xml file, you still need to > jar > > > things up. > > > > > > Wayne > > > > > > On 8/22/07, EJ Ciramella <[EMAIL PROTECTED]> wrote: > > > > I'm really interested in getting this working as currently, we > have > > > one > > > > module that always has to build. > > > > > > > > What I don't see is how do these actually get jarred up or > packaged > > up > > > > into some kind of distributable? > > > > > > > > Running "mvn remote-resources:bundle" just creates a manifest file > > but > > > > no archive for down loading. > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
