[ANN] Maven Doxia Tools shared component 1.1 Released

[Dennis Lundberg]

The Maven team is pleased to announce the release of the Maven Doxia
Tools shared component, version 1.1

This shared component has some utilities that are useful when
integrating Doxia in Maven, mainly for site generation and report
creation. The main entry point is the SiteTool Plexus component.

http://maven.apache.org/shared/maven-doxia-tools/


Release Notes - Maven Shared Components - Version  maven-doxia-tools 1.1


** Bug
* [MSHARED-102] - The modules menu is not inherited to sub-modules
* [MSHARED-116] - If module has no site.xml then the decoration
model is set equal to the parent instead of inheriting from it
* [MSHARED-117] - Parent menu item is not inherited if no url in parent



** Task
* [MSHARED-115] - Upgrade to doxia 1.1.1




Enjoy,

-The Maven team


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

[ANN] Maven JAR Plugin 2.3 Released

[Dennis Lundberg]

The Maven team is pleased to announce the release of the Maven JAR
Plugin, version 2.3

This plugin provides the capability to build jars. Signing is deprecated
starting with this version. Please use Maven Jarsigner Plugin if you
need to sign JARs.

http://maven.apache.org/plugins/maven-jar-plugin/

You should specify the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-jar-plugin
 2.3



Release Notes - Maven 2.x JAR Plugin - Version 2.3


** Bug
* [MJAR-28] - Using the jar plugin with addClasspath and snapshots
can create manifest classpath with incorrect jar versions
* [MJAR-105] - Regression: Build fails for an empty main jar with 2.2
* [MJAR-118] - Upgrade maven-archiver dependency to 2.4



** Task
* [MJAR-127] - Deprecate jarsigner related goals in favor of
dedicated maven-jarsigner-plugin




Enjoy,

-The Maven team


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

[ANN] APT Maven Plugin 1.0-alpha-3 Released

[Benjamin Bentmann]

The Mojo team is pleased to announce the release of the APT Maven
Plugin, version 1.0-alpha-3.

   http://mojo.codehaus.org/apt-maven-plugin/

The major change in this release is a fix to the embedded invocation of 
APT to enable interoperability with Maven 3.


To get this update, simply specify the version in the plugin
configuration of your POM:

   
 org.codehaus.mojo
 apt-maven-plugin
 1.0-alpha-3
   


Release Notes - Maven 2.x APT Plugin - Version 1.0-alpha-3

** Bug
 * [MOJO-1458] - Fix non-forked APT invocation to not hack system 
class loader


** Improvement
 * [MOJO-] - Uplift code from 1.4 to 1.5


Enjoy,


The Mojo Team

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

Re: Subject: Adding version numbers to artifacts

[Anders Hammar]

Looks to me that what you're doing is a release build, not a nightly build
(at least not what I associate with the "nightly build" expression". You
should take a look at the release plugin:
http://maven.apache.org/plugins/maven-release-plugin/

It will release your project including updating the version correctly and
set a label in your scm.

/Anders

On Wed, Nov 25, 2009 at 05:29, Jeff French  wrote:

>
> I'm trying to replicate our Maven-1 nightly build/deploy process with
> Maven-2. Basically, a build server passes the current version to a maven
> process that then produces artifacts with that version number appended.
>
> Since the build occurs on the same machine as the repo, I'm guessing I can
> perform an 'install' instead of a 'deploy'. I've found that this:
>
>mvn -Dversion=1.1.1 install
>
> will produce numbered artifacts if the pom contains these snippets:
>
>
>...
>${version}
>
>
>1.1-SNAPSHOT
>
>...
>
>
> The problem is the reposed .pom files contain the ${version} string instead
> of the defined version (1.1.1). Is there any way for the deployed pom to be
> the result of filtering the build pom with the defined system property?  Or
> more importantly, is there a better way to go about what I'm trying to
> achieve?
>
> Thanks for any pointers.
>
> Jeff
> --
> View this message in context:
> http://old.nabble.com/Subject%3A-Adding-version-numbers-to-artifacts-tp26507407p26507407.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Subject: Adding version numbers to artifacts

[Jeff French]

I'm trying to replicate our Maven-1 nightly build/deploy process with
Maven-2. Basically, a build server passes the current version to a maven
process that then produces artifacts with that version number appended.

Since the build occurs on the same machine as the repo, I'm guessing I can
perform an 'install' instead of a 'deploy'. I've found that this:

mvn -Dversion=1.1.1 install

will produce numbered artifacts if the pom contains these snippets:


...
${version}


1.1-SNAPSHOT

...


The problem is the reposed .pom files contain the ${version} string instead
of the defined version (1.1.1). Is there any way for the deployed pom to be
the result of filtering the build pom with the defined system property?  Or
more importantly, is there a better way to go about what I'm trying to
achieve?

Thanks for any pointers.

 Jeff
-- 
View this message in context: 
http://old.nabble.com/Subject%3A-Adding-version-numbers-to-artifacts-tp26507407p26507407.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

RE: merging testng into surefire..

[Martin Gainty]

i managed to work thru the integration issues 

this is the specific error
java.util.MissingResourceException: Can't find bundle for base name 
org.apache.maven.surefire.surefire, locale en_US

Thanks,
Martin Gainty 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




> From: mickknut...@gmail.com
> Date: Tue, 24 Nov 2009 07:55:38 -0500
> Subject: Re: merging testng into surefire..
> To: users@maven.apache.org
> 
> I do not understand the problem space at this point. What PROVIDER code
> issue are you having?
> 
> ---
> Thank You…
> 
> Mick Knutson, President
> 
> BASE Logic, Inc.
> Enterprise Architecture, Design, Mentoring & Agile Consulting
> p. (866) BLiNC-411: (254-6241-1)
> f. (415) 685-4233
> 
> Website: http://baselogic.com
> Linked IN: http://linkedin.com/in/mickknutson
> Vacation Rental: http://tahoe.baselogic.com
> ---
> 
> 
> 
> On Tue, Nov 24, 2009 at 7:47 AM, Martin Gainty  wrote:
> 
> >
> > this would work only IF the providers integrated with surefire properly
> > which is not the case
> > the side effect is that integrating a provider such as testng (which only
> > works with surefire last time i checked)
> > creates integration exceptions
> > NONE of these integration exceptions would occur IF the testng codebase was
> > merged into surefire
> > any integration exceptions would be discovered in the surefire packaging
> > phase before deployment
> >
> > comments?
> > Martin Gainty
> > __
> > Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
> >
> > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
> > Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> > dient lediglich dem Austausch von Informationen und entfaltet keine
> > rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> > E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
> > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
> > destinataire prévu, nous te demandons avec bonté que pour satisfaire
> > informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
> > de ceci est interdite. Ce message sert à l'information seulement et n'aura
> > pas n'importe quel effet légalement obligatoire. Étant donné que les email
> > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
> > aucune responsabilité pour le contenu fourni.
> >
> >
> >
> >
> > > From: mickknut...@gmail.com
> > > Date: Mon, 23 Nov 2009 18:57:58 -0800
> > > Subject: Re: merging testng into surefire..
> > > To: users@maven.apache.org
> > >
> > > I do not think I fully understand the different 'Provider' concept, but
> > if
> > > you are looking to run different types of tests in 1 suite, then you
> > could
> > > create a separate PROFILE in Maven, then your suite could have something
> > > like:
> > >
> > > http://testng.org/testng-1.0.dtd";>
> > > 
> > >
> > > **
> > > http://localhost:8889/webapp/"; /
> > >
> > > 
> > > 
> > > 
> > > 
> > > 
> > > ...
> > >
> > > Or you could hard code them per test section:
> > >
> > > 
> > > * *
> > > 
> > > 
> > > 
> > > 
> > >
> > > 
> > > * *
> > > 
> > > 
> > > 
> > > 
> > >
> > > Is this what you mean?
> > >
> > >
> > > ---
> > > Thank You…
> > >
> > > Mick Knutson, President
> > >
> > > BASE Logic, Inc.
> > > Enterprise Architecture, Design, Mentoring & Agile Consulting
> > > p. (866) BLiNC-411: (254-6241-1)
> > > f. (415) 685-4233
> > >
> > > Website: http://baselogic.com
> > > Linked IN: http://linkedin.com/in/mickknutson
> > > Vacation Rental: http://tahoe.baselogic.com
> > > ---
> > >
> > >
> > >
> > > On Mon, Nov 23, 2009 at 6:46 PM, Martin Gainty 
> > wrote:
> > >
> > > >
> > > > i understand paul's assertion for a separate provider suite
>

Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

[Wayne Fay]

> My adversion to running 'mvn clean install' is just that I'd prefer not to 
> have
> to build and install something just to be able to examine its dependencies.

This is merely a preference, right?

> under various 3rd party dependency scenarios. It seems backwards to me to have
> to first build and install something only to be able to examine some abstract
> properties of it, so that's my main blocker.

This is merely a mental blocker, right?

> If there is some more maven-ey way to go about this stuff, I'm all for it.

Run mvn clean install... that is the "maven-ey way to go about this
stuff." As Brian already said "running tree on a not-yet compiled or
installed project is an edge case."

Wayne

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

Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

[Jonathan Gold]

Jamie --

My adversion to running 'mvn clean install' is just that I'd prefer not to have
to build and install something just to be able to examine its dependencies.
Indeed, this problem came up originally as I was configuring a new project and
trying to do sort of a dry run to understand where things would be coming from
under various 3rd party dependency scenarios. It seems backwards to me to have
to first build and install something only to be able to examine some abstract
properties of it, so that's my main blocker.

I'm finding this same pattern (need to activate the reactor) with the eclipse
plugin, which also seems odd to me, since I effectively have to install a
project before I can add it to an eclipse workspace where, presumably, I would
actually be doing the work to get it to a point where there is something to
install.

If there is some more maven-ey way to go about this stuff, I'm all for it.

jon

On Fri, Nov 20, 2009 at 01:42:27PM -0800, Jamie Whitehouse wrote:
> Yes, thanks for clarifying Brian.
> 
> Jon, I'm still wondering why you're adverse to running mvn clean install? 
> 
> -Original Message-
> From: Jonathan Gold [mailto:jgold...@gmail.com] 
> Sent: Friday, November 20, 2009 4:26 PM
> To: users@maven.apache.org
> Subject: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?
> 
> Brian --
> 
> Thanks for this. I did run the combo 'mvn compile dependency:tree' as you 
> mention below, and it works. What I'm taking away from this is that 
> dependency:tree will work if it's part of the *same* mvn invocation as 
> something like compile, which forces maven to do the resolution of the local 
> workspace.
> Doing 'mvn compile' and then 'mvn dependency:tree' thus does not work.
> 
> As a new user, this was (and still is) a bit bizarre, but I'm happy to know 
> how to get it to work. 
> 
> Thanks!
> 
> jon
> 
> On Fri, Nov 20, 2009 at 03:54:11PM -0500, Brian Fox wrote:
> > This isn't exactly true. First, lets take a look at the stack trace:
> > 
> > --
> > 1 required artifact is missing.
> > 
> > for artifact:
> >   com.example:mod_b:jar:1.0
> > 
> > from the specified remote repositories:
> >   mynexus (http://192.168.101.21:8081/nexus/content/groups/public)
> > 
> > 
> > at 
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTra
> > nsitively(DefaultArtifactResolver.java:360)
> > at 
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTra
> > nsitively(DefaultArtifactResolver.java:304)
> > at 
> > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDepende
> > ncies(DefaultPluginManager.java:1499)
> > at 
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> > nManager.java:442)
> > at 
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> > ultLifecycleExecutor.java:694)
> > ... 17 more
> > 
> > 
> > Notice this is all core code. It's trying to resolve the dependencies 
> > prior to invoking the plugin. As I mentioned earlier in the thread, 
> > the plugin sets @requiresDependencyResolution test which tells Maven 
> > to resolve the test scope (which means everything) before invoking the 
> > plugin.
> > 
> > If you only run "mvn dependency:tree" there are no references to the 
> > other projects in the reactor for Maven to find and use. Try running 
> > "mvn compile dependency:tree: and you'll see that it does in fact 
> > work. This is just a side effect of how maven 2.x does the resolution.
> > 
> > Could we rewrite the dependency tree goal to completely work around 
> > this? Probably, but it would mean duplicating tons of core logic to 
> > make the resolution work in all cases and running tree on a not-yet 
> > compiled or installed project is an edge case imo.
> > 
> > 
> > 2009/11/19 Jamie Whitehouse :
> > > Many of the dependency plugin goals are reactor aware, but 
> > > dependency:tree isn't.  I'm not too sure why, but you could search the 
> > > issue tracker and if there's no issue for this file one.
> > >
> > > -Original Message-
> > > From: Jonathan Gold [mailto:jgold...@gmail.com]
> > > Sent: Thursday, November 19, 2009 3:00 PM
> > > To: users@maven.apache.org
> > > Subject: Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' 
> > > works?
> > >
> > > Jamie --
> > >
> > > Thanks for trying it out, and for the explanation. This makes sense in 
> > > terms of why things are happening, so that's nice.
> > >
> > > I'm not familiar with the dependency plugin developers (are you one?), 
> > > and wonder if having the dependency plugin be reactor-aware is something 
> > > they would consider? Perhaps its an old tired discussion and the decision 
> > > to build that plugin the way it is is said and done.
> > >
> > > Thanks for your help!
> > >
> > > jon
> > >
> > > On Thu, Nov 19, 2009 at 11:43:33AM -0800, Jamie Whitehouse wrote:
> > >> What maven commands did you issue to test this?
> > >>
> >

Re: mvn site

[Dennis Lundberg]

Richard Bibb wrote:
> Appologies if I'm in the wrong part of the forum.
> 
> If I have a favicon.ico file that I want to be included in my site
> distribution doesn anyone know where I should put it? site/resources/Images
> doesn't seem to work

/src/site/resources/favicon.ico is the correct place for it.

-- 
Dennis Lundberg

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

[ANN] Maven Changes Plugin 2.2 Released

[Dennis Lundberg]

The Maven team is pleased to announce the release of the Maven Changes
Plugin, version 2.2

This plugin is used to inform your users of the changes that have
occured between different releases of your project. The plugin can
extract these changes, either from a changes.xml file or from the JIRA
issue management system, and present them as a report. You also have the
option of creating a release announcement and even sending this via
email to your users.

http://maven.apache.org/plugins/maven-changes-plugin/

You should specify the version in your project's plugin configuration:


 org.apache.maven.plugins
 maven-changes-plugin
 2.2



Release Notes - Maven 2.x Changes Plugin - Version 2.2


** Bug
* [MCHANGES-116] - FileNotFoundException and NullPointerException if
src/changes/changes.xml is missing
* [MCHANGES-143] - Specifying sender email address using
fromDeveloperId is no longer working.
* [MCHANGES-147] - MavenProject object not initialize due to
mispelling into the declaration
* [MCHANGES-156] - An empty table is shown for a  which
doesn't have any  in it
* [MCHANGES-166] - Problem with issueLinkTemplatePerSystem
* [MCHANGES-185] - Output special characters like < and > in the
JIRA report

** Improvement
* [MCHANGES-177] - Allow specification of report columns in Trac report
* [MCHANGES-178] - Make the url parameter non-required
* [MCHANGES-179] - Improve the announcement template reference
documentation
* [MCHANGES-181] - Add Swedish translation
* [MCHANGES-183] - Add French translations
* [MCHANGES-184] - Add German translation for the Trac report

** New Feature
* [MCHANGES-161] - Add limited properties interpolation

** Task
* [MCHANGES-157] - Update to Doxia 1.0
* [MCHANGES-158] - Document how to use the XML schema for changes.xml
* [MCHANGES-170] - Review the Doxia Sink calls
* [MCHANGES-171] - Fix Modello build warning
* [MCHANGES-180] - Update to Maven Reporting Impl 2.0.4.3


Enjoy,

-The Maven team


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

Re: MAVEN2 PROJECT DEPLOYMENT FAILING....

[Wayne Fay]

>> I'm trying to build and deploy a maven2 project via hudson, and the build
>> works fine, but the deployment is failing... It's trying to deploy to a
>> location that's not specified in  in my parent
>> pom.xml... Does anyone know why this is happening...??? If someone could

Try this to see what your pom looks like:
mvn -e -cpu -B -P ci,jws,code-drop help:effective-pom

Wayne

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

Re: yelling not needed

[Mick Knutson]

ok, I will speak softly for only 1 observation I have:

file:///*/*home/COMPANY/repository/maven2

there should be 4 (/) slashes and no (*) asterisks or other odd characters.
At least that is how I use this currently

I also use:

file:///C:/Temp/sites/${pom.version}


---
Thank You…

Mick Knutson, President

BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring & Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233

Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---



On Tue, Nov 24, 2009 at 10:31 AM, Christopher Styles wrote:

> Also, I forgot to added the commands I'm trying to run via hudson...
>
> mvn -e -cpu -B -P ci,jws,code-drop clean install
> mvn -e -B -P ci,jws,code-drop -DpreparationGoals="clean install"
> release:prepare
> mvn -e -cpu -B -P ci,jws,code-drop release:perform
>
> Thanks
>
>
> On Tue, Nov 24, 2009 at 10:23 AM, Christopher Styles  >wrote:
>
> > Hi,
> >
> > I'm trying to build and deploy a maven2 project via hudson, and the build
> > works fine, but the deployment is failing... It's trying to deploy to a
> > location that's not specified in  in my parent
> > pom.xml... Does anyone know why this is happening...??? If someone could
> > please provide insight as to why this is happening and what I need to do
> to
> > fix it I'd really appreciate it...
> >
> >
> > THIS IS WHERE I WANT TO UPLOAD (DEPLOY) MY POM FILE LOCALLY
> >
> > 
> > 
> > archiva.internal
> > Internal Release Repository
> > *file:///home//repository/maven2*/
> > 
> > 
> > archiva.snapshots
> > Internal Snapshot Repository
> > *file:///home//repository/maven2*/
> > false
> > 
> > 
> > arizona.site
> > *file:///home//repository/maven2*/
> > 
> > 
> >
> >
> > THIS IS WHERE IT'S TRYING TO DEPLOY (ERROR)
> >
> > WARNING: No credentials available for the 'Repository Archiva Managed
> > Internal Repository' authentication realm at  [INFO] Nov
> 24,
> > 2009 9:26:28 AM org.apache.commons.httpclient.HttpMethodBase
> > processAuthenticationResponse [INFO] WARNING: No credentials available
> for
> > the 'Repository Archiva Managed Internal Repository' authentication realm
> at
> >  [INFO] Nov 24, 2009 9:26:28 AM
> > org.apache.commons.httpclient.HttpMethodBase
> processAuthenticationResponse
> > [INFO] WARNING: No credentials available for the 'Repository Archiva
> Managed
> > Internal Repository' authentication realm at  [INFO]
> [INFO]
> > 
> > [INFO] [ERROR] BUILD ERROR
> > [INFO] [INFO]
> > 
> > [INFO] [INFO] Error deploying artifact: Failed to transfer file:
> > http://
> :8080/archiva/repository/internal/com/statcom/pfl/statcom-pfl/
> 1.1.0.5/statcom-pfl-1.1.0.5.pom %3csvnrepository%3e:8080/archiva/repository/internal/com/statcom/pfl/statcom-pfl/
> 1.1.0.5/statcom-pfl-1.1.0.5.pom>.
> > Return code is: 401 Unauthorized [INFO] [INFO] [INFO]
> >
>

Re: MAVEN2 PROJECT DEPLOYMENT FAILING....

[Christopher Styles]

Also, I forgot to added the commands I'm trying to run via hudson...

mvn -e -cpu -B -P ci,jws,code-drop clean install
mvn -e -B -P ci,jws,code-drop -DpreparationGoals="clean install"
release:prepare
mvn -e -cpu -B -P ci,jws,code-drop release:perform

Thanks


On Tue, Nov 24, 2009 at 10:23 AM, Christopher Styles wrote:

> Hi,
>
> I'm trying to build and deploy a maven2 project via hudson, and the build
> works fine, but the deployment is failing... It's trying to deploy to a
> location that's not specified in  in my parent
> pom.xml... Does anyone know why this is happening...??? If someone could
> please provide insight as to why this is happening and what I need to do to
> fix it I'd really appreciate it...
>
>
> THIS IS WHERE I WANT TO UPLOAD (DEPLOY) MY POM FILE LOCALLY
>
> 
> 
> archiva.internal
> Internal Release Repository
> *file:///home//repository/maven2*/
> 
> 
> archiva.snapshots
> Internal Snapshot Repository
> *file:///home//repository/maven2*/
> false
> 
> 
> arizona.site
> *file:///home//repository/maven2*/
> 
> 
>
>
> THIS IS WHERE IT'S TRYING TO DEPLOY (ERROR)
>
> WARNING: No credentials available for the 'Repository Archiva Managed
> Internal Repository' authentication realm at  [INFO] Nov 24,
> 2009 9:26:28 AM org.apache.commons.httpclient.HttpMethodBase
> processAuthenticationResponse [INFO] WARNING: No credentials available for
> the 'Repository Archiva Managed Internal Repository' authentication realm at
>  [INFO] Nov 24, 2009 9:26:28 AM
> org.apache.commons.httpclient.HttpMethodBase processAuthenticationResponse
> [INFO] WARNING: No credentials available for the 'Repository Archiva Managed
> Internal Repository' authentication realm at  [INFO] [INFO]
> 
> [INFO] [ERROR] BUILD ERROR
> [INFO] [INFO]
> 
> [INFO] [INFO] Error deploying artifact: Failed to transfer file:
> http://:8080/archiva/repository/internal/com/statcom/pfl/statcom-pfl/1.1.0.5/statcom-pfl-1.1.0.5.pom.
> Return code is: 401 Unauthorized [INFO] [INFO] [INFO]
>

MAVEN2 PROJECT DEPLOYMENT FAILING....

[Christopher Styles]

Hi,

I'm trying to build and deploy a maven2 project via hudson, and the build
works fine, but the deployment is failing... It's trying to deploy to a
location that's not specified in  in my parent
pom.xml... Does anyone know why this is happening...??? If someone could
please provide insight as to why this is happening and what I need to do to
fix it I'd really appreciate it...


THIS IS WHERE I WANT TO UPLOAD (DEPLOY) MY POM FILE LOCALLY



archiva.internal
Internal Release Repository
*file:///home//repository/maven2*/


archiva.snapshots
Internal Snapshot Repository
*file:///home//repository/maven2*/
false


arizona.site
*file:///home//repository/maven2*/




THIS IS WHERE IT'S TRYING TO DEPLOY (ERROR)

WARNING: No credentials available for the 'Repository Archiva Managed
Internal Repository' authentication realm at  [INFO] Nov 24,
2009 9:26:28 AM org.apache.commons.httpclient.HttpMethodBase
processAuthenticationResponse [INFO] WARNING: No credentials available for
the 'Repository Archiva Managed Internal Repository' authentication realm at
 [INFO] Nov 24, 2009 9:26:28 AM
org.apache.commons.httpclient.HttpMethodBase processAuthenticationResponse
[INFO] WARNING: No credentials available for the 'Repository Archiva Managed
Internal Repository' authentication realm at  [INFO] [INFO]

[INFO] [ERROR] BUILD ERROR
[INFO] [INFO]

[INFO] [INFO] Error deploying artifact: Failed to transfer file:
http://:8080/archiva/repository/internal/com/statcom/pfl/statcom-pfl/1.1.0.5/statcom-pfl-1.1.0.5.pom.
Return code is: 401 Unauthorized [INFO] [INFO] [INFO]

mvn site

[Richard Bibb]

Appologies if I'm in the wrong part of the forum.

If I have a favicon.ico file that I want to be included in my site
distribution doesn anyone know where I should put it? site/resources/Images
doesn't seem to work
-- 
View this message in context: 
http://old.nabble.com/mvn-site-tp26497635p26497635.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Skip dependencies

[Gajo Csaba]

Because they're not optional, they just cannot be installed by Maven 
because they're in a YUM repository.

But I guess the effect would be the same?


Stephen Connolly wrote:

why don't you just set true on your dependencies?

2009/11/24 Gajo Csaba :
  

Regarding this subject, I've managed to "resolve" dependencies by removing
them from the project. So my plugin will check if an rpm is installed, and
if not, it will fail. If everything is ok, then the rpm dependency will be
removed from the project, so that Maven cannot do the check on its own. This
way, it will "skip" all rpm dependencies.

List deps = mavenProject.getDependencies();
Iterator diter = deps.iterator();
while (diter.hasNext()) {
 Dependency dep = diter.next();
 if ("rpm".equals(dep.getType())) {
diter.remove();   // make Maven "forget" about this dependency
checkDependencyOnMyOwn(dep);
 }
}

I'm now waiting for comments why this is a horrible butchering of Maven :)

Regards, Csaba


Gajo Csaba wrote:


Ah cool, some of my colleagues are experimenting with it, I'll ask them
tomorrow!


Csaba Madai wrote:
  

Have you tried Artifactory? It's not a plugin, but I assume it will do
the job for you :)

Csaba

2009/11/23 Gajo Csaba :



Hello Csaba :)

The problem I might potentially have is that we use two repositories,
one is
Maven and the other is YUM. So it is possible for an artifact (rpm) to
be in
YUM, but not in the Maven repository. In this case, my plugin would
check if
it's in YUM and download it... otherwise it would fail. But it should
not
fail if it's not in the Maven repository.

Regards, Csaba


Csaba Madai wrote:

  

Hi,

I think thats the point of the dependency, to "be there", why do you
use a dependency in your pom when it's not necesarry? :)

Csaba

2009/11/23 Gajo Csaba :




Hello,

Is there a way to write a plugin or something, which would check if a
dependency exists, and if it doesn't, then just skips it? Currently if
a
dependency is missing and cannot be downloaded, then the build will
fail.

Thanks, Csaba




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




  

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





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



  

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




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

  

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





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

  



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

Re: Skip dependencies

[Stephen Connolly]

why don't you just set true on your dependencies?

2009/11/24 Gajo Csaba :
> Regarding this subject, I've managed to "resolve" dependencies by removing
> them from the project. So my plugin will check if an rpm is installed, and
> if not, it will fail. If everything is ok, then the rpm dependency will be
> removed from the project, so that Maven cannot do the check on its own. This
> way, it will "skip" all rpm dependencies.
>
> List deps = mavenProject.getDependencies();
> Iterator diter = deps.iterator();
> while (diter.hasNext()) {
>  Dependency dep = diter.next();
>  if ("rpm".equals(dep.getType())) {
>     diter.remove();       // make Maven "forget" about this dependency
>     checkDependencyOnMyOwn(dep);
>  }
> }
>
> I'm now waiting for comments why this is a horrible butchering of Maven :)
>
> Regards, Csaba
>
>
> Gajo Csaba wrote:
>>
>> Ah cool, some of my colleagues are experimenting with it, I'll ask them
>> tomorrow!
>>
>>
>> Csaba Madai wrote:
>>>
>>> Have you tried Artifactory? It's not a plugin, but I assume it will do
>>> the job for you :)
>>>
>>> Csaba
>>>
>>> 2009/11/23 Gajo Csaba :
>>>

 Hello Csaba :)

 The problem I might potentially have is that we use two repositories,
 one is
 Maven and the other is YUM. So it is possible for an artifact (rpm) to
 be in
 YUM, but not in the Maven repository. In this case, my plugin would
 check if
 it's in YUM and download it... otherwise it would fail. But it should
 not
 fail if it's not in the Maven repository.

 Regards, Csaba


 Csaba Madai wrote:

>
> Hi,
>
> I think thats the point of the dependency, to "be there", why do you
> use a dependency in your pom when it's not necesarry? :)
>
> Csaba
>
> 2009/11/23 Gajo Csaba :
>
>
>>
>> Hello,
>>
>> Is there a way to write a plugin or something, which would check if a
>> dependency exists, and if it doesn't, then just skips it? Currently if
>> a
>> dependency is missing and cannot be downloaded, then the build will
>> fail.
>>
>> Thanks, Csaba
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
>

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



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

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

Re: Skip dependencies

[Gajo Csaba]

Regarding this subject, I've managed to "resolve" dependencies by 
removing them from the project. So my plugin will check if an rpm is 
installed, and if not, it will fail. If everything is ok, then the rpm 
dependency will be removed from the project, so that Maven cannot do the 
check on its own. This way, it will "skip" all rpm dependencies.


List deps = mavenProject.getDependencies();
Iterator diter = deps.iterator();
while (diter.hasNext()) {
 Dependency dep = diter.next();
 if ("rpm".equals(dep.getType())) {
 diter.remove();   // make Maven "forget" about this dependency
 checkDependencyOnMyOwn(dep);
 }
}

I'm now waiting for comments why this is a horrible butchering of Maven :)

Regards, Csaba


Gajo Csaba wrote:
Ah cool, some of my colleagues are experimenting with it, I'll ask 
them tomorrow!



Csaba Madai wrote:

Have you tried Artifactory? It's not a plugin, but I assume it will do
the job for you :)

Csaba

2009/11/23 Gajo Csaba :
 

Hello Csaba :)

The problem I might potentially have is that we use two 
repositories, one is
Maven and the other is YUM. So it is possible for an artifact (rpm) 
to be in
YUM, but not in the Maven repository. In this case, my plugin would 
check if
it's in YUM and download it... otherwise it would fail. But it 
should not

fail if it's not in the Maven repository.

Regards, Csaba


Csaba Madai wrote:
   

Hi,

I think thats the point of the dependency, to "be there", why do you
use a dependency in your pom when it's not necesarry? :)

Csaba

2009/11/23 Gajo Csaba :

 

Hello,

Is there a way to write a plugin or something, which would check if a
dependency exists, and if it doesn't, then just skips it? 
Currently if a
dependency is missing and cannot be downloaded, then the build 
will fail.


Thanks, Csaba




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





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


  

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





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

  



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




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

Re: One project, two outputs, how to do it?

[Anders Hammar]

Look at the far bottom of this page:
http://maven.apache.org/plugins/maven-jar-plugin/usage.html

/Anders

2009/11/24 Gajo Csaba 

> Hello,
>
> Usually when I build a project and install it to my local repository, I
> have one jar file there. In one specific case, I would like two jars to be
> created, and they should both be installed into the repository. Is there a
> way to do this?
>
> Creating two jars is not so much a problem, the problem is how to tell the
> project to use both during installation.
>
> Regards, Csaba
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: merging testng into surefire..

[Mick Knutson]

I do not understand the problem space at this point. What PROVIDER code
issue are you having?

---
Thank You…

Mick Knutson, President

BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring & Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233

Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---



On Tue, Nov 24, 2009 at 7:47 AM, Martin Gainty  wrote:

>
> this would work only IF the providers integrated with surefire properly
> which is not the case
> the side effect is that integrating a provider such as testng (which only
> works with surefire last time i checked)
> creates integration exceptions
> NONE of these integration exceptions would occur IF the testng codebase was
> merged into surefire
> any integration exceptions would be discovered in the surefire packaging
> phase before deployment
>
> comments?
> Martin Gainty
> __
> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> dient lediglich dem Austausch von Informationen und entfaltet keine
> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
> destinataire prévu, nous te demandons avec bonté que pour satisfaire
> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
> de ceci est interdite. Ce message sert à l'information seulement et n'aura
> pas n'importe quel effet légalement obligatoire. Étant donné que les email
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
> aucune responsabilité pour le contenu fourni.
>
>
>
>
> > From: mickknut...@gmail.com
> > Date: Mon, 23 Nov 2009 18:57:58 -0800
> > Subject: Re: merging testng into surefire..
> > To: users@maven.apache.org
> >
> > I do not think I fully understand the different 'Provider' concept, but
> if
> > you are looking to run different types of tests in 1 suite, then you
> could
> > create a separate PROFILE in Maven, then your suite could have something
> > like:
> >
> > http://testng.org/testng-1.0.dtd";>
> > 
> >
> > **
> > http://localhost:8889/webapp/"; /
> >
> > 
> > 
> > 
> > 
> > 
> > ...
> >
> > Or you could hard code them per test section:
> >
> > 
> > * *
> > 
> > 
> > 
> > 
> >
> > 
> > * *
> > 
> > 
> > 
> > 
> >
> > Is this what you mean?
> >
> >
> > ---
> > Thank You…
> >
> > Mick Knutson, President
> >
> > BASE Logic, Inc.
> > Enterprise Architecture, Design, Mentoring & Agile Consulting
> > p. (866) BLiNC-411: (254-6241-1)
> > f. (415) 685-4233
> >
> > Website: http://baselogic.com
> > Linked IN: http://linkedin.com/in/mickknutson
> > Vacation Rental: http://tahoe.baselogic.com
> > ---
> >
> >
> >
> > On Mon, Nov 23, 2009 at 6:46 PM, Martin Gainty 
> wrote:
> >
> > >
> > > i understand paul's assertion for a separate provider suite
> > >
> > > but how would this suite of packages work?
> > > once constructed is there a way to construct integration tests to
> prevent
> > > potential version mismatch between provider and surefire?
> > >
> > > Thanks!
> > > Martin
> > >
> > > > From: mickknut...@gmail.com
> > > > Date: Mon, 23 Nov 2009 18:06:06 -0800
> > > > Subject: Re: merging testng into surefire..
> > > > To: users@maven.apache.org
> > > >
> > > > You can create a suite of Packages instead of defining each class to
> make
> > > > the suite easier at 1st.
> > > >
> > > > ---
> > > > Thank You…
> > > >
> > > > Mick Knutson, President
> > > >
> > > > BASE Logic, Inc.
> > > > Enterprise Architecture, Design, Mentoring & Agile Consulting
> > > > p. (866) BLiNC-411: (254-6241-1)
> > > > f. (415) 685-4233
> > > >
> > > > Website: http://baselogic.com
> > > > Linked IN: http://linkedin.com/in/mickknutson
> > > > Vacation Rental: http://tahoe.baselogic.com
> > > > ---
> > > >
> > > >
> > > >
> > > > On Mon, Nov 23, 2009 at 5:42 PM, Martin Gainty 
> > > wrote:
> > > >
> > > > >
> > > > > Good Evening All-
> > > > >
> > > > > org.apache.maven.surefire.booter.SurefireExecutionException:
> > > > > org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;; nested
> > > exception is
> > > > > java.lang.NoSuchMethodError:
> > > > > org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;
> > > > > java.lang.NoSuchMethodError:
> > > > > org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;
> > > > >at
> > > > >
> > >
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:132)
> > > > >at
> > > > >
> > >
> org.apache.maven.surefire.

Re: One project, two outputs, how to do it?

[Aleksey Didik]

But what about maven-assembly-plugin?All assemblies will be installed 
and deployed, not only main jar.


http://maven.apache.org/plugins/maven-assembly-plugin/usage.html

Getting started with the Assembly Plugin is pretty simple. If you're 
using one of the prefabricated assembly descriptors, you just tell it 
which one; if you're using a custom assembly descriptor, you give it the 
path to the descriptor. Note that a single invocation of the Assembly 
Plugin can actually produce assemblies from multiple descriptors, 
allowing you maximum flexibility to customize the suite of binaries your 
project produces. When the assembly is created it will use the 
assemblyId as the artifact's classifier and will attach the created 
assembly to the project and will be uploaded into the repository on an 
install and deploy goal.


Aleksey.

Gajo Csaba ?:
No, different, one containing one part of the compiled code, the other 
the rest.



Alexander wrote:

Two identical jar?

2009/11/24 Gajo Csaba 

 

Hello,

Usually when I build a project and install it to my local repository, I
have one jar file there. In one specific case, I would like two jars 
to be
created, and they should both be installed into the repository. Is 
there a

way to do this?

Creating two jars is not so much a problem, the problem is how to 
tell the

project to use both during installation.

Regards, Csaba


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






  



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

RE: merging testng into surefire..

[Martin Gainty]

this would work only IF the providers integrated with surefire properly which 
is not the case 
the side effect is that integrating a provider such as testng (which only works 
with surefire last time i checked)
creates integration exceptions 
NONE of these integration exceptions would occur IF the testng codebase was 
merged into surefire
any integration exceptions would be discovered in the surefire packaging phase 
before deployment
 
comments?
Martin Gainty 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




> From: mickknut...@gmail.com
> Date: Mon, 23 Nov 2009 18:57:58 -0800
> Subject: Re: merging testng into surefire..
> To: users@maven.apache.org
> 
> I do not think I fully understand the different 'Provider' concept, but if
> you are looking to run different types of tests in 1 suite, then you could
> create a separate PROFILE in Maven, then your suite could have something
> like:
> 
> http://testng.org/testng-1.0.dtd";>
> 
> 
> **
> http://localhost:8889/webapp/"; /
> 
> 
> 
> 
> 
> 
> ...
> 
> Or you could hard code them per test section:
> 
> 
> * *
> 
> 
> 
> 
> 
> 
> * *
> 
> 
> 
> 
> 
> Is this what you mean?
> 
> 
> ---
> Thank You…
> 
> Mick Knutson, President
> 
> BASE Logic, Inc.
> Enterprise Architecture, Design, Mentoring & Agile Consulting
> p. (866) BLiNC-411: (254-6241-1)
> f. (415) 685-4233
> 
> Website: http://baselogic.com
> Linked IN: http://linkedin.com/in/mickknutson
> Vacation Rental: http://tahoe.baselogic.com
> ---
> 
> 
> 
> On Mon, Nov 23, 2009 at 6:46 PM, Martin Gainty  wrote:
> 
> >
> > i understand paul's assertion for a separate provider suite
> >
> > but how would this suite of packages work?
> > once constructed is there a way to construct integration tests to prevent
> > potential version mismatch between provider and surefire?
> >
> > Thanks!
> > Martin
> >
> > > From: mickknut...@gmail.com
> > > Date: Mon, 23 Nov 2009 18:06:06 -0800
> > > Subject: Re: merging testng into surefire..
> > > To: users@maven.apache.org
> > >
> > > You can create a suite of Packages instead of defining each class to make
> > > the suite easier at 1st.
> > >
> > > ---
> > > Thank You…
> > >
> > > Mick Knutson, President
> > >
> > > BASE Logic, Inc.
> > > Enterprise Architecture, Design, Mentoring & Agile Consulting
> > > p. (866) BLiNC-411: (254-6241-1)
> > > f. (415) 685-4233
> > >
> > > Website: http://baselogic.com
> > > Linked IN: http://linkedin.com/in/mickknutson
> > > Vacation Rental: http://tahoe.baselogic.com
> > > ---
> > >
> > >
> > >
> > > On Mon, Nov 23, 2009 at 5:42 PM, Martin Gainty 
> > wrote:
> > >
> > > >
> > > > Good Evening All-
> > > >
> > > > org.apache.maven.surefire.booter.SurefireExecutionException:
> > > > org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;; nested
> > exception is
> > > > java.lang.NoSuchMethodError:
> > > > org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;
> > > > java.lang.NoSuchMethodError:
> > > > org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;
> > > >at
> > > >
> > org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:132)
> > > >at
> > > >
> > org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:150)
> > > >
> > > > as you can see Surefire createSuiteFromDefinition method calls to
> > testng
> > > > which calls a nonexistent parse() routine which if corrrect would
> > return an
> > > > array XmlSuite
> > > >
> > > > these integration scenarios could be fleshed out more easily if
> >  surefire
> > > > completely merged the testng codebase.
> > > >
> > > > Eventually i will find a parse routine that works from testng TestSuite
> > if
> > > > not i will of course code the missing method
> > > >
> > > > im wondering if testng should be merged completely into surefire to
> > avert
> > > > these types of integration errors
> > > >
> > > > any viable reaso

Re: One project, two outputs, how to do it?

[Gajo Csaba]

No, different, one containing one part of the compiled code, the other 
the rest.



Alexander wrote:

Two identical jar?

2009/11/24 Gajo Csaba 

  

Hello,

Usually when I build a project and install it to my local repository, I
have one jar file there. In one specific case, I would like two jars to be
created, and they should both be installed into the repository. Is there a
way to do this?

Creating two jars is not so much a problem, the problem is how to tell the
project to use both during installation.

Regards, Csaba


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






  



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

Re: One project, two outputs, how to do it?

[Alexander]

Two identical jar?

2009/11/24 Gajo Csaba 

> Hello,
>
> Usually when I build a project and install it to my local repository, I
> have one jar file there. In one specific case, I would like two jars to be
> created, and they should both be installed into the repository. Is there a
> way to do this?
>
> Creating two jars is not so much a problem, the problem is how to tell the
> project to use both during installation.
>
> Regards, Csaba
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>


-- 
Regards,
Alexander

One project, two outputs, how to do it?

[Gajo Csaba]

Hello,

Usually when I build a project and install it to my local repository, I 
have one jar file there. In one specific case, I would like two jars to 
be created, and they should both be installed into the repository. Is 
there a way to do this?


Creating two jars is not so much a problem, the problem is how to tell 
the project to use both during installation.


Regards, Csaba


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

Re: How to include images into Doxia generated site?

[Lukas Theussl]

The doxia maven plugin currently ignores resources, see 
http://jira.codehaus.org/browse/DOXIA-355 and 
http://jira.codehaus.org/browse/DOXIA-354 for a workaround.


HTH,
-Lukas


Gajo Csaba wrote:

Hello,

I'm generating a PDF from DocBook XML, and I don't know how to include 
images, as in, where should they be located? I've tried next to the xml 
file, in the root directory...


http://maven.apache.org/doxia/book/index.html

Thanks, Csaba



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




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

How to include images into Doxia generated site?

[Gajo Csaba]

Hello,

I'm generating a PDF from DocBook XML, and I don't know how to include 
images, as in, where should they be located? I've tried next to the xml 
file, in the root directory...


http://maven.apache.org/doxia/book/index.html

Thanks, Csaba



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

Re: How to skip testResources execution when tests are skipped

[Aleksey Didik]

Sorry, looks like I don't understand your question.
The shame.

Aleksey.

maik.eb...@icw.de пишет:

Hello everyone,

is it possible to remove the maven-resource-plugin with its testResources 
mojo execution from the lifecycle when tests are skipped?


The maven-compiler-plugin respects the skipTests parameter and does not 
compile the test classes, but the maven-resource-plugin does still process 
the test resources. That's not necessary in my opinion.


Is there a solution to my problem without patching the 
maven-resource-plugin?


Thanks,

Maik Ebert | R&D ProfessionalGate
InterComponentWare AG | Industriestraße 41 | 69190 Walldorf (Baden) | 
Germany 
Tel.: +49 (0) 6227 385 203 | Fax: +49 (0) 6227 385

maik.eb...@icw.de | www.icw.de | www.lifesensor.com

InterComponentWare AG:  
Vorstand: Dr. Lutz Kleinholz (Vors.), Dr. Georg Ralle, Jörg Stadler / Aufsichtsratsvors.: Prof. Dr. Christof Hettich  
Firmensitz: 69190 Walldorf, Industriestraße 41 / AG Mannheim HRB 351761 / USt.-IdNr.: DE 198388516  


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

Re: How to skip testResources execution when tests are skipped

[Aleksey Didik]

Hello,
as to me, the best way for integration tests organization is using 'pom' 
packaging for it module.
In this case you could manually switch on only necessary plugins like 
compiling only tests, copy resources or not, and etc..


My it-module pom:

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


...
...
0.1-SNAPSHOT

4.0.0
functional-tests
pom
0.1-SNAPSHOT


${basedir}/it/main/java


${basedir}/it/main/resources
true






it


it





maven-compiler-plugin



testCompile





maven-resources-plugin



testResources





maven-surefire-plugin

never



it
integration-test

test











In hope to help,
Aleksey.

maik.eb...@icw.de пишет:

Hello everyone,

is it possible to remove the maven-resource-plugin with its testResources 
mojo execution from the lifecycle when tests are skipped?


The maven-compiler-plugin respects the skipTests parameter and does not 
compile the test classes, but the maven-resource-plugin does still process 
the test resources. That's not necessary in my opinion.


Is there a solution to my problem without patching the 
maven-resource-plugin?


Thanks,

Maik Ebert | R&D ProfessionalGate
InterComponentWare AG | Industriestraße 41 | 69190 Walldorf (Baden) | 
Germany 
Tel.: +49 (0) 6227 385 203 | Fax: +49 (0) 6227 385

maik.eb...@icw.de | www.icw.de | www.lifesensor.com

InterComponentWare AG:  
Vorstand: Dr. Lutz Kleinholz (Vors.), Dr. Georg Ralle, Jörg Stadler / Aufsichtsratsvors.: Prof. Dr. Christof Hettich  
Firmensitz: 69190 Walldorf, Industriestraße 41 / AG Mannheim HRB 351761 / USt.-IdNr.: DE 198388516  


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

How to skip testResources execution when tests are skipped

[maik . ebert]

Hello everyone,

is it possible to remove the maven-resource-plugin with its testResources 
mojo execution from the lifecycle when tests are skipped?

The maven-compiler-plugin respects the skipTests parameter and does not 
compile the test classes, but the maven-resource-plugin does still process 
the test resources. That's not necessary in my opinion.

Is there a solution to my problem without patching the 
maven-resource-plugin?

Thanks,

Maik Ebert | R&D ProfessionalGate
InterComponentWare AG | Industriestraße 41 | 69190 Walldorf (Baden) | 
Germany 
Tel.: +49 (0) 6227 385 203 | Fax: +49 (0) 6227 385
maik.eb...@icw.de | www.icw.de | www.lifesensor.com

InterComponentWare AG:  
Vorstand: Dr. Lutz Kleinholz (Vors.), Dr. Georg Ralle, Jörg Stadler / 
Aufsichtsratsvors.: Prof. Dr. Christof Hettich  
Firmensitz: 69190 Walldorf, Industriestraße 41 / AG Mannheim HRB 351761 / 
USt.-IdNr.: DE 198388516  

Re: Maven 3 incompatiblity

[Anders Hammar]

I'm not sure I understand your use case fully, but I'm thinking that you
should probably keep your ITs outside of your project. You would then build
your project for a specific version, but could then run the ITs on any other
version. And this strategy could then be extended to run the ITs with
different profiles for using different versions, or even several IT projects
for a set of different pre-defined version.

/Anders

On Tue, Nov 24, 2009 at 10:23, Andreas M wrote:

>
> After I upgraded to the latest m2eclipse the builds of out integration
> tests
> started failing.
> The reason was this:
> I had set up our integration tests so that I could run one side of the
> communication with an older version of our product (for compatibility
> tests). I did this by setting up two dependencies for the same artifact,
> with different scopes (compile and runtime).  (See example below)
> This failed in Maven 3, the error message was that I had two dependencies
> with the same version.
>
> Now, I solved my problem by changing the setup of the tests from using
> copy-dependencies to using copy (and all the dependencies spelled out in
> the
> configuration). But the previous solution was nicer, in that copy-dependecy
> also brought with it the transitive dependencies as well. Now I had to
> duplicate 'em by hand instead.
>
> Question: is this intended behavior? Or should the version check look at
> the
> scope as well?
>
> Example:
>
> 
>  com.example
>  component
>  ${client-side-version}
>  compile
> 
> 
>  com.example
>  component
>  ${server-side-version}
>  runtime
> 
>
> The jars are copied with maven-dependency-plugin:copy-dependency.
> When a developer builds client- and server-side-version are the same.
> During
> compatiblility tests one is pointed to the previous version.
>
> --
> View this message in context:
> http://old.nabble.com/Maven-3-incompatiblity-tp26492785p26492785.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Maven 3 incompatiblity

[Andreas M]

After I upgraded to the latest m2eclipse the builds of out integration tests
started failing.
The reason was this:
I had set up our integration tests so that I could run one side of the
communication with an older version of our product (for compatibility
tests). I did this by setting up two dependencies for the same artifact,
with different scopes (compile and runtime).  (See example below)
This failed in Maven 3, the error message was that I had two dependencies
with the same version. 

Now, I solved my problem by changing the setup of the tests from using
copy-dependencies to using copy (and all the dependencies spelled out in the
configuration). But the previous solution was nicer, in that copy-dependecy
also brought with it the transitive dependencies as well. Now I had to
duplicate 'em by hand instead.

Question: is this intended behavior? Or should the version check look at the
scope as well?

Example:


  com.example
  component
  ${client-side-version}
  compile


  com.example
  component
  ${server-side-version}
  runtime


The jars are copied with maven-dependency-plugin:copy-dependency.
When a developer builds client- and server-side-version are the same. During
compatiblility tests one is pointed to the previous version.

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


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