Re: Maven Central Repository - Cleanup Efforts
I hope I get this right Jason here states that there should only be one central And yes we can ONLY have ONE central. And this is the ONE we got today That must be the game we are playing. The community must be able to TRUST maven / central. Starting changing this could cause doubt, and a very easy attach zone for competitors... When this is stated We must acknowledge we got problems !!! The central is full of legacy, some artifacts that even might not work, moved etc. Here the solution can be to add deprecation lists or better component- qualtiy-attributes (an xml file next to a component) To speak clear: pom.xml xx.jar xxx.war ... is read-only. But a component-quality-attribute.xml file can be maintained, and updated. The quality attributes can be like: deprecated false / true .. when true + a description runs-JVM-1.5 true/ (false + description / problem reference ) runs-JVM-1.6true/ (false + description / problem reference ) runs-JVM-1.7 true/ (false + description / problem reference ) runs-JVM-1.8 when this becomes relevant is-moved (no) or path to new location osgi-compliant true / false ivy-enabled true /false groovy-enabled maven-2 enabled true / false ... most of our maven-2 artifacts should hopefully have true here :-) maven-3 enabled (soon..) maven-4 enabled (when this becomes relevant) various PMD level compliant I here by tries to state that we cannot predict the future. What today seens perfect, might tomorrow be less usable. With such attributes users can select the artifacts matching their demands. I am not sure a point system from 1..10 will match the requirements. Best regards Anders Kristian Andersen On 26/09/2009, at 21.15, Jason van Zyl wrote: On 2009-09-26, at 10:58 AM, Albert Kurucz wrote: Very nice idea to measure the quality. But sorry Tamas, 50% corrupt or 90% corrupt does not make a difference for me. Especially not, when I have feeling that it is possible to maintain a 100% clean repo with the right automation tools. If Sonatype's goal is to sell these tools only for paying customers I don't have a bad feeling about that. Everyone has to make a living. But I hope sometime similar tools and a clean repo will be available for the open public. I hope OSS developers will recognize the need for quality (and a high quality repo). Not having a super high quality central repository actually makes our commercial efforts a lot harder. If I was devious I would have agreed with Brett and would make a completely clean central repository as our plans require intact repositories. But we don't have a clean repository and trying to make a separate one would be a disaster for general use. You have to live with what's there and Sonatype will actually invest in cleaning up the generally available repository. We already have with efforts like this: http://nexus.sonatype.org/oss-repository-hosting.html It would actually cost us more in support with our clients to maintain a dirty Maven Central and a clean Maven Central with the confusion, interoperability problems and general issues of potential distrust it just makes no business sense. Now the information we want to add is of enormous value but it's predicated on generally improving the quality of Maven Central. I don't want Sonatype to be known as the company that stole Maven Central, doesn't do us any good. So trying to sequester improved metadata somewhere is pointless. If the base information is not good, then the whole system is crippled and that screws Sonatype as well as everyone else. So the information in Maven Central on a per-project basis I see increasing greatly with some tools that Sonatype is developing in Nexus and M2Eclipse and this will benefit all Maven users generally. I'm certainly going to leverage that improved information, but so can anyone else. On Sat, Sep 26, 2009 at 11:22 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: Le samedi 26 septembre 2009, Tamás Cservenák a écrit : I think we all need some clarification, since we all talk about quality (we all agreed upon the basic things unanimously). What is the quality of a maven repository (in general)? Can we measure it? Can we define it? A wiki page with piled up (even personal) opinions would be good -- don't hesitate to start one on MAVENUSER Wiki [1] whatever they are -- and later we should cherry-pick the most relevant ones to build some tooling to build these metric. And then, we could measure the quality of different reposes (like central) and have a list of reposes that do meet certain level of quality and list publicly the others that does not. [1] http://docs.codehaus.org/display/MAVENUSER/Home - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
Re: Forced to do maven clean before each maven
Hi Amtixx Yes ofcause you can get it fixed. The situation is that maven 1 is an older generation of maven, and there is not likely comming a new release here. So your fix can be to migrate to maven 2, here the clean procedure is better. Okay it is friday, so an other solution is to send The apache foundation a large check. Keep happy /Anders On 19/03/2009, at 19.40, amtixx wrote: I am having a issue where i am forced to do a maven clean before i do a maven. I am using Maven 1.1. If i don't do a Maven clean, then I can't see my new changes. i.e it seems like the application uses the old class files. Can someone help me to fix this issue? -- View this message in context: http://www.nabble.com/Forced-to-do-maven-clean-before-each-maven-tp22606807p22606807.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven vs. Hudson
Yes good question You use maven to define your projects for building your jar, war and ear You use hudson to run these projects in an automated way. /Anders On 18/03/2009, at 11.50, Łukasz Warchoł wrote: Hello, Can anybody tell me what are de differences between Maven and Hudson? Thanks in advance, Luke - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to add test classes into jar?
Hi I'm not 100 pct sure I get this right. You have some test classes that extends something else than TestCase and you want to share these intermediate classes between projects ? If this is the case. I re comment to re-engineer your test cases so they only extends TestCase /Anders On 12/12/2008, at 08.43, Linghua Wang wrote: Hi, I want to try maven-surefire-plugin. There are two projects A and B, A depends on B, and some test classes in A depend on that of in B. Both A and B's POM has the following snippet. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration skipfalse/skip /configuration /plugin - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Steps: 1. CD to directory of project B, execute mvn compiler:testCompile and mvn install 2. CD to directory of project A, execute mvn compiler:testComplie, maven always complain that some test classes can not be found in project B. Question: Simply, we can resolve it by adding test classes into jar (default packaging). Somebody could tell me how? Or any other suggestions would be appriciated. Thanks. Linghua. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Keep version when doing a release
Hi You need a trunk to each module you want to release individually /Anders On 09/12/2008, at 11.02, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I have a multi module project that I want to make a release for. Some of the modules changes frequently and they are marked as SNAPSHOTS. Some modules are very stable and have a fixed version. I run maven 2 release plug-in 2.0-beta-7 with the --batch-mode parameter. The problem is that the stable modules will also have there version upgraded. Is there any way to tell the plug-in to only change version for SNAPSHOT modules? /Gunnar - 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: release ${properties} in pom.xml to make different sites
Hi again
I am using the expresson language support like ${pom.artifactId} that
is official called ${project.artifactId} as I have understood.
And this does not solve the issue I am adressing here..
The issue is that the TRUNK or VV-SNAPSHOT version is located at url
... common/my-project/trunk
The tagged version in example 3.0 will be located at
... common/my-project/tags/my-project-3.0
The value trunk when snapshot and the value tags/my-project-30 when
And I am searching for a way to express this without having to change
the pom.xml too much.
Therefore I am looking for expression variables that leverage out /
manage the CMS urls for the same artifact in different release stage.
Therefore I am looking for variables like:
${project.basePath} and ${project. versionPath}
with the functionality described in earlier mail below.
Maybe the problem is at a pom level. Maven seems not to deal with
trunk/tags/branches in its model ?
It is usage that deals with that. I mean how people setup and uses it..
In documentation for subversion it is a recommented usage to make the
directory tree like
my-project/trunk
my-project/tags
my-project/branches
But this is not reflected in maven (as I see it) Okay the maven
release plugin knows these rules, but it is programmed into the plugin.
/Anders
On 08/12/2008, at 08.13, Baptiste MATHUS wrote:
Hi Anders,
There's already variables that I guess you could use for your use
case.
Did you try putting something like this? :
url
http://my-site.xxx/sites/common/${pom.groupId}/${pom.artifactId}/$
{pom.version}http://my-site.xxx/sites/common/my-project/tags/my-project-3.0
/url
I'm not sure I got all your point from your message. If so, please
let us
know.
Cheers.
2008/12/8 Anders Kristian Andersen
[EMAIL PROTECTED]
Hi
I am working with at wish to make a site per release of my artifact
assume the following
The trunk: for my-project
urlhttp://my-site.xxx/sites/common/my-project/url
This means that the URL http://my-site.xxx/sites/common/my-project/contains
the site.
When I release the 3.0 version of my-project I want a released site
urlhttp://my-site.xxx/sites/common/my-project/tags/my-
project-3.0/url
The problem is that I manually have to change the URL in the released
artifacts to solve this.
I would like a property that makes this URL a constant in my pom.xml
An idea could be two properties property
1) project.basePath=**/common/my-project
** This property must probably be set in the pom, or guessed by
maven
when not set
2) project.versionPath=. when pom.xml is in a trunk directory
or
project.versionPath=tags/my-project-3.0 when the directory after
basePath is tags, branches and directory after..
** This property should be calculated by maven based on the
standard
usages of directories trunk, tags, branches
Finally I want to be able to set the url to a value like
urlhttp://my-site.xxx/sites/${project.basePath}/${projecthttp://my-site.xxx/sites/$%7Bproject.basePath%7D/$%7Bproject
.
versionPath}/url
My Questions are:
a) Is this possible already today? Am I just missing some Maven
knowledge?
b) Can I add property handlers to a project? I belive that a plugin
would
not be enough here ?
/Anders
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
expression language for project.groupId dots as slash
Hi
When I refere URL's it could be usable to refere the ${project.groupId}
like urlhttp://my-server/${project.groupId}/${project.artifactId}/
url
This is just not possible because project.groupId == com.my-
company.package1..n.my-group
I mean this is dots not slashes that separates the urls.
I would like operators on the expression language strings like $
{project.groupId.dot2slash}
Is it possible to make a plugin that handles that, or a listener or ??
/Anders
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to build classes, WAR, EAR in one POM?
Hi Alex One pom produces one artifact You can see it as a structure parent ear-artifact war-artifact It is not worth trying other things.. Maven assembly plugins can make attachments, but this is not good in your situation /Anders On 08/12/2008, at 09.10, Shananin, Alexei wrote: Dear All! I am new to Maven 2.0.9 and I am facing the following problem. We started migration from JDeveloper 10g towards Maven. Current JDeveloper project structure looks like that: 1) WebProject/src -- java sources, resources 2) WebProject/public_html -- web sources (jsp, html, libs, compiled classes) The build sequence from JDev perspective contains these phases: 1) compile classes and JSPs to WebProject/public_html/classes 2) build war file with contents from previous step 3) build ear containing war from previous step and add META-INF/orion-application.xml This build can be done using 3 different POMs with 3 packaging types: JAR, WAR, EAR. I want to incorporate 3 phases above in one pom.xml as we can not change the directory structure. The result must be EAR. Is that possible to do all-in-one? Please give me a clue of how to do it. Thanks for your help! Alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to build classes, WAR, EAR in one POM?
I see it is still possible to make the three artifacts I describe You just have to change the source/build location a lot You can specify sources outside a project by ../../../here/there/ probably ugly, and probably hard to understand /Anders On 08/12/2008, at 11.13, Shananin, Alexei wrote: Hi Anders! -Original Message- From: Anders Kristian Andersen [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2008 12:44 To: Maven Users List Subject: Re: How to build classes, WAR, EAR in one POM? Hi Alex One pom produces one artifact You can see it as a structure parent ear-artifact war-artifact This is obvious structure and if I had not legacy JDeveloper project I would use it for sure. Unfortunately, we can not get rid of JDeveloper as it has TopLink Workbench able to edit mappings that can not be opened by standalone workbenches (damn Oracle! :( ). So we bound to project structure below. Additionally, we consider EAR file as the only artifact. No JAR or WAR files makes sense without EAR. This is the second point in my struggling to use single POM. It is not worth trying other things.. Maven assembly plugins can make attachments, but this is not good in your situation /Anders On 08/12/2008, at 09.10, Shananin, Alexei wrote: Dear All! I am new to Maven 2.0.9 and I am facing the following problem. We started migration from JDeveloper 10g towards Maven. Current JDeveloper project structure looks like that: 1) WebProject/src -- java sources, resources 2) WebProject/public_html -- web sources (jsp, html, libs, compiled classes) The build sequence from JDev perspective contains these phases: 1) compile classes and JSPs to WebProject/public_html/classes 2) build war file with contents from previous step 3) build ear containing war from previous step and add META-INF/orion-application.xml This build can be done using 3 different POMs with 3 packaging types: JAR, WAR, EAR. I want to incorporate 3 phases above in one pom.xml as we can not change the directory structure. The result must be EAR. Is that possible to do all-in-one? Please give me a clue of how to do it. Thanks for your help! Alex. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
release ${properties} in pom.xml to make different sites
Hi
I am working with at wish to make a site per release of my artifact
assume the following
The trunk: for my-project
urlhttp://my-site.xxx/sites/common/my-project/url
This means that the URL http://my-site.xxx/sites/common/my-project/
contains the site.
When I release the 3.0 version of my-project I want a released site
urlhttp://my-site.xxx/sites/common/my-project/tags/my-project-3.0/
url
The problem is that I manually have to change the URL in the released
artifacts to solve this.
I would like a property that makes this URL a constant in my pom.xml
An idea could be two properties property
1) project.basePath=**/common/my-project
** This property must probably be set in the pom, or guessed by
maven when not set
2) project.versionPath=. when pom.xml is in a trunk directory
or
project.versionPath=tags/my-project-3.0 when the directory
after basePath is tags, branches and directory after..
** This property should be calculated by maven based on the
standard usages of directories trunk, tags, branches
Finally I want to be able to set the url to a value like
urlhttp://my-site.xxx/sites/${project.basePath}/${project.
versionPath}/url
My Questions are:
a) Is this possible already today? Am I just missing some Maven
knowledge?
b) Can I add property handlers to a project? I belive that a plugin
would not be enough here ?
/Anders
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Will toolchain work for maven-antrun-plugin ?
Hi I have just seen the toolchain feature in Maven 2.0.9 ++ Will it be possible to run maven-antrun-plugin in various JVM's My situation is that we use Weblogic 9.2 (and therefore JVM 1.5) for our builds But we have a few weblogic 8.x things that runs JVM 1.4 Therefore it could actually be meaning full to run the entire build for an artifact in JVM 1.4 and especially the maven-antrun-plugin. /Anders Kr. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-antrun-plugin maven.compile.classpath does not respect systemPath
Hi
Regarding
http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html
I have found that maven.compile.classpath does not respect systemPath
Is this correct behaviour?
I belive that
dependency
groupIdcom.bea.weblogic.server.lib/groupId
artifactIdweblogic/artifactId
version9.2/version
scopesystem/scope
systemPath${WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
should be seen as.
/opt/bea/weblogic92//server/lib/weblogic.jar
(assuming that WL_HOME == /opt/bea/weblogic92) but it is not
it is seen as
/Users/aka/.m2/repository/com/be... 92./weblogic-9.2.jar
I think it is wrong, I just want a second opinion before i pass a JIRA
/Anders
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: guide-ant-plugin-development.html requires maven-plugin-plugin 2.3 but it is not newest
I have solved the problem my self, by looking into the great book maven-definitive-guide It is possible to give other version numbers maven-plugin-plugin version 2.4.3 maven-plugin-tools-ant version 2.4.3 maven-script-ant version 2.0.9 Hereby there is no need to use old versions, so the problems behind my mail does not exist / is solved. /Anders So a working pom can be: build plugins plugin !-- NOTE: We don't need groupId if the plugin's groupId is org.apache.maven.plugins OR org.codehaus.mojo. -- artifactIdmaven-plugin-plugin/artifactId version2.4.3/version !-- Add the Ant plugin tools -- dependencies dependency groupIdorg.apache.maven.plugin-tools/ groupId artifactIdmaven-plugin-tools-ant/artifactId version2.4.3/version /dependency /dependencies /plugin /plugins /build dependencies dependency groupIdorg.apache.maven/groupId artifactIdmaven-script-ant/artifactId version2.0.9/version /dependency /dependencies On 11/11/2008, at 09.29, Anders Kristian Andersen wrote: Hi Friends I have seen the guide http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html and it requires plugins to use the maven-plugin-plugin version 2.3 In the list of plugins http://maven.apache.org/plugins/index.html maven-plugin-plugin is version 2.4.3 When I run mvn install I get several problems It scares me a little bit. /Anders Error trace below::: Goal prefix is specified as: 'generate'. Maven currently expects it to be 'channel-aggregate'. [FATAL ERROR] org.apache.maven.plugin.plugin.DescriptorGeneratorMojo#execute() caused a linkage error (java.lang.NoSuchMethodError) and may be out- of-date. Check the realms: [FATAL ERROR] Plugin realm = app0.child- container[org.apache.maven.plugins:maven-plugin-plugin] urls[0] = file:/Users/aka/.m2/repository/org/apache/maven/plugins/ maven-plugin-plugin/2.4.3/maven-plugin-plugin-2.4.3.jar urls[1] = file:/Users/aka/.m2/repository/org/apache/maven/maven- plugin-tools-ant/2.0.1/maven-plugin-tools-ant-2.0.1.jar urls[2] = file:/Users/aka/.m2/repository/org/apache/maven/maven- plugin-tools-api/2.0.1/maven-plugin-tools-api-2.0.1.jar urls[3] = file:/Users/aka/.m2/repository/org/codehaus/plexus/plexus- utils/1.5.6/plexus-utils-1.5.6.jar urls[4] = file:/Users/aka/.m2/repository/org/apache/maven/maven- plugin-tools-model/2.0.1/maven-plugin-tools-model-2.0.1.jar urls[5] = file:/Users/aka/.m2/repository/com/bea/weblogic/server/lib/ weblogic/9.2/weblogic-9.2.jar urls[6] = file:/Users/aka/.m2/repository/com/bea/weblogic/common/lib/ apache_xbean/9.2/apache_xbean-9.2.jar urls[7] = file:/Users/aka/.m2/repository/com/bea/weblogic/server/lib/ knex81/9.2/knex81-9.2.jar urls[8] = file:/Users/aka/.m2/repository/com/bea/weblogic/server/lib/ jpd/9.2/jpd-9.2.jar urls[9] = file:/Users/aka/.m2/repository/com/bea/weblogic/ integration/lib/jpdpublic/9.2/jpdpublic-9.2.jar urls[10] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/ doxia-site-renderer/1.0-alpha-10/doxia-site-renderer-1.0-alpha-10.jar urls[11] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/ doxia-core/1.0-alpha-10/doxia-core-1.0-alpha-10.jar urls[12] = file:/Users/aka/.m2/repository/org/codehaus/plexus/plexus- i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar urls[13] = file:/Users/aka/.m2/repository/org/codehaus/plexus/plexus- velocity/1.1.7/plexus-velocity-1.1.7.jar urls[14] = file:/Users/aka/.m2/repository/org/apache/velocity/ velocity/1.5/velocity-1.5.jar urls[15] = file:/Users/aka/.m2/repository/commons-collections/ commons-collections/3.2/commons-collections-3.2.jar urls[16] = file:/Users/aka/.m2/repository/commons-lang/commons-lang/ 2.1/commons-lang-2.1.jar urls[17] = file:/Users/aka/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar urls[18] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/ doxia-decoration-model/1.0-alpha-10/doxia-decoration-model-1.0- alpha-10.jar urls[19] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/ doxia-module-apt/1.0-alpha-10/doxia-module-apt-1.0-alpha-10.jar urls[20] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/ doxia-module-fml/1.0-alpha-10/doxia-module-fml-1.0-alpha-10.jar urls[21] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/ doxia-module-xdoc/1.0-alpha-10/doxia-module-xdoc-1.0-alpha-10.jar urls[22] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/ doxia-module-xhtml/1.0-alpha-10/doxia-module-xhtml-1.0-alpha-10.jar urls[23] = file:/Users/aka/.m2/repository/org/apache/maven/plugin- tools/maven-plugin-tools-api/2.4.3/maven-plugin-tools-api-2.4.3.jar urls[24] = file:/Users/aka/.m2/repository/jtidy/jtidy/4aug2000r7-dev/ jtidy-4aug2000r7-dev.jar urls[25] = file:/Users/aka/.m2
guide-ant-plugin-development.html requires maven-plugin-plugin 2.3 but it is not newest
Hi Friends I have seen the guide http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html and it requires plugins to use the maven-plugin-plugin version 2.3 In the list of plugins http://maven.apache.org/plugins/index.html maven-plugin-plugin is version 2.4.3 When I run mvn install I get several problems It scares me a little bit. /Anders Error trace below::: Goal prefix is specified as: 'generate'. Maven currently expects it to be 'channel-aggregate'. [FATAL ERROR] org.apache.maven.plugin.plugin.DescriptorGeneratorMojo#execute() caused a linkage error (java.lang.NoSuchMethodError) and may be out-of- date. Check the realms: [FATAL ERROR] Plugin realm = app0.child- container[org.apache.maven.plugins:maven-plugin-plugin] urls[0] = file:/Users/aka/.m2/repository/org/apache/maven/plugins/ maven-plugin-plugin/2.4.3/maven-plugin-plugin-2.4.3.jar urls[1] = file:/Users/aka/.m2/repository/org/apache/maven/maven-plugin- tools-ant/2.0.1/maven-plugin-tools-ant-2.0.1.jar urls[2] = file:/Users/aka/.m2/repository/org/apache/maven/maven-plugin- tools-api/2.0.1/maven-plugin-tools-api-2.0.1.jar urls[3] = file:/Users/aka/.m2/repository/org/codehaus/plexus/plexus- utils/1.5.6/plexus-utils-1.5.6.jar urls[4] = file:/Users/aka/.m2/repository/org/apache/maven/maven-plugin- tools-model/2.0.1/maven-plugin-tools-model-2.0.1.jar urls[5] = file:/Users/aka/.m2/repository/com/bea/weblogic/server/lib/ weblogic/9.2/weblogic-9.2.jar urls[6] = file:/Users/aka/.m2/repository/com/bea/weblogic/common/lib/ apache_xbean/9.2/apache_xbean-9.2.jar urls[7] = file:/Users/aka/.m2/repository/com/bea/weblogic/server/lib/ knex81/9.2/knex81-9.2.jar urls[8] = file:/Users/aka/.m2/repository/com/bea/weblogic/server/lib/ jpd/9.2/jpd-9.2.jar urls[9] = file:/Users/aka/.m2/repository/com/bea/weblogic/integration/ lib/jpdpublic/9.2/jpdpublic-9.2.jar urls[10] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/doxia- site-renderer/1.0-alpha-10/doxia-site-renderer-1.0-alpha-10.jar urls[11] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/doxia- core/1.0-alpha-10/doxia-core-1.0-alpha-10.jar urls[12] = file:/Users/aka/.m2/repository/org/codehaus/plexus/plexus- i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar urls[13] = file:/Users/aka/.m2/repository/org/codehaus/plexus/plexus- velocity/1.1.7/plexus-velocity-1.1.7.jar urls[14] = file:/Users/aka/.m2/repository/org/apache/velocity/velocity/ 1.5/velocity-1.5.jar urls[15] = file:/Users/aka/.m2/repository/commons-collections/commons- collections/3.2/commons-collections-3.2.jar urls[16] = file:/Users/aka/.m2/repository/commons-lang/commons-lang/ 2.1/commons-lang-2.1.jar urls[17] = file:/Users/aka/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar urls[18] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/doxia- decoration-model/1.0-alpha-10/doxia-decoration-model-1.0-alpha-10.jar urls[19] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/doxia- module-apt/1.0-alpha-10/doxia-module-apt-1.0-alpha-10.jar urls[20] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/doxia- module-fml/1.0-alpha-10/doxia-module-fml-1.0-alpha-10.jar urls[21] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/doxia- module-xdoc/1.0-alpha-10/doxia-module-xdoc-1.0-alpha-10.jar urls[22] = file:/Users/aka/.m2/repository/org/apache/maven/doxia/doxia- module-xhtml/1.0-alpha-10/doxia-module-xhtml-1.0-alpha-10.jar urls[23] = file:/Users/aka/.m2/repository/org/apache/maven/plugin- tools/maven-plugin-tools-api/2.4.3/maven-plugin-tools-api-2.4.3.jar urls[24] = file:/Users/aka/.m2/repository/jtidy/jtidy/4aug2000r7-dev/ jtidy-4aug2000r7-dev.jar urls[25] = file:/Users/aka/.m2/repository/org/apache/maven/reporting/ maven-reporting-impl/2.0.4.1/maven-reporting-impl-2.0.4.1.jar urls[26] = file:/Users/aka/.m2/repository/commons-validator/commons- validator/1.2.0/commons-validator-1.2.0.jar urls[27] = file:/Users/aka/.m2/repository/commons-beanutils/commons- beanutils/1.7.0/commons-beanutils-1.7.0.jar urls[28] = file:/Users/aka/.m2/repository/commons-logging/commons- logging/1.0.4/commons-logging-1.0.4.jar urls[29] = file:/Users/aka/.m2/repository/commons-digester/commons- digester/1.6/commons-digester-1.6.jar urls[30] = file:/Users/aka/.m2/repository/xml-apis/xml-apis/1.0.b2/xml- apis-1.0.b2.jar urls[31] = file:/Users/aka/.m2/repository/org/apache/maven/plugin- tools/maven-plugin-tools-java/2.4.3/maven-plugin-tools-java-2.4.3.jar urls[32] = file:/Users/aka/.m2/repository/com/thoughtworks/qdox/qdox/ 1.6.3/qdox-1.6.3.jar urls[33] = file:/Users/aka/.m2/repository/ant/ant/1.5.1/ant-1.5.1.jar urls[34] = file:/Users/aka/.m2/repository/jmock/jmock/1.0.0/ jmock-1.0.0.jar urls[35] = file:/Users/aka/.m2/repository/org/apache/maven/plugin- tools/maven-plugin-tools-beanshell/2.4.3/maven-plugin-tools- beanshell-2.4.3.jar urls[36] = file:/Users/aka/.m2/repository/bsh/bsh/1.3.0/bsh-1.3.0.jar [FATAL ERROR] Container realm = plexus.core urls[0] =
Re: Error updating 2.0.4 plugins
Hi I see that www.codehouse.org/ says We are currently experiencing disk problems with beaver.codehaus.org. The problem is being looked at by our service provider. I see that http://snapshots.maven.codehaus.org/ is unable to connect. You comment... A temporary solution is to define a mirror of snapshots.maven.codehaus.org to repo1.maven.org until codehaus.org is back Your comment is great, but I do not understand it. I don't know if it is 101 now, but it is not precise enough for me After more than 10 experiments I ended up with the following settings mirrors mirror idrepo1.maven.org/id nameMirror to solve problem 17. may 2006/name urlhttp://repo1.maven.org/maven2/url mirrorOfsnapshots/mirrorOf /mirror /mirrors /settings So thanks a lot anyway, it solved the problem Now I get the error Downloading: http://dist.codehaus.org/org.mortbay.jetty/jars/servlet-api-2.5-6.0.0beta12.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Error transferring file org.mortbay.jetty:servlet-api-2.5:jar:6.0.0beta12 from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus (http://dist.codehaus.org), apache.snapshots (http://svn.apache.org/maven-snapshot-repository), snapshots (http://snapshots.maven.codehaus.org/maven2) Path to dependency: 1) org.apache.maven.plugins:maven-site-plugin:maven-plugin:2.0-beta-5 2) org.mortbay.jetty:jetty:jar:6.0.0beta12 3) org.mortbay.jetty:servlet-api-2.5:jar:6.0.0beta12 /Anders Emmanuel Venisse wrote: codehaus.org is temporarily down so request on it generate an error. A temporary solution is to define a mirror of snapshots.maven.codehaus.org to repo1.maven.org until codehaus.org is back Emmanuel Wim Deblauwe a écrit : I did a mvn -U and I get the following error: Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/servlet-api-2.5/6.0.0beta12/servlet-api-2.5-6.0.0beta12.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-8/doxia-site-renderer-1.0-alpha-8.pom 1K downloaded Downloading: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-8/doxia-1.0-alpha-8.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: null:doxia-site-renderer:jar:1.0-alpha-8 Reason: Cannot find parent: org.apache.maven.doxia:doxia for project: null:doxia-site-renderer:jar:1.0-alpha-8 what should I do about this? regards, Wim - 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: Running junit test with maven
Hi java.lang.NoClassDefFoundError It might be because the MANIFEST.MF in your jar file is wrong. When you make a pom.xml with a large description clause in the pom the MANIFEST.MF becomes huge. Bigger than allowed for execution. Try to verify the size of the MANIFEST in your jars. /Anders Kr. Andersen Tom Huybrechts wrote: You could also produce a test-jar from the tests from A and include them as test-scope dependency to B. See http://maven.apache.org/guides/mini/guide-attached-tests.html Tom On 4/19/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: You need a third module that will contain your share test classes (under src/main/java) and you'll add it as a dependency of module a and b with test scope. Emmanuel Patrick GIRY a écrit : I have defined two module A and B with a common parent module because B depend on A. I have imported the module as Eclipse project. The problem i have a TestCase class into the B module which extends a TestCase into the A module. When I run the test suite with the Eclipse console all is ok, but when I run the mvn test command into the B module, I have java.lang.NoClassDefFoundError with TestCase into A. How can I indicate to surefire plugin to include depend test classpath into it's classpath, to avoid to duplicate the TestCase into the A module? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] . - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Optional modules in modules list
Hi Maven Users I have build a multi-level application in maven1 where I uses maven to load the subprojects from the version-control-system. Each module is in its own repository.. In maven-2 I have considered would make a project containing modelVersion4.0.0/modelVersion groupIdmanager/groupId artifactIdmanager/artifactId packagingpom/packaging nameManagemement project for this mix of my components/name version1.0/version modules modulecomponent_project_A/module modulecomponent_project_B/module modulecomponent_project_C/module /modules In maven 1 I could use maven to read the component_project_X's from the version control system using maven. But in m2 I will get an error as long as the modules does not exist yet I have tried the mvn -fn (--fail-never) option, but maven still fails as long as the module does not exist yet. My dream could be to be able to specify optional=true Or to be able to specify modulecomponent_*/module /Anders - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
