Re: missing

[pankjajain15]

Thanks wayne;

following is settings.xml file from conf folder of maven

please have a look at it and tell me the error as i am very much new to the
maven






http://maven.apache.org/SETTINGS/1.0.0";
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd";>
  

  

  

  
  

  

  
  

  

  
  



  

  
  

  

  
  








  

  





Wayne Fay wrote:
> 
>> javax.faces:jsf-api:jar:1.2_12:compile
>> javax.faces:jsf-impl:jar:1.2_12:compile
>> 4/23/10 4:55:53 PM IST: Missing artifact el-impl:el-impl:jar:1.0:provided
>> org.richfaces.framework:richfaces-api:jar:3.3.3-SNAPSHOT:compile
>> org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT:compile
>> org.richfaces.ui:richfaces-ui:jar:3.3.3-SNAPSHOT:compile
>> org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT:provided
> 
> It seems you are missing a  declaration in your settings.xml
> file.
> 
> SNAPSHOTs are not hosted in Central. And the latest jsf-api and -impl
> versions in Central is 1.2_02.
> 
> Wayne
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/missing-tp28363089p28373087.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Timestamped SNAPSHOTS

[Kumar Ampani]

I have a web(war) project and I see a SNAPSHOT (ex: mylib-2.0-SNAPSHOT)
dependency copied to WEB-INF/lib sometimes with Timestamp
(mylib-2.0-20100426-27282.jar) and sometimes just SNAPSHOT (
mylib-2.0-SNAPSHOT).
Why is that and any work arounds ? As one would expect,  I always like to
see 2.0-SNAPSHOT in my web-inf/lib.

Thanks
Kumar

Re: Help with Ant task

[Eduardo M KALINOWSKI]

On 04/26/2010 06:41 PM, Lorenzo Thurman wrote:

I'm just learning both Maven and Ant. I have a couple of weeks of working with 
Maven, but not I need to get it execute and Ant task. I know nothing about Ant, 
but using the antrun plugin for Maven, I've got things to the point where the 
task attempts to execute, but fails because it can't find a class which is 
contained within a jar file. The jar containing the class is actually 
referenced in the build.xml via classpath and classname tags. It seems to 
follow that if the Ant task can find the jar when running under Ant, it should 
do so when running via Maven, but that's not the case. So, my question is how 
do I pass a classpath variable to an Ant task from Maven? I case there are 
fundamental flaws in my approach, I've included both my pom.xml and the 
build.xml that should be executed.
   


List the jar file with the custom task as a dependency of the plugin:



4.0.0
acquitygroup.AMA
AMA
1


primary



org.apache.maven.plugins
maven-antrun-plugin





   



...
  ...









   



--
Someday we'll look back on this moment and plow into a parked car.
-- Evan Davis

Eduardo M KALINOWSKI
edua...@kalinowski.com.br


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Help with Ant task

[Lorenzo Thurman]

I'm just learning both Maven and Ant. I have a couple of weeks of working with 
Maven, but not I need to get it execute and Ant task. I know nothing about Ant, 
but using the antrun plugin for Maven, I've got things to the point where the 
task attempts to execute, but fails because it can't find a class which is 
contained within a jar file. The jar containing the class is actually 
referenced in the build.xml via classpath and classname tags. It seems to 
follow that if the Ant task can find the jar when running under Ant, it should 
do so when running via Maven, but that's not the case. So, my question is how 
do I pass a classpath variable to an Ant task from Maven? I case there are 
fundamental flaws in my approach, I've included both my pom.xml and the 
build.xml that should be executed.

Here is my pom.xml:

4.0.0
acquitygroup.AMA
AMA
1


primary



org.apache.maven.plugins
maven-antrun-plugin













Here is the build.xml that's being called:





































 
 
 
 
Module Build Order: ${module.files.string}







































   


























Copying server configs from ${global.server.dir} to 
${dynamo.home}/servers

   
 
   






  
  
  
  


  


http://java.sun.com/j2se/1.4.2/docs/api/";
packagelistLoc="${jdk.docs.dir}"/>
http://www.atg.com/repositories/ContentCatalogRepository_en/manuals/ATG7.1/apidoc/";
packagelistLoc="${dynamo.docs.dir}"/>
  






"There are 10 types of people in this world: those who understand binary, those 
who don't"
--Unknown

Lorenzo Thurman
lore...@thethurmans.com

Re: Release plugin & git repo with multiple projects

[Kathryn Huxtable]

Although you can create a new git repo, add a remote, and then pull a single 
branch. Not the same as checking out a directory from svn, but you don't *have* 
to get the entire repo.

I use this in my wagon-gitsite app to push docs to the gh-pages branch of 
github projects.

-K

On Apr 26, 2010, at 3:18 PM, Justin Edelson wrote:

> Jean-Laurent de Morlhon wrote:
>> You say the git way of doing things is 1 project -> 1 git repository, I 
>> understand, and it's not very far of having a svn repo for every project in 
>> svn altough the release plugin do not enforce this.
> Subversion doesn't enforce this. In fact, Subversion is designed to support a 
> 1 to many relationship between projects and repositories whereas Git is 
> designed for a 1 to 1 relationship. This has nothing to do with Maven.
>> 
>> The current state of the release plugin force you to have the pom.xml at the 
>> root of your  git repository or to say it differently if you have a pom.xml 
>> anywhere else than the root directory you can't release the project. (of 
>> course submodule of root located pom.xml do not count)...
>> 
>> It's also common practice in the maven world to have a parent pom to share 
>> common settings. If I follow blindlessly the 1 project -> 1 git repository, 
>> it means I have to setup a git repository for a single parent pom ?
> A multi-module project should be in a single git repository. An 
> organizational pom should be in its own repository which may, you are 
> correct, result in a repository with a single file in it.
>> I have the feeling, but I maybe wrong, that this is more a limitation of the 
>> release plugin / scm provider more than a design goal.
> No. It's a design goal. See 
> https://git.wiki.kernel.org/index.php/GitSvnComparison#Partial_Checkout.2FUsed_bandwidth
> 
> Justin
> 
>> 
>> Those who migrated to git, what do you do for the above cases, especially 
>> the parent pom one ?
>> 
>> Jean-Laurent
>> 
>> 
>> On Mon, Apr 26, 2010 at 5:37 PM, Justin Edelson > > wrote:
>> 
>>OK. Then we're on the same page...
>> 
>>On 4/26/10 11:32 AM, Kathryn Huxtable wrote:
>>> Perhaps I wasn't clear. I don't support multiple projects in one
>>repository. Definitely not. I was trying to criticize the
>>svn-centric thinking, not support it.
>>>
>>> I think there should be a JIRA issue to make modules work, given
>>that they'll be in separate repositories.
>>>
>>> I'm not going to file this because I have almost zero experience
>>with nested projects. There have been places it would have made
>>sense and I shied away.
>>>
>>> But the release plugin should work with git projects that have
>>modules and it should do it in the standard git manner, which is
>>one repository containing one project. (Distributed, of course.)
>>>
>>> -K
>>>
>>> On Apr 26, 2010, at 9:06 AM, Justin Edelson wrote:
>>>
>>>> Kathryn-
>>>> Maybe I'm misunderstanding what you mean, but I think you have this
>>>> exactly backwards. The "svn-centric thinking" is what's
>>inspired someone
>>>> to put multiple projects in the same repository. AFAIK, this is
>>simply
>>>> not supported by git, i.e. there's no way to clone, branch or
>>tag _part_
>>>> of a repository.
>>>>
>>>> I am by no means a git expert, so I could be mistaken about this.
>>>>
>>>> Justin
>>>>
>>>>
>>>>
>>>> On 4/26/10 9:21 AM, Kathryn Huxtable wrote:
>>>>> Having recently switched from svn to git for most of my
>>projects, I have an opinion.
>>>>>
>>>>> I think you should create a JIRA ticket and consider this a bug.
>>>>>
>>>>> What we're dealing with here is a bit of svn-centric thinking
>>during design. It needs to be fixed.
>>>>>
>>>>> -K
>>>>>
>>>>> On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote:
>>>>>
>> We're considering migrating from svn to git, we stumble on the
>> maven-release-plugin usage with git.
>> We think we prefer to use a single repository for many
>>independently built
>> projects like :
>>
>> foobar-repo.git
>>  |-> project-foo/
>>  ||-> pom.xml
>>  ||–> module A/
>>  ||-> module B/
>>  |
>>  |-> project-bar/
>>   |-> pom.xml
>>
>>
>> project-bar scm url looks like :
>> scm:git:ssh://somehost.nowhere:/foobar-repo.git
>>
>>
>> This hints to the right repository but I can't write that the
>>actual
>> project-bar is in the project-bar subdirectory.
>>
>> mvn release:prepare goes well and ends succesfully.
>>
>> mvn release:perform fails whenever it tries to build the
>>project from the
>> tag. It effectively clone correctly the repository.
>> But use the root of the repository rather

Re: Release plugin & git repo with multiple projects

[Jean-Laurent de Morlhon]

Thanks !

Migration would be a bit stiffer than I thought, but it make sense.

Jean-Laurent


On Mon, Apr 26, 2010 at 10:18 PM, Justin Edelson wrote:

> Jean-Laurent de Morlhon wrote:
>
>> You say the git way of doing things is 1 project -> 1 git repository, I
>> understand, and it's not very far of having a svn repo for every project in
>> svn altough the release plugin do not enforce this.
>>
> Subversion doesn't enforce this. In fact, Subversion is designed to support
> a 1 to many relationship between projects and repositories whereas Git is
> designed for a 1 to 1 relationship. This has nothing to do with Maven.
>
>
>> The current state of the release plugin force you to have the pom.xml at
>> the root of your  git repository or to say it differently if you have a
>> pom.xml anywhere else than the root directory you can't release the project.
>> (of course submodule of root located pom.xml do not count)...
>>
>> It's also common practice in the maven world to have a parent pom to share
>> common settings. If I follow blindlessly the 1 project -> 1 git repository,
>> it means I have to setup a git repository for a single parent pom ?
>>
> A multi-module project should be in a single git repository. An
> organizational pom should be in its own repository which may, you are
> correct, result in a repository with a single file in it.
>
>
>  I have the feeling, but I maybe wrong, that this is more a limitation of
>> the release plugin / scm provider more than a design goal.
>>
> No. It's a design goal. See
> https://git.wiki.kernel.org/index.php/GitSvnComparison#Partial_Checkout.2FUsed_bandwidth
>
> Justin
>
>
>> Those who migrated to git, what do you do for the above cases, especially
>> the parent pom one ?
>>
>> Jean-Laurent
>>
>>
>> On Mon, Apr 26, 2010 at 5:37 PM, Justin Edelson 
>> > justinedel...@gmail.com>> wrote:
>>
>>OK. Then we're on the same page...
>>
>>On 4/26/10 11:32 AM, Kathryn Huxtable wrote:
>>> Perhaps I wasn't clear. I don't support multiple projects in one
>>repository. Definitely not. I was trying to criticize the
>>svn-centric thinking, not support it.
>>>
>>> I think there should be a JIRA issue to make modules work, given
>>that they'll be in separate repositories.
>>>
>>> I'm not going to file this because I have almost zero experience
>>with nested projects. There have been places it would have made
>>sense and I shied away.
>>>
>>> But the release plugin should work with git projects that have
>>modules and it should do it in the standard git manner, which is
>>one repository containing one project. (Distributed, of course.)
>>>
>>> -K
>>>
>>> On Apr 26, 2010, at 9:06 AM, Justin Edelson wrote:
>>>
>>>> Kathryn-
>>>> Maybe I'm misunderstanding what you mean, but I think you have this
>>>> exactly backwards. The "svn-centric thinking" is what's
>>inspired someone
>>>> to put multiple projects in the same repository. AFAIK, this is
>>simply
>>>> not supported by git, i.e. there's no way to clone, branch or
>>tag _part_
>>>> of a repository.
>>>>
>>>> I am by no means a git expert, so I could be mistaken about this.
>>>>
>>>> Justin
>>>>
>>>>
>>>>
>>>> On 4/26/10 9:21 AM, Kathryn Huxtable wrote:
>>>>> Having recently switched from svn to git for most of my
>>projects, I have an opinion.
>>>>>
>>>>> I think you should create a JIRA ticket and consider this a bug.
>>>>>
>>>>> What we're dealing with here is a bit of svn-centric thinking
>>during design. It needs to be fixed.
>>>>>
>>>>> -K
>>>>>
>>>>> On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote:
>>>>>
>> We're considering migrating from svn to git, we stumble on the
>> maven-release-plugin usage with git.
>> We think we prefer to use a single repository for many
>>independently built
>> projects like :
>>
>> foobar-repo.git
>>  |-> project-foo/
>>  ||-> pom.xml
>>  ||–> module A/
>>  ||-> module B/
>>  |
>>  |-> project-bar/
>>   |-> pom.xml
>>
>>
>> project-bar scm url looks like :
>> scm:git:ssh://somehost.nowhere:/foobar-repo.git
>>
>>
>> This hints to the right repository but I can't write that the
>>actual
>> project-bar is in the project-bar subdirectory.
>>
>> mvn release:prepare goes well and ends succesfully.
>>
>> mvn release:perform fails whenever it tries to build the
>>project from the
>> tag. It effectively clone correctly the repository.
>> But use the root of the repository rather than going into
>>project-bar
>> subdirectory whenever it tries to clean deploy the tag.
>>
>> This prevent using git and multiple projects in the same
>>director

Re: Release plugin & git repo with multiple projects

[Justin Edelson]

Jean-Laurent de Morlhon wrote:
You say the git way of doing things is 1 project -> 1 git repository, 
I understand, and it's not very far of having a svn repo for every 
project in svn altough the release plugin do not enforce this.
Subversion doesn't enforce this. In fact, Subversion is designed to 
support a 1 to many relationship between projects and repositories 
whereas Git is designed for a 1 to 1 relationship. This has nothing to 
do with Maven.


The current state of the release plugin force you to have the pom.xml 
at the root of your  git repository or to say it differently if you 
have a pom.xml anywhere else than the root directory you can't release 
the project. (of course submodule of root located pom.xml do not count)...


It's also common practice in the maven world to have a parent pom to 
share common settings. If I follow blindlessly the 1 project -> 1 git 
repository, it means I have to setup a git repository for a single 
parent pom ?
A multi-module project should be in a single git repository. An 
organizational pom should be in its own repository which may, you are 
correct, result in a repository with a single file in it.


I have the feeling, but I maybe wrong, that this is more a limitation 
of the release plugin / scm provider more than a design goal.
No. It's a design goal. See 
https://git.wiki.kernel.org/index.php/GitSvnComparison#Partial_Checkout.2FUsed_bandwidth


Justin



Those who migrated to git, what do you do for the above cases, 
especially the parent pom one ?


Jean-Laurent


On Mon, Apr 26, 2010 at 5:37 PM, Justin Edelson 
mailto:justinedel...@gmail.com>> wrote:


OK. Then we're on the same page...

On 4/26/10 11:32 AM, Kathryn Huxtable wrote:
> Perhaps I wasn't clear. I don't support multiple projects in one
repository. Definitely not. I was trying to criticize the
svn-centric thinking, not support it.
>
> I think there should be a JIRA issue to make modules work, given
that they'll be in separate repositories.
>
> I'm not going to file this because I have almost zero experience
with nested projects. There have been places it would have made
sense and I shied away.
>
> But the release plugin should work with git projects that have
modules and it should do it in the standard git manner, which is
one repository containing one project. (Distributed, of course.)
>
> -K
>
> On Apr 26, 2010, at 9:06 AM, Justin Edelson wrote:
>
>> Kathryn-
>> Maybe I'm misunderstanding what you mean, but I think you have this
>> exactly backwards. The "svn-centric thinking" is what's
inspired someone
>> to put multiple projects in the same repository. AFAIK, this is
simply
>> not supported by git, i.e. there's no way to clone, branch or
tag _part_
>> of a repository.
>>
>> I am by no means a git expert, so I could be mistaken about this.
>>
>> Justin
>>
>>
>>
>> On 4/26/10 9:21 AM, Kathryn Huxtable wrote:
>>> Having recently switched from svn to git for most of my
projects, I have an opinion.
>>>
>>> I think you should create a JIRA ticket and consider this a bug.
>>>
>>> What we're dealing with here is a bit of svn-centric thinking
during design. It needs to be fixed.
>>>
>>> -K
>>>
>>> On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote:
>>>
 We're considering migrating from svn to git, we stumble on the
 maven-release-plugin usage with git.
 We think we prefer to use a single repository for many
independently built
 projects like :

 foobar-repo.git
  |-> project-foo/
  ||-> pom.xml
  ||–> module A/
  ||-> module B/
  |
  |-> project-bar/
   |-> pom.xml


 project-bar scm url looks like :
 scm:git:ssh://somehost.nowhere:/foobar-repo.git


 This hints to the right repository but I can't write that the
actual
 project-bar is in the project-bar subdirectory.

 mvn release:prepare goes well and ends succesfully.

 mvn release:perform fails whenever it tries to build the
project from the
 tag. It effectively clone correctly the repository.
 But use the root of the repository rather than going into
project-bar
 subdirectory whenever it tries to clean deploy the tag.

 This prevent using git and multiple projects in the same
directory.
 Some may think we should use gitmodules but
 1) the release plugin does not support it [1]
 2) gitmodules is an aggregate of single repository

 Should I issue a "new feature" ticket into jira project
MRELEASE or SCM ?
 Or should I fall back to the current convention of 1 project
= 1 git
 repository ??
 Or maybe someo

Re: Release plugin & git repo with multiple projects

[Jean-Laurent de Morlhon]

You say the git way of doing things is 1 project -> 1 git repository, I
understand, and it's not very far of having a svn repo for every project in
svn altough the release plugin do not enforce this.

The current state of the release plugin force you to have the pom.xml at the
root of your  git repository or to say it differently if you have a pom.xml
anywhere else than the root directory you can't release the project. (of
course submodule of root located pom.xml do not count)...

It's also common practice in the maven world to have a parent pom to share
common settings. If I follow blindlessly the 1 project -> 1 git repository,
it means I have to setup a git repository for a single parent pom ?

I have the feeling, but I maybe wrong, that this is more a limitation of the
release plugin / scm provider more than a design goal.

Those who migrated to git, what do you do for the above cases, especially
the parent pom one ?

Jean-Laurent


On Mon, Apr 26, 2010 at 5:37 PM, Justin Edelson wrote:

> OK. Then we're on the same page...
>
> On 4/26/10 11:32 AM, Kathryn Huxtable wrote:
> > Perhaps I wasn't clear. I don't support multiple projects in one
> repository. Definitely not. I was trying to criticize the svn-centric
> thinking, not support it.
> >
> > I think there should be a JIRA issue to make modules work, given that
> they'll be in separate repositories.
> >
> > I'm not going to file this because I have almost zero experience with
> nested projects. There have been places it would have made sense and I shied
> away.
> >
> > But the release plugin should work with git projects that have modules
> and it should do it in the standard git manner, which is one repository
> containing one project. (Distributed, of course.)
> >
> > -K
> >
> > On Apr 26, 2010, at 9:06 AM, Justin Edelson wrote:
> >
> >> Kathryn-
> >> Maybe I'm misunderstanding what you mean, but I think you have this
> >> exactly backwards. The "svn-centric thinking" is what's inspired someone
> >> to put multiple projects in the same repository. AFAIK, this is simply
> >> not supported by git, i.e. there's no way to clone, branch or tag _part_
> >> of a repository.
> >>
> >> I am by no means a git expert, so I could be mistaken about this.
> >>
> >> Justin
> >>
> >>
> >>
> >> On 4/26/10 9:21 AM, Kathryn Huxtable wrote:
> >>> Having recently switched from svn to git for most of my projects, I
> have an opinion.
> >>>
> >>> I think you should create a JIRA ticket and consider this a bug.
> >>>
> >>> What we're dealing with here is a bit of svn-centric thinking during
> design. It needs to be fixed.
> >>>
> >>> -K
> >>>
> >>> On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote:
> >>>
>  We're considering migrating from svn to git, we stumble on the
>  maven-release-plugin usage with git.
>  We think we prefer to use a single repository for many independently
> built
>  projects like :
> 
>  foobar-repo.git
>   |-> project-foo/
>   ||-> pom.xml
>   ||–> module A/
>   ||-> module B/
>   |
>   |-> project-bar/
>    |-> pom.xml
> 
> 
>  project-bar scm url looks like :
>  scm:git:ssh://somehost.nowhere:/foobar-repo.git
> 
> 
>  This hints to the right repository but I can't write that the actual
>  project-bar is in the project-bar subdirectory.
> 
>  mvn release:prepare goes well and ends succesfully.
> 
>  mvn release:perform fails whenever it tries to build the project from
> the
>  tag. It effectively clone correctly the repository.
>  But use the root of the repository rather than going into project-bar
>  subdirectory whenever it tries to clean deploy the tag.
> 
>  This prevent using git and multiple projects in the same directory.
>  Some may think we should use gitmodules but
>  1) the release plugin does not support it [1]
>  2) gitmodules is an aggregate of single repository
> 
>  Should I issue a "new feature" ticket into jira project MRELEASE or
> SCM ?
>  Or should I fall back to the current convention of 1 project = 1 git
>  repository ??
>  Or maybe someone managed to do it ?
> 
>  any advice appreciated.
> 
>  [1] : http://jira.codehaus.org/browse/SCM-530
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >>> For additional commands, e-mail: users-h...@maven.apache.org
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
>
>
> --

Re: provided depedencies and Maven best practices ...

[Justin Edelson]

provided-scoped dependencies aren't transitive. As a result, there's no 
reason to put them in the "our-dependencies" pom.


Kedar Mhaswade wrote:

The Maven books at sonatype.org suggest that while employing Maven to do
multi module builds, it is better to carefully segregate your dependencies
in a separate module whose packaging type is pom and then depend on this
module with pom.

I followed that advice and now I have the following:


  mygroup
  our-dependencies
  ${project.version}
  pom


declared in my web-app's pom.xml. The idea being all the dependencies there
are depended on by this web-app module.  One of the dependencies declared at
this common place (our-dependencies) is the servlet-api which should be
declared a "provided" dependency:


  javax.servlet
  servlet-api
  2.5
  provided

 
The trouble is that with this dependency, my web-app fails to compile since

it can't find the servlet-api classes and interfaces. The only work-around
is that in my web-app, the servlet-api dependency has to be re-declared.

Is this a bug or a feature? Alternatively, is the best practice in such
cases to explicitly declare "provided" dependencies where they are actually
needed rather than grouping them as "our-dependencies"?

Thank you, in advance.
  



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

provided depedencies and Maven best practices ...

[Kedar Mhaswade]

The Maven books at sonatype.org suggest that while employing Maven to do
multi module builds, it is better to carefully segregate your dependencies
in a separate module whose packaging type is pom and then depend on this
module with pom.

I followed that advice and now I have the following:


  mygroup
  our-dependencies
  ${project.version}
  pom


declared in my web-app's pom.xml. The idea being all the dependencies there
are depended on by this web-app module.  One of the dependencies declared at
this common place (our-dependencies) is the servlet-api which should be
declared a "provided" dependency:


  javax.servlet
  servlet-api
  2.5
  provided

 
The trouble is that with this dependency, my web-app fails to compile since
it can't find the servlet-api classes and interfaces. The only work-around
is that in my web-app, the servlet-api dependency has to be re-declared.

Is this a bug or a feature? Alternatively, is the best practice in such
cases to explicitly declare "provided" dependencies where they are actually
needed rather than grouping them as "our-dependencies"?

Thank you, in advance.
-- 
View this message in context: 
http://maven-users.828.n2.nabble.com/provided-depedencies-and-Maven-best-practices-tp4964099p4964099.html
Sent from the maven users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Force Maven to use my newer version of Jaxb instead of the one from Java 6?

[Wayne Fay]

> How can force Maven to use my newer version of Jaxb instead of the one from
> Java 6?

This is not a Maven problem per-se. You can find ways to deal with this here:
https://jaxb.dev.java.net/guide/Migrating_JAXB_2_0_applications_to_JavaSE_6.html

The easiest approach is using the endorsed directory mechanism but
realize this means you need to deploy jars to all JDKs/JREs in your
environments.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RES: maven-dependency-plugin: Question about copy-dependencies goal

[Luciano Mantuaneli]

Hi, Karl. Thanks for answering!

>Have you thought about linking the plugin to the package phase for >example
>
>and did you tried that on command line ?

I wish I could, but it's not possible due to restrictions on the specification 
of this job. It's imperative that the "magic" happens while using Eclipse and 
it must be at the moment that he builds (just compile) the project.

I know that this is pretty dumb and this is not the correct way to proceed, but 
I don't have the permission to change those restrictions...

If you need, I'll gladly explain more about this bizarre task I have to 
manage... I really enjoy making people laugh! 

Luciano Mantuaneli 
TI Melhorias - Suporte a Canais
 
CPM Braxis
Cel: 55 11 8399 0319
Tel: 55 11 4196 4622
www.cpm.com.br
www.cpminternational.com
www.braxis.com.br
-Mensagem original-
De: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] 
Enviada em: segunda-feira, 26 de abril de 2010 12:16
Para: Maven Users List; users@maven.apache.org
Assunto: Re: maven-dependency-plugin: Question about copy-dependencies goal

Hi,


> 
> 
> process-resources
Have you thought about linking the plugin to the package phase for example

and did you tried that on command line ?

Kind regards
Karl Heinz Marbaise
-- 
MfG
Karl Heinz Marbaise
-- 
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen   http://www.soebes.de


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Why the error with settings.xml when building using m2eclipse?

[Wayne Fay]

> Is it a bug in m2Eclipse, or did I miss a step in m2eclipse setup?
> I can successfully build from the command line even without this file

M2eclipse questions belong on the m2eclipse user list:
http://m2eclipse.sonatype.org/project-information.html

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Unclear about maven web app directory structure

[Wayne Fay]

> However, I do have one follow-up question. It seems that in the
> case of webapps/web services it make sense to use maven (sub)modules,
> to that end how many (sub)modules should one use? Is there a
> recommended/best practice? For example does the following set of
> (sub)modules make sense?

If this makes sense to you right now, then just use it, and plan for
refactoring if/when needed in the future which may mean more or fewer
modules. The "cost" of adding a new module in Maven is exceptionally
low.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Dependency Management +

[Nick Stolwijk]

To enforce that all plugins are versioned use the enforcer plugin [1]
with the rule requirePluginVersions [2].

For the dependencymanagement enforcement take a look at the Maven
Dependency Plugin [3] with the goals analyze-only [4] and
anaylyze-dep-mgt [5].

[1] http://maven.apache.org/plugins/maven-enforcer-plugin/
[2] http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html
[3] http://maven.apache.org/plugins/maven-dependency-plugin/
[4] 
http://maven.apache.org/plugins/maven-dependency-plugin/analyze-only-mojo.html
[5] 
http://maven.apache.org/plugins/maven-dependency-plugin/analyze-dep-mgt-mojo.html

Hth,

Nick Stolwijk
~Java Developer~

IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl



On Mon, Apr 26, 2010 at 5:59 PM, solo1970
 wrote:
>
> Hello,
>
> For my project, I need to identify plugins/dependencies that don't have
> explicit versions specified (i.e. that would use the latest version)
>
> Also, I would need a plugin to fail my build if the aggregated modules don't
> use the same version of inter-project dependencies. (would check for project
> dependency inconsistency)
>
> Any ideas?
>
> Sonia
> --
> View this message in context: 
> http://old.nabble.com/Dependency-Management-%2B-tp28366761p28366761.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Dependency Management +

[solo1970]

Hello,

For my project, I need to identify plugins/dependencies that don't have
explicit versions specified (i.e. that would use the latest version)

Also, I would need a plugin to fail my build if the aggregated modules don't
use the same version of inter-project dependencies. (would check for project
dependency inconsistency)

Any ideas?

Sonia 
-- 
View this message in context: 
http://old.nabble.com/Dependency-Management-%2B-tp28366761p28366761.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Unclear about maven web app directory structure

[Dan King]

>> The java folder is for your java source code, while the webapp folder is for
>> your web application source files such as jsp files. Create a jar project
>> through the quickstart archetype to get an example of the former and the
>> webapp archetype shows the latter.
>
>> /Anders

>Exactly, you have to see the source/main/<... structure as structure by 
>type. A Servlet is mostly coded in java, so it is a java file,
>if you code it in groovy it would go into src/main/groovy

@Anders, @Wayne, @Werner: thanks for the clarifications, they fully answered my 
immediate queries.

However, I do have one follow-up question. It seems that in the case of 
webapps/web services it make sense to use maven (sub)modules, to that end how 
many (sub)modules should one use? Is there a recommended/best practice? For 
example does the following set of (sub)modules make sense?

web-service/ <-- directory that contains parent POM
| models/ (maven sub-module for entities)
| persistence/ (maven sub-module for DAOs)
| service/ (maven sub-module for web service logic)
| webapp/ (maven sub-module for the web app)


  

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Defining ejb-jar.xml for ejb 3.0 via pom

[Wayne Fay]

> Can anyone help me and tell me what parameter to use in my pom file in
> order to specify the location of the ejb-jar.xml file so that it will be
> packed in my ejb file?

Google "maven ejb xml" gives me:
http://stackoverflow.com/questions/1716567/how-do-i-change-the-location-of-ejb-jar-xml-in-my-maven-project

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Release plugin & git repo with multiple projects

[Justin Edelson]

OK. Then we're on the same page...

On 4/26/10 11:32 AM, Kathryn Huxtable wrote:
> Perhaps I wasn't clear. I don't support multiple projects in one repository. 
> Definitely not. I was trying to criticize the svn-centric thinking, not 
> support it.
> 
> I think there should be a JIRA issue to make modules work, given that they'll 
> be in separate repositories.
> 
> I'm not going to file this because I have almost zero experience with nested 
> projects. There have been places it would have made sense and I shied away.
> 
> But the release plugin should work with git projects that have modules and it 
> should do it in the standard git manner, which is one repository containing 
> one project. (Distributed, of course.)
> 
> -K
> 
> On Apr 26, 2010, at 9:06 AM, Justin Edelson wrote:
> 
>> Kathryn-
>> Maybe I'm misunderstanding what you mean, but I think you have this
>> exactly backwards. The "svn-centric thinking" is what's inspired someone
>> to put multiple projects in the same repository. AFAIK, this is simply
>> not supported by git, i.e. there's no way to clone, branch or tag _part_
>> of a repository.
>>
>> I am by no means a git expert, so I could be mistaken about this.
>>
>> Justin
>>
>>
>>
>> On 4/26/10 9:21 AM, Kathryn Huxtable wrote:
>>> Having recently switched from svn to git for most of my projects, I have an 
>>> opinion.
>>>
>>> I think you should create a JIRA ticket and consider this a bug.
>>>
>>> What we're dealing with here is a bit of svn-centric thinking during 
>>> design. It needs to be fixed.
>>>
>>> -K
>>>
>>> On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote:
>>>
 We're considering migrating from svn to git, we stumble on the
 maven-release-plugin usage with git.
 We think we prefer to use a single repository for many independently built
 projects like :

 foobar-repo.git
  |-> project-foo/
  ||-> pom.xml
  ||–> module A/
  ||-> module B/
  |
  |-> project-bar/
   |-> pom.xml


 project-bar scm url looks like :
 scm:git:ssh://somehost.nowhere:/foobar-repo.git 

 This hints to the right repository but I can't write that the actual
 project-bar is in the project-bar subdirectory.

 mvn release:prepare goes well and ends succesfully.

 mvn release:perform fails whenever it tries to build the project from the
 tag. It effectively clone correctly the repository.
 But use the root of the repository rather than going into project-bar
 subdirectory whenever it tries to clean deploy the tag.

 This prevent using git and multiple projects in the same directory.
 Some may think we should use gitmodules but
 1) the release plugin does not support it [1]
 2) gitmodules is an aggregate of single repository

 Should I issue a "new feature" ticket into jira project MRELEASE or SCM ?
 Or should I fall back to the current convention of 1 project = 1 git
 repository ??
 Or maybe someone managed to do it ?

 any advice appreciated.

 [1] : http://jira.codehaus.org/browse/SCM-530
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Release plugin & git repo with multiple projects

[Kathryn Huxtable]

Perhaps I wasn't clear. I don't support multiple projects in one repository. 
Definitely not. I was trying to criticize the svn-centric thinking, not support 
it.

I think there should be a JIRA issue to make modules work, given that they'll 
be in separate repositories.

I'm not going to file this because I have almost zero experience with nested 
projects. There have been places it would have made sense and I shied away.

But the release plugin should work with git projects that have modules and it 
should do it in the standard git manner, which is one repository containing one 
project. (Distributed, of course.)

-K

On Apr 26, 2010, at 9:06 AM, Justin Edelson wrote:

> Kathryn-
> Maybe I'm misunderstanding what you mean, but I think you have this
> exactly backwards. The "svn-centric thinking" is what's inspired someone
> to put multiple projects in the same repository. AFAIK, this is simply
> not supported by git, i.e. there's no way to clone, branch or tag _part_
> of a repository.
> 
> I am by no means a git expert, so I could be mistaken about this.
> 
> Justin
> 
> 
> 
> On 4/26/10 9:21 AM, Kathryn Huxtable wrote:
>> Having recently switched from svn to git for most of my projects, I have an 
>> opinion.
>> 
>> I think you should create a JIRA ticket and consider this a bug.
>> 
>> What we're dealing with here is a bit of svn-centric thinking during design. 
>> It needs to be fixed.
>> 
>> -K
>> 
>> On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote:
>> 
>>> We're considering migrating from svn to git, we stumble on the
>>> maven-release-plugin usage with git.
>>> We think we prefer to use a single repository for many independently built
>>> projects like :
>>> 
>>> foobar-repo.git
>>>  |-> project-foo/
>>>  ||-> pom.xml
>>>  ||–> module A/
>>>  ||-> module B/
>>>  |
>>>  |-> project-bar/
>>>   |-> pom.xml
>>> 
>>> 
>>> project-bar scm url looks like :
>>> scm:git:ssh://somehost.nowhere:/foobar-repo.git 
>>> 
>>> This hints to the right repository but I can't write that the actual
>>> project-bar is in the project-bar subdirectory.
>>> 
>>> mvn release:prepare goes well and ends succesfully.
>>> 
>>> mvn release:perform fails whenever it tries to build the project from the
>>> tag. It effectively clone correctly the repository.
>>> But use the root of the repository rather than going into project-bar
>>> subdirectory whenever it tries to clean deploy the tag.
>>> 
>>> This prevent using git and multiple projects in the same directory.
>>> Some may think we should use gitmodules but
>>> 1) the release plugin does not support it [1]
>>> 2) gitmodules is an aggregate of single repository
>>> 
>>> Should I issue a "new feature" ticket into jira project MRELEASE or SCM ?
>>> Or should I fall back to the current convention of 1 project = 1 git
>>> repository ??
>>> Or maybe someone managed to do it ?
>>> 
>>> any advice appreciated.
>>> 
>>> [1] : http://jira.codehaus.org/browse/SCM-530
>> 
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Defining ejb-jar.xml for ejb 3.0 via pom

[Weichselbaumer Michael (MWE 4170)]

Hello!
 
I am using the maven-ejb-plugin (2.2.1) and I want to create an version
3.0 ejb without client.
I want to provide an ejb-jar.xml (weblogic-ejb-jar.xml to be more
precise) along with my ejb file.
 
When trying to create a version 2.x ejb, I am forced to provide an
ejb-jar.xml -> when doing so with 3.0 i am not.
 
When looking at the documentation @
http://maven.apache.org/plugins/maven-ejb-plugin/ejb-mojo.html i cannot
find
a paramter for specifying the deployment descriptor.
The error message provided by the plugin when trying to create a version
2.x ejb doesn't tell me how to pass it.
 
So now i am failing to create a version 2.x ejb because of the missing
parameter and suceeding in creating a version 3.0 ejb without the
descriptor,
which makes it useless to me.
 
Can anyone help me and tell me what parameter to use in my pom file in
order to specify the location of the ejb-jar.xml file so that it will be
packed in my ejb file?

Re: maven-dependency-plugin: Question about copy-dependencies goal

[Karl Heinz Marbaise]

Hi,


> 
> 
> process-resources
Have you thought about linking the plugin to the package phase for example

and did you tried that on command line ?

Kind regards
Karl Heinz Marbaise
-- 
MfG
Karl Heinz Marbaise
-- 
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen   http://www.soebes.de


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: missing

[Wayne Fay]

> javax.faces:jsf-api:jar:1.2_12:compile
> javax.faces:jsf-impl:jar:1.2_12:compile
> 4/23/10 4:55:53 PM IST: Missing artifact el-impl:el-impl:jar:1.0:provided
> org.richfaces.framework:richfaces-api:jar:3.3.3-SNAPSHOT:compile
> org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT:compile
> org.richfaces.ui:richfaces-ui:jar:3.3.3-SNAPSHOT:compile
> org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT:provided

It seems you are missing a  declaration in your settings.xml file.

SNAPSHOTs are not hosted in Central. And the latest jsf-api and -impl
versions in Central is 1.2_02.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: missing

[Wayne Fay]

> javax.faces:jsf-api:jar:1.2_12:compile
> javax.faces:jsf-impl:jar:1.2_12:compile
> 4/23/10 4:55:53 PM IST: Missing artifact el-impl:el-impl:jar:1.0:provided
> org.richfaces.framework:richfaces-api:jar:3.3.3-SNAPSHOT:compile
> org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT:compile
> org.richfaces.ui:richfaces-ui:jar:3.3.3-SNAPSHOT:compile
> org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT:provided

It seems you are missing a  declaration in your settings.xml file.

SNAPSHOTs are not hosted in Central. And the latest jsf-api and -impl
versions in Central is 1.2_02.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

maven-dependency-plugin: Question about copy-dependencies goal

[Luciano Mantuaneli]

Greetings.

 

I have a very specific need in a java project in Eclipse: The jars which
the project depends on must be copied to an external folder.

 

The maven-dependency-plugin and its copy-dependencies goal come to mind
immediately.

 

As a test, I wrote the following pom.xml:

 

-



...



...



   ...

   

 
org.apache.maven.plugins

 
maven-dependency-plugin

   

   

 
copy-dependencies

 
process-resources

 


 
copy-dependencies

 


 


 
${my.external.location}/alterloc

 
servlet-api

 


   

   

   







-

 

However, the above pom shows some bogus behavior, depending on the user
action:

1)Right-clicking the project and selecting "Maven >
Update Project Configuration": The folder "alterloc" is created in
"my.external.location", and the jars, but servlet-api, are copied to it
- Just as expected.

2)Compiling the project: The folder "dependency" is
created in "project.build.directory", and the jars, including
servlet-api, are copied to it - Not expected, once the configurations
seems to be ignored

 

I already tried to change the phase to "compile", to "process-classes",
but in that case it's even worst: The dependencies wasn't copied at all.

 

What am I doing wrong?

 

Thanks in advance

 

 

Luciano Mantuaneli    

 

TI Melhorias - Suporte a Canais

 

CPM Braxis

Cel: 55 11 8399 0319

Tel: 55 11 4196 4622

www.cpm.com.br  

www.cpminternational.com  

www.braxis.com.br  

 

Re: Release plugin & git repo with multiple projects

[Justin Edelson]

Kathryn-
Maybe I'm misunderstanding what you mean, but I think you have this
exactly backwards. The "svn-centric thinking" is what's inspired someone
to put multiple projects in the same repository. AFAIK, this is simply
not supported by git, i.e. there's no way to clone, branch or tag _part_
of a repository.

I am by no means a git expert, so I could be mistaken about this.

Justin



On 4/26/10 9:21 AM, Kathryn Huxtable wrote:
> Having recently switched from svn to git for most of my projects, I have an 
> opinion.
> 
> I think you should create a JIRA ticket and consider this a bug.
> 
> What we're dealing with here is a bit of svn-centric thinking during design. 
> It needs to be fixed.
> 
> -K
> 
> On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote:
> 
>> We're considering migrating from svn to git, we stumble on the
>> maven-release-plugin usage with git.
>> We think we prefer to use a single repository for many independently built
>> projects like :
>>
>> foobar-repo.git
>>   |-> project-foo/
>>   ||-> pom.xml
>>   ||–> module A/
>>   ||-> module B/
>>   |
>>   |-> project-bar/
>>|-> pom.xml
>>
>>
>> project-bar scm url looks like :
>> scm:git:ssh://somehost.nowhere:/foobar-repo.git 
>>
>> This hints to the right repository but I can't write that the actual
>> project-bar is in the project-bar subdirectory.
>>
>> mvn release:prepare goes well and ends succesfully.
>>
>> mvn release:perform fails whenever it tries to build the project from the
>> tag. It effectively clone correctly the repository.
>> But use the root of the repository rather than going into project-bar
>> subdirectory whenever it tries to clean deploy the tag.
>>
>> This prevent using git and multiple projects in the same directory.
>> Some may think we should use gitmodules but
>> 1) the release plugin does not support it [1]
>> 2) gitmodules is an aggregate of single repository
>>
>> Should I issue a "new feature" ticket into jira project MRELEASE or SCM ?
>> Or should I fall back to the current convention of 1 project = 1 git
>> repository ??
>> Or maybe someone managed to do it ?
>>
>> any advice appreciated.
>>
>> [1] : http://jira.codehaus.org/browse/SCM-530
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven inheritance for multiple build executions

[Tim O'Brien]

On Mon, Apr 26, 2010 at 8:39 AM, Marshall Schor  wrote:
> My use case:
>
> I'm running the maven docbkx plugin to produce both pdf and html outputs
> from multiple docbook sources.
>
> The docbkx plugin says to use two executions (with ids, for instance, of
> "html" and "pdf", one for each of the outputs).
>
> I would like to reuse this setup 4 times in my builds, because I have 4
> "books" to process in this project.
>
> I'm trying to factor out common configuration for these, into a
> pluginManagement element, having 2 configurations with those ids of
> "html" and "pdf".
>
> I understand that the configuration merging is done by matching "ids".
> My trouble is that when I now try to write my 8 executions (2 per book),
> I have to write 8 unique "ids", which can't match up with the 2 ids in
> the pluginManagement.
>
> Is there a maven best practice for how to factor this?
>
> I know the one "solution" of splitting up the 4 docbooks into 4 separate
> projects, but I'm looking for another solution since I would rather not
> split these up.
>

One solution would be to separate content from rendering.   I have
books that need to be packaged into a different formats.   Each book
is rendered as a PDF, HTML, and as an eclipse book.   In addition to
these formats, a book may need to be rendered in a reduced format for
a special print, and each book needs to be published to Scribd, Lulu,
etc.

I reached a point with docbkx where I was frustrated with having to
deal with a massively customized lifecycle in one central "book"
project.Instead of dealing with 8 executions, I have a content
project that installs docbook source as a JAR in the local repo.
Other projects in the multimodule project then declare the source as a
dependency and process the docbook accordingly.   See here:
http://github.com/sonatype/nexus-book/

While it is substantially more complex than what you are doing, you
might find that the separation allows you to avoid having to define 8
plugin execution ids.   Or, you might be able to fiddle around with
project hierarchy once you've moved away from the "massive, monolithic
docbkx project" approach.

> -Marshall
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

maven inheritance for multiple build executions

[Marshall Schor]

My use case:

I'm running the maven docbkx plugin to produce both pdf and html outputs
from multiple docbook sources.

The docbkx plugin says to use two executions (with ids, for instance, of
"html" and "pdf", one for each of the outputs).

I would like to reuse this setup 4 times in my builds, because I have 4
"books" to process in this project.

I'm trying to factor out common configuration for these, into a
pluginManagement element, having 2 configurations with those ids of
"html" and "pdf".

I understand that the configuration merging is done by matching "ids". 
My trouble is that when I now try to write my 8 executions (2 per book),
I have to write 8 unique "ids", which can't match up with the 2 ids in
the pluginManagement.

Is there a maven best practice for how to factor this? 

I know the one "solution" of splitting up the 4 docbooks into 4 separate
projects, but I'm looking for another solution since I would rather not
split these up.

-Marshall

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: About Maven 3.0 beta plugin

[Baptiste MATHUS]

Hi,

See this presentation:
http://www.sonatype.com/people/2009/04/jason-van-zyl-on-the-future-of-maven-maven-3/


Cheers

2010/4/26 

> Hi,
>
> We are using Maven 2.1 in our project. Recently Maven 3.0 beta plugin
> has been released. How long Maven 2.1 is supported and if Maven 3.0 is
> released how much does it impact the existing maven project structures
> and other things ?
>
> Regards,
> LeelaRam
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments to
> this message are intended for the exclusive use of the addressee(s) and may
> contain proprietary, confidential or privileged information. If you are not
> the intended recipient, you should not disseminate, distribute or copy this
> e-mail. Please notify the sender immediately and destroy all copies of this
> message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses. The
> company accepts no liability for any damage caused by any virus transmitted
> by this email.
>
> www.wipro.com
>



-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

Re: About Maven 3.0 beta plugin

[nicolas de loof]

Maven 3 is expected to replace Maven 2.1 with no changes.

You can use maven 2.x and we will still support it. Until your build uses
fixed plugin versions you will not get "polluted" by new Maven artifacts.

Anyway, you're encouraged to TEST your build with Maven 3 (beta) to detect
potential issues, and help improving compatibility, but we expect few of
them. It comes with many improvements and more rigourous POM format, that
can help detect misused

Nicolas.

2010/4/26 

> Hi,
>
> We are using Maven 2.1 in our project. Recently Maven 3.0 beta plugin
> has been released. How long Maven 2.1 is supported and if Maven 3.0 is
> released how much does it impact the existing maven project structures
> and other things ?
>
> Regards,
> LeelaRam
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments to
> this message are intended for the exclusive use of the addressee(s) and may
> contain proprietary, confidential or privileged information. If you are not
> the intended recipient, you should not disseminate, distribute or copy this
> e-mail. Please notify the sender immediately and destroy all copies of this
> message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses. The
> company accepts no liability for any damage caused by any virus transmitted
> by this email.
>
> www.wipro.com
>

Re: Release plugin & git repo with multiple projects

[Kathryn Huxtable]

Having recently switched from svn to git for most of my projects, I have an 
opinion.

I think you should create a JIRA ticket and consider this a bug.

What we're dealing with here is a bit of svn-centric thinking during design. It 
needs to be fixed.

-K

On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote:

> We're considering migrating from svn to git, we stumble on the
> maven-release-plugin usage with git.
> We think we prefer to use a single repository for many independently built
> projects like :
> 
> foobar-repo.git
>   |-> project-foo/
>   ||-> pom.xml
>   ||–> module A/
>   ||-> module B/
>   |
>   |-> project-bar/
>|-> pom.xml
> 
> 
> project-bar scm url looks like :
> scm:git:ssh://somehost.nowhere:/foobar-repo.git 
> 
> This hints to the right repository but I can't write that the actual
> project-bar is in the project-bar subdirectory.
> 
> mvn release:prepare goes well and ends succesfully.
> 
> mvn release:perform fails whenever it tries to build the project from the
> tag. It effectively clone correctly the repository.
> But use the root of the repository rather than going into project-bar
> subdirectory whenever it tries to clean deploy the tag.
> 
> This prevent using git and multiple projects in the same directory.
> Some may think we should use gitmodules but
> 1) the release plugin does not support it [1]
> 2) gitmodules is an aggregate of single repository
> 
> Should I issue a "new feature" ticket into jira project MRELEASE or SCM ?
> Or should I fall back to the current convention of 1 project = 1 git
> repository ??
> Or maybe someone managed to do it ?
> 
> any advice appreciated.
> 
> [1] : http://jira.codehaus.org/browse/SCM-530


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

About Maven 3.0 beta plugin

[leelaram.tenneti]

Hi,

We are using Maven 2.1 in our project. Recently Maven 3.0 beta plugin
has been released. How long Maven 2.1 is supported and if Maven 3.0 is
released how much does it impact the existing maven project structures
and other things ?

Regards,
LeelaRam

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email. 

www.wipro.com

Release plugin & git repo with multiple projects

[Jean-Laurent de Morlhon]

We're considering migrating from svn to git, we stumble on the
maven-release-plugin usage with git.
We think we prefer to use a single repository for many independently built
projects like :

foobar-repo.git
   |-> project-foo/
   ||-> pom.xml
   ||–> module A/
   ||-> module B/
   |
   |-> project-bar/
|-> pom.xml


project-bar scm url looks like :
scm:git:ssh://somehost.nowhere:/foobar-repo.git 

This hints to the right repository but I can't write that the actual
project-bar is in the project-bar subdirectory.

mvn release:prepare goes well and ends succesfully.

mvn release:perform fails whenever it tries to build the project from the
tag. It effectively clone correctly the repository.
But use the root of the repository rather than going into project-bar
subdirectory whenever it tries to clean deploy the tag.

This prevent using git and multiple projects in the same directory.
Some may think we should use gitmodules but
1) the release plugin does not support it [1]
2) gitmodules is an aggregate of single repository

Should I issue a "new feature" ticket into jira project MRELEASE or SCM ?
Or should I fall back to the current convention of 1 project = 1 git
repository ??
Or maybe someone managed to do it ?

any advice appreciated.

[1] : http://jira.codehaus.org/browse/SCM-530

Why the error with settings.xml when building using m2eclipse?

[Binod Pant]

I tried m2eclipse for the first time. I got Eclipse running fine with the 
plugin, but when I tried to build a project using Maven, I got the error

"The specified  user settings  file does  not exist: 
myuserfolder/.m2/settings.xml"

I manually created a settings.xml file, and got rid of the problem, as per 
http://www.inexas.org/Wiki.jsp?page=Eclipse%20setup

Is it a bug in m2Eclipse, or did I miss a step in m2eclipse setup? I can 
successfully build from the command line even without this file

Re: Maven project organization

[Francis Lalonde]

Stephan, I'm not sure I understand what you want to do... How  many war 
files do you want to build? How many jar files? What are the 
dependencies between the projects? When you speak of source files, is 
that java? Maybe one or two ascii graphs would help.


Some rules of thumb (for me) are :
1-you should have (at least) as many packaging "war" projects as you 
want warfiles

2- use should have as many packaging "jar" projects as you want jarfiles
3- build the jars first, then the wars
3- the root project is of packaging "pom" should contain a  
list and shared properties/dependencies

4- all projects inherit from the root using 
5- only the parent declares a version

My folders look a bit like that :

- root
- jars
-jar1
-jar2
-wars
-war1
-war2

If you have stuff that is shared between multiple wars, you can put it 
in a separate war that the others derive from (i think this is called 
war overloading)


Francis

On 23/04/2010 3:32 AM, "Näcker, Stephan (UIT)" wrote:

Hey,

I 'm thinking about the appropriate project structure for a coming multi module 
web application project. I would like to have it separated something like that:

root-application
webapp
module1-web
module1
module2-web
module2

The root-application is the root-project (Surprise!!!), the webapp contains any 
web application wide source files, like the web.xml for example. Most of the 
source files are contained by the module projects. Any module has a web-project 
and the module project itself. Now I would like to have the webapp source files 
of the modules' web projects copied into the single destination WAR.

Is there something like a "best practice"? What kind of packaging do I have to 
choose for the module-web projects?

Thanks,
Stephan


   



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: passing parameters to plugin Archetype

[slew77]

Thanks Martin.  I've looked through all 3 parts, but can't find any details
on passing custom paramters to the archetype.

E.g. in my generated code if I want to be able to substitute ${myProperty},
I can't figure out how to supply this to Maven via the command line, e.g:

mvn archetype:generate -DarchetypeGroupId=%ARCHETYPE_GROUPID%
-DarchetypeArtifactId=%ARCHETYPE_ARTIFACTID%
-DarchetypeVersion=%ARCHETYPE_VERSION% -DgroupId=%GROUPID%
-DartifactId=%MODULE_PREFIX%%MODULE_NAME%
-Dpackage=%PACKAGE_PREFIX%%MODULE_NAME_PACKAGE% -Dversion=%VERSION%
-DmyProperty=test

However, if I use M2Eclipse there is a section for specifying the archetype
parameters including a list of custom name/value parameters.  If I use this
section to specify, e.g. myProperty=test then the project is generated with
this value correctly substituted.

Thanks again,
Steve.



matinh wrote:
> 
> Did you have a look at 
> http://blogs.mikeci.com/2010/01/14/working-with-custom-maven-archetypes-part-1/
> and
> http://blogs.mikeci.com/2010/01/26/working-with-custom-maven-archetypes-part-2/
> and its references!
> 
> hth,
> - martin
> 
> Am Montag, 26. April 2010 10:44:29 schrieb slew77:
>> Anyone have any idea on this?  It's really frustrating me :confused:
>>
>> Thanks,
>> Steve.
>>
>> slew77 wrote:
>> > I'm trying to do the same thing - can someone post instructions, I've
>> > searched everywhere.  I can see it's possible as when I use m2eclipse
>> it
>> > allows me to specify custom properties that are picked up, I just can't
>> > figure out how to do it from the command line.
>> >
>> > Thanks,
>> > Steve.
>> >
>> > iiggzz wrote:
>> >> I found it out! So if anybody has the same problem go ahead and ask
>> me.
>> >> Now I have another problem. I need to specify the path to my files
>> like
>> >> this: ${projectName}-mymodule/myfile.txt so after creation it should
>> >> look like this: helloworld-mymodule.
> 
>  
> 

-- 
View this message in context: 
http://old.nabble.com/passing-parameters-to-plugin-Archetype-tp16807963p28363473.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: passing parameters to plugin Archetype

[Martin Höller]

Did you have a look at 
http://blogs.mikeci.com/2010/01/14/working-with-custom-maven-archetypes-part-1/
and
http://blogs.mikeci.com/2010/01/26/working-with-custom-maven-archetypes-part-2/
and its references!

hth,
- martin

Am Montag, 26. April 2010 10:44:29 schrieb slew77:
> Anyone have any idea on this?  It's really frustrating me :confused:
>
> Thanks,
> Steve.
>
> slew77 wrote:
> > I'm trying to do the same thing - can someone post instructions, I've
> > searched everywhere.  I can see it's possible as when I use m2eclipse it
> > allows me to specify custom properties that are picked up, I just can't
> > figure out how to do it from the command line.
> >
> > Thanks,
> > Steve.
> >
> > iiggzz wrote:
> >> I found it out! So if anybody has the same problem go ahead and ask me.
> >> Now I have another problem. I need to specify the path to my files like
> >> this: ${projectName}-mymodule/myfile.txt so after creation it should
> >> look like this: helloworld-mymodule.


signature.asc
Description: This is a digitally signed message part.

missing

[pankjajain15]

while creating a maven project in eclipse, it creates project successfully
but showing following errors after building a project

4/23/10 4:55:53 PM IST: Missing artifact
javax.faces:jsf-api:jar:1.2_12:compile
4/23/10 4:55:53 PM IST: Missing artifact
javax.faces:jsf-impl:jar:1.2_12:compile
4/23/10 4:55:53 PM IST: Missing artifact el-impl:el-impl:jar:1.0:provided
4/23/10 4:55:53 PM IST: Missing artifact
org.richfaces.framework:richfaces-api:jar:3.3.3-SNAPSHOT:compile
4/23/10 4:55:53 PM IST: Missing artifact
org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT:compile
4/23/10 4:55:53 PM IST: Missing artifact
org.richfaces.ui:richfaces-ui:jar:3.3.3-SNAPSHOT:compile
4/23/10 4:55:53 PM IST: Missing artifact
org.richfaces.ui:richfaces-ui:jar:3.3.3-SNAPSHOT:compile
4/23/10 4:55:53 PM IST: Missing artifact
org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT:provided


please help me out 
-- 
View this message in context: 
http://old.nabble.com/missing-tp28363089p28363089.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Could we configure mapper in maven-resources-plugin?

[Arnaud bourree]

2010/4/23 Arnaud bourree:
> Hello
>
> Could we configure mapper in maven-resources-plugin?
>
> I try without success the following:
> 
>   maven-resources-plugin
>   2.4.2
>   
>      
>         copy-with-mapper
>         pre-integration-test
>         
>            ${project.build.directory}
>               
>                  
>                     src/test/config
>                     
>                  
>               
>            
>         
>            copy-resources
>         
>      
>   
> 
>
> Regards,
>
> Arnaud.
>

OK, I just see open issue on the subject for assembly-plugin:
http://jira.codehaus.org/browse/MASSEMBLY-45
May be should open similar issue for resource-plugin?

Arnaud.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Scrolling blindness with maven-javadoc-plugin

[Ognjen Blagojevic]

It works, thanks.

-Ognjen


Nick Stolwijk wrote:

Try the quiet option. [1]

[1] http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#quiet

With regards,

Nick Stolwijk
~Java Developer~

IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl



2010/4/20 Ognjen Blagojevic :

Hi,

Is there a way to get rid of the "Loading source files for package..." and
"Generating ... .html..." messages when using maven-javadoc-plugin?

-Ognjen

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: passing parameters to plugin Archetype

[slew77]

Anyone have any idea on this?  It's really frustrating me :confused:

Thanks,
Steve.


slew77 wrote:
> 
> I'm trying to do the same thing - can someone post instructions, I've
> searched everywhere.  I can see it's possible as when I use m2eclipse it
> allows me to specify custom properties that are picked up, I just can't
> figure out how to do it from the command line.
> 
> Thanks,
> Steve.
> 
> 
> iiggzz wrote:
>> 
>> I found it out! So if anybody has the same problem go ahead and ask me.
>> Now I have another problem. I need to specify the path to my files like
>> this: ${projectName}-mymodule/myfile.txt so after creation it should look
>> like this: helloworld-mymodule.
>> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/passing-parameters-to-plugin-Archetype-tp16807963p28362249.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Unclear about maven web app directory structure

[Werner Punz]

Am 25.04.10 22:33, schrieb Dan King:

From: Anders Hammar



To: Maven Users List
Sent: Sun, April 25, 2010 4:11:57 PM
Subject: Re: Unclear about maven web app directory structure



The java folder is for your java source code, while the webapp folder is for
your web application source files such as jsp files. Create a jar project
through the quickstart archetype to get an example of the former and the
webapp archetype shows the latter.



/Anders


So, if I understand correctly for 'jar' projects the source code goes in the 
src/main/java directory, while in webapps the source code (such as jsps, 
servlets, daos, models, etc.) go into the src/main/webapp directory.

Exactly, you have to see the source/main/<... structure as structure by 
type. A Servlet is mostly coded in java, so it is a java file,

if you code it in groovy it would go into src/main/groovy


Not to be belabor the question, but why in "Maven by Example" is the source 
code for the simple servlet in the src/main/java directory?

Link to the example follows: 
http://www.sonatype.com/books/mvnex-book/reference/web-sect-adding-simple-servlet.html

See above, the src/main/webapp is only for web related resources, a 
servlet however in most instances is a java file.




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Force Maven to use my newer version of Jaxb instead of the one from Java 6?

[VanIngen, Erik (FIPS)]

Hi there,

I have this problem during mvn install of my application:
Caused by: javax.xml.bind.JAXBException:
"org.fao.fi.fisheryresources.domain" doesnt contain ObjectFactory.class or
jaxb.index
which is probably a classpath problem. Java 6 has an older version of Jaxb
than I need. The newer version is specified in the pom.xml but Maven on Linux
takes the version of Java 6. 

How can force Maven to use my newer version of Jaxb instead of the one from
Java 6?

Thanks for helping me out,
Erik

Re: How to add jar file into a Maven 2 environment?

[Yoav Landman]

2010/4/23 Vernon 

>
> Thanks Yoav.
>
> Based on my reading (a quick scanning), JFrog does the same thing as
> Nexus. I will use Nexus for now.
>

Same thing just a lot better :)
Anyway, good luck!


>
>
> 
> > This article is pretty old. You may can follow the new Artifactory
> install
> > instructions here:
> > http://wiki.jfrog.org/confluence/display/RTF/Installing+Artifactory
> > A
> > quick
> > 1 minute setup demo is available here:
> > http://www.youtube.com/watch?v=2FGHwZSAqog
> >
> > HTH,
> >
> > Yoav
> >
> > 2010/4/22 Vernon 
> >
> >> I find an article on the subject:
> >> http://www.theserverside.com/news/1364121/Setting-Up-a-Maven-Repository
> >> .
> >> Does the procedures described in the article good enough for our need?
> >>
> >> 
> >> > Thanks for the information.
> >> >
> >> > How long it will take me to read through the book and set up an
> >> internal
> >> > Maven proxy server?
> >> >
> >> > In a non-Maven environment, we can add those jar files in a minutes.
> >> Of
> >> > course, the downside will be a potential version issues.
> >> >
> >> >
> >> > 
> >> >> Here's a good book on the topic:
> >> >> http://www.sonatype.com/books/nexus-book/reference/
> >> >>
> >> >> 2010/4/22 Vernon :
> >> >>> Thanks a lot for your information.
> >> >>>
> >> >>> Where I can find a documentation on the subject (an internal Maven
> >> >>> proxy
> >> >>> server)? I have a look at the maven documentation under the user
> >> center
> >> >>> and haven't find any useful information yet.
> >> >>>
> >> >>>
> >> >>> 
> >>  Right if its not in a public Maven repository you have to add it to
> >>  yours.  Ideally you will have an internal Maven proxy server such
> >> as
> >>  Artifactory/Nexus where you can deploy it once and all can get it
> >> from
> >>  there.
> >> 
> >>  (Regarding iText 5.x the reason that's not in a public maven is the
> >>  license has changed greatly starting with this version.)
> >> 
> >>  -Dave
> >> 
> >>  2010/4/20 Vernon :
> >> >
> >> > We need to add PayPal Java library files into our Maven
> >> development
> >> > environment. PayPal doesn't make any Maven artifact ID. What is a
> >> > right
> >> > way of adding a jar file?
> >> >
> >> > And one more related question: shall we add jar file by ourselves
> >> for
> >> > a
> >> > new version of jar file? For example, the current version of iText
> >> is
> >> > 5.0.x and the highest version with Maven artifact ID is 2.7.x.
> >> >
> >> > Thanks very much in advance.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> -
> >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> > For additional commands, e-mail: users-h...@maven.apache.org
> >> >
> >> >
> >> 
> >> 
> -
> >>  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >>  For additional commands, e-mail: users-h...@maven.apache.org
> >> 
> >> 
> >>  
> >>  Spam/Virus scanning by CanIt Pro
> >> 
> >>  For more information see
> >>  http://www.kgbinternet.com/SpamFilter.htm
> >> 
> >>  To control your spam filter, log in at
> >>  http://filter.kgbinternet.com
> >> 
> >> >>>
> >> >>>
> >> >>> --
> >> >>> 蒲公苁  http://www.pu-gong-ying.info -
> >> 您的社区信息服务网站
> >> >>>
> >> >>> 新闻门户 -
> >> >>> 容易、快速地浏览来自世界各地主要新闻机构的超迁 0个新闻条目ã€
> >> >>> 社会新闻 - 与他人分享您的故事ã€
> >> >>> 服务指南 -
> 寻找或评论的吃喝、购物ã€�游玩地方ã€
> >> >>> 分类广告 - 张贴和浏览当地的分类广告、
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> -
> >> >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> >>> For additional commands, e-mail: users-h...@maven.apache.org
> >> >>>
> >> >>>
> >> >>
> >> >> -
> >> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> >> For additional commands, e-mail: users-h...@maven.apache.org
> >> >>
> >> >>
> >> >> 
> >> >> Spam/Virus scanning by CanIt Pro
> >> >>
> >> >> For more information see
> >> >> http://www.kgbinternet.com/SpamFilter.htm
> >> >>
> >> >> To control your spam filter, log in at
> >> >> http://filter.kgbinternet.com
> >> >>
> >> >
> >> >
> >> > --
> >> > 蒲公苁  http://www.pu-gong-ying.info -
> >> 您的社区信息服务网站
> >> >
> >> > 新闻门户 -
> >> 容易、快速地浏览来自世界各地主要新闻机构的超迁 0个新闻条目ã€
> >> > 社会新闻 - 与他人分享您的故事ã€
> >> > 服务指南 -
> 寻找或评论的吃喝、购物ã€�游玩地方ã€
> >> > 分类广告 - 张贴和浏览当地的分类广告、
> >> >
> >> >
> >> >
> >> > -
> >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> > For additional commands, e-mail: users-