solved Re: archiva setup question as repository

[Mick Knutson]

It seems I do not need dav:*url* in my . Sorry

On Dec 14, 2007 5:44 PM, Mick Knutson <[EMAIL PROTECTED]> wrote:

> I have my archiva defined in my pom.xml:
>
> 
> 
> dap.internal
> DAP Managed Internal Repository
> 
> http://rc-sun66e.ut.dentegra.lab:8081/archiva/repository/internal/
> 
> true
> 
> 
> false
> 
> 
> 
>
> Then the mirror in my settings.xml:
>
> 
>   dap.internal
>   
> dav:http://rc-sun66e.ut.dentegra.lab:8081/archiva/repository/internal/
> 
>   *
> 
>
>
> When I go to the UI and look for "regexp:regexp:jar: 1.3" it was not in
> the REPO, but then it went and downloaded it, so now when I browser I can
> see "archiva/browse/regexp/regexp/1.3/" and the jar description.
>
> Now when I run a clean package, the jar in not in my local repo, and tries
> to download it but does not find it:
>
>
> [INFO] Failed to resolve artifact.
>
> Missing:
> --
> 1) regexp:regexp:jar:1.3
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>   mvn install:install-file -DgroupId=regexp -DartifactId=regexp \
>   -Dversion=1.3 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:   mvn deploy:deploy-file -DgroupId=regexp -DartifactId=regexp \
>   -Dversion=1.3 -Dpackaging=jar -Dfile=/path/to/file \
>-Durl=[url] -DrepositoryId=[id]
>
>   Path to dependency:
> 1)
> org.codehaus.mojo:buildnumber-maven-plugin:maven-plugin:1.0-beta-1-SNAPSHOT
> 2) org.apache.maven.scm:maven-scm-provider-perforce:jar:1.0-beta-3
> 3) regexp:regexp:jar:1.3
>
> --
> 1 required artifact is missing.
>
> for artifact:
>
> org.codehaus.mojo:buildnumber-maven-plugin:maven-plugin:1.0-beta-1-SNAPSHOT
>
> from the specified remote repositories:
>   codehaus.org (http://snapshots.repository.codehaus.org),
>   central ( http://repo1.maven.org/maven2),
>   dap.internal (
> http://rc-sun66e.ut.dentegra.lab:8081/archiva/repository/internal/)
>
>
>
>
> Any ideas on how to resolve this?
>
>
>
>
> --
> Thanks,
> Mick Knutson
>
> http://www.baselogic.com
> http://www.blincmagazine.com
> http://www.djmick.com
> http://www.myspace.com/mickknutson
> http://www.myspace.com/BLiNCMagazine
> http://tahoe.baselogic.com
> ---




-- 
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/BLiNCMagazine
http://tahoe.baselogic.com
---

archiva setup question as repository

[Mick Knutson]

I have my archiva defined in my pom.xml:



dap.internal
DAP Managed Internal Repository

http://rc-sun66e.ut.dentegra.lab:8081/archiva/repository/internal/

true


false




Then the mirror in my settings.xml:


  dap.internal
  dav:
http://rc-sun66e.ut.dentegra.lab:8081/archiva/repository/internal/
  *



When I go to the UI and look for "regexp:regexp:jar:1.3" it was not in the
REPO, but then it went and downloaded it, so now when I browser I can see
"archiva/browse/regexp/regexp/1.3/" and the jar description.

Now when I run a clean package, the jar in not in my local repo, and tries
to download it but does not find it:


[INFO] Failed to resolve artifact.

Missing:
--
1) regexp:regexp:jar:1.3

  Try downloading the file manually from the project website.

  Then, install it using the command:
  mvn install:install-file -DgroupId=regexp -DartifactId=regexp \
  -Dversion=1.3 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:   mvn deploy:deploy-file -DgroupId=regexp -DartifactId=regexp \
  -Dversion=1.3 -Dpackaging=jar -Dfile=/path/to/file \
   -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
1)
org.codehaus.mojo:buildnumber-maven-plugin:maven-plugin:1.0-beta-1-SNAPSHOT
2) org.apache.maven.scm:maven-scm-provider-perforce:jar:1.0-beta-3
3) regexp:regexp:jar:1.3

--
1 required artifact is missing.

for artifact:

org.codehaus.mojo:buildnumber-maven-plugin:maven-plugin:1.0-beta-1-SNAPSHOT

from the specified remote repositories:
  codehaus.org (http://snapshots.repository.codehaus.org),
  central (http://repo1.maven.org/maven2),
  dap.internal (
http://rc-sun66e.ut.dentegra.lab:8081/archiva/repository/internal/)




Any ideas on how to resolve this?




-- 
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/BLiNCMagazine
http://tahoe.baselogic.com
---

Re: Building war with multi-module classes and no module jars

[bayamos]

OK, here's the situation.

The JIBX bytecode enhancer modifies classes across multiple modules and it
has to work this way because of dependencies between the classes.  This is
executed with a process-classes phase after all the jars are built, but
before the war is built.  Since all the jars are built before the JIBX
plugin can run, the enhanced classes are in the jar modules target/classes
directory but not in the jar.

Another possibility is if there was a way to run the jibx plugin after all
the modules are compiled but before they are assembled into jars that would
work too.

I can live with the jars being built so continuum can work.


stojcevicht wrote:
> 
> maven isn't really setup to be able to "reach into" other projects, to
> use artifacts created in other projects, you should go through jars
> via the repo
> 
> You can however still do it by using the antrun plugin and ant's copy
> target with relative referencing  "../project-a/target/classes", but
> doing so you loose true project independence (and you won't be able to
> add the projects individually to continuum if you use continuum).
> 
> To stop the jar packaging you could:
> 1 - just call mvn compile in the common project, that won't jar up the
> classes
> 2 - change the project type in the pom from jar to pom, but then
> you'll have to setup each plugin you want to call since the jar
> lifecycle won't get called
> 
> 
> Couldn't you just add the class file post processing to the projects
> that the class files are compiled in?
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Building-war-with-multi-module-classes-and-no-module-jars-tp14332309s177p14339854.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]

Continuum and SSO

[Arnaud Bailly]

Hello,
I would like to use continuum (and archiva) in a tomcat container behind an
Apache, and I would like to delegate the authentication to the apache httpd.
I think this is possible with tomcat using Ajp13 connector and some
configuration, but I wonder how I can handle this in continuum. 

Regards

Arnaud Bailly
-- 
View this message in context: 
http://www.nabble.com/Continuum-and-SSO-tp14339806p14339806.html
Sent from the Continuum - Users mailing list archive at Nabble.com.

Re: [M2] Reproducible build

[Rob Hasselbaum]

Comparing hashes (MD5 or SHA1) will definitely tell you whether two
files are identical, but it won't tell you what the differences are.
However, you could write a script that processes the output of "jar -tv"
or "unzip -lv" and spits out the differences. The latter tool ("unzip"
from www.info-zip.org) is nice because the output contains a checksum
per file, which is a more reliable indicator of differences compared to
using file sizes or timestamps.


On 12/14/2007 12:02 PM, Rémy Sanlaville wrote:
> Hi,
>
> I would like to make sure that my project build is reproducible.
> For instance, I want to be sure that I can package again a tagged version.
>
> So I am looking for a tools that can compare two package (two jar, two war,
> two ear...) and eventually shows the potential differences.
> Do you know if a such tools exists ?
>
> In order two verify if two package are identical, I was thinking of
> generating and comparing the corresponding checksum (md5 or sha1) .
> Do you think that it would be good enough ?
>
> Rémy
>
>   

Re: [M2] Reproducible build

[Aaron Metzger]

Rémy Sanlaville wrote:

Hi,

I would like to make sure that my project build is reproducible.
For instance, I want to be sure that I can package again a tagged version.

So I am looking for a tools that can compare two package (two jar, two war,
two ear...) and eventually shows the potential differences.
Do you know if a such tools exists ?

In order two verify if two package are identical, I was thinking of
generating and comparing the corresponding checksum (md5 or sha1) .
Do you think that it would be good enough ?



Comparing checksums can be a bad strategy if any of your build artifacts 
are crypographically signed or otherwise include data which might 
legitimately vary from build to build because it is time dependent or 
actually includes date or time stamps.




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

Re: [m2][c1.1] How to run dashboard in Continuum?

[Mick Knutson]

I did check the build fresh on all 3 items but still only the 1st (default)
task is run. Nothing else...

On Dec 12, 2007 12:21 AM, dvicente <[EMAIL PROTECTED]> wrote:

>
> This bug should have been corrected since Continuum 1.0.3.
>
> Have you used the "build fresh" checkbox ? i think it's used to force
> Continuum to execute the goal even if there is no SCM change between 2
> goals
> ?
>
>
>
>
> Mick Knutson-4 wrote:
> >
> > Can I please get a little help on this? I have been looking for 2
> days...
> >
> >
> > On Dec 10, 2007 12:44 PM, Mick Knutson <[EMAIL PROTECTED]> wrote:
> >
> >> I have setup the 3 phases I needed on my project group:
> >> Goals Arguments Build File Schedule Profile From Build Fresh Default
> >> Description Type clean site:site -P documentation -e pom.xmlSite
> >> Schedule<
> http://rc-sun66e.ut.dentegra.lab:8080/continuum/schedule.action?id=6>
> >> site
> >> documentation GROUP false true Run clean site:site -P documentation -e
> >> maven2  [image:
> >> Build]<
> http://rc-sun66e.ut.dentegra.lab:8080/continuum/buildProject.action?goals=dashboard-report%3Adashboard&arguments=-P+documentation+-e&groupBuildDefinition=true&scheduleId=6&buildDefinitionType=maven2&defaultBuildDefinition=true&fromProjectPage=true&projectId=81&buildDefinitionId=24&description=Run+dashboard-report%3Adashboard+-P+documentation+-e&projectGroupId=11&buildFile=pom.xml&profileId=11
> >
> >> [image:
> >> Edit]<
> http://rc-sun66e.ut.dentegra.lab:8080/continuum/buildDefinition%21input.action?arguments=-P+documentation+-e&goals=dashboard-report%3Adashboard&projectId=81&buildDefinitionId=24&description=Run+dashboard-report%3Adashboard+-P+documentation+-e&groupBuildDefinition=true&projectGroupId=11&buildDefinitionType=maven2&scheduleId=6&defaultBuildDefinition=true&profileId=11&buildFile=pom.xml
> >
> >> [image:
> >> Delete]<
> http://rc-sun66e.ut.dentegra.lab:8080/continuum/removeGroupBuildDefinition.action?goals=dashboard-report%3Adashboard&arguments=-P+documentation+-e&groupBuildDefinition=true&scheduleId=6&buildDefinitionType=maven2&defaultBuildDefinition=true&projectId=81&buildDefinitionId=24&confirmed=false&description=Run+dashboard-report%3Adashboard+-P+documentation+-e&projectGroupId=11&buildFile=pom.xml&profileId=11
> >
> >> dashboard-report:dashboard -P documentation -e pom.xml Site
> >> Schedule<
> http://rc-sun66e.ut.dentegra.lab:8080/continuum/schedule.action?id=6>
> >> site
> >> documentation GROUP false false Run dashboard-report:dashboard -P
> >> documentation -e maven2  [image:
> >> Build]<
> http://rc-sun66e.ut.dentegra.lab:8080/continuum/buildProject.action?goals=dashboard-report%3Adashboard&arguments=-P+documentation+-e&groupBuildDefinition=true&scheduleId=6&buildDefinitionType=maven2&defaultBuildDefinition=true&fromProjectPage=true&projectId=81&buildDefinitionId=25&description=Run+dashboard-report%3Adashboard+-P+documentation+-e&projectGroupId=11&buildFile=pom.xml&profileId=11
> >
> >> [image:
> >> Edit]<
> http://rc-sun66e.ut.dentegra.lab:8080/continuum/buildDefinition%21input.action?arguments=-P+documentation+-e&goals=dashboard-report%3Adashboard&projectId=81&buildDefinitionId=25&description=Run+dashboard-report%3Adashboard+-P+documentation+-e&groupBuildDefinition=true&projectGroupId=11&buildDefinitionType=maven2&scheduleId=6&defaultBuildDefinition=true&profileId=11&buildFile=pom.xml
> >
> >> [image:
> >> Delete]<
> http://rc-sun66e.ut.dentegra.lab:8080/continuum/removeGroupBuildDefinition.action?goals=dashboard-report%3Adashboard&arguments=-P+documentation+-e&groupBuildDefinition=true&scheduleId=6&buildDefinitionType=maven2&defaultBuildDefinition=true&projectId=81&buildDefinitionId=25&confirmed=false&description=Run+dashboard-report%3Adashboard+-P+documentation+-e&projectGroupId=11&buildFile=pom.xml&profileId=11
> >
> >> site:site-deploy -P documentation -e pom.xml Site
> >> Schedule<
> http://rc-sun66e.ut.dentegra.lab:8080/continuum/schedule.action?id=6>
> >> site
> >> documentation GROUP false false Run clean site:site-deploy -P
> >> documentation -e maven2  [image:
> >> Build]<
> http://rc-sun66e.ut.dentegra.lab:8080/continuum/buildProject.action?goals=dashboard-report%3Adashboard&arguments=-P+documentation+-e&groupBuildDefinition=true&scheduleId=6&buildDefinitionType=maven2&defaultBuildDefinition=true&fromProjectPage=true&projectId=81&buildDefinitionId=26&description=Run+dashboard-report%3Adashboard+-P+documentation+-e&projectGroupId=11&buildFile=pom.xml&profileId=11
> >
> >> [image:
> >> Edit]<
> http://rc-sun66e.ut.dentegra.lab:8080/continuum/buildDefinition%21input.action?arguments=-P+documentation+-e&goals=dashboard-report%3Adashboard&projectId=81&buildDefinitionId=26&description=Run+dashboard-report%3Adashboard+-P+documentation+-e&groupBuildDefinition=true&projectGroupId=11&buildDefinitionType=maven2&scheduleId=6&defaultBuildDefinition=true&profileId=11&buildFile=pom.xml
> >
> >> [image:
> >> Delete]<
> http://rc-sun66e.ut.dentegra.lab:8080/continuum/removeGroupBuildDefinition

Re: Wacky Duplicate Path Problem

[Dan Tran]

release plugin never work with cygwn's svn ( at least in my case),
switch non cygwin version never a problem.

-D

On Dec 14, 2007 10:54 AM, Harper, Brad <[EMAIL PROTECTED]> wrote:
> Hi:
>
> I've suddenly been hit by the problem described at
>
>   http://jira.codehaus.org/browse/SCM-213
>
> when running the 'release:prepare release:perform' goals.
>
> The svn command-line client fails when receiving an argument containing
> duplicate paths using two different conventions: one cygwin, the other
> Windows.
>
>   svn:
> '/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclipse-workspace-
> qa-
> 2.4.12/framework' is not a working copy
>
> Last week it worked. Today it doesn't. Anyone have thoughts?
>
> Thanks.
>
> Brad
>
> -
> Here's a fragment of the -X output
>
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-release-plugin:2.0-beta
> -6:prepare' -->
> [DEBUG]   (f) addSchema = true
> [DEBUG]   (f) autoVersionSubmodules = false
> [DEBUG]   (s) basedir = p:\eclipse-workspace-qa-2.4.12\framework
> [DEBUG]   (f) commitByProject = false
> [DEBUG]   (f) dryRun = false
> [DEBUG]   (f) generateReleasePoms = false
> [DEBUG]   (f) preparationGoals = clean verify
> [DEBUG]   (f) project = [EMAIL PROTECTED]
> [DEBUG]   (f) reactorProjects =
> [EMAIL PROTECTED]
>
> [DEBUG]   (f) resume = true
> [DEBUG]   (f) scmCommentPrefix = [maven-release-plugin]
> [DEBUG]   (f) settings = [EMAIL PROTECTED]
> [DEBUG]   (f) updateDependencies = true
> [DEBUG]   (f) useEditMode = false
> [DEBUG] -- end configuration --
> [INFO] [release:prepare]
> [INFO] Resuming release from phase 'scm-commit-release'
> [INFO] Checking in modified POMs...
> [INFO] Executing: svn --non-interactive commit --file
> c:\DOCUME~1\bsharp\LOCALS~
> 1\Temp\maven-scm-298175632.commit --targets
> c:\DOCUME~1\bsharp\LOCALS~1\Temp\mav
> en-scm-46278-targets
> [INFO] Working directory: p:\eclipse-workspace-qa-2.4.12\framework
> [INFO]
> 
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] Unable to commit files
> Provider message:
> The svn command failed.
> Command output:
> svn:
> '/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclipse-workspace-
> qa-
> 2.4.12/framework' is not a working copy
> svn: Can't open file
> '/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclip
> se-workspace-qa-2.4.12/framework/.svn/entries': No such file or
> directory
>
> [INFO]
> 
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: Unable to commit files
> Provider message:
> The svn command failed.
> Command output:
> svn:
> '/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclipse-workspace-
> qa-
> 2.4.12/framework' is not a working copy
> svn: Can't open file
> '/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclip
> se-workspace-qa-2.4.12/framework/.svn/entries': No such file or
> directory
> ...
>
> Caused by: org.apache.maven.plugin.MojoFailureException: Unable to
> commit files
> Provider message:
> The svn command failed.
> Command output:
> svn:
> '/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclipse-workspace-
> qa-
> 2.4.12/framework' is not a working copy
> svn: Can't open file
> '/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclip
> se-workspace-qa-2.4.12/framework/.svn/entries': No such file or
> directory
> ...
>
> [INFO]
> 
> [INFO] Total time: 4 seconds
> [INFO] Finished at: Fri Dec 14 12:45:11 CST 2007
> [INFO] Final Memory: 5M/9M
> [INFO]
> 
>
> -
> 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]

Wacky Duplicate Path Problem

[Harper, Brad]

Hi:

I've suddenly been hit by the problem described at

   http://jira.codehaus.org/browse/SCM-213

when running the 'release:prepare release:perform' goals.

The svn command-line client fails when receiving an argument containing
duplicate paths using two different conventions: one cygwin, the other
Windows.

   svn:
'/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclipse-workspace-
qa-
2.4.12/framework' is not a working copy
 
Last week it worked. Today it doesn't. Anyone have thoughts?

Thanks.

Brad

-
Here's a fragment of the -X output

[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-release-plugin:2.0-beta
-6:prepare' -->
[DEBUG]   (f) addSchema = true
[DEBUG]   (f) autoVersionSubmodules = false
[DEBUG]   (s) basedir = p:\eclipse-workspace-qa-2.4.12\framework
[DEBUG]   (f) commitByProject = false
[DEBUG]   (f) dryRun = false
[DEBUG]   (f) generateReleasePoms = false
[DEBUG]   (f) preparationGoals = clean verify
[DEBUG]   (f) project = [EMAIL PROTECTED]
[DEBUG]   (f) reactorProjects =
[EMAIL PROTECTED]

[DEBUG]   (f) resume = true
[DEBUG]   (f) scmCommentPrefix = [maven-release-plugin]
[DEBUG]   (f) settings = [EMAIL PROTECTED]
[DEBUG]   (f) updateDependencies = true
[DEBUG]   (f) useEditMode = false
[DEBUG] -- end configuration --
[INFO] [release:prepare]
[INFO] Resuming release from phase 'scm-commit-release'
[INFO] Checking in modified POMs...
[INFO] Executing: svn --non-interactive commit --file
c:\DOCUME~1\bsharp\LOCALS~
1\Temp\maven-scm-298175632.commit --targets
c:\DOCUME~1\bsharp\LOCALS~1\Temp\mav
en-scm-46278-targets
[INFO] Working directory: p:\eclipse-workspace-qa-2.4.12\framework
[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn:
'/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclipse-workspace-
qa-
2.4.12/framework' is not a working copy
svn: Can't open file
'/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclip
se-workspace-qa-2.4.12/framework/.svn/entries': No such file or
directory

[INFO]

[DEBUG] Trace
org.apache.maven.BuildFailureException: Unable to commit files
Provider message:
The svn command failed.
Command output:
svn:
'/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclipse-workspace-
qa-
2.4.12/framework' is not a working copy
svn: Can't open file
'/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclip
se-workspace-qa-2.4.12/framework/.svn/entries': No such file or
directory
...

Caused by: org.apache.maven.plugin.MojoFailureException: Unable to
commit files
Provider message:
The svn command failed.
Command output:
svn:
'/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclipse-workspace-
qa-
2.4.12/framework' is not a working copy
svn: Can't open file
'/cygdrive/p/eclipse-workspace-qa-2.4.12/framework/p:/eclip
se-workspace-qa-2.4.12/framework/.svn/entries': No such file or
directory
...

[INFO]

[INFO] Total time: 4 seconds
[INFO] Finished at: Fri Dec 14 12:45:11 CST 2007
[INFO] Final Memory: 5M/9M
[INFO]


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

[M2] Reproducible build

[Rémy Sanlaville]

Hi,

I would like to make sure that my project build is reproducible.
For instance, I want to be sure that I can package again a tagged version.

So I am looking for a tools that can compare two package (two jar, two war,
two ear...) and eventually shows the potential differences.
Do you know if a such tools exists ?

In order two verify if two package are identical, I was thinking of
generating and comparing the corresponding checksum (md5 or sha1) .
Do you think that it would be good enough ?

Rémy

Re: license-report

[Dennis Lundberg]

Julien Graglia wrote:

If i'm right, maven-remote-resources-plugin just allow to include some 
"bundles" in all generated ja : it can be used to include a LICENSE or NOTICE 
file.

But I think that Andreas is looking for a plugin that will generate a "License 
reports" listing all licenses used in his project (dependencies) , and by who..
Then, he can use this report to create a LICENSE/NOTICE file and include it in 
hist generated jars...

I 'am currently doing this by hand, but I'd love to find a plugin that will 
create such a report...!


maven-remote-resources can be used to automate this.



--
Julien Graglia




olivier lamy a écrit :

Hi,
Have a look at the maven-remote-resources-plugin and how it's used for the
maven build to License and Notice files.

--
Olivier

2007/12/10, Hoehmann, Andreas <[EMAIL PROTECTED]>:
  

Hello,

i need a file (LICENSES.TXT) which contains all dependend modules with
there licenses.
Exists a plugin to generate such a "license-report" for my project? I
use maven 2.

Best regards
Andreas

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



  






--
Dennis Lundberg


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

[M2] multi-modules vs multi-projects

[Rémy Sanlaville]

Hi,

I am looking for some criteria in order to can decide how to organized my
project.

For instance, I want to produce three artifacts a.jar, b.jar and c.war.
I can organized my project in different ways :
1) Multiple Projects
project A => a.jar
project B => b.jar
project C => c.war

2) Multi-modules project
parent project
|__ module A => a.jar
|__ module B => b.jar
|__ module C => c.war

3) Combination of multiple projects and Multi-modules project(s)
project A => a.jar
parent project
|__ module B => b.jar
|__ module C => c.war
...

I found that it's not always easy to found the good criteria in order to
choose or explain which project structure is better.
It seems that the release is a criterion because it's really structuring
(even more with maven).
For instance, if I always release all the artifacts in the same time, I will
choose the second option.

I will be happy to have your point of view about this question and if you
have some criteria to propose.

Rémy

Re: Using componentDescriptors with a multi-module assembly

[Westfall, Eric Curtis]

Right, I tried the following:


  standalone
  
war
  
  
path/to/component.xml
  
  false
  ...
  

  
false
WEB-INF/lib
  

  


The problem is that the jar excludes don't appear to be applied when packaging 
up the binaries from within the module sets.  Instead I get all of the 
dependencies from my modules in the WEB-INF/lib directory (including the ones 
I'm wanting to exclude)

Thanks,
Eric



On 12/14/07 10:37 AM, "Mick Knutson" <[EMAIL PROTECTED]> wrote:

In you assembly descriptor:


src/assemble/reusable-component.xml







On Dec 14, 2007 7:28 AM, Westfall, Eric Curtis <[EMAIL PROTECTED]> wrote:

> (sent this earlier but I don't think it made it through so I apologize if
> this reaches the list twice)
>
> Hello, I'm attempting to figure out how to use a componentDescriptors
> element with one of my assemblies for a multi-module project and I'm
> having
> some trouble.  My original assembly looked like:
>
> 
>  standalone
>  
>war
>  
>  false
>  ...
>  
>
>  
>
> 
>  true
>
>  junit:*
>  org.mortbay.jetty:*
>  tomcat:*
>  com.oracle:*
>  *:servlet-api
>  *:jsp-api
>
> 
>
>false
>WEB-INF/lib
>  
>
>  
> 
>
> I wanted to re-use that exclusion set in multiple assemblies so I created
> a
> component descriptor:
>
> 
>  
>
>  true
>  
>junit:*
>org.mortbay.jetty:*
>tomcat:*
>com.oracle:*
>*:servlet-api
>*:jsp-api
>  
>
>  
> 
>
> However, I can't seem to get this to work when I attempt to include it
> back
> in my original assembly.  At first I figured the 
> element would go into the moduleSet but I got "Unrecognised tag" errors
> when
> trying that.  Whenever I put the component descriptor at top-level under
>  the assembly would execute successfully but my exclusion list
> was not being honored for the individual module dependencies (so I would
> end
> up with junt, etc. in my WEB-INF/lib directory)
>
> Does anyone have an example of how I can make this work?  Any help would
> be
> greatly appreciated.
>
> Thank you,
> Eric
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/BLiNCMagazine
http://tahoe.baselogic.com
---



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

RE: Issue with jspc-maven-plugin - specifying uriroot

[Matthew Tordoff]

Hi Murali,

I think that this is a problem relating to the :

- Have you checked that the  is an existing
directory?
- I also read somewhere that you also might have to specify the
 starting with ${basedir}/

Please let me know if either of these solutions help.

Regards,

Matt

-Original Message-
From: S.Murali [mailto:[EMAIL PROTECTED] 
Sent: 14 December 2007 16:08
To: users@maven.apache.org
Subject: Issue with jspc-maven-plugin - specifying uriroot


Hi,
I using jspc-maven-plugin pre-compile my JSP in a war packaged module.
I am using following plugin configuration


org.codehaus.mojo.jspc
jspc-maven-plugin


check-jsp-source
process-sources

 compile




../mymodule/vfe/WEB-INF/web.xml
../mymodule/vfe





org.codehaus.mojo.jspc
jspc-compiler-tomcat6
2.0-SNAPSHOT  




On building module, I am getting following exception. 

[INFO] Compiling JSP source files to
/home/dev1/codebase/sandbox/teams/work/dev3/mymodule/target/jsp-source
[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] The -uriroot option must specify a pre-existing directory [INFO]

[INFO] Trace
org.apache.jasper.JasperException: The -uriroot option must specify a
pre-existing directory
at org.apache.jasper.JspC.execute(JspC.java:1128)
at
org.codehaus.mojo.jspc.compiler.tomcat6.JspCompilerImpl.compile(JspCompi
lerImpl.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(Reflec
tionMetaMethod.java:52)
at
org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke(MetaClassHelp
er.java:714)
at
groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:583)
at
groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:476)
at
org.codehaus.groovy.runtime.Invoker.invokePojoMethod(Invoker.java:104)
at
org.codehaus.groovy.runtime.Invoker.invokeMethod(Invoker.java:77)
at
org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.jav
a:85)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodN(ScriptBy
tecodeAdapter.java:158)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethod0(ScriptBy
tecodeAdapter.java:182)
at
org.codehaus.mojo.jspc.CompilationMojoSupport.execute(CompilationMojoSup
port.groovy:333)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:140)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

I have no clue how to set the -uriroot to have these JSPs pre-compiled.
Pl.
let know if you any idea on this.

Thanks, Murali
--
View this message in context:
http://www.nabble.com/Issue-with-jspc-maven-plugin---specifying-uriroot-
tp14338706s177p14338706.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To un

Re: Building war with multi-module classes and no module jars

[Tomislav Stojcevich]

maven isn't really setup to be able to "reach into" other projects, to
use artifacts created in other projects, you should go through jars
via the repo

You can however still do it by using the antrun plugin and ant's copy
target with relative referencing  "../project-a/target/classes", but
doing so you loose true project independence (and you won't be able to
add the projects individually to continuum if you use continuum).

To stop the jar packaging you could:
1 - just call mvn compile in the common project, that won't jar up the classes
2 - change the project type in the pom from jar to pom, but then
you'll have to setup each plugin you want to call since the jar
lifecycle won't get called


Couldn't you just add the class file post processing to the projects
that the class files are compiled in?

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

Re: own plugin without need for pom.xml

[Peter Fischer]

Hello,

next question? ;)

The DeployFileMojo uses a method getDeployer() of the AbstractDeployMojo
class;

I also tried to extend the AbstractDeployMojo class, but now getDeployer()
returns only null.
What do I wrong?

regards,
Peter
-- 
View this message in context: 
http://www.nabble.com/own-plugin-without-need-for-pom.xml-tp14318109s177p14339201.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]

Re: Building war with multi-module classes and no module jars

[bayamos]

Thanks for the reply.

What I would like to be able to do is copy the classes from from the other
modules target/classes directories into the war's target/classes directory. 
I would also like to stop the package phase of the jars since I will not be
using them and make the build go faster.  It is a very large project.

Is this possible?



stojcevicht wrote:
> 
> You can use the dependency:unpack
> http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html
> to unpack the classes from the jars.
> 
> -
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Building-war-with-multi-module-classes-and-no-module-jars-tp14332309s177p14338754.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]

Issue with jspc-maven-plugin - specifying uriroot

[S.Murali]

Hi, 
I using jspc-maven-plugin pre-compile my JSP in a war packaged module.  I am
using following plugin configuration


org.codehaus.mojo.jspc
jspc-maven-plugin


check-jsp-source
process-sources

 compile




../mymodule/vfe/WEB-INF/web.xml
../mymodule/vfe





org.codehaus.mojo.jspc
jspc-compiler-tomcat6
2.0-SNAPSHOT
 




On building module, I am getting following exception. 

[INFO] Compiling JSP source files to
/home/dev1/codebase/sandbox/teams/work/dev3/mymodule/target/jsp-source
[INFO]

[ERROR] FATAL ERROR
[INFO]

[INFO] The -uriroot option must specify a pre-existing directory
[INFO]

[INFO] Trace
org.apache.jasper.JasperException: The -uriroot option must specify a
pre-existing directory
at org.apache.jasper.JspC.execute(JspC.java:1128)
at
org.codehaus.mojo.jspc.compiler.tomcat6.JspCompilerImpl.compile(JspCompilerImpl.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.groovy.runtime.metaclass.ReflectionMetaMethod.invoke(ReflectionMetaMethod.java:52)
at
org.codehaus.groovy.runtime.MetaClassHelper.doMethodInvoke(MetaClassHelper.java:714)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:583)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:476)
at
org.codehaus.groovy.runtime.Invoker.invokePojoMethod(Invoker.java:104)
at org.codehaus.groovy.runtime.Invoker.invokeMethod(Invoker.java:77)
at
org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:85)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodN(ScriptBytecodeAdapter.java:158)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethod0(ScriptBytecodeAdapter.java:182)
at
org.codehaus.mojo.jspc.CompilationMojoSupport.execute(CompilationMojoSupport.groovy:333)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

I have no clue how to set the -uriroot to have these JSPs pre-compiled.  Pl.
let know if you any idea on this.

Thanks, Murali
-- 
View this message in context: 
http://www.nabble.com/Issue-with-jspc-maven-plugin---specifying-uriroot-tp14338706s177p14338706.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]

Re: Errror while running the target mvn:archetype

[Wayne Fay]

You need to specify what archetype to use. I'd guess you want to use
maven-archetype-simple or maven-archetype-quickstart.

Here's a list:
http://maven.apache.org/plugins/maven-archetype-plugin/
and
http://docs.codehaus.org/display/MAVENUSER/Archetypes+List

Here's the full command:
mvn archetype:create\
  -DarchetypeGroupId=\
  -DarchetypeArtifactId=  \
  -DarchetypeVersion=\
  -DgroupId=\
  -DartifactId=

Wayne

On 12/14/07, Aneena <[EMAIL PROTECTED]> wrote:
>
> I'm getting the following error please help me to solve this
>
> D:\Annhunts>mvn archetype:create -DgroupId=com.mycompany.app
> -DartifactId=my-app
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'archetype'.
> [INFO] org.apache.maven.plugins: checking for updates from central
> [INFO] org.codehaus.mojo: checking for updates from central
> [INFO] artifact org.apache.maven.plugins:maven-archetype-plugin: checking
> for up
> dates from central
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-archet
> ype-plugin/1.0-alpha-7/maven-archetype-plugin-1.0-alpha-7.pom
> 4K downloaded
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/archetype/maven-arch
> etype/1.0-alpha-7/maven-archetype-1.0-alpha-7.pom
> 3K downloaded
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/archetype/maven-arch
> etype-parent/2/maven-archetype-parent-2.pom
> 2K downloaded
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/maven-parent/5/maven
> -parent-5.pom
> 14K downloaded
> Downloading: http://repo1.maven.org/maven2/org/apache/apache/3/apache-3.pom
> 3K downloaded
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-archet
> ype-plugin/1.0-alpha-7/maven-archetype-plugin-1.0-alpha-7.jar
> 2K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '9eaf6ba99d
> 12f776fb14d486ab2942887dfcc55a'; remote =
> 'b0280b2e376542c692104f38b14a4892e509a
> 379' - RETRYING
> Downloading:
> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-archet
> ype-plugin/1.0-alpha-7/maven-archetype-plugin-1.0-alpha-7.jar
> 2K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '009aa04756
> a4faf583ae3f70bac15f780ba10a11'; remote =
> 'b0280b2e376542c692104f38b14a4892e509a
> 379' - IGNORING
> [INFO]
> 
> [ERROR] FATAL ERROR
> [INFO]
> 
> [INFO] The PluginDescriptor for the plugin Plugin
> [org.apache.maven.plugins:mave
> n-archetype-plugin] was not found.
> [INFO]
> 
> [INFO] Trace
> java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin
> [org
> .apache.maven.plugins:maven-archetype-plugin] was not found.
>at
> org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginM
> anager.java:321)
>at
> org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(De
> faultPluginManager.java:208)
>at
> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlug
> inManager.java:172)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa
> ultLifecycleExecutor.java:1257)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor
> (DefaultLifecycleExecutor.java:1522)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListBy
> AggregationNeeds(DefaultLifecycleExecutor.java:386)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:138)
>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
>at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
>at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:324)
>at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>
>at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO]
> 
> [INFO] Total time: 15 seconds
> [INFO] Finished at: Thu Dec 13 20:06:36 IST 2007
> [INFO] Final Memory: 1M/3M
> [INFO]
> 
> --
> View this message in context: 
> ht

[c-1.1] Anyone have Activa and CI running on the same Tomcat instance?

[Mick Knutson]

I have been trying for a few hours now. I can get Continuum.war with a Derby
DB running. But then when I add Activa.war I either be *no trace at
all*when I use the same user datasource as CI:

  **



or when I run a different Datasource like:

 **



SEVERE: Null component
Catalina:type=JspMonitor,name=jsp,WebModule=//localhost/archiva,J2EEApplication=none,J2EEServer=none
Dec 14, 2007 7:58:23 AM org.apache.catalina.startup.HostConfigdeployDescriptor
*SEVERE: Error deploying configuration descriptor archiva.xml*
*java.lang.ClassCastException: org.apache.tomcat.dbcp.dbcp.BasicDataSource
*




I also notice that in
/home/build/opt/*apache-tomcat-5.5.25/webapps/archiva*the war has not
been exploded.



Here is my continuum.xml:



  

  

  




-- 
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/BLiNCMagazine
http://tahoe.baselogic.com
---

Resolving snapshot filenames from Mojo

[ewhauser]

Hi,

I wrote a Mojo that generates a wrapper.conf file for installing ActiveMQ as
a service.  One of the things it generates is the class path:

wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.classpath.2=../lib/activemq-all-5.0-SNAPSHOT.jar
wrapper.java.classpath.3=../lib/activemq-core-5.0-SNAPSHOT.jar
wrapper.java.classpath.4=../lib/commons-logging-api-1.1.jar
wrapper.java.classpath.5=../lib/camel-core-1.2.0.jar
...

This works for except when using the assembly:assembly command, the files
are archived as their actual snapshot filename (i.e.
activeio-core-3.1-20071214.010031-268.jar,
activemq-core-5.0-20071208.031023-17.jar).  I am retrieving the classpath
references by looping over MavenProject#getRuntimeArtifacts and calling
Artifact#getFile#getName.

I am trying to figure out how to get the true snapshot filename, so so it
matches what is bundled through the assembly plugin.  Any help would be
appreciated.

Thanks.
-- 
View this message in context: 
http://www.nabble.com/Resolving-snapshot-filenames-from-Mojo-tp14338324s177p14338324.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]

Re: maven2 release plugin - no dependencies update

[Tomislav Stojcevich]

http://maven.apache.org/general.html#plugin-version

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

Re: maven2 release plugin - no dependencies update

[Tomasz Zieleniewski]

But this way I will loose tha independence of submodule version agains main
project version:/

how can I check wich version is acctualy used??

On Dec 14, 2007 3:49 PM, <[EMAIL PROTECTED]> wrote:

> Looking at central, I see beta-7 is already there, so you don't have to
> use snapshot.
>
> Maybe if you try it this way:
>
> > 
> >  
> >group
> >sub1
> >${pom.version}
> >provided
> >  
> > 
>
> Hth,
>
> Nick Stolwijk
>
> -Original Message-
> From: Tomasz Zieleniewski [mailto:[EMAIL PROTECTED]
> Sent: Fri 12/14/2007 3:37 PM
> To: Maven Users List
> Subject: Re: maven2 release plugin - no dependencies update
>
> Hi,
>
> what is the vesion tag for the snapshot version??
>
> regards
> tomasz
>
> On Dec 14, 2007 10:22 AM, <[EMAIL PROTECTED]> wrote:
>
> > If I recall correctly, the updateDependencies option was added recently.
> > As you see in the plugin page, it is for a snapshot version. Perhaps you
> are
> > using a stable version, which does not have this option included yet.
> >
> > As far as I know, the updateDependencies option is just what you need.
> >
> > With regards,
> >
> > Nick Stolwijk
> >
> >
> > -Original Message-
> > From: Tomasz Zieleniewski [mailto: [EMAIL PROTECTED]
> > Sent: Fri 12/14/2007 9:55 AM
> > To: users@maven.apache.org
> > Subject: maven2 release plugin - no dependencies update
> >
> > Hi,
> >
> > I have following problem.
> > I have a main maven project of the pom type which consists of 4
> > subprojects
> > of the type jar.
> > Two of my subprojects have dependency on the two previous ones.
> > When I invoke mvn release:prepare -D dryRun=true
> > everything works fine except that the dependencies from two last
> > subrojects
> > are not updated to the new dev version
> >
> > So for instance when I have following release state
> > pom - 1.0.0-SNAPSHOT
> > sub1 - 1.0-SNAPSHOT
> > sub2 - 1.0-SNAPSHOT
> > sub3 - 1.0-SNAPSHOT
> > sub4 - 1.0-SNAPSHOT
> >
> > and inside sub3 pom.xml such dependency
> > 
> >  
> >group
> >sub1
> >1.0-SNAPSHOT
> >provided
> >  
> > 
> >
> > and even if the version for sub1 is increased by release the dependency
> > version is not changed.
> > I tried to use -D*updateDependencies
> > <
> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#updateDependencies
> > >
> > <
> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#updateDependencies
> > >=true
> > but it didn't help*
> >
> > Is it an error or did I miss something?
> >
> > bests regards
> > tomasz zieleniewski
> >
> >
>
>

Re: [c-1.1] Need to understand hot to set MyProject_HOME for continuum

[Tomislav Stojcevich]

i see, i had a similar issue.  projects are independent and should not
'reach into' each other.

to use common stuff,  jar them up in one project, install them into
your repo, then in the other projects you can add as a dependency or
use the unpack goal of the dependency plugin to explode them into each
project that needs them.

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

Re: Using componentDescriptors with a multi-module assembly

[Mick Knutson]

In you assembly descriptor:


src/assemble/reusable-component.xml







On Dec 14, 2007 7:28 AM, Westfall, Eric Curtis <[EMAIL PROTECTED]> wrote:

> (sent this earlier but I don't think it made it through so I apologize if
> this reaches the list twice)
>
> Hello, I'm attempting to figure out how to use a componentDescriptors
> element with one of my assemblies for a multi-module project and I'm
> having
> some trouble.  My original assembly looked like:
>
> 
>  standalone
>  
>war
>  
>  false
>  ...
>  
>
>  
>
> 
>  true
>
>  junit:*
>  org.mortbay.jetty:*
>  tomcat:*
>  com.oracle:*
>  *:servlet-api
>  *:jsp-api
>
> 
>
>false
>WEB-INF/lib
>  
>
>  
> 
>
> I wanted to re-use that exclusion set in multiple assemblies so I created
> a
> component descriptor:
>
> 
>  
>
>  true
>  
>junit:*
>org.mortbay.jetty:*
>tomcat:*
>com.oracle:*
>*:servlet-api
>*:jsp-api
>  
>
>  
> 
>
> However, I can't seem to get this to work when I attempt to include it
> back
> in my original assembly.  At first I figured the 
> element would go into the moduleSet but I got "Unrecognised tag" errors
> when
> trying that.  Whenever I put the component descriptor at top-level under
>  the assembly would execute successfully but my exclusion list
> was not being honored for the individual module dependencies (so I would
> end
> up with junt, etc. in my WEB-INF/lib directory)
>
> Does anyone have an example of how I can make this work?  Any help would
> be
> greatly appreciated.
>
> Thank you,
> Eric
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/BLiNCMagazine
http://tahoe.baselogic.com
---

Re: [c-1.1] Need to understand hot to set MyProject_HOME for continuum

[Mick Knutson]

This variable is set for several different modules to use the same common
base for tests files. So '.' would assume that I am copying them over to
each module in my tree. When there is actually only one copy.


On Dec 14, 2007 7:30 AM, Tomislav Stojcevich <[EMAIL PROTECTED]> wrote:

> Can't you just use . for "current directory" instead of a variable?
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/BLiNCMagazine
http://tahoe.baselogic.com
---

Re: [c-1.1] Need to understand hot to set MyProject_HOME for continuum

[Tomislav Stojcevich]

Can't you just use . for "current directory" instead of a variable?

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

Using componentDescriptors with a multi-module assembly

[Westfall, Eric Curtis]

(sent this earlier but I don't think it made it through so I apologize if
this reaches the list twice)

Hello, I'm attempting to figure out how to use a componentDescriptors
element with one of my assemblies for a multi-module project and I'm having
some trouble.  My original assembly looked like:


  standalone
  
war
  
  false
  ...
  

  

 
  true

  junit:*
  org.mortbay.jetty:*
  tomcat:*
  com.oracle:*
  *:servlet-api
  *:jsp-api

 

false
WEB-INF/lib
  

  


I wanted to re-use that exclusion set in multiple assemblies so I created a
component descriptor:


  

  true
  
junit:*
org.mortbay.jetty:*
tomcat:*
com.oracle:*
*:servlet-api
*:jsp-api
  

  


However, I can't seem to get this to work when I attempt to include it back
in my original assembly.  At first I figured the 
element would go into the moduleSet but I got "Unrecognised tag" errors when
trying that.  Whenever I put the component descriptor at top-level under
 the assembly would execute successfully but my exclusion list
was not being honored for the individual module dependencies (so I would end
up with junt, etc. in my WEB-INF/lib directory)

Does anyone have an example of how I can make this work?  Any help would be
greatly appreciated.

Thank you,
Eric



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

FOUND SOLUTION Re: Proxying SNAPSHOT repositories

[gumnaam23]

Found the problem.
The culprit seems to be Maven 2.0.7+. It has problems with SNAPSHOT
dependency resolution with mirrorOf set tp *.

The solution is outlined here.
http://www.jfrog.org/sites/artifactory/latest/maven.html

I did as the post suggested and it worked.
May be this should end up on the WIKI, or archiva proxy setup guide.

thanks


Brett Porter wrote:
> 
> I've been seeing this also - I'm not yet sure of the conditions under
> which they don't work. I have seen it work for the majority of
> snapshots - but particularly those with long versions beforehand seem
> problematic.
> 
> I intend to investigate next week - if you can create an issue that'd
> be helpful.
> 
> Cheers,
> Brett
> 
> On 15/12/2007, gumnaam23 <[EMAIL PROTECTED]> wrote:
>>
>> I have setup Archiva Managed Internal Repository as my whole and sole
>> mirror
>> in my settings.xml.
>> The settings.xml does not contain any other repository information, just
>> the
>> mirror entry .
>>
>> The Archiva Manged Internal Repository is set to proxy 4/5 external
>> repositories,
>> One of which contains certain SNAPSHOTs that I have as dependencies.
>>
>> The proxy connector for this repository has snapshot policy set to
>> "always",
>> I also tried
>> "daily", "hourly". But the SNAPSHOT is never downloaded any my build
>> fails.
>>
>> The log files show no special activity, how do I debug this issue ?
>> --
>> View this message in context:
>> http://www.nabble.com/Proxying-SNAPSHOT-repositories-tp14336170p14336170.html
>> Sent from the archiva-users mailing list archive at Nabble.com.
>>
>>
> 
> 
> -- 
> Brett Porter
> Blog: http://www.devzuz.org/blogs/bporter/
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Proxying-SNAPSHOT-repositories-tp14336170p14337896.html
Sent from the archiva-users mailing list archive at Nabble.com.

Re: [c-1.1] Need to understand hot to set MyProject_HOME for continuum

[Mick Knutson]

No one can help me out here?

On Dec 13, 2007 5:56 PM, Mick Knutson <[EMAIL PROTECTED]> wrote:

> In my normal Manen build, I have a variable called MyProject_HOME set to *
> C:\opt\MyProject* and I use that throughout my build. Now I want to
> understand where to set that in order to still run Continuum?
>
> Am I going to set a another system variable to *
> /opt/contiuum/workingDirectory/*
>
>
>
>
> --
> Thanks,
> Mick Knutson
>
> http://www.baselogic.com
> http://www.blincmagazine.com
> http://www.djmick.com
> http://www.myspace.com/mickknutson
> http://www.myspace.com/BLiNCMagazine
> http://tahoe.baselogic.com
> ---




-- 
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/BLiNCMagazine
http://tahoe.baselogic.com
---

Re: own plugin without need for pom.xml

[Peter Fischer]

Hello,

I use maven as build-tool and need many not mavenized equinox-bundles in an
internal project (gmf, ...). Upgrading to a new version of this set of
bundles is much stupid work.


struberg wrote:
> 
> Peter, just out of curiosity: How do you decide which groupId, artifactId
> and versionId you should
> take for each jar?
> 

You 'r right, the separation, of what is groupId and what is artifactId is
not included in the manifest-file. For me, I decided to use the whole
"Bundle-SymbolicName" for both. 
"Bundle-Version" is used for the maven-version.

The greater problem is the dependency-version. For this, I have to deploy
all needed jars together, so that the version of the previously parsed
manifest-file of the needed jar is used. 

I know that this is not the best solution, but for the moment it works.

But I don't know, if someone else would be interested in using this hack...

regards,
Peter
-- 
View this message in context: 
http://www.nabble.com/own-plugin-without-need-for-pom.xml-tp14318109s177p14337471.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]

Re: Profiles and filtering - global files

[Mick Knutson]

You could make a system variable PROJECT_ROOT other than that I don't know.

On Dec 13, 2007 11:56 PM, heimlich <[EMAIL PROTECTED]> wrote:

>
> Thanks a lot, Mick. That ought to do the trick. One question though, is
> there
> any way to avoid having a hardcoded path as projectRoot? What I'm looking
> for is some way of defining the top-level pom directory (e.g.
> ${toplevel.project.dir} that points to the directory where I started my
> mvn
> command).
>
> I'm sorry I'm not able to return the favor by helping you out in turn...
>
>
>
>
> Mick Knutson-4 wrote:
> >
> > I have solved that issue by setting a projectRoot variable:
> >
> > 
> > local
> > 
> > 
> > 
> >
>  C:/viewstore/esp_lynx_dap/esp/dap
> > 
> >
> > Then my filter is:
> >
> > 
> > local
> > 
> > 
> > ${projectRoot}/src/main/filters/filter-
> > local.properties
> > 
> > 
> > 
> >
> > 
> > dev-
> > 
> > 
> > ${projectRoot}/src/main/filters/filter-
> > dev-.properties
> > 
> > 
> > 
> >
> >
> > Then they all use the same filter.
> >
> > But I have an issue where only the local filter is picked up.
> > Any idea how to override each filter as a profile?
> >
> >
> >
> > On Dec 4, 2007 12:05 PM, CasMeiron <[EMAIL PROTECTED]> wrote:
> >
> >> Yes, i got this problem too this week.
> >>
> >> On Dec 4, 2007 7:40 AM, heimlich <[EMAIL PROTECTED]> wrote:
> >>
> >> >
> >> > Hi all,
> >> >
> >> > I'm in a bit of a pickle, and I'm hoping someone can help me out.
> >> >
> >> > I have an extensive Maven project with the following layout:
> >> >
> >> > project A, packaging: pom
> >> >  project A.A, packaging: pom
> >> >project A.A.A, packaging: jar
> >> >project A.A.B, packaging: jar
> >> >project A.A.C, packaging: war
> >> >...
> >> >  project A.B, packaging: pom
> >> >project A.B.A, packaging: jar
> >> >project A.B.B, packaging: war
> >> >project A.B.C, packaging: war
> >> >  ...
> >> >
> >> > And I have a global properties file used as a configuration file that
> I
> >> > want
> >> > filtered depending on which profile I run:
> >> >
> >> > # conf.properties
> >> > URL_TO_SERVER1=${env.server1.address}
> >> > URL_TO_SERVER2=${env.server1.address}
> >> > ...
> >> >
> >> > And I have three filter files:
> >> >
> >> > #dev.properties
> >> > env.server1.address=server1.dev.example.com
> >> > env.server2.address=server2.dev.example.com
> >> >
> >> > #test.properties
> >> > env.server1.address=server1.test.example.com
> >> > env.server2.address=server2.test.example.com
> >> >
> >> > #prod.properties
> >> > env.server1.address=server1.prod.example.com
> >> > env.server2.address=server2.prod.example.com
> >> >
> >> > Now, How do I configure the top POM (project A above) to filter
> >> > conf.properties using (say) filter dev.properties.
> >> >
> >> > I had a go at it with the following top POM:
> >> >
> >> > 
> >> >  4.0.0
> >> >  com.example
> >> >  projA
> >> >  pom
> >> >  1.0-SNAPSHOT
> >> >  Project A
> >> >  
> >> >  
> >> >  
> >> >A
> >> >B
> >> >  
> >> >  
> >> > ...
> >> >  
> >> >  
> >> >
> >> >  junit
> >> >  junit
> >> >  test
> >> >
> >> >  
> >> >  
> >> >
> >> >  dev
> >> >  
> >> >true
> >> >  
> >> >  
> >> >
> >> >  ${basedir}/filters/dev.properties
> >> >
> >> >
> >> >  
> >> >src/main/resources
> >> >true
> >> >  
> >> >
> >> >  
> >> >
> >> >
> >> >  test
> >> >  
> >> >
> >> >  ${basedir}/filters/test.properties
> >> >
> >> >
> >> >  
> >> >src/main/resources
> >> >true
> >> >  
> >> >
> >> >  
> >> >
> >> >
> >> >  prod
> >> >  
> >> >
> >> >  ${basedir}/filters/prod.properties
> >> >
> >> >
> >> >  
> >> >src/main/resources
> >> >true
> >> >  
> >> >
> >> >  
> >> >
> >> >  
> >> > 
> >> >
> >> > The problem is that each subproject tries to refer to the 'filters'
> >> > directory IN ITS OWN directory structure,
> >> > not the one at the top.
> >> >
> >> > The reason for this structure is that I want:
> >> >
> >> > ONE conf.properties
> >> > ONE filter file per profile
> >> >
> >> > and I want the filtered conf.properties copied into
> src/main/resources
> >> of
> >> > each subproject
> >> > (I'm, willing to consider having copies of an unfiltered
> >> conf.propertiesin
> >> > each project's resources directory).
> >> > Can it be done (how?) or should try a different approach (any
> >> > suggestions)?
> >> >
> >> > Or should I have no filtering, and just three different properties
> >> files
> >> > (d

RE: maven2 release plugin - no dependencies update

[nicklist]

Looking at central, I see beta-7 is already there, so you don't have to use 
snapshot.

Maybe if you try it this way:

> 
>  
>group
>sub1
>${pom.version}
>provided
>  
> 

Hth,

Nick Stolwijk

-Original Message-
From: Tomasz Zieleniewski [mailto:[EMAIL PROTECTED]
Sent: Fri 12/14/2007 3:37 PM
To: Maven Users List
Subject: Re: maven2 release plugin - no dependencies update
 
Hi,

what is the vesion tag for the snapshot version??

regards
tomasz

On Dec 14, 2007 10:22 AM, <[EMAIL PROTECTED]> wrote:

> If I recall correctly, the updateDependencies option was added recently.
> As you see in the plugin page, it is for a snapshot version. Perhaps you are
> using a stable version, which does not have this option included yet.
>
> As far as I know, the updateDependencies option is just what you need.
>
> With regards,
>
> Nick Stolwijk
>
>
> -Original Message-
> From: Tomasz Zieleniewski [mailto: [EMAIL PROTECTED]
> Sent: Fri 12/14/2007 9:55 AM
> To: users@maven.apache.org
> Subject: maven2 release plugin - no dependencies update
>
> Hi,
>
> I have following problem.
> I have a main maven project of the pom type which consists of 4
> subprojects
> of the type jar.
> Two of my subprojects have dependency on the two previous ones.
> When I invoke mvn release:prepare -D dryRun=true
> everything works fine except that the dependencies from two last
> subrojects
> are not updated to the new dev version
>
> So for instance when I have following release state
> pom - 1.0.0-SNAPSHOT
> sub1 - 1.0-SNAPSHOT
> sub2 - 1.0-SNAPSHOT
> sub3 - 1.0-SNAPSHOT
> sub4 - 1.0-SNAPSHOT
>
> and inside sub3 pom.xml such dependency
> 
>  
>group
>sub1
>1.0-SNAPSHOT
>provided
>  
> 
>
> and even if the version for sub1 is increased by release the dependency
> version is not changed.
> I tried to use -D*updateDependencies
>  >
>  >=true
> but it didn't help*
>
> Is it an error or did I miss something?
>
> bests regards
> tomasz zieleniewski
>
>

Re: maven2 release plugin - no dependencies update

[Tomasz Zieleniewski]

Hi,

what is the vesion tag for the snapshot version??

regards
tomasz

On Dec 14, 2007 10:22 AM, <[EMAIL PROTECTED]> wrote:

> If I recall correctly, the updateDependencies option was added recently.
> As you see in the plugin page, it is for a snapshot version. Perhaps you are
> using a stable version, which does not have this option included yet.
>
> As far as I know, the updateDependencies option is just what you need.
>
> With regards,
>
> Nick Stolwijk
>
>
> -Original Message-
> From: Tomasz Zieleniewski [mailto: [EMAIL PROTECTED]
> Sent: Fri 12/14/2007 9:55 AM
> To: users@maven.apache.org
> Subject: maven2 release plugin - no dependencies update
>
> Hi,
>
> I have following problem.
> I have a main maven project of the pom type which consists of 4
> subprojects
> of the type jar.
> Two of my subprojects have dependency on the two previous ones.
> When I invoke mvn release:prepare -D dryRun=true
> everything works fine except that the dependencies from two last
> subrojects
> are not updated to the new dev version
>
> So for instance when I have following release state
> pom - 1.0.0-SNAPSHOT
> sub1 - 1.0-SNAPSHOT
> sub2 - 1.0-SNAPSHOT
> sub3 - 1.0-SNAPSHOT
> sub4 - 1.0-SNAPSHOT
>
> and inside sub3 pom.xml such dependency
> 
>  
>group
>sub1
>1.0-SNAPSHOT
>provided
>  
> 
>
> and even if the version for sub1 is increased by release the dependency
> version is not changed.
> I tried to use -D*updateDependencies
>  >
>  >=true
> but it didn't help*
>
> Is it an error or did I miss something?
>
> bests regards
> tomasz zieleniewski
>
>

provided dep + tomcat:deploy + performRelease = "package XXX does not exist"

[Alexandre Gomes]

I'm not sure if I found a bug in tomcat-maven-plugin or if it's an expected
behaviour [1].

1) Create a project with a "provided" scoped dependency [2]
2) Try to execute tomcat:deploy with -DperformRelease=true [3]
3) During the javadoc:jar phase, a warning is raised [4]

[1]

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

[2]


   xstream
   xstream
   1.0.1
   provided
   jar


[3]

mvn tomcat:deploy
-Dmaven.tomcat.url=http://192.168.1.40:8080/manager-DperformRelease=true

[4]

[INFO] Javadoc Warnings
[WARNING]
/Users/alegomes/Documents/tmp/seaup.sea/src/main/java/br/com/seatecnologia/seaup/negocio/ConvertendoXML.java:5:
package com.thoughtworks.xstream does not exist
[WARNING] import com.thoughtworks.xstream.XStream;
[WARNING] ^
[INFO] Building jar: /Users/alegomes/Documents/tmp/seaup.sea/target/seaup-
javadoc.jar


thanks
Alexandre Gomes

Re: maven2 release plugin - no dependencies update

[Tomasz Zieleniewski]

Hi,

releaseManagement ??
where is it? You mean pluginManagement??
I tried plugin management but tha same the version number was not changed in
the main
pom

Regards
Tomasz

On Dec 14, 2007 10:17 AM, maarten roosendaal <[EMAIL PROTECTED]> wrote:

> try using the releaseManagement tags in you root pom.xml, that way you
> will not have to define a version (and/or groupId) in the pom.xml's of the
> children. Works perfectly for me.
>
> Regards,
> Maarten
>
> - Original Message 
> From: Tomasz Zieleniewski <[EMAIL PROTECTED]>
> To: users@maven.apache.org
> Sent: Friday, December 14, 2007 9:55:28 AM
> Subject: maven2 release plugin - no dependencies update
>
>
> Hi,
>
> I have following problem.
> I have a main maven project of the pom type which consists of 4
>  subprojects
> of the type jar.
> Two of my subprojects have dependency on the two previous ones.
> When I invoke mvn release:prepare -D dryRun=true
> everything works fine except that the dependencies from two last
>  subrojects
> are not updated to the new dev version
>
> So for instance when I have following release state
> pom - 1.0.0-SNAPSHOT
> sub1 - 1.0-SNAPSHOT
> sub2 - 1.0-SNAPSHOT
> sub3 - 1.0-SNAPSHOT
> sub4 - 1.0-SNAPSHOT
>
> and inside sub3 pom.xml such dependency
> 
>  
>group
>sub1
>1.0-SNAPSHOT
>provided
>  
> 
>
> and even if the version for sub1 is increased by release the dependency
> version is not changed.
> I tried to use -D*updateDependencies
> <
> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#updateDependencies
> >
> <
> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#updateDependencies
> >=true
> but it didn't help*
>
> Is it an error or did I miss something?
>
> bests regards
> tomasz zieleniewski
>
>
>
>
>
>
>
>  
> 
> Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile.  Try it now.
> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
>

Proxying SNAPSHOT repositories

[gumnaam23]

I have setup Archiva Managed Internal Repository as my whole and sole mirror
in my settings.xml.
The settings.xml does not contain any other repository information, just the
mirror entry .

The Archiva Manged Internal Repository is set to proxy 4/5 external
repositories,
One of which contains certain SNAPSHOTs that I have as dependencies.

The proxy connector for this repository has snapshot policy set to "always",
I also tried
"daily", "hourly". But the SNAPSHOT is never downloaded any my build fails.

The log files show no special activity, how do I debug this issue ?
-- 
View this message in context: 
http://www.nabble.com/Proxying-SNAPSHOT-repositories-tp14336170p14336170.html
Sent from the archiva-users mailing list archive at Nabble.com.

Re: Building war with multi-module classes and no module jars

[Tomislav Stojcevich]

You can use the dependency:unpack
http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html
to unpack the classes from the jars.

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

Cannot use archiva browse function after 2 days running

[Julien CARSIQUE]

Hello,

Sorry for the precedent message with subject from another thread.

We use Archiva 1.0.
I have to restart it every one or two days; if not, archiva becomes
unstable :

   * main page and admin section are accessible and work fine,
   * archiva/browse/ function is dead :


   Proxy Error

 The proxy server received an invalid response from an upstream server.
 The proxy server could not handle the request /GET /archiva/browse
 /.

 Reason: *Error reading from remote server*


   * artifact resolution is very slow, sometimes down.

Restarting archiva immediately solves the problem.

I don't see explicit logs about this, all I can find in archiva.log is
some warnings (not raised when clicking on browse button) like those :
|29910993 [SocketListener0-7] WARN
org.apache.maven.archiva.web.tags.DependencyTree:default  - Unable to
generate graph for
[org.nuxeo.ecm.platform:nuxeo-platform-events-core:5.1.3-20071121.011030-30] 


: Unable to create ArchivaArtifact with empty version
[org.nuxeo.common:nuxeo-common:null::pom]
org.apache.maven.archiva.dependency.graph.GraphTaskException: Unable to
create ArchivaArtifact with empty version
[org.nuxeo.common:nuxeo-common:null::pom]
   at
org.apache.maven.archiva.dependency.DependencyGraphFactory.getGraph(DependencyGraphFactory.java:151)
   at
org.apache.maven.archiva.web.tags.DependencyTree.fetchGraph(DependencyTree.java:245)
   at
org.apache.maven.archiva.web.tags.DependencyTree.gatherTreeList(DependencyTree.java:144)
   at
org.apache.maven.archiva.web.tags.DependencyTreeTag.doStartTag(DependencyTreeTag.java:134)
   at
org.apache.jsp.WEB_002dINF.jsp.artifact.dependencyTree_jsp._jspx_meth_archiva_dependency$1tree_0(dependencyTree_jsp.java:93)
   at
org.apache.jsp.WEB_002dINF.jsp.artifact.dependencyTree_jsp._jspService(dependencyTree_jsp.java:64)
   (...)
Caused by: java.lang.IllegalArgumentException: Unable to create
ArchivaArtifact with empty version [org.nuxeo.common:nuxeo-common:null::pom]
   at
org.apache.maven.archiva.model.ArchivaArtifact.(ArchivaArtifact.java:56)
   at
org.apache.maven.archiva.repository.project.resolvers.ManagedRepositoryProjectResolver.resolveProjectModel(ManagedRepositoryProjectResolver.java:54)
   at
org.apache.maven.archiva.repository.project.resolvers.ProjectModelResolverStack.findProject(ProjectModelResolverStack.java:96)
   at
org.apache.maven.archiva.repository.project.dependencies.ProjectModelBasedGraphBuilder.resolveModel(ProjectModelBasedGraphBuilder.java:84)
   at
org.apache.maven.archiva.repository.project.dependencies.ProjectModelBasedGraphBuilder.resolveNode(ProjectModelBasedGraphBuilder.java:71)
   at
org.apache.maven.archiva.dependency.graph.tasks.ResolveGraphTask.executeTask(ResolveGraphTask.java:84)
   at
org.apache.maven.archiva.dependency.graph.tasks.PopulateGraphMasterTask.executeTask(PopulateGraphMasterTask.java:60)
   at
org.apache.maven.archiva.dependency.DependencyGraphFactory.getGraph(DependencyGraphFactory.java:137)
   ... 88 more
|
or :
|39001320 [SocketListener0-7] WARN
org.apache.maven.archiva.repository.project.resolvers.ProjectModelResolutionListener:model-to-db 


- Unable to check for existing model from database: Error in JDO during
get of Database object id [stax:stax-api:1.0] of type
org.apache.maven.archiva.model.ArchivaProjectModel using no fetch-group
org.apache.maven.archiva.repository.project.ProjectModelException:
Unable to check for existing model from database: Error in JDO during
get of Database object id [stax:stax-api:1.0] of type
org.apache.maven.archiva.model.ArchivaProjectModel using no fetch-group
   at
org.apache.maven.archiva.database.project.ProjectModelToDatabaseListener.existsInDatabase(ProjectModelToDatabaseListener.java:98)
   (...)
Caused by: org.apache.maven.archiva.database.ArchivaDatabaseException:
Error in JDO during get of Database object id [stax:stax-api:1.0] of
type org.apache.maven.archiva.model.ArchivaProjectModel using no fetch-group
   at
org.apache.maven.archiva.database.jdo.JdoAccess.getObjectById(JdoAccess.java:452)
   at
org.apache.maven.archiva.database.jdo.JdoProjectModelDAO.getProjectModel(JdoProjectModelDAO.java:74)
   at
org.apache.maven.archiva.database.project.ProjectModelToDatabaseListener.existsInDatabase(ProjectModelToDatabaseListener.java:86)
   ... 96 more
Caused by: javax.jdo.JDODataStoreException: Fetch request failed: SELECT
THIS.CI_MANAGEMENT_URL_OID,THIS.DESCRIPTION,THIS.ISSUE_MANAGEMENT_URL_OID,THIS."NAME",THIS.ORGANIZATION_NAME_OID,THIS.ORIGIN,THIS.PACKAGING,THIS.PARENT_PROJECT_ARCHIVA_VERSIONED_REFERENCE_ID_OID,THIS.RELOCATION_ARCHIVA_VERSIONED_REFERENCE_ID_OID,THIS.SCM_ARCHIVA_SCM_ID_OID,THIS.URL,THIS.WHEN_INDEXED,THIS.ARTIFACT_ID,THIS.GROUP_ID,THIS.VERSION 


FROM SA.ARCHIVA_PROJECT THIS WHERE (THIS.ARTIFACT_ID=?) AND
(THIS.GROUP_ID=?) AND (THIS.VERSION=?)
NestedThrowables:
SQL Exception: Java e

RE: [assembly] add all dependency jars to lib folder in a "bin" assembly

[Richard Chamberlain]

You'll need the manifest file to put "lib/" in front of all of its
classpath declarations.



4.0.0
groud.id
artefactid
 artefactid 
1.0-SNAPSHOT




org.apache.maven.plugins

maven-jar-plugin





main.classname.here


true

lib









-Original Message-
From: Erik Drolshammer [mailto:[EMAIL PROTECTED] 
Sent: 14 December 2007 07:11
To: Maven Users List
Subject: Re: [assembly] add all dependency jars to lib folder in a "bin"
assembly

Richard Chamberlain wrote:
> Hi.
> 
> I use the following:
> 
> 
>   
>   /lib 
>   false 
>   runtime 
>   
> 
> 
> It puts all the dependencies into lib.

Any idea how to add the contents of lib to classpath?
(I have an executable jar file and when I add the dependencies to the 
lib folder the main class cannot be found.)

-- 
Regards
Erik Drolshammer

-
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: FATAL ERROR on release:prepare with a super-pom

[nicklist]

This is deep down in the maven-release code, so no, you don't have to adjust it.

Why are you using relativePath? If you remove it and do a mvn install the super 
pom is copied to your local repository and found from there.

With regards,

Nick Stolwijk

-Original Message-
From: javijava [mailto:[EMAIL PROTECTED]
Sent: Fri 12/14/2007 12:46 PM
To: users@maven.apache.org
Subject: RE: FATAL ERROR on release:prepare  with a super-pom
 



>De code at the linenumber is:
>
if ( trunkPath.endsWith( "/" ) )
{
trunkPath = trunkPath.substring( 0, trunkPath.length() - 1 );
}
if ( tagPath.endsWith( "/" ) )
{
tagPath = tagPath.substring( 0, tagPath.length() - 1 );
}
>

.Where are placed this lines? in a maven-configuration fike?
.i must modify this..or is only the way that maven work with paths?


>Which will throw an exception if your trunkPath or tagPath is empty.
Is possible, that the  tags in each sub-project are wrong?

i have the super-pom in a folder like the sub projects (same level), an
example of tags:


   xxx
   super-pom 
   0.1-SNAPSHOT
   ../super-pom/pom.xml


Thanks 4 the reply Nick.





-- 
View this message in context: 
http://www.nabble.com/FATAL-ERROR-on-release%3Aprepare--with-a-super-pom-tp14332951s177p14334423.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]

RE: FATAL ERROR on release:prepare with a super-pom

[javijava]

>De code at the linenumber is:
>
if ( trunkPath.endsWith( "/" ) )
{
trunkPath = trunkPath.substring( 0, trunkPath.length() - 1 );
}
if ( tagPath.endsWith( "/" ) )
{
tagPath = tagPath.substring( 0, tagPath.length() - 1 );
}
>

.Where are placed this lines? in a maven-configuration fike?
.i must modify this..or is only the way that maven work with paths?


>Which will throw an exception if your trunkPath or tagPath is empty.
Is possible, that the  tags in each sub-project are wrong?

i have the super-pom in a folder like the sub projects (same level), an
example of tags:


   xxx
   super-pom 
   0.1-SNAPSHOT
   ../super-pom/pom.xml


Thanks 4 the reply Nick.





-- 
View this message in context: 
http://www.nabble.com/FATAL-ERROR-on-release%3Aprepare--with-a-super-pom-tp14332951s177p14334423.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]

RE: FATAL ERROR on release:prepare with a super-pom

[nicklist]

De code at the linenumber is:

if ( trunkPath.endsWith( "/" ) )
{
trunkPath = trunkPath.substring( 0, trunkPath.length() - 1 );
}
if ( tagPath.endsWith( "/" ) )
{
tagPath = tagPath.substring( 0, tagPath.length() - 1 );
}

Which will throw an exception if your trunkPath or tagPath is empty.

So something is wrong with that, I don't know what.

With regards,

Nick Stolwijk


-Original Message-
From: javijava [mailto:[EMAIL PROTECTED]
Sent: Fri 12/14/2007 11:04 AM
To: users@maven.apache.org
Subject: FATAL ERROR on release:prepare  with a super-pom
 

Hi folks,

I'm trying to do a mv nrelease:prepare  from a super-pom that have a lsit of
proyects i want to release to the same version..

All was runing fine,asking the new version, the SCM TAG ..but just after
this i have a "FATAL ERROR" : java.lang.ArrayIndexOutOfBoundsException: 37
at
...shared.release.phase.RewritePomsForReleasePhase.TranslateUrlPath(RewritePomForReleasePhase.java:249)

If any one  know this issue, reply quickly please, i need do the release
this morning.

Thanks a lot to all for all.

Have a nice day and nice holydays!!
-- 
View this message in context: 
http://www.nabble.com/FATAL-ERROR-on-release%3Aprepare--with-a-super-pom-tp14332951s177p14332951.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]

FATAL ERROR on release:prepare with a super-pom

[javijava]

Hi folks,

I'm trying to do a mv nrelease:prepare  from a super-pom that have a lsit of
proyects i want to release to the same version..

All was runing fine,asking the new version, the SCM TAG ..but just after
this i have a "FATAL ERROR" : java.lang.ArrayIndexOutOfBoundsException: 37
at
...shared.release.phase.RewritePomsForReleasePhase.TranslateUrlPath(RewritePomForReleasePhase.java:249)

If any one  know this issue, reply quickly please, i need do the release
this morning.

Thanks a lot to all for all.

Have a nice day and nice holydays!!
-- 
View this message in context: 
http://www.nabble.com/FATAL-ERROR-on-release%3Aprepare--with-a-super-pom-tp14332951s177p14332951.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]

RE: Refresh local repository SNAPSHOTS every morning

[Mark Struberg]

Thomas, do you know what exactly causes the time delays? Your own snapshots or 
the snapshots you
take from external repositories?

for the 2nd case there is another option for you:

What if you use a maven-proxy for your company?

This way only the first guy in the morning (or much better the cruisecontrol or 
continuum server)
triggers the maven-proxy to look for new modules. 
All other colleagues will get the artifacts from the maven-proxy with almost no 
delay!


LieGrü,
strub


--- [EMAIL PROTECTED] schrieb:

> It's not a problem as much as a curiosity.  We just moved from Ant to
> Maven, and I want to reduce any increase of build times to ease the
> transition for the team - most of which have yet to migrate from the Ant
> branches of the projects to the new Maven-ized main line.  Building our
> main ear pulls down every SNAPSHOT war dependency, which takes >10 mins
> to package on the day's first run.  I have our CIS server doing builds
> on SCM changes + nightly, but I suppose I could remove nightly condition
> to eliminate this side effect.
> 
> Regards,
> -Blue
> 
> -Original Message-
> From: Wayne Fay [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, December 13, 2007 11:42 AM
> To: Maven Users List
> Subject: Re: Refresh local repository SNAPSHOTS every morning
> 
> You could probably use "mvn dependency:go-offline"... but as you said,
> it will act on all dependencies, not just SNAPSHOTs. (Why is this a
> problem for you?)
> 
> Wayne
> 
> On 12/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> > Is there a way to refresh the SNAPSHOTS in your local repository?  We 
> > have nightly builds for all of our projects, and every morning there 
> > are new SNAPSHOTS in our internal repository to pull down, whether 
> > they contain changes or not. I'd like to be able to update all of my 
> > local SNAPSHOTS every morning, instead of when I build a project for 
> > the first time of the day.
> >
> > Alternatively, if there's a mojo I can run while inside each project 
> > that will pull down their SNAPSHOT dependencies _without_ compiling, 
> > packaging, etc, I could run that as well, but I'm at a loss on what to
> 
> > use.  I thought I could attach dependency:purge-local-repository to 
> > phase 'validate' on a non-default profile, but that will act on all 
> > dependencies, not just SNAPSHOTS.
> >
> > Thanks,
> > -Blue
> >
> > Visit our website at http://www.ubs.com
> >
> > This message contains confidential information and is intended only 
> > for the individual named.  If you are not the named addressee you 
> > should not disseminate, distribute or copy this e-mail.  Please notify
> 
> > the sender immediately by e-mail if you have received this e-mail by 
> > mistake and delete this e-mail from your system.
> >
> > E-mail transmission cannot be guaranteed to be secure or error-free as
> 
> > information could be intercepted, corrupted, lost, destroyed, arrive 
> > late or incomplete, or contain viruses.  The sender therefore does not
> 
> > accept liability for any errors or omissions in the contents of this 
> > message which arise as a result of e-mail transmission.  If 
> > verification is required please request a hard-copy version.  This 
> > message is provided for informational purposes and should not be 
> > construed as a solicitation or offer to buy or sell any securities or 
> > related financial instruments.
> >


  Machen Sie Yahoo! zu Ihrer Startseite. Los geht's: 
http://de.yahoo.com/set

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

RE: Unable to remove maven default build definition

[Pallavi.Satish]

You can not delete that and you may find it very useful as well. Just try 
running it once. It will make your build faster.


Regards
Pallavi.

-Original Message-
From: Ingo Siebert [mailto:[EMAIL PROTECTED]
Sent: Friday, December 14, 2007 2:10 PM
To: [EMAIL PROTECTED]
Subject: Unable to remove maven default build definition

Hi,

i want to delete that
"clean install  --batch-mode --non-recursivepom.xml"
entry in my contiuum project, because i'm using ANT.

I've set the default attribute to false, but i still can't delete it.
The error message:

org.apache.maven.continuum.ContinuumException: can't remove default
build definition from project group

Why do i need it or why can't i delete it, if i use ANT?

Ingo



Show/hide Stack Trace
 org.apache.maven.continuum.ContinuumException: can't remove
default build definition from project group
at
org.apache.maven.continuum.core.action.RemoveBuildDefinitionFromProjectGroupAction.execute(RemoveBuildDefinitionFromProjectGroupAction.java:50)
at
org.apache.maven.continuum.DefaultContinuum.executeAction(DefaultContinuum.java:2810)
at
org.apache.maven.continuum.DefaultContinuum.removeBuildDefinitionFromProjectGroup(DefaultContinuum.java:2243)
at
org.apache.maven.continuum.web.action.BuildDefinitionAction.removeFromProjectGroup(BuildDefinitionAction.java:400)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:358)
at
com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192)
at
org.codehaus.plexus.xwork.interceptor.PlexusReleaseComponentInterceptor.intercept(PlexusReleaseComponentInterceptor.java:69)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.apache.maven.continuum.web.interceptor.ForceContinuumConfigurationInterceptor.intercept(ForceContinuumConfigurationInterceptor.java:72)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:149)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:178)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
org.codehaus.plexus.xwork.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:58)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115)
at
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190)
at
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31)
at
co

RE: Wrong running state

[Pallavi.Satish]

You may restart your continuum and the try to delete that.

Some time as noticed by me if your build is taking time, try running
default maven2 buildDefinition(you will have this under Project Information 
tab) first and then your usual build definition it may help.

Regards
Pallavi

-Original Message-
From: Ingo Siebert [mailto:[EMAIL PROTECTED]
Sent: Friday, December 14, 2007 2:01 PM
To: [EMAIL PROTECTED]
Subject: Wrong running state

Hi,

i have an ANT build which needs 7 minutes.

It's working in general, but i have two build which are listed as
"running" since 18 hours.

They are not running, i also restartet my tomcat with the continuum
application.
But if i try to delete them, continuum says they can't be deleted
because they are running.

Do i have to delete the entries in my database witl a sql-delete command?
Is this problem known that the "running" state detection isn't 100% working?

Cheers,

Ingo

RE: maven2 release plugin - no dependencies update

[nicklist]

If I recall correctly, the updateDependencies option was added recently. As you 
see in the plugin page, it is for a snapshot version. Perhaps you are using a 
stable version, which does not have this option included yet.

As far as I know, the updateDependencies option is just what you need.

With regards,

Nick Stolwijk


-Original Message-
From: Tomasz Zieleniewski [mailto:[EMAIL PROTECTED]
Sent: Fri 12/14/2007 9:55 AM
To: users@maven.apache.org
Subject: maven2 release plugin - no dependencies update
 
Hi,

I have following problem.
I have a main maven project of the pom type which consists of 4 subprojects
of the type jar.
Two of my subprojects have dependency on the two previous ones.
When I invoke mvn release:prepare -D dryRun=true
everything works fine except that the dependencies from two last subrojects
are not updated to the new dev version

So for instance when I have following release state
pom - 1.0.0-SNAPSHOT
sub1 - 1.0-SNAPSHOT
sub2 - 1.0-SNAPSHOT
sub3 - 1.0-SNAPSHOT
sub4 - 1.0-SNAPSHOT

and inside sub3 pom.xml such dependency

  
group
sub1
1.0-SNAPSHOT
provided
  


and even if the version for sub1 is increased by release the dependency
version is not changed.
I tried to use -D*updateDependencies

=true
but it didn't help*

Is it an error or did I miss something?

bests regards
tomasz zieleniewski

Re: maven2 release plugin - no dependencies update

[maarten roosendaal]

try using the releaseManagement tags in you root pom.xml, that way you will not 
have to define a version (and/or groupId) in the pom.xml's of the children. 
Works perfectly for me.

Regards,
Maarten

- Original Message 
From: Tomasz Zieleniewski <[EMAIL PROTECTED]>
To: users@maven.apache.org
Sent: Friday, December 14, 2007 9:55:28 AM
Subject: maven2 release plugin - no dependencies update


Hi,

I have following problem.
I have a main maven project of the pom type which consists of 4
 subprojects
of the type jar.
Two of my subprojects have dependency on the two previous ones.
When I invoke mvn release:prepare -D dryRun=true
everything works fine except that the dependencies from two last
 subrojects
are not updated to the new dev version

So for instance when I have following release state
pom - 1.0.0-SNAPSHOT
sub1 - 1.0-SNAPSHOT
sub2 - 1.0-SNAPSHOT
sub3 - 1.0-SNAPSHOT
sub4 - 1.0-SNAPSHOT

and inside sub3 pom.xml such dependency

  
group
sub1
1.0-SNAPSHOT
provided
  


and even if the version for sub1 is increased by release the dependency
version is not changed.
I tried to use -D*updateDependencies

=true
but it didn't help*

Is it an error or did I miss something?

bests regards
tomasz zieleniewski






  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 

RE: [assembly] add all dependency jars to lib folder in a "bin" assembly

[Richard Chamberlain]

My assembly build does not include the main artefact in lib. Here's more
of how I package up:


  kit
  
zip
  
  
...
Other resources to copy
...

  target
  
  
*.jar
  

  


  /lib
  false
  runtime





-Original Message-
From: deckrider [mailto:[EMAIL PROTECTED] 
Sent: 13 December 2007 18:03
To: Maven Users List
Subject: Re: [assembly] add all dependency jars to lib folder in a "bin"
assembly

On Dec 13, 2007 10:11 AM, Daniele Dellafiore <[EMAIL PROTECTED]> wrote:
> it works!
> The only problem is that include the main artifact in lib folder. I
> just want the dependencies jars.
> Now I have:
>
>   
>
>/lib
>false
>runtime
>
>  arte*
>
>
>   
>
> where arte-0.1.jar and "arte" is the name of the artifact I am
> assembling is the name of the project artifact. Even with this,
> arte-0.1.jar is in lib folder... any ideas?

I think this has to be not a file name, but a groupId:artifactId
format.  For example if arte-1.2.3.jar must be excluded I assume its
artifactId=arte.  And lets pretend its groupId=com.foo.bar to have
this:

com.foo.bar:arte

> On Dec 13, 2007 1:19 PM, Daniele Dellafiore <[EMAIL PROTECTED]> wrote:
> > Hi all.
> >
> > I am trying to accomplish this task. My target is to create a
> > compressed archive with the jar of my app and all the jars it
depends
> > upon in a subfolder called lib. I am trying to customize the
standard
> > bin descriptor so I have
> >
> >   
> > 
> >
src/assembly/bin.xml
> > 
> >  [.]
> >
> >
> > and the bin.xml file is almost the same than the original. I just
added a
> >
> > lib/**
> >
> > to include some native libraries I keep in lib folder. But the point
> > is that of course the jars are handled by maven so I expect there is
> > some automatic way to put all them in a custom output folder. I am
> > trying to understand how to do but I am failing.
> > I think the solutions is somewhere here:
> >
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#clas
s_binaries
> > but I Cannot figure out how...
> >
> > Here is the bin.xml, thanks for any help.
> >
> > 
> >   bin
> >   
> > tar.gz
> >   
> >   
> > 
> >   
> > true
> > lib
> >   
> > 
> >   
> >   
> > 
> >   
> > README*
> > LICENSE*
> > NOTICE*
> > lib/**
> >   
> > 
> > 
> >   target
> >   
> >   
> > *.jar
> >   
> > 
> >   
> > 
> >
> > --
> > Daniele Dellafiore
> > http://ildella.wordpress.com/
> >
>
>
>
> --
> Daniele Dellafiore
> http://ildella.wordpress.com/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-- 
ASCII ribbon campaign:
()  against HTML email
/\  against Microsoft attachments
Information:  http://www.expita.com/nomime.html

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

how to set subversion authentication information into settings.xml (instead of writing it into project pom)

[Fred Zhang]

Hi there,
I'm working on configuring maven-scm plugin to use maven to do daily 
update/commit jobs.

A problem is that I don't want to write my authentication information 
(username/password) into the project pom file (otherwise it will be shared 
through subversion). Neither want I use subversion "cached password" mechanism. 
I found some web-pages said that the svn repository server information (with 
username/password) could be written in settings.xml as following:

   
  http://svnrepo.my.com/svn/project/trunk
  username
  password
   

And in project pom, just write
   
   
scm:svn:http://svnrepo.my.com/svn/project/trunk
   http://svnrepo.my.com/svn/project/trunk
   

Then the mvn scm:update should work.

I tried. But I still got authentication failure.

Is there any way to make it?

Thanks in advance.

Fred

Building war with multi-module classes and no module jars

[bayamos]

I have a multi-module war project that currently creates a jar per module,
then the jars of the jar modules are copied to WEB-INF/lib using the normal
semantics for the war plugin.

I am using the maven-jibx-plugin and would like to copy the classes
generated from the non-war modules into the war's target/classes directory
so I can bytecode-enhance the classes before building the war.  I would also
like to skip the step that builds the jars and copies them to the war's lib
directory.

Is this done with an assembly?  I have read the documentation for the
assembly plugin, but there is no mention on how to do this.
 
-- 
View this message in context: 
http://www.nabble.com/Building-war-with-multi-module-classes-and-no-module-jars-tp14332309s177p14332309.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]

maven2 release plugin - no dependencies update

[Tomasz Zieleniewski]

Hi,

I have following problem.
I have a main maven project of the pom type which consists of 4 subprojects
of the type jar.
Two of my subprojects have dependency on the two previous ones.
When I invoke mvn release:prepare -D dryRun=true
everything works fine except that the dependencies from two last subrojects
are not updated to the new dev version

So for instance when I have following release state
pom - 1.0.0-SNAPSHOT
sub1 - 1.0-SNAPSHOT
sub2 - 1.0-SNAPSHOT
sub3 - 1.0-SNAPSHOT
sub4 - 1.0-SNAPSHOT

and inside sub3 pom.xml such dependency

  
group
sub1
1.0-SNAPSHOT
provided
  


and even if the version for sub1 is increased by release the dependency
version is not changed.
I tried to use -D*updateDependencies

=true
but it didn't help*

Is it an error or did I miss something?

bests regards
tomasz zieleniewski

Re: [m2] issue activating profiles.

[sherai]

I have run into a similar problem. I fixed it by setting each profile to
false, like

*
dev-

false


dev-
no-documentation



dev-7778

false



dev-7778
no-documentation



HTH



Mick Knutson-4 wrote:
> 
> I am trying to switch profiles for each environment.
> I have dev-, and dev-7778
> 
> :*When I run:*
> *mvn -P dev- assembly:assembly -e -X > .out.txt*
> *
> I keep getting this:*
> 
> *[WARNING] Overriding profile: 'dev-' (source: pom) with new instance
> from source: profiles.xml
> [WARNING] Overriding profile: 'dev-7778' (source: pom) with new instance
> from source: profiles.xml*
> 
> 
> so it looks like I get both, but 7778 seems to always override . I
> only
> want one of these profiles active at the same time. Can someone please
> help
> me out?
> 
> 
> -- 
> Thanks,
> Mick Knutson
> 
> http://www.baselogic.com
> http://www.blincmagazine.com
> http://www.djmick.com
> http://www.myspace.com/mickknutson
> http://www.myspace.com/BLiNCMagazine
> http://tahoe.baselogic.com
> ---
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-m2--issue-activating-profiles.-tp14280508s177p14331915.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]