running jaxb twice with different configs

[lists]

Hello,
to build my app I compile two differen xsd files to generate O/X mapping. I 
have duplicated the jaxb-maven-plugin in my pom. When I run the build from 
eclipse both xsds are compiled, when i run from the command lineonly one xsd is 
compiled. Is my solution at fault or is the maven failing?

Thank you for help. I'm a bloddy maven newbie, please excuse if the answer is 
obvious or the question dumb. 

jacques

com.sun.tools.xjc.maven2
maven-jaxb-plugin


generate-sources

generate





com.danube.codes.ws.schema

src/main/webapp/WEB-INF/xsd



com.sun.tools.xjc.maven2
maven-jaxb-plugin


generate-sources

generate





com.danube.codes.versioninfo.schema  
  
src/main/resources/com/danube/codes/versioninfo/xsd



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Packaging HTML/JavaScript files into WAR from outside project

[David Harkness]

Greetings all,

I've used Maven on a couple projects -- just enough to get by and
build a webapp -- and I've got an issue I can't find a solution to. I
have a non-maven project (Shindig in Apache incubator) that contains
implementations in various languages (Java and PHP so far). They all
share common HTML and JavaScript files in parallel directories, and
the Java implementation is Mavenized:

  shindig/
html/
javascript/
java/
  pom.xml
  src/
main/
  webapp/
php/

When building the java webapp, I'd like some HTML and JS files to be
packaged into the WAR, but those files live in the "html" and
"javascript" directories instead of in "java/src/main/webapp". What's
the appropriate plugin to use in this case?

On a side note, there are other JavaScript files from those same
directories that get packaged into "WEB-INF/classes" since they need
to be available as resources to the Java code and not as files via
HTTP. This works great, and I want something similar that makes them
available via HTTP instead of to the Java code.

Thanks,
Dave

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Cargo issues

[Wayne Fay]

I don't really use Cargo so I guess I'm not following what you're
talking about entirely... I just saw o.a.m.p when I know o.c.c is
correct for the groupId.

What exactly are you experiencing -- what is "this issue"? And why is
this conversation occuring on the Maven list rather than the Cargo
list?

I feel like I've come into this conversation in the middle or
something... I don't really have any idea what your problem is and
what triggers it. When are you getting the "plugin does not exist"
error message -- when you are trying to run "mvn cargo:xyz"?

But realistically, this thread should be moved to the Cargo User list, right?

Wayne

On 1/11/08, Robert Morse <[EMAIL PROTECTED]> wrote:
> I wish you were correct.   If you check the archive, you'll see this
> issue posted on this list as well as codehaus.
> I can get it to work by specifically naming the groupid, artifactid,
> and version on the command line.
>
> On Jan 11, 2008, at 1:18 PM, Wayne Fay wrote:
>
> > It seems you didn't copy Manuel's example "verbatim". There is no
> > o.a.m.p:maven-cargo-plugin. What Maven is telling you is correct --
> > this does not exist, as you can see here:
> > http://repo1.maven.org/maven2/org/apache/maven/plugins/
> >
> > Instead you need:
> >org.codehaus.cargo
> >cargo-maven2-plugin
> >0.3-20061103.124657-5
> >
> > Wayne
> >
> > On 1/11/08, Robert Morse <[EMAIL PROTECTED]> wrote:
> >> This is a late follow-up to this thread, but has anyone solved the
> >> issue of why this error comes up:
> >>
> >> The plugin 'org.apache.maven.plugins:maven-cargo-plugin' does not
> >> exist or no valid version could be found
> >>
> >> For what it's worth, I copied Manuel's example of using this plug-in
> >> verbatim.   This seems to be a common error, but I haven't seen a
> >> solution.
> >>
> >>
> >>
> >> On Aug 27, 2007, at 3:08 AM, Manuel J. Recena Soto wrote:
> >>
> >>> Hi Alexander:
> >>>
> >>> On Sat, 25 Aug 2007 20:14:39 -0400, Alexander Sack wrote
>  Does anyone have Cargo working?  If so, could you post a sample
>  POM?
>  I would really appreciate it.
> 
>  -aps
> 
>  --
>  "What lies behind us and what lies in front of us is of little
>  concern to what lies within us." -Ralph Waldo Emerson
> >>>
> >>> This is a example with Cargo:
> >>> http://www.manuelrecena.com/blog/uploads/code_snippets/cargo_plugin_conf.txt
> >>>
> >>> Regards,
> >>>
> >>> --
> >>> Manuel J. Recena Soto
> >>> * www.manuelrecena.com[/blog]
> >>> * [EMAIL PROTECTED]
> >>> * +34 609710280 (ES)
> >>>
> >>>
> >>> -
> >>> 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]

Re: Remote repository with self signed cert

[Todd Nine]

But that's the wagon that works.  Its when maven attempts to download the
dependencies via an https:// (non-dav) connection it pukes.

On Jan 11, 2008 5:06 PM, Jeff MAURY <[EMAIL PROTECTED]> wrote:

> Which Wagon provider do you use ? If you use WebDAV, see this page :
> http://maven.apache.org/wagon/wagon-providers/wagon-webdav/
>
> Jeff
>
>
> On Jan 11, 2008 10:56 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
>
> > Unfortunately the stack trace I sent was with -X.  Not very helpful is
> it
> > :)?  What I don't understand, is if the dav deploy works with the self
> > signed cert in my kestore, why does the build process not trust the
> > certificate as well?
> >
> > On Jan 11, 2008 4:15 PM, Jeff MAURY <[EMAIL PROTECTED]> wrote:
> >
> > > I suppose wagon has trouble with your self signed certificate.
> > >
> > > Jeff
> > >
> > >
> > > On Jan 11, 2008 9:45 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
> > >
> > > > Just an FYI, it does work with http, however we need to use https
> for
> > > > security reasons, so our http repository will be shut off shortly.
> > > >
> > > > On Jan 11, 2008 3:38 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > Hi all,
> > > > >   I have a repository that is DAV compatible.  I can upload to it,
> > as
> > > > well
> > > > > as download from an http client.  Only the upload requires a
> > password.
> > > > > However whenever I try to perform a build that requires me to
> > download
> > > > an
> > > > > artifact I receive the following stacktrace.  If I go to the repo
> > with
> > > > my
> > > > > browser (firefox), the artifacts are located exactly where they
> > should
> > > > be.
> > > > > The repository uses a self signed certificate, however I have
> > > installed
> > > > the
> > > > > certificate into my keystore with the "keytool" command.  I can
> > > > successfully
> > > > > release/deploy to the repository, but I can't download the
> released
> > > > > artifacts on another machine, or my own if I delete the built
> > > artifacts
> > > > from
> > > > > my local repo.  Is this possibly an issue with the self signed
> cert?
> > > >  Below
> > > > > is my stack trace, any help would be appreciated.
> > > > >
> > > > > Thanks,
> > > > > Todd
> > > > >
> > > > > from the specified remote repositories:
> > > > >   central (http://repo1.maven.org/maven2),
> > > > >   bnp-repo ( https://projects.bnpmedia.com/repository/)
> > > > >  for project com.bnpmedia.standards:config
> > > > > at
> > > > >
> > > >
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > > > > (DefaultMavenProjectBuilder.java:571)
> > > > > at
> > > > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage
> > > > > (DefaultMavenProjectBuilder.java:1255)
> > > > > ... 17 more
> > > > > Caused by:
> > > org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> > > > > Unable to download the artifact from any repository
> > > > >
> > > > >   com.bnpmedia.standards:config:pom:1.0.0
> > > > >
> > > > > from the specified remote repositories:
> > > > >   central (http://repo1.maven.org/maven2),
> > > > >   bnp-repo ( https://projects.bnpmedia.com/repository/)
> > > > >
> > > > > at
> > > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > > > DefaultArtifactResolver.java:206)
> > > > > at
> > > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > > > DefaultArtifactResolver.java:73)
> > > > > at
> > > > >
> > > >
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > > > > (DefaultMavenProjectBuilder.java:524)
> > > > > ... 18 more
> > > > > Caused by: org.apache.maven.wagon.ResourceDoesNotExistException :
> > > Unable
> > > > > to download the artifact from any repository
> > > > > at
> > > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
> > > > (
> > > > > DefaultWagonManager.java:324)
> > > > > at
> > > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > > > DefaultArtifactResolver.java:194)
> > > > > ... 20 more
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > La mélancolie c'est communiste
> > > Tout le monde y a droit de temps en temps
> > > La mélancolie n'est pas capitaliste
> > > C'est même gratuit pour les perdants
> > > La mélancolie c'est pacifiste
> > > On ne lui rentre jamais dedans
> > > La mélancolie oh tu sais ça existe
> > > Elle se prend même avec des gants
> > > La mélancolie c'est pour les syndicalistes
> > > Il faut juste sa carte de permanent
> > >
> > > Miossec (2006)
> > >
> > > http://www.jeffmaury.com
> > > http://riadiscuss.jeffmaury.com
> > >
> >
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La méla

Re: Cargo issues

[Robert Morse]

I wish you were correct.   If you check the archive, you'll see this  
issue posted on this list as well as codehaus.
I can get it to work by specifically naming the groupid, artifactid,  
and version on the command line.


On Jan 11, 2008, at 1:18 PM, Wayne Fay wrote:


It seems you didn't copy Manuel's example "verbatim". There is no
o.a.m.p:maven-cargo-plugin. What Maven is telling you is correct --
this does not exist, as you can see here:
http://repo1.maven.org/maven2/org/apache/maven/plugins/

Instead you need:
   org.codehaus.cargo
   cargo-maven2-plugin
   0.3-20061103.124657-5

Wayne

On 1/11/08, Robert Morse <[EMAIL PROTECTED]> wrote:

This is a late follow-up to this thread, but has anyone solved the
issue of why this error comes up:

The plugin 'org.apache.maven.plugins:maven-cargo-plugin' does not
exist or no valid version could be found

For what it's worth, I copied Manuel's example of using this plug-in
verbatim.   This seems to be a common error, but I haven't seen a
solution.



On Aug 27, 2007, at 3:08 AM, Manuel J. Recena Soto wrote:


Hi Alexander:

On Sat, 25 Aug 2007 20:14:39 -0400, Alexander Sack wrote
Does anyone have Cargo working?  If so, could you post a sample  
POM?

I would really appreciate it.

-aps

--
"What lies behind us and what lies in front of us is of little
concern to what lies within us." -Ralph Waldo Emerson


This is a example with Cargo:
http://www.manuelrecena.com/blog/uploads/code_snippets/cargo_plugin_conf.txt

Regards,

--
Manuel J. Recena Soto
* www.manuelrecena.com[/blog]
* [EMAIL PROTECTED]
* +34 609710280 (ES)


-
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]

Re: Remote repository with self signed cert

[Jeff MAURY]

Which Wagon provider do you use ? If you use WebDAV, see this page :
http://maven.apache.org/wagon/wagon-providers/wagon-webdav/

Jeff


On Jan 11, 2008 10:56 PM, Todd Nine <[EMAIL PROTECTED]> wrote:

> Unfortunately the stack trace I sent was with -X.  Not very helpful is it
> :)?  What I don't understand, is if the dav deploy works with the self
> signed cert in my kestore, why does the build process not trust the
> certificate as well?
>
> On Jan 11, 2008 4:15 PM, Jeff MAURY <[EMAIL PROTECTED]> wrote:
>
> > I suppose wagon has trouble with your self signed certificate.
> >
> > Jeff
> >
> >
> > On Jan 11, 2008 9:45 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
> >
> > > Just an FYI, it does work with http, however we need to use https for
> > > security reasons, so our http repository will be shut off shortly.
> > >
> > > On Jan 11, 2008 3:38 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
> > >
> > > > Hi all,
> > > >   I have a repository that is DAV compatible.  I can upload to it,
> as
> > > well
> > > > as download from an http client.  Only the upload requires a
> password.
> > > > However whenever I try to perform a build that requires me to
> download
> > > an
> > > > artifact I receive the following stacktrace.  If I go to the repo
> with
> > > my
> > > > browser (firefox), the artifacts are located exactly where they
> should
> > > be.
> > > > The repository uses a self signed certificate, however I have
> > installed
> > > the
> > > > certificate into my keystore with the "keytool" command.  I can
> > > successfully
> > > > release/deploy to the repository, but I can't download the released
> > > > artifacts on another machine, or my own if I delete the built
> > artifacts
> > > from
> > > > my local repo.  Is this possibly an issue with the self signed cert?
> > >  Below
> > > > is my stack trace, any help would be appreciated.
> > > >
> > > > Thanks,
> > > > Todd
> > > >
> > > > from the specified remote repositories:
> > > >   central (http://repo1.maven.org/maven2),
> > > >   bnp-repo ( https://projects.bnpmedia.com/repository/)
> > > >  for project com.bnpmedia.standards:config
> > > > at
> > > >
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > > > (DefaultMavenProjectBuilder.java:571)
> > > > at
> > > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage
> > > > (DefaultMavenProjectBuilder.java:1255)
> > > > ... 17 more
> > > > Caused by:
> > org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> > > > Unable to download the artifact from any repository
> > > >
> > > >   com.bnpmedia.standards:config:pom:1.0.0
> > > >
> > > > from the specified remote repositories:
> > > >   central (http://repo1.maven.org/maven2),
> > > >   bnp-repo ( https://projects.bnpmedia.com/repository/)
> > > >
> > > > at
> > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > > DefaultArtifactResolver.java:206)
> > > > at
> > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > > DefaultArtifactResolver.java:73)
> > > > at
> > > >
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > > > (DefaultMavenProjectBuilder.java:524)
> > > > ... 18 more
> > > > Caused by: org.apache.maven.wagon.ResourceDoesNotExistException :
> > Unable
> > > > to download the artifact from any repository
> > > > at
> > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
> > > (
> > > > DefaultWagonManager.java:324)
> > > > at
> > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > > DefaultArtifactResolver.java:194)
> > > > ... 20 more
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > La mélancolie c'est communiste
> > Tout le monde y a droit de temps en temps
> > La mélancolie n'est pas capitaliste
> > C'est même gratuit pour les perdants
> > La mélancolie c'est pacifiste
> > On ne lui rentre jamais dedans
> > La mélancolie oh tu sais ça existe
> > Elle se prend même avec des gants
> > La mélancolie c'est pour les syndicalistes
> > Il faut juste sa carte de permanent
> >
> > Miossec (2006)
> >
> > http://www.jeffmaury.com
> > http://riadiscuss.jeffmaury.com
> >
>



-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com

Setting up Blacklist for Maven1 repo

[Zach Legein]

I am trying to setup a black list of a remote repository. I currently have
this remote repo configured:

Maven 1 Central Repository
Identifier  m1-central
NameMaven 1 Central Repository
URL http://repo1.maven.org/maven/
TypeMaven 1.x Repository

With this proxy connectory setup to blacklist certain things

m1-central
Maven 1 Central Repository
http://repo1.maven.org/maven/
Expand
Network Proxy:  (direct connection)
Policies:   
releasesalways
snapshots   never
checksumfix
cache-failures  yes
Black List: 
"javax/**"
"com/sun/**"

And I have the reciprocal whitelist on the 

Java.net Repository for Maven 1
Identifier  maven1-repository.dev.java.net
NameJava.net Repository for Maven 1
URL http://download.java.net/maven/1/
TypeMaven 1.x Repository

Now the reason for this is that the dependency for 

com.sun.xml.bind:jaxb-impl:jar:2.0.1
3) javax.xml:jaxb-api:jar:2.0
4) javax.xml:jsr173:jar:1.0

on http://repo1.maven.org/maven/ has a pom that points to some dead
artifacts.

Now the problem is that this setup doesn't seem to work, I keep getting
com.sun.xml.bind:jaxb-impl:jar:2.0.1 from http://repo1.maven.org/maven/ when
I want to get com.sun.xml.bind:jaxb-impl:jar:2.0.1 from
http://download.java.net/maven/1/.

Is this the right setup?

zach

 
-- 
View this message in context: 
http://www.nabble.com/Setting-up-Blacklist-for-Maven1-repo-tp14766037p14766037.html
Sent from the archiva-users mailing list archive at Nabble.com.

Re: Remote repository with self signed cert

[Todd Nine]

Unfortunately the stack trace I sent was with -X.  Not very helpful is it
:)?  What I don't understand, is if the dav deploy works with the self
signed cert in my kestore, why does the build process not trust the
certificate as well?

On Jan 11, 2008 4:15 PM, Jeff MAURY <[EMAIL PROTECTED]> wrote:

> I suppose wagon has trouble with your self signed certificate.
>
> Jeff
>
>
> On Jan 11, 2008 9:45 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
>
> > Just an FYI, it does work with http, however we need to use https for
> > security reasons, so our http repository will be shut off shortly.
> >
> > On Jan 11, 2008 3:38 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
> >
> > > Hi all,
> > >   I have a repository that is DAV compatible.  I can upload to it, as
> > well
> > > as download from an http client.  Only the upload requires a password.
> > > However whenever I try to perform a build that requires me to download
> > an
> > > artifact I receive the following stacktrace.  If I go to the repo with
> > my
> > > browser (firefox), the artifacts are located exactly where they should
> > be.
> > > The repository uses a self signed certificate, however I have
> installed
> > the
> > > certificate into my keystore with the "keytool" command.  I can
> > successfully
> > > release/deploy to the repository, but I can't download the released
> > > artifacts on another machine, or my own if I delete the built
> artifacts
> > from
> > > my local repo.  Is this possibly an issue with the self signed cert?
> >  Below
> > > is my stack trace, any help would be appreciated.
> > >
> > > Thanks,
> > > Todd
> > >
> > > from the specified remote repositories:
> > >   central (http://repo1.maven.org/maven2),
> > >   bnp-repo ( https://projects.bnpmedia.com/repository/)
> > >  for project com.bnpmedia.standards:config
> > > at
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > > (DefaultMavenProjectBuilder.java:571)
> > > at
> > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage
> > > (DefaultMavenProjectBuilder.java:1255)
> > > ... 17 more
> > > Caused by:
> org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> > > Unable to download the artifact from any repository
> > >
> > >   com.bnpmedia.standards:config:pom:1.0.0
> > >
> > > from the specified remote repositories:
> > >   central (http://repo1.maven.org/maven2),
> > >   bnp-repo ( https://projects.bnpmedia.com/repository/)
> > >
> > > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > DefaultArtifactResolver.java:206)
> > > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > DefaultArtifactResolver.java:73)
> > > at
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > > (DefaultMavenProjectBuilder.java:524)
> > > ... 18 more
> > > Caused by: org.apache.maven.wagon.ResourceDoesNotExistException :
> Unable
> > > to download the artifact from any repository
> > > at
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
> > (
> > > DefaultWagonManager.java:324)
> > > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > DefaultArtifactResolver.java:194)
> > > ... 20 more
> > >
> > >
> >
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>

Re: Continuum: what does default mean?

[Olivier Lamy]

Hi,
In fact, we're not talking about the same field ;-).
The default you talk is to say this builddefinition will be used when
the user will force a build from the project group menu page.
Concerning build definition template this feature is available in 1.1
final (the myfaces continuum instance is 1.1-beta-2).

--
Olivier
PS : if you have more questions please use the continuum users ml (thanks)

2008/1/11, simon <[EMAIL PROTECTED]>:
> Hi Olivier,
>
> I think we're talking about the same field, but unfortunately I don't
> understand your answer. I'll try to be more precise...
>
> When looking at an existing "build definition", the columns are:
>   goals
>   arguments
>   build file
>   schedule
>   profile
>   from
>   build fresh
>   default
>
> This "default" setting is a boolean value.
>
> I'm talking specifically about the continuum server at
>myfaces.zones.apache.org:8080/continuum
> although unfortunately you won't be able to see anything there without a
> login account.
>
> There are lots of definitions there with default=true, and lots with
> default=false. In particular, it appears that definitions for building
> "jars" is typically default=true while building sites is typically
> default=false.
>
> But I don't understand why things are set up this way..
>
> What is a "default maven2 template"? I see in the continuum docs a
> section about "build templates", although I see no such menu in the
> myfaces continuum site. Maybe I don't have sufficient privileges to see
> the menu; if so, how would I find out whether "default=true" is what I
> want or not for a new build definition? And what does one do anyway?
>
> Thanks,
> Simon
>
> On Wed, 2008-01-09 at 17:58 +0100, Olivier Lamy wrote:
> > Hi,
> > You mean when adding a project in the Build Definition list box ?
> > If yes it's the default build definition for the project type (maven1,
> > maven2, ant).
> > If you are adding a m2 project : Default == default maven2 template.
> >
> > Sure it's a little verbose here because we repeat the same things.
> >
> > --
> > Olivier
> >
> >
> > 2008/1/9, Simon Kitching <[EMAIL PROTECTED]>:
> > > Hi,
> > >
> > > On a continuum site, what does the "default" setting mean for a project?
> > >
> > > Thanks, Simon
> > >
> > > -
> > > 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]

Re: Remote repository with self signed cert

[Jeff MAURY]

I suppose wagon has trouble with your self signed certificate.

Jeff


On Jan 11, 2008 9:45 PM, Todd Nine <[EMAIL PROTECTED]> wrote:

> Just an FYI, it does work with http, however we need to use https for
> security reasons, so our http repository will be shut off shortly.
>
> On Jan 11, 2008 3:38 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
>
> > Hi all,
> >   I have a repository that is DAV compatible.  I can upload to it, as
> well
> > as download from an http client.  Only the upload requires a password.
> > However whenever I try to perform a build that requires me to download
> an
> > artifact I receive the following stacktrace.  If I go to the repo with
> my
> > browser (firefox), the artifacts are located exactly where they should
> be.
> > The repository uses a self signed certificate, however I have installed
> the
> > certificate into my keystore with the "keytool" command.  I can
> successfully
> > release/deploy to the repository, but I can't download the released
> > artifacts on another machine, or my own if I delete the built artifacts
> from
> > my local repo.  Is this possibly an issue with the self signed cert?
>  Below
> > is my stack trace, any help would be appreciated.
> >
> > Thanks,
> > Todd
> >
> > from the specified remote repositories:
> >   central (http://repo1.maven.org/maven2),
> >   bnp-repo ( https://projects.bnpmedia.com/repository/)
> >  for project com.bnpmedia.standards:config
> > at
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > (DefaultMavenProjectBuilder.java:571)
> > at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage
> > (DefaultMavenProjectBuilder.java:1255)
> > ... 17 more
> > Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> > Unable to download the artifact from any repository
> >
> >   com.bnpmedia.standards:config:pom:1.0.0
> >
> > from the specified remote repositories:
> >   central (http://repo1.maven.org/maven2),
> >   bnp-repo ( https://projects.bnpmedia.com/repository/)
> >
> > at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > DefaultArtifactResolver.java:206)
> > at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > DefaultArtifactResolver.java:73)
> > at
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > (DefaultMavenProjectBuilder.java:524)
> > ... 18 more
> > Caused by: org.apache.maven.wagon.ResourceDoesNotExistException : Unable
> > to download the artifact from any repository
> > at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
> (
> > DefaultWagonManager.java:324)
> > at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > DefaultArtifactResolver.java:194)
> > ... 20 more
> >
> >
>



-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com

Re: Remote repository with self signed cert

[Todd Nine]

Just an FYI, it does work with http, however we need to use https for
security reasons, so our http repository will be shut off shortly.

On Jan 11, 2008 3:38 PM, Todd Nine <[EMAIL PROTECTED]> wrote:

> Hi all,
>   I have a repository that is DAV compatible.  I can upload to it, as well
> as download from an http client.  Only the upload requires a password.
> However whenever I try to perform a build that requires me to download an
> artifact I receive the following stacktrace.  If I go to the repo with my
> browser (firefox), the artifacts are located exactly where they should be.
> The repository uses a self signed certificate, however I have installed the
> certificate into my keystore with the "keytool" command.  I can successfully
> release/deploy to the repository, but I can't download the released
> artifacts on another machine, or my own if I delete the built artifacts from
> my local repo.  Is this possibly an issue with the self signed cert?  Below
> is my stack trace, any help would be appreciated.
>
> Thanks,
> Todd
>
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   bnp-repo ( https://projects.bnpmedia.com/repository/)
>  for project com.bnpmedia.standards:config
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> (DefaultMavenProjectBuilder.java:571)
> at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage
> (DefaultMavenProjectBuilder.java:1255)
> ... 17 more
> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> Unable to download the artifact from any repository
>
>   com.bnpmedia.standards:config:pom:1.0.0
>
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   bnp-repo ( https://projects.bnpmedia.com/repository/)
>
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:206)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:73)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> (DefaultMavenProjectBuilder.java:524)
> ... 18 more
> Caused by: org.apache.maven.wagon.ResourceDoesNotExistException : Unable
> to download the artifact from any repository
> at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(
> DefaultWagonManager.java:324)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:194)
> ... 20 more
>
>

Re: Remote repository with self signed cert

[Wayne Fay]

Does running with mvn -X tell you any more details than what we're seeing here?

Wayne

On 1/11/08, Todd Nine <[EMAIL PROTECTED]> wrote:
> Hi all,
>  I have a repository that is DAV compatible.  I can upload to it, as well
> as download from an http client.  Only the upload requires a password.
> However whenever I try to perform a build that requires me to download an
> artifact I receive the following stacktrace.  If I go to the repo with my
> browser (firefox), the artifacts are located exactly where they should be.
> The repository uses a self signed certificate, however I have installed the
> certificate into my keystore with the "keytool" command.  I can successfully
> release/deploy to the repository, but I can't download the released
> artifacts on another machine, or my own if I delete the built artifacts from
> my local repo.  Is this possibly an issue with the self signed cert?  Below
> is my stack trace, any help would be appreciated.
>
> Thanks,
> Todd
>
> from the specified remote repositories:
>  central (http://repo1.maven.org/maven2),
>  bnp-repo (https://projects.bnpmedia.com/repository/)
>  for project com.bnpmedia.standards:config
>at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(
> DefaultMavenProjectBuilder.java:571)
>at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(
> DefaultMavenProjectBuilder.java:1255)
>... 17 more
> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> Unable to download the artifact from any repository
>
>  com.bnpmedia.standards:config:pom:1.0.0
>
> from the specified remote repositories:
>  central (http://repo1.maven.org/maven2),
>  bnp-repo (https://projects.bnpmedia.com/repository/)
>
>at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:206)
>at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:73)
>at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(
> DefaultMavenProjectBuilder.java:524)
>... 18 more
> Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to
> download the artifact from any repository
>at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(
> DefaultWagonManager.java:324)
>at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:194)
>... 20 more
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Cobertura

[Wayne Fay]

Modify the Cobertura plugin so it does what you want. ;-)

It is open source, after all.
http://mojo.codehaus.org/cobertura-maven-plugin/

Wayne

On 1/11/08, Hilco Wijbenga <[EMAIL PROTECTED]> wrote:
> I'd like to do something like this:
> http://www.devx.com/Java/Article/36231 but not with Ant but with
> Maven. (In summary, it extracts the line coverage rate from the
> coverage.xml file created by Cobertura and uses it to make sure future
> builds can only do better, not worse.)
>
> The problem is that the Cobertura Maven plugin doesn't seem to make
> the resulting coverage percentage public. I can do a
> cobertura:dump-datafile but this doesn't output to a file. Besides
> there does not seem to be a way to tell the plugin to use any kind of
> configuration file.
>
> The only solution I can think of is to go the AntRun plugin route...
> Does anyone have a better idea?
>
> Cheers,
> Hilco
>
> -
> 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]

Remote repository with self signed cert

[Todd Nine]

Hi all,
  I have a repository that is DAV compatible.  I can upload to it, as well
as download from an http client.  Only the upload requires a password.
However whenever I try to perform a build that requires me to download an
artifact I receive the following stacktrace.  If I go to the repo with my
browser (firefox), the artifacts are located exactly where they should be.
The repository uses a self signed certificate, however I have installed the
certificate into my keystore with the "keytool" command.  I can successfully
release/deploy to the repository, but I can't download the released
artifacts on another machine, or my own if I delete the built artifacts from
my local repo.  Is this possibly an issue with the self signed cert?  Below
is my stack trace, any help would be appreciated.

Thanks,
Todd

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  bnp-repo (https://projects.bnpmedia.com/repository/)
 for project com.bnpmedia.standards:config
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(
DefaultMavenProjectBuilder.java:571)
at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(
DefaultMavenProjectBuilder.java:1255)
... 17 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
Unable to download the artifact from any repository

  com.bnpmedia.standards:config:pom:1.0.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  bnp-repo (https://projects.bnpmedia.com/repository/)

at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
DefaultArtifactResolver.java:206)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
DefaultArtifactResolver.java:73)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(
DefaultMavenProjectBuilder.java:524)
... 18 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to
download the artifact from any repository
at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(
DefaultWagonManager.java:324)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
DefaultArtifactResolver.java:194)
... 20 more

Cobertura

[Hilco Wijbenga]

I'd like to do something like this:
http://www.devx.com/Java/Article/36231 but not with Ant but with
Maven. (In summary, it extracts the line coverage rate from the
coverage.xml file created by Cobertura and uses it to make sure future
builds can only do better, not worse.)

The problem is that the Cobertura Maven plugin doesn't seem to make
the resulting coverage percentage public. I can do a
cobertura:dump-datafile but this doesn't output to a file. Besides
there does not seem to be a way to tell the plugin to use any kind of
configuration file.

The only solution I can think of is to go the AntRun plugin route...
Does anyone have a better idea?

Cheers,
Hilco

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Cargo issues

[Wayne Fay]

It seems you didn't copy Manuel's example "verbatim". There is no
o.a.m.p:maven-cargo-plugin. What Maven is telling you is correct --
this does not exist, as you can see here:
http://repo1.maven.org/maven2/org/apache/maven/plugins/

Instead you need:
org.codehaus.cargo
cargo-maven2-plugin
0.3-20061103.124657-5

Wayne

On 1/11/08, Robert Morse <[EMAIL PROTECTED]> wrote:
> This is a late follow-up to this thread, but has anyone solved the
> issue of why this error comes up:
>
> The plugin 'org.apache.maven.plugins:maven-cargo-plugin' does not
> exist or no valid version could be found
>
> For what it's worth, I copied Manuel's example of using this plug-in
> verbatim.   This seems to be a common error, but I haven't seen a
> solution.
>
>
>
> On Aug 27, 2007, at 3:08 AM, Manuel J. Recena Soto wrote:
>
> > Hi Alexander:
> >
> > On Sat, 25 Aug 2007 20:14:39 -0400, Alexander Sack wrote
> >> Does anyone have Cargo working?  If so, could you post a sample POM?
> >> I would really appreciate it.
> >>
> >> -aps
> >>
> >> --
> >> "What lies behind us and what lies in front of us is of little
> >> concern to what lies within us." -Ralph Waldo Emerson
> >
> > This is a example with Cargo:
> > http://www.manuelrecena.com/blog/uploads/code_snippets/cargo_plugin_conf.txt
> >
> > Regards,
> >
> > --
> > Manuel J. Recena Soto
> > * www.manuelrecena.com[/blog]
> > * [EMAIL PROTECTED]
> > * +34 609710280 (ES)
> >
> >
> > -
> > 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]

Maven & java2wsdl...

[Fernando da Motta Hildebrand]

Hi,

I'm using Maven 1.x with Axis 1, here's below my maven.xml






  

  
  

  
  


  


  




Copying server-config.wsdd and context.xml...

  
  


  
  

  


  


  


  
  

http://localhost:8080/${pom.artifactId}/soap/${pom.artifactId}";
output="${maven.src.dir}\webapp\${pom.artifactId}.wsdl">

  

  


   




But I can't get it to work, it doesn't generate any wsdl files.

Can anyone give a hint here?

Thanks.

-- 
Fernando da Motta Hildebrand
IT Consultant
Brooks' Law : "adding manpower to a late software project makes it later..."

Re: Cargo issues

[Robert Morse]

This is a late follow-up to this thread, but has anyone solved the  
issue of why this error comes up:


The plugin 'org.apache.maven.plugins:maven-cargo-plugin' does not  
exist or no valid version could be found


For what it's worth, I copied Manuel's example of using this plug-in  
verbatim.   This seems to be a common error, but I haven't seen a  
solution.




On Aug 27, 2007, at 3:08 AM, Manuel J. Recena Soto wrote:


Hi Alexander:

On Sat, 25 Aug 2007 20:14:39 -0400, Alexander Sack wrote

Does anyone have Cargo working?  If so, could you post a sample POM?
I would really appreciate it.

-aps

--
"What lies behind us and what lies in front of us is of little
concern to what lies within us." -Ralph Waldo Emerson


This is a example with Cargo:
http://www.manuelrecena.com/blog/uploads/code_snippets/cargo_plugin_conf.txt

Regards,

--
Manuel J. Recena Soto
* www.manuelrecena.com[/blog]
* [EMAIL PROTECTED]
* +34 609710280 (ES)


-
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]

Re: Continuum: what does default mean?

[Wendy Smoak]

On Jan 11, 2008 10:46 AM, simon <[EMAIL PROTECTED]> wrote:

> I'm talking specifically about the continuum server at
>myfaces.zones.apache.org:8080/continuum
> although unfortunately you won't be able to see anything there without a
> login account.

I made 'guest' a global project user, so the projects are now visible.

The MyFaces zone is running 1.1-beta-2, so the docs on the Continuum
site won't match exactly.

Can we move this to [EMAIL PROTECTED] instead?
http://maven.apache.org/continuum/mail-lists.html

-- 
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Continuum: what does default mean?

[simon]

Hi Olivier,

I think we're talking about the same field, but unfortunately I don't
understand your answer. I'll try to be more precise...

When looking at an existing "build definition", the columns are:
  goals
  arguments
  build file
  schedule
  profile
  from
  build fresh
  default

This "default" setting is a boolean value.

I'm talking specifically about the continuum server at
   myfaces.zones.apache.org:8080/continuum
although unfortunately you won't be able to see anything there without a
login account.

There are lots of definitions there with default=true, and lots with
default=false. In particular, it appears that definitions for building
"jars" is typically default=true while building sites is typically
default=false.

But I don't understand why things are set up this way..

What is a "default maven2 template"? I see in the continuum docs a
section about "build templates", although I see no such menu in the
myfaces continuum site. Maybe I don't have sufficient privileges to see
the menu; if so, how would I find out whether "default=true" is what I
want or not for a new build definition? And what does one do anyway?

Thanks,
Simon

On Wed, 2008-01-09 at 17:58 +0100, Olivier Lamy wrote:
> Hi,
> You mean when adding a project in the Build Definition list box ?
> If yes it's the default build definition for the project type (maven1,
> maven2, ant).
> If you are adding a m2 project : Default == default maven2 template.
> 
> Sure it's a little verbose here because we repeat the same things.
> 
> --
> Olivier
> 
> 
> 2008/1/9, Simon Kitching <[EMAIL PROTECTED]>:
> > Hi,
> >
> > On a continuum site, what does the "default" setting mean for a project?
> >
> > Thanks, Simon
> >
> > -
> > 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]

Maven 2.1 release

[Graham Leggett]

Hi all,

Is there any expected timeframe for the first stab (an alpha or beta) 
release of maven 2.1?


I found this claiming around December time, is there any update?

http://mail-archives.apache.org/mod_mbox/maven-users/200710.mbox/[EMAIL 
PROTECTED]

Regards,
Graham
--


smime.p7s
Description: S/MIME Cryptographic Signature

Re: regarding creating a project using maven

[Wayne Fay]

First I would upgrade to the latest 2.0.8 version of Maven.

Then I would read the documentation around configuring an Internet
proxy for Maven in settings.xml. It sounds like Maven cannot connect
to the Internet to download necessary files.

Wayne

On 1/11/08, Praphul Chalasani <[EMAIL PROTECTED]> wrote:
> When I check for mvn -version  ,it has displayed the version(Maven version:
> 2.0).
>
>
>
> When I ran the following command , I am getting the error .
>
>
>
> F:\work2> mvn archetype:create -DgroupId=com.mycompany.app
> -DartifactId=my-app
>
> [INFO] Scanning for projects...
>
> [INFO] Searching repository for plugin with prefix: 'archetype'.
>
> [INFO] artifact org.apache.maven.plugins:maven-archetype-plugin: checking
> for up
>
> dates from central
>
> [WARNING] repository metadata for: 'artifact
> org.apache.maven.plugins:maven-archetype-plugin' could not be retrieved from
> repository: central due to an error: Error transferring file
>
> [INFO] Repository 'central' will be blacklisted
>
> [INFO]
> 
>
> [ERROR] BUILD ERROR
>
> [INFO]
> 
>
> [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not
> exist or no valid version could be found
>
> [INFO]
> 
>
> [INFO] For more information, run Maven with the -e switch
>
> [INFO]
> 
>
> [INFO] Total time: 36 seconds
>
> [INFO] Finished at: Thu Jan 10 18:28:03 GMT+05:30 2008
>
> [INFO] Final Memory: 1M/2M
>
> [INFO]
> 
>
>
>
>
>
> Can you suggest me the solution.
>
>
>
>
>
> Thanks®ards,
>
> Praphul.
>
>
>
>
> DISCLAIMER
> ==
> This e-mail may contain privileged and confidential information which is the 
> property of Persistent Systems Ltd. It is intended only for the use of the 
> individual or entity to which it is addressed. If you are not the intended 
> recipient, you are not authorized to read, retain, copy, print, distribute or 
> use this message. If you have received this communication in error, please 
> notify the sender and delete all copies of this message. Persistent Systems 
> Ltd. does not accept any liability for virus infected mails.
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: plug-in vs dependency

[Wayne Fay]

A dependency is something your project uses itself internally eg log4j
or hibernate.

A plugin is something that Maven uses during its build cycle to do
something for your project eg the hibernate3 plugin can read your
hibernate configuration files and generate some Java classes.

Wayne

On 1/11/08, rakeshsugirtharaj <[EMAIL PROTECTED]> wrote:
>
> What is the difference between a plug-in and a dependency? Examples?
> --
> View this message in context: 
> http://www.nabble.com/plug-in-vs-dependency-tp14750516s177p14750516.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> 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]

Re: How to deploy a non-maven-built WAR to Tomcat with MAVEN2?

[Thomas Chang]

I have maven2 and don't want to install ant. 



Wayne Fay <[EMAIL PROTECTED]> schrieb: Maven is great, but in this particular 
case, I would think about just
using an Ant "deploy to Tomcat" script.

Wayne

On 1/11/08, Jeff MAURY  wrote:
> Create a profile in your pom with configuration to your other war and follow
> these instructions:
> http://mojo.codehaus.org/tomcat-maven-plugin/deployment.html#Deploying%20a%20WAR%20file
>
> Jeff
>
>
> On Jan 11, 2008 3:43 PM, Thomas Chang  wrote:
>
> > Hi all,
> >
> > We know we can deploy a maven-built war to Tomcat using "mvn
> > tomcat:deploy". Now I have a WAR which is not built with maven2. That means
> > it has no pom.xml. Can I even thoug use maven2 to deploy it to Tomcat?
> >
> > Regards
> >
> > Thomas
> >
> >
> >
> >
> > -
> > Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s
> > mit dem  neuen Yahoo! Mail.
> >
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



   
-
Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit 
dem  neuen Yahoo! Mail. 

Re: How to deploy a non-maven-built WAR to Tomcat with MAVEN2?

[Wayne Fay]

Maven is great, but in this particular case, I would think about just
using an Ant "deploy to Tomcat" script.

Wayne

On 1/11/08, Jeff MAURY <[EMAIL PROTECTED]> wrote:
> Create a profile in your pom with configuration to your other war and follow
> these instructions:
> http://mojo.codehaus.org/tomcat-maven-plugin/deployment.html#Deploying%20a%20WAR%20file
>
> Jeff
>
>
> On Jan 11, 2008 3:43 PM, Thomas Chang <[EMAIL PROTECTED]> wrote:
>
> > Hi all,
> >
> > We know we can deploy a maven-built war to Tomcat using "mvn
> > tomcat:deploy". Now I have a WAR which is not built with maven2. That means
> > it has no pom.xml. Can I even thoug use maven2 to deploy it to Tomcat?
> >
> > Regards
> >
> > Thomas
> >
> >
> >
> >
> > -
> > Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s
> > mit dem  neuen Yahoo! Mail.
> >
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Error: Cannot invoke Tomcat manager by running tomcat:deploy

[Thomas Chang]

Yes. I can open  http://localhost:8080/manager/html. In this page this is a 
table where there is "/manager". If I click it, I got the error. It seems it 
will call up the manager app but failed.



Jeff MAURY <[EMAIL PROTECTED]> schrieb: What url do you use ?
The URL to use is http://localhost:8080/manager/html
and not *http://localhost:8080/manager*

Jeff


On Jan 11, 2008 3:04 PM, Thomas Chang  wrote:

> You are right. I change the "tomcat-users.xml" as you wrote, it runs.
> Thank!
>
> But, if I open the Tomcat and go into the Manager page. When I click the
> link "manager", I will get error of "HTTP Status 404 - /manager/".
>
> Do you know why?
>
>
>
> Jeff MAURY  schrieb: By default, the tomcat
> plugin uses admin as a user name and no password.
> If you don't specify them in your POM, your use modify your
> tomcat-users.xmlfile as follows:
>
>
>
>
>
>
>
>
>
>
>  **
>
>
> Jeff
>
>
>
> On Jan 11, 2008 2:36 PM, Thomas Chang  wrote:
>
> > Now I change the "tomcat-users.xml" as follow, but it's the same.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Jeff MAURY  schrieb: You must have the manager
> > role so supply tomcat as user and password.
> >
> > Regards
> > Jeff
> >
> >
> > On Jan 11, 2008 2:03 PM, Thomas Chang  wrote:
> >
> > > Sure. My "tomcat-users.xml" looks as follow. Is it OK?
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Jeff MAURY  schrieb: You must specify user and
> > > password because the manager application is
> > > protected by default.
> > >
> > > Jeff
> > >
> > >
> > > On Jan 11, 2008 1:27 PM, Thomas Chang  wrote:
> > >
> > > > Hi all,
> > > >
> > > > I try to deploy a WAR to Tomcat using "
> > > > mvn tomcat:deploy -Dmaven.tomcat.url=http://localhost:8585/manager";.
> > But
> > > I
> > > > got error as follow. What's wrong?
> > > >
> > > > [ERROR] BUILD ERROR
> > > > [INFO]
> > > >
> > 
> > > > [INFO] Cannot invoke Tomcat manager
> > > >
> > > > Embedded error: Server returned HTTP response code: 401 for URL:
> > > > http://localhos
> > > > t:8585/manager/deploy?path=%2FTestWeb&war=
> > > > [INFO]
> > > >
> > 
> > > > [INFO] For more information, run Maven with the -e switch
> > > > [INFO]
> > > >
> > 
> > > > [INFO] Total time: 10 seconds
> > > > [INFO] Finished at: Fri Jan 11 13:19:55 CET 2008
> > > > [INFO] Final Memory: 6M/11M
> > > > [INFO]
> > > >
> > 
> > > >
> > > > C:\Projects\eclipse_workspace\TestWeb>
> > > >
> > > >
> > > > -
> > > > Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen
> > > Sie´s
> > > > mit dem  neuen Yahoo! Mail.
> > > >
> > >
> > >
> > >
> > > --
> > > La mélancolie c'est communiste
> > > Tout le monde y a droit de temps en temps
> > > La mélancolie n'est pas capitaliste
> > > C'est même gratuit pour les perdants
> > > La mélancolie c'est pacifiste
> > > On ne lui rentre jamais dedans
> > > La mélancolie oh tu sais ça existe
> > > Elle se prend même avec des gants
> > > La mélancolie c'est pour les syndicalistes
> > > Il faut juste sa carte de permanent
> > >
> > > Miossec (2006)
> > >
> > > http://www.jeffmaury.com
> > > http://riadiscuss.jeffmaury.com
> > >
> > >
> > >
> > > -
> > > Beginnen Sie den Tag mit den neuesten Nachrichten. Machen Sie Yahoo!
> zu
> > > Ihrer Startseite!
> > >
> >
> >
> >
> > --
> > La mélancolie c'est communiste
> > Tout le monde y a droit de temps en temps
> > La mélancolie n'est pas capitaliste
> > C'est même gratuit pour les perdants
> > La mélancolie c'est pacifiste
> > On ne lui rentre jamais dedans
> > La mélancolie oh tu sais ça existe
> > Elle se prend même avec des gants
> > La mélancolie c'est pour les syndicalistes
> > Il faut juste sa carte de permanent
> >
> > Miossec (2006)
> >
> > http://www.jeffmaury.com
> > http://riadiscuss.jeffmaury.com
> >
> >
> >
> > -
> > Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen
> Sie´s
> > mit dem  neuen Yahoo! Mail.
> >
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>
>
>
> -
> Beginnen Sie den Tag mit den neuesten Nachrichten. Machen Sie Yahoo! zu
> Ihrer Startseite!
>



-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie 

RE: Classpath order of dependencies

[Jörg Schaible]

Simon Kitching wrote:
>  Marco Huber <[EMAIL PROTECTED]> schrieb:
>> Hello,
>> 
>> I have a little problem with the order of my dependencies.
>> Depending on the posistion of one dependency I get an error during
>> my tests. 
>> 
>> The first pom snippet result in an NoClassDefFoundError:
>> 
>> ...
>> 
>> org.hibernate
>> hibernate-validator
>> 3.0.0.ga
>> 
>> 
>> 
>> org.jboss.embedded
>> hibernate-all
>> beta2
>> 
>> ...
>> 
>> 
>> If I change the order of this two dependencies I get not error.
>> 
>> Is the order in the pom the crucial factor on how the classpath is
>> build in maven? Or is it possible that transient dependencies
>> overwrites direct dependencies?

[snip]
 
> My guess is that the pom for hibernate-validator is wrong,
> and has left out a dependency. Of course if that is the case,
> then a maven project using that pom would not build - but
> perhaps the jboss people don't use maven for building and
> just create poms by hand for maven users.

[snip]

My guess is that hibernate-all contains an own version of hibernate-validator 
and since the version of the explicit hibernate-validator artifact is a lot 
newer, compilation will fail if the newer classes are found first in the 
classpath. That's why most people here do not recommend assembled artifacts 
because you'll get all kind of weird problems.

- Jörg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to deploy a non-maven-built WAR to Tomcat with MAVEN2?

[Jeff MAURY]

Create a profile in your pom with configuration to your other war and follow
these instructions:
http://mojo.codehaus.org/tomcat-maven-plugin/deployment.html#Deploying%20a%20WAR%20file

Jeff


On Jan 11, 2008 3:43 PM, Thomas Chang <[EMAIL PROTECTED]> wrote:

> Hi all,
>
> We know we can deploy a maven-built war to Tomcat using "mvn
> tomcat:deploy". Now I have a WAR which is not built with maven2. That means
> it has no pom.xml. Can I even thoug use maven2 to deploy it to Tomcat?
>
> Regards
>
> Thomas
>
>
>
>
> -
> Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s
> mit dem  neuen Yahoo! Mail.
>



-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com

How to deploy a non-maven-built WAR to Tomcat with MAVEN2?

[Thomas Chang]

Hi all,

We know we can deploy a maven-built war to Tomcat using "mvn tomcat:deploy". 
Now I have a WAR which is not built with maven2. That means it has no pom.xml. 
Can I even thoug use maven2 to deploy it to Tomcat?

Regards

Thomas



   
-
Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit 
dem  neuen Yahoo! Mail. 

RE: Configure FROM mailbox

[Bernard Brady]

Ivan

Take a look at this
http://www.mail-archive.com/users@maven.apache.org/msg77767.html

Should solve your problem.

 

Regards

Bernard Brady

  

Senior Software Developer

Autometrics 

370/374 Upper Newtownards Road

Belfast

County Antrim 

BT43EX

United Kingdom

 

tel:   +44 (0) 02890652888

 

 

-Original Message-
From: ivan [mailto:[EMAIL PROTECTED] 
Sent: 10 January 2008 13:42
To: [EMAIL PROTECTED]
Subject: Re: Configure FROM mailbox

 

Olivier Lamy wrote:

> Hi,

> In the webapp, you will find the find

> WEB-INF/classes/META-INF/plexus/application.xml

> It's contains the empty elements :

>

> 

> 

> --

> Olivier

> 

> 2008/1/10, ivan <[EMAIL PROTECTED]>:

>> Hi!

>> I configured file plexus.xml (continuum 1.1), and also section
"Mail".

>> But while starting continuum, following line are printed into log:

>> 

>>  org.codehaus.plexus.notification.notifier.Notifier:mail  - The from

>> mailbox is not configured, will use the nag email address from the
project.

>> 

>> So, how can I set FROM mailbox and where? Thanks

>> 

> 

 

Thanks! It helps, but particular.

 

In fact, while starting continuum, I got following:

 

org.codehaus.plexus.notification.notifier.Notifier:mail  - Using 

'[EMAIL PROTECTED]' as the from mailbox for all emails.

 

But when I try to register new user, I got this:

 

INFO   | jvm 1| 2008/01/10 15:29:32 | DEBUG SMTP: use8bit false

INFO   | jvm 1| 2008/01/10 15:29:32 | MAIL FROM:<[EMAIL PROTECTED]>

INFO   | jvm 1| 2008/01/10 15:29:32 | 550 Sender verify failed

INFO   | jvm 1| 2008/01/10 15:29:32 | 

com.sun.mail.smtp.SMTPSendFailedException: 550 Sender verify failed

 

It is interesting, but when I got letters about building status - 

continuum use [EMAIL PROTECTED]

 

May be somebody face it?  Thanks

 

Re: Error: Cannot invoke Tomcat manager by running tomcat:deploy

[Jeff MAURY]

What url do you use ?
The URL to use is http://localhost:8080/manager/html
and not *http://localhost:8080/manager*

Jeff


On Jan 11, 2008 3:04 PM, Thomas Chang <[EMAIL PROTECTED]> wrote:

> You are right. I change the "tomcat-users.xml" as you wrote, it runs.
> Thank!
>
> But, if I open the Tomcat and go into the Manager page. When I click the
> link "manager", I will get error of "HTTP Status 404 - /manager/".
>
> Do you know why?
>
>
>
> Jeff MAURY <[EMAIL PROTECTED]> schrieb: By default, the tomcat
> plugin uses admin as a user name and no password.
> If you don't specify them in your POM, your use modify your
> tomcat-users.xmlfile as follows:
>
>
>
>
>
>
>
>
>
>
>  **
>
>
> Jeff
>
>
>
> On Jan 11, 2008 2:36 PM, Thomas Chang  wrote:
>
> > Now I change the "tomcat-users.xml" as follow, but it's the same.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Jeff MAURY  schrieb: You must have the manager
> > role so supply tomcat as user and password.
> >
> > Regards
> > Jeff
> >
> >
> > On Jan 11, 2008 2:03 PM, Thomas Chang  wrote:
> >
> > > Sure. My "tomcat-users.xml" looks as follow. Is it OK?
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Jeff MAURY  schrieb: You must specify user and
> > > password because the manager application is
> > > protected by default.
> > >
> > > Jeff
> > >
> > >
> > > On Jan 11, 2008 1:27 PM, Thomas Chang  wrote:
> > >
> > > > Hi all,
> > > >
> > > > I try to deploy a WAR to Tomcat using "
> > > > mvn tomcat:deploy -Dmaven.tomcat.url=http://localhost:8585/manager";.
> > But
> > > I
> > > > got error as follow. What's wrong?
> > > >
> > > > [ERROR] BUILD ERROR
> > > > [INFO]
> > > >
> > 
> > > > [INFO] Cannot invoke Tomcat manager
> > > >
> > > > Embedded error: Server returned HTTP response code: 401 for URL:
> > > > http://localhos
> > > > t:8585/manager/deploy?path=%2FTestWeb&war=
> > > > [INFO]
> > > >
> > 
> > > > [INFO] For more information, run Maven with the -e switch
> > > > [INFO]
> > > >
> > 
> > > > [INFO] Total time: 10 seconds
> > > > [INFO] Finished at: Fri Jan 11 13:19:55 CET 2008
> > > > [INFO] Final Memory: 6M/11M
> > > > [INFO]
> > > >
> > 
> > > >
> > > > C:\Projects\eclipse_workspace\TestWeb>
> > > >
> > > >
> > > > -
> > > > Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen
> > > Sie´s
> > > > mit dem  neuen Yahoo! Mail.
> > > >
> > >
> > >
> > >
> > > --
> > > La mélancolie c'est communiste
> > > Tout le monde y a droit de temps en temps
> > > La mélancolie n'est pas capitaliste
> > > C'est même gratuit pour les perdants
> > > La mélancolie c'est pacifiste
> > > On ne lui rentre jamais dedans
> > > La mélancolie oh tu sais ça existe
> > > Elle se prend même avec des gants
> > > La mélancolie c'est pour les syndicalistes
> > > Il faut juste sa carte de permanent
> > >
> > > Miossec (2006)
> > >
> > > http://www.jeffmaury.com
> > > http://riadiscuss.jeffmaury.com
> > >
> > >
> > >
> > > -
> > > Beginnen Sie den Tag mit den neuesten Nachrichten. Machen Sie Yahoo!
> zu
> > > Ihrer Startseite!
> > >
> >
> >
> >
> > --
> > La mélancolie c'est communiste
> > Tout le monde y a droit de temps en temps
> > La mélancolie n'est pas capitaliste
> > C'est même gratuit pour les perdants
> > La mélancolie c'est pacifiste
> > On ne lui rentre jamais dedans
> > La mélancolie oh tu sais ça existe
> > Elle se prend même avec des gants
> > La mélancolie c'est pour les syndicalistes
> > Il faut juste sa carte de permanent
> >
> > Miossec (2006)
> >
> > http://www.jeffmaury.com
> > http://riadiscuss.jeffmaury.com
> >
> >
> >
> > -
> > Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen
> Sie´s
> > mit dem  neuen Yahoo! Mail.
> >
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>
>
>
> -
> Beginnen Sie den Tag mit den neuesten Nachrichten. Machen Sie Yahoo! zu
> Ihrer Startseite!
>



-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancoli

Re: Release plugin for multiple projects with dependencyManagement in parent pom.xml

[Simon Kitching]

 Simon Kitching <[EMAIL PROTECTED]> schrieb:
> I've never really understood why the dependencyManagement section is useful 
> at all.

Just to clarify: I meant using it to define lib versions for child poms, with 
simple stuff like.
  
..
...
...
  

Obviously the ability to define default *configurations* of plugins that child 
modules can reference is very useful.

I guess one valid use for simple version declaration is to ensure that when you 
plan to release a product with version X of a lib, then that exact version is 
used when running the unit tests of every module, rather than just the "minimum 
required version" for that module. Of course for this to be effective, I 
believe the version tags need to be explicit version declarations using 
[2.2] otherwise you are not guaranteed to get that version 
anyway. And if exact versions are forced in the parent pom, it becomes pretty 
useless for release to public repositories.

I have proposed earlier a mechanism for "dumping" the resolved dependencies of 
a module to an external file, and a mechanism for forcing dependency resolution 
to use exact versions from an external file. This could then be used during 
release to solve the above issue; first dump exact dependencies for the 
artifact you want to release and inspect them to make sure they are what you 
expect. Then run the release plugin passing this file as an argument, which 
forces each module in the tree to build and test against exactly those versions.

Regards,
Simon

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Classpath order of dependencies

[Simon Kitching]

 Marco Huber <[EMAIL PROTECTED]> schrieb:
> Hello,
> 
> I have a little problem with the order of my dependencies.
> Depending on the posistion of one dependency I get an error during my tests.
> 
> The first pom snippet result in an NoClassDefFoundError:
> 
> ...
> 
> org.hibernate
> hibernate-validator
> 3.0.0.ga
> 
> 
> 
> org.jboss.embedded
> hibernate-all
> beta2
> 
> ...
> 
> 
> If I change the order of this two dependencies I get not error.
> 
> Is the order in the pom the crucial factor on how the classpath is build 
> in maven? Or is it possible that transient dependencies overwrites 
> direct dependencies?

I believe that Maven calculates the order of libs in the classpath based upon 
the declared dependencies, and that the order of dependency entries in the pom 
doesn't normally matter. I've certainly not had this problem before, and have 
never cared about the order of dependency entries in poms.

My guess is that the pom for hibernate-validator is wrong, and has left out a 
dependency. Of course if that is the case, then a maven project using that pom 
would not build - but perhaps the jboss people don't use maven for building and 
just create poms by hand for maven users.

If you really care about the cause of this, then perhaps run with
  java -verbose:class
to see what class wants what class. I presume a hibernate-validator class will 
be the cause of the problem. Then have a look at whether the missing class is 
in the dependencies of hibernate-validator's pom.

Regards,
Simon

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Error: Cannot invoke Tomcat manager by running tomcat:deploy

[Thomas Chang]

You are right. I change the "tomcat-users.xml" as you wrote, it runs. Thank!

But, if I open the Tomcat and go into the Manager page. When I click the link 
"manager", I will get error of "HTTP Status 404 - /manager/".

Do you know why?



Jeff MAURY <[EMAIL PROTECTED]> schrieb: By default, the tomcat plugin uses 
admin as a user name and no password.
If you don't specify them in your POM, your use modify your
tomcat-users.xmlfile as follows:


 
 
 
 
 
 
 
 
 **


Jeff



On Jan 11, 2008 2:36 PM, Thomas Chang  wrote:

> Now I change the "tomcat-users.xml" as follow, but it's the same.
>
> 
> 
>  
>  
>  
>  
>  
>  
>  
>  
>  
> 
>
>
>
> Jeff MAURY  schrieb: You must have the manager
> role so supply tomcat as user and password.
>
> Regards
> Jeff
>
>
> On Jan 11, 2008 2:03 PM, Thomas Chang  wrote:
>
> > Sure. My "tomcat-users.xml" looks as follow. Is it OK?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Jeff MAURY  schrieb: You must specify user and
> > password because the manager application is
> > protected by default.
> >
> > Jeff
> >
> >
> > On Jan 11, 2008 1:27 PM, Thomas Chang  wrote:
> >
> > > Hi all,
> > >
> > > I try to deploy a WAR to Tomcat using "
> > > mvn tomcat:deploy -Dmaven.tomcat.url=http://localhost:8585/manager";.
> But
> > I
> > > got error as follow. What's wrong?
> > >
> > > [ERROR] BUILD ERROR
> > > [INFO]
> > >
> 
> > > [INFO] Cannot invoke Tomcat manager
> > >
> > > Embedded error: Server returned HTTP response code: 401 for URL:
> > > http://localhos
> > > t:8585/manager/deploy?path=%2FTestWeb&war=
> > > [INFO]
> > >
> 
> > > [INFO] For more information, run Maven with the -e switch
> > > [INFO]
> > >
> 
> > > [INFO] Total time: 10 seconds
> > > [INFO] Finished at: Fri Jan 11 13:19:55 CET 2008
> > > [INFO] Final Memory: 6M/11M
> > > [INFO]
> > >
> 
> > >
> > > C:\Projects\eclipse_workspace\TestWeb>
> > >
> > >
> > > -
> > > Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen
> > Sie´s
> > > mit dem  neuen Yahoo! Mail.
> > >
> >
> >
> >
> > --
> > La mélancolie c'est communiste
> > Tout le monde y a droit de temps en temps
> > La mélancolie n'est pas capitaliste
> > C'est même gratuit pour les perdants
> > La mélancolie c'est pacifiste
> > On ne lui rentre jamais dedans
> > La mélancolie oh tu sais ça existe
> > Elle se prend même avec des gants
> > La mélancolie c'est pour les syndicalistes
> > Il faut juste sa carte de permanent
> >
> > Miossec (2006)
> >
> > http://www.jeffmaury.com
> > http://riadiscuss.jeffmaury.com
> >
> >
> >
> > -
> > Beginnen Sie den Tag mit den neuesten Nachrichten. Machen Sie Yahoo! zu
> > Ihrer Startseite!
> >
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>
>
>
> -
> Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s
> mit dem  neuen Yahoo! Mail.
>



-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com


   
-
Beginnen Sie den Tag mit den neuesten Nachrichten. Machen Sie Yahoo! zu Ihrer 
Startseite!

Re: Release plugin for multiple projects with dependencyManagement in parent pom.xml

[Simon Kitching]

 Aleksandras Skrynikovas <[EMAIL PROTECTED]> schrieb:
> Hi, I've browsed the mailing list for a solution but there doesn't  
> seem to be a clear cut answer.
> 
> Problem: in my app many projects depend on a single parent which uses  
> dependencyManagement to keep
> module versions nice and tidy. When releasing some project with the  
> release plugin, I have to update the
> version of that project in the dependencyManagement element of the  
> parent pom as I understand,
> which leads to a new version of the parent itself, but how can I  
> avoid having to manually increment the parent version
> in all child poms?
> 
> I've read in a couple of places that the release plugin somehow  
> handles this but haven't been able to find any documentation
> of explanation. If there is no pretty solution, what could be the  
> most viable workaround?

Currently, either the updates are done manually in the children, or the 
maven-release-plugin is used, which just does automatically the same tasks that 
could be done by hand. However the maven-release-plugin can only be used if the 
children of the released parent are actually in the same directory tree in the 
version control repository, and if the children are released at the same time 
as the parent.



I've never really understood why the dependencyManagement section is useful at 
all.

Why not just have each module declare the minimum version of a library that 
*it* needs in order to compile and pass the unit tests? 

Why would you ever want to omit the version tag? That just seems to be 
deliberate obfuscation.

When someone uses this module in another project, any library that is the 
target of multiple dependencies just gets automatically resolved as the max 
value of all the versioned references to it. So what version a *user* of this 
module gets depends on the "global needs", but that's a different issue and is 
handled fine by Maven. The pom of the original module, however, is still being 
"true to itself" and honestly declaring exactly what its requirements are.

A pom then only ever updates its  reference to a dependency if it is 
modified in such a way that it needs the new version. Otherwise leave it alone.

This then completely does away with the need to release new versions of parent 
poms just in order to update dependencyManagement versions.

If you're building a final distribution bundle for product, then that *final* 
pom may choose to lock down all the dependencies to specific versions. But that 
is then being done at a *leaf* of the tree, not at the *root* so changes don't 
trigger cascading problems throughout the parent/child chain.

Otherwise, what possible reason is there for requiring a tree of modules to use 
the same dependency version?


And for plugins, IMO every plugin reference in a pom should specify the version 
exactly, and maven should always provide exactly that version (ignoring any 
parent). If that version of the plugin is sufficient to correctly build the 
project, why would you ever want anything different? That is just asking for 
trouble. App libs need dependency resolution because only one copy can be 
present in the classpath of the final app. However that constraint doesn't 
apply to plugins; each module can have its own private version that suits it.

And if dependencyManagement is not used then the parent pom only needs updating 
if it adds functionality that the child actually wants, eg binding a new plugin 
or adding a new report. Children that *want* that functionality should then be 
updated to point to the new parent.

Have I missed something here? [I'm not a maven newbie, but not a pro either. 
Any corrections happily accepted...]

Regards,

Simon

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Error: Cannot invoke Tomcat manager by running tomcat:deploy

[Jeff MAURY]

By default, the tomcat plugin uses admin as a user name and no password.
If you don't specify them in your POM, your use modify your
tomcat-users.xmlfile as follows:


 
 
 
 
 
 
 
 
 **


Jeff



On Jan 11, 2008 2:36 PM, Thomas Chang <[EMAIL PROTECTED]> wrote:

> Now I change the "tomcat-users.xml" as follow, but it's the same.
>
> 
> 
>  
>  
>  
>  
>  
>  
>  
>  
>  
> 
>
>
>
> Jeff MAURY <[EMAIL PROTECTED]> schrieb: You must have the manager
> role so supply tomcat as user and password.
>
> Regards
> Jeff
>
>
> On Jan 11, 2008 2:03 PM, Thomas Chang  wrote:
>
> > Sure. My "tomcat-users.xml" looks as follow. Is it OK?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Jeff MAURY  schrieb: You must specify user and
> > password because the manager application is
> > protected by default.
> >
> > Jeff
> >
> >
> > On Jan 11, 2008 1:27 PM, Thomas Chang  wrote:
> >
> > > Hi all,
> > >
> > > I try to deploy a WAR to Tomcat using "
> > > mvn tomcat:deploy -Dmaven.tomcat.url=http://localhost:8585/manager";.
> But
> > I
> > > got error as follow. What's wrong?
> > >
> > > [ERROR] BUILD ERROR
> > > [INFO]
> > >
> 
> > > [INFO] Cannot invoke Tomcat manager
> > >
> > > Embedded error: Server returned HTTP response code: 401 for URL:
> > > http://localhos
> > > t:8585/manager/deploy?path=%2FTestWeb&war=
> > > [INFO]
> > >
> 
> > > [INFO] For more information, run Maven with the -e switch
> > > [INFO]
> > >
> 
> > > [INFO] Total time: 10 seconds
> > > [INFO] Finished at: Fri Jan 11 13:19:55 CET 2008
> > > [INFO] Final Memory: 6M/11M
> > > [INFO]
> > >
> 
> > >
> > > C:\Projects\eclipse_workspace\TestWeb>
> > >
> > >
> > > -
> > > Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen
> > Sie´s
> > > mit dem  neuen Yahoo! Mail.
> > >
> >
> >
> >
> > --
> > La mélancolie c'est communiste
> > Tout le monde y a droit de temps en temps
> > La mélancolie n'est pas capitaliste
> > C'est même gratuit pour les perdants
> > La mélancolie c'est pacifiste
> > On ne lui rentre jamais dedans
> > La mélancolie oh tu sais ça existe
> > Elle se prend même avec des gants
> > La mélancolie c'est pour les syndicalistes
> > Il faut juste sa carte de permanent
> >
> > Miossec (2006)
> >
> > http://www.jeffmaury.com
> > http://riadiscuss.jeffmaury.com
> >
> >
> >
> > -
> > Beginnen Sie den Tag mit den neuesten Nachrichten. Machen Sie Yahoo! zu
> > Ihrer Startseite!
> >
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>
>
>
> -
> Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s
> mit dem  neuen Yahoo! Mail.
>



-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com

Re: - possible maven defect?

[Marshall Schor]

William Ferguson wrote:

>From what you've said it seems that all your problems are solved by
hardcoding the version in the parent.
Ie don't use the property. Which is standard practice.

I don't know what causes the problem that you are describing, but if it
goes away when you stop punishing yourself with it then that would be a
good option IMHO.
  

Hi William -

The only reason I was, as you say, "punishing myself" with this approach 
was an attempt to follow the DRY philosophy ( 
http://en.wikipedia.org/wiki/Don't_repeat_yourself 
 ), which has 
served us well in the past in reducing maintenance difficulties.  It's 
possible that using maven's Release plugin would alleviate some of this, 
and I'll look into that further.  We do have version info in places I 
don't think Maven would know about (such as in our documentation, and 
inside the names of our Eclipse plugins - which use a slightly different 
syntax than normal maven things.)


Thanks for your help and advice.

-Marshall

William


  

-Original Message-
From: Marshall Schor [mailto:[EMAIL PROTECTED] 
Sent: Friday, 11 January 2008 12:42 PM

To: Maven Users List
Subject: [***POSSIBLE SPAM***] - Re: - possible maven defect? 
- Sender is forged (SPF Fail)


William Ferguson wrote:

My apologies Marshall, not quite sure how it occurred but my answer 
was for an entirely different question by someone else.


To answer your question, Maven seems to be working largely 
  

as designed.

I'm actually surprised that your child POMs could build in any 
scenario if their reference to the parent POM contains a build 
property only found in the parent POM. Because that would 
  

be a circular reference.

  
  
True, but that's not what we're doing, exactly.  In our code, 
the "reference to the parent POM" *is* *"hard-coded", and 
doesn't contain any references such as 
${property-defined-in-parent} for the very reason you describe.

You should really have groupId, artifactId and version 
  
hard-coded in 


all POMs.
  
  
Well, that's the question.  We have groupId and artifactId 
hard-coded. 
The version *is* inheriting from the parent, via a 
${property-defined-in-parent} (*this is working*). 
What's not working is the parent  itself being able to have a 
${property-defined-in-itself} value for the  value.

The standard Maven way of doing things would be to have the version 
hard-coded with a similar value as the version of the parent in the 
child POMs. You would then use the release-plugin to manage the 
increment of the version.


Is there a particular reason that you needed to define ?
   0.7.0
 


  

${uimaj-version}-incubating-SNAPSHOT
release-version> I think you need to reconsider your 
  
project version. 


I think you want it as 0.7.0-SNAPSHOT.
"incubating" would seem to belong as part of an artifactId 
  
or assembly 


annotation (see the asembly plugin).
I hope this helps.
  
  
Because we are a project in the Apache Incubator, our version 
names include the word "incubator" in them to insure that 
users realize they are working with an incubating project.


The reason we define version numbers this way is that we have 
some conflicting naming standards - some require 
0.7.0-incubating-SNAPSHOT, while others (Eclipse plugins, in 
particular) want 0.7.0.incubating-SNAPSHOT (not the "." 
instead of the '-' in front of the word "incubating".


So we thought that we could put all this kind of stuff in one 
common, factored out, "parent", and be done with it :-)


-Marshall


William

  
  

-Original Message-
From: Marshall Schor [mailto:[EMAIL PROTECTED]
Sent: Friday, 11 January 2008 10:06 AM
To: Maven Users List
Subject: [***POSSIBLE SPAM***] - Re: - possible maven defect? 
- Sender is forged (SPF Fail)


William Ferguson wrote:



Marshall,

the standard solution for what you are attempting would be to 
install/deploy those libraries "not managed by Maven" 
  
into your own 


repository or corporate repository and then you *would*
  
  

have access to



them.

William
  
  
  

Hi William -

I must have not communicated well.  All of the libraries 

are manged 

by Maven.  The situation where the failure occurs is like 

a startup - 

when a user first checks out the set of projects (having 

child POMs) 

and the main parent POM, then tries to do a "mvn install" on the 
parent.


(I'm assuming here that they check out a development 

level, where the 


components have not been installed to any repository, yet).

This first "mvn install" is intended to install of the 

parts into the 

local repository, but it only works if you don't use ${ ... } 
variable substitution in the way I was trying to use it.


My question is whether this limitation on use of variable 
su

Re: Error: Cannot invoke Tomcat manager by running tomcat:deploy

[Thomas Chang]

Now I change the "tomcat-users.xml" as follow, but it's the same.



  
  
  
  
  
  
  
  
  




Jeff MAURY <[EMAIL PROTECTED]> schrieb: You must have the manager role so 
supply tomcat as user and password.

Regards
Jeff


On Jan 11, 2008 2:03 PM, Thomas Chang  wrote:

> Sure. My "tomcat-users.xml" looks as follow. Is it OK?
>
> 
> 
>  
>  
>  
>  
>  
>  
>  
> 
>
>
> Jeff MAURY  schrieb: You must specify user and
> password because the manager application is
> protected by default.
>
> Jeff
>
>
> On Jan 11, 2008 1:27 PM, Thomas Chang  wrote:
>
> > Hi all,
> >
> > I try to deploy a WAR to Tomcat using "
> > mvn tomcat:deploy -Dmaven.tomcat.url=http://localhost:8585/manager";. But
> I
> > got error as follow. What's wrong?
> >
> > [ERROR] BUILD ERROR
> > [INFO]
> > 
> > [INFO] Cannot invoke Tomcat manager
> >
> > Embedded error: Server returned HTTP response code: 401 for URL:
> > http://localhos
> > t:8585/manager/deploy?path=%2FTestWeb&war=
> > [INFO]
> > 
> > [INFO] For more information, run Maven with the -e switch
> > [INFO]
> > 
> > [INFO] Total time: 10 seconds
> > [INFO] Finished at: Fri Jan 11 13:19:55 CET 2008
> > [INFO] Final Memory: 6M/11M
> > [INFO]
> > 
> >
> > C:\Projects\eclipse_workspace\TestWeb>
> >
> >
> > -
> > Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen
> Sie´s
> > mit dem  neuen Yahoo! Mail.
> >
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>
>
>
> -
> Beginnen Sie den Tag mit den neuesten Nachrichten. Machen Sie Yahoo! zu
> Ihrer Startseite!
>



-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com


   
-
Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit 
dem  neuen Yahoo! Mail. 

Re: Error: Cannot invoke Tomcat manager by running tomcat:deploy

[Jeff MAURY]

You must have the manager role so supply tomcat as user and password.

Regards
Jeff


On Jan 11, 2008 2:03 PM, Thomas Chang <[EMAIL PROTECTED]> wrote:

> Sure. My "tomcat-users.xml" looks as follow. Is it OK?
>
> 
> 
>  
>  
>  
>  
>  
>  
>  
> 
>
>
> Jeff MAURY <[EMAIL PROTECTED]> schrieb: You must specify user and
> password because the manager application is
> protected by default.
>
> Jeff
>
>
> On Jan 11, 2008 1:27 PM, Thomas Chang  wrote:
>
> > Hi all,
> >
> > I try to deploy a WAR to Tomcat using "
> > mvn tomcat:deploy -Dmaven.tomcat.url=http://localhost:8585/manager";. But
> I
> > got error as follow. What's wrong?
> >
> > [ERROR] BUILD ERROR
> > [INFO]
> > 
> > [INFO] Cannot invoke Tomcat manager
> >
> > Embedded error: Server returned HTTP response code: 401 for URL:
> > http://localhos
> > t:8585/manager/deploy?path=%2FTestWeb&war=
> > [INFO]
> > 
> > [INFO] For more information, run Maven with the -e switch
> > [INFO]
> > 
> > [INFO] Total time: 10 seconds
> > [INFO] Finished at: Fri Jan 11 13:19:55 CET 2008
> > [INFO] Final Memory: 6M/11M
> > [INFO]
> > 
> >
> > C:\Projects\eclipse_workspace\TestWeb>
> >
> >
> > -
> > Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen
> Sie´s
> > mit dem  neuen Yahoo! Mail.
> >
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>
>
>
> -
> Beginnen Sie den Tag mit den neuesten Nachrichten. Machen Sie Yahoo! zu
> Ihrer Startseite!
>



-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com

Re: Error: Cannot invoke Tomcat manager by running tomcat:deploy

[Thomas Chang]

Sure. My "tomcat-users.xml" looks as follow. Is it OK?



  
  
  
  
  
  
  



Jeff MAURY <[EMAIL PROTECTED]> schrieb: You must specify user and password 
because the manager application is
protected by default.

Jeff


On Jan 11, 2008 1:27 PM, Thomas Chang  wrote:

> Hi all,
>
> I try to deploy a WAR to Tomcat using "
> mvn tomcat:deploy -Dmaven.tomcat.url=http://localhost:8585/manager";. But I
> got error as follow. What's wrong?
>
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Cannot invoke Tomcat manager
>
> Embedded error: Server returned HTTP response code: 401 for URL:
> http://localhos
> t:8585/manager/deploy?path=%2FTestWeb&war=
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: 10 seconds
> [INFO] Finished at: Fri Jan 11 13:19:55 CET 2008
> [INFO] Final Memory: 6M/11M
> [INFO]
> 
>
> C:\Projects\eclipse_workspace\TestWeb>
>
>
> -
> Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s
> mit dem  neuen Yahoo! Mail.
>



-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com


   
-
Beginnen Sie den Tag mit den neuesten Nachrichten. Machen Sie Yahoo! zu Ihrer 
Startseite!

Re: Error: Cannot invoke Tomcat manager by running tomcat:deploy

[Jeff MAURY]

You must specify user and password because the manager application is
protected by default.

Jeff


On Jan 11, 2008 1:27 PM, Thomas Chang <[EMAIL PROTECTED]> wrote:

> Hi all,
>
> I try to deploy a WAR to Tomcat using "
> mvn tomcat:deploy -Dmaven.tomcat.url=http://localhost:8585/manager";. But I
> got error as follow. What's wrong?
>
> [ERROR] BUILD ERROR
> [INFO]
> 
> [INFO] Cannot invoke Tomcat manager
>
> Embedded error: Server returned HTTP response code: 401 for URL:
> http://localhos
> t:8585/manager/deploy?path=%2FTestWeb&war=
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: 10 seconds
> [INFO] Finished at: Fri Jan 11 13:19:55 CET 2008
> [INFO] Final Memory: 6M/11M
> [INFO]
> 
>
> C:\Projects\eclipse_workspace\TestWeb>
>
>
> -
> Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s
> mit dem  neuen Yahoo! Mail.
>



-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com

Release plugin for multiple projects with dependencyManagement in parent pom.xml

[Aleksandras Skrynikovas]

Hi, I've browsed the mailing list for a solution but there doesn't  
seem to be a clear cut answer.


Problem: in my app many projects depend on a single parent which uses  
dependencyManagement to keep
module versions nice and tidy. When releasing some project with the  
release plugin, I have to update the
version of that project in the dependencyManagement element of the  
parent pom as I understand,
which leads to a new version of the parent itself, but how can I  
avoid having to manually increment the parent version

in all child poms?

I've read in a couple of places that the release plugin somehow  
handles this but haven't been able to find any documentation
of explanation. If there is no pretty solution, what could be the  
most viable workaround?


-Alex


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

regarding creating a project using maven

[Praphul Chalasani]

When I check for mvn -version  ,it has displayed the version(Maven version:
2.0).

 

When I ran the following command , I am getting the error .

 

F:\work2> mvn archetype:create -DgroupId=com.mycompany.app
-DartifactId=my-app

[INFO] Scanning for projects...

[INFO] Searching repository for plugin with prefix: 'archetype'.

[INFO] artifact org.apache.maven.plugins:maven-archetype-plugin: checking
for up

dates from central

[WARNING] repository metadata for: 'artifact
org.apache.maven.plugins:maven-archetype-plugin' could not be retrieved from
repository: central due to an error: Error transferring file

[INFO] Repository 'central' will be blacklisted

[INFO]


[ERROR] BUILD ERROR

[INFO]


[INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not
exist or no valid version could be found

[INFO]


[INFO] For more information, run Maven with the -e switch

[INFO]


[INFO] Total time: 36 seconds

[INFO] Finished at: Thu Jan 10 18:28:03 GMT+05:30 2008

[INFO] Final Memory: 1M/2M

[INFO]


 

 

Can you suggest me the solution.

 

 

Thanks®ards,

Praphul.

 


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.

Error: Cannot invoke Tomcat manager by running tomcat:deploy

[Thomas Chang]

Hi all,

I try to deploy a WAR to Tomcat using "
mvn tomcat:deploy -Dmaven.tomcat.url=http://localhost:8585/manager";. But I got 
error as follow. What's wrong?

[ERROR] BUILD ERROR
[INFO] 
[INFO] Cannot invoke Tomcat manager

Embedded error: Server returned HTTP response code: 401 for URL: http://localhos
t:8585/manager/deploy?path=%2FTestWeb&war=
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 10 seconds
[INFO] Finished at: Fri Jan 11 13:19:55 CET 2008
[INFO] Final Memory: 6M/11M
[INFO] 

C:\Projects\eclipse_workspace\TestWeb>

   
-
Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit 
dem  neuen Yahoo! Mail. 

Re: Excluding files from JAR

[amit kumar]

Hi,
Sorry for incomplete information about the problem. I used  task ,
and it is working now.
Did not try the snapshot jar plugin yet.

Thanks and regards,
Amit Kumar

On Jan 11, 2008 5:46 AM, Wayne Fay <[EMAIL PROTECTED]> wrote:

> I don't think Simon is telling you to use Ant's jar command -- instead
> he is suggesting that you use Ant's  task to physically remove
> the unwanted files out of /target/ before allowing Maven to do its own
> packaging step. (Right, Simon?) You would probably want to bind this
> to prepare-package as you have done below.
>
> Here's the Ant Delete task page:
> http://ant.apache.org/manual/CoreTasks/delete.html
>
> Also, you should be using -X to get full debugging information. And if
> it "doesn't work" this time, please reply back with a lot more details
> about what exactly happened when you tried this eg what errors were
> reported, what seemed to happen, etc. Simply saying "it didn't work"
> tells us absolutely nothing about what actually happened vs what you
> were expecting etc.
>
> Wayne
>
> On 1/10/08, amit kumar <[EMAIL PROTECTED]> wrote:
> > Hi Simon,
> > Being totally unaware of ANT although I tried but of no use.
> > I used this with google's help
> >
> >  
> >maven-antrun-plugin
> >
> >  
> >prepare-package
> >
> > 
> > 
> >  > excludes="*.xsd,*.xsb" />
> > 
> > 
> >
> >
> >  run
> >
> >  
> >
> >  
> >
> >
> > Where am I lacking?
> >
> >
> > Regards,
> > Amit
> >
> > On Jan 10, 2008 9:45 PM, amit kumar <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> > > I have downloaded the patches from the link mentioned by you. But I
> don't
> > > know how to apply them.
> > >
> > > regards,
> > > Amit
> > >
> > >
> > > On Jan 10, 2008 6:29 PM, Olivier Lamy < [EMAIL PROTECTED]> wrote:
> > >
> > > > Hi,
> > > > No you don't miss something here.
> > > > It's a know issue [1] and it's fixed in trunk.
> > > > You can try last snapshot to test the fix.
> > > >
> > > > --
> > > > Olivier
> > > > [1] http://jira.codehaus.org/browse/MJAR-30
> > > >
> > > > 2008/1/10, amit kumar < [EMAIL PROTECTED]>:
> > > > > HI,
> > > > > Just like WAR can I as well exclude some files from JAR builds as
> > > > well?
> > > > >
> > > > > I have used this, but not working.
> > > > >
> > > > >   
> > > > > 
> > > > >   org.apache.maven.plugins
> > > > >   maven-jar-plugin
> > > > >   2.1
> > > > >   
> > > > >
> > > > >   
> > > > >  jar
> > > > > 
> > > > >
> > > > > 
> > > > > 
> > > > > **/*.xsd
> > > > >src/schema/xsd
> > > > > 
> > > > >   
> > > > >
> > > > > Am I missing something?
> > > > >
> > > > > Amit
> > > > >
> > > >
> > > >
> -
> > > > 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]
>
>

Classpath order of dependencies

[Marco Huber]

Hello,

I have a little problem with the order of my dependencies.
Depending on the posistion of one dependency I get an error during my tests.

The first pom snippet result in an NoClassDefFoundError:

   ...
   
   org.hibernate
   hibernate-validator
   3.0.0.ga
   

   
   org.jboss.embedded
   hibernate-all
   beta2
   
   ...


If I change the order of this two dependencies I get not error.

Is the order in the pom the crucial factor on how the classpath is build 
in maven? Or is it possible that transient dependencies overwrites 
direct dependencies?


Thank you for your help

Marco

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to deploy WAR to Tomcat with MAVEN2?

[ben short]

Or this one..

http://mojo.codehaus.org/tomcat-maven-plugin/introduction.html

2008/1/11 Jeff MAURY <[EMAIL PROTECTED]>:
> You can use the cargo Maven plugin (http://cargo.codehaus.org).
>
> Jeff
>
>
>
> On Jan 11, 2008 9:49 AM, Thomas Chang <[EMAIL PROTECTED]> wrote:
>
> >
> > Hi all,
> >
> > I use maven2. I wonder if there is a mvn-command which can
> > deploy/reploy/delete the war to/from Tomcat?
> >
> > Regards
> >
> >
> >
> > -
> > Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern.
>
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to deploy WAR to Tomcat with MAVEN2?

[Jeff MAURY]

You can use the cargo Maven plugin (http://cargo.codehaus.org).

Jeff


On Jan 11, 2008 9:49 AM, Thomas Chang <[EMAIL PROTECTED]> wrote:

>
> Hi all,
>
> I use maven2. I wonder if there is a mvn-command which can
> deploy/reploy/delete the war to/from Tomcat?
>
> Regards
>
>
>
> -
> Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern.




-- 
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent

Miossec (2006)

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com

How to deploy WAR to Tomcat with MAVEN2?

[Thomas Chang]

Hi all,

I use maven2. I wonder if there is a mvn-command which can deploy/reploy/delete 
the war to/from Tomcat?

Regards


   
-
Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern.